Disclosure of Invention
The present application is directed to solving, at least to some extent, one of the technical problems in the related art.
Therefore, the application provides a data transmission consistency checking method, a data transmission consistency checking device and a data transmission consistency checking storage medium, which are used for solving the technical problem that a sender cannot prevent from denying the sent data and a receiver cannot prevent from tampering the data in the prior art.
To achieve the above object, an embodiment of a first aspect of the present application provides a method for checking consistency of data transmission, including:
coding data to be sent by a message digest algorithm to generate a data digest to be sent, and encrypting the data digest to be sent by using a first private key to generate a data signature to be sent;
sending the data to be sent and the data signature to be sent to a receiver so that the receiver decrypts the data signature to be sent through a first public key to obtain a first received data abstract, codes the received data to be sent through a message abstract algorithm to generate a second received data abstract, and if the first received data abstract is the same as the second received data abstract, determines that the data transmission is consistent;
and receiving a message signature, decrypting the message signature through a second public key, judging that the received message number is the same as the sent message number, and determining that the receiver receives the data.
The data transmission consistency checking method of the embodiment of the application includes the steps of coding data to be transmitted through a message digest algorithm to generate a data digest to be transmitted, encrypting the data digest to be transmitted through a first private key to generate a data signature to be transmitted, transmitting the data to be transmitted and the data signature to be transmitted to a receiving party, enabling the receiving party to decrypt the data signature to be transmitted through a first public key to obtain a first received data digest, coding the received data to be transmitted through the message digest algorithm to generate a second received data digest, determining that data transmission is consistent if the first received data digest is the same as the second received data digest, receiving the message signature, decrypting the message signature through the second public key, judging that a received message number is the same as a transmitted message number, and determining that the receiving party receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to achieve the above object, an embodiment of a second aspect of the present application provides a method for checking consistency of data transmission, including:
acquiring data to be sent and a data signature to be sent;
decrypting the to-be-sent data signature through a first public key to obtain a first received data abstract, and coding received to-be-sent data through a message abstract algorithm to generate a second received data abstract;
if the first received data abstract and the second received data abstract are the same, determining that the data transmission is consistent;
encrypting the received information number by a second private key to generate a message signature;
and sending the message signature to a sender so that the sender decrypts the message signature through a second public key, judges that the received message number is the same as the sent message number, and determines that the receiver receives the data.
The data transmission consistency verification method of the embodiment of the application decrypts the data signature to be transmitted through the first public key by acquiring the data to be transmitted and the data signature to be transmitted to obtain a first received data abstract, and codes the received data to be transmitted through a message abstract algorithm to generate a second received data abstract; and if the first received data digest is the same as the second received data digest, determining that the data transmission is consistent, encrypting the received information number through a second private key to generate a message signature, sending the message signature to the sender so that the sender decrypts the message signature through a second public key, judging that the received information number is the same as the sent information number, and determining that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to achieve the above object, an embodiment of a third aspect of the present application provides a data transmission consistency checking apparatus, including:
the encoding and encrypting module is used for encoding data to be transmitted through a message digest algorithm to generate a data digest to be transmitted and encrypting the data digest to be transmitted by using a first private key to generate a data signature to be transmitted;
the sending module is used for sending the data to be sent and the data signature to be sent to a receiving party so that the receiving party decrypts the data signature to be sent through a first public key to obtain a first received data abstract, codes the received data to be sent through a message abstract algorithm to generate a second received data abstract, and if the first received data abstract is the same as the second received data abstract, the data transmission is determined to be consistent.
And the receiving judgment module is used for receiving the message signature, decrypting the message signature through a second public key, judging that the received message number is the same as the sent message number, and determining that the receiver receives the data.
The data transmission consistency verification device of the embodiment of the application encodes data to be transmitted through a message digest algorithm to generate a data digest to be transmitted, encrypts the data digest to be transmitted through a first private key to generate a data signature to be transmitted, transmits the data to be transmitted and the data signature to be transmitted to a receiver, so that the receiver decrypts the data signature to be transmitted through a first public key to obtain a first received data digest, encodes the received data to be transmitted through a message digest algorithm to generate a second received data digest, determines that the data are transmitted consistently if the first received data digest is the same as the second received data digest, receives the message signature, decrypts the message signature through the second public key, judges that a received message number is the same as a transmitted message number, and determines that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
To achieve the above object, a fourth aspect of the present application provides a data transmission consistency check apparatus, including:
the acquisition module is used for acquiring data to be transmitted and a data signature to be transmitted;
the decryption coding module is used for decrypting the to-be-sent data signature through a first public key to obtain a first received data abstract, and coding the received to-be-sent data through a message abstract algorithm to generate a second received data abstract;
a determining module, configured to determine that data transmission is consistent if the first received data digest is the same as the second received data digest;
the encryption module is used for encrypting the received information number through a second private key to generate a message signature;
and the first sending module is used for sending the message signature to a sender so that the sender decrypts the message signature through a second public key, judges that the received message number is the same as the sent message number, and determines that the receiver receives the data.
The data transmission consistency verification device of the embodiment of the application decrypts the data signature to be transmitted through the first public key by acquiring the data to be transmitted and the data signature to be transmitted to obtain a first received data abstract, and codes the received data to be transmitted through a message abstract algorithm to generate a second received data abstract; and if the first received data digest is the same as the second received data digest, determining that the data transmission is consistent, encrypting the received information number through a second private key to generate a message signature, sending the message signature to the sender so that the sender decrypts the message signature through a second public key, judging that the received information number is the same as the sent information number, and determining that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
To achieve the above object, a fifth embodiment of the present application provides a computer device, including: a processor and a memory; wherein the processor executes a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to implement the data transmission consistency check method according to the first and second aspects.
To achieve the above object, a sixth aspect of the present application provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the data transmission consistency checking method according to the embodiments of the first and second aspects.
To achieve the above object, a seventh embodiment of the present application proposes a computer program product, wherein instructions of the computer program product, when executed by a processor, implement the data transmission consistency checking method according to the first and second embodiments.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.
The following describes a data transmission consistency check method, apparatus, computer device, and storage medium according to embodiments of the present application with reference to the drawings.
Fig. 1 is a flowchart illustrating a data transmission consistency checking method according to an embodiment of the present application.
First, a data transmission consistency check method is described on the receiving side, as shown in fig. 1, the data transmission consistency check method may include the following steps:
step 101, encoding data to be transmitted by a message digest algorithm to generate a data digest to be transmitted, and encrypting the data digest to be transmitted by using a first private key to generate a data signature to be transmitted.
In practical application, data transmission may be performed between a terminal and a server, or between a server and a server, and may be selected according to practical application requirements, so that the sender and the receiver in the present application may be devices such as a terminal and a server.
Specifically, in different application scenarios, the data to be sent is different, for example, the terminal a needs to send a document to the terminal B, the data to be sent is document data, for example, the terminal a needs to send a video file to the server C, and the data to be sent is video data.
Specifically, data to be sent is encoded through a message digest algorithm to generate a data digest to be sent, and then the data digest to be sent is encrypted by using a first private key to generate a data signature to be sent. The first private key has a corresponding first public key, and the first public key is sent to the receiving party after the sending party generates a key pair of the first private key and the first public key.
Step 102, sending the data to be sent and the data signature to be sent to a receiver, so that the receiver decrypts the data signature to be sent through a first public key to obtain a first received data digest, encodes the received data to be sent through a message digest algorithm to generate a second received data digest, and if the first received data digest is the same as the second received data digest, determining that the data transmission is consistent.
Specifically, after generating the data signature to be sent, the data to be sent and the data signature to be sent are sent to the receiver. It can be understood that, after receiving the data to be transmitted and the data signature to be transmitted, the receiver may also encode the received data to be transmitted by using a message digest algorithm to generate a second received data digest, decrypt the data signature to be transmitted by using the first public key to obtain a first received data digest, and determine whether the data transmission is consistent by determining whether the first received data digest and the second received data digest are the same, that is, determining that the data transmission is consistent if the first received data digest and the second received data digest are the same.
It should be noted that, the specific transmission mode of data transmission of the sending party and the receiving party is not limited, and the HTTP/HTTPs/FTP/SFTP, RPC, WebService, and the like are all applicable.
And 103, receiving the message signature, decrypting the message signature through the second public key, judging that the received message number is the same as the sent message number, and determining that the receiver receives the data.
It is to be understood that the second private key and the second public key are generated before the received information number is encrypted by the second private key to generate the message signature, and the second public key is transmitted to the sender.
Specifically, the receiver encrypts a received information number through a second private key to generate a message signature and sends the message signature to the sender, the sender decrypts the message signature through a second public key and judges that the received information number is the same as the sent message number, the receiver is determined to receive data, data transmission is determined to be successful when the received information number is the same as the sent message number, and the sender can resend the data if the received information number is not the same as the sent message number, that is, the data transmission is unsuccessful.
The data transmission consistency checking method of the embodiment of the application includes the steps of coding data to be transmitted through a message digest algorithm to generate a data digest to be transmitted, encrypting the data digest to be transmitted through a first private key to generate a data signature to be transmitted, transmitting the data to be transmitted and the data signature to be transmitted to a receiving party, enabling the receiving party to decrypt the data signature to be transmitted through a first public key to obtain a first received data digest, coding the received data to be transmitted through the message digest algorithm to generate a second received data digest, determining that data transmission is consistent if the first received data digest is the same as the second received data digest, receiving the message signature, decrypting the message signature through the second public key, judging that a received message number is the same as a transmitted message number, and determining that the receiving party receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to more fully describe the data transmission consistency check method of the present application, the following description is made on the receiving side.
Fig. 2 is a schematic flow chart of a data transmission consistency checking method according to a second embodiment of the present application, as shown in fig. 2, where the data transmission consistency checking method may include the following steps:
step 201, acquiring data to be transmitted and a signature of the data to be transmitted.
Step 202, decrypting the data signature to be transmitted through the first public key to obtain a first received data digest, and encoding the received data to be transmitted through a message digest algorithm to generate a second received data digest.
In step 203, if the first received data digest is the same as the second received data digest, it is determined that the data transmission is consistent.
It will also be appreciated that the receipt information may be sent to the sender after the first received data digest and the second received data digest are identical, and the transmission of the data is determined to be consistent.
And step 204, encrypting the received information number by a second private key to generate a message signature.
Step 205, sending the message signature to the sender, so that the sender decrypts the message signature through the second public key, and determines that the receiver receives the data if the received message number is the same as the sent message number.
It is to be understood that the second private key and the second public key are generated before the received information number is encrypted by the second private key to generate the message signature, and the second public key is transmitted to the sender.
Specifically, the receiver encrypts a received information number through a second private key to generate a message signature and sends the message signature to the sender, the sender decrypts the message signature through a second public key and judges that the received information number is the same as the sent message number, the receiver is determined to receive data, data transmission is determined to be successful when the received information number is the same as the sent message number, and the sender can resend the data if the received information number is not the same as the sent message number, that is, the data transmission is unsuccessful.
Therefore, because the receiver encrypts the message signature by the second private key and sends the encrypted message signature to the sender, the sender confirms that the receiver has received the message after receiving the message, and the receiver cannot deny the received message, and the sender cannot forge the message signature of the receiver.
Specifically, after acquiring the data to be transmitted and the data signature to be transmitted, the receiver may decrypt the data signature to be transmitted through the first public key transmitted by the previous transmitter to obtain a first received data digest, encode the received data to be transmitted through a message digest algorithm to generate a second received data digest, and determine that the data transmission is consistent when the first received data digest is the same as the second received data digest.
It should be noted that, if the first received data digest is different from the second received data digest, it is determined that the data transmission is inconsistent, and data transmission failure information is sent to the sender.
The data transmission consistency verification method of the embodiment of the application decrypts the data signature to be transmitted through the first public key by acquiring the data to be transmitted and the data signature to be transmitted to obtain a first received data abstract, and codes the received data to be transmitted through a message abstract algorithm to generate a second received data abstract; and if the first received data digest is the same as the second received data digest, determining that the data transmission is consistent, encrypting the received information number through a second private key to generate a message signature, sending the message signature to the sender so that the sender decrypts the message signature through a second public key, judging that the received information number is the same as the sent information number, and determining that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to make the above process more clear to those skilled in the art, the following detailed description is made with reference to fig. 3, as shown in fig. 3:
first, a sender generates a public/private key pair, wherein the public key is called a, the private key is called a1, the sender gives the public key a to a receiver, the receiver generates a public/private key pair, wherein the public key is called B, the private key is called B1, and the receiver gives the public key B to the sender.
Then, the sender performs MD5 digest on the data message body to be sent to obtain the data digest, then performs private key (private key A1 of the sender) encryption on the data digest, and the obtained encrypted signature sender sends the data and the signature encrypted by the private key to the receiver.
And then the receiver receives the data and the signature, records the log, decrypts the encrypted signature by using the public key A of the sender to obtain a data digest A, performs MD5 digest on the received data by the receiver to obtain a data digest B, and determines that the receiver receives the data if the receiver compares the data digest A with the data digest B and is the same as the data digest A and the data digest B.
If the compared data digests A and B of the receiver are consistent, the number of the received message is encrypted by a private key (private key B1 of the receiver) to obtain a message signature, and the receiver sends the message signature to the sender; if the receiver compares the data abstracts A and B to be inconsistent, the receiver sends the message with the message number receiving failure information to the sender, and the sender is required to resend the message.
Further, the sender receives the message receipt of the receiver, records the message receipt of the receiver, and verifies whether the message is successfully sent, and if the receipt shows that the message is failed to be sent, the sender continues to resend the message; the sender receives the message receipt of the receiver, and if the message receipt is the receipt failed in reception, the sender continues to retransmit the message; if the sender receives the encrypted receipt message, the public key B of the receiver is used for decrypting the receipt message, and if the message number is obtained after decryption, the receiver is indicated to successfully receive the receipt message. If no message number is obtained, the message is continuously retransmitted.
In the application, a private key is used for encrypting the signature at the sender, the data and the signature cannot be tampered after the receiver receives the data, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data and the signature cannot be tampered, and the data and the signature received by the receiver are necessarily sent by the sender as long as the data and the signature are consistent.
In addition, because the receiving party sends the receipt information to the sending party after encrypting the receipt information by using the private key of the receiving party, the sending party confirms that the receiving party receives the information after receiving the receipt information, and the receiving party cannot deny the received information, and the sending party cannot forge the message receipt of the receiving party.
In order to implement the above embodiment, the present application further provides a data transmission consistency checking apparatus.
Fig. 4 is a schematic structural diagram of a data transmission consistency check apparatus according to an embodiment of the present application.
As shown in fig. 4, the data transmission consistency check device 40 includes: an encoding encryption module 410, a sending module 420 and a receiving judgment module 430. Wherein,
the encoding and encrypting module 410 is configured to encode data to be sent by using a message digest algorithm to generate a data digest to be sent, and encrypt the data digest to be sent by using a first private key to generate a data signature to be sent.
The sending module 420 is configured to send the data to be sent and the data signature to be sent to the receiver, so that the receiver decrypts the data signature to be sent by using the first public key to obtain a first received data digest, encodes the received data to be sent by using a message digest algorithm to generate a second received data digest, and determines that the data transmission is consistent if the first received data digest is the same as the second received data digest.
And the receiving judgment module 430 is configured to receive the message signature, decrypt the message signature through the second public key, and determine that the receiving party receives the data if the received message number is the same as the sent message number.
It should be noted that the explanation of the foregoing embodiment of the data transmission consistency check method is also applicable to the data transmission consistency check apparatus of this embodiment, and the implementation principle is similar, and is not described herein again.
The data transmission consistency verification device of the embodiment of the application encodes data to be transmitted through a message digest algorithm to generate a data digest to be transmitted, encrypts the data digest to be transmitted through a first private key to generate a data signature to be transmitted, transmits the data to be transmitted and the data signature to be transmitted to a receiver, so that the receiver decrypts the data signature to be transmitted through a first public key to obtain a first received data digest, encodes the received data to be transmitted through a message digest algorithm to generate a second received data digest, determines that the data are transmitted consistently if the first received data digest is the same as the second received data digest, receives the message signature, decrypts the message signature through the second public key, judges that a received message number is the same as a transmitted message number, and determines that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to implement the above embodiment, the present application further provides a data transmission consistency checking apparatus.
Fig. 5 is a schematic structural diagram of a data transmission consistency check apparatus according to a second embodiment of the present application.
As shown in fig. 5, the data transmission consistency check device 50 includes: an obtaining module 510, a decryption encoding module 520, a determining module 530, an encrypting module 540, and a first transmitting module 550. Wherein,
an obtaining module 510, configured to obtain data to be sent and a signature of the data to be sent.
The decryption coding module 520 is configured to decrypt the to-be-transmitted data signature through the first public key to obtain a first received data digest, and code the received to-be-transmitted data through a message digest algorithm to generate a second received data digest.
A determining module 530, configured to determine that the transmission of the data is consistent if the first received data digest is the same as the second received data digest.
And the encryption module 540 is configured to encrypt the received information number by using a second private key to generate a message signature.
The first sending module 550 is configured to send the message signature to the sender, so that the sender decrypts the message signature through the second public key, and determines that the data received by the receiver is the same as the sent message number if the received message number is determined to be the same as the sent message number.
It should be noted that the explanation of the foregoing embodiment of the data transmission consistency check method is also applicable to the data transmission consistency check apparatus of this embodiment, and the implementation principle is similar, and is not described herein again.
The data transmission consistency verification device of the embodiment of the application decrypts the data signature to be transmitted through the first public key by acquiring the data to be transmitted and the data signature to be transmitted to obtain a first received data abstract, and codes the received data to be transmitted through a message abstract algorithm to generate a second received data abstract; and if the first received data digest is the same as the second received data digest, determining that the data transmission is consistent, encrypting the received information number through a second private key to generate a message signature, sending the message signature to the sender so that the sender decrypts the message signature through a second public key, judging that the received information number is the same as the sent information number, and determining that the receiver receives the data. Therefore, a data signature to be sent is generated by the sender through encryption by the first private key, the data to be sent and the data signature to be sent cannot be tampered by the receiver after the receiver receives the data signature, and the sender cannot deny the sent data, because the receiver does not have the private key of the sender, the data to be sent and the data signature to be sent cannot be sent by the sender, and the accuracy and the efficiency of data transmission consistency check are improved as long as the data and the signature received by the receiver are consistent.
In order to implement the foregoing embodiments, the present application also provides a computer device, including: a processor and a memory. The processor reads the executable program code stored in the memory to run a program corresponding to the executable program code, so as to implement the data transmission consistency check method according to the foregoing embodiments.
FIG. 6 is a block diagram of a computer device provided in an embodiment of the present application, illustrating an exemplary computer device 90 suitable for use in implementing embodiments of the present application. The computer device 90 shown in fig. 6 is only an example, and should not bring any limitation to the function and the scope of use of the embodiments of the present application.
As shown in fig. 6, the computer device 90 is in the form of a general purpose computer device. The components of computer device 90 may include, but are not limited to: one or more processors or processing units 906, a system memory 910, and a bus 908 that couples the various system components (including the system memory 910 and the processing unit 906).
Bus 908 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. These architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, to name a few.
Computer device 90 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 90 and includes both volatile and nonvolatile media, removable and non-removable media.
The system Memory 910 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 911 and/or cache Memory 912. The computer device 90 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 913 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, and commonly referred to as a "hard disk drive"). Although not shown in FIG. 6, a disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk Read Only Memory (CD-ROM), a Digital versatile disk Read Only Memory (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 908 by one or more data media interfaces. System memory 910 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the application.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
Program/utility 914 having a set (at least one) of program modules 9140 may be stored, for example, in system memory 910, such program modules 9140 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination of these examples may comprise an implementation of a network environment. Program modules 9140 generally perform the functions and/or methods of embodiments described herein.
The computer device 90 may also communicate with one or more external devices 10 (e.g., keyboard, pointing device, display 100, etc.), with one or more devices that enable a user to interact with the terminal device 90, and/or with any devices (e.g., network card, modem, etc.) that enable the computer device 90 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 902. Moreover, computer device 90 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public Network such as the Internet) via Network adapter 900. As shown in FIG. 6, network adapter 900 communicates with the other modules of computer device 90 via bus 908. It should be appreciated that although not shown in FIG. 6, other hardware and/or software modules may be used in conjunction with computer device 90, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 906 executes various functional applications and data processing by executing programs stored in the system memory 910, for example, implementing the data transmission consistency check method mentioned in the foregoing embodiments.
In order to implement the foregoing embodiments, the present application further proposes a non-transitory computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the data transmission consistency checking method according to the foregoing embodiments.
In order to implement the foregoing embodiments, the present application also proposes a computer program product, wherein when the instructions in the computer program product are executed by a processor, the data transmission consistency checking method according to the foregoing embodiments is implemented.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing steps of a custom logic function or process, and alternate implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. If implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc. Although embodiments of the present application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present application, and that variations, modifications, substitutions and alterations may be made to the above embodiments by those of ordinary skill in the art within the scope of the present application.