Short message verification code sending method and device, equipment and medium

Abstract

The present disclosure relates to a short message verification code sending method, device, equipment and medium. The short message verification code sending method comprises: receiving a short message sending request, the short message sending request comprising a request parameter; in the case that the request parameter passes parameter verification, generating a short message verification code and saving the short message verification code in a distributed cache server cluster; determining a target cache server in the distributed cache server cluster and sending the short message verification code through the target cache server by calling a first service interface. According to the embodiment of the present disclosure, the situation that sending fails due to unstable interface can be avoided, and the user experience is improved.

Description

Technical Field

[0001] This disclosure relates to the field of information processing technology, and in particular to a method, apparatus, device and medium for sending SMS verification codes. Background Technology

[0002] With the rapid development of the internet, SMS verification codes are being used more and more widely. When a user logs into a website or software application (APP), they are usually required to verify their identity via SMS verification code to ensure that the login is performed by the user themselves.

[0003] In related technologies, SMS verification codes can be sent by calling third-party interfaces, such as Tencent Cloud Platform SMS, Alibaba Cloud, etc. However, when the third-party interface is unstable, such as due to network fluctuations, SMS verification code sending may fail, causing users to be unable to receive SMS verification codes in a timely manner, thus affecting user experience. Summary of the Invention

[0004] To address the aforementioned technical problems, this disclosure provides a method, apparatus, device, and medium for sending SMS verification codes.

[0005] Firstly, this disclosure provides a method for sending SMS verification codes, including:

[0006] Receive SMS sending requests, which include request parameters;

[0007] If the request parameters pass the parameter validation, an SMS verification code is generated and stored in the distributed cache server cluster.

[0008] In the distributed cache server cluster, the target cache server is determined, and the first service interface is called through the target cache server to send the SMS verification code.

[0009] Secondly, this disclosure provides a device for sending SMS verification codes, including:

[0010] The first receiving module is used to receive SMS sending requests, which include request parameters.

[0011] The first generation module is used to generate an SMS verification code when the request parameters pass the parameter validation, and to store the SMS verification code in a distributed cache server cluster.

[0012] The first sending module is used to determine the target cache server in the distributed cache server cluster, and send the SMS verification code by calling the first service interface through the target cache server.

[0013] Thirdly, this disclosure provides a device for sending SMS verification codes, including:

[0014] processor;

[0015] Memory, used to store executable instructions;

[0016] The processor is used to read executable instructions from memory and execute the executable instructions to implement the SMS verification code sending method of the first aspect.

[0017] Fourthly, this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the SMS verification code sending method of the first aspect.

[0018] The technical solution provided in this disclosure has the following advantages compared with the prior art:

[0019] The SMS verification code sending method, apparatus, device, and medium of this disclosure are capable of receiving an SMS sending request, which includes request parameters. Then, if the request parameters pass parameter validation, an SMS verification code is generated and stored in a distributed cache server cluster. Finally, a target cache server is determined within the distributed cache server cluster, and the SMS verification code is sent by calling a first service interface through the target cache server. Therefore, upon receiving an SMS sending request, the target cache server can be determined first within the distributed cache server cluster, and the SMS verification code can be sent by calling the first service interface through the target cache server. This allows for the selection of a normal service interface for sending, thus avoiding sending failures due to interface instability and improving user experience. Attached Figure Description

[0020] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0021] Figure 1 A flowchart illustrating a method for sending SMS verification codes provided in this embodiment of the present disclosure;

[0022] Figure 2 This is a schematic diagram of the structure of a text message verification code sending device provided in an embodiment of the present disclosure;

[0023] Figure 3 This is a schematic diagram of the structure of a text message verification code sending device provided in an embodiment of the present disclosure. Detailed Implementation

[0024] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0025] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0026] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0027] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0028] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0029] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0030] To address the aforementioned problems, this disclosure provides a method, apparatus, device, and medium for sending SMS verification codes. The following is a detailed description... Figure 1 The method for sending SMS verification codes provided in this disclosure will be described in detail.

[0031] Figure 1 A flowchart illustrating a method for sending SMS verification codes according to an embodiment of this disclosure is shown.

[0032] In this embodiment of the disclosure, the SMS verification code sending method can be executed by a server device. For example, the server device can be a server or server cluster that includes storage and computing functions.

[0033] like Figure 1 As shown, the method for sending SMS verification codes may include the following steps.

[0034] S110. Receive SMS sending request. The SMS sending request includes request parameters.

[0035] In this embodiment of the disclosure, the server device can receive SMS sending requests.

[0036] Optionally, the SMS sending request can be a request that requires sending an SMS verification code. For example, when a user logs in or accesses an app, they need to authenticate their identity via an SMS verification code. In this case, the user can send an SMS sending request to the server device through their terminal, and the server device can receive the SMS sending request.

[0037] Alternatively, SMS verification codes can be an effective verification code system that sends verification codes to a terminal.

[0038] Optionally, the SMS sending request may include request parameters. These request parameters may include a mobile phone number parameter and a country code parameter.

[0039] Specifically, a user can send an SMS sending request to a server device through a terminal. The server device can receive the SMS sending request, which may include request parameters.

[0040] S120. If the request parameters pass the parameter validation, generate an SMS verification code and store the SMS verification code in the distributed cache server cluster.

[0041] In this embodiment of the disclosure, after receiving an SMS sending request, the server device can generate an SMS verification code if the request parameters pass the parameter verification, and store the SMS verification code in a distributed cache server cluster.

[0042] Optionally, parameter validation can be used to verify the accuracy of the request parameters.

[0043] Optionally, a distributed cache server cluster can be a cluster consisting of multiple cache servers deployed in a distributed manner. For example, the cache server can be a cache server for a remote dictionary service (Redis).

[0044] Specifically, after receiving an SMS sending request, the server device can perform parameter validation on the request parameters in the SMS sending request, and if the request parameters pass the parameter validation, generate an SMS verification code, such as a randomly generated 6-digit numeric verification code, and store the SMS verification code in a distributed cache server cluster.

[0045] S130. Determine the target cache server in the distributed cache server cluster, and send the SMS verification code by calling the first service interface through the target cache server.

[0046] In this embodiment of the disclosure, the server device can determine the target cache server in the distributed cache server cluster, and send the SMS verification code by calling the first service interface through the target cache server.

[0047] Optionally, the target cache server can be a cache server used to send SMS verification codes.

[0048] Optionally, the first service interface can be a service interface for sending SMS verification codes.

[0049] Specifically, the server device can determine the target cache server from multiple cache servers in the distributed cache server cluster. For example, the server device can dynamically sense multiple cache servers in real time and select a cache server that is working properly as the target cache server; or the server device can perform load balancing on multiple cache servers and select a cache server with a lower load as the target cache server; or when the selected cache server fails, a suitable target cache server can be selected from the remaining cache servers, etc. After determining the target cache server, the first service interface can be determined from multiple corresponding service interfaces through the target cache server, and the SMS verification code can be sent through the first service interface. For specific implementation methods, please refer to the following text.

[0050] Therefore, in this embodiment of the present disclosure, an SMS sending request can be received. The SMS sending request includes request parameters. Then, if the request parameters pass parameter validation, an SMS verification code is generated and stored in a distributed cache server cluster. Finally, a target cache server is determined in the distributed cache server cluster, and the SMS verification code is sent by calling the first service interface through the target cache server. Thus, after receiving an SMS sending request, the target cache server can be determined in the distributed cache server cluster first, and the SMS verification code can be sent by calling the first service interface through the target cache server. That is, a normal service interface can be selected for sending, thereby avoiding the situation where sending fails due to interface instability and improving user experience.

[0051] Optionally, after S110, the SMS verification code sending method may further include: performing a first parameter verification on the request parameters; and performing a second parameter verification on the request parameters if the request parameters pass the first parameter verification.

[0052] In this embodiment of the disclosure, after receiving the SMS sending request, the server device can perform a first parameter verification on the request parameters.

[0053] Optionally, the first parameter verification can be a preliminary verification.

[0054] Specifically, after receiving an SMS sending request, the server device can perform a first parameter validation on the request parameters. For example, the server device can first perform a first parameter validation on the mobile phone number parameter in the request parameters through the front-end page, such as determining whether the number of mobile phone numbers is the preset number (11 digits for Chinese mobile phone numbers and 10 digits for foreign mobile phone numbers). The server device can also perform a first parameter validation on the country code parameter in the request parameters through the front-end page, such as determining whether the code length corresponding to the country code parameter is correct, etc., without limitation.

[0055] Furthermore, after the server device performs the first parameter validation on the request parameters, if the request parameters pass the first parameter validation, it can then perform the second parameter validation on the request parameters.

[0056] Optionally, the first parameter verification can be a second verification.

[0057] Specifically, after the server device performs the first parameter validation on the request parameters, if the request parameters pass the first parameter validation (e.g., the number of mobile phone numbers is the preset number, and the code length corresponding to the country code parameter is correct), then the request parameters can be validated for the second parameter. For example, the backend service can validate the second parameter of the request parameters, such as determining whether the mobile phone number parameter matches the country code parameter. When the number of mobile phone numbers is 11 digits, the mobile phone number can be a Chinese mobile phone number, so it is necessary to determine whether the country code parameter is the code parameter corresponding to China; and determining whether the format of the mobile phone number parameter is correct, such as determining whether the mobile phone number is a valid mobile phone number, etc., without limitation here.

[0058] Therefore, the request parameters can be validated a second time to ensure their accuracy, thereby improving subsequent sending efficiency.

[0059] Optionally, parameter validation of request parameters may include the request parameters passing both a first parameter validation and a second parameter validation.

[0060] In this embodiment of the disclosure, the server device can determine that the request parameter has passed parameter validation if the request parameter passes both the first parameter validation and the second parameter validation.

[0061] Optionally, S130 may specifically include: determining the first service interface among multiple service interfaces corresponding to the target cache server based on interface priority, the service interfaces including operator service interfaces and third-party service interfaces; and sending the SMS verification code by calling the first service interface through the target cache server.

[0062] In this embodiment of the disclosure, the server device can determine the first service interface from among the multiple service interfaces corresponding to the target cache server by means of interface priority.

[0063] Optionally, the service interface can be an interface used to send SMS verification codes. This service interface can include carrier service interfaces and third-party service interfaces.

[0064] Optionally, the operator service interface can be an interface provided by the three major operators. For example, the operator service interface can be an interface provided by the platforms of the three major operators: China Mobile, China Unicom, and China Telecom.

[0065] Alternatively, the third-party service interface can be an interface provided by an SMS service provider. For example, the third-party service interface could be an interface provided by Tencent Cloud Platform SMS, Alibaba Cloud, etc.

[0066] Optionally, the interface priority can be used to characterize the priority of multiple service interfaces. For example, the priority of a service interface can be determined by the usage evaluation of each service interface, or by user preferences, or by region, etc., and there is no limitation here.

[0067] Optionally, the first service interface can be the service interface with the highest interface priority among multiple service interfaces.

[0068] Specifically, the server device can determine the first service interface from among the multiple service interfaces corresponding to the target cache server by interface priority, that is, determine the service interface with the highest interface priority as the first service interface.

[0069] Furthermore, after determining the first service interface, the server device can send the SMS verification code by calling the first service interface through the target cache server.

[0070] Specifically, after the server device determines the first service interface, for example, when the first service interface is a carrier service interface, it can directly call the carrier service interface to send the SMS verification code. Directly calling the carrier service interface requires certain qualifications. When the first service interface is a third-party service interface, the target cache server can call the third-party service interface to send the SMS verification code.

[0071] Therefore, by prioritizing interfaces, the first service interface can be determined, thus identifying the appropriate interface for sending SMS verification codes, thereby improving sending efficiency and success rate.

[0072] Optionally, the SMS verification code sending method may further include: in the event of a failure of the first service interface, determining a second service interface from among multiple service interfaces based on interface priority; and sending the SMS verification code by calling the second service interface through the target cache server.

[0073] In this embodiment of the disclosure, after the server device determines the first service interface, if the first service interface fails, the second service interface can be determined from multiple service interfaces based on the interface priority.

[0074] Optionally, the second service interface can be the service interface with the second highest priority among multiple service interfaces.

[0075] Specifically, once the server device determines the first service interface, if the first service interface fails and cannot send SMS verification codes, the server device can determine the second service interface from among multiple service interfaces based on the interface priority. That is, the service interface with the highest priority other than the first service interface is determined as the second service interface.

[0076] Furthermore, after determining the second service interface, the server device can call the second service interface through the target cache server to send the SMS verification code.

[0077] Therefore, in this embodiment of the disclosure, SMS verification codes can be sent through the second service interface after the first service interface fails, thereby avoiding the situation where sending fails due to interface instability and improving user experience.

[0078] In some embodiments, if a new SMS service is introduced, such as sending SMS verification codes to overseas mobile phone numbers, a new cache server can be built and directly registered in the distributed cache server cluster without changing the original system architecture and functions.

[0079] Optionally, the SMS verification code sending method may further include: receiving and recording feedback results, including sending results and return results; and performing event statistics and generating corresponding alarm information if the feedback result is a failure result.

[0080] In this embodiment of the disclosure, the server device can receive and record feedback results.

[0081] Optionally, the feedback result may include the sending result and the return result.

[0082] Optionally, the sending result can be used to indicate whether the SMS verification code was sent successfully.

[0083] Optionally, the returned result can be a result used to characterize whether the user terminal has received the SMS verification code.

[0084] Specifically, the server device can receive and record feedback results, which may include sending results and returning results.

[0085] Furthermore, the server device can perform event statistics and generate corresponding alarm information when the feedback result is a failure.

[0086] Optionally, event statistics may include events such as the number of failures and faulty interfaces.

[0087] Optionally, the alarm information can be information used to provide alarm notifications.

[0088] Specifically, after receiving the feedback result, if the feedback result is a failure, the server device can perform event statistics, such as counting the number of failed transmissions, transmission interface failures, etc., and generate corresponding alarm information, such as alarming a certain service interface failure.

[0089] Figure 2 A schematic diagram of the structure of an SMS verification code sending device provided in an embodiment of this disclosure is shown.

[0090] like Figure 2 As shown, the SMS verification code sending device 200 may include a first receiving module 210, a first generating module 220, and a first sending module 230.

[0091] The first receiving module 210 can be used to receive SMS sending requests, which include request parameters.

[0092] The first generation module 220 can be used to generate an SMS verification code when the request parameters pass the parameter validation, and store the SMS verification code in a distributed cache server cluster.

[0093] The first sending module 230 can be used to determine the target cache server in the distributed cache server cluster, and send the SMS verification code by calling the first service interface through the target cache server.

[0094] Therefore, in this embodiment of the present disclosure, an SMS sending request can be received. The SMS sending request includes request parameters. Then, if the request parameters pass parameter validation, an SMS verification code is generated and stored in a distributed cache server cluster. Finally, a target cache server is determined in the distributed cache server cluster, and the SMS verification code is sent by calling the first service interface through the target cache server. Thus, after receiving an SMS sending request, the target cache server can be determined in the distributed cache server cluster first, and the SMS verification code can be sent by calling the first service interface through the target cache server. That is, a normal service interface can be selected for sending, thereby avoiding the situation where sending fails due to interface instability and improving user experience.

[0095] In some embodiments of this disclosure, the request parameters may include mobile phone number parameters and country code parameters.

[0096] In some embodiments of this disclosure, the SMS verification code sending device 200 may further include a first verification module and a second verification module.

[0097] The first verification module can be used to perform the first parameter verification on the request parameters after receiving the SMS sending request.

[0098] The second verification module is used to perform a second parameter verification on the request parameters if the request parameters pass the first parameter verification.

[0099] In some embodiments of this disclosure, the request parameters can be validated by parameter verification, including the request parameters being validated by a first parameter and by a second parameter.

[0100] In some embodiments of this disclosure, the first sending module 230 may specifically include an interface determination unit and an SMS sending unit.

[0101] This interface determination unit can be used to determine the first service interface among multiple service interfaces corresponding to the target cache server based on interface priority. The service interfaces include carrier service interfaces and third-party service interfaces.

[0102] This SMS sending unit can be used to send SMS verification codes by calling the first service interface through the target cache server.

[0103] In some embodiments of this disclosure, the SMS verification code sending device 200 may further include an interface determination module and a second sending module.

[0104] This interface determination module can be used to determine a second service interface from multiple service interfaces based on interface priority when the first service interface fails.

[0105] The second sending module can be used to send SMS verification codes by calling the second service interface through the target cache server.

[0106] In some embodiments of this disclosure, the SMS verification code sending device 200 may further include a second receiving module and an event statistics module.

[0107] The second receiving module can be used to receive and record feedback results after the SMS verification code is sent by calling the first service interface through the target cache server. The feedback results include the sending result and the return result.

[0108] This event statistics module can be used to perform event statistics and generate corresponding alarm information when the feedback result is a failure.

[0109] It should be noted that, Figure 2 The SMS verification code sending device 200 shown can perform... Figure 1 The various steps in the method embodiment shown are implemented. Figure 1 The processes and effects in the method embodiments shown are not described in detail here.

[0110] Figure 3 A schematic diagram of the structure of an SMS verification code sending device provided in an embodiment of this disclosure is shown.

[0111] In some embodiments of this disclosure, Figure 3 The SMS verification code sending device shown can be a server device. For example, the server device can be a server or server cluster that includes storage and computing capabilities.

[0112] like Figure 3 As shown, the SMS verification code sending device may include a processor 301 and a memory 302 storing computer program instructions.

[0113] Specifically, the processor 301 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0114] Memory 302 may include a large-capacity storage for information or instructions. For example, and not limitingly, memory 302 may include a hard disk drive (HDD), a floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or a Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 302 may include removable or non-removable (or fixed) media. Where appropriate, memory 302 may be internal or external to the integrated gateway device. In a particular embodiment, memory 302 is a non-volatile solid-state memory. In a particular embodiment, memory 302 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (Electrically Programmable ROM, EPROM), an electrically erasable programmable PROM (EEPROM), an electrically alterable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0115] The processor 301 reads and executes computer program instructions stored in the memory 302 to perform the steps of the SMS verification code sending method provided in this embodiment of the disclosure.

[0116] In one example, the SMS verification code sending device may further include a transceiver 303 and a bus 304. Wherein, as... Figure 3 As shown, the processor 301, memory 302 and transceiver 303 are connected via bus 304 and communicate with each other.

[0117] Bus 304 may include hardware, software, or both. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 304 may include one or more buses. Although specific buses are described and illustrated in the embodiments of this application, this application considers any suitable bus or interconnection.

[0118] This disclosure also provides a non-volatile computer-readable storage medium that can store a computer program. When the computer program is executed by a processor, the processor implements the SMS verification code sending method provided in this disclosure.

[0119] The aforementioned storage medium may include, for example, a memory 302 containing computer program instructions, which can be executed by the processor 301 of the SMS verification code sending device to complete the SMS verification code sending method provided in this embodiment. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), compact disc ROM (CD-ROM), magnetic tape, floppy disk, and optical data storage device.

[0120] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the term "comprising" is 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.

[0121] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for sending a short message authentication code, characterized by, include: Receive an SMS sending request, wherein the SMS sending request includes request parameters; If the request parameters pass the parameter validation, an SMS verification code is generated and stored in a distributed cache server cluster. The target cache server is determined in the distributed cache server cluster, and the SMS verification code is sent by calling the first service interface through the target cache server.

2. The method according to claim 1, characterized in that, The request parameters include mobile phone number parameters and country code parameters.

3. The method according to claim 1, characterized in that, After receiving the SMS sending request, the method further includes: Perform a first parameter validation on the request parameters; If the request parameters pass the first parameter validation, the request parameters are then validated as a second parameter.

4. The method according to claim 3, characterized in that, The request parameters passing parameter validation includes the request parameters passing both the first parameter validation and the second parameter validation.

5. The method according to claim 1, characterized in that, The step of sending the SMS verification code by calling the first service interface through the target cache server includes: Among the multiple service interfaces corresponding to the target cache server, the first service interface is determined by interface priority. The service interface includes carrier service interfaces and third-party service interfaces. The SMS verification code is sent by calling the first service interface through the target cache server.

6. The method according to claim 5, characterized in that, The method further includes: In the event of a failure of the first service interface, a second service interface is determined from the plurality of service interfaces based on the interface priority. The SMS verification code is sent by calling the second service interface through the target cache server.

7. The method according to claim 1, characterized in that, After sending the SMS verification code by calling the first service interface through the target cache server, the method further includes: Receive and record feedback results, including sending results and return results; If the feedback result is a failure, event statistics are performed and corresponding alarm information is generated.

8. A device for sending SMS verification codes, characterized in that, include: The first receiving module is used to receive SMS sending requests, the SMS sending requests including request parameters; The first generation module is used to generate an SMS verification code when the request parameters pass the parameter verification, and to store the SMS verification code in a distributed cache server cluster. The first sending module is used to determine the target cache server in the distributed cache server cluster, and send the SMS verification code by calling the first service interface through the target cache server.

9. A device for sending SMS verification codes, characterized in that, include: processor; Memory, used to store executable instructions; The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement the SMS verification code sending method according to any one of claims 1-7.

10. A non-volatile computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, causes the processor to implement the SMS verification code sending method according to any one of claims 1-7.

Images