A method, system and related device for cross-device input of an SMS verification code

Abstract

The one or more embodiments of the specification disclose a short message verification code cross-device input method, system and related device, the method comprising: a first user equipment sending a verification request carrying an encryption key to a server corresponding to a target number associated with a target account, so that the server generates a short message verification code based on the verification request, and sends the short message verification code to a second user equipment corresponding to the target number after encrypting the short message verification code using the encryption key, and the second user equipment sends the first user equipment after decrypting the encrypted verification code according to the locally pre-received decryption key. In the process, the plaintext of the short message verification code is not exposed, ensuring the security of the verification, and the decrypted short message verification code is sent to the first user equipment by the second user equipment, and the verification is automatically input on the first user equipment, without the need for manual input by the user, realizing cross-device automatic input of the short message verification code, and improving the security and accuracy of the verification.

Description

Technical Field

[0001] This document relates to the field of communication technology, and in particular to a cross-device input method, system and related apparatus for SMS verification codes. Background Technology

[0002] With the continuous development of communication and electronic technologies, electronic products have brought many conveniences to people, especially in current work, study and life scenarios, where they play a vital role.

[0003] For electronic devices lacking cellular network capabilities, it may be necessary to utilize devices with cellular network capabilities to implement a cross-device verification code input scheme. For example, when registering or logging into an account on a computer, the phone receives and displays a verification code, which the user then enters onto the computer for cross-device verification. Clearly, current cross-device verification methods are cumbersome, requiring manual input by the user, and are less secure and accurate. Summary of the Invention

[0004] The purpose of one or more embodiments of this specification is to provide a method, system and related apparatus for cross-device input of SMS verification codes, so as to realize automatic input of SMS verification codes across devices and improve verification security and accuracy.

[0005] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows:

[0006] Firstly, a cross-device input method for SMS verification codes is proposed, applied to a first user device, the method comprising:

[0007] In response to a user's verification operation for a target account initiated based on a target service, a verification request carrying an encryption key is sent to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and sends the SMS verification code to the second user device corresponding to the target number after encrypting it with the encryption key.

[0008] The system receives an SMS verification code and automatically enters it into a verification box to verify the target service; wherein the SMS verification code is obtained by the second user equipment after decrypting the encrypted verification code using a decryption key.

[0009] Secondly, a cross-device input method for SMS verification codes is proposed, applied to a second user device, the method comprising:

[0010] The server receives an encrypted verification code, wherein the encrypted verification code is an SMS verification code generated by the server based on a verification request sent by the first user device, and is obtained by encrypting it using the encryption key carried in the verification request;

[0011] The encrypted verification code is decrypted using the decryption key, and the decrypted SMS verification code is sent to the first user device so that the first user device can automatically enter the verification box after receiving the SMS verification code to verify the target service.

[0012] Thirdly, a cross-device input device for SMS verification codes is proposed, comprising:

[0013] The sending module is used to respond to a user's verification operation for a target account initiated based on a target service, and send a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and sends the SMS verification code to the second user device corresponding to the target number after encrypting it with the encryption key.

[0014] The receiving module is used to receive SMS verification codes and automatically input them into a verification box to verify the target service; wherein the SMS verification code is obtained by the second user equipment after decrypting the encrypted verification code according to the decryption key.

[0015] Fourthly, a cross-device input device for SMS verification codes is proposed, comprising:

[0016] The receiving module is used to receive an encrypted verification code sent by the server, wherein the encrypted verification code is an SMS verification code generated by the server based on a verification request sent by the first user device, and is obtained by encrypting it with the encryption key carried in the verification request;

[0017] The sending module is used to decrypt the encrypted verification code according to the decryption key, and send the decrypted SMS verification code to the first user equipment, so that the first user equipment can automatically enter the verification box to verify the target service after receiving the SMS verification code.

[0018] Fifthly, a cross-device input system for SMS verification codes is proposed, comprising: a first user device, a second user device, and a server; wherein,

[0019] The first user equipment is used to respond to a user's verification operation for a target account based on a target service, and to send a verification request carrying an encryption key to the server corresponding to the target number associated with the target account.

[0020] The server is configured to receive the verification request, generate an SMS verification code based on the verification request, encrypt the SMS verification code with the encryption key, and send it to the second user device corresponding to the target number.

[0021] The second user equipment is used to receive the encrypted verification code, and decrypt the encrypted verification code according to the decryption key received by this equipment and send it to the first user equipment;

[0022] The first user equipment is also used to receive SMS verification codes and automatically input verification codes into a verification box to verify the target service.

[0023] Sixthly, an electronic device is proposed, comprising:

[0024] Processor; and

[0025] A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the cross-device input method for SMS verification codes as described in the first or second aspect.

[0026] In a seventh aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform the cross-device input method for SMS verification codes described in the first or second aspect.

[0027] As can be seen from the technical solutions provided by one or more embodiments in the above specification, the first user equipment sends a verification request carrying an encryption key to the server corresponding to the target number associated with the target account. The server then generates an SMS verification code based on the verification request, encrypts the SMS verification code using the encryption key, and sends it to the second user equipment corresponding to the target number. The second user equipment decrypts the encrypted verification code using a pre-received decryption key and sends it back to the first user equipment. During this process, the plaintext of the SMS verification code is not exposed, ensuring verification security. Furthermore, by sending the decrypted SMS verification code to the first user equipment via the second user equipment, and automatically inputting the verification code on the first user equipment, manual input by the user is not required, achieving automatic input of the SMS verification code across devices and improving verification security and accuracy. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in one or more embodiments or prior art of this specification, the accompanying drawings used in the description of one or more embodiments or prior art will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 This is a schematic diagram of the architecture of the cross-device input system for SMS verification codes provided in the embodiments of this specification.

[0030] Figure 2 This is one of the schematic diagrams of a cross-device input method for SMS verification codes provided in the embodiments of this specification.

[0031] Figure 3 This is the second schematic diagram of a cross-device input method for SMS verification codes provided in the embodiments of this specification.

[0032] Figure 4 This is a schematic diagram of a cross-device input process for SMS verification codes provided in the embodiments of this specification.

[0033] Figure 5 This is one of the structural schematic diagrams of a cross-device input device for SMS verification codes provided in the embodiments of this specification.

[0034] Figure 6 This is the second structural schematic diagram of a cross-device input device for SMS verification codes provided in the embodiments of this specification.

[0035] Figure 7 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this specification. Detailed Implementation

[0036] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described one or more embodiments are only some embodiments of this specification, and not all embodiments. All other embodiments obtained by those skilled in the art based on one or more embodiments of this specification without creative effort should fall within the protection scope of this document.

[0037] In current cross-device SMS verification code input solutions, the verification code is displayed on a mobile device such as a smartphone, and the user then manually enters it onto a computer or other terminal device for verification to complete registration or login. Clearly, this manual input method is overly reliant on manual operation and is cumbersome. Furthermore, considering that the verification code is displayed on a mobile device, there is a risk of leakage. Therefore, given the aforementioned problems of cumbersome verification input and poor security and accuracy of the verification code, the solution proposed in this application is presented.

[0038] To address the aforementioned issues, this specification proposes a novel cross-device input scheme based on SMS verification codes. The main inventive concept is as follows: A first user device sends a verification request carrying an encryption key to a server corresponding to a target number associated with a target account. The server then generates an SMS verification code based on the request, encrypts the code using the encryption key, and sends it to a second user device corresponding to the target number. The second user device decrypts the encrypted verification code using a pre-received decryption key and sends it back to the first user device. During this process, the plaintext of the SMS verification code is not exposed, ensuring verification security. Furthermore, by sending the decrypted verification code from the second user device to the first user device, and automatically inputting the verification code on the first user device, manual input by the user is eliminated, achieving automatic cross-device input of SMS verification codes and improving verification security and accuracy.

[0039] Reference Figure 1 The diagram shown illustrates the architecture of a cross-device input system for SMS verification codes provided in an embodiment of this specification. This system architecture may include a first user device 102, a second user device 104, and a server 106. The first user device 102 may be a terminal device without cellular network capabilities, such as a computer, tablet, smart wearable device, or other smart terminal. The second user device 104 may be a terminal device with cellular network capabilities, such as a mobile phone or other mobile terminal. The server 106 may be a communication service system deployed by a telecommunications operator, including, for example, a base station and an SMS service platform. In this system architecture, the first user equipment 102 needs to use the second user equipment 104 to verify the input of SMS verification codes across devices. Therefore, when the first user equipment responds to a user's verification operation for a target account based on a target service, it sends a verification request carrying an encryption key to the server 106 corresponding to the target number associated with the target account. The server 106 receives the verification request, generates an SMS verification code based on the verification request, encrypts the SMS verification code with the encryption key, and sends it to the second user equipment 104 corresponding to the target number. In this way, the second user equipment 104 receives the encrypted verification code, decrypts it according to the decryption key received by the device, and sends it to the first user equipment 102. This allows the first user equipment 102 to receive the SMS verification code and automatically enter it into the verification box to verify the target service.

[0040] The following detailed examples illustrate the cross-device input scheme for SMS verification codes.

[0041] Example 1

[0042] Reference Figure 2As shown, this embodiment of the specification provides a cross-device input method for SMS verification codes, applied to a first user device. The method may include the following steps:

[0043] Step 202: In response to the user's verification operation for the target account initiated based on the target service, the first user equipment sends a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and encrypts the SMS verification code with the encryption key before sending it to the second user equipment corresponding to the target number.

[0044] For ease of illustration, the first user device in this embodiment is a computer, but it can also be other smart terminals, which are not limited here. The target service may include registration or login operations performed by the target account on an application, webpage, or mini-program. For example, logging into a social networking application based on the target account, transferring funds on an online banking website based on the target account, or changing a password on a cloud storage mini-program based on the target account. These target service operations can trigger verification of the current operation, for example, verification of the target service can be achieved through cross-device input of SMS verification codes as described in this specification.

[0045] The target account here can be a user account used to log in to an application, webpage, or mini-program. For example, it can be a string composed of one or more combinations of characters, letters, numbers, and special symbols. In the embodiments of this specification, the target account can be associated with a target number; in specific implementations, the target number can be the SIM card number of a second user device. When registering the target account, the target number can be used as registration information to assist in registration, thereby establishing the association between the target account and the target number.

[0046] When the first user equipment responds to a verification operation targeting a target account, it can send a verification request to the server corresponding to the target number associated with the target account. This means it can send a verification request to the server operated and maintained by the second user equipment's carrier to obtain an SMS verification code. The verification request can carry an encryption key and the target number. The encryption key can be a pre-generated fixed key, which can be added to any verification request; alternatively, the encryption key can be randomly generated triggered by the verification operation, so the encryption key carried in each verification request may be different. The target number is used to help the server identify the recipient of the SMS verification code, i.e., the second user equipment.

[0047] In one exemplary scheme, after sending a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, a decryption key corresponding to the encryption key can also be sent to the second user device. The encryption key and the decryption key are randomly generated when the user initiates a verification operation for the target account based on the target service. In other words, after the user initiates a verification operation for the target account based on the target service, the first user device can be triggered to randomly generate an encryption key and a corresponding decryption key. After adding the encryption key to the verification request and sending it to the server corresponding to the target number associated with the target account, or simultaneously, the decryption key corresponding to the encryption key can also be sent to the second user device corresponding to the target number. Thus, after obtaining the encryption key, the server uses it to encrypt the SMS verification code generated for this verification request. And after receiving the encrypted SMS verification code from the server, the second user device uses the decryption key corresponding to the encryption key to decrypt it. This ensures that the SMS verification code is not leaked due to plaintext transmission during transmission, guaranteeing the security of SMS verification code transmission and subsequent verification.

[0048] It should be understood that in the above example scheme, after the second user equipment uses the decryption key to decrypt the encrypted SMS verification code, the decryption key can be deleted and no longer retained, so that the decryption key used by the second user equipment is generated based on the latest verification request each time decryption is performed.

[0049] Another exemplary approach involves generating an encryption key and a decryption key for the target service before the user initiates a verification operation for the target account based on the target service. The decryption key is then bound to the device identifier of the first user device and sent to the second user device. In other words, before initiating a verification operation for the target account, an encryption key and a corresponding decryption key can be generated for the target service in advance. This encryption and decryption key is not generated based on each verification operation but can be updated periodically, and can then be used as a fixed key before the next cycle. Furthermore, during the initial generation or subsequent updates, the decryption key can be bound to the device identifier of the first user device and sent to the second user device. This approach is taken because multiple first user devices and multiple target accounts may be associated with the target number of the second user device. Therefore, the second user device may receive decryption keys from multiple first user devices. To distinguish different target services, the decryption key can be bound to the device identifier of the first user device that initiated the corresponding verification operation to establish an association.

[0050] It should be noted that the encryption and decryption keys involved in this specification can be symmetric or asymmetric keys, and the key generation and key processing algorithms used can be implemented according to existing schemes, without any restrictions.

[0051] Step 204: The first user equipment receives the SMS verification code and automatically enters it into the verification box to verify the target service; wherein, the SMS verification code is obtained by the second user equipment after decrypting the encrypted verification code according to the decryption key.

[0052] Considering that the SMS verification code is not displayed in plaintext on the second user's device, but is instead decrypted and sent directly to the first user's device, where it is automatically entered into the verification box to verify the target service, the SMS verification code will not be displayed on either the first or second user's device during the entire cross-device input process, ensuring that the SMS verification code is not leaked. Furthermore, the code is automatically entered into the verification box on the first user's device during cross-device input, eliminating the need for manual input by the user, reducing input errors, and improving input accuracy and convenience.

[0053] Reference Figure 3 The diagram illustrates a cross-device input method for SMS verification codes provided in an embodiment of this specification, applied to a second user device. The method may include the following steps:

[0054] Step 302: The second user equipment receives an encrypted verification code sent by the server, wherein the encrypted verification code is an SMS verification code generated by the server based on the verification request sent by the first user equipment, and is obtained by encrypting it with the encryption key carried in the verification request.

[0055] After the first user equipment sends a verification request carrying an encryption key to the server, the server can determine the second user equipment that will receive the SMS verification code based on the target number carried in the verification request, and encrypt the SMS verification code according to the encryption key carried in the verification request to obtain the encrypted verification code.

[0056] Step 304: The second user equipment decrypts the encrypted verification code according to the decryption key and sends the decrypted SMS verification code to the first user equipment, so that the first user equipment can automatically enter the verification box after receiving the SMS verification code to verify the target service.

[0057] In fact, before the second user device decrypts the encrypted verification code using the decryption key, the second user device can also receive and save the decryption key sent by the first user device. The decryption key and the corresponding encryption key are randomly generated by the user initiating a verification operation against the target account based on the target service. Furthermore, the second user device can pre-store the association relationship between the first and second user devices linked through the target account. Therefore, when the second user device decrypts the encrypted verification code using the decryption key, it can first determine whether it is associated with the first user device through the target account. If the determination result is yes, it decrypts the encrypted verification code using the decryption key sent by the first user device to obtain the SMS verification code.

[0058] In practice, you can check whether the second user device is associated with the first user device through the target account in the association relationship. If you find this association relationship, you can decrypt the encrypted verification code according to the received decryption key, and then return the decrypted SMS verification code to the first user device that sent the decryption key.

[0059] Another feasible approach is that, before the second user equipment decrypts the encrypted verification code using the decryption key, the second user equipment can receive and store the decryption key sent by the first user equipment, wherein the decryption key carries the device identifier of the first user equipment. Then, when decrypting the encrypted verification code using the decryption key, the decryption keys stored on the device can be traversed to find a decryption key that matches the target service corresponding to the encrypted verification code and whose device identifier matches; based on the found decryption key, the encrypted verification code is decrypted to obtain the SMS verification code.

[0060] In fact, the same encryption key and corresponding decryption key can be configured for different target services on the same first user device. In this way, when iterating through the decryption keys stored on the device, a decryption key that matches the device identifier can be found. Then, the encrypted verification code can be decrypted based on the found decryption key. After that, the decrypted SMS verification code is returned to the first user device that sent the decryption key.

[0061] Furthermore, considering that the first user device may not be held by a legitimate user, security risks may arise when using the above method for cross-device input verification. Therefore, after receiving the SMS verification code, and before sending the SMS verification code to the first user device, the second user device can also perform near-field security verification on itself and the first user device; if the verification is successful, the SMS verification code will be sent to the first user device.

[0062] In the embodiments described in this specification, the near-field security verification may involve verifying whether a first user device and a second user device are within the same account verification domain. For example, biometric features such as fingerprints, voiceprints, irises, and faces can be detected on the first user device to verify whether it is being used by a legitimate user. Alternatively, near-field recognition devices or personal tokens can be used to detect whether the first and second user devices are sufficiently close to verify whether the first user device is being used by a legitimate user.

[0063] Through the above technical solution, the first user device sends a verification request carrying an encryption key to the server corresponding to the target number associated with the target account. The server then generates an SMS verification code based on the verification request, encrypts the SMS verification code using the encryption key, and sends it to the second user device corresponding to the target number. The second user device decrypts the encrypted verification code using a pre-received decryption key and sends it back to the first user device. During this process, the plaintext of the SMS verification code is not exposed, ensuring verification security. Furthermore, by sending the decrypted SMS verification code from the second user device to the first user device, and automatically inputting the verification code on the first user device, manual input by the user is not required, achieving cross-device automatic input of the SMS verification code and improving verification security and accuracy.

[0064] Reference Figure 4 The diagram shown is a schematic flowchart of a cross-device input scheme for SMS verification codes provided in an embodiment of this specification. Figure 4 In this scheme, taking a computer as the first user device, a mobile phone as the second user device, and an SMS platform as the server as an example, after a user registers a user account for the social networking app DG on their computer using their mobile phone number, the mobile phone can store the association between the computer and the mobile phone linked through that user account. When the user logs into the social networking app DG on their computer, the cross-device verification scheme is triggered, and the specific process is as follows:

[0065] Step 402: The computer triggers a verification operation based on the social software DG and randomly generates a key pair.

[0066] The key pair can be asymmetric keys, including an encryption key and a decryption key.

[0067] Step 404: The computer sends a verification request carrying the encryption key to the SMS platform.

[0068] Step 406: The computer sends the decryption key to the mobile phone.

[0069] Step 408: The SMS platform generates an SMS verification code based on the verification request and encrypts it to obtain an encrypted verification code.

[0070] Step 410: The SMS platform sends an encrypted verification code to the mobile phone.

[0071] Step 412: The mobile phone verifies the association between the computer and the mobile phone.

[0072] Step 414: After successful verification, the mobile phone uses the received decryption key to decrypt the encrypted verification code and obtain the SMS verification code.

[0073] Step 416: The mobile phone performs near-field security verification between the device and the computer.

[0074] Step 418: After successful verification, the mobile phone will send the SMS verification code to the computer.

[0075] Step 420: The computer will automatically enter the SMS verification code in the verification box to verify.

[0076] After successful verification, the user successfully logged into the social networking app DG on their computer.

[0077] It should be noted that the user-related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0078] Example 2

[0079] Reference Figure 5 As shown, this is a cross-device input device for SMS verification codes provided in an embodiment of this specification. The device 500 may include:

[0080] The sending module 502 is used to respond to a user's verification operation for a target account based on a target service, and send a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and encrypts the SMS verification code with the encryption key before sending it to the second user device corresponding to the target number.

[0081] The receiving module 504 is used to receive SMS verification codes and automatically input them into a verification box to verify the target service; wherein the SMS verification code is obtained by the second user equipment after decrypting the encrypted verification code according to the decryption key.

[0082] Optionally, as an embodiment, after sending a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, the sending module 502 is further configured to send a decryption key corresponding to the encryption key to the second user equipment, wherein the encryption key and the decryption key are randomly generated by the user initiating a verification operation against the target account based on the target service.

[0083] In one specific implementation of the embodiments of this specification, before the user initiates a verification operation for the target account based on the target service, the sending module 502 is further configured to generate an encryption key and a decryption key for the target service; and bind the decryption key and the device identifier of the first user device to send it to the second user device.

[0084] Reference Figure 6 As shown, this is a cross-device input device for SMS verification codes provided in an embodiment of this specification. The device 600 may include:

[0085] The receiving module 602 is used to receive an encrypted verification code sent by the server, wherein the encrypted verification code is an SMS verification code generated by the server based on a verification request sent by the first user equipment, and is obtained by encrypting it with the encryption key carried in the verification request;

[0086] The sending module 604 is used to decrypt the encrypted verification code according to the decryption key, and send the decrypted SMS verification code to the first user equipment, so that the first user equipment can automatically enter the verification box to verify the target service after receiving the SMS verification code.

[0087] In one specific implementation of an embodiment of this specification, the receiving module 602 is further configured to receive and save a decryption key sent by the first user device; wherein, the decryption key and the corresponding encryption key are randomly generated by the user initiating a verification operation against the target account based on the target service; then, when the sending module 604 decrypts the encrypted verification code according to the decryption key, it is specifically configured to determine whether the device is associated with the first user device through the target account; if the determination result is yes, the encrypted verification code is decrypted according to the decryption key sent by the first user device to obtain an SMS verification code.

[0088] In another specific implementation of the embodiments of this specification, the receiving module 602 is further configured to receive and store the decryption key sent by the first user equipment, wherein the decryption key carries the device identifier of the first user equipment; then, when the sending module 604 decrypts the encrypted verification code according to the decryption key, it is specifically configured to traverse the decryption keys stored in the device, search for a decryption key that matches the target service corresponding to the encrypted verification code and matches the device identifier; and decrypt the encrypted verification code based on the found decryption key to obtain the SMS verification code.

[0089] In another specific implementation of the embodiments of this specification, after receiving the SMS verification code and before sending the SMS verification code to the first user equipment, the sending module 604 is also used to perform near-field security verification on the device and the first user equipment; if the verification is successful, the sending module 604 triggers the sending of the SMS verification code to the first user equipment.

[0090] Through the above technical solution, the first user device sends a verification request carrying an encryption key to the server corresponding to the target number associated with the target account. The server then generates an SMS verification code based on the verification request, encrypts the SMS verification code using the encryption key, and sends it to the second user device corresponding to the target number. The second user device decrypts the encrypted verification code using a pre-received decryption key and sends it back to the first user device. During this process, the plaintext of the SMS verification code is not exposed, ensuring verification security. Furthermore, by sending the decrypted SMS verification code from the second user device to the first user device, and automatically inputting the verification code on the first user device, manual input by the user is not required, achieving cross-device automatic input of the SMS verification code and improving verification security and accuracy.

[0091] Example 3

[0092] Figure 7 This is a schematic diagram of the structure of an electronic device according to one embodiment of this specification. Please refer to it. Figure 7 At the hardware level, the electronic device includes a processor, and optionally also an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include hardware required for other services.

[0093] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0094] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0095] The processor reads the corresponding computer program from non-volatile memory into memory and then executes it, logically forming a cross-device input device for SMS verification codes. The processor executes the program stored in memory and specifically performs the following operations:

[0096] In response to a user's verification operation initiated based on a target service for a target account, a verification request carrying an encryption key is sent to the server corresponding to the target number associated with the target account. This causes the server to generate an SMS verification code based on the verification request, encrypt the SMS verification code using the encryption key, and then send it to the second user device corresponding to the target number. The user device receives the SMS verification code and automatically enters it into a verification box to verify the target service. The SMS verification code is obtained by the second user device decrypting the encrypted verification code using a decryption key. Alternatively,

[0097] The server receives an encrypted verification code, which is an SMS verification code generated by the server based on a verification request sent by a first user device and obtained by encrypting the verification code using the encryption key carried in the verification request. The encrypted verification code is then decrypted using a decryption key, and the decrypted SMS verification code is sent to the first user device so that the first user device can automatically enter the verification code into a verification box to verify the target service.

[0098] The above is as described in this instruction manual. Figure 2 and Figure 3The methods performed by the apparatus disclosed in the illustrated embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in one or more embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in one or more embodiments of this specification can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0099] The electronic device can also perform Figure 2 and Figure 3 The method, and implement the corresponding device in Figure 2 and Figure 3 The functions of the embodiments shown are not described in detail here.

[0100] Of course, in addition to the software implementation, the electronic devices in the embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0101] Example 4

[0102] This specification also provides an embodiment of a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by a portable electronic device including multiple applications, enable the portable electronic device to perform... Figure 2 and Figure 3 The method of the illustrated embodiment is specifically used to perform the following method:

[0103] In response to a user's verification operation initiated based on a target service for a target account, a verification request carrying an encryption key is sent to the server corresponding to the target number associated with the target account. This causes the server to generate an SMS verification code based on the verification request, encrypt the SMS verification code using the encryption key, and then send it to the second user device corresponding to the target number. The user device receives the SMS verification code and automatically enters it into a verification box to verify the target service. The SMS verification code is obtained by the second user device decrypting the encrypted verification code using a decryption key. Alternatively,

[0104] The server receives an encrypted verification code, which is an SMS verification code generated by the server based on a verification request sent by a first user device and obtained by encrypting the verification code using the encryption key carried in the verification request. The encrypted verification code is then decrypted using a decryption key, and the decrypted SMS verification code is sent to the first user device so that the first user device can automatically enter the verification code into a verification box to verify the target service.

[0105] In summary, the above description is merely a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

[0106] The systems, apparatuses, modules, or units described in one or more of the above embodiments may be implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, a computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0107] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0108] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0109] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0110] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

Claims

1. A method for cross-device input of SMS verification codes, applied to a first user device, the method comprising: In response to a user's verification operation for a target account initiated based on a target service, a verification request carrying an encryption key is sent to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and sends the SMS verification code to the second user device corresponding to the target number after encrypting it with the encryption key. The system receives an SMS verification code and automatically enters it into a verification box to verify the target service. The SMS verification code is obtained by the second user device after decrypting the encrypted verification code using a decryption key. The SMS verification code is sent to the first user device after the second user device receives the SMS verification code and before sending it to the first user device, provided that the verification is successful through biometric detection on the first user device. Before the user initiates a verification operation for the target account based on the target service, the method further includes: Generate encryption and decryption keys for the target service; The decryption key and the device identifier of the first user device are bound and sent to the second user device, so that the second user device can traverse the decryption keys stored in its device to find a decryption key that matches the target service corresponding to the encrypted verification code and whose device identifier matches; based on the found decryption key, the encrypted verification code is decrypted to obtain the SMS verification code.

2. The cross-device input method for SMS verification codes as described in claim 1, after sending a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, the method further includes: Send a decryption key corresponding to the encryption key to the second user equipment, wherein the encryption key and the decryption key are randomly generated by the user initiating a verification operation against the target account based on the target service.

3. A method for inputting SMS verification codes across devices, applied to a second user device, the method comprising: The server receives an encrypted verification code, wherein the encrypted verification code is an SMS verification code generated by the server based on a verification request sent by the first user device, and is obtained by encrypting it using the encryption key carried in the verification request; The encrypted verification code is decrypted using the decryption key, and the decrypted SMS verification code is sent to the first user device so that the first user device can automatically enter the verification box after receiving the SMS verification code to verify the target service. After receiving the SMS verification code, and before sending the SMS verification code to the first user device, the method further includes: If the biometrics are detected and verified on the first user device, the SMS verification code will be sent to the first user device. The method further includes: receiving and storing a decryption key sent by a first user equipment, wherein the decryption key carries the device identifier of the first user equipment; The encrypted verification code is then decrypted using the decryption key, specifically including: traversing the decryption keys stored on the device, searching for a decryption key that matches the target service corresponding to the encrypted verification code and whose device identifier matches; and decrypting the encrypted verification code based on the found decryption key to obtain the SMS verification code.

4. The cross-device input method for SMS verification codes as described in claim 3, further comprising: Receive and save the decryption key sent by the first user equipment; wherein the decryption key and the corresponding encryption key are randomly generated by the user initiating a verification operation against the target account based on the target service; The encrypted verification code is then decrypted using the decryption key, specifically including: Determine whether this device is associated with the first user device through the target account; If the determination result is yes, the encrypted verification code is decrypted according to the decryption key sent by the first user equipment to obtain the SMS verification code.

5. A cross-device input device for SMS verification codes, comprising: The sending module is used to respond to a user's verification operation for a target account initiated based on a target service, and send a verification request carrying an encryption key to the server corresponding to the target number associated with the target account, so that the server generates an SMS verification code based on the verification request, and sends the SMS verification code to the second user device corresponding to the target number after encrypting it with the encryption key. The receiving module is used to receive SMS verification codes and automatically input them into a verification box to verify the target service; wherein, the SMS verification code is obtained by the second user equipment after decrypting the encrypted verification code according to the decryption key, and the SMS verification code is sent to the first user equipment after the second user equipment receives the SMS verification code and before sending the SMS verification code to the first user equipment, and the verification is successful through biometrics at the first user equipment. Before the user initiates a verification operation against the target account based on the target service, the sending module is also used to generate an encryption key and a decryption key for the target service; bind the decryption key and the device identifier of the first user device and send them to the second user device, so that the second user device can traverse the decryption keys stored in its own device to find a decryption key that matches the target service corresponding to the encrypted verification code and whose device identifier matches; and decrypt the encrypted verification code based on the found decryption key to obtain the SMS verification code.

6. A cross-device input device for SMS verification codes, comprising: The receiving module is used to receive an encrypted verification code sent by the server, wherein the encrypted verification code is an SMS verification code generated by the server based on a verification request sent by the first user device, and is obtained by encrypting it with the encryption key carried in the verification request; The sending module is used to decrypt the encrypted verification code according to the decryption key and send the decrypted SMS verification code to the first user device so that the first user device can automatically enter the verification box to verify the target service after receiving the SMS verification code; after obtaining the SMS verification code and before sending the SMS verification code to the first user device, if the biometric detection is performed on the first user device and the verification is successful, the sending of the SMS verification code to the first user device is triggered. The receiving module is further configured to receive and store a decryption key sent by the first user equipment, wherein the decryption key carries the device identifier of the first user equipment; then, when the sending module decrypts the encrypted verification code according to the decryption key, it is specifically configured to traverse the decryption keys stored in the device, search for a decryption key that matches the target service corresponding to the encrypted verification code and matches the device identifier; and decrypt the encrypted verification code based on the found decryption key to obtain an SMS verification code.

7. A cross-device input system for SMS verification codes, comprising: The first user equipment, the second user equipment, and the server; among which... The first user equipment is used to respond to a user's verification operation for a target account based on a target service, and to send a verification request carrying an encryption key to the server corresponding to the target number associated with the target account. The server is configured to receive the verification request, generate an SMS verification code based on the verification request, encrypt the SMS verification code with the encryption key, and send it to the second user device corresponding to the target number. The second user equipment is used to receive the encrypted verification code, and decrypt the encrypted verification code according to the decryption key received by this equipment and send it to the first user equipment; The first user equipment is also used to receive SMS verification codes and automatically input verification codes into a verification box to verify the target service; Wherein, after receiving the SMS verification code and before sending the SMS verification code to the first user device, the second user device is also used to trigger sending the SMS verification code to the first user device if the biometrics are detected and verified on the first user device. The first user equipment is further configured to generate an encryption key and a decryption key for the target service before the user initiates a verification operation for the target account based on the target service; and bind the decryption key and the device identifier of the first user equipment and send them to the second user equipment; The second user equipment is further configured to receive and store a decryption key sent by the first user equipment, wherein the decryption key carries the device identifier of the first user equipment; and to decrypt the encrypted verification code according to the decryption key, specifically including: traversing the decryption keys stored in the device, searching for a decryption key that matches the target service corresponding to the encrypted verification code and whose device identifier matches; and decrypting the encrypted verification code based on the found decryption key to obtain an SMS verification code.

8. An electronic device, comprising: processor; as well as A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the cross-device input method for SMS verification codes as described in any one of claims 1-4.

9. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of applications, cause the electronic device to perform the cross-device input method for SMS verification codes according to any one of claims 1-4.

Images