A fingerprint module factory testing method, apparatus, and computer-readable storage medium

Abstract

This invention discloses a fingerprint module factory testing method, device, and computer-readable storage medium. The method includes: creating an initial password verification factor for the device in the fingerprint module's factory testing mode; setting the device's password to a preset keystore based on the initial password verification factor; when the device's password is successfully set, recording a test value of 1 through a corresponding system attribute; verifying the initial password verification factor and the keystore to obtain verification response body parameters; if the verification response body parameters are not empty, obtaining the verification token of the verification response body, and using the verification token to enable fingerprint verification of the device. This provides an efficient fingerprint module factory testing scheme, greatly simplifying the testing steps for fingerprint modules in smart devices, reducing labor and time costs, and improving productivity.

Description

Technical Field

[0001] This invention relates to the field of mobile communications, and more particularly to a fingerprint module factory testing method, apparatus, and computer-readable storage medium. Background Technology

[0002] In existing technologies, with the continuous development of smart terminal devices, the production and testing efficiency of these devices also needs to be further improved. In particular, when conducting factory testing on fingerprint modules for smart terminal devices, due to the fingerprint security mechanism of the operating system, it is necessary to first manually set a password lock in the system settings, and then manually verify the password lock in the verification interface before the fingerprint module testing can begin. It can be seen that this process of manually setting and verifying the password lock by testers is time-consuming (generally requiring more than ten seconds).

[0003] In scenarios requiring large-scale, routine fingerprint module verification, the aforementioned time consumption will severely impact the production and testing efficiency of smart terminal devices. Summary of the Invention

[0004] To address the aforementioned technical deficiencies in the prior art, this invention proposes a factory testing method for fingerprint modules, comprising:

[0005] In the factory test mode of the fingerprint module, an initial password verification factor for the device is created, and the device password is set to the preset key library according to the initial password verification factor. When the device password is successfully set, the test value is recorded as 1 through the corresponding system attribute.

[0006] Verify the initial password verification factor with the key library to obtain the verification response body parameters. If the verification response body parameters are not empty, obtain the verification token of the verification response body and enable fingerprint verification of the device through the verification token.

[0007] Fingerprint data is collected through the fingerprint verification and the verification result of the fingerprint data is monitored. If the verification is successful or the fingerprint verification is terminated normally, the test value is recorded as 0 when the key library is successfully erased. If the verification fails or the fingerprint verification is terminated abnormally, the test value is recorded as 1.

[0008] If the test value is detected as 1 when the device is in the initialization phase of restarting, the keystore is erased by deleting the preset password file.

[0009] Optionally, the step of creating an initial password verification factor for the device in the factory test mode of the fingerprint module, and setting the device's password to a preset keystore according to the initial password verification factor, and when the device's password is successfully set, recording the test value as 1 through the corresponding system attribute, includes:

[0010] Control the device to enter the factory test mode of the fingerprint module.

[0011] In the factory test mode, an initial password verification factor for LockscreenCredential is created, and a preset password is set to the preset keystore through the LockPatternUtils lock screen module.

[0012] Optionally, the step of creating an initial password verification factor for the device in the factory test mode of the fingerprint module, setting the device's password to a preset keystore according to the initial password verification factor, and recording the test value as 1 through the corresponding system attribute when the device's password is successfully set, further includes:

[0013] When the password is set successfully, the test value of factory.test.fingerprint.setlock is recorded as 1 through the SystemProperties system property.

[0014] When the password setting fails, the test value of factory.test.fingerprint.setlock is recorded as 0 through the SystemProperties system property.

[0015] Optionally, the step of verifying the initial password verification factor and the keystore to obtain verification response body parameters, and if the verification response body parameters are not empty, obtaining the verification token of the verification response body, and using the verification token to enable fingerprint verification of the device, includes:

[0016] Verify the keystore using the LockscreenCredential initial password verification factor.

[0017] Obtain the VerifyCredentialResponse body based on the verification result.

[0018] Optionally, the step of verifying the initial password verification factor and the key library to obtain verification response body parameters, and if the verification response body parameters are not empty, obtaining the verification token of the verification response body and enabling fingerprint verification of the device through the verification token, further includes:

[0019] If the VerifyCredentialResponse body is not empty, then obtain the Token verification token from the VerifyCredentialResponse body.

[0020] Fingerprint verification of the device is enabled by verifying the token.

[0021] Optionally, the step of collecting fingerprint data through fingerprint verification and monitoring the verification result of the fingerprint data, if the verification is successful or the fingerprint verification terminates normally, then when the keystore erasure is successful, the test value is recorded as 0; if the verification fails or the fingerprint verification terminates abnormally, then the test value is recorded as 1, including:

[0022] The device generates a prompt message on the screen indicating that a finger should be pressed, and initiates the interaction between the enrollment module and the fingerprint module by calling startEnrollment, so as to transmit and collect the fingerprint data.

[0023] Register a fingerprint module result callback listener using FingerprintManager.EnrollmentCallback and wait for the verification result.

[0024] Optionally, the step of collecting fingerprint data through the fingerprint verification and monitoring the verification result of the fingerprint data, and recording the test value as 0 when the key library erasure is successful if the verification is successful or the fingerprint verification terminates normally, and recording the test value as 1 if the verification fails or the fingerprint verification terminates abnormally, further includes:

[0025] If the verification passes or the fingerprint verification terminates normally, the test value of factory.test.fingerprint.setlock will be set to 0 when the keystore keybase is successfully erased.

[0026] If the verification fails or the fingerprint verification terminates abnormally, the test value of factory.test.fingerprint.setlock will be set to 1.

[0027] Optionally, if the test value is detected as 1 during the device's restart initialization phase, the keystore is erased by deleting a preset password file, including:

[0028] During the initialization phase of the system interface of the device, the test value of factory.test.fingerprint.setlock is detected.

[0029] If the test value of factory.test.fingerprint.setlock is 0, then the factory test mode of the fingerprint module is exited. If the test value of factory.test.fingerprint.setlock is 1, then the files / data / system / locksettings.db, / data / system / locksettings.db-shm, / data / system / locksettings.db-wal, / data / system / gatekeeper.password.key, / data / system / gatekeeper.pattern.key, / data / system / fingerprintpassword.key, / data / system / personal.key, / data / system / gesture.key, and / data / system / password.key are deleted, and the factory test mode of the fingerprint module is exited.

[0030] The present invention also proposes a fingerprint module factory testing device, the device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the fingerprint module factory testing method as described in any of the preceding claims.

[0031] The present invention also proposes a computer-readable storage medium storing a fingerprint module factory test program, which, when executed by a processor, implements the steps of the fingerprint module factory test method as described in any of the preceding claims.

[0032] The fingerprint module factory testing method, device, and computer-readable storage medium of this invention create an initial password verification factor for the device in the factory testing mode of the fingerprint module, and set the device's password to a preset key library according to the initial password verification factor. When the device password is successfully set, the test value is recorded as 1 through the corresponding system attribute. The initial password verification factor and the key library are verified to obtain verification response body parameters. If the verification response body parameters are not empty, the verification token of the verification response body is obtained, and the fingerprint verification of the device is started through the verification token. Fingerprint data is collected through the fingerprint verification, and the verification result of the fingerprint data is monitored. If the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the key library is successfully erased. If the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1. When the device is in the initialization phase of restarting, if the test value is detected as 1, the key library is erased by deleting the preset password file. This provides an efficient fingerprint module factory testing scheme, greatly simplifies the testing steps of fingerprint modules for smart devices, reduces labor and time costs, and improves productivity. Attached Figure Description

[0033] The present invention will be further described below with reference to the accompanying drawings and embodiments. In the accompanying drawings:

[0034] Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal according to the present invention;

[0035] Figure 2 This is a communication network system architecture diagram provided in an embodiment of the present invention;

[0036] Figure 3 This is a first flowchart of the first embodiment of the fingerprint module factory testing method of the present invention;

[0037] Figure 4 This is a second flowchart of a second embodiment of the fingerprint module factory testing method of the present invention;

[0038] Figure 5 This is the third flowchart of the second embodiment of the fingerprint module factory testing method of the present invention;

[0039] Figure 6 This is the fourth flowchart of the second embodiment of the fingerprint module factory testing method of the present invention;

[0040] Figure 7 This is the fifth flowchart of the second embodiment of the fingerprint module factory testing method of the present invention;

[0041] Figure 8 This is the sixth flowchart of the second embodiment of the fingerprint module factory testing method of the present invention;

[0042] Figure 9 This is the seventh flowchart of the second embodiment of the fingerprint module factory testing method of the present invention;

[0043] Figure 10 This is the eighth flowchart of the second embodiment of the fingerprint module factory testing method of the present invention. Detailed Implementation

[0044] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0045] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0046] Terminals can be implemented in various forms. For example, the terminals described in this invention may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.

[0047] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to embodiments of the present invention can also be applied to fixed-type terminals.

[0048] Please see Figure 1 This is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of the present invention. The mobile terminal 100 may include: an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that... Figure 1 The mobile terminal structure shown does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0049] The following is combined Figure 1 A detailed introduction to each component of the mobile terminal:

[0050] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, and a duplexer. Furthermore, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), and TDD-LTE (Time Division Duplexing-Long Term Evolution).

[0051] WiFi is a short-range wireless transmission technology. Mobile terminals using the WiFi module 102 can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 1 WiFi module 102 is shown, but it is understood that it is not a necessary component of a mobile terminal and can be omitted as needed without changing the nature of the invention.

[0052] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, etc. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0053] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0054] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0055] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0056] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands from processor 110. In addition, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Specifically, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being limited here.

[0057] Furthermore, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 based on the type of touch event. Although in Figure 1 In this embodiment, the touch panel 1071 and the display panel 1061 are two independent components to realize the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0058] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more elements within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0059] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0060] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0061] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0062] although Figure 1 As not shown, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0063] To facilitate understanding of the embodiments of the present invention, the communication network system on which the mobile terminal of the present invention is based is described below.

[0064] Please see Figure 2 , Figure 2 This invention provides a communication network system architecture diagram. The communication network system is an LTE system based on the universal mobile communication technology. The LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and the operator's IP services 204, which are connected in sequence.

[0065] Specifically, UE201 can be the aforementioned terminal 100, which will not be elaborated here.

[0066] E-UTRAN202 includes eNodeB2021 and other eNodeB2022s. Among them, eNodeB2021 can connect to other eNodeB2022s via backhaul (e.g., X2 interface), and eNodeB2021 connects to EPC203. eNodeB2021 can provide UE201 with access to EPC203.

[0067] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gateway) 2034, PGW (Packet Data Network Gateway) 2035, and PCRF (Policy and Charging Rules Function) 2036, etc. Among them, MME2031 is the control node that handles signaling between UE201 and EPC203, providing bearer and connection management. HSS2032 provides registers to manage functions such as the Home Location Register (not shown in the diagram) and stores user-specific information such as service characteristics and data rates. All user data can be sent through SGW2034. PGW2035 can provide UE 201 IP address allocation and other functions. PCRF2036 is the policy and charging control decision point for service data flow and IP bearer resources. It selects and provides available policy and charging control decisions for the policy and charging enforcement function unit (not shown in the figure).

[0068] IP services 204 may include the Internet, intranet, IMS (IP Multimedia Subsystem), or other IP services.

[0069] Although the above description uses the LTE system as an example, those skilled in the art should understand that the present invention is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems, etc., which are not limited here.

[0070] Based on the aforementioned mobile terminal hardware structure and communication network system, various embodiments of the method of the present invention are proposed.

[0071] Example 1

[0072] Figure 3 This is a flowchart of the first embodiment of the fingerprint module factory testing method of the present invention. A fingerprint module factory testing method, the method comprising:

[0073] S1. In the factory test mode of the fingerprint module, create the initial password verification factor of the device, and set the password of the device to the preset key library according to the initial password verification factor. When the password of the device is successfully set, record the test value as 1 through the corresponding system attribute.

[0074] S2. Verify the initial password verification factor and the key library to obtain the verification response body parameters. If the verification response body parameters are not empty, obtain the verification token of the verification response body and enable fingerprint verification of the device through the verification token.

[0075] S3. Collect fingerprint data through the fingerprint verification and monitor the verification result of the fingerprint data. If the verification is successful or the fingerprint verification ends normally, the test value is recorded as 0 when the key library is successfully erased. If the verification fails or the fingerprint verification ends abnormally, the test value is recorded as 1.

[0076] S4. When the device is in the initialization phase of restarting, if the test value is detected as 1, the key database is erased by deleting the preset password file.

[0077] In this embodiment, the existing fingerprint module testing scheme is broken down into six steps: Step 1: Enter the system settings interface and find the password setting option (manual operation); Step 2: Set the password, which can be a numeric password, pattern password, etc. (manual operation); Step 3: Confirm the password. Repeatedly enter the password to confirm (manual operation); Step 4: Exit the settings interface and enter the fingerprint testing interface (manual operation); Step 5: Press your finger according to the prompts (manual operation); Step 6: Display the test results. It can be seen that the existing fingerprint module testing scheme involves many manual steps, which is time-consuming. Therefore, the solution in this embodiment is to simulate manual operation and automatically set and verify the password lock, thus eliminating the manual setting step. It can be seen that since factory mode testing involves large-scale repetitive testing, saving more than ten seconds in this step can greatly improve production testing efficiency.

[0078] In this embodiment, if the fingerprint test fails and the password lock is not erased in time, or if the password lock is not completely erased, the device will require a password to be entered after restarting. However, the factory testers may not know the password, and sometimes the original password cannot unlock the device. In this case, the device cannot be used and requires a re-flashing, which causes considerable trouble for factory mode testing. Therefore, the solution in this embodiment is to record abnormal scenarios during fingerprint testing. When the device restarts, if the recorded fingerprint test anomaly is detected, the password lock is automatically erased, thus restoring the phone to its state before testing.

[0079] As can be seen, in this embodiment, the optimized fingerprint testing process makes the testing steps simpler and clearer for testers. Testers no longer need to configure the system settings interface to ensure the preconditions for testing, thereby greatly improving the testing experience.

[0080] Optionally, in this embodiment, for various engineering modes, when there are some test items that require manual configuration before they can be performed, similar optimization schemes as described above can be adopted to automate some manual configuration processes through the above schemes.

[0081] The beneficial effects of this embodiment are as follows: By creating an initial password verification factor for the device in the factory test mode of the fingerprint module, and setting the device password to a preset key library according to the initial password verification factor, when the device password is successfully set, the test value is recorded as 1 through the corresponding system attribute; the initial password verification factor and the key library are verified to obtain the verification response body parameter. If the verification response body parameter is not empty, the verification token of the verification response body is obtained, and the fingerprint verification of the device is started through the verification token; fingerprint data is collected through the fingerprint verification, and the verification result of the fingerprint data is monitored. If the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the key library is successfully erased; if the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1; when the device is in the initialization phase of restarting, if the test value is detected as 1, the key library is erased by deleting the preset password file. This achieves an efficient fingerprint module factory testing scheme, greatly simplifies the testing steps of fingerprint modules for smart devices, reduces labor and time costs, and improves productivity.

[0082] Example 2

[0083] Based on the above embodiments, please refer to Figure 4The process involves creating an initial password verification factor for the device in the factory test mode of the fingerprint module, setting the device's password to a preset keystore based on the initial password verification factor, and recording the test value as 1 through the corresponding system attributes when the device password is successfully set. This includes:

[0084] S11. Control the device to enter the factory test mode of the fingerprint module.

[0085] S12. In the factory test mode, create an initial password verification factor for LockscreenCredential, and set a preset password to the preset keystore through the LockPatternUtils lock screen module.

[0086] Based on the above embodiments, please refer to Figure 5 The step of creating an initial password verification factor for the device in the factory test mode of the fingerprint module, and setting the device's password to a preset keystore according to the initial password verification factor, and recording the test value as 1 through the corresponding system attribute when the device password is successfully set, also includes:

[0087] S13. When the password is successfully set, the test value of factory.test.fingerprint.setlock is recorded as 1 through the SystemProperties system property.

[0088] S14. When the password setting fails, the test value of factory.test.fingerprint.setlock is recorded as 0 through the SystemProperties system property.

[0089] Based on the above embodiments, please refer to Figure 6 The process of verifying the initial password verification factor and the key library to obtain verification response body parameters, and if the verification response body parameters are not empty, obtaining the verification token of the verification response body, and using the verification token to enable fingerprint verification of the device, includes:

[0090] S21. Verify the keystore using the LockscreenCredential initial password verification factor.

[0091] S22. Obtain the VerifyCredentialResponse body based on the verification result.

[0092] Based on the above embodiments, please refer to Figure 7The step of verifying the initial password verification factor and the key library to obtain verification response body parameters, and if the verification response body parameters are not empty, obtaining the verification token of the verification response body, and using the verification token to enable fingerprint verification of the device, further includes:

[0093] S23. If the VerifyCredentialResponse body is not empty, then obtain the Token verification token from the VerifyCredentialResponse body.

[0094] S24. Enable fingerprint verification of the device using a token verification token.

[0095] Based on the above embodiments, please refer to Figure 8 The process involves collecting fingerprint data through fingerprint verification and monitoring the verification result of the fingerprint data. If the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the keystore erasure is successful. If the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1. This includes:

[0096] S31. Generate a prompt message for pressing a finger on the screen of the device, and start the interaction between the enrollment module and the fingerprint module by calling startEnrollment to transmit and collect the fingerprint data.

[0097] S32. Register a fingerprint module result callback listener through FingerprintManager.EnrollmentCallback and wait for the verification result.

[0098] Based on the above embodiments, please refer to Figure 9 The process of collecting fingerprint data through fingerprint verification and monitoring the verification result of the fingerprint data, wherein if the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the key library is successfully erased; and if the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1, further includes:

[0099] S33. If the verification passes or the fingerprint verification terminates normally, the test value of factory.test.fingerprint.setlock is recorded as 0 when the keystore key database is successfully erased.

[0100] S34. If the verification fails or the fingerprint verification terminates abnormally, the test value of factory.test.fingerprint.setlock is recorded as 1.

[0101] Based on the above embodiments, please refer to Figure 10When the device is in the initialization phase of a restart, if the test value is detected as 1, the key store is erased by deleting a preset password file, including:

[0102] S41. During the initialization phase of the system interaction interface of the device, the test value of factory.test.fingerprint.setlock is detected.

[0103] S42. If the test value of factory.test.fingerprint.setlock is 0, then exit the factory test mode of the fingerprint module. If the test value of factory.test.fingerprint.setlock is 1, then delete the files / data / system / locksettings.db, / data / system / locksettings.db-shm, / data / system / locksettings.db-wal, / data / system / gatekeeper.password.key, / data / system / gatekeeper.pattern.key, / data / system / fingerprintpassword.key, / data / system / personal.key, / data / system / gesture.key, and / data / system / password.key, and exit the factory test mode of the fingerprint module.

[0104] The beneficial effects of this embodiment are as follows: By creating an initial password verification factor for the device in the factory test mode of the fingerprint module, and setting the device password to a preset key library according to the initial password verification factor, when the device password is successfully set, the test value is recorded as 1 through the corresponding system attribute; the initial password verification factor and the key library are verified to obtain the verification response body parameter. If the verification response body parameter is not empty, the verification token of the verification response body is obtained, and the fingerprint verification of the device is started through the verification token; fingerprint data is collected through the fingerprint verification, and the verification result of the fingerprint data is monitored. If the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the key library is successfully erased; if the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1; when the device is in the initialization phase of restarting, if the test value is detected as 1, the key library is erased by deleting the preset password file. This achieves an efficient fingerprint module factory testing scheme, greatly simplifies the testing steps of fingerprint modules for smart devices, reduces labor and time costs, and improves productivity.

[0105] Example 3

[0106] Based on the above embodiments, the present invention also proposes a fingerprint module factory testing device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps of the fingerprint module factory testing method as described in any of the above embodiments.

[0107] It should be noted that the above-described device embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the device embodiments, which will not be repeated here.

[0108] Example 4

[0109] Based on the above embodiments, the present invention also proposes a computer-readable storage medium storing a fingerprint module factory test program, which, when executed by a processor, implements the steps of the fingerprint module factory test method as described in any of the above embodiments.

[0110] It should be noted that the above-described medium embodiments and method embodiments belong to the same concept. The specific implementation process can be found in the method embodiments, and the technical features in the method embodiments are also applicable to the medium embodiments, which will not be repeated here.

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

[0112] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0113] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0114] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims. All of these forms are within the protection scope of the present invention.

Claims

1. A factory testing method for a fingerprint module, characterized in that, The method includes: In the factory test mode of the fingerprint module, an initial password verification factor for the device is created, and the device's password is set to a preset keystore based on the initial password verification factor. When the device's password is successfully set, the test value is recorded as 1 through the corresponding system property. The device is controlled to enter the factory test mode of the fingerprint module. In the factory test mode, an initial password verification factor (LockscreenCredential) is created, and a preset password is set to a preset keystore through the LockPatternUtils lock screen module. When the password is successfully set, the test value of factory.test.fingerprint.setlock is recorded as 1 through the SystemProperties system property; when the password setting fails, the test value of factory.test.fingerprint.setlock is recorded as 0 through the SystemProperties system property. The initial password verification factor and the keystore are verified to obtain verification response body parameters. If the verification response body parameters are not empty, the verification token of the verification response body is obtained, and the fingerprint verification of the device is enabled through the verification token. Specifically, the keystore is verified using the LockscreenCredential initial password verification factor. The VerifyCredentialResponse verification response body is obtained based on the verification result. If the VerifyCredentialResponse verification response body is not empty, the Token verification token of the VerifyCredentialResponse verification response body is obtained. The fingerprint verification of the device is enabled through the Token verification token. Fingerprint data is collected through fingerprint verification, and the verification result of the fingerprint data is monitored. If the verification is successful or the fingerprint verification terminates normally, the test value is recorded as 0 when the keystore is successfully erased; if the verification fails or the fingerprint verification terminates abnormally, the test value is recorded as 1. Specifically, a finger-pressing prompt is generated on the device screen, and the interaction between the enrollment module and the fingerprint module is initiated by calling `startEnrollment` to transmit and collect the fingerprint data. A fingerprint module result callback listener is registered through `FingerprintManager.EnrollmentCallback` to wait for the verification result. If the verification is successful or the fingerprint verification terminates normally, the `factory.test.fingerprint.setlock` test value is recorded as 0 when the keystore is successfully erased; if the verification fails or the fingerprint verification terminates abnormally, the `factory.test.fingerprint.setlock` test value is recorded as 1. When the device is in the initialization phase of a restart, if the test value is detected as 1, the keystore is erased by deleting the preset password file. Specifically, during the initialization phase of the device's system interface, the factory.test.fingerprint.setlock test value is checked. If the factory.test.fingerprint.setlock test value is 0, the factory test mode of the fingerprint module is exited. If the factory.test.fingerprint.setlock test value is 1, the files / data / system / locksettings.db, / data / system / locksettings.db-shm, / data / system / locksettings.db-wal, / data / system / gatekeeper.password.key, / data / system / gatekeeper.pattern.key, / data / system / fingerprintpassword.key, / data / system / personal.key, / data / system / gesture.key, and / data / system / password.key are deleted, and the factory test mode of the fingerprint module is exited.

2. A fingerprint module factory testing device, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the fingerprint module factory testing method as described in claim 1.

3. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a fingerprint module factory test program, which, when executed by a processor, implements the steps of the fingerprint module factory test method as described in claim 1.

Images