WO2023198208A1 - 一种验证信息发送方法、电子设备及介质 - Google Patents

一种验证信息发送方法、电子设备及介质 Download PDF

Info

Publication number
WO2023198208A1
WO2023198208A1 PCT/CN2023/088499 CN2023088499W WO2023198208A1 WO 2023198208 A1 WO2023198208 A1 WO 2023198208A1 CN 2023088499 W CN2023088499 W CN 2023088499W WO 2023198208 A1 WO2023198208 A1 WO 2023198208A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
user
verification information
trusted terminal
identification
Prior art date
Application number
PCT/CN2023/088499
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 WO2023198208A1 publication Critical patent/WO2023198208A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]

Definitions

  • the present application relates to the field of communication technology, and in particular to a verification information sending method, electronic device and medium.
  • the user logs in on the login interface 200 of the shopping application of the first electronic device 100 .
  • the server of the shopping application will generate the verification code information and send it to the corresponding terminal device.
  • the user can enter the verification code in the verification code input box 203 of the login interface 200 to perform identity authentication and log in.
  • the current way in which the application server sends verification code information is generally shown in Figure 2.
  • the application server first sends the verification code information to the operator's SMS network equipment, and the operator network SMS equipment sends the verification code information through the operator's communication network. Go to the terminal device where the mobile phone number reserved by the user or the mobile phone number entered by the user on the registration or login interface is located.
  • the above method of sending verification code information must rely on the operator's exclusive signaling channel, resulting in a high cost of sending verification codes.
  • the application server sends the verification code information by the application using Push technology.
  • the specific method is shown in Figure 3.
  • the application server sends the verification information to Push server.
  • the Push server sends verification information to the terminal device where the user is currently accessing the application through the long link Push channel established between the Push server and the terminal device.
  • the mechanism by which the Push server sends verification code information is to send the verification code information to the terminal used to access the application. Therefore, the above method cannot ensure that the user corresponding to the target number receives the verification code. That is, if the owner of the non-target number logs in with the target number on the terminal device, he or she can also receive the verification pushed by the Push server on the terminal device. code, resulting in low verification security and, to a certain extent, the problem of user information leakage.
  • embodiments of the present application provide a verification information sending method, electronic device, and medium.
  • embodiments of the present application provide a method for sending verification information, which is applied to electronic devices, including:
  • the preset correspondence relationship includes at least one user
  • the terminal equipment identification corresponding to the user identification in the corresponding relationship is used to identify the user's trusted terminal equipment
  • the first user identification mentioned in the embodiment of this application may be the user identification carried in the delivery request mentioned later.
  • the second user identification is a target user identification mentioned later that matches the user identification carried in the delivery request.
  • the preset correspondence relationship may refer to the mapping relationship between the user identification registered by the user and the corresponding trusted terminal device identification stored in the second electronic device later.
  • the terminal device identification may refer to the trusted terminal device identification mentioned later.
  • the above-mentioned electronic device may be the second electronic device mentioned below.
  • the electronic device can determine the stored target user identification that matches the user identification sent by the server of the application program based on the user identification sent by the server of the application program, and send the verification information sent by the server of the application program to the target user identification
  • the corresponding target trusted terminal device can effectively ensure user information security. Even if some users want to enter other people's accounts or mobile phone numbers to log in to other people's accounts, the electronic device will only send the verification information to the trusted terminal device corresponding to the other people's accounts or mobile phone numbers, rather than directly to the currently accessed application.
  • the program's equipment effectively protects the security of other people's accounts.
  • the target device identity is determined from the terminal device identity corresponding to the second user identity according to preset rules; including:
  • the trusted terminal device identification corresponding to the second user identification When it is determined that among the trusted terminal devices identified by the trusted terminal device identification corresponding to the second user identification, there is a trusted terminal device whose current connection state with the electronic device is the connected state, then the current connection state of the electronic device is The connected trusted terminal device serves as the target trusted terminal device;
  • the trusted terminal device that is connected to the second electronic device can be selected as the target trusted terminal device, and Send verification information to the target trusted terminal device. In this way, it can be further ensured that the terminal device receiving the verification information is the terminal device currently being used by the user, thereby improving verification efficiency.
  • the method further includes:
  • the trusted terminal device identification corresponding to the second user identification When it is determined that among the trusted terminal devices identified by the trusted terminal device identification corresponding to the second user identification, there is no trusted terminal device whose current connection status with the electronic device is the connected state, then after determining that the trusted terminal equipment corresponding to the second user identification If there is a trusted terminal device that is currently in an active state among the trusted terminal devices identified by the trusted terminal device identifier, the trusted terminal device that is currently in an active state is used as the target trusted terminal device.
  • the trusted terminal device serves as the target trusted terminal device and sends the verification information to the target trusted terminal device.
  • the terminal device receiving the verification information is the terminal device that the user uses normally or is currently using, rather than the terminal device that is in abnormal use such as being stopped or shut down, which can improve the verification efficiency.
  • the method further includes: determining that the current state of the trusted terminal device is an active state includes: when it is determined that the trusted terminal device currently has a running thread, then determining that the trusted terminal device The current status of the device is active.
  • determining that the status of the trusted terminal device is an active state may include determining that the status of the trusted terminal device is a state in normal use. This application is not limited to any method that can determine whether a trusted terminal device is active.
  • determining the target device identity from the terminal device identity corresponding to the second user identity according to preset rules further including:
  • the terminal equipment identification corresponding to the second user identification is used as the target device identification.
  • the terminal equipment identification can be directly used as the target trusted terminal equipment identification.
  • sending verification information to the target trusted terminal device identified by the target device identifier includes:
  • the verification information sending method uses a push channel to send verification information, which can greatly save costs compared to the method of sending verification information through an operator's exclusive signaling channel.
  • the verification information can be sent to any device that can connect to the Internet through the push channel, not just mobile phones, increasing the range of devices for which verification information is sent.
  • the user identification includes user account information, mobile phone number and email address.
  • the terminal device identification includes a terminal device identification number, a terminal device name, and terminal device routing information.
  • the verification information is generated by the application server, and the verification information is included in the verification information delivery request.
  • the verification information may be generated by the application server corresponding to the application program accessed by the user.
  • the delivery request sent by the application server to the second electronic device carries the verification information and the user identification.
  • Generating verification information through the application server can facilitate the storage of the verification information in the application server itself and facilitate comparison with the verification information input by the user.
  • the verification information is generated by the electronic device based on a request issued by the verification information
  • Methods also include:
  • the electronic device After the electronic device generates the verification information, it sends the verification information to the application server.
  • the server of the application program sends a delivery request to generate and deliver the verification information to the electronic device.
  • the electronic device After receiving the delivery request to generate and deliver the verification information, the electronic device generates the verification information.
  • the delivery request sent by the server corresponding to the application program to the electronic device carries the user ID but does not carry verification information.
  • the electronic device can send the verification information to the application server, so that the application server can verify the verification code entered by the last user.
  • the application server sends a verification information delivery request to the operator's network equipment.
  • the verification information can be sent through the operator's network equipment. To ensure that users can eventually receive verification information.
  • the method further includes: obtaining the time interval between the closest identity authentication time of the trusted terminal device identified by the terminal device identification stored in the electronic device and the current time;
  • the trusted terminal device identified by the terminal device identifier is in a state to be activated, where the server prohibits sending verification information to the terminal device in the state of being activated,
  • the second preset time is greater than the first preset time
  • the terminal device identification is logged out.
  • the security of the user information can be further improved to prevent the user from trusting the terminal device. When lost, the user's verification information will be leaked.
  • the electronic device determines that the time interval between the current moment of the trusted terminal device and the nearest identity authentication moment is greater than the second set time, it can be proved that the trusted terminal device has not been used for a long time or has not been authenticated for a long time. Certification. It can be inferred that there is a possibility of loss of the trusted terminal device. Therefore, the electronic device can log out the trusted terminal device to protect the security of user information.
  • the method further includes: when it is determined that the trusted terminal device identified by the terminal device identifier is in the to-be-activated state, sending the identity to the trusted terminal device identified by the terminal device identifier. Authentication prompt information.
  • the electronic device can set the trusted terminal device in the to-be-activated state to be unable to receive the verification information.
  • the electronic device may send identity authentication prompt information to the trusted terminal device in the pending activation state.
  • the identity authentication prompt information may also be sent to other trusted terminal devices corresponding to the user identification associated with the trusted terminal equipment identification corresponding to the trusted terminal equipment in the to-be-activated state. Among them, the identity authentication prompt information is used to remind the user to authenticate.
  • the identity authentication time includes the time when the terminal device performs unlocking authentication.
  • the method of determining the most recent identity authentication time of the trusted terminal device may be to determine the most recent time when the user performs PIN unlocking, pattern unlocking, fingerprint unlocking, or face unlocking on the trusted terminal device, or the most recent time when the user performs PIN unlocking, pattern unlocking, fingerprint unlocking, or face unlocking on the trusted terminal device.
  • inventions of the present application provide an electronic device.
  • the electronic device is a first electronic device.
  • the first electronic device includes:
  • the identity authentication module is used to send a registration request for the user ID and terminal device ID to the trusted terminal device registration module when it is determined that the user is an authorized registered user;
  • a trusted terminal device registration module configured to obtain the corresponding relationship between the user identification letter and the terminal device identification when receiving the registration request, and send the corresponding relationship between the user identification and the terminal device identification to the second electronic device ;
  • the first application module is configured to send a verification request to the application server in response to the user's operation, where the verification request includes the user identification.
  • the first electronic device further includes:
  • a message receiving module is used to receive verification information and control the first electronic device to display the verification information.
  • the message receiving module is configured to control the first electronic device to display the verification information after the user identity is verified.
  • the first electronic device can display the verification information after verifying the user's identity, which can further enhance the security of the user's information.
  • the first electronic device can use any authentication method such as fingerprint authentication, voiceprint authentication, face authentication, or iris authentication to verify the user's identity.
  • authentication method such as fingerprint authentication, voiceprint authentication, face authentication, or iris authentication to verify the user's identity.
  • inventions of the present application provide an electronic device.
  • the electronic device is a second electronic device.
  • the second electronic device includes:
  • the verification information receiving module is configured to receive the verification information delivery request sent by the application server, send the first user identification carried in the verification information delivery request to the device verification module, and send the verification information delivery request carried in the verification information delivery request. Verification information is sent to the message push module;
  • the device verification module is used to determine the second user identification that matches the first user identification in the stored preset correspondence relationship, and obtain the terminal device identification corresponding to the second user identification from the preset correspondence relationship; wherein, the preset correspondence relationship
  • the relationship includes a correspondence relationship between at least one user identifier and at least one terminal device identifier, and the terminal device identifier corresponding to the user identifier in the correspondence relationship is used to identify the user's trusted terminal device;
  • a device verification module configured to determine the target device identity from the terminal device identity corresponding to the second user identity according to preset rules, and send the target device identity to the message push module;
  • the message push module is used to send verification information to the target trusted terminal device identified by the target device identifier.
  • the second electronic device provided by the embodiment of the present application can determine the stored target user identification that matches the user identification sent by the server of the application based on the user identification sent by the server of the application, and send the user identification sent by the server of the application.
  • the verification information is sent to the target trusted terminal device corresponding to the target user ID, which can effectively ensure the user's information security. Even if some users want to enter other people's accounts or mobile phone numbers to log in to other people's accounts, the second electronic device will only send the verification information to the trusted terminal device corresponding to the other people's accounts or mobile phone numbers, rather than directly sending it to the current user. Devices that access the application effectively protect the security of other people's accounts.
  • embodiments of the present application provide an electronic device, including: a memory for storing instructions executed by one or more processors of the electronic device, and a processor that is one of the one or more processors of the electronic device. 1. Used to perform the above verification information sending method in the claims.
  • embodiments of the present application provide a computer-readable storage medium. Instructions are stored on the computer-readable storage medium. When the instructions are executed on an electronic device, they cause the electronic device to execute the above verification information sending method.
  • embodiments of the present application provide a computer program product, including instructions that, when the computer program product is run on a computer, cause the computer to execute the above verification information sending method.
  • Figure 1 shows a schematic diagram of a login interface of an electronic device according to some embodiments of the present application
  • Figure 2 shows a schematic diagram of sending verification code information according to some embodiments of the present application
  • Figure 3 shows a schematic diagram of sending verification code information according to some embodiments of the present application
  • Figures 4a-4c show a schematic diagram of the process of trusted device registration according to some embodiments of the present application.
  • Figure 5 shows a schematic diagram of a scenario for sending verification code information according to some embodiments of the present application
  • Figure 6a shows a schematic diagram of a first electronic device according to some embodiments of the present application.
  • Figure 6b shows a schematic diagram of an application server according to some embodiments of the present application.
  • Figure 6c shows a schematic diagram of a second electronic device according to some embodiments of the present application.
  • Figure 7 shows a schematic flow chart of sending verification information according to some embodiments of the present application.
  • Figures 8a-8c show a schematic diagram of the process of trusted device registration according to some embodiments of the present application.
  • Figures 9a-9b show a schematic diagram of the process of trusted device registration according to some embodiments of the present application.
  • Figure 10 shows a schematic diagram of a login interface of an electronic device according to some embodiments of the present application.
  • Figure 11 shows a schematic diagram of the notification center interface of an electronic device according to some embodiments of the present application.
  • Figure 12a shows a schematic diagram of the notification center interface of an electronic device according to some embodiments of the present application.
  • Figure 12b shows a schematic diagram of the notification center interface of an electronic device according to some embodiments of the present application.
  • Figure 13 shows a schematic flowchart of a device verification module of a second electronic device managing a user-registered trusted terminal device according to some embodiments of the present application.
  • Illustrative embodiments of the present application include, but are not limited to, a verification information sending method, electronic devices, and media.
  • Push technology an Internet-based information push technology, specifically refers to the technology of data transmission between the client and the server through the long link push channel established between the client and the server.
  • Push channel The long link push channel established between the client and the server. It can be established by the mobile phone brand manufacturer’s self-built push or the mobile phone application’s self-built push.
  • the server of the shopping application will generate the verification code information and send the verification code information to the second electronic device.
  • the electronic device will send the verification code information to the first electronic device 100 that accesses the shopping application.
  • user A After viewing the verification code information through the first electronic device 100, user A will enter the verification code in the verification code input box 203 to log in to user B's account. In this way, user B's account information is leaked.
  • the method includes: the user first registers the user identity and the identity of a trusted terminal device trusted by the user through the first electronic device.
  • the way for the user to register the user identity and the identity of the trusted terminal device trusted by the user through the first device may be that the user calls the device registration interface of the second electronic device to register through the first electronic device; or the user may register through the first electronic device.
  • the electronic device first obtains the user identification and the trusted terminal device identification trusted by the user, and then sends the obtained user identification and the trusted terminal device identification trusted by the user to the second electronic device.
  • the second electronic device stores the mapping relationship between the user identification registered by the user and the corresponding trusted terminal device identification.
  • the electronic device will send The verification request carrying the user identification is sent to the application server.
  • the application server can generate verification information corresponding to the verification request, and send the verification information delivery request to the second electronic device. It can be understood that the verification information is issued.
  • the delivery request may include user identification and verification information.
  • the second electronic device When the second electronic device receives the delivery request, it determines whether there is a target user identification that matches the user identification in the delivery request based on the mapping relationship between the pre-stored user identification and the corresponding trusted terminal device. If there is a target user identification that matches the user identification in the delivery request, obtain all trusted terminal device identities corresponding to the target user identifications stored in the second electronic device that match the user identification in the delivery request, The target trusted terminal device identification is determined from all trusted terminal device identifications according to the preset rules, and verification information is sent to the target trusted terminal device corresponding to the target trusted terminal device identification. After receiving the verification information, the target trusted terminal device displays the verification information.
  • the second electronic device determines that there is no target user identification that matches the user identification in the delivery request, it will determine that there is no target user identification that matches the user identification in the delivery request.
  • the result is sent to the application's server.
  • the application's server sends the verification information to the operator's network equipment.
  • the operator's network equipment calls the operator's exclusive signaling channel to send the verification code information in the form of SMS to the user ID in the verification request.
  • the terminal device where the mobile phone number carried in is located.
  • the above-mentioned user identification may be the user's mobile phone number, email address, and third-party service account information such as WeChat TM account, QQ TM account, etc.;
  • the above-mentioned trusted terminal device identification may be a trusted terminal
  • the above verification information can be generated by the server corresponding to the application program accessed by the user.
  • the delivery request sent by the server corresponding to the application program to the second electronic device carries the verification information. and user ID.
  • Generating verification information through the application server can facilitate the storage of the verification information in the application server itself and facilitate comparison with the verification information input by the user.
  • the above-mentioned verification information may be generated by the second electronic device, that is, after receiving the verification request, the server of the application sends a delivery request to generate and deliver the verification information to the second electronic device, and the second electronic device After receiving the request to generate and deliver verification information, the device generates verification information.
  • the delivery request sent by the server corresponding to the application program to the second electronic device carries the user identification but does not carry the verification information.
  • the second electronic device can send the verification information to the application
  • the program server facilitates the application server to verify the verification code entered by the last user.
  • any number of user identifications and any number of trusted terminal device identifications corresponding to any number of user identifications can be stored in the second electronic device.
  • Each user identification may correspond to one trusted terminal device identification or may correspond to multiple trusted terminal device identifications.
  • the above-mentioned method of determining the target trusted terminal device identification from all trusted terminal device identifications according to preset rules may include:
  • the trusted terminal device connected to the second electronic device shall be the trusted terminal device connected to the second electronic device as the target trusted terminal device, and the trusted terminal device identification corresponding to the target trusted terminal device shall be used as the target trusted terminal device. Terminal device identification.
  • connection status of the trusted terminal device corresponding to the target user ID and the second electronic device is not connected, it is further determined whether there is a terminal device in the current active state in the trusted terminal device corresponding to the target user ID. If there is, Then the trusted terminal device in the active state is used as the target trusted terminal device. If it does not exist, all trusted terminal devices corresponding to the live target user identification are used as target trusted terminal devices, and the trusted terminal device identification corresponding to the target trusted terminal device is used as the target trusted terminal device identification.
  • the way to determine whether the trusted terminal device corresponding to the target user ID is in an active state may be to determine whether the trusted terminal device corresponding to the target user ID has a running thread. If so, determine that the current status of the trusted terminal device is Active state; if not, it is determined that the current state of the trusted terminal device is the active state.
  • the second electronic device can obtain whether the trusted terminal device corresponding to the target user ID has a running thread by sending a status acquisition request to all trusted terminal devices corresponding to the target user ID.
  • the trusted terminal device identifier can be directly used as the target trusted terminal device identifier.
  • the way in which the second electronic device sends the verification information to the corresponding target trusted terminal device is: after the second electronic device obtains the target trusted terminal device identification, it uses the device routing information in the target trusted terminal device identification. , establish a push channel with the corresponding target trusted terminal device, and send the verification information to the corresponding target trusted terminal device through the push channel.
  • the second electronic device after sending the verification information to the target trusted terminal device through the push channel, can send the verification message sent prompt information to the server of the application program, and the server of the application program can Control the interface corresponding to the verification code generation task, such as the login interface, registration interface or payment interface of the application, etc. to display the verification message has been sent prompt message.
  • the verification message has been sent prompt information may include the target trusted terminal device identification (such as device identification information, device name information, etc.).
  • the verification message has been sent prompt information may be used to prompt the user that the verification message has been sent to the target trusted terminal device. It also prompts the user for the trusted terminal device identification, making it easier for the user to find the corresponding trusted terminal device based on the device information to view the verification information.
  • the above verification message has been sent prompt message can be "Verification information has been sent to HUAWEI MATE40".
  • the target trusted terminal device can display the verification information after verifying the user's identity. It is feasible that the target trusted terminal device can use any authentication method such as fingerprint authentication, voiceprint authentication, face authentication, iris authentication, etc. to verify the user's identity. In some embodiments, after confirming that the environment is safe, the target trusted terminal device can also perform a voice broadcast of the verification information.
  • the above-mentioned application program can be any application program such as a shopping application program, a video entertainment application program, an office application program, etc., and can also be implemented as some web page applications.
  • the second electronic device can determine the target user identification stored in the second electronic device that matches the user identification sent by the server of the application program based on the user identification sent by the server of the application program, and send the user identification sent by the server of the application program.
  • the verification information is sent to the trusted terminal device corresponding to the target user ID, effectively ensuring the user's information security. That is, if some users want to enter other people’s accounts When logging in to another person's account or mobile phone number, the second electronic device will only send the verification information to the trusted terminal device corresponding to the other person's account or mobile phone number, rather than directly to the device currently accessing the application, effectively protecting others. Account security.
  • the trusted terminal device that is in a connected state or an active state with the second electronic device can be selected as the target trusted terminal device, and the verification is performed.
  • the information is sent to the target trusted terminal device. In this way, it can be further ensured that the terminal device receiving the verification information is the terminal device currently being used by the user, thereby improving verification efficiency.
  • the verification information sending method uses a push channel to send verification information, which can greatly save costs compared to the method of sending verification information through an operator's exclusive signaling channel.
  • the verification information can be sent to any device that can connect to the Internet through the push channel, not just mobile phones, increasing the range of devices for which verification information is sent.
  • the verification information sending method provided by the embodiment of the present application can be used in any scenario where verification information needs to be sent.
  • the following describes the verification information sending method in the embodiment of the present application using a scenario where user A registers a trusted terminal device and logs in to an account in application B.
  • FIG. 4a shows a schematic diagram of the device registration interface 402 of the second electronic device 300.
  • User A can register the user's mobile phone number, email and other user identifications in the device registration interface 402, and can also register the device identification number, device IP and device name. and other device identification.
  • the second electronic device 300 can correspondingly store the user identification registered by user A and the trusted terminal device identification.
  • user A accesses application B through the first electronic device 100 .
  • user A logs in on the login interface 200 of application B of the first electronic device 100 .
  • the first electronic device 100 will send a verification request to the application server 500 corresponding to application B.
  • the application server 500 responds to the verification request, generates corresponding verification information and sends the verification information and user A's mobile phone number "12345678901" for account login to the second electronic device 300 .
  • the verification information generated by the server of application B can be "Hello, you are logging in, and your verification code is 667788.”
  • the second electronic device 300 determines the target user identification that matches the mobile phone number of the user A based on the mobile phone number of the user A.
  • the target user identification stored in the second electronic device 300 that matches the mobile phone number of the user A is the mobile phone number " 123456789” and the email number "12345@qq.com", and it was determined that the identities of the trusted terminal devices associated with this user identity are only the device identification number "abc01"; the device IP "192.168.1.201"; and the device name "HUAWEI".
  • the second electronic device 300 will establish a push channel with the trusted terminal device based on the device IP "192.168.1.201" in the trusted terminal device identification, and send the verification information "Hello, you are logging in, your verification code is 667788” ” is sent to the trusted terminal device 001 with the device identification number “abc01” through the push channel.
  • the message notification center interface 404 of the trusted terminal device 001 can display verification information "Hello, you are logging in, and your verification code is 667788.”
  • the application server 500 will generate the verification code information and send the verification code information and the user B's mobile phone number is sent to the second electronic device 300.
  • the second electronic device 300 determines the trusted terminal device associated with user B's mobile phone number based on user B's mobile phone number, and sends the verification code information to user B's mobile phone number. Associated trusted end devices. In this way, user A will not be able to check user B's verification information, and will not be able to log in to user B's account. Effectively ensure the security of user B’s account.
  • the structures of the first electronic device 100, the application server 500 and the second electronic device 300 provided by the embodiment of the present application are first briefly introduced.
  • the first electronic device 100 can be any terminal electronic device such as a computer, a tablet, or a mobile phone. As shown in Figure 6a, the first electronic device 100 may include:
  • the identity authentication module 101 is used to determine whether the user is an authorized registered user.
  • the identity authentication module 101 determines that the user is an authorized registered user by: obtaining the user's identity authentication information, and when detecting that the user's identity authentication information is passed, determines that the user is an authorized user. When it is detected that the user identity authentication information fails, the user is determined to be an unauthorized user.
  • the first electronic device 100 can be provided with a device account login interface.
  • the user can log in with account and password and other identity authentication logins on the device account login interface.
  • the identity authentication module 101 can obtain the account number entered by the user on the device account login interface. Password or obtain other identity authentication information of the user.
  • the identity authentication module 101 is also configured to send a device registration request to the trusted terminal device registration module 102 after detecting that the user identity authentication has passed, that is, after determining that the user is an authorized registered user.
  • the user can log in to the device account on the device account login interface 400 of the first electronic device 100 shown in FIG. 4a.
  • the identity authentication module 101 can obtain the account password entered by the user on the device account login interface 400.
  • the user can also log in to the user device account through any authentication method such as fingerprint authentication, voiceprint authentication, face authentication, iris authentication, etc.
  • the identity authentication module 101 can obtain identity information such as user fingerprint information, voiceprint information, face information, and iris information.
  • the identity authentication module 101 detects that the user identity authentication is passed, that is, the device account login is successful, and when it detects that the user performs operations such as clicking on the "Trusted Terminal Device Registration" control, it sends a device registration request to the trusted terminal device registration module 102 .
  • the trusted terminal device registration module 102 is configured to call the device registration interface of the second electronic device 300 in response to the trusted terminal device registration request sent by the user identity authentication module 101 .
  • the trusted terminal device registration module 102 may be used to obtain a user identification and a trusted terminal device identification associated with the user identification. and sends the user identification and the trusted terminal device identification associated with the user identification to the second electronic device 300 .
  • the first application module 103 is configured to send a verification request to the application server 500 in response to the user's operation of clicking to obtain the verification code control or other operations that trigger the electronic device to generate a verification request. Among them, the user ID is included in the verification request.
  • the message receiving module 104 is configured to establish a push channel with the second electronic device 300 , receive verification information sent by the second electronic device 300 , and control the verification information to be displayed in the message notification center of the first electronic device 100 .
  • application server 500 may include:
  • the second application module 501 is configured to receive the verification request sent by the first application module 103 of the first electronic device 100, and send the verification request to the verification information generation module 502.
  • the verification information generation module 502 is configured to generate verification information according to the verification request, and send a verification information delivery request to the verification information receiving module 301 of the second electronic device 300 .
  • the verification information delivery request includes the user ID and verification information.
  • the second electronic device 300 may be a cloud server, a base station device, a server or a local area network mounted on the first electronic device 100, or the like. As shown in Figure 6c, the second electronic device 300 may include:
  • the verification information receiving module 301 is configured to receive a verification information delivery request sent by the verification information generation module 502 of the application server 500.
  • the verification information delivery request includes the user identification and verification information. and used to send the user identification to the device verification module 302. It is also used to send the verification information and the target trusted terminal device identification to the message push module 303.
  • the device verification module 302 is configured to determine, based on the user identification sent by the verification information receiving module 301, the target user identification stored in the second electronic device 300 that matches the user identification sent by the verification information receiving module 301, and obtain the corresponding target user identification. All trusted terminal device identifiers. It is also used to determine the target trusted terminal device identification from all trusted terminal device identifications corresponding to the target user identification according to the preset rules. It is also used to send the device routing information in the target trusted terminal device identification to the message push module 303 of the second electronic device 300 .
  • the message push module 303 establishes a secure push channel with the target trusted terminal device based on the device routing information corresponding to the target trusted terminal device, and sends the verification information to the target trusted terminal device through the push channel.
  • FIGS. 6a-6c show a schematic interaction flow diagram of a verification information sending method according to an embodiment of the present application.
  • the verification information sending method shown in Figure 7 specifically includes a registration stage of a trusted terminal device and a generation and sending stage of verification information.
  • 701-705 in Figure 7 show the registration process of the trusted terminal device, and 706-718 show the generation and sending process of the verification information. Details are as follows:
  • the identity authentication module 101 of the first electronic device 100 determines that the user is an authorized registered user.
  • the identity authentication module 101 determines that the user is an authorized registered user by: obtaining the user's identity authentication information, and when detecting that the user's identity authentication information is passed, determines that the user is an authorized user. When it is detected that the user identity authentication information fails, the user is determined to be an unauthorized user.
  • the first electronic device 100 can be provided with a device account login interface.
  • the user can log in with account and password and other identity authentication logins on the device account login interface.
  • the identity authentication module 101 can obtain the account number entered by the user on the device account login interface. Password or obtain other identity authentication information of the user.
  • the user can log in to the device account on the device account login interface 400 of the first electronic device 100 shown in FIG. 4a.
  • the identity authentication module 101 can obtain the account password entered by the user on the device account login interface 400.
  • the user can also log in to the user device account through any authentication method such as fingerprint authentication, voiceprint authentication, face authentication, iris authentication, etc.
  • the identity authentication module 101 can obtain identity information such as user fingerprint information, voiceprint information, face information, and iris information.
  • the identity authentication module 101 detects that the user identity authentication is passed, that is, the device account login is successful, it is determined that the user is an authorized registered user.
  • a control for triggering the sending of a device registration request such as a "trusted device registration" control 4011, may be provided in the account center interface 401 shown in Figure 4b.
  • the identity authentication module 101 detects that the user identity authentication has passed, that is, it determines that the user is an authorized registered user, and can only send a trusted terminal device registration request to Trusted terminal device registration module 102.
  • the control used to trigger the sending of the device registration request can also be set in the settings interface and other interfaces that can be viewed without identity authentication. That is, the user can first click the control that triggers the sending of the device registration request and then trigger the identity authentication.
  • the setting interface 405 of the first electronic device 100 is provided with a "Trusted Device Registration" control 4011.
  • the user clicks the "Trusted Device Registration” control 4011 it will be displayed as shown in Figure 8b Identity authentication page 406.
  • the user can perform device account login verification on the identity authentication page 406.
  • the identity authentication page 406 may also use other identity authentication, such as face recognition authentication, etc.
  • the identity authentication module 101 can obtain the identity verification information input by the user on the identity authentication page 406 . When it is detected that the user identity verification information has passed, a device registration request is initiated to the trusted terminal device registration module 102.
  • the identity authentication module 101 of the first electronic device 100 sends a device registration request to the trusted terminal device registration module 102.
  • a control for triggering the sending of a device registration request such as a "trusted terminal device registration” control
  • a control for triggering the sending of a device registration request can be set in the account center interface shown in Figure 4b.
  • the identity authentication module 101 detects that the user identity authentication has passed and determines that the user is authorized to register.
  • the user can send a trusted terminal device registration request to the trusted terminal device registration module 102 only when it is obtained that the user performs an operation of clicking the "Trusted Device Registration" control 4011.
  • control used to trigger the sending of the device registration request can also be set in the settings interface and other interfaces that can be viewed without identity authentication. That is, the user can first click the control that triggers the sending of the device registration request and then trigger the identity authentication.
  • a "trusted terminal device registration" control 4011 is provided on the setting interface 404 of the first electronic device 100.
  • the identity authentication module 101 detects that the user identity verification information has passed, it directly initiates a device registration request to the trusted terminal device registration module 102.
  • the identity authentication module can directly obtain all the identity authentication information when the user unlocks the first electronic device.
  • the identity authentication module 101 confirms that the user is an authorized user.
  • the identity authentication module 101 detects that the control used to trigger the sending of the device registration request is clicked, such as the "Trusted Terminal Device" of the setting interface 404 shown in Figure 8a After "Register” control 4011, the identity authentication module directly initiates a device registration request to the trusted terminal device registration module 102.
  • the trusted terminal device registration module 102 of the first electronic device 100 obtains the user identification and the trusted terminal device identification associated with the user identification.
  • the trusted terminal device registration module 102 when the trusted terminal device registration module 102 obtains the user's registration request, the device registration page can be directly displayed, and the user can register the user identity and the corresponding trusted terminal device identity on the registration page. After the user registration is completed, the user's registered user identification and the trusted terminal device identification associated with the user identification may be sent to the device verification module 302 of the second electronic device 300 .
  • the trusted terminal device registration module 102 when the trusted terminal device registration module 102 obtains the user's registration request, the trusted terminal device registration module 102 can directly call the device registration interface of the device verification module 302 of the second electronic device 300 , that is, the user can register the user identity and the corresponding trusted terminal device identity in the device registration interface.
  • User identification may include mobile phone number, email address and third-party service account such as WeChat TM account, QQ TM account and other identification information representing the user's identity.
  • the trusted terminal device identification may be the device identification number, device name and device routing information of the trusted terminal device, where the device routing information may include the IP address or MAC address of the device.
  • users can register one or more trusted terminal device identities.
  • the user can register the user identity and the device identity in the device registration interface, that is, the device registration interface interface 402 .
  • the user registered the mobile phone number "12345678901" in the device registration interface interface 402; the email address
  • the user can also use manual dragging to register the trusted terminal device identity.
  • a device registration box 4022 is provided, and a local device icon and a device icon associated with the local device can be displayed.
  • Figure 9a shows a local device icon 601, a computer device icon 602 associated with the local device, and a tablet device icon 603.
  • the user can register the trusted terminal device identity by dragging the device icon.
  • the user drags the computer device icon 602 into the device registration box 4022.
  • a device identification box 604 may be displayed, and the device identification box may display a device identification such as the name or identification number of the dragged device to facilitate the user to identify the device.
  • the identification number "abc02" of the computer device corresponding to the computer device icon 602 may be displayed in the device identification box.
  • the second electronic device 300 can directly obtain the device identifier corresponding to the device icon.
  • the computer device icon 602 corresponds to computer equipment
  • the device identification number is "abc02"
  • the device IP is "192.168.1.202”
  • the device name is "HUAWEI2”.
  • the device icon may be generated by the second electronic device 300 based on the device identification of the first electronic device 100 obtained from the first electronic device 100 or the device identification of a device associated with the first electronic device 100 .
  • the trusted terminal device registration module 102 of the first electronic device 100 sends the user identification and the trusted terminal device identification associated with the user identification to the device verification module 302 of the second electronic device 300.
  • the device verification module 302 of the second electronic device 300 stores the user identification and the trusted terminal device identification associated with the user identification.
  • the storage method between the user identification and the trusted terminal devices associated with the user identification can be in the form of building an index table.
  • the first application module 103 of the first electronic device 100 sends a verification request to the second application module 501 of the application server 500.
  • the first electronic device 100 When the user accesses the application through the first electronic device 100 and performs the operation of clicking on the verification code control or other operations that trigger the electronic device to generate a verification request in scenarios such as account registration, account login or payment, the first electronic device The first application module 103 of 100 will send a verification request to the second application module 501 of the application server 500 .
  • user A accesses application B through the first electronic device 100 .
  • user A logs in on the login interface 200 of application B of the first electronic device 100 .
  • the first application module 103 of the first electronic device 100 will send a request to the application server 500 corresponding to application B.
  • the second application module 501 sends a verification request.
  • the verification request carries the user ID.
  • the user identification can be the user's mobile phone number, email address and third-party service account such as WeChat TM account, QQ TM account and other account information.
  • the user identification carried in the verification request may be the mobile phone number used by the user to log in to the first electronic device 100 or the email address carried by the user when registering an account for the application, etc.
  • the second application module 501 of the application server 500 sends the verification request to the verification information generation module 502.
  • the verification information generation module 502 of the application server 500 generates verification information according to the verification request.
  • the verification information generation module 502 of the application server 500 generates corresponding verification information according to the verification request.
  • the verification information may include verification codes and prompt information such as prompts that the user is logging in, registering, etc.
  • the verification information can be: "Hello, you are logging in, and your verification code is 667788.”
  • the verification information generating module 502 of the application server 500 sends the verification information delivery request to the verification information receiving module 301 of the second electronic device 300 .
  • the application server 500 will send a verification information delivery request to the verification information receiving module 301 of the second electronic device 300 .
  • the verification information delivery request may include a verification information delivery instruction, verification information, and user identification.
  • the verification information receiving module 301 of the second electronic device 300 sends the user ID carried in the verification information delivery request to the device verification module 302.
  • the device verification module 302 of the second electronic device 300 determines, based on the received user identification, whether the device verification module 302 stores a target user identification that matches the received user identification.
  • the device verification module 302 sends the result that there is no trusted terminal device to the verification information generation module 502 of the application server 500.
  • the device verification module 302 when the device verification module 302 obtains the user ID as "12345678901", it can query all user IDs stored in the device verification module 302 that match the mobile phone number "12345678901".
  • the queried user identification matching the mobile phone number "12345678901" may include a consistent mobile phone number stored in the second electronic device 300
  • the device verification module 302 of the second electronic device 300 obtains the trusted terminal device identification corresponding to the target user identification.
  • the device verification module 302 can determine the corresponding trusted terminal device identity based on the user identity that matches the user identity in the verification information delivery request.
  • the device verification module 302 determines the trusted terminal device associated with the target user ID based on the mobile phone number "123456789” and the email number "12345@qq.com” in the target user ID.
  • the identification includes the device identification number "abc01”; the device IP "192.168.1.201”; and the device name "HUAWEI”.
  • the device verification module 302 of the second electronic device 300 determines the target trusted terminal device identification from the trusted terminal equipment identification corresponding to the target user identification according to the preset rules.
  • the method of determining the target trusted terminal device identification from all trusted terminal equipment identifications corresponding to the target user identification according to the preset rules may include:
  • connection status of the trusted terminal device corresponding to the target user ID and the second electronic device 300 is not connected, it is further determined whether there is a terminal device in the current active state in the trusted terminal device corresponding to the target user ID. If there is , then the trusted terminal device in the active state is used as the target trusted terminal device. If it does not exist, all trusted terminal devices corresponding to the target user identification are used as the target trusted terminal equipment, and the trusted terminal equipment identification corresponding to the target trusted terminal equipment is used as the target trusted terminal equipment identification.
  • the way to determine whether the trusted terminal device corresponding to the target user ID is in an active state may be to determine whether the trusted terminal device corresponding to the target user ID has a running thread. If so, determine that the current status of the trusted terminal device is Active state; if not, it is determined that the current state of the trusted terminal device is the active state.
  • the second electronic device 300 may obtain whether the trusted terminal device corresponding to the target user ID has a running thread by sending a status acquisition request to all trusted terminal devices corresponding to the target user ID.
  • the trusted terminal device ID can be directly used as the target trusted terminal device ID.
  • the device verification module 302 of the second electronic device 300 sends the target trusted terminal device identification to the verification information receiving module 301.
  • the verification information receiving module 301 of the second electronic device 300 sends the verification information and the target trusted terminal device identification to the message push module 303.
  • the message push module 303 of the second electronic device 300 pushes the verification information to the message receiving module 801 of the target trusted terminal device 800 corresponding to the target trusted terminal device identification.
  • the structure of the target trusted terminal device may be the same as the structure of the first electronic device.
  • the verification information receiving module 301 of the second electronic device 300 obtains the corresponding target trusted terminal device identification, it communicates with the corresponding target trusted terminal device 800 through the device routing information in the corresponding target trusted terminal device identification. Establish a push channel between The verification information is sent to the corresponding target trusted terminal device 800 through the push channel.
  • the verification information can be displayed through the message notification center.
  • the second electronic device 300 may send the verification message sent prompt information to the interface of the application program.
  • the verification message has been sent prompt information may include the device identification information of the target trusted terminal device 800.
  • the verification message has been sent prompt information may be used to remind the user that the verification message has been sent to the target trusted terminal device 800, and to prompt the user that the verification message has been sent to the target trusted terminal device 800.
  • the device identification of the device 800 facilitates the user to find the corresponding target trusted terminal device 800 according to the device information to view the verification information.
  • the device account login interface 200 of the first electronic device 100 may display the verification message sent prompt message “Verification information has been sent to HUAWEI”.
  • the message receiving module 801 of the target trusted terminal device 800 controls the target terminal device 800 to display the verification information.
  • the message receiving module 801 of the target trusted terminal device 800 can directly control the message notification center to display the verification information.
  • the verification information "Hello, you are logging in, your verification code is 667788" can be directly displayed on the message notification center interface 404 of the target trusted terminal device 800.
  • the target trusted terminal device 800 may display the verification information after verifying the user's identity.
  • the target trusted terminal device 800 may use any authentication method such as fingerprint authentication, voiceprint authentication, face authentication, or iris authentication to verify the user's identity.
  • the message notification center interface of the target trusted terminal device 800 can display prompts such as "You have received a verification message”.
  • identity authentication such as face verification
  • the message notification center interface 404 displays the verification information "Hello, you are logging in, and your verification code is 667788.”
  • the target trusted terminal device 800 may also perform a voice broadcast of the verification information.
  • the way for the target trusted terminal device 800 to confirm the security of the environment can be:
  • the target trusted terminal device 800 may send an environment security identification request to a third device with a camera function that is within a certain distance from the target trusted terminal device 800 and is connected to the target trusted terminal device 800 .
  • the third electronic device receives the environment security identification request and turns on the camera function to obtain the environment image, and sends the environment image to the target trusted terminal device 800 .
  • the target trusted terminal device 800 determines that the portrait in the environment image is only a user image or a trusted image, it confirms that the surrounding environment is a safe environment.
  • the target trusted terminal device 800 may perform voice broadcast on the verification information by sending the verification information to a device that is within a certain distance from the target trusted terminal device 800 and has a voice broadcast function that establishes a connection with the target trusted terminal device 800 Electronic devices such as speakers broadcast verification information.
  • the target terminal device controls the loudspeaker of the target terminal device to perform voice broadcast.
  • the above-mentioned trusted image may be a trusted image pre-registered by the user in the target trusted terminal device 800 .
  • it may be an image of the user's family or an image of the user's housing environment, for example, a picture of the user's room.
  • the environment image includes unrecognizable face images or other portraits, for example, the environment image includes unrecognizable side faces or portrait backs, then it is judged that there may be strangers in the environment. At this time, it is determined that the surrounding environment is illegal. In a safe environment, verification information is not broadcast.
  • the user works in a room at home.
  • the target trusted terminal device 800 After the target trusted terminal device 800 receives the verification information, it can send an environment security identification request to a device that is within a set distance range from the target trusted terminal device 800 and is connected to the target trusted terminal device 800 .
  • Photography of the room where device 800 establishes connection The camera device turns on the camera function to obtain the environment image and send it to the target trusted terminal device 800 .
  • the target trusted terminal device 800 determines that the environment image matches the user room image registered in the target trusted terminal device 800, the verification information is broadcast.
  • the user can obtain the verification information without checking it on the target trusted terminal device 800, thereby improving the user experience.
  • the device verification module 302 sends the result that there is no trusted terminal device to the verification code generation module of the application server 500.
  • the device verification module 302 queries the trusted terminal device according to the received user identification, there may be a situation where there is no corresponding trusted terminal device.
  • the device verification module 302 sends the result that there is no trusted terminal device to the verification code generation module of the application server 500, which can facilitate the application server 500 to re-send the verification information delivery request to the operator's network equipment.
  • the verification information code generation module of the application server 500 sends the verification information delivery request to the operator's network equipment.
  • the verification information delivery request may include verification information and a user identification, and the user identification may include a mobile phone number reserved by the user or a mobile phone number entered by the user on the registration or login interface.
  • the operator's network equipment After receiving the delivery request, the operator's network equipment sends the verification information through the operator's communication network to the mobile phone number reserved by the user in the user ID or the terminal device where the mobile phone number entered by the user on the registration or login interface is located.
  • the verification information can be sent through the operator's network equipment. To ensure that users can eventually receive verification information.
  • the scenarios for sending verification codes mentioned above are all introduced by taking the user's account login or registration interface in the application to trigger verification as an example.
  • the scenario in which the verification code is sent in this application can also be any scenario that can trigger verification, such as user payment, user transfer, etc.
  • the second electronic device can determine the target user identification stored in the second electronic device that matches the user identification sent by the server of the application program based on the user identification sent by the server of the application program, and send the user identification sent by the server of the application program.
  • the verification information is sent to the trusted terminal device corresponding to the target user ID, effectively ensuring the user's information security. Even if some users want to enter other people's accounts or mobile phone numbers to log in to other people's accounts, the second electronic device will only send the verification information to the trusted terminal device corresponding to the other people's accounts or mobile phone numbers, rather than directly sending it to the current user. Devices that access the application effectively protect the security of other people's accounts.
  • the trusted terminal device that is in a connected state or an active state with the second electronic device can be selected as the target trusted terminal device, and the verification is performed.
  • the information is sent to the target trusted terminal device. In this way, it can be further ensured that the terminal device receiving the verification information is the terminal device currently being used by the user, thereby improving verification efficiency.
  • the verification information sending method uses a push channel to send verification information, which can greatly save costs compared to the method of sending verification information through an operator's exclusive signaling channel.
  • the verification information can be sent to any device that can connect to the Internet through the push channel, not just mobile phones, increasing the range of devices for which verification information is sent.
  • the verification information sending method provided by the embodiment of the present application also includes managing the trusted terminal device.
  • FIG. 13 shows a schematic flowchart of the device verification module 302 of the second electronic device 300 managing the trusted terminal device registered by the user in the embodiment of the present application.
  • the specific manner in which the device verification module 302 of the second electronic device 300 manages the trusted terminal device registered by the user specifically includes:
  • the method of determining the most recent identity authentication time of the trusted terminal device may be to determine the most recent time when the user performed PIN unlocking, pattern unlocking, fingerprint unlocking, or face unlocking on the trusted terminal device, or the most recent time when the user performed the PIN unlock, pattern unlock, fingerprint unlock, or face unlock on the trusted terminal device. The time to log in to the device account of the trusted terminal device.
  • the first set time is longer than the second set time.
  • the first set time and the second set time can be determined according to actual needs.
  • the first set time may be three days, and the second set time may be one week.
  • the second electronic device 300 determines that the time interval between the current time of the trusted terminal device and the nearest identity authentication time is greater than the second set time, it can be proved that the trusted terminal device has not been used for a long time or has not been used for a long time. Not authenticated. It can be inferred that there is a possibility of loss of the trusted terminal device. Therefore, the second electronic device 300 can log out of the trusted terminal device to protect the security of user information.
  • the second electronic device 300 may set the trusted terminal device in the to-be-activated state to be unable to receive the verification information. However, when the second electronic device 300 determines that the current state of the trusted terminal device is the pending activation state, the second electronic device 300 may send the identity authentication prompt information to the trusted terminal device in the pending activation state.
  • the identity authentication prompt information may also be sent to other trusted terminal devices corresponding to the user identification associated with the trusted terminal equipment identification corresponding to the trusted terminal equipment in the to-be-activated state. Among them, the identity authentication prompt information is used to remind the user to authenticate.
  • the second electronic device can determine the target user identification stored in the second electronic device that matches the user identification sent by the server of the application program based on the user identification sent by the server of the application program, and send the user identification sent by the server of the application program.
  • the verification information is sent to the trusted terminal device corresponding to the target user ID, effectively ensuring the user's information security. Even if some users want to enter other people's accounts or mobile phone numbers to log in to other people's accounts, the second electronic device will only send the verification information to the trusted terminal device corresponding to the other people's accounts or mobile phone numbers, rather than directly sending it to the current user. Devices that access the application effectively protect the security of other people's accounts.
  • the trusted terminal device that is in a connected state or an active state with the second electronic device can be selected as the target trusted terminal device, and the verification is performed.
  • the information is sent to the target trusted terminal device. In this way, it can be further ensured that the terminal device receiving the verification information is the terminal device currently being used by the user, thereby improving verification efficiency.
  • the verification information sending method uses a push channel to send verification information, which can greatly save costs compared to the method of sending verification information through an operator's exclusive signaling channel.
  • the verification information can be sent to any device that can connect to the Internet through the push channel, not just mobile phones, increasing the range of devices for which verification information is sent.
  • An embodiment of the present application discloses an electronic device, including: a memory for storing instructions executed by one or more processors of the electronic device; and a processor, which is one of the one or more processors of the electronic device, for Execute the above verification information sending method.
  • An embodiment of the present application discloses a computer-readable storage medium. Instructions are stored on the computer-readable storage medium. When the instructions are executed on an electronic device, the electronic device causes the electronic device to execute the above verification information sending method.
  • An embodiment of the present application discloses a computer program product, which includes instructions that, when the computer program product is run on a computer, cause the computer to execute the above verification information sending method.
  • Embodiments disclosed in this application may be implemented in hardware, software, firmware, or a combination of these implementation methods.
  • Embodiments of the present application may be implemented as a computer program or program code executing on a programmable system including at least one processor, a storage system (including volatile and non-volatile memory and/or storage elements) , at least one input device and at least one output device.
  • Program code may be applied to input instructions to perform the functions described herein and to generate output information.
  • Output information can be applied to one or more output devices in a known manner.
  • a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • Program code may be implemented in a high-level procedural language or an object-oriented programming language to communicate with the processing system.
  • assembly language or machine language can also be used to implement program code.
  • the mechanisms described in this application are not limited to the scope of any particular programming language. In either case, the language may be a compiled or interpreted language.
  • the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof.
  • the disclosed embodiments may also be implemented as instructions carried on or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be operated by one or more processors Read and execute.
  • instructions may be distributed over a network or through other computer-readable media.
  • machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including, but not limited to, floppy disks, optical disks, optical disks, read-only memories (CD-ROMs), magnetic Optical disk, read-only memory (ROM), random-access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical card, flash memory, or Tangible machine-readable storage used to transmit information (e.g., carrier waves, infrared signals, digital signals, etc.) using electrical, optical, acoustic, or other forms of propagated signals over the Internet.
  • machine-readable media includes any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, computer).
  • each unit/module mentioned in each device embodiment of this application is a logical unit/module.
  • a logical unit/module can be a physical unit/module, or it can be a physical unit/module.
  • Part of the module can also be implemented as a combination of multiple physical units/modules.
  • the physical implementation of these logical units/modules is not the most important.
  • the combination of functions implemented by these logical units/modules is what solves the problem of this application. Key technical issues raised.
  • the above-mentioned equipment embodiments of this application do not introduce units/modules that are not closely related to solving the technical problems raised by this application. This does not mean that the above-mentioned equipment embodiments do not exist. Other units/modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请涉及通信技术领域，公开了一种验证信息发送方法、电子设备及介质。验证信息发送方法包括：当接收到应用程序服务器发送的包括第一用户标识的验证信息下发请求；从存储的用户标识与对应的终端设备标识的预设对应关系中，确定出与第一用户标识匹配的第二用户标识，并从预设对应关系中获取与第二用户标识对应的终端设备标识；根据预设规则从第二用户标识对应的终端设备标识中确定出目标设备标识；向目标设备标识所标识的目标可信终端设备发送验证信息。基于上述方案，可以有效提高验证信息发送的安全性，有效确保用户的信息安全。

Description

一种验证信息发送方法、电子设备及介质
本申请要求于2022年04月15日提交中国专利局、申请号为202210399815.6、申请名称为“一种验证信息发送方法、电子设备及介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种验证信息发送方法、电子设备及介质。
背景技术
目前，用户在终端设备的各种应用程序上进行注册或登录等操作时，一般需要通过验证码验证的方式进行身份验证。例如，如图1所示，用户若在第一电子设备100的购物应用程序的登录界面200进行登录。当用户A在手机号输入框201中输入用户A的手机号码并点击获取验证码控件202，购物应用程序的服务器则会生成验证码信息并发送至对应的终端设备。当用户查看过验证码信息后，可以在登录界面200的验证码输入框203中输入验证码以进行身份认证实现登录。
目前应用程序的服务器发送验证码信息的方式一般如图2所示，应用程序的服务器先将验证码信息发送到运营商短信网络设备，运营商网络短信设备将验证码信息通过运营商通信网络发送到用户预留的手机号码或者用户在注册或登录界面输入的手机号码所在的终端设备。但是上述发送验证码信息的方式必须依赖于运营商专属的信令通道，导致发送验证码的成本较高。
目前还有一些方案中，应用程序的服务器发送验证码信息的方式为应用程序通过Push(推送)技术进行验证码信息的推送，具体方式如图3所示，应用程序的服务器将验证信息发送至推送(Push)服务器，Push服务器通过Push服务器与终端设备之间建立的长链接Push通道将验证信息发送至用户当前访问应用程序的终端设备。但Push服务器发送验证码信息的机制是将验证码信息发送至访问应用程序所使用的终端。因此，上述方式无法确保是目标号码对应的用户本人接收到验证码，即存在非目标号码的拥有者若在终端设备上用目标号码进行登录时，也可以在终端设备收到Push服务器推送的验证码，造成验证安全性较低，在一定程度会造成用户信息泄露的问题。
发明内容
为解决现有技术中验证信息发送方式安全性较低的技术问题，本申请实施例提供一种验证信息发送方法、电子设备及介质。
第一方面，本申请实施例提供一种验证信息发送方法，应用于电子设备，包括：
接收到应用程序服务器发送的验证信息下发请求，其中验证信息下发请求包括第一用户标识；
确定出存储的预设对应关系中与第一用户标识匹配的第二用户标识，并从预设对应关系中获取与第二用户标识对应的终端设备标识；其中，预设对应关系包括至少一个用户标识与至少一个终端设备标识之间的对应关系，并且对应关系中与用户标识对应的终端设备标识用于标识用户的可信终端设备；
根据预设规则从第二用户标识对应的终端设备标识中确定出目标设备标识；
向目标设备标识所标识的目标可信终端设备发送验证信息。
可以理解，本申请实施例中提及的第一用户标识可以为后文所提及的下发请求中携带的用户标识。 第二用户标识为后文中所提及的与下发请求中携带的用户标识匹配的目标用户标识。预设对应关系可以指后文中第二电子设备中存储的用户注册的用户标识以及对应的可信终端设备标识之间的映射关系。终端设备标识可以指后文所提及的可信终端设备标识。上述电子设备可以为后文所提及的第二电子设备。
基于上述方案，电子设备可以基于应用程序的服务器发送的用户标识确定出存储的与应用程序的服务器发送的用户标识匹配的目标用户标识，并将应用程序的服务器发送的验证信息发送至目标用户标识对应的目标可信终端设备，能够有效确保用户的信息安全。即若一些用户想要输入他人账号或手机号进行他人账号的登录时，电子设备也只会将验证信息发送至他人账号或手机号对应的可信终端设备上，而不是直接发送至当前访问应用程序的设备，有效保护他人账号安全。
在上述第一方面的一种可能的实现中，根据预设规则从第二用户标识对应的终端设备标识中确定出目标设备标识；包括：
确定预设对应关系中第二用户标识对应的终端设备标识的数量；
在第二用户标识对应的终端设备标识的数量为多个的情况下，确定第二用户标识对应的每个终端设备标识所标识的可信终端设备与第二电子设备当前的连接状态；
在确定第二用户标识对应的可信终端设备标识所标识的可信终端设备中，存在与电子设备当前的连接状态为已连接状态的可信终端设备，则将于电子设备当前的连接状态为已连接的可信终端设备作为目标可信终端设备；
将目标可信终端设备对应的终端设备标识作为目标设备标识。
可以理解，在目标用户标识即第二用户标识所对应的可信终端设备有多个的情况下，可以选择处于与第二电子设备处于连接状态的可信终端设备作为目标可信终端设备，并将验证信息发送至目标可信终端设备。如此，能够进一步确保接收验证信息的终端设备为用户当前正在使用的终端设备，提高验证效率。
在上述第一方面的一种可能的实现中，方法还包括：
在确定第二用户标识对应的可信终端设备标识所标识的可信终端设备中，不存在与电子设备当前的连接状态为已连接状态的可信终端设备，则在确定第二用户标识对应的可信终端设备标识所标识的可信终端设备中，存在当前状态为活跃状态的可信终端设备的情况下，将当前状态为活跃状态的可信终端设备作为目标可信终端设备。
可以理解，在目标用户标识即第二用户标识所对应的可信终端设备有多个的情况下，且不存在与第二电子设备处于连接状态的可信终端设备时，可以选择处于活跃状态的可信终端设备作为目标可信终端设备，并将验证信息发送至目标可信终端设备。如此，能够进一步确保接收验证信息的终端设备为用户正常使用或当前正在使用的终端设备，而不是处于停机或者关机等非正常使用的终端设备，能够提高验证效率。
在上述第一方面的一种可能的实现中，方法还包括：确定可信终端设备的当前状态为活跃状态的方式包括：当确定可信终端设备当前存在正在运行的线程，则确定可信终端设备的当前状态为活跃状态。
可以理解，确定可信终端设备状态为活跃状态可以为包括确定可信终端设备状态为正常使用中的状态。本申请不限于任何可以判断可信终端设备为活跃状态的方式。
在上述第一方面的一种可能的实现中，根据预设规则从第二用户标识对应的终端设备标识中确定出目标设备标识；还包括：
在第二用户标识对应的终端设备标识的数量为一个的情况下，将第二用户标识对应的终端设备标识作为目标设备标识。
可以理解，若确定目标用户标识及第二用户标识对应的终端设备标识数量为一个，则可以直接将该终端设备标识作为目标可信终端设备标识。
在上述第一方面的一种可能的实现中，向目标设备标识所标识的目标可信终端设备发送验证信息，包括：
获取目标可信终端设备的路由信息；
根据目标可信终端设备的路由信息建立目标可信终端设备与电子设备之间的推送通道；
通过推送通道向目标可信终端设备发送验证信息。
本申请实施例提供的验证信息发送方法采用推送通道进行验证信息的发送，相对于通过运营商专属信令通道发送验证信息的方式，能够极大地节约成本。同时，能通过推送通道将验证信息发送至任意可进行互联网连接的设备，而不仅限于手机，增大验证信息发送的设备范围。
在上述第一方面的一种可能的实现中，用户标识包括用户账号信息、手机号码和邮箱地址。
在上述第一方面的一种可能的实现中，终端设备标识包括终端设备标识号、终端设备名称和终端设备路由信息。
在上述第一方面的一种可能的实现中，验证信息由应用程序服务器生成，验证信息下发请求中包括验证信息。
可以理解，验证信息可以为用户所访问的应用程序对应的应用程序服务器生成的，此时，应用程序服务器向第二电子设备发送的下发请求中携带有验证信息和用户标识。通过应用程序服务器生成验证信息可以便于应用程序服务器中本身存储该验证信息，便于与用户输入的验证信息进行比对。
在上述第一方面的一种可能的实现中，验证信息由电子设备根据验证信息下发请求生成；
方法还包括：
电子设备生成验证信息后，将验证信息发送至应用程序服务器。
可以理解，应用程序的服务器接收到验证请求后将生成以及下发验证信息的下发请求发送至电子设备，电子设备接收到该生成以及下发验证信息的下发请求后，生成验证信息。此时，应用程序所对应的服务器向电子设备发送的下发请求中携带有用户标识，未携带有验证信息。电子设备在生成验证信息后，可以将验证信息发送至应用程序服务器，便于应用程序服务器对最后用户输入的验证码进行验证。
在上述第一方面的一种可能的实现中，在确定出预设对应关系中不存在与第一用户标识匹配的用户标识的情况下，发送不存在与第一用户标识匹配的用户标识的结果至应用程序服务器；
应用程序服务器向运营商网络设备发送验证信息下发请求。
可以理解，基于上述方案，可以使得在电子设备未存储有与验证信息的下发请求中携带的用户标识所匹配的用户标识时，能通过运营商网络设备发送验证信息。以保证用户最终能够收到验证信息。
在上述第一方面的一种可能的实现中，方法还包括：获取电子设备中存储的终端设备标识所标识的可信终端设备最邻近的身份认证时刻与当前时刻之间的时间间隔；
在时间间隔大于第一设定时间小于第二设定时间的情况下，确定终端设备标识所标识的可信终端设备为待激活状态，其中，服务器禁止向待激活状态的终端设备发送验证信息，第二预设时间大于第一预设时间；
在时间间隔大于第二设定时间的情况下，注销终端设备标识。
可以理解，通过判断电子设备中存储的终端设备标识所标识的可信终端设备最邻近的身份认证时刻与当前时刻之间的时间间隔可以进一步提高用户信息的安全性，防止由于用户可信终端设备发生丢失时，造成用户的验证信息泄露。
可以理解，当电子设备判断出可信终端设备当前时刻与最邻近的身份认证时刻之间的时间间隔大于第二设定时间，则可以证明可信终端设备已经长久未被使用或者长久未经过身份认证。可推断可信终端设备存在丢失的可能性，因此，电子设备可注销该可信终端设备，以保护用户信息安全。
在上述第一方面的一种可能的实现中，方法还包括：在确定终端设备标识所标识的可信终端设备为待激活状态的情况下，向终端设备标识所标识的可信终端设备发送身份认证提示信息。
可以理解，电子设备可以设置处于待激活状态的可信终端设备不能接收验证信息。但电子设备在确定出可信终端设备的当前状态为待激活状态时，可以发送身份认证提示信息至该处于待激活状态的可信终端设备。也可以发送身份认证提示信息至与该处于待激活状态的可信终端设备对应的可信终端设备标识所关联的用户标识对应的其他可信终端设备。其中，身份认证提示信息用于提醒用户进行认证。
在上述第一方面的一种可能的实现中，身份认证时刻包括终端设备进行解锁认证的时刻。
可以理解，确定可信终端设备最邻近的身份认证时刻的方式可以为确定出用户最邻近的对可信终端设备进行PIN解锁、图案解锁、指纹解锁、人脸解锁的时刻，或者用户最邻近的登录可信终端设备的设备账号的时间。
第二方面，本申请实施例提供一种电子设备，电子设备为第一电子设备，第一电子设备包括：
身份认证模块，用于在确定用户为授权注册用户的情况下，向可信终端设备注册模块发送用户标识和终端设备标识的注册请求；
可信终端设备注册模块，用于在接收到注册请求的情况下，获取用户标识信和终端设备标识之间的对应关系，且将用户标识和终端设备标识之间的对应关系发送至第二电子设备；
第一应用模块，用于响应于用户的操作，向应用程序服务器发送验证请求，验证请求中包括用户标识。
在上述第二方面的一种可能的实现中，第一电子设备还包括：
消息接收模块，用于接收验证信息，并控制第一电子设备显示验证信息。
在上述第二方面的一种可能的实现中，消息接收模块，用于在验证用户身份通过后，控制第一电子设备显示验证信息。
可以理解，第一电子设备可以在验证用户身份后进行验证信息的显示可以进一步增强用户信息的安全性。
可实施的，第一电子设备验证用户身份的方式可以为指纹认证、声纹认证、人脸认证、虹膜认证等任意认证方式。
第三方面，本申请实施例提供一种电子设备，电子设备为第二电子设备，第二电子设备包括：
验证信息接收模块，用于在接收到应用程序服务器发送的验证信息下发请求，将验证信息下发请求中携带的第一用户标识发送至设备验证模块，并将验证信息下发请求中携带的验证信息发送至消息推送模块；
设备验证模块，用于确定出存储的预设对应关系中与第一用户标识匹配的第二用户标识，从预设对应关系中获取与第二用户标识对应的终端设备标识；其中，预设对应关系包括至少一个用户标识与至少一个终端设备标识之间的对应关系，并且对应关系中与用户标识对应的终端设备标识用于标识用户的可信终端设备；
设备验证模块，用于根据预设规则从第二用户标识对应的终端设备标识中确定出目标设备标识，并将目标设备标识发送至消息推送模块；
消息推送模块，用于向目标设备标识所标识的目标可信终端设备发送验证信息。
可以理解，本申请实施例提供的第二电子设备可以基于应用程序的服务器发送的用户标识确定出存储的与应用程序的服务器发送的用户标识匹配的目标用户标识，并将应用程序的服务器发送的验证信息发送至目标用户标识对应的目标可信终端设备，能够有效确保用户的信息安全。即若一些用户想要输入他人账号或手机号进行他人账号的登录时，第二电子设备也只会将验证信息发送至他人账号或手机号对应的可信终端设备上，而不是直接发送至当前访问应用程序的设备，有效保护他人账号安全。
第四方面，本申请实施例提供一种电子设备，包括：存储器，用于存储由电子设备的一个或多个处理器执行的指令，以及处理器，是电子设备的一个或多个处理器之一，用于执行权利要求上述验证信息发送方法。
第五方面，本申请实施例提供一种计算机可读存储介质，计算机可读存储介质上存储有指令，该指令在电子设备上执行时，使电子设备执行上述验证信息发送方法。
第六方面，本申请实施例提供一种计算机程序产品，包括指令，当计算机程序产品在计算机上运行时，使得计算机执行上述验证信息发送方法。
附图说明
图1根据本申请的一些实施例，示出了一种电子设备的登录界面示意图；
图2根据本申请的一些实施例，示出了一种验证码信息的发送示意图；
图3根据本申请的一些实施例，示出了一种验证码信息的发送示意图；
图4a-4c根据本申请的一些实施例，示出了一种可信设备注册的过程示意图；
图5根据本申请的一些实施例，示出了一种验证码信息发送的场景示意图；
图6a根据本申请的一些实施例，示出了一种第一电子设备的示意图；
图6b根据本申请的一些实施例，示出了一种应用程序服务器的示意图；
图6c根据本申请的一些实施例，示出了一种第二电子设备的示意图；
图7根据本申请的一些实施例，示出了一种验证信息发送的流程示意图；
图8a-8c根据本申请的一些实施例，示出了一种可信设备注册的过程示意图；
图9a-9b根据本申请的一些实施例，示出了一种可信设备注册的过程示意图；
图10根据本申请的一些实施例，示出了一种电子设备的登录界面示意图；
图11根据本申请的一些实施例，示出了一种电子设备的通知中心界面示意图；
图12a根据本申请的一些实施例，示出了一种电子设备的通知中心界面示意图；
图12b根据本申请的一些实施例，示出了一种电子设备的通知中心界面示意图；
图13根据本申请的一些实施例，示出了一种第二电子设备的设备验证模块对用户注册的可信终端设备进行管理的流程示意图。
具体实施方式
本申请的说明性实施例包括但不限于一种验证信息发送方法、电子设备及介质。
为更加清楚的理解本申请实施例的方案，首先对本申请实施例中涉及到的一些术语进行简要解释。
Push技术：一种基于互联网的信息推送技术，具体指通过客户端与服务器端建立的长链接推送通道进行客户端与服务器之间的数据传输的技术。
Push通道：客户端与服务器端建立的长链接推送通道，可以由手机品牌厂商自建推送、手机应用自建等方式建立。
如前所述，目前，通过推送服务器发送验证码，难以确保是目标号码用户本人接收到验证码，造成用户信息安全的问题。
例如，用户A若在如图1中所示的第一电子设备100的购物应用程序的登录界面200进行登录。当用户A在手机号输入框201中输入用户B的手机号码并点击获取验证码控件202，购物应用程序的服务器将则会生成验证码信息并将验证码信息发送至第二电子设备，第二电子设备则会将验证码信息发送至访问该购物应用程序的第一电子设备100。用户A通过第一电子设备100查看验证码信息后将在验证码输入框203中输入验证码将可以进行用户B账号的登录。如此，造成了用户B的账户信息的泄露。
为解决上述问题，本申请实施例提供一种验证信息发送方法，具体地，该方法包括：用户首先通过第一电子设备进行用户标识以及用户信任的可信终端设备标识的注册。其中，用户通过第一设备进行用户标识以及用户信任的可信终端设备标识的注册的方式可以为用户通过第一电子设备调用第二电子设备的设备注册接口进行注册；还可以为用户通过第一电子设备首先获取用户标识以及用户信任的可信终端设备标识，然后将获取的用户标识以及用户信任的可信终端设备标识发送至第二电子设备。第二电子设备对用户注册的用户标识以及对应的可信终端设备标识之间的映射关系进行存储。
如此，当用户通过任意电子设备访问应用程序，并在进行账号注册、账号登录或支付等场景中执行了点击获取验证码控件的操作或其他触发电子设备生成验证请求的操作后，电子设备会发送携带有用户标识的验证请求至应用程序服务器，应用程序服务器可以生成该验证请求对应的验证信息，并将下发验证信息的下发请求发送至第二电子设备，可以理解，下发验证信息的下发请求中可以包括用户标识以及验证信息。
当第二电子设备接受到上述下发请求后，从上述预先存储的用户标识以及对应的可信终端设备之间的映射关系确定是否存在与下发请求中的用户标识相匹配的目标用户标识。如果存在与下发请求中的用户标识相匹配的目标用户标识，则获取第二电子设备中存储的与下发请求中的用户标识相匹配的目标用户标识所对应的所有可信终端设备标识，并根据预设规则从所有可信终设备标识中确定出目标可信终端设备标识，并向目标可信终端设备标识对应的目标可信终端设备发送验证信息。目标可信终端设备在接受到验证信息后对验证信息进行显示。
在一些实施例中，第二电子设备若判断出不存在与下发请求中的用户标识相匹配的目标用户标识，则将不存在与下发请求中的用户标识相匹配的目标用户标识的判断结果发送至应用程序的服务器，应用程序的服务器将验证信息发送至运营商网络设备，运营商网络设备调用运营商专属的信令通道以短信的形式将验证码信息发送到验证请求中的用户标识中携带的手机号码所在的终端设备。
可以理解，在本申请一些实施例中，上述用户标识可以是用户手机号码、邮箱地址以及第三方服务账号例如微信TM账号、QQTM账号等账号信息；上述可信终端设备标识可以是可信终端设备的设备标识号、设备名称以及设备路由信息，其中设备路由信息可以包括设备的IP地址或者MAC地址。
可以理解，如前所述，上述验证信息可以为用户所访问的应用程序所对应的服务器生成的，此时，应用程序所对应的服务器向第二电子设备发送的下发请求中携带有验证信息和用户标识。通过应用程序服务器生成验证信息可以便于应用程序服务器中本身存储该验证信息，便于与用户输入的验证信息进行比对。
在另一些实施例中，上述验证信息可以为第二电子设备生成的，即应用程序的服务器接收到验证请求后将生成以及下发验证信息的下发请求发送至第二电子设备，第二电子设备接收到该生成以及下发验证信息的下发请求后，生成验证信息。此时，应用程序所对应的服务器向第二电子设备发送的下发请求中携带有用户标识，未携带有验证信息。第二电子设备在生成验证信息后，可以将验证信息发送至应用 程序服务器，便于应用程序服务器对最后用户输入的验证码进行验证。
可以理解，第二电子设备中可以存储任意个用户标识以及任意个用户标识对应的可信终端设备标识。每个用户标识可以对应一个可信终端设备标识，也可以对应多个可信终端设备标识。
可以理解，上述根据预设规则从所有可信终设备标识中确定出目标可信终端设备标识的方法可以包括：
确定目标用户标识对应的所有可信终端设备的数量，若确定目标用户标识对应的可信终端设备的数量为多个，则确定每个可信终端设备与第二电子设备的连接状态，若存在与第二电子设备的连接的可信终端设备，则将与第二电子设备的连接的可信终端设备作为目标可信终端设备，将目标可信终端设备对应的可信终端设备标识作为目标可信终端设备标识。
若目标用户标识对应的可信终端设备与第二电子设备的连接状态均为未进行连接，则进一步确定目标用户标识对应的可信终端设备是否存在当前状态为活跃状态的终端设备，若存在，则将处于活跃状态的可信终端设备作为目标可信终端设备。若不存在，则将活目标用户标识对应的所有可信终端设备均作为目标可信终端设备，将目标可信终端设备对应的可信终端设备标识作为目标可信终端设备标识。
其中，判断目标用户标识对应的可信终端设备是否处于活跃状态的方式可以为判断目标用户标识对应的可信终端设备是否具有正在运行的线程，若是，则确定该可信终端设备的当前状态为活跃状态；若否，则确定该可信终端设备的当前状态为活跃状态。
具体的，第二电子设备可以通过向目标用户标识对应的所有可信终端设备发送状态获取请求，以获取目标用户标识对应的可信终端设备是否具有正在运行的线程。
若确定目标用户标识对应的可信终端设备标识数量为一个，则可以直接将该可信终端设备标识作为目标可信终端设备标识。
可以理解，第二电子设备向对应的目标可信终端设备发送验证信息的方式可以为：在第二电子设备获取到目标可信终端设备标识后，通过目标可信终端设备标识中的设备路由信息，与对应的目标可信终端设备之间建立推送通道，通过推送通道将验证信息发送至对应的目标可信终端设备。
可以理解，在一些时候实施例中，第二电子设备在将验证信息通过推送通道发送至目标可信终端设备后，可以将验证消息已发送提示信息发送至应用程序的服务器，应用程序的服务器可以控制触发验证码生成任务所对应的界面，例如应用程序的登录界面、注册界面或者支付界面等显示验证消息已发送提示信息。验证消息已发送提示信息中可以包括目标可信终端设备标识(例如设备标识信息、设备名称信息等)，验证消息已发送提示信息可以用于提示用户已将验证消息发送至目标可信终端设备，且提示用户可信终端设备标识，便于用户根据设备信息找到对应的可信终端设备以进行验证信息的查看。例如，上述验证消息已发送提示信息可以为“已将验证信息发送至HUAWEI MATE40”。
此外，为了进一步增强用户信息的安全性，目标可信终端设备可以在验证用户身份后再进行验证信息的显示。可实施的，目标可信终端设备验证用户身份的方式可以为指纹认证、声纹认证、人脸认证、虹膜认证等任意认证方式。在一些实施例中，目标可信终端设备在确认环境安全后，还可以对验证信息进行语音播报。
可以理解，上述应用程序可以为购物应用程序、视频娱乐应用程序、办公用用程序等任意应用程序，可实施的，也可以为一些网页应用。
基于上述方案，第二电子设备可以基于应用程序的服务器发送的用户标识确定出第二电子设备中存储的与应用程序的服务器发送的用户标识匹配的目标用户标识，并将应用程序的服务器发送的验证信息发送至目标用户标识对应的可信终端设备，有效确保用户的信息安全。即若一些用户想要输入他人账号 或手机号进行他人账号的登录时，第二电子设备也只会将验证信息发送至他人账号或手机号对应的可信终端设备上，而不是直接发送至当前访问应用程序的设备，有效保护他人账号安全。
此外，在目标用户标识所对应的可信终端设备有多个的情况下，可以选择处于与第二电子设备处于连接状态或者处于活跃状态的可信终端设备作为目标可信终端设备，并将验证信息发送至目标可信终端设备。如此，能够进一步确保接收验证信息的终端设备为用户当前正在使用的终端设备，提高验证效率。
另外，本申请实施例提供的验证信息发送方法采用推送通道进行验证信息的发送，相对于通过运营商专属信令通道发送验证信息的方式，能够极大地节约成本。同时，能通过推送通道将验证信息发送至任意可进行互联网连接的设备，而不仅限于手机，增大验证信息发送的设备范围。
可以理解，本申请实施例提供的验证信息发送方法可以用于任何需要发送验证信息的场景中。下面以用户A进行可信终端设备注册以及在应用程序B进行账号登录的场景说明本申请实施例中的验证信息发送方法。
首先介绍用户A通过第一电子设备100进行用户标识以及用户信任的可信终端设备标识的注册场景。例如，如图4a中所示，用户可以通过在第一电子设备100的设备账号登录界面400进行设备账号的登录，在登录设备账号后，用户可以在账号中心界面401点击“可信设备注册”控件4011，以调用第二电子设备300的设备注册接口，进行用户标识和可信终端设备的注册。图4c展示了第二电子设备300的设备注册接口界面402的示意图，用户A可以在设备注册接口界面402注册用户的手机号码、邮箱等用户标识，还可以注册设备标识号、设备IP和设备名称等设备标识。例如，用户A在设备注册接口界面402注册了手机号码“12345678901”；邮箱地址“12345@qq.com”；设备标识号码“abc01”；设备IP“192.168.1.201”；设备名称“HUAWEI”。当用户点击“注册”控件4021，第二电子设备300可以将用户A注册的用户标识以及可信终端设备标识进行对应存储。
可以理解，上述用户进行可信终端设备注册的方式只是举例说明，本申请实施例中不限于任意的可实施的可信终端设备注册方式。
如图5所示，用户A若通过第一电子设备100访问应用程序B。例如，用户A若在第一电子设备100的应用程序B的登录界面200进行登录。当用户A在手机号输入框201中输入用户A的手机号码并点击“获取验证码”控件202，则第一电子设备100会向应用程序B对应的应用程序服务器500发送验证请求，应用程序服务器500响应于该验证请求，会生成对应的验证信息并将验证信息以及用户A进行账号登录用的手机号码“12345678901”发送至第二电子设备300。例如，应用程序B的服务器生成的验证信息可以为“您好，您正在登录，您的验证码是667788”。
第二电子设备300根据用户A的手机号码确定出与用户A的手机号码匹配的目标用户标识，例如，第二电子设备300中存储的与用户A的手机号码匹配的目标用户标识为手机号码“123456789”以及邮箱号码“12345@qq.com”，并确定出与该用户标识关联的可信终端设备的标识只有设备标识号码“abc01”；设备IP“192.168.1.201”；设备名称“HUAWEI”。
此时，第二电子设备300会根据可信终端设备标识中的设备IP“192.168.1.201”与可信终端设备建立推送通道，将验证信息“您好，您正在登录，您的验证码是667788”通过推送通道发送至设备标识号码为“abc01”的可信终端设备001上。
如图5中所示，可信终端设备001的消息通知中心界面404可以显示验证信息“您好，您正在登录，您的验证码是667788”。
可以理解，基于上述方案，若用户A在手机号输入框201中输入用户B的手机号码想要登录B的账号。当点击获取验证码控件202，应用程序服务器500则会生成验证码信息并将验证码信息以及用户 B的手机号码发送至第二电子设备300，第二电子设备300根据用户B的手机号码确定出与用户B的手机号码关联的可信终端设备,并将验证码信息发送至用户B的手机号码关联的可信终端设备。如此，用户A将无法查收到用户B的验证信息，也无法进行用户B的账号的登录。有效保证用户B的账号安全。
下面在详细介绍本申请实施例的验证信息发送方法之前，首先对本申请实施例提供的第一电子设备100、应用程序服务器500和第二电子设备300的结构进行简要介绍。
可以理解，本申情实施例中，第一电子设备100可以为电脑、平板、手机等任意终端电子设备。如图6a中所示，第一电子设备100可以包括：
身份认证模块101，用于确定用户是否为授权注册用户。身份认证模块101确定用户为授权注册用户的方式可以为：获取用户的身份认证信息，当检测到用户的身份认证信息为通过的情况下，确定该用户为授权用户。当检测到用户身份认证信息为不通过的情况下，确定该用户为非授权用户。
具体的，第一电子设备100可以设置有设备账号登录接口，用户可以在该设备账号登录接口进行账号密码登录以及其他的身份认证登录，身份认证模块101可以获取用户在设备账号登录接口输入的账号密码或者获取用户的其他身份认证信息。
身份认证模块101还用于当检测到用户身份认证通过后，即确定用户为授权注册用户后，发送设备注册请求至可信终端设备注册模块102。
例如，用户可以在前述图4a中所示的第一电子设备100的设备账号登录界面400进行设备账号的登录，此时，身份认证模块101可以获取用户在设备账号登录界面400输入的账号密码。在一些实施例中，用户也可以通过指纹认证、声纹认证、人脸认证、虹膜认证等任意认证方式进行用户设备账号的登录。此时，身份认证模块101可以获取用户指纹信息、声纹信息、人脸信息、虹膜信息等身份信息。当身份认证模块101检测到用户身份认证通过即设备账号登录成功时，且在检测到用户执行了点击“可信终端设备注册”控件等操作时，发送设备注册请求至可信终端设备注册模块102。
可信终端设备注册模块102，用于响应于用户身份认证模块101发送的可信终端设备注册请求，调用第二电子设备300的设备注册接口。
在一些实施例中，可信终端设备注册模块102可以用于获取用户标识以及与用户标识关联的可信终端设备标识。并将用户标识以及与用户标识关联的可信终端设备标识发送至第二电子设备300。
第一应用模块103，用于响应于用户点击获取验证码控件的操作或其他触发电子设备生成验证请求的操作，将验证请求发送至应用程序服务器500。其中，验证请求中包括用户标识。
消息接收模块104，用于建立与第二电子设备300之间的推送通道，接收第二电子设备300发送的验证信息，并用于控制验证信息在第一电子设备100的消息通知中心显示。
如图6b中所示，应用程序服务器500可以包括：
第二应用模块501，用于接收第一电子设备100的第一应用模块103发送的验证请求，并将验证请求发送至验证信息生成模块502。
验证信息生成模块502，用于根据验证请求生成验证信息，并发送验证信息下发请求至第二电子设备300的验证信息接收模块301。验证信息下发请求中包括用户标识和验证信息。
第二电子设备300可以为云端服务器，也可以为基站设备，也可以为第一电子设备100搭载的服务器或者局域网络等。如图6c所示，第二电子设备300可以包括：
验证信息接收模块301，用于接收应用程序服务器500的验证信息生成模块502发送的验证信息下发请求，验证信息下发请求中包括用户标识和验证信息。并用于将用户标识发送至设备验证模块302。还用于将验证信息和目标可信终端设备标识发送至消息推送模块303。
设备验证模块302，用于根据验证信息接收模块301发送的用户标识确定出第二电子设备300中存储的与验证信息接收模块301发送的用户标识相匹配的目标用户标识，并获取目标用户标识对应的所有可信终端设备标识。还用于根据预设规则从目标用户标识对应的所有可信终端设备标识中确定出目标可信终端设备标识。还用于将目标可信终端设备标识中的设备路由信息发送至第二电子设备300的消息推送模块303。
消息推送模块303，根据目标可信终端设备对应的设备路由信息建立同目标可信终端设备的安全的推送通道，通过推送通道将验证信息到目标可信终端设备。
下面结合上述图6a-6c中提及的第一电子设备100、应用程序服务器500和第二电子设备300的结构对本申请实施例中提供的验证信息发送方法进行详细介绍。图7示出了本申请实施例一种验证信息发送方法的交互流程示意图。图7所示的验证信息发送方法具体包括可信终端设备的注册阶段和验证信息的生成发送阶段。
其中，图7中701-705示出了可信终端设备的注册流程，706-718示出了验证信息的生成发送流程。详述如下：
701：第一电子设备100的身份认证模块101确定用户为授权注册用户。
可以理解，身份认证模块101确定用户为授权注册用户的方式可以为：获取用户的身份认证信息，当检测到用户的身份认证信息为通过的情况下，确定该用户为授权用户。当检测到用户身份认证信息为不通过的情况下，确定该用户为非授权用户。
具体的，第一电子设备100可以设置有设备账号登录接口，用户可以在该设备账号登录接口进行账号密码登录以及其他的身份认证登录，身份认证模块101可以获取用户在设备账号登录接口输入的账号密码或者获取用户的其他身份认证信息。
例如，用户可以在前述图4a中所示的第一电子设备100的设备账号登录界面400进行设备账号的登录，此时，身份认证模块101可以获取用户在设备账号登录界面400输入的账号密码。在一些实施例中，用户也可以通过指纹认证、声纹认证、人脸认证、虹膜认证等任意认证方式进行用户设备账号的登录。此时，身份认证模块101可以获取用户指纹信息、声纹信息、人脸信息、虹膜信息等身份信息。当身份认证模块101检测到用户身份认证通过即设备账号登录成功时，即确定用户为授权注册用户。
在一些实施例中，用于触发设备注册请求发送的控件，例如“可信设备注册”控件4011可以设置于图4b中所示的账号中心界面401。此时，身份认证模块101检测到用户身份认证通过即确定用户为授权注册用户，且在获取到用户执行了点击可信终端设备注册控件时的操作时，才可以发送可信终端设备注册请求至可信终端设备注册模块102。
在另一些实施例中，用于触发设备注册请求发送的控件也可以设置于设置界面等无需进行身份认证即可查看的界面，即用户可以先点击触发设备注册请求发送的控件再触发身份认证。例如，如图8a中所示，第一电子设备100的设置界面405设置有“可信设备注册”控件4011，当用户点击“可信设备注册”控件4011后，会显示如图8b中所示的身份认证页面406，此时用户可以在身份认证页面406进行设备账号登录验证。在一些实施例中，身份认证页面406也可以采用其他的身份认证，例如人脸识别认证等。身份认证模块101可以获取用户在身份认证页面406输入的身份验证信息。当检测到用户身份验证信息通过后，向可信终端设备注册模块102发起设备注册请求。
702：第一电子设备100的身份认证模块101向可信终端设备注册模块102发送设备注册请求。
在一些实施例中，用于触发设备注册请求发送的控件，例如“可信终端设备注册”控件可以设置于图4b中所示的账号中心界面。此时，身份认证模块101检测到用户身份认证通过即确定用户为授权注册 用户，且在获取到用户执行了点击“可信设备注册”控件4011的操作时，才可以发送可信终端设备注册请求至可信终端设备注册模块102。
在另一些实施例中，用于触发设备注册请求发送的控件也可以设置于设置界面等无需进行身份认证即可查看的界面，即用户可以先点击触发设备注册请求发送的控件再触发身份认证。例如，如图8a中所示，“可信终端设备注册”控件4011设置于第一电子设备100的设置界面404。当身份认证模块101检测到用户身份验证信息通过后，直接向可信终端设备注册模块102发起设备注册请求。
在一些实施例中，若第一电子设备100设置有设备锁，例如锁屏密码、人脸识别等，身份认证模块可以直接获取用户解锁第一电子设备时所有的身份认证信息，当用户解锁成功，则身份认证模块101确认用户为授权用户，此时，身份认证模块101检测到用在点击用于触发设备注册请求发送的控件，例如图8a中所示的设置界面404的“可信终端设备注册”控件4011后，身份认证模块直接向可信终端设备注册模块102发起设备注册请求。
703：第一电子设备100的可信终端设备注册模块102获取用户标识以及与用户标识关联的可信终端设备标识。
在一些实施例中，当可信终端设备注册模块102获取到用户的注册请求时，可以直接显示设备注册页面，用户可以在该注册页面进行用户标识以及对应的可信终端设备标识的注册，在用户注册完成后，可以将用户注册的用户标识以及与用户标识关联的可信终端设备标识发送至第二电子设备300的设备验证模块302。
可以理解，在另一些实施例中，当可信终端设备注册模块102获取到用户的注册请求时，可信终端设备注册模块102可以直接调用第二电子设备300的设备验证模块302的设备注册接口，即用户可以在该设备注册接口进行用户标识以及对应的可信终端设备标识的注册。
用户标识可以包括手机号码、邮箱地址以及第三方服务账号例如微信TM账号、QQTM账号等代表用户身份的标识信息。可信终端设备标识可以是可信终端设备的设备标识号、设备名称以及设备路由信息，其中设备路由信息可以包括设备的IP地址或者MAC地址。可实施的，用户可以注册一个或者多个可信终端设备标识。
例如，如图8c所示，用户可以在设备注册接口即设备注册接口界面402进行用户标识以及设备标识的注册。如图8c中所示，用户在设备注册接口界面402注册了手机号码“12345678901”；邮箱地址
“12345@qq.com”；设备标识号码1“abc01”；设备IP1“192.168.1.201”；设备名称1“HUAWEI”。以及设备标识号码2“abc02”；设备IP2“192.168.1.202”；设备名称2“HUAWEI2”。
可以理解，用户除了可以采用上述在对应文本框中填写设备标识的方式进行可信终端设备标识的注册，也可以采用手动拖动的方式进行可信终端设备标识的注册。
例如，如图9a所示，在设备注册接口界面402，设置有设备注册框4022，且可以显示有本机设备图标和与本机设备关联的设备图标。例如，图9a中显示了本机设备图标601，与本机设备关联的计算机设备图标602和以及平板设备图标603，用户可以通过拖动设备图标实现可信终端设备标识的注册。例如，如图9b中所示，用户将计算机设备图标602拖进了设备注册框4022中。可以理解，在对设备图标进行拖动时可以显示有设备标识框604，设备标识框中可以显示被拖动设备的名称或标识号等设备标识，以便用户辨认设备。例如，图9b中在拖动计算机设备图标602时，设备标识框中可以显示计算机设备图标602对应的计算机设备的标识号“abc02”。
可以理解，当设备图标被拖进设备注册框4022后，第二电子设备300可以直接获取设备图标对应的设备标识，例如，当计算机设备图标602被拖进设备注册框4022后，计算机设备图标602对应的计算机设 备的标识号“abc02”；设备IP“192.168.1.202”；设备名称“HUAWEI2”。
可以理解，设备图标的生成方式可以为第二电子设备300基于从第一电子设备100获取的第一电子设备100的设备标识或者与第一电子设备100相关联的设备的设备标识生成的。
可以理解，本申请实施例中上述进行用户标识和可信终端设备标识的注册方式只是举例说明，本申请实施例中的用户标识和可信终端设备标识也可以为其他任意可实施的方式。
704：第一电子设备100的可信终端设备注册模块102将用户标识以及与用户标识关联的可信终端设备标识发送至第二电子设备300的设备验证模块302。
705：第二电子设备300的设备验证模块302将用户标识以及与用户标识关联的可信终端设备标识进行存储。
可以理解，用户标识与用户标识关联的可信终端设备间的存储方式可以为通过构建索引表的形式进行存储。
706：第一电子设备100的第一应用模块103响应于用户的操作，向应用程序服务器500的第二应用模块501发送验证请求。
当用户通过第一电子设备100访问应用程序，并在进行账号注册、账号登录或支付等场景中执行了点击获取验证码控件的操作或其他触发电子设备生成验证请求的操作后，第一电子设备100的第一应用模块103会向应用程序服务器500的第二应用模块501发送验证请求。
例如，如前述图5所示，用户A若通过第一电子设备100访问应用程序B。例如，用户A若在第一电子设备100的应用程序B的登录界面200进行登录。当用户A在手机号输入框201中输入用户A的手机号码并点击“获取验证码”控件202，则第一电子设备100的第一应用模块103会向应用程序B对应的应用程序服务器500的第二应用模块501发送验证请求。
可以理解，该验证请求中携带有用户标识。用户标识可以是用户手机号码、邮箱地址以及第三方服务账号例如微信TM账号、QQTM账号等账号信息。例如，对于图5中的场景，验证请求中携带的用户标识可以为用户在第一电子设备100用于登录的手机号或在用户进行应用程序的账号注册时携带的邮箱地址等。
707：应用程序服务器500的第二应用模块501将验证请求发送至验证信息生成模块502。
708：应用程序服务器500的验证信息生成模块502根据验证请求生成验证信息。
可以理解，在一些实施例中，应用程序服务器500的验证信息生成模块502根据验证请求生成对应的验证信息。其中验证信息可以包括验证码以及提示用户正在进行登录、注册等操作等提示信息。例如，验证信息可以为：“您好，您正在登录，您的验证码是667788”。
709：应用程序服务器500的验证信息生成模块502将验证信息下发请求发送至第二电子设备300的验证信息接收模块301。
可以理解，应用程序服务器500在生成验证信息后，会发送验证信息下发请求至第二电子设备300的验证信息接收模块301。其中，验证信息下发请求可以包括验证信息下发指令、验证信息以及用户标识。
710：第二电子设备300的验证信息接收模块301将验证信息下发请求中携带的用户标识发送至设备验证模块302。
711：第二电子设备300的设备验证模块302根据接收到的用户标识判断设备验证模块302中是否存储有与接收到的用户标识相匹配的目标用户标识。
若存在，则转至712，获取设备验证模块302中存储的与目标用户标识所对应的可信终端设备标识。 若不存在，则转至718，设备验证模块302将不具备可信终端设备的结果发送至应用程序服务器500的验证信息生成模块502。
例如，如前述图5中所示，当设备验证模块302获取到用户标识为手“12345678901”时，则可以查询到设备验证模块302中存储的与该手机号码“12345678901”匹配的所有用户标识，例如，查询到的与该手机号码“12345678901”匹配的用户标识可以包括第二电子设备300中存储的一致的手机号码
“12345678901”，邮箱地址“12345@qq.com”。
712：第二电子设备300的设备验证模块302获取目标用户标识所对应的可信终端设备标识。
可以理解，设备验证模块302可以根据与验证信息下发请求的用户标识相匹配的用户标识确定对应的可信终端设备标识。
例如，如前述图5中所示，设备验证模块302根据目标用户标识中的手机号码“123456789”以及邮箱号码“12345@qq.com”，确定出与该目标用户标识关联的可信终端设备的标识包括设备标识号码“abc01”；设备IP“192.168.1.201”；设备名称“HUAWEI”。
713：第二电子设备300的设备验证模块302根据预设规则从目标用户标识对应的可信终端设备标识中确定出目标可信终端设备标识。
其中，按照预设规则从目标用户标识对应的所有可信终端设备标识中确定目标可信终端设备标识的方式可以包括:
确定目标用户标识对应的所有可信终端设备的数量，若确定目标用户标识对应的可信终端设备的数量为多个，则确定每个可信终端设备与第二电子设备300的连接状态，若存在与第二电子设备300的连接的可信终端设备，则将与第二电子设备300的连接的可信终端设备作为目标可信终端设备，将目标可信终端设备对应的可信终端设备标识作为目标可信终端设备标识。
若目标用户标识对应的可信终端设备与第二电子设备300的连接状态均为未进行连接，则进一步确定目标用户标识对应的可信终端设备是否存在当前状态为活跃状态的终端设备，若存在，则将处于活跃状态的可信终端设备作为目标可信终端设备。若不存在，则将目标用户标识对应的所有可信终端设备均作为目标可信终端设备，将目标可信终端设备对应的可信终端设备标识作为目标可信终端设备标识。
其中，判断目标用户标识对应的可信终端设备是否处于活跃状态的方式可以为判断目标用户标识对应的可信终端设备是否具有正在运行的线程，若是，则确定该可信终端设备的当前状态为活跃状态；若否，则确定该可信终端设备的当前状态为活跃状态。
具体的，第二电子设备300可以通过向目标用户标识对应的所有可信终端设备发送状态获取请求，以获取目标用户标识对应的可信终端设备是否具有正在运行的线程。
若确定目标用户标识对应的可信终端设备数量为一个，则可以直接将该可信终端设备标识作为目标可信终端设备标识。
714：第二电子设备300的设备验证模块302将目标可信终端设备标识发送至验证信息接收模块301。
715：第二电子设备300的验证信息接收模块301将验证信息和目标可信终端设备标识发送至消息推送模块303。
716：第二电子设备300的消息推送模块303将验证信息推送至目标可信终端设备标识对应的目标可信终端设备800的消息接收模块801。
可以理解，本申请实施例中，目标可信终端设备的结构可以与第一电子设备的结构相同。
可以理解，第二电子设备300的验证信息接收模块301获取到对应的目标可信终端设备标识后，通过对应的目标可信终端设备标识中的设备路由信息，与对应的目标可信终端设备800之间建立推送通道， 通过推送通道将验证信息发送至对应的目标可信终端设备800。
可以理解，本申请实施例中，当目标可信终端设备800接收到验证信息后，可以通过消息通知中心进行验证信息的显示。
可以理解，在一些时候实施例中，第二电子设备300在将验证信息通过推送通道发送至目标可信终端设备800后，可以将验证消息已发送提示信息发送至应用程序的界面。验证消息已发送提示信息中可以包括目标可信终端设备800的设备标识信息，验证消息已发送提示信息可以用于提示用户已将验证消息发送至目标可信终端设备800，且提示用户可信终端设备800的设备标识，便于用户根据设备信息找到对应的目标可信终端设备800以进行验证信息的查看。
例如，如图10中所示，第一电子设备100的设备账号登录界面200可以显示验证消息已发送提示信息“已将验证信息发送至HUAWEI”。
717：目标可信终端设备800的消息接收模块801控制目标终端设备800显示验证信息。
可以理解，在一些实施例中，目标可信终端设备800的消息接收模块801可以直接控制消息通知中心显示验证信息。如图11中所示，验证信息“您好，您正在登录，您的验证码是667788”可以直接显示在目标可信终端设备800的消息通知中心界面404。
在另一些实施例中，为了进一步增强用户信息的安全性，目标可信终端设备800可以在验证用户身份后进行验证信息的显示。可实施的，目标可信终端设备800验证用户身份的方式可以为指纹认证、声纹认证、人脸认证、虹膜认证等任意认证方式。
具体的，如图12a中所示，目标可信终端设备800的消息通知中心界面可以显示“您收到一条验证信息”等提示语，当用户进行身份认证，例如人脸验证后，如图12b中所示，消息通知中心界面404显示验证信息“您好，您正在登录，您的验证码是667788”。
在一些实施例中，目标可信终端设备800在确认周围环境为安全环境后，还可以对验证信息进行语音播报。
具体的，目标可信终端设备800确认环境安全的方式可以为：
目标可信终端设备800在接收到验证信息后，可以发送环境安全识别请求至与目标可信终端设备800在一定距离范围内的，且与目标可信终端设备800建立连接的具备摄像功能的第三电子设备，第三电子设备接收到环境安全识别请求开启摄像功能以获取环境图像，并将环境图像发送至目标可信终端设备800。目标可信终端设备800当判断出环境图像中的人像只有用户图像或可信任图像时，确认周围环境为安全环境。
目标可信终端设备800对验证信息进行语音播报的方式可以为将验证信息发送至与目标可信终端设备800在一定距离范围内的，且与目标可信终端设备800建立连接的具有语音播报功能的电子设备，例如音箱等设备对验证信息进行播报。在一些实施例中，目标终端设备控制目标终端设备的扩音器进行语音播报。
可以理解，上述可信任图像可以为用户在目标可信终端设备800中预先注册的可信任图像。例如，可以为用户家人的图像或用户住房环境的图像，例如，用户房间图片。
可以理解，当环境图像中包括无法识别的人脸图像或其他人像，例如环境图像中包括无法识别的人像侧脸或人像背影，则判断出环境可能存在陌生人，此时，确定周围环境为非安全环境，不对验证信息进行播报。
例如，用户在家中房间内办公，当目标可信终端设备800接收到验证信息后，可以发送环境安全识别请求至与目标可信终端设备800在设定距离范围内的，且与目标可信终端设备800建立连接的房间的摄 像装置，摄像装置开启摄像功能以获取环境图像发送至目标可信终端设备800。当目标可信终端设备800判断出环境图像与用户在目标可信终端设备800中进行注册的用户房间图像匹配，则对验证信息进行播报。
如此，用户可以无需在目标可信终端设备800上进行查看即可获取到验证信息，提高用户体验。
718：设备验证模块302将不具备可信终端设备的结果发送至应用程序服务器500的验证码生成模块。
可以理解，本申请实施例中，可以理解，当设备验证模块302根据接收到的用户标识进行可信终端设备的查询时，存在不具有对应的可信终端设备的情况。设备验证模块302将不具备可信终端设备的结果发送至应用程序服务器500的验证码生成模块，能够便于应用程序服务器500能够重新向运营商网络设备发送验证信息的下发请求。
719：应用程序服务器500的验证信息码生成模块将验证信息下发请求发送至运营商网络设备。
其中，验证信息下发请求可以包括验证信息和用户标识，用户标识中可以包括用户预留的手机号码或者用户在注册或登录界面输入的手机号码。
运营商网络设备接收到下发请求后，通过运营商通信网络将验证信息发送到用户标识中的用户预留的手机号码或者用户在注册或登录界面输入的手机号码所在的终端设备。
基于上述方案，可以使得在第二电子设备300未存储有与验证信息的下发请求中携带的用户标识所匹配的可信终端设备标识时，能通过运营商网络设备发送验证信息。以保证用户最终能够收到验证信息。
上述验证码发送的场景均是以用户在应用程序中的账号登录或注册界面触发验证为例进行介绍的。本申请中验证码发送的场景也可以为用户支付、用户转账等任意可触发验证的场景中。
基于上述方案，第二电子设备可以基于应用程序的服务器发送的用户标识确定出第二电子设备中存储的与应用程序的服务器发送的用户标识匹配的目标用户标识，并将应用程序的服务器发送的验证信息发送至目标用户标识对应的可信终端设备，有效确保用户的信息安全。即若一些用户想要输入他人账号或手机号进行他人账号的登录时，第二电子设备也只会将验证信息发送至他人账号或手机号对应的可信终端设备上，而不是直接发送至当前访问应用程序的设备，有效保护他人账号安全。
此外，在目标用户标识所对应的可信终端设备有多个的情况下，可以选择处于与第二电子设备处于连接状态或者处于活跃状态的可信终端设备作为目标可信终端设备，并将验证信息发送至目标可信终端设备。如此，能够进一步确保接收验证信息的终端设备为用户当前正在使用的终端设备，提高验证效率。
另外，本申请实施例提供的验证信息发送方法采用推送通道进行验证信息的发送，相对于通过运营商专属信令通道发送验证信息的方式，能够极大地节约成本。同时，能通过推送通道将验证信息发送至任意可进行互联网连接的设备，而不仅限于手机，增大验证信息发送的设备范围。
可以理解，为了进一步提高用户信息的安全性，防止由于用户可信终端设备发生丢失时，造成用户的验证信息泄露，本申请实施例提供的验证信息发送方法还包括对可信终端设备进行管理。
具体的，图13示出了本申请实施例中第二电子设备300的设备验证模块302对用户注册的可信终端设备进行管理的流程示意图。如图13所示，第二电子设备300的设备验证模块302对用户注册的可信终端设备进行管理的具体方式具体包括：
1301：获取设备验证模块302中存储的可信终端设备标识所对应的可信终端设备最邻近的身份认证时刻与当前时刻之间的时间间隔。
可以理解，确定可信终端设备最邻近的身份认证时刻的方式可以为确定出用户最邻近的对可信终端设备进行PIN解锁、图案解锁、指纹解锁、人脸解锁的时间，或者用户最邻近的登录可信终端设备的设备账号的时间。
1302：判断时间间隔是否大于第一设定时间。
若判断结果为是，即时间间隔大于第一设定时间，则转至1303，进一步判断时间间隔是否大于第二设定时间。
若判断结果为否，即时间间隔小于等于第一设定时间，则转至1305，确定可信终端设备的当前状态为激活状态。
可以理解，第一设定时间大于第二设定时间。例如，其中第一设定时间与第二设定时间可以根据实际需求确定。例如，第一设定时间可以为三天，第二设定时间可以为一周。
1303：判断时间间隔是否大于第二设定时间。
若判断结果为时间间隔小于等于第二设定时间，则转至1306，确定可信终端设备的当前状态为待激活状态。
若判断结果为时间间隔大于第二设定时间，则转至1304，注销可信终端设备，即删除第二电子设备300中存储的可信终端设备标识。
1304：注销可信终端设备。
可以理解，当第二电子设备300判断出可信终端设备当前时刻与最邻近的身份认证时刻之间的时间间隔大于第二设定时间，则可以证明可信终端设备已经长久未被使用或者长久未经过身份认证。可推断可信终端设备存在丢失的可能性，因此，第二电子设备300可注销该可信终端设备，以保护用户信息安全。
1305：确定可信终端设备的当前状态为激活状态。
1306：确定可信终端设备的当前状态为待激活状态。
可以理解，第二电子设备300可以设置处于待激活状态的可信终端设备不能接收验证信息。但第二电子设备300在确定出可信终端设备的当前状态为待激活状态时，可以发送身份认证提示信息至该处于待激活状态的可信终端设备。也可以发送身份认证提示信息至与该处于待激活状态的可信终端设备对应的可信终端设备标识所关联的用户标识对应的其他可信终端设备。其中，身份认证提示信息用于提醒用户进行认证。
基于上述方案，第二电子设备可以基于应用程序的服务器发送的用户标识确定出第二电子设备中存储的与应用程序的服务器发送的用户标识匹配的目标用户标识，并将应用程序的服务器发送的验证信息发送至目标用户标识对应的可信终端设备，有效确保用户的信息安全。即若一些用户想要输入他人账号或手机号进行他人账号的登录时，第二电子设备也只会将验证信息发送至他人账号或手机号对应的可信终端设备上，而不是直接发送至当前访问应用程序的设备，有效保护他人账号安全。
此外，在目标用户标识所对应的可信终端设备有多个的情况下，可以选择处于与第二电子设备处于连接状态或者处于活跃状态的可信终端设备作为目标可信终端设备，并将验证信息发送至目标可信终端设备。如此，能够进一步确保接收验证信息的终端设备为用户当前正在使用的终端设备，提高验证效率。
另外，本申请实施例提供的验证信息发送方法采用推送通道进行验证信息的发送，相对于通过运营商专属信令通道发送验证信息的方式，能够极大地节约成本。同时，能通过推送通道将验证信息发送至任意可进行互联网连接的设备，而不仅限于手机，增大验证信息发送的设备范围。
本申请实施例公开一种电子设备，包括：存储器，用于存储由电子设备的一个或多个处理器执行的指令，以及处理器，是电子设备的一个或多个处理器之一，用于执行上述验证信息发送方法。
本申请实施例公开一种计算机可读存储介质，计算机可读存储介质上存储有指令，该指令在电子设备上执行时，使电子设备执行上述验证信息发送方法。
本申请实施例公开一种计算机程序产品，包括指令，当计算机程序产品在计算机上运行时，使得计算机执行上述验证信息发送方法。
本申请公开的各实施例可以被实现在硬件、软件、固件或这些实现方法的组合中。本申请的实施例可实现为在可编程系统上执行的计算机程序或程序代码，该可编程系统包括至少一个处理器、存储系统(包括易失性和非易失性存储器和/或存储元件)、至少一个输入设备以及至少一个输出设备。
可将程序代码应用于输入指令，以执行本申请描述的各功能并生成输出信息。可以按已知方式将输出信息应用于一个或多个输出设备。为了本申请的目的，处理系统包括具有诸如例如数字信号处理器(DSP)、微控制器、专用集成电路(ASIC)或微处理器之类的处理器的任何系统。
程序代码可以用高级程序化语言或面向对象的编程语言来实现，以便与处理系统通信。在需要时，也可用汇编语言或机器语言来实现程序代码。事实上，本申请中描述的机制不限于任何特定编程语言的范围。在任一情形下，该语言可以是编译语言或解释语言。
在一些情况下，所公开的实施例可以以硬件、固件、软件或其任何组合来实现。所公开的实施例还可以被实现为由一个或多个暂时或非暂时性机器可读(例如，计算机可读)存储介质承载或存储在其上的指令，其可以由一个或多个处理器读取和执行。例如，指令可以通过网络或通过其他计算机可读介质分发。因此，机器可读介质可以包括用于以机器(例如，计算机)可读的形式存储或传输信息的任何机制，包括但不限于，软盘、光盘、光碟、只读存储器(CD-ROMs)、磁光盘、只读存储器(ROM)、随机存取存储器(RAM)、可擦除可编程只读存储器(EPROM)、电可擦除可编程只读存储器(EEPROM)、磁卡或光卡、闪存、或用于利用因特网以电、光、声或其他形式的传播信号来传输信息(例如，载波、红外信号数字信号等)的有形的机器可读存储器。因此，机器可读介质包括适合于以机器(例如，计算机)可读的形式存储或传输电子指令或信息的任何类型的机器可读介质。
在附图中，可以以特定布置和/或顺序示出一些结构或方法特征。然而，应该理解，可能不需要这样的特定布置和/或排序。而是，在一些实施例中，这些特征可以以不同于说明书附图中所示的方式和/或顺序来布置。另外，在特定图中包括结构或方法特征并不意味着暗示在所有实施例中都需要这样的特征，并且在一些实施例中，可以不包括这些特征或者可以与其他特征组合。
需要说明的是，本申请各设备实施例中提到的各单元/模块都是逻辑单元/模块，在物理上，一个逻辑单元/模块可以是一个物理单元/模块，也可以是一个物理单元/模块的一部分，还可以以多个物理单元/模块的组合实现，这些逻辑单元/模块本身的物理实现方式并不是最重要的，这些逻辑单元/模块所实现的功能的组合才是解决本申请所提出的技术问题的关键。此外，为了突出本申请的创新部分，本申请上述各设备实施例并没有将与解决本申请所提出的技术问题关系不太密切的单元/模块引入，这并不表明上述设备实施例并不存在其它的单元/模块。
需要说明的是，在本专利的示例和说明书中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
虽然通过参照本申请的某些优选实施例，已经对本申请进行了图示和描述，但本领域的普通技术人员应该明白，可以在形式上和细节上对其作各种改变，而不偏离本申请的范围。

Claims (21)

  1. 一种验证信息发送方法，其特征在于，应用于电子设备，包括：
    接收到应用程序服务器发送的验证信息下发请求，其中所述验证信息下发请求包括第一用户标识；
    确定出存储的预设对应关系中与所述第一用户标识匹配的第二用户标识，并从所述预设对应关系中获取与所述第二用户标识对应的终端设备标识；其中，所述预设对应关系包括至少一个用户标识与至少一个终端设备标识之间的对应关系，并且所述对应关系中与用户标识对应的终端设备标识用于标识用户的可信终端设备；
    根据预设规则从所述第二用户标识对应的终端设备标识中确定出目标设备标识；
    向所述目标设备标识所标识的目标可信终端设备发送验证信息。
  2. 根据权利要求1所述的验证信息发送方法，其特征在于，所述根据预设规则从所述第二用户标识对应的终端设备标识中确定出目标设备标识；包括：
    确定所述预设对应关系中所述第二用户标识对应的终端设备标识的数量；
    在所述第二用户标识对应的终端设备标识的数量为多个的情况下，确定所述第二用户标识对应的每个终端设备标识所标识的可信终端设备与所述第二电子设备当前的连接状态；
    在确定所述第二用户标识对应的可信终端设备标识所标识的可信终端设备中，存在与所述电子设备当前的连接状态为已连接状态的可信终端设备，则将所述于电子设备当前的连接状态为已连接的可信终端设备作为目标可信终端设备；
    将目标可信终端设备对应的终端设备标识作为目标设备标识。
  3. 根据权利要求2所述的验证信息发送方法，其特征在于，还包括：
    在确定所述第二用户标识对应的可信终端设备标识所标识的可信终端设备中，不存在与所述电子设备当前的连接状态为已连接状态的可信终端设备，则在确定所述第二用户标识对应的可信终端设备标识所标识的可信终端设备中，存在当前状态为活跃状态的可信终端设备的情况下，将所述当前状态为活跃状态的可信终端设备作为目标可信终端设备。
  4. 根据权利要求3所述的验证信息发送方法，其特征在于，确定所述可信终端设备的当前状态为活跃状态的方式包括：当确定所述可信终端设备当前存在正在运行的线程，则确定所述可信终端设备的当前状态为活跃状态。
  5. 根据权利要求2所述的验证信息发送方法，其特征在于，所述根据预设规则从所述第二用户标识对应的终端设备标识中确定出目标设备标识；还包括：
    在所述第二用户标识对应的终端设备标识的数量为一个的情况下，将所述第二用户标识对应的终端设备标识作为目标设备标识。
  6. 根据权利要求2-5任一项所述的验证信息发送方法，其特征在于，所述向所述目标设备标识所标识的目标可信终端设备发送验证信息，包括：
    获取所述目标可信终端设备的路由信息；
    根据所述目标可信终端设备的路由信息建立所述目标可信终端设备与所述电子设备之间的推送通道；
    通过所述推送通道向所述目标可信终端设备发送所述验证信息。
  7. 根据权利要求1-6任一项所述的验证信息发送方法，其特征在于，所述用户标识包括用户账号信 息、手机号码和邮箱地址。
  8. 根据权利要求1-7任一项所述的验证信息发送方法，其特征在于，所述终端设备标识包括终端设备标识号、终端设备名称和终端设备路由信息。
  9. 根据权利要求1所述的验证信息发送方法，其特征在于，所述验证信息由所述应用程序服务器生成，所述验证信息下发请求中包括所述验证信息。
  10. 根据权利要求1所述的验证信息发送方法，其特征在于，所述验证信息由所述电子设备根据所述验证信息下发请求生成；
    所述方法还包括：
    所述电子设备生成所述验证信息后，将所述验证信息发送至所述应用程序服务器。
  11. 根据权利要求1所述的验证信息发送方法，其特征在于，在确定出预设对应关系中不存在与所述第一用户标识匹配的用户标识的情况下，发送所述不存在与所述第一用户标识匹配的用户标识的结果至所述应用程序服务器；
    所述应用程序服务器向所述运营商网络设备发送验证信息下发请求。
  12. 根据权利要求1所述的验证信息发送方法，其特征在于，还包括：获取所述电子设备中存储的终端设备标识所标识的可信终端设备最邻近的身份认证时刻与当前时刻之间的时间间隔；
    在所述时间间隔大于第一设定时间小于第二设定时间的情况下，确定所述终端设备标识所标识的可信终端设备为待激活状态，其中，所述服务器禁止向所述待激活状态的终端设备发送验证信息，所述第二预设时间大于所述第一预设时间；
    在所述时间间隔大于第二设定时间的情况下，注销所述终端设备标识。
  13. 根据权利要求12所述的验证信息发送方法，其特征在于，还包括：在确定所述终端设备标识所标识的可信终端设备为待激活状态的情况下，向所述终端设备标识所标识的可信终端设备发送身份认证提示信息。
  14. 根据权利要求12-13所述的验证信息发送方法，其特征在于，所述身份认证时刻包括终端设备进行解锁认证的时刻。
  15. 一种电子设备，其特征在于，所述电子设备为第一电子设备，所述第一电子设备包括：
    身份认证模块，用于在确定用户为授权注册用户的情况下，向可信终端设备注册模块发送用户标识和终端设备标识的注册请求；
    所述可信终端设备注册模块，用于在接收到所述注册请求的情况下，获取所述用户标识信和所述终端设备标识之间的对应关系，且将所述用户标识和所述终端设备标识之间的对应关系发送至第二电子设备；
    第一应用模块，用于响应于用户的操作，向应用程序服务器发送验证请求，所述验证请求中包括用户标识。
  16. 根据权利要求15所述的电子设备，其特征在于，所述第一电子设备还包括：
    消息接收模块，用于接收验证信息，并控制所述第一电子设备显示所述验证信息。
  17. 根据权利要求16所述的电子设备，其特征在于，所述消息接收模块，用于在验证用户身份通过后，控制所述第一电子设备显示所述验证信息。
  18. 一种电子设备，其特征在于，所述电子设备为第二电子设备，所述第二电子设备包括：
    验证信息接收模块，用于在接收到应用程序服务器发送的验证信息下发请求，将所述验证信息下发请求中携带的第一用户标识发送至设备验证模块，并将所述验证信息下发请求中携带的验证信息发送至 消息推送模块；
    所述设备验证模块，用于确定出存储的预设对应关系中与所述第一用户标识匹配的第二用户标识，从所述预设对应关系中获取与所述第二用户标识对应的终端设备标识；其中，所述预设对应关系包括至少一个用户标识与至少一个终端设备标识之间的对应关系，并且所述对应关系中与用户标识对应的终端设备标识用于标识用户的可信终端设备；
    所述设备验证模块，用于根据预设规则从所述第二用户标识对应的终端设备标识中确定出目标设备标识，并将所述目标设备标识发送至所述消息推送模块；
    所述消息推送模块，用于向所述目标设备标识所标识的目标可信终端设备发送所述验证信息。
  19. 一种电子设备，其特征在于，包括：存储器，用于存储由电子设备的一个或多个处理器执行的指令，以及处理器，是所述电子设备的所述一个或多个处理器之一，用于执行权利要求1-14中任一项所述的验证信息发送方法。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有指令，该指令在电子设备上执行时，使所述电子设备执行权利要求1-14中任一项所述的验证信息发送方法。
  21. 一种计算机程序产品，其特征在于，包括指令，当所述计算机程序产品在计算机上运行时，使得所述计算机执行权利要求1-14任一项所述的验证信息发送方法。
PCT/CN2023/088499 2022-04-15 2023-04-14 一种验证信息发送方法、电子设备及介质 WO2023198208A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210399815.6 2022-04-15
CN202210399815.6A CN116962998A (zh) 2022-04-15 2022-04-15 一种验证信息发送方法、电子设备及介质

Publications (1)

Publication Number Publication Date
WO2023198208A1 true WO2023198208A1 (zh) 2023-10-19

Family

ID=88329096

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088499 WO2023198208A1 (zh) 2022-04-15 2023-04-14 一种验证信息发送方法、电子设备及介质

Country Status (2)

Country Link
CN (1) CN116962998A (zh)
WO (1) WO2023198208A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104869111A (zh) * 2015-04-16 2015-08-26 长安大学 一种终端可信接入认证系统及方法
US20160036800A1 (en) * 2013-04-15 2016-02-04 Visa Europe Limited Method and system for creating a unique identifier
CN106209569A (zh) * 2015-05-04 2016-12-07 腾讯科技（深圳）有限公司 一种企业即时通讯的鉴权方法及装置
CN106548342A (zh) * 2015-09-22 2017-03-29 阿里巴巴集团控股有限公司 一种可信设备确定方法及装置
CN111581616A (zh) * 2020-05-11 2020-08-25 青岛聚好联科技有限公司 一种多端登录控制的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160036800A1 (en) * 2013-04-15 2016-02-04 Visa Europe Limited Method and system for creating a unique identifier
CN104869111A (zh) * 2015-04-16 2015-08-26 长安大学 一种终端可信接入认证系统及方法
CN106209569A (zh) * 2015-05-04 2016-12-07 腾讯科技（深圳）有限公司 一种企业即时通讯的鉴权方法及装置
CN106548342A (zh) * 2015-09-22 2017-03-29 阿里巴巴集团控股有限公司 一种可信设备确定方法及装置
CN111581616A (zh) * 2020-05-11 2020-08-25 青岛聚好联科技有限公司 一种多端登录控制的方法及装置

Also Published As

Publication number Publication date
CN116962998A (zh) 2023-10-27

Similar Documents

Publication Publication Date Title
EP3691215B1 (en) Access token management method, terminal and server
CA2744971C (en) Secure transaction authentication
JP5719871B2 (ja) フィッシング攻撃を防ぐ方法および装置
US7954137B2 (en) Method and approach for linking of devices within a communication system
US9781105B2 (en) Fallback identity authentication techniques
US20100197293A1 (en) Remote computer access authentication using a mobile device
US11978053B2 (en) Systems and methods for estimating authenticity of local network of device initiating remote transaction
KR20210134816A (ko) 전자 토큰 프로세싱
US20220255929A1 (en) Systems and methods for preventing unauthorized network access
JP2002055955A (ja) 本人認証方法および本人認証システム
US11165768B2 (en) Technique for connecting to a service
WO2012004640A1 (en) Transaction authentication
US10951616B2 (en) Proximity-based device authentication
CN110719252A (zh) 用于通过通信信道授权交易的方法、系统和计算机可读媒体
KR101879843B1 (ko) Ip 주소와 sms를 이용한 인증 방법 및 시스템
TWI759908B (zh) 產生授權允許名單的方法與利用其之資安系統
CN100438446C (zh) 接入控制设备、接入控制系统和接入控制方法
WO2023198208A1 (zh) 一种验证信息发送方法、电子设备及介质
KR101980828B1 (ko) 공유계정 인증방법 및 그 장치
CN107846410B (zh) 一种入网验证的方法和装置
KR101879842B1 (ko) Otp를 이용한 사용자 인증 방법 및 시스템
JP7305072B1 (ja) 方法およびシステム
WO2022049753A1 (ja) サービス提供システム、電話受付装置、及び、プログラム
JP2006260454A (ja) 第三者による不正操作の検知システム、及び検知方法
KR20150085167A (ko) 인증서 관리 방법

Legal Events

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

Ref document number: 23787850

Country of ref document: EP

Kind code of ref document: A1