Data verification method and device, internet of things equipment, electronic equipment and storage medium

Abstract

This disclosure discloses a data verification method and apparatus, an IoT device, an electronic device, and a storage medium, relating to the field of IoT technology. The method includes: sending M IoT data points collected by the IoT device at M time points to a verification platform, wherein before each IoT data point is sent to the verification platform, encrypted data corresponding to the IoT data is determined, where M is a positive integer greater than 1; after determining the encrypted data corresponding to each of the M IoT data points, generating signature information to be verified for each of the M IoT data points; and sending the signature information to be verified to the verification platform so that the verification platform can verify the M IoT data points based on the signature information to be verified. The data verification method provided in this disclosure can reduce the requirements for the computing power and storage capacity of IoT devices, and is particularly suitable for IoT devices with low computing power and low cache.

Description

Technical Field

[0001] This disclosure relates to the field of Internet of Things (IoT) technology, specifically to a data verification method and apparatus, IoT devices, electronic devices, and computer-readable storage media. Background Technology

[0002] With the rapid development of network technology, Internet of Things (IoT) devices are becoming increasingly mature. Correspondingly, analyzing industry or asset data collected by IoT devices is gradually becoming a research hotspot. To ensure the accuracy of the analysis, the reliability of the source data from the IoT is crucial.

[0003] Traditional data verification methods often require IoT devices to have strong computing and storage capabilities. However, when the computing and / or storage capabilities of IoT devices are limited (such as when the IoT device is a sensor device with low cache and low computing power), traditional data verification methods are difficult to implement. Summary of the Invention

[0004] In view of this, the present disclosure provides a data verification method and apparatus, an Internet of Things (IoT) device, an electronic device, and a computer-readable storage medium to address the problem of how to perform data verification when the computing power and / or storage capacity of IoT devices are limited.

[0005] Firstly, a data verification method is provided for use with Internet of Things (IoT) devices. The method includes: sending M IoT data points collected by the IoT device at M time points to a verification platform, wherein before each IoT data point is sent to the verification platform, encrypted data corresponding to the IoT data is determined, where M is a positive integer greater than 1; after determining the encrypted data corresponding to each of the M IoT data points, generating signature information to be verified corresponding to the M IoT data points; and sending the signature information to be verified to the verification platform so that the verification platform can verify the M IoT data points based on the signature information to be verified.

[0006] Secondly, a data verification method is provided, applied to a verification platform. The verification platform is used to verify IoT data collected by IoT devices. The method includes: receiving M IoT data collected by the IoT device at M time points, where M is a positive integer greater than 1; receiving signature information to be verified corresponding to the M IoT data, wherein the signature information to be verified is generated by the IoT device after determining the encrypted data corresponding to each of the M IoT data, and before each IoT data is sent to the verification platform, the IoT device determines the encrypted data corresponding to the IoT data; and verifying the M IoT data based on the signature information to be verified.

[0007] Thirdly, an Internet of Things (IoT) device is provided, comprising: a first sending module configured to send M IoT data collected by the IoT device at M time points to a verification platform, wherein, before each IoT data is sent to the verification platform, encrypted data corresponding to the IoT data is determined, and M is a positive integer greater than 1; a generation module configured to generate signature information to be verified corresponding to the M IoT data after determining the encrypted data corresponding to each of the M IoT data; and a second sending module configured to send the signature information to be verified to the verification platform, so that the verification platform can verify the M IoT data based on the signature information to be verified.

[0008] Fourthly, a data verification device is provided, applied to a verification platform. The verification platform is used to verify IoT data collected by IoT devices. The device includes: a first receiving module configured to receive M IoT data collected by the IoT device at M time points, where M is a positive integer greater than 1; a second receiving module configured to receive signature information to be verified corresponding to the M IoT data, wherein the signature information to be verified is generated by the IoT device after determining the encrypted data corresponding to each of the M IoT data, and the IoT device determines the encrypted data corresponding to each IoT data before each IoT data is sent to the verification platform; and a verification module configured to verify the M IoT data based on the signature information to be verified.

[0009] Fifthly, an electronic device is provided, comprising: a processor and a memory for storing computer-executable instructions, the processor being configured to execute the computer-executable instructions to implement the methods mentioned in the first and / or second aspects above.

[0010] Sixthly, a computer-readable storage medium is provided that stores instructions which, when executed, enable the implementation of the methods mentioned in the first and / or second aspects above.

[0011] In a seventh aspect, a computer program product is provided, including instructions that, when executed, enable the implementation of the methods mentioned in the first and / or second aspects above.

[0012] The data verification method disclosed herein achieves the goal of timely transmission of collected IoT data to the verification platform by sending M IoT data points collected by an IoT device at M time points to the verification platform, thereby reducing the storage capacity requirements of the IoT device. Furthermore, before each IoT data point is sent to the verification platform, this disclosure separately determines the encrypted data corresponding to that IoT data point, ultimately generating verification signature information for each of the M IoT data points, further reducing the computational power requirements of the IoT device. In addition, this disclosure sends the verification signature information to the verification platform for verification, achieving the goal of accurately verifying the trustworthiness of the IoT data collected by the IoT device using the verification platform. Attached Figure Description

[0013] Figure 1 The diagram shown is a system architecture diagram of an application scenario of the data verification method provided in an embodiment of this disclosure.

[0014] Figure 2 The diagram shown is a flowchart of a data verification method provided in an embodiment of this disclosure.

[0015] Figure 3 The diagram shown is a flowchart of a data verification method provided in another embodiment of this disclosure.

[0016] Figure 4 The diagram shown is a flowchart of a data verification method provided in another embodiment of this disclosure.

[0017] Figure 5 The diagram shown is a structural schematic of an Internet of Things (IoT) device provided in an embodiment of this disclosure.

[0018] Figure 6 The diagram shown is a structural schematic of an Internet of Things (IoT) device provided in another embodiment of this disclosure.

[0019] Figure 7 The diagram shown is a structural schematic of a data verification device provided in an embodiment of this disclosure.

[0020] Figure 8 The diagram shown is a structural schematic of a data verification device provided in another embodiment of this disclosure.

[0021] Figure 9 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0022] The technical solutions of the present disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present disclosure, and not all embodiments.

[0023] With the rapid development of internet technology, the Internet of Things (IoT) and blockchain have attracted much attention. The IoT is a network that extends and expands upon the internet. According to agreed-upon protocols, the IoT connects various types of objects to the internet for information exchange and communication, enabling intelligent identification, location, tracking, monitoring, and management of these objects. Blockchain is a distributed, shared ledger and database with characteristics such as decentralization, immutability, full traceability, accountability, collective maintenance, and transparency. Due to these characteristics, the IoT plus blockchain model has been widely applied in many fields.

[0024] Storing IoT data collected by IoT devices on the blockchain and then using that data for big data analytics is widely used across various industries. For example, it allows for industry or asset analysis by aggregating IoT data collected by distributed IoT devices. However, in many IoT application scenarios, it is crucial to ensure that the source IoT data uploaded to the blockchain is complete and tamper-proof; in other words, the reliability of the source IoT data must be guaranteed.

[0025] Traditional data verification methods rely on asymmetric cryptography and hashing algorithms to encrypt and verify IoT data. While these methods can verify the trustworthiness of IoT data and ensure its reliability, they require IoT devices to perform large number modular multiplication and modular inverse operations. However, when IoT devices have limited computing power and / or storage capacity (e.g., when they are low-cache, low-computing-power sensor devices), traditional data verification methods are difficult to implement.

[0026] To address the aforementioned issues, this disclosure provides a data verification method. By sending M IoT data points collected by an IoT device at M time points to a verification platform, the method achieves timely transmission of the collected IoT data to the verification platform, thereby reducing the storage capacity requirements of the IoT device. Furthermore, before each IoT data point is sent to the verification platform, this disclosure separately determines the corresponding encrypted data, ultimately generating verification signature information for each of the M IoT data points, further reducing the computational power requirements of the IoT device. In addition, this disclosure sends the verification signature information to the verification platform for verification, achieving the goal of accurately verifying the trustworthiness of the IoT data collected by the IoT device using the verification platform.

[0027] The following is combined with Figure 1 An example is given to illustrate the system architecture of the data validation method.

[0028] like Figure 1As shown, the system architecture of the data verification method provided in this embodiment involves an Internet of Things (IoT) device 110, a verification platform 120 that is communicatively connected to the IoT device 110, and a blockchain system 130 that is communicatively connected to the verification platform 120.

[0029] In practical applications, IoT device 110 collects M IoT data points (M being a positive integer greater than 1) at M time points, and then promptly sends each of the M collected IoT data points to verification platform 120. Before each IoT data point is sent to the verification platform, the encrypted data corresponding to each of the M IoT data points is first determined, and a signature information to be verified for each of the M IoT data points is generated. This signature information is then sent to the verification platform for trustworthiness verification. In other words, for each IoT data point collected, IoT device 110 determines the corresponding encrypted data and then sends that IoT data to verification platform 120.

[0030] Accordingly, the verification platform 120 receives M IoT data points collected by the IoT device 110 at M time points, and receives the signature information to be verified corresponding to the M IoT data points. Then, it verifies the feasibility of the M IoT data points based on the signature information to be verified. If the M IoT data points pass verification, they are uploaded to the blockchain system 130 (e.g., a blockchain node in the blockchain system 130). If the M IoT data points fail verification, an untrusted data prompt message is sent to the IoT device 110.

[0031] For example, IoT device 110 refers to a device capable of collecting IoT data and transmitting data with the Internet. In one example, IoT device 110 includes sensor devices. Further considering that IoT device 110 needs to have the ability to communicate and compute with Internet devices, IoT device 110 is a sensor device equipped with chips, such as temperature sensors, humidity sensors, and speed sensors. In one example, verification platform 120 can be a separate server, meaning that the functions of the verification platform are executed by a single server. In another example, verification platform 120 is integrated into blockchain system 130, meaning that the functions of the verification platform can also be implemented using smart contracts deployed in blockchain system 130. The aforementioned smart contract is a set of commitments defined in digital form, including protocols that allow contract participants to execute these commitments. In other words, a smart contract can be understood as a program deployed on a blockchain system that can be automatically executed when the triggering conditions of the smart contract are met.

[0032] Blockchain system 130 is a blockchain system with storage capabilities, used for distributed storage of successfully verified IoT data, thereby providing an accurate foundation for subsequent data analysis and other operations. Furthermore, blockchain system 130 can maintain one or more blockchains (e.g., public blockchain, private blockchain, consortium blockchain, etc.) and includes multiple blockchain nodes to host these one or more blockchains.

[0033] This disclosure utilizes a data verification method that reduces the computational and storage requirements of IoT devices to verify the trustworthiness of IoT data, thereby ensuring the trustworthiness of the data source. Based on this, the successfully verified IoT data is stored in the blockchain system 130, preventing the trusted data from being tampered with after being uploaded to the blockchain, thus providing an accurate foundation for subsequent data analysis.

[0034] The following is combined Figures 2 to 4 The data verification methods mentioned in the embodiments of this disclosure are described in detail.

[0035] Figure 2 The diagram shown is a flowchart illustrating a data verification method provided in an embodiment of this disclosure. Figure 2 As shown, the data verification method mentioned in the embodiments of this disclosure involves IoT devices and verification platforms.

[0036] For IoT devices, the data verification method provided in this disclosure includes the following steps.

[0037] Step S210 involves sending M IoT data points collected at M time points to the verification platform. Before each IoT data point is sent to the verification platform, the corresponding encrypted data is determined, where M is a positive integer greater than 1.

[0038] For example, sending M IoT data points collected at M time points to the verification platform can be performed as follows: the IoT device collects data at preset intervals (e.g., 10 seconds), collecting IoT data of a preset byte length (e.g., 16 bytes or 64 bytes) each time, then encrypts the collected IoT data to obtain the encrypted data corresponding to the IoT data, and immediately sends the IoT data to the verification platform after obtaining the encrypted data.

[0039] In some embodiments, the method for determining the encrypted data corresponding to IoT data mentioned in the above embodiments may be to encrypt the IoT data using a symmetric encryption operator to obtain the encrypted data corresponding to the IoT data.

[0040] The aforementioned symmetric encryption operators can characterize the specific encryption operation process for symmetric encryption. Symmetric encryption refers to an encryption method that uses the same key for both encryption and decryption; it is also known as a single-key algorithm. Symmetric encryption operators include, but are not limited to, DES, 3DES, AES, RC2, RC4, and RC5. Symmetric encryption operators have the advantages of being standardized and fast. Especially compared to traditional data verification methods, the embodiments of this disclosure do not require the use of asymmetric cryptographic algorithms and hash algorithms, avoiding large number modular multiplication and modular inverse operations, thus effectively reducing the computational requirements of IoT devices. Therefore, using symmetric encryption operators to encrypt IoT data can reduce system computational pressure, thereby providing conditions for verifying IoT data generated by micro IoT devices.

[0041] Step S220: After determining the encrypted data corresponding to each of the M IoT data, generate the signature information to be verified corresponding to the M IoT data.

[0042] The aforementioned signature information to be verified is essentially a digital signature, also known as a public-key digital signature. It's a string of numbers that only the sender of the information can generate and that cannot be forged by others. This string also serves as valid proof of the authenticity of the information sent by the sender, and is used to authenticate digital information. In data transmission, there are generally senders and receivers, and the process is bidirectional. Therefore, identity verification is crucial. For the receiver, it's essential to confirm that the data was indeed sent by the original sender. In other words, the two parties in the actual communication are the direct recipients of the communication; there are no proxy objects.

[0043] In other words, the signature information to be verified corresponding to M IoT data points is essentially a string generated based on the encrypted data corresponding to each of the M IoT data points, used to verify whether the sender is the IoT device that collected the M IoT data points. Therefore, after determining the encrypted data corresponding to each of the M IoT data points, generating the signature information to be verified for the M IoT data points can provide a verification basis for subsequent verification of whether the IoT device has been fraudulently proxies.

[0044] Step S230: Send the signature information to be verified to the verification platform so that the verification platform can verify M IoT data based on the signature information to be verified.

[0045] Accordingly, for the verification platform, the data verification method provided in this disclosure includes the following steps.

[0046] Step S240: Receive M IoT data points collected by the IoT device at M time points.

[0047] Step S250: Receive the signature information to be verified corresponding to M IoT data.

[0048] Step S260: Verify M IoT data based on the signature information to be verified.

[0049] For example, the implementation of verifying M IoT data points based on the signature information to be verified can be as follows: The verification platform generates signature information on its side based on a pre-acquired symmetric encryption operator and the M IoT data points. Then, the generated signature information is compared with the received signature information to be verified. If the signature information to be verified matches the signature information on the verification platform, the M IoT data points are considered to have passed verification. In other words, the M IoT data points are considered complete and tamper-proof, and therefore trustworthy. If the signature information to be verified does not match the signature information on the verification platform, the M IoT data points fail verification. In other words, the M IoT data points are considered to have been potentially tampered with or are incomplete, and therefore untrustworthy.

[0050] The specific implementation method for generating signature information on the verification platform mentioned above is the same as the specific implementation method for generating signature information to be verified by IoT devices. That is, after determining the encrypted data corresponding to each of the M received IoT data, signature information on the verification platform corresponding to the M received IoT data is generated.

[0051] The data verification method provided in this disclosure achieves the timely transmission of collected IoT data to the verification platform by sending M IoT data points collected by an IoT device at M time points to the verification platform, thereby reducing the storage capacity requirements of the IoT device. Furthermore, before each IoT data point is sent to the verification platform, this disclosure separately determines the encrypted data corresponding to that IoT data point, ultimately generating verification signature information for each of the M IoT data points, further reducing the computational power requirements of the IoT device. In addition, this disclosure sends the verification signature information to the verification platform for verification, achieving the goal of accurately verifying the trustworthiness of the IoT data collected by the IoT device using the verification platform.

[0052] Down Figure 3 The diagram shown is a flowchart of a data verification method provided in another embodiment. Specifically, the following focuses on the description... Figure 3 The illustrated embodiments and Figure 2 The differences between the embodiments shown are not repeated here, and the similarities are not repeated here.

[0053] like Figure 3 As shown, for IoT devices, in this embodiment of the disclosure, the step of encrypting IoT data using a symmetric encryption operator to obtain the encrypted data corresponding to the IoT data includes the following steps.

[0054] Step S310: If the IoT data is IoT data collected by the IoT device at the earliest time point in the time series, then the IoT data is encrypted using a symmetric encryption operator and a first key to obtain the encrypted data corresponding to the IoT data.

[0055] The purpose of using symmetric encryption operators and a first key to encrypt IoT data collected at the earliest time point in the time series is that the IoT data collected at the earliest time point in the time series can be random, thus providing a good start to ensuring the integrity of M IoT data.

[0056] Step S320: If the IoT data is IoT data collected by the IoT device at a time point other than the earliest in the time series, then the IoT data is encrypted using a symmetric encryption operator and the encrypted data of the previous time point corresponding to the IoT data, to obtain the encrypted data corresponding to the IoT data.

[0057] The purpose of encrypting IoT data collected at a time point other than the earliest in the time series by using symmetric encryption operators and encrypted data corresponding to the previous time point of IoT data is to make the encrypted data at the later time point strongly correlated with the closely related data at the previous time point, thus providing a basis for verifying the integrity of M IoT data.

[0058] It should be noted that in the above-mentioned process of encrypting IoT data, although a first key and a second key are involved, both keys are used for encryption. Correspondingly, if decryption is involved, these two keys are also used. Therefore, it is still a symmetric encryption, only that it uses two keys for symmetric encryption.

[0059] Furthermore, for IoT devices, in this embodiment of the disclosure, the step of generating the signature information to be verified corresponding to M IoT data includes the following steps.

[0060] Step S330: Using the symmetric encryption operator, the second key, and the encrypted data corresponding to the last time point of the time series, generate the signature information to be verified for M IoT data.

[0061] The purpose of generating the signature information to be verified for M IoT data using the symmetric encryption operator, the second key, and the encrypted data corresponding to the last time point of the time series is to further improve the security of symmetric encryption using the second key, and based on a deeper consideration of data security, to ensure that the device that sends the M IoT data to the verification platform is the IoT device that collects the M IoT data, and not other fake proxy devices.

[0062] For the verification platform, in this embodiment of the disclosure, verifying M IoT data based on the signature information to be verified (step S260) includes the following steps.

[0063] Step S340: Based on the first registration key, the second registration key, the symmetric encryption operator, and the received M IoT data, the signature information of the verification platform is generated using the same operation rules as those used by the IoT device to generate the signature information to be verified.

[0064] For example, step S340 can be executed as follows: if the received IoT data is IoT data collected by the IoT device at the earliest time point in the time series, then the received IoT data is encrypted using a symmetric encryption operator and a first registration key to obtain encrypted data corresponding to the IoT data. If the received IoT data is IoT data collected by the IoT device at a time point other than the earliest time point in the time series, then the IoT data is encrypted using a symmetric encryption operator and encrypted data corresponding to the previous time point in the time series to obtain encrypted data corresponding to the IoT data. Finally, signature information for the verification platform corresponding to the M received IoT data is generated using a symmetric encryption operator, a second registration key, and encrypted data corresponding to the last time point in the time series.

[0065] Therefore, it can be seen that using the first key, the second key, and symmetric encryption operators to encrypt M IoT data and generate signature information to be verified can not only avoid the large number modular multiplication and modular inverse operations in asymmetric cryptography and hash algorithms, but also provide a basis for comparison to verify IoT data.

[0066] It should be noted that the first and second registration keys mentioned above are keys that are logically encoded and written into the IoT device during manufacturing, and sent to the verification platform for storage immediately after manufacturing is completed. Correspondingly, the first and second keys are used during the encryption of collected IoT data during the operation of the IoT device. Essentially, if a device has not been tampered with or had its address forged, the first key and the first registration key are the same, and the second key and the second registration key are also the same.

[0067] Step S350: If the signature information to be verified is the same as the signature information on the verification platform, then the M IoT data are determined to have passed verification.

[0068] Step S360: If M IoT data points pass verification, upload the M IoT data points to the blockchain.

[0069] In other words, if the signature information to be verified is different from the signature information on the verification platform, then M IoT data points are determined to have failed verification and cannot be uploaded to the blockchain. The failure of M IoT data points to be verified indicates that the M IoT data points are untrustworthy, that they may have been tampered with, that one of the IoT data points may have been modified, or that the data was not sent by the IoT device that collected the M IoT data points (i.e., the IoT device corresponding to the first registration key and the second registration key). Therefore, the M IoT data points cannot be uploaded to the blockchain.

[0070] In this embodiment, M IoT data points are encrypted using a first key, a second key, and a symmetric encryption operator to generate a signature to be verified. A signature on the verification platform is then generated using the same method as the signature to be verified. This allows the trustworthiness of the M IoT data points to be determined by comparing the signature to be verified with the signature on the verification platform. Since the above process does not involve large number modular multiplication or modular inverse operations, this embodiment can determine the trustworthiness of IoT data with minimal requirements for the computing and storage capabilities of the IoT devices.

[0071] In some embodiments, for IoT devices, the data verification method further includes: releasing the memory occupied by the IoT data in the IoT device after each IoT data is sent to the verification platform.

[0072] For example, one possible way to release the memory occupied by IoT data in an IoT device is to delete the IoT data from the IoT device. Considering the limited storage capacity of IoT devices, the encrypted data of the IoT data has been determined before being sent to the verification platform. Deleting the encrypted data after each IoT data is sent to the verification platform will not affect the data integrity verification and can also release the memory occupied by the IoT device, thereby effectively reducing the memory pressure on the IoT device.

[0073] The following example uses smart contracts within a blockchain system, where sensor devices and verification platforms are integrated, in conjunction with... Figure 4 Further examples are provided.

[0074] like Figure 4 As shown, for sensor devices (which can be considered as IoT devices mentioned in the above embodiments), this disclosure involves the following steps.

[0075] Step S410, at t1, t2......t m Sensor data are collected at time points n1, n2, ..., n. m Where m is a positive integer greater than 1. Where t1, t2, ..., tt... mThe interval between any two adjacent time points is 60 seconds, and the sensor data are n1, n2, ..., n. m Each sensor data point is 64KB.

[0076] Step S420: Encrypt n1 using the AES symmetric encryption operator and the first key K1 to obtain the encrypted data C1 = F(K1, n1) corresponding to t1. Then send the n1 collected at time t1 to the smart contract of the blockchain system, and then delete the sensing data n1 in the sensor device.

[0077] Step S430, for t2......t m Sensor data collected at each time point n2......n m Each sensor data point in the dataset is encrypted using the AES symmetric encryption operator and t. i The time point t before the time point i-1 The corresponding encrypted data C i-1 Encryption is performed to obtain t i Encrypted data C corresponding to the time point i =F(C i-1 n i Where i is a positive integer greater than or equal to 2 and less than or equal to n.

[0078] Step S440, after obtaining t i Encrypted data C corresponding to the time point i After that, t i n collected at time points i The smart contract is sent to the blockchain system, and then the sensor data n is deleted from the sensor device. i .

[0079] Step S450, after obtaining t1, t2......t m The encrypted data C1, C2...C1 corresponding to each time point. m Then, using the AES symmetric encryption operator and the second key K2 to pair C m Encryption is performed to obtain sensor data n1, n2, ..., n m The corresponding signature information to be verified is sign = F(K2, C). m ).

[0080] Step S460: Verify the signature information sign = F(K2, C m The data is sent to the smart contract of the blockchain system so that the smart contract of the blockchain system can verify the sensor data n1, n2...n based on the signature information to be verified. m .

[0081] For smart contracts in a blockchain system, the embodiments disclosed herein involve the following steps.

[0082] Step S470: Receive data from the sensor device at t1, t2...t... m The sensor data collected at each time point is denoted as sensor data n. 1s n 2s ...n ms .

[0083] Step S480: Receive the signature information to be verified: sign = F(K2, C m ).

[0084] Step S490, based on the first registration key K corresponding to the sensor device 1s Second registration key K 2s AES symmetric encryption operator, received sensor data n 1s n 2s ...n ms The signature information (sign) on the verification platform is generated using the generation operation rules of the signature information to be verified. s .

[0085] Specifically, using the AES symmetric encryption operator and the first registration key K1 to pair n 1s Data encryption is performed to obtain the encrypted data C corresponding to t1. 1s =F(K 1s n 1s ). Subsequently, regarding the sensor data n 2s ...n ms Each sensor data point in the dataset is encrypted using the AES symmetric encryption operator and t. i The time point t before the time point i-1 The corresponding encrypted data C i-1s Encryption is performed to obtain t i Encrypted data C corresponding to the time point is =F(C i-1s n is ). After obtaining t1, t2...t m The encrypted data C corresponding to each time point 1s C 2s ......C ms Then, using the AES symmetric encryption operator and the second registration key K2, C is... ms Data encryption is performed to obtain the signature information "sign" from the verification platform. s =F(K 2s C ms ).

[0086] Step S4110, if the signature information to be verified is sign = F(K2, C m (sign information from the verification platform) s =F(K) 2s C ms If the values ​​are the same, then the sensor data n1, n2, ..., n are determined. m Through verification, the sensor data n1, n2......n m Upload to the blockchain.

[0087] Step S4120, if the signature information to be verified is sign = F(K2, C m The signature information (sign) from the verification platform. s =F(K) 2s C ms If they are not the same, then determine the sensing data n1, n2, ..., n. m If the verification fails, a prompt message will be sent to the control terminal corresponding to the sensor device.

[0088] This disclosed embodiment utilizes the advantages of symmetric encryption, such as low memory requirements and low operational burden compared to the signature information to be verified and the signature information on the verification platform. This enables the timely confirmation of the reliability of data collected by sensor devices, thereby ensuring the accuracy of the sensor data uploaded to the blockchain and providing a foundation for subsequent industry analysis.

[0089] The above text combined Figures 2 to 4 The present disclosure describes in detail the method embodiments, which are then combined with the following. Figures 5 to 8 The present disclosure provides a detailed description of the apparatus embodiments. Furthermore, it should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be found in the foregoing method embodiments.

[0090] Figure 5 The diagram shown is a structural schematic of an Internet of Things (IoT) device according to an embodiment of this disclosure. Figure 5 As shown in the embodiments of this disclosure, the IoT device 500 includes a first sending module 510, a generation module 520, and a second sending module 530. Specifically, the first sending module 510 is configured to send M IoT data collected by the IoT device at M time points to a verification platform, wherein, before each IoT data is sent to the verification platform, encrypted data corresponding to the IoT data is determined, and M is a positive integer greater than 1. The generation module 520 is configured to generate signature information to be verified corresponding to the M IoT data after determining the encrypted data corresponding to each of the M IoT data. The second sending module 530 is configured to send the signature information to be verified to the verification platform so that the verification platform can verify the M IoT data based on the signature information to be verified.

[0091] In some embodiments, the generation module 520 is further configured to encrypt the IoT data using a symmetric encryption operator to obtain encrypted data corresponding to the IoT data, and after obtaining the encrypted data corresponding to each of the M IoT data, generate signature information to be verified corresponding to the M IoT data.

[0092] In some embodiments, the generation module 520 is further configured to: if the IoT data is IoT data collected by the IoT device at the earliest time point in the time series, then encrypt the IoT data using a symmetric encryption operator and a first key to obtain encrypted data corresponding to the IoT data; if the IoT data is IoT data collected by the IoT device at a time point other than the earliest time point in the time series, then encrypt the IoT data using a symmetric encryption operator and the encrypted data corresponding to the previous time point in the time series to obtain encrypted data corresponding to the IoT data; and generate M signature information to be verified corresponding to IoT data using a symmetric encryption operator, a second key, and the encrypted data corresponding to the last time point in the time series.

[0093] Figure 6 The diagram shown is a structural schematic of an Internet of Things (IoT) device according to another embodiment of this disclosure. Figure 5 Extending from the illustrated embodiment Figure 6 The illustrated embodiment will be described in detail below. Figure 6 The illustrated embodiments and Figure 5 The differences between the embodiments shown are not repeated here, and the similarities are not repeated here.

[0094] like Figure 6 As shown, the IoT device 500 mentioned in this embodiment of the disclosure also includes a memory release module 610. The memory release module 610 is configured to release the memory occupied by the IoT data in the IoT device after each IoT data is sent to the verification platform.

[0095] In some embodiments, the Internet of Things (IoT) device includes sensor devices in the Internet of Things (IoT).

[0096] Figure 7 The diagram shown is a structural schematic of a data verification device according to an embodiment of this disclosure. This data verification device is applied to a verification platform, which is used to verify IoT data collected by IoT devices. Figure 7As shown in the embodiments of this disclosure, the data verification device 700 includes a first receiving module 710, a second receiving module 720, and a verification module 730. Specifically, the first receiving module 710 is configured to receive M IoT data points collected by the IoT device at M time points, where M is a positive integer greater than 1. The second receiving module 720 is configured to receive signature information to be verified corresponding to the M IoT data points, wherein the signature information to be verified is generated by the IoT device after determining the encrypted data corresponding to each of the M IoT data points. Before each IoT data point is sent to the verification platform, the IoT device determines the encrypted data corresponding to the IoT data point. The verification module 730 is configured to verify the M IoT data points based on the signature information to be verified.

[0097] In some embodiments, the verification module 730 is further configured to generate signature information on the verification platform, compare the signature information to be verified with the signature information on the verification platform, and if the signature information to be verified is the same as the signature information on the verification platform, then determine that M IoT data have passed verification; if the signature information to be verified is different from the signature information on the verification platform, then determine that M IoT data have failed verification.

[0098] Figure 8 The diagram shown is a structural schematic of a data verification device provided in another embodiment of this disclosure. Figure 7 Extending from the illustrated embodiment Figure 8 The illustrated embodiment will be described in detail below. Figure 8 The illustrated embodiments and Figure 7 The differences between the embodiments shown are not repeated here, and the similarities are not repeated here.

[0099] like Figure 8 As shown, the data verification device 700 also includes an on-chain module 810. The on-chain module 810 is configured to upload M IoT data points to the blockchain if the M IoT data points pass verification.

[0100] Figure 9 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this disclosure. Figure 9 The electronic device 900 shown (which may specifically be a computer device) includes a memory 901, a processor 902, a communication interface 903, and a bus 904. The memory 901, processor 902, and communication interface 903 are interconnected via the bus 904.

[0101] The memory 901 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 901 may store a program, and when the program stored in the memory 901 is executed by the processor 902, the processor 902 and the communication interface 903 are used to execute the various steps of the data verification method of the embodiments of this disclosure.

[0102] The processor 902 may be a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), graphics processing unit (GPU), or one or more integrated circuits, used to execute relevant programs to achieve the functions required by the units in the Internet of Things device or data verification apparatus of this disclosure embodiment.

[0103] The processor 902 can also be an integrated circuit chip with signal processing capabilities. In implementation, each step of the data verification method of this disclosure can be completed by the integrated logic circuits in the hardware of the processor 902 or by instructions in software form. The processor 902 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this disclosure. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this disclosure can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory 901. The processor 902 reads the information in the memory 901 and, in conjunction with its hardware, performs the functions required by the units included in the data verification device of this disclosure embodiment, or executes the data verification method of this disclosure method embodiment.

[0104] The communication interface 903 uses transceiver devices, such as, but not limited to, transceivers, to enable communication between the electronic device 900 and other devices or communication networks. For example, sensor data can be acquired through the communication interface 903.

[0105] Bus 904 may include a pathway for transmitting information between various components of electronic device 900 (e.g., memory 901, processor 902, communication interface 903).

[0106] It should be noted that, although Figure 9 The illustrated electronic device 900 only shows the memory, processor, and communication interface. However, those skilled in the art should understand that in specific implementations, the electronic device 900 may also include other devices necessary for normal operation. Furthermore, depending on specific needs, those skilled in the art should understand that the electronic device 900 may also include hardware devices for implementing other additional functions. Moreover, those skilled in the art should understand that the electronic device 900 may only include the devices necessary for implementing the embodiments of this disclosure, and may not necessarily include... Figure 9 All the devices shown.

[0107] In addition to the methods, apparatus, and devices described above, embodiments of this disclosure may also be computer program products, including computer program instructions that, when executed by a processor, cause the processor to perform the various steps of the data verification methods provided in the various embodiments of this disclosure.

[0108] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0109] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions that, when executed by a processor, cause the processor to perform the various steps of the data verification methods provided in the various embodiments of this disclosure.

[0110] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0111] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0112] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0113] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0114] The units described as separate components may or may not be physically separate. 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 units can be selected to achieve the purpose of this embodiment according to actual needs.

[0115] In addition, the functional units in the various embodiments of this disclosure can be integrated into a similar region segmentation unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0116] If the aforementioned functions 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, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

[0117] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A data verification method applied to an Internet of Things (IoT) device, the method comprising: The IoT device collects M IoT data points at M time points and sends them to the verification platform. Before each IoT data point is sent to the verification platform, the encrypted data corresponding to the IoT data is determined. The IoT device collects data at preset time intervals, collecting IoT data of preset byte length each time, and then encrypts the collected IoT data to obtain the encrypted data corresponding to the IoT data. M is a positive integer greater than 1. After determining the encrypted data corresponding to each of the M IoT data, generate the signature information to be verified corresponding to the M IoT data; The signature information to be verified is sent to the verification platform so that the verification platform can verify the M IoT data based on the signature information to be verified. The step of determining the encrypted data corresponding to the IoT data includes: By using symmetric encryption operators and encrypted data from the previous time point corresponding to the IoT data, the IoT data collected at a time point other than the earliest in the time series is encrypted to obtain the encrypted data corresponding to the IoT data.

2. The method according to claim 1, wherein encrypting the IoT data using a symmetric encryption operator to obtain encrypted data corresponding to the IoT data includes: If the IoT data is IoT data collected by the IoT device at the earliest time point in the time series, then the IoT data is encrypted using the symmetric encryption operator and the first key to obtain the encrypted data corresponding to the IoT data. If the IoT data is IoT data collected by the IoT device at a time point other than the earliest in the time series, then the IoT data is encrypted using the symmetric encryption operator and the encrypted data of the previous time point corresponding to the IoT data to obtain the encrypted data corresponding to the IoT data.

3. The method according to claim 1 or 2, wherein generating the signature information to be verified corresponding to the M IoT data includes: Using the symmetric encryption operator, the second key, and the encrypted data corresponding to the last time point in the time series, the signature information to be verified for the M IoT data is generated.

4. The method according to claim 1 or 2, wherein after each IoT data is sent to the verification platform, the memory occupied by the IoT data in the IoT device is released.

5. The method according to claim 1 or 2, wherein the IoT device includes sensor devices in the Internet of Things.

6. A data verification method applied to a verification platform, the verification platform being used to verify IoT data collected by IoT devices, the method comprising: The system receives M IoT data points collected by the IoT device at M time points, where M is a positive integer greater than 1. The system receives signature information to be verified corresponding to the M IoT data points. The signature information to be verified is generated by the IoT device after determining the encrypted data corresponding to each of the M IoT data points. Before each IoT data point is sent to the verification platform, the IoT device determines the encrypted data corresponding to the IoT data point. The IoT device collects data at preset intervals, collecting IoT data of a preset byte length each time, and then encrypts the collected IoT data to obtain the encrypted data corresponding to the IoT data point. Verify the M IoT data based on the signature information to be verified; The step of determining the encrypted data corresponding to the IoT data includes: By using symmetric encryption operators and encrypted data from the previous time point corresponding to the IoT data, the IoT data collected at a time point other than the earliest in the time series is encrypted to obtain the encrypted data corresponding to the IoT data.

7. The method according to claim 6, after verifying the M IoT data based on the signature information to be verified, further comprising: If the M IoT data points are verified, the M IoT data points will be uploaded to the blockchain.

8. An Internet of Things (IoT) device, comprising: The first sending module is configured to send M IoT data collected by the IoT device at M time points to the verification platform respectively. Before each IoT data is sent to the verification platform, the encrypted data corresponding to the IoT data is determined. The IoT device collects data at preset time intervals, and collects IoT data of preset byte length each time. Then, the collected IoT data is encrypted to obtain the encrypted data corresponding to the IoT data. M is a positive integer greater than 1. The generation module is configured to generate the signature information to be verified corresponding to the M IoT data after determining the encrypted data corresponding to each of the M IoT data. The second sending module is configured to send the signature information to be verified to the verification platform, so that the verification platform can verify the M IoT data based on the signature information to be verified. The step of determining the encrypted data corresponding to the IoT data includes: By using symmetric encryption operators and encrypted data from the previous time point corresponding to the IoT data, the IoT data collected at a time point other than the earliest in the time series is encrypted to obtain the encrypted data corresponding to the IoT data.

9. A data verification device applied to a verification platform, the verification platform being used to verify Internet of Things (IoT) data collected by IoT devices, the device comprising: The first receiving module is configured to receive M IoT data points collected by IoT devices at M time points, where M is a positive integer greater than 1. The second receiving module is configured to receive the signature information to be verified corresponding to the M IoT data. The signature information to be verified is generated by the IoT device after determining the encrypted data corresponding to each of the M IoT data. Before each IoT data is sent to the verification platform, the IoT device determines the encrypted data corresponding to the IoT data. The IoT device collects data at preset intervals, collecting IoT data of preset byte length each time, and then encrypts the collected IoT data to obtain the encrypted data corresponding to the IoT data. The verification module is configured to verify the M IoT data based on the signature information to be verified; The step of determining the encrypted data corresponding to the IoT data includes: By using symmetric encryption operators and encrypted data from the previous time point corresponding to the IoT data, the IoT data collected at a time point other than the earliest in the time series is encrypted to obtain the encrypted data corresponding to the IoT data.

10. An electronic device, comprising: processor; as well as A memory storing computer program instructions that, when executed by the processor, cause the processor to perform the method as described in any one of claims 1 to 7.

11. A computer-readable storage medium storing computer program instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1 to 7.

Images