Smart contract-based digital archive sharing and collaboration method and system

Abstract

This invention provides a method and system for sharing and collaborating on digital archives based on smart contracts, relating to the field of digital archive sharing and collaboration technology. Firstly, upon receiving a request to share a digital archive, a pre-defined smart contract is triggered to construct a shared collaboration rights pool. Based on the collaboration rules in the smart contract, the request information is mapped to rights allocation parameters to construct the rights pool. A sharing license agreement is generated based on the rights pool and synchronized to a blockchain network for notarization. The target digital archive is then encrypted and its rights are bound before being transmitted to the requesting party's terminal. By capturing usage data in real time through smart contracts, the rights ratio of collaborating entities is dynamically adjusted according to rights transfer trigger conditions, and the results are written into the blockchain distributed ledger. This effectively solves the problems of security, rights allocation, and flexibility in traditional digital archive sharing and collaboration.

Description

Technical Field

[0001] This invention relates to the field of digital archive sharing and collaboration technology, and more specifically, to a digital archive sharing and collaboration method and system based on smart contracts. Background Technology

[0002] In today's digital age, the number of digital archives is exploding, and the need for sharing and collaboration is becoming increasingly urgent. Traditional methods of sharing digital archives mainly rely on centralized management platforms, but this model has many drawbacks.

[0003] On the one hand, centralized platforms are prone to single points of failure. If the platform malfunctions or is attacked, archival data may be lost or leaked, severely impacting the security and integrity of the archives. On the other hand, traditional methods lack transparent and fair mechanisms for distributing rights. The contributions of different participants in the archive-sharing and collaboration process are difficult to accurately measure, and the distribution of rights often relies on human negotiation, which can easily lead to disputes and low collaboration efficiency.

[0004] Furthermore, existing file-sharing models struggle to achieve dynamic transfer and real-time adjustment of rights and interests. As the collaboration process progresses, the contributions and needs of each participant may change, but traditional models cannot respond to these changes in a timely manner, severely limiting the flexibility and adaptability of collaboration. Summary of the Invention

[0005] In view of the aforementioned problems, and in conjunction with the first aspect of the present invention, the present invention provides a method for sharing and collaborating on digital archives based on smart contracts, the method comprising: Upon receiving a request to share digital archives, a shared collaboration rights pool construction process based on the request is triggered using a preset smart contract. The digital archive sharing request includes the requester's identifier, the target digital archive identifier, and a description of the shared collaboration requirements. According to the digital archive collaboration rules pre-stored in the smart contract, the requester identifier, the target digital archive identifier, and the description of the sharing collaboration requirements are mapped to rights allocation parameters. A shared collaboration rights pool is constructed based on the rights allocation parameters. The shared collaboration rights pool includes the rights ratio of the collaboration subject, the archive usage rights node, and the rights transfer triggering conditions. A digital archive sharing license agreement is generated based on the shared collaborative rights pool, and the digital archive sharing license agreement is synchronized to the blockchain network for storage. The sharing license agreement includes the rights pool association identifier, archive usage permission boundaries, and rights transfer rules. According to the file usage permission boundaries in the shared license agreement, the target digital file is subjected to rights binding encryption processing to generate rights binding encrypted file, which includes rights pool association identifier and usage permission trigger key; The rights-binding encrypted file is transmitted to the terminal corresponding to the sharing requester. Based on the smart contract, the usage operation data of the sharing requester on the rights-binding encrypted file is captured in real time. According to the usage operation data and the rights transfer triggering conditions of the shared collaboration rights pool, the rights ratio of the collaborative entities in the shared collaboration rights pool is dynamically adjusted, and the adjustment result is written into the blockchain distributed ledger.

[0006] Furthermore, the present invention also provides a digital archive sharing and collaboration system based on smart contracts, comprising: processor; A machine-readable storage medium for storing machine-executable instructions of the processor; wherein the processor is configured to execute the aforementioned smart contract-based digital file sharing collaboration method by executing the machine-executable instructions.

[0007] Based on the above, the process of constructing a shared collaboration rights pool by triggering a pre-set smart contract upon receiving a request to share digital archives fundamentally changes the traditional centralized management model, effectively avoiding the risk of single points of failure and greatly improving the reliability and stability of the archive sharing system. Utilizing the pre-stored digital archive collaboration rules in the smart contract, request information is mapped to rights allocation parameters, and a shared collaboration rights pool is constructed, achieving transparency and automation in rights allocation, eliminating the uncertainty brought about by human negotiation, and significantly improving the fairness of rights allocation and collaboration efficiency. A digital archive sharing license agreement is generated based on the shared collaboration rights pool and synchronized to the blockchain network for notarization. Leveraging the immutability of the blockchain, the authenticity and integrity of the sharing license agreement are ensured, providing a reliable legal basis for archive sharing collaboration. Rights binding encryption is applied to the target digital archives, generating rights-bound encrypted archives, strictly limiting the access rights to the archives and ensuring their security. The smart contract captures the usage operation data of the sharing requester in real time and dynamically adjusts the rights ratio of the collaborating entities according to the rights transfer trigger conditions. The adjustment results are written into the blockchain distributed ledger, realizing the dynamic transfer and real-time adjustment of rights, enhancing the flexibility and adaptability of collaboration, and meeting the ever-changing needs in the process of digital archive sharing collaboration. Attached Figure Description

[0008] Figure 1 This is a schematic diagram of the execution flow of the digital archive sharing and collaboration method based on smart contracts provided in an embodiment of the present invention.

[0009] Figure 2 This is a schematic diagram of exemplary hardware and software components of a smart contract-based digital archive sharing and collaboration system provided in an embodiment of the present invention. Detailed Implementation

[0010] The present invention will now be described in detail with reference to the accompanying drawings. Figure 1 This is a flowchart illustrating a smart contract-based digital archive sharing and collaboration method according to an embodiment of the present invention. The following is a detailed description of this smart contract-based digital archive sharing and collaboration method.

[0011] Step S110: Receive a digital archive sharing request, and trigger the sharing and collaboration rights pool construction process of the preset smart contract based on the digital archive sharing request. The digital archive sharing request includes the requester identifier, the target digital archive identifier, and a description of the sharing and collaboration requirements.

[0012] In this embodiment, we take the example of research institution A requesting research institution B to share a digital archive about a certain research project. Research institution A's terminal acts as the sender of the digital archive sharing request, establishing a connection with the system's communication module. The system's communication module uses a secure communication protocol to communicate with research institution A's terminal to receive the digital archive sharing request. In this request, the requester is identified by research institution A's unique institutional code, the target digital archive is identified by the unique code of the research project archive in the system, and the sharing collaboration requirement description includes the type of collaboration task (e.g., joint analysis of research data), the collaboration period (e.g., 12 months), and the required frequency of archive use (e.g., twice daily).

[0013] Step S111: Establish a secure communication link with the sending end of the digitized archive sharing request, and receive the digitized archive sharing request through the secure communication link.

[0014] The system's communication module will perform a handshake operation with the research institution's terminal according to the preset secure communication configuration, negotiating and determining parameters such as the encryption algorithm and key to establish a secure communication link. After the secure communication link is established, the research institution's terminal will send a digital archive sharing request to the system through this link. The system's communication module will receive the request and temporarily store the request data in a data receiving buffer for subsequent processing.

[0015] Step S112: Perform format parsing processing on the digital archive sharing request to extract the requester identifier, target digital archive identifier, and sharing collaboration requirement description, which includes the collaboration task type, collaboration cycle, and archive usage frequency requirement.

[0016] The system's parsing module invokes a pre-defined parsing program to identify the format of digitized archive sharing requests and determine if it conforms to the system's specified request format specifications. If it does, the parsing module extracts the requester identifier, target digitized archive identifier, and sharing collaboration requirement description from the request data according to pre-defined field extraction rules. For example, for the collaboration task type field in the request data, the parsing module identifies its corresponding content as joint analysis of scientific research data; for the collaboration period field, it identifies its content as 12 months; and for the archive usage frequency requirement field, it identifies its content as twice a day.

[0017] Step S113: Query the preset smart contract association table, and determine the corresponding preset smart contract based on the target digital file identifier. The smart contract association table records the mapping relationship between different digital file identifiers and corresponding smart contracts.

[0018] The system's query module accesses a pre-defined smart contract association table, which is stored in the system's storage module as a database table. This table contains a digitized document identifier field and a corresponding smart contract identifier field. The query module searches the smart contract association table based on the extracted target digitized document identifier to find the corresponding smart contract identifier. For example, when the target digitized document identifier is the code of a research project document, the query module will find the corresponding smart contract identifier as Contract A in the smart contract association table.

[0019] Step S114: Send a rights pool construction trigger instruction to the determined preset smart contract. The rights pool construction trigger instruction carries the parsed requester identifier, target digital file identifier, and sharing collaboration requirement description.

[0020] The system's instruction sending module sends a stake pool construction trigger instruction to the corresponding preset smart contract based on the queried smart contract identifier. This stake pool construction trigger instruction carries the parsed requester identifier, target digital file identifier, and description of sharing and collaboration requirements as parameters, so that the smart contract can obtain the relevant information and process it after receiving the instruction.

[0021] Step S115: After receiving the equity pool construction trigger instruction, the preset smart contract starts the built-in shared collaborative equity pool construction process and reads the basic equity parameters corresponding to the target digital file identifier from the contract storage area. The basic equity parameters include the basic equity ratio of the file holder, the collaborative task equity coefficient, and the basic rules for equity transfer.

[0022] Upon receiving a trigger instruction to build a stake pool, a pre-defined smart contract (such as Contract A) will initiate a built-in shared collaborative stake pool construction process. The smart contract's storage and retrieval module will access the contract's storage area, which stores basic stake parameters corresponding to different target digital archive identifiers in key-value pairs. The storage and retrieval module will then retrieve the corresponding basic stake parameters based on the target digital archive identifier in the trigger instruction. For example, for this research project archive, the retrieved basic stake percentage for the archive holder is 60%, and the collaborative task stake coefficient is 0.8 (this coefficient is used to adjust the stake percentage later based on the type of collaborative task). The basic rule for stake transfer is that stake transfer can be triggered when the collaborative task completion progress reaches a certain percentage.

[0023] Step S116: Perform association matching processing between the shared collaboration requirement description in the equity pool construction trigger instruction and the basic equity parameters to generate initial parameters for equity pool construction. The initial parameters for equity pool construction include a list of collaborative entities, an initial equity allocation ratio, and an equity adjustment benchmark threshold.

[0024] The smart contract's matching module matches the shared collaboration requirement description in the equity pool construction trigger instruction with the read basic equity parameters. First, based on the collaboration task type in the shared collaboration requirement description and the collaboration task equity coefficient in the basic equity parameters, the basic equity allocation ratio for each collaboration entity is determined. Then, based on the requester's identifier and the file holder's identifier, a list of collaboration entities is generated, including Research Institution A (the requester) and Research Institution B (the file holder). Next, based on the file holder's basic equity percentage and the collaboration task equity coefficient in the basic equity parameters, the initial equity allocation ratio is calculated; for example, the file holder's initial equity percentage is 60% × 0.8 = 48%, and the requester's initial equity percentage is 52%. Simultaneously, based on the basic equity transfer rules in the basic equity parameters and the collaboration cycle and file usage frequency requirements in the shared collaboration requirement description, an equity adjustment benchmark threshold is determined; for example, equity adjustment is triggered when the file usage frequency exceeds 3 times per day or the task completion progress within the collaboration cycle is less than 50%.

[0025] Step S120: Based on the digital archive collaboration rules pre-stored in the smart contract, the requester identifier, target digital archive identifier, and shared collaboration requirement description are mapped to rights allocation parameters. A shared collaboration rights pool is constructed based on the rights allocation parameters. The shared collaboration rights pool includes the rights ratio of the collaboration subject, the archive usage rights node, and the rights transfer triggering conditions.

[0026] In this embodiment, the smart contract (contract A) processes the requester identifier, the target digital archive identifier, and the description of the sharing collaboration requirements according to its own pre-stored digital archive collaboration rules to generate rights allocation parameters, and builds a shared collaboration rights pool based on these parameters.

[0027] Step S121: Read the pre-stored digital archive collaboration rules from the collaboration rule storage area of ​​the smart contract. The digital archive collaboration rules include a mapping table of collaboration task types and equity coefficients, a comparison table of archive usage frequency and equity adjustment ratio, and a rule relating collaboration cycle and equity transfer interval.

[0028] The smart contract's rule reading module accesses its own collaboration rule storage area, which stores digital archive collaboration rules in the form of files or database tables. The rule reading module reads a mapping table between collaboration task types and equity coefficients, which records the equity coefficients corresponding to different collaboration task types (such as joint analysis of scientific research data, project technical exchange collaboration, etc.); it reads a table comparing archive usage frequency and equity adjustment ratios, which records the equity adjustment ratios corresponding to different archive usage frequency ranges (such as 1-2 times per day, 3-5 times per day, etc.); and it reads a rule linking collaboration period and equity transfer interval, which defines the equity transfer interval time (such as every 3 months, every 6 months, etc.) corresponding to different collaboration periods (such as 6 months, 12 months, etc.).

[0029] Step S122: Perform matching processing between the extracted requester identifier and the pre-stored collaboration entity qualification information in the smart contract to determine the collaboration qualification level of the requester, and generate qualification equity coefficient based on the collaboration qualification level.

[0030] The smart contract's qualification matching module reads pre-stored qualification information of collaborating entities from the smart contract's collaborating entity qualification information database. This database contains the identifier, qualification level (e.g., Level 1, Level 2, Level 3), and corresponding qualification equity coefficient (e.g., Level 1 corresponds to 1.2, Level 2 to 1.0, Level 3 to 0.8, etc.) of each collaborating entity. The qualification matching module matches the extracted requester identifier (the institution code of research institution A) with the identifier in the collaborating entity qualification information database, determining that research institution A's collaborative qualification level is Level 2, and the corresponding qualification equity coefficient is 1.0.

[0031] Step S123: Match the collaborative task types in the shared collaboration requirements description with the collaborative task types and rights coefficient mapping table in the digital archive collaboration rules, and extract the corresponding task rights coefficients.

[0032] The task coefficient matching module of the smart contract matches the collaborative task type (joint analysis of scientific research data) in the shared collaboration requirement description with the task type and equity coefficient mapping table. In this mapping table, the equity coefficient for the joint analysis of scientific research data is 0.9. The task coefficient matching module extracts this equity coefficient for subsequent calculation of equity allocation parameters.

[0033] Step S124: Match the frequency of file usage in the shared collaboration requirements description with the comparison table of file usage frequency and rights adjustment ratio in the digital file collaboration rules, and extract the corresponding usage rights adjustment ratio.

[0034] The frequency adjustment ratio matching module of the smart contract matches the file usage frequency (twice a day) in the shared collaboration requirement description with the file usage frequency and rights adjustment ratio lookup table. In this lookup table, the usage rights adjustment ratio corresponding to 1-2 times a day is 1.0 (i.e., no adjustment). The frequency adjustment ratio matching module extracts this usage rights adjustment ratio for use in the calculation of subsequent rights allocation parameters.

[0035] Step S125: Match the collaboration cycle in the shared collaboration requirement description with the collaboration cycle and rights transfer interval association rule in the digital archive collaboration rules, and extract the corresponding rights transfer interval parameter.

[0036] The smart contract's transfer interval matching module matches the collaboration period (12 months) in the shared collaboration requirement description with the association rule between the collaboration period and the equity transfer interval. In this association rule, the equity transfer interval parameter corresponding to the 12-month collaboration period is every 4 months. The transfer interval matching module extracts this equity transfer interval parameter to generate subsequent equity transfer trigger conditions.

[0037] Step S126: Integrate the qualification equity coefficient, task equity coefficient, usage equity adjustment ratio, and equity transfer interval parameters into equity allocation parameters.

[0038] The smart contract's parameter integration module integrates the qualification equity coefficient (1.0), task equity coefficient (0.9), usage equity adjustment ratio (1.0), and equity transfer interval parameter (every 4 months) according to a preset parameter format to generate equity allocation parameters. These equity allocation parameters will serve as the basis for subsequently building a shared collaborative equity pool.

[0039] Step S127: Based on the qualification equity coefficient and task equity coefficient in the equity allocation parameters, determine the initial equity ratio of each entity in the collaborative entity list.

[0040] The smart contract's equity percentage calculation module calculates the initial equity percentage of each entity in the collaborative entity list based on the qualification equity coefficient and task equity coefficient in the equity allocation parameters, combined with the basic equity percentage of the file holder in the basic equity parameters. For example, if the file holder (research institution B) has a basic equity percentage of 60%, a qualification equity coefficient of 1.0 (the default qualification equity coefficient for the file holder is 1.0), and a task equity coefficient of 0.9, then the file holder's initial equity percentage is 60% × 1.0 × 0.9 = 54%; the requester (research institution A)'s initial equity percentage is 100% - 54% = 46%.

[0041] Step S128: Based on the usage rights adjustment ratio in the rights allocation parameters, set the file usage rights node, which includes a usage frequency threshold, rights enhancement nodes, and rights reduction nodes.

[0042] The smart contract's rights node setting module sets the file usage rights node based on the usage rights adjustment ratio (1.0) in the rights allocation parameters, combined with the file usage frequency requirement (2 times per day). For example, if the usage frequency threshold is set to 3 times per day, when the file usage frequency reaches 3 times per day, the rights increase node is triggered, and the rights increase ratio is the usage rights adjustment ratio × 0.1 = 0.1; when the file usage frequency is less than 1 time per day, the rights decrease node is triggered, and the rights decrease ratio is the usage rights adjustment ratio × 0.1 = 0.1.

[0043] Step S129: Based on the equity transfer interval parameter in the equity allocation parameters and the equity transfer trigger condition template in the digital archive collaboration rules, generate equity transfer trigger conditions. The equity transfer trigger conditions include transfer interval trigger conditions, usage operation trigger conditions, and equity ratio adjustment trigger conditions.

[0044] The smart contract's trigger condition generation module generates equity transfer trigger conditions based on the equity transfer interval parameter (every 4 months) in the equity allocation parameters and the equity transfer trigger condition template in the digital archive collaboration rules. The transfer interval trigger condition is set to trigger equity transfer once every 4 months; the usage operation trigger condition is set to trigger equity transfer when the frequency of archive usage exceeds the usage frequency threshold (3 times per day) or is less than 1 time per day; and the equity proportion adjustment trigger condition is set to trigger equity transfer when the equity proportion of a certain collaborating entity changes by more than 10%.

[0045] Step S1210: Integrate the equity ratio of the collaborating entities, the equity nodes for file use, and the triggering conditions for equity transfer to construct a structured shared collaborative equity pool, and assign a unique equity pool identifier to the shared collaborative equity pool.

[0046] The smart contract's equity pool construction module integrates the equity proportions of the collaborating entities (Research Institution B 54%, Research Institution A 46%), the equity nodes for file usage (usage frequency threshold of 3 times per day, equity increase ratio of 0.1, equity decrease ratio of 0.1), and equity transfer triggering conditions (transfer interval every 4 months, usage operation triggering conditions, and equity proportion adjustment triggering conditions) according to a preset equity pool structure format to construct a structured shared collaborative equity pool. Then, the smart contract's identifier allocation module assigns a unique equity pool identifier to this shared collaborative equity pool, for example, an equity pool identifier of EP-001, for subsequent management and reference of the equity pool.

[0047] Step S130: Generate a digital archive sharing license agreement based on the shared collaborative rights pool, and synchronize the digital archive sharing license agreement to the blockchain network for storage. The sharing license agreement includes the rights pool association identifier, archive usage permission boundaries, and rights transfer rules.

[0048] In this embodiment, the smart contract (Contract A) generates a digital archive sharing license agreement based on the constructed shared collaborative rights pool, and synchronizes the agreement to the blockchain network for storage.

[0049] Step S131: Extract the rights pool identifier from the shared collaboration rights pool and write it as the rights pool association identifier into the specified field of the shared license agreement template.

[0050] The smart contract's identifier extraction module extracts the equity pool identifier (EP-001) from the shared collaboration equity pool, and then writes this identifier into the equity pool association identifier field of the shared license agreement template. The shared license agreement template is predefined by the system and contains multiple fields, such as the equity pool association identifier field, the file usage permission boundary field, and the equity transfer rule field.

[0051] Step S132: Determine the file usage permission boundary based on the file usage right node in the shared collaboration right pool. The file usage permission boundary includes the allowed usage operation type, usage frequency limit and usage time range. Write the file usage permission boundary into the shared license agreement template.

[0052] The smart contract's permission boundary determination module determines the file usage permission boundaries based on the file usage right nodes in the shared collaboration right pool. For example, allowed usage operation types include data query and data download (excluding modification); the usage frequency limit is 3 times per day; and the usage time range is 9:00-18:00 on weekdays. The permission boundary determination module writes the above information into the file usage permission boundary field of the shared license agreement template.

[0053] Step S133: Extract the rights transfer triggering conditions from the shared collaborative rights pool, combine them with the rights transfer rule template pre-stored in the smart contract, generate rights transfer rules, the rights transfer rules include the method of adjusting the proportion of the main rights after the rights transfer is triggered, the method of recording rights transfer, and the method of handling transfer objections, and write the rights transfer rules into the shared license agreement template.

[0054] The smart contract's transfer rule generation module extracts the trigger conditions for rights transfer from the shared collaborative rights pool, and then combines them with the pre-stored rights transfer rule template in the smart contract to generate rights transfer rules. The method for adjusting the principal's rights percentage after a rights transfer is triggered is to adjust the collaborative principal's rights percentage according to the rights adjustment ratio (e.g., a rights increase of 0.1 or a rights decrease of 0.1). The method for recording rights transfer is to record relevant information (such as transfer time, transfer reason, and the percentage before and after rights adjustment) in the blockchain ledger. The method for handling transfer objections is to allow collaborative principals to initiate an objection application through the smart contract within 3 business days of receiving the rights transfer notification, which is then adjudicated by the consensus nodes in the blockchain network. The transfer rule generation module writes the above rights transfer rules into the rights transfer rule field of the shared license agreement template.

[0055] Step S134: Add the requester identifier, target digital archive identifier, and collaboration cycle information to the sharing license agreement template to generate a complete digital archive sharing license agreement.

[0056] The smart contract's protocol supplementation module will add the requester's identifier (the institution code of research institution A), the target digital archive identifier (the code of a research project archive), and the collaboration period information (12 months) to the corresponding fields of the shared license agreement template, thereby generating a complete digital archive shared license agreement.

[0057] Step S135: Perform a hash operation on the digital archive sharing license agreement to generate a protocol hash value.

[0058] The smart contract's hashing module calls a preset hash algorithm (such as SHA-256) to hash the content of the digital archive sharing license agreement, generating a protocol hash value. This protocol hash value will be used to subsequently verify the integrity of the agreement.

[0059] Step S136: Send the digital archive sharing license agreement and the corresponding protocol hash value to the evidence storage node of the blockchain network.

[0060] The smart contract's protocol sending module sends the digital archive sharing license agreement and its corresponding hash value to the evidence storage nodes in the blockchain network. The evidence storage nodes in the blockchain network receive the agreement and hash value for subsequent evidence storage processing.

[0061] Step S137: The evidence storage node performs integrity verification on the digital archive sharing license agreement and the protocol hash value. After the verification is successful, the digital archive sharing license agreement and the protocol hash value are written into the blockchain evidence storage ledger, and an evidence storage certificate is generated. The evidence storage certificate includes the evidence storage time, the evidence storage node identifier, and the protocol hash value.

[0062] The verification module of the evidence storage node first verifies the protocol hash value, that is, it re-hashes the digital archive sharing license agreement and compares the resulting hash value with the received protocol hash value. If they match, it means that the integrity of the protocol is guaranteed and the verification passes. After successful verification, the ledger writing module of the evidence storage node writes the digital archive sharing license agreement and the protocol hash value into the blockchain evidence storage ledger. At the same time, the certificate generation module of the evidence storage node generates an evidence storage certificate, which includes the evidence storage time (e.g., January 1, 2024, 10:00:00), the evidence storage node identifier (e.g., Node - 001), and the protocol hash value.

[0063] Step S138: Return the evidence storage certificate to the smart contract, and the smart contract will associate and store the evidence storage certificate with the shared collaborative rights pool.

[0064] The certificate return module of the certificate storage node will return the certificate storage to the smart contract. The associated storage module of the smart contract will associate the certificate storage with the shared collaborative rights pool, that is, associate the relevant information of the certificate storage (such as the certificate storage time, certificate storage node identifier, protocol hash value) with the identifier of the shared collaborative rights pool (EP-001) and store it in the storage area of ​​the smart contract for subsequent query and verification.

[0065] Step S140: According to the file usage permission boundaries in the shared license agreement, perform rights binding encryption processing on the target digital file to generate rights binding encrypted file, wherein the rights binding encrypted file contains rights pool association identifier and usage permission trigger key.

[0066] In this embodiment, the smart contract (contract A) performs rights-binding encryption processing on the target digital archive (a scientific research project archive) according to the archive usage permission boundaries in the shared license agreement, so as to generate a rights-binding encrypted archive.

[0067] Step S141: Extract the file usage permission boundaries from the shared license agreement, determine the allowed operation types and usage frequency limits, and generate permission encryption parameters.

[0068] The smart contract's permission extraction module extracts the file usage permission boundaries from the shared license agreement, determines the permitted operation types (data query, data download) and usage frequency limits (3 times per day), and then integrates the above information with the equity pool association identifier (EP-001) to generate permission encryption parameters. The permission encryption parameters are structured data containing permitted operation types, usage frequency limits, and equity pool association identifiers.

[0069] Step S142: Extract the rights pool association identifier from the shared collaboration rights pool and write it as encrypted association information into the permission encryption parameters.

[0070] The smart contract's identifier extraction module extracts the equity pool association identifier (EP-001) from the shared collaborative equity pool, and then writes this identifier as encrypted association information into the permission encryption parameters to ensure that the encryption process is associated with the shared collaborative equity pool.

[0071] Step S143: Call the equity binding encryption algorithm built into the smart contract, input the original data of the target digitized archive into the archive data encryption module, use the encryption association information in the permission encryption parameters to generate a basic encryption key, perform segmented encryption on the original data of the target digitized archive to obtain the archive encryption segment. The equity binding encryption algorithm includes a permission parameter encryption module, an archive data encryption module and a key association module.

[0072] Step S1431: Start the smart contract's built-in rights binding encryption algorithm and initialize the permission parameter encryption module, file data encryption module, and key association module.

[0073] The smart contract invokes a built-in stake-binding encryption algorithm, which initializes the permission parameter encryption module, file data encryption module, and key association module upon startup. The initialization process includes allocating memory space for each module and setting initial parameters to ensure that each module functions correctly.

[0074] Step S1432: Input the permission encryption parameters into the permission parameter encryption module, and perform encryption processing on the rights pool association identifier, allowed operation type and usage frequency limit to generate encrypted permission parameters.

[0075] The permission parameter encryption module receives the permission encryption parameters and then uses a preset encryption algorithm (such as AES) to encrypt the rights pool association identifier, allowed operation types, and usage frequency limits in the permission encryption parameters to generate encrypted permission parameters. The encrypted parameters will be used to generate the base encryption key later.

[0076] Step S1433: Send the encryption permission parameters to the key association module, which extracts the rights pool association identifier and performs a hash operation on the rights pool association identifier to generate a hash value.

[0077] The key association module receives the encryption permission parameters, extracts the equity pool association identifier (EP-001) from the encryption permission parameters, and performs a hash operation (such as SHA-256 hash operation) on the identifier to generate a hash value. This hash value will be used as the base key seed to generate the base encryption key.

[0078] Step S1434: Use the hash value as the basic key seed and combine it with the key generation algorithm pre-stored in the smart contract to generate the basic encryption key.

[0079] The key association module uses the generated hash value as the base key seed, and combines it with the key generation algorithm pre-stored in the smart contract (such as a hash-based key derivation function) to generate a base encryption key. This base encryption key will be used to encrypt the original data of the target digitized archive.

[0080] Step S1435: Divide the original data of the target digitized archive into multiple data segments, each data segment containing a data segment identifier and data content.

[0081] The archive data encryption module divides the original data of the target digitized archive into multiple data segments according to preset segmentation rules (such as segmentation according to data size or logical structure). Each data segment is assigned a unique data segment identifier (such as DS-001, DS-002, etc.) and contains the corresponding data content.

[0082] Step S1436: Input each data segment into the archive data encryption module in sequence, and use the basic encryption key to perform encryption processing on the data content in the data segment to generate encrypted data content.

[0083] The archive data encryption module receives each data segment sequentially and then encrypts the data content within each segment using a basic encryption key. During the encryption process, the data content is encrypted according to a preset encryption mode (such as CBC mode) to generate encrypted data.

[0084] Step S1437: Integrate the data segment identifier with the corresponding encrypted data content to generate an archive encrypted segment unit.

[0085] The archive data encryption module integrates the identifier of each data segment with the corresponding encrypted data content to generate an archive encryption segment unit. For example, if the data segment identifier is DS-001 and the corresponding encrypted data content is an encrypted data block, then the archive encryption segment unit is structured data containing DS-001 and that data block.

[0086] Step S1438: Sort all encrypted segment units of the archive according to the segmentation order of the original data of the target digitized archive to generate a complete encrypted segment of the archive.

[0087] The archive data encryption module sorts all generated encrypted archive segments according to the original data segmentation order of the target digitized archive, thus generating a complete encrypted archive segment. This ensures that the original data can be restored in the correct order during decryption.

[0088] Step S144: Generate a corresponding usage permission trigger key based on the allowed usage operation type in the file usage permission boundary. Each allowed usage operation type corresponds to a unique usage permission trigger key.

[0089] The smart contract's key generation module generates corresponding access trigger keys based on the permitted operation types (data query, data download) within the file's access permission boundaries. For example, key K1 is generated for the data query operation type, and key K2 is generated for the data download operation type. Each permitted operation type corresponds to a unique access trigger key to ensure that only operations with the corresponding permissions can trigger decryption.

[0090] Step S145: Integrate the rights pool association identifier, file encryption segment, and usage permission trigger key to generate the structural framework of the rights-bound encrypted file.

[0091] The smart contract's file integration module integrates the equity pool association identifier (EP-001), the file encryption segment, and the usage permission trigger key (K1, K2) according to a preset structural framework format to generate a structural framework for the equity-bound encrypted file. This structural framework includes the equity pool association identifier field, the file encryption segment field, and the usage permission trigger key field.

[0092] Step S146: Perform check code calculation on each component in the structural framework of the rights-binding encrypted file, generate check codes corresponding to each component, and attach the check codes to the corresponding components to obtain the complete rights-binding encrypted file.

[0093] The smart contract's checksum calculation module performs checksum calculations (such as CRC checks) on each component of the equity-bound encrypted file's structural framework (equity pool association identifier, encrypted file segment, and usage permission trigger key), generating a checksum corresponding to each component. Then, the checksum is appended to the end of the corresponding component, resulting in the complete equity-bound encrypted file. This allows for verification of the integrity of each component during subsequent transmission and use.

[0094] Step S150: Transmit the rights-binding encrypted file to the terminal corresponding to the sharing requester, capture the usage operation data of the sharing requester on the rights-binding encrypted file in real time based on the smart contract, dynamically adjust the proportion of the rights of the collaborative entities in the shared collaborative rights pool according to the usage operation data and the rights transfer triggering conditions of the shared collaborative rights pool, and write the adjustment result into the blockchain distributed ledger.

[0095] In this embodiment, the smart contract (contract A) transmits the equity-bound encrypted file to the terminal corresponding to the sharing requester (research institution A), and captures the research institution A's usage operation data of the file in real time. Based on the operation data and the triggering conditions for equity transfer, the equity ratio of the collaborating entities is dynamically adjusted, and finally the adjustment result is written into the blockchain distributed ledger.

[0096] Step S151: Establish a transmission channel for the rights-bound encrypted file. This transmission channel is associated with the smart contract's operation capture module. During the transmission process, the transmission progress data is synchronized to the operation capture module in real time.

[0097] The system's transmission channel establishment module establishes a transmission channel for the rights-bound encrypted file according to a preset transmission protocol (such as HTTP or FTP). This transmission channel is associated with the smart contract's operation capture module. During the transmission process, the transmission channel will synchronize transmission progress data (such as the amount of data transmitted, the amount of data remaining, the transmission speed, etc.) to the operation capture module in real time, so that the operation capture module can understand the transmission status in real time.

[0098] Step S152: Divide the rights-binding encrypted file into multiple transmission units. Each transmission unit contains a unit identifier, a transmission sequence number, and encrypted data content. These units are then sent sequentially to the terminal corresponding to the sharing requester through the transmission channel.

[0099] The system's file partitioning module divides the rights-bound encrypted files into multiple transmission units according to a preset size (e.g., 1MB per transmission unit). Each transmission unit is assigned a unique unit identifier (e.g., TU-001, TU-002, etc.) and a transmission sequence number (e.g., 1, 2, 3, etc.), and contains corresponding encrypted data content. Then, the transmission module sequentially sends the above transmission units to the terminal corresponding to the sharing requester (Research Institution A) through the transmission channel.

[0100] Step S153: After receiving all transmission units, the terminal corresponding to the sharing requester reassembles them according to the transmission sequence number to obtain a complete rights-binding encrypted file, and sends a reception completion feedback to the smart contract.

[0101] After receiving all the transmission units, the terminal of research institution A will reassemble the transmission units according to their transmission sequence numbers, and concatenate the encrypted data content of all transmission units in order to obtain a complete rights-bound encrypted file. Then, the terminal will send a reception completion feedback to the smart contract, informing the smart contract that the file has been successfully received.

[0102] Step S154: After receiving the feedback that the reception is complete, the smart contract starts the operation capture module to capture the operation data of the sharing requester terminal on the use of the rights-bound encrypted file in real time. The operation data includes the operation type, operation time, operation duration and operation result.

[0103] Step S1541: The smart contract sends an operation capture authorization instruction to the terminal corresponding to the sharing requester. The operation capture authorization instruction includes the capture range and data transmission format requirements.

[0104] The smart contract's instruction sending module sends an operation capture authorization instruction to the terminal corresponding to the sharing requester (research institution A). This authorization instruction includes the capture scope (such as opening, querying, and downloading the equity-bound encrypted file) and data transmission format requirements (such as operation type, operation time, operation duration, and operation result format requirements).

[0105] Step S1542: After receiving the operation capture authorization instruction, the terminal corresponding to the sharing requester starts the local operation monitoring component. The operation monitoring component establishes an association with the opening program of the rights-bound encrypted file and monitors the operation behavior of the opening program in real time.

[0106] Upon receiving the operation capture authorization command, the terminal of research institution A will activate its local operation monitoring component. This operation monitoring component will establish a connection with the program that opens the rights-bound encrypted file (such as dedicated file viewing software), and monitor the program's operation behavior on the rights-bound encrypted file in real time through hook functions or process monitoring.

[0107] Step S1543: When it is detected that the opening program performs an operation on the rights-bound encrypted file, the operation monitoring component records the operation type and synchronously obtains the system time as the operation time.

[0108] When the operation monitoring component detects that an application is performing an operation on a rights-bound encrypted file, it will record the operation based on the type of operation (such as query or download). Simultaneously, the operation monitoring component will obtain the terminal's system time and record that time as the operation time.

[0109] Step S1544: Calculate the time difference from the start to the end of the operation as the operation duration.

[0110] The operation monitoring component records the start time and end time of the operation, then calculates the difference between these two times and records this difference as the operation duration. For example, if the operation starts at 9:00:00 and ends at 9:01:00, the operation duration is 1 minute.

[0111] Step S1545: Capture the return result after the operation is executed, determine whether the operation was successful, and use the determination result as the operation result.

[0112] The operation monitoring component captures the return results after an operation is executed and determines whether the operation was successful based on the status code or prompt message in the return result. For example, if the return result contains the prompt message "Operation successful," the operation result is successful; if the return result contains the prompt message "Insufficient permissions," the operation result is unsuccessful. The operation monitoring component records the determined result as the operation result.

[0113] Step S1546: Integrate the operation type, operation time, operation duration, and operation result into operation data according to the data transmission format specified by the smart contract.

[0114] The operation monitoring component integrates the recorded operation type, operation time, operation duration, and operation result according to the data transmission format specified by the smart contract to generate usage operation data. For example, if the data transmission format is JSON, the operation type is "query", the operation time is "2024-01-02 09:00:00", the operation duration is "1 minute", and the operation result is "success", then the integrated usage operation data will be {"operation type":"query","operation time":"2024-01-02 09:00:00","operation duration":"1 minute","operation result":"success"}.

[0115] Step S1547: Send the operation data to the smart contract's operation capture module in real time via a secure communication link.

[0116] Research institution A's terminal will send the integrated user operation data to the smart contract's operation capture module in real time via a secure communication link (such as a TLS protocol communication link). The secure communication link ensures the security and integrity of the user operation data during transmission.

[0117] Step S1548: After receiving the operation data, the operation capture module performs format verification on the operation data and checks whether the data fields are complete. If the format verification passes, the operation data is stored in the operation data buffer. If the format verification fails, a data retransmission instruction is returned to the terminal corresponding to the sharing requester.

[0118] After receiving the operation data, the smart contract's operation capture module validates the format of the data and checks the completeness of the data fields (such as whether it includes operation type, operation time, operation duration, and operation result fields). If the format validation passes, the operation capture module stores the operation data in the operation data cache for subsequent processing; if the format validation fails, the operation capture module returns a data retransmission instruction to the terminal corresponding to the sharing requester (research institution A), requesting the terminal to resend the operation data.

[0119] Step S155: The captured usage operation data is transmitted in real time to the rights adjustment module of the smart contract. The rights adjustment module extracts the rights transfer trigger conditions from the shared collaborative rights pool.

[0120] The smart contract's operation data transmission module transmits the usage operation data in the operation data cache to the equity adjustment module in real time. The equity adjustment module extracts the equity transfer trigger conditions from the shared collaborative equity pool. These equity transfer trigger conditions include transfer interval trigger conditions, usage operation trigger conditions, and equity percentage adjustment trigger conditions.

[0121] Step S156: Match the operation data with the equity transfer trigger conditions to determine whether the equity transfer trigger conditions are met. If they are met, extract the corresponding equity adjustment rules.

[0122] The rights adjustment module matches usage data with rights transfer trigger conditions. For example, it checks whether the frequency of operations in the usage data exceeds the usage frequency threshold (3 times per day), whether the operation duration meets the requirements, and whether the operation result is successful, to determine whether the rights transfer trigger conditions are met. If the rights transfer trigger conditions are met, the rights adjustment module extracts the corresponding rights adjustment rules from the shared collaborative rights pool. These rules include information such as the rights adjustment ratio and adjustment method.

[0123] Step S157: Calculate the adjustment range of the equity ratio of the collaborating entity based on the equity adjustment rules and usage operation data.

[0124] The rights adjustment module calculates the adjustment range of the rights percentage for collaborating entities based on the rights adjustment rules and usage data. For example, if the rights adjustment rules stipulate that the rights percentage increases by 0.1 when the operation frequency exceeds 3 times per day, and the usage data shows an operation frequency of 4 times per day, then the adjustment range is 0.1. The rights adjustment module calculates the accurate adjustment range based on factors such as operation type, operation duration, and operation result, combined with the rights adjustment rules.

[0125] Step S158: Based on the adjustment range, dynamically adjust the equity ratio of the collaborative entities in the shared collaborative equity pool, and generate an equity adjustment record. The equity adjustment record includes the adjustment time, equity ratio before adjustment, equity ratio after adjustment, and adjustment basis.

[0126] The rights adjustment module dynamically adjusts the rights percentage of collaborative entities in the shared collaboration rights pool based on the calculated adjustment range. For example, if Research Institution B's initial rights percentage is 54% and the adjustment range is 0.1 (an increase), then the adjusted rights percentage will be 54% + 0.1 × 54% = 59.4%; Research Institution A's initial rights percentage is 46%, and the adjusted rights percentage will be 46% - 0.1 × 46% = 41.4%. The rights adjustment module generates a rights adjustment record, which includes the adjustment time (e.g., January 2, 2024, 10:00:00), the rights percentage before adjustment (Research Institution B 54%, Research Institution A 46%), the rights percentage after adjustment (Research Institution B 59.4%, Research Institution A 41.4%), and the basis for the adjustment (operation frequency exceeding 3 times per day).

[0127] Step S159: Perform a hash operation on the equity adjustment record to generate the adjustment record hash value.

[0128] The equity adjustment module calls a preset hash algorithm (such as SHA-256) to perform a hash operation on the content of the equity adjustment record, generating an adjustment record hash value. This adjustment record hash value will be used for subsequent verification of the integrity of the equity adjustment record.

[0129] Step S1510: Send the equity adjustment record and the hash value of the adjustment record to the ledger node of the blockchain distributed ledger.

[0130] The equity adjustment module sends the equity adjustment record and its hash value to the ledger nodes of the blockchain distributed ledger. The ledger nodes receive the record and hash value for subsequent accounting processing.

[0131] Step S1511: The accounting node performs verification processing on the equity adjustment record and the hash value of the adjustment record. After confirming the integrity and legality of the record, it writes the equity adjustment record and the hash value of the adjustment record into a block of the blockchain distributed ledger. This block connects with other blockchains through the consensus mechanism. The smart contract sends a notification message that the operation record has been written into the ledger to the terminal corresponding to the sharing requester and the terminal corresponding to the file holder.

[0132] The verification module of the ledger node first verifies the hash value of the adjustment record. This involves re-hashing the equity adjustment record and comparing the resulting hash value with the received adjustment record hash value. If they match, the integrity of the equity adjustment record is guaranteed. Simultaneously, the ledger node verifies the legality of the equity adjustment record, checking whether the adjustment basis meets the triggering conditions for equity transfer and whether the adjustment range is calculated correctly. After successful verification, the ledger writing module of the ledger node writes the equity adjustment record and its hash value into a block of the blockchain distributed ledger. This block connects with other blockchains through a consensus mechanism (such as proof-of-work or proof-of-stake) to form a complete blockchain ledger. Finally, the smart contract sends notifications to the terminals corresponding to the sharing requester (Research Institution A) and the archive holder (Research Institution B), informing both parties that the operation record has been successfully written into the blockchain ledger.

[0133] After capturing the usage data of the sharing requester on the rights-bound encrypted file in real time based on the smart contract, the method further includes: Step S210: The operation analysis module based on smart contracts performs classification statistics on the captured usage operation data, and generates operation type statistics, operation frequency statistics, and operation duration statistics.

[0134] In this embodiment, the operation analysis module of the smart contract (contract A) will classify and statistically analyze the captured usage operation data to generate relevant statistical results.

[0135] For example, in step S211: the smart contract's operation analysis module reads all captured usage operation data from the operation data cache.

[0136] The smart contract's operation analysis module accesses the operation data cache and reads all the usage operation data stored therein. The aforementioned usage operation data includes various operation information of the sharing requester (research institution A) on the rights-bound encrypted file, such as operation type, operation time, operation duration, and operation result.

[0137] Step S212: Group the operation data according to the operation type, count the number of operations in each group, and generate operation type statistics results, which include the operation type name and the corresponding number of operations.

[0138] The operation analysis module groups usage data according to operation type (such as query, download). For example, all usage data with the operation type "query" are grouped into one group, and usage data with the operation type "download" are grouped into another group. Then, the number of operations in each group is counted, generating operation type statistics results. For example, if the number of query operations is 10 and the number of download operations is 5, the operation type statistics results would be {"Operation Type":"Query","Number of Operations":10},{"Operation Type":"Download","Number of Operations":5}.

[0139] Step S213: Extract the operation time from all the operation data and divide the operation time into multiple statistical periods according to the collaboration period in the shared license agreement.

[0140] The operations analysis module extracts the operation time from all usage operation data and then divides the operation time into multiple statistical periods based on the collaboration period (12 months) in the shared license agreement. For example, the 12-month collaboration period can be divided into one statistical period per month, or one statistical period per 3 months.

[0141] Step S214: Within each statistical period, count the number of operations for different operation types and generate operation frequency statistics results. These operation frequency statistics results include the statistical period, operation type, and corresponding frequency.

[0142] The operation analysis module counts the number of operations of different operation types within each statistical period. For example, in the first statistical period (January to March), there were 3 query operations and 1 download operation; in the second statistical period (April to June), there were 4 query operations and 2 download operations. The operation analysis module integrates the above information to generate operation frequency statistics, such as {"Statistical Period":"January to March","Operation Type":"Query","Frequency":3},{"Statistical Period":"January to March","Operation Type":"Download","Frequency":1},{"Statistical Period":"April to June","Operation Type":"Query","Frequency":4},{"Statistical Period":"April to June","Operation Type":"Download","Frequency":2}.

[0143] Step S215: Extract the operation duration from all operation data, group them according to operation type, calculate the sum, average and maximum operation duration of each group, and generate operation duration statistics. The operation duration statistics include operation type, total duration, average duration and longest duration.

[0144] The operation analysis module extracts the operation duration from all usage data and then groups them according to operation type. For example, the operation durations of "query" are grouped into one group, and the operation durations of "download" are grouped into another. Then, the module calculates the sum, average, and maximum operation durations for each group. For example, the total duration of a query operation is 10 minutes, the average duration is 1 minute (10 operations, total duration 10 minutes), and the longest duration is 2 minutes; the total duration of a download operation is 15 minutes, the average duration is 3 minutes (5 operations, total duration 15 minutes), and the longest duration is 5 minutes. The operation analysis module integrates the above information to generate operation duration statistics, such as {"Operation Type":"Query","Total Duration":10 minutes,"Average Duration":1 minute,"Longest Duration":2 minutes}, {"Operation Type":"Download","Total Duration":15 minutes,"Average Duration":3 minutes,"Longest Duration":5 minutes}.

[0145] Step S216: Perform data format standardization processing on the operation type statistics, operation frequency statistics, and operation duration statistics. Associate the standardized operation type statistics, operation frequency statistics, and operation duration statistics with the shared collaboration equity pool identifier and store them in the statistical result storage area of ​​the smart contract.

[0146] The operation analysis module performs data format standardization processing on the operation type statistics, operation frequency statistics, and operation duration statistics, converting them into a unified data format defined by the system. Then, the standardized statistical results are associated with the shared collaboration equity pool identifier (EP-001) and stored in the statistical result storage area of ​​the smart contract for subsequent querying and analysis.

[0147] Step S217: Generate a statistical result index, which includes the statistical result generation time, equity pool association identifier, and statistical result type.

[0148] The operation analysis module generates a statistical results index, which includes the statistical results generation time (e.g., January 3, 2024, 10:00:00), equity pool association identifier (EP-001), and statistical result type (e.g., operation type statistics, operation frequency statistics, operation duration statistics). The statistical results index will be used for quick querying and locating statistical results.

[0149] Step S220: Compare the operation type statistics, operation frequency statistics, and operation duration statistics with the file usage permission boundaries in the sharing license agreement to determine whether there are any operations that exceed the usage permission boundaries.

[0150] In this embodiment, the smart contract (contract A) compares the generated operation type statistics, operation frequency statistics, and operation duration statistics with the file usage permission boundaries in the shared license agreement to determine whether there are any operations that exceed the usage permission boundaries.

[0151] The operation analysis module extracts the file usage permission boundaries from the shared license agreement. These boundaries include allowed operation types (data query, data download), usage frequency limit (3 times per day), and usage time range (9:00-18:00 on weekdays). Then, it compares the operation types in the operation type statistics with the allowed operation types to check for any disallowed operation types; it compares the operation frequency in the operation frequency statistics with the usage frequency limit to check for any operation frequencies exceeding the limit; and it compares the operation time in the operation duration statistics with the usage time range to check for any operation times exceeding the time range. For example, if the operation type statistics show "modify," it indicates an operation exceeding the usage permission boundaries; if the operation frequency statistics show 4 queries per day within a certain statistical period, it indicates an operation exceeding the usage permission boundaries; and if the operation duration statistics show an operation at 20:00, it indicates an operation exceeding the usage permission boundaries.

[0152] Step S230: If there is an operation that exceeds the usage permission boundary, generate a permission violation record. The permission violation record includes the type of violation, the time of violation, the number of violations, and the consequences of the violation.

[0153] If the operation analysis module determines that an operation exceeds the usage permission boundary, the smart contract's violation record generation module will generate a permission violation record. This record includes the type of violation (e.g., modification, excessive querying), the violation time (e.g., the specific time the operation occurred), the number of violations (e.g., the number of times the violation occurred), and the consequences (e.g., affecting the integrity of the archive data, causing an imbalance in rights allocation). For example, if the violation type is excessive querying, the violation time is January 4, 2024, at 10:00:00, the number of violations is 2, and the consequence is that rights allocation needs to be readjusted.

[0154] Step S240: Associate the permission violation record with the shared collaboration rights pool, and determine the rights penalty method according to the violation handling rules pre-stored in the smart contract. The rights penalty method includes the reduction of rights percentage and the duration of rights freeze.

[0155] The violation record generation module associates permission violation records with the shared collaboration equity pool, specifically through an equity pool association identifier (EP-001). Then, the smart contract penalty determination module determines the penalty method based on the pre-stored violation handling rules within the smart contract. These rules specify the reduction in equity percentage and the duration of equity freeze for different violation types and frequencies. For example, for excessive queries with two violations, the equity percentage reduction is 0.05, and the equity freeze duration is one month.

[0156] Step S250: Based on the aforementioned rights penalty method, adjust the rights percentage of the collaborative entities in the shared collaborative rights pool and generate rights penalty records.

[0157] The penalty method determination module will adjust the equity percentage of collaborative entities in the shared collaboration equity pool based on the determined penalty method. For example, if Research Institution A's equity percentage is 41.4%, and the equity percentage decreases by 0.05, then the adjusted equity percentage will be 41.4% - 0.05 × 41.4% = 39.33%. Simultaneously, Research Institution A's equity will be frozen for one month. The penalty method determination module will generate an equity penalty record, which includes the adjustment time (e.g., January 4, 2024, 11:00:00), the equity percentage before adjustment (Research Institution A 41.4%), the equity percentage after adjustment (Research Institution A 39.33%), the equity freeze duration (one month), and the basis for the penalty (violation of excessive query frequency).

[0158] Step S260: Send the records of permission violations and penalty records to the blockchain distributed ledger for storage.

[0159] The violation record generation module sends the permission violation records and penalty records to the ledger nodes of the blockchain distributed ledger. The ledger nodes verify and write the permission violation records and penalty records in a manner similar to step S1511, storing them in the blockchain distributed ledger to ensure the immutability and traceability of the records.

[0160] Step S270: Send a permission violation notification to the terminal corresponding to the sharing requester, informing them of the violation content and the penalty results in the permission violation notification.

[0161] The smart contract's notification module sends a permission violation notification to the terminal corresponding to the sharing requester (Research Institution A). This notification includes the violation details (such as the type of violation, the time of violation, the number of violations, and the consequences of the violation) and the penalty results (such as the reduction in equity percentage and the duration of equity freeze), so that Research Institution A can understand its violation and the penalty results.

[0162] Step S280: Synchronize the permission violation records and rights penalty records with the terminal corresponding to the file holder, and allow the file holder to initiate a rights adjustment objection application through a smart contract.

[0163] The notification sending module will synchronize the records of permission violations and rights penalties with the terminal corresponding to the archive holder (Research Institution B). Simultaneously, the smart contract will provide an interface allowing the archive holder to initiate a rights adjustment objection request via the smart contract. If the archive holder believes that the rights penalty method is unreasonable or the permission violation record is inaccurate, they can submit an objection request through the smart contract within a specified time (e.g., within 3 business days), which will be adjudicated by the consensus nodes in the blockchain network.

[0164] Based on the same inventive concept, please refer to Figure 2 This paper shows a schematic block diagram of a smart contract-based digital archive sharing and collaboration system 100 for executing the above-described smart contract-based digital archive sharing and collaboration method, provided in an embodiment of this application. The smart contract-based digital archive sharing and collaboration system 100 may include a communication unit 110, a machine-readable storage medium 120, and a processor 130.

[0165] In this embodiment, both the machine-readable storage medium 120 and the processor 130 are located within the smart contract-based digital archive sharing and collaboration system 100 and are configured separately. However, it should be understood that the machine-readable storage medium 120 may also be independent of the smart contract-based digital archive sharing and collaboration system 100 and may be accessed by the processor 130 via a bus interface. Alternatively, the machine-readable storage medium 120 may also be integrated into the processor 130 and may communicate and interact with external systems through the communication unit 110.

[0166] The processor 130 is the control center of the smart contract-based digital archive sharing and collaboration system 100. It connects various parts of the system via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the machine-readable storage medium 120, and by calling data stored in the machine-readable storage medium 120, thereby providing overall monitoring of the smart contract-based digital archive sharing and collaboration system 100. Optionally, the processor 130 may include one or more processing cores; for example, the processor 130 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor. The machine-readable storage medium 120 stores machine-executable instructions for executing the scheme of this application, and the processor 130 executes the machine-executable instructions stored in the machine-readable storage medium 120 to implement the smart contract-based digital archive sharing and collaboration method provided in the foregoing method embodiments.

[0167] It should be noted that, in order to simplify the description of the present invention and thus help to understand one or more embodiments of the invention, multiple features may sometimes be grouped into one embodiment, drawing or description thereof in the foregoing description of the embodiments of the present invention.

Claims

1. A method for sharing and collaborating on digital archives based on smart contracts, characterized in that, The method includes: Upon receiving a request to share digital archives, a shared collaboration rights pool construction process based on the request is triggered using a preset smart contract. The digital archive sharing request includes the requester's identifier, the target digital archive identifier, and a description of the shared collaboration requirements. According to the digital archive collaboration rules pre-stored in the smart contract, the requester identifier, the target digital archive identifier, and the description of the sharing collaboration requirements are mapped to rights allocation parameters. A shared collaboration rights pool is constructed based on the rights allocation parameters. The shared collaboration rights pool includes the rights ratio of the collaboration subject, the archive usage rights node, and the rights transfer triggering conditions. A digital archive sharing license agreement is generated based on the shared collaborative rights pool, and the digital archive sharing license agreement is synchronized to the blockchain network for storage. The sharing license agreement includes the rights pool association identifier, archive usage permission boundaries, and rights transfer rules. According to the file usage permission boundaries in the shared license agreement, the target digital file is subjected to rights binding encryption processing to generate rights binding encrypted file, which includes rights pool association identifier and usage permission trigger key; The rights-binding encrypted file is transmitted to the terminal corresponding to the sharing requester. Based on the smart contract, the usage operation data of the sharing requester on the rights-binding encrypted file is captured in real time. According to the usage operation data and the rights transfer triggering conditions of the shared collaboration rights pool, the rights ratio of the collaborative entities in the shared collaboration rights pool is dynamically adjusted, and the adjustment result is written into the blockchain distributed ledger. The step involves mapping the requester's identifier, the target digital archive identifier, and the description of the shared collaboration requirement to equity allocation parameters based on the pre-stored digital archive collaboration rules in the smart contract, and constructing a shared collaboration equity pool based on the equity allocation parameters, including: Read the pre-stored digital archive collaboration rules from the collaboration rule storage area of ​​the smart contract. The digital archive collaboration rules include a mapping table of collaboration task types and equity coefficients, a comparison table of archive usage frequency and equity adjustment ratio, and a rule relating collaboration cycle and equity transfer interval. The extracted requester identifier is matched with the pre-stored collaboration entity qualification information in the smart contract to determine the requester's collaboration qualification level, and a qualification equity coefficient is generated based on the collaboration qualification level. Match the collaborative task types in the shared collaboration requirements description with the collaborative task types and rights coefficient mapping table in the digital archive collaboration rules, and extract the corresponding task rights coefficients. Match the frequency of archive usage in the description of shared collaboration needs with the comparison table of archive usage frequency and rights adjustment ratio in the digital archive collaboration rules, and extract the corresponding usage rights adjustment ratio; The collaboration cycle in the description of shared collaboration needs is matched with the collaboration cycle and rights transfer interval association rule in the digital archive collaboration rules, and the corresponding rights transfer interval parameter is extracted. The qualification equity coefficient, task equity coefficient, usage equity adjustment ratio and equity transfer interval parameters are integrated into equity allocation parameters; Based on the qualification equity coefficient and task equity coefficient in the equity allocation parameters, the initial equity ratio of each entity in the list of collaborating entities is determined. Based on the usage rights adjustment ratio in the rights allocation parameters, file usage rights nodes are set, and the file usage rights nodes include usage frequency thresholds, rights enhancement nodes, and rights reduction nodes. Based on the rights transfer interval parameter in the rights allocation parameters, and combined with the rights transfer trigger condition template in the digital archive collaboration rules, rights transfer trigger conditions are generated. The rights transfer trigger conditions include transfer interval trigger conditions, usage operation trigger conditions, and rights ratio adjustment trigger conditions. By integrating the proportion of rights and interests of the collaborating entities, the nodes of rights and interests for file use, and the triggering conditions for rights and interests transfer, a structured shared collaborative rights and interests pool is constructed, and a unique rights and interests pool identifier is assigned to the shared collaborative rights and interests pool.

2. The method for sharing and collaborating on digital archives based on smart contracts according to claim 1, characterized in that, The process of receiving a digitized archive sharing request and triggering a shared collaborative equity pool construction process based on the digitized archive sharing request using a preset smart contract includes: Establish a secure communication link with the end that sends the digitized archive sharing request, and receive the digitized archive sharing request through the secure communication link; The digital archive sharing request is parsed to extract the requester identifier, the target digital archive identifier, and the sharing collaboration requirement description, which includes the collaboration task type, collaboration period, and archive usage frequency requirement. The system queries a preset smart contract association table and determines the corresponding preset smart contract based on the target digital file identifier. The smart contract association table records the mapping relationship between different digital file identifiers and corresponding smart contracts in terms of collaboration rules. Send a rights pool construction trigger instruction to the predetermined smart contract. The rights pool construction trigger instruction carries the parsed requester identifier, target digital file identifier and sharing collaboration requirement description. After receiving the equity pool construction trigger instruction, the preset smart contract starts the built-in shared collaborative equity pool construction process and reads the basic equity parameters corresponding to the target digital archive identifier from the contract storage area. The basic equity parameters include the basic equity ratio of the archive holder, the equity coefficient of the collaborative task, and the basic rules for equity transfer. The shared collaboration requirement description in the trigger instruction for building the rights pool is associated and matched with the basic rights parameters to generate initial parameters for building the rights pool. The initial parameters for building the rights pool include a list of collaborating entities, an initial rights allocation ratio, and a rights adjustment benchmark threshold.

3. The method for sharing and collaborating on digital archives based on smart contracts according to claim 1, characterized in that, The process of generating a digital archive sharing license agreement based on the shared collaborative rights pool and synchronizing the digital archive sharing license agreement to the blockchain network for notarization includes: Extract the rights pool identifier from the shared collaboration rights pool and write it as the rights pool association identifier into a specified field of the shared license agreement template; Based on the file usage rights nodes in the shared collaboration rights pool, the file usage permission boundaries are determined. The file usage permission boundaries include the allowed usage operation types, usage frequency limits, and usage time ranges. The file usage permission boundaries are written into the shared license agreement template. Extract the rights transfer trigger conditions from the shared collaborative rights pool, combine them with the rights transfer rule template pre-stored in the smart contract, generate rights transfer rules, the rights transfer rules include the method of adjusting the proportion of the main rights after the rights transfer is triggered, the method of recording rights transfer, and the method of handling transfer objections, and write the rights transfer rules into the shared license agreement template; Add the requester identifier, target digitized archive identifier, and collaboration cycle information to the sharing license agreement template to generate a complete digitized archive sharing license agreement; Perform a hash operation on the digital archive sharing license agreement to generate a protocol hash value; The digital archive sharing license agreement and its corresponding protocol hash value are sent to the evidence storage node of the blockchain network; The evidence storage node performs integrity verification on the digital archive sharing license agreement and the protocol hash value. After the verification is successful, the digital archive sharing license agreement and the protocol hash value are written into the blockchain evidence storage ledger, and an evidence storage certificate is generated. The evidence storage certificate includes the evidence storage time, the evidence storage node identifier and the protocol hash value. The stored evidence is returned to the smart contract, which then associates and stores the evidence with the shared collaborative rights pool.

4. The method for sharing and collaborating on digital archives based on smart contracts according to claim 1, characterized in that, The step of performing rights-binding encryption processing on the target digitized archive according to the archive usage permission boundaries in the shared license agreement to generate rights-binding encrypted archives includes: Extract the file usage permission boundaries from the shared license agreement, determine the allowed operation types and usage frequency limits, and generate permission encryption parameters; Extract the rights pool association identifier from the shared collaboration rights pool and write it as encrypted association information into the permission encryption parameters; The smart contract's built-in rights-binding encryption algorithm is invoked to input the original data of the target digitized archive into the archive data encryption module. The encryption association information in the permission encryption parameters is used to generate a basic encryption key. The original data of the target digitized archive is then encrypted in segments to obtain the archive encryption segment. The rights-binding encryption algorithm includes a permission parameter encryption module, an archive data encryption module, and a key association module. Based on the permitted operation types in the file usage permission boundary, a corresponding usage permission trigger key is generated, and each permitted operation type corresponds to a unique usage permission trigger key; The rights pool association identifier, file encryption segment and usage permission trigger key are integrated and processed to generate a structural framework for rights-bound encrypted files; Perform checksum calculation on each component of the structure framework of the rights-binding encrypted file, generate a checksum corresponding to each component, and attach the checksum to the corresponding component to obtain the complete rights-binding encrypted file.

5. The method for sharing and collaborating on digital archives based on smart contracts according to claim 4, characterized in that, The process involves invoking the built-in rights-binding encryption algorithm of the smart contract, inputting the original data of the target digitized archive into the archive data encryption module, generating a basic encryption key using the encryption association information in the permission encryption parameters, and performing segmented encryption on the original data of the target digitized archive to obtain the archive encrypted segment, including: Start the smart contract's built-in rights binding encryption algorithm, and initialize the permission parameter encryption module, file data encryption module, and key association module; Input the permission encryption parameters into the permission parameter encryption module, and perform encryption processing on the rights pool association identifier, allowed operation type and usage frequency limit to generate encrypted permission parameters. The encryption permission parameters are sent to the key association module, which extracts the rights pool association identifier and performs a hash operation on the rights pool association identifier to generate a hash value. The hash value is used as the base key seed, and combined with the key generation algorithm pre-stored in the smart contract, a base encryption key is generated. The original data of the target digitized archive is divided into multiple data segments, each containing a data segment identifier and data content; Each data segment is input into the archive data encryption module in sequence, and the data content in the data segment is encrypted using the basic encryption key to generate encrypted data content. The data segment identifier is integrated with the corresponding encrypted data content to generate an archive encrypted segment unit; All encrypted segments of the archive are sorted according to the original data segmentation order of the target digitized archive to generate a complete encrypted segment.

6. The method for sharing and collaborating on digital archives based on smart contracts according to claim 1, characterized in that, The process of transmitting the encrypted rights-bound file to the terminal corresponding to the sharing requester, capturing the sharing requester's usage data of the encrypted rights-bound file in real time based on the smart contract, dynamically adjusting the rights ratio of the collaborative entities in the shared collaborative rights pool according to the usage data and the rights transfer trigger conditions of the shared collaborative rights pool, and writing the adjustment result into the blockchain distributed ledger includes: Establish a transmission channel for the encrypted files bound to rights. This transmission channel is associated with the operation capture module of the smart contract. During the transmission process, the transmission progress data is synchronized to the operation capture module in real time. The rights-binding encrypted file is divided into multiple transmission units. Each transmission unit contains a unit identifier, a transmission sequence number, and encrypted data content, which are then sent sequentially to the terminal corresponding to the sharing requester through the transmission channel. After receiving all transmission units, the terminal corresponding to the sharing requester reassembles them according to the transmission sequence number to obtain a complete rights-binding encrypted file, and sends a reception completion feedback to the smart contract. After receiving the feedback that the reception is complete, the smart contract starts the operation capture module to capture the operation data of the sharing requester terminal on the use of the rights-bound encrypted file in real time. The operation data includes operation type, operation time, operation duration and operation result. The captured usage data is transmitted in real time to the rights adjustment module of the smart contract, and the rights adjustment module extracts the rights transfer trigger conditions from the shared collaborative rights pool. The operation data will be matched with the equity transfer triggering conditions to determine whether the equity transfer triggering conditions are met. If they are met, the corresponding equity adjustment rules will be extracted. Based on the rights and interests adjustment rules and usage data, calculate the adjustment range of the rights and interests ratio of the collaborating entities; Based on the aforementioned adjustment range, the equity ratio of collaborative entities in the shared collaborative equity pool is dynamically adjusted, and an equity adjustment record is generated. The equity adjustment record includes the adjustment time, equity ratio before adjustment, equity ratio after adjustment, and adjustment basis. Perform a hash operation on the equity adjustment record to generate an adjustment record hash value; Send the equity adjustment record and the hash value of the adjustment record to the ledger node of the blockchain distributed ledger; The accounting node verifies the equity adjustment record and its hash value. After confirming the integrity and legality of the record, it writes the equity adjustment record and its hash value into a block of the blockchain distributed ledger. This block connects with other blockchains through a consensus mechanism. The smart contract sends notification information that the operation record has been written into the ledger to the terminal corresponding to the sharing requester and the terminal corresponding to the file holder.

7. The method for sharing and collaborating on digital archives based on smart contracts according to claim 6, characterized in that, After receiving the feedback indicating completion of reception, the smart contract activates the operation capture module to capture in real time the operation data of the requesting terminal regarding the use of the rights-bound encrypted file, including: The smart contract sends an operation capture authorization instruction to the terminal corresponding to the sharing requester. The operation capture authorization instruction includes the capture range and data transmission format requirements. After receiving the operation capture authorization instruction, the terminal corresponding to the sharing requester starts the local operation monitoring component. This operation monitoring component establishes an association with the opening program of the rights-bound encrypted file and monitors the operation behavior of the opening program in real time. When the program is detected to perform an operation on the encrypted file bound to rights, the operation monitoring component records the operation type and synchronously obtains the system time as the operation time. The time difference from the start to the end of the operation is calculated as the operation duration. Capture the return result after the operation is executed, determine whether the operation was successful, and use the determination result as the operation result; The operation type, operation time, operation duration, and operation result are integrated into the operation data according to the data transmission format specified by the smart contract; The operation data is sent to the smart contract's operation capture module in real time via a secure communication link; After receiving the operation data, the operation capture module performs format validation on the operation data and checks whether the data fields are complete. If the format validation passes, the operation data is stored in the operation data buffer. If the format validation fails, a data retransmission instruction is returned to the terminal corresponding to the sharing requester.

8. The method for sharing and collaborating on digital archives based on smart contracts according to claim 1, characterized in that, After capturing the usage data of the sharing requester on the rights-bound encrypted file in real time based on the smart contract, the method further includes: The smart contract-based operation analysis module performs classification and statistics on the captured usage operation data, generating operation type statistics, operation frequency statistics, and operation duration statistics. The operation type statistics, operation frequency statistics, and operation duration statistics are compared with the file usage permission boundaries in the shared license agreement to determine whether there are any operations that exceed the usage permission boundaries. If any operation exceeds the scope of the access permission, a permission violation record is generated. The permission violation record includes the type of violation, the time of violation, the number of violations, and the consequences of the violation. The permission violation records are associated with the shared collaboration rights pool. Based on the violation handling rules pre-stored in the smart contract, the rights penalty method is determined, which includes the reduction of rights percentage and the duration of rights freeze. Based on the aforementioned rights and penalties method, the rights and interests ratio of the collaborative entities in the shared collaborative rights and interests pool are adjusted, and rights and penalties records are generated. Records of permission violations and penalties will be sent to a blockchain distributed ledger for storage. Send a permission violation notification to the terminal corresponding to the sharing requester, informing them of the violation content and the penalty results in the permission violation notification; Synchronize records of permission violations and rights penalties with the terminal corresponding to the archive holder, and allow the archive holder to initiate an objection to rights adjustment through a smart contract.

9. A digital archive sharing and collaboration system based on smart contracts, characterized in that, include: processor; A machine-readable storage medium for storing machine-executable instructions of the processor; The processor is configured to execute the smart contract-based digital archive sharing and collaboration method according to any one of claims 1 to 8 by executing the machine-executable instructions.

Images