Block chain tourism data privacy protection method and system

Abstract

The invention relates to the technical field of block chains, in particular to a block chain tourism data privacy protection method and system, and the method comprises the steps: constructing a distributed cache layer which is disposed between a block chain node and a user terminal, and is used for dynamically capturing the newly-added tourism data of a user, and taking a preset time window or a data size threshold value as a unit; and aggregating the newly added tourism data into a data block group. According to the method, the distributed cache layer is constructed between the block chain node and the user terminal, the newly-added tourism data of the user is aggregated into the data block group according to the preset time window or the data volume threshold value, the situation that a complete privacy protection process is independently executed on each piece of newly-added data is avoided, and repeated operation and verification operation are reduced; double-layer encryption is adopted for a data block group, so that the basic data efficiency is guaranteed through lightweight symmetric encryption, and the group-level metadata security is enhanced through asymmetric encryption; and the fragmented parallel verification is started and the lock-free operation is realized by means of the message queue, so that the verification time is shortened.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of blockchain, in particular to a blockchain tourism data privacy protection method and system. BACKGROUND

[0002] The blockchain technology has gradually been applied to the data management field of the tourism industry due to its characteristics of decentralization, non-tamperability and traceability. Tourism data covers multiple types of sensitive information such as user identity information, travel itinerary, consumption records, accommodation preferences, etc. These data not only relate to the personal privacy and security of users, but also may affect the accurate provision of tourism services and the compliance operation of the industry. At present, the industry often attempts to store and protect tourism data through blockchain technology, hoping to prevent data from being illegally tampered with or leaked by taking advantage of its technical characteristics, and to provide a new solution for the safe management of tourism data.

[0003] In the existing blockchain tourism data privacy protection technology, there is a problem of imbalance between the efficiency and resource consumption of privacy protection processing for dynamically added tourism data. Tourism data is not static and unchangeable. Users will continuously generate new data during the tourism process, such as temporarily added scenic spot reservation records, real-time updated transportation ticket information, etc. When processing these dynamically added data, the existing technology often needs to perform a complete privacy protection process on the added data, including re-encryption operation, node verification and chain storage. This process not only increases the data processing delay, making users unable to obtain or use their latest tourism data in time, but also excessively occupies the computing resources and storage resources of the blockchain network due to repeated operation and verification operations. Especially when the data addition amount is large during the tourism peak period, the imbalance of resource consumption will be more obvious, thereby affecting the stable operation of the entire blockchain tourism data system. SUMMARY

[0004] In view of the deficiencies of the prior art, the present application provides a blockchain tourism data privacy protection method and system, which solves the problem of imbalance between efficiency and resource consumption when processing dynamically added tourism data in the prior art.

[0005] To achieve the above purpose, the present application is implemented by the following technical scheme: a blockchain tourism data privacy protection method, comprising:

[0006] A distributed cache layer is constructed, which is deployed between the blockchain nodes and the user terminals, used to dynamically capture user-added tourism data, and aggregate the added tourism data into a data block group in units of a preset time window or a data volume threshold;

[0007] The data block group is subjected to double-layer encryption processing, which includes applying lightweight symmetric encryption to the basic data in the data block group, and applying asymmetric encryption to the group-level metadata in the data block group;

[0008] submitting the double-encrypted data block group to the blockchain network and starting sharded parallel verification, the sharded parallel verification comprising:

[0009] dividing the verification nodes in the blockchain network into a metadata verification group, a content consistency group, and a permission audit group;

[0010] verifying the source and digital signature of the data block group by the metadata verification group;

[0011] parallelly comparing the hash values of the data in the data block group by the content consistency group;

[0012] synchronously checking the access permission of the user to the data by the permission audit group;

[0013] realizing the lock-free parallel operation between the metadata verification group, the content consistency group, and the permission audit group through a message queue;

[0014] storing the aggregated fingerprint of the data block group on the core blockchain, the aggregated fingerprint containing the data feature digest of the data block group, the user permission marker, and the pointer of the distributed cache layer;

[0015] splitting the double-encrypted original data into data segments and storing the data segments in a lightweight side chain;

[0016] adopting a two-stage consensus mechanism for data processing, the two-stage consensus mechanism comprising:

[0017] in the first stage, the distributed cache layer quickly responds to the request for new tourism data and returns a temporary receiving voucher;

[0018] in the second stage, the final verification and storage of the data block group are completed asynchronously in the background of the blockchain, and the operation frequency of the double encryption and the number of shards of the lightweight side chain are automatically adjusted by a dynamic resource scheduler according to real-time data traffic.

[0019] Further, the construction of the distributed cache layer comprises:

[0020] establishing a distributed cache layer between the blockchain nodes and the user terminals, the distributed cache layer being used as a real-time incremental buffer area for new tourism data;

[0021] the real-time incremental buffer area dynamically receiving real-time new tourism data from the user terminals;

[0022] when the amount of data in the real-time incremental buffer area reaches a preset storage threshold, or when the real-time incremental buffer area has passed a preset time window, the new tourism data in the real-time incremental buffer area is aggregated into a data block group.

[0023] Further, the double-encryption processing of the data block group comprises:

[0024] symmetrically encrypting the base data in the data block group using a first preset key;

[0025] asymmetrically encrypting group-level metadata in the data block group using a second preset key, the group-level metadata including user identity feature information and key operation records;

[0026] triggering a one-time aggregate encryption operation to encrypt the entire data block group only after the data block group is completed.

[0027] Further, the verifying, by the metadata verification group, the origin and digital signature of the data block group comprises:

[0028] the metadata verification group receives the data block group and extracts metadata verification information contained in the data block group;

[0029] verifying the data origin in the metadata verification information to ensure the legality of the data block group;

[0030] verifying the digital signature in the metadata verification information to ensure the integrity and non-repudiation of the data block group.

[0031] Further, the parallel comparing, by the content consistency group, the hash values of the data in the data block group comprises:

[0032] the content consistency group receives the data block group and independently calculates hash values of each data segment in the data block group;

[0033] parallel comparing the independently calculated hash values with a pre-stored hash digest in the data block group;

[0034] confirming the content consistency of the data in the data block group according to the comparison result.

[0035] Further, the synchronously checking, by the permission audit group, the access permission of the user to the data comprises:

[0036] the permission audit group obtains user identity information associated with the data block group and an access request type;

[0037] retrieving the permission rules corresponding to the user from a preset permission management policy;

[0038] synchronously checking whether the user identity has the permission to access or operate the data block group.

[0039] Further, the storing, on the core blockchain, the aggregate fingerprint of the data block group and splitting the double-layer encrypted original data into data segments and storing the data segments in a lightweight side chain comprises:

[0040] uploading the aggregated fingerprint of the data block group to the core blockchain, the aggregated fingerprint serving as a unique identifier of the data block group;

[0041] performing sharding on the double-layer encrypted original data, and storing the sharded data segments off-chain in the lightweight sidechain;

[0042] when the original data needs to be queried, locating the corresponding data segment in the lightweight sidechain through the aggregated fingerprint on the core blockchain, and performing data recombination.

[0043] Further, the when the original data needs to be queried, locating the corresponding data segment in the lightweight sidechain through the aggregated fingerprint on the core blockchain, and performing data recombination includes:

[0044] receiving a data query request issued by a user;

[0045] retrieving an aggregated fingerprint matching the query request in the core blockchain;

[0046] retrieving the corresponding encrypted data segment from the lightweight sidechain according to the pointer information of the distributed cache layer and the data feature digest contained in the aggregated fingerprint;

[0047] decrypting and recombining the retrieved encrypted data segment to restore the original data.

[0048] Further, the according to the real-time data traffic, automatically adjusting the operation frequency of the double-layer encryption and the number of sharding of the lightweight sidechain by the dynamic resource scheduler includes:

[0049] the dynamic resource scheduler monitors the data traffic in the blockchain network in real time;

[0050] when the data traffic is in a non-peak period, the dynamic resource scheduler reduces the operation frequency of the double-layer encryption and reduces the number of sharding of the lightweight sidechain;

[0051] when the data traffic is in a peak period, the dynamic resource scheduler increases the operation frequency of the double-layer encryption and increases the number of sharding of the lightweight sidechain, and simultaneously enables a backup verification node group to assist in processing.

[0052] The application also provides a blockchain tourism data privacy protection system, which implements any one of the above-mentioned blockchain tourism data privacy protection methods, and comprises:

[0053] a data aggregation module configured to construct a distributed cache layer, the distributed cache layer being deployed between a blockchain node and a user terminal, configured to dynamically capture newly added tourism data of a user, and configured to aggregate the newly added tourism data into a data block group in a preset time window or data volume threshold unit.

[0054] The encryption processing module is configured to perform double-layer encryption processing on the data block group, the double-layer encryption processing comprising: applying lightweight symmetric encryption to base data in the data block group, and applying asymmetric encryption to group-level metadata in the data block group;

[0055] The parallel verification module is configured to submit the double-layer encrypted data block group to a blockchain network and start sharded parallel verification, and the parallel verification module comprises:

[0056] The node sharding unit is configured to divide verification nodes in the blockchain network into a metadata verification group, a content consistency group and an authority audit group;

[0057] The collaborative verification unit is configured to check the source and digital signature of the data block group by the metadata verification group, to compare hash values of data in the data block group by the content consistency group in parallel, and to synchronously check access rights of the user to the data by the authority audit group;

[0058] The message queue unit is configured to realize lock-free parallel operation between the metadata verification group, the content consistency group and the authority audit group;

[0059] The cross-chain storage module is configured to store an aggregated fingerprint of the data block group on a core blockchain, the aggregated fingerprint containing a data feature digest of the data block group, a user authority marker and a pointer of a distributed cache layer, and to split original double-layer encrypted data into data segments and store the data segments in a lightweight side chain;

[0060] The consensus optimization module is configured to adopt a two-stage consensus mechanism for data processing, the two-stage consensus mechanism comprising: a first stage in which the distributed cache layer quickly responds to a new tourism data request and returns a temporary receiving voucher, and a second stage in which final verification and storage of the data block group are completed asynchronously in the background of the blockchain;

[0061] The resource scheduling module is configured to automatically adjust an operation frequency of double-layer encryption and a number of shards of the lightweight side chain by a dynamic resource scheduler according to real-time data traffic.

[0062] Compared with the prior art, the present application has the following advantages:

[0063] The application constructs a distributed cache layer between the blockchain node and the user terminal, aggregates the user's new tourism data into a data block group according to a preset time window or a data volume threshold, avoids performing a complete privacy protection process on each new data, reduces repeated operation and verification operations, adopts double-layer encryption for the data block group, guarantees the efficiency of the basic data through lightweight symmetric encryption, and strengthens the security of the group-level metadata through asymmetric encryption, starts a sharded parallel verification, realizes a lock-free operation through a message queue, shortens the verification time consumption, adopts a two-stage consensus mechanism, makes the distributed cache layer quickly respond to the user's request and return a temporary credential, and asynchronously completes the final verification and storage in the background, and adjusts the encryption operation frequency and the side chain shard number according to the real-time traffic through a dynamic resource scheduler, improves the processing capacity during the peak period, and reduces resource waste during the off-peak period. Therefore, the problems of low efficiency and unbalanced resource consumption in processing dynamic tourism data in the prior art are solved, the resource pressure during the tourism peak period is relieved, and the stable operation of the blockchain tourism data system is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0064] Figure 1 The method flowchart of the application;

[0065] Figure 2 The system structure diagram of the application. DETAILED DESCRIPTION

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

[0067] Please refer to Figure 1 The application provides a blockchain tourism data privacy protection method, which comprises the following steps:

[0068] A distributed cache layer is constructed, which is deployed between the blockchain node and the user terminal, is used for dynamically capturing user's new tourism data, and aggregates the new tourism data into a data block group according to a preset time window or a data volume threshold;

[0069] Double-layer encryption processing is performed on the data block group, which comprises the following steps: lightweight symmetric encryption is applied to the basic data in the data block group, and asymmetric encryption is applied to the group-level metadata in the data block group;

[0070] The double-layer encrypted data block group is submitted to the blockchain network, and a sharded parallel verification is started, which comprises the following steps:

[0071] The verification nodes in the blockchain network are divided into a metadata verification group, a content consistency group, and an authority audit group;

[0072] The metadata verification group checks the source and digital signature of the data block group;

[0073] The content consistency group compares the hash values of the data in the data block group in parallel;

[0074] The authority audit group synchronously checks the access rights of the user to the data;

[0075] The metadata verification group, the content consistency group, and the authority audit group are implemented in a lock-free parallel operation through a message queue;

[0076] The aggregated fingerprint of the data block group is stored on the core blockchain, and the aggregated fingerprint includes a data feature digest of the data block group, a user authority marker, and a pointer to the distributed cache layer;

[0077] The double-encrypted original data is split into data segments and stored in a lightweight side chain;

[0078] A two-stage consensus mechanism is used for data processing, which includes:

[0079] In the first stage, the distributed cache layer quickly responds to the request for new tourism data and returns a temporary receiving voucher;

[0080] In the second stage, the final verification and storage of the data block group are completed asynchronously in the background of the blockchain, and the operation frequency of the double encryption and the number of fragments of the lightweight side chain are automatically adjusted by a dynamic resource scheduler according to real-time data traffic.

[0081] Specifically, in the blockchain tourism data privacy protection scenario, a distributed cache layer is first deployed between the blockchain node and the user terminal. The cache layer can capture real-time new data generated by the user during the tourism process, such as temporary scenic spot reservation records and real-time traffic ticket information. To determine the data aggregation trigger condition, the following parameters are set: the cumulative amount of real-time new tourism data in the distributed cache layer is , the preset storage threshold is , the cumulative duration of data received by the cache layer is , and the preset time window is When the condition of formula (1) is met, the cache layer automatically aggregates the scattered new data into a data block group, avoiding the need to perform a complete processing flow on each new data and reducing resource consumption caused by repeated operations.

[0082]

[0083] wherein, the unit of the unit of which is consistent with preset according to system storage capacity; the unit of which is second, the unit of which is consistent with preset according to tourism data addition frequency; represents logical "or" operation, and any condition meets triggers aggregation.

[0084] Double-layer encryption is performed on the aggregated data block group. Lightweight symmetric encryption is used for the basic data in the block group, such as travel route details and consumption amount, to ensure basic privacy while improving encryption efficiency; asymmetric encryption is used for the group-level metadata in the block group, such as user identity features and data upload operation records, to strengthen the security protection of sensitive information.

[0085] After encryption, the data block group is submitted to the blockchain network and parallel verification is started. The verification nodes in the network are divided into metadata verification group, content consistency group and permission audit group. The metadata verification group is responsible for checking whether the source of the data block group is legal and the digital signature is complete. The content consistency group calculates the hash value of each data segment in the block group in parallel and compares it with the pre-stored hash digest (hash value calculation uses existing technology, which is not described here). The permission audit group synchronously checks the access permission of the user to the data block group, and at the same time, through the message queue, the three groups of nodes are realized in a lock-free parallel operation, which greatly shortens the verification time.

[0086] In the storage link, the aggregation fingerprint of the data block group is stored in the core blockchain, which contains data feature digest, user permission mark and distributed cache layer pointer. The original data after double-layer encryption is split into data segments and stored in a lightweight side chain, reducing the storage pressure of the core blockchain.

[0087] A two-stage consensus mechanism is used to process data. When the user initiates a request to add new tourism data, the distributed cache layer responds first and returns a temporary receiving voucher, allowing the user to quickly obtain operation feedback. Subsequently, the final verification and storage of the data block group are completed asynchronously in the background of the blockchain, avoiding user waiting. At the same time, a dynamic resource scheduler monitors network data traffic in real time. To realize dynamic resource adjustment, the following parameters are set: real-time data traffic is , the system preset reference traffic is , the traffic coefficient is , the double-layer encryption basic operation frequency is , the real-time operation frequency is , the lightweight side chain basic number of fragments is , and the real-time number of fragments is . First, calculate the traffic coefficient (normalize the flow to ensure the same dimension), and then the encryption operation frequency and the number of side chain fragments are adjusted through formula (3) and formula (4) respectively.

[0088] Formula (2):

[0089] Formula (3):

[0090] Formula (4):

[0091] wherein, and have the same unit of byte / s; is a dimensionless coefficient, reflecting the ratio of real-time flow to reference flow; and have the same unit of times / s; and are both positive integers. When the data volume surges during the peak travel period, , at this time and correspondingly increase; when the flow is in the off-peak period, , , and correspondingly decrease, realizing the reasonable allocation of resources and solving the problems of low processing efficiency of dynamic data and unbalanced resource consumption in the prior art, and guaranteeing the stable operation of the system.

[0092] In the embodiment, the construction of the distributed cache layer comprises:

[0093] A distributed cache layer is established between the blockchain node and the user terminal, and the distributed cache layer is used as a real-time incremental buffer area of the newly added travel data;

[0094] The real-time incremental buffer area dynamically receives real-time newly added travel data from the user terminal;

[0095] When the data volume in the real-time incremental buffer area reaches a preset storage threshold, or when the real-time incremental buffer area passes through a preset time window, the newly added travel data in the real-time incremental buffer area is aggregated into a data block group.

[0096] Specifically, a distributed cache layer is established between the blockchain node and the user terminal, and the cache layer is used as a real-time incremental buffer area of the newly added travel data, which can continuously receive real-time newly added data sent by the user terminal, including but not limited to hotel check-in update information, scenic spot play records, etc. The data aggregation triggering condition follows the judgment logic of formula (1). When the data volume stored in the real-time incremental buffer area reaches a preset storage threshold Or the data storage time in the buffer After a preset time window At this time, the buffer automatically integrates and aggregates all newly added travel data inside into a data block group. Through this aggregation processing, the subsequent encryption, verification, and other operations for each newly added data are avoided, the frequency of data processing is reduced, the system operation burden is reduced, the overall time consumption caused by processing a large number of scattered data is shortened, and the data processing efficiency is improved.

[0097] In this embodiment, the double-layer encryption processing of the data block group includes:

[0098] The basic data in the data block group is symmetrically encrypted using a first preset key;

[0099] The group-level metadata in the data block group is asymmetrically encrypted using a second preset key, and the group-level metadata includes user identity feature information and key operation records;

[0100] Only after the data block group is completed, a one-time aggregation encryption operation is triggered to encrypt the entire data block group.

[0101] Specifically, when the double-layer encryption processing of the data block group formed by aggregation is performed, the basic data in the data block group is first symmetrically encrypted using a first preset key. The basic data covers non-sensitive information in the travel itinerary, such as opening time of scenic spots, traffic schedule information, etc. The lightweight symmetric encryption method can quickly complete the encryption operation to ensure processing efficiency. Then, the group-level metadata in the data block group is asymmetrically encrypted using a second preset key. The group-level metadata includes user identity feature information and key operation records. Such information has high sensitivity, and asymmetric encryption can provide higher security level to prevent information leakage or tampering. Moreover, only after the data block group is completely aggregated, a one-time aggregation encryption operation is triggered to encrypt the entire data block group, ensuring the overall security of the data block group, while avoiding the aggregation operation being blocked due to early encryption, and balancing security and smooth processing.

[0102] In this embodiment, the source and digital signature of the data block group are verified by the metadata verification group, including:

[0103] The metadata verification group receives the data block group and extracts the metadata verification information contained in the data block group;

[0104] The data source in the metadata verification information is verified to ensure the legality of the data block group;

[0105] The digital signature in the metadata verification information is verified to ensure the integrity and non-repudiation of the data block group.

[0106] Specifically, after receiving the double-layer encrypted data block group, the metadata verification group first extracts the metadata verification information containing data source, digital signature and other information from the data block group. Then, the data source in the metadata verification information is checked to confirm whether the data block group comes from a legal user terminal or an authorized platform, excluding the possibility of illegal data entering the blockchain network. Then, the digital signature in the metadata verification information is verified to ensure that the data block group has not been tampered with during transmission, while ensuring the non-repudiation of the data sender, so that subsequent data processing links are based on reliable data sources, improving the security and credibility of the entire blockchain tourism data system.

[0107] In this embodiment, the parallel comparison of the hash values of the data in the data block group by the content consistency group includes:

[0108] The content consistency group receives the data block group and independently calculates the hash values of each data segment in the data block group;

[0109] The independently calculated hash values are compared in parallel with the pre-stored hash digest in the data block group;

[0110] According to the comparison result, the content consistency of the data in the data block group is confirmed.

[0111] Specifically, after receiving the data block group, the content consistency group independently calculates the hash values of each data segment in the data block group (hash value calculation uses existing technology, which is not described here). The calculation process is carried out in parallel to avoid delays in single data segment calculation affecting the overall progress. After calculation, the obtained hash values are compared in parallel with the pre-stored hash digest in the data block group. Through multiple comparison operations, the consistency of each data segment hash value with the pre-stored hash digest is confirmed quickly. According to the final comparison result, it is determined whether the data in the data block group remains complete and has not been tampered with, ensuring the consistency of the data in terms of content before entering the storage link, providing reliable protection for subsequent user query and use of data.

[0112] In this embodiment, the synchronous inspection of the access rights of the user to the data by the permission audit group includes:

[0113] The permission audit group obtains the user identity information associated with the data block group and the access request type;

[0114] The corresponding permission rules of the user are retrieved from the pre-set permission management strategy;

[0115] The user identity is synchronously checked to determine whether it has the right to access or operate the data block group.

[0116] Specifically, when processing the data block group, the authority audit group first acquires the user identity information associated with the data block group and the access request type initiated by the user, and explicitly the user identity corresponding to the current operation and the operation purpose. Then, from the preset authority management strategy, the specific authority rule corresponding to the user identity is retrieved to understand the data range accessible by the user and the operation type executable by the user. Based on the retrieved authority rule, it is synchronously checked whether the user identity has the authority to access or operate the current data block group. If the user authority does not meet the requirement, the access or operation request of the user is rejected to prevent unauthorized users from obtaining sensitive tourism data and effectively protect the user data privacy.

[0117] In the embodiment, the aggregated fingerprint of the data block group is stored on the core blockchain, and the double-encrypted original data is split into data segments and stored in the lightweight side chain, including:

[0118] The aggregated fingerprint of the data block group is uploaded to the core blockchain, and the aggregated fingerprint serves as the unique identifier of the data block group;

[0119] The double-encrypted original data is fragmented, and the fragmented data segments are stored off-chain in the lightweight side chain;

[0120] When the original data needs to be queried, the corresponding data segments on the lightweight side chain are located through the aggregated fingerprint on the core blockchain, and data recombination is performed.

[0121] Specifically, when the aggregated fingerprint of the data block group is stored on the core blockchain, the aggregated fingerprint is first uploaded to the core blockchain, and the aggregated fingerprint serves as the unique identifier of the data block group, which can quickly locate the corresponding data block group related information. The double-encrypted original data is fragmented, and the split data segments are stored in the lightweight side chain, realizing off-chain storage of the original data and the core blockchain, greatly reducing the storage pressure of the core blockchain and improving the operation efficiency of the core blockchain. When the original data needs to be queried, the corresponding data segments on the lightweight side chain are located through the aggregated fingerprint stored on the core blockchain, and the data segments are integrated and recombined to ensure that the user can accurately obtain the required original data, taking into account the storage efficiency and data query convenience.

[0122] In the embodiment, when the original data needs to be queried, the corresponding data segments on the lightweight side chain are located through the aggregated fingerprint on the core blockchain, and data recombination is performed, including:

[0123] A data query request issued by a user is received;

[0124] An aggregated fingerprint matching the query request is retrieved in the core blockchain;

[0125] According to the pointer information of the distributed cache layer and the data feature digest contained in the aggregation fingerprint, the corresponding encrypted data segment is retrieved from the lightweight side chain;

[0126] The retrieved encrypted data segment is decrypted and recombined to restore the original data.

[0127] Specifically, when a user issues a data query request, the system first receives the query request and determines the range and type of tourism data required by the user. Then, the aggregation fingerprint matching the query request is retrieved in the core blockchain, and the associated data block group information is quickly locked through the aggregation fingerprint. According to the pointer information of the distributed cache layer and the data feature digest contained in the aggregation fingerprint, the corresponding encrypted data segment is accurately retrieved in the lightweight side chain. The retrieved encrypted data segment is decrypted, and the decrypted data segments are recombined according to the original data structure, finally restoring the original tourism data required by the user, allowing the user to quickly obtain accurate data while avoiding direct processing of large amounts of original data queries on the core blockchain, ensuring the stability of the core blockchain.

[0128] In this embodiment, the double-layer encryption operation frequency and the number of lightweight side chain shards are automatically adjusted by the dynamic resource scheduler according to real-time data traffic, including:

[0129] The dynamic resource scheduler monitors the data traffic in the blockchain network in real time;

[0130] When the data traffic is in a non-peak period, the dynamic resource scheduler reduces the double-layer encryption operation frequency and reduces the number of lightweight side chain shards;

[0131] When the data traffic is in a peak period, the dynamic resource scheduler increases the double-layer encryption operation frequency and increases the number of lightweight side chain shards, and simultaneously enables a backup verification node group to assist in processing.

[0132] Specifically, the dynamic resource scheduler monitors the data traffic changes in the blockchain network in real time and understands the data processing needs in the network at different times. The resource adjustment logic follows the calculation method of formula (2), formula (3), and formula (4). First, the real-time data traffic is compared with the baseline traffic to calculate the traffic coefficient . Then, the double-layer encryption operation frequency and the number of lightweight side chain shards are adjusted according to . When the monitored data traffic is in a non-peak period, , the dynamic resource scheduler automatically reduces the double-layer encryption operation frequency , reducing unnecessary operation resource consumption, and simultaneously reducing the number of lightweight side chain shards Avoid resource waste caused by excessive fragmentation. When data traffic enters the peak period, the amount of tourism data increases significantly, The dynamic resource scheduler immediately increases the operation frequency of double-layer encryption Ensure that the new data can be encrypted in time, and increase the number of light side chain fragments Improve the storage and reading efficiency of raw data, and enable the standby verification node group to assist in data verification operation, relieve the pressure of the main verification node, ensure that the system can still run efficiently and stably during the peak period, and avoid data processing delay or system lag.

[0133] Please refer to Figure 2 The application also provides a blockchain tourism data privacy protection system, comprising:

[0134] The data aggregation module is used to build a distributed cache layer between the blockchain node and the user terminal, which is used to dynamically capture user new tourism data, and aggregate the new tourism data into a data block group in a preset time window or data volume threshold unit.

[0135] The encryption processing module is used for double-layer encryption processing of the data block group, which includes applying lightweight symmetric encryption to the basic data in the data block group and applying asymmetric encryption to the group-level metadata in the data block group.

[0136] The parallel verification module is used to submit the double-layer encrypted data block group to the blockchain network and start the fragmented parallel verification, and the parallel verification module comprises:

[0137] The node fragmentation unit is used to divide the verification nodes in the blockchain network into a metadata verification group, a content consistency group and a permission audit group.

[0138] The collaborative verification unit is used to check the source and digital signature of the data block group by the metadata verification group, to parallelly compare the hash values of the data in the data block group by the content consistency group, and to synchronously check the access permission of the user to the data by the permission audit group.

[0139] The message queue unit is used to realize the lock-free parallel operation between the metadata verification group, the content consistency group and the permission audit group.

[0140] The cross-chain storage module is used to store the aggregation fingerprint of the data block group on the core blockchain, and the aggregation fingerprint contains the data feature digest of the data block group, the user permission mark and the pointer of the distributed cache layer, and is used to split the double-layer encrypted raw data into data segments and store them in the light side chain.

[0141] The consensus optimization module is configured to adopt a two-stage consensus mechanism for data processing, which includes: a first stage of quickly responding to a new travel data request by the distributed cache layer and returning a temporary receiving voucher; and a second stage of asynchronously completing final verification and storage of the data block group in the background of the blockchain.

[0142] The resource scheduling module is configured to automatically adjust the operation frequency of the double-layer encryption and the number of fragments of the lightweight side chain by a dynamic resource scheduler according to real-time data traffic.

[0143] Specifically, the data aggregation module in the blockchain travel data privacy protection system constructs a distributed cache layer between the blockchain node and the user terminal, dynamically captures new travel data of the user, and aggregates the new data into a data block group according to the trigger condition of formula (1), i.e., when the data accumulation amount or the accumulated time is greater than or equal to a preset threshold. The encryption processing module performs double-layer encryption on the data block group, i.e., lightweight symmetric encryption on the basic data and asymmetric encryption on the group-level metadata.

[0144] The parallel verification module submits the double-layer encrypted data block group to the blockchain network, the node fragment unit divides the verification nodes into a metadata verification group, a content consistency group and a permission audit group, and the collaborative verification unit respectively completes data source and signature verification, data hash value comparison (hash value calculation uses existing technology), access permission check, and the message queue unit realizes the lock-free parallel operation of the three groups of nodes.

[0145] The cross-chain storage module stores the aggregation fingerprint of the data block group in the core blockchain and stores the original data fragments in the lightweight side chain. The consensus optimization module adopts a two-stage consensus, i.e., first responding to the user request by the distributed cache layer and returning the voucher, and then asynchronously completing the final verification and storage in the background. The resource scheduling module adjusts the encryption operation frequency and the number of side chain fragments according to formula (2), formula (3) and formula (4) in combination with real-time data traffic. The modules work collaboratively to realize the efficiency and security of travel data privacy protection and adapt to the dynamic change requirements of travel data.

[0146] In summary, the application constructs a distributed cache layer between the blockchain node and the user terminal, aggregates the user's new tourism data into a data block group according to a preset time window or data volume threshold, avoids performing a complete privacy protection process on each new data, reduces repeated operation and verification operations, adopts double-layer encryption for the data block group, ensures the efficiency of the basic data through lightweight symmetric encryption, and strengthens the security of the group-level metadata through asymmetric encryption, starts a sharded parallel verification and realizes a lock-free operation through a message queue, shortens the verification time consumption, adopts a two-stage consensus mechanism, makes the distributed cache layer quickly respond to user requests and return a temporary credential, and asynchronously completes the final verification and storage in the background, and a dynamic resource scheduler adjusts the encryption operation frequency and the side chain shard number according to real-time traffic, improves the processing capacity during peak periods, and reduces resource waste during off-peak periods. Thus, the problems of low efficiency and unbalanced resource consumption in processing dynamic tourism data in the prior art are solved, the resource pressure during the tourism peak period is relieved, and the stable operation of the blockchain tourism data system is ensured.

[0147] It should be noted that the relational terms herein such as first and second and the like are used solely to distinguish one entity or action from another, without necessarily requiring or implying any such actual relationship or order between such entities or actions. Moreover, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0148] Although embodiments of the present application have been shown and described, it is to be understood that various modifications, substitutions, replacements and changes can be made to these embodiments without departing from the principles and spirit of the present application, and the scope of the present application is defined by the appended claims and their equivalents.

Claims

1. A blockchain-based method for protecting the privacy of tourism data, characterized in that, include: A distributed caching layer is constructed and deployed between blockchain nodes and user terminals. It is used to dynamically capture new travel data from users and aggregate the new travel data into data block groups in a preset time window or data volume threshold. The data block group is subjected to two-layer encryption, which includes applying lightweight symmetric encryption to the basic data in the data block group and applying asymmetric encryption to the group-level metadata in the data block group. The double-encrypted data block group is submitted to the blockchain network, and sharded parallel verification is initiated. Sharded parallel verification includes: The verification nodes in the blockchain network are divided into a metadata verification group, a content consistency group, and an authorization audit group. The metadata verification group verifies the origin and digital signature of the data block group; The hash values ​​of data within a data block group are compared in parallel by the content consistency group; The access control group synchronously checks users' access permissions to data. Implement lock-free parallel operations between the metadata verification group, content consistency group, and permission audit group through message queues; The aggregate fingerprint of the data block group is stored on the core blockchain. The aggregate fingerprint contains a summary of the data characteristics of the data block group, a user permission token, and a pointer to the distributed cache layer. The original data after double encryption is split into data fragments and stored in a lightweight sidechain; Data processing employs a two-phase consensus mechanism, which includes: In the first phase, the distributed caching layer quickly responds to requests for new tourism data and returns temporary receiving credentials; The second phase involves asynchronously verifying and storing the data block group in the blockchain backend; and Based on real-time data traffic, the dynamic resource scheduler automatically adjusts the computation frequency of the double-encryption and the number of shards in the lightweight sidechain.

2. The blockchain tourism data privacy protection method according to claim 1, characterized in that, The construction of the distributed caching layer includes: A distributed caching layer is established between blockchain nodes and user terminals. The distributed caching layer is used as a real-time incremental buffer for newly added tourism data. The real-time incremental buffer dynamically receives new tourism data from user terminals in real time; When the amount of data in the real-time incremental buffer reaches the preset storage threshold, or when the real-time incremental buffer passes through the preset time window, the newly added tourism data in the real-time incremental buffer will be aggregated into a data block group.

3. The blockchain tourism data privacy protection method according to claim 1, characterized in that, The two-layer encryption process for the data block group includes: The basic data in the data block group is symmetrically encrypted using the first preset key; The group-level metadata in the data block group is asymmetrically encrypted using a second preset key. The group-level metadata includes user identity information and key operation records. A one-time aggregation encryption operation is triggered only after the data block group has been aggregated, in order to encrypt the entire data block group.

4. The blockchain tourism data privacy protection method according to claim 1, characterized in that, The verification of the source and digital signature of the data block group by the metadata verification group includes: The metadata verification group receives the data block group and extracts the metadata verification information contained in the data block group; Verify the data source in the metadata verification information to ensure the legitimacy of the data block group; Verify the digital signature in the metadata verification information to ensure the integrity and non-repudiation of the data block group.

5. A blockchain-based tourism data privacy protection method according to claim 1, characterized in that, The hash values ​​of the data within the data block group that are compared in parallel by the content consistency group include: The content consistency group receives the data block group and independently calculates the hash value of each data fragment within the data block group; The independently computed hash values ​​are compared in parallel with the pre-stored hash digests in the data block group; Based on the comparison results, the consistency of data content within the data block group was confirmed.

6. A blockchain-based tourism data privacy protection method according to claim 1, characterized in that, The synchronous check of user access permissions to data by the permissions audit group includes: The access control audit group obtains the user identity information and access request type associated with the data block group; Retrieve the user's corresponding permission rules from the preset permission management policy; Simultaneously verify whether the user's identity has the permission to access or operate on the data block group.

7. A blockchain-based tourism data privacy protection method according to claim 1, characterized in that, The process of storing aggregated fingerprints of data block groups on the core blockchain and splitting the double-encrypted original data into data fragments and storing them on a lightweight sidechain includes: The aggregate fingerprint of the data block group is uploaded to the core blockchain, and the aggregate fingerprint serves as the unique identifier of the data block group. The original data after double encryption is fragmented, and the fragmented data segments are stored off-chain in a lightweight sidechain. When it is necessary to query the original data, the corresponding data fragment on the lightweight sidechain is located by the aggregate fingerprint on the core blockchain, and the data is reconstructed.

8. A blockchain-based tourism data privacy protection method according to claim 7, characterized in that, When it is necessary to query the original data, the process of locating the corresponding data fragment on the lightweight sidechain using the aggregated fingerprint on the core blockchain and reconstructing the data includes: Receive data query requests from users; Retrieve aggregate fingerprints that match the query request within the core blockchain; Based on the pointer information of the distributed cache layer and the data feature digest contained in the aggregate fingerprint, the corresponding encrypted data fragment is retrieved from the lightweight sidechain; The retrieved encrypted data fragments are decrypted and reassembled to restore the original data.

9. A blockchain-based tourism data privacy protection method according to claim 1, characterized in that, The automatic adjustment of the double-layer encryption operation frequency and the number of lightweight sidechain shards based on real-time data traffic via a dynamic resource scheduler includes: The dynamic resource scheduler monitors data traffic in the blockchain network in real time; When data traffic is at off-peak times, the dynamic resource scheduler reduces the frequency of double encryption operations and decreases the number of shards in the lightweight sidechain. When data traffic is at its peak, the dynamic resource scheduler increases the frequency of double-encrypted operations and the number of shards in the lightweight sidechain, while also enabling backup validator node groups to assist in processing.

10. A blockchain-based tourism data privacy protection system, implementing the blockchain-based tourism data privacy protection method according to any one of claims 1-9, characterized in that, include: The data aggregation module is used to build a distributed caching layer. The distributed caching layer is deployed between the blockchain node and the user terminal to dynamically capture new travel data from users and aggregate the new travel data into data block groups in a preset time window or data volume threshold. The encryption processing module is used to perform two-layer encryption processing on the data block group. The two-layer encryption processing includes: applying lightweight symmetric encryption to the basic data in the data block group, and applying asymmetric encryption to the group-level metadata in the data block group. The parallel verification module is used to submit the double-encrypted data block group to the blockchain network and initiate sharded parallel verification. The parallel verification module includes: The node sharding unit is used to divide the verification nodes in the blockchain network into a metadata verification group, a content consistency group, and a permission audit group. The collaborative verification unit is used by the metadata verification group to verify the source and digital signature of the data block group, by the content consistency group to compare the hash values ​​of the data within the data block group in parallel, and by the permission audit group to synchronously check the user's access rights to the data. The message queue unit is used to enable lock-free parallel operations between the metadata verification group, the content consistency group, and the permission audit group. The cross-chain storage module is used to store the aggregate fingerprint of data block groups on the core blockchain. The aggregate fingerprint contains the data feature digest of the data block group, the user permission mark, and the pointer to the distributed cache layer. It is also used to split the double-encrypted original data into data fragments and store them on a lightweight sidechain. The consensus optimization module is used to process data using a two-stage consensus mechanism, which includes: a first stage in which a distributed caching layer quickly responds to new tourism data requests and returns temporary receipt credentials; and a second stage in which the final verification and storage of data block groups are completed asynchronously in the blockchain backend. The resource scheduling module is used to automatically adjust the computation frequency of the double-encrypted system and the number of shards in the lightweight sidechain based on real-time data traffic through a dynamic resource scheduler.

Images