WO2017101704A1 - 验证方法及装置 - Google Patents

验证方法及装置 Download PDF

Info

Publication number
WO2017101704A1
WO2017101704A1 PCT/CN2016/108633 CN2016108633W WO2017101704A1 WO 2017101704 A1 WO2017101704 A1 WO 2017101704A1 CN 2016108633 W CN2016108633 W CN 2016108633W WO 2017101704 A1 WO2017101704 A1 WO 2017101704A1
Authority
WO
WIPO (PCT)
Prior art keywords
verification
verification mode
user
current time
time
Prior art date
Application number
PCT/CN2016/108633
Other languages
English (en)
French (fr)
Inventor
姜建
雷鑫
孙宏发
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Priority to JP2018532099A priority Critical patent/JP6795598B2/ja
Priority to SG11201805147YA priority patent/SG11201805147YA/en
Priority to MYPI2018000937A priority patent/MY186946A/en
Priority to KR1020187020365A priority patent/KR102365586B1/ko
Priority to EP16874761.6A priority patent/EP3393080B1/en
Priority to AU2016372750A priority patent/AU2016372750A1/en
Publication of WO2017101704A1 publication Critical patent/WO2017101704A1/zh
Priority to PH12018501271A priority patent/PH12018501271A1/en
Priority to US16/009,424 priority patent/US10686801B2/en
Priority to US16/720,337 priority patent/US11196753B2/en
Priority to AU2020260569A priority patent/AU2020260569A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/108—Network architectures or network communication protocols for network security for controlling access to devices or network resources when the policy decisions are valid for a limited amount of time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
    • H04L63/0838—Network architectures or network communication protocols for network security for authentication of entities using passwords using one-time-passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0861—Network architectures or network communication protocols for network security for authentication of entities using biometrical features, e.g. fingerprint, retina-scan
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a verification method and apparatus.
  • the server verifies the identity of the user to ensure that the operation is The user performs the operation so that the user can successfully implement the purpose of modifying the account password, online shopping or network transfer.
  • the currently used authentication method is SMS verification.
  • the user may perform multiple sensitive operations related to the user's property security in a short period of time. Since each time the sensitive operation server performs the verification of the identity of the user by using the short message verification, the server will use the short message during the whole process. Verify that the user's identity is verified multiple times. For example, the user first modifies the account password, and immediately performs network payment after the modification; wherein, when the user performs the operation of modifying the account password, the server uses the short message verification to verify the identity of the user. When the user performs the network payment operation, the server will Use SMS verification again to verify the identity of the user.
  • the present invention provides a verification method and apparatus.
  • a verification method comprising:
  • the user is authenticated by the failed verification method.
  • the method for obtaining the verification that the user fails in the preset duration before the current moment includes:
  • each row in the verification mode list includes at least one verification mode
  • the method for verifying, by the user, the preset time duration before the current time is removed from the verification mode list including:
  • the found verification mode is deleted from the verification mode list.
  • the method further includes:
  • the passing time corresponding to the failed verification mode is replaced with the determined passing time.
  • the method further includes:
  • a verification method comprising:
  • the user is authenticated using the unused authentication method.
  • the obtaining the verification mode that is not used when the user is verified within the preset duration before the current time includes:
  • each row in the verification mode list includes at least one verification mode
  • the method for verifying the user when the user is verified in the preset duration before the current time is removed from the verification mode list includes:
  • the found verification mode is deleted from the verification mode list.
  • the method further includes:
  • the verification time corresponding to the unused verification mode is replaced by the determined verification time.
  • the removing the verification mode that is used when the user is verified in the preset duration before the current time in the verification mode list further includes:
  • a verification apparatus comprising:
  • a first current time acquisition module configured to acquire a local current time when the user needs to be verified
  • a first verification mode acquiring module configured to acquire a verification mode that the user fails to pass within a preset duration before the current time
  • the first verification module is configured to verify the user by using the failed verification manner.
  • a verification apparatus comprising:
  • a second current time acquiring module configured to acquire a local current time when the user needs to be verified
  • a second verification mode acquiring module configured to acquire an authentication mode that is not used when the user is verified within a preset duration before the current time
  • the second verification module is configured to verify the user by using the unused verification manner.
  • the technical solution provided by the embodiment of the present invention may include the following beneficial effects: in the prior art, each time the user performs a sensitive operation, the server verifies the identity of the user by using the short message verification, if the user performs the multiple times in a short time. For sensitive operations, the server will use the same authentication method to verify the user multiple times in a short period of time, resulting in a lower user experience.
  • the verification mode that the user fails to pass within the preset time period before the current time is acquired, or the user is verified within the preset time period before the current time.
  • FIG. 1 is a flowchart of a verification method according to an exemplary embodiment
  • FIG. 2 is a flow chart showing a verification method according to an exemplary embodiment
  • FIG. 3 is a flowchart of a verification method according to an exemplary embodiment
  • FIG. 4 is a flowchart of a verification method according to an exemplary embodiment
  • FIG. 5 is a flowchart of a verification method according to an exemplary embodiment
  • FIG. 6 is a flowchart of a verification method according to an exemplary embodiment
  • FIG. 7 is a block diagram of a verification apparatus according to an exemplary embodiment
  • FIG. 8 is a block diagram of a verification apparatus, according to an exemplary embodiment.
  • FIG. 1 is a flowchart of a verification method according to an exemplary embodiment. As shown in FIG. 1, the method includes the following steps.
  • step S101 when the user needs to be verified, the local current time is obtained
  • the user In the process of using the terminal, the user sometimes needs to perform sensitive operations related to the security of the user, such as modifying the account password, online shopping or network transfer, on the terminal, and the terminal receives the user input related to the security of the user's property.
  • sensitive operations are performed, sensitive requests are generated and sent to the server.
  • the server receives the sensitive request sent by the terminal, in order to protect the security of the user's property, the server needs to verify the identity of the user before responding to the sensitive request to ensure sensitivity. The operation is performed by the user himself, and when the user passes the verification, the server responds to the sensitive request.
  • the server when receiving the sensitive request sent by the terminal, it is determined that the user needs to be authenticated and the local current time is obtained.
  • step S102 the verification mode that the user fails to pass within the preset time period before the current time is acquired
  • the preset duration may be a duration set by the technician in the server in advance, and may be 30 seconds, 1 minute, or 2 minutes, etc., which is not limited by the present invention.
  • verification methods for the server to verify the user, for example, SMS verification, mailbox verification, face verification, security problem verification and fingerprint verification.
  • the preset duration is 10 minutes. If the server verifies the identity of the user by using the short message verification within 10 minutes before the current time, and the user passes the verification, the short message verification is the verification mode that the user passes within the preset time period before the current time. If the server authenticates the identity of the user by using the mailbox verification within 10 minutes before the current time, but the user fails the verification, the mailbox is verified as the authentication mode that the user fails within the preset time period before the current time.
  • step S103 the user is authenticated using the failed verification method.
  • the server verifies the identity of the user by using the short message verification. If the user continuously performs multiple sensitive operations in a short time, the server will utilize the same in a short time. The verification method of the user is verified multiple times, resulting in a lower user experience.
  • the verification mode that the user fails to pass within the preset time period before the current time is obtained; and then the user is verified by the obtained verification mode to avoid using the same verification mode.
  • the user is authenticated multiple times in a short period of time to improve the user experience.
  • step S102 includes:
  • step S201 a verification mode list is obtained
  • the verification mode list includes multiple lines, and each line includes at least one verification mode, and any two rows of the package
  • the verification methods are not exactly the same. If multiple verification methods are included in a row, any two verification methods in that row are different.
  • Table 1 includes three rows.
  • the first row includes two authentication methods, namely SMS authentication and email authentication.
  • the second row includes a verification method for face verification.
  • the third row Two verification methods are included, which are mailbox verification and security problem verification.
  • step S202 the verification mode adopted by the user within the preset duration before the current time is removed from the verification mode list
  • this step can be implemented by the following processes, including:
  • each time the server authenticates the user by using a certain verification mode if the user passes the verification mode, the server obtains the time when the user passes the verification mode; and then the local storage verification mode and Find whether the verification mode exists by the correspondence between the moments.
  • the verification mode When the verification mode does not exist in the corresponding relationship, it indicates that the user has not passed the verification mode. In this case, the verification mode and the transit time may be stored as one record in the corresponding relationship.
  • the verification mode exists in the corresponding relationship, it indicates that the previous user has passed the verification mode. In this case, it is necessary to find the transit time corresponding to the verification mode in the corresponding relationship, and then replace the found by using the acquired transit time. The time is passed to update the passing time of the user through the verification mode.
  • the server can obtain the correspondence between the locally stored verification mode and the passing time, and then find and verify in the corresponding relationship.
  • the mode corresponds to the passing time, thereby obtaining the passing time of the user passing the verification mode most recently in the history process.
  • the correspondence between the verification mode and the passing time can be as shown in Table 2 below.
  • the authentication methods adopted by the user include mailbox verification, short message verification, face verification, security problem verification, and fingerprint verification.
  • the last time the user passed the mailbox verification is 09:09:22
  • the last time the user passed the SMS verification is 13:05:27
  • the last time the user passed the face verification is 12:08:12.
  • the last time the user passed the security verification is 11:32:45
  • the last time the user passed the fingerprint verification is 13:01:21.
  • obtaining a pass time included in the record and subtracting the current time from the pass time to obtain a duration, and comparing the duration with the preset duration, if the duration is less than the preset duration
  • obtaining the verification mode included in the record and as the verification mode corresponding to the passing time that the distance between the current time is less than the preset duration.
  • the foregoing operations are performed, so that the verification manner corresponding to the transit times when the distance between the current time and the current time is less than the preset duration is found.
  • the verification time For example, suppose the current time is 13:10:04 and the preset duration is 10 minutes. Then, in the correspondence relationship shown in Table 2, it can be found that the verification time with the distance between the current time 13:10:04 and less than 10 minutes is 13:05:27 and 13:01:21, respectively, and the two can be determined.
  • the verification methods corresponding to the verification time are SMS verification and fingerprint verification.
  • the verification mode list is searched for whether the verification mode exists, and when the verification mode exists in the verification mode list, the verification mode is deleted from the verification list; Step 12)
  • Each of the other verification methods found performs the above operations, so that all the verification methods found in step 12) are deleted from the verification mode list.
  • the searched verification methods are short message verification and fingerprint verification respectively; then, in the verification mode list shown in Table 1, it is found whether there is SMS verification, and the verification method shown in Table 1 is determined. If there is SMS verification in the list, the SMS verification is deleted from the authentication method list shown in Table 1, and the verification mode list shown in Table 3 is obtained.
  • the verification mode list shown in Table 3 it is found whether fingerprint verification exists, and if there is no fingerprint verification in the verification mode list shown in Table 3, the verification mode list shown in Table 3 is determined as the removed verification mode. List.
  • step S203 the verification mode in one of the removed verification mode lists is obtained.
  • the purpose of the present invention is to determine a row from the verification mode list, and verify the user by using all the verification methods in the determined row; when the user passes all the verification modes in the determined row, the server can determine The user passed this verification.
  • the server may actively select one row from the removed verification mode list, for example, randomly select one row from the removed verification mode list, and then obtain all the verification modes in the selected row.
  • the server may further send the removed verification mode list to the terminal, so that the terminal displays the removed verification mode list to the user; the user may select from the removed verification mode list displayed by the terminal. Select a row; the terminal sends the row selected by the user to the server; the server obtains the authentication mode in the row selected by the user.
  • the server can determine that the user passes the verification because the user must pass all the verification methods in one of the rows in the verification mode list. Therefore, if the user selects a line that includes only one verification method, the user can pass the verification by simply passing the verification mode. If the user selects a line including multiple verification methods, the user needs to pass the verification separately. This verification method can pass this verification. Therefore, in order to pass this verification as soon as possible, the user generally selects a smaller number of rows including the verification method in the removed verification mode list.
  • the number of verification methods in the first row and the number of verification methods in the second row are small, and the number of verification methods in the third row is large, so With this verification, the user will usually select the first line or the second line.
  • the server actively selects a row from the removed verification mode list, the number of rows including the verification mode may be selected to enable the user to pass the verification as soon as possible.
  • the method further includes:
  • step S301 it is determined whether the number of rows in the removed verification mode list is less than the number of rows in the verification mode list before removal;
  • step S202 if all the verification modes in a certain row in the verification mode list are the verification manners that the user passes within the preset duration before the current time, all the rows in the row are removed when step S202 is performed.
  • the verification method that is, the line no longer exists in the verification mode list, so that the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal.
  • the verification mode passed by the user within the preset duration before the current time is SMS verification and face verification
  • the SMS verification and the face are removed from the verification mode list shown in Table 1 when step S202 is performed. Verify that the list of verification methods shown in Table 4 is obtained.
  • the verification mode list shown in Table 4 includes 2 rows, and the verification mode list shown in Table 1 before the removal includes 3 rows, so that it can be determined that the number of rows in the removed verification mode list is smaller than before the removal.
  • the number of rows in the verification mode list is then executed in step S302.
  • step S302 it is determined that the user passes the current verification
  • the verification can be passed as long as the user passes all the verification methods in any row in the verification mode list. Therefore, once it is determined that the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal, it indicates that the user presets before the current time for any one of the rows that have been removed. All the verification methods in the line are passed within the duration, so there is no need to verify the user, so that the user can confirm that the user has passed the verification and ends the process.
  • step S203 is performed to obtain the verification mode in one of the removed verification mode lists.
  • the verification method includes the verification mode in another row, that is, the verification mode in the other row exists in the certain row, but the number of verification modes in the one row is greater than the number of authentication modes in the other row.
  • the authentication method in the third row is the mailbox verification and security problem verification.
  • the authentication method in the first row is the mailbox verification, and the mailbox verification in the first row exists in the third row.
  • Medium and third line The number of verification methods in the first row is greater than the number of authentication methods in the first row of Chinese women, so the verification method in the third row includes the verification method in the first row.
  • the first line only needs to pass the mailbox verification to pass the verification
  • the third line not only needs to pass the mailbox verification and needs to pass the security problem verification to pass the verification. Therefore, in order to pass this verification as soon as possible, in the first row and the third row, in general, the user is more inclined to choose the first row.
  • the server may actively select a row from the list of removed authentication methods, and select the first row relative to the server. If the server selects the third row, the user not only needs to pass the mailbox verification but also needs to pass the security question verification. This will not allow the user to pass this verification as soon as possible.
  • the server determines the row for any row in the removed verification mode list. Whether the verification mode in the row includes the verification mode in other rows. When the verification mode in the row includes the verification mode in other rows, the row is deleted from the removed verification mode list; for each of the other rows, the above execution is performed. operating.
  • the third row is deleted from the list of authentication methods shown in Table 3, and a list of authentication methods as shown in Table 5 is obtained.
  • the server selects a row from the list of authentication modes shown in Table 5, except for selecting the second row including the face verification, only the first row including the mailbox verification is selected, and the mailbox including the original table 3 is not selected.
  • the third line of verification and security issue verification In this way, the server only uses the mailbox verification to authenticate the user, and the user can pass the verification by passing the mailbox verification; thereby enabling the user to pass the verification as soon as possible, thereby improving the verification efficiency.
  • the server after the server authenticates the user by using the unverified verification mode, when the user passes the verification mode, the server acquires the local current time and acts as the passing time when the user passes the verification mode. Then, in the correspondence between the locally stored verification mode and the passing time, the passing time corresponding to the verification mode is replaced with the passing time to update the passing time of the user through the verification mode.
  • FIG. 4 is a flowchart of a verification method according to an exemplary embodiment. As shown in FIG. 4, the method includes the following steps.
  • step S401 when the user needs to be verified, the local current time is obtained
  • the user In the process of using the terminal, the user sometimes needs to perform sensitive operations related to the security of the user, such as modifying the account password, online shopping or network transfer, on the terminal, and the terminal receives the user input related to the security of the user's property.
  • sensitive operations are performed, sensitive requests are generated and sent to the server.
  • the server receives the sensitive request sent by the terminal, in order to protect the security of the user's property, the server needs to verify the identity of the user before responding to the sensitive request to ensure sensitivity. The operation is performed by the user himself, and when the user passes the verification, the server responds to the sensitive request.
  • the server when receiving the sensitive request sent by the terminal, it is determined that the user needs to be authenticated and the local current time is obtained.
  • step S402 the verification mode that is not used when the user is verified within the preset duration before the current time is acquired
  • the preset duration may be a duration set by the technician in the server in advance, and may be 30 seconds, 1 minute, or 2 minutes, etc., which is not limited by the present invention.
  • verification methods for the server to verify the user, for example, SMS verification, mailbox verification, face verification, security problem verification and fingerprint verification.
  • the server may only use some of the multiple verification methods described above when verifying the user.
  • the short message verification is the verification method used when verifying the user within the preset time period before the current time. If the server does not use the mailbox verification to verify the identity of the user within 10 minutes before the current time, the mailbox verification is an authentication method that is not used during the verification of the user within the preset time period before the current time.
  • step S403 the user is authenticated using an unused verification method.
  • the server verifies the identity of the user by using the short message verification. If the user continuously performs multiple sensitive operations in a short time, the server will utilize the same in a short time. The verification method of the user is verified multiple times, resulting in a lower user experience.
  • the verification mode that is not used during the verification of the user within the preset time period before the current time is acquired; and then the user is verified by the obtained verification mode. Avoid using the same verification method to authenticate users multiple times in a short period of time, thus improving the user experience.
  • step S402 includes:
  • step S501 a verification mode list is obtained
  • the verification mode list includes multiple lines, and each line includes at least one verification mode, and the verification methods included in any two lines are not completely the same. If multiple verification methods are included in a row, any two verification methods in that row are different.
  • Table 1 includes three rows.
  • the first row includes two authentication methods, namely SMS authentication and email authentication.
  • the second row includes a verification method for face verification.
  • the third row Two verification methods are included, which are mailbox verification and security problem verification.
  • step S502 the verification mode used in the verification of the user within the preset duration before the current time is removed from the verification mode list;
  • this step can be implemented by the following processes, including:
  • the server each time the server authenticates the user by using a certain verification manner, the server obtains the local current time and serves as the verification time when the user is verified; and then stores the verification mode and the verification time locally. Find the existence of this verification method in the correspondence between them.
  • the verification mode does not exist in the foregoing correspondence, it is indicated that the verification mode has not been used to verify the user.
  • the verification mode and the verification time may be stored as one record in the corresponding relationship.
  • the verification time corresponding to the verification mode needs to be searched in the corresponding relationship, and then the search time is replaced by the obtained verification time.
  • the verification time to arrive is to update the verification time when the user is authenticated by the verification method.
  • the server can obtain the correspondence between the locally stored verification mode and the verification time, and then find and match in the corresponding relationship.
  • the verification time corresponds to the verification time, thereby obtaining the verification time when the user is verified by the verification method in the history.
  • the correspondence between the verification mode and the verification time can be as shown in Table 7 below.
  • the authentication methods used in the verification of the user include mailbox verification, short message verification, face verification, security problem verification, and fingerprint verification.
  • the last verification time when using the mailbox verification to authenticate the user is 09:09:22
  • the last verification time when using the short message verification to authenticate the user is 13:05:27
  • the last time using the face verification to the user The verification time for verification is 12:08:12.
  • the verification time for verifying the user with the latest security problem verification is 11:32:45
  • the verification time when the user is verified by the latest email fingerprint verification is 13:01:21.
  • the foregoing operations are performed, so that the verification manner corresponding to the verification moments in which the distance between the current time and the current time is less than the preset duration is found.
  • the verification time For example, suppose the current time is 13:10:04 and the preset duration is 10 minutes. Then, in the correspondence relationship shown in Table 2, it can be found that the verification time with the distance between the current time 13:10:04 and less than 10 minutes is 13:05:27 and 13:01:21, respectively, and the two can be determined.
  • the verification methods corresponding to the verification time are SMS verification and fingerprint verification.
  • the verification mode list is searched for whether the verification mode exists, and when the verification mode exists in the verification mode list, the verification mode is deleted from the verification list; Step 22)
  • Each of the other verification methods found performs the above operations, so that all the verification methods found in step 22) are deleted from the verification mode list.
  • the searched verification methods are short message verification and fingerprint verification respectively; then, in the verification mode list shown in Table 6, it is found whether there is SMS verification, and the verification method shown in Table 6 is determined. List If there is SMS verification, the SMS verification is deleted from the verification mode list shown in Table 6, and the verification mode list shown in Table 8 is obtained.
  • the verification mode list shown in Table 8 it is found whether there is fingerprint verification, and it is determined that there is no fingerprint verification in the verification mode list shown in Table 3, and the verification mode list shown in Table 3 is determined as the removed verification mode. List.
  • step S503 the verification mode in one of the removed verification mode lists is obtained.
  • the purpose of the present invention is to determine a row from the verification mode list, and verify the user by using all the verification methods in the determined row; when the user passes all the verification modes in the determined row, the server can determine The user passed this verification.
  • the server may actively select one row from the removed verification mode list, for example, randomly select one row from the removed verification mode list, and then obtain all the verification modes in the selected row.
  • the server may further send the removed verification mode list to the terminal, so that the terminal displays the removed verification mode list to the user; the user may select from the removed verification mode list displayed by the terminal. Select a row; the terminal sends the row selected by the user to the server; the server obtains the authentication mode in the row selected by the user.
  • the server can determine that the user passes the verification because the user must pass all the verification methods in one of the rows in the verification mode list. Therefore, if the user selects a line that includes only one verification method, the user can pass the verification by simply passing the verification mode. If the user selects a line including multiple verification methods, the user needs to pass the verification separately. This verification method can pass this verification. Therefore, in order to pass this verification as soon as possible, the user generally selects a smaller number of rows including the verification method in the removed verification mode list.
  • the number of verification methods in the first line and the number of verification methods in the second line are small, and the number of verification methods in the third line is large, so With this verification, the user will usually select the first line or the second line.
  • the server actively selects a row from the removed verification mode list, the number of rows including the verification mode may be selected to enable the user to pass the verification as soon as possible.
  • the method further includes:
  • step S601 it is determined whether the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal;
  • step S502 if all the verification methods in a certain row in the verification mode list are the verification manners that the user passes within the preset duration before the current time, all the rows in the row are removed when step S502 is performed.
  • the verification method that is, the line no longer exists in the verification mode list, so that the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal.
  • the verification method used for verifying the user within the preset duration before the current time is SMS verification and face verification
  • the SMS verification is removed from the verification mode list shown in Table 6.
  • the list of verification methods shown in Table 9 can be obtained.
  • the verification mode list shown in Table 9 includes 2 rows, and the verification mode list shown in Table 6 before removal includes 3 rows, so that it is determined that the number of rows in the removed verification mode list is smaller than the verification before removal.
  • the number of rows in the mode list is then executed in step S602.
  • step S602 it is determined that the user passes the current verification
  • the verification can be passed as long as the user passes all the verification methods in any row in the verification mode list. Therefore, once it is determined that the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal, it indicates that the user presets before the current time for any one of the rows that have been removed. All the verification methods in the line are passed within the duration, so there is no need to verify the user, so that the user can complete the process through this verification.
  • step S503 is performed: obtaining the verification mode in one of the removed verification mode lists.
  • the removed verification mode list when the number of rows in the removed verification mode list is equal to the number of rows in the verification mode list before the removal, in the removed verification mode list, there may be a row.
  • Verification The manner includes the verification mode in another row, that is, the verification mode in the other row exists in the certain row, but the number of verification modes in the one row is greater than the number of verification modes in the other airline.
  • the authentication method in the third row is the mailbox verification and security problem verification.
  • the authentication method in the first row is the mailbox verification, and the mailbox verification in the first row exists in the third row.
  • the number of verification methods in the third row is greater than the number of authentication methods in the first row of Chinese women, so the verification method in the third row includes the verification mode in the first row.
  • the first line only needs to pass the mailbox verification to pass the verification
  • the third line not only needs to pass the mailbox verification and needs to pass the security problem verification to pass the verification. Therefore, in order to pass this verification as soon as possible, in the first row and the third row, in general, the user is more inclined to choose the first row.
  • the server may actively select a row from the list of removed authentication methods, and select the first row relative to the server. If the server selects the third row, the user not only needs to pass the mailbox verification but also needs to pass the security question verification. This will not allow the user to pass this verification as soon as possible.
  • the server determines the row for any row in the removed verification mode list. Whether the verification mode in the row includes the verification mode in other rows. When the verification mode in the row includes the verification mode included in other rows, the row is deleted from the removed verification mode list; for each other row, the execution is performed. The above operation.
  • the third row is deleted from the list of authentication methods shown in Table 8, and a list of authentication methods as shown in Table 10 is obtained.
  • the server selects a row from the list of authentication modes shown in Table 10, except for selecting the second row including the face verification, only the first row including the mailbox verification is selected, and the mailbox including the original table 8 is not selected.
  • the third line of verification and security issue verification In this way, the server only uses the mailbox verification to authenticate the user, and the user can pass the verification by passing the mailbox verification; thereby enabling the user to pass the verification as soon as possible, thereby improving the verification efficiency.
  • the server when the server authenticates the user by using the unused verification manner, the server acquires the current current time and verifies the time when the user is authenticated by using the unused verification method; In the corresponding relationship between the locally stored verification method and the verification time, the verification time corresponding to the verification method is replaced with the verification time to update the verification time when the user is verified by the verification method.
  • FIG. 7 is a block diagram of a verification apparatus, according to an exemplary embodiment.
  • the apparatus includes:
  • the first current time acquisition module 11 is configured to acquire a local current time when the user needs to be verified
  • the first verification mode obtaining module 12 is configured to acquire an authentication mode that the user fails to pass within a preset duration before the current time;
  • the first verification module 13 is configured to verify the user by using the failed verification mode.
  • the server verifies the identity of the user by using the short message verification. If the user continuously performs multiple sensitive operations in a short time, the server will utilize the same in a short time. The verification method of the user is verified multiple times, resulting in a lower user experience.
  • the verification mode that the user fails to pass within the preset time period before the current time is obtained; and then the user is verified by the obtained verification mode to avoid using the same verification mode.
  • the user is authenticated multiple times in a short period of time to improve the user experience.
  • the first verification mode obtaining module 12 includes:
  • a first verification mode list obtaining unit configured to obtain a verification mode list; each row in the verification mode list includes at least one verification mode;
  • a first removing unit configured to remove, from the verification mode list, a verification mode that the user passes within a preset time period before the current time
  • the first verification mode obtaining unit is configured to obtain the verification mode in one of the removed verification mode lists.
  • the first removal unit includes:
  • a first acquiring subunit configured to acquire a correspondence between a local storage verification mode and a passing time
  • a first search subunit configured to search, in the correspondence relationship, a verification manner corresponding to a transit time that is shorter than a preset duration by the current time
  • a first deletion subunit configured to delete the searched verification manner from the verification mode list.
  • the device further includes:
  • the time acquisition module is configured to acquire a local current time when the user passes the failed verification mode, and determine a passing time when the user passes the failed verification mode;
  • a first replacement module configured to replace, in the corresponding relationship, a transit time corresponding to the failed verification mode by using the determined transit time.
  • the first verification mode obtaining module 12 further includes:
  • a first determining unit configured to determine whether the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal
  • a first determining unit configured to determine that the user passes the current verification when the number of rows in the removed verification mode list is less than the number of rows in the verification mode list before removal;
  • the first verification mode acquiring unit is further configured to: when the number of rows in the removed verification mode list is equal to the number of rows in the verification mode list before the removal, perform the acquiring the verification mode after the removal The steps for the verification method in one of the rows in the list.
  • FIG. 8 is a block diagram of a verification apparatus, according to an exemplary embodiment.
  • the apparatus includes:
  • the second current time acquisition module 21 is configured to acquire a local current time when the user needs to be verified
  • the second verification mode obtaining module 22 is configured to acquire an authentication mode that is not used when the user is verified within a preset time period before the current time;
  • the second verification module 23 is configured to verify the user by using the unused verification manner.
  • the server verifies the identity of the user by using the short message verification. If the user continuously performs multiple sensitive operations in a short time, the server will utilize the same in a short time. The verification method of the user is verified multiple times, resulting in a lower user experience.
  • the verification mode that is not used during the verification of the user within the preset time period before the current time is acquired; and then the user is verified by the obtained verification mode. Avoid using the same verification method to authenticate users multiple times in a short period of time, thus improving the user experience.
  • the second verification mode obtaining module 22 includes:
  • a second verification mode list obtaining unit configured to obtain a verification mode list; each row in the verification mode list includes at least one verification mode;
  • a second removing unit configured to remove, from the verification mode list, a verification mode that is used when the user is verified within a preset duration before the current time
  • the second verification mode acquiring unit is configured to obtain the verification mode in one of the removed verification mode lists.
  • the second removal unit includes:
  • a second acquiring sub-unit configured to obtain a correspondence between a locally stored verification mode and a verification time
  • a second search subunit configured to search, in the correspondence relationship, a verification manner corresponding to a verification time when the distance between the current time is less than a preset duration
  • a second deletion subunit configured to delete the found verification mode from the verification mode list.
  • the device further includes:
  • a verification time acquisition module configured to acquire a local current time when the user is authenticated by using the unverified verification mode, and determine a verification time when the user is verified by using the unused verification mode;
  • a second replacement module configured to replace, in the corresponding relationship, the verification time corresponding to the unused verification mode by using the determined verification time.
  • the second verification mode obtaining module 22 further includes:
  • a second determining unit configured to determine whether the number of rows in the removed verification mode list is smaller than the number of rows in the verification mode list before removal
  • a second determining unit configured to determine that the user passes the current verification when the number of rows in the removed verification mode list is less than the number of rows in the verification mode list before the removal;
  • the second verification mode acquiring unit is further configured to: when the number of rows in the removed verification mode list is equal to the number of rows in the verification mode list before the removal, perform the acquiring the verification mode after the removal The steps for the verification method in one of the rows in the list.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Hardware Design (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Health & Medical Sciences (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephone Function (AREA)
  • Stored Programmes (AREA)
  • Collating Specific Patterns (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Mobile Radio Communication Systems (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

本发明实施例提供了一种验证方法及装置，其方法包括：当需要对用户进行验证时，获取本地的当前时刻；获取在当前时刻之前的预设时长内用户未通过的验证方式，或者，获取在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式，并以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。

Description

验证方法及装置
本申请要求2015年12月16日递交的申请号为201510946529.7、发明名称为“验证方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及互联网技术领域，尤其涉及一种验证方法及装置。
背景技术
当前，为了保障用户的财产不受损失，当用户执行修改账户密码、网络购物或网络转账等与用户的财产安全息息相关的敏感操作时，服务器就会对用户的身份进行验证，以确保该操作为用户本人执行的操作，这样，用户才能成功实现修改账户密码、网络购物或网络转账等目的。其中，目前常用的验证方式为短信验证。
其中，有时候用户可能会短时间内连续执行多次与用户的财产安全息息相关的敏感操作，由于每执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，因此整个过程中服务器会利用短信验证对用户的身份进行多次验证。例如用户先修改账户密码，修改完毕后立即进行网络支付；其中，当用户执行修改账户密码的操作时，服务器会利用短信验证对用户的身份进行验证，当用户执行网络支付的操作时，服务器会再次利用短信验证对用户的身份进行验证。
发明内容
为克服相关技术中存在的问题，本发明提供一种验证方法及装置。
根据本发明实施例的第一方面，提供一种验证方法，所述方法包括：
当需要对用户进行验证时，获取本地的当前时刻；
获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式；
利用所述未通过的验证方式对所述用户进行验证。
其中，所述获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式，包括：
获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式；
获取所述去除后的验证方式列表中的其中一行中的验证方式。
其中，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式，包括：
获取本地存储的验证方式与通过时刻之间的对应关系；
在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的通过时刻对应的验证方式；
从所述验证方式列表中删除所述查找到的验证方式。
进一步地，所述方法还包括：
当所述用户通过所述未通过的验证方式时，获取本地的当前时刻并确定为所述用户通过所述未通过的验证方式时的通过时刻；
在所述对应关系中，利用所述确定的通过时刻替换与所述未通过的验证方式对应的通过时刻。
进一步地，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式之后，还包括：
判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
根据本发明实施例的第二方面，提供一种验证方法，所述方法包括：
当需要对用户进行验证时，获取本地的当前时刻；
获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式；
利用所述未利用过的验证方式对所述用户进行验证。
其中，所述获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式，包括：
获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式；
获取所述去除后的验证方式列表中的其中一行中的验证方式。
其中，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式，包括：
获取本地存储的验证方式与验证时刻之间的对应关系；
在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的验证时刻对应的验证方式；
从所述验证方式列表中删除所述查找到的验证方式。
进一步地，所述方法还包括：
当利用所述未通过的验证方式对所述用户进行验证时，获取本地的当前时刻并确定为利用所述未利用过的验证方式对用户进行验证时验证时刻；
在所述对应关系中，利用所述确定出的验证时刻替换与所述未利用过的验证方式对应的验证时刻。
进一步地，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式之后，还包括：
判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
根据本发明实施例的第三方面，提供一种验证装置，所述装置包括：
第一当前时刻获取模块，用于当需要对用户进行验证时，获取本地的当前时刻；
第一验证方式获取模块，用于获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式；
第一验证模块，用于利用所述未通过的验证方式对所述用户进行验证。
根据本发明实施例的第四方面，提供一种验证装置，所述装置包括：
第二当前时刻获取模块，用于当需要对用户进行验证时，获取本地的当前时刻；
第二验证方式获取模块，用于获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式；
第二验证模块，用于利用所述未利用过的验证方式对所述用户进行验证。
本发明的实施例提供的技术方案可以包括以下有益效果：在现有技术中，每当用户执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，如果用户在短时间内连续执行多次敏感操作，则在短时间内服务器就会利用相同的验证方式多次对用户进行验证，导致用户体验较低。
而在本发明实施例中，当需要对用户进行验证时，获取在当前时刻之前的预设时长内用户未通过的验证方式，或者，获取在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式；然后以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是根据一示例性实施例示出的一种验证方法的流程图；
图2是根据一示例性实施例示出的一种验证方法的流程图；
图3是根据一示例性实施例示出的一种验证方法的流程图；
图4是根据一示例性实施例示出的一种验证方法的流程图；
图5是根据一示例性实施例示出的一种验证方法的流程图；
图6是根据一示例性实施例示出的一种验证方法的流程图；
图7是根据一示例性实施例示出的一种验证装置的框图；
图8是根据一示例性实施例示出的一种验证装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
图1是根据一示例性实施例示出的一种验证方法的流程图，如图1所示，该方法包括以下步骤。
在步骤S101中，当需要对用户进行验证时，获取本地的当前时刻；
用户在使用终端的过程中，有时候需要在终端上执行诸如修改账户密码、网络购物或网络转账等与用户的财产安全息息相关的敏感操作，当终端接收到用户输入的与用户的财产安全息息相关的敏感操作时，会生成敏感请求并发送给服务器，当服务器接收到终端发送的敏感请求时，为了对保障用户的财产安全，在响应敏感请求之前，服务器需要对用户的身份进行验证，以确保敏感操作为用户本人执行的操作，当用户通过验证时，服务器再响应敏感请求。
对于服务器而言，当接收到终端发送的敏感请求时，确定需要对用户进行验证，并获取本地的当前时刻。
在步骤S102中，获取在当前时刻之前的预设时长内用户未通过的验证方式；
预设时长可以为技术人员事先在服务器中设置的时长，可以为30秒钟、1分钟或2分钟等，本发明对此不加以限定。
其中，服务器对用户进行验证的验证方式有很多中，例如，短信验证，邮箱验证，人脸验证、安保问题验证和指纹验证等等。
例如，假设预设时长为10分钟。如果在当前时刻之前的10分钟内，服务器利用短信验证对用户的身份进行验证，且用户通过了该验证，则短信验证为在当前时刻之前的预设时长内用户通过的验证方式。如果在当前时刻之前的10分钟内，服务器利用邮箱验证对用户的身份进行验证，但用户未通过该验证，则邮箱验证为在当前时刻之前的预设时长内用户未通过的验证方式。
在步骤S103中，利用未通过的验证方式对用户进行验证。
其中，在现有技术中，每当用户执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，如果用户在短时间内连续执行多次敏感操作，则在短时间内服务器就会利用相同的验证方式多次对用户进行验证，导致用户体验较低。
而在本发明实施例中，当需要对用户进行验证时，获取在当前时刻之前的预设时长内用户未通过的验证方式；然后以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。
其中，在本发明另一实施例中，参见图2，步骤S102包括：
在步骤S201中，获取验证方式列表；
其中，验证方式列表包括多行，每一行中都包括至少一个验证方式，任意两行中包 括的验证方式不完全相同。如果某一行中包括多个验证方式，则该行中的任意两个验证方式都不相同。
例如，验证方式列表可以如下表1所示，表1包括三行，第一行包括两个验证方式，分别为短信验证和邮箱验证；第二行包括一个验证方式，为人脸验证；第三行包括两个验证方式，分别为邮箱验证和安保问题验证。
表1
短信验证邮箱验证
人脸验证
邮箱验证安保问题验证
在步骤S202中，从验证方式列表中去除在当前时刻之前的预设时长内用户通过的验证方式；
具体地，本步骤可以通过如下流程实现，包括：
11)、获取本地存储的验证方式与通过时刻之间的对应关系；
在本发明实施例中，每当服务器利用某一验证方式对用户进行验证时，如果用户通过了该验证方式，则服务器就会获取用户通过该验证方式的通过时刻；然后本地存储的验证方式与通过时刻之间的对应关系中查找是否存在该验证方式。
当上述对应关系中不存在该验证方式时，说明之前用户未曾通过该验证方式，此时可将该验证方式和该通过时刻作为一条记录存储在上述对应关系中。
当上述对应关系中存在该验证方式时，则说明之前用户曾经通过了该验证方式，此时需要在上述对应关系中查找与该验证方式对应的通过时刻，然后利用获取的通过时刻替换查找到的通过时刻，以实现对用户通过该验证方式的通过时刻进行更新。
这样，当需要查找在历史过程中用户最近一次通过某一验证方式的通过时刻时，服务器就可以获取本地存储的验证方式与通过时刻之间的对应关系，然后在上述对应关系中查找与该验证方式对应的通过时刻，从而得到在历史过程中用户最近一次通过该验证方式的通过时刻。
例如，验证方式与通过时刻之间的对应关系可以如下表2所示。
表2
验证方式 通过时刻
邮箱验证 09:09:22
短信验证 13:05:27
人脸验证 12:08:12
安保问题验证 11:32:45
指纹验证 13:01:21
其中，如表2所示，在历史过程中，用户通过的验证方式包括邮箱验证、短信验证、人脸验证、安保问题验证以及指纹验证。其中，用户最近一次通过邮箱验证的通过时刻为09:09:22，用户最近一次通过短信验证的通过时刻为13:05:27，用户最近一次通过人脸验证的通过时刻为12:08:12，用户最近一次通过安保问题验证的通过时刻为11:32:45，以及用户最近一次通过指纹验证的通过时刻为13:01:21。
12)、在上述对应关系中查找与当前时刻之间的距离小于预设时长的通过时刻对应的验证方式；
对于上述对应关系中的任一条记录，获取该记录中包括的通过时刻，将当前时刻与该通过时刻进行减法运算得到一时长，将该时长与预设时长进行比较，如果该时长小于预设时长，则获取该记录中包括的验证方式，并作为与当前时刻之间的距离小于预设时长的通过时刻对应的验证方式。
对于上述对应关系中的其他每一条记录，均执行上述操作，如此实现从对应关系中查找到所有与当前时刻之间的距离小于预设时长的通过时刻对应的验证方式。
例如，假设当前时刻为13:10:04，且预设时长为10分钟。则在表2所示的对应关系中可以查找到与当前时刻13:10:04之间距离小于10分钟的验证时刻分别为13:05:27和13:01:21，以及可以确定出这两个验证时刻对应的验证方式分别为短信验证和指纹验证。
13)、从验证方式列表中删除查找到的验证方式。
具体地，对于在步骤12)中查找到的任一个验证方式，在验证方式列表中查找是否存在该验证方式，当验证方式列表中存在该验证方式时，从验证列表中删除该验证方式；对于步骤12)查找到的其他每一个验证方式，均执行上述操作，如此实现从验证方式列表中删除在步骤12)中查找到的所有验证方式。
例如，在步骤12)中的例子中，查找到的验证方式分别为短信验证和指纹验证；则在表1所示的验证方式列表中查找是否存在短信验证，且确定表1所示的验证方式列表中存在短信验证，则从表1所示的验证方式列表中删除短信验证，得到表3所示的验证方式列表。
表3
邮箱验证
扫脸验证
邮箱验证安保问题验证
然后在表3所示的验证方式列表中查找是否存在指纹验证，且确定表3所示的验证方式列表中不存在指纹验证，则将表3所示的验证方式列表确定为去除后的验证方式列表。
在步骤S203中，获取去除后的验证方式列表中的其中一行中的验证方式。
其中，本发明的目的是从验证方式列表中确定出一行，利用确定出的行中的所有验证方式对用户进行验证；当用户通过了确定出的行中的所有验证方式后，服务器就可以确定用户通过本次验证。
因此，在本发明实施例中，服务器可以主动从去除后的验证方式列表中选择一行，例如随机从去除后的验证方式列表中选择一行，然后获取选择的行中的所有的验证方式。
在本发明另一实施例中，服务器还可以将去除后的验证方式列表发送给终端，以使终端将去除后的验证方式列表显示给用户；用户可以从终端显示的去除后的验证方式列表中选择一行；终端将用户选择的行发送给服务器；服务器获取用户选择的行中的验证方式。
其中，对于用户而言，由于用户必须在通过了验证方式列表中的其中一行中的所有验证方式后，服务器才能确定用户通过本次验证。因此，如果用户选择了一个只包括一个验证方式的行，则用户只要通过了该一个验证方式就可以通过本次验证，如果用户选择了一个包括了多个验证方式的行，则用户需要分别通过该多个验证方式才可以通过本次验证。因此为了能够尽快通过本次验证，用户一般会在去除后的验证方式列表中选择包括的验证方式的数量较少的行。
例如在表3所示的去除后的验证方式列表中，第一行中的验证方式和第二行中的验证方式的数量较少，而第三行中的验证方式的数量较多，因此为了能够通过本次验证，用户一般会选择第一行或第二行。
因此，在本步骤中，如果是服务器主动从去除后的验证方式列表中选择一行，则可以选择包括的验证方式的数量较少的行，以使用户能够尽快通过本次验证。
其中，在前述实施例中已经说明了，只要用户通过了验证方式列表中的任意一行中的所有验证方式，用户就可以通过本次验证。因此，为了能够尽快使得用户通过本次验证，在本发明又一实施例中，在步骤S202之后，参见图3，该方法还包括：
在步骤S301中，判断去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
在有些情况下，如果验证方式列表中的某一行中的所有验证方式均为用户在当前时刻之前的预设时长内通过的验证方式，则在执行步骤S202时就会去除掉该行中的所有验证方式，即该行就不再存在于验证方式列表中，这样，去除后的验证方式列表中的行的数量就小于去除前的验证方式列表中的行的数量。
例如，假设用户在当前时刻之前的预设时长内通过的验证方式为短信验证和人脸验证，则在执行步骤S202时就会从从表1所示的验证方式列表中去除短信验证和人脸验证，得到表4所示的验证方式列表。
表4
邮箱验证
邮箱验证安保问题验证
其中，表4所示的验证方式列表包括2行，而去除前的表1所示的验证方式列表包括3行，这样，则可以确定去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量，然后执行步骤S302。
当去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，在步骤S302中，确定用户通过本次验证；
在本发明实施例中，只要用户通过了验证方式列表中的任意一行中的所有验证方式，就可以通过本次验证。因此，一旦确定出去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量，则说明对于已经被去除的行中的任意一行，用户在当前时刻之前的预设时长内通过了该行中的所有验证方式，因此就无需再对用户进行验证，从而可以确定用户通过本次验证，结束流程。
当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行步骤S203：获取去除后的验证方式列表中的其中一行中的验证方式。
其中，在本发明实施例中，当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，在去除后的验证方式列表中，可能会存在某一行中的验证方式包括另一行中的验证方式的情况，即，该另一行中的验证方式都存在于该某一行，但是该某一行中的验证方式的数量大于该另一行中的验证方式的数量。
例如在表3所示的验证方式列表中，第三行中的验证方式为邮箱验证和安保问题验证，第一行中的验证方式为邮箱验证，第一行中的邮箱验证存在于第三行中，且第三行 中的验证方式的数量大于第一行中国女的验证方式的数量，因此第三行中的验证方式包括第一行中的验证方式。
对于用户而言，选择第一行只需要通过邮箱验证就可以通过本次验证，而选择第三行则不仅需要通过邮箱验证且需要通过安保问题验证才能够通过本次验证。因此，为了能够尽快通过本次验证，在第一行和第三行中，一般情况下，用户会更倾向于选择选择第一行。
然而，有时候服务器也可能会主动从去除后的验证方式列表中选择一行，相对于服务器选择第一行，如果服务器选择了第三行，则用户不仅需要通过邮箱验证且需要通过安保问题验证，这样就无法使用户尽快通过本次验证。
因此，在本发明实施例中，当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，对于去除后的验证方式列表中的任意一行，服务器判断该行中的验证方式是否包括其他行中的验证方式，当该行中的验证方式包括其他行中的验证方式时，从去除后的验证方式列表中删除该行；对于其他每一行，均执行上述操作。
例如，从表3所示的验证方式列表中删除第三行，得到如表5所示的验证方式列表。服务器从表5所示的验证方式列表中选择一行时，除了选择包括扫脸验证的第二行外，只会选择包括邮箱验证的第一行，而不会选择到原来表3中的包括邮箱验证和安保问题验证的第三行。如此，服务器仅仅利用邮箱验证对用户进行验证，用户只要通过了邮箱验证就可以通过本次验证；从而使得用户能够尽快通过验证，提高验证效率。
表5
邮箱验证
扫脸验证
进一步地，在本发明上述实施例中，当服务器利用未通过的验证方式对用户进行验证之后，当用户通过该验证方式时，服务器获取本地的当前时刻并作为用户通过该验证方式时的通过时刻；然后在本地存储的验证方式与通过时刻之间的对应关系中，利用该通过时刻替换与该验证方式对应的通过时刻，以实现对用户通过该验证方式的通过时刻进行更新。
图4是根据一示例性实施例示出的一种验证方法的流程图，如图4所示，该方法包括以下步骤。
在步骤S401中，当需要对用户进行验证时，获取本地的当前时刻；
用户在使用终端的过程中，有时候需要在终端上执行诸如修改账户密码、网络购物或网络转账等与用户的财产安全息息相关的敏感操作，当终端接收到用户输入的与用户的财产安全息息相关的敏感操作时，会生成敏感请求并发送给服务器，当服务器接收到终端发送的敏感请求时，为了对保障用户的财产安全，在响应敏感请求之前，服务器需要对用户的身份进行验证，以确保敏感操作为用户本人执行的操作，当用户通过验证时，服务器再响应敏感请求。
对于服务器而言，当接收到终端发送的敏感请求时，确定需要对用户进行验证，并获取本地的当前时刻。
在步骤S402中，获取在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式；
预设时长可以为技术人员事先在服务器中设置的时长，可以为30秒钟、1分钟或2分钟等，本发明对此不加以限定。
其中，服务器对用户进行验证的验证方式有很多中，例如，短信验证，邮箱验证，人脸验证、安保问题验证和指纹验证等等。
在本发明实施例中，在当前时刻之前的预设时长内，服务器对用户进行验证时可能仅仅利用过上述多种验证方式中的一部分验证方式。
例如，假设预设时长为10分钟。如果在当前时刻之前的10分钟内，服务器利用过短信验证对用户的身份进行验证，则短信验证为在当前时刻之前的预设时长内，对用户进行验证时利用过的验证方式。如果在当前时刻之前的10分钟内，服务器未利用过邮箱验证对用户的身份进行验证，则邮箱验证为在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式。
在步骤S403中，利用未利用过的验证方式对用户进行验证。
其中，在现有技术中，每当用户执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，如果用户在短时间内连续执行多次敏感操作，则在短时间内服务器就会利用相同的验证方式多次对用户进行验证，导致用户体验较低。
而在本发明实施例中，当需要对用户进行验证时，获取在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式；然后以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。
其中，在本发明另一实施例中，参见图5，步骤S402包括：
在步骤S501中，获取验证方式列表；
其中，验证方式列表包括多行，每一行中都包括至少一个验证方式，任意两行中包括的验证方式不完全相同。如果某一行中包括多个验证方式，则该行中的任意两个验证方式都不相同。
例如，验证方式列表可以如下表1所示，表1包括三行，第一行包括两个验证方式，分别为短信验证和邮箱验证；第二行包括一个验证方式，为人脸验证；第三行包括两个验证方式，分别为邮箱验证和安保问题验证。
表6
短信验证邮箱验证
人脸验证
邮箱验证安保问题验证
在步骤S502中，从验证方式列表中去除在当前时刻之前的预设时长内，对用户进行验证时利用过的验证方式；
具体地，本步骤可以通过如下流程实现，包括：
21)、获取验证方式与验证时刻之间的对应关系；
在本发明实施例中，每当服务器利用某一验证方式对用户进行验证时，服务器会就获取本地的当前时刻并作为对用户进行验证时的验证时刻；然后在本地存储的验证方式与验证时刻之间的对应关系中查找是否存在该验证方式。
当上述对应关系中不存在该验证方式时，说明之前未曾利用过该验证方式对用户进行验证，此时可以将该验证方式与该验证时刻作为一条记录存储在上述对应关系中。
当上述对应关系中存在该验证方式时，则说明之前利用过该验证方式对用户进行验证，此时需要在上述对应关系中查找与该验证方式对应的验证时刻，然后利用获取的验证时刻替换查找到的验证时刻，以实现利用该验证方式对用户进行验证时的验证时刻进行更新。
这样，如果需要查找在历史过程中最近一次利用某一验证方式对用户进行验证时的验证时刻，服务器可以获取本地存储的验证方式与验证时刻之间的对应关系，然后在上述对应关系中查找与该验证方式对应的验证时刻，从而得到在历史过程中最近一次利用该验证方式对用户进行验证时的验证时刻。
例如，验证方式与验证时刻之间的对应关系可以如下表7所示。
表7
验证方式 验证时刻
邮箱验证 09:09:22
短信验证 13:05:27
人脸验证 12:08:12
安保问题验证 11:32:45
指纹验证 13:01:21
其中，如表7所示，在历史过程中，对用户进行验证时利用过的验证方式包括邮箱验证、短信验证、人脸验证、安保问题验证以及指纹验证。其中，最近一次利用邮箱验证对用户进行验证时的验证时刻为09:09:22，最近一次利用短信验证对用户进行验证时的验证时刻为13:05:27，最近一次利用人脸验证对用户进行验证时的验证时刻为12:08:12，最近一次利用安保问题验证对用户进行验证时的验证时刻为11:32:45，以及最近一次利用邮指纹验证对用户进行验证时的验证时刻为13:01:21。
22)、在上述对应关系中查找与当前时刻之间的距离小于预设时长的验证时刻对应的验证方式；
对于上述对应关系中的任一条记录，获取该记录中包括的验证时刻，将当前时刻与该验证时刻进行减法运算得到一时长，将该时长与预设时长进行比较，如果该时长小于预设时长，则获取该记录中包括的验证方式，并作为与当前时刻之间的距离小于预设时长的验证时刻对应的验证方式。
对于上述对应关系中的其他每一条记录，均执行上述操作，如此实现从对应关系中查找到所有与当前时刻之间的距离小于预设时长的验证时刻对应的验证方式。
例如，假设当前时刻为13:10:04，且预设时长为10分钟。则在表2所示的对应关系中可以查找到与当前时刻13:10:04之间距离小于10分钟的验证时刻分别为13:05:27和13:01:21，以及可以确定出这两个验证时刻对应的验证方式分别为短信验证和指纹验证。
23)、从验证方式列表中删除查找到的验证方式。
具体地，对于在步骤22)中查找到的任一个验证方式，在验证方式列表中查找是否存在该验证方式，当验证方式列表中存在该验证方式时，从验证列表中删除该验证方式；对于步骤22)查找到的其他每一个验证方式，均执行上述操作，如此实现从验证方式列表中删除在步骤22)中查找到的所有验证方式。
例如，在步骤22)中的例子中，查找到的验证方式分别为短信验证和指纹验证；则在表6所示的验证方式列表中查找是否存在短信验证，且确定表6所示的验证方式列表 中存在短信验证，则从表6所示的验证方式列表中删除短信验证，得到表8所示的验证方式列表。
表8
邮箱验证
扫脸验证
邮箱验证安保问题验证
然后在表8所示的验证方式列表中查找是否存在指纹验证，且确定表3所示的验证方式列表中不存在指纹验证，则将表3所示的验证方式列表确定为去除后的验证方式列表。
在步骤S503中，获取去除后的验证方式列表中的其中一行中的验证方式。
其中，本发明的目的是从验证方式列表中确定出一行，利用确定出的行中的所有验证方式对用户进行验证；当用户通过了确定出的行中的所有验证方式后，服务器就可以确定用户通过本次验证。
因此，在本发明实施例中，服务器可以主动从去除后的验证方式列表中选择一行，例如随机从去除后的验证方式列表中选择一行，然后获取选择的行中的所有的验证方式。
在本发明另一实施例中，服务器还可以将去除后的验证方式列表发送给终端，以使终端将去除后的验证方式列表显示给用户；用户可以从终端显示的去除后的验证方式列表中选择一行；终端将用户选择的行发送给服务器；服务器获取用户选择的行中的验证方式。
其中，对于用户而言，由于用户必须在通过了验证方式列表中的其中一行中的所有验证方式后，服务器才能确定用户通过本次验证。因此，如果用户选择了一个只包括一个验证方式的行，则用户只要通过了该一个验证方式就可以通过本次验证，如果用户选择了一个包括了多个验证方式的行，则用户需要分别通过该多个验证方式才可以通过本次验证。因此为了能够尽快通过本次验证，用户一般会在去除后的验证方式列表中选择包括的验证方式的数量较少的行。
例如在表8所示的去除后的验证方式列表中，第一行中的验证方式和第二行中的验证方式的数量较少，而第三行中的验证方式的数量较多，因此为了能够通过本次验证，用户一般会选择第一行或第二行。
因此，在本步骤中，如果是服务器主动从去除后的验证方式列表中选择一行，则可以选择包括的验证方式的数量较少的行，以使用户能够尽快通过本次验证。
其中，在前述实施例中已经说明了，只要用户通过了验证方式列表中的任意一行中的所有验证方式，用户就可以通过本次验证。因此，为了能够尽快使得用户通过本次验证，在本发明又一实施例中，在步骤S502之后，参见图6，该方法还包括：
在步骤S601中，判断去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
在有些情况下，如果验证方式列表中的某一行中的所有验证方式均为用户在当前时刻之前的预设时长内通过的验证方式，则在执行步骤S502时就会去除掉该行中的所有验证方式，即该行就不再存在于验证方式列表中，这样，去除后的验证方式列表中的行的数量就小于去除前的验证方式列表中的行的数量。
例如，假设在当前时刻之前的预设时长内对用户进行验证时利用过的验证方式为短信验证和人脸验证，则在步骤S502之后，即从表6所示的验证方式列表中去除短信验证和人脸验证之后，可以得到表9所示的验证方式列表。
表9
邮箱验证
邮箱验证安保问题验证
其中，表9所示的验证方式列表包括2行，而去除前的表6所示的验证方式列表包括3行，这样，则确定去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量，然后执行步骤S602。
当去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，在步骤S602中，确定用户通过本次验证；
在本发明实施例中，只要用户通过了验证方式列表中的任意一行中的所有验证方式，就可以通过本次验证。因此，一旦确定出去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量，则说明对于已经被去除的行中的任意一行，用户在当前时刻之前的预设时长内通过了该行中的所有验证方式，因此就无需再对用户进行验证，从而确定用户通过本次验证，结束流程。
当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行步骤S503：获取去除后的验证方式列表中的其中一行中的验证方式。
其中，在本发明实施例中，当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，在去除后的验证方式列表中，可能会存在某一行中的验证 方式包括另一行中的验证方式的情况，即，该另一行中的验证方式都存在于该某一行，但是该某一行中的验证方式的数量大于该另一航中的验证方式的数量。
例如在表8所示的验证方式列表中，第三行中的验证方式为邮箱验证和安保问题验证，第一行中的验证方式为邮箱验证，第一行中的邮箱验证存在于第三行中，且第三行中的验证方式的数量大于第一行中国女的验证方式的数量，因此第三行中的验证方式包括第一行中的验证方式。
对于用户而言，选择第一行只需要通过邮箱验证就可以通过本次验证，而选择第三行则不仅需要通过邮箱验证且需要通过安保问题验证才能够通过本次验证。因此，为了能够尽快通过本次验证，在第一行和第三行中，一般情况下，用户会更倾向于选择选择第一行。
然而，有时候服务器也可能会主动从去除后的验证方式列表中选择一行，相对于服务器选择第一行，如果服务器选择了第三行，则用户不仅需要通过邮箱验证且需要通过安保问题验证，这样就无法使用户尽快通过本次验证。
因此，在本发明实施例中，当去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，对于去除后的验证方式列表中的任意一行，服务器判断该行中的验证方式是否包括其他行中的验证方式，当该行中的验证方式包括其他行中的验证方式包括时，从去除后的验证方式列表中删除该行；对于其他每一行，均执行上述操作。
例如，从表8所示的验证方式列表中删除第三行，得到如表10所示的验证方式列表。服务器从表10所示的验证方式列表中选择一行时，除了选择包括扫脸验证的第二行外，只会选择包括邮箱验证的第一行，而不会选择到原来表8中的包括邮箱验证和安保问题验证的第三行。如此，服务器仅仅利用邮箱验证对用户进行验证，用户只要通过了邮箱验证就可以通过本次验证；从而使得用户能够尽快通过验证，提高验证效率。
表10
邮箱验证
扫脸验证
进一步地，在本发明上述实施例中，当服务器利用未利用过的验证方式对用户进行验证时，服务器获取本地的当前时刻并作为利用未利用过的验证方式对用户进行验证时验证时刻；然后在本地存储的验证方式与验证时刻之间的在对应关系中，利用该验证时刻替换与该验证方式对应的验证时刻，以实现对利用该验证方式对用户进行验证时的验证时刻进行更新。
图7是根据一示例性实施例示出的一种验证装置的框图。参照图7，该装置包括：
第一当前时刻获取模块11，用于当需要对用户进行验证时，获取本地的当前时刻；
第一验证方式获取模块12，用于获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式；
第一验证模块13，用于利用所述未通过的验证方式对所述用户进行验证。
其中，在现有技术中，每当用户执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，如果用户在短时间内连续执行多次敏感操作，则在短时间内服务器就会利用相同的验证方式多次对用户进行验证，导致用户体验较低。
而在本发明实施例中，当需要对用户进行验证时，获取在当前时刻之前的预设时长内用户未通过的验证方式；然后以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。
其中，所述第一验证方式获取模块12包括：
第一验证方式列表获取单元，用于获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
第一去除单元，用于从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式；
第一验证方式获取单元，用于获取所述去除后的验证方式列表中的其中一行中的验证方式。
其中，所述第一去除单元包括：
第一获取子单元，用于获取本地存储的验证方式与通过时刻之间的对应关系；
第一查找子单元，用于在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的通过时刻对应的验证方式；
第一删除子单元，用于从所述验证方式列表中删除所述查找到的验证方式。
进一步地，所述装置还包括：
通过时刻获取模块，用于当所述用户通过所述未通过的验证方式时，获取本地的当前时刻并确定为所述用户通过所述未通过的验证方式时的通过时刻；
第一替换模块，用于在所述对应关系中，利用所述确定的通过时刻替换与所述未通过的验证方式对应的通过时刻。
进一步地，所述第一验证方式获取模块12还包括：
第一判断单元，用于判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
第一确定单元，用于当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
所述第一验证方式获取单元还用于当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
图8是根据一示例性实施例示出的一种验证装置的框图。参照图8，该装置包括：
第二当前时刻获取模块21，用于当需要对用户进行验证时，获取本地的当前时刻；
第二验证方式获取模块22，用于获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式；
第二验证模块23，用于利用所述未利用过的验证方式对所述用户进行验证。
其中，在现有技术中，每当用户执行一次敏感操作服务器都会利用短信验证对用户的身份进行验证，如果用户在短时间内连续执行多次敏感操作，则在短时间内服务器就会利用相同的验证方式多次对用户进行验证，导致用户体验较低。
而在本发明实施例中，当需要对用户进行验证时，获取在当前时刻之前的预设时长内，对用户进行验证时未利用过的验证方式；然后以获取的验证方式对用户进行验证，避免利用相同的验证方式在短时间内多次对用户进行验证，从而提高用户体验。
其中，所述第二验证方式获取模块22，包括：
第二验证方式列表获取单元，用于获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
第二去除单元，用于从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式；
第二验证方式获取单元，用于获取所述去除后的验证方式列表中的其中一行中的验证方式。
其中，所述第二去除单元包括：
第二获取子单元，用于获取本地存储的验证方式与验证时刻之间的对应关系；
第二查找子单元，用于在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的验证时刻对应的验证方式；
第二删除子单元，用于从所述验证方式列表中删除所述查找到的验证方式。
进一步地，所述装置还包括：
验证时刻获取模块，用于当利用所述未通过的验证方式对所述用户进行验证时，获取本地的当前时刻并确定为利用所述未利用过的验证方式对用户进行验证时验证时刻；
第二替换模块，用于在所述对应关系中，利用所述确定出的验证时刻替换与所述未利用过的验证方式对应的验证时刻。
进一步地，所述第二验证方式获取模块22还包括：
第二判断单元，用于判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
第二确定单元，用于当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
所述第二验证方式获取单元还用于当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本申请旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本发明未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由所附的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (12)

  1. 一种验证方法，其特征在于，所述方法包括：
    当需要对用户进行验证时，获取本地的当前时刻；
    获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式；
    利用所述未通过的验证方式对所述用户进行验证。
  2. 根据权利要求1所述的方法，其特征在于，所述获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式，包括：
    获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
    从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式；
    获取所述去除后的验证方式列表中的其中一行中的验证方式。
  3. 根据权利要求2所述的方法，其特征在于，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式，包括：
    获取本地存储的验证方式与通过时刻之间的对应关系；
    在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的通过时刻对应的验证方式；
    从所述验证方式列表中删除所述查找到的验证方式。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    当所述用户通过所述未通过的验证方式时，获取本地的当前时刻并确定为所述用户通过所述未通过的验证方式时的通过时刻；
    在所述对应关系中，利用所述确定的通过时刻替换与所述未通过的验证方式对应的通过时刻。
  5. 根据权利要求2-4任一项权利要求所述的方法，其特征在于，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内所述用户通过的验证方式之后，还包括：
    判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中 的行的数量；
    当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
    当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
  6. 一种验证方法，其特征在于，所述方法包括：
    当需要对用户进行验证时，获取本地的当前时刻；
    获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式；
    利用所述未利用过的验证方式对所述用户进行验证。
  7. 根据权利要求6所述的方法，其特征在于，所述获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式，包括：
    获取验证方式列表；所述验证方式列表中的每一行均包括至少一个验证方式；
    从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式；
    获取所述去除后的验证方式列表中的其中一行中的验证方式。
  8. 根据权利要求7所述的方法，其特征在于，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式，包括：
    获取本地存储的验证方式与验证时刻之间的对应关系；
    在所述对应关系中查找与所述当前时刻之间的距离小于预设时长的验证时刻对应的验证方式；
    从所述验证方式列表中删除所述查找到的验证方式。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    当利用所述未通过的验证方式对所述用户进行验证时，获取本地的当前时刻并确定为利用所述未利用过的验证方式对用户进行验证时验证时刻；
    在所述对应关系中，利用所述确定出的验证时刻替换与所述未利用过的验证方式对 应的验证时刻。
  10. 根据权利要求7-9任一项权利要求所述的方法，其特征在于，所述从所述验证方式列表中去除在所述当前时刻之前的预设时长内，对所述用户进行验证时利用过的验证方式之后，还包括：
    判断所述去除后的验证方式列表中的行的数量是否小于去除前的验证方式列表中的行的数量；
    当所述去除后的验证方式列表中的行的数量小于去除前的验证方式列表中的行的数量时，确定所述用户通过本次验证；
    当所述去除后的验证方式列表中的行的数量等于去除前的验证方式列表中的行的数量时，执行所述获取所述去除后的验证方式列表中的其中一行中的验证方式的步骤。
  11. 一种验证装置，其特征在于，所述装置包括：
    第一当前时刻获取模块，用于当需要对用户进行验证时，获取本地的当前时刻；
    第一验证方式获取模块，用于获取在所述当前时刻之前的预设时长内所述用户未通过的验证方式；
    第一验证模块，用于利用所述未通过的验证方式对所述用户进行验证。
  12. 一种验证装置，其特征在于，所述装置包括：
    第二当前时刻获取模块，用于当需要对用户进行验证时，获取本地的当前时刻；
    第二验证方式获取模块，用于获取在所述当前时刻之前的预设时长内，对所述用户进行验证时未利用过的验证方式；
    第二验证模块，用于利用所述未利用过的验证方式对所述用户进行验证。
PCT/CN2016/108633 2015-12-16 2016-12-06 验证方法及装置 WO2017101704A1 (zh)

Priority Applications (10)

Application Number Priority Date Filing Date Title
JP2018532099A JP6795598B2 (ja) 2015-12-16 2016-12-06 照合方法及びデバイス
SG11201805147YA SG11201805147YA (en) 2015-12-16 2016-12-06 Verification method and device
MYPI2018000937A MY186946A (en) 2015-12-16 2016-12-06 Verification method and device
KR1020187020365A KR102365586B1 (ko) 2015-12-16 2016-12-06 검증 방법 및 디바이스
EP16874761.6A EP3393080B1 (en) 2015-12-16 2016-12-06 Verification method and device
AU2016372750A AU2016372750A1 (en) 2015-12-16 2016-12-06 Verification method and device
PH12018501271A PH12018501271A1 (en) 2015-12-16 2018-06-14 Verification method and device
US16/009,424 US10686801B2 (en) 2015-12-16 2018-06-15 Selecting user identity verification methods based on verification results
US16/720,337 US11196753B2 (en) 2015-12-16 2019-12-19 Selecting user identity verification methods based on verification results
AU2020260569A AU2020260569A1 (en) 2015-12-16 2020-10-30 Verification method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510946529.7 2015-12-16
CN201510946529.7A CN106888195B (zh) 2015-12-16 2015-12-16 验证方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/009,424 Continuation US10686801B2 (en) 2015-12-16 2018-06-15 Selecting user identity verification methods based on verification results

Publications (1)

Publication Number Publication Date
WO2017101704A1 true WO2017101704A1 (zh) 2017-06-22

Family

ID=59055810

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/108633 WO2017101704A1 (zh) 2015-12-16 2016-12-06 验证方法及装置

Country Status (10)

Country Link
US (2) US10686801B2 (zh)
EP (1) EP3393080B1 (zh)
JP (1) JP6795598B2 (zh)
KR (1) KR102365586B1 (zh)
CN (1) CN106888195B (zh)
AU (2) AU2016372750A1 (zh)
MY (1) MY186946A (zh)
PH (1) PH12018501271A1 (zh)
SG (1) SG11201805147YA (zh)
WO (1) WO2017101704A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106888195B (zh) * 2015-12-16 2020-05-05 阿里巴巴集团控股有限公司 验证方法及装置
CN110087235B (zh) * 2019-05-08 2022-07-29 北京芯盾时代科技有限公司 一种身份认证、认证方式调整的方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136582A1 (en) * 2005-12-13 2007-06-14 Giuseppe Longobardi Method and system for transaction validation
CN101090575A (zh) * 2006-06-15 2007-12-19 株式会社卡西欧日立移动通信 便携式电子装置
CN101686126A (zh) * 2008-09-24 2010-03-31 北京创原天地科技有限公司 一套新型动态密码认证和实名上网的方法
CN102685106A (zh) * 2012-03-27 2012-09-19 北京百纳威尔科技有限公司 一种安全验证方法及设备

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE10249801B3 (de) * 2002-10-24 2004-05-06 Giesecke & Devrient Gmbh Verfahren zum Ausführen einer gesicherten elektronischen Transaktion unter Verwendung eines tragbaren Datenträgers
DE102004014416A1 (de) * 2004-03-18 2005-10-06 Deutsche Telekom Ag Verfahren und System zur Personen/Sprecherverifikation über Kommunikationssysteme
JP4471898B2 (ja) * 2005-07-22 2010-06-02 シャープ株式会社 携帯情報端末装置
KR20070016534A (ko) * 2005-08-04 2007-02-08 (주)링스텔레콤 디티엠에프 톤 형태의 일회용 패스워드 발생장치, 상기일회용 패스워드 발생장치를 이용한 전화 거래 인증방법 및시스템
JP2007272600A (ja) * 2006-03-31 2007-10-18 Fujitsu Ltd 環境認証と連携した本人認証方法、環境認証と連携した本人認証システムおよび環境認証と連携した本人認証用プログラム
DE102007007345A1 (de) * 2007-02-14 2008-08-21 Siemens Enterprise Communications Gmbh & Co. Kg Verfahren und Anordnung zum Bereitstellen eines drahtlosen Mesh-Netzwerks
CN101087193A (zh) * 2007-02-27 2007-12-12 马骏 使用与帐号绑定的手机号码进行身份确认的新方法
JP5012247B2 (ja) * 2007-06-21 2012-08-29 ソニー株式会社 認証装置、入場管理装置、入退場管理装置、入場管理システム、入退場管理システム、認証処理方法およびプログラム
WO2009075180A1 (ja) * 2007-12-11 2009-06-18 Nec Corporation 認証装置、認証システム、認証方法及びプログラム
US8087071B2 (en) * 2008-12-05 2011-12-27 International Business Machines Corporation Authentication method and system
US20110017608A1 (en) 2009-07-27 2011-01-27 Faraday Technology, Inc. Electrochemical etching and polishing of conductive substrates
US8756661B2 (en) 2009-08-24 2014-06-17 Ufp Identity, Inc. Dynamic user authentication for access to online services
CN102110200A (zh) * 2009-12-25 2011-06-29 凹凸电子（武汉）有限公司 计算机可执行的认证方法
US8442297B2 (en) * 2010-02-23 2013-05-14 Arinc Incorporated Methods of evaluating the quality of two-dimensional matrix dot-peened marks on objects and mark verification systems
US8910279B2 (en) * 2010-03-10 2014-12-09 Sonicwall, Inc. Reputation-based threat protection
CN102073810B (zh) * 2010-12-06 2013-01-23 上海合合信息科技发展有限公司 输入法软件中集成账户管理功能的方法
US9955014B2 (en) * 2010-12-29 2018-04-24 Avaya Inc. Method and system for delivering messages
JP5679567B2 (ja) * 2011-03-31 2015-03-04 西日本電信電話株式会社 認証支援装置、認証支援方法
US20130104187A1 (en) * 2011-10-18 2013-04-25 Klaus Helmut Weidner Context-dependent authentication
US9519769B2 (en) * 2012-01-09 2016-12-13 Sensible Vision, Inc. System and method for disabling secure access to an electronic device using detection of a predetermined device orientation
SG194267A1 (en) * 2012-05-03 2013-11-29 C3S Pte Ltd Method and system for protecting a password during an authentication process
CN102684882B (zh) * 2012-05-16 2016-08-03 中国科学院计算机网络信息中心 验证方法和验证设备
KR101367621B1 (ko) * 2012-06-28 2014-02-28 삼성에스디에스 주식회사 Ｏｔｐ 기반 인증 시스템 및 방법
WO2014049854A1 (ja) * 2012-09-28 2014-04-03 株式会社日立製作所 計算機システム、及びプログラム
CN103927464A (zh) * 2013-01-11 2014-07-16 深圳市腾讯计算机系统有限公司 共同验证方法、二维码生成方法、设备和系统
US8917939B2 (en) * 2013-02-21 2014-12-23 International Business Machines Corporation Verifying vendor identification and organization affiliation of an individual arriving at a threshold location
JP6048210B2 (ja) * 2013-02-26 2016-12-21 沖電気工業株式会社 情報処理装置及びプログラム
JP6081857B2 (ja) * 2013-04-26 2017-02-15 エヌ・ティ・ティ・コミュニケーションズ株式会社 認証システムおよび認証方法
US10331866B2 (en) * 2013-09-06 2019-06-25 Apple Inc. User verification for changing a setting of an electronic device
US20150186628A1 (en) * 2013-12-27 2015-07-02 Isabel F. Bush Authentication with an electronic device
CN105101196B (zh) * 2014-05-06 2018-11-02 阿里巴巴集团控股有限公司 一种用户账户管理方法及装置
US9363263B2 (en) 2014-08-27 2016-06-07 Bank Of America Corporation Just in time polymorphic authentication
CN105518713A (zh) * 2015-02-15 2016-04-20 北京旷视科技有限公司 活体人脸验证方法及系统、计算机程序产品
CN106888195B (zh) * 2015-12-16 2020-05-05 阿里巴巴集团控股有限公司 验证方法及装置
US10762262B1 (en) * 2017-11-03 2020-09-01 Synopsys, Inc. Multi-dimensional constraint solver using modified relaxation process

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136582A1 (en) * 2005-12-13 2007-06-14 Giuseppe Longobardi Method and system for transaction validation
CN101090575A (zh) * 2006-06-15 2007-12-19 株式会社卡西欧日立移动通信 便携式电子装置
CN101686126A (zh) * 2008-09-24 2010-03-31 北京创原天地科技有限公司 一套新型动态密码认证和实名上网的方法
CN102685106A (zh) * 2012-03-27 2012-09-19 北京百纳威尔科技有限公司 一种安全验证方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3393080A4 *

Also Published As

Publication number Publication date
AU2020260569A1 (en) 2020-11-26
US20200128021A1 (en) 2020-04-23
KR102365586B1 (ko) 2022-02-18
PH12018501271A1 (en) 2019-01-28
CN106888195B (zh) 2020-05-05
US10686801B2 (en) 2020-06-16
EP3393080B1 (en) 2023-04-05
EP3393080A4 (en) 2018-10-24
EP3393080A1 (en) 2018-10-24
JP2019507408A (ja) 2019-03-14
JP6795598B2 (ja) 2020-12-02
KR20180095885A (ko) 2018-08-28
US20180309767A1 (en) 2018-10-25
AU2016372750A1 (en) 2018-07-05
SG11201805147YA (en) 2018-07-30
CN106888195A (zh) 2017-06-23
US11196753B2 (en) 2021-12-07
MY186946A (en) 2021-08-26

Similar Documents

Publication Publication Date Title
US10880306B2 (en) Verification information update
US9432339B1 (en) Automated token renewal using OTP-based authentication codes
US10013692B2 (en) Systems and methods for authorizing transactions via a digital device
US10454913B2 (en) Device authentication agent
US11374767B2 (en) Key-based authentication for backup service
US10630488B2 (en) Method and apparatus for managing application identifier
CN108111473B (zh) 混合云统一管理方法、装置和系统
BR112013018940B1 (pt) método e aparelho para gerenciar identidade para terminal móvel
US9747434B1 (en) Authenticating with an external device by providing a message having message fields arranged in a particular message field order
WO2016076913A1 (en) Conditional login promotion
US9294474B1 (en) Verification based on input comprising captured images, captured audio and tracked eye movement
EP3178191B1 (en) Mitigating risk of account enumeration
TW201430607A (zh) 判定認證能力之查詢系統及方法
WO2019118218A1 (en) Methods and systems for securing and recovering a user passphrase
CN112581233A (zh) 订单离线操作的方法、装置、设备和计算机可读存储介质
WO2017101704A1 (zh) 验证方法及装置
CN107566329A (zh) 一种访问控制方法及装置
WO2018036220A1 (zh) 一种接入无线设备的权限认证方法及系统
WO2015018311A1 (en) Method and apparatus for verifying captcha
JP2019506660A (ja) データ漏洩検出システム
US9614835B2 (en) Automatic provisioning of a device to access an account
CN103384249A (zh) 网络接入认证方法、装置及系统、认证服务器
KR102087287B1 (ko) 대화형 메시징 기반의 이벤트 실행이 가능한 챗봇 시스템 서버 및 그 동작 방법
WO2016112792A1 (zh) 身份认证方法及装置
US10298575B2 (en) Multicomputer processing of an event authentication request with centralized event orchestration

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16874761

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 12018501271

Country of ref document: PH

WWE Wipo information: entry into national phase

Ref document number: 11201805147Y

Country of ref document: SG

Ref document number: 2018532099

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016372750

Country of ref document: AU

Date of ref document: 20161206

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20187020365

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187020365

Country of ref document: KR

Ref document number: 2016874761

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2016874761

Country of ref document: EP

Effective date: 20180716