WO2017190668A1 - 身份验证方法和装置 - Google Patents

身份验证方法和装置 Download PDF

Info

Publication number
WO2017190668A1
WO2017190668A1 PCT/CN2017/083015 CN2017083015W WO2017190668A1 WO 2017190668 A1 WO2017190668 A1 WO 2017190668A1 CN 2017083015 W CN2017083015 W CN 2017083015W WO 2017190668 A1 WO2017190668 A1 WO 2017190668A1
Authority
WO
WIPO (PCT)
Prior art keywords
contact
identifier
user
user identifier
target
Prior art date
Application number
PCT/CN2017/083015
Other languages
English (en)
French (fr)
Inventor
陈杰
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2017190668A1 publication Critical patent/WO2017190668A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint

Definitions

  • the present application relates to the field of communications technologies, and in particular, to an identity verification method and apparatus.
  • the security of the data is generally improved by means of authentication, for example, according to the verification information provided by the user, such as an account number and a password, a verification code, etc., compared with the pre-stored verification information, if they are consistent, The verification is passed, otherwise, it is determined that the verification does not pass.
  • the verification information provided by the user, such as an account number and a password, a verification code, etc.
  • SMS verification is currently the most mainstream authentication method.
  • the server obtains the mobile phone number bound to the account (ie, the secret mobile phone number), and then the server sends a verification code to the mobile phone through the short message.
  • the mobile phone corresponding to the number the server receives the verification code sent by the mobile phone, and compares it with the pre-stored verification code. If the same, the identity verification passes, otherwise, the identity verification fails.
  • the inventor of the present application found that the existing short message verification method needs to send a verification code to the secret mobile phone bound to the account, but as the technology of the criminals becomes more sophisticated, the user The secret mobile phone number is easily stolen by criminals, so that the verification code received by the secret mobile phone can be easily stolen, such as by means of SMS phishing, thus reducing the security of the authentication.
  • the embodiment of the present application provides an identity verification method and apparatus, which can improve the security of identity verification.
  • An embodiment of the present application provides an identity verification method, including:
  • the target user identifier is the user User ID of the contact
  • an identity verification apparatus including:
  • a request receiving unit configured to receive an identity verification request sent by the terminal, where the identity verification request carries a user identifier of the user;
  • An identifier obtaining unit configured to acquire a target user identifier according to the identity verification request, where the target user identifier is a user identifier of a contact of the user;
  • An information sending unit configured to send, according to the target user identifier, verification information to the corresponding target terminal, so that the target terminal provides the verification information to the terminal;
  • the verification unit is configured to receive the verification information sent by the terminal, and perform identity verification on the user corresponding to the user identifier according to the verification information.
  • the embodiment of the present application adopts an identity verification request sent by the receiving terminal, where the identity verification request carries the user identifier of the user, and then obtains the target user identifier according to the identity verification request, where the target user identifier is the user identifier of the contact of the user, according to The target user identifier sends the verification information to the corresponding target terminal, so that the target terminal provides the verification information to the terminal, receives the verification information sent by the terminal, and performs identity verification on the user corresponding to the user identifier according to the verification information.
  • the solution may send the verification information to the terminal of the user's contact, so that the user obtains the verification information from the contact person to complete the identity verification; since the verification information is not sent to the user himself, but is sent to the user's contact, even if In the case that the secret mobile phone number is leaked, it is difficult for the criminals to know which contact the verification information is sent to, so that the verification information cannot be stolen from the contact person, and the security of the identity verification can be improved compared with the prior art.
  • FIG. 1a is a flowchart of an identity verification method according to Embodiment 1 of the present application.
  • FIG. 1b is a schematic diagram of a social relationship map provided by Embodiment 1 of the present application.
  • FIG. 2 is a flowchart of an identity verification method according to Embodiment 2 of the present application.
  • FIG. 3 is a schematic structural diagram of an identity verification apparatus according to Embodiment 3 of the present application.
  • FIG. 4 is a schematic diagram of a network environment applied to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a hardware of a server according to an embodiment of the present application.
  • the embodiment of the present application provides an identity verification method and apparatus. The details will be described separately below.
  • An authentication method includes: receiving an identity verification request sent by a terminal, where the identity verification request carries a user identifier of the user, and then acquiring a target user identifier according to the identity verification request, where the target user identifier is a user of the user's contact The identifier is sent to the corresponding target terminal according to the target user identifier, so that the target terminal provides the verification information to the terminal, receives the verification information sent by the terminal, and performs the user corresponding to the user identifier according to the verification information. Authentication.
  • the specific process of the identity verification method can be as follows:
  • the identity verification request sent by the terminal may be received through the wireless network, for example, the identity verification request sent by the terminal is received through the wifi.
  • the user identifier may be a communication account, and the communication account may be an instant messaging account or other communication account, such as an email account, a social network account, and the like.
  • Target user identifier is a user identifier of a contact of the user.
  • the user's contact may be another user corresponding to another user identifier that establishes contact with the user identifier of the user, and may be other users corresponding to other communication identifiers that establish contact with the user's communication identifier in the communication network.
  • it can be added to each other on social networks and users.
  • Other users of the friend such as other users in the instant messaging who have added friends to each other, other users in the email mailbox who have added friends to each other, etc., therefore, the user's contacts are not limited to real friends in reality, It can be a user who is not a friend in the real world but is a friend on the network.
  • the method for obtaining the target user identifier according to the identity verification request may be multiple.
  • an identifier set for sending the verification information may be set.
  • a user identifier may be randomly selected from the identifier set.
  • Sending verification information; that is, the step of "acquiring the target user identifier according to the identity verification request" may include:
  • a candidate identifier group corresponding to the user identifier where the candidate identifier group includes at least one contact user identifier, where the contact user identifier is a user identifier of the contact of the user;
  • the contact user identifier is randomly selected from the candidate identifier group as the target user identifier.
  • the candidate identifier group may be set by the user or may be set by the system.
  • the candidate identifier group may be set based on the contact group corresponding to the user identifier, that is, the step “acquiring the candidate corresponding to the user identifier according to the identity verification request.
  • the identification group can include:
  • each contact group includes at least one contact user identifier
  • the at least one contact group corresponding to the user identifier is a contact user identification group obtained by classifying the contact user identifier corresponding to the user identifier; the classification of the contact user identifier may be classified by the user according to his or her preference. It can also be classified according to a certain classification rule; for example, the contact group can be "family", “classmate”, “colleague” and the like.
  • the embodiment may select at least one contact user identifier from the at least one contact group to form a candidate identifier group, and the selection manner may be multiple.
  • the at least one contact group may be selected.
  • the contact user identifiers whose user IDs reach the preset thresholds constitute a candidate identifier group, that is, the step of “selecting at least one contact user identifier from the at least one contact group” may include:
  • a contact user identifier whose intimacy is greater than a preset threshold is selected from the at least one contact group.
  • the interaction between the two user identifiers may be counted, and then the intimacy between the user identifiers is obtained based on the statistical result.
  • This interaction can include chats, mutual reviews, and the like.
  • the intimacy between the user identifiers can be obtained, for example, between the father and the child, between the mother and the child, the intimacy between the siblings is high, and between the students. The intimacy is slightly lower, the intimacy between strangers is the lowest, and so on.
  • the contact user identifier corresponding to the preset type may be selected from the at least one contact group to form a candidate identifier group, for example, a contact user identifier that is related to the user's family relationship may be selected, that is,
  • the step of “selecting at least one contact user identifier from the at least one contact group” may include:
  • the contact type may be set by the user, or may be a system default contact type, which may represent a social relationship between the contact and the user; for example, the contact type may be: family, colleague, classmate and many more.
  • the contact type in the embodiment may be obtained according to the contact type grouped by the contact where the contact user identifier is located, that is, the step “acquiring the contact type corresponding to the contact user identifier in each contact group” may include :
  • the contact type corresponding to each contact group is used as the contact type corresponding to the contact user identifier in the contact group.
  • the identifier information corresponding to each contact group is obtained to obtain the contact type corresponding to the contact group, that is, the step of “acquiring the contact type corresponding to each contact group” may include:
  • the information obtains the contact type corresponding to the contact group; for example, when the contact group includes “family” or “colleague”, the name “family” of the contact group can be obtained, and then the contact user can be determined based on the name of the group.
  • the corresponding contact type of the logo is a relative or family member.
  • the default type can be set according to actual requirements.
  • the preset type can be intimate with the user.
  • the intimacy calculation can refer to the calculation scheme described above, and can be set as the user in this embodiment.
  • Family members parents, children, siblings, etc., etc., at this time, the contact user ID corresponding to the user's family member can be selected from the contact group.
  • a contact user identifier whose contact type is the same as the preset type may be selected from the contact group as a candidate identifier group; that is, the step “according to the contact type corresponding to the contact user identifier, from the at least one
  • the selecting a contact user identifier corresponding to the preset type in the contact group includes: selecting, from the at least one contact group, a contact identifier whose contact type is the same as the preset type. For example, when the preset contact type is family, the user ID of the family member can be selected from the contact group.
  • the contact group with the same contact type and the preset type can be directly selected as the candidate identifier group, that is, the contact type corresponding to the contact user identifier is the contact of the contact user identifier.
  • the step of “selecting a contact identifier whose contact type is the same as the preset type from the at least one contact group” may include: selecting a contact type and a pre-selection from the at least one contact group. Set the contact group of the same type; for example, the preset contact type is family and the contact group has a family group. In this case, all the user identifiers in the family group can be selected to form a candidate identifier group.
  • the contact user identifier may be randomly selected from the candidate identifier group as the target user identifier, for example, the social relationship between the contact and the user may be obtained, and then, based on the relationship between the contact and the user.
  • the social relationship is randomly selected; in actual application, the social relationship between the contact and the user can be established through the mutual remark information of the contact and the user; that is, the step “selectly select the contact user identifier from the candidate identification group as the target user identifier.
  • the contact user identifier is randomly selected from the candidate identifier group as the target user identifier according to the social relationship.
  • the social relationship map may also be established, and then the target user identifier is randomly selected based on the social relationship map; that is, the step “according to the The social relationship randomly selecting the contact user identifier from the candidate identifier group as the target user identifier may include:
  • the contact user identifier corresponding to the target contact is obtained from the candidate identifier group, and the obtained contact user identifier is used as the target user identifier.
  • the user when the preset contact type is family, that is, when the candidate identification group includes the user identifier of the user's family, the user can obtain the remark information of the user identification of the user, and the remark information of the user identification of the user by the family, and then, based on The mutual information between the user and the family can obtain the specific social relationship between the user and the family (parents, children, siblings, etc.), and after acquiring the social relationship between the user and the family, a social relationship map can be generated; for example, There is a family group in the contact group of user A. The family group has three contact user identifiers, and the user A notes the father (user B), the mother (user C), and the brother (user D) respectively.
  • the backup of user A in user C and user D is: son, son, brother; so the system can get the social relationship between user A, user B, user C, and user D.
  • a social relationship map between the user A and the user B, the user C, and the user D can be established based on the social relationship, and reference is made to FIG. 1b.
  • the embodiment may send the verification information based on the login status of the target user identifier, that is, the step of “sending the verification information to the corresponding target terminal according to the target user identifier” may include:
  • the verification information is sent to the target terminal corresponding to the target user identifier.
  • the login information of the instant messaging identifier can be obtained, and then the instant messaging identifier is determined to be online (ie, whether the user is logged in), and if so, the authentication information is sent to the terminal corresponding to the instant messaging identifier. .
  • the method in this embodiment sends the verification information to the terminal corresponding to the communication identifier bound to the target user identifier in the case that the target user identifier is not logged in; that is, the step “ Sending verification information to the corresponding target terminal according to the target user identifier may also include:
  • the mobile phone number (such as the secret mobile phone number) bound to the target instant messaging identifier may be obtained, and then the verification letter is sent to the terminal corresponding to the mobile phone number. interest.
  • the verification information may be a verification code or other information for verification
  • the target terminal may be a terminal such as a mobile phone, a tablet computer, or a personal computer.
  • the target terminal can provide the verification information to the terminal in multiple manners.
  • the target terminal can send the verification information to the terminal, and for example, the target terminal can also display the verification information, so that the user can view the input terminal, etc. Etc., the specific way of providing can be selected according to actual needs.
  • the server receives the verification information sent by the terminal, and then compares the verification information with the pre-stored verification information. If they are consistent, the identity verification is determined to pass; otherwise, the identity verification fails.
  • the identity verification method in this embodiment can be applied to various scenarios, such as modifying a password, a large amount of payment, and the like.
  • the embodiment of the present application adopts an identity verification request sent by the receiving terminal, where the identity verification request carries the user identifier of the user, and then obtains the target user identifier according to the identity verification request, where the target user identifier is the contact of the user.
  • the user identifier sends the verification information to the corresponding target terminal according to the target user identifier, so that the target terminal provides the verification information to the terminal, receives the verification information sent by the terminal, and identifies the user corresponding to the user identifier according to the verification information.
  • the scheme can send the verification information to the terminal of the user's contact, so that the user obtains the verification information from the contact to complete the authentication; since the verification information is not sent to the user but is sent to the user Contact (such as a user in a social network), even in the case of a confidential mobile phone number leak, it is difficult for criminals to know which contact the verification information is sent to, so that the verification information cannot be stolen from the contact, as opposed to the current Technically, you can improve the security of authentication.
  • the solution can also avoid the problem that the user cannot receive the authentication certificate due to the replacement of the secret mobile phone, thereby failing to complete the identity authentication, and also saving the SMS cost of the mobile phone.
  • an example in which the identity verification device is integrated in the server, the user's contact is the user's instant messaging friend, and the user identifier is the instant messaging identifier is taken as an example.
  • the identity verification device is integrated into the server in various ways, for example, to the client or its His software is installed on the server.
  • the specific process of the identity verification method can be as follows:
  • the terminal sends an identity verification request to the server, where the identity verification request carries the instant messaging identifier a of the user A.
  • the terminal receives the identity verification request triggered by the user through the authentication request interface, and sends the identity verification request to the server through the network, where the identity verification request carries the instant messaging identifier of the user.
  • the server obtains a friend group corresponding to the instant message identifier a according to the identity verification request, where the friend group includes a friend instant message identifier, and the friend instant message identifier is an instant message identifier of the friend of the user A.
  • the server may check the buddy group corresponding to the instant messaging identifier a in the database, such as family grouping, colleague grouping, classmate grouping, etc.; each buddy group includes at least one user A's instant messaging identifier.
  • the friend of the user A may be another user associated with the instant messaging identifier a.
  • the instant messaging identifier adds a friend or a user of interest to each other. Therefore, the friend of the user A may be in reality. Friends, can also be friends on the network.
  • the buddy grouping may be a buddy grouping that is obtained by classifying the instant messaging identifier of the buddy of the user A.
  • the categorization of the identities may be classified into multiple types, for example, may be classified based on the user's preferences or settings, and For example, the system default classification rules are used for classification.
  • the server selects a friend instant messaging identifier from the group of friends to obtain a candidate identifier group.
  • the server may obtain the friend type corresponding to the friend instant message in the friend group, and then select the friend instant message identifier whose friend type is the same as the preset type from the friend group, and form a candidate identifier group according to the selected friend instant message identifier.
  • the buddy type may be a buddy type set by the user according to his or her own situation, or may be a default buddy type of the system, such as a family member, a colleague, a classmate, a leader, and the like.
  • the preset type can also be set according to actual needs, for example, the preset type can be a family member or the like.
  • the friend type corresponding to the friend instant message identifier may be the friend type corresponding to the friend group of the friend instant message identifier.
  • the server may group the friend with the same friend type and the preset type as the candidate identifier group.
  • the server randomly selects a friend instant messaging identifier from the candidate identifier group as the target instant messaging identifier.
  • the server randomly selects a friend instant messaging identifier from the candidate identifier group as the target instant messaging identifier.
  • the embodiment may also obtain a social relationship map between the friend and the user, and then randomly select the target instant messaging identifier based on the social relationship map between the friend and the user; for example, the server may obtain the The first remark information set by the user A for the buddy instant messaging identifier in the candidate identification group, and the second remark information set by the buddy to the instant messaging identifier a, and then, according to the first remark information and the second remark information Establish a social relationship map between the user A and the friend; at this time, if the target identifier needs to be selected, the target friend of the user may be randomly selected from the social relationship map, and then the friend corresponding to the target friend is obtained from the candidate identifier group. The instant messaging identifier is obtained, and the obtained friend instant messaging identifier is used as the target user identifier.
  • the target friend selected by the server in the social relationship graph of the user A is “mother”.
  • the server will obtain the instant messaging identifier of the user A mother from the candidate identification group.
  • the server obtains login information corresponding to the target instant messaging identifier.
  • the server determines, according to the login information, whether the target instant messaging identifier is logged in. If yes, step 207 is performed, and if no, step 208 is performed.
  • the server may obtain the login status information corresponding to the target instant messaging identifier, and then determine, according to the login status information, whether the target instant messaging identifier is online (ie, logged in).
  • the server sends the verification information to the target terminal corresponding to the target instant messaging identifier, so that the target terminal provides the verification information to the terminal, and then proceeds to step 209.
  • the server invokes the message push interface to send the verification information to the target terminal corresponding to the target instant messaging identifier.
  • the server may send a verification code to the target terminal corresponding to the instant messaging identifier of the user A's mother.
  • the server obtains the communication identifier bound to the target instant messaging identifier, and sends the verification information to the target terminal corresponding to the communication identifier, so that the target terminal provides the verification information to the terminal.
  • the server may obtain a mobile phone number or an email address bound to the target instant messaging identifier, and send the verification information to the corresponding target terminal by using a short message method or a mail method.
  • the target terminal may provide the verification information to the terminal, for example, sending the terminal to the terminal, for example, displaying the verification information, waiting for the user A to view the acquisition, and the like.
  • the terminal acquires the verification information, and sends the verification information to the server.
  • the terminal may receive the verification information sent by the target terminal, and then send the verification information to the server; for example, the terminal may further receive the verification information input by the user, and then send the verification information to the server; for example, the terminal may receive the user through The information enters the verification information input by the control, and then sends the verification information to the server, and the like.
  • the server performs identity verification on the user A corresponding to the instant messaging identifier a according to the verification information.
  • the server may compare the verification information with the previously saved verification information. If they are consistent, the verification passes, and if they are inconsistent, the verification fails.
  • the manner of performing identity verification based on the verification information in this embodiment is not limited to information comparison, and may be other methods.
  • the identity verification method of the present application is not only applicable to the instant messaging identifier, but also applicable to other user identifiers.
  • the embodiment of the present application uses the terminal to send an identity verification request to the server, and then the server obtains the friend group corresponding to the instant message identifier a according to the identity verification request, and the server selects the friend instant message identifier from the friend group to obtain
  • the server randomly selects the friend instant messaging identifier from the candidate identifier group as the target instant messaging identifier, and the server obtains the login information corresponding to the target instant messaging identifier, and the server determines, according to the login information, whether the target instant messaging identifier has been Logging in, if yes, the server sends the verification information to the target terminal corresponding to the target instant messaging identifier, so that the target terminal provides the verification information to the terminal, and if not, the server obtains the communication bound to the target instant messaging identifier.
  • Identifying, and sending verification information to the target terminal corresponding to the communication identifier so that the target terminal provides the verification information to the terminal, the terminal obtains the verification information, and sends the verification information to the server, and the server performs the verification information according to the verification information.
  • the user A corresponding to the communication identifier a performs identity verification; the solution may randomly send the verification information to the terminal of the user's friend, so that the user obtains the verification information from the friend to complete the identity verification; since the verification information is not sent to the user himself It is sent to a friend, even if the secret mobile phone number is leaked, it is difficult for the criminals to know which friend the verification information is sent to, so that the verification information cannot be stolen from the friend, and the authentication can be improved compared with the prior art. safety.
  • the solution can also avoid the problem that the user cannot receive the authentication certificate due to the replacement of the secret mobile phone, thereby failing to complete the identity authentication, and also saving the SMS cost of the mobile phone.
  • the embodiment of the present application further provides an identity verification apparatus.
  • the identity verification apparatus may further include a request receiving unit 301, an identifier obtaining unit 302, an information sending unit 303, and a verification unit. 304, as follows:
  • the request receiving unit 301 is configured to receive an identity verification request sent by the terminal, where the identity verification request carries a user identifier of the user.
  • the request receiving unit 301 may be specifically configured to receive an identity verification request sent by the terminal through the wireless network.
  • the user identifier may be a communication account, and the communication account may be an instant messaging account or other communication account, such as an email account, a social network account, and the like.
  • the identifier obtaining unit 302 is configured to obtain a target user identifier according to the identity verification request, where the target user identifier is a user identifier of the contact of the user.
  • the user's contact may be another user corresponding to another user identifier that establishes contact with the user identifier of the user, such as a user who has added a contact to each other in the instant messaging. Therefore, the user's contact is not limited to the reality.
  • a friend can also be a user who is not a contact with the user in reality but is a contact on the network.
  • the identifier obtaining unit 302 may specifically include: an identifier group obtaining subunit and an identifier selecting subunit.
  • the identifier group obtaining sub-unit is configured to obtain, according to the identity verification request, a candidate identifier group corresponding to the user identifier, where the candidate identifier group includes at least one contact user identifier, where the contact user identifier is a user identifier of the user's contact .
  • the identifier selection subunit is configured to randomly select a contact user identifier from the candidate identifier group as the target user identifier.
  • the identity group obtaining subunit is specifically used for:
  • each contact group includes at least one contact user identifier
  • the identifier group acquires a subunit, specifically for:
  • Each contact group includes at least one contact user identifier
  • the contact group corresponding to the user identifier is an identifier group obtained by classifying the contact user identifier corresponding to the user identifier; the classification of the user identifier may be classified by the user according to his or her preference, or may be classified according to a certain classification. The rules are classified; for example, the contact group can be "family", “classmate”, “colleague”, and the like.
  • the identifier selection subunit in this embodiment may be specifically used to:
  • the contact user identifier is randomly selected from the candidate identifier group as the target user identifier according to the social relationship.
  • the identifier selects a subunit, specifically for:
  • the contact user identifier corresponding to the target contact is obtained from the candidate identifier group, and the obtained contact user identifier is used as the target user identifier.
  • the information sending unit 303 is configured to send verification information to the corresponding target terminal according to the target user identifier, so that the target terminal provides the verification information to the terminal.
  • the information sending unit 303 can be specifically configured to:
  • the verification information is sent to the target terminal corresponding to the target user identifier.
  • the information sending unit 303 can also be used to:
  • the verification unit 304 is configured to receive the verification information sent by the terminal, and perform identity verification on the user corresponding to the user identifier according to the verification information.
  • the verification unit 304 can be specifically configured to:
  • the foregoing units may be implemented as a separate entity, or may be implemented in any combination, and may be implemented as the same or a plurality of entities. For the specific implementation of the foregoing, refer to the foregoing method embodiments, and details are not described herein.
  • the authentication device can be integrated in a device such as a server, for example, in a server or other software.
  • the request receiving unit 301 receives the identity verification request sent by the terminal, where the identity verification request carries the user identifier of the user, and then the identifier obtaining unit 302 acquires the target user identifier according to the identity verification request, and the target The user identifier is the user identifier of the user's contact, and the information sending unit 303 sends the verification information to the corresponding target terminal according to the target user identifier, so that the target terminal provides the verification information to the terminal, and the verification unit 304 receives the terminal.
  • the solution may randomly send the verification information to the terminal of the user's contact, so that the user obtains the verification information from the contact and completes Authentication; since the authentication information is not sent to the user but to the contact, even in the case where the secret mobile phone number is leaked, it is difficult for the criminals to know which contact the verification information is sent to, and thus cannot be stolen from the contact person.
  • Verification information relative to the prior art, Improve the security of authentication.
  • the solution can also avoid the problem that the user cannot receive the authentication certificate due to the replacement of the secret mobile phone, thereby failing to complete the identity authentication, and also saving the SMS cost of the mobile phone.
  • the foregoing identity authentication method can be applied to a network environment formed by the server 403 and the terminal 401 as shown in FIG. 4.
  • FIG. 4 is a schematic diagram of a network environment according to an embodiment of the present application.
  • the server 403 is connected to the terminal 401 through a network, where the network includes but is not limited to: a wide area network, a metropolitan area network, or a local area network, and the terminal 401 is not limited.
  • the network includes but is not limited to: a wide area network, a metropolitan area network, or a local area network
  • the terminal 401 is not limited.
  • the terminal 401 is not limited.
  • FIG. 5 is a schematic structural diagram of a server 403 according to an embodiment of the present application.
  • the server 403 includes The processor 510, the memory 550, and the transceiver 530, the memory 550 can include read only memory and random access memory, and provide operational instructions and data to the processor 510.
  • a portion of the memory 550 may also include non-volatile random access memory (NVRAM).
  • NVRAM non-volatile random access memory
  • memory 550 stores elements, executable modules or data structures, or a subset thereof, or their extended set.
  • the memory 550 is configured to store program instructions required to execute the method and related data required or generated by the execution of the program instructions
  • the transceiver 530 is used in the processor 510.
  • the processor 510 controls the operation of the server 403, which may also be referred to as a CPU (Central Processing Unit).
  • Memory 550 can include read only memory and random access memory and provides instructions and data to processor 510. A portion of the memory 550 may also include non-volatile random access memory (NVRAM).
  • the specific components of the server 403 are coupled together by a bus system 520 in a specific application.
  • the bus system 520 may include a power bus, a control bus, a status signal bus, and the like in addition to the data bus. However, for clarity of description, various buses are labeled as bus system 520 in the figure.
  • Processor 510 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method may be completed by an integrated logic circuit of hardware in the processor 510 or an instruction in a form of software.
  • the processor 510 described above may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or discrete hardware. Component.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 550, and the processor 510 reads the information in the memory 550 and completes it in combination with hardware. The steps of the above method.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.
  • ROM Read Only Memory
  • RAM Random Access Memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例公开了一种身份验证方法和装置。所述身份验证方法包括：接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识；根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识；根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端；接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证。该方案可以将验证信息发给用户的联系人的终端，以使用户从联系人处获取验证信息从而完成身份验证，相对于现有技术而言，可以提高身份验证的安全性。

Description

身份验证方法和装置
本申请要求于2016年5月5日提交中国专利局、申请号为201610296640.0、发明名称为“一种身份验证方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通讯技术领域，具体涉及一种身份验证方法和装置。
背景技术
现如今，各种各样的数据充斥着人们的生活，比如网络购物、转账以及会话等等，无不涉及到数据的处理，而数据的安全，更是牵涉到人们的生命财产安全。
在现有技术中，一般都会通过身份验证的方式来提高数据的安全性，比如，根据用户提供的验证信息，如账号和密码、验证码等，与预存的验证信息进行比较，若一致，则验证通过，否则，则确定验证不通过。
其中，短信验证是目前最主流的身份验证方式，具体地，在进行身份验证时，服务器获取与账号绑定的手机号码(即密保手机号码)，然后，服务器通过短信发送验证码给该手机号码对应的手机，服务器接收该手机发送的验证码，并与预存的验证码进行比较，若相同，则身份验证通过，否则，身份验证不通过。
在对现有技术的研究和实践过程中，本申请的发明人发现，现有短信验证方式，需要向账户绑定的密保手机发送验证码，然而随着不法分子的技术越来高明，用户的密保手机号码很容易被不法分子窃取，这样密保手机接收到的验证码很容易被窃取，如通过短信钓鱼手段获取，因此，降低身份验证的安全性。
发明内容
本申请实施例提供一种身份验证方法和装置，可以提高身份验证的安全性。
本申请实施例提供一种身份验证方法，包括：
接收终端发送的身份验证请求，所述身份验证请求携带用户的用户标识；
根据所述身份验证请求获取目标用户标识，所述目标用户标识为所述用户 的联系人的用户标识；
根据目标用户标识向相应的目标终端发送验证信息，以便所述目标终端将所述验证信息提供给所述终端；
接收所述终端发送的所述验证信息，并根据所述验证信息对所述用户标识对应的用户进行身份验证。
相应地，本申请实施例还提供一种身份验证装置，包括：
请求接收单元，用于接收终端发送的身份验证请求，所述身份验证请求携带用户的用户标识；
标识获取单元，用于根据所述身份验证请求获取目标用户标识，所述目标用户标识为所述用户的联系人的用户标识；
信息发送单元，用于根据目标用户标识向相应的目标终端发送验证信息，以便所述目标终端将所述验证信息提供给所述终端；
验证单元，用于接收所述终端发送的所述验证信息，并根据所述验证信息对所述用户标识对应的用户进行身份验证。
本申请实施例采用接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识，然后，根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识，根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证；该方案可以将验证信息发给用户的联系人的终端，以使用户从其联系人处获取验证信息从而完成身份验证；由于将验证信息不是发给用户本人而是发给用户的联系人，即使在密保手机号码泄露的情况下，不法分子很难获知验证信息发送给哪个联系人，从而无法从联系人处窃取验证信息，相对于现有技术而言，可以提高身份验证的安全性。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1a是本申请实施例一提供的一种身份验证方法的流程图；
图1b是本申请实施例一提供的一种社会关系图谱示意图；
图2是本申请实施例二提供的一种身份验证方法的流程图；
图3是本申请实施例三提供的一种身份验证装置的结构示意图；
图4是本申请实施例所应用的网络环境的示意图；
图5是本申请实施例的服务器的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整的描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例提供一种身份验证方法和装置。以下将分别进行详细说明。
实施例一
本实施例将从身份验证装置的角度进行描述，该身份验证装置具体可以集成在服务器等其他需要进行身份验证的设备中。
一种身份验证方法，包括：接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识，然后，根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识，根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证。
如图1a所示，该身份验证方法的具体流程可以如下：
101、接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识。
具体地，可以通过无线网络接收终端发送的身份验证请求，例如，通过wifi接收终端发送的身份验证请求。
其中，用户标识可以为通讯账号，该通讯账号可以为即时通讯账号、或者其他通讯账号，如电子邮箱账号、社交网络账号等等。
102、根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识。
本实施例中，用户的联系人可以为与该用户的用户标识建立联系的其他用户标识对应的其他用户，其可以为在通讯网络中与用户的通讯标识建立联系的其他通讯标识对应的其他用户，比如，可以为在社交网络与用户相互添加了好 友的其他用户，例如即时通讯中与用户相互添加了好友的其他用户、电子邮箱中与用户相互添加了好友的其他用户等等，因此，该用户的联系人不仅限于现实中的好朋友，也可以是与该用户在现实中不是好友，但是在网络上是好友的用户。
其中，根据身份验证请求获取目标用户标识的方式可以有多种，比如，可以设置一个用于发送验证信息的标识集合，在需要发送验证信息时，可以从该标识集合随机选取一个用户标识进行下发验证信息；也即步骤“根据该身份验证请求获取目标用户标识”可以包括：
根据该身份验证请求获取该用户标识对应的候选标识组，该候选标识组包括至少一个联系人用户标识，该联系人用户标识为该用户的联系人的用户标识；
从该候选标识组中随机选取联系人用户标识作为目标用户标识。
其中，候选标识组可以由用户自行设置，也可以由系统设置，比如，可以基于用户标识对应的联系人分组来设置候选标识组，也即步骤“根据该身份验证请求获取该用户标识对应的候选标识组”可以包括：
根据该身份验证请求获取该用户标识对应的至少一个联系人分组，其中，每个联系人分组包括至少一个联系人用户标识；
从所述至少一个联系人分组中选取至少一个联系人用户标识，以得到该候选标识组。
其中，用户标识对应的至少一个联系人分组为对该用户标识对应的联系人用户标识进行分类后得到的联系人用户标识群组；联系人用户标识的分类可以是用户根据自己的喜好进行分类，也可以是按照某种分类规则进行分类；比如，联系人分组可以为“家人”、“同学”、“同事”等等。
本实施例可以从所述至少一个联系人分组中选取至少一个联系人用户标识来组成候选标识组，该选取的方式可以有多种，可选地，可以从所述至少一个联系人分组中选取与用户标识的亲密度达到预设阈值的联系人用户标识组成候选标识组，也即步骤“从所述至少一个联系人分组中选取至少一个联系人用户标识”可以包括：
获取所述至少一个联系人分组中联系人用户标识与用户标识之间的亲密度；
从所述至少一个联系人分组中选取亲密度大于预设阈值的联系人用户标识。
其中，获取两个用户标识之间的亲密度方式可以有多种，比如，可以统计两个用户标识之间的互动情况，然后，基于统计结果来获取用户标识之间的亲密度。该互动情况可以包括聊天情况、相互评论情况等等。又比如，还可以基于两个用户之间的亲属关系，来获取用户标识之间的亲密度，比如，父子之间，母子之间，姐弟之间的亲密度就高点，同学之间的亲密度稍微低一点，陌生人之间的亲密度最低等等。
可选地，本实施例还可以从至少一个联系人分组中选取与预设类型对应的联系人用户标识，组成候选标识组，比如，可以选取与用户为家人关系的联系人用户标识，也即步骤“从所述至少一个联系人分组中选取至少一个联系人用户标识”可以包括：
获取每个联系人分组中联系人用户标识对应的联系人类型；
根据联系人用户标识对应的联系人类型，从所述至少一个联系人分组中选取与预设类型对应的联系人用户标识。
本实施例中联系人类型可以由用户自己设置，也可以采用系统默认的联系人类型，其可以表示该联系人与用户之间的社会关系；比如，联系人类型可以为：家人、同事、同学等等。可选地，本实施例中联系人类型可以根据联系人用户标识所在联系人分组的联系人类型获取，也即步骤“获取每个联系人分组中联系人用户标识对应的联系人类型”可以包括：
获取每个联系人分组对应的联系人类型；
将各联系人分组对应的联系人类型作为与该联系人分组中联系人用户标识对应的联系人类型。
具体地，获取各联系人分组对应的标识信息来获取该联系人分组对应的联系人类型，也即步骤“获取每个联系人分组对应的联系人类型”可以包括：根据各联系人分组的标识信息获取该联系人分组对应的联系人类型；比如，联系人分组包括“家人”、“同事”时，可以获取联系人分组的名称“家人”，然后基于该分组的名称可以确定该联系人用户标识对应的联系人类型为亲属或者家人等。
其中，预设类型可以根据实际需求设定，比如，预设类型可以与用户具有亲密度高的联系人类型；该亲密度计算可以参考上述介绍的计算方案，如本实施例可以设置为用户的家人(父母、子女、兄弟姐妹等)等，此时可以从联系人分组中选取用户家人对应的联系人用户标识。
具体地，可以从联系人分组中选取联系人类型与预设类型相同的联系人用户标识，以作为候选标识组；也即步骤“根据联系人用户标识对应的联系人类型，从所述至少一个联系人分组中选取与预设类型对应的联系人用户标识”具体包括：从所述至少一个联系人分组中选取联系人类型与预设类型相同的联系人标识。比如，预设联系人类型为家人时，可以从联系人分组中选取家人的用户标识。
在实际应用中，为了提高身份验证速度，可以直接选取联系人类型与预设类型相同的联系人分组作为候选标识组，即在联系人用户标识对应的联系人类型为联系人用户标识所在联系人分组的联系人类型时，步骤“从所述至少一个联系人分组中选取联系人类型与预设类型相同的联系人标识”可以包括：从所述至少一个联系人分组中选取联系人类型与预设类型相同的联系人分组；比如，预设联系人类型为家人且联系人分组存在家人分组，此时，可以选取家人分组中所有的用户标识组成候选标识组。
本实施例在获取候选标识组之后，可以从候选标识组中随机选取联系人用户标识作为目标用户标识，例如可以获取联系人与用户之间的社会关系，然后，基于联系人与用户之间的社会关系来随机选取；实际应用中可以通过联系人与用户相互的备注信息来建立联系人与用户之间的社会关系；也即步骤“从候选标识组中随机选取联系人用户标识作为目标用户标识”可以包括：
获取该用户对该候选标识组中联系人用户标识设置的第一备注信息，以及该联系人对该用户标识设置的第二备注信息；
根据该第一备注信息和该第二备注信息获取该用户与该联系人之间的社会关系；
根据该社会关系从该候选标识组中随机选取联系人用户标识作为目标用户标识。
可选地，为方便选取目标用户标识，在获取联系人与用户之间的社会关系之后，还可以建立社会关系图谱，然后，基于该社会关系图谱随机选取目标用户标识；也即步骤“根据该社会关系从该候选标识组中随机选取联系人用户标识作为目标用户标识”可以包括：
根据联系人与用户之间的社交关系建立用户与联系人之间的社会关系图谱；
从该社会关系图谱中随机选取该用户的目标联系人；
从候选标识组中获取该目标联系人对应的联系人用户标识，并将获取的联系人用户标识作为目标用户标识。
比如，在预设联系人类型为家人时，即候选标识组包括用户家人的用户标识时，可以获取用户对家人的用户标识的备注信息，以及家人对用户的用户标识的备注信息，然后，基于用户与家人相互的备注信息，可以获取用户与家人之间的具体社会关系(父母、子女、兄弟姐妹等)，在获取用户与家人之间的社会关系之后，可以生成社会关系图谱；例如，在用户A的联系人分组中存在家人分组，该家人分组有三个联系人用户标识，分别被用户A备注爸爸(用户B)、妈妈(用户C)、哥哥(用户D)，此时，可以获取用户B、用户C、用户D的联系人备注中对用户A的备份为：儿子、儿子、弟弟；这样系统就能得到用户A、用户B、用户C、用户D这个四个用户之间的社会关系，此时，可以基于社会关系建立用户A与用户B、用户C、用户D之间的社会关系图谱，参考图1b。
103、根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端。
为保证验证信息可以发送成功，本实施例可以基于目标用户标识的登录情况来发送验证信息，也即步骤“根据目标用户标识向相应的目标终端发送验证信息”可以包括：
获取该目标用户标识对应的登录信息；
根据该登录信息确定该目标用户标识是否已登录；
若是，则向该目标用户标识对应的目标终端发送验证信息。
比如，当用户标识为即时通讯标识时，可以获取即时通讯标识的登录信息，然后，判断该即时通讯标识是否在线(即是否已登录)，若是，则向该即时通讯标识对应的终端发送验证信息。
可选地，为了保证用户可以接收到验证信息，本实施例方法还在目标用户标识没有登录情况下，向与该目标用户标识绑定的通讯标识对应的终端发送验证信息；也即，步骤“根据目标用户标识向相应的目标终端发送验证信息”还可以包括：
当确定该目标用户标识未登录时，获取与该目标用户标识绑定的通讯标识；
向该通讯标识对应的目标终端发送验证信息。
例如，当目标即时通讯标识没有登录时，可以获取与该目标即时通讯标识绑定的手机号码(如密保手机号码)，然后，向该手机号对应的终端发送验证信 息。
本实施例中验证信息可以为验证码或者其他用于验证的信息，该目标终端可以为手机、平板电脑、个人计算机等终端。
其中，该目标终端将该验证信息提供给该终端的方式有多种，比如，目标终端可以将验证信息发送给终端，又比如，目标终端还可以显示验证信息，以便用户查看后输入终端，等等，具体的提供方式可以根据实际需求选择。
104、接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证。
比如，服务器接收终端发送的验证信息，然后，将验证信息与预先存储的验证信息进行比较，若一致，则确定身份验证通过，否则，确定身份验证不通过。
本实施例中身份验证方法可以应用于各种场景，比如，修改密码，大额支付等敏感场景。
由上可知，本申请实施例采用接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识，然后，根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识，根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证；该方案可以将验证信息发给用户的联系人的终端，以使用户从其联系人处获取验证信息从而完成身份验证；由于将验证信息不是发给用户本人而是发给用户的联系人(如用户在社交网络中的好友)，即使在密保手机号码泄露的情况下，不法分子很难获知验证信息发送给哪个联系人，从而无法从联系人处窃取验证信息，相对于现有技术而言，可以提高身份验证的安全性。
此外，该方案还可以避免用户由于更换密保手机，无法收到鉴权凭证，从而无法完成身份鉴权的问题，同时还可节约手机的短信成本。
实施例二
根据实施例一所描述的方法，以下将举例作进一步详细说明。
在本实施例中，将以身份验证装置集成在服务器中、用户的联系人为用户的即时通讯好友、以及用户标识为即时通讯标识为例进行详细说明。
其中，该身份验证装置集成在服务器的方式有多种，比如，以客户端或其 他软体形式安装在服务器中。
如图2所示，该身份验证方法的具体流程可以如下：
201、终端向服务器发送身份验证请求，该身份验证请求携带用户A的即时通讯标识a。
比如，终端接收用户通过验证请求接口触发的身份验证请求，并通过网络向服务器发送该身份验证请求，其中，该身份验证请求携带该用户的即时通讯标识。
202、服务器根据身份验证请求获取该即时通讯标识a对应的好友分组，其中，该好友分组包括好友即时通讯标识，该好友即时通讯标识为用户A的好友的即时通讯标识。
比如，服务器可以在数据库中查收该即时通讯标识a对应的好友分组，如，家人分组、同事分组、同学分组等等；每个好友分组均包括至少一个用户A的好友的即时通讯标识。
本实施例中，用户A的好友可以为与即时通讯标识a建立关联的其他用户，如，即时通讯标识之间相互添加了好友或者关注的用户，因此，该用户A的好友可以为现实中的好友，也可以为网络中好友。
具体地，该好友分组可以为对用户A的好友的即时通讯标识分类后得到的好友分组，本实施例中对标识分类的方式有多种，比如，可以基于用户的喜好或者设置来分类，又比如，采用系统默认的分类规则进行分类。
203、服务器从好友分组中选取好友即时通讯标识，以得到候选标识组。
比如，服务器可以获取好友分组中好友即时通讯对应的好友类型，然后，从好友分组中选取好友类型与预设类型相同的好友即时通讯标识，并根据选取的好友即时通讯标识构成候选标识组。
其中，好友类型可以由用户根据自身情况自行设置的好友类型，也可以是系统默认的好友类型，比如，家人、同事、同学、领导等等。
该预设类型也可以根据实际需求设定，比如，预设类型可以为家人等等。在实际应用中，好友即时通讯标识对应的好友类型可以为该好友即时通讯标识所在好友分组对应的好友类型，此时，服务器可以将好友类型与预设类型相同的好友分组作为候选标识组。
204、服务器从该候选标识组中随机选取好友即时通讯标识作为目标即时通讯标识。
具体地，服务器从该候选标识组中随机选取一个好友即时通讯标识作为目标即时通讯标识。
可选地，为了方便选取，本实施例还可以获取好友与用户之间的社会关系图谱，然后，基于好友与用户之间的社会关系图谱来随机选取目标即时通讯标识；比如，服务器可以获取该用户A对该候选标识组中好友即时通讯标识设置的第一备注信息，以及所述好友对该即时通讯标识a设置的第二备注信息，然后，根据该第一备注信息和该第二备注信息建立用户A与好友之间的社会关系图谱；此时，如果需要选取目标标识，可以从该社会关系图谱中随机选取该用户的目标好友，然后，从候选标识组中获取该目标好友对应的好友即时通讯标识，并将获取的好友即时通讯标识作为目标用户标识。
例如，服务器在用户A的社会关系图谱中选取的目标好友为“妈妈”，此时，服务器将会从候选标识组中获取用户A妈妈的即时通讯标识。
205、服务器获取目标即时通讯标识对应的登录信息。
206、服务器根据该登录信息确定该目标即时通讯标识是否已登录，若是，则执行步骤207，若否，则执行步骤208。
比如，服务器可以获取目标即时通讯标识对应的登录状态信息，然后，根据该登录状态信息确定该目标即时通讯标识是否在线(即已登录)。
207、服务器向该目标即时通讯标识对应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，转步骤209。
具体地，服务器调用消息推送接口向目标即时通讯标识对应的目标终端发送验证信息。
例如，服务器可以向用户A妈妈的即时通讯标识对应的目标终端发送验证码。
208，服务器获取与目标即时通讯标识绑定的通讯标识，并向该通讯标识对应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端。
比如，服务器在确定目标即时通讯标识没有登录时，可以获取与目标即时通讯标识绑定的手机号码或者电子邮箱，并通过短信方式或者邮件方式相相应的目标终端发送验证信息。
其中，该目标终端将该验证信息提供给该终端可以有多种，比如，主动发送给终端，又比如，显示该验证信息等待用户A来查看获取等等。
209，终端获取该验证信息，并向服务器发送该验证信息。
比如，终端可以接收目标终端发送的验证信息，然后，向服务器发送该验证信息；又比如，终端还可以接收用户输入的验证信息，然后，向服务器发送该验证信息；例如，终端可以接收用户通过信息输入控件输入的验证信息，然后，向服务器发送该验证信息等等。
210、服务器根据该验证信息对即时通讯标识a对应的用户A进行身份验证。
具体地，服务器可以将该验证信息与之前保存的验证信息进行比较，若一致，则验证通过，若不一致，则验证不通过。
本实施例中基于验证信息进行身份验证的方式不仅限于信息对比，还可以是其他方式。
应当理解的是：本实施例虽然以即时通讯标识为例来介绍本申请的身份验证方法，但是本申请的身份验证方法不仅限适用于即时通讯标识，还可以适用于其他用户标识。
由上可知，本申请实施例采用终端向服务器发送身份验证请求，然后，由服务器根据身份验证请求获取该即时通讯标识a对应的好友分组，由服务器从好友分组中选取好友即时通讯标识，以得到候选标识组，由服务器从该候选标识组中随机选取好友即时通讯标识作为目标即时通讯标识，由服务器获取目标即时通讯标识对应的登录信息，由服务器根据该登录信息确定该目标即时通讯标识是否已登录，若是，则由服务器向该目标即时通讯标识对应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，若否，则由服务器获取与目标即时通讯标识绑定的通讯标识，并向该通讯标识对应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，由终端获取该验证信息，并向服务器发送该验证信息，由服务器根据该验证信息对即时通讯标识a对应的用户A进行身份验证；该方案可以将验证信息随机发给用户的好友的终端，以使用户从好友处获取验证信息从而完成身份验证；由于将验证信息不是发给用户本人而是发给好友，即使在密保手机号码泄露的情况下，不法分子很难获知验证信息发送给哪个好友，从而无法从好友处窃取验证信息，相对于现有技术而言，可以提高身份验证的安全性。
此外，该方案还可以避免用户由于更换密保手机，无法收到鉴权凭证，从而无法完成身份鉴权的问题，同时还可节约手机的短信成本。
实施例三
为了更好地实施以上方法，本申请实施例还提供一种身份验证装置，如图3所示，该身份验证装置还可以包括请求接收单元301、标识获取单元302、信息发送单元303和验证单元304，如下：
(1)、请求接收单元301；
该请求接收单元301，用于接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识。
比如，请求接收单元301，可以具体用于可以通过无线网络接收终端发送的身份验证请求。
其中，用户标识可以为通讯账号，该通讯账号可以为即时通讯账号、或者其他通讯账号，如电子邮箱账号、社交网络账号等等。
(2)标识获取单元302；
标识获取单元302，用于根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识。
其中，用户的联系人可以为与该用户的用户标识建立联系的其他用户标识对应的其他用户，如即时通讯中相互添加了联系人的用户，因此，该用户的联系人不仅限于现实中的好朋友，也可以是与该用户在现实中不是联系人，但是在网络上是联系人的用户。
本实施例中，该标识获取单元302可以具体包括：标识组获取子单元和标识选取子单元。
所述标识组获取子单元用于根据该身份验证请求获取该用户标识对应的候选标识组，该候选标识组包括至少一个联系人用户标识，该联系人用户标识为该用户的联系人的用户标识。
所述标识选取子单元用于从该候选标识组中随机选取联系人用户标识作为目标用户标识。
比如，该标识组获取子单元具体用于：
根据该身份验证请求获取该用户标识对应的至少一个联系人分组，其中，每个联系人分组包括至少一个联系人用户标识；
从所述至少一个联系人分组中选取至少一个联系人用户标识，以得到该候选标识组。
又比如，该标识组获取子单元，具体用于：
根据该身份验证请求获取该用户标识对应的至少一个联系人分组，其中， 每个联系人分组包括至少一个联系人用户标识；
获取每个联系人分组中联系人用户标识对应的联系人类型；
根据联系人用户标识对应的联系人类型，从所述至少一个联系人分组中选取与预设类型对应的联系人用户标识，以得到该候选标识组。
其中，用户标识对应的联系人分组为对该用户标识对应的联系人用户标识进行分类后得到的标识群组；用户标识的分类可以是用户根据自己的喜好进行分类，也可以是按照某种分类规则进行分类；比如，联系人分组可以为“家人”、“同学”、“同事”等等。可选地，本实施例中标识选取子单元可以具体用于：
获取该用户对该候选标识组中联系人用户标识设置的第一备注信息，以及该联系人对该用户标识设置的第二备注信息；
根据该第一备注信息和该第二备注信息获取该用户与该联系人之间的社会关系；
根据该社会关系从该候选标识组中随机选取联系人用户标识作为目标用户标识。
比如，该标识选取子单元，具体用于：
根据该联系人与该用户之间的社会关系建立用户与联系人之间的社会关系图谱；
从该社会关系图谱中随机选取该用户的目标联系人；
从候选标识组中获取该目标联系人对应的联系人用户标识，并将获取的联系人用户标识作为目标用户标识。
(3)信息发送单元303；
信息发送单元303，用于根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端。
比如，信息发送单元303可以具体用于：
获取该目标用户标识对应的登录信息；
根据该登录信息确定该目标用户标识是否已登录；
若是，则向该目标用户标识对应的目标终端发送验证信息。
又比如，该信息发送单元303还可以用于：
当确定该目标用户标识未登录时，获取与该目标用户标识绑定的通讯标识；
向该通讯标识对应的目标终端发送验证信息。
(4)验证单元304；
验证单元304，用于接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证。
比如，该验证单元304可以具体用于：
接收终端发送的验证信息，然后，将验证信息与预先存储的验证信息进行比较，若一致，则确定身份验证通过，否则，确定身份验证不通过。具体实施时，以上各个单元可以作为独立的实体来实现，也可以进行任意组合，作为同一或若干个实体来实现，以上各个单元的具体实施可参见前面的方法实施例，在此不再赘述。
该身份验证装置可以集成在服务器等设备中，比如，以客户端或其他软体形式安装服务器中。
由上可知，本申请实施例采用请求接收单元301接收终端发送的身份验证请求，该身份验证请求携带用户的用户标识，然后，由标识获取单元302根据该身份验证请求获取目标用户标识，该目标用户标识为该用户的联系人的用户标识，由信息发送单元303根据目标用户标识向相应的目标终端发送验证信息，以便该目标终端将该验证信息提供给该终端，由验证单元304接收该终端发送的该验证信息，并根据该验证信息对该用户标识对应的用户进行身份验证；该方案可以将验证信息随机发给用户的联系人的终端，以使用户从联系人处获取验证信息从而完成身份验证；由于将验证信息不是发给用户本人而是发给联系人，即使在密保手机号码泄露的情况下，不法分子很难获知验证信息发送给哪个联系人，从而无法从联系人处窃取验证信息，相对于现有技术而言，可以提高身份验证的安全性。
此外，该方案还可以避免用户由于更换密保手机，无法收到鉴权凭证，从而无法完成身份鉴权的问题，同时还可节约手机的短信成本。
根据本申请实施例，上述的身份认证方法可以应用于如图4所示的服务器403和终端401所构成的网络环境中。图4是根据本申请实施例的网络环境的示意图，如图4所示，服务器403通过网络与终端401进行连接，上述网络包括但不限于：广域网、城域网或局域网，终端401并不限定于计算机、手机、平板电脑等。
根据本申请的另一方面，还提供了一种用于实施上述身份认证方法的服务器，图5是本申请实施例提供的服务器403的结构示意图。所述服务器403包括处 理器510、存储器550和收发器530，存储器550可以包括只读存储器和随机存取存储器，并向处理器510提供操作指令和数据。存储器550的一部分还可以包括非易失性随机存取存储器(NVRAM)。
在一些实施方式中，存储器550存储了如下的元素，可执行模块或者数据结构，或者他们的子集，或者他们的扩展集。
在本申请实施例中，所述存储器550用于存储执行本方法所需的程序指令以及执行所述程序指令所需要的或者所产生的相关数据，所述收发器530用于在处理器510的控制下接收所述终端发送的身份验证请求以及身份验证信息，并且向目标终端发送验证信息；所述处理器510用于控制存储器550和收发器530的操作，根据所述身份验证请求获取目标用户标识，并根据所述验证信息对所述用户标识对应的用户进行身份验证。
处理器510控制服务器403的操作，处理器510还可以称为CPU(Central Processing Unit，中央处理单元)。存储器550可以包括只读存储器和随机存取存储器，并向处理器510提供指令和数据。存储器550的一部分还可以包括非易失性随机存取存储器(NVRAM)。具体的应用中服务器403的各个组件通过总线系统520耦合在一起，其中总线系统520除包括数据总线之外，还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见，在图中将各种总线都标为总线系统520。
上述本申请实施例揭示的方法可以应用于处理器510中，或者由处理器510实现。处理器510可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器510中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器510可以是通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器550，处理器510读取存储器550中的信息，结合其硬件完成 上述方法的步骤。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：只读存储器(ROM，Read Only Memory)、随机存取记忆体(RAM，Random Access Memory)、磁盘或光盘等。
以上对本申请实施例所提供的一种身份验证方法和装置进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (16)

  1. 一种身份验证方法，其特征在于，包括：
    接收终端发送的身份验证请求，所述身份验证请求携带用户的用户标识；
    根据所述身份验证请求获取目标用户标识，所述目标用户标识为所述用户的联系人的用户标识；
    根据目标用户标识向相应的目标终端发送验证信息，以便所述目标终端将所述验证信息提供给所述终端；
    接收所述终端发送的所述验证信息，并根据所述验证信息对所述用户标识对应的用户进行身份验证。
  2. 如权利要求1所述的身份验证方法，其特征在于，所述根据所述身份验证请求获取目标用户标识的步骤具体包括：
    根据所述身份验证请求获取所述用户标识对应的候选标识组，所述候选标识组包括至少一个联系人用户标识，所述联系人用户标识为所述用户的联系人的用户标识；
    从所述候选标识组中随机选取联系人用户标识作为目标用户标识。
  3. 如权利要求2所述的身份验证方法，其特征在于，所述根据所述身份验证请求获取所述用户标识对应的候选标识组的步骤具体包括：
    根据所述身份验证请求获取所述用户标识对应的至少一个联系人分组，其中，每个联系人分组包括至少一个所述联系人用户标识；
    从所述至少一个联系人分组中选取至少一个联系人用户标识，以得到所述候选标识组。
  4. 如权利要求3所述的身份验证方法，其特征在于，所述从所述至少一个联系人分组中选取至少一个联系人用户标识的步骤具体包括：
    获取所述每个联系人分组中联系人用户标识对应的联系人类型；
    根据所述联系人用户标识对应的联系人类型，从所述至少一个联系人分组中选取与预设联系人类型对应的联系人用户标识。
  5. 如权利要求2所述的身份验证方法，其特征在于，所述从所述候选标识组中随机选取联系人用户标识作为目标用户标识的步骤具体包括：
    获取所述用户对所述候选标识组中联系人用户标识设置的第一备注信息，以及所述联系人对所述用户标识设置的第二备注信息；
    根据所述第一备注信息和所述第二备注信息获取所述用户与所述联系人之间的社会关系；
    根据所述社会关系从所述候选标识组中随机选取联系人用户标识作为目标用户标识。
  6. 如权利要求5所述的身份验证方法，其特征在于，所述根据所述社会关系从所述候选标识组中随机选取联系人用户标识作为目标用户标识的步骤具体包括：
    根据所述联系人与所述用户之间的社会关系建立用户与联系人之间的社会关系图谱；
    从所述社会关系图谱中随机选取所述用户的目标联系人；
    从候选标识组中获取所述目标联系人对应的联系人用户标识，并将获取的联系人用户标识作为目标用户标识。
  7. 如权利要求1所述的身份验证方法，其特征在于，所述根据目标用户标识向相应的目标终端发送验证信息的步骤具体包括：
    获取所述目标用户标识对应的登录信息；
    根据所述登录信息确定所述目标用户标识是否已登录；
    当确定所述目标用户标识已登录时，向所述目标用户标识对应的目标终端发送验证信息。
  8. 如权利要求7所述的身份验证方法，其特征在于，所述根据目标用户标识向相应的目标终端发送验证信息的步骤还包括：
    当确定所述目标用户标识未登录时，获取与所述目标用户标识绑定的通讯标识；
    向所述通讯标识对应的目标终端发送验证信息。
  9. 一种身份验证装置，其特征在于，包括：
    请求接收单元，用于接收终端发送的身份验证请求，所述身份验证请求携带用户的用户标识；
    标识获取单元，用于根据所述身份验证请求获取目标用户标识，所述目标用户标识为所述用户的联系人的用户标识；
    信息发送单元，用于根据目标用户标识向相应的目标终端发送验证信息，以便所述目标终端将所述验证信息提供给所述终端；
    验证单元，用于接收所述终端发送的所述验证信息，并根据所述验证信息对所述用户标识对应的用户进行身份验证。
  10. 如权利要求9所述的身份验证装置，其特征在于，所述标识获取单元具体包括：
    标识组获取子单元，用于根据所述身份验证请求获取所述用户标识对应的候选标识组，所述候选标识组包括至少一个联系人用户标识，所述联系人用户标识为所述用户的联系人的用户标识；
    标识选取子单元，用于从所述候选标识组中随机选取联系人用户标识作为目标用户标识。
  11. 如权利要求10所述的身份验证装置，其特征在于，所述标识组获取子单元具体用于：
    根据所述身份验证请求获取所述用户标识对应的至少一个联系人分组，其中，每个联系人分组包括至少一个所述联系人用户标识；
    从所述至少一个联系人分组中选取至少一个联系人用户标识，以得到所述候选标识组。
  12. 如权利要求11所述的身份验证装置，其特征在于，所述标识组获取子单元，具体用于：
    根据所述身份验证请求获取所述用户标识对应的至少一个联系人分组，其中，每个联系人分组包括至少一个所述联系人用户标识；
    获取所述每个联系人分组中联系人用户标识对应的联系人类型；
    根据所述联系人用户标识对应的联系人类型，从所述至少一个联系人分组中选取与预设类型对应的联系人用户标识，以得到所述候选标识组。
  13. 如权利要求10所述的身份验证装置，其特征在于，所述标识选取子单元具体用于：
    获取所述用户对所述候选标识组中联系人用户标识设置的第一备注信息，以及所述联系人对所述用户标识设置的第二备注信息；
    根据所述第一备注信息和所述第二备注信息获取所述用户与所述联系人之间的社会关系；
    根据所述社会关系从所述候选标识组中随机选取联系人用户标识作为目标用户标识。
  14. 如权利要求13所述的身份验证装置，其特征在于，所述标识选取子单元具体用于：
    根据所述联系人与所述用户之间的社会关系建立用户与联系人之间的社会关系图谱；
    从所述社会关系图谱中随机选取所述用户的目标联系人；
    从候选标识组中获取所述目标联系人对应的联系人用户标识，并将获取的联系人用户标识作为目标用户标识。
  15. 如权利要求9所述的身份验证装置，其特征在于，所述信息发送单元具体用于：
    获取所述目标用户标识对应的登录信息；
    根据所述登录信息确定所述目标用户标识是否已登录；
    当确定所述目标用户标识已登录时，向所述目标用户标识对应的目标终端发送验证信息。
  16. 如权利要求15所述的身份验证装置，其特征在于，所述信息发送单元，还用于：
    当确定所述目标用户标识未登录时，获取与所述目标用户标识绑定的通讯标识；
    向所述通讯标识对应的目标终端发送验证信息。
PCT/CN2017/083015 2016-05-05 2017-05-04 身份验证方法和装置 WO2017190668A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610296640.0A CN107347054B (zh) 2016-05-05 2016-05-05 一种身份验证方法和装置
CN201610296640.0 2016-05-05

Publications (1)

Publication Number Publication Date
WO2017190668A1 true WO2017190668A1 (zh) 2017-11-09

Family

ID=60202794

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/083015 WO2017190668A1 (zh) 2016-05-05 2017-05-04 身份验证方法和装置

Country Status (2)

Country Link
CN (1) CN107347054B (zh)
WO (1) WO2017190668A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110401669A (zh) * 2019-07-31 2019-11-01 广州华多网络科技有限公司 一种身份校验方法及相关设备
CN110809001A (zh) * 2019-11-12 2020-02-18 北京三快在线科技有限公司 身份验证的方法、装置、设备及存储介质
CN111090801A (zh) * 2019-12-18 2020-05-01 创新奇智(青岛)科技有限公司 一种专家人脉关系图谱绘制方法及系统
CN114338581A (zh) * 2022-01-10 2022-04-12 土巴兔集团股份有限公司 多账号的通讯管理方法及相关装置
CN115022016A (zh) * 2022-05-31 2022-09-06 中国银行股份有限公司 基于区块链的用户身份认证方法及装置
CN116436633A (zh) * 2023-02-08 2023-07-14 广州希倍思智能科技有限公司 基于即时通讯进行验证码收发的平台登录方法及系统

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108429745B (zh) * 2018-03-05 2021-08-10 广州杰赛科技股份有限公司 登录的认证方法和认证系统、网页登录方法和系统
CN108718337B (zh) * 2018-05-22 2021-09-24 国政通科技股份有限公司 网站账号登录、验证、验证信息处理方法、装置及系统
CN109367988A (zh) * 2018-09-26 2019-02-22 陕西昱鑫科技发展有限责任公司 一种能够进行信息采集与认证的物证转运箱及其使用方法
CN110138851A (zh) * 2019-05-07 2019-08-16 甄十信息科技（上海）有限公司 智能穿戴设备的交友方法
CN111475843B (zh) * 2020-04-08 2023-03-14 腾讯科技（深圳）有限公司 一种数据处理方法和相关装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047503A (zh) * 2006-03-30 2007-10-03 腾讯科技（深圳）有限公司 一种密码取回的方法和系统
CN103179098A (zh) * 2011-12-23 2013-06-26 阿里巴巴集团控股有限公司 一种网络账号的密码找回方法和装置
CN103701683A (zh) * 2013-11-08 2014-04-02 金硕澳门离岸商业服务有限公司 获取好友的方法、装置和系统
CN105323219A (zh) * 2014-07-01 2016-02-10 腾讯科技（深圳）有限公司 验证用户帐号身份信息的方法及装置
CN105516133A (zh) * 2015-12-08 2016-04-20 腾讯科技（深圳）有限公司 用户身份的验证方法、服务器及客户端

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060153346A1 (en) * 2005-01-11 2006-07-13 Metro Enterprises, Inc. On-line authentication registration system
CN101572606B (zh) * 2009-06-12 2012-05-23 阿里巴巴集团控股有限公司 一种社会化网络中认证请求消息发送方法及装置
CN102111275B (zh) * 2011-04-01 2014-12-03 王冬梅 一种用户认证授权的方法及其实现系统
CN102231779A (zh) * 2011-07-13 2011-11-02 宇龙计算机通信科技(深圳)有限公司 信息获取方法、终端和服务器
CN103428069B (zh) * 2012-05-15 2015-07-01 腾讯科技（深圳）有限公司 社交网络中加好友的方法和装置
CN103701763B (zh) * 2012-09-27 2017-03-22 中国移动通信集团公司 用于验证用户侧设备的系统、方法和装置
CN104751032A (zh) * 2013-12-31 2015-07-01 腾讯科技（深圳）有限公司 身份验证方法及装置
CN104796310B (zh) * 2014-01-16 2019-07-05 腾讯科技（深圳）有限公司 社交通信方法和系统
CN104573081B (zh) * 2015-01-27 2017-11-03 南京烽火星空通信发展有限公司 一种基于sns的个人社会关系数据挖掘方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047503A (zh) * 2006-03-30 2007-10-03 腾讯科技（深圳）有限公司 一种密码取回的方法和系统
CN103179098A (zh) * 2011-12-23 2013-06-26 阿里巴巴集团控股有限公司 一种网络账号的密码找回方法和装置
CN103701683A (zh) * 2013-11-08 2014-04-02 金硕澳门离岸商业服务有限公司 获取好友的方法、装置和系统
CN105323219A (zh) * 2014-07-01 2016-02-10 腾讯科技（深圳）有限公司 验证用户帐号身份信息的方法及装置
CN105516133A (zh) * 2015-12-08 2016-04-20 腾讯科技（深圳）有限公司 用户身份的验证方法、服务器及客户端

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110401669A (zh) * 2019-07-31 2019-11-01 广州华多网络科技有限公司 一种身份校验方法及相关设备
CN110401669B (zh) * 2019-07-31 2021-06-11 广州方硅信息技术有限公司 一种身份校验方法及相关设备
CN110809001A (zh) * 2019-11-12 2020-02-18 北京三快在线科技有限公司 身份验证的方法、装置、设备及存储介质
CN110809001B (zh) * 2019-11-12 2022-05-10 北京三快在线科技有限公司 身份验证的方法、装置、设备及存储介质
CN111090801A (zh) * 2019-12-18 2020-05-01 创新奇智(青岛)科技有限公司 一种专家人脉关系图谱绘制方法及系统
CN111090801B (zh) * 2019-12-18 2023-06-09 创新奇智(青岛)科技有限公司 一种专家人脉关系图谱绘制方法及系统
CN114338581A (zh) * 2022-01-10 2022-04-12 土巴兔集团股份有限公司 多账号的通讯管理方法及相关装置
CN114338581B (zh) * 2022-01-10 2023-09-29 土巴兔集团股份有限公司 多账号的通讯管理方法及相关装置
CN115022016A (zh) * 2022-05-31 2022-09-06 中国银行股份有限公司 基于区块链的用户身份认证方法及装置
CN116436633A (zh) * 2023-02-08 2023-07-14 广州希倍思智能科技有限公司 基于即时通讯进行验证码收发的平台登录方法及系统
CN116436633B (zh) * 2023-02-08 2023-12-05 广州希倍思智能科技有限公司 基于即时通讯进行验证码收发的平台登录方法及系统

Also Published As

Publication number Publication date
CN107347054A (zh) 2017-11-14
CN107347054B (zh) 2021-08-03

Similar Documents

Publication Publication Date Title
WO2017190668A1 (zh) 身份验证方法和装置
US10554655B2 (en) Method and system for verifying an account operation
US9264418B1 (en) Client-side spam detection and prevention
US10223524B1 (en) Compromised authentication information clearing house
US10299118B1 (en) Authenticating a person for a third party without requiring input of a password by the person
JP2022169529A (ja) エフェメラルコンテンツメッセージを処理するための方法およびシステム
US9491155B1 (en) Account generation based on external credentials
US8594632B1 (en) Device to-device (D2D) discovery without authenticating through cloud
US9838384B1 (en) Password-based fraud detection
US9439072B2 (en) System and method for authentication
AU2016219712B2 (en) Method and devices for managing user accounts across multiple electronic devices
US20160321745A1 (en) Account binding processing method, apparatus and system
US20130318581A1 (en) Multi-factor authentication using a unique identification header (uidh)
TW201730806A (zh) 用於偵測網路釣魚之登入失敗序列
US9824207B1 (en) Authentication information update based on fraud detection
US20170149771A1 (en) Automated device discovery of pairing-eligible devices for authentication
CN101218626A (zh) 通过“我附近的人”来捕捉联系人
WO2018018697A1 (zh) 伪基站垃圾短信鉴别方法及系统
KR20200020946A (ko) 다중-에이전트 메시징을 위한 기술들
US10333915B2 (en) Customization of user account authentication
US20140372544A1 (en) System and Method for Establishing 2-Way Communications Between an App and a Browser
WO2017020551A1 (zh) 一种用于管理无线接入点的方法和设备
US20200036749A1 (en) Web browser incorporating social and community features
WO2022028198A1 (zh) 基于即时通讯的数据处理方法、装置、设备及介质
US10165126B2 (en) Method for securing a transaction between a mobile terminal and a server of a service provider through a platform

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17792494

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17792494

Country of ref document: EP

Kind code of ref document: A1