Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the appended claims.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The specification provides a verification scheme, when a password to be verified is not matched with a preset legal password, a verification assistance request can be sent to a trusted third party, whether the verification is passed or not is confirmed by the trusted third party, and therefore the fact that a legal user can still pass the verification when forgetting the password and losing the wrong password is ensured, and the use experience of special groups such as old people and disabled people is improved.
The verification scheme can be applied to electronic equipment such as mobile phones, tablet computers and electronic door locks.
For example, the method can be applied to unlocking operation of the electronic equipment, and the unlocking password is verified.
The verification scheme can also be applied to internet service operation.
For example, the method can be applied to login operation of a user account, and the login password is verified.
For another example, the method can be applied to the implementation operation of electronic services, the verification of payment passwords in the electronic payment services, the verification of transfer passwords in the electronic transfer services and the like.
The application scenario is only an exemplary illustration, and the verification scheme provided in this specification may also be applied to other scenarios, which is not described herein any more.
Fig. 1 is a schematic flow chart of a verification method according to an exemplary embodiment of the present disclosure.
Referring to fig. 1, the verification method may include the following steps:
step 102, after receiving the password to be verified, judging whether the password to be verified matches a preset legal password.
In this embodiment, the validity of the operation request for the verifier may be verified.
For example, when the verification method is applied to an unlocking operation of an electronic device, the verifier is usually the electronic device, and the operation request is an unlocking request.
For another example, when the verification method is applied to an electronic payment service, the verifier is usually a payment account, and the operation request is a payment request.
In this embodiment, the valid password may be a character password, a gesture password, and the like, which is not limited in this specification.
And 104, if the verification request is not matched with the trusted third party, sending a verification assistance request to the trusted third party bound by the verifier through a preset communication channel.
In an example, when a user unlocks an electronic device, if a password input by the user does not match a legal unlocking password, the electronic device may send a verification assistance request to a trusted third party bound to the electronic device through a predetermined communication channel to request the trusted third party to perform validity confirmation on the current unlocking request.
The trusted third party may be preset by the legitimate owner of the electronic device, e.g., a teenager may bind his electronic device to a parent, etc.
In another example, when the user is performing an electronic payment service, if the input password does not match a legal payment password, the payment platform may send a verification assistance request to a trusted third party bound to the payment account through a predetermined communication channel, so as to request the trusted third party to perform validity confirmation on the payment request.
The trusted third party may be pre-set by the payer, e.g., the elderly may bind their payment account with children, etc.
In this embodiment, the predetermined communication channel may include: a voice channel, a short message channel, an instant communication channel, etc., which are not limited in this specification.
And 106, in response to a verification passing instruction input by the trusted third party for the verification assistance request, canceling the verification operation of the verifier according to a preset cancellation strategy.
In this embodiment, the trusted third party may perform validity check on the operation request.
If the trusted third party determines that the operation request is legal, a verification passing instruction can be input, and the verification operation of the operation request facing the verifier can be cancelled based on the verification passing instruction.
For example, the verification of the present operation request is cancelled, the lock of the electronic device is released, the payment request is processed, and the like.
For another example, a verification operation for an operation request to the verifier is cancelled for a predetermined cancellation time period, and the like.
If the trusted third party determines that the operation request is risky, a verification failing instruction can be input, and the operation request can be rejected based on the verification failing instruction.
For example, the electronic device is kept locked and a password error is prompted.
For another example, the payment request is rejected, and a prompt of payment failure is returned to the payer.
The above description shows that the verification assisting request can be sent to the trusted third party when the password to be verified does not match the preset legal password, and the trusted third party confirms whether the password passes the verification, so that the legal user can still pass the verification when forgetting the password and losing the wrong password, and the use experience of special groups such as the old, the disabled and the like is improved.
The following describes in detail a specific implementation process of the present specification by taking an example in which an application scenario is an electronic payment scenario, a verifier is a payment account, and an operation request is a payment request.
Because the electronic payment scene has very high requirements on safety, many electronic payment scenes can adopt biometric identification schemes such as fingerprint identification and face recognition to check payment requests. However, these biometric schemes are not friendly to a particular group of the elderly, the disabled, and the like, for example, fingerprints of the elderly are generally faded, and the like, and recording and recognition of fingerprints are difficult, and the like.
In view of the above problems, the present embodiment provides a simple and safe verification method for special groups such as the elderly and the disabled.
The verification method can be realized by adopting a character password. Taking digital password as an example, the password is different from the traditional 4-bit short password and 6-bit long password, and the length of the password can be defined by the old for the convenience of the old to remember. More simply, the elderly may set a digital code that is less than 4 bits, such as a 1-bit digital code, a 2-bit digital code, or a 3-bit digital code.
For example, zhangongbo has poor memorability, but son zhang has a birth date of 18, he does not forget, and to avoid forgetting, zhangbo may set the payment password to 18.
In this embodiment, the number of cipher retries may be positively correlated with the cipher length. The shorter the password length, the less difficulty in memorizing, so that a relatively small number of password retries can be set, for example, for a numeric password having a length of 1, the number of password retries can be set to 2. Conversely, the longer the password length, the greater the difficulty of memorizing, so a relatively large number of password retries can be set, for example, for a digital password of length 3, the number of password retries can be set to 4, and so on.
Fig. 2 is a schematic flow chart of another verification method according to an exemplary embodiment of the present disclosure.
Referring to fig. 2, the verification method may include the following steps:
step 202, when the payment platform receives the payment request, it determines whether the password to be verified matches a legal payment password preset by the payment account.
In this embodiment, if the password to be verified matches a valid payment password preset by the payment account, the payment platform may perform a payment operation.
If the password to be verified does not match the valid payment password preset by the payment account, step 204 may be executed.
At step 204, the payment platform determines whether a number of password retries has been reached.
If the password retry times are not reached, the payment platform can return a prompt of password error to the payer and guide the payer to input the password again.
If the number of password retries has been reached, step 206 may be performed.
In step 206, the payment platform sends a verification assistance request to the trusted third party bound to the payment account through a predetermined communication channel.
In this embodiment, the payment platform may send a verification assistance request to a payment client of the payer, and the payment client may further display a communication button to the payer. The communication button can be used for sending a verification assistance request to a trusted third party bound by the payment account through a corresponding communication channel.
In one example, the communication button may be a push button for a push-to-call trusted third party. When the payer triggers the one-key call button, a voice call request can be sent to the trusted third party, and the payer can communicate with the trusted third party after answering so as to request the trusted third party to assist the trusted third party in payment verification.
In another example, the communication button may also be a short message button. When the payer triggers the short message button, a verification assistance request can be sent to the trusted third party through the short message, and the short message can include information such as payment amount, payment reason, payee and the like of the electronic payment service. Of course, when the payer triggers the short message button, the payment client of the payer may also pop up a short message editing box to allow the payer to edit the information to be sent by himself, which is not limited in this specification.
In another example, the communication button may also be a voice button. When the payer triggers the voice button, the verification assistance request can be sent to the trusted third party through a voice message, for example, the voice message is sent to the payment client of the trusted third party. The voice message can also comprise information of the payment amount, the payment reason, the payee and the like of the electronic payment service. Similar to the short message button, when the payer triggers the voice button, the payer may dictate a voice to the trusted third party.
Of course, the communication button may also be an instant communication button or the like, and this specification does not specifically limit this.
In this embodiment, the payment client of the payer may display the above-mentioned one communication button, and may also display a plurality of different communication buttons corresponding to different communication modes for the payer to select.
Of course, in other embodiments, the communication button may not be displayed to the payer, and the verification assistance request may be directly sent to the trusted third party according to a predetermined communication channel, which is not limited in this specification.
And step 208, trusting a third party to input a verification passing instruction for the verification assistance request.
In this embodiment, when receiving the verification assistance request, the trusted third party may assist the payment platform in determining whether the payment request is initiated by a legitimate user. For example, Zhang III may recognize the voice of the payment request initiating user based on a voice message to determine whether the payment request initiating user is Zhang magna, etc.
If the trusted third party confirms that the payment request is initiated by a legal user and no security risk exists, a verification passing instruction can be input.
For example, the trusted third party may enter the verification pass instruction through its payment client.
As another example, the trusted third party may enter the verification pass instruction via a short message.
If the trusted third party confirms that the payment request is not initiated by a legal user and has a security risk, a verification failure instruction can be input. The payment platform can further refuse to execute the electronic payment service and return a corresponding risk prompt.
And step 210, canceling the verification operation by the payment platform according to the payment request of the payment account.
In this embodiment, after receiving the verification passing instruction input by the trusted third party, the payment platform may cancel the verification operation of the verifier according to a predetermined cancellation policy.
In one example, the cancellation policy may be to cancel a validation operation for a payment request from the payment account within a predetermined number of times. The predetermined number of times may be preset or may be specified by a trusted third party when the verification passing instruction is input, for example, 1 time, 3 times, and the like.
And if the preset times are 3 times, the payment platform can execute the payment operation. The payment platform also does not need to be verified for the next two electronic payment requests from the payment account. For example, the payment platform returns a cancellation instruction to the client of the payment account, and when the payer uses the payment client again to pay, the payment client can skip the password acquisition step, that is, a password input box does not need to be popped up, the payment request can be directly sent to the payment platform, the payment platform does not need to check the payment request, and the corresponding deduction operation can be directly executed.
In another example, the cancellation policy may also be to cancel a verification operation for a payment request from the payment account within a predetermined cancellation period. The cancellation period may be preset or may be specified by a trusted third party when a verification pass instruction is input, for example, 1 hour, 2 hours, or the like.
Assuming that the cancellation period is 2 hours, no verification is required for the payment request from the payment account in the next two hours.
The foregoing cancellation policy is only an exemplary illustration, and in practical applications, other cancellation policies may also be set, and this specification does not limit this to any particular one.
It is noted that payment platforms often follow a timeout mechanism when performing payment operations. If the verification passing instruction is received within the overtime, the payment operation can be executed. If the verification passing instruction is not received within the overtime, the payment operation is not executed, and a prompt of payment failure is returned to the payer. And subsequently, if a verification passing instruction returned by the trusted third party is received, the verification can be cancelled according to the cancellation strategy.
For example, if the payment timeout time is 1 minute, and the payment platform does not receive the verification passing instruction sent by the trusted third party within 1 minute, the payment platform does not execute the electronic payment service. If the preset cancellation strategy is to cancel 1 time of the verification operation, the trusted third party sends a verification passing instruction 1 hour after the payment timeout time is reached, and the payment platform does not perform verification when receiving a payment request from the payment account next time.
Step 212, the payment platform pushes a password reset reminder for the payment account to the trusted third party.
At step 214, the trusted third party resets the password.
In step 216, the payment platform updates the valid payment password of the payment account with the reset password.
In this embodiment, when the payment platform determines that the number of password retries has been reached, it indicates that the user has forgotten the payment password, the payment platform can push a password reset reminder to a trusted third party, and the trusted third party assists the legitimate user in resetting the password, so that operations of special groups such as the elderly and the disabled are simplified, and the use difficulty is reduced.
For example, Zhang III can help Zhang Bo reset the payment password and then tell Zhang Bo the set payment password without requiring Zhang Bo to master the password reset operation.
In this embodiment, the payment platform may update the password retry number according to the new payment password after the trusted third party resets the payment password of the payment account.
Optionally, in another example, the step 204 may not be performed, and when the password to be verified does not match a preset legal payment password of the payment account, a step of sending a verification assistance request to a trusted third party bound to the payment account through a predetermined communication channel may be performed, which is not limited in this specification.
It can be seen from the above description that, in the embodiment, when the password to be verified does not match the preset legal payment password, the verification assistance request is sent to the trusted third party bound to the payment account, and the trusted third party confirms whether the password passes the verification, so that the legal user can still realize payment when forgetting the password and losing the wrong password, and the payment experience of special groups such as the elderly and the disabled is improved.
Corresponding to the embodiment of the verification method, the specification also provides an embodiment of the verification device.
The embodiment of the verification device in the specification can be applied to a terminal or a server. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and as a logical device, the device is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the terminal or the server where the device is located. From a hardware aspect, as shown in fig. 3, the hardware structure diagram of the terminal or the server where the verification apparatus is located in this specification is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 3, the terminal or the server where the apparatus is located in the embodiment may also include other hardware according to the actual function of the terminal or the server, which is not described again.
Fig. 4 is a block diagram of a verification device shown in an exemplary embodiment of the present description.
Referring to fig. 4, the verification apparatus 300 may be applied to the terminal or the server shown in fig. 3, and includes: a password judgment unit 301, a request assistance unit 302, a verification cancellation unit 303, a number judgment unit 304, and a password resetting unit 305.
The password judgment unit 301 judges whether the password to be verified matches a preset legal password after receiving the password to be verified;
the request assisting unit 302, if not matched, sends a verification assisting request to a trusted third party bound by the verifier through a predetermined communication channel;
and the verification canceling unit 303 is configured to cancel, in response to a verification passing instruction input by the trusted third party for the verification assistance request, a verification operation of the verifier according to a predetermined cancellation policy.
The number-of-times determining unit 304 determines whether the number of password retries has been reached when the password to be verified does not match a preset legal password, and if so, notifies the request assisting unit 302 to perform a step of sending a verification assisting request to a trusted third party bound by the verifier through a predetermined communication channel.
And a password resetting unit 305 for pushing a password resetting reminder for the verifier to the trusted third party, receiving a reset password input by the trusted third party based on the password resetting reminder, and updating the valid password with the reset password.
Optionally, the number of password retries is positively correlated to the length of the valid password.
Optionally, the verification canceling unit 303 skips, in a predetermined canceling time period, a step of acquiring a password to be verified for the operation request facing the verifier, and determines that the operation request passes verification.
Optionally, the verification canceling unit 303 skips, for the operation request facing the verifier within the predetermined number of times, a step of acquiring a password to be verified, and determines that the operation request passes verification.
Optionally, when the password to be verified is a character password, the length of the character password is customized by a user.
Optionally, the length of the character code is less than 4.
Optionally, the predetermined communication channel includes one or more of:
voice channel, short message channel, instant messaging channel.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
Corresponding to the foregoing embodiments of the verification method, this specification further provides a verification apparatus, including: a processor and a memory for storing machine executable instructions. Wherein the processor and the memory are typically interconnected by means of an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.
In this embodiment, by reading and executing machine-executable instructions stored by the memory that correspond to check logic, the processor is caused to:
after receiving a password to be verified, judging whether the password to be verified is matched with a preset legal password or not;
if not, sending a verification assistance request to a trusted third party bound by the verifier through a preset communication channel;
and canceling the verification operation of the verifier according to a preset cancellation strategy in response to a verification passing instruction input by the trusted third party for the verification assistance request.
Optionally, the processor is further caused to:
when the password to be verified does not match a preset legal password, judging whether the password retry times are reached;
and if so, executing the step of sending a verification assistance request to a trusted third party bound by the verifier through a preset communication channel.
Optionally, the processor is further caused to:
pushing a password reset reminder for the verifier to the trusted third party;
receiving a reset password input by the trusted third party based on the password reset reminder;
and updating the legal password by using the reset password.
Optionally, the number of password retries is positively correlated to the length of the valid password.
Optionally, when cancelling the verification operation of the verifier according to a predetermined cancellation policy, the processor is caused to:
and in a preset cancellation period, skipping the step of acquiring the password to be verified aiming at the operation request facing the verifier, and determining that the operation request passes verification.
Optionally, when cancelling the verification operation of the verifier according to a predetermined cancellation policy, the processor is caused to:
and skipping the step of acquiring the password to be verified aiming at the operation request facing the verifier within the preset times, and determining that the operation request passes verification.
Optionally, when the password to be verified is a character password, the length of the character password is customized by a user.
Optionally, the length of the character code is less than 4.
Optionally, the predetermined communication channel includes one or more of:
voice channel, short message channel, instant messaging channel.
In correspondence with the foregoing embodiments of the verification method, the present specification also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of:
after receiving a password to be verified, judging whether the password to be verified is matched with a preset legal password or not;
if not, sending a verification assistance request to a trusted third party bound by the verifier through a preset communication channel;
and canceling the verification operation of the verifier according to a preset cancellation strategy in response to a verification passing instruction input by the trusted third party for the verification assistance request.
Optionally, the method further includes:
when the password to be verified does not match a preset legal password, judging whether the password retry times are reached;
and if so, executing the step of sending a verification assistance request to a trusted third party bound by the verifier through a preset communication channel.
Optionally, the method further includes:
pushing a password reset reminder for the verifier to the trusted third party;
receiving a reset password input by the trusted third party based on the password reset reminder;
and updating the legal password by using the reset password.
Optionally, the number of password retries is positively correlated to the length of the valid password.
Optionally, the canceling the verification operation of the verifier according to a predetermined cancellation policy includes:
and in a preset cancellation period, skipping the step of acquiring the password to be verified aiming at the operation request facing the verifier, and determining that the operation request passes verification.
Optionally, the canceling the verification operation of the verifier according to a predetermined cancellation policy includes:
and skipping the step of acquiring the password to be verified aiming at the operation request facing the verifier within the preset times, and determining that the operation request passes verification.
Optionally, when the password to be verified is a character password, the length of the character password is customized by a user.
Optionally, the length of the character code is less than 4.
Optionally, the predetermined communication channel includes one or more of:
voice channel, short message channel, instant messaging channel.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements, etc. made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.