An identity authentication method and device

Abstract

This specification provides an authentication method that verifies a user's identity based on multiple sets of touch data generated on a touch device. Each set of touch data includes the coordinates of multiple touch points generated by the user's touch actions at the same time, with each set of touch data generated at different times. Using the first set of touch data acquired initially, the touch areas corresponding to each finger are determined. For each subsequent set of touch data acquired, multiple touch areas corresponding to that set are determined, and the finger touch state corresponding to that set is determined based on the difference between that set of touch data and the first set of touch data. The finger touch states corresponding to each subsequent set of touch data are then used to form a sequence of touch actions to be verified according to their respective acquisition times. This sequence of touch actions to be verified is compared with a preset sequence of valid touch actions. Based on the comparison result, it is determined whether the current user has passed authentication.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of communication technology, and in particular to an authentication method and apparatus. Background Technology

[0002] In real life, there are many scenarios that require identity verification, such as when making payments with a mobile phone, unlocking the phone screen, or retrieving a password.

[0003] Identity verification has become a common occurrence in life, and there is a need for more diverse identity verification methods for users to choose from, thereby improving the user experience. Summary of the Invention

[0004] In view of the above, one or more embodiments of this specification provide an authentication method and apparatus.

[0005] To achieve the above objectives, one or more embodiments of this specification provide the following technical solutions:

[0006] According to a first aspect of one or more embodiments of this specification, an authentication method is provided for verifying the identity of a user based on multiple sets of touch data generated by the user on a touch device, wherein each set of touch data includes multiple touch point coordinates generated by the user's touch behavior at the same time, and each set of touch data is generated at different times; the method includes:

[0007] Using the first set of touch data acquired initially, the fingers and touch areas corresponding to this set of data are determined;

[0008] For each set of touch data subsequently acquired: determine the multiple touch areas corresponding to the set of data, and determine the finger touch state corresponding to the set of data based on the difference between the set of data and the first set of data;

[0009] The finger touch states corresponding to each set of touch data acquired subsequently are used to form a sequence of touch behaviors to be verified according to the corresponding acquisition time.

[0010] The sequence of touch behaviors to be verified is compared with a preset sequence of valid touch behaviors, and the user's authentication status is determined based on the comparison result.

[0011] According to a second aspect of one or more embodiments of this specification, an authentication device is provided for verifying the identity of a user based on multiple sets of touch data generated by the user on a touch device, wherein each set of touch data includes multiple touch point coordinates generated by the user's touch behavior at the same time, and each set of touch data is generated at different times; the device includes:

[0012] The touch area determination module is used to determine each finger and touch area corresponding to the first set of touch data acquired for the first time.

[0013] The touch state determination module is used to determine multiple touch areas corresponding to each set of touch data acquired subsequently, and to determine the finger touch state corresponding to the set of data based on the difference between the set of data and the first set of data.

[0014] The behavior sequence determination module is used to form a touch behavior sequence to be verified by taking the finger touch state corresponding to each set of touch data acquired subsequently and according to the corresponding acquisition time.

[0015] The comparison module is used to compare the touch behavior sequence to be verified with a preset legal touch behavior sequence, and determine whether the current user has passed the authentication based on the comparison result.

[0016] According to a third aspect of one or more embodiments of this specification, an electronic device is provided, comprising:

[0017] processor;

[0018] Memory used to store processor-executable instructions;

[0019] The processor implements the authentication method as described above by running the executable instructions.

[0020] According to a fourth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the authentication method as described above.

[0021] This specification proposes a novel authentication method that verifies a user's identity based on multiple sets of touch data generated on a touch device. Each set of touch data includes the coordinates of multiple touch points generated by the user's touch actions at the same time, with each set of touch data generated at different times. Using the first set of touch data acquired initially, the touch areas corresponding to each finger are determined. For each subsequent set of touch data, multiple touch areas corresponding to that set are determined, and the finger touch state corresponding to that set is determined based on the difference between that set of touch data and the first set. The finger touch states corresponding to each subsequent set of touch data are then used to form a sequence of touch actions to be verified according to their respective acquisition times. This sequence of touch actions to be verified is compared with a preset sequence of valid touch actions. Based on the comparison result, it is determined whether the current user has passed authentication.

[0022] Using one or more embodiments of this specification, a user performs corresponding touch actions on a touch device, obtains corresponding touch data, and then determines whether the user's touch action sequence is the same as a valid touch action sequence, thereby determining whether the user's authentication is successful. Attached Figure Description

[0023] Figure 1 This is a flowchart illustrating an authentication method provided in an exemplary embodiment.

[0024] Figure 2A This is an exemplary embodiment of a schematic diagram of a touch point and a schematic diagram of the touch area corresponding to each finger.

[0025] Figure 2B This is an exemplary embodiment of another schematic diagram of touch points and a schematic diagram of the touch areas corresponding to each finger.

[0026] Figure 3 This is a schematic diagram of the structure of an authentication device provided in an exemplary embodiment.

[0027] Figure 4 This is a schematic diagram of the structure of a device provided in an exemplary embodiment. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0029] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0030] As mentioned above, there are many scenarios in life that require identity verification, and there are also various ways to verify identity. With the emergence of multi-factor authentication, the methods of identity verification have become more diversified. In order to be applicable to more application scenarios, the more identity verification methods there are, the more choices users have, and the better the user experience will be.

[0031] Based on this, this specification proposes a novel authentication method that verifies a user's identity based on multiple sets of touch data generated on a touch device. Each set of touch data includes the coordinates of multiple touch points generated by the user's touch actions at the same time, with each set of touch data generated at different times. Using the first set of touch data acquired initially, the touch areas corresponding to each finger are determined. For each subsequent set of touch data, multiple touch areas corresponding to that set are determined, and the finger touch state corresponding to that set is determined based on the difference between that set of touch data and the first set. The finger touch states corresponding to each subsequent set of touch data are then used to form a sequence of touch actions to be verified according to their respective acquisition times. This sequence of touch actions to be verified is compared with a preset sequence of valid touch actions. Based on the comparison result, it is determined whether the current user has passed authentication.

[0032] Using one or more embodiments of this specification, a user performs corresponding touch actions on a touch device, obtains corresponding touch data, and then determines whether the user's touch action sequence is the same as a valid touch action sequence, thereby determining whether the user's authentication is successful.

[0033] This specification provides an authentication method that verifies the identity of a user based on multiple sets of touch data generated by the user on a touch device, as well as the corresponding authentication device, equipment, and computer-readable storage medium.

[0034] The authentication methods will be explained in detail below.

[0035] In this manual, after a user makes a corresponding touch on the touch device, the touch device will obtain a set of touch data. The set of touch data includes multiple touch point coordinates, which are multiple touch point coordinates generated by the user's touch behavior at the same time.

[0036] Before using the authentication method shown in this manual, it is necessary to obtain the valid touch behavior sequence set by the user. The valid touch behavior sequence is either preset by the user or collected from the user in advance. If it is preset, you can set a finger code like setting a password. For example, you can number each finger, with the thumb as number 1, the index finger as number 2, the middle finger as number 3, the ring finger as number 4, and the little finger as number 5. Then, when setting the code, it can be (1,3,4,5,3). The corresponding valid touch behavior sequence is: raise the thumb → raise the middle finger → raise the ring finger → raise the little finger → raise the middle finger.

[0037] It can also be a code such as ((12), (15), (23)). Accordingly, the legal sequence of touch behavior is: raise the thumb and index finger → raise the thumb and little finger → raise the index finger and middle finger.

[0038] It can also be a code such as (2, (34), 1, 4, (15)). Accordingly, the legal sequence of touch behavior is: raise index finger → raise middle finger and ring finger → raise thumb → raise ring finger → raise thumb and little finger.

[0039] If the data is collected from the user in advance, the user can be prompted to place their hand on the touch device. Following the prompts, touch data generated by the user's touch actions is acquired in sets, resulting in a user-defined touch action sequence. Specifically, the first set of touch data is used to determine the touch areas of each finger corresponding to that set. For each subsequent set of touch data: multiple touch areas are identified, and the finger touch state is determined based on the difference between this set and the first set. The finger touch states corresponding to each subsequent set of touch data are then combined according to their acquisition times to form a touch action sequence, which serves as the touch action sequence collected from the user—that is, the valid touch action sequence. The above-mentioned touch behavior sequences (lifting thumb → lifting middle finger → lifting ring finger → lifting pinky → lifting middle finger) and (lifting thumb and index finger → lifting thumb and pinky → lifting index and middle finger) are used as the user's legitimate touch behavior sequences. When storing, the above conversion can also be performed to number each finger: thumb is number 1, index finger is number 2, middle finger is number 3, ring finger is number 4, and pinky is number 5, and then stored as a code.

[0040] Once a user's legitimate touch behavior sequence is obtained, the user can be authenticated. For example... Figure 1 The diagram shown is a flowchart of an authentication method illustrated in this specification, including the following steps:

[0041] Step 101: Using the first set of touch data obtained initially, determine each finger and touch area corresponding to this set of data.

[0042] The first set of touch data is used to determine the touch area corresponding to each finger. Therefore, when collecting the first set of touch data, all of the user's fingers need to be on the touch device. Only in this way can the touch area of ​​all fingers be obtained from the touch data generated by the touch device.

[0043] It should be noted that after a user touches the touch device with their hand, there will be many points on the touch device. The touch device can detect whether each point has been touched. When the user places their hand on the touch device, the touch device will detect the coordinates of each touched point.

[0044] The touch device and the authentication device can be integrated into one device, such as a touch screen and a mobile phone, tablet, or laptop for authentication. Alternatively, they can be set up separately, that is, a dedicated device for collecting touch data.

[0045] In this process, the touch area of ​​each finger corresponding to the first set of touch data is determined using the first set of touch data. This can be done by using a standard hand shape or by using a model.

[0046] The process of determining using a standard hand shape is as follows:

[0047] Using the coordinates of each touch point in the first set of touch data, multiple touch areas are determined from the set of touch point coordinates. The relative positions of these multiple touch areas are compared with a standard hand shape to determine the touch areas that match the relative positions of each finger, thus obtaining the touch areas corresponding to each finger.

[0048] The standard hand shape can be a general hand shape, such as a general hand shape with the five fingers spread or a general hand shape with the five fingers together. Accordingly, when acquiring the user's touch data, it is required that the user's touch behavior is either with the five fingers together or with the five fingers spread on the touch device.

[0049] Alternatively, the standard hand shape can be the user's hand shape collected in advance. When collecting the user's legal touch behavior sequence, the user's hand shape is collected at the same time. Then, using the saved user's hand shape, the touch area that matches the relative position of each finger is found among multiple touch areas.

[0050] The specific process determined using the model is as follows:

[0051] The first set of touch data is input into a pre-trained finger touch area determination model. Then, based on the output of the finger touch area determination model, the touch area corresponding to each finger is obtained.

[0052] The training process for the finger touch area determination model is as follows:

[0053] Obtain a training sample set. Each training sample includes a set of touch data containing multiple touch point coordinates. The multiple touch point coordinates in this set are the touch point coordinates generated when the user places all five fingers on the touch device at the same time, as well as the annotation of the touch area of ​​each finger.

[0054] Using the aforementioned training sample set, train the finger touch area determination model until it achieves the expected results.

[0055] like Figure 2AThe diagram shown is a schematic of the touch points shown in this specification and the touch areas of each finger determined based on the touch points. Each small black dot represents the coordinates of a touch point.

[0056] Figure 2A This description is merely an illustrative diagram of touch points and touch areas. In actual applications, the size of touch devices may be limited, so the palm area or number of fingers can be reduced accordingly. For example, a mobile phone screen cannot accommodate the entire hand, so only four fingers (index, middle, ring, and little fingers) may be placed on the screen. Therefore, when determining the touch area corresponding to each finger, only the touch area corresponding to the four fingers can be determined, and the subsequent touch behaviors will be determined for these four fingers.

[0057] like Figure 2B The diagram shown is another schematic diagram of the touch point and the touch area shown in this specification. The palm is placed on the touch device, so only the touch area corresponding to each fingertip can be determined.

[0058] The determination of the touch state of each finger corresponding to each set of touch data shown in this specification is based on the difference between the first set of touch areas and the set of touch areas. It can include the touch area corresponding to the entire finger, or the touch area corresponding to the fingertip, etc., as long as it can represent the touch state of the finger.

[0059] Step 103: For each set of touch data subsequently acquired: determine the multiple touch areas corresponding to the set of data, and determine the finger touch state corresponding to the set of data based on the difference between the set of data and the first set of data.

[0060] The first set of touch data is used for the touch areas corresponding to each finger. Each subsequent set of touch data is used to determine the touch state of a finger. When determining the touch state of a finger corresponding to each set of touch data, first determine the multiple touch areas of that set of touch data. Based on the touch areas corresponding to each finger determined in the first set, determine whether there is a corresponding touch area for each finger in the multiple touch areas determined in that set. If not, it means that the finger has not touched; if so, it means that the finger has touched.

[0061] For example, if the multiple touch areas identified in the third group are different from those in the first group, the touch area corresponding to the index finger is missing. Therefore, the finger touch state of the touch data in the third group is to lift the index finger.

[0062] Each set of touch data is compared with the first set to determine the finger touch state. During this process, the touch area corresponding to some fingers may change. For example, when a user performs a certain touch action, the touch area corresponding to the index finger in the first set might shift one touch coordinate to the left or right. This difference is negligible. However, if the touch area of ​​the index finger shifts seven or eight touch coordinates to the left or right relative to the first set, then the touch area corresponding to the index finger will not be detected. In other words, the touch action determined based on this set of touch data is incorrect.

[0063] Therefore, in one or more embodiments of this specification, when comparing the difference between the group of data and the first group of data, a threshold can be set. When the overlap of a certain area is greater than a certain percentage, the touch area corresponding to the group is considered to be the same area as the touch area of ​​the first group.

[0064] Touch state refers to the state of each finger touching the aforementioned touch device. For example, if the thumb, middle finger, ring finger, and little finger have all touched the device, but the index finger is suspended and has not touched the device, then the corresponding touch state is to lift the index finger. Or, if the thumb, middle finger, and ring finger have all touched the device, but the index finger and little finger are suspended and have not touched the device, then the corresponding touch state is to lift the index finger and little finger.

[0065] Step 105: The finger touch states corresponding to each set of touch data subsequently acquired are used to form a sequence of touch behaviors to be verified according to the corresponding acquisition time.

[0066] The acquisition time for each set of touch data is different, and the order is sorted according to the acquisition time. Therefore, the sequence of touch behavior is also sorted according to the acquisition time.

[0067] It's important to note that when a user performs a series of touch actions on a touch device, the touch areas of different parts of the hand remain relatively stable. That is, when a user verifies something on a touch device, their hand should not move relative to the device from side to side, ensuring that the touch areas corresponding to each finger are relatively fixed each time. For example, if the second set of touch actions corresponds to raising the index finger, and the third set corresponds to raising the little finger, then when the user performs the second and third sets of touch actions, the touch areas corresponding to the thumb, middle finger, ring finger, and little finger in the third set should be the same as those in the first set. Similarly, the touch areas corresponding to the thumb, index finger, middle finger, and ring finger in the third set should be the same as those in the first set. This ensures that the user's actual touch behavior can be determined when identifying the touch actions corresponding to each set of touch data.

[0068] Step 107: Compare the touch behavior sequence to be verified with the preset legal touch behavior sequence, and determine whether the current user has passed the authentication based on the comparison result.

[0069] The hand-touch behavior authentication method shown in this specification can be one step in the authentication process. If the comparison result of the touch behavior sequence to be verified is the same as the preset legal touch behavior sequence, the authentication process continues to the next step. If the comparison result is different, the user is prompted that the touch behavior sequence is incorrect.

[0070] It can also be any step of the authentication process, that is, directly using hand touch behavior for authentication. If the sequence of touch behavior to be verified is the same as the preset valid touch behavior sequence, the authentication is successful; otherwise, the authentication fails.

[0071] Since the first set of touch data is used to determine the touch area corresponding to each finger, the number of sets of touch data acquired is one number greater than the length of the legal touch behavior sequence. For example, if the length of the touch behavior sequence is 4, then five sets of touch data need to be acquired. The touch state of the finger is determined based on the touch data of the first set of touch data.

[0072] In practical applications, when a user makes a corresponding touch action on a touch device, there is a short process. When the hand is first placed on the touch device, the user's hand may be unstable, and the touch data detected by the touch device will also be unstable. Once the touch data of the touch device stabilizes, the user's touch action is considered to be stable.

[0073] Therefore, in one or more embodiments of this specification, the following method can be used to acquire each set of touch data:

[0074] The system prompts the user to perform the corresponding finger touch action. If the difference in the touch data of the touch device is less than the preset condition, it determines that the touch data has reached a stable state and acquires the touch data of the touch device at that moment as the touch data corresponding to that group.

[0075] For example, Group 1 prompts the user to place all fingers used to determine the touch action on the touch device; Group 2 prompts the user to perform the first touch action; Group 3 prompts the user to perform the second touch action, until the acquisition of touch data ends.

[0076] Touch data stabilization means that the coordinates of multiple touch points contained in the touch data change only slightly, rather than significantly. At this point, the user's hand is considered to be stable on the touch device.

[0077] Based on this, when acquiring each group of touch data, a time limit can be set for acquiring each group of touch data. If the touch data of the touch device does not reach stability for a long time when acquiring a certain group of touch data, and the corresponding touch data of that group cannot be acquired, the user can be prompted that the touch data acquisition failed. Then, the touch data of that group of touch data can be acquired again. After the touch data of the touch device reaches stability, the touch data at this time can be acquired as the touch data of that group.

[0078] Furthermore, in practical applications, the length of the touch behavior sequence can be fixed or variable, so the way to obtain the touch data input by the user will be different.

[0079] When the touch action sequence is of fixed length, meaning the user can set a maximum length for a valid touch action sequence (e.g., a length of 6), then a valid touch action sequence must include 6 touch actions; more or fewer than 6 is not allowed. Similarly, if the length is 4, then a valid touch action sequence must include 4 touch actions; more or fewer than 4 is not allowed. Therefore, when acquiring touch data, the acquisition process ends after acquiring the 7th or 5th group of touch data (the 1st group is used to determine the touch area corresponding to each finger).

[0080] When the touch action sequence is variable-length—meaning the user can set any length and any number of touch actions (e.g., 3, 7, or 4) when setting a valid touch action sequence—then the acquisition of touch data ends upon receiving the user's end command.

[0081] The above describes the authentication method. The new authentication method proposed in this manual involves the user making corresponding touch actions on the touch device according to the prompts. The touch device analyzes the user's touch actions based on the acquired touch data and compares them with a valid sequence of touch actions to determine whether the user's authentication is successful.

[0082] In addition, before verifying the touch behavior sequence, the user's hand shape can be verified first. That is, before identity verification, the user's hand shape is verified to be less than a preset range if the difference between the user's hand shape and the pre-saved user's hand shape is less than a preset range (for example, if the similarity is 95% after similarity comparison, then the difference is 5%). If it is less than the preset range, then the hand shape of the user to be verified is considered to be consistent with the pre-saved user's hand shape, and then the touch data corresponding to the touch behavior sequence of the user to be verified is further obtained.

[0083] In practical applications, there may be situations where users are unable to use their hands for authentication, such as when the user is a person with disabilities who has no hands. Therefore, those skilled in the art can extend this to other touch behavior sequences, such as those using feet. The key point is to obtain the touch states corresponding to other groups by comparing the differences between the first group of touch data and other groups of touch data. For other methods of implementing touch behavior sequences, please refer to the description of the method of authentication using fingers, which will not be elaborated here.

[0084] This specification also provides an authentication device for verifying a user's identity based on multiple sets of touch data generated on a touch device. Each set of touch data includes the coordinates of multiple touch points generated by the user's touch actions at the same time, and each set of touch data is generated at different times. Figure 3 As shown, the device includes:

[0085] The touch area determination module 301 is used to determine each finger and touch area corresponding to the first set of touch data acquired for the first time.

[0086] The touch state determination module 303 is used to determine multiple touch areas corresponding to each set of touch data subsequently acquired, and to determine the finger touch state corresponding to the set of data based on the difference between the set of data and the first set of data.

[0087] The behavior sequence determination module 305 is used to form a touch behavior sequence to be verified by taking the finger touch state corresponding to each set of touch data acquired subsequently and according to the corresponding acquisition time.

[0088] The comparison module 307 is used to compare the touch behavior sequence to be verified with the preset legal touch behavior sequence, and determine whether the current user has passed the authentication based on the comparison result.

[0089] The device may further include a touch data acquisition module, which acquires each set of touch data. The touch data acquisition module is used to:

[0090] Prompt the user to perform the corresponding finger touch action for that group;

[0091] If the difference in the touch data of the touch device is less than a preset condition, it is determined that the touch data has reached a stable state, and the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

[0092] In addition, the touch data acquisition module can also be used for:

[0093] If the touch data of the touch device does not reach a stable state within a preset time period, the user is prompted that the acquisition of the set of touch data has failed and the corresponding finger touch behavior is repeated.

[0094] Once it is determined that the touch data of the touch device has reached a stable state, the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

[0095] In addition, the touch data acquisition module can also be used for:

[0096] If the number of acquired touch data sets reaches the preset length of a valid touch behavior sequence, the acquisition of touch data will end; or

[0097] Upon receiving a user-inputted end command, the acquisition of touch data is terminated.

[0098] The touch area determination module can also be specifically used for:

[0099] Based on the coordinates of each touch point in the first set of touch data, multiple touch areas are determined from the set of touch point coordinates.

[0100] The relative positions of the multiple touch areas are compared with a standard hand shape to determine the touch areas that conform to the relative positions of each finger, thus obtaining the touch areas corresponding to each finger; the standard hand shape is used to characterize the relative positional relationship between each fingertip.

[0101] Or specifically used for:

[0102] The first set of touch data is input into the pre-trained finger touch area to determine the model;

[0103] Based on the output of the model determined by the finger touch area, the touch area corresponding to each finger is obtained.

[0104] The embodiments of the authentication device correspond to the embodiments of the authentication method. For the embodiments of the authentication device, the relevant parts can be referred to the description of the authentication method, which will not be described in detail here.

[0105] The apparatus, module, or unit described in the above embodiments can be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer, which can be a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0106] This specification also provides an electronic device, including:

[0107] processor;

[0108] Memory used to store processor-executable instructions;

[0109] The processor implements the authentication method as described above by running the executable instructions.

[0110] Figure 4 This diagram illustrates a more specific hardware structure of a computing device provided in an embodiment of this specification. The device may include a processor 410, a memory 420, an input / output interface 430, a communication interface 440, and a bus 450. The processor 410, memory 420, input / output interface 430, and communication interface 440 are interconnected internally via the bus 450.

[0111] The processor 410 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0112] The memory 420 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 420 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 420 and is called and executed by the processor 410.

[0113] Input / output interface 430 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touch screens, microphones, various sensors, etc., and output devices may include displays, speakers, vibrators, indicator lights, etc.

[0114] The communication interface 440 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0115] Bus 450 includes a pathway for transmitting information between various components of the device (e.g., processor 410, memory 420, input / output interface 430, and communication interface 440).

[0116] It should be noted that although the above-described device only shows the processor 410, memory 420, input / output interface 430, communication interface 440, and bus 450, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0117] This specification also provides a computer-readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the steps of the authentication method as described above.

[0118] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0119] It should also be noted that 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. Without further limitation, 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 said element.

[0120] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0121] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this specification. The singular forms “a,” “described,” and “the” used in one or more embodiments of this specification and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0122] It should be understood that although the terms first, second, third, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of one or more embodiments of this specification, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "in response to a determination," or "when," or "in the event of a determination."

[0123] The above description is merely a preferred embodiment of one or more embodiments of this specification and is not intended to limit the scope of one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of one or more embodiments of this specification should be included within the protection scope of one or more embodiments of this specification.

Claims

1. An authentication method for verifying a user's identity based on multiple sets of touch data generated on a touch device, wherein each set of touch data includes multiple touch point coordinates generated by the user's touch actions at the same time, and each set of touch data is generated at different times; the method includes: The system prompts the user to place all fingers used to determine touch behavior on the touch device. Using the first set of touch data acquired initially, the touch area of ​​each finger corresponding to this set of data is determined. For each set of touch data acquired subsequently: multiple touch areas corresponding to this set of data are determined, and the finger touch state corresponding to this set of data is determined based on the difference between this set of data and the first set of data. The step of determining the finger touch state corresponding to the data set based on the difference between the data set and the data set 1 includes: determining whether there is a corresponding touch area for each finger among the multiple touch areas determined in the data set, based on the touch areas corresponding to each finger determined in the data set 1. The conditions for determining whether there is a corresponding touch area for each finger include: the overlap between the touch area in the data set and the touch area of ​​the corresponding finger in the data set 1 is greater than a set threshold; if not, the finger has not performed a touch; if so, the finger has performed a touch. The finger touch states corresponding to each set of touch data acquired subsequently are used to form a sequence of touch behaviors to be verified according to the corresponding acquisition time. The sequence of touch behaviors to be verified is compared with a preset sequence of valid touch behaviors, and the user's authentication status is determined based on the comparison result.

2. The method as described in claim 1, wherein each set of touch data is obtained using the following method: Prompt the user to perform the corresponding finger touch action for that group; If the difference in the touch data of the touch device is less than a preset condition, it is determined that the touch data has reached a stable state, and the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

3. The method of claim 2, wherein the method for acquiring each set of touch data further includes: If the touch data of the touch device does not reach a stable state within a preset time period, the user is prompted that the acquisition of the set of touch data has failed and the corresponding finger touch behavior is repeated. Once it is determined that the touch data of the touch device has reached a stable state, the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

4. The method of claim 2, further comprising: The acquisition of touch data ends when the number of groups of acquired touch data reaches the preset length of a valid touch behavior sequence. or Upon receiving a user-inputted end command, the acquisition of touch data is terminated.

5. The method as described in claim 1, wherein determining the corresponding fingers and touch areas using the first set of detected touch data comprises: Using the coordinates of each touch point in the first set of touch data, determine multiple touch areas within the set of touch point coordinates; The relative positions of the multiple touch areas are compared with a standard hand shape to determine the touch areas that conform to the relative positions of each finger, thus obtaining the touch areas corresponding to each finger; the standard hand shape is obtained in advance and is used to characterize the relative positional relationship between each fingertip.

6. The method of claim 1, wherein determining the corresponding fingers and touch areas using the first set of detected touch data comprises: The first set of touch data is input into the pre-trained finger touch area to determine the model; Based on the output of the model determined by the finger touch area, the touch area corresponding to each finger is obtained.

7. An authentication device for verifying a user's identity based on multiple sets of touch data generated on a touch device, wherein each set of touch data includes multiple touch point coordinates generated by the user's touch behavior at the same time, and each set of touch data is generated at different times; the device comprises: The touch area determination module is used to prompt the user to place all fingers used to determine the touch behavior on the touch device, and to determine each finger and touch area corresponding to the first set of touch data acquired for the first time. The touch state determination module is used to determine multiple touch areas corresponding to each set of subsequently acquired touch data, and to determine the finger touch state corresponding to the set of data based on the difference between the set of data and the first set of data. Specifically, the touch state determination module is used to determine whether there is a corresponding touch area for each finger among the multiple touch areas determined in the first set of data. The conditions for determining whether there is a corresponding touch area for each finger include: the overlap between the touch area in the set of data and the touch area of ​​the corresponding finger in the first set of data is greater than a set threshold; if not, the finger has not touched; if so, the finger has touched. The behavior sequence determination module is used to form a touch behavior sequence to be verified by taking the finger touch state corresponding to each set of touch data acquired subsequently and according to the corresponding acquisition time. The comparison module is used to compare the touch behavior sequence to be verified with a preset legal touch behavior sequence, and determine whether the current user has passed the authentication based on the comparison result.

8. The apparatus of claim 7, further comprising a touch data acquisition module, wherein each set of touch data is acquired using the touch data acquisition module, the touch data acquisition module being used to: Prompt the user to perform the corresponding finger touch action for that group; If the difference in the touch data of the touch device is less than a preset condition, it is determined that the touch data has reached a stable state, and the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

9. The apparatus of claim 8, wherein the touch data acquisition module is further configured to: If the touch data of the touch device does not reach a stable state within a preset time period, the user is prompted that the acquisition of the set of touch data has failed and the corresponding finger touch behavior is repeated. Once it is determined that the touch data of the touch device has reached a stable state, the touch data of the touch device at that moment is acquired as the touch data corresponding to that group.

10. The apparatus of claim 8, wherein the touch data acquisition module is further configured to: If the number of acquired touch data sets reaches the preset length of a valid touch behavior sequence, the acquisition of touch data will end; or Upon receiving a user-inputted end command, the acquisition of touch data is terminated.

11. The apparatus of claim 7, wherein the touch area determination module is specifically used for: Based on the coordinates of each touch point in the first set of touch data, multiple touch areas are determined from the set of touch point coordinates. The relative positions of the multiple touch areas are compared with a standard hand shape to determine the touch areas that conform to the relative positions of each finger, thus obtaining the touch areas corresponding to each finger; the standard hand shape is used to characterize the relative positional relationship between each fingertip.

12. The apparatus of claim 7, wherein the touch area determination module is specifically used for: The first set of touch data is input into the pre-trained finger touch area to determine the model; Based on the output of the model determined by the finger touch area, the touch area corresponding to each finger is obtained.

13. An electronic device, comprising: processor; Memory used to store processor-executable instructions; The processor implements the method as described in any one of claims 1-6 by executing the executable instructions.

14. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 1-6.

Images