Cooperation debugging tool, cooperation debugging method, control device and readable storage medium

Abstract

The present application relates to the technical field of system joint debugging, and specifically provides a joint debugging tool, a joint debugging method, a control device and a readable storage medium, aiming to solve the problem of how to improve the efficiency of signature joint debugging process while reducing the dependence on the technical language mastered by the interfacing personnel. To this end, the present application checks whether the input parameters to be verified meet the signature requirements through the input parameter checking module in the joint debugging tool, checks whether the public key and the private key meet the preset format requirements through the public key and private key checking module, generates spliced data and signature through the spliced data and signature generation module, compares the generated spliced data with the request data through the spliced data comparison module, compares the generated signature with the corresponding signature in the joint debugging process through the signature comparison module, can improve the efficiency of the joint debugging process, and reduce the dependence on the technical language mastered by the interfacing personnel.

Description

Technical Field

[0001] This invention relates to the field of system integration and debugging technology, and specifically provides an integration and debugging tool, an integration and debugging method, a control device, and a readable storage medium. Background Technology

[0002] A joint debugging environment is an environment provided by developers, testers, and integraters to debug and verify the functionality of business products. After the joint debugging environment is deployed, specific business functions are often encapsulated into OpenAPIs for use by users or merchants. OpenAPI services are characterized by atomicity. A piece of business functionality in the joint debugging environment, that is, a certain use case of a user or merchant, often requires multiple OpenAPI services to be called sequentially and cyclically to be implemented.

[0003] When integrating with user or merchant interfaces, ensuring the security of interface interactions requires signing and verifying HTTP messages in JSON format. The languages ​​used by these users or merchants include Java, PHP, .NET, and even older versions of Delphi. Because the technical skills and mastery of signature processing technologies vary among users and merchants, familiarity with these various languages ​​is essential for quickly resolving any issues encountered. Technically, this presents a challenge.

[0004] Chinese patent publication number CN106406826A, entitled "A Method and Apparatus for Creating and Debugging Joint Components," discloses a method that manually judges the correctness of generated messages through an approval process and determines whether there are any problems with the signature by generating a signature from the input message. However, message errors are only one of the possible causes of problems with signature debugging, and this existing technology cannot fundamentally solve the problem of signature errors.

[0005] Accordingly, a new joint debugging solution is needed in this field to address the above problems. Summary of the Invention

[0006] To overcome the above-mentioned shortcomings, this invention is proposed to provide a solution, or at least a partial solution, to how to improve the efficiency of solving technical problems in the signature integration process while reducing the reliance on the technical language of the personnel involved.

[0007] In a first aspect, the present invention provides a joint debugging tool, the tool comprising:

[0008] The input parameter checking module is used to check whether the input parameters to be verified meet the signature requirements;

[0009] The public and private key checking module is used to check whether the public and / or private keys used in the integration process meet the preset format requirements.

[0010] The data concatenation and signature generation module is used to generate concatenated data and signatures based on input parameters and private keys;

[0011] The spliced ​​data comparison module is used to compare the generated spliced ​​data with the requested data;

[0012] The signature comparison module is used to compare the generated signature with the corresponding signature during the integration testing process.

[0013] In one technical solution of the aforementioned debugging tool, the input parameter checking module includes a first verification button and a parameter input box, and the input parameter detection module is further configured as follows:

[0014] In response to a first verification command input based on the first verification button, the input parameters to be verified in the parameter input box are detected to determine whether the input parameters meet the signature requirements.

[0015] In one technical solution of the aforementioned debugging tool, the input parameter detection module further includes a first format correction button, and the input parameter detection module is further configured as follows:

[0016] In response to a first format correction instruction input based on the first format correction key input, the format of the input parameter to be verified in the parameter input box is corrected.

[0017] In one technical solution of the aforementioned integration tool, the public-private key checking module includes a second verification button, a private key input box, and a public key input box. The public-private key checking module is further configured as follows:

[0018] In response to the second verification command input based on the second verification button, check whether the public key in the public key input box and the private key in the private key input box are a pair.

[0019] In one technical solution of the aforementioned integration tool, the public-private key checking module includes a first format checking button and / or a second format checking button, and the public-private key checking module is further configured as follows:

[0020] In response to a first format check instruction based on the first format check key input, the format of the private key in the private key input box is checked to see if it is correct; and / or,

[0021] In response to a second format check instruction based on the second format check key input, the format of the public key in the public key input box is checked to see if it is correct; and / or,

[0022] The public-private key checking module includes a second format correction button and / or a third format correction button, and the public-private key checking module is further configured to:

[0023] In response to a second format correction instruction input based on the second format correction key input, the format of the private key in the private key input box is corrected; and / or,

[0024] In response to a third format correction instruction based on the third format correction key input, the format of the public key in the public key input box is corrected; and / or,

[0025] The public key / private key checking module includes a first data clear button, and the public key / private key checking module is further configured to:

[0026] In response to a first data clearing command input based on the first data clearing button, the data in the public key input box and the private key input box are cleared.

[0027] In one technical solution of the aforementioned joint debugging tool, the data splicing and signature generation module includes a data generation button; the data splicing and signature generation module is further configured as follows:

[0028] In response to a data generation instruction based on the data generated by key input, concatenated data and a signature are generated according to the input parameters and the private key.

[0029] In one technical solution of the aforementioned joint debugging tool, the splicing data generation module further includes a second data clearing button, and the splicing data and signature generation module is further configured as follows:

[0030] In response to a second data clearing command input based on the second data clearing button, the generated concatenated data and signature are cleared.

[0031] In one technical solution of the aforementioned joint debugging tool, the spliced ​​data comparison module includes a third verification button and a request data input box, and the spliced ​​data comparison module is further configured as follows:

[0032] In response to the third verification instruction input based on the third verification button, the generated concatenated data is compared with the request data in the request data input box.

[0033] In one technical solution of the aforementioned joint debugging tool, the spliced ​​data comparison module further includes a third data clear button, and the spliced ​​data comparison module is further configured as follows:

[0034] In response to the third data clearing instruction input based on the third data clearing button, the request data in the request data input box is cleared.

[0035] In one technical solution of the aforementioned integration tool, the signature comparison module includes a fourth verification button and a program signature input box, and the signature comparison module is further configured as follows:

[0036] In response to the fourth verification instruction input based on the fourth verification button, the generated signature is compared with the corresponding signature in the program signature input box during the joint debugging process.

[0037] In one technical solution of the aforementioned joint debugging tool, the signature comparison module further includes a fourth data clear button, and the signature comparison module is further configured as follows:

[0038] In response to the fourth data clearing instruction input based on the fourth data clearing button, the signature in the program in the program signature input box is cleared.

[0039] In a second aspect, the present invention provides a joint debugging method, the method being based on the joint debugging tool according to any one of claims 1 to 11, the method comprising:

[0040] The input parameter checking module checks whether the input parameters to be verified meet the signature requirements.

[0041] When the input parameters meet the signature requirements, the public key and / or private key checking module checks whether the public key and / or private key in the joint debugging process meet the preset format requirements.

[0042] When the public key and / or private key meet the format requirements, the concatenated data and signature are generated by the concatenated data and signature generation module according to the input parameters and the private key;

[0043] The spliced ​​data comparison module compares the generated spliced ​​data with the requested data to obtain a first comparison result.

[0044] The generated signature is compared with the corresponding signature during the joint debugging process using the signature comparison module to obtain a second comparison result.

[0045] Based on the first comparison result and / or the second comparison result, the joint debugging process between the execution end and the application end is realized.

[0046] In one technical solution of the above-mentioned joint debugging method, the step of implementing the joint debugging process between the execution end and the application end based on the first comparison result and / or the second comparison result includes:

[0047] When the first comparison result is that the comparison fails, the reason for the comparison failure is obtained based on the first comparison result;

[0048] When the second comparison result is that the comparison fails, the joint debugging process is implemented according to the public key and / or private key in the joint debugging process.

[0049] In one technical solution of the above-mentioned joint debugging method, the step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes:

[0050] When the input parameter to be verified is the parameter of the verification signature of the execution end, the public key private key checking module checks whether the private key and the public key of the application end are a pair;

[0051] If so, check the correctness of the signature algorithm to implement the aforementioned integration testing process;

[0052] If not, regenerate the public and private keys of the application to implement the joint debugging process.

[0053] In one technical solution of the above-mentioned joint debugging method, the step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes:

[0054] When the input parameter to be verified is the concatenated return parameter received by the application, the correct public key is queried from the execution end, and the correctness of the signature algorithm is checked to realize the joint debugging process.

[0055] In one technical solution of the above-mentioned joint debugging method, the step of checking whether the input parameters to be verified meet the signature requirements through the input parameter checking module includes:

[0056] The input parameters are checked using the input parameter checking module.

[0057] If the check passes, the input parameters are deemed to meet the signature requirements;

[0058] If the check fails, a first format correction command is input via the first format correction button of the input parameter detection module to correct the format of the input parameters so that they meet the signature requirements; and / or,

[0059] The step of checking whether the public key and / or private key conforms to preset format requirements through the public key and / or private key checking module includes:

[0060] The public key and / or the private key are checked using the public key and private key checking module.

[0061] If the public key and / or the private key conform to the format requirements, execute the step of "generating concatenated data and a signature based on the input parameters and the private key through the concatenated data and signature generation module";

[0062] If the public key and / or the private key does not conform to the format requirements, the format of the public key and / or the private key is corrected by using the second format correction button and / or the third format correction button of the public key and private key checking module to obtain a public key and / or private key that conforms to the format requirements.

[0063] In a third aspect, a control device is provided, comprising at least one processor and at least one storage device, the storage device being adapted to store a plurality of program codes, the program codes being adapted to be loaded and run by the processor to perform the joint debugging method described in any of the above-described joint debugging methods.

[0064] In a fourth aspect, a computer-readable storage medium is provided, wherein a plurality of program codes are stored therein, the program codes being adapted to be loaded and run by a processor to perform the joint debugging method described in any of the above-described joint debugging methods.

[0065] The above-described technical solutions of the present invention have at least one or more of the following beneficial effects:

[0066] In implementing the technical solution of this invention, the inventors designed an input parameter checking module, a public / private key checking module, a data concatenation and signature generation module, a concatenated data comparison module, and a signature comparison module to address all possible points of potential problems during the signature integration process. This invention uses the input parameter checking module in the integration tool to check whether the input parameters to be verified meet the signature requirements; the public / private key checking module to check whether the public and private keys meet the preset format requirements; the data concatenation and signature generation module to generate concatenated data and a signature from the input parameters and private key; the data concatenation comparison module to compare the generated concatenated data with the request data; and the signature comparison module to compare the generated signature with the corresponding signature during the integration process. Through this configuration, this invention can effectively troubleshoot problems during the integration process using the integration tool, improving the efficiency of resolving technical issues during integration. Furthermore, using the integration tool of this invention for problem troubleshooting does not require the personnel involved to possess the corresponding technical language, reducing reliance on such personnel. Furthermore, the inventors discovered that problems in the content checked by subsequent modules are often not solely due to errors in their own content, but rather stem from errors in the content checked by preceding modules. For example, if errors in the public or private key formats are not detected and corrected before being directly used in the data concatenation and signature generation modules, the private key format error will be incorporated into the concatenation process, making it impossible to pinpoint the exact source of the problem. Therefore, the use of these modules requires an inherent execution logic order. In a preferred embodiment, when the preceding module is active (editable), the subsequent module is disabled (uneditable, e.g., grayscale display). Only after the preceding module has generated a check result will the next module become active. This approach reduces the likelihood of errors during integration testing, making it particularly user-friendly for beginners.

[0067] Solution 1. A joint debugging tool, characterized in that the tool comprises:

[0068] The input parameter checking module is used to check whether the input parameters to be verified meet the signature requirements;

[0069] The public and private key checking module is used to check whether the public and / or private keys used in the integration process meet the preset format requirements.

[0070] The data concatenation and signature generation module is used to generate concatenated data and signatures based on input parameters and private keys;

[0071] The spliced ​​data comparison module is used to compare the generated spliced ​​data with the requested data;

[0072] The signature comparison module is used to compare the generated signature with the corresponding signature during the integration testing process.

[0073] Solution 2. The debugging tool according to Solution 1, characterized in that the input parameter checking module includes a first verification button and a parameter input box, and the input parameter detection module is further configured as follows:

[0074] In response to a first verification command input based on the first verification button, the input parameters to be verified in the parameter input box are detected to determine whether the input parameters meet the signature requirements.

[0075] Option 3. The joint debugging tool according to Option 2, characterized in that,

[0076] The input parameter detection module further includes a first format correction button, and the input parameter detection module is further configured to:

[0077] In response to a first format correction instruction input based on the first format correction key input, the format of the input parameter to be verified in the parameter input box is corrected.

[0078] Solution 4. The integration tool according to Solution 1, characterized in that the public key / private key checking module includes a second verification button, a private key input box, and a public key input box, and the public key / private key checking module is further configured as follows:

[0079] In response to the second verification command input based on the second verification button, check whether the public key in the public key input box and the private key in the private key input box are a pair.

[0080] Solution 5. The integration tool according to Solution 4, characterized in that the public key / private key checking module includes a first format checking button and / or a second format checking button, and the public key / private key checking module is further configured as follows:

[0081] In response to a first format check instruction based on the first format check key input, the format of the private key in the private key input box is checked to see if it is correct; and / or,

[0082] In response to a second format check instruction based on the second format check key input, the format of the public key in the public key input box is checked to see if it is correct; and / or,

[0083] The public-private key checking module includes a second format correction button and / or a third format correction button, and the public-private key checking module is further configured to:

[0084] In response to a second format correction instruction input based on the second format correction key input, the format of the private key in the private key input box is corrected; and / or,

[0085] In response to a third format correction instruction based on the third format correction key input, the format of the public key in the public key input box is corrected; and / or,

[0086] The public key / private key checking module includes a first data clear button, and the public key / private key checking module is further configured to:

[0087] In response to a first data clearing command input based on the first data clearing button, the data in the public key input box and the private key input box are cleared.

[0088] Solution 6. The joint debugging tool according to Solution 1, characterized in that the data splicing and signature generation module includes a data generation button; the data splicing and signature generation module is further configured as follows:

[0089] In response to a data generation instruction based on the data generated by key input, concatenated data and a signature are generated according to the input parameters and the private key.

[0090] Solution 7. The joint debugging tool according to Solution 6, characterized in that the splicing data generation module further includes a second data clearing button, and the splicing data and signature generation module is further configured as follows:

[0091] In response to a second data clearing command input based on the second data clearing button, the generated concatenated data and signature are cleared.

[0092] Solution 8. The joint debugging tool according to Solution 1, characterized in that the spliced ​​data comparison module includes a third verification button and a request data input box, and the spliced ​​data comparison module is further configured as follows:

[0093] In response to the third verification instruction input based on the third verification button, the generated concatenated data is compared with the request data in the request data input box.

[0094] Solution 9. The joint debugging tool according to Solution 8, characterized in that the spliced ​​data comparison module further includes a third data clear button, and the spliced ​​data comparison module is further configured as follows:

[0095] In response to the third data clearing instruction input based on the third data clearing button, the request data in the request data input box is cleared.

[0096] Solution 10. The integration tool according to Solution 1, characterized in that the signature comparison module includes a fourth verification button and a program signature input box, and the signature comparison module is further configured as follows:

[0097] In response to the fourth verification instruction input based on the fourth verification button, the generated signature is compared with the corresponding signature in the program signature input box during the joint debugging process.

[0098] Solution 11. The joint debugging tool according to Solution 10, characterized in that the signature comparison module further includes a fourth data clear button, and the signature comparison module is further configured as follows:

[0099] In response to the fourth data clearing instruction input based on the fourth data clearing button, the signature in the program in the program signature input box is cleared.

[0100] Scheme 12. A joint debugging method, characterized in that the method is based on the joint debugging tool of any one of Schemes 1 to 11, the method comprising:

[0101] The input parameter checking module checks whether the input parameters to be verified meet the signature requirements.

[0102] When the input parameters meet the signature requirements, the public key and / or private key checking module checks whether the public key and / or private key in the joint debugging process meet the preset format requirements.

[0103] When the public key and / or private key meet the format requirements, the concatenated data and signature are generated by the concatenated data and signature generation module according to the input parameters and the private key;

[0104] The spliced ​​data comparison module compares the generated spliced ​​data with the requested data to obtain a first comparison result.

[0105] The generated signature is compared with the corresponding signature during the joint debugging process using the signature comparison module to obtain a second comparison result.

[0106] Based on the first comparison result and / or the second comparison result, the joint debugging process between the execution end and the application end is realized.

[0107] Scheme 13. The joint debugging method according to Scheme 12, characterized in that,

[0108] The process of implementing joint debugging between the execution end and the application end based on the first comparison result and / or the second comparison result includes:

[0109] When the first comparison result is that the comparison fails, the reason for the comparison failure is obtained based on the first comparison result;

[0110] When the second comparison result is that the comparison fails, the joint debugging process is implemented according to the public key and / or private key in the joint debugging process.

[0111] Scheme 14. The joint debugging method according to Scheme 13, characterized in that,

[0112] The step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes:

[0113] When the input parameter to be verified is the parameter of the verification signature of the execution end, the public key private key checking module checks whether the private key and the public key of the application end are a pair;

[0114] If so, check the correctness of the signature algorithm to implement the aforementioned integration testing process;

[0115] If not, regenerate the public and private keys of the application to implement the joint debugging process.

[0116] Scheme 15. The joint debugging method according to Scheme 13, characterized in that,

[0117] The step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes:

[0118] When the input parameter to be verified is the concatenated return parameter received by the application, the correct public key is queried from the execution end, and the correctness of the signature algorithm is checked to realize the joint debugging process.

[0119] Scheme 16. The joint debugging method according to Scheme 12, characterized in that,

[0120] The step of checking whether the input parameters to be verified meet the signature requirements through the input parameter checking module includes:

[0121] The input parameters are checked using the input parameter checking module.

[0122] If the check passes, the input parameters are deemed to meet the signature requirements;

[0123] If the check fails, a first format correction command is input via the first format correction button of the input parameter detection module to correct the format of the input parameters so that they meet the signature requirements; and / or,

[0124] The step of checking whether the public key and / or private key conforms to preset format requirements through the public key and / or private key checking module includes:

[0125] The public key and / or the private key are checked using the public key and private key checking module.

[0126] If the public key and / or the private key conform to the format requirements, execute the step of "generating concatenated data and a signature based on the input parameters and the private key through the concatenated data and signature generation module";

[0127] If the public key and / or the private key does not conform to the format requirements, the format of the public key and / or the private key is corrected by using the second format correction button and / or the third format correction button of the public key and private key checking module to obtain a public key and / or private key that conforms to the format requirements.

[0128] Scheme 17. A control device comprising at least one processor and at least one storage device, the storage device being adapted to store a plurality of program codes, characterized in that the program codes are adapted to be loaded and run by the processor to perform the joint debugging method described in any one of Schemes 12 to 16.

[0129] Scheme 18. A computer-readable storage medium storing a plurality of program codes, characterized in that the program codes are adapted to be loaded and run by a processor to perform the integration method described in any one of Schemes 12 to 16. Attached Figure Description

[0130] The disclosure of this invention will become more readily understood with reference to the accompanying drawings. It will be readily understood by those skilled in the art that these drawings are for illustrative purposes only and are not intended to limit the scope of protection of this invention. Furthermore, similar numbers in the drawings are used to denote similar components, wherein:

[0131] Figure 1 This is a schematic diagram of the main components of a joint debugging tool according to an embodiment of the present invention;

[0132] Figure 2 This is a schematic flowchart of the main steps of a joint debugging method according to an embodiment of the present invention;

[0133] Figure 3 This is a flowchart illustrating the main steps of a joint debugging method as an example in the prior art;

[0134] Figure 4 This is a schematic diagram of the main components of a joint debugging tool according to one embodiment of the present invention.

[0135] Figure 5 This is a schematic diagram illustrating the process of an application input parameter checking module checking input parameters according to an embodiment of the present invention.

[0136] Figure 6 This is a schematic diagram illustrating the process of using a public-private key checking module to check public and private keys according to an embodiment of the present invention.

[0137] Figure 7 This is a schematic diagram illustrating the process of generating concatenated data and a signature using an application concatenated data and signature generation module according to an embodiment of the present invention;

[0138] Figure 8 This is a schematic diagram illustrating the process of comparing generated spliced ​​data and requested data using an application spliced ​​data comparison module according to an embodiment of the present invention;

[0139] Figure 9 This is a schematic diagram illustrating the process of comparing the generated signature with the corresponding signature during the joint debugging process using an application signature comparison module, according to an embodiment of the present invention.

[0140] List of reference numerals in the attached diagram:

[0141] 11: Input parameter checking module; 12: Public key / private key checking module; 13: Data concatenation and signature generation module; 14: Concatenated data comparison module; 15: Signature comparison module. Detailed Implementation

[0142] Some embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0143] In the description of this invention, "module" and "processor" can include hardware, software, or a combination of both. A module can include hardware circuitry, various suitable sensors, communication ports, memory, and may also include software components, such as program code, or a combination of software and hardware. A processor can be a central processing unit, microprocessor, image processor, digital signal processor, or any other suitable processor. The processor has data and / or signal processing capabilities. The processor can be implemented in software, in hardware, or a combination of both. Non-transitory computer-readable storage media includes any suitable medium capable of storing program code, such as magnetic disks, hard disks, optical disks, flash memory, read-only memory, random access memory, etc. The term "A and / or B" means all possible combinations of A and B, such as only A, only B, or A and B. The terms "at least one A or B" or "at least one of A and B" have a similar meaning to "A and / or B" and can include only A, only B, or A and B. The singular terms "a" or "this" can also include plural forms.

[0144] For current traditional joint debugging methods, please refer to the appendix. Figure 3 , Figure 3 This is a flowchart illustrating the main steps of a joint debugging method in an example of existing technology. In a payment scenario, Company B is a third-party payment company (i.e., the execution end), and Company A is its merchant (i.e., the application end). Figure 3 As shown,

[0145] Q1: Company A's R&D personnel input the parameters (i.e., the message) intended for Company B to verify the signature using a programming tool, as shown below:

[0146] "orgId":"66690416","reqData":{"ordNo":"2018031601582703488262843965","mno":"865190513665078"},

[0147] "reqId":"f67271bedd2041e79ed3754dcc5319db",

[0148] "signType":"RSA",

[0149] "timestamp":"201803162345",

[0150] "version":"1.0"

[0151] }

[0152] Q2: Company A's R&D personnel assemble and sort parameters in a programming tool according to their own assembly and sorting rules to generate the target message, as shown below:

[0153] orgId=66690416&reqData={"ordNo":"2018031601582703488262843965","mno":"86519051366507 8"}&reqId=f67271bedd2041e79ed3754dcc5319db&signType=RSA×tamp=201803162345&version=1.0

[0154] Q3 and Q4: Company A's R&D personnel use Company A's private key, which they know, to sign (add signature) the target message. Company A's private key is given below:

[0155] MIIEvwIBADANBgkqhkiG9w0BAQEFAASCBKkwggSlAgEAAoIBAQ DE5HVmh0c5E4Z8tLHQn3Cxf2EMtt7qLnN6KJnS8g4G08jGtzaGcRGzekuNJwTher6aY / q48 / eYpy5k5dQyDQ3EYjJQzsYZsF7d+KORQaH3etib2sG7TclFNfkB0GRwkZVv7j8JZ p1+f9UOXObxzL6yFmnLJ4RLUnlknX6TkNCVUi16uqqzLRiZ6UxIgeaf3sy6eSC2sRfeU i9kN5NXRtCz8v0GwjPCHDIorFuXoSEJEskpSxgVRqpfKYE1FVIgN / 8zSHsbQgh+lLGx I2p3LU / oGsVqap / iLpgg0Bro0Xoli4Tero9HglMa+WIWDqTefrENzATPLdULYiStTVKDpvARAgMBAAECggEBALo4njVv41Q / fGa8fKWl929Z28+rsqBpeLzkY8DZQZ0BeBdCt+ZmUOig1Y5Whk5Ayr+5qix+SwLttHqnyY / hOtEwUwiM2V74qnFlNkcvfWJVpUObnrpp8uBsEOy / ThAOEfoAq0xX6sP3YeqowaGXFhHYEw2bfYvEIJ6iO1KUmENxAWizM8W / fmtxB2YHnD / 6nWj2k9U64CsQ02XAHBH / lcsJc5Avfmf1tAu31K1J3eQRv84ocNFlX9uJJ o1sLVcRZjdYPaQ7PupkUxPUokSsx4aOOqFvPt / 4DwazOPPt2rpfwgcAJnvd+bSDlvC3hc kuuw0WzzeVg4uc / S+ZoZxtPKUCgYEA8NQiO56Lz9t5 / PIbu5MoLvaaVU9huxjnZoFvh9lXe2foS4bhU+xv1kZJyTdTMIlCIHqmEiLKt9q08WQYkNLMDngnjvZwuCpkWZQ5q1l5fwlUKhqWsRXobco85ZBA9LejQHdtnCuydwCWWIgw5OmOuSgZr6hjuLWpZQ4Rnxt8NP8CgYEA0UvC2fyVeLkEuyGOKHlmWgSQKvgaEzg8dMvJlgzHD+bUiKWRn / dKkWlzMYsAqnM4T5KyGEoStX4P3wpWiv7hxNvUC8xuaUvg06ZZbSND7rmOlg9QKsCyqD5BoijFyaLHJ7NbaKQY0psqBkT / hvv13oPLd3ub630Kn4NAxHngiu8CgYBgNf9vHgnxAle bzAV0THfzOyWxC0OaAXsAopkyBoxCiuJsuffvFTggvHfh4S5k55D5dMY / 3JJsHP3Iqhp+URigdzQmkyG5 EYaBmwvm / pnhPJLZN0IYgQ4YPoFRnO22Vl7r9Epf570meZ+WwuH1sbEJG5IXcQhV1I1WB+bWT56xdQKBgQ CoHKORdsoU4wBC00wdhI3K5nlqmkhPgc9FvV7ZkL / gLPgwHlWfWQHjVQE7HTzWrJ / hgqJc0jq+31gePm6P TPXJqw1iwL07BMC9IJQaDsaFHTTDod8xyAB5FTCg8QEV2hL / 95gHsC9kE1ApIwjgwseWCOTIv1fZSmHbCJ Fgf8j1rwKBgQCFU2Sq3WwM8YM8F1XD9UPOAS77ZjX5k1tSnniOz+F+tds / jnpIYTvH Oy6fX+LQC4HNpHc9bMUmQ5WUmw12EFZnleopLxe7aX7ecuh8choSRszRSx0P2hsxP P0C5mL6geIgRoGz579QYhwreMDNFJbSr1IUqdUlutaMZlPsOTaTuQ==

[0156] Q5: The signed message is sent to Company B's interface. After being assembled, Company B's R&D personnel verify the signature using the public key paired with the aforementioned private key. The public key is shown below:

[0157] MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxOR1Zo dHOROGfLSx0J9wsX9hDLbe6i5zeiiZ0vIOBtPIxrc2hnERs3pLjScE4Xq+mmP6uPP3mK cuZOXUMg0NxGIyUM7GGbBe3fijkUGh93rYm9rBu03JRTX5AdBkcJGVb+4 / CWadfn / VDlzm8cy+shZpyyeES1J5ZJ1+k5DQlVIterqqsy0YmelMSIHmn97MunkgtrEX3lIvZDeT V0bQs / L9BsIzwhwyKKxbl6EhCRLJKUsYFUaqXymBNRVSIDf / M0h7G0IIfpSxsSNqdy1P6BrFamqf4i6YINAa6NF6JYuE3q6PR4JTGvliFg6k3n6xDcwEzy3VC2IkrU1Sg6bwEQIDAQAB

[0158] When Company B's interface returns a feedback result to Company A's interface, there is also a process where Company B adds the signature and Company A verifies the signature. Figure 3 The latter half is shown.

[0159] During the joint debugging process of Company A and Company B's interface for signature verification, since the interface standard was defined by Company B, if an error occurs during the debugging process, Company B will usually only encounter a problem with the public key provided by Company A in Q5 (the public key is a public-private key pair generated by Company B; Company B keeps the private key for signature verification and sends the public key to Company B for signature verification). However, Company A may have problems in multiple places throughout the process, such as parameter (message) format not conforming to signature requirements, incorrect concatenation syntax, incorrect private key format, the public key sent to Company B and the private key used for signature verification not being a pair, etc.

[0160] The process of troubleshooting these issues one by one is not only time-consuming and inefficient, but also requires the personnel involved to be proficient in the various technical terms involved, which presents technical challenges. Accordingly, a new method for joint debugging is needed in this field to solve these problems.

[0161] See appendix Figure 1 , Figure 1 This is a schematic diagram of the main components of a debugging tool according to an embodiment of the present invention, which can be deployed online for use by Company A mentioned above. Figure 1 As shown, the integration tool mainly includes an input parameter checking module 11, a public key and private key checking module 12, a data splicing and signature generation module 13, a data splicing comparison module 14, and a signature comparison module 15.

[0162] In this embodiment, the input parameter checking module 11 can be used to check whether the input parameters to be verified meet the signature requirements. The public key / private key checking module 12 can be used to check whether the public key and / or private key during the integration process meet the preset format requirements. The concatenated data and signature generation module 13 can be used to generate concatenated data and a signature based on the input parameters and private key. The concatenated data comparison module 14 can be used to compare the generated concatenated data with the request data. The signature comparison module 15 can be used to compare the generated signature with the corresponding signature during the integration process.

[0163] Through the above settings, this embodiment of the invention uses an input parameter checking module in the integration tool to check whether the input parameters to be verified meet the signature requirements, a public key / private key checking module to check whether the public and private keys meet the preset format requirements, a data concatenation and signature generation module to generate concatenated data and a signature from the input parameters and private key, a data concatenation comparison module to compare the generated concatenated data with the request data, and a signature comparison module to compare the generated signature with the corresponding signature during the integration process. This embodiment of the invention can effectively troubleshoot problems during the integration process using the integration tool, improving the efficiency of resolving technical issues during integration. Furthermore, using this integration tool for problem troubleshooting does not require the personnel involved to possess the corresponding technical language, reducing reliance on such personnel.

[0164] The following is a reference to the appendix. Figure 4 The integration testing tool of the present invention will be further described below. Among them, Figure 4 This is a schematic diagram of the main components of a debugging tool according to one embodiment of the present invention.

[0165] In one embodiment of the present invention, the input parameter checking module may include a first verification button and a parameter input box. The input parameter detection module may be further configured to: in response to a first verification instruction input based on the first verification button, detect the input parameter to be verified in the parameter input box to determine whether the input parameter meets the signature requirements.

[0166] In this embodiment, such as Figure 4 As shown, the input parameter checking module (M1) includes a first verification button (format JSON button) and a parameter input box. After entering the input parameters to be verified into the parameter input box, you can click the first verification button to verify the input parameters in the parameter input box.

[0167] In one implementation, after clicking the first verification button, a prompt will pop up in the parameter input box asking whether the input parameters meet the signature requirements.

[0168] In one implementation, the input parameters can be either concatenated return parameters received by the application or verification signature parameters from the execution end.

[0169] In one embodiment, the input parameter detection module further includes a first format correction button, and the input parameter detection module can also be configured to: in response to a first format correction instruction input based on the first format correction button, correct the format of the input parameter to be verified in the parameter input box.

[0170] In this embodiment, such as Figure 4 As shown, the first format correction button is for removing spaces. Input parameters generated during programming may contain spaces; spaces may also be added during the copying of input parameters, causing the input parameters to fail to meet signature requirements. You can click the first format correction button (remove spaces button) to remove the spaces.

[0171] In one embodiment of the present invention, the public key and private key checking module may include a second verification button, a private key input box, and a public key input box. The public key and private key checking module is further configured to: in response to a second verification command input based on the second verification button, check whether the public key in the public key input box and the private key in the private key input box are a pair.

[0172] In this embodiment, such as Figure 4 As shown, you can input the public key and private key into the public key input box and private key input box in the public key and private key checking module (M2) respectively, and click the second verification button (comparison button) to determine whether the public key and private key are a pair.

[0173] In one implementation, the public-private key checking module may include a first format checking button and a second format checking button. The public-private key checking module may also be configured to: detect whether the format of the private key in the private key input box is correct in response to a first format checking instruction input based on the first format checking button; and detect whether the format of the public key in the public key input box is correct in response to a second format checking instruction input based on the second format checking button.

[0174] In this embodiment, such as Figure 4 As shown, clicking the first format check button (the check format button above the private key input box) checks if the private key format is correct, and a prompt will appear indicating whether the private key is correct or not. Clicking the second format check button (the check format button above the public key input box) checks if the public key format is correct, and a prompt will appear indicating whether the public key is correct or not.

[0175] In one embodiment, the public key / private key checking module may include a second format correction button and a third format correction button. The public key / private key checking module is further configured to: correct the format of the private key in the private key input box in response to a second format correction instruction input based on the second format correction button; and correct the format of the public key in the public key input box in response to a third format correction instruction input based on the third format correction button.

[0176] In this embodiment, such as Figure 4 As shown, if the private key format is incorrect, such as containing extra spaces, you can click the second format correction button (private key formatting button) to correct the private key format, such as deleting extra spaces. If the public key format is incorrect, such as containing extra spaces, you can click the third format correction button (public key formatting button) to correct the public key format, such as deleting extra spaces.

[0177] In one implementation, the public key and private key checking module may include a first data clear button, and the public key and private key checking module may also be configured to clear the data in the public key input box and the private key input box in response to a first data clear instruction input based on the first data clear button.

[0178] In this embodiment, such as Figure 4 As shown, the data in the public key input box and the private key input box can be cleared by using the first data clear button (the clear button in M2).

[0179] In one embodiment of the present invention, the data concatenation and signature generation module may include a data generation button; the data concatenation and signature generation module may be further configured to: in response to a data generation instruction input based on the data generation button, generate concatenated data and a signature according to input parameters and a private key.

[0180] In this embodiment, such as Figure 4 As shown, you can click the data generation button (generate button) in the data splicing and signature generation module (M3) to generate spliced ​​data and a signature. The generated spliced ​​data can be displayed above the spliced ​​data comparison module (M4), and the generated signature can be displayed above the signature comparison module (M5).

[0181] In one implementation, the input parameters can be formatted as key=value and sorted in ASCII lexicographical order according to the parameter names to generate concatenated data.

[0182] In one implementation, a signature can be generated based on the generated concatenated data and the private key.

[0183] In one embodiment, the concatenated data generation module may further include a second data clear button, and the concatenated data and signature generation module may be further configured to clear the generated concatenated data and signature in response to a second data clear instruction input based on the second data clear button.

[0184] In this embodiment, such as Figure 4 As shown, you can click the second data clear button (the clear generation button in M3) to delete the generated spliced ​​data and signature.

[0185] In one embodiment of the present invention, the splicing data comparison module may include a third verification button and a request data input box. The splicing data comparison module may be further configured to: in response to a third verification instruction input based on the third verification button, compare the generated splicing data with the request data in the request data input box.

[0186] In this embodiment, such as Figure 4 As shown, you can enter the requested data into the request data input box (the input box below M4), and click the third verification button (the comparison button in M4) to compare the concatenated data with the requested data. The comparison result provides helpful prompts.

[0187] In one implementation, after copying the request data to the request data input box, it can be formatted first (such as deleting spaces that may be copied accidentally), and then the comparison button can be clicked to compare.

[0188] In one embodiment, the splicing data comparison module may further include a third data clear button, and the splicing data comparison module may also be configured to: clear the requested data in the requested data input box in response to a third data clear instruction input based on the third data clear button.

[0189] In this embodiment, such as Figure 4 As shown, you can clear the request data in the request data input box by clicking the third data clear button (the clear button in M4).

[0190] In one embodiment of the present invention, the signature comparison module may include a fourth verification button and a program signature input box. The signature comparison module may be further configured to: in response to a fourth verification instruction input based on the fourth verification button, compare the generated signature with the signature corresponding to the joint debugging process in the program signature input box.

[0191] In this embodiment, such as Figure 4As shown, the signature corresponding to the joint debugging process can be copied to the program signature input box in the signature comparison module (M5). Clicking the fourth verification button (the comparison button in M5) will compare the generated signature with the signature in the program signature input box, and the comparison result can provide a user-friendly prompt.

[0192] In one implementation, after copying the signature from the program to the program signature input box, the signature can be formatted (e.g., removing spaces).

[0193] In one embodiment, the signature comparison module may further include a fourth data clear button, and the signature comparison module may also be configured to: clear the signature in the program in the program signature input box in response to a fourth data clear instruction input based on the fourth data clear button.

[0194] In this embodiment, such as Figure 4 As shown, you can click the fourth data clear button (the clear button in M5) to clear the signature in the program signature input box.

[0195] This invention addresses all potential issues that may arise during the signature integration process by designing an input parameter checking module, a public / private key checking module, a data concatenation and signature generation module, a concatenated data comparison module, and a signature comparison module. The invention utilizes the input parameter checking module in the integration tool to check if the input parameters to be verified meet the signature requirements. The public / private key checking module checks if the public and private keys conform to preset format requirements. The data concatenation and signature generation module generates concatenated data and a signature from the input parameters and private key. The data concatenation comparison module compares the generated concatenated data with the request data. The signature comparison module compares the generated signature with the corresponding signature from the integration process. Through this configuration, this invention can effectively troubleshoot problems during the integration process using the integration tool, improving the efficiency of resolving technical issues. Furthermore, using this invention's integration tool for troubleshooting eliminates the need for personnel to possess specialized technical language skills, reducing reliance on such expertise.

[0196] Furthermore, since problems found in the content checked by later modules are often not solely due to errors in their own content, but rather stem from errors in the content checked by earlier modules—for example, if errors in public or private key formats are not detected and corrected before being directly used in the data concatenation and signature generation modules—then the private key format error will be introduced into the concatenation process, making it impossible to pinpoint the exact source of the problem. Therefore, the use of these modules requires an inherent execution logic order. In a preferred embodiment, when the preceding module is active (editable), the subsequent module is disabled (uneditable, e.g., grayscale display). Only after the preceding module has generated a check result will the next module become active. This approach makes it less prone to errors during integration testing, especially for beginners. With active and disabled modules distinguished, the modules in the integration testing tool can be dragged and dropped, allowing users to arrange the page layout according to their work habits without worrying about which module to use at the current stage.

[0197] Furthermore, the present invention also provides a method for joint debugging.

[0198] See appendix Figure 2 , Figure 2 This is a schematic flowchart illustrating the main steps of a joint debugging method according to an embodiment of the present invention. Figure 2 As shown, the joint debugging method in this embodiment of the invention is based on the joint debugging tool in the above-mentioned joint debugging tool embodiment. The joint debugging method mainly includes the following steps S101-S106.

[0199] Step S101: Check whether the input parameters to be verified meet the signature requirements through the input parameter checking module.

[0200] Optionally, in response to the launch of the integration testing tool (for example, if the integration testing tool is a web page, then in response to the opening of the page; or if the integration testing tool is an APP on a mobile phone, then in response to the opening of the APP), the input parameter detection module is set to an active state, and other modules are set to a disabled state.

[0201] With modules distinguishing between active and disabled states, the modules in the integration tool can be dragged and dropped. Users can arrange the page layout according to their own work habits without worrying about which module to use at the current stage, which is especially helpful for beginners.

[0202] In a preferred example, if it is detected that the size of the display interface of the debugging tool is smaller than the preset size (for example, if the debugging tool is a mobile APP), all disabled modules are hidden, and only the currently active modules are displayed in the maximum size to adapt to the needs of small screens. At the same time, since only one module is displayed on the display interface at a time, there is no need to worry about the user having to consider which module to use at the current stage, especially for beginners.

[0203] In this embodiment, the input parameters to be verified can be checked using an input parameter checking module.

[0204] In one embodiment, step S101 may include steps S1011 to S1013:

[0205] Step S1011: The input parameters are checked by the input parameter checking module. If the check passes, proceed to step S1012; if the check fails, proceed to step S1013.

[0206] Step S1012: Determine if the input parameters meet the signature requirements.

[0207] Step S1013: Input the first format correction command through the first format correction button of the input parameter detection module to correct the format of the input parameters so that the input parameters meet the signature requirements.

[0208] In this embodiment, if the input parameters meet the signature requirements, step S102 can be continued; if the input parameters do not meet the signature requirements, the format of the input parameters can be corrected by using the first format correction button so that the input parameters meet the signature requirements.

[0209] Optionally, in response to detecting that the input parameters meet the signature requirements, the public key / private key checking module is changed from a disabled state to an active state.

[0210] Furthermore, other unused modules can be disabled, including those that were previously disabled and those that have already completed input parameter checks. Similarly, all currently disabled modules can be hidden, and only the public / private key check module can be displayed in maximum size according to the display interface to adapt to small screens. Since only one module is displayed at a time, users don't need to worry about which module to use at the current stage, especially for beginners.

[0211] Step S102: When the input parameters meet the signature requirements, the public key and / or private key in the joint debugging process are checked by the public key and / or private key checking module to see if they meet the preset format requirements.

[0212] In this embodiment, after the input parameters pass the check, the public and private key checking module can be used to check the format of the public and private keys. The format requirements may include whether the public and private keys are a pair, and whether the public key format and the private key format are correct.

[0213] In one embodiment, step S102 may further include steps S1021 and S1023:

[0214] Step S1021: Check the public key and / or private key through the public key and private key checking module.

[0215] Step S1022: If the public key and / or private key meet the format requirements, proceed to step S103;

[0216] Step S1023: If the public key and / or private key do not conform to the format requirements, the format of the public key and / or private key is corrected by using the second format correction button and / or the third format correction button of the public key and private key checking module to obtain a public key and / or private key that conforms to the format requirements.

[0217] In this embodiment, the format of the public key and private key can be checked. If they meet the format requirements, step S103 can be continued. If they do not meet the format requirements, the format of the public key and private key can be corrected to obtain a public key and private key that meet the format requirements.

[0218] Optionally, in response to the detection that the public key and / or private key conforms to the format requirements, the concatenation data and signature generation module is changed from a disabled state to an active state.

[0219] Furthermore, other unused modules can be disabled, including those that were previously disabled and those that have already completed checks, such as input parameter checking and public / private key checking modules. Similarly, all currently disabled modules can be hidden, and only the data concatenation and signature generation modules can be displayed in maximum size according to the display interface to adapt to small screens. Since only one module is displayed at a time, users don't need to worry about which module to use at the current stage, especially for beginners.

[0220] Step S103: When the public key and / or private key meet the format requirements, the concatenated data and signature are generated by the data concatenation and signature generation module based on the input parameters and the private key.

[0221] In this embodiment, once the public and private keys meet the format requirements, the concatenated data and signature can be generated based on the input parameters and the private key through the concatenated data and signature generation module.

[0222] In one implementation, the input parameters can be arranged in a key=value format and sorted according to the ASCII lexicographical order of the parameter names to generate concatenated data. A signature can then be generated based on the sorted input parameter string and the private key.

[0223] Optionally, in response to the detection that the stitched data has been generated, the stitched data comparison module is changed from a disabled state to an active state.

[0224] Furthermore, other unused modules can be disabled, including previously disabled modules and modules that have already completed checks, such as the input parameter checking module, public / private key checking module, and data concatenation and signature generation module. Similarly, all currently disabled modules can be hidden, and only the data concatenation comparison module can be displayed in maximum size according to the display interface to adapt to small screens. Since only one module is displayed at a time, users don't need to worry about which module to use at the current stage, especially for beginners.

[0225] Step S104: The generated spliced ​​data is compared with the requested data through the spliced ​​data comparison module to obtain the first comparison result.

[0226] In this embodiment, after generating the spliced ​​data, the spliced ​​data can be compared with the requested data through the spliced ​​data comparison module to obtain the first comparison result.

[0227] In one implementation, the first comparison result can be normal or abnormal. When the first comparison result is abnormal, the specific problem point will be indicated, and the problem can be investigated and corrected based on the specific problem point.

[0228] Optionally, in response to detecting that a signature has been generated, the signature comparison module is changed from a disabled state to an active state.

[0229] Furthermore, other unused modules can be disabled, including the input parameter checking module, public / private key checking module, data concatenation and signature generation module, and concatenated data comparison module, which have already been checked. Similarly, all currently disabled modules can be hidden, and only the signature comparison module can be displayed in maximum size according to the display interface to adapt to small screens. Since only one module is displayed at a time, there's no need for users to consider which module to use at the current stage, especially for beginners.

[0230] Step S105: The generated signature is compared with the corresponding signature during the joint debugging process using the signature comparison module to obtain the second comparison result.

[0231] In this embodiment, after the signature is generated, the generated signature can be compared with the corresponding signature during the joint debugging process through the signature comparison module to obtain a second comparison result.

[0232] In one implementation, the second comparison result can be normal or abnormal.

[0233] Step S106: Based on the first comparison result and / or the second comparison result, implement the joint debugging process between the execution end and the application end.

[0234] In this embodiment, the first comparison result and the second comparison result can be used to check for possible problems in the joint debugging process and make corrections, thereby realizing the joint debugging process between the execution end and the application end.

[0235] In one implementation, step S106 may include steps S1061 and S1062:

[0236] Step S1061: When the first comparison result is that the comparison fails, obtain the reason for the comparison failure based on the first comparison result.

[0237] In this embodiment, the reason for the failure of the comparison can be obtained based on the first comparison result, so as to make targeted corrections.

[0238] Step S1062: When the second comparison result is that the comparison fails, the joint debugging process is carried out according to the public key and / or private key during the joint debugging process.

[0239] In this embodiment, step S1062 may further include steps S10621 and S10624:

[0240] Step S10621: When the input parameter to be verified is the verification signature parameter of the execution end, check whether the application's private key and public key are a pair through the public key / private key checking module. If yes, proceed to step S10622; if no, proceed to step S10623.

[0241] Step S10622: Check the correctness of the signature algorithm to implement the joint debugging process.

[0242] Step S10623: Regenerate the public and private keys of the application to enable the joint debugging process.

[0243] Step S10624: When the input parameter to be verified is the concatenated return parameter received by the application, query the execution end for the correct public key and check the correctness of the signature algorithm to realize the joint debugging process.

[0244] In this implementation, when the input parameter is the signature verification parameter of the execution end, the public and private keys can be put into the public-private key checking module to check whether the application's private key and public key are a pair; if they are, the correctness of the signature algorithm can be checked; if not, the application's public and private keys can be regenerated. When the input parameter is the concatenated return parameter received by the application end, the correct public key can be queried from the execution end, and the correctness of the signature algorithm can be checked.

[0245] Through steps S101-S106 described above, this embodiment of the invention can systematically check for issues such as whether the input parameter format meets signature requirements, whether the concatenation syntax is correct, whether the private key format is incorrect, and whether the sent public key and the private key used for signing are a pair. This allows for the identification of errors during the integration testing process, ensuring a correct integration testing procedure. This not only improves the efficiency of resolving technical problems during integration testing but also eliminates the need for personnel to possess the relevant technical jargon during troubleshooting, reducing reliance on such jargon and effectively ensuring the correctness of the integration testing.

[0246] See the appendix below. Figure 5 To be continued Figure 9 The method for joint debugging of the present invention will be further illustrated by an example. Figure 5 This is a schematic diagram illustrating the process of an application input parameter checking module checking input parameters according to an embodiment of the present invention. Figure 6 This is a schematic diagram illustrating the process of using a public-private key checking module to check public and private keys according to an embodiment of the present invention. Figure 7 A schematic diagram illustrating the process of generating concatenated data and a signature using an application concatenated data and signature generation module according to an embodiment of the present invention; Figure 8 This is a schematic diagram illustrating the process of comparing generated spliced ​​data and requested data using an application spliced ​​data comparison module according to an embodiment of the present invention; Figure 9 This is a schematic diagram illustrating the process of comparing the generated signature with the corresponding signature during the joint debugging process using an application signature comparison module, according to an embodiment of the present invention.

[0247] like Figure 5 As shown above, input parameters can be entered into the parameter input box of the output parameter checking module (M1); for example... Figure 5 As shown below, click the "Format JSON" button (first verification button) to check the input parameters.

[0248] like Figure 6As shown above, you can copy the private key to the private key input box of the public key / private key check module (M2) and the public key to the public key input box. You can click the check format buttons (first format check button, second format check button) to check if the public and private keys meet the format requirements. After checking the format of the public and private keys, a result will pop up, as shown in the figure, "Private key format is correct!". You can click the private key format (second format correction button) and public key format (third format correction button) to correct the format of the private and public keys. After correcting the format, a correction result will pop up, as shown in the figure, "Public key formatting complete!".

[0249] like Figure 6 As shown below, you can click the comparison button (second verification button) in M2 to compare whether the private key and public key are a pair. After the comparison is completed, the comparison result will pop up, as shown in the figure: "Public key and private key match successfully!".

[0250] like Figure 7 As shown, you can click the "Generate" button (data generation button) in M3 (data splicing and signature generation module) to generate spliced ​​data and a signature. The generated spliced ​​data is filled into the spliced ​​data box, and the generated signature is filled into the generated Sign box.

[0251] like Figure 8 As shown, you can click the comparison button (third verification button) in M4 (data splicing comparison module) to compare the generated spliced ​​data with the requested data. After the comparison is complete, the first comparison result will pop up, as shown in the figure: "Congratulations! Comparison passed, exactly the same!"

[0252] like Figure 9 As shown, you can click the comparison button (fourth verification button) in M5 (signature comparison module) to compare the generated signature with the corresponding signature during the integration process. After the comparison is complete, the comparison result will pop up. As shown in the image, "Comparison failed!"

[0253] By applying integration testing tools, issues such as whether the input parameter format meets signature requirements, whether the concatenation syntax is correct, whether the private key format is incorrect, and whether the sent public key and the private key used for signing are a pair can be checked one by one during the integration testing process. This allows for more efficient troubleshooting of the causes of errors during integration testing. Moreover, operators do not need to master various technical languages ​​to complete the troubleshooting process, reducing reliance on operators' technical language skills and enabling a more efficient and correct integration testing process.

[0254] It should be noted that although the steps in the above embodiments are described in a specific order, those skilled in the art will understand that in order to achieve the effects of the present invention, different steps do not necessarily have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders, and these variations are all within the scope of protection of the present invention.

[0255] Those skilled in the art will understand that all or part of the processes in the method of the above embodiment of the present invention can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable storage medium can include any entity or device capable of carrying the computer program code, a medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc. It should be noted that the content included in the computer-readable storage medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable storage medium does not include electrical carrier signals and telecommunication signals.

[0256] Furthermore, the present invention also provides a control device. In one embodiment of the control device according to the present invention, the control device includes a processor and a storage device. The storage device can be configured to store a program for executing the joint debugging method of the above-described method embodiments, and the processor can be configured to execute the program in the storage device. The program includes, but is not limited to, a program for executing the joint debugging method of the above-described method embodiments. For ease of explanation, only the parts related to the embodiments of the present invention are shown; for specific technical details not disclosed, please refer to the method section of the embodiments of the present invention. This control device can be a control device device comprising various electronic devices.

[0257] In embodiments of the present invention, the control device may be a control device device comprising various electronic devices. In some possible implementations, the control device may include multiple storage devices and multiple processors. The program executing the joint debugging method of the above method embodiments can be divided into multiple subroutines, each subroutine can be loaded and run by a processor to execute different steps of the joint debugging method of the above method embodiments. Specifically, each subroutine can be stored in different storage devices, and each processor can be configured to execute programs in one or more storage devices to jointly implement the joint debugging method of the above method embodiments, that is, each processor executes different steps of the joint debugging method of the above method embodiments to jointly implement the joint debugging method of the above method embodiments.

[0258] The aforementioned multiple processors can be processors deployed on the same device. For example, the aforementioned control device can be a high-performance device composed of multiple processors, and the aforementioned multiple processors can be processors configured on that high-performance device. Alternatively, the aforementioned multiple processors can also be processors deployed on different devices. For example, the aforementioned control device can be a server cluster, and the aforementioned multiple processors can be processors on different servers within the server cluster.

[0259] Furthermore, the present invention also provides a computer-readable storage medium. In one embodiment of the computer-readable storage medium according to the present invention, the computer-readable storage medium can be configured to store a program for performing the integration method of the above-described method embodiments, the program being loaded and run by a processor to implement the above-described integration method. For ease of explanation, only the parts related to the embodiments of the present invention are shown; for specific technical details not disclosed, please refer to the method section of the embodiments of the present invention. The computer-readable storage medium can be a storage device device comprising various electronic devices. Optionally, in the embodiments of the present invention, the computer-readable storage medium is a non-transitory computer-readable storage medium.

[0260] Furthermore, it should be understood that since the various modules are only provided to illustrate the functional units of the device of the present invention, the physical devices corresponding to these modules may be the processor itself, or a part of the processor's software, hardware, or a combination of software and hardware. Therefore, the number of modules shown in the figures is merely illustrative.

[0261] Those skilled in the art will understand that the various modules in the device can be adaptively split or combined. Such splitting or combining of specific modules will not cause the technical solution to deviate from the principles of the present invention; therefore, the technical solutions after splitting or combining will fall within the protection scope of the present invention.

[0262] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A joint debugging tool, characterized in that, The tools include: The input parameter checking module is used to check whether the input parameters to be verified meet the signature requirements; The public and private key checking module is used to check whether the public and / or private keys used in the integration process meet the preset format requirements. The data concatenation and signature generation module is used to generate concatenated data and signatures based on input parameters and private keys; The process of generating the spliced ​​data includes: sorting the input parameters in the format of key=value and in ASCII lexicographical order of the parameter names to generate the spliced ​​data; The signature generation process includes: generating the signature based on the generated concatenated data and the private key; A data splicing comparison module is used to compare the generated spliced ​​data with the requested data; the data splicing comparison module includes a request data input box; the requested data is the data input based on the request data input box; The signature comparison module is used to compare the generated signature with the corresponding signature during the integration testing process; The input parameter checking module includes a first verification button and a parameter input box, and the input parameter checking module is further configured as follows: In response to a first verification command input based on the first verification button, the input parameter to be verified in the parameter input box is detected to determine whether the input parameter meets the signature requirements; The input parameter checking module further includes a first format correction button, and the input parameter checking module is further configured to: In response to a first format correction instruction input based on the first format correction key input, the format of the input parameter to be verified in the parameter input box is corrected.

2. The debugging tool according to claim 1, characterized in that, The public-private key verification module includes a second verification button, a private key input box, and a public key input box. The public-private key verification module is further configured as follows: In response to the second verification command input based on the second verification button, check whether the public key in the public key input box and the private key in the private key input box are a pair.

3. The debugging tool according to claim 2, characterized in that, The public key / private key verification module includes a first format verification button and / or a second format verification button, and the public key / private key verification module is further configured to: In response to a first format check instruction based on the first format check key input, the format of the private key in the private key input box is checked to see if it is correct; and / or, In response to a second format check instruction based on the second format check key input, the format of the public key in the public key input box is checked to see if it is correct; and / or, The public-private key checking module includes a second format correction button and / or a third format correction button, and the public-private key checking module is further configured to: In response to a second format correction instruction input based on the second format correction key input, the format of the private key in the private key input box is corrected; and / or, In response to a third format correction instruction based on the third format correction key input, the format of the public key in the public key input box is corrected; and / or, The public key / private key checking module includes a first data clear button, and the public key / private key checking module is further configured to: In response to a first data clearing command input based on the first data clearing button, the data in the public key input box and the private key input box are cleared.

4. The debugging tool according to claim 1, characterized in that, The data concatenation and signature generation module includes a data generation button; the data concatenation and signature generation module is further configured as follows: In response to a data generation instruction based on the data generated by key input, concatenated data and a signature are generated according to the input parameters and the private key.

5. The debugging tool according to claim 4, characterized in that, The concatenated data generation module also includes a second data clear button, and the concatenated data and signature generation module is further configured as follows: In response to a second data clearing command input based on the second data clearing button, the generated concatenated data and signature are cleared.

6. The debugging tool according to claim 1, characterized in that, The spliced ​​data comparison module includes a third verification button and a request data input box, and the spliced ​​data comparison module is further configured as follows: In response to the third verification instruction input based on the third verification button, the generated concatenated data is compared with the request data in the request data input box.

7. The joint debugging tool according to claim 6, characterized in that, The spliced ​​data comparison module also includes a third data clear button, and the spliced ​​data comparison module is further configured to: In response to the third data clearing instruction input based on the third data clearing button, the request data in the request data input box is cleared.

8. The joint debugging tool according to claim 1, characterized in that, The signature comparison module includes a fourth verification button and a program signature input box, and the signature comparison module is further configured as follows: In response to the fourth verification instruction input based on the fourth verification button, the generated signature is compared with the corresponding signature in the program signature input box during the joint debugging process.

9. The joint debugging tool according to claim 8, characterized in that, The signature comparison module also includes a fourth data clear button, and the signature comparison module is further configured as follows: In response to the fourth data clearing instruction input based on the fourth data clearing button, the signature in the program in the program signature input box is cleared.

10. A method for joint debugging, characterized in that, The method is based on the debugging tool according to any one of claims 1 to 9, and the method includes: The input parameter checking module checks whether the input parameters to be verified meet the signature requirements. When the input parameters meet the signature requirements, the public key and / or private key checking module checks whether the public key and / or private key in the joint debugging process meet the preset format requirements. When the public key and / or private key meet the format requirements, the concatenated data and signature are generated by the concatenated data and signature generation module according to the input parameters and the private key; The spliced ​​data comparison module compares the generated spliced ​​data with the requested data to obtain a first comparison result. The generated signature is compared with the corresponding signature during the joint debugging process using the signature comparison module to obtain a second comparison result. Based on the first comparison result and / or the second comparison result, potential problems in the joint debugging process are checked and corrected, thereby realizing the joint debugging process between the execution end and the application end.

11. The joint debugging method according to claim 10, characterized in that, The process of implementing joint debugging between the execution end and the application end based on the first comparison result and / or the second comparison result includes: When the first comparison result is that the comparison fails, the reason for the comparison failure is obtained based on the first comparison result; When the second comparison result is a failure, the joint debugging process is implemented according to the public key and / or private key in the joint debugging process. The step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes: When the input parameter to be verified is the parameter of the verification signature of the execution end, the public key private key checking module checks whether the private key and the public key of the application end are a pair; If so, check the correctness of the signature algorithm to implement the aforementioned integration testing process; If not, regenerate the public and private keys of the application to implement the joint debugging process.

12. The joint debugging method according to claim 11, characterized in that, The step of implementing the joint debugging process based on the public key and / or private key during the joint debugging process includes: When the input parameter to be verified is the concatenated return parameter received by the application, the correct public key is queried from the execution end, and the correctness of the signature algorithm is checked to realize the joint debugging process.

13. The joint debugging method according to claim 10, characterized in that, The step of checking whether the input parameters to be verified meet the signature requirements through the input parameter checking module includes: The input parameters are checked using the input parameter checking module. If the check passes, the input parameters are deemed to meet the signature requirements; If the check fails, a first format correction command is input via the first format correction button of the input parameter check module to correct the format of the input parameters so that they meet the signature requirements; and / or, The step of checking whether the public key and / or private key conforms to preset format requirements through the public key and / or private key checking module includes: The public key and / or the private key are checked using the public key and private key checking module. If the public key and / or the private key conform to the format requirements, execute the step of "generating concatenated data and a signature based on the input parameters and the private key through the concatenated data and signature generation module"; If the public key and / or the private key does not conform to the format requirements, the public key and / or the private key can be corrected by using the second format correction button and / or the third format correction button of the public key and private key checking module to obtain a public key and / or private key that conforms to the format requirements.

14. A control device comprising at least one processor and at least one storage device, said storage device being adapted to store a plurality of program codes, characterized in that, The program code is adapted to be loaded and run by the processor to perform the integration method according to any one of claims 10 to 13.

15. A computer-readable storage medium storing a plurality of program codes, characterized in that, The program code is adapted to be loaded and run by a processor to perform the integration method according to any one of claims 10 to 13.

Images