Construction safety data synchronization method and system in closed space weak network environment

Abstract

This invention discloses a method and system for synchronizing construction safety data in a confined space with a weak network environment, belonging to the field of data processing. The method includes: a business terminal collecting and standardizing construction safety data and then caching it locally; intelligently triggering a first synchronization condition based on the local network status between the business terminal and edge nodes to synchronize the data to the edge node cache; the edge nodes triggering a second synchronization condition based on the wide area network status between the edge nodes and the cloud center or a timed period to synchronize the accumulated data to the cloud center in batches; and the cloud center triggering a third synchronization condition at a longer interval to initiate a consistency verification task, correcting missing, redundant, or erroneous data by comparing the full snapshots of the edge nodes with the cloud data, and then reversing the synchronization of the correction results. This invention, through three-level collaboration, network status awareness triggering, and proactive consistency verification, effectively solves the problems of unreliable, inefficient, and difficult-to-guarantee eventual consistency of construction safety data synchronization in confined spaces with weak networks, thus improving the robustness and accuracy of data synchronization.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically to a method and system for synchronizing construction safety data in a confined space with a weak network environment. Background Technology

[0002] In the construction industry, the real-time collection, transmission, and aggregation of construction safety data are crucial for ensuring on-site operational safety and enabling risk warning and process supervision. Traditional data synchronization methods typically rely on a stable network environment, directly uploading data collected by business terminals to a cloud center for processing and storage. However, construction sites are often located in confined spaces with weak network environments, characterized by unstable network conditions, uneven signal coverage, or even network outages. Direct cloud synchronization can easily lead to data loss, synchronization delays, or transmission failures, affecting the integrity, accuracy, and real-time performance of the data.

[0003] Existing technologies often employ local caching, breakpoint resumption, or simple retry mechanisms to address network instability. However, these methods still have significant shortcomings under the complex and ever-changing network conditions at construction sites: First, direct communication between business terminals and the cloud has a low success rate in confined spaces with weak networks, and frequent retries can easily lead to wasted terminal resources and power consumption. Second, the lack of hierarchical data relay and verification mechanisms means that data may be lost or erroneous during transmission due to network jitter or interruptions, and it is difficult to ensure end-to-end data consistency. Furthermore, the lack of effective verification and correction mechanisms for data status synchronization between the cloud and terminals makes it difficult to efficiently locate and repair data inconsistencies, affecting the overall system reliability.

[0004] Therefore, how to construct a construction safety data synchronization method and system that adapts to the weak network environment of a closed space on the construction site and supports efficient and reliable data transmission and consistency maintenance is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] In view of this, the present invention provides a method and system for synchronizing construction safety data in a confined space with a weak network environment. Through a hierarchical synchronization architecture of business terminals, edge nodes, and cloud centers, combined with a multi-synchronization condition triggering mechanism, the timeliness, integrity, and consistency of data synchronization are ensured, thereby improving the reliability of construction safety data management.

[0006] To achieve the above objectives, the present invention adopts the following technical solution: On the one hand, the present invention provides a method for synchronizing construction safety data in a confined space with weak network conditions, comprising: The business terminal collects construction safety data, generates standard construction safety data for each piece of construction safety data, and stores it in the local cache database after synchronization. When the first synchronization condition is detected, the standard construction safety data is synchronized to the built-in cache database of the edge node. After the edge node passes the verification, it sends a feedback signal, and the business terminal updates the data status. The first synchronization condition is triggered based on the local network status between the business terminal and the edge node. When the second synchronization condition is met, the edge node will use the standard construction safety data accumulated in the built-in cache database as batch historical data and initiate synchronization with the cloud center. The second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period is longer than the synchronization period triggered by the first synchronization condition. When the third synchronization condition is met, the cloud center initiates a consistency verification task. The verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center based on the verification result. The synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. After correcting the stored data, the cloud center synchronizes the correction results to the edge nodes and then distributes them to the corresponding business terminals.

[0007] Preferably, the business terminal generates standard construction safety data for each piece of construction safety data, including: The collected raw construction safety data is cleaned, converted in format, and standardized to generate standard construction safety data that conforms to the preset data structure. A unique data identifier, timestamp, and data fingerprint are generated for each piece of the standard construction safety data, and the data fingerprint is calculated using a hash algorithm. The standard construction safety data, the unique data identifier, the timestamp, and the data fingerprint are stored as a single synchronous record in the local cache database.

[0008] Preferably, the triggering logic for the first synchronization condition includes: Real-time monitoring of local network bandwidth, network latency, and network connection stability between business terminals and edge nodes; When the local network bandwidth is greater than or equal to the preset bandwidth threshold, the network latency is less than or equal to the preset latency threshold, and the continuous network connection is stable for a period of time reaching the first preset duration, the first synchronization condition is triggered. If the local network status drops below the preset latency threshold during the synchronization process, the service terminal suspends synchronization and records the interruption position. When the first synchronization condition is met again, the uncompleted standard construction safety data will continue to be synchronized from the interruption position.

[0009] Preferably, the service terminal synchronizes the standard construction safety data to the edge node through the first data channel and the second data channel, and generates a first update log and a second update log respectively; The edge node determines a list of valid standard construction safety data that is not duplicated by checking the first update log and the second update log, and updates the built-in cache database based on the list of valid standard construction safety data.

[0010] Preferably, the cloud center corrects the data based on the verification results, including: If the verification result indicates that data is missing, the corresponding missing data will be extracted from the full snapshot and added to the cloud center storage database. If the verification result indicates data redundancy, delete the redundant data in the cloud center storage database that exceeds the scope of the full snapshot; If the verification result shows that the data content does not match, the corresponding erroneous data in the cloud center storage database will be updated based on the data in the edge node's built-in cache database. If the verification results show that the data is consistent, then the data in the cloud center storage database will remain unchanged.

[0011] Preferably, the edge node performs priority processing on the batch of historical data, including: Standard construction safety data is prioritized based on its business type. When the second synchronization condition is met, standard construction safety data with a priority higher than the preset value are packaged into batch historical data first. When network resources are limited, only standard construction safety data with a priority higher than the preset value is processed, while the remaining standard construction safety data is cached in the built-in cache database and awaits the next synchronization cycle.

[0012] Preferably, the standard construction safety data is encrypted during the synchronization process: Data transmission between the service terminal and the edge node, and between the edge node and the cloud center, all use encrypted channels. The content of the standard construction safety data is encrypted using a symmetric encryption algorithm, and the data digest and verification information are encrypted using an asymmetric encryption algorithm. After receiving the data, the edge node and the cloud center first use the private key to decrypt and obtain the data digest and verification information. After successful verification, they then use the symmetric key to decrypt the data content.

[0013] On the other hand, the present invention also provides a construction safety data synchronization system in a confined space with weak network environment, including: a business terminal, an edge node and a cloud center; The service terminal is used to collect construction safety data, generate standard construction safety data for each piece of construction safety data, and store it in the built-in local cache database after synchronization; it is also used to detect whether the first synchronization condition is met, and when the first synchronization condition is met, synchronize the standard construction safety data in the local cache database to the edge node, receive the verification pass signal returned by the edge node and update the status of the corresponding data; the first synchronization condition is triggered based on the local network status between the service terminal and the edge node. The edge node is equipped with a built-in cache database for receiving and storing standard construction safety data synchronized by the business terminal, verifying the received standard construction safety data and sending a verification pass signal back to the business terminal; it is also used to detect whether a second synchronization condition is met, and when the second synchronization condition is met, it uses the standard construction safety data accumulated in the built-in cache database as batch historical data and initiates synchronization with the cloud center; the second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period corresponding to the second synchronization condition is longer than the synchronization period triggered by the first synchronization condition; The cloud center is used to receive and store batch historical data synchronized by the edge nodes; it is also used to detect whether the third synchronization condition is met, and when the third synchronization condition is met, to start a consistency verification task; the consistency verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the edge node's built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center according to the verification result; the synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. The cloud center is also used to synchronize the correction results to the edge nodes after completing the correction of the stored data; after receiving the correction results, the edge nodes further distribute them to the corresponding business terminals.

[0014] As can be seen from the above technical solution, compared with the prior art, this invention discloses a method and system for synchronizing construction safety data in a confined space with weak network conditions. Through a three-level collaborative synchronization architecture of business terminals, edge nodes, and a cloud center, and by intelligently triggering differentiated synchronization conditions based on the network status of different levels, it achieves hierarchical and time-sharing data transmission. Business terminals can utilize short-term, high-quality local network windows with edge nodes for rapid synchronization, avoiding long waiting times or failures caused by direct connections to the remote cloud center. Edge nodes can temporarily store data when WAN conditions are poor, and then upload it to the cloud center in batches after network recovery or reaching the scheduled period, thereby greatly improving the overall success rate of data upload and the system's robustness to confined space environments with weak network conditions. Furthermore, the cloud center of this invention can obtain full data snapshots from edge nodes for comparison and correction, proactively discovering and repairing data loss, redundancy, or inconsistency problems that may be caused by network interruptions, transmission errors, etc., constructing a reliable closed loop of data from the edge to the cloud. Simultaneously, the correction results can be reverse-synchronized to the terminal, ensuring the consistency of data status across all nodes in the entire link, providing an accurate and reliable data foundation for construction safety management. Furthermore, the service terminal adopts a dual-channel synchronization and breakpoint resume mechanism, improving the reliability and speed of single synchronization. Edge nodes can intelligently package and schedule transmission based on data service priorities, prioritizing the reporting of critical security data when network resources are strained. This design ensures both the timeliness of important information and the rational allocation of limited network bandwidth, achieving an optimal balance between efficiency and resource consumption. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0016] Figure 1 This is a schematic diagram of the process provided by the present invention.

[0017] Figure 2 This is a schematic diagram of the structure provided by the present invention. Detailed Implementation

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

[0019] This invention discloses a method for synchronizing construction safety data in a confined space with a weak network environment, such as... Figure 1 As shown, it includes: The business terminal collects construction safety data, generates standard construction safety data for each piece of construction safety data, and stores it in the local cache database after synchronization. When the first synchronization condition is detected, the standard construction safety data is synchronized to the built-in cache database of the edge node. After the edge node verifies the data, it sends a feedback signal and the business terminal updates the data status. The first synchronization condition is triggered based on the local network status between the business terminal and the edge node. When the second synchronization condition is met, the edge node will use the standard construction safety data accumulated in the built-in cache database as batch historical data and initiate synchronization with the cloud center. The second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period is longer than the synchronization period triggered by the first synchronization condition. When the third synchronization condition is met, the cloud center initiates a consistency verification task. The verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center based on the verification result. The synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. After correcting the stored data, the cloud center synchronizes the correction results to the edge nodes and then distributes them to the corresponding business terminals.

[0020] Furthermore, the business terminal generates standard construction safety data for each piece of construction safety data, including: The collected raw construction safety data undergoes data cleaning, format conversion, and standardization to generate standard construction safety data conforming to a preset data structure. First, a data cleaning process is executed to remove invalid data such as outliers caused by sensor malfunctions, redundant data from repeated collections, and invalid records with incorrect formats. Fluctuating data is calibrated based on reasonable thresholds for the construction scenario to correct deviations. Next, format conversion is performed to uniformly convert heterogeneous data acquired from different acquisition devices and methods into a preset standardized format. Finally, standardization is completed by supplementing missing necessary attribute information according to preset data field specifications, generating standard construction safety data that fully conforms to the system's preset data structure, ensuring data format uniformity and information completeness.

[0021] Each piece of standard construction safety data is assigned a unique data identifier, timestamp, and data fingerprint. The data fingerprint is calculated using a hash algorithm. Specifically, each piece of preprocessed standard construction safety data is assigned a globally unique data identifier. In this embodiment, a combination of equipment number, acquisition time, and serial number is used to determine the data identifier, ensuring that the data can be accurately traced in the fully synchronous link. The precise timestamp of data acquisition is recorded synchronously to provide a time reference for subsequent data time-series sorting and synchronization cycle determination. The complete content of the standard construction safety data is calculated using mainstream hash algorithms such as SHA-256 to generate a unique data fingerprint. This data fingerprint can serve as the core basis for integrity verification during subsequent data transmission, effectively avoiding the risk of tampering during data transmission.

[0022] Standard construction safety data, unique data identifiers, timestamps, and data fingerprints are stored as a single synchronization record in a local cache database. To distinguish between synchronized and unsynchronized data, newly stored records can be marked as awaiting synchronization to edge nodes. This facilitates tracking and updating of data status during subsequent synchronization processes, ensuring the manageability and traceability of the locally cached data.

[0023] Furthermore, the triggering logic for the first synchronization condition includes: Real-time monitoring of local network bandwidth, network latency, and network connection stability between service terminals and edge nodes; specifically, service terminals send lightweight UDP probe packets to edge nodes once per second via an independent heartbeat probe thread to continuously monitor local network bandwidth, network latency, and network connection stability. Bandwidth measurement uses a sliding window algorithm to calculate the effective data throughput over the most recent 10 seconds, excluding jitter values ​​with abnormal increases or decreases; network latency is calculated using the 50th and 95th percentiles of the RTT, reflecting average latency and long-tail latency, respectively; network connection stability is comprehensively evaluated through continuous probe success rate, out-of-order packet rate, and packet loss rate, with the packet loss rate calculated based on the percentage of lost packets over 100 consecutive probe packets.

[0024] The first synchronization condition is triggered when the local network bandwidth is greater than or equal to a preset bandwidth threshold, the network latency is less than or equal to a preset latency threshold, and the duration of a stable continuous network connection reaches a first preset duration. If the local network status drops below the preset latency threshold during synchronization, the service terminal pauses synchronization and records the interruption position. When the first synchronization condition is met again, it resumes synchronization of the standard construction safety data that was not fully transmitted from the interruption position. The preset bandwidth threshold, combined with the requirements for construction safety data transmission, can be set to 1 Mbps and can be dynamically adjusted according to the data type. The preset latency threshold can generally be set to 100 ms to ensure timely data transmission. The first preset duration can be set to 3 seconds to avoid accidental synchronization triggering due to instantaneous network fluctuations.

[0025] Furthermore, the business terminal synchronizes standard construction safety data to the edge node through the first data channel and the second data channel, and generates the first update log and the second update log respectively; Edge nodes determine a list of valid standard construction safety data that is not duplicated by checking the first update log and the second update log, and update the built-in cache database based on the list of valid standard construction safety data.

[0026] In another embodiment, the cloud center corrects the data based on the verification results, including: If the verification result indicates missing data, the corresponding missing data is extracted from the full snapshot and added to the cloud center storage database. Specifically, the specific range of missing data (including data identifier, timestamp range, etc.) is first located through the index information of the full snapshot. Then, the corresponding missing data records are accurately extracted from the full snapshot. After the data fingerprint is verified to be correct, the missing data is added to the cloud center storage database according to the preset data storage structure, and the data storage index table is updated. At the same time, the "data completion" operation log is recorded for traceability.

[0027] If the verification result indicates data redundancy, redundant data exceeding the scope of the full snapshot in the cloud center storage database will be deleted. Specifically, data exceeding the scope of the full snapshot (i.e., data deleted or expired by edge nodes) will be marked as "pending deletion" and retained for a 14-day observation period. If no objection is received from edge nodes or business terminals during the observation period, it will be converted to physical deletion; if an objection is received, it will be immediately rolled back to the state before logical deletion and manual verification will be triggered. Physical deletion adopts a segmented cleanup strategy, limiting the number of rows affected by each deletion operation to no more than 10,000, and automatically triggering database snapshot backups before and after deletion. For redundant data with foreign key relationships, the system will initiate cascading detection, automatically generate a cascading impact analysis report, and execute cascading deletion only when the impact scope is controllable; otherwise, it will be converted to manual intervention. The entire deletion operation is written to the audit log, recording the operator, deletion time, data fingerprint, deletion reason, and backup storage path to meet security and compliance requirements.

[0028] If the verification result indicates a data mismatch, the corresponding erroneous data in the cloud center storage database is updated based on the data in the edge node's built-in cache database. Specifically, the difference repair process is initiated based on the data in the edge node's built-in cache database. First, specific discrepancies are located through fine-grained field comparison, generating a detailed list of differences. For inconsistencies in non-critical fields, incremental updates are performed directly, only updating the discrepancies to reduce database locking time. For critical security fields, a full replacement is performed, triggering version number increments to identify the data change trajectory. Before the update, a transaction isolation mechanism is activated, using a repeatable read isolation level to lock the record to be updated, preventing concurrent modifications. After the update, the data fingerprint is recalculated and compared with the edge node snapshot to ensure repair accuracy. If the repair fails, the transaction is automatically rolled back, and the record is added to the error isolation area. Automatic repair is paused, awaiting re-push from the edge node or manual intervention. The repair results are synchronously written to the data quality monitoring dashboard, and metrics such as mismatch rate, repair success rate, and average repair time are statistically analyzed.

[0029] If the verification results show that the data is consistent, then the data in the cloud center storage database will remain unchanged.

[0030] In another embodiment, the edge nodes prioritize batch historical data, including: Standard construction safety data is prioritized based on its business type. Specifically, edge nodes first identify the core business types of construction safety data and then assign priority levels based on the data's impact on construction safety management. For example, data directly related to construction safety red lines, such as records of hidden danger investigations in high-risk areas, equipment operating parameters exceeding limits, and records of personnel violating regulations, are classified as first-level priority. Routine environmental monitoring data and daily inspection records without abnormalities are classified as second-level priority. Non-core safety-related data, such as construction progress auxiliary data and routine equipment maintenance records, are classified as third-level priority. Priority preset values ​​are also set.

[0031] When the second synchronization condition is met, standard construction safety data with a priority higher than the preset value are packaged into batch historical data first. When network resources are limited, only standard construction safety data with a priority higher than the preset value is processed, while the rest of the standard construction safety data is cached in the built-in cache database to wait for the next synchronization cycle.

[0032] In another embodiment, standard construction safety data is encrypted during the synchronization process: Data transmission between business terminals and edge nodes, and between edge nodes and the cloud center, all use encrypted channels. The data transmission links between business terminals and edge nodes, and between edge nodes and the cloud center, all use SSL / TLS protocols to build encrypted channels. Through processes such as identity authentication and key negotiation, the security of the transmission links is ensured, and data is prevented from being eavesdropped on or intercepted during transmission.

[0033] Symmetric encryption algorithms are used to encrypt the content of standard construction safety data, while asymmetric encryption algorithms are used to encrypt the data digest and verification information. Different encryption strategies are employed for different parts of the standard construction safety data: for large amounts of standard construction safety data, the AES-256 symmetric encryption algorithm is used, which is highly efficient and resource-saving, meeting the needs of efficient transmission of construction safety data; for the data digest and verification information, the RSA-2048 asymmetric encryption algorithm is used. Utilizing the "public key encryption, private key decryption" characteristic of asymmetric encryption, the authenticity and uniqueness of the verification information are ensured, preventing tampering.

[0034] After receiving data, edge nodes and cloud centers first use their private keys to decrypt the data to obtain a data digest and verification information. Once the verification is successful, they then use their symmetric keys to decrypt the data content.

[0035] On the other hand, the present invention also provides a construction safety data synchronization system for a confined space with weak network conditions, such as... Figure 2 As shown, it includes: business terminals, edge nodes, and cloud center; The business terminal is used to collect construction safety data, generate standard construction safety data for each piece of construction safety data, and store it in the built-in local cache database after synchronization; it is also used to detect whether the first synchronization condition is met. When the first synchronization condition is met, the standard construction safety data in the local cache database is synchronized to the edge node, the verification pass signal returned by the edge node is received, and the status of the corresponding data is updated; the first synchronization condition is triggered based on the local network status between the business terminal and the edge node. The edge node has a built-in cache database for receiving and storing standard construction safety data synchronized by business terminals, verifying the received standard construction safety data and sending a verification pass signal back to the business terminals; it is also used to detect whether the second synchronization condition is met. When the second synchronization condition is met, the standard construction safety data accumulated in the built-in cache database is used as batch historical data and synchronization is initiated with the cloud center; the second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period corresponding to the second synchronization condition is longer than the synchronization period triggered by the first synchronization condition. The cloud center is used to receive and store batch historical data synchronized by edge nodes; it is also used to detect whether the third synchronization condition is met. When the third synchronization condition is met, a consistency verification task is initiated. The consistency verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the edge node's built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center based on the verification result. The synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. The cloud center is also used to synchronize the correction results to the edge nodes after the correction of the stored data is completed; after receiving the correction results, the edge nodes further distribute them to the corresponding business terminals.

[0036] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to the method section.

[0037] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for synchronizing construction safety data in a confined space with a weak network environment, characterized in that, include: The business terminal collects construction safety data, generates standard construction safety data for each piece of construction safety data, and stores it in the local cache database after synchronization. When the first synchronization condition is detected, the standard construction safety data is synchronized to the built-in cache database of the edge node. After the edge node passes the verification, it sends a feedback signal, and the business terminal updates the data status. The first synchronization condition is triggered based on the local network status between the business terminal and the edge node. When the second synchronization condition is met, the edge node will use the standard construction safety data accumulated in the built-in cache database as batch historical data and initiate synchronization with the cloud center. The second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period is longer than the synchronization period triggered by the first synchronization condition. When the third synchronization condition is met, the cloud center initiates a consistency verification task. The verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center based on the verification result. The synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. After correcting the stored data, the cloud center synchronizes the correction results to the edge nodes and then distributes them to the corresponding business terminals.

2. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, The business terminal generates standard construction safety data for each piece of construction safety data, including: The collected raw construction safety data is cleaned, converted in format, and standardized to generate standard construction safety data that conforms to the preset data structure. A unique data identifier, timestamp, and data fingerprint are generated for each piece of the standard construction safety data, and the data fingerprint is calculated using a hash algorithm. The standard construction safety data, the unique data identifier, the timestamp, and the data fingerprint are stored as a single synchronous record in the local cache database.

3. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, The triggering logic for the first synchronization condition includes: Real-time monitoring of local network bandwidth, network latency, and network connection stability between business terminals and edge nodes; When the local network bandwidth is greater than or equal to the preset bandwidth threshold, the network latency is less than or equal to the preset latency threshold, and the continuous network connection is stable for a period of time reaching the first preset duration, the first synchronization condition is triggered. If the local network status drops below the preset latency threshold during the synchronization process, the service terminal suspends synchronization and records the interruption position. When the first synchronization condition is met again, the uncompleted standard construction safety data will continue to be synchronized from the interruption position.

4. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, The business terminal synchronizes the standard construction safety data to the edge node through the first data channel and the second data channel, and generates the first update log and the second update log respectively; The edge node determines a list of valid standard construction safety data that is not duplicated by checking the first update log and the second update log, and updates the built-in cache database based on the list of valid standard construction safety data.

5. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, The cloud center corrects the data based on the verification results, including: If the verification result indicates that data is missing, the corresponding missing data will be extracted from the full snapshot and added to the cloud center storage database. If the verification result indicates data redundancy, delete the redundant data in the cloud center storage database that exceeds the scope of the full snapshot; If the verification result shows that the data content does not match, the corresponding erroneous data in the cloud center storage database will be updated based on the data in the edge node's built-in cache database. If the verification results show that the data is consistent, then the data in the cloud center storage database will remain unchanged.

6. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, The edge node performs priority processing on the batch of historical data, including: Standard construction safety data is prioritized based on its business type. When the second synchronization condition is met, standard construction safety data with a priority higher than the preset value are packaged into batch historical data first. When network resources are limited, only standard construction safety data with a priority higher than the preset value is processed, while the remaining standard construction safety data is cached in the built-in cache database and awaits the next synchronization cycle.

7. The method for synchronizing construction safety data in a confined space with a weak network environment according to claim 1, characterized in that, During the synchronization process, the standard construction safety data is encrypted. Data transmission between the service terminal and the edge node, and between the edge node and the cloud center, all use encrypted channels. The content of the standard construction safety data is encrypted using a symmetric encryption algorithm, and the data digest and verification information are encrypted using an asymmetric encryption algorithm. After receiving the data, the edge node and the cloud center first use the private key to decrypt and obtain the data digest and verification information. After successful verification, they then use the symmetric key to decrypt the data content.

8. A construction safety data synchronization system for a confined space with weak network conditions, characterized in that, include: Business terminals, edge nodes, and cloud centers; The service terminal is used to collect construction safety data, generate standard construction safety data for each piece of construction safety data, and store it in the built-in local cache database after synchronization; it is also used to detect whether the first synchronization condition is met, and when the first synchronization condition is met, synchronize the standard construction safety data in the local cache database to the edge node, receive the verification pass signal returned by the edge node and update the status of the corresponding data; the first synchronization condition is triggered based on the local network status between the service terminal and the edge node. The edge node is equipped with a built-in cache database for receiving and storing standard construction safety data synchronized by the business terminal, verifying the received standard construction safety data and sending a verification pass signal back to the business terminal; it is also used to detect whether a second synchronization condition is met, and when the second synchronization condition is met, it uses the standard construction safety data accumulated in the built-in cache database as batch historical data and initiates synchronization with the cloud center; the second synchronization condition is triggered based on the wide area network status between the edge node and the cloud center or a preset time period, and the synchronization period corresponding to the second synchronization condition is longer than the synchronization period triggered by the first synchronization condition; The cloud center is used to receive and store batch historical data synchronized by the edge nodes; it is also used to detect whether the third synchronization condition is met, and when the third synchronization condition is met, to start a consistency verification task; the consistency verification task is used to obtain a full snapshot of standard construction safety data of a specified time period or type from the edge node's built-in cache database, compare the full snapshot with the corresponding data already stored in the cloud center, obtain the verification result, and then correct the data already stored in the cloud center according to the verification result; the synchronization period corresponding to the third synchronization condition is longer than the synchronization period corresponding to the second synchronization condition. The cloud center is also used to synchronize the correction results to the edge nodes after the correction of the stored data is completed; After receiving the correction result, the edge node further distributes it to the corresponding service terminal.

Images