Blockchain-based intelligent internet of things device data storage transmission system and method

Abstract

The application relates to the field of data transmission, in particular to a smart Internet of Things equipment storage data transmission system and method based on a blockchain, which comprises an edge relay module, a cloud coordination module, a local update module, a verification encryption module and a distributed recovery module; the edge relay module is used for setting an edge communication gateway; the cloud coordination module is used for verifying and forwarding an encrypted data packet; the local update module is used for version marking and common dependent data confirmation; the verification encryption module is used for querying data availability; and the distributed recovery module is used for recovery and reconstruction when data is lost; the application realizes encryption and authentication of Internet of Things data through dynamic local data indexing, stores the data in a decentralized manner in a device network, can improve data security, reduces the probability of Internet of Things data being leaked or maliciously attacked in the cloud, and enhances the decentralized fault tolerance function of the Internet of Things system.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data transmission, in particular to a blockchain-based intelligent Internet of Things device storage data transmission system and method. BACKGROUND

[0002] Intelligent Internet of Things data is a type of data collected by Internet of Things devices, transmitted through cloud or edge computing nodes, and can be converted into instructions to feed back to other Internet of Things devices. The amount of Internet of Things data is huge, the format is various, and the storage system requires high scalability. The life cycle from generation, transmission, storage, processing to destruction is longer, and it is more vulnerable to external attacks or leaks, so it needs a security processing solution different from traditional distributed storage systems.

[0003] Most of the security transmission solutions of Internet of Things devices rely on encryption, identity verification, virtual isolation and other services provided by the cloud. However, cloud service providers or cloud attackers can provide false service interfaces to intercept Internet of Things devices, causing security vulnerabilities of Internet of Things data. Even if the data is communicated through a multi-cloud distributed collaboration method, due to the consistency of data characteristics, it can be easily identified through data trajectory analysis, and multiple clouds will greatly reduce the data transmission efficiency.

[0004] In addition, the data stored in the Internet of Things identification may be partially lost due to damage and interference, and additional backup data will greatly reduce the security of data storage. Most Internet of Things terminal devices have weak computing power and limited power, and cannot run complex security backup protocols, so they cannot balance the reliability and security of data well. SUMMARY

[0005] The purpose of the present application is to provide a blockchain-based intelligent Internet of Things device storage data transmission system and method to solve the problems raised in the background.

[0006] In order to solve the above technical problems, the present application provides the following technical scheme: a blockchain-based intelligent Internet of Things device storage data transmission system, comprising: an edge relay module, a cloud coordination module, a local update module, a verification encryption module, and a distributed recovery module.

[0007] The edge relay module is used to set up an edge communication gateway in the Internet of Things device. The gateway has sensing and execution capabilities and has the required storage space for operation. The gateway maintains real-time link with the cloud through wireless signals and connects with the Internet of Things device through short-range communication. It receives the Internet of Things data obtained by the Internet of Things device sensors, divides the Internet of Things data into local data and communication data, and stores the local data in the edge communication gateway in the format of a dynamic distributed index table.

[0008] The cloud coordination module is configured to establish a gateway registry in the cloud, receive and process a data transmission request generated by a source gateway, and obtain index ciphertext by splitting and shuffling a data packet using a local data index table. The cloud forwards the encrypted index ciphertext between the source gateway and a destination gateway, restores the original data packet at the destination gateway based on the locally dependent data, and confirms the data synchronization status of both parties.

[0009] The local update module is configured to generate new local data by a one-way update function based on a random hash of the current communication after the communication is successful, mark the newly generated local data with a version, and update the marked data to the local of each gateway, so that the locally dependent data between the gateways is updated following the version mark, and the local data is stored in each IoT device by the virtualization engine. When verifying the data, the locally dependent data is confirmed based on the minimum version mark of the local data of the communication parties, and the locally dependent data of the corresponding version is used as the data packet unpacking index.

[0010] The verification encryption module is configured to query data availability, verify the integrity of the communication data, determine the consistency of the data features and the marking features of the communication parties, continue the process if the consistency is met, and abort the transmission if the consistency is not met. After completing the data transmission, the destruction process is triggered to delete all temporary data related to the current transmission, except for the communication log.

[0011] The distributed recovery module is configured to report the lost index table shard version interval to the cloud when part of the data of the IoT device is lost, determine the data coverage source based on the communication log of the local data, extract the shard copy with the missing version interval from each IoT device of the corresponding source, and verify the data authenticity. After the verification is passed, the data is recovered using the remaining local data as the index to rebuild the lost part of the index table locally.

[0012] Further, the edge relay module includes a communication gateway unit and a signal linkage unit.

[0013] The communication gateway unit constitutes a lightweight edge node with computing, storage, and communication capabilities, and is configured to participate in the distributed storage of local data segments.

[0014] The signal linkage unit is configured to control the wireless network communication between the cloud and the gateway, and the short-distance communication between the IoT device and the gateway. The short-distance communication methods include Zigbee, LoRaWAN, and Bluetooth.

[0015] Further, the cloud coordination module includes a data transmission unit and an index shuffling unit.

[0016] The data transmission unit is used to maintain the identity public key certificate and network address of all gateways, and establish a gateway registration table;

[0017] The index scrambling unit is used to receive and store scrambled data packets, and forward encrypted data packets between source gateways and sink gateways.

[0018] Further, the local update module includes a data marking unit, a distributed storage unit and a version verification unit;

[0019] The data marking unit is used to assign an incremental version mark to each piece of data in the local index table, and the version mark contains the position index of the common dependent data;

[0020] The distributed storage unit is used to manage the extended local data distributed on various Internet of Things devices, and record the mapping relationship between data blocks and storage device addresses;

[0021] The version verification unit is used to receive and compare the version marks uploaded by the communication gateway of both parties, and determine the common dependent data.

[0022] Further, the verification encryption module includes a consistency authentication unit and a trace destruction unit;

[0023] The consistency authentication unit is used to perform redundant storage and consistency verification of data through erasure code technology, and return the verification result;

[0024] The trace destruction unit is used to trigger and confirm the deletion of all related temporary data in the cloud after the transmission verification is successful.

[0025] Further, the distributed recovery module includes a missing request unit, a source traversal unit and an index recovery unit;

[0026] The missing request unit is used to send a recovery request to the cloud through the gateway when the local data is found to be damaged or the version is lost after the self-check of the Internet of Things device is restarted;

[0027] The source traversal unit is used to piece together the common dependent data in other gateways that have successfully communicated with the gateway according to the communication log until the length of the non-repeated data reaches the threshold;

[0028] The index recovery unit is used to establish a secure cloud recovery channel, and transmit at least one piece of data index between gateways through short-distance communication.

[0029] The smart Internet of Things device storage data transmission method based on blockchain includes the following steps:

[0030] Step S1. Set up an edge communication gateway in the Internet of Things device, which is connected to the cloud through wireless signals and connected to the Internet of Things device through short-range communication, divides the received Internet of Things data into local data and communication data, and stores the local data in the gateway in the format of a dynamic distributed index table;

[0031] Step S2. Establish a gateway registry in the cloud, receive and process data transmission requests generated by the source gateway, split and scramble the communication data packet using the local data index table, perform version verification in the cloud, and forward the encrypted data packet through the blockchain, and unpack the data packet at the sink gateway based on the locally dependent data;

[0032] Step S3. After successful communication, the source gateway and the sink gateway respectively update the local data incrementally, and mark the newly generated local data with a version, so that the locally dependent data between the gateways is updated following the version mark;

[0033] Step S4. When verifying the version, confirm the commonly dependent data according to the minimum version mark of the local data of the communication gateway, use the corresponding commonly dependent data with the minimum version mark as the unpacking index of the communication data packet, and perform data consistency verification;

[0034] Step S5. When some data of the Internet of Things device is lost, the gateway reports the lost index table shard interval to the cloud, and the cloud assembles the commonly dependent data in other gateways that have successfully communicated with the gateway according to the communication log until the length of the non-repeated data reaches a threshold, and reconstructs the lost data locally.

[0035] Further, step S1 includes:

[0036] Step S11. Set up an edge communication gateway in the Internet of Things device or within the communication range of the device, the gateway has sensing and execution capabilities and has the required storage space for operation, constitutes a lightweight edge node with computing, storage and communication capabilities, and is used to participate in distributed storage of local data segments;

[0037] Step S12. Establish a wireless network communication link between the cloud and the gateway, and a short-range communication link between the Internet of Things device and the gateway, the short-range communication includes Zigbee, LoRaWAN and Bluetooth;

[0038] Step S13. Divide the Internet of Things data into local data and communication data, the local data is data that does not need to exchange information with the cloud, and is stored in the edge communication gateway in the format of a dynamic distributed index table, the communication data is data that needs to exchange with the cloud or other Internet of Things devices, and the same initial local data is stored in each gateway before the gateway and the cloud are connected.

[0039] Further, step S2 includes:

[0040] Step S21. The cloud maintains the identity public key certificate and network address of all gateways, and establishes a gateway registration table, acquires the communication request of the source gateway, finds the information sending address in the registration table according to the sink gateway name in the communication request, and informs the local data version of the sink gateway;

[0041] Step S22. The sink gateway randomly intercepts a piece of data as the dependent data of this communication in the fixed length data interval of the local data possessed by both parties according to the local data version of the sink gateway, the same dependent data is transmitted only once in the cloud, and the data packet is processed by using the AES encryption scrambling algorithm with the dependent data as the key, and the processed data packet is sent to the cloud;

[0042] Step S23. The cloud receives and stores the scrambled data packet, forwards the encrypted data packet and data interval position between the source gateway and the sink gateway, restores the original data packet based on the data interval position and the common local data at the sink gateway, and confirms the data synchronization state of both parties.

[0043] Further, step S3 includes:

[0044] Step S31. After the communication is successful, the source gateway and the sink gateway respectively generate new local data by using a one-way update function according to the random hash of this communication, mark the newly generated local data with a version, and update the marked data to the local of each gateway, so that the common dependent local data between the gateways is updated following the version mark;

[0045] Step S32. The extended local data distributed on each Internet of Things device is managed, the mapping relationship between the data block and the storage device address is recorded, and the local data is dispersedly stored in each Internet of Things device through a virtualization engine.

[0046] Further, step S4 includes:

[0047] Step S41. The version mark uploaded by the communication parties is received and compared to determine the common dependent data, the data availability is queried, the integrity of the communication data is verified, the data is redundantly stored and consistency is verified through the erasure code technology, and the verification result is returned, if consistent, the process continues, if inconsistent, the transmission is aborted;

[0048] Step S42. After the data transmission is completed, a destruction process is triggered to delete all temporary data related to this transmission, but the communication log is not included.

[0049] Further, step S5 includes:

[0050] Step S51. When the local data is found to be damaged or the version is lost after the self-check of the Internet of Things equipment restarts, a recovery request is sent to the cloud through the gateway, the cloud determines the data coverage source according to the communication log of the local data, extracts the shard copy with the missing version interval from each Internet of Things equipment corresponding to the source, and performs data authenticity verification respectively;

[0051] Step S52. According to the communication log, the common dependent data is pieced together in other gateways that have successfully communicated with the gateway until the length of the non-repeated data reaches the threshold, a secure cloud recovery channel is established, and at least one data index is transmitted between the gateways through short-distance communication, and the lost data is reconstructed according to the pieced together common dependent data.

[0052] Compared with the prior art, the beneficial effects achieved by the present application are:

[0053] The present application sets up a communication relay gateway in the Internet of Things equipment, the gateway and the cloud transmit through network signals, and the gateway and the Internet of Things equipment are connected through short-distance communication, local data is deployed in each gateway, communication data is split and scrambled through local data index, so that the data always exists in the form of ciphertext during cloud transmission, reducing the probability of leakage or malicious attack of Internet of Things data in the cloud.

[0054] The present application can mark newly generated local data, update the local data along with the data transmission process, and store the local data in the Internet of Things equipment through a virtualization engine, confirm the updated version as index data transmission according to the minimum mark of the local data of the communication parties, realize the encryption and authentication of Internet of Things data through dynamically changing local data index, and design the cloud as an untrusted coordination channel, so that the data is stored in a decentralized manner in the device network, greatly improving the data security.

[0055] The present application can determine the data coverage source from the corresponding source of each Internet of Things equipment according to the communication interval of the local data when part of the local data of the Internet of Things equipment is lost, extract information for data recovery, give the system distributed self-healing ability, enhance the decentralized fault tolerance function of the Internet of Things system, and be suitable for industrial Internet of Things, city Internet of Things and other scenes with high requirements for data security. BRIEF DESCRIPTION OF DRAWINGS

[0056] The accompanying drawings are included to provide a further understanding of the present application, and constitute a part of the specification, together with the embodiments of the present application, to explain the present application, and do not constitute a limitation on the present application. In the drawings:

[0057] Fig. 1 is a structural schematic diagram of the data transmission system of the smart Internet of Things equipment based on the blockchain of the present application;

[0058] Fig. 2is the execution flow schematic diagram of the data transmission system of the blockchain-based intelligent Internet of Things equipment storage of the application;

[0059] Fig. 3 is the step schematic diagram of the data transmission method of the blockchain-based intelligent Internet of Things equipment storage of the application. DETAILED DESCRIPTION

[0060] The technical solutions in the embodiments of the application will be clearly and completely described below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are only part of the embodiments of the application, rather than all the embodiments. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the application.

[0061] Please refer to Figs. 1 to 3 The application provides a technical solution: a blockchain-based intelligent Internet of Things equipment storage data transmission system, comprising: an edge relay module, a cloud coordination module, a local update module, a verification encryption module and a distributed recovery module.

[0062] The edge relay module is used for setting an edge communication gateway in the Internet of Things equipment. The gateway has sensing and execution capabilities and has a storage space required for operation. The gateway keeps real-time linkage with the cloud through wireless signals and is connected with the Internet of Things equipment through short-distance communication. The gateway receives Internet of Things data obtained by the sensors of the Internet of Things equipment, divides the Internet of Things data into local data and communication data, and stores the local data in the edge communication gateway in the format of a dynamic distributed index table. The local data is data that does not need to exchange information with the cloud.

[0063] The edge relay module comprises a communication gateway unit and a signal linkage unit.

[0064] The communication gateway unit constitutes a lightweight edge node with computing, storage and communication capabilities and is used for participating in distributed storage of local data segments.

[0065] The signal linkage unit is used for controlling wireless network communication between the cloud and the gateway and short-distance communication between the Internet of Things equipment and the gateway. The short-distance communication mode includes Zigbee, LoRaWAN and Bluetooth.

[0066] The cloud coordination module is used for establishing a gateway registration table in the cloud, receiving and processing a data transmission request generated by a source gateway and index ciphertext obtained by splitting and scrambling a data packet by using a local data index table, forwarding the encrypted index ciphertext between the source gateway and a sink gateway, restoring the original data packet at the sink gateway based on the locally dependent data, and confirming the data synchronization state of both parties.

[0067] The cloud coordination module comprises a data transmission unit and an index scrambling unit;

[0068] The data transmission unit is configured to maintain the identity public key certificate and network address of all gateways, and establish a gateway registration table;

[0069] The index scrambling unit is configured to receive and store scrambled data packets, and forward encrypted data packets between the source gateway and the sink gateway.

[0070] The local update module is configured to, after successful communication, generate new local data by a one-way update function according to the random hash of this communication, respectively by the source gateway and the sink gateway, mark the newly generated local data with a version, and update the marked data to the local of each gateway, so that the local data commonly relied on by the gateways is updated following the version mark, and the local data is stored in each Internet of Things device by the virtualization engine, and when verifying the data, the commonly relied data is confirmed according to the minimum version mark of the local data of the gateways of the two parties of communication, and the commonly relied data of the corresponding version is used as the data packet unpacking index;

[0071] The local update module comprises a data marking unit, a distributed storage unit and a version verification unit;

[0072] The data marking unit is configured to assign an incremental version mark to each piece of data in the local index table, and the version mark contains the position index of the commonly relied data;

[0073] The distributed storage unit is configured to manage the extended local data distributed in each Internet of Things device, and record the mapping relationship between the data blocks and the storage device addresses;

[0074] The version verification unit is configured to receive and compare the version marks uploaded by the gateways of the two parties of communication, and determine the commonly relied data.

[0075] The verification encryption module is configured to query the data availability, verify the integrity of the communication data, determine the consistency of the data features and the marking features of the two parties of communication, continue the process if the consistency is met, and abort the transmission if the consistency is not met, and trigger the destruction process after completing the data transmission to delete all temporary data related to this transmission, but excluding the communication log;

[0076] The verification encryption module comprises a consistency authentication unit and a trace destruction unit;

[0077] The consistency authentication unit is configured to perform redundant storage and consistency verification of the data by using the erasure code technology, and return the verification result;

[0078] The trace destruction unit is configured to trigger and confirm the deletion of all related temporary data in the cloud after the transmission verification is successful.

[0079] The distribution recovery module is used for reporting the missing index table shard version interval to the cloud by the gateway when part of the data of the Internet of Things device is lost, determining the data coverage source according to the communication log of the local data, extracting the shard copy with the missing version interval from each Internet of Things device corresponding to the source, and performing data authenticity verification respectively, and after the verification, recovering the data with the remaining local data as the index to rebuild the missing index table part locally.

[0080] The distribution recovery module comprises a missing request unit, a source traversal unit and an index recovery unit.

[0081] The missing request unit is used for sending a recovery request to the cloud through the gateway when local data is found to be damaged or the version is missing after the Internet of Things device restarts self-checking.

[0082] The source traversal unit is used for piecing together the commonly dependent data in other gateways that have successfully communicated with the gateway according to the communication log until the length of the non-repeated data reaches the threshold.

[0083] The index recovery unit is used for establishing a secure cloud recovery channel and transmitting at least one data index between the gateways through a short-distance communication mode.

[0084] The smart Internet of Things device storage data transmission method based on a blockchain comprises the following steps:

[0085] Step S1. An edge communication gateway is set in the Internet of Things device, the edge communication gateway is connected with the cloud through wireless signals and connected with the Internet of Things device through short-distance communication, received Internet of Things data is divided into local data and communication data, and the local data is stored in the gateway in the format of a dynamic distributed index table.

[0086] Step S1 comprises:

[0087] Step S11. An edge communication gateway is set in the Internet of Things device or within the communication range of the device, the gateway has sensing and execution capabilities and has the required storage space for running, constitutes a lightweight edge node with computing, storage and communication capabilities, and is used for participating in the distributed storage of local data segments.

[0088] Step S12. A wireless network communication link between the cloud and the gateway and a short-distance communication link between the Internet of Things device and the gateway are established, and the short-distance communication comprises Zigbee, LoRaWAN and Bluetooth.

[0089] Step S13. Divide IoT data into local data and communication data. The local data is data that does not need to be exchanged with the cloud and is stored in the edge communication gateway in the format of a dynamic distributed index table. The communication data is data that needs to be exchanged with the cloud or other IoT devices. Before the gateway establishes a connection with the cloud, the same initial local data is stored in each gateway.

[0090] Step S2. Establish a gateway registry in the cloud, receive and process data transmission requests generated by the source gateway, split and scramble communication data packets using the local data index table, perform version verification in the cloud, forward the encrypted data packets, and unpack them at the destination gateway based on the common local data.

[0091] Step S2 includes:

[0092] Step S21. Maintain the identity public key certificates and network addresses of all gateways in the cloud, establish a gateway registry, obtain the communication requests of the source gateway, find the information sending address in the registry according to the name of the destination gateway in the communication request, and inform the destination gateway of the local data version.

[0093] Step S22. The destination gateway, based on its local data version, randomly extracts a segment of data from the local data available to both communicating parties using a fixed-length data range as the dependency data for the current communication. The same dependency data is transmitted only once in the cloud. The AES encryption scrambling algorithm is used to process the communication data packets using the dependency data as the key, and the processed data packets are sent to the cloud.

[0094] Step S23. The cloud receives and stores the scrambled data packets, forwards the encrypted data packets and data range locations between the source gateway and the destination gateway, restores the original data packets at the destination gateway based on the data range locations and common local data, and confirms the data synchronization status of both parties.

[0095] Step S3. After successful communication, the source gateway and the destination gateway perform incremental updates on the local data respectively, and mark the newly generated local data with version tags so that the local data that the gateways depend on together are updated with the version tags.

[0096] Step S3 includes:

[0097] Step S31. After successful communication, the source gateway and the destination gateway generate new local data according to the random hash of this communication through a one-way update function, mark the version of the newly generated local data, and each gateway updates the marked data to its local data so that the local data that the gateways depend on each other are updated with the version mark.

[0098] Step S32. Manage the extended local data distributed across various IoT devices, record the mapping relationship between data blocks and storage device addresses, and distribute the local data across various IoT devices through a virtualization engine.

[0099] In step S4, during version verification, common dependency data is confirmed based on the minimum version tag of the local data of both communication gateways. The common dependency data corresponding to the minimum version tag is used as the unpacking index of the communication data packet, and data consistency verification is performed.

[0100] Step S4 includes:

[0101] Step S41. Receive and compare the version tags uploaded by the gateways of both communicating parties to determine the common dependent data, query the data availability, verify the integrity of the communication data, perform redundant storage and consistency verification of the data through erasure code technology, and return the verification result. If they are consistent, continue the process; otherwise, stop the transmission.

[0102] Step S42. After the data transmission is completed, trigger the destruction process to delete all temporary data related to this transmission, excluding communication logs.

[0103] Step S5. When some data of the IoT device is lost, the gateway reports the lost index table fragment range to the cloud. The cloud, based on the communication log, pieces together the common dependent data from other gateways that have successfully communicated with the gateway until the length of the non-duplicate data reaches the threshold, and then reconstructs the lost data locally.

[0104] Step S5 includes:

[0105] Step S51. When the IoT device restarts and self-tests and finds that the local data is corrupted or the version is lost, a recovery request is sent to the cloud through the gateway. The cloud determines the source of the data overwrite based on the communication log of the local data, extracts the fragmented copies with the missing version range from each IoT device of the corresponding source, and verifies the authenticity of the data respectively.

[0106] Step S52. Based on the communication log, piece together common dependency data from other gateways that have successfully communicated with the gateway until the length of the non-duplicate data reaches a threshold, establish a secure cloud recovery channel, and transmit at least one data index between gateways through short-distance communication, and reconstruct the lost data based on the pieced-together common dependency data.

[0107] Example: An IoT device collects user sensor information and needs to link with other IoT devices. After sending the sensor information to the edge computing gateway, the gateway encapsulates the sensor information required for the link into a communication data packet, and the remaining information is used as local data. After sending the name of the destination device to the cloud, the cloud returns version tags for both parties. The gateway extracts 20 bits of information from the same local data as a key index and scrambles the communication data packet. After the destination device obtains the data packet, it uses the key index to restore the key in the local data and obtains the original data packet.

[0108] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus.

[0109] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A blockchain-based method for storing and transmitting data in smart IoT devices, characterized in that, The method includes the following steps: Step S1. Set up an edge communication gateway in the IoT device. The edge communication gateway is connected to the cloud via a wireless signal and to the IoT device via a short-range communication connection. The received IoT data is divided into local data and communication data. The local data is stored in the gateway in the format of a dynamic distributed index table. Step S2. Establish a gateway registry in the cloud, receive and process data transmission requests generated by the source gateway, split and scramble communication data packets using the local data index table, perform version verification in the cloud, forward the encrypted data packets, and unpack them at the destination gateway based on the common local data. Step S3. After successful communication, the source gateway and the destination gateway perform incremental updates on the local data respectively, and mark the newly generated local data with version tags so that the local data that the gateways depend on together are updated with the version tags. In step S4, during version verification, common dependency data is confirmed based on the minimum version tag of the local data of both communication gateways. The common dependency data corresponding to the minimum version tag is used as the unpacking index of the communication data packet, and data consistency verification is performed. Step S5. When some data of the IoT device is lost, the gateway reports the lost index table fragment range to the cloud. The cloud, based on the communication log, pieces together the common dependent data from other gateways that have successfully communicated with the gateway until the length of the non-duplicate data reaches the threshold, and then reconstructs the lost data locally. Step S2 includes: Step S21. Maintain the identity public key certificates and network addresses of all gateways in the cloud, establish a gateway registry, obtain the communication requests of the source gateway, find the information sending address in the registry according to the name of the destination gateway in the communication request, and inform the destination gateway of the local data version. Step S22. The destination gateway, based on its local data version, randomly extracts a segment of data from the local data available to both communicating parties using a fixed-length data range as the dependency data for the current communication. The same dependency data is transmitted only once in the cloud. The AES encryption scrambling algorithm is used to process the communication data packets using the dependency data as the key, and the processed data packets are sent to the cloud. Step S23. The cloud receives and stores the scrambled data packets, forwards the encrypted data packets and data range locations between the source gateway and the destination gateway, restores the original data packets at the destination gateway based on the data range locations and common local data, and confirms the data synchronization status of both parties.

2. The method for storing and transmitting data in a blockchain-based smart IoT device according to claim 1, characterized in that: Step S1 includes: Step S11. Set up an edge communication gateway within the IoT device or within the device's communication range. The gateway has sensing and execution capabilities and storage space required for operation, forming a lightweight edge node with computing, storage, and communication capabilities, used to participate in the distributed storage of local data fragments. Step S12. Establish a wireless network communication link between the cloud and the gateway, and a short-range communication link between the IoT device and the gateway. The short-range communication includes Zigbee, LoRaWAN, and Bluetooth. Step S13. Divide IoT data into local data and communication data. The local data is data that does not need to be exchanged with the cloud and is stored in the edge communication gateway in the format of a dynamic distributed index table. The communication data is data that needs to be exchanged with the cloud or other IoT devices. Before the gateway establishes a connection with the cloud, the same initial local data is stored in each gateway.

3. The method for storing and transmitting data in a blockchain-based smart IoT device according to claim 2, characterized in that: Step S3 includes: Step S31. After successful communication, the source gateway and the destination gateway generate new local data according to the random hash of this communication through a one-way update function, mark the version of the newly generated local data, and each gateway updates the marked data to its local data so that the local data that the gateways depend on each other are updated with the version mark. Step S32. Manage the extended local data distributed across various IoT devices, record the mapping relationship between data blocks and storage device addresses, and distribute the local data across various IoT devices through the virtualization engine; Step S4 includes: Step S41. Receive and compare the version tags uploaded by the gateways of both communicating parties to determine the common dependent data, query the data availability, verify the integrity of the communication data, perform redundant storage and consistency verification of the data through erasure code technology, and return the verification result. If they are consistent, continue the process; otherwise, stop the transmission. Step S42. After the data transmission is completed, trigger the destruction process to delete all temporary data related to this transmission, excluding communication logs.

4. The method for storing and transmitting data in a blockchain-based smart IoT device according to claim 3, characterized in that: Step S5 includes: Step S51. When the IoT device restarts and self-tests and finds that the local data is corrupted or the version is lost, a recovery request is sent to the cloud through the gateway. The cloud determines the source of the data overwrite based on the communication log of the local data, extracts the fragmented copies with the missing version range from each IoT device of the corresponding source, and verifies the authenticity of the data respectively. Step S52. Based on the communication log, piece together common dependency data from other gateways that have successfully communicated with the gateway until the length of the non-duplicate data reaches a threshold, establish a secure cloud recovery channel, and transmit at least one data index between gateways through short-distance communication, and reconstruct the lost data based on the pieced-together common dependency data.

5. A blockchain-based smart IoT device storage and data transmission system, wherein the system executes the blockchain-based smart IoT device storage and data transmission method as described in claim 1, characterized in that, The system includes the following modules: edge relay module, cloud coordination module, local update module, verification and encryption module, and distributed recovery module; The edge relay module is used to set up an edge communication gateway within the IoT device. The gateway has sensing and execution capabilities and storage space required for operation. The gateway maintains a real-time connection with the cloud via wireless signals and connects with the IoT device via short-range communication. It receives IoT data acquired by the IoT device's sensors and divides the IoT data into local data and communication data. The local data is data that does not require information exchange with the cloud and is stored in the edge communication gateway in the format of a dynamic distributed index table. The cloud coordination module is used to establish a gateway registry in the cloud, receive and process data transmission requests generated by the source gateway and index ciphertext obtained by splitting and scrambling data packets using a local data index table. The cloud forwards the encrypted index ciphertext between the source gateway and the destination gateway. At the destination gateway, the original data packet is restored based on the local data that they both depend on, and the data synchronization status of both parties is confirmed. The local update module is used to generate new local data by the source gateway and the destination gateway respectively based on the random hash of this communication through a one-way update function after successful communication. The newly generated local data is version-marked, and each gateway updates the marked data to its local data. This ensures that the local data that the gateways depend on each other is updated with the version mark. The local data is distributed and stored in various IoT devices through a virtualization engine. When verifying data, the common dependency data is confirmed based on the smallest version mark of the local data of the two gateways. The common dependency data of the corresponding version is used as the data packet unpacking index. The verification encryption module is used to query data availability, verify the integrity of communication data, and determine the consistency between data characteristics and the marking characteristics of both communicating parties. If they are consistent, the process continues; if they are inconsistent, the transmission is terminated. After the data transmission is completed, a destruction process is triggered to delete all temporary data related to this transmission, excluding communication logs. The distributed recovery module is used to report the lost index table fragment version range to the cloud when some data of IoT devices is lost. The cloud determines the source of data overlay based on the communication log of local data, extracts fragment copies with missing version ranges from each IoT device of the corresponding source, and verifies the authenticity of the data respectively. After the verification is passed, the remaining local data is used as the index to recover the data and reconstruct the lost index table part locally.

6. The blockchain-based smart IoT device storage and data transmission system according to claim 5, characterized in that: The edge relay module includes: a communication gateway unit and a signal link unit; The communication gateway unit constitutes a lightweight edge node with computing, storage and communication capabilities, used to participate in the distributed storage of local data fragments; The signal link unit is used to control wireless network communication between the cloud and the gateway, as well as short-range communication between IoT devices and the gateway. The short-range communication methods include Zigbee, LoRaWAN, and Bluetooth. The cloud coordination module includes: a data transmission unit and an index scrambling unit; The data transmission unit is used to maintain the public key certificates and network addresses of all gateways and to establish a gateway registry. The index scrambling unit is used to receive and store scrambled data packets and forward encrypted data packets between the source gateway and the destination gateway.

7. The blockchain-based smart IoT device storage and data transmission system according to claim 6, characterized in that: The local update module includes: a data tagging unit, a distributed storage unit, and a version verification unit; The data tagging unit is used to assign an incrementing version tag to each piece of data in the local index table, and the version tag contains the location index of common dependent data; The distributed storage unit is used to manage extended local data distributed across various IoT devices and to record the mapping relationship between data blocks and storage device addresses; The version verification unit is used to receive and compare the version tags uploaded by the gateways of both communicating parties to determine common dependency data.

8. The blockchain-based smart IoT device storage and data transmission system according to claim 7, characterized in that: The verification encryption module includes: a consistency authentication unit and a trace destruction unit; The consistency authentication unit is used to perform redundant data storage and consistency verification through erasure code technology, and returns the verification result; The trace destruction unit is used to trigger and confirm the deletion of all relevant temporary data in the cloud after successful transmission verification.

9. The blockchain-based smart IoT device storage and data transmission system according to claim 8, characterized in that: The distributed recovery module includes: a missing request unit, a source traversal unit, and an index recovery unit; The missing request unit is used to send a recovery request to the cloud through the gateway when the IoT device finds that the local data is corrupted or the version is lost after restarting and self-testing. The source traversal unit is used to piece together common dependency data from other gateways that have successfully communicated with the gateway, based on the communication log, until the length of non-duplicate data reaches a threshold. The index recovery unit is used to establish a secure cloud recovery channel and transmit at least one data index between gateways via short-range communication.

Images