Consortium blockchain-based methods, devices, and systems for multi-concurrency, multi-file collaboration.

By adopting a consortium blockchain-based multi-concurrency, multi-file collaboration method, a summary document is generated, confirmed on the blockchain, and file attribute information and ontology upload are asynchronously decoupled. This solves the problem of low file collaboration efficiency in high-concurrency scenarios and achieves efficient and secure file collaboration.

CN123115079APending Publication Date: 2026-11-17HANGZHOU HIGH-TECH ZONE (BINJIANG) INSTITUTE OF BLOCKCHAIN & DATA SECURITY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610917781.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-06-24
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In enterprise multi-department collaboration scenarios, file collaboration efficiency is low under high concurrency. Centralized cloud servers are prone to service response delays and single points of failure, resulting in low collaboration efficiency and security risks.

Method used

A multi-concurrency, multi-file collaborative approach based on consortium blockchain is adopted. By generating a summary document and confirming it on the blockchain, the integrity and reliable traceability of file versions are guaranteed by leveraging the immutability of the consortium blockchain. File attribute information is asynchronously decoupled from the ontology upload step, and priority sorting and parallel upload mechanisms improve file upload efficiency.

Benefits of technology

It improves the efficiency of multi-file collaboration in high-concurrency scenarios, reduces file upload pressure and the possibility of collaboration chaos, and ensures file version consistency and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115079A_ABST
    Figure CN123115079A_ABST
Patent Text Reader

Abstract

This application relates to a method, apparatus, and system for multi-concurrency, multi-file collaboration based on a consortium blockchain. The method includes: acquiring files to be synchronized and generating a first summary document based on the hash value and attribute information of the files to be synchronized; submitting the first summary document to a consortium blockchain node deployed on a server, so that the consortium blockchain node writes the first summary document into a block of the consortium blockchain; after the first summary document is on the blockchain, uploading the files to be synchronized to a file storage module on the server using the hash value of the files to be synchronized as the storage index key, so that the file storage module stores the files to be synchronized if it determines that the hash value in the storage index key is consistent with the hash value of the corresponding files to be synchronized in the first summary document. This application solves the problem of low efficiency in multi-file collaboration under high concurrency scenarios.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of blockchain, and in particular to methods, apparatus and systems for multi-concurrency multi-file collaboration based on consortium blockchains. Background Technology

[0002] In multi-departmental collaboration scenarios within an enterprise, multiple collaborators often need to concurrently edit and submit a large number of files related to the same project. Each edit and submission may involve changes to dozens or even hundreds of files. However, in high-concurrency scenarios, uploading changed files to a central server will lead to severe bandwidth bottlenecks and server-side write load pressure. Especially when collaborators from multiple departments submit files intensively at the same time, network congestion and upload queuing significantly reduce collaboration efficiency, increase file synchronization delays, and seriously affect the speed of business process advancement.

[0003] Among related technologies, cloud-based collaborative office platforms are selected, using centralized cloud servers to store files and supporting multiple users editing the same document online in real time. All versions of the file are managed uniformly by the cloud platform, and collaborators can directly operate the cloud files through a browser or client. This type of solution relies on the storage and computing power of centralized servers, which is prone to service response delays or even downtime under high concurrency access, and also poses a single point of failure risk, resulting in low efficiency for multi-file collaboration.

[0004] Currently, no effective solution has been proposed to address the issue of low file collaboration efficiency in high-concurrency scenarios in related technologies. Summary of the Invention

[0005] This application provides a method, apparatus, and system for multi-concurrency multi-file collaboration based on consortium blockchains, in order to improve file collaboration efficiency in high-concurrency scenarios.

[0006] In a first aspect, embodiments of this application provide a multi-concurrency, multi-file collaborative method based on a consortium blockchain, applied to a first terminal, the method comprising:

[0007] Obtain the file to be synchronized, and generate a first summary document based on the hash value and attribute information of the file to be synchronized;

[0008] Submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain;

[0009] After the first summary document is uploaded to the blockchain, the file to be synchronized is uploaded to the file storage module on the server side using the hash value of the file to be synchronized as the storage index key. This allows the file storage module to store the file to be synchronized if it determines that the hash value in the storage index key matches the hash value of the corresponding file to be synchronized in the first summary document.

[0010] In some embodiments, the file storage module that uploads the file to be synchronized to the server includes:

[0011] The priority level of the file to be synchronized is determined based on its size; the smaller the file, the higher the priority level.

[0012] Add the corresponding file to be synchronized to the upload queue;

[0013] Files are uploaded to the file storage module in the upload queue in descending order of priority.

[0014] In some embodiments, after adding the corresponding file to be synchronized to the upload queue, the method further includes:

[0015] Receive priority upgrade instruction; the priority upgrade instruction is generated by the server when it receives a download request instruction for a target file initiated by the second terminal and determines that the target file has not been stored in the file storage module;

[0016] In the upload queue, a target file is determined according to the priority boosting instruction, and the priority of the target file in the upload queue is increased; or, in the upload queue, a target file is determined according to the priority boosting instruction, a second upload channel is established in parallel with the first upload channel where the current upload queue is located, and the target file is uploaded by the second upload channel.

[0017] In some embodiments, the method further includes:

[0018] Obtain a second summary document uploaded by a third terminal in the consortium blockchain; the second summary document includes hash values ​​and attribute information corresponding to one or more associated files, wherein the associated files are files to be synchronized obtained by the third terminal;

[0019] In response to the user's selection of associated files in the second summary document, the target file to be downloaded in the associated file and the priority level of the target file for download are determined, and a download request instruction is generated based on the hash value of the target file in the second summary document, the attribute information of the target file, and the priority level;

[0020] The download request instruction is uploaded to the server, so that the server responds to the download request instruction by determining the target file in the file storage module and sending the download address of the target file to the first terminal;

[0021] Receive the download address and obtain the target file based on the download address.

[0022] In some embodiments, obtaining the file to be synchronized includes:

[0023] Scan the files in the first terminal;

[0024] The current scan results of the first terminal are compared with the historical scan results, and one or more files that show differences are selected as the files to be synchronized.

[0025] Secondly, embodiments of this application provide a multi-concurrency, multi-file collaborative method based on a consortium blockchain, applied to a server. The server includes a file storage module and a server deploying consortium blockchain nodes. The method includes:

[0026] The system receives a summary document uploaded by a first terminal; the summary document includes a hash value generated by the first terminal based on the file to be synchronized, and attribute information of the file to be synchronized.

[0027] The consortium blockchain node writes the summary document into a block of the consortium blockchain;

[0028] Receive the file to be synchronized uploaded by the first terminal, and the hash value of the file to be synchronized;

[0029] When the hash value of the file to be synchronized matches the hash value of the file to be synchronized in the summary document, the file to be synchronized is stored in the file storage module using the hash value as the storage index key.

[0030] In some embodiments, the method further includes:

[0031] Receive a download request instruction for a target file initiated by a second terminal, and obtain the target hash value of the target file according to the download request instruction;

[0032] In the file storage module, the target file is located based on the target hash value, and the download address of the target file is sent to the second terminal.

[0033] In some embodiments, after searching for the target file based on the target hash value in the file storage module, the method further includes:

[0034] In the file storage module, if the target file cannot be indexed based on the target hash value, the priority level and attribute information of the target file are obtained according to the download request instruction.

[0035] The third terminal for uploading the target file is determined based on the attribute information of the target file;

[0036] A priority upgrade instruction for the target file is generated based on the priority level, the initiation time of the download request instruction, and the load of the file upload channel of the third terminal.

[0037] The priority increase instruction is sent to the third terminal, so that the third terminal responds to the priority increase instruction by increasing the priority of uploading the target file to the file storage module, or responds to the priority increase instruction by uploading the target file and other files in parallel.

[0038] Thirdly, embodiments of this application provide a multi-concurrency, multi-file collaborative device based on a consortium blockchain, including:

[0039] The file acquisition module is used to acquire the files to be synchronized and generate a first summary document based on the hash value and attribute information of the files to be synchronized.

[0040] The first submission module is used to submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain.

[0041] The second submission module is used to upload the file to be synchronized to the file storage module on the server side after the first summary document is uploaded to the blockchain, using the hash value of the file to be synchronized as the storage index key. This allows the file storage module to store the file to be synchronized if it determines that the hash value in the storage index key is consistent with the hash value of the corresponding file to be synchronized in the first summary document.

[0042] Fourthly, embodiments of this application provide a multi-concurrency, multi-file collaborative system based on a consortium blockchain, comprising: a terminal and a server, wherein the terminal is used to execute the method described in the first aspect above, and the server is used to execute the method described in the second aspect above.

[0043] Compared to related technologies, the multi-concurrency multi-file collaboration method, apparatus, and system based on consortium blockchain provided in this application aggregates the attribute information and hash values ​​of all files to be synchronized in each submission into a summary document. Only the summary document is uploaded to the blockchain for consensus confirmation. This leverages the immutability of the consortium blockchain to ensure the integrity and reliable traceability of file versions, reducing the possibility of file collaboration chaos and improving collaboration efficiency. The upload of the file body to be synchronized runs as an independent process, achieving asynchronous decoupling between the submission of file attribute information and hash values ​​and the upload of the file body, and ensuring the consistency between the summary document and the file body. The above decoupling design allows other collaborative terminals connected to the server to obtain the hash value and attribute information of the file synchronized by the first terminal after the summary document is submitted. This allows for advance task planning based on the hash value and attribute information of the synchronized file, without waiting for all file bodies to be uploaded. The time complexity of file submission confirmation depends only on the consensus time of the summary document, rather than the total upload time of the file body. At the same time, the bandwidth pressure of file body upload is distributed to the time window after consensus is completed, reducing file upload pressure and improving the multi-file collaboration efficiency in high-concurrency scenarios.

[0044] Details of one or more embodiments of this application are set forth in the following drawings and description to make other features, objects and advantages of this application more readily apparent. Attached Figure Description

[0045] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0046] Figure 1 This application provides a diagram illustrating a multi-concurrency, multi-file collaborative application scenario based on a consortium blockchain.

[0047] Figure 2 A flowchart of an embodiment of the multi-concurrency, multi-file collaboration method based on consortium blockchain provided in this application;

[0048] Figure 3 This is a schematic diagram illustrating a general document uplink to the blockchain, as shown in an exemplary embodiment of this application.

[0049] Figure 4 A flowchart of Embodiment 2 of the consortium blockchain-based multi-concurrency, multi-file collaboration method provided in this application;

[0050] Figure 5 A flowchart of Embodiment 3 of the consortium blockchain-based multi-concurrency, multi-file collaboration method provided in this application;

[0051] Figure 6A flowchart of Embodiment 4 of the consortium blockchain-based multi-concurrency multi-file collaboration method provided in this application;

[0052] Figure 7 A flowchart of Embodiment 5 of the consortium blockchain-based multi-concurrency multi-file collaboration method provided in this application;

[0053] Figure 8 The structural block diagram of the multi-concurrency, multi-file collaborative method device based on consortium blockchain provided in this application. Detailed Implementation

[0054] To make the objectives, technical solutions, and advantages of this application clearer, the application is described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the application. All other embodiments obtained by those skilled in the art based on the embodiments provided in this application without inventive effort are within the scope of protection of this application. Furthermore, it is understood that although the efforts made in such a development process may be complex and lengthy, for those skilled in the art related to the content disclosed in this application, modifications to design, manufacturing, or production based on the technical content disclosed in this application are merely conventional technical means and should not be construed as insufficient disclosure of the content of this application.

[0055] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment that is mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application may be combined with other embodiments without conflict.

[0056] Unless otherwise defined, the technical or scientific terms used in this application shall have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms “a,” “an,” “an,” “the,” and similar words used in this application do not indicate quantity limitation and may indicate singular or plural. The terms “comprising,” “including,” “having,” and any variations thereof used in this application are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units not listed, or may include other steps or units inherent to these processes, methods, products, or devices. The terms “connected,” “linked,” “coupled,” and similar words used in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. “Multiple” used in this application means two or more. “And / or” describes the relationship between related objects, indicating that three relationships may exist; for example, “A and / or B” can represent: A alone, A and B simultaneously, and B alone. The terms “first,” “second,” “third,” etc., used in this application are merely to distinguish similar objects and do not represent a specific ordering of the objects.

[0057] This embodiment provides an application scenario for multi-concurrency, multi-file collaboration based on a consortium blockchain. Figure 1 This is a diagram illustrating an application scenario of multi-concurrency, multi-file collaboration based on a consortium blockchain, according to an embodiment of this application. Figure 1 As shown, the system includes at least one terminal 12 and a server 14. The terminal 12 and the server 14 communicate via a network, which may include a local area network (LAN), a wide area network (WAN), the Internet, or a combination thereof, and is connected to a website, user equipment (e.g., computing devices), and a backend system.

[0058] Terminal 12 obtains the file to be synchronized, generates a first summary document based on the hash value and attribute information of the file to be synchronized, and then submits the summary document, the file to be synchronized, and its hash value to server 14. Terminal 12 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, and IoT devices.

[0059] Server 14 is deployed with consortium blockchain nodes, which are interconnected to form a consortium blockchain network. The consortium blockchain is a blockchain network jointly maintained by multiple pre-selected nodes. Nodes must be authorized to participate in consensus, balancing decentralization and controllability. Server 14 also deploys a file storage module. This module stores files to be synchronized and can be implemented using a centralized file server or an enterprise-grade object storage service (such as MinIO or Ceph) as the file storage backend, leveraging its native sharded upload, breakpoint resume, and parallel transmission capabilities to further improve the transmission efficiency of large files. Server 14 can write the first generalized document into blocks on the consortium blockchain through the consortium blockchain nodes and store files to be synchronized through the file storage module deployed on the server. Optionally, server 14 can be a node in a cloud computing system (not shown in the figure), or each server 14 can be a separate cloud computing system, including multiple computers interconnected by a network and operating as a distributed processing system. Server 14 can run any suitable computing system, enabling it to function as a node in the consortium blockchain network 16.

[0060] based on Figure 1 The application scenario diagram shown illustrates that this embodiment provides a multi-concurrency, multi-file collaboration method based on a consortium blockchain. Figure 2 This is a flowchart of a multi-concurrency, multi-file collaborative method based on a consortium blockchain according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0061] Step S201: Obtain the file to be synchronized, and generate a first summary document based on the hash value and attribute information of the file to be synchronized.

[0062] The files to be synchronized are one or more files that the first terminal needs to submit to the file storage module. These files can be files specified by the first terminal user or modified files obtained from scanning the file body. In one possible implementation, obtaining the files to be synchronized includes the following steps: scanning files in the first terminal; comparing the current scan results with historical scan results, and identifying one or more files with discrepancies as the files to be synchronized. For example, the first terminal scans all files stored locally, obtaining metadata such as filename, path, size, and last modified time for each file; comparing the metadata obtained from the current scan (current scan results) with the corresponding metadata saved from historical scans (historical scan results); and based on the comparison results, identifying one or more files whose content, size, modification timestamp, or any other attribute has changed, and determining these one or more files as the files to be synchronized.

[0063] For each file to be synchronized, the hash value can be calculated using the SHA-256 secure hash algorithm. It should be understood that other hash algorithms can also be used, and there are no restrictions on the method of hash value calculation.

[0064] The attribute information includes one or more of the following: filename, relative file path, file size, file MIME type, modification timestamp, file version number, change type flag, and hash value of the previous version of the file to be synchronized. Specifically, the change type flag includes: Add (ADD), Modify (MODIFY), and Delete (DELETE). ADD indicates that the file exists in the current scan results but not in the historical scan results; MODIFY indicates that the file exists in both the current and historical scan results, but its metadata has changed; DELETE indicates that the file exists in the historical scan results but not in the current scan results.

[0065] Optionally, after obtaining the attribute information and hash values ​​of all files to be synchronized, the first terminal automatically generates a summary document. This summary document is a structured metadata file encoded in JSON format, including commit header information and a file list (an array of files to be synchronized). The commit header information may include one or more of the following fields: a globally unique identifier for this commit (commitId, generated by the UUID algorithm), a commit timestamp, the committer's identity, the committer's department identifier, the total number of files to be synchronized, the total size of the files to be synchronized, and the identifier of the previous commit (parentCommitId, used to build the commit chain) or the initial commit identifier.

[0066] The following table, Table 1, provides a detailed explanation of the fields that may be involved in the summary document:

[0067] Table 1. Fields that may be involved in the summary document

[0068]

[0069] Each file record in the fileList array contains complete metadata for that file. Table 2 describes the metadata for each file record in the fileList array:

[0070] Table 2 shows the metadata for each file record in the fileList array.

[0071]

[0072] Step S202: Submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain.

[0073] A first terminal sends a first summary document to a consortium blockchain node deployed on the server. Upon receiving the first summary document, the node in the consortium blockchain triggers a smart contract deployed on the chain to execute pre-defined verification logic to verify the legality and validity of the summary document. The verification logic includes, but is not limited to: verifying whether the document format conforms to predefined specifications; and verifying whether the submitter corresponding to the first terminal is a legitimate member node of the consortium blockchain, specifically by verifying the digital certificate or public key provided by the submitter. Once the smart contract confirms that the summary document is legal and valid, the consortium blockchain nodes, based on the Practical Byzantine Fault Tolerance (PBFT) consensus mechanism, reach a consensus and write the summary document and the hash values ​​of all files to be synchronized contained within it as transaction data into a newly generated block, completing the on-chain notarization. Figure 3 A general diagram illustrating document uplink is provided, such as... Figure 3 As shown, the data payload of each block (Block N-1, Block N, Block N+1) on the consortium blockchain contains the complete content of one or more summary documents. For example, Block N-1 may include the hashes of 15 files in summary document A, denoted as CommitDoc_A; and the hashes of 8 files in summary document B, denoted as CommitDoc_B. Block N may include the hashes of another 20 files in summary document A, denoted as CommitDoc_A_v2; and the hashes of 5 files in summary document C, denoted as CommitDoc_C. Block N+1 may include the hashes of another 12 files in summary document B, denoted as CommitDoc_B_v2; and the hashes of 3 files in summary document D, denoted as CommitDoc_D. Each block on each consortium blockchain may also record other data from the first summary document, such as commit time, file name, or one or more fields. Figure 3 (Not shown in the image), the specific field content stored in each block can be designed according to requirements.

[0074] Optionally, to further compress the on-chain data volume, the first summary document can be partially processed on-chain. Specifically, a Merkle Tree structure can be used to organize the hash values ​​corresponding to each file to be synchronized in the summary document. For example, extract the file list (fileList) of files to be synchronized from the summary document, obtain the hash value of each file to be synchronized based on fileList; use the hash value of each file to be synchronized as a leaf node of the Merkle Tree, calculate the Merkle root hash layer by layer, and use the Merkle root hash as the integrity digest of all files to be synchronized in the first summary document. The specific construction method of the Merkle tree can be found in the relevant technical documentation, and will not be elaborated here. Subsequently, the Merkle root hash is written into a new block of the consortium blockchain, while the other fields of the first summary document are stored in a trusted off-chain storage system. Compared with the full storage of the first summary document, this further compresses the on-chain data volume.

[0075] After a consortium blockchain node writes the first summary document into a block on the consortium blockchain, the submission of the file to be synchronized by the first terminal is considered confirmed, and all participating consortium blockchain nodes can obtain the summary document submitted this time through on-chain query.

[0076] Step S203: After the first summary document is uploaded to the blockchain, the file to be synchronized is uploaded to the file storage module on the server side using the hash value of the file to be synchronized as the storage index key. This ensures that the file storage module stores the file to be synchronized when it determines that the hash value in the storage index key matches the hash value of the corresponding file to be synchronized in the first summary document.

[0077] The file storage module can employ an object storage system or a distributed file system, where each file is stored using its hash value as the storage index key. After uploading the files to be synchronized to the server's file storage module, the server can establish an end-to-end file integrity guarantee link based on the immutable hash records on the consortium blockchain. Compared to traditional digital signature verification methods, this method, which directly compares the hash values ​​of the files to be synchronized, saves steps such as public key decryption and certificate chain verification, significantly reducing the computational complexity of the verification process and improving verification efficiency.

[0078] Through the aforementioned multi-concurrency, multi-file collaboration steps based on a consortium blockchain, the attribute information and hash values ​​of all files to be synchronized in each submission are aggregated into a lightweight summary document. Only this document is uploaded to the blockchain for consensus confirmation, while the upload of the file itself runs as an independent asynchronous background process. This asynchronous decoupling of the submission of file attribute information and hash values ​​from the upload of the file itself fundamentally eliminates the performance bottleneck in high-concurrency submission scenarios—the time complexity of submission confirmation depends only on the consensus time of the summary document, not the total upload time of the file itself, significantly improving the efficiency of multi-file collaboration in high-concurrency scenarios.

[0079] Furthermore, a first summary document is generated based on the hash value and attribute information of the files to be synchronized. Since the size of a single summary document is typically between several KB and tens of KB, much smaller than the total size of the file it describes, storing the summary document rather than the file itself on-chain ensures lightweight on-chain data. This prevents the consensus efficiency of the consortium blockchain from significantly decreasing with the increase in the number and size of files.

[0080] In some embodiments, uploading a file to be synchronized to a file storage module includes: determining the priority level of the file to be synchronized based on its size; the smaller the file, the higher the priority level; adding the corresponding file to be synchronized to an upload queue; and uploading the file to the file storage module in the upload queue in descending order of priority level.

[0081] For example, the upload queue adopts a priority-based sorting mechanism. By default, all files to be synchronized are sorted according to their file size from smallest to largest, prioritizing the upload of smaller files to quickly complete the synchronization of more files. The first terminal uploads the files to be synchronized to the file storage module one by one according to the priority order in the upload queue, using the hash value of the file to be synchronized as the storage index key during the upload process. To avoid blocking subsequent work of collaborators, the upload operation can optionally be performed asynchronously in the background of the first terminal, ensuring that file upload tasks are processed in parallel outside the main thread of the user interface, so that the responsiveness of the main interface of the first terminal is not affected.

[0082] In this embodiment, the upload priority of the file to be synchronized in the upload queue is obtained according to the file size. By prioritizing the upload of smaller files, the first terminal can complete the synchronization of more files per unit time, avoiding the upload blockage caused by large files monopolizing the transmission channel for a long time, thereby improving the overall response speed and throughput efficiency of the synchronization task.

[0083] Furthermore, in some of these embodiments, Figure 4 The flowchart of Embodiment 2 of the consortium blockchain-based multi-concurrency multi-file collaboration method provided in this application is as follows: Figure 4As shown, after adding the corresponding file to be synchronized to the upload queue, the method also includes:

[0084] Step S401: Receive priority upgrade instruction; the priority upgrade instruction is generated by the server when it receives the download request instruction for the target file initiated by the second terminal and determines that the target file has not been stored in the file storage module.

[0085] The second terminal is another terminal connected to the server. The second terminal can also execute the multi-concurrency multi-file collaboration method based on consortium blockchain as described in any embodiment.

[0086] Optionally, the collaborator on the second terminal selects the desired target file and sends a download request instruction to the server via the second terminal. The target file is the file to be synchronized obtained by the first terminal. If the first terminal has already uploaded the file to be synchronized to the file storage module, the second terminal can directly obtain the target file from the file storage module; if the first terminal has not uploaded the file to be synchronized to the file storage module, the second terminal cannot obtain the target file from the file storage module. In this case, the server needs to respond to the download request instruction for the target file initiated by the second terminal by generating a priority upgrade instruction and sending the priority upgrade instruction to the first terminal.

[0087] Step S402: In the upload queue, determine the target file according to the priority promotion instruction; increase the priority of the target file in the upload queue; or, establish a second upload channel parallel to the first upload channel where the current upload queue is located, and upload the target file through the second upload channel.

[0088] The priority boosting instruction includes the target file's attribute information, which the first terminal uses to determine the target file in the upload queue. The priority boosting instruction can also indicate whether to establish a parallel upload channel. Specifically, for the server side, the priority level of the target file, the initiation time of the download request instruction, and the target file's attribute information can be obtained from the download request instruction. The terminal used to upload the target file can be determined based on the target file's attribute information. A priority boosting instruction for the target file is generated based on the priority level, initiation time, and the load of the terminal's file upload channel. Further, if the load of the terminal's file upload channel is greater than a specified load threshold and supports parallel transmission, the priority boosting instruction can instruct the establishment of a second upload channel parallel to the first upload channel currently in the upload queue. If the load of the terminal's file upload channel is not greater than the specified load threshold and does not support parallel transmission, the priority boosting instruction can instruct the target file to have its priority increased in the queue. The higher the priority level of the target file and the earlier the initiation time of the download request instruction, the higher the priority of the target file in the upload queue after being boosted by the priority boosting instruction.

[0089] Optionally, for the first terminal, if the current transmission load configuration between the first terminal and the server supports multi-channel parallel upload, the first terminal dynamically allocates an independent second upload channel for the target file, enabling it to be uploaded to the server synchronously with other files, thereby maximizing the utilization of available network bandwidth. If the current transmission load configuration between the first terminal and the server does not support multi-channel parallel upload, upon receiving a priority increase instruction, the first terminal immediately moves the target file from its current position in the upload queue to the head of the queue, assigning it the highest priority. If there is an ongoing upload task, the target file is uploaded after the currently pending file is uploaded. If there is no ongoing upload task, the target file is uploaded directly.

[0090] In this embodiment, the first terminal first submits a first summary document to the consortium blockchain, enabling the collaborating party (the second terminal) to quickly determine the file to be uploaded by the first terminal based on the on-chain records. Based on the asynchronous decoupling of the summary document submission and file body submission steps, the first terminal responds to the priority promotion instruction and adjusts the upload order of the target files in the local upload queue, thereby quickly satisfying the target file download request of the second terminal and significantly shortening the waiting time for the collaborators at the second terminal.

[0091] In some of these embodiments, Figure 5 The flowchart of Embodiment 3 of the consortium blockchain-based multi-concurrency multi-file collaboration method provided in this application is as follows: Figure 5 As shown, the multi-concurrency, multi-file collaboration method based on consortium blockchains also includes:

[0092] Step S501: Obtain the second summary document uploaded by the third terminal in the consortium blockchain; the second summary document includes the hash value and attribute information corresponding to one or more associated files, and the associated files are the files to be synchronized obtained by the third terminal.

[0093] In this system, the third terminal connects to the server and can also execute the multi-concurrency, multi-file collaborative method based on a consortium blockchain as described in any embodiment. For example, the third terminal obtains the file to be synchronized, generates a second summary document based on the hash value and attribute information of the file, and submits it to the consortium blockchain node.

[0094] Step S502: In response to the user's selection operation of the associated file in the second summary document, determine the target file to be downloaded in the associated file and the priority level of the target file when downloading, and generate a download request instruction based on the hash value of the target file, the attribute information of the target file, and the priority level in the second summary document.

[0095] The priority levels can be set to three levels: NORMAL, HIGH, and URGENT. It's understandable that the priority levels can be increased or decreased as needed. The target file's attribute information includes the commit ID (commitId) to which the target file belongs, and the target file's SHA-256 hash value (fileHash).

[0096] Specifically, users can query the consortium blockchain through a first terminal to obtain a second summary document, and select one or more target files to download from the second summary document. Users can specify target files using file hash values ​​or unique attribute identifiers (such as file ID, path, name, etc.), set the priority level to URGENT, and send a request to the server to download the target files. For example, the download request instruction includes: a unique identifier for the request (requestId), a requester identifier (requesterId), a commit identifier for the target file (commitId), the SHA-256 hash value of the target file (fileHash), the request priority level, and the request timestamp. Table 3 explains the fields that may be involved in the download request instruction:

[0097] Table 3. Fields that may be involved in the download request instruction

[0098]

[0099] In this embodiment, the requester is the user using the first terminal.

[0100] Step S503: Upload the download request instruction to the server, so that the server responds to the download request instruction, determines the target file in the file storage module, and sends the download address of the target file to the first terminal.

[0101] Step S504: Receive the download address and obtain the target file based on the download address.

[0102] Optionally, the server generates a temporary download address for the target file, and the first terminal downloads the target file from the file storage module using the address and existing communication protocols.

[0103] Furthermore, since the summary document already contains the hash values ​​of all files to be synchronized, any consortium blockchain node can independently verify whether the file downloaded from the central file server is consistent with the original file submitted, thus forming a decentralized file integrity verification mechanism. Specifically, after obtaining the target file, the first terminal can also calculate the hash value of the target file and compare it with the hash value corresponding to the target file in the second summary document. If they are consistent, the target file is obtained according to the download address; if they are inconsistent, steps S502 to S504 can be executed to obtain the target file again.

[0104] In this way, when the target file is uploaded to the central server, a first SHA-256 hash verification is performed, which can be verified by the uploading end (third terminal). After the target file is downloaded, a second hash verification can be performed by the downloading end (first terminal), forming a dual verification mechanism for file hash based on the consortium blockchain. This ensures that both verifications are based on the immutable hash record on the consortium blockchain, forming an end-to-end file integrity guarantee link.

[0105] Through steps S501 to S504, collaborators can quickly browse the overall picture of the submitted files using a summary document, requesting only the files they actually need, thus avoiding the bandwidth waste of indiscriminately downloading all files in traditional solutions. Simultaneously, the first terminal, after confirming the target files to be downloaded based on on-chain data, generates a download address based on actual collaborative needs to achieve the transmission of the target files, avoiding the situation where collaborators passively receive all files. Experiments have shown that in large projects, where a single submission involves 100 files and collaborators only need 5 of them, the on-demand transmission method based on this embodiment can improve effective bandwidth utilization by approximately 20 times.

[0106] In some of these embodiments, Figure 6 This application provides a fourth embodiment of a multi-concurrency, multi-file collaborative method based on a consortium blockchain. Figure 6 The multi-concurrency, multi-file collaborative method based on consortium blockchains shown is applied to the server side and includes the following steps:

[0107] Step S601: Receive a summary document uploaded by the first terminal; the summary document includes a hash value generated by the first terminal based on the file to be synchronized, and attribute information of the file to be synchronized.

[0108] In step S602, the consortium blockchain node writes the summary document into the block of the consortium blockchain.

[0109] Optionally, the summary document includes the submitter's digital certificate, signature, and commit chain identifier `parentCommitId`. The consortium blockchain node triggers the smart contract to execute the following verification logic: verifying the submitter's digital certificate and signature to confirm that the submitter is a legitimate member node of the consortium blockchain; verifying the format integrity of the summary document to ensure all necessary fields are filled in and the data types are correct; and verifying whether `parentCommitId` points to a valid historical commit record. Once the smart contract confirms the summary document is legitimate and valid, the consortium blockchain node, based on the Practical Byzantine Fault Tolerance (PBFT) consensus mechanism and the Raft-based consensus algorithm, writes the summary document and the hash values ​​of all files to be synchronized contained within it as transaction data into the newly generated block.

[0110] Step S603: Receive the file to be synchronized and its hash value uploaded by the first terminal.

[0111] Step S604: When the hash value of the file to be synchronized is consistent with the hash value of the file to be synchronized in the summary document, the file to be synchronized is stored in the file storage module using the hash value as the storage index key.

[0112] Optionally, the server-side verification module or off-chain verification service extracts the hash value contained in the storage index key and compares it with the hash value of the corresponding file to be synchronized recorded in the file list (fileList) in the first summary document. If the two are exactly the same, consistency is determined, and the file is allowed to be written to the storage layer; otherwise, the upload is rejected and a verification failure message is returned. By using the hash value as the storage index key, storage efficiency is improved and the consistency of file storage data is ensured.

[0113] Steps S601 to S604 above involve receiving a summary document via a consortium blockchain, and then storing the corresponding ontology file via a file storage module, achieving asynchronous decoupling between file information and file ontology storage. The immutability of the consortium blockchain ensures the integrity and reliable traceability of file attribute information and hash values, reducing the possibility of file collaboration chaos and improving collaboration efficiency. Subsequently, files to be synchronized are stored, reducing the file upload pressure on these files and further improving file collaboration efficiency.

[0114] In some embodiments, the multi-concurrency, multi-file collaborative method based on consortium blockchain applied to the server side further includes: receiving a download request instruction for a target file initiated by a second terminal, and obtaining the target hash value of the target file according to the download request instruction; in the file storage module, searching for the target file according to the target hash value, and sending the download address of the target file to the second terminal.

[0115] Because the file storage module uses the file's hash value as its unique storage index key, the server can directly locate and retrieve the corresponding target file based on the received target hash value. A temporary download address is generated and returned to the second terminal, allowing the second terminal to download the file within the validity period. The method for generating the download address can be found in relevant technical documentation and will not be elaborated upon here.

[0116] In this embodiment, the target file is located based on the target hash value, which achieves accurate file search; at the same time, the target file is provided through the download address, avoiding the security risk of long-term exposure of the storage path.

[0117] Furthermore, in the file storage module, after finding the target file based on the target hash value, the method further includes: if the target file cannot be indexed based on the target hash value in the file storage module, obtaining the priority level and attribute information of the target file based on the download request instruction; determining the third terminal for uploading the target file based on the attribute information of the target file; generating a priority upgrade instruction for the target file based on the priority level, the initiation time of the download request instruction, and the load of the file upload channel of the third terminal; and sending the priority upgrade instruction to the third terminal so that the third terminal responds to the priority upgrade instruction by increasing the priority of uploading the target file to the file storage module, or responds to the priority upgrade instruction by uploading the target file and other files in parallel.

[0118] Optionally, a priority value can be calculated based on the priority level and the initiation time of the download request. The higher the priority value (newPriority), the higher the priority. For example, the priority value of the target file can be calculated using a weighted scoring model; the priority level is mapped to a first score, and the initiation time is converted to a second score. Higher priority levels correspond to higher weights for the first score, and earlier initiation times correspond to higher weights for the second score. The final priority value is the weighted sum of the first and second scores. Alternatively, a mapping table between priority levels and initiation time intervals can be pre-established, allowing the server to directly look up the priority value based on the request's priority level and the initiation time interval.

[0119] Load includes, but is not limited to, one or more parameters such as network bandwidth utilization and CPU utilization. When the current load of the file upload channel of the third terminal is lower than the preset concurrency threshold, a priority increase instruction is used to instruct the third terminal to establish a parallel upload channel for the target file; conversely, if the upload channel load is not lower than the concurrency threshold, a parallel upload channel is not generated.

[0120] Furthermore, a priority escalation instruction may also include one or more of the following fields: a unique instruction identifier (instructionId), a third-party terminal identifier (targetTerminalId), the target file's hash value (fileHash), the requester's (first-party terminal) identifier (requesterId), and a priority escalation instruction generation timestamp. Table 4 illustrates the fields that may be involved in a priority escalation instruction:

[0121] Table 4. Fields that may be involved in priority promotion instructions

[0122]

[0123] After generating the priority elevation instruction, the server can send the instruction to the third terminal of the file's collaborator via the consortium blockchain network's message channel or a direct TCP connection. Further, after the third terminal uploads the target file to the file storage module, it sends a file ready notification to the requesting terminal (the first terminal), along with the download address of the target file. Table 5 explains the fields that may be involved in the file ready notification:

[0124] Table 5. Fields that may be involved in a file readiness notification.

[0125]

[0126] Optionally, after the third terminal uploads the target file to the file storage module, the server can also update its internal file status table. The file status table uses the file's hash value as the primary key to associate and store the file's metadata information, including but not limited to: the original filename, the upload terminal identifier, and the current storage status. The file status table records the association between file hash values ​​and files in the file storage module, enabling subsequent fast retrieval of uploaded files based on the hash value.

[0127] In this embodiment, by generating a priority boosting instruction, high-priority target files are transmitted first according to file download requirements, effectively shortening the target file upload time and improving file collaboration efficiency.

[0128] The following description is based on specific embodiments. Figure 7 This is a flowchart of Embodiment 5 of the Consortium Blockchain-based Multi-Concurrency Multi-File Collaboration Method according to the embodiments of this application, as follows: Figure 7 As shown, the process includes the following steps:

[0129] In step S701, the first terminal obtains the file to be synchronized and generates a first summary document based on the hash value and attribute information of the file to be synchronized; and submits the first summary document to the consortium blockchain node deployed on the server.

[0130] In step S702, the consortium blockchain node writes the first summary document into the consortium blockchain block.

[0131] In step S703, terminal A uploads the file to be synchronized to the file storage module on the server using the hash value of the file to be synchronized as the storage index key.

[0132] In step S704, if the server determines that the hash value in the storage index key is consistent with the hash value of the corresponding file to be synchronized in the first summary document, it stores the file to be synchronized to the file storage module.

[0133] In step S705, in response to the user's selection of the first general document on the consortium blockchain, terminal B determines the target file to be downloaded and sends a download request instruction to the server.

[0134] In step S706, the server searches for the target file in the file storage module based on the target hash value. If the target file can be found, proceed to step S710; otherwise, proceed to step S707.

[0135] In step S707, the server generates a priority upgrade instruction for the target file based on the download request instruction and sends it to terminal A corresponding to the target file.

[0136] In step S708, terminal A responds to the priority boosting instruction by increasing the priority of the target file in the local upload queue; or, it establishes a second upload channel parallel to the first upload channel where the current upload queue is located, and uploads the target file through the second upload channel.

[0137] In step S709, if the server determines that the hash value of the target file in the storage index key is consistent with the hash value in the first summary document, it stores the file to be synchronized to the file storage module and sends a file ready notification to terminal B.

[0138] In step S710, the server generates and sends the download address of the target file to terminal B.

[0139] In step S711, terminal B downloads the target file according to the download address, calculates the hash value of the target file, and compares whether the calculated hash value is consistent with the hash value corresponding to the target file in the first summary document. If they are consistent, the target file acquisition process ends; if they are inconsistent, step S705 is executed until the calculated hash value is consistent with the hash value corresponding to the target file in the first summary document.

[0140] Specifically, the implementation principles and processes of steps S701 to S711 can be found in the descriptions in the preceding embodiments, and will not be repeated here. It should be noted that the steps shown in the above flow chart or the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0141] This embodiment also provides a multi-concurrency, multi-file collaborative device based on a consortium blockchain. This device is used to implement the above embodiments and preferred embodiments, and details already described will not be repeated. As used below, the terms "module," "unit," "subunit," etc., can refer to a combination of software and / or hardware that performs a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0142] Figure 8 This is a structural block diagram of a multi-concurrency, multi-file collaborative device based on a consortium blockchain, as described in an embodiment of this application. Figure 8 As shown, the device includes:

[0143] The file acquisition module 801 is used to acquire the file to be synchronized and generate a first summary document based on the hash value and attribute information of the file to be synchronized.

[0144] The first submission module 802 is used to submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain.

[0145] The second submission module 803 is used to upload the file to be synchronized to the file storage module on the server side after the first summary document is uploaded to the blockchain, using the hash value of the file to be synchronized as the storage index key. This allows the file storage module to store the file to be synchronized if it determines that the hash value in the storage index key matches the hash value of the corresponding file to be synchronized in the first summary document.

[0146] In some embodiments, the second submission module 803 uploads the file to be synchronized to the file storage module, including: obtaining the priority level of the file to be synchronized based on its file size; the smaller the file, the higher the corresponding priority level; adding the corresponding file to be synchronized to the upload queue; and uploading the file to the file storage module in the upload queue in descending order of priority level.

[0147] Furthermore, after adding the corresponding file to be synchronized to the upload queue, the second submission module 803 further includes: receiving a priority boosting instruction; the priority boosting instruction is an instruction generated by the server when it receives a download request instruction for the target file initiated by the second terminal and determines that the target file has not been stored in the file storage module; in the upload queue, the target file is determined according to the priority boosting instruction, and the priority of the target file in the upload queue is increased; or, in the upload queue, the target file is determined according to the priority boosting instruction, a second upload channel is established in parallel with the first upload channel where the current upload queue is located, and the target file is uploaded by the second upload channel.

[0148] In some embodiments, the apparatus further includes a download module for acquiring a second summary document uploaded by a third terminal in the consortium blockchain. The second summary document includes hash values ​​and attribute information corresponding to one or more associated files, which are files to be synchronized obtained by the third terminal. In response to a user's selection of associated files in the second summary document, the apparatus determines the target file to be downloaded in the associated files and the priority level for downloading the target file, and generates a download request instruction based on the hash value, attribute information, and priority level of the target file in the second summary document. The apparatus uploads the download request instruction to the server, so that the server determines the target file in the file storage module in response to the download request instruction and sends the download address of the target file to the first terminal. The apparatus receives the download address and acquires the target file based on the download address.

[0149] In some embodiments, the file acquisition module 801 acquires the files to be synchronized, including: scanning the files in the first terminal; comparing the current scan results of the first terminal with the historical scan results, and selecting one or more files that differ from each other as the files to be synchronized.

[0150] This embodiment also provides a consortium blockchain-based multi-concurrency multi-file collaboration system, which includes a terminal and a server. Based on this system, the consortium blockchain-based multi-concurrency multi-file collaboration method described in any of the above embodiments can be implemented.

[0151] It should be noted that the above modules can be functional modules or program modules, and can be implemented through software or hardware. For modules implemented through hardware, the above modules can reside in the same processor; or the above modules can be located in different processors in any combination.

[0152] This embodiment also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0153] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0154] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0155] S1, obtain the file to be synchronized, and generate a first summary document based on the hash value and attribute information of the file to be synchronized.

[0156] S2, Submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain.

[0157] S3, after the first summary document is uploaded to the blockchain, the file to be synchronized is uploaded to the file storage module on the server side using the hash value of the file to be synchronized as the storage index key, so that the file storage module stores the file to be synchronized when it determines that the hash value in the storage index key is consistent with the hash value of the corresponding file to be synchronized in the first summary document.

[0158] It should be noted that the specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0159] Furthermore, in conjunction with the consortium blockchain-based multi-file collaboration method in the above embodiments, this application embodiment can provide a storage medium for implementation. This storage medium stores a computer program; when executed by a processor, the computer program implements any of the consortium blockchain-based multi-file collaboration methods described above.

[0160] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0161] Those skilled in the art should understand that the technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments have been described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0162] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A multi-concurrent multi-file collaboration method based on a consortium chain, characterized in that, Applied to a first terminal, the method includes: Obtain the file to be synchronized, and generate a first summary document based on the hash value and attribute information of the file to be synchronized; Submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain; After the first summary document is uploaded to the blockchain, the file to be synchronized is uploaded to the file storage module on the server side using the hash value of the file to be synchronized as the storage index key. This allows the file storage module to store the file to be synchronized if it determines that the hash value in the storage index key matches the hash value of the corresponding file to be synchronized in the first summary document.

2. The method of claim 1, wherein, The file storage module for uploading the files to be synchronized to the server includes: The priority level of the file to be synchronized is determined based on its size; the smaller the file, the higher the priority level. Add the corresponding file to be synchronized to the upload queue; Files are uploaded to the file storage module in the upload queue in descending order of priority.

3. The method of claim 2, wherein, After adding the corresponding file to be synchronized to the upload queue, the method further includes: Receive priority upgrade instruction; the priority upgrade instruction is generated by the server when it receives a download request instruction for a target file initiated by the second terminal and determines that the target file has not been stored in the file storage module; In the upload queue, a target file is determined according to the priority boosting instruction, and the priority of the target file in the upload queue is increased; or, in the upload queue, a target file is determined according to the priority boosting instruction, a second upload channel is established in parallel with the first upload channel where the current upload queue is located, and the target file is uploaded by the second upload channel.

4. The method of claim 1, wherein, The method further includes: Obtain a second summary document uploaded by a third terminal in the consortium blockchain; the second summary document includes hash values ​​and attribute information corresponding to one or more associated files, wherein the associated files are files to be synchronized obtained by the third terminal; In response to the user's selection of associated files in the second summary document, the target file to be downloaded in the associated file and the priority level of the target file for download are determined, and a download request instruction is generated based on the hash value of the target file in the second summary document, the attribute information of the target file, and the priority level; The download request instruction is uploaded to the server, so that the server responds to the download request instruction by determining the target file in the file storage module and sending the download address of the target file to the first terminal; Receive the download address and obtain the target file based on the download address.

5. The method of claim 1, wherein, The process of obtaining the file to be synchronized includes: Scan the files in the first terminal; The current scan results of the first terminal are compared with the historical scan results, and one or more files that show differences are selected as the files to be synchronized.

6. A multi-concurrency, multi-file collaborative method based on consortium blockchain, characterized in that, Applied to the server side, the server side includes a file storage module and a server for deploying consortium blockchain nodes, the method includes: The system receives a summary document uploaded by a first terminal; the summary document includes a hash value generated by the first terminal based on the file to be synchronized, and attribute information of the file to be synchronized. The consortium blockchain node writes the summary document into a block of the consortium blockchain; Receive the file to be synchronized uploaded by the first terminal, and the hash value of the file to be synchronized; When the hash value of the file to be synchronized matches the hash value of the file to be synchronized in the summary document, the file to be synchronized is stored in the file storage module using the hash value as the storage index key.

7. The method according to claim 6, characterized in that, The method further includes: Receive a download request instruction for a target file initiated by a second terminal, and obtain the target hash value of the target file according to the download request instruction; In the file storage module, the target file is located based on the target hash value, and the download address of the target file is sent to the second terminal.

8. The method according to claim 7, characterized in that, After locating the target file based on the target hash value in the file storage module, the method further includes: In the file storage module, if the target file cannot be indexed based on the target hash value, the priority level and attribute information of the target file are obtained according to the download request instruction. The third terminal for uploading the target file is determined based on the attribute information of the target file; A priority upgrade instruction for the target file is generated based on the priority level, the initiation time of the download request instruction, and the load of the file upload channel of the third terminal. The priority increase instruction is sent to the third terminal, so that the third terminal responds to the priority increase instruction by increasing the priority of uploading the target file to the file storage module, or responds to the priority increase instruction by uploading the target file and other files in parallel.

9. A multi-concurrency, multi-file collaborative device based on a consortium blockchain, characterized in that, include: The file acquisition module is used to acquire the files to be synchronized and generate a first summary document based on the hash value and attribute information of the files to be synchronized. The first submission module is used to submit the first summary document to the consortium blockchain node deployed on the server, so that the consortium blockchain node writes the first summary document into the block of the consortium blockchain. The second submission module is used to upload the file to be synchronized to the file storage module on the server side after the first summary document is uploaded to the blockchain, using the hash value of the file to be synchronized as the storage index key. This allows the file storage module to store the file to be synchronized if it determines that the hash value in the storage index key is consistent with the hash value of the corresponding file to be synchronized in the first summary document.

10. A multi-concurrency, multi-file collaborative system based on a consortium blockchain, characterized in that, include: A terminal and a server, wherein the terminal is used to perform the method of any one of claims 1 to 5, and the server is used to perform the method of any one of claims 6 to 8.