Engineering delivery data security verification system based on blockchain

Abstract

The present invention relates to the field of data processing technology, and in particular to a blockchain-based engineering delivery data security verification system, comprising: a data acquisition module for collecting engineering delivery data in an engineering project database and storing it in a corresponding block of a blockchain; a data processing module connected to the data acquisition module for processing the engineering delivery data to output a delivery record; a storage module including a storage unit for storing the engineering delivery data, the hash value, and the delivery record; a verification module connected to the storage module for verifying the hash value to determine user access rights; and a control module for adjusting the cleaning frequency of historical delivery records when the stability of security verification is determined to be unsatisfactory according to the variance of feature data verified in the delivery record. The present invention achieves an improvement in the stability of security verification.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a blockchain-based engineering delivery data security verification system. Background Art

[0002] In the existing technology, blockchain is a decentralized, distributed ledger technology that ensures the immutability of data through the consensus mechanism and encryption algorithm of blockchain. Blockchain technology provides a reliable basis for the verification and storage of project delivery data and ensures the security of data. In the process of secure verification of project delivery data, the integrity and traceability of delivery records can be ensured, and a transparent audit path can be provided. Smart contracts in blockchain can automatically execute contract terms in the project delivery process, improve efficiency and reduce disputes.

[0003] Chinese Patent Publication No.: CN107609874A discloses a transaction log data verification method and verification system, including: a storage module, storing all transaction log data and transaction log data Hash value; a first acquisition module, acquiring all transaction log data; a calculation module, calculating the latest transaction log data Hash value according to all transaction log data; a second acquisition module, reading the stored latest transaction log data Hash value; a determination module, determining whether the calculated latest transaction log data Hash value is consistent with the read latest transaction log data Hash value; a first output module, responding to the calculated latest transaction log data Hash value being consistent with the read latest transaction log data Hash value, determining that the transaction log data has not been tampered with. It can be seen that the transaction log data verification method and verification system have the problem that the system fails to clean up the existing problematic data in time, resulting in a decrease in data quality, resulting in bugs when processing the data, and then causing the blockchain nodes to fail to operate normally, thereby causing the stability of security verification to decrease. Summary of the invention

[0004] To this end, the present invention provides a blockchain-based engineering delivery data security verification system to overcome the problem in the prior art that the system fails to clean up existing problematic data in a timely manner, resulting in a decline in data quality, causing bugs when processing data, and further causing the blockchain nodes to be unable to operate normally, thereby causing a decline in the stability of security verification.

[0005] To achieve the above-mentioned purpose, the present invention provides a blockchain-based project delivery data security verification system, comprising: a data acquisition module, used to collect the project delivery data in the project database and store it in the corresponding block of the blockchain; a data processing module, which is connected to the data acquisition module, used to process the project delivery data to output a delivery record, including a calculation unit for performing hash calculation on the project delivery data to output a hash value and a compression unit for compressing the project delivery data; a storage module, which is respectively connected to the data acquisition module and the data processing module, including a storage unit for storing the project delivery data, the hash value and the delivery record. A unit and a data cleaning unit connected to the storage unit for clearing historical delivery records; a verification module, which is connected to the storage module and verifies the hash value to determine the user access rights; a control module, which is respectively connected to the data acquisition module, the data processing module, the storage module and the verification module, and is used to adjust the cleaning frequency of historical delivery records or adjust the storage capacity of blocks according to the average throughput of blockchain nodes when the stability of security verification is determined to be unsatisfactory according to the variance of feature data verified in the delivery record, and adjust the compression rate of engineering delivery data in combination with the average throughput of the several blockchain nodes and the proportion of the number of times the access verification fails.

[0006] Furthermore, the verification module includes:

[0007] A permission control unit, used to control the user's access permission level according to the user's management priority information;

[0008] A verification unit is connected to the authority control unit and is used to verify the access authority.

[0009] Further, the control module is used to calculate the variance of the verification-passed feature data in the delivery record according to the number of verification-passed delivery records in a number of verification cycles, and to determine that the stability of the safety verification does not meet the requirements when the variance of the verification-passed feature data in the delivery record satisfies the first variance condition or the second variance condition;

[0010] Among them, the first variance condition is that the variance of the verified feature data in the delivery record is greater than the preset first variance and less than or equal to the preset second variance; the second variance condition is that the variance of the verified feature data in the delivery record is greater than the preset second variance.

[0011] Furthermore, the control module is used to verify in the delivery record that when the variance of the feature data only satisfies the first variance condition, it is preliminarily determined that the interaction validity of the delivery record does not meet the requirements, and to make a secondary determination on whether the interaction validity of the delivery record meets the requirements based on the average throughput of several blockchain nodes.

[0012] Further, the control module is used to increase the cleaning frequency of the historical delivery records when the variance of the feature data in the delivery records only satisfies the second variance condition;

[0013] The increase in the cleaning frequency of the historical delivery records is determined by the difference between the variance of the verified feature data in the delivery records and a preset second variance.

[0014] Further, the control module is used to make a second determination that the interaction validity of the delivery record does not meet the requirement when the average throughput of the plurality of blockchain nodes meets the first throughput condition or the second throughput condition, and to make a preliminary determination that the control validity of the access rights does not meet the requirement when the average throughput of the plurality of blockchain nodes only meets the second throughput condition, and to make a second determination on whether the control validity of the access rights meets the requirement according to the proportion of the number of failed access verifications;

[0015] The control module is used to reduce the storage capacity of the block when the average throughput of the plurality of blockchain nodes only meets the first throughput condition;

[0016] Among them, the first throughput condition is that the average throughput of several blockchain nodes is greater than the preset first throughput and less than or equal to the preset second throughput; the second throughput condition is that the average throughput of several blockchain nodes is greater than the preset second throughput.

[0017] Furthermore, the reduction extent of the storage capacity of the block is determined by the difference between an average throughput of a number of blockchain nodes and a preset first throughput.

[0018] Furthermore, the calculation formula for the average throughput of the several blockchain nodes is:

[0019]

[0020] Among them, Z is the average throughput of several blockchain nodes, X a is the throughput of engineering payment data of the a-th blockchain node, n is the number of blockchain nodes, and n is a natural number greater than or equal to 1.

[0021] Furthermore, the control module is used to re-determine that the control effectiveness of the access rights does not meet the requirements when the proportion of the number of times the access verification fails is greater than a preset proportion, and to increase the compression rate of the project delivery data.

[0022] Furthermore, the increase in the compression rate of the engineering delivery data is determined by the difference between the proportion of the number of times the access verification fails and a preset proportion.

[0023] Compared with the prior art, the beneficial effect of the present invention lies in that the system of the present invention adjusts the cleaning frequency of historical delivery records according to the variance of the feature data verified in the delivery records by setting a data acquisition module, a data processing module, a storage module, a verification module and a control module. Since the system fails to clean up the existing problematic data in time, the data quality is reduced, resulting in bugs when processing the data, which in turn causes the nodes of the blockchain to be unable to operate normally, thereby reducing the number of verification passes. By increasing the cleaning frequency of historical delivery records, the cumulative number of problematic data in the system is reduced, and the number of data verification passes is increased. By adjusting the storage capacity of the block according to the average throughput of several blockchain nodes, due to the decentralized nature of the blockchain, the data of each node has certain inconsistencies, leading to This leads to insufficient real-time monitoring of the deployment environment, which in turn leads to inappropriate configuration of the deployment environment, and then problems in the operation of smart contracts, which in turn leads to reduced throughput of blockchain nodes. By reducing the storage capacity of blocks, the delay in data synchronization is reduced, and the processing speed of the entire blockchain is improved. By adjusting the compression rate of project delivery data according to the proportion of failed access verifications, some historical data has not been cleaned up in a timely manner, and long-term operation has led to insufficient storage capacity, resulting in damaged integrity of access control-related data, unreasonable allocation of access rights, and then problems in the access rights control process, resulting in a reduction in the number of access verifications passed. By increasing the compression rate of project delivery data, the storage space occupied is effectively reduced, the integrity of the data is improved, and the stability of security verification is improved.

[0024] Furthermore, the system of the present invention adjusts the frequency of clearing historical delivery records by setting a preset first variance and a preset second variance. Since the system fails to clean up existing problematic data in a timely manner, data quality is reduced, resulting in bugs when processing data, which in turn causes the nodes of the blockchain to be unable to operate normally, resulting in a reduction in the number of passed verifications. By increasing the frequency of clearing historical delivery records, the cumulative number of problematic data in the system is reduced, the number of data verification passes is increased, and the stability of security verification is further improved.

[0025] Furthermore, the system of the present invention adjusts the storage capacity of the block by setting a preset first throughput and a preset second throughput. Due to the decentralized nature of the blockchain, there is a certain inconsistency in the data of each node, resulting in insufficient real-time monitoring of the deployment environment, inappropriate configuration of the deployment environment, and further problems in the operation of the smart contract, which leads to a reduction in the throughput of the blockchain node. By reducing the storage capacity of the block, the delay in data synchronization is reduced, the processing speed of the entire blockchain is improved, and the stability of security verification is further improved.

[0026] Furthermore, the system of the present invention adjusts the compression rate of the project delivery data by setting a preset ratio. Since some historical data has not been cleaned up in time, long-term operation has led to insufficient storage capacity, which has damaged the integrity of access control related data and caused unreasonable allocation of access rights, which in turn has led to problems in the access rights control process, resulting in a decrease in the number of access verifications passed. By increasing the compression rate of the project delivery data, the storage space occupied is effectively reduced, the integrity of the data is improved, and the stability of security verification is further improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is an overall structural block diagram of a blockchain-based engineering delivery data security verification system according to an embodiment of the present invention;

[0028] Figure 2 This is a specific structural block diagram of a data processing module of a blockchain-based engineering delivery data security verification system according to an embodiment of the present invention;

[0029] Figure 3 This is a specific structural block diagram of a storage module of a blockchain-based engineering delivery data security verification system according to an embodiment of the present invention;

[0030] Figure 4 This is a specific structural block diagram of the verification module of the blockchain-based engineering delivery data security verification system in an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to make the objects and advantages of the present invention more clearly understood, the present invention is further described below in conjunction with embodiments; it should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0032] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

[0033] It should be noted that, in the description of the present invention, terms such as "up", "down", "left", "right", "inside" and "outside" indicating directions or positional relationships are based on the directions or positional relationships shown in the drawings. This is merely for the convenience of description and does not indicate or imply that the device or element must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation on the present invention.

[0034] In addition, it should be noted that in the description of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For those skilled in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0035] See also Figure 1 , Figure 2 , Figure 3 as well as Figure 4 As shown, they are respectively the overall structural block diagram of the engineering delivery data security verification system based on blockchain in an embodiment of the present invention, the specific structural block diagram of the data processing module, the specific structural block diagram of the storage module, and the specific structural block diagram of the verification module. The present invention is a system for secure verification of engineering delivery data based on blockchain, including:

[0036] The data collection module is used to collect the project delivery data in the project database and store it in the corresponding block of the blockchain;

[0037] A data processing module, which is connected to the data acquisition module and is used to process the project delivery data to output a delivery record, including a calculation unit for performing hash calculation on the project delivery data to output a hash value and a compression unit for compressing the project delivery data;

[0038] A storage module, which is connected to the data acquisition module and the data processing module respectively, and includes a storage unit for storing the project delivery data, the hash value and the delivery record, and a data cleaning unit connected to the storage unit for clearing historical delivery records;

[0039] A verification module, connected to the storage module, which verifies the hash value to determine the user's access rights;

[0040] A control module, which is respectively connected to the data acquisition module, the data processing module, the storage module and the verification module, and is used to adjust the cleaning frequency of historical delivery records or adjust the storage capacity of blocks according to the average throughput of blockchain nodes when it is determined that the stability of security verification does not meet the requirements based on the variance of feature data verified in the delivery records, and adjust the compression rate of engineering delivery data in combination with the average throughput of the several blockchain nodes and the proportion of the number of times the access verification fails.

[0041] Specifically, project payment data includes payment amount, fund payment time, and contract validity date of project payment.

[0042] Specifically, the delivery records include the number of parties involved, the time of project inspection, and the time points of project progress.

[0043] Specifically, historical delivery records include historical hash values, historical payment times, and historical payment amounts.

[0044] Specifically, the process of verification to determine the user's access rights is to query the blockchain for user permissions, compare the queried information with the user information stored in the blockchain, and if the information is the same, the access rights verification is successful.

[0045] Specifically, the storage capacity of the block is monitored by the security verification system through the amount of data stored in the blockchain. If the storage capacity of the current block exceeds the threshold, the storage capacity of the block is automatically adjusted.

[0046] Specifically, the characteristic data includes the start time of the project, the end time of the project, and the construction data of the project.

[0047] Specifically, the hash value is a unique identifier output by the hash algorithm for the engineering payment data.

[0048] Specifically, a hash algorithm is an algorithm that maps data of arbitrary length into a fixed-length hash value, including MD5, SHA-1, and SHA-256.

[0049] Specifically, the throughput of a blockchain node refers to the speed at which a single blockchain node processes data.

[0050] In implementation, the system of the present invention sets a data acquisition module, a data processing module, a storage module, a verification module and a control module, and adjusts the cleaning frequency of historical delivery records according to the variance of the feature data that has passed the verification in the delivery records. Since the system fails to clean up the existing problematic data in time, the data quality is reduced, resulting in bugs when processing the data, which in turn causes the nodes of the blockchain to fail to operate normally, thereby reducing the number of verification passes. By increasing the cleaning frequency of historical delivery records, the cumulative number of problematic data in the system is reduced, and the amount of data verification passes is increased. By adjusting the storage capacity of the block according to the average throughput of several blockchain nodes, due to the decentralized nature of the blockchain, there is a certain inconsistency in the data of each node, which leads to the deployment environment. Insufficient real-time monitoring leads to inappropriate configuration of the deployment environment, which in turn causes problems in the operation of smart contracts, resulting in a decrease in the throughput of blockchain nodes. By reducing the storage capacity of blocks, the delay in data synchronization is reduced, and the processing speed of the entire blockchain is improved. The compression rate of project delivery data is adjusted according to the proportion of failed access verifications. Since some historical data has not been cleaned up in a timely manner, long-term operation has led to insufficient storage capacity, resulting in damaged integrity of access control-related data, unreasonable allocation of access rights, and problems in the access rights control process, resulting in a decrease in the number of access verifications passed. By increasing the compression rate of project delivery data, the storage space occupied is effectively reduced, the integrity of the data is improved, and the stability of security verification is improved.

[0051] Specifically, the verification module includes:

[0052] A permission control unit, used to control the user's access permission level according to the user's management priority information;

[0053] A verification unit is connected to the authority control unit and is used to verify the access authority.

[0054] Specifically, the user's management priority information includes management personnel information, review personnel information, and construction personnel information.

[0055] Specifically, the control module is used to calculate the variance of the verification-passing feature data in the delivery record according to the number of verification-passing feature data in the delivery record within a number of verification cycles, and to determine that the stability of the safety verification does not meet the requirements when the variance of the verification-passing feature data in the delivery record satisfies the first variance condition or the second variance condition;

[0056] Among them, the first variance condition is that the variance of the verified feature data in the delivery record is greater than the preset first variance and less than or equal to the preset second variance; the second variance condition is that the variance of the verified feature data in the delivery record is greater than the preset second variance.

[0057] It can be understood that the three intervals corresponding to the preset first variance Q1 and the preset second variance Q2 correspond to three situations respectively. The first situation is Q≤Q1, and the stability of the security verification is judged to meet the requirements; the second situation is Q1<Q≤Q2, the blockchain has the decentralized characteristics, resulting in certain inconsistencies in the data of each node, which leads to a reduction in the throughput of the blockchain node; the third situation is Q>Q2, the system fails to clean up the existing problematic data in time, resulting in bugs when processing the data, which in turn causes the blockchain nodes to fail to operate normally, resulting in a reduction in the number of verifications passed. In practice, the range of Q1 is generally [0.6, 0.7], and the range of Q2 is generally [0.75, 0.85].

[0058] Preferably, the first variance Q1 is preset to be 0.65, and the second variance Q2 is preset to be 0.8.

[0059] Specifically, the variance of the verified feature data in the delivery record is denoted as Q.

[0060] Specifically, the variance of the verified feature data in the delivery record is the variance of the verified feature data in the delivery record within several verification cycles. The method for calculating the variance of the verified feature data in the delivery record is a conventional technical means well known to those skilled in the art. Therefore, the calculation process of the variance of the verified feature data in the delivery record will not be repeated here.

[0061] Specifically, the formula for calculating the percentage of delivery records that have passed verification is:

[0062]

[0063] Among them, G is the percentage of delivery records that have passed verification, K1 is the number of delivery records that have passed verification, and K2 is the total number of delivery records that have been verified.

[0064] In implementation, the system of the present invention determines the stability of security verification by setting a preset first variance and a preset second variance, thereby reducing the impact of decreased verification stability of the security verification system due to inaccurate determination of the stability of security verification, and further improving the stability of security verification.

[0065] Specifically, the control module is used to verify in the delivery record that when the variance of the feature data only satisfies the first variance condition, it is preliminarily determined that the interaction validity of the delivery record does not meet the requirements, and a secondary determination is made on whether the interaction validity of the delivery record meets the requirements based on the average throughput of several blockchain nodes.

[0066] Specifically, the control module is used to increase the cleaning frequency of historical delivery records when verifying in the delivery records that the variance of the feature data only satisfies the second variance condition.

[0067] Specifically, the increase in the cleaning frequency of the historical delivery records is determined by the difference between the variance of the verified feature data in the delivery records and a preset second variance.

[0068] Specifically, the calculation formula for the cleanup frequency of the increased historical delivery records is:

[0069]

[0070] Among them, V' is the increased cleaning frequency of historical delivery records, V is the current cleaning frequency of historical delivery records, A is the minimum unit variance for adjusting the cleaning frequency of historical delivery records, and v is the cleaning frequency of historical delivery records when the variance of the verified feature data in the delivery record is the minimum unit variance.

[0071] In practice, the value of A is generally 0.4 to 0.6, and preferably, the preferred embodiment of A is 0.5.

[0072] In implementation, the optional range of the value of v is [3 times / h, 5 times / h]. Preferably, when the cleaning frequency of historical delivery records is less than 4 times / h, the number of verification passes may be reduced. Therefore, the preferred embodiment of v is 4 times / h.

[0073] Specifically, when the value of V' is a decimal, the value of V' is automatically rounded up to an integer.

[0074] For example, the project delivery data security verification system based on blockchain is used to verify the project delivery data, where V = 2 times / h, Q = 0.9, and the calculation is

[0075] In implementation, the system of the present invention adjusts the frequency of cleaning up historical delivery records by setting a preset first variance and a preset second variance. Since the system fails to clean up existing problematic data in a timely manner, the data quality is reduced, resulting in bugs when processing the data, which in turn causes the nodes of the blockchain to be unable to operate normally, resulting in a reduction in the number of verification passes. By increasing the frequency of cleaning up historical delivery records, the cumulative number of problematic data in the system is reduced, the number of data verification passes is increased, and the stability of security verification is further improved.

[0076] Specifically, the control module is used to make a second determination that the interaction validity of the delivery record does not meet the requirement when the average throughput of the plurality of blockchain nodes meets the first throughput condition or the second throughput condition, and to make a preliminary determination that the control validity of the access rights does not meet the requirement when the average throughput of the plurality of blockchain nodes only meets the second throughput condition, and to make a second determination on whether the control validity of the access rights meets the requirement according to the proportion of the number of failed access verifications;

[0077] The control module is used to reduce the storage capacity of the block when the average throughput of the plurality of blockchain nodes only meets the first throughput condition;

[0078] Among them, the first throughput condition is that the average throughput of several blockchain nodes is greater than the preset first throughput and less than or equal to the preset second throughput; the second throughput condition is that the average throughput of several blockchain nodes is greater than the preset second throughput.

[0079] It can be understood that the three intervals corresponding to the preset first throughput P1 and the preset second throughput P2 correspond to three situations respectively. The first situation is P≤P1, and the interactive validity of the secondary judgment delivery record meets the requirements; the second situation is P1<P≤P2, the blockchain has the decentralized characteristics, resulting in certain inconsistencies in the data of each node, which leads to a decrease in the throughput of the blockchain node; the third situation is P>P2, some historical data has not been cleaned up in time, and long-term operation leads to insufficient storage capacity, resulting in damage to the integrity of access control related data, resulting in a decrease in the number of access verification passes. In practice, the range of P1 is generally [400Byte / s, 600Byte / s], and the range of P2 is generally [650Byte / s, 750Byte / s].

[0080] Preferably, the first throughput P1 is preset to be 500 Byte / s, and the second throughput P2 is preset to be 700 Byte / s.

[0081] Specifically, the average throughput of several blockchain nodes is denoted as P.

[0082] In implementation, the system of the present invention performs a secondary determination on the interactive validity of the delivery record by setting a preset first throughput and a preset second throughput, thereby reducing the impact of the decreased stability of security verification due to inaccurate secondary determination of the interactive validity of the delivery record, and further improving the stability of security verification.

[0083] Specifically, the reduction extent of the storage capacity of the block is determined by the difference between the average throughput of several blockchain nodes and a preset first throughput.

[0084] Specifically, the calculation formula for the storage capacity of the reduced block is:

[0085]

[0086] Among them, H' is the reduced storage capacity of the block, H is the current storage capacity of the block, B is the minimum unit throughput for adjusting the storage capacity of the block, and h is the storage capacity of the block when the average throughput of several blockchain nodes is the minimum unit throughput.

[0087] In practice, the value of B is generally 500 Byte / s to 700 Byte / s. Preferably, the preferred embodiment of B is 600 Byte / s.

[0088] In implementation, the optional value range of h is [4MB, 6MB]. Preferably, when the storage capacity of the block is less than 5MB, it may cause operation jams, so the preferred embodiment of h is 5MB.

[0089] For example, the project delivery data security verification system based on blockchain is used to verify the project delivery data, where H = 10MB, P = 800Byte / s,

[0090] Calculated

[0091] In implementation, the system of the present invention adjusts the storage capacity of the block by setting a preset first throughput and a preset second throughput. Due to the decentralized nature of the blockchain, there is a certain inconsistency in the data of each node, resulting in insufficient real-time monitoring of the deployment environment, inappropriate configuration of the deployment environment, and further problems in the operation of the smart contract, which leads to a reduction in the throughput of the blockchain node. By reducing the storage capacity of the block, the delay in data synchronization is reduced, the processing speed of the entire blockchain is improved, and the stability of security verification is further improved.

[0092] Specifically, the calculation formula for the average throughput of the several blockchain nodes is:

[0093]

[0094] Among them, Z is the average throughput of several blockchain nodes, X a is the throughput of engineering payment data of the a-th blockchain node, n is the number of blockchain nodes, and n is a natural number greater than or equal to 1.

[0095] Specifically, the control module is used to re-determine that the control effectiveness of the access rights does not meet the requirements when the proportion of the number of times that the access verification fails is greater than a preset proportion, and to increase the compression rate of the project delivery data.

[0096] It can be understood that the two intervals corresponding to the preset proportion Y0 correspond to two situations. The first situation is Y≤Y0, and the secondary determination of the control effectiveness of the access rights meets the requirements; the second situation is Y>Y0, some historical data is not cleaned up in time, and the long-term operation leads to insufficient storage capacity, resulting in the integrity of the access control related data being damaged, which leads to a decrease in the number of access verification passes. In practice, Y0 is generally selected in the range of [0.3, 0.5].

[0097] Preferably, the preset proportion Y0=0.4.

[0098] Specifically, the percentage of times that access verification fails is recorded as Y.

[0099] Specifically, the calculation formula for the percentage of failed access verifications is:

[0100]

[0101] Among them, Y is the proportion of access verification failures, T1 is the number of access verification failures, and T2 is the total number of accesses.

[0102] In implementation, the system of the present invention performs a secondary determination on the effectiveness of control of access rights by setting a preset ratio, thereby reducing the impact of decreased stability of security verification due to inaccurate secondary determination on the effectiveness of control of access rights, and further improving the stability of security verification.

[0103] Specifically, the increase in the compression rate of the project delivery data is determined by the difference between the proportion of the number of times the access verification fails and a preset proportion.

[0104] Specifically, the calculation formula for the compression rate of the increased project delivery data is:

[0105]

[0106] Among them, L' is the compression rate of the increased project delivery data, L is the compression rate of the current project delivery data, C is the minimum unit ratio for adjusting the compression rate of the project delivery data, and l is the compression rate of the project delivery data when the number of times the access verification fails is the minimum unit ratio.

[0107] In practice, the value of C is generally 0.4 to 0.6, and preferably, the preferred embodiment of C is 0.5.

[0108] In implementation, the optional value range of l is [50%, 70%]. Preferably, when the compression rate of the project delivery data is greater than 60%, it may cause insufficient storage capacity, so the preferred embodiment of l is 60%.

[0109] For example, the project delivery data security verification system based on blockchain is used to verify the project delivery data, where L = 70%, Y = 0.6, and the calculation is

[0110] During implementation, the system of the present invention adjusts the compression rate of the project delivery data by setting a preset ratio. Since some historical data has not been cleaned up in time, long-term operation has led to insufficient storage capacity, which has damaged the integrity of access control related data and caused unreasonable allocation of access rights, which in turn led to problems in the access rights control process, resulting in a decrease in the number of access verifications passed. By increasing the compression rate of the project delivery data, the storage space occupied is effectively reduced, the integrity of the data is improved, and the stability of security verification is further improved.

[0111] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.

Claims

1. A blockchain-based engineering delivery data security verification system, characterized in that: include: The data collection module is used to collect the project delivery data in the project database and store it in the corresponding block of the blockchain; A data processing module, which is connected to the data acquisition module and is used to process the project delivery data to output a delivery record, including a calculation unit for performing hash calculation on the project delivery data to output a hash value and a compression unit for compressing the project delivery data; A storage module, which is connected to the data acquisition module and the data processing module respectively, and includes a storage unit for storing the project delivery data, the hash value and the delivery record, and a data cleaning unit connected to the storage unit for clearing historical delivery records; A verification module, connected to the storage module, which verifies the hash value to determine the user's access rights; A control module, which is respectively connected to the data acquisition module, the data processing module, the storage module and the verification module, and is used to adjust the cleaning frequency of historical delivery records or adjust the storage capacity of blocks according to the average throughput of blockchain nodes when it is determined that the stability of security verification does not meet the requirements based on the variance of feature data verified in the delivery records, and adjust the compression rate of engineering delivery data in combination with the average throughput of several blockchain nodes and the proportion of the number of times the access verification fails.

2. According to the blockchain-based engineering delivery data security verification system of claim 1, it is characterized in that: The verification module comprises: A permission control unit, used to control the user's access permission level according to the user's management priority information; A verification unit is connected to the authority control unit and is used to verify the access authority.

3. The blockchain-based engineering delivery data security verification system according to claim 1 is characterized in that: The control module is used to calculate the variance of the verification-passing feature data in the delivery record according to the number of verification-passing delivery records in a number of verification cycles, and to determine that the stability of the safety verification does not meet the requirements when the variance of the verification-passing feature data in the delivery record satisfies the first variance condition or the second variance condition; Among them, the first variance condition is that the variance of the verified feature data in the delivery record is greater than the preset first variance and less than or equal to the preset second variance; the second variance condition is that the variance of the verified feature data in the delivery record is greater than the preset second variance.

4. The blockchain-based engineering delivery data security verification system according to claim 3 is characterized in that: The control module is used to verify in the delivery record that when the variance of the feature data only satisfies the first variance condition, preliminarily determine that the interaction validity of the delivery record does not meet the requirements, and make a secondary determination on whether the interaction validity of the delivery record meets the requirements based on the average throughput of several blockchain nodes.

5. The blockchain-based engineering delivery data security verification system according to claim 4 is characterized in that: The control module is used to increase the cleaning frequency of the historical delivery records when verifying in the delivery records that the variance of the characteristic data only satisfies the second variance condition; The increase in the cleaning frequency of the historical delivery records is determined by the difference between the variance of the verified feature data in the delivery records and a preset second variance.

6. The blockchain-based engineering delivery data security verification system according to claim 5 is characterized in that: The control module is used to make a second determination that the interaction validity of the delivery record does not meet the requirement when the average throughput of the plurality of blockchain nodes meets the first throughput condition or the second throughput condition, and to make a preliminary determination that the control validity of the access rights does not meet the requirement when the average throughput of the plurality of blockchain nodes only meets the second throughput condition, and to make a second determination on whether the control validity of the access rights meets the requirement according to the proportion of the number of failed access verifications; The control module is used to reduce the storage capacity of the block when the average throughput of the plurality of blockchain nodes only meets the first throughput condition; Among them, the first throughput condition is that the average throughput of several blockchain nodes is greater than the preset first throughput and less than or equal to the preset second throughput; the second throughput condition is that the average throughput of several blockchain nodes is greater than the preset second throughput.

7. The blockchain-based engineering delivery data security verification system according to claim 6 is characterized in that: The reduction extent of the storage capacity of the block is determined by the difference between the average throughput of several blockchain nodes and a preset first throughput.

8. The blockchain-based engineering delivery data security verification system according to claim 7 is characterized in that: The calculation formula for the average throughput of the several blockchain nodes is: Among them, Z is the average throughput of several blockchain nodes, X a is the throughput of engineering payment data of the a-th blockchain node, n is the number of blockchain nodes, and n is a natural number greater than or equal to 1.

9. The blockchain-based engineering delivery data security verification system according to claim 8 is characterized in that: The control module is used to secondarily determine that the control effectiveness of the access authority does not meet the requirements when the proportion of the number of times that the access verification fails is greater than a preset proportion, and to increase the compression rate of the project delivery data.

10. The blockchain-based engineering delivery data security verification system according to claim 9 is characterized in that: The increase in the compression rate of the engineering delivery data is determined by the difference between the proportion of the number of times the access verification fails and a preset proportion.

Images