CN106506459B - Identity information verification method and device - Google Patents

Abstract

The present disclosure relates to a method and device for verifying identity information, belonging to the field of network technology. The method includes: when it is detected that an identity verification event of a user account is triggered, acquiring historical usage information of the user account, the historical usage information being the The information used by the user account for network operations before the current time. Based on the historical usage information, an identity verification request message is generated, and the identity verification request message is sent to the user terminal that currently triggers the identity verification event. When receiving the user When the terminal sends an identity verification response message based on the identity verification request message, it verifies the identity information based on the identity verification response message and the historical usage information. Therefore, the user does not need to deliberately remember the information, which avoids the situation that the user is easy to forget, and provides convenience for the user.

Description

Identity information verification method and device

technical field

The present disclosure relates to the field of network technology, in particular to a method and device for verifying identity information.

Background technique

With the continuous development of network technology, email accounts, instant messaging accounts, online bank accounts, social network accounts, etc. play an important role in people's daily life. At the same time, users usually set different passwords for such accounts. . In actual use, in some cases, it is usually necessary to verify the user's identity information, for example, when the user needs to modify the set password, or when the password entered by the user does not match the account number, etc.

In related technologies, the process of identity information verification usually includes: when setting the initial password, the account management server provides the user with multiple questions, the user selects at least one question from the multiple questions, fills in the answer to the at least one question, and passes The terminal sends the message to the account management server, and the account management server stores the at least one question and the answer correspondingly. When the identity information needs to be verified, the account management server provides the user with at least one of the above questions again, and the user needs to fill in the answer to the at least one question, and then sends the filled answer to the account management server through the terminal. The management server verifies the answer filled in by the user, that is, judges whether the answer filled in by the user is the same as the answer set when the user sets the initial password, and if they are the same, then it is determined that the identity information verification is passed.

Contents of the invention

In order to overcome the problems existing in related technologies, the present disclosure provides a method and device for verifying identity information.

In a first aspect, a method for verifying identity information is provided, the method comprising:

When it is detected that the identity verification event of the user account is triggered, the historical usage information of the user account is obtained, the historical usage information is the information used by the user account to perform network operations before the current time;

Generate an identity verification request message based on the historical usage information;

sending the identity verification request message to the user terminal currently triggering the identity verification event;

When receiving the identity verification response message sent by the user terminal based on the identity verification request message, verify the identity information based on the identity verification response message and the historical use information.

Optionally, the obtaining historical usage information of the user account includes:

sending an information acquisition request to the data server, where the information acquisition request carries the user account, and the information acquisition request is used to instruct the data server to acquire and return historical usage information of the user account;

receiving the historical usage information sent by the data server.

Optionally, the generating an identity verification request message based on the historical usage information includes:

Obtain part of the historical usage information according to the specified policy;

Based on the partial information, generate a first verification request message, where the first verification request message is used to indicate that information other than the partial information in the historical usage information should be supplemented based on the partial information;

Determine the first verification request message as the identity verification request message.

Optionally, the generating an identity verification request message based on the historical usage information includes:

When the historical usage information is a phone number, randomly add a plurality of phone numbers to the historical usage information;

Based on the added historical usage information, generate a second verification request message, where the second verification request message is used to indicate to select the historical usage information from the added historical usage information;

determining the second verification request message as the identity verification request message.

Optionally, the generating an identity verification request message based on the historical usage information includes:

When the historical usage information includes a picture and picture information of the picture, generating a third verification request message based on the picture, the third verification request message is used to indicate to fill in the picture information of the picture;

Determine the third verification request message as the identity verification request message.

Optionally, the generating an identity verification request message based on the historical usage information includes:

When the historical usage information further includes a security level identifier, selecting target usage information corresponding to the security level identifier from the historical usage information, the security level identifier being used to indicate historical usage information that needs to be verified;

The identity verification request message is generated based on the target usage information.

Optionally, the verifying identity information based on the identity verification response message and the historical usage information includes:

Acquire first verification information carried in the identity verification response message, where the first verification information includes at least the partial information;

When the first verification information is the same as the historical use information, determine that the identity information has been verified;

When the first verification information is different from the historical usage information, it is determined that the verification of the identity information fails.

Optionally, the verifying identity information based on the identity verification response message and the historical usage information includes:

Obtain the second verification information carried in the identity verification response message;

When the second verification information is the same as the phone number, determine that the identity information has been verified;

When the second verification information is different from the phone number, it is determined that the verification of the identity information fails.

Optionally, the verifying identity information based on the identity verification response message and the historical usage information includes:

Obtain the third verification information carried in the identity verification response message;

When the third verification information is the same as the picture information, it is determined that the verification of the identity information is passed;

When the third verification information is different from the picture information, it is determined that the verification of the identity information fails.

Optionally, after determining that the authentication of the identity information fails, the method further includes:

Resending the identity verification request message, and counting the number of times the identity verification request message is resent;

When the number of times of resending the identity verification request message is greater than or equal to a preset threshold, stop resending the identity verification request message.

Optionally, before obtaining the historical usage information of the user account, it also includes:

When it is detected that the number of times that the user account does not match the password reaches a preset number of times, an identity verification event of the user account is triggered; or

When receiving a password modification request, an identity verification event of the user account is triggered.

In a second aspect, an identity information verification device is provided, the device comprising:

An acquisition module, configured to acquire historical usage information of the user account when it is detected that the identity verification event of the user account is triggered, the historical usage information being the information used by the user account for network operations before the current time ;

A generating module, configured to generate an identity verification request message based on the historical usage information acquired by the acquiring module;

a sending module, configured to send the identity verification request message generated by the generation module to the user terminal currently triggering the identity verification event;

A verification module, configured to verify identity information based on the identity verification response message and the historical usage information when receiving the identity verification response message sent by the user terminal based on the identity verification request message.

Optionally, the acquisition module is used for:

sending an information acquisition request to the data server, where the information acquisition request carries the user account, and the information acquisition request is used to instruct the data server to acquire and return historical usage information of the user account;

receiving the historical usage information sent by the data server.

Optionally, the generating module is used for:

Obtain part of the historical usage information according to the specified policy;

Based on the partial information, generate a first verification request message, where the first verification request message is used to indicate that information other than the partial information in the historical usage information should be supplemented based on the partial information;

Determine the first verification request message as the identity verification request message.

Optionally, the generating module is also used for:

When the historical usage information is a phone number, randomly add a plurality of phone numbers to the historical usage information;

Based on the added historical usage information, generate a second verification request message, where the second verification request message is used to indicate to select the historical usage information from the added historical usage information;

determining the second verification request message as the identity verification request message.

Optionally, the generating module is also used for:

When the historical usage information includes a picture and picture information of the picture, generating a third verification request message based on the picture, the third verification request message is used to indicate to fill in the picture information of the picture;

Determine the third verification request message as the identity verification request message.

Optionally, the generating module is also used for:

When the historical usage information further includes a security level identifier, selecting target usage information corresponding to the security level identifier from the historical usage information, the security level identifier being used to indicate historical usage information that needs to be verified;

The identity verification request message is generated based on the target usage information.

Optionally, the verification module is used for:

Acquire first verification information carried in the identity verification response message, where the first verification information includes at least the partial information;

When the first verification information is the same as the historical use information, determine that the identity information has been verified;

When the first verification information is different from the historical usage information, it is determined that the verification of the identity information fails.

Optionally, the verification module is also used for:

Obtain the second verification information carried in the identity verification response message;

When the second verification information is the same as the phone number, determine that the identity information has been verified;

When the second verification information is different from the phone number, it is determined that the verification of the identity information fails.

Optionally, the verification module is also used for:

Obtain the third verification information carried in the identity verification response message;

When the third verification information is the same as the picture information, it is determined that the verification of the identity information is passed;

When the third verification information is different from the picture information, it is determined that the verification of the identity information fails.

Optionally, the device also includes:

A statistics module, configured to resend the identity verification request message, and count the number of times the identity verification request message is resent;

A stop module, configured to stop resending the identity verification request message when the number of times the identity verification request message is resent is greater than or equal to a preset threshold.

Optionally, the device further includes a trigger module, and the trigger module is used for:

When it is detected that the number of times that the user account does not match the password reaches a preset number of times, an identity verification event of the user account is triggered; or

When receiving a password modification request, an identity verification event of the user account is triggered.

In a third aspect, an identity information verification device is provided, the device comprising:

processor;

memory for storing processor-executable instructions;

Wherein, the processor is configured as:

When it is detected that the identity verification event of the user account is triggered, the historical usage information of the user account is obtained, the historical usage information is the information used by the user account to perform network operations before the current time;

Generate an identity verification request message based on the historical usage information;

sending the identity verification request message to the user terminal currently triggering the identity verification event;

When receiving the identity verification response message sent by the user terminal based on the identity verification request message, verify the identity information based on the identity verification response message and the historical use information.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

In the embodiment of the present disclosure, when the server detects that the identity verification event of the user account is triggered, it indicates that the identity information of the user needs to be verified, and the server obtains the history used by the user account for network operations before the current time. Usage information, that is, the historical usage information is the information used by the user in daily network operations, for example, the historical usage information can be delivery address information, etc., and the server generates an identity verification request based on the historical usage information message, and then send the identity verification request message to the user terminal, when the server receives the identity verification response message sent by the user terminal based on the identity verification request message, the server based on the identity verification response message, the user's Identity information is verified. Since the historical usage information is the information used by the user in daily network operations, the user does not need to remember it deliberately, avoiding the situation that the user is easy to forget, and providing convenience for the user.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

Fig. 1A is a schematic diagram showing an implementation environment according to an exemplary embodiment.

Fig. 1B is a flowchart showing a method for verifying identity information according to an exemplary embodiment.

Fig. 2A is a flow chart showing a method for verifying identity information according to another exemplary embodiment.

Fig. 2B is a schematic display of a login interface involved in the embodiment of Fig. 2A.

Fig. 2C(1) is a schematic display of an identity verification request message involved in the embodiment of Fig. 2A.

Fig. 2C(2) is a schematic display of another identity verification request message involved in the embodiment of Fig. 2A.

Fig. 2D is a schematic display diagram of another identity verification request message involved in the embodiment of Fig. 2A.

Fig. 3A is a block diagram of an identity information verification device according to an exemplary embodiment.

Fig. 3B is a block diagram of an identity information verification device according to another exemplary embodiment.

Fig. 3C is a block diagram of an identity information verification device according to another exemplary embodiment.

Fig. 4 is a block diagram of an identity information verification device 400 according to an exemplary embodiment.

Detailed ways

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, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

Fig. 1A is a schematic diagram showing an implementation environment according to an exemplary embodiment, the implementation environment mainly includes a user terminal 110, an account management server 120 and a data server 130. Wherein, the data server 130 establishes communication connections with the user terminal 110 and the account management server 120 through a wired network or a wireless network.

Wherein, the user terminal 110 may run an application or a browser, and the user may perform operations such as account login through the application or the browser. The user terminal 110 may be a device such as a mobile phone, a tablet computer, a computer, and the like.

Wherein, the account management server 120 is mainly used to verify the user's identity information. In addition, the account management server 120 can also be used to manage user accounts and passwords, wherein, in a possible implementation manner, the account management server 120 and the aforementioned data server 130 may be the same server.

Wherein, the data server 130 can at least be used to store the historical use information of the user account, for example, the data server 130 can be a cloud server, an operator's background server, etc., for example, the operator's background server can be a Xiaomi store's background server Wait.

Fig. 1B is a flowchart showing a method for verifying identity information according to an exemplary embodiment. As shown in Fig. 1 , the method for verifying identity information includes the following steps.

In step 101, when it is detected that the identity verification event of the user account is triggered, the historical usage information of the user account is obtained, and the historical usage information is the information used by the user account for network operations before the current time.

In step 102, an identity verification request message is generated based on the historical usage information.

In step 103, the identity verification request message is sent to the user terminal currently triggering the identity verification event.

In step 104, when an identity verification response message sent by the user terminal based on the identity verification request message is received, identity information is verified based on the identity verification response message and the historical usage information.

In the embodiment of the present disclosure, when the server detects that the identity verification event of the user account is triggered, it indicates that the identity information of the user needs to be verified, and the server obtains the history used by the user account for network operations before the current time. Usage information, that is, the historical usage information is the information used by the user in daily network operations, for example, the historical usage information can be the delivery address, etc., and the server generates an identity verification request message based on the historical usage information , after that, the identity verification request message is sent to the user terminal, and when the server receives the identity verification response message sent by the user terminal based on the identity verification request message, the server determines the identity of the user based on the identity verification response message Since the historical usage information is the information used by the user in daily network operations, the user does not need to remember it deliberately, avoiding the situation that the user is easy to forget, and providing convenience for the user.

Optionally, the acquisition of historical usage information of the user account includes:

Send an information acquisition request to the data server, the information acquisition request carries the user account, and the information acquisition request is used to instruct the data server to acquire and return the historical use information of the user account;

The historical usage information sent by the data server is received.

Optionally, based on the historical usage information, an identity verification request message is generated, including:

Obtain part of the historical usage information according to the specified policy;

Based on the partial information, generate a first verification request message, where the first verification request message is used to indicate that information other than the partial information in the historical usage information should be supplemented based on the partial information;

The first verification request message is determined as the identity verification request message.

Optionally, based on the historical usage information, an identity verification request message is generated, including:

When the historical usage information is a phone number, randomly add multiple phone numbers to the historical usage information;

Based on the added historical usage information, generate a second verification request message, where the second verification request message is used to indicate to select the historical usage information from the added historical usage information;

The second verification request message is determined as the identity verification request message.

Optionally, based on the historical usage information, an identity verification request message is generated, including:

When the historical usage information includes a picture and the picture information of the picture, a third verification request message is generated based on the picture, and the third verification request message is used to indicate to fill in the picture information of the picture;

The third verification request message is determined as the identity verification request message.

Optionally, based on the historical usage information, an identity verification request message is generated, including:

When the historical usage information also includes a security level identifier, select the target usage information corresponding to the security level identifier from the historical usage information, and the security level identifier is used to indicate the historical usage information that needs to be verified;

Based on the target usage information, the authentication request message is generated.

Optionally, the identity information is verified based on the identity verification response message and the historical usage information, including:

Obtain the first verification information carried in the identity verification response message, where the first verification information includes at least the part of the information;

When the first verification information is the same as the historical usage information, it is determined that the identity information has been verified;

When the first verification information is different from the historical usage information, it is determined that the identity information verification fails.

Optionally, the identity information is verified based on the identity verification response message and the historical usage information, including:

Obtain the second verification information carried in the identity verification response message;

When the second verification information is the same as the phone number, it is determined that the identity information has been verified;

When the second verification information is different from the phone number, it is determined that the identity information verification fails.

Optionally, the identity information is verified based on the identity verification response message and the historical usage information, including:

Obtain the third verification information carried in the identity verification response message;

When the third verification information is the same as the picture information, it is determined that the identity information has been verified;

When the third verification information is different from the picture information, it is determined that the verification of the identity information fails.

Optionally, after determining that the authentication of the identity information fails, it also includes:

Resend the identity verification request message, and count the number of times the identity verification request message is resent;

When the number of times of resending the identity verification request message is greater than or equal to the preset threshold, stop resending the identity verification request message.

Optionally, before obtaining the historical usage information of the user account, it also includes:

When it is detected that the number of times that the user account does not match the password reaches a preset number of times, an authentication event of the user account is triggered; or

When a password change request is received, an authentication event of the user account is triggered.

All the above optional technical solutions may be combined in any way to form optional embodiments of the present disclosure, which will not be described in detail in the embodiments of the present disclosure.

Fig. 2A is a flow chart of a method for verifying identity information according to an exemplary embodiment. The method includes the following steps:

In step 201, when the account management server detects that the identity verification event of the user account is triggered, it obtains the historical use information of the user account, and the historical use information is the information used by the user account for network operations before the current time .

In the process of using the user account and password, in some cases, it is inevitable to verify the user's identity information. At present, in the identity information verification method provided by the related technology, since the user usually easily forgets the answer set when setting the initial password, the user cannot pass the identity information verification, which brings inconvenience to the user. Therefore, in an embodiment of the present disclosure, a method for verifying identity information is provided, which can avoid the above-mentioned problems, specifically as described below.

Among them, before verifying the identity information of the user, the identity verification event of the user account needs to be triggered, that is, before obtaining the historical use information of the user account, the account management server needs to trigger the user account under specified conditions. Account authentication events. Wherein, the specified condition may include any of the following possible implementation methods:

The first way: when it is detected that the number of times that the user account does not match the password reaches a preset number of times, an authentication event of the user account is triggered.

Wherein, the preset number of times can be customized by the user according to actual needs, or can be set by default by the account management server, which is not limited in this embodiment of the present disclosure.

In this implementation, when it is detected that the number of times that the user account does not match the password reaches the preset number of times, it means that the user may not be the owner of the user account. Therefore, the identity of the user needs to be verified. In this case, the authentication event of the user account is triggered.

The second way: when a password modification request is received, an authentication event of the user account is triggered.

In this implementation, when a password change request is received, in order to ensure the security of the account, it is necessary to verify the identity information of the user who wants to change the password, that is, the account management server triggers an identity verification event for the user account.

Wherein, in a possible implementation manner, the password modification request is sent by the user terminal, and the user terminal sends the password modification request when receiving the password modification instruction. Wherein, the password modification instruction may be triggered by a user, and the user may trigger it through a specified operation, and the specified operation may include a click operation, a slide operation, etc., which is not limited in this embodiment of the present disclosure.

For example, referring to FIG. 2B, the current display interface of the user terminal includes a login account option 21, a login password option 22, and the password modification option 23. When the user wants to modify the password, he can click the password modification option 23. The user terminal confirms that the password modification instruction has been received, and then, the user terminal sends the password modification request to the account management server.

It should be noted that, in the embodiment of the present disclosure, the account management server triggers the identity verification event of the user account in the above two cases as an example for illustration. In another embodiment, it may also be In other cases, the account management server triggers an identity verification event of the user account, which is not limited in this embodiment of the present disclosure.

When the account management server detects that the authentication event of the user account is triggered, it obtains the historical usage information of the user account, and the historical usage information is the information used by the user for daily network operations. Wherein, the network operation may be an operation of synchronizing data information on the user terminal, for example, the data information on the user terminal may include: phone numbers of all friends, pictures in albums, short messages, and so on. Alternatively, the network operation may also be an online transaction operation, wherein the online transaction operation may include online shopping operations, online money transfer operations, and the like. Certainly, the network operation may also be other operations, which are not limited in this embodiment of the present disclosure.

That is to say, when the user performs this type of network operation based on the user account, the historical usage information will be stored in the server. address information, etc. Wherein, the server may be the account management server. Of course, the server may also be a data server for storing network data. According to different types of the server, the above-mentioned realization process of obtaining the historical usage information of the user account may be Including any of the following possible implementations:

The first method: send an information acquisition request to the data server, the information acquisition request carries the user account, and the information acquisition request is used to instruct the data server to acquire and return the historical usage information of the user account, and receive the information sent by the data server Historical usage information.

Wherein, the data server is at least used to store the historical use information of the user account, for example, the data server may be a cloud server, and the cloud server stores data information on the user terminal corresponding to the user account, in this case , the historical usage information may be part or all of the data information on the user terminal.

In this implementation, when the account management server detects that the user account authentication event is triggered, it sends an information acquisition request to the data server. In the usage information, the historical usage information corresponding to the user account is obtained, and the historical usage information is sent to the account management server, so that the account management server obtains the historical usage information of the user account.

In addition, in this implementation, the data server may also have security level requirements for verification information, that is, different data servers may have different security level requirements for verification information, for example, for cloud servers, Usually it is necessary to verify the phone number, which can be the user's own phone number or the phone number of the user's friend. For some shopping websites, it may not be necessary to verify the phone number, as long as the delivery address information is verified. Can. When the data server also has security level requirements for verifying information, after the data server receives the information acquisition request, it may also include any of the following (1)-(2) implementations:

(1) The data server obtains the historical use information of the user account that needs to be verified according to its own security level requirements, and sends the historical use information to the account management server.

In this implementation, for the account management server, there is no need to filter the historical use information sent by the data server, that is, the data server has already Select the historical usage information that needs to be verified from the multiple historical usage information corresponding to the user account according to its own security level requirements.

(2) The data server obtains its own security level identification and all historical usage information of the user account, and sends the security level identification and all historical usage information of the user account to the account management server.

Wherein, the security level identifier is used to indicate historical usage information that needs to be verified. The difference from the above implementation (1) is that in this implementation, after the data server sends the security level identifier and all historical usage information of the user account to the account management server, the account management server needs to Security level identification, select the historical usage information that needs to be verified from all the historical usage information of the user account.

Wherein, the division of the above-mentioned security levels can be set by technicians according to actual needs. For example, the division of the security levels can be: the verification level of the phone number is higher than the verification level of the delivery address information, etc. This is not limited. In addition, the security level identification can be level 1, level 2, level 3, etc. As the number increases, the security level becomes smaller. Taking the above as an example, the security level identification corresponding to the verification level of the phone number is level 1. The security level identifier corresponding to the verification level of the delivery address information may be level 2 or level 3, etc. Of course, the security level identifier may also exist in other forms, which is not limited in this embodiment of the present disclosure.

The second way: the account management server obtains the historical usage information of the user account from a plurality of pre-stored usage information.

As mentioned above, in a possible implementation manner, since the account management server and the data server may be the same device, when the account management server and the data server are the same device, the historical usage information may be obtained from the The account management server itself stores in advance.

In step 202, the account management server generates an identity verification request message based on the historical use information.

Wherein, the implementation process of the account management server generating the identity verification request message based on the historical usage information may include at least one of the following possible implementation methods:

The first way: According to the specified strategy, obtain part of the information in the historical usage information, and generate a first verification request message based on the part of information, and the first verification request message is used to indicate that the part of the information in the historical usage information Other information except the part of information is supplemented, and the first verification request message is determined as the identity verification request message.

Wherein, the specified policy may be set in advance in the account management server. For example, the designated policy may be: obtain other information in the historical usage information except numbers and letters, and determine the other information as the part of information. Alternatively, the specified strategy may also be: determine the number i of characters included in the historical usage information, obtain the historical usage information corresponding to the first i/2 characters in the historical usage information, and determine the acquired historical usage information as The above partial information, etc., wherein the number i of characters is greater than or equal to 1.

For example, taking the above-mentioned specified policy as obtaining information other than numbers and letters in the historical usage information and determining the other information as this part of the information, when the historical usage information includes delivery address information, and the The delivery address information is Block A, Bank of New York Building, No. 16 Wall Street, New York, and this part of information may be Block X, Bank of New York Building, No. xx, Wall Street, New York. That is, the user is required to fill in "16" and "A" in the delivery address information.

The second method: when the historical usage information is a phone number, randomly add a plurality of phone numbers to the historical usage information, and generate a second verification request message based on the added historical usage information, the second verification request message uses In order to select the historical usage information from the added historical usage information, the second verification request message is determined as the identity verification request message.

In this implementation, the purpose of adding the multiple phone numbers randomly is to allow the user to select a phone number belonging to his friend from the added historical usage information based on the added confusing number, that is, When the user selects the user's friend's phone number from the historical usage information added with the confusing number, it can be determined that the user is not the owner of the user account.

The third way: when the historical use information includes a picture and the picture information of the picture, a third verification request message is generated based on the picture, and the third verification request message is used to indicate to fill in the picture information of the picture, and the third verification request message is The third verification request message is determined as the identity verification request message.

For example, in a possible implementation manner, the picture information may be used to indicate who the person in the picture is, that is, after the third verification request message is generated based on the picture, so that the user terminal receives the third verification request message. 3. Verification request message. After displaying the picture, the user identifies the person in the picture, and sends the determined person information to the account management server, so that the account management server can judge whether the person information determined by the user is consistent with the picture information. same.

It should be noted that, in the embodiment of the present disclosure, the above-mentioned three ways are used as an example to generate an identity verification request message based on the historical usage information. In another embodiment, it is also possible to use other forms based on The historical use information generates an identity verification request message, which is not limited in this embodiment of the present disclosure.

The three implementations provided above all correspond to the implementation (1) in step 201, that is, in the three implementations provided above, the data server can use the user account according to its own security level requirements. Among the multiple corresponding historical usage information, select the historical usage information that needs to be verified, and send the selected historical usage information to the account management server, that is to say, for the account management server, there is no need for the account management server to The historical use information is selected, which historical use information is sent by the data server to the account management server, and the account management server generates an identity verification request message based on the historical use information.

In addition, in another possible implementation manner, as described in the implementation manner (2) in step 201, when the historical usage information also includes a security level identifier, the account management server selects the security level identifier from the historical usage information. The target usage information corresponding to the level identifier is used to indicate the historical usage information to be verified, and the identity verification request message is generated based on the target usage information.

Wherein, the implementation manner of generating the identity verification request message based on the target usage information is the same as the above-mentioned realization manner of generating the identity verification request message based on the historical use information, and will not be described in detail here.

In step 203, the account management server sends the identity verification request message to the user terminal currently triggering the identity verification event.

In step 204, the user terminal receives an identity verification request message, and displays the identity verification request message in a current display interface.

The account management server sends the identity verification request message to the user terminal. Correspondingly, after receiving the identity verification request message, the user terminal displays the identity verification request message in the current display interface, so that the user can , fill in or select information related to historical usage information.

For example, in a possible implementation, the identity verification request message may be displayed as shown in Figure 2C(1). When the identity verification request message is generated by the account management server based on the above part of the information, the display interface Part of the information 24 carried in the identity verification request message is displayed in the display interface, and the display interface also includes an input prompt item 25. The input prompt item 25 corresponds to an input box 26, and the user can input the historical usage in the input box 26. Other information in the information except the above-mentioned partial information, after that, the user can click the confirmation option 27 .

As another example, in another possible implementation, the identity verification request message may be displayed as shown in Figure 2C(2), when the identity verification request message is generated by the account management server based on the above phone number, the The display interface displays all the phone numbers carried in the identity verification request message, and displays a prompt as shown in Figure 281: Please select a friend's phone number, and each phone number in all the phone numbers corresponds to an option 282 , the user can select the phone number of his friend from the displayed multiple phone numbers, that is, click the option 282 corresponding to the phone number of his friend, and then the user can click the confirmation option 27.

For another example, in yet another possible implementation, the identity verification request message may be displayed as shown in Figure 2D. When the identity verification request message is generated by the account management server based on the above picture, the display interface displays The picture 29 carried in the identity verification request message prompts the user to input the name of the person in the picture, that is, the display interface provides an input box 30, and the user can input the name of the person in the picture in the input box 30. After that, the user This confirmation option 27 may be clicked.

In step 205, when the user terminal receives an identity verification response instruction based on the identity verification request message, an identity verification response message is generated based on the verification information, and the identity verification response message is sent to the account management server.

Wherein, the identity verification response instruction may be triggered by a user, and the user may trigger the above-mentioned specified operation. For example, as shown in Figure 2C, when the user clicks the confirmation option 27, the user terminal confirms receipt of the identity verification response instruction, and the user terminal generates the identity verification response based on the information entered by the user and the part of information information.

In step 206, when the account management server receives the identity verification response message sent by the user terminal based on the identity verification request message, it verifies the identity information based on the identity verification response message and the historical usage information.

Wherein, according to the content included in the historical usage information, based on the identity verification response message and the historical usage information, the implementation process of verifying the identity information may include any of the following:

The first method: obtain the first verification information carried in the identity verification response message, the first verification information includes at least this part of the information, and when the first verification information is the same as the historical usage information, it is determined that the identity information has passed the verification , when the first verification information is different from the historical usage information, it is determined that the identity information verification fails.

The first implementation mode corresponds to the implementation mode (1) in the above step 202. For example, if the historical usage information is the delivery address information, and the delivery address information is Block A, Bank of New York Building, 16 Wall Street, New York, This part of the information is Building X, Bank of New York Building, No. xx, Wall Street, New York. When the first verification information is Building A, Bank of New York, No. 16, Wall Street, New York, it is determined that the identity information has passed the verification, and when the first verification information is Wall Street, New York 23, Block B of the Bank of New York Building, it was determined that the verification of the identity information failed.

It should be noted that it is only exemplary that the above-mentioned first verification information includes at least this part of information. In another embodiment, the first verification information may only include other information in the historical usage information except this part of information. , in this case, after receiving the first verification information, the account management server judges whether the first verification information is the same as other information in the historical usage information except for this part of information, if the first verification information If it is the same as other information except this part of information in the historical usage information, it is determined that the user's identity information has passed the verification; otherwise, it is determined that the user's identity information has not passed the verification, which is not limited in this embodiment of the present disclosure.

The second method: obtain the second verification information carried in the identity verification response message, and when the second verification information is the same as the phone number, determine that the identity information has been verified; when the second verification information is different from the phone number If they are the same, it is determined that the authentication of the identity information fails.

The second method corresponds to the implementation method (2) in the above-mentioned step 202. When the second verification information is the same as the phone number, it means that the user can choose his/her own phone number from the multiple phone numbers added with confusion. The friend's phone number, that is, it can be determined that the user's identity information is the identity information corresponding to the account information, and the account management server determines that the user's identity information has been verified.

Taking the above example as an example, the historical usage information includes phone numbers 138xxxx5608, 136xxxx3507 and 184xxxx9561. When the second verification information includes 138xxxx5608, 136xxxx3507 and 184xxxx9561, it is determined that the user’s identity information has passed the verification. When the second verification information includes 138xxxx75608 , 135xxxx3507 and 184xxxx3561, it is determined that the user's identity information verification has failed.

The third method: obtain the third verification information carried in the identity verification response message, and when the third verification information is the same as the picture information, determine that the identity information has passed the verification; when the third verification information is different from the picture information If they are the same, it is determined that the authentication of the identity information fails.

Taking the above example as an example, the picture information in the historical usage information is "jony", when the third verification information is "jony", it is determined that the user's identity information has been verified, and when the third verification information is "honiey" , it is determined that the user's identity information verification has failed.

It should be noted that the embodiments of the present disclosure are only described by using the above three ways to verify the identity information based on the identity verification response message and the historical usage information as an example. In another embodiment, other methods can also be used. In a manner, the identity information is verified based on the identity verification response message and the historical usage information, which is not limited in this embodiment of the present disclosure.

So far, this embodiment of the present disclosure has implemented the identity information verification method. In addition, in the actual application process, the information entered by the user for the first time may be wrong due to reasons such as input errors. In this case, if it is determined that the user Failed to verify the identity information of , which may cause inconvenience to the user. Therefore, for this situation, the embodiment of the present disclosure also provides the following steps 207 and 208 .

In step 207, the account management server resends the identity verification request message, and counts the times of resending the identity verification request message.

When it is determined that the user's identity information verification has not passed, in order to avoid the verification failure caused by the user's mistake, the account management server resends the identity verification request message to the terminal, so that the user can refill or select the corresponding information.

In addition, when the information entered by the user is always incorrect, it means that the user may not be the owner of the user account. Therefore, for the security of the user account, the server also counts the number of times the identity verification request message is resent.

In step 208, the account management server stops resending the identity verification request message when the number of resends of the identity verification request message is greater than or equal to a preset threshold.

Wherein, the preset threshold can be customized and set by the user according to actual needs, or can be set by default by the account management server, which is not limited in this embodiment of the present disclosure.

When the number of times the identity verification request message is resent is greater than or equal to the preset threshold, it can be determined that the user is not the owner of the user account, that is, the user does not have the authority to use the user account, or the user does not have The authority to modify the password of the user account, therefore, the account management server stops resending the identity verification request message, that is, it determines that the verification of the user's identity information fails.

In the embodiment of the present disclosure, when the server detects that the identity verification event of the user account is triggered, it indicates that the identity information of the user needs to be verified, and the server obtains the history used by the user account for network operations before the current time. Usage information, that is, the historical usage information is the information used by the user in daily network operations, for example, the historical usage information can be the delivery address, etc., and the server generates an identity verification request message based on the historical usage information , after that, sending the identity verification request message to the user terminal, so that the user can fill in or select information related to the historical user information based on the identity verification request message, and then, the user fills in or selects information related to the historical user information through the user terminal The selected information is sent to the server, that is, the user terminal sends an identity verification response message to the server, and the identity verification response message carries the information filled in or selected by the user. Identity information is verified. Since the historical usage information is the information used by the user in daily network operations, the user does not need to remember it deliberately, avoiding the situation that the user is easy to forget, and providing convenience for the user.

Fig. 3A is a device for verifying identity information according to an exemplary embodiment. The identity information verification device can be realized by software, hardware or a combination of the two, and the identity information verification device includes:

The acquiring module 310 is configured to acquire historical usage information of the user account when it is detected that the identity verification event of the user account is triggered, the historical usage information being the information used by the user account for network operations before the current time;

A generating module 320, configured to generate an identity verification request message based on the historical usage information acquired by the acquiring module 310;

A sending module 330, configured to send the identity verification request message generated by the generation module 320 to the user terminal currently triggering the identity verification event;

The verification module 340 is configured to verify identity information based on the identity verification response message and the historical usage information when receiving the identity verification response message sent by the user terminal based on the identity verification request message.

Optionally, please refer to FIG. 3B to FIG. 3C, the acquiring module 310 is used for:

Send an information acquisition request to the data server, the information acquisition request carries the user account, and the information acquisition request is used to instruct the data server to acquire and return the historical use information of the user account;

The historical usage information sent by the data server is received.

Optionally, the generating module 320 is used for:

Obtain part of the historical usage information according to the specified policy;

Based on the partial information, generate a first verification request message, where the first verification request message is used to indicate that information other than the partial information in the historical usage information should be supplemented based on the partial information;

The first verification request message is determined as the identity verification request message.

Optionally, the generating module 320 is also used for:

When the historical usage information is a phone number, randomly add multiple phone numbers to the historical usage information;

Based on the added historical usage information, generate a second verification request message, where the second verification request message is used to indicate to select the historical usage information from the added historical usage information;

The second verification request message is determined as the identity verification request message.

Optionally, the generating module 320 is also used for:

When the historical usage information includes a picture and the picture information of the picture, a third verification request message is generated based on the picture, and the third verification request message is used to indicate to fill in the picture information of the picture;

The third verification request message is determined as the identity verification request message.

Optionally, the generating module 320 is also used for:

When the historical usage information also includes a security level identifier, select the target usage information corresponding to the security level identifier from the historical usage information, and the security level identifier is used to indicate the historical usage information that needs to be verified;

Based on the target usage information, the authentication request message is generated.

Optionally, the verification module 340 is used for:

Obtain the first verification information carried in the identity verification response message, where the first verification information includes at least the part of the information;

When the first verification information is the same as the historical usage information, it is determined that the identity information has been verified;

When the first verification information is different from the historical usage information, it is determined that the identity information verification fails.

Optionally, the verification module 340 is also used for:

Obtain the second verification information carried in the identity verification response message;

When the second verification information is the same as the phone number, it is determined that the identity information has been verified;

When the second verification information is different from the phone number, it is determined that the identity information verification fails.

Optionally, the verification module 340 is also used for:

Obtain the third verification information carried in the identity verification response message;

When the third verification information is the same as the picture information, it is determined that the identity information has been verified;

When the third verification information is different from the picture information, it is determined that the verification of the identity information fails.

Optionally, the device also includes:

A statistics module 350, configured to resend the identity verification request message, and count the number of times the identity verification request message is resent;

The stop module 360 is configured to stop resending the identity verification request message when the number of times the identity verification request message is resent is greater than or equal to a preset threshold.

Optionally, the device further includes a trigger module 370, which is used for:

When it is detected that the number of times that the user account does not match the password reaches a preset number of times, an authentication event of the user account is triggered; or

When a password change request is received, an authentication event of the user account is triggered.

In the embodiment of the present disclosure, when the server detects that the identity verification event of the user account is triggered, it indicates that the identity information of the user needs to be verified, and the server obtains the history used by the user account for network operations before the current time. Usage information, that is, the historical usage information is the information used by the user in daily network operations, for example, the historical usage information can be the delivery address, etc., and the server generates an identity verification request message based on the historical usage information , after that, the identity verification request message is sent to the user terminal, and when the server receives the identity verification response message sent by the user terminal based on the identity verification request message, the server determines the identity of the user based on the identity verification response message Since the historical usage information is the information used by the user in daily network operations, the user does not need to remember it deliberately, avoiding the situation that the user is easy to forget, and providing convenience for the user.

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Fig. 4 is a block diagram of an identity information verification device 400 according to an exemplary embodiment. For example, the device 400 may be provided as an account management server. Referring to FIG. 4 , apparatus 400 includes processing component 422 , which further includes one or more processors, and a memory resource represented by memory 432 for storing instructions executable by processing component 422 , such as application programs. The application program stored in memory 432 may include one or more modules each corresponding to a set of instructions. In addition, the processing component 422 is configured to execute instructions to perform the above identity information verification method.

Device 400 may also include a power component 426 configured to perform power management of device 400 , a wired or wireless network interface 450 configured to connect device 400 to a network, and an input-output (I/O) interface 458 . The apparatus 400 may operate based on an operating system stored in the memory 432, such as Windows Server ^™ , Mac OS X ^™ , Unix ^™ , Linux ^™ , FreeBSD ^™ or the like.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (21)

1. a kind of identity information verification method, which is characterized in that the described method includes:

When the Authentication Events for detecting user account are triggered, the history of the user account is obtained from data server Use information, the history use information are that the user account carries out used letter when network operation before current time Breath；

When the history use information further includes safe class mark, selection and the safety from the history use information The corresponding target use information of class letter, the history use information that the safe class mark is verified needed for being used to indicate, institute The safe class mark that safe class mark is the data server itself is stated, for different data server, verifying is believed Ceasing has different security level requirements；

Based on the target use information, the authentication request message is generated；

The authentication request message is sent to the user terminal for currently triggering the Authentication Events；

When receiving the authentication response message that the user terminal is sent based on the authentication request message, it is based on The authentication response message and the history use information, verify identity information；

Wherein, the verifying grade of telephone number is higher than the verifying grade of shipping address information.

2. the method as described in claim 1, which is characterized in that the history use information for obtaining the user account, packet It includes:

Information acquisition request is sent to the data server, the information acquisition request carries the user account, the letter Breath acquisition request is used to indicate the history use information that the data server obtains and returns to the user account；

Receive the history use information that the data server is sent.

3. method according to claim 1 or 2, which is characterized in that the method also includes:

According to specified strategy, the partial information in the history use information is obtained；

Based on the partial information, the first checking request message is generated, the first checking request message is used to indicate based on institute Partial information is stated to supplement the other information in the history use information other than the partial information；

The first checking request message is determined as the authentication request message.

4. method according to claim 1 or 2, which is characterized in that the method also includes:

When the history use information is telephone number, multiple telephone numbers are added at random in the history use information；

Based on the history use information after addition, the second checking request message is generated, the second checking request message is for referring to Show and selects the history use information from the history use information after addition；

The second checking request message is determined as the authentication request message.

5. method according to claim 1 or 2, which is characterized in that the method also includes:

When in the history use information including the pictorial information of picture and the picture, third is generated based on the picture and is tested Request message is demonstrate,proved, the third checking request message is used to indicate the pictorial information for filling in the picture；

The third checking request message is determined as the authentication request message.

6. method as claimed in claim 3, which is characterized in that described to be based on the authentication response message and the history Use information verifies identity information, comprising:

The first verification information carried in the authentication response message is obtained, first verification information includes at least described Partial information；

When first verification information is identical as the history use information, determine that the identity information is verified；

When first verification information and the history use information be not identical, determine that the identity information verifying does not pass through.

7. method as claimed in claim 4, which is characterized in that described to be based on the authentication response message and the history Use information verifies identity information, comprising:

Obtain the second verification information carried in the authentication response message；

When second verification information is identical as the telephone number, determine that the identity information is verified；

When second verification information and the telephone number be not identical, determine that the identity information verifying does not pass through.

8. method as claimed in claim 5, which is characterized in that described to be based on the authentication response message and the history Use information verifies identity information, comprising:

Obtain the third verification information carried in the authentication response message；

When the third verification information is identical as the pictorial information, determine that the identity information is verified；

When the third verification information and the pictorial information be not identical, determine that the identity information verifying does not pass through.

9. such as method as claimed in claim 6 to 8, which is characterized in that the determination identity information verifying does not pass through it Afterwards, further includes:

The authentication request message is retransmitted, and is united to the number for retransmitting the authentication request message Meter；

When the number for retransmitting the authentication request message is greater than or equal to preset threshold, stop described in retransmission Authentication request message.

10. the method as described in claim 1, which is characterized in that before the history use information for obtaining the user account, also Include:

When detecting that the user account and the unmatched number of password reach preset times, the body of the user account is triggered Part verifying event；Or

When receiving Modify password request, the Authentication Events of the user account are triggered.

11. a kind of identity information verifies device, which is characterized in that described device includes:

Obtain module, for when the Authentication Events for detecting user account are triggered, obtain from data server described in The history use information of user account, the history use information are that the user account carries out network behaviour before current time Used information when making；

Generation module, for when the history use information further includes safe class mark, from the history use information That verifies needed for selecting target use information corresponding with the safe class mark, the safe class mark to be used to indicate goes through History use information, the safe class mark are the safe class marks of the data server itself, and different data is taken Business device has different security level requirements to verification information；

Based on the target use information, the authentication request message is generated；

Sending module, the authentication request message for generating the generation module, which is sent to, currently triggers the body The user terminal of part verifying event；

Authentication module, for working as the authentication sound for receiving the user terminal and sending based on the authentication request message When answering message, it is based on the authentication response message and the history use information, identity information is verified；

Wherein, the verifying grade of telephone number is higher than the verifying grade of shipping address information.

12. device as claimed in claim 11, which is characterized in that the acquisition module is used for:

Information acquisition request is sent to the data server, the information acquisition request carries the user account, the letter Breath acquisition request is used to indicate the history use information that the data server obtains and returns to the user account；

Receive the history use information that the data server is sent.

13. the device as described in claim 11 or 12, which is characterized in that the generation module is also used to:

According to specified strategy, the partial information in the history use information is obtained；

Based on the partial information, the first checking request message is generated, the first checking request message is used to indicate based on institute Partial information is stated to supplement the other information in the history use information other than the partial information；

The first checking request message is determined as the authentication request message.

14. the device as described in claim 11 or 12, which is characterized in that the generation module is also used to:

When the history use information is telephone number, multiple telephone numbers are added at random in the history use information；

Based on the history use information after the addition, the second checking request message is generated, the second checking request message is used The history use information is selected from the history use information after addition in instruction；

The second checking request message is determined as the authentication request message.

15. the device as described in claim 11 or 12, which is characterized in that the generation module is also used to:

When in the history use information including the pictorial information of picture and the picture, third is generated based on the picture and is tested Request message is demonstrate,proved, the third checking request message is used to indicate the pictorial information for filling in the picture；

The third checking request message is determined as the authentication request message.

16. device as claimed in claim 13, which is characterized in that the authentication module is used for:

The first verification information carried in the authentication response message is obtained, first verification information includes at least described Partial information；

When first verification information is identical as the history use information, determine that the identity information is verified；

When first verification information and the history use information be not identical, determine that the identity information verifying does not pass through.

17. device as claimed in claim 14, which is characterized in that the authentication module is also used to:

Obtain the second verification information carried in the authentication response message；

When second verification information is identical as the telephone number, determine that the identity information is verified；

When second verification information and the telephone number be not identical, determine that the identity information verifying does not pass through.

18. device as claimed in claim 15, which is characterized in that the authentication module is also used to:

Obtain the third verification information carried in the authentication response message；

When the third verification information is identical as the pictorial information, determine that the identity information is verified；

When the third verification information and the pictorial information be not identical, determine that the identity information verifying does not pass through.

19. the device as described in claim 16-18 is any, which is characterized in that described device further include:

Statistical module disappears for retransmitting the authentication request message, and to the authentication request is retransmitted The number of breath is counted；

Stopping modular, for stopping when the number for retransmitting the authentication request message is greater than or equal to preset threshold Only retransmit the authentication request message.

20. device as claimed in claim 11, which is characterized in that described device further includes trigger module, the trigger module For:

When detecting that the user account and the unmatched number of password reach preset times, the body of the user account is triggered Part verifying event；Or

When receiving Modify password request, the Authentication Events of the user account are triggered.

21. a kind of identity information verifies device, which is characterized in that described device includes:

Processor；

Memory for storage processor executable instruction；

Wherein, the processor is configured to:

When the Authentication Events for detecting user account are triggered, the history of the user account is obtained from data server Use information, the history use information are that the user account carries out used letter when network operation before current time Breath；

When the history use information further includes safe class mark, selection and the safety from the history use information The corresponding target use information of class letter, the history use information that the safe class mark is verified needed for being used to indicate, institute The safe class mark that safe class mark is the data server itself is stated, for different data server, verifying is believed Ceasing has different security level requirements；

Based on the target use information, the authentication request message is generated；

The authentication request message is sent to the user terminal for currently triggering the Authentication Events；

When receiving the authentication response message that the user terminal is sent based on the authentication request message, it is based on The authentication response message and the history use information, verify identity information；

Wherein, the verifying grade of telephone number is higher than the verifying grade of shipping address information.