Authentication test method and device

Abstract

The invention provides an authentication test method and device. The method comprises the following steps: sending a first test application carrying first name information and equipment model information of first equipment to a server; receiving an initial block, wherein the initial block is generated by the server according to the first random number, the first name information and the equipment model information of the first equipment; generating a test result file and a test evidence chain in the process of performing the authentication test on the first equipment, wherein the test evidence chain is generated based on the initial block; and sending the test result file and the test evidence chain to the server for the server to judge whether the test result is tampered or not. Through the method and the device, the client generates the test evidence chain based on the test process, the server performs tampering judgment based on the test evidence chain, and the two ends do not need to frequently interact; moreover, the test evidence chain can comprise a plurality of evidence blocks, and the server can identify the tampering of the test result file, and also can identify the tampering of the test equipment or the test application.

Description

Technical Field

[0001] The present application relates to the field of certification testing, and more specifically, to a certification testing method and device. Background Art

[0002] With the development of mobile Internet, more and more mobile platform companies are transforming into ecological companies. Platform companies (service end) sign relevant commercial agreements with third-party equipment manufacturers (client end) to pre-install ecological products (such as mobile application apps and mobile services) in the equipment (such as mobile devices) of third-party equipment manufacturers (such as mobile phone manufacturers), thereby increasing the installation volume of ecological products and expanding their own ecology. At the same time, third-party equipment manufacturers can participate in the sharing of their commercial benefits.

[0003] In this context, mobile platform companies (servers) usually provide "certification testing" services to third-party device manufacturers (clients) in order to ensure that third-party devices pre-installed with their ecological products meet their compatibility requirements and technical specifications. The certification test is completed locally by the client (i.e., the third-party device manufacturer), which makes it possible for both the tested device and the test result file to be tampered with.

[0004] Therefore, how to prevent the test results of the certification test from being tampered with is a problem that needs to be solved urgently. Summary of the invention

[0005] The present application provides a method and device for authentication testing. Through the method and device, the client generates a test evidence chain based on the test process, and the server makes tampering judgment based on the test evidence chain, without frequent interaction between the two ends; and the test evidence chain can include multiple evidence blocks, and the server can not only identify tampering of the test result file, but also identify tampering of the test equipment or test application.

[0006] In a first aspect, a method for authentication testing is provided, the method comprising: sending a first test application to a server, the first test application carrying first name information and device model information of a first device; receiving an initial block sent by the server, the initial block being generated by the server according to a first random number, the first name information and the device model information of the first device; generating a test result file and a test evidence chain in the process of performing an authentication test on the first device, the test evidence chain being generated based on the initial block; sending the test result file and the test evidence chain to the server, the test result file and the test evidence chain being used by the server to determine whether the test result has been tampered with.

[0007] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side can make a tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function. The client and the server do not need to interact frequently to achieve the purpose of anti-tampering of the authentication test results.

[0008] In combination with the first aspect, in certain implementations of the first aspect, a test result file and a test evidence chain are generated during the authentication test of the first device, including: when the test starts, a first block is generated by reading the device model information of the first device; when the test is completed, the test result file is generated, and a second block is generated based on the test result file; after the test is completed, a third block is generated by reading the device model information of the first device; and the test evidence chain is generated by sequentially connecting the initial block, the first block, the second block, and the third block.

[0009] That is to say, the initial block records the first random number, the first name information and the device model information of the first device, the first block records the device model information of the first device read by the client from the first device when the authentication test is started, the second block records the fingerprint information calculated according to the test result file generated during the authentication test, and the third block records the device model information of the first device read by the client from the first device when the authentication test is completed.

[0010] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0011] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving a test suite sent by the server; and performing an authentication test on the first device according to the test suite.

[0012] In a second aspect, a method for authentication testing is provided, the method comprising: receiving a first test application sent by a client, the first test application carrying first name information and device model information of a first device; generating an initial block according to a first random number, the first name information and the device model information of the first device; sending the initial block to the client, the initial block being used for the client to generate a test evidence chain; receiving a test result file and the test evidence chain sent by the client; and determining whether the test result has been tampered with according to the test result file and the test evidence chain.

[0013] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side can make a tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function. The client and the server do not need to interact frequently to achieve the purpose of anti-tampering of the authentication test results.

[0014] In combination with the second aspect, in certain implementations of the second aspect, the test evidence chain includes the initial block, a first block, a second block and a third block, wherein the first block includes the device model information of the first device read when the test is started, the second block includes the fingerprint information of the test result file generated when the test is completed, and the third block includes the device model information of the first device read after the test is completed, and the initial block, the first block, the second block and the third block are connected in series in sequence.

[0015] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record test result files, test equipment information, and test applications during the test process, so that the server side can not only identify tampering of test result files, but also identify tampering of "test equipment information" and "test application", which can expand the scope of anti-tampering protection of test results.

[0016] In combination with the second aspect, in certain implementations of the second aspect, determining whether the test result has been tampered with is performed based on the test result file and the test evidence chain, including: determining whether the fingerprint information of the test result file received from the client is the same as the fingerprint information of the test result file in the second block; if they are the same, determining that the test result file received from the client has not been tampered with.

[0017] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the test result file during the test process. After receiving the test result file, the server can compare the received test result file with the test result file recorded in the evidence block, and then determine whether the test result file has been tampered with based on the comparison result (if they are the same, it has not been tampered with; if they are not the same, it has been tampered with). That is, this method can achieve tamper-proofing of the test result file, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, and can save signaling overhead.

[0018] In combination with the second aspect, in certain implementations of the second aspect, determining whether the test result has been tampered with based on the test result file and the test evidence chain also includes: determining whether the device model information of the first device stored in the server is the same as the device model information of the first device in the first block; if they are the same, determining that the device under test has not been tampered with.

[0019] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the model information of the device under test during the test process. After receiving the test results, the server can compare the model information of the device under test stored on the local side with the model information of the device under test recorded in the evidence block, and then determine whether the device under test has been tampered with based on the comparison result (if they are the same, it has not been tampered with; if they are not the same, it has been tampered with). That is, this method can achieve tamper-proofing of the device under test, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, which can save signaling overhead.

[0020] In combination with the second aspect, in certain implementations of the second aspect, determining whether the test result has been tampered with based on the test result file and the test evidence chain also includes: determining whether the initial block stored by the server is the same as the initial block in the test evidence chain; if they are the same, determining that the test result matches the first test application.

[0021] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the test application information (first name information (for example, three-party partner name information), device information of the device under test, etc.) during the test process. After receiving the test results, the server can compare the test application information stored on this side with the test application information recorded in the evidence block, and then determine whether the test application information has been tampered with based on the comparison result (that is, whether the test result matches the test application; if they are the same, it has not been tampered with; if they are not the same, it has been tampered with). That is, this method can achieve tamper-proofing of the test application information, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, which can save signaling overhead.

[0022] In combination with the second aspect, in some implementations of the second aspect, the method further includes: storing the first name information and device model information of the first device.

[0023] In an embodiment of the present application, the server stores the first name information and the device model information of the first device before the test begins, so as to be used for tampering determination of the model of the tested device and the test application information in a subsequent tampering determination process.

[0024] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending a test suite to the client, where the test suite is used by the client to perform an authentication test on the first device.

[0025] According to a third aspect, a device for authentication testing is provided, comprising: a first transceiver module, used to send a first test application to a server, the first test application carrying first name information and device model information of a first device; the first transceiver module is also used to receive an initial block sent by the server, the initial block is generated by the server according to a first random number, the first name information and the device model information of the first device; a second generation module is used to generate a test result file and a test evidence chain during an authentication test of the first device, the test evidence chain is generated based on the initial block; the first transceiver module is also used to send the test result file and the test evidence chain to the server, the test result file and the test evidence chain are used by the server to determine whether the test result has been tampered with.

[0026] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side can make a tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function. The client and the server do not need to interact frequently to achieve the purpose of anti-tampering of the authentication test results.

[0027] In combination with the third aspect, in certain implementations of the third aspect, the second generation module is specifically used to: generate a first block by reading the device model information of the first device when the test is started; generate the test result file when the test is completed, and generate a second block based on the test result file; generate a third block by reading the device model information of the first device after the test is completed; generate the test evidence chain by sequentially connecting the initial block, the first block, the second block and the third block.

[0028] That is to say, the initial block records the first random number, the first name information and the device model information of the first device, the first block records the device model information of the first device read by the client from the first device when the authentication test is started, the second block records the fingerprint information calculated according to the test result file generated during the authentication test, and the third block records the device model information of the first device read by the client from the first device when the authentication test is completed.

[0029] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0030] In combination with the third aspect, in certain implementations of the third aspect, the first transceiver module is further used to: receive a test suite sent by the server; the apparatus further includes: a test execution module, used to perform an authentication test on the first device according to the test suite.

[0031] In a fourth aspect, a device for authentication testing is provided, comprising: a second transceiver module, used to receive a first test application sent by a client, the first test application carrying first name information and device model information of a first device; a first generation module, used to generate an initial block according to a first random number, the first name information and the device model information of the first device; the second transceiver module, also used to send the initial block to the client, the initial block is used for the client to generate a test evidence chain; the second transceiver module, also used to receive a test result file and the test evidence chain sent by the client; a determination module, used to determine whether the test result has been tampered with according to the test result file and the test evidence chain.

[0032] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side can make a tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function. The client and the server do not need to interact frequently to achieve the purpose of anti-tampering of the authentication test results.

[0033] In combination with the fourth aspect, in certain implementations of the fourth aspect, the test evidence chain includes the initial block, a first block, a second block and a third block, wherein the first block includes the device model information of the first device read when the test is started, the second block includes the fingerprint information of the test result file generated when the test is completed, and the third block includes the device model information of the first device read after the test is completed, and the initial block, the first block, the second block and the third block are connected in series sequentially.

[0034] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record test result files, test equipment information, and test applications during the test process, so that the server side can not only identify tampering of test result files, but also identify tampering of "test equipment information" and "test application", which can expand the scope of anti-tampering protection of test results.

[0035] In combination with the fourth aspect, in certain implementations of the fourth aspect, the determination module is specifically used to determine whether the fingerprint information of the test result file received from the client is the same as the fingerprint information of the test result file in the second block; if they are the same, determining that the test result file received from the client has not been tampered with.

[0036] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the test result file during the test process. After receiving the test result file, the server can compare the received test result file with the test result file recorded in the evidence block, and then determine whether the test result file has been tampered with based on the comparison result (if they are the same, it has not been tampered with; if they are not the same, it has been tampered with). That is, the device can implement tamper-proofing of the test result file, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, and can save signaling overhead.

[0037] In combination with the fourth aspect, in certain implementations of the fourth aspect, the determination module is further specifically used to determine whether the device model information of the first device stored in the server is the same as the device model information of the first device in the first block; if they are the same, determining that the device under test has not been tampered with.

[0038] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the model information of the device under test during the test process. After receiving the test results, the server can compare the model information of the device under test stored on the local side with the model information of the device under test recorded in the evidence block, and then determine whether the device under test has been tampered with based on the comparison result (if they are the same, it has not been tampered with; if they are not the same, it has been tampered with). That is, the device can achieve tamper-proofing of the device under test, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, which can save signaling overhead.

[0039] In combination with the fourth aspect, in certain implementations of the fourth aspect, the determination module is further specifically used to determine whether the initial block stored by the server is the same as the initial block in the test evidence chain; if they are the same, determining that the test result matches the first test application.

[0040] In an embodiment of the present application, the test evidence chain generated by the client includes an evidence block that records the test application information (first name information (for example, three-party partner name information), device information of the device under test, etc.) during the test process. After receiving the test results, the server can compare the test application information stored on this side with the test application information recorded in the evidence block, and then determine whether the test application information has been tampered with based on the comparison result (that is, whether the test result matches the test application; if they are the same, it has not been tampered with; if they are not the same, it has been tampered with), that is, the device can achieve tamper-proofing of the test application information, and since the test evidence chain is generated on the client, the determination process does not rely on frequent interactions between the client and the server, which can save signaling overhead.

[0041] In combination with the fourth aspect, in some implementations of the fourth aspect, the apparatus further includes: a storage module, configured to store the first name information and device model information of the first device.

[0042] In an embodiment of the present application, the server stores the first name information and the device model information of the first device before the test begins, so as to be used for tampering determination of the model of the tested device and the test application information in a subsequent tampering determination process.

[0043] In combination with the fourth aspect, in some implementations of the fourth aspect, the second transceiver module is further used to: send a test suite to the client, where the test suite is used by the client to perform an authentication test on the first device.

[0044] In a fifth aspect, a system for certification testing is provided, the system comprising: the device in the third aspect or any possible implementation of the third aspect, and / or the device in the fourth aspect or any possible implementation of the fourth aspect.

[0045] In a sixth aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory is used to store computer program code, and the processor is used to execute the computer program code stored in the memory to implement the method in the above-mentioned first aspect or any possible implementation of the first aspect, and / or to implement the method in the above-mentioned second aspect or any possible implementation of the second aspect.

[0046] In the seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed, it implements the method in the above-mentioned first aspect or any possible implementation of the first aspect, and / or implements the above-mentioned second aspect or any possible implementation of the second aspect.

[0047] In an eighth aspect, a chip is provided, in which instructions are stored. When the chip is executed on a device, the chip executes the method in the above-mentioned first aspect or any possible implementation of the first aspect, and / or executes the above-mentioned second aspect or any possible implementation of the second aspect.

[0048] In the ninth aspect, a computer program product is provided, comprising: a computer program code, which, when executed, implements the method in the first aspect or any possible implementation of the first aspect, and / or implements the method in the second aspect or any possible implementation of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 is a schematic flow chart of a general method for authentication testing provided in an embodiment of the present application;

[0050] Figure 2 is a schematic flow chart of an existing authentication test method provided in an embodiment of the present application;

[0051] Figure 3 is a schematic flow chart of a method for authentication testing provided in an embodiment of the present application;

[0052] Figure 4 is a schematic flow chart of another authentication test method provided in an embodiment of the present application;

[0053] Figure 5 It is a schematic diagram of the composition of four evidence blocks (i.e., the initial block, the first block, the second block, and the third block) provided in an embodiment of the present application;

[0054] Figure 6 is a schematic flow chart of a method for determining anti-tampering of test results provided in an embodiment of the present application;

[0055] Figure 7 It is a schematic diagram of three traceback points involved in the evidence chain traceback process provided in the embodiment of the present application;

[0056] Figure 8 It is a schematic diagram of the determination process of anti-tampering of test results provided in an embodiment of the present application;

[0057] Fig. 9 This is a system architecture diagram of a certification test provided by an embodiment of the present application;

[0058] Fig.10 It is a schematic flow chart of a certification test device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" or "multiple" refers to two or more than two.

[0060] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0061] The terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one, two or more. The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0062] References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "one embodiment", "some embodiments", "another embodiment", "some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

[0063] The method provided in the embodiment of the present application can be applied to offline client testing scenarios, and the main application scenario is to ensure that the client test results are tamper-proof.

[0064] With the development of mobile Internet, more and more mobile platform companies are transforming into ecological companies. Platform companies (service end) sign relevant commercial agreements with third-party equipment manufacturers (client end) to pre-install ecological products (such as mobile application apps and mobile services) in the equipment (such as mobile devices) of third-party equipment manufacturers (such as mobile phone manufacturers), thereby increasing the installation volume of ecological products and expanding their own ecology. At the same time, third-party equipment manufacturers can participate in the sharing of their commercial benefits.

[0065] In this context, mobile platform companies (servers) usually provide "certification testing" services to third-party device manufacturers (clients) in order to ensure that third-party devices pre-installed with their ecological products meet their compatibility requirements and technical specifications.

[0066] Figure 1 FIG. 1 is a schematic flow chart of a method 100 for authentication testing provided in an embodiment of the present application. Figure 1 As shown, the method 100 includes:

[0067] S101: The client sends an authentication test request to the server.

[0068] S102: After receiving the certification test application, the server sends an application approval notification to the client after determining that the application is approved.

[0069] S103: After receiving the application approval notification, the client downloads the test suite from the server.

[0070] The test suite includes test cases and test execution devices.

[0071] S104: The client tests the device under test based on the test suite.

[0072] S105: After completing the test, the client generates a test result file.

[0073] S106: The client sends the test result file to the server.

[0074] S107: After receiving the test result file, the server reviews the test result according to the test result file.

[0075] S108: The server sends a review result notification to the client, where the review result notification is used to inform the client whether the review is passed.

[0076] In this method, the authentication test is completed locally by the client (i.e., the third-party equipment manufacturer), which makes it possible for both the tested equipment and the test result files to be tampered with. The client also has the motivation to tamper with the test result files, which can easily lead to inaccurate test results and cause commercial losses to the server (i.e., the platform company).

[0077] Therefore, how to prevent the test results of the certification test from being tampered with is an issue that needs to be solved urgently.

[0078] For example, Figure 2 FIG. 2 is a schematic flow chart of an existing authentication test method 200 provided in an embodiment of the present application. Figure 2 As shown, the method 200 includes:

[0079] S201: Establishing real-time interaction between the monitoring software server and the monitoring software client.

[0080] The monitoring software client is used to download and execute the test software. Before testing, you first need to download the test software corresponding to the corresponding test machine through the monitoring software client, and then the monitoring software client executes the test software and displays the test process and results on the display interface. The monitoring software server is used to monitor whether the test software has been tampered with or whether there is a new update.

[0081] S202: Download all test software to the distributed file system through the monitoring software server, and calculate the first MD5 value of the file in each directory of the test software.

[0082] When monitoring whether the test software has been modified, it is necessary to download all the test software to the local distributed file system to avoid omissions. At the same time, all the test software is divided into directories, and the first MD5 value of the file in each directory is calculated, and the MD5 value is used as the basis for judging whether the test software has been modified. MD5 is a widely used cryptographic hash function that can generate a 128-bit (16-byte) hash value to ensure that information transmission is complete and consistent.

[0083] S203: When the monitoring software client is started, the second MD5 value of the files in each directory of the test software is calculated regularly, and the second MD5 value is compared with the first MD5 value.

[0084] When testing, the monitoring software server will download the test software and periodically calculate the second MD5 value of the files in each directory of the test software to determine whether the test software has been modified. In this solution, the second MD5 value is calculated periodically, and the trigger interval can be set according to actual needs.

[0085] S204: If the second MD5 value is different from the corresponding first MD5, it is determined that the test software has been tampered with.

[0086] By setting up a monitoring software server and having the monitoring software server interact with the monitoring software client in real time, the monitoring software server can download all the test software to the local computer. By calculating the first MD5 value of the files in each directory of the test software and comparing it with the second MD5 value of the files in each directory of the test software when the monitoring software client is started, it can accurately determine whether the test software has been tampered with, thereby avoiding the outflow of a large number of defective products due to the operator manually modifying the test parameters of the software.

[0087] Although this method can determine whether the test result file has been tampered with, it is necessary to install monitoring software on the client side, which requires frequent interactions between the client and the server, making deployment and implementation more difficult. Moreover, this method can only determine whether the test result file has been tampered with, but cannot determine whether the relevance of the device environment in which the file is located is legal. It can only prevent tampering of "things" (i.e. files), but cannot prevent tampering of "relationships" (i.e. the consistency between the device under test and the test application), and the protection against tampering scenarios is limited.

[0088] In view of this, the embodiments of the present application provide a method, device and system for authentication testing. Through this method, device and system, a test evidence chain can be generated on the client side based on the test process, and the server side can make a tampering judgment based on the test evidence chain after the test is completed. In this method, the test evidence chain is generated entirely locally on the client side, providing an offline anti-tampering function, and the client and server do not need to interact frequently; and the test evidence chain generated in this method includes multiple evidence blocks for writing "test result files", "test equipment information" and "test applications", which can not only identify tampering of test result files, but also identify tampering of "test equipment information" and "test applications".

[0089] For example, Figure 3 FIG. 3 is a schematic flow chart of a method 300 for authentication testing provided in an embodiment of the present application. Figure 3 As shown, the method 300 includes:

[0090] S301: The client sends a first test request to the server.

[0091] The first test application carries the name information of the three-party partners and the device model information of the first device.

[0092] The first device is the device under test.

[0093] S302: After receiving the first test application, the server stores the name information of the three-party partners and the device model information of the first device, generates a first random number, and generates an initial block according to the first random number, the name information of the three-party partners and the device model information of the first device.

[0094] S303: The server sends the test suite and the generated initial block to the client.

[0095] The test suite includes test cases and test execution devices.

[0096] S304: The client tests the first device based on the test suite.

[0097] S305: The client generates a test result file after the test is completed.

[0098] S306: The client generates a test evidence chain based on the initial block during the test process.

[0099] The test evidence chain includes an initial block, a first block, a second block, and a third block. The initial block records the first random number, the name information of the three-party partner, and the device model information of the first device; the first block records the device model information of the first device read by the client from the first device when the authentication test is started; the second block records the fingerprint information calculated according to the test result file generated during the authentication test; and the third block records the device model information of the first device read by the client from the first device when the authentication test is completed.

[0100] The order of step S305 and step S306 is not limited.

[0101] S307: The client sends the test result file and the test evidence chain to the server.

[0102] S308: After receiving the test result file and the test evidence chain sent by the client, the server performs backtracking based on the test result file and the test evidence chain to determine whether the test result has been tampered with.

[0103] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0104] For example, Figure 4 FIG. 4 is a schematic flow chart of another authentication test method 400 provided in an embodiment of the present application. Figure 4 As shown, the method 400 includes:

[0105] S401: The client sends a first test request to the server.

[0106] The first test application is used to request an authentication test for the first device, and the first test application carries the name information of the three-party partner and the device model information of the first device.

[0107] The first device is the device under test.

[0108] Among them, the client sends the first test application to the server, which can be understood as: the client registers the name information of the three-party partner (for example: Good Friend Mobile Company) and the device model information of the first device (for example: Frind-888) to the server.

[0109] S402: After receiving the first test request, the server stores the name information of the three-party partners and the device model information of the first device, generates a first random number, and generates an initial block according to the first random number, the name information of the three-party partners and the device model information of the first device.

[0110] The first random number generated by the server may be, for example, a first random number generated according to a timestamp.

[0111] Specifically, after the server generates a first random number (for example: 2023051701365673), it combines the first random number with the name information of the three-party partner (for example: Good Friend Mobile Company) and the device model information of the first device (for example: Frind-888) to generate an initial block.

[0112] S403: The server sends the test suite and the generated initial block to the client.

[0113] The test suite includes test cases and test execution devices.

[0114] In some embodiments, the server serializes the initial block and sends it to the client.

[0115] S404: After the client accesses the first device, when starting a test based on the test suite, the device model information (eg, Frind-888) of the first device is read from the first device, and a first block is generated according to the read device model information of the first device.

[0116] That is, the first block records the device model information of the first device read by the client from the first device when the authentication test is started.

[0117] S405: The client executes the test based on the test suite, generates a test result file, and generates a second block.

[0118] Specifically, the client executes the test case through the test suite and generates a test result file (for example: TestSummary_202305170945.html), and then generates the second block by calculating the fingerprint of the test result file (for example: SHA256).

[0119] The second block records the fingerprint information calculated according to the test result file.

[0120] S406: After the authentication test is completed, the client reads the device model of the first device from the first device again, and generates a third block according to the read device model of the first device.

[0121] The third block records the device model information of the first device read by the client from the first device after the authentication test is completed.

[0122] S407: The client connects the initial block, the first block, the second block and the third block in series in a linked list sequence to generate a test evidence chain.

[0123] In some embodiments, the client relies on the test execution device to deserialize the initial block, and concatenates it with the first block, the second block and the third block in a linked list sequence to generate a test evidence chain.

[0124] S408: The client sends the test result file and the test evidence chain to the server.

[0125] S409: After receiving the test result file and the test evidence chain sent by the client, the server performs backtracking based on the test result file and the test evidence chain to determine whether the test result has been tampered with.

[0126] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0127] In order to more clearly understand the above initial block, the first block, the second block and the third block, the following is exemplarily described in combination with Figure 5 , the composition of the four evidence blocks (i.e., the above-mentioned initial block, the first block, the second block and the third block) provided in the embodiment of the present application is schematically illustrated.

[0128] like Figure 5 As shown, the initial block is generated on the server side after the client initiates the first test application and passes it. The fields of the initial block are as follows: the value of the Data field is composed of the name information of the three-party partner, the model information of the first device and the first random number combination; the value of the Hash field is obtained by performing a Hash operation on the value of the Data field; the Pre_Hash field is empty (Null), and the value of the Timestamp field is the timestamp of the test initiation (i.e.: the time when the initial block was generated). The initial block is generated on the server side, and the server side sends the initial block to the client through the test suite, and saves a copy of the initial block on the server side.

[0129] The first block is generated on the client side when the test is started. The fields of the first block are as follows: the value of the Data field is the model information of the first device read when the test is started; the value of the Hash field is obtained by performing a hash operation on the Data field value; the Pre_Hash field points to the Hash field of the initial block; the value of the Timestamp field is the test start timestamp (i.e., the time when the first block was generated).

[0130] The second block is generated on the client side after the test result file is generated. The fields of the second block are as follows: the value of the Data field is the fingerprint obtained by calculating the "test result file"; the value of the Hash field is obtained by performing a hash operation on the Data field value; the Pre_Hash field points to the Hash field of the first block; the value of the Timestamp field is the timestamp of the test result file generation (i.e., the time when the second block was generated).

[0131] The third block is generated on the client side when the test ends. The fields of the third block are as follows: the value of the Data field is the device model information of the first device read at the end of the test; the value of the Hash field is obtained by performing a hash operation on the Data field value; the Pre_Hash field points to the Hash field of the second block; the value of the Timestamp field is the test end timestamp, i.e., the time when the third block was generated).

[0132] The initial block, the first block, the second block and the third block are processed as follows Figure 5 The logical links shown constitute the test evidence chain.

[0133] For example, Figure 6 A schematic flow chart of a method 600 for determining anti-tampering of test results provided in an embodiment of the present application is shown.

[0134] like Figure 6 As shown, the method 600 occurs at the server, and the method 600 includes:

[0135] S601: After initiating the test result anti-tampering determination, the server calculates a first hash value by calculating the fingerprint of the test result file.

[0136] That is to say, the first hash value records the fingerprint information of the test result file sent by the client and received by the server after the authentication test is completed.

[0137] In some embodiments, after the server receives the test result file (for example: TestSummary_202305170945.html) and the test evidence chain uploaded by the client, it initiates a test result anti-tampering judgment.

[0138] S602: Compare the first hash value with the Pre Hash in the third block.

[0139] Among them, the Pre Hash field in the third block points to the Hash field of the second block, the value of the Hash field in the second block is obtained by performing a hash operation on the Data field value in the second block, and the value of the Data field in the second block is the fingerprint information obtained by calculating the test result file generated when the test is completed.

[0140] Among them, the first hash value is compared with the Pre Hash in the third block, that is, the fingerprint information of the test result file sent by the client received by the server after the authentication test is completed is compared with the fingerprint information obtained from the test result file generated by the client when the test is completed.

[0141] S603: Determine whether the first hash value is the same as the Pre Hash in the third block. If the first hash value is the same as the Pre Hash in the third block, then further execute step S604; if the first hash value is not the same as the Pre Hash in the third block, then determine that the test result file has been tampered with.

[0142] Specifically, it is determined whether the fingerprint information of the test result file sent by the client and received by the server after the authentication test is completed is the same as the fingerprint information obtained by the test result file generated by the client when the test is completed. If they are the same, it means that the test result file has not been tampered with, and step S604 is continued; if they are not the same, it means that the test result file has been tampered with, and it can be determined that the test result has been tampered with.

[0143] S604: Calculate a second hash value by obtaining the first device model stored on the local end.

[0144] That is, the second hash value records the first device model information stored by the server before the authentication test starts.

[0145] S605: Compare the second hash value with the Pre Hash in the second block.

[0146] Among them, the Pre Hash field in the second block points to the Hash field in the first block, the value of the Hash field in the first block is obtained by performing a hash operation on the Data field value in the first block, and the value of the Data field in the first block is the model information of the first device read when the test is started.

[0147] The second hash value is compared with the Pre Hash in the second block, that is, the first device model information stored on the server before the authentication test starts is compared with the first device model information read by the client when the test starts.

[0148] S606: Determine whether the second hash value is the same as the Pre Hash in the second block. If the second hash value is the same as the Pre Hash in the second block, further execute step S607; if the second hash value is not the same as the Pre Hash in the second block, determine that the test device (ie, the first device) has been tampered with.

[0149] Specifically, determine whether the first device model information stored in the server before the authentication test starts is the same as the model information of the first device read by the client when the test starts. If they are the same, it means that the test device has not been tampered with, and continue to step S607; if they are not the same, it means that the test device has been tampered with, and it can be determined that the test result has been tampered with.

[0150] S607: The server obtains the hash value in the stored initial block.

[0151] The hash value in the stored initial block is obtained by performing a hash operation on the value of the Data field in the stored initial block, and the value of the Data field in the stored initial block is composed of the name information of the three-party partner, the model information of the first device, and the first random number. In other words, the hash value of the stored initial block records the combination information of the name information of the three-party partner when the test was initiated, the model information of the first device, and the first random number.

[0152] S608: Compare the hash value in the stored initial block with the Pre Hash in the first block.

[0153] Among them, the Pre Hash field in the first block points to the Hash field of the initial block. The value of the Hash field in the initial block is obtained by performing a hash operation on the Data field value in the initial block. The value of the Data field in the initial block is composed of the name information of the three-party partners, the model information of the first device and the first random number combination.

[0154] Among them, the hash value stored in the initial block is compared with the Pre Hash in the first block, that is, the combination information of the three-party partner name information, the model information of the first device and the first random number stored on the server before the authentication test starts is compared with the combination information of the three-party partner name information, the model information of the first device and the first random number of the initial block in the evidence chain.

[0155] S609: Determine whether the hash value in the stored initial block is the same as the Pre Hash in the first block. If the hash value in the stored initial block is the same as the Pre Hash in the first block, it is determined that the test result has not been tampered with; if the hash value in the stored initial block is different from the Pre Hash in the first block, it is determined that the test result does not match the test application and the test result has been tampered with.

[0156] Specifically, determine whether the combination information of the three-party partner name information, the model information of the first device and the first random number stored on the server before the start of the authentication test is the same as the combination information of the three-party partner name information, the model information of the first device and the first random number in the initial block in the evidence chain. If they are the same, it means that the test result of this test matches the test application; if they are different, it means that the test result of this test does not match the test application, and it can be determined that the test result has been tampered with.

[0157] In order to more clearly understand the process of backtracking the test evidence chain (i.e. Figure 4 Step S409 shown), the following, exemplarily, combined with Figure 7 , the three tracing points involved in the process of tracing the chain of evidence are introduced.

[0158] Backtracking point 1 is the backtracking point from the third block to the second block, and this backtracking point 1 is used to determine whether the test result file has been tampered with. Specifically: after the server initiates the anti-tampering determination of the test result, the server calculates the fingerprint of the test result file uploaded by the client, and calculates its Hash value, and compares the calculated Hash value with the Pre_Hash value in the third block. If the Hash value is different from the Pre_Hash value in the third block, it is determined that the test result file uploaded by the client has been tampered with. If the Hash value is the same as the Pre_Hash value in the third block, it is determined that the test result file uploaded by the client has not been tampered with.

[0159] Backtracking point 2 is the backtracking point from the second block to the first block, which is used to determine whether the test device (i.e., the first device mentioned above) has been tampered with. Specifically: the server obtains the model of the test device stored on the local end, calculates its Hash value, and compares the calculated Hash value with the Pre_Hash value in the second block. If the Hash value is different from the Pre_Hash value in the second block, it is determined that the test device has been tampered with. If the Hash value is the same as the Pre_Hash value in the second block, it is determined that the test device has not been tampered with.

[0160] Backtracking point 3 is the backtracking point from the first block to the initial block, which is used to determine whether the test result matches the test request. Specifically: the server obtains the Hash value in the initial block stored on this end, and compares the Hash value in the initial block stored on this end with the Pre_Hash value in the first block. If the Hash value is different from the Pre_Hash value in the first block, it is determined that the evidence chain has been tampered with (because the client and the server both store the same initial block). If the Hash value is the same as the Pre_Hash value in the first block, it is determined that the evidence chain has not been tampered with and the test result has not been tampered with.

[0161] For example, taking the test result file being tampered as an example, combined with Figure 8 , the determination process of anti-tampering of test results is introduced in detail.

[0162] Depend on Figure 8 It can be seen that the original test result file A is uploaded to the server after being tampered with on the client. After the server receives the tampered test result file A and the test evidence chain uploaded by the client, it starts the backtracking process of the evidence chain.

[0163] (1) Compare the Pre_Hash field value in the third block with the Hash field value in the second block. If the two are equal, it proves that this section of the evidence chain has not been tampered with;

[0164] (2) Calculate the fingerprint information of the test result file A (which has been tampered with) received by the server, and calculate the hash value of the fingerprint to obtain Hash1;

[0165] (3) Obtain the Hash field value in the second block to obtain Hash2;

[0166] The value of Hash2 is automatically calculated and generated by the test executor based on the actual test result file.

[0167] (4) By comparison, we know that Hash1≠Hash2, which means that the test result file A has been tampered with.

[0168] The above steps (1) to (4) correspond to backtracking point 1.

[0169] (5) Compare the Pre_Hash field value in the second block with the Hash field value in the first block. If the two are equal, it proves that this section of the evidence chain has not been tampered with;

[0170] (6) Obtain the value of the Data field in the first block and obtain device A;

[0171] (7) Obtain the Data field value in the initial block stored on the server, parse the device information, and obtain device A`;

[0172] (8) By comparison, we can see that device A = device A`, which means that the test device has not been tampered with.

[0173] The above steps (5) to (8) correspond to backtracking point 2.

[0174] (9) Read the initial block in the test evidence chain and compare the Data field value with the initial block saved by the server. When the Data field values ​​of the two are the same, it can be known that the test evidence chain has not been tampered with and the test application has not been tampered with.

[0175] For example, Fig. 9 FIG. 1 shows a system architecture diagram of a certification test provided by an embodiment of the present application. Fig. 9As shown, in the system architecture, the server includes a certification test application service module 910 and a certification test review service module 920; the client includes a test suite 930 and a test management module 940; wherein, the certification test application service module 910 includes a certification application management module 911, a test suite management module 912 and a certification information management module 913, the certification test review service module 920 includes an evidence chain management module 921, a result final review module 922 and a certification certificate issuance management module 923, the test suite 930 includes a test executor 931, an evidence chain processing module 932 and a test case package 933, and the test management module 940 includes a test log management module 941, a result upload module 942 and a test equipment management module 943.

[0176] Specifically:

[0177] The authentication application management module 911 is used to receive a first test application sent by the server, and is also used to approve the first test application sent by the server.

[0178] The first test application is used to request an authentication test for the first device, and the first test application carries the name information of the three-party partner and the device model information of the first device.

[0179] The first device is the device under test.

[0180] The test suite management module 912 is used to download the test suite and send the test suite to the client.

[0181] The authentication information management module 913 is used to maintain / view the authentication information of the three-party partners (for example, the name information of the three-party partners and the device model information of the first device, etc.).

[0182] The evidence chain management module 921 is used to store the three-party partner name information and the device model information of the first device after receiving the first test application, and generate a first random number, and generate an initial block according to the first random number, the three-party partner name information and the device model information of the first device; it is also used to distribute the initial block to the client; it is also used to test the backtracking judgment of the evidence chain (that is, the anti-tampering judgment of the test result).

[0183] The result final review module 922 is used to approve or reject the test results.

[0184] For example: when the test result has not been tampered with, the test result is determined to be approved; when the test result has been tampered with, the test result is rejected.

[0185] The authentication certificate issuance management module 923 is used to test the issuance, display or life cycle maintenance of authentication certificates.

[0186] The test executor 931 is used to install the received test case package in the first device (ie, the device under test), start the certification test, and generate a test result file.

[0187] The evidence chain processing module 932 is used to record key evidence information of the test sub-process (for example, the device model information of the first device read, etc.) into the test evidence chain during the test execution of the test executor.

[0188] Test case package 933, test cases for certification testing.

[0189] The test log management module 941 is used for recording and / or compressing test logs.

[0190] The result uploading module 942 is used to upload the test result file and the test evidence chain file to the server.

[0191] The test device management module 943 is used to provide a driver for connecting to the first device (ie, the device under test).

[0192] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0193] For example, Fig.10 FIG. 1 is a schematic flow chart of an authentication test apparatus 1000 provided in an embodiment of the present application. Fig.10 As shown, the device 1000 includes a client and a server, wherein the client includes a first transceiver module 1010, a test execution module 1020 and a second generation module 1030; the server includes a second transceiver module 1040, a storage module 1050, a first generation module 1060 and a determination module 1070. Specifically:

[0194] The first transceiver module 1010 is used to send a first test request to the server.

[0195] The first test application carries the name information of the three-party partners and the device model information of the first device.

[0196] The first device is the device under test.

[0197] The second transceiver module 1040 is used to receive a first test application.

[0198] The storage module 1050 is used to store the name information of the three-party partners and the device model information of the first device carried in the first test application.

[0199] The first generating module 1060 is used to generate a first random number, and generate an initial block according to the first random number, the name information of the three-party partners, and the device model information of the first device.

[0200] The second transceiver module 1040 is further used to send the test suite and the generated initial block to the client.

[0201] The test suite includes test cases and test execution devices.

[0202] The test execution module 1020 is configured to test the first device based on the test suite.

[0203] The second generating module 1030 is used to generate a test result file after the test is completed.

[0204] The second generating module 1030 is further used to generate a test evidence chain during the testing process based on the initial block.

[0205] The test evidence chain includes an initial block, a first block, a second block, and a third block. The initial block records the first random number, the name information of the three-party partner, and the device model information of the first device; the first block records the device model information of the first device read by the client from the first device when the authentication test is started; the second block records the fingerprint information calculated according to the test result file generated during the authentication test; and the third block records the device model information of the first device read by the client from the first device when the authentication test is completed.

[0206] The first transceiver module 1010 is also used to send the test result file and the test evidence chain to the server.

[0207] The determination module 1070 is used to perform backtracking according to the test result file and the test evidence chain after receiving the test result file and the test evidence chain sent by the client, and then determine whether the test result has been tampered with.

[0208] In an embodiment of the present application, a test evidence chain can be generated on the client side based on the test process, and the server side performs tampering judgment based on the test evidence chain after the test is completed. The test evidence chain is all generated locally on the client side, which is equivalent to having an offline anti-tampering function, and the client and the server do not need to interact frequently; and the generated test evidence chain includes multiple evidence blocks that record "test result files", "test equipment information", and "test applications" during the test process, so that the server side can not only identify tampering of the test result files, but also identify tampering of the "test equipment information" and "test applications", which can expand the scope of anti-tampering protection of the test results.

[0209] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0210] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0211] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0212] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0213] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0214] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0215] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for certification testing, characterized in that: The method comprises: Sending a first test application to the server, where the first test application carries the first name information and the device model information of the first device; receiving an initial block sent by the server, where the initial block is generated by the server according to a first random number, the first name information, and device model information of the first device; generating a test result file and a test evidence chain during the authentication test of the first device, wherein the test evidence chain is generated based on the initial block; The test result file and the test evidence chain are sent to the server, and the test result file and the test evidence chain are used by the server to determine whether the test result has been tampered with.

2. The method according to claim 1, characterized in that The generating of a test result file and a test evidence chain during the process of performing an authentication test on the first device includes: When the test is started, generating a first block by reading device model information of the first device; When the test is completed, generating the test result file, and generating the second block according to the test result file; After the test is completed, generating a third block by reading the device model information of the first device; The test evidence chain is generated by sequentially connecting the initial block, the first block, the second block, and the third block.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Receiving a test suite sent by the server; Perform a certification test on the first device according to the test suite.

4. A method for certification testing, characterized in that: The method comprises: Receive a first test application sent by a client, where the first test application carries first name information and device model information of a first device; Generate an initial block according to a first random number, the first name information, and the device model information of the first device; Sending the initial block to the client, where the initial block is used by the client to generate a test evidence chain; Receive the test result file and the test evidence chain sent by the client, the test evidence chain including the initial block, the first block, the second block and the third block, wherein the first block includes the device model information of the first device read when the test is started, the second block includes the fingerprint information of the test result file generated when the test is completed, and the third block includes the device model information of the first device read after the test is completed, and the initial block, the first block, the second block and the third block are sequentially connected in series; Determine whether the test result has been tampered with based on the test result file and the test evidence chain.

5. The method according to claim 4, characterized in that The determining whether the test result has been tampered with according to the test result file and the test evidence chain includes: It is determined whether the fingerprint information of the test result file received from the client is the same as the fingerprint information of the test result file in the second block. If they are the same, it is determined that the test result file received from the client has not been tampered with.

6. The method according to claim 4 or 5, characterized in that: The determining whether the test result has been tampered with according to the test result file and the test evidence chain also includes: It is determined whether the device model information of the first device stored in the server is the same as the device model information of the first device in the first block. If they are the same, it is determined that the device under test has not been tampered with.

7. The method according to any one of claims 4 to 6, characterized in that The determining whether the test result has been tampered with according to the test result file and the test evidence chain also includes: Determine whether the initial block stored in the server is the same as the initial block in the test evidence chain. If they are the same, determine that the test result matches the first test application.

8. The method according to any one of claims 4 to 7, characterized in that The method further comprises: The first name information and the device model information of the first device are stored.

9. The method according to any one of claims 4 to 8, characterized in that The method further comprises: A test suite is sent to the client, where the test suite is used by the client to perform an authentication test on the first device.

10. A certification test device, characterized in that: The device comprises: A first transceiver module is used to send a first test application to the server, where the first test application carries first name information and device model information of the first device; The first transceiver module is further used to receive an initial block sent by the server, where the initial block is generated by the server according to the first random number, the first name information, and the device model information of the first device; A second generating module, configured to generate a test result file and a test evidence chain during the process of performing an authentication test on the first device, wherein the test evidence chain is generated based on the initial block; The first transceiver module is further used to send the test result file and the test evidence chain to the server, and the test result file and the test evidence chain are used by the server to determine whether the test result has been tampered with.

11. The device according to claim 10, characterized in that The second generating module is specifically used for: When the test is started, generating a first block by reading device model information of the first device; When the test is completed, generating the test result file, and generating the second block according to the test result file; After the test is completed, generating a third block by reading the device model information of the first device; The test evidence chain is generated by sequentially connecting the initial block, the first block, the second block, and the third block.

12. The device according to claim 10 or 11, characterized in that The first transceiver module is also used for: Receiving a test suite sent by the server; The device also includes: A test execution module is used to perform a certification test on the first device according to the test suite.

13. A certification test device, characterized in that: The device comprises: A second transceiver module is used to receive a first test application sent by a client, where the first test application carries first name information and device model information of a first device; A first generating module, configured to generate an initial block according to a first random number, the first name information, and device model information of the first device; The second transceiver module is further used to send the initial block to the client, where the initial block is used by the client to generate a test evidence chain; The second transceiver module is further used to receive the test result file and the test evidence chain sent by the client, wherein the test evidence chain includes the initial block, the first block, the second block and the third block, wherein the first block includes the device model information of the first device read when the test is started, the second block includes the fingerprint information of the test result file generated when the test is completed, and the third block includes the device model information of the first device read after the test is completed, and the initial block, the first block, the second block and the third block are sequentially connected in series; A determination module is used to determine whether the test result has been tampered with based on the test result file and the test evidence chain.

14. The device according to claim 13, characterized in that The determination module is specifically used for: It is determined whether the fingerprint information of the test result file received from the client is the same as the fingerprint information of the test result file in the second block. If they are the same, it is determined that the test result file received from the client has not been tampered with.

15. The device according to claim 13 or 14, characterized in that The determination module is also specifically used for: It is determined whether the device model information of the first device stored in the server is the same as the device model information of the first device in the first block. If they are the same, it is determined that the device under test has not been tampered with.

16. The device according to any one of claims 13 to 15, characterized in that The determination module is also specifically used for: Determine whether the initial block stored in the server is the same as the initial block in the test evidence chain. If they are the same, determine that the test result matches the first test application.

17. The device according to any one of claims 13 to 16, characterized in that The device also includes: A storage module is used to store the first name information and the device model information of the first device.

18. The device according to any one of claims 13 to 17, characterized in that The second transceiver module is also used for: A test suite is sent to the client, where the test suite is used by the client to perform an authentication test on the first device.

19. A system for certification testing, the system comprising: The device as claimed in any one of claims 10 to 13, and / or A device as claimed in any one of claims 14 to 18.

20. An electronic device, characterized in that: include: one or more processors; one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and the one or more computer programs include instructions, which, when executed by the one or more processors, enable the electronic device to perform the method as described in any one of claims 1 to 3, or, to perform the method as described in any one of claims 4 to 9.

21. A computer-readable storage medium, characterized in that: The storage medium stores a program or an instruction. When the program or the instruction is executed, the method according to any one of claims 1 to 3 is implemented, or the method according to any one of claims 4 to 9 is implemented.

22. A chip, characterized in that: include: one or more processors; One or more memories, the one or more processors are coupled to the one or more memories, and are used to read and execute instructions in the one or more memories to perform the method as claimed in any one of claims 1 to 3, or to perform the method as claimed in any one of claims 4 to 9.

23. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is executed, the method according to any one of claims 1 to 3 is implemented, or the method according to any one of claims 4 to 9 is implemented.

Images