Non-local verification code information authentication and acquisition method and device and readable storage medium

Abstract

The invention provides a non-local verification code information authentication and acquisition method and device and a readable storage medium, and the method comprises the steps: responding to a received request of a target user for obtaining a verification code of a second communication identity through a first communication identity, and verifying whether the second communication identity is matched with the target user; if the second communication identity identifier is matched with the target user, acquiring a verification code of the second communication identity identifier; and sending the verification code of the second communication identity identifier to a terminal corresponding to the first communication identity identifier. The invention provides a non-local verification code information authentication and acquisition method, and the method comprises the steps: enabling a user to request an operator for obtaining a verification code of a second mobile phone number under the condition that the user holds a first mobile phone number, and transmitting the verification code of the second mobile phone number to the first mobile phone number if the operator determines that the second mobile phone number belongs to the user, therefore, the user can authenticate and acquire the non-local verification code information, so that more convenient service experience can be provided for the user.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method, device, and readable storage medium for authenticating and obtaining non-local verification code information. Background Art

[0002] Mobile phone verification codes are typically sent via SMS (Short Message Service), but can also be sent via in-app messaging, voice calls, and other methods. Due to the ubiquity and uniqueness of mobile phone numbers, the verification code sent to the user's registered phone number allows the system to confirm whether the operator is the legitimate owner of the account. Furthermore, mobile phone verification codes can effectively prevent malicious users from abusing accounts through automated scripts or software, such as account manipulation, ticket manipulation, and comment manipulation.

[0003] Normally, obtaining verification code information requires directly using the corresponding mobile phone number, which requires the user to hold a terminal device loaded with the mobile phone card when receiving the verification code.

[0004] However, users sometimes need to obtain verification code information of non-local numbers. Therefore, how to authenticate and obtain non-local verification code information becomes a problem that needs to be solved. Summary of the Invention

[0005] The technical problem to be solved by this application is to address the above-mentioned deficiencies in the prior art and provide a non-local verification code information authentication and acquisition method, device and readable storage medium to solve the problems existing in the prior art.

[0006] In a first aspect, the present application provides a method for authenticating and obtaining non-local verification code information, which is applied to an operator server, and the method includes:

[0007] S1. In response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, verify whether the second communication identity matches the target user;

[0008] S2. If the second communication identity matches the target user, obtain a verification code for the second communication identity;

[0009] S3. Send the verification code of the second communication identity to the terminal corresponding to the first communication identity.

[0010] In some embodiments, S1 includes:

[0011] In response to receiving a request from a target user to obtain a verification code for a second communication identity through a first communication identity, determining whether a format of the request matches a preset format, wherein the preset format is used to obtain non-local verification code information;

[0012] If the format of the request matches the preset format, verify whether the second communication identity matches the target user.

[0013] In some embodiments, verifying whether the second communication identity matches the target user includes:

[0014] Determining whether the operator of the second communication identity identifier is consistent with the operator of the first communication identity identifier;

[0015] If the operator of the second communication identity is the same as the operator of the first communication identity, verify whether the second communication identity belongs to the target user.

[0016] In some embodiments, further comprising:

[0017] If the operator of the second communication identity identifier is inconsistent with the operator of the first communication identity identifier, an authentication request is sent to the operator of the second communication identity identifier to verify whether the second communication identity identifier belongs to the target user, and an authentication result sent by the operator of the second communication identity identifier is received.

[0018] In some embodiments, further comprising:

[0019] If the second communication identity does not match the target user, sending an authorization request to the terminal corresponding to the second communication identity;

[0020] After obtaining authorization from the second communication identity, a verification code of the second communication identity is obtained.

[0021] In some embodiments, further comprising:

[0022] If the second communication identity identifier is not authorized, a response message indicating that the verification code acquisition failed is sent to the terminal corresponding to the first communication identity identifier.

[0023] In some embodiments, the first communication identity identifier and the second communication identity identifier include at least one of a mobile communication terminal identifier, a mobile phone user identifier, an email account identifier, and a network communication address.

[0024] In a second aspect, the present application provides a non-local verification code information authentication and acquisition device, which is applied to an operator server, and the device includes:

[0025] an identity authentication module configured to, in response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, verify whether the second communication identity matches the target user;

[0026] a verification code acquisition module configured to acquire a verification code of the second communication identity if the second communication identity matches the target user;

[0027] The verification code sending module is configured to send the verification code of the second communication identity to the terminal corresponding to the first communication identity.

[0028] In a third aspect, the present application provides a non-local verification code information authentication and acquisition device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the non-local verification code information authentication and acquisition method described in the first aspect above.

[0029] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the non-local verification code information authentication and acquisition method described in the first aspect above is implemented.

[0030] The present application provides a method, device, and readable storage medium for authenticating and obtaining non-local verification code information. The method comprises: in response to receiving a request from a target user to obtain a verification code for a second communication identity through a first communication identity, verifying whether the second communication identity matches the target user; if the second communication identity matches the target user, obtaining a verification code for the second communication identity; and sending the verification code for the second communication identity to the terminal corresponding to the first communication identity. The present application provides a method for authenticating and obtaining non-local verification code information. When a user holds a first mobile phone number, they can request a verification code for a second mobile phone number from an operator. If the operator determines that the second mobile phone number belongs to the user, the operator sends the verification code for the second mobile phone number to the first mobile phone number, allowing the user to authenticate and obtain non-local verification code information, thereby providing a more convenient service experience for the user. The technical solution of the present application allows users to remotely obtain verification codes for non-local mobile phone numbers, facilitating the management of multiple mobile phone numbers. In addition, the present application provides an authorization mechanism for other people's mobile phone numbers to ensure the legitimacy and integrity of verification code acquisition. In addition, the technical solution of the present application is compatible with existing verification code acquisition processes, is easy to implement, and does not affect the existing user experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] Figure 1 A flowchart of a non-local verification code information authentication and acquisition method provided in an embodiment of the present application;

[0033] Figure 2 This is a specific application example diagram of the technical solution of this application;

[0034] Figure 3 A schematic diagram of the structure of a non-local verification code information authentication and acquisition device provided in an embodiment of the present application;

[0035] Figure 4 A schematic diagram of the structure of another non-local verification code information authentication and acquisition device provided in an embodiment of the present application.

[0036] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0037] In order to enable those skilled in the art to better understand the technical solution of the present application, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0038] It should be understood that the specific embodiments and drawings described herein are only used to explain the present application, rather than to limit the present application.

[0039] It can be understood that, in the absence of conflict, the various embodiments and features in the embodiments of the present application can be combined with each other.

[0040] It will be understood that, for the sake of ease of description, the drawings of this application only show the parts related to this application, while the parts not related to this application are not shown in the drawings.

[0041] It can be understood that each unit and module involved in the embodiments of the present application may correspond to only one physical structure, or may be composed of multiple physical structures, or multiple units and modules may be integrated into one physical structure.

[0042] It can be understood that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.

[0043] It is understandable that, in the absence of conflict, the functions and steps marked in the flowcharts and block diagrams of the present application may occur in an order different from that marked in the drawings.

[0044] It is understood that the flowcharts and block diagrams of the present application illustrate the possible architectures, functions, and operations of the systems, devices, equipment, and methods according to the various embodiments of the present application. Each box in the flowchart or block diagram may represent a unit, module, program segment, or code, which contains executable instructions for implementing the specified functions. Moreover, each box or combination of boxes in the block diagram and flowchart may be implemented by a hardware-based system that implements the specified functions, or by a combination of hardware and computer instructions.

[0045] It can be understood that the units and modules involved in the embodiments of the present application can be implemented by software or hardware, for example, the units and modules can be located in a processor.

[0046] Currently, the existing verification code acquisition methods have the following problems:

[0047] 1. Typically, obtaining a SMS verification code requires directly using the corresponding mobile phone number, which limits the user's flexibility when they lack a device.

[0048] 2. It is inconvenient to manage multiple numbers, and you need to have real-time access to the relevant mobile phone number devices.

[0049] 3. Security issue: If your mobile phone number is lent or lost, the verification code may be obtained by others.

[0050] This application provides a method for authenticating and obtaining non-local verification code information. When a user holds a first mobile phone number, he or she can request the operator to obtain the verification code of a second mobile phone number. If the operator determines that the second mobile phone number belongs to the user, the verification code of the second mobile phone number will be sent to the first mobile phone number, so that the user can authenticate and obtain non-local verification code information, thereby providing users with a more convenient service experience.

[0051] The technical solution of this application allows users to remotely obtain verification codes for non-local mobile phone numbers, making it easier to manage multiple mobile phone numbers. Furthermore, this application provides an authorization mechanism for other people's mobile phone numbers, ensuring the legitimacy and integrity of verification code acquisition. Furthermore, the technical solution of this application is compatible with existing verification code acquisition processes, making it easy to implement and not impacting the existing user experience.

[0052] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0053] The present application provides a method for authenticating and obtaining non-local verification code information. The working process of the method can be implemented by electronic devices, such as computers, handheld smart terminals, etc. For the convenience of explanation, the embodiments of the present application are described with the method execution subject being a computer.

[0054] Figure 1 A schematic diagram of a non-native verification code information authentication and acquisition method provided in an embodiment of the present application, such as Figure 1 As shown, this application provides a non-local verification code information authentication and acquisition method, which is applied to the operator server. The method includes S1-S3, which are as follows:

[0055] S1. In response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, verify whether the second communication identity matches the target user;

[0056] In some embodiments, the first communication identity identifier and the second communication identity identifier include at least one of a mobile communication terminal identifier, a mobile phone user identifier, an email account identifier, and a network communication address, such as a mobile phone number, an email address, or other identifiable user identity information.

[0057] In this step, after receiving a request from the target user using their first communication identity to obtain a verification code for the second communication identity associated with the target user, the operator's server performs the following steps to complete the verification process: First, the server parses the target user's request and identifies the first communication identity provided by the target user, which is usually the user's mobile phone number, email address, or other identifiable user information. The server then queries an internal database or calls the corresponding authentication interface to verify whether the target user has permission or has registered the corresponding second communication identity.

[0058] After confirming the validity of the first communication identity, the server will further verify that the second communication identity requested by the target user is legitimate and matches the target user's account information. This process may involve comparing the user's account information, checking the identity's registration status, and confirming whether the second communication identity is authorized to receive verification codes.

[0059] It can be understood that since the execution entity of this application is the operator server, the operator server corresponds to the operator corresponding to the first communication identity identifier.

[0060] In some embodiments, S1 includes: in response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, determining whether a format of the request matches a preset format, wherein the preset format is used to obtain non-local verification code information; if the format of the request matches the preset format, verifying whether the second communication identity matches the target user.

[0061] Specifically, when a carrier server receives a request from a target user using their first communication identity to obtain a verification code for their second communication identity, a verification process is also included. First, the carrier server performs a preliminary analysis of the incoming request to determine whether the format of the request conforms to the system's pre-set standard format requirements for obtaining non-native verification code information. This step includes, but is not limited to, checking the request structure, parameter types, parameter order, character encoding, and any encryption or signature information to ensure the integrity and standardization of the request.

[0062] For example, the carrier server will do the following:

[0063] (1) Check whether the request contains all necessary information fields, such as the first communication identity, the type of the second communication identity, the request timestamp, etc.

[0064] (2) Verify that the data format in the request complies with predetermined rules, such as whether a mobile phone number follows a specific international format and whether an email address has the correct domain format.

[0065] (3) Confirm whether the request uses the correct protocol and version and complies with the security communication standards specified by the operator's server.

[0066] If, after the above steps, the operator server confirms that the format of the request exactly matches the preset format, it will proceed to the next step of identity verification.

[0067] In some embodiments, verifying whether the second communication identity matches the target user includes:

[0068] Determining whether the operator of the second communication identity identifier is consistent with the operator of the first communication identity identifier;

[0069] If the operator of the second communication identity is the same as the operator of the first communication identity, verify whether the second communication identity belongs to the target user.

[0070] In some embodiments, further comprising:

[0071] If the operator of the second communication identity identifier is inconsistent with the operator of the first communication identity identifier, an authentication request is sent to the operator of the second communication identity identifier to verify whether the second communication identity identifier belongs to the target user, and an authentication result sent by the operator of the second communication identity identifier is received.

[0072] Specifically, when the operator server processes the target user's request to obtain the second communication identity verification code through the first communication identity, it will perform the following detailed judgment and operation steps:

[0073] First, the operator server analyzes and extracts relevant information of the second communication identity to determine the operator to which it belongs. This step involves identifying the number segment, domain name suffix or other identification information that can indicate the operator of the identity.

[0074] The operator's server will then compare the following:

[0075] 1. Determine whether the operator of the second communication identity is the same as the operator of the first communication identity, that is, whether both belong to the operator represented by the operator server itself.

[0076] 2. If the judgment result shows that the operator of the second communication identity is the same as the operator of the first communication identity, the operator server will continue to perform the following operations:

[0077] (1) Query the internal database to verify whether the second communication identity is actually registered under the target user's account.

[0078] (2) Confirm the use authority of the second communication identity to ensure that it has not been stolen or abused.

[0079] (3) If the verification is successful, the operator server will generate a verification code and send it to the target user through the appropriate channel to complete the identity verification process.

[0080] 3. If the operator of the second communication identity is different from the operator of the first communication identity, the operator server will take the following measures:

[0081] (1) Construct an identity authentication request, which includes the target user's first communication identity, second communication identity, and necessary verification information.

[0082] (2) Sending the identity authentication request to the operator of the second communication identity through the cross-operator communication interface or protocol.

[0083] (3) Waiting for and receiving the identity authentication result returned by the operator of the second communication identity identifier.

[0084] During this process, the carrier server must ensure communication security and data privacy, potentially using encrypted transmission and identity authentication mechanisms. It must promptly process identity verification requests and, upon receiving the verification results, take appropriate action based on the results, such as sending a verification code or rejecting the request. It must also log the entire verification process for subsequent audits and problem tracking.

[0085] Through the above process, the operator server can not only ensure the accuracy of identity authentication, but also handle cross-operator authentication requests, thereby providing more flexible and secure communication services.

[0086] S2. If the second communication identity matches the target user, obtain a verification code for the second communication identity;

[0087] If the second communication identity matches the target user and verification is successful, the operator server obtains a verification code for the second communication identity. If the operator of the second communication identity is the same as the operator of the first communication identity, the verification code may be generated by the operator server. If the operator of the second communication identity is different from the operator of the first communication identity, the verification code may be generated by the operator of the second communication identity.

[0088] The verification code is usually a short sequence of numbers with a certain validity period to prevent reuse and ensure transaction security.

[0089] After generating the verification code, the carrier server or the operator of the second communication identity will send it to the second communication identity provided by the target user via SMS, email, or other communication channels. At the same time, the carrier server or the operator of the second communication identity will record relevant information about the verification code, including the verification code itself, generation time, validity period, and the association record with the target user and the second communication identity, to facilitate subsequent verification and audit.

[0090] S3. Send the verification code of the second communication identity to the terminal corresponding to the first communication identity.

[0091] After obtaining the verification code for the second communication identity, the operator server will send the verification code for the second communication identity to the terminal corresponding to the target user's first communication identity through an appropriate communication channel, such as Short Message Service (SMS), email service, or other instant messaging service. During the transmission process, the operator server will ensure the encryption of the communication and the privacy of the data to prevent the verification code from being intercepted or leaked during transmission. Once the verification code is successfully sent, the operator server will provide a confirmation message to the target user's terminal, and at the same time remind the user to check for the verification code and complete the subsequent identity verification process according to the instructions.

[0092] In addition, the operator's server will also monitor the sending status of the verification code, including whether it is sent successfully, whether it is received, and whether there is a sending delay, and take corresponding measures when necessary, such as resending the verification code or providing other auxiliary verification methods.

[0093] After receiving the verification code sent by the operator server, the terminal corresponding to the first communication identity completes the login by inputting the second communication identity and the corresponding verification code.

[0094] Through the above steps, the operator server not only ensures the secure issuance of verification codes, but also provides target users with a convenient identity verification experience, thereby improving the overall quality of user services while ensuring account security.

[0095] In some embodiments, the method further includes: if the second communication identity identifier does not match the target user, sending an authorization request to a terminal corresponding to the second communication identity identifier; and after obtaining authorization from the second communication identity identifier, obtaining a verification code of the second communication identity identifier.

[0096] Specifically, if the verification process finds that the second communication identity does not match the target user, the operator server constructs an authorization request message. This message will clearly indicate the identity mismatch and request confirmation or authorization from the terminal user corresponding to the second communication identity. The authorization request message will be sent to the terminal corresponding to the second communication identity through an appropriate communication channel, such as a text message, email, or app push notification, informing the user of the verification request regarding their identity and explaining the reason for the user's authorization. After receiving the authorization request, the terminal corresponding to the second communication identity can choose whether to authorize.

[0097] Once the operator server receives an authorization response from the second communication identity (for example, the terminal corresponding to the second communication identity replies to a specific SMS message, clicks a link in an email, or confirms through the authorization interface within the application, etc.), the server will verify the validity of the authorization. After confirming that the authorization is valid, it will obtain the verification code of the second communication identity.

[0098] Through the above process, the operator server can not only handle identity mismatch situations, but also ensure the legitimacy and accuracy of identity authentication through user authorization, thereby providing a more flexible and user-friendly service experience while ensuring the security of user accounts.

[0099] In some embodiments, the method further includes: if the second communication identity identifier is not authorized, sending a response message indicating that the verification code acquisition failed to the terminal corresponding to the first communication identity identifier.

[0100] Specifically, if the second communication identity is not authorized, the operator server will refuse to send the verification code and return a corresponding response message of verification code acquisition failure to the target user. Optionally, further security measures can also be taken, such as temporarily locking the account or notifying the user to conduct a security check.

[0101] Through the above process, the operator server effectively maintains the security of user accounts and ensures the normal operation of communication services.

[0102] Figure 2 This is a specific application example diagram of the technical solution of this application, such as Figure 2 As shown, taking obtaining a SMS verification code from a non-local mobile phone number as an example, the following steps are mainly included:

[0103] 1. User A uses their phone number Y to send a text message containing a specific command to the operator to request a verification code from number X.

[0104] 2. The operator verifies whether the ownership of number X matches the identity of user A.

[0105] 3. If number X belongs to user A, send the verification code directly to number Y;

[0106] If not, send an authorization request to number X.

[0107] 4. After number X user authorizes, the operator sends a verification code to number Y.

[0108] 5. User A enters number X and verification code in the designated APP or H5 interface to complete login.

[0109] The present application provides a method for authenticating and obtaining non-native verification code information. When a user holds a first mobile phone number, he can request the operator to obtain the verification code of the second mobile phone number. If the operator determines that the second mobile phone number belongs to the user, the verification code of the second mobile phone number will be sent to the first mobile phone number, so that the user can authenticate and obtain the non-native verification code information, thereby providing users with a more convenient service experience. The technical solution of the present application allows users to remotely obtain the verification code of a non-native mobile phone number, which is convenient for managing multiple mobile phone numbers. In addition, the present application provides an authorization mechanism for other people's mobile phone numbers to ensure the legitimacy and completeness of obtaining verification codes. In addition, the technical solution of the present application is compatible with the existing verification code acquisition process, is easy to implement and does not affect the existing user experience.

[0110] It should be understood that, although the various steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they may be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times, and their execution order is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of sub-steps or stages of other steps.

[0111] Figure 3 A schematic diagram of a non-local verification code information authentication and acquisition device provided in an embodiment of the present application, such as Figure 3 As shown, the present application provides a non-local verification code information authentication and acquisition device, which is applied to an operator server, and the device includes:

[0112] an identity authentication module 11 configured to, in response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, verify whether the second communication identity matches the target user;

[0113] a verification code acquisition module 12, configured to acquire a verification code of the second communication identity if the second communication identity matches the target user;

[0114] The verification code sending module 13 is configured to send the verification code of the second communication identity to the terminal corresponding to the first communication identity.

[0115] Regarding the limitation of the non-local verification code information authentication and acquisition device, reference may be made to the limitation of the non-local verification code information authentication and acquisition method in the above embodiments of this application, which will not be repeated in this embodiment.

[0116] Figure 4 Another schematic diagram of the non-local verification code information authentication and acquisition device provided in the embodiment of the present application is as follows Figure 4 As shown, in some embodiments, the present application provides a non-local verification code information authentication and acquisition device, including a memory 22 and a processor 21, the memory stores a computer program, and the processor is configured to run the computer program to execute the non-local verification code information authentication and acquisition method in the above-mentioned embodiments of the present application.

[0117] The memory is connected to the processor, the memory may be a flash memory, a read-only memory or other memory, and the processor may be a central processing unit or a single-chip microcomputer.

[0118] In some embodiments, the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the non-local verification code information authentication and acquisition method in the above-mentioned embodiments of the present application is implemented.

[0119] The computer-readable storage medium includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0120] It is understood that the above embodiments are merely exemplary embodiments for illustrating the principles of the present application, and the present application is not limited thereto. Those skilled in the art may make various modifications and improvements without departing from the spirit and substance of the present application, and such modifications and improvements are also considered to be within the scope of protection of the present application.

Claims

1. A method for authenticating and obtaining non-local verification code information, characterized in that: Applied to an operator server, the method includes: S1, in response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, verifying whether the second communication identity matches the target user; S2. If the second communication identity matches the target user, obtain a verification code of the second communication identity; S3. Send the verification code of the second communication identity to the terminal corresponding to the first communication identity.

2. The non-local verification code information authentication and acquisition method according to claim 1, characterized in that: S1, including: In response to receiving a request from a target user to obtain a verification code of a second communication identity through a first communication identity, determining whether a format of the request matches a preset format, wherein the preset format is used to obtain non-local verification code information; If the format of the request matches the preset format, verify whether the second communication identity matches the target user.

3. The non-local verification code information authentication and acquisition method according to claim 2, characterized in that: Verifying whether the second communication identity matches the target user includes: Determining whether the operator of the second communication identity is consistent with the operator of the first communication identity; If the operator of the second communication identity is the same as the operator of the first communication identity, verify whether the second communication identity belongs to the target user.

4. The non-local verification code information authentication and acquisition method according to claim 3, characterized in that: Also includes: If the operator of the second communication identity is inconsistent with the operator of the first communication identity, an identity authentication request is sent to the operator of the second communication identity to verify whether the second communication identity belongs to the target user, and an identity authentication result sent by the operator of the second communication identity is received.

5. The non-local verification code information authentication and acquisition method according to claim 1, characterized in that: Also includes: If the second communication identity does not match the target user, sending an authorization request to the terminal corresponding to the second communication identity; After obtaining authorization from the second communication identity, a verification code of the second communication identity is obtained.

6. The non-local verification code information authentication and acquisition method according to claim 5, characterized in that: Also includes: If the second communication identity is not authorized, a response message indicating that the verification code acquisition failed is sent to the terminal corresponding to the first communication identity.

7. The non-local verification code information authentication and acquisition method according to any one of claims 1 to 6, characterized in that: The first communication identity identifier and the second communication identity identifier include at least one of a mobile communication terminal identifier, a mobile phone user identifier, an email account identifier, and a network communication address.

8. A non-local verification code information authentication and acquisition device, characterized in that: Applied to an operator server, the device comprises: an identity authentication module, configured to verify whether the second communication identity matches the target user in response to receiving a request from the target user to obtain a verification code of the second communication identity through the first communication identity; a verification code acquisition module, configured to acquire a verification code of the second communication identity if the second communication identity matches the target user; A verification code sending module is configured to send the verification code of the second communication identity to a terminal corresponding to the first communication identity.

9. A non-local verification code information authentication and acquisition device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to implement the non-local verification code information authentication and acquisition method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the non-local verification code information authentication and acquisition method according to any one of claims 1 to 7 is implemented.

Images