Lossless transmission verification method and system

Abstract

The application discloses a lossless transmission checking method and system, the method comprises the following steps: a sending end reading thread receives a user command sent by a front end, calls a file processing method, reads a file, cuts the file content into messages with a specified size, calculates a checksum of the file, and sends the messages to a sending end sending thread through a queue; the sending end sending thread sends the messages to a receiving end receiving thread through an improved efficient RPC protocol, the receiving end receiving thread calculates checksums of the messages, calculates a checksum of an entire file after receiving a file, and stores the checksum in a message queue; a receiving end processing thread reads the assembled messages, calls a message processing method to process the messages, and the processing is performed until all the messages are processed; the front end compares a sending file checksum description list with a receiving file checksum description list, and obtains a transmission result of whether lossless transmission is realized. The application improves the objectivity of data lossless checking.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, and in particular to a lossless transmission verification method and system. Background Technology

[0002] When performing high-volume lossless transmission, the question often arises as to how to verify that the transmission is truly lossless. One lossless transmission verification method addresses situations where the receiving end has insufficient storage space and cannot store all received files for an extended period, but needs to maintain high throughput. This method visually demonstrates the accuracy of the transmitted data by querying the file IDs and corresponding checksums at both the sending and receiving ends.

[0003] There's a benchmark for achieving lossless transmission while maintaining high speeds. We need to visually verify that lossless transmission has indeed been achieved. The best approach would be to prepare a batch of files, send them to the receiving end, store them on the receiving end's server, and then verify lossless transmission using MD5 hashes. However, this is clearly impractical because server hard drives are insufficient in size, and the storage speed is not fast enough. Therefore, we plan to repeatedly transmit multiple files, simultaneously calculating their checksums at the receiving end. By comparing the checksums at the sending and receiving ends, we can guarantee that all data has been transmitted losslessly.

[0004] like Figure 1 As shown, existing efficient RPC technology can achieve lossless message transmission up to 8MB in size, but its verification is not intuitive or objective enough. It only checks the third bit of data after receiving the message. Obviously, existing efficient RPC technology cannot achieve lossless verification under continuous high traffic conditions, nor can it achieve the objectivity of lossless verification.

[0005] Therefore, existing technologies still need to be improved and developed. Summary of the Invention

[0006] The main objective of this invention is to provide a lossless transmission verification method and system, which aims to solve the problems in the prior art that lossless data transmission verification cannot be performed under continuous high-volume conditions for a long time, and the objectivity of lossless verification cannot be achieved.

[0007] To achieve the above objectives, the present invention provides a lossless transmission verification method, which is applied to a lossless transmission verification system. The lossless transmission verification system includes a front-end, a sending server, and a receiving server. The sending server includes a sending-end reading thread and a sending-end sending thread, and the receiving server includes a receiving-end receiving thread and a receiving-end processing thread. The lossless transmission verification method includes the following steps: The sending end reading thread receives user commands sent by the front end. The user commands include a list of file checksums to be sent and a list of files to be stored. It calls a file processing method, reads the file according to the user commands, splits the file content into messages of a specified size, calculates the checksum of the file, sends the message to the sending end sending thread according to the message sent by the front end, and sends the message to the sending end sending thread through a queue. The sending thread of the sending end sends the message to the receiving thread of the receiving end through the improved efficient RPC protocol. After receiving the message, the receiving thread of the receiving end calculates the checksum of each message. After receiving a file, it calculates the checksum of the entire file and stores it in the message queue. The receiving end processing thread reads the assembled message from the message queue, calls the message processing method to process the message, until all messages have been processed; After all files from the front end have been sent, the sender queries and prints the send file checksum description list of the sending end reading thread, and queries and prints the receive file checksum description list of the receiving end processing thread. The send file checksum description list and the receive file checksum description list are compared to obtain the transmission result of whether lossless transmission has been achieved, and the send file checksum description list and the receive file checksum description list are displayed in a list.

[0008] Optionally, in the lossless transmission verification method, the structure of the sent file checksum list is a file checksum description list; the structure of the sent file storage list is a file storage list; and the message includes a file ID, a message ID, and a file message count.

[0009] Optionally, in the lossless transmission verification method, the receiving end processing thread includes a received file checksum list; the structure of the received file checksum list is a file checksum description list.

[0010] Optionally, in the lossless transmission verification method, the process of the sending server sending a file to the receiving server includes: The sending end reading thread puts the messages of a file into the message queue in sequence, and each message carries the file ID, message ID and file message count; After popping a message from the message queue, the sending thread of the sending end divides the message into packets, each packet carrying a file ID, a message ID, and the number of file messages; The sending thread at the sending end sends messages to the receiving thread at the receiving end, and each message carries a file ID, a message ID, and the number of file messages. The receiving end receiving thread replies with an ACK message to the sending end sending thread; The receiving thread at the receiving end parses the message header and assembles the complete message based on the file ID and message ID; The receiving thread at the receiving end puts the assembled message into a message queue, and the message queue records the file ID, message ID, and number of file messages. The receiving end processing thread retrieves messages from the message queue, calls the message processing method to process the messages, and continues until all messages have been processed.

[0011] Optionally, in the lossless transmission verification method, the process of the sending end reading thread calling the file processing method to process the file includes: Enter a filename; Search for elements in the sent file storage list to check if the file has been read. If the file has not been read before, create a file data storage structure, store it in the file storage list, update the number of messages in the file data storage structure according to the file size and the size of each message, update the file name, create a file data buffer, and read the file into the buffer of the file data buffer according to the configured message size; If the file has been read, create a file checksum description structure, obtain the file ID by incrementing by 1, assign the message count, store the file name, create a message buffer, and start traversing the cache in the file data buffer; Check if the cache has been traversed completely; If not completed, calculate the 16-bit checksum for each cache, store the checksum in the message description in the message buf, update the message ID, update the message length to the length of the data in the cache, and update the message start address to the cache address. If completed, calculate the total file checksum based on the message checksums of each message in the message buffer, and store the total checksum in the file checksum description structure.

[0012] Optionally, in the lossless transmission verification method, the process of the receiving end processing thread calling the message processing method to process the message includes: When the receiving end processing thread receives a message from the message queue, it searches the file checksum description list by file ID to determine whether the file checksum description structure is found. If not found, create a file checksum description structure, store the file ID, store the file checksum description list, create a message buffer, and initialize the message checksum and message ID of all message descriptions in the message buffer; If found, calculate the message checksum and store it in the message description corresponding to the message ID in the message buf. Determine whether the file has been completely received by using file integrity checks. If all messages have been received, calculate the total file checksum based on the message checksums of all messages described in the message buf, and store it in the file checksum description structure.

[0013] Optionally, in the lossless transmission verification method, the process of the receiving end processing thread performing file integrity checks includes: Find the message buf pointer in the file checksum description structure in the file checksum list by using the file ID in the message; The message buf is located by checking the message buf pointer in the file checksum and description structure. Check that all messages in the message buffer have been checked and traversed; If all messages in the message buffer have been checked and traversed, then the message buffer will return that file reception is complete. If all message checksums in the message buffer have not been checked and traversed, then check if the message checksum is the initial value. If the message checksum is not the initial value, return indicating that all message checksums in the message buffer have been traversed. If the message checksum is the initial value, then file reception is not complete.

[0014] Optionally, in the lossless transmission verification method, the file checksum description list includes a file checksum description structure.

[0015] Optionally, in the lossless transmission verification method, the file checksum description structure includes a message structure diagram; the message structure diagram includes a message ID, a message checksum, a message start address, and a message length.

[0016] In addition, to achieve the above objectives, the present invention also provides a lossless transmission verification system, wherein the lossless transmission verification system includes: a front end, a sending end server and a receiving end server, the sending end server includes a sending end reading thread and a sending end sending thread, and the receiving end server includes a receiving end receiving thread and a receiving end processing thread. The sending end reading thread is used to receive user commands sent by the front end. The user commands include a list of file checksums to be sent and a list of files to be stored. The thread calls a file processing method, reads the file according to the user commands, splits the file content into messages of a specified size, calculates the checksum of the file, sends a message command according to the front end, and sends the message to the sending end sending thread through a queue. The sending thread at the sending end is used to send the message to the receiving thread at the receiving end through the improved efficient RPC protocol. After receiving the message, the receiving thread at the receiving end calculates the checksum of each message. After receiving a file, it calculates the checksum of the entire file and stores it in the message queue. The receiving end processing thread is used to read the assembled message from the message queue, call the message processing method to process the message, until all messages have been processed. The front end is used to query and print the sent file checksum description list of the sending end reading thread and the received file checksum description list of the receiving end processing thread after all files have been sent. The front end compares the sent file checksum description list with the received file checksum description list to obtain the transmission result of whether lossless transmission has been achieved, and displays the sent file checksum description list and the received file checksum description list in a list.

[0017] In this invention, the sending end's reading thread receives user commands sent by the front end, calls the file processing method, reads the file according to the user commands, segments the file content into messages of a specified size, calculates the file's checksum, and sends the messages to the sending end's sending thread via a queue according to the front end's message sending command. The sending end's sending thread sends the messages to the receiving end's receiving thread through an improved efficient RPC protocol. After receiving the messages, the receiving end's receiving thread calculates the checksum of each message. Once a file is collected, it calculates the checksum of the entire file and stores it in a message queue. The receiving end's processing thread reads the assembled messages from the message queue, calls the message processing method to process the messages, and so on until all messages are processed. After all files have been sent, the front end queries and prints the sending file checksum description list from the sending end's reading thread and the receiving file checksum description list from the receiving end's processing thread. The sending file checksum description lists are compared with the receiving file checksum description lists to determine whether lossless transmission has been achieved, and the results are displayed in lists. This invention improves the objectivity of lossless data verification. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of an efficient RPC system architecture for message transmission in the prior art; Figure 2 This is a schematic diagram of an improved efficient RPC system architecture in a preferred embodiment of the lossless transmission verification method of the present invention. Figure 3 This is a flowchart of a preferred embodiment of the lossless transmission verification method of the present invention; Figure 4 This is a schematic diagram of the message structure in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 5 This is a schematic diagram of the file verification and description structure in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 6 This is a schematic diagram of a file checksum description list in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 7 This is a schematic diagram of the data storage structure of the transmitted file in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 8 This is a schematic diagram of the file storage list in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 9 This is a schematic diagram of the lossless verification interaction process in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 10 This is a schematic diagram of a file transfer interaction process in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 11 This is a schematic diagram of the file processing process in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 12 This is a schematic diagram of the message processing process in a preferred embodiment of the lossless transmission verification method of the present invention; Figure 13 This is a schematic diagram of the file integrity check process in a preferred embodiment of the lossless transmission verification method of the present invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0020] The lossless transmission verification system described in the preferred embodiment of the present invention, such as... Figure 2 As shown, the lossless transmission verification system includes a front-end, a sending server, and a receiving server. The sending server includes a sending read thread and a sending send thread, and the receiving server includes a receiving receive thread and a receiving processing thread.

[0021] The sending end reading thread is used to receive user commands sent by the front end. The user commands include a list of file checksums to be sent and a list of file storage to be sent. The thread calls a file processing method, reads the file according to the user commands, splits the file content into messages of a specified size, calculates the checksum of the file, sends the message to the sending end sending thread according to the message sent by the front end, and sends the message to the sending end sending thread through a queue.

[0022] The sending thread at the sending end sends the message to the receiving thread at the receiving end via an improved efficient RPC protocol. After receiving the message, the receiving thread at the receiving end calculates the checksum of each message. Once a file is collected, it calculates the checksum of the entire file and stores it in the message queue.

[0023] The receiving end processing thread is used to read the assembled messages from the message queue, call the message processing method to process the messages, until all messages have been processed.

[0024] The front-end is used to query and print the sent file checksum description list of the sending end reading thread and the received file checksum description list of the receiving end processing thread after all files have been sent. The front-end compares the sent file checksum description list with the received file checksum description list to obtain the transmission result of whether lossless transmission has been achieved, and displays the sent file checksum description list and the received file checksum description list in a list.

[0025] This invention adds a sending-end reading thread and a receiving-end processing thread to the existing efficient RPC system architecture, along with a front-end. The front-end issues commands to the sending-end reading thread to read the file. After reading the file, the sending-end reading thread segments the file content into messages of a specified size and calculates the file's checksum; then, it sends the messages out using the improved efficient RPC protocol. Upon receiving the messages, the receiving-end processing thread calculates the checksum of each message, and after receiving all the messages, it calculates the checksum of the entire file. After all files have been sent, the front-end queries and prints the file checksum description list from both the sending-end reading thread and the receiving-end processing thread, thus providing a clear and objective transmission result.

[0026] The lossless transmission verification method described in the preferred embodiment of the present invention, such as... Figure 3 As shown, the lossless transmission verification method includes the following steps: Step S10: The sending end reading thread receives the user command sent by the front end. The user command includes a list of file checksums to be sent and a list of file storage to be sent. The thread calls the file processing method, reads the file according to the user command, cuts the file content into messages of a specified size, calculates the checksum of the file, sends the message to the sending end sending thread according to the message sending command from the front end, and sends the message to the sending end sending thread through the queue. Step S20: The sending thread of the sending end sends the message to the receiving thread of the receiving end through the improved efficient RPC protocol. After receiving the message, the receiving thread of the receiving end calculates the checksum of each message. After receiving a file, it calculates the checksum of the entire file and stores it in the message queue. Step S30: The receiving end processing thread reads the assembled message from the message queue, calls the message processing method to process the message, until all messages have been processed; Step S40: After all files, including those from the front end, have been sent, query and print the sent file checksum description list of the sending end reading thread, query and print the received file checksum description list of the receiving end processing thread, compare the sent file checksum description list with the received file checksum description list to obtain the transmission result of whether lossless transmission has been achieved, and display the sent file checksum description list and the received file checksum description list in a list.

[0027] The structure of the sent file checksum list is a file checksum description list; the structure of the sent file storage list is a file storage list; the message includes a file ID, a message ID, and a file message count; the receiving end processing thread includes a received file checksum list; the structure of the received file checksum list is a file checksum description list.

[0028] like Figure 4 As shown, the message structure diagram includes a message ID, a message checksum, a message start address, and a message length. The message ID is a 16-bit unsigned integer representing the message's order within the file; the message checksum is a 32-bit unsigned integer used to store the 16-bit unsigned checksum of the message; the message start address is a pointer; and the message length is a 16-bit unsigned integer representing the number of bytes occupied by the message.

[0029] like Figure 5 As shown, the file checksum description structure includes a file ID, filename, total checksum, message count, and a message buffer pointer. The file ID is an integer representing the sequence number of the file checksum description structure; the total checksum is a 16-bit unsigned integer representing the checksum of the file; the message count is an integer representing how many messages the file was split into; the message buffer pointer is a pointer to the message buffer; the message buffer consists of several message descriptions, and the structure of each message description is as follows: Figure 4 The message structure diagram (message description structure).

[0030] like Figure 6The diagram illustrates the structure of the document verification and description list, which is a list containing multiple elements, where each element is... Figure 5 File verification and description structure.

[0031] like Figure 7 As shown, the file data storage structure includes a filename, a file data buffer pointer, and a message count. The filename is a string representing the absolute path of the file; the file data buffer pointer is a pointer to a file data buffer; the file data buffer is an array containing message buffers. Each buffer is used to store data read from the file.

[0032] like Figure 8 As shown, the file storage list is a list structure containing multiple elements, which are the data storage structures for the sent files.

[0033] like Figure 9 As shown, the process of the lossless verification method (representing the file verification method for transmitting 3 files) is as follows: S101. The front end calls the file read command (i.e., the user command) to request the file to be read from the sending end's read thread; S102, The sending end reading thread executes the file processing method (S101-S102 are executed three times repeatedly). S103. The front end calls the message sending command to read the thread request from the sending end to send a message; S104. The sending end reading thread and the receiving end processing thread execute the file transfer method (repeated three times). S105. The front end reads the sending thread from the sending end to check whether the sending is complete; S106. The sending end's reading thread returns a message to the front end indicating that the sending is complete. S107. The front end reads the checksum and description list of the file to be sent from the sending end's reading thread; S108. The sending end's reading thread sends a file checksum and description list to the front end; S109. The front end reads the checksum and description list of the received file from the receiving end processing thread. S110. The receiving end processing thread returns a list of received file checksums and descriptions to the front end. S111. The front end compares the sent file checksum description list with the received file checksum description list to determine whether lossless transmission has been achieved; and displays the sent file checksum description list and the received file checksum description list in a list.

[0034] like Figure 10 As shown, the process of the sending server sending a file to the receiving server includes: S201, The sending end reading thread puts the messages of a file into the message queue in order, and each message carries the file ID, message ID and file message count; S202. After popping a message from the message queue, the sending thread of the sending end divides the message into packets, each packet carrying a file ID, a message ID, and the number of file messages. S203. The sending thread of the sending end sends a message to the receiving thread of the receiving end, and each message carries a file ID, a message ID and a number of file messages; S204. The receiving end receiving thread replies with an ACK message to the sending end sending thread. S205. The receiving thread at the receiving end parses the message header and assembles the complete message according to the file ID and message ID; S206. The receiving thread of the receiving end puts the assembled message into a message queue, and the message queue records the file ID, message ID and the number of file messages; S207. The receiving end processing thread retrieves messages from the message queue and calls the message processing method to process the messages until all messages have been processed.

[0035] like Figure 11 As shown, the process of the sending end reading thread calling the file processing method to process the file includes: S301, Enter the file name; S302. Search for elements in the file storage list to check if the file has been read. S303. If the file has not been read before, create a file data storage structure, store it in the file storage list, update the number of messages in the file data storage structure according to the file size and the size of each message, update the file name, create a file data buffer, and read the file into the buffer of the file data buffer according to the configured message size. S304. If the file has been read, create a file checksum description structure, obtain the file ID by incrementing by 1, assign the message count, store the file name, create a message buffer, and start traversing the cache in the file data buffer. S305. Determine if the cache iteration is complete; S306. If not completed, calculate the 16-bit checksum of each cache, store the checksum in the message description in the message buf, update the message ID, update the message length to the length of the data in the cache, and update the message start address to the cache address. S307. If completed, calculate the total file checksum based on the message checksums of each message in the message buf, and store the total checksum in the file checksum description structure.

[0036] like Figure 12As shown, the process of the receiving end processing thread calling the message processing method to process messages includes: S401. When the receiving end processing thread receives a message from the message queue, it searches the file checksum description list by file ID and determines whether the file checksum description structure is found. S402. If not found, create a file checksum description structure, store the file ID, store the file checksum description list, create a message buffer, and initialize the message checksum and message ID of all message descriptions in the message buffer. S403. If found, calculate the message checksum and store it in the message description corresponding to the message ID in the message buf. S404. Determine whether the file has been completely received by using the file integrity check method; S405. If all messages have been received, calculate the total file checksum based on the message checksums of all messages described in the message buf, and store it in the file checksum description structure.

[0037] like Figure 13 As shown, the process of the receiving end processing thread performing file integrity checks includes: S501. Locate the message buf pointer in the file checksum description structure in the file checksum list by the file ID in the message; S502, Locate the message buf using the message buf pointer in the file checksum and description structure; S503. Determine that all messages in the message buffer have been checked and traversed. S504. If the message checksum in the message buffer is not yet complete, check if the message checksum is the initial value. If the message checksum is not the initial value, return to check if the message checksum in the message buffer is complete. S505. If all messages in the message buffer have been checked and traversed, then return that file reception is complete. S506. If the message checksum is the initial value, then return "File reception not completed".

[0038] In summary, this invention provides a lossless transmission verification method and system. The method includes: a sending end reading thread receiving a user command sent by a front end, calling a file processing method, reading a file according to the user command, splitting the file content into messages of a specified size, calculating the file checksum, and sending the messages to the sending end sending thread through a queue according to the front end's message sending command; the sending end sending thread sending the messages to the receiving end receiving thread through an improved efficient RPC protocol; the receiving end receiving thread receiving the messages, calculating the checksum of each message, and after receiving a file, calculating the checksum of the entire file and storing it in a message queue; the receiving end processing thread reading the assembled messages from the message queue, calling the message processing method to process the messages until all messages are processed; after all files have been sent, the front end queries and prints the sent file checksum description list of the sending end reading thread, queries and prints the received file checksum description list of the receiving end processing thread, compares the sent file checksum description list with the received file checksum description list to obtain the transmission result of whether lossless transmission has been achieved, and displays the sent file checksum description list and the received file checksum description list in a list. This invention improves the objectivity of lossless data verification.

[0039] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal that includes that element.

[0040] Of course, those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.). The program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The computer-readable storage medium can be a memory, magnetic disk, optical disk, etc.

[0041] It should be understood that the application of the present invention is not limited to the examples above. Those skilled in the art can make improvements or modifications based on the above description, and all such improvements and modifications should fall within the protection scope of the appended claims.

Claims

1. A lossless transmission verification method, characterized in that, The lossless transmission verification method is applied to a lossless transmission verification system, which includes a front-end, a sending server, and a receiving server. The sending server includes a sending reading thread and a sending sending thread, and the receiving server includes a receiving receiving thread and a receiving processing thread. The lossless transmission verification method includes: The sending end reading thread receives user commands sent by the front end. The user commands include a list of file checksums to be sent and a list of files to be stored. It calls a file processing method, reads the file according to the user commands, splits the file content into messages of a specified size, calculates the checksum of the file, sends the message to the sending end sending thread according to the message sent by the front end, and sends the message to the sending end sending thread through a queue. The sending thread of the sending end sends the message to the receiving thread of the receiving end through the improved efficient RPC protocol. After receiving the message, the receiving thread of the receiving end calculates the checksum of each message. After receiving a file, it calculates the checksum of the entire file and stores it in the message queue. The receiving end processing thread reads the assembled message from the message queue, calls the message processing method to process the message, until all messages have been processed; After all files from the front end have been sent, the sender queries and prints the send file checksum description list of the sending end reading thread, and queries and prints the receive file checksum description list of the receiving end processing thread. The send file checksum description list and the receive file checksum description list are compared to obtain the transmission result of whether lossless transmission has been achieved, and the send file checksum description list and the receive file checksum description list are displayed in a list.

2. The lossless transmission verification method according to claim 1, characterized in that, The structure of the sent file checksum list is a file checksum description list; the structure of the sent file storage list is a file storage list; the message includes a file ID, a message ID, and a file message count.

3. The lossless transmission verification method according to claim 1, characterized in that, The receiving end processing thread includes a received file checksum list; the structure of the received file checksum list is a file checksum description list.

4. The lossless transmission verification method according to claim 1, characterized in that, The process of the sending server sending a file to the receiving server includes: The sending end reading thread puts the messages of a file into the message queue in sequence, and each message carries the file ID, message ID and file message count; After popping a message from the message queue, the sending thread of the sending end divides the message into packets, each packet carrying a file ID, a message ID, and the number of file messages; The sending thread at the sending end sends messages to the receiving thread at the receiving end, and each message carries a file ID, a message ID, and the number of file messages. The receiving end receiving thread replies with an ACK message to the sending end sending thread; The receiving thread at the receiving end parses the message header and assembles the complete message based on the file ID and message ID; The receiving thread at the receiving end puts the assembled message into a message queue, and the message queue records the file ID, message ID, and number of file messages. The receiving end processing thread retrieves messages from the message queue, calls the message processing method to process the messages, and continues until all messages have been processed.

5. The lossless transmission verification method according to claim 1, characterized in that, The process of the sending end reading thread calling the file processing method to process the file includes: Enter a filename; Search for elements in the sent file storage list to check if the file has been read. If the file has not been read, create a file data storage structure, store it in the file storage list, update the message count of the file data storage structure according to the file size and the size of each message, update the file name, create a file data buffer, and read the file into the buffer of the file data buffer according to the configured message size; If the file has been read, create a file checksum description structure, obtain the file ID by incrementing by 1, assign the message count, store the file name, create a message buffer, and start traversing the cache in the file data buffer; Check if the cache has been traversed completely; If not completed, calculate the 16-bit checksum for each cache, store the checksum in the message description in the message buf, update the message ID, update the message length to the length of the data in the cache, and update the message start address to the cache address. If completed, calculate the total file checksum based on the message checksums of each message in the message buffer, and store the total checksum in the file checksum description structure.

6. The lossless transmission verification method according to claim 1, characterized in that, The process of the receiving end processing thread calling the message processing method to process the message includes: When the receiving end processing thread receives a message from the message queue, it searches the file checksum description list by file ID to determine whether the file checksum description structure is found. If not found, create a file checksum description structure, store the file ID, store the file checksum description list, create a message buffer, and initialize the message checksum and message ID of all message descriptions in the message buffer; If found, calculate the message checksum and store it in the message description corresponding to the message ID in the message buf. Determine whether the file has been completely received by using file integrity checks. If all messages have been received, calculate the total file checksum based on the message checksums of all messages described in the message buf, and store it in the file checksum description structure.

7. The lossless transmission verification method according to claim 6, characterized in that, The process of file integrity checking performed by the receiving end processing thread includes: Find the message buf pointer in the file checksum description structure in the file checksum list by using the file ID in the message; The message buf is located by checking the message buf pointer in the file checksum and description structure. Check that all messages in the message buffer have been checked and traversed; If all messages in the message buffer have been checked and traversed, then the message buffer will return that file reception is complete. If all message checksums in the message buffer have not been checked and traversed, then check if the message checksum is the initial value. If the message checksum is not the initial value, return indicating that all message checksums in the message buffer have been traversed. If the message checksum is the initial value, then file reception is not complete.

8. The lossless transmission verification method according to claim 2, characterized in that, The file checksum description list includes a file checksum description structure.

9. The lossless transmission verification method according to claim 8, characterized in that, The file checksum description structure includes a message structure diagram; the message structure diagram includes a message ID, a message checksum, a message start address, and a message length.

10. A lossless transmission verification system, characterized in that, The lossless transmission verification system includes a front-end, a sending server, and a receiving server. The sending server includes a sending reading thread and a sending sending thread. The receiving server includes a receiving receiving thread and a receiving processing thread. The sending end reading thread is used to receive user commands sent by the front end. The user commands include a list of file checksums to be sent and a list of files to be stored. The thread calls a file processing method, reads the file according to the user commands, splits the file content into messages of a specified size, calculates the checksum of the file, sends a message command according to the front end, and sends the message to the sending end sending thread through a queue. The sending thread at the sending end is used to send the message to the receiving thread at the receiving end through the improved efficient RPC protocol. After receiving the message, the receiving thread at the receiving end calculates the checksum of each message. After receiving a file, it calculates the checksum of the entire file and stores it in the message queue. The receiving end processing thread is used to read the assembled message from the message queue, call the message processing method to process the message, until all messages have been processed. The front end is used to query and print the sent file checksum description list of the sending end reading thread and the received file checksum description list of the receiving end processing thread after all files have been sent. The front end compares the sent file checksum description list with the received file checksum description list to obtain the transmission result of whether lossless transmission has been achieved, and displays the sent file checksum description list and the received file checksum description list in a list.

Images