A handshake interaction system

Abstract

The present application discloses a handshake interaction system, the system includes a client and a server, the client includes a central control module, a storage module and a protocol module, the server includes a protocol verification module and a functional module; the central control module is used to write a first handshake request information to the storage module, so that the protocol verification module obtains the first handshake request information written in the storage module; the protocol verification module is used to write a second handshake request information to the storage module, so that the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information; the functional module is used to match the data to be detected with the preset reference data, and establish a communication connection with the client when it is determined that the data to be detected is consistent with the reference data. By configuring the storage module, the data interaction between the client and the server can be carried out in an orderly and accurate manner in a system-level verification environment, thereby improving the operating efficiency, reliability and overall performance of the system.

Description

Technical Field

[0001] The present invention relates to the field of chip information technology, and in particular to a handshake interaction system. Background Art

[0002] In the chip field, the handshake interaction technology between SoC (System on Chip) and VIP (Verification IP) is a key link to ensure the correctness and performance of system design.

[0003] In the interaction process between SoC and VIP, it involves ensuring the order in which SoC and VIP execute instructions alternately. SoC and VIP need to execute instructions in a specific order to ensure the correctness of data and the stability of the system.

[0004] In system-level verification, on the one hand, IP (Intellectual Property core) is embedded inside the SoC, and the built-in control unit controls its behavior by sending instructions. On the other hand, VIP is located outside the SoC, and its behavior needs to be controlled by the test platform.

[0005] However, the above two behaviors represent two different programming perspectives, among which the operation of the SoC control control unit represents the perspective of one programming language, while the operation of the control test platform represents the perspective of another programming language. These two perspectives cannot perceive each other's specific behavior during operation, making the communication process between the SoC and VIP too redundant, resulting in data not being processed in the correct order, low system operation efficiency, and poor reliability and overall performance. Summary of the invention

[0006] The purpose of this application is to provide a handshake interaction system, aiming to provide a solution that can ensure orderly communication between the client and the server, ensure that data is processed in the correct order, improve the operating efficiency of the system, and thus improve the reliability and overall performance of the system.

[0007] To achieve the above objectives: In a first aspect, an embodiment of the present application provides a handshake interaction system, the system comprising a client and a server, the client comprising a central control module, a storage module and a protocol module, the server comprising a protocol verification module and a function module; The central control module is used to write the first handshake request information into the register module, so that the protocol verification module obtains the first handshake request information written into the register module; The protocol verification module is used to write second handshake request information to the storage module, so that the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information; The functional module is used to match the data to be detected with preset reference data, and to establish a communication connection with the client when it is determined that the data to be detected is consistent with the reference data.

[0008] In one embodiment, the client further includes: A first cache module is used to store the data to be detected written by the central control module before the central control module writes the first handshake request information into the storage module, and is used to send the data to be detected to the protocol module before the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information.

[0009] In one embodiment, the server further includes: A second cache module is used to store the benchmark data written by the server after the protocol verification module obtains the first handshake request information written in the storage module, and to send the benchmark data to the functional module after the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information.

[0010] In one embodiment, the central control module is further configured to poll the protocol module to send an end mark when controlling the protocol module to send the preset data to be detected to the protocol verification module according to the second handshake request information.

[0011] In one embodiment, the central control module is further configured to write third handshake request information to the register module after receiving the end flag sent by the protocol module, so that the protocol verification module obtains the third handshake request information written by the central control module to the register module; The protocol verification module is further configured to send the data to be detected to the functional module according to the third handshake request information.

[0012] In a second aspect, an embodiment of the present application further provides another operation mode of a handshake interaction system, wherein the system includes a client and a server, wherein the client includes a central control module, a storage module and a protocol module, and the server includes a protocol verification module; The protocol verification module is used to write the first handshake request information to the storage module, so that the central control module controls the protocol module to enter a preset information receiving mode according to the first handshake request information; The central control module is used to write the second handshake request information to the storage module, so that the protocol verification module obtains the second handshake request information written into the storage module, and the protocol verification module is used to send the preset data to be detected to the protocol module according to the second handshake request information; The central control module is also used to match the data to be detected with preset reference data, and to establish a communication connection with the server when it is determined that the data to be detected is consistent with the reference data.

[0013] In one embodiment, the client further includes: The first cache module is used to receive and store the data to be detected sent by the protocol module after the protocol verification module sends the preset data to be detected to the protocol module according to the second handshake request information.

[0014] In one embodiment, the central control module is further configured to poll the protocol module to send a receiving end flag when the protocol module sends the data to be detected to the first cache module; The first cache module is further configured to send the data to be detected to the central control module after the central control module receives the end mark sent by the protocol module.

[0015] In one embodiment, the server further includes: The second cache module is used to store the to-be-detected data written by the server before the protocol verification module writes the first handshake request information to the storage module.

[0016] In one embodiment, the server further includes: The functional module is used to obtain the data to be detected from the second cache module after the protocol verification module obtains the second handshake request information written into the storage module, and send the data to be detected to the protocol verification module.

[0017] In the present application, by configuring the storage module, it is possible to ensure that in a system-level verification environment, data interaction between the client and the server can be carried out in an orderly and accurate manner, thereby improving the operating efficiency of the system and further improving the reliability and overall performance of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A structural diagram of a handshake interaction system provided by an embodiment of the present invention Figure 1 .

[0019] Figure 2 A structural diagram of a handshake interaction system provided by an embodiment of the present invention Figure 2 .

[0020] Description of reference numerals: 10. Client; 11. Central control module; 12. Storage module; 13. Protocol module; 14. First cache module; 20. Server; 21. Protocol verification module; 22. Functional module; 23. Second cache module. DETAILED DESCRIPTION

[0021] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0022] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0023] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of..." or "when..." or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, “A, B, or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition will occur only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.

[0024] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0025] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0026] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0027] The following is an explanation of the terms that may be involved in this application, as follows: Dummy registers usually refer to registers reserved in certain hardware devices, such as memory (such as NAND flash or NOR Flash), which are used for specific purposes but are not directly involved in data storage or processing.

[0028] DMA (Direct Memory Access) is a technology that allows certain hardware subsystems to directly access system memory without the intervention of the central processing unit (CPU). This technology can significantly increase data transfer rates and reduce the burden on the CPU.

[0029] First embodiment Please refer to Figure 1 , Figure 1 The structure diagram of a handshake interaction system is shown. The system includes a client 10 and a server 20. The client 10 includes a central control module 11, a storage module 12 and a protocol module 13. The server 20 includes a protocol verification module 21 and a functional module 22. Specifically, in this embodiment, the client 10 is a SoC, and the server 20 is a testbench (test platform), which is used to verify and test the simulation environment of the design module, mainly used to generate input signals and simulate the output of the design module, and then test whether the function and performance of the design circuit are consistent with the design expectations. The central control module 11 can be a CPU for managing the configuration and debugging process of IP; the storage module 12 can be a Dummy register (REG) loaded inside the SoC; the protocol module 13 is an IP module; the protocol verification module 21 is a VIP module for processing the data information transmission of VIP; the functional module 22 is a task complex for driving the protocol verification module 21 to perform a series of characteristic behaviors. When the server is the receiver of the data, the functional module 22 is used for result determination, and when the server is the sender of the data, the functional module 22 is used for data encapsulation.

[0030] The central control module 11 is used to write the first handshake request information to the storage module 12, so that the protocol verification module 21 obtains the first handshake request information written in the storage module 12. Specifically, in this embodiment, the central control module 11 first writes the first handshake request information to the storage module 12, and after the storage module 12 receives the first handshake request information, the protocol verification module 21 of the server 20 will automatically obtain the first handshake request information.

[0031] In one implementation, when the protocol verification module 21 receives the first handshake request information, it proves that the handshake is successful, and the thread is transferred from the client 10 to the server 20 .

[0032] Further, the protocol verification module 21 is used to write the second handshake request information to the storage module 12, so that the central control module 11 controls the protocol module 13 to send the preset data to be detected to the protocol verification module 21 according to the second handshake request information. Specifically, in this embodiment, the server 20 controls the protocol verification module 21 to write the second handshake request information to the storage module 12 of the client 10, so that the central control module 11 of the client 10 can control the protocol module 13 to send the preset data to be detected to the protocol verification module 21 of the server 20 according to the second handshake request information. Among them, the specific value of the data to be detected is determined by humans according to the test requirements.

[0033] In one implementation, when the central control module 11 receives the second handshake request information, it proves that the handshake is successful, and the thread is transferred from the server 20 to the client 10 .

[0034] Further, the functional module 22 is used to match the data to be detected with the preset benchmark data, and establish a communication connection with the client 10 when it is determined that the data to be detected is consistent with the benchmark data. Specifically, in the present embodiment, after receiving the data to be detected, the server 20 compares and matches the data to be detected with the preset benchmark data by the functional module 22, and establishes a communication connection with the client 10 when it is determined that the data to be detected is consistent with the benchmark data, and reports the successful establishment of the communication connection with the client 10, and the protocol module verification is passed this time. Otherwise, the communication connection is not established with the client 10, and the failure to establish communication with the client 10 is reported, and the protocol module 13 verification is not passed this time. Among them, the preset benchmark data determines the specific value according to the test requirements and is the same as the data to be detected.

[0035] The present invention sets a dummy register inside the SoC, which is specially used to enable the CPU and VIP to simultaneously sense and change the value of the register when the IP is verified at the system level. This design allows both parties to perform handshake interaction through the change of the register value, thereby achieving precise sequential control.

[0036] Based on the handshake interaction system mentioned above, by establishing a set of behavior rules corresponding to the changes in the Dummy register values, the SoC and the Testbench can perceive each other's behavior. Specifically, each change in the Dummy register marks a handshake between the SoC and the VIP, ensuring the order and synchronization of the behavior, and achieving efficient and orderly interaction between the SoC and the VIP during the IP system-level verification process. This not only optimizes the system-level verification process, but also enhances the overall reliability of the system design.

[0037] In the first embodiment, SoC (client 10) acts as the sender of data, and Testbench (server 20) acts as the receiver and judge of data. By adopting the handshake interaction technology between SoC and VIP, the present invention can ensure that in the system-level verification environment, the interaction between IP and VIP can be executed in sequence and accurately, thereby realizing effective verification of the IP interface protocol.

[0038] Optionally, the client 10 further includes a first cache module 14, which is used to store the data to be detected written by the central control module 11 before the central control module 11 writes the first handshake request information into the storage module 12. Specifically, in this embodiment, the first cache module 14 can be a buffer (RAM), and before the central control module 11 writes the first handshake request information into the storage module 12, the central control module 11 will first write the preset data to be detected into the first cache module 14, and the first cache module 14 is used to receive and store the data to be detected.

[0039] Furthermore, the first cache module 14 is also used to send the data to be detected to the protocol module 13 under the control of the central control module 11 before the central control module 11 controls the protocol module 13 to send the preset data to be detected to the protocol verification module 21 according to the second handshake request information.

[0040] Optionally, the server 20 further includes a second cache module 23, which is used to store the reference data written by the server 20 after the protocol verification module 21 obtains the first handshake request information written into the storage module 12. Specifically, in this embodiment, after the protocol verification module 21 obtains the first handshake request information written into the storage module 12, when the protocol verification module 21 waits for the first handshake request information, it proves that the handshake is successful. At this time, the server 20 writes the preset reference data into the second cache module 23, and the second cache module 23 is used to receive and store the reference data. Among them, the second cache module 23 can also be a cache (RAM).

[0041] Furthermore, the second cache module 23 is also used to send the stored benchmark data to the functional module 22 for result determination after the central control module 11 controls the protocol module 13 to send the preset data to be detected to the protocol verification module 21 according to the second handshake request information. In this way, the data to be detected and the benchmark data are stored in the functional module 22 at the same time.

[0042] Optionally, the central control module 11 is further configured to poll the protocol module 13 for sending an end flag when the central control module 11 controls the protocol module 13 to send the preset data to be detected to the protocol verification module 21 according to the second handshake request information. Specifically, in this embodiment, the central control module 11 polls the protocol module 13 for sending an end flag when the central control module 11 controls the protocol module 13 to send the preset data to be detected to the protocol verification module 21 according to the second handshake request information, so as to achieve the purpose of judging whether the protocol module 13 has completed sending all the data.

[0043] Optionally, the central control module 11 is further configured to write the third handshake request information to the register module 12 after receiving the end mark sent by the protocol module 13, so that the protocol verification module 21 obtains the third handshake request information written in the register module 12. Specifically, in this embodiment, the central control module 11 can determine at the first time that the protocol module 13 has completed the sending of all data by polling the sending end mark, after which the central control module 11 writes the third handshake request information to the register module 12, so that the protocol verification module 21 obtains the third handshake request information written in the register module 12.

[0044] In one implementation, when the protocol verification module 21 waits for the third handshake request information, it proves that the handshake is successful, and the thread is transferred from the client 10 to the server 20 .

[0045] Further, the protocol verification module 21 is also used to send the data to be detected to the functional module 22 according to the third handshake request information. Specifically, in the present embodiment, after receiving the third handshake request information, the protocol verification module 21 automatically sends the data to be detected sent by the protocol module 13 to the functional module 22 for result determination, and the functional module 22 compares and matches the data to be detected with the preset reference data, and when it is determined that the data to be detected is consistent with the reference data, establishes a communication connection with the client 10, reports that the communication connection is established with the client 10, and the verification of the protocol module 13 is passed this time, otherwise it reports that the communication connection cannot be established with the client 10, and the verification of the protocol module 13 is not passed this time.

[0046] Second embodiment Please refer to Figure 2 , Figure 2Another operation mode of a handshake interaction system is shown, the system includes a client 10 and a server 20, the client 10 includes a central control module 11, a storage module 12 and a protocol module 13, and the server 20 includes a protocol verification module 21. Specifically, in this embodiment, the client 10 is a SoC, and the server 20 is a Testbench (test platform), which is used to verify and test the simulation environment of the design module, mainly used to generate input signals and simulate the output of the design module, and then test whether the function and performance of the design circuit are consistent with the design expectations. The central control module 11 can be a CPU for managing the configuration and debugging process of the IP; the storage module 12 can be a Dummy register (REG) loaded inside the SoC; the protocol module 13 is an IP module; the protocol verification module 21 is a VIP module, which is used to receive data packets from the IP module and / or send data packets to the IP module.

[0047] The protocol verification module 21 is used to write the first handshake request information to the register module 12, so that the central control module 11 controls the protocol module 13 to enter the preset information receiving mode according to the first handshake request information. Specifically, in this embodiment, the protocol verification module 21 is used to write the first handshake request information to the register module 12 of the client 10, so that the central control module 11 will send an instruction to the protocol module 13 according to the first handshake information, so that the protocol module 13 prepares for DMA transfer, that is, enters the preset information receiving mode.

[0048] In one implementation, when the central control module 11 receives the first handshake request information, it proves that the handshake is successful, and the thread is transferred from the server 20 to the client 10 .

[0049] Further, the central control module 11 is used to write the second handshake request information to the storage module 12, so that the protocol verification module 21 obtains the second handshake request information written in the storage module 12, and the protocol verification module 21 is used to send the preset data to be detected to the protocol module 13 according to the second handshake request information. Specifically, in this embodiment, after the thread is transferred from the server 20 to the client 10, the central control module 11 writes the second handshake request information to the storage module 12, so that the protocol verification module 21 obtains the second handshake request information written in the storage module 12, so that the protocol verification module 21 will send the preset data to be detected to the protocol module 13 of the client 10 according to the second handshake request information. Among them, the specific value of the data to be detected is determined by humans according to the test requirements.

[0050] In one implementation, when the protocol verification module 21 receives the second handshake request information, it proves that the handshake is successful, and the thread is transferred from the client 10 to the server 20 .

[0051] Furthermore, the central control module 11 is also used to match the data to be detected with the preset reference data, and to establish a communication connection with the server 20 when it is determined that the data to be detected is consistent with the reference data. Specifically, in the present embodiment, the central control module 11 is also used to match the data to be detected sent by the server 20 with the preset reference data, and to establish a communication connection with the server 20 when it is determined that the data to be detected is consistent with the reference data, and to report the establishment of a communication connection with the server 20, and the protocol module 13 verifies this time. Otherwise, no communication connection is established with the server 20, and the failure to establish a communication connection with the server 20 is reported, and the protocol module 13 verifies this time. The preset reference data determines the specific value according to the test requirements and is the same as the data to be detected.

[0052] The present invention sets a dummy register inside the SoC, which is specially used to enable the CPU and VIP to simultaneously sense and change the value of the register when the IP is verified at the system level. This design allows both parties to perform handshake interaction through the change of the register value, thereby achieving precise sequential control.

[0053] Based on the above handshake interaction system, by establishing a set of behavior rules corresponding to the changes in the Dummy register values, SoC and Testbench can perceive each other's behavior. Specifically, each change in the Dummy register marks a handshake between the SoC and the VIP, ensuring the sequentiality and synchronization of the behavior, and realizing the efficient and orderly interaction between the SoC and the VIP during the IP system-level verification process, which not only optimizes the system-level verification process, but also enhances the overall reliability and performance of the client 10 design.

[0054] In the second embodiment, SoC (client 10) acts as the receiver and judge of data, while Testbench (server 20) acts as the sender of data. By adopting the handshake interaction technology between SoC and VIP, the present invention can ensure that in the system-level verification environment, the interaction between IP and VIP can be executed in sequence and accurately, thereby realizing effective verification of the IP interface protocol.

[0055] Optionally, the client 10 further includes: a first cache module 14, which is used to receive and store the data to be detected sent by the protocol module 13 after the protocol verification module 21 sends the preset data to be detected to the protocol module 13 according to the second handshake request information. Specifically, in this embodiment, the first cache module 14 can be a cache (RAM), and after the protocol verification module 21 sends the preset data to be detected to the protocol module 13 according to the second handshake request information, the protocol module 13 sends the received data to be detected to the first cache module 14, and at this time, the first cache module 14 is used to receive and store the data to be detected.

[0056] Optionally, the central control module 11 is further configured to poll the protocol module 13 for a receiving end flag when the protocol module 13 sends the data to be detected to the first cache module 14. Specifically, in this embodiment, in the process of the protocol module 13 sending the data to be detected to the first cache module 14, the central control module 11 is configured to poll the protocol module 13 for a receiving end flag, so as to determine whether the protocol module 13 has received all the data.

[0057] Furthermore, the first cache module 14 is also used to send the data to be detected to the central control module 11 after the central control module 11 receives the end mark sent by the protocol module 13. Specifically, in this embodiment, the central control module 11 can determine at the first time that the protocol module 13 has completed the reception of all data by polling the reception end mark, and thereafter, the central control module 11 obtains all the data to be detected written by the protocol module 13 from the first cache module 14.

[0058] Optionally, the server 20 further includes: a second cache module 23, which is used to store the data to be detected written by the server 20 before the protocol verification module 21 writes the first handshake request information to the storage module 12. Specifically, in this embodiment, before the protocol verification module 21 of the server 20 writes the first handshake request information to the storage module 12 of the client 10, the server 20 writes the preset data to be detected to the second cache module 23, and at this time, the second cache module 23 is used to receive and store the data to be detected.

[0059] Optionally, the server 20 further includes: a functional module 22, which is used to obtain the data to be detected from the second cache module 23 after the protocol verification module 21 obtains the second handshake request information written into the storage module 12, and sends the data to be detected to the protocol verification module 21. Specifically, in this embodiment, after the central control module 11 enables the protocol verification module 21 to obtain the second handshake request information written into the storage module 12, the functional module 22 is used to obtain the data to be detected from the second cache module 23, and send all the data to be detected to the protocol verification module 21, so that the protocol verification module 21 encapsulates the data to be detected in a specific form and sends it to the protocol module 13 of the client 10.

[0060] In the above-mentioned first embodiment and second embodiment, the register module 12 is a Dummy register, which is a small storage area for quickly accessing data, usually used to store instructions, data, addresses, etc., and can significantly reduce the number of times the CPU accesses the main memory and improve the processing speed.

[0061] Furthermore, the first handshake request information, the second handshake request information, and the third handshake request information are behavior characterization values ​​(wait values) that the recipient of the request information is waiting for, which generally refers to a specific state or signal used to indicate that a certain operation (such as data transmission) has been completed. Exemplarily, during the data transmission process, the CPU sets a flag bit or register value to indicate the "wait" state. For the recipient of the data, the wait value will be checked after receiving the data. If the wait value meets expectations (for example, a specific flag bit is set), it means that the data has been successfully received, that is, the handshake is successful.

[0062] Furthermore, if the data receiver does not detect the expected wait value, it means that the data transmission has failed or there is an error. At this time, the system may need to perform error handling procedures, such as retrying transmission, reporting errors, etc.

[0063] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0064] In this document, the terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion of elements other than those listed and may also include additional elements not expressly listed.

[0065] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A handshake interaction system, characterized in that: The system includes a client and a server, wherein the client includes a central control module, a storage module and a protocol module, and the server includes a protocol verification module and a function module; The central control module is used to write the first handshake request information into the register module, so that the protocol verification module obtains the first handshake request information written into the register module; The protocol verification module is used to write second handshake request information to the storage module, so that the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information; The functional module is used to match the data to be detected with preset reference data, and to establish a communication connection with the client when it is determined that the data to be detected is consistent with the reference data.

2. The system according to claim 1, characterized in that The client also includes: A first cache module is used to store the data to be detected written by the central control module before the central control module writes the first handshake request information into the storage module, and is used to send the data to be detected to the protocol module before the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information.

3. The system according to claim 1, characterized in that The server also includes: A second cache module is used to store the benchmark data written by the server after the protocol verification module obtains the first handshake request information written in the storage module, and to send the benchmark data to the functional module after the central control module controls the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information.

4. The system according to claim 1, characterized in that The central control module is further configured to poll the protocol module to send an end mark when controlling the protocol module to send preset data to be detected to the protocol verification module according to the second handshake request information.

5. The system according to claim 4, characterized in that The central control module is further configured to write the third handshake request information to the register module after receiving the end mark sent by the protocol module, so that the protocol verification module obtains the third handshake request information written by the central control module into the register module; The protocol verification module is further configured to send the data to be detected to the functional module according to the third handshake request information.

6. A handshake interaction system, characterized in that: The system includes a client and a server, wherein the client includes a central control module, a storage module and a protocol module, and the server includes a protocol verification module; The protocol verification module is used to write the first handshake request information to the storage module, so that the central control module controls the protocol module to enter a preset information receiving mode according to the first handshake request information; The central control module is used to write the second handshake request information to the storage module, so that the protocol verification module obtains the second handshake request information written into the storage module, and the protocol verification module is used to send the preset data to be detected to the protocol module according to the second handshake request information; The central control module is also used to match the data to be detected with preset reference data, and to establish a communication connection with the server when it is determined that the data to be detected is consistent with the reference data.

7. The system according to claim 6, characterized in that The client also includes: The first cache module is used to receive and store the data to be detected sent by the protocol module after the protocol verification module sends the preset data to be detected to the protocol module according to the second handshake request information.

8. The system according to claim 7, characterized in that The central control module is further configured to poll the protocol module for a receiving end flag when the protocol module sends the data to be detected to the first cache module; The first cache module is further configured to send the data to be detected to the central control module after the central control module receives the end mark sent by the protocol module.

9. The system according to claim 6, characterized in that The server also includes: The second cache module is used to store the to-be-detected data written by the server before the protocol verification module writes the first handshake request information to the storage module.

10. The system according to claim 9, characterized in that The server also includes: The functional module is used to obtain the data to be detected from the second cache module after the protocol verification module obtains the second handshake request information written into the storage module, and send the data to be detected to the protocol verification module.

Images