File uploading method and device, file processing method and device, file verification method and device and equipment
By verifying transmission integrity and merging fragment checksums in real time during file fragment upload, the problem of cumbersome file verification process and high resource consumption in existing technologies is solved, achieving efficient and reliable file upload and a simplified verification process.
Patent Information
- Application Number
- CN202511208170.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-08-26
- Publication Date
- 2025-10-28
AI Technical Summary
The multipart technology based on the conventional S3 standard requires downloading all fragments and merging them into a complete file before calculating the checksum during file verification. This results in a cumbersome verification process, high resource consumption, and low efficiency.
After splitting the file and uploading the file fragments, the first client receives the first checksum of the file fragments returned by the server and compares it with the second checksum of the file fragments calculated by the first client itself to generate the upload result. The integrity of the transmission of each file fragment is verified in real time during the file fragment upload process. The server receives and calculates the first checksum of the set of file fragments and then merges them to generate the first checksum of the whole file. The second client requests and receives the set of file fragments and the first checksum of the whole file, calculates and merges them to generate the third checksum of the whole file and then compares them.
Real-time verification of transmission integrity during file chunked upload reduces resource waste, improves file upload reliability and efficiency, simplifies the verification process for both the server and client, reduces storage and computing resource consumption, and improves the efficiency and accuracy of file verification.
Smart Images

Figure CN120856694A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of cloud computing technology, and in particular to a method, apparatus, device, medium, and program product for file uploading, file processing, and file verification. Background Technology
[0002] In the field of object storage, with the continuous growth of large file data such as high-definition video, enterprise backup data, and industrial logs, the problems of traditional whole file uploads being susceptible to network fluctuations and having low transmission efficiency are becoming increasingly prominent. To address this, multipart upload technology, which follows the S3 standard (an object storage upload standard based on RESTful (Representational State Transfer) style), has become the mainstream solution. By splitting large files into fragments and transmitting them concurrently, it effectively improves the stability and efficiency of large file uploads and has been widely used in various object storage systems.
[0003] In multipart technology based on the standard S3, data integrity verification is a crucial step in ensuring file reliability. Its process logic is clear: After the client completes the file upload in chunks, if file integrity verification is required, all file chunks must first be downloaded from the server, merged into a complete file in their original order, and then the checksum of the complete file is calculated. Finally, this checksum is compared with the checksum of the complete file recorded by the server during upload. If they match, the file is considered complete; otherwise, the file is considered corrupted or tampered with, thus completing the integrity verification of the entire multipart uploaded file. Summary of the Invention
[0004] This application provides a file upload method, apparatus, device, medium, and program product to solve the technical problem that the multipart technology based on the conventional S3 standard requires downloading all fragments and merging them into a complete file before calculating the verification value, resulting in a cumbersome verification process, high resource consumption, and low efficiency.
[0005] One aspect of this application provides a file upload method applied to a first client, comprising: splitting a file to generate a set of file fragments; uploading the set of file fragments to a server; receiving a first verification value of a file fragment from the set of file fragments sent by the server; calculating a second verification value of a file fragment; comparing the first verification value and the second verification value of the file fragment to generate an upload result of the file fragment.
[0006] Another aspect of this application provides a file processing method applied to a server, comprising: receiving a set of file fragments uploaded by a first client, which are divided into file segments; calculating a first check value of the file fragments in the set of file fragments; and, in response to determining that all file fragments in the set of file fragments have been uploaded, merging the first check values of the file fragments in the set of file fragments to generate a first check value of the file.
[0007] Another aspect of this application provides a file verification method applied to a second client, comprising: sending a file retrieval request to a server; receiving a set of file fragments and a first verification value sent by the server; calculating a third verification value of the file fragments in the set of file fragments; merging the third verification values of the file fragments in the set of file fragments to generate a third verification value of the file; and comparing the first verification value and the third verification value of the file to generate a verification result of the file.
[0008] Another aspect of this application provides a file upload device, set on a first client, comprising: a file splitting module configured to split a file to generate a set of file fragments; a fragment upload module configured to upload the set of file fragments to a server; a verification value receiving module configured to receive a first verification value of a file fragment from the set of file fragments sent by the server; a verification value calculation module configured to calculate a second verification value of a file fragment; and a verification value comparison module configured to compare the first verification value and the second verification value of the file fragments to generate an upload result for the file fragments.
[0009] Another aspect of this application provides a file processing apparatus, disposed on a server, comprising: a fragment receiving module configured to receive a set of file fragments uploaded by a first client, which are divided into file fragments; a checksum calculation module configured to calculate a first checksum of the file fragments in the file fragment set; and a checksum merging module configured to merge the first checksums of the file fragments in the file fragment set and generate a first checksum of the file in response to determining that all file fragments in the file fragment set have been uploaded.
[0010] Another aspect of this application provides a file verification device, disposed on a second client, comprising: a request sending module configured to send a file retrieval request to a server, the file retrieval request including a file identifier; a fragment receiving module configured to receive a set of file fragments and a first verification value sent by the server; a verification value calculation module configured to calculate a third verification value of the file fragments in the file fragment set; a verification value merging module configured to merge the third verification values of the file fragments in the file fragment set to generate a third verification value of the file; and a verification value comparison module configured to compare the first verification value and the third verification value of the file to generate a verification result of the file.
[0011] Another aspect of this application provides a file verification system, including a first client, a second client, and a server: the first client is used to split a file to generate a set of file fragments; and upload the set of file fragments to the server; the server is used to calculate a first verification value of the file fragments in the set of file fragments; and in response to determining that all file fragments in the set of file fragments have been uploaded, merge the first verification values of the file fragments in the set of file fragments to generate a first verification value of the file; the second client is used to send a file retrieval request to the server; receive the set of file fragments and the first verification value of the file sent by the server; calculate a third verification value of the file fragments in the set of file fragments; merge the third verification values of the file fragments in the set of file fragments to generate a third verification value of the file; and compare the first verification value and the third verification value of the file to generate a verification result of the file.
[0012] In another aspect of this application, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the file upload, file processing, and file verification methods as described above.
[0013] In another aspect, this application provides a computer-readable storage medium having stored thereon computer program instructions that can be executed by a processor to implement the file upload, file processing, and file verification methods described above.
[0014] Another aspect of this application provides a computer program product, including a computer program that, when executed by a processor, implements the file upload, file processing, and file verification methods described above.
[0015] In the solution provided in this application embodiment, the file is split into segments and uploaded as file fragments. The first verification value of the file fragment returned by the server is received and compared with the second verification value of the file fragment calculated by the first client itself to generate the upload result. This can verify the transmission integrity of each file fragment in real time during the file fragment upload process, avoiding the problem that the subsequent complete file needs to be re-uploaded after being merged due to the failure to detect abnormal file fragment transmission in time. This effectively improves the reliability and efficiency of file upload and reduces the waste of resources caused by fragment transmission errors.
[0016] In the solution provided in this application embodiment, by receiving a set of file fragments uploaded by a first client, calculating the first check value of each file fragment, and merging the first check values of the file fragments to generate the first check value of the entire file after confirming that all file fragments have been uploaded, the solution provides an accurate basis for the client to verify the integrity of the uploaded file fragments, ensuring the reliability of the file fragment transmission process. On the other hand, it eliminates the need to wait for the complete file to be merged before calculating the overall check value, but directly generates it based on the merged file fragment check values, greatly simplifying the process of the server generating the overall file integrity identifier and reducing the server's storage and computing resource consumption. At the same time, the overall file check value also provides a unified and directly comparable core basis for subsequent client file integrity verification, improving the server's processing efficiency and data management standardization in the entire object storage multipart upload process.
[0017] In the solution provided in this application embodiment, by requesting and receiving a set of file fragments and a first checksum of the entire file from the server, the file integrity verification can be completed simply by calculating the third checksum of the file fragments, merging them to generate the third checksum of the entire file, and comparing it with the first checksum of the entire file. This eliminates the need to download all file fragments, merge them into a complete file, and then calculate the overall checksum, significantly reducing the file storage footprint and computational resource consumption of the second client, greatly simplifying the verification process, and ensuring consistency between the verification logic and the server. This effectively improves the efficiency and accuracy of file verification, meeting the need for rapid file integrity verification in object storage scenarios. Attached Figure Description
[0018] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 A flowchart illustrating an embodiment of the file upload method provided in this application; Figure 2 A flowchart illustrating an embodiment of the document processing method provided in this application; Figure 3 A flowchart illustrating an embodiment of the document verification method provided in this application; Figure 4 A schematic diagram of the structure of an embodiment of the file upload device provided in this application; Figure 5 A schematic diagram of the structure of one embodiment of the document processing apparatus provided in this application; Figure 6 A schematic diagram of the structure of an embodiment of the document verification device provided in this application; Figure 7 This is an interaction timing diagram of an embodiment of the document verification system provided in this application; Figure 8 This is a schematic diagram of the structure of a device suitable for implementing the solutions in the embodiments of this application; The same or similar reference numerals in the accompanying drawings represent the same or similar parts. Detailed Implementation
[0020] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0021] In a typical configuration of this application, the terminal and the service network devices each include one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0022] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0023] Computer-readable media include permanent and non-permanent, removable and non-removable media, which can store information by any method or technology. Information can be computer program instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only optical disc (CD-ROM), digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.
[0024] In the solution provided in this application embodiment, a file is divided into a set of file fragments and uploaded to the server. A second checksum for each file fragment is calculated and compared with the first checksum returned by the server to generate the upload result for that file fragment. The integrity of each file fragment is verified in real time during the file fragment upload process, effectively improving the reliability and efficiency of file upload and reducing resource waste caused by fragment transmission errors.
[0025] In the solution provided in this application embodiment, after receiving a set of file fragments into which a file has been split, the first checksum of each file fragment in the set is calculated. Once all file fragments in the set have been uploaded, the first checksums of the file fragments in the set are merged to generate the first checksum of the file. This direct generation based on the merged file fragment checksums significantly simplifies the process of generating the overall file integrity identifier on the server side and reduces the consumption of server-side storage and computing resources.
[0026] In the solution provided in this application embodiment, a file fragment set and a first checksum are obtained from the server by sending a file retrieval request. The third checksum of each file fragment in the file fragment set is calculated, merged into a third checksum for the entire file, and compared with the first checksum to generate a file verification result. File integrity verification can be completed simply by calculating the third checksum of each file fragment, merging them to generate the overall third checksum of the file, and then comparing it with the overall first checksum of the file. This significantly reduces the file storage footprint and computational resource consumption of the second client, simplifies the verification process, and effectively improves the efficiency and accuracy of file verification.
[0027] In practical scenarios, the entity executing the above method can be a user device, a network device, or a device formed by integrating user devices and network devices through a network, or it can be an application running on the above devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and wristbands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server sets, or cloud computing-based computer sets. Here, the cloud consists of a large number of hosts or network servers based on cloud computing, where cloud computing is a type of distributed computing, consisting of a virtual computer composed of a group of loosely coupled computer sets.
[0028] Figure 1 The present application illustrates a processing flow 100 of an embodiment of the file upload method provided in this application, the method comprising at least the following processing steps: Step S101: Split the file to generate a set of file fragments.
[0029] In this embodiment, the first client can split the file to generate a set of file fragments.
[0030] By splitting files, we can ensure that the split file fragments meet the high-efficiency transmission requirements of multipart uploads, and also provide reusable fragmentation logic for subsequent file consistency checks. File splitting methods can include, but are not limited to: splitting according to a fixed fragment size, splitting according to a fixed number of fragments, splitting according to file content characteristics, and random splitting.
[0031] In some embodiments, the file is split according to a preset partsize value to generate a set of file parts.
[0032] The preset chunk size can be flexibly set according to the total file size. For example, it can be set to 5-10MB for files under 1GB, 10-20MB for files between 1-10GB, and 20-50MB for files over 10GB, to balance the reasonableness of the number of chunks and the transmission efficiency of each chunk. If the total file size cannot be divided by the preset chunk size, the actual size of the last file chunk in the file chunk set can be smaller than the preset chunk size to ensure that no file data is missed. At the same time, a unique chunk number (partnum) is assigned to each file chunk to record the order of the file chunks in the original file, ensuring that the file chunk order during subsequent verification is consistent with the order during upload.
[0033] By splitting files according to preset segment sizes, the system can flexibly configure segment sizes based on the total file size, providing a suitable segmentation basis for subsequent multipart concurrent uploads and effectively improving the stability and efficiency of large file uploads. Furthermore, the unique segment number ensures traceability of the segmentation order, providing standardized segmentation logic support for the second client to calculate file segment verification values and compare them with the server's verification values, as well as for the first client to verify file consistency at any time through segment-level verification. This also avoids verification deviations caused by inconsistent segmentation rules.
[0034] Step S102: Upload the file fragment set to the server.
[0035] In this embodiment, the first client can upload a set of file fragments to the server.
[0036] By splitting files into sets of file chunks and then using a concurrent upload mode, large file transfer tasks can be broken down, thereby improving file upload efficiency.
[0037] In some embodiments, multiple upload threads are started; the file fragment set is uploaded in parallel using the multiple upload threads.
[0038] The number of upload threads can be determined by combining the number of CPU (Central Processing Unit) cores and network bandwidth of the first client. Typically, the number of upload threads should not exceed twice the number of CPU cores to balance hardware resource utilization and transmission stability. During the upload process, each file fragment carries a corresponding fragment number and file identifier, enabling the server to accurately associate each file fragment with the file, providing a basis for subsequent calculation of file fragment checksums and storage of file fragment metadata.
[0039] By combining the number of CPU cores on the first client with network bandwidth to determine a reasonable number of upload threads, it avoids CPU overload and impacts device stability caused by too many threads, while fully utilizing the hardware computing power and network bandwidth of the first client. Furthermore, compared to traditional one-time uploads of the entire file, parallel upload mode breaks down large file transfer tasks into multiple independent file chunk transfer tasks. Even if the upload of a single file chunk is interrupted due to network fluctuations, only that file chunk needs to be retransmitted, eliminating the need to re-upload the entire file. This significantly reduces the impact of network fluctuations on the upload process and substantially improves the stability of large file uploads. Simultaneously, parallel transmission effectively shortens the overall upload time, further optimizing the efficiency of large file uploads.
[0040] Step S103: Receive the first check value of the file fragment in the file fragment set sent by the server.
[0041] In this embodiment, the first client can receive the first verification value of a file fragment from the file fragment set sent by the server.
[0042] The first checksum can be the file fragment checksum calculated by the server after receiving each file fragment using an algorithm consistent with that of the first client (such as MD5 (Message-Digest Algorithm 5)). The server can associate the first checksum with the corresponding fragment number and send it to the first client to ensure that the first client can accurately match the checksum result of each file fragment. Step S104: Calculate the second checksum of the file fragment.
[0043] In this embodiment, the first client can calculate the second checksum of the file fragments.
[0044] The second verification value can be the file fragment verification value generated by the first client using the same algorithm as the server.
[0045] In some embodiments, an MD5 operation is performed on the file fragments to generate a second checksum for the file fragments.
[0046] The first client, while uploading each file fragment or after uploading, performs a hash operation on the local file fragments using the MD5 algorithm. The generated second checksum is calculated using the same logic as the server's first checksum, avoiding verification discrepancies caused by algorithm differences. Simultaneously, the first client records the correspondence between the second checksum and the fragment number for accurate comparison later. In other embodiments, the verification algorithm can also be other hash algorithms such as SHA (Secure Hash Algorithm)-256.
[0047] Step S105: Compare the first checksum and the second checksum of the file fragments to generate the file fragment upload result.
[0048] In this embodiment, the first client can compare the first checksum and the second checksum of the file fragments to generate the file fragment upload result.
[0049] By performing fragment-level verification, transmission anomalies can be detected in real time, avoiding the waste of resources that would otherwise be required to re-transmit the complete file after merging. Specifically, the first client compares the first and second checksums of each file fragment with its fragment number. If they match, the file fragment is determined to have been undamaged or unaltered during transmission, and a successful upload result is generated. If they do not match, the file fragment is determined to have been transmitted abnormally, an upload failure result is generated, and the re-upload process for that file fragment is triggered until the file fragment verification passes.
[0050] In some embodiments, in response to determining that all file fragments in the file fragment set have been uploaded, an upload completion message is sent to the server.
[0051] Based on the correspondence between fragment numbers and actual fragment sizes, and the verification results of successful uploads of each file fragment, the system checks each fragment number to ensure that it has been uploaded successfully and passed verification, ensuring that no file fragments are missing or transmission errors occur. Once it is confirmed that all file fragments have been uploaded, the first client generates and sends an upload completion message to the server. This upload completion message may carry core identification information for this multipart upload, including but not limited to file identifiers, total file size, preset fragment size values, and a list of all file fragment numbers.
[0052] This application provides a file upload method that uploads file fragments by splitting the file into segments, receiving a first verification value of the file fragment returned by the server, and comparing it with a second verification value of the file fragment calculated by the first client to generate an upload result. This method can verify the transmission integrity of each file fragment in real time during the file fragment upload process, avoiding the problem of rework and re-upload after merging the complete file due to the failure to detect abnormal file fragment transmission in time. This effectively improves the reliability and efficiency of file upload and reduces the waste of resources caused by fragment transmission errors.
[0053] Figure 2 The present application illustrates a processing flow 200 of an embodiment of the document processing method provided in this application, the method comprising at least the following processing steps: Step S201: Receive the set of file fragments uploaded by the first client, which are the file segments split into parts.
[0054] In this embodiment, the server can receive a set of file fragments, which are split from a file, uploaded by the first client.
[0055] Before receiving data, the server can establish a multipart upload session with the first client based on the S3 protocol, generating a unique session identifier for this upload. This ensures a one-to-one correspondence with the identifier in the client's upload request, preventing confusion between file fragments from different files. During the receiving process, each file fragment carries a unique fragment number assigned by the first client, a preset fragment size value, and a session identifier. The fragment number is used by the server to record the order of file fragments within the original file. The preset fragment size value is used to verify whether the actual size of the file fragment conforms to the client's splitting rules. The session identifier is used to associate the file fragment with the file it belongs to, ensuring an accurate match between the file fragment set and the file. Simultaneously, the server can also record the received file fragment numbers and statuses in real time, forming a file fragment reception log to determine whether all fragments have been uploaded.
[0056] Step S202: Calculate the first check value of the file fragment in the file fragment set.
[0057] In this embodiment, the server can calculate the first checksum of the file fragments in the file fragment set.
[0058] The first checksum can be the file fragment checksum generated by the server after receiving each file fragment, using the same algorithm as the first client and the second client.
[0059] In some embodiments, an MD5 operation is performed on the file fragments to generate a first checksum value for the file fragments.
[0060] The server uses the MD5 algorithm to hash the received file fragments. The resulting first checksum is calculated using the same logic as the second checksum from the first client and the third checksum from the second client, avoiding verification discrepancies caused by algorithm differences. After calculation, the server associates the first checksum with the corresponding file fragment number and session identifier, forming a mapping between fragment number and checksum. This provides data support for merging the overall file checksum and returning the checksum to the first client.
[0061] In other embodiments, the verification algorithm may also be other hash algorithms such as SHA-256.
[0062] In some embodiments, multiple processing threads are allocated from a thread pool, the number of which is adapted to the number of upload threads started by the first client; the multiple processing threads are used to receive a set of file fragments in parallel; and the multiple processing threads are used to calculate the first checksum of the received file fragments in parallel.
[0063] Concurrent processing improves the efficiency of file fragment reception and checksum calculation on the server side, adapting to the parallel upload rhythm of the first client and avoiding upload blocking caused by insufficient server processing capacity. The number of processing threads is matched to the number of upload threads on the first client (e.g., if the first client starts 8 upload threads, the server allocates 6-8 processing threads accordingly), fully utilizing the server's CPU core resources while avoiding resource contention and scheduling overhead caused by too many threads. In the parallel reception phase, each processing thread is responsible for receiving file fragments under a specific session identifier, ensuring that the reception order does not affect subsequent processing through fragment numbering. In the parallel computation phase, processing threads immediately start MD5 calculation after receiving a single file fragment, without waiting for all file fragments to be received, significantly reducing the overall checksum calculation time.
[0064] Step S203: In response to determining that all file fragments in the file fragment set have been uploaded, merge the first checksums of the file fragments in the file fragment set and generate the first checksum of the file.
[0065] In this embodiment, in response to determining that all file fragments in the file fragment set have been uploaded, the server can merge the first checksums of the file fragments in the file fragment set to generate the first checksum of the file.
[0066] By replacing the calculation of the checksum after merging the complete file with the checksum of the merged file fragments, the storage and computing resource consumption on the server side is significantly reduced.
[0067] In some embodiments, the first checksum of the file fragments in the file is generated by concatenating the first checksums of the file fragments in the file fragment set according to the order of the file fragments in the file.
[0068] The order of file fragments within a file is determined by their fragment numbers. The server can sort the fragments in the file fragment reception log by their numbers, and then concatenate the first checksums of each fragment in ascending order to form the file's first checksum. This first checksum can be denoted as Etag (a resource-specific version identifier), for example, Etag= <md5-1> <md5-2> … <md5-n>This concatenation method does not require merging complete files; it only needs to manipulate lightweight data such as file fragment checksums. Compared to merging complete files and then calculating the MD5 value, it can save a lot of storage (no need to temporarily store complete files) and computation (no need to perform overall calculations on large files) resources, and the efficiency of generating ETags is significantly improved.
[0069] In some embodiments, in response to receiving an upload completion message sent by the first client, it is determined that all file fragments in the file fragment set have been uploaded.
[0070] The upload complete message is the core signal that the file segments have been completely uploaded, which is transmitted from the first client to the server. It carries the core identification information of this multipart upload, including but not limited to the file identifier, total file size, preset segment size value, and a list of all file segment numbers.
[0071] In some embodiments, a first checksum of a file fragment in the file fragment set is sent to a first client so that the first client can determine the upload result of the file fragment.
[0072] After calculating the first checksum for a single file fragment, the server can send the fragment number, the first checksum, and the association information between the session identifier and the first client back to the first client. The first client can then compare this with the locally calculated second checksum, instantly detect transmission anomalies, and trigger a re-upload. This real-time interaction between fragment upload, checksum calculation, and result feedback avoids the rework problem of discovering anomalies only after all fragments have been uploaded, as is common in traditional solutions. It also reduces bandwidth waste caused by invalid transmissions and ensures that only file fragments that pass checksum verification participate in subsequent ETag merging, providing fragment-level protection for the overall integrity of the file.
[0073] This application provides a file processing method that receives a set of file fragments uploaded by a first client, calculates a first checksum for each file fragment, and merges the first checksums of the file fragments to generate a first checksum for the entire file after confirming that all file fragments have been uploaded. On the one hand, this provides an accurate basis for the client to verify the integrity of the uploaded file fragments, ensuring the reliability of the file fragment transmission process. On the other hand, it eliminates the need to wait for the complete file to be merged before calculating the overall checksum; instead, it directly generates the checksum based on the merged file fragment checksums, greatly simplifying the process of generating the overall file integrity identifier on the server side and reducing the consumption of server-side storage and computing resources. At the same time, the overall file checksum also provides a unified and directly comparable core basis for subsequent client file integrity verification, improving the server-side processing efficiency and data management standardization in the entire object storage multipart upload process.
[0074] Figure 3 The present invention illustrates a processing flow 300 of an embodiment of the file verification method provided in this application, the method comprising at least the following processing steps: Step S301: Send the file retrieval request to the server.
[0075] In this embodiment, the second client can send a file retrieval request to the server. The file retrieval request may include a file identifier to ensure the server accurately locates the file to be verified and avoids file confusion.
[0076] In some embodiments, a file metadata retrieval request is sent to the server; file metadata information is received from the server; and a file retrieval request is sent based on the metadata information.
[0077] File metadata retrieval requests can be used to obtain key configuration information required for verification. The metadata information returned by the server may include, but is not limited to: preset fragment size value, total number of fragments, and the first checksum of the file.
[0078] After receiving and parsing the metadata information, the second client generates a precise file retrieval request based on the preset fragment size value and fragment number list. The file retrieval request can also carry the fragment number to ensure that the server only returns the corresponding fragment data, avoiding bandwidth and storage waste caused by downloading the complete file.
[0079] Step S302: Receive the file fragment set and first check value of the file sent by the server.
[0080] In this embodiment, the second client can receive the file fragment set and the first check value sent by the server.
[0081] The first checksum can be a file fragment checksum calculated by the server after receiving each file fragment, using the same algorithm as the first and second clients. Synchronously receiving file fragments and the first checksum as a comparison benchmark ensures the integrity and accuracy of the verification process.
[0082] In some embodiments, multiple verification threads are started; the file fragment set is downloaded in parallel using the multiple verification threads; and the third verification value of the downloaded file fragment is calculated in parallel using the multiple verification threads.
[0083] The number of verification threads needs to be determined based on the number of CPU cores and network bandwidth of the second client. Typically, it should be matched to the number of concurrent download threads supported by the server (e.g., 6-8 verification threads for an 8-core CPU client). This fully utilizes hardware resources while avoiding resource contention caused by too many threads. In the parallel download phase, each verification thread is responsible for downloading a file segment with a specific number. The segment number ensures that the download order does not affect subsequent verification, significantly reducing the time spent acquiring file segments compared to single-threaded download. In the parallel computation phase, the verification thread starts calculating the verification value immediately after downloading a single file segment, without waiting for all file segments to complete downloading. This achieves pipelined processing from download to computation, further improving verification efficiency.
[0084] Step S303: Calculate the third check value of the file fragments in the file fragment set.
[0085] In this embodiment, the second client can calculate the third checksum of the file fragments in the file fragment set.
[0086] The third checksum can be a file fragment checksum calculated by the second client using the same algorithm as the server. It should be noted that the definition of the third checksum is exactly the same as the second checksum; it is only used to distinguish between different client instances.
[0087] In some embodiments, an MD5 hash is performed on the file fragments to generate a third checksum for the file fragments.
[0088] The second client uses the MD5 algorithm to hash the received file fragments. The generated third checksum is calculated using the same logic as the server's first checksum, avoiding verification discrepancies caused by algorithm differences. Simultaneously, the second client records the correspondence between the third checksum and the fragment number, storing it in its local verification log.
[0089] In other embodiments, the verification algorithm may also be other hash algorithms such as SHA-256.
[0090] Step S304: Merge the third checksums of the file fragments in the file fragment set to generate the third checksum of the file.
[0091] In this embodiment, the second client can merge the third checksums of file fragments in the file fragment set to generate the third checksum of the file.
[0092] By replacing the calculation of the checksum after merging the complete file with the merged file fragment checksum, the storage and computing resource consumption of the second client is significantly reduced.
[0093] In some embodiments, the third checksum of the file fragments in the file is generated by concatenating the third checksums of the file fragments in the file fragment set according to the order of the file fragments in the file.
[0094] The order of file fragments within a file is determined by their fragment numbers. The second client can sort the fragments according to their local verification logs, and then concatenate the third checksums of each file fragment in ascending order of fragment number to form the file's third checksum. This third checksum can be compared with the server's first checksum (Etag). For example, if the server's Etag is... <md5-1> <md5-2> <md5-3>The third checksum of the file generated by the second client must also be a concatenation of MD5 values in the same order. This merging method does not require merging all file fragments into a complete file; it only requires manipulating the lightweight MD5 values. Compared to merging complete files and then calculating the MD5 value, it can save a lot of storage (no need to temporarily store complete files) and computation (no need to perform overall calculations on large files) resources, and the merging efficiency is significantly improved.
[0095] Step S305: Compare the first checksum with the third checksum of the file to generate the file's checksum result.
[0096] In this embodiment, the second client can compare the first checksum and the third checksum of the file to generate the file's checksum result.
[0097] If the first checksum (server-side ETag) and the third checksum (client-side merged result) of the file are completely consistent, it is determined that the file has not been damaged or tampered with during storage and transmission, and a checksum passing result is generated. If the two are inconsistent, it is determined that the file has an integrity problem (such as fragment loss, data tampering, etc.), and a checksum failing result is generated. Furthermore, the abnormal file fragment can be located by the mapping relationship between fragment number and checksum. Only the abnormal file fragment needs to be re-downloaded to complete the repair, without having to re-download all file fragments, further reducing resource waste.
[0098] This application provides a file verification method. By requesting and receiving a set of file fragments and a first verification value for the entire file from the server, the method only needs to calculate the third verification value of each file fragment, merge them to generate the third verification value for the entire file, and then compare it with the first verification value for the entire file to complete the file integrity verification. This eliminates the need to download all file fragments, merge them into a complete file, and then calculate the overall verification value. This significantly reduces the file storage and computational resource consumption of the second client, greatly simplifies the verification process, and ensures consistency between the verification logic and the server. It effectively improves the efficiency and accuracy of file verification, meeting the need for rapid file integrity verification in object storage scenarios.
[0099] Figure 4 A schematic diagram of a structure of an embodiment of the file upload device provided in this application is shown. This device embodiment is similar to... Figure 1 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.
[0100] like Figure 4 As shown, the file upload device 400 of this embodiment may include: a file splitting module 401, a chunk upload module 402, a verification value receiving module 403, a verification value calculation module 404, and a verification value comparison module 405. The file splitting module 401 is configured to split the file to generate a set of file chunks; the chunk upload module 402 is configured to upload the set of file chunks to the server; the verification value receiving module 403 is configured to receive the first verification value of the file chunks in the set of file chunks sent by the server; the verification value calculation module 404 is configured to calculate the second verification value of the file chunks; and the verification value comparison module 405 is configured to compare the first verification value and the second verification value of the file chunks to generate the upload result of the file chunks.
[0101] In this embodiment, the specific processing of the file splitting module 401, the fragmented upload module 402, the checksum receiving module 403, the checksum calculation module 404, and the checksum comparison module 405 in the file upload device 400, and the resulting technical effects, can be found in the following references: Figure 1 The relevant descriptions of steps S101-S105 in the corresponding embodiments will not be repeated here.
[0102] In some optional implementations of this embodiment, the file splitting module 401 is further configured to split the file according to a preset split size value to generate a file split set.
[0103] In some optional implementations of this embodiment, the chunked upload module 402 is further configured to: start multiple upload threads; and use the multiple upload threads to upload the file chunk set in parallel.
[0104] In some optional implementations of this embodiment, the verification value calculation module 404 is further configured to: perform message digest algorithm 5 operation on the file fragments to generate a second verification value for the file fragments.
[0105] In some optional implementations of this embodiment, the file upload device 400 further includes a message sending module configured to send an upload completion message to the server in response to determining that all file fragments in the file fragment set have been uploaded.
[0106] Figure 5 A schematic diagram of a structure of an embodiment of the document processing apparatus provided in this application is shown. This apparatus embodiment is similar to... Figure 2 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.
[0107] like Figure 5 As shown, the file processing device 500 of this embodiment may include: a fragment receiving module 501, a checksum calculation module 502, and a checksum merging module 503. The fragment receiving module 501 is configured to receive a set of file fragments uploaded by a first client, which are composed of file segments. The checksum calculation module 502 is configured to calculate a first checksum of each file fragment in the file fragment set. The checksum merging module 503 is configured to, in response to determining that all file fragments in the file fragment set have been uploaded, merge the first checksums of the file fragments in the file fragment set to generate a first checksum for the file.
[0108] In this embodiment, the specific processing of the file processing device 500, including the fragment receiving module 501, the checksum calculation module 502, and the checksum merging module 503, and the resulting technical effects, can be found by referring to [reference needed]. Figure 2 The relevant descriptions of steps S201-S203 in the corresponding embodiments will not be repeated here.
[0109] In some optional implementations of this embodiment, the file processing device 500 further includes: a verification value sending module, configured to send the first verification value of a file fragment in the file fragment set to the first client, so that the first client can determine the upload result of the file fragment.
[0110] In some optional implementations of this embodiment, the file processing device 500 further includes a message receiving module, configured to determine that all file fragments in the file fragment set have been uploaded in response to receiving an upload completion message sent by the first client.
[0111] In some optional implementations of this embodiment, the fragment receiving module 501 is further configured to allocate multiple processing threads from the thread pool, the number of processing threads being adapted to the number of upload threads started by the first client; to receive the file fragment set in parallel using the multiple processing threads; and the check value calculation module 502 is further configured to calculate the first check value of the received file fragments in parallel using the multiple processing threads.
[0112] In some optional implementations of this embodiment, the verification value calculation module 502 is further configured to: perform message digest algorithm 5 operation on the file fragments to generate the first verification value of the file fragments.
[0113] In some optional implementations of this embodiment, the check value merging module 503 is further configured to: concatenate the first check values of the file fragments in the file fragment set according to the order of the file fragments in the file, and generate the first check value of the file.
[0114] Figure 6 A schematic diagram of an embodiment of the document verification device provided in this application is shown. This device embodiment is similar to... Figure 3 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.
[0115] like Figure 6 As shown, the file verification device 600 of this embodiment may include: a request sending module 601, a fragment receiving module 602, a verification value calculation module 603, a verification value merging module 604, and a verification value comparison module 605. The request sending module 601 is configured to send a file acquisition request to the server, the file acquisition request including a file identifier; the fragment receiving module 602 is configured to receive a set of file fragments and a first verification value sent by the server; the verification value calculation module 603 is configured to calculate a third verification value for each file fragment in the file fragment set; the verification value merging module 604 is configured to merge the third verification values of the file fragments in the file fragment set to generate a third verification value for the file; and the verification value comparison module 605 is configured to compare the first verification value and the third verification value of the file to generate a verification result for the file.
[0116] In this embodiment, the specific processing of the request sending module 601, the fragment receiving module 602, the checksum calculation module 603, the checksum merging module 604, and the checksum comparison module 605 in the file verification device 600, and the resulting technical effects, can be found in the following references: Figure 3 The relevant descriptions of steps S301-S305 in the corresponding embodiments will not be repeated here.
[0117] In some optional implementations of this embodiment, the request sending module 601 is further configured to: send a file metadata acquisition request to the server; receive file metadata information sent by the server; and send a file acquisition request based on the metadata information.
[0118] In some optional implementations of this embodiment, the fragment receiving module 602 is further configured to: start multiple verification threads; use the multiple verification threads to download the file fragment set in parallel; and the check value calculation module 603 is further configured to: use the multiple verification threads to calculate the third check value of the downloaded file fragments in parallel.
[0119] In some optional implementations of this embodiment, the verification value calculation module 603 is further configured to: perform message digest algorithm 5 operation on the file fragments to generate a third verification value for the file fragments.
[0120] In some optional implementations of this embodiment, the check value merging module 604 is further configured to: concatenate the third check values of the file fragments in the file fragment set according to the order of the file fragments in the file, and generate the third check value of the file.
[0121] Figure 7 The interactive timing 700 of an embodiment of the document verification system provided in this application is illustrated. The system includes a first client, a second client, and a server, and performs at least the following interactive steps: Step S701: The first client splits the file to generate a set of file fragments.
[0122] In step S702, the first client uploads the file fragment set to the server.
[0123] Step S703: The server calculates the first checksum of the file fragment in the file fragment set.
[0124] In step S704, in response to determining that all file fragments in the file fragment set have been uploaded, the server merges the first checksums of the file fragments in the file fragment set and generates the first checksum of the file.
[0125] In step S705, the second client sends a file retrieval request to the server.
[0126] Step S706: The second client receives the file fragment set and the first check value of the file sent by the server.
[0127] Step S707: The second client calculates the third check value of the file fragments in the file fragment set.
[0128] Step S708: The second client merges the third checksums of the file fragments in the file fragment set and generates the third checksum of the file.
[0129] Step S709: The second client compares the first checksum with the third checksum of the file and generates the file checksum result.
[0130] In this embodiment, the specific operations of steps S701 and S702 can be referred to Figure 1 For details regarding steps S101 and S102 in the corresponding embodiments, please refer to the following for specific operations of steps S703-S704. Figure 2 For details regarding steps S202-S203 in the corresponding embodiment, please refer to the following for specific operations of steps S705-S709. Figure 3 The relevant descriptions of steps S301-S305 in the corresponding embodiments will not be repeated here.
[0131] Based on the same inventive concept, this application also provides an electronic device. The method corresponding to the electronic device can be the file uploading, file processing, and file verification methods described in the foregoing embodiments, and its problem-solving principle is similar to that of the method. The electronic device provided in this application includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the methods and / or technical solutions of the various embodiments of this application described above.
[0132] The electronic device can be a user device, or a device formed by integrating user devices and network devices through a network, or it can be an application running on the aforementioned devices. The user device includes, but is not limited to, various terminal devices such as computers, mobile phones, tablets, smartwatches, and wristbands. The network device includes, but is not limited to, network hosts, single network servers, multiple network server sets, or cloud computing-based computer sets, and can be used to implement some processing functions when setting an alarm clock. Here, the cloud consists of a large number of hosts or network servers based on cloud computing. Cloud computing is a type of distributed computing, consisting of a virtual computer composed of a group of loosely coupled computer sets.
[0133] Figure 8 The diagram illustrates the structure of an apparatus suitable for implementing the methods and / or technical solutions in the embodiments of this application. The apparatus 800 includes a Central Processing Unit (CPU) 801, which can perform various appropriate actions and processes based on a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage portion 808 into a Random Access Memory (RAM) 803. The RAM 803 also stores various programs and data required for system operation. The CPU 801, ROM 802, and RAM 803 are interconnected via a bus 804. An Input / Output (I / O) interface 805 is also connected to the bus 804.
[0134] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, touchscreen, microphone, infrared sensor, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), LED display, OLED display, etc., and speakers, etc.; a storage section 808 including one or more computer-readable media such as hard disk, optical disk, magnetic disk, semiconductor memory, etc.; and a communication section 809 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet.
[0135] In particular, the methods and / or embodiments in this application can be implemented as computer software programs. For example, the embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. When the computer program is executed by a central processing unit (CPU) 801, it performs the functions defined in the methods of this application.
[0136] Another embodiment of this application provides a computer-readable storage medium having computer program instructions stored thereon, which can be executed by a processor to implement the methods and / or technical solutions of any one or more embodiments of this application described above.
[0137] Specifically, this embodiment may employ any combination of one or more computer-readable media. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device.
[0138] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including—but not limited to—electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, capable of sending, propagating, or transmitting programs for use by or in connection with an instruction execution system, apparatus, or device.
[0139] The program code contained on a computer-readable medium may be transmitted using any suitable medium, including—but not limited to—wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.
[0140] Computer program code for performing the operations of this application can be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, and C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0141] The flowcharts or block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-specific system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0142] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0143] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or page components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.
[0144] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0145] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.
[0146] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0147] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
[0148] Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in a device claim may also be implemented by a single unit or device through software or hardware. Terms such as "first," "second," etc., are used to indicate names and do not indicate any specific order. < / md5-2> < / md5-1> < / md5-2> < / md5-1>
Claims
1. A file upload method, applied to a first client, comprising: The file is split into segments, generating a set of file fragments; Upload the file fragment set to the server; Receive the first verification value of the file fragment in the file fragment set sent by the server; Calculate the second checksum of the file fragment; The first and second check values of the file segments are compared to generate the upload result of the file segments.
2. A file processing method, applied on a server side, comprising: Receive the set of file fragments uploaded by the first client, which are the files split into segments; Calculate the first checksum of the file fragments in the file fragment set; In response to determining that all file fragments in the file fragment set have been uploaded, the first checksums of the file fragments in the file fragment set are merged to generate the first checksum of the file.
3. The method according to claim 2, wherein, The method further includes: The first verification value of the file fragment in the file fragment set is sent to the first client so that the first client can determine the upload result of the file fragment.
4. The method according to claim 2, wherein, The step of merging the first checksums of file fragments in the file fragment set to generate the first checksum of the file includes: According to the order of the file fragments in the file, the first checksums of the file fragments in the file fragment set are concatenated to generate the first checksum of the file.
5. A file verification method, applied to a second client, comprising: Send the file retrieval request to the server; Receive the file fragment set and first checksum of the file sent by the server; Calculate the third checksum of the file fragments in the file fragment set; Merge the third checksums of the file fragments in the file fragment set to generate the third checksum of the file; The first checksum and the third checksum of the file are compared to generate the checksum result of the file.
6. The method according to claim 5, wherein, Sending the file retrieval request to the server includes: Send the file metadata retrieval request to the server; Receive the metadata information of the file sent by the server; Based on the metadata information, the file retrieval request is sent.
7. The method according to claim 5, wherein, The process of merging the third checksums of file fragments in the file fragment set to generate the third checksum of the file includes: The third checksum of the file is generated by concatenating the third checksums of the file fragments in the file fragment set according to the order of the file fragments in the file.
8. A file upload device, configured in a first client, comprising: The file splitting module is configured to split files and generate a set of file fragments; The file chunk upload module is configured to upload the set of file chunks to the server. The verification value receiving module is configured to receive the first verification value of a file fragment in the file fragment set sent by the server; The checksum calculation module is configured to calculate a second checksum for the file fragment; The verification value comparison module is configured to compare the first verification value and the second verification value of the file segment to generate the upload result of the file segment.
9. A file processing device, disposed on a server, comprising: The file fragment receiving module is configured to receive a set of file fragments that are split from a file and uploaded by the first client. The checksum calculation module is configured to calculate the first checksum of the file fragments in the file fragment set; The checksum merging module is configured to, in response to determining that all file fragments in the file fragment set have been uploaded, merge the first checksums of the file fragments in the file fragment set to generate the first checksum of the file.
10. A file verification device, configured on a second client, comprising: The request sending module is configured to send a file retrieval request to the server, wherein the file retrieval request includes the file identifier; The file fragment receiving module is configured to receive the file fragment set and the first check value of the file sent by the server; The checksum calculation module is configured to calculate the third checksum of the file fragments in the file fragment set; The checksum merging module is configured to merge the third checksums of file fragments in the file fragment set to generate the third checksum of the file. The checksum comparison module is configured to compare the first checksum and the third checksum of the file and generate the checksum result of the file.
11. A file verification system, comprising a first client, a second client, and a server: The first client is used to split the file and generate a set of file fragments; and upload the set of file fragments to the server. The server is used to calculate the first check value of the file fragment in the file fragment set; In response to determining that all file fragments in the file fragment set have been uploaded, the first checksums of the file fragments in the file fragment set are merged to generate the first checksum of the file; The second client is used to send a file retrieval request to the server; and to receive the file fragment set and first verification value of the file sent by the server. Calculate the third checksum of the file fragments in the file fragment set; Merge the third checksums of the file fragments in the file fragment set to generate the third checksum of the file; The first checksum and the third checksum of the file are compared to generate the checksum result of the file.
12. An electronic device, the electronic device comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
13. A computer-readable medium having stored thereon computer program instructions that can be executed by a processor to implement the method as described in any one of claims 1-7.
14. A computer program product comprising a computer program that, when executed by a processor, implements the method as described in any one of claims 1-7.
Citation Information
Cited By
Front-end processing method, system and equipment for large file and storage medium
CN121056452A
Front-end processing method, system and device of large file and storage medium
CN121056452B
