A short message sending method and related device

Abstract

The application provides a short message sending method and related device to improve the safety of short message receiving and sending and to govern the behavior of junk short messages. A short message sending method is applied to a first client, and the method comprises: in response to a short message sending instruction, generating a first authentication data packet, wherein the first authentication data packet comprises a number corresponding to the first client, a target short message, a number corresponding to a second client, historical sending behavior information of the first client, and the second client is a receiving client of the target short message; and sending the first authentication data packet.

Description

Technical Field

[0001] This application relates to the field of network security, and in particular to a method for sending text messages and related devices. Background Technology

[0002] With the development of SMS applications, spam messages have become a nuisance in daily life. Spam message monitoring methods have emerged to address this need. Currently, these methods employ a "pre-set strategy, then identify suspicious users" approach. For example, strategies can be set based on factors such as data usage, frequency, and keywords. However, non-compliant users can typically bypass existing spam message monitoring strategies by using botnets to send spam messages, changing SMS keywords, using multiple virtual numbers, or mixing legitimate and spam messages. Summary of the Invention

[0003] This application provides a method and related apparatus for sending text messages, which can improve the security of sending and receiving text messages and combat spam text message behavior.

[0004] In a first aspect, embodiments of this application provide a method for sending text messages, which can be applied to a first client, the method comprising:

[0005] In response to a text message sending command, a first authentication data packet is generated. The first authentication data packet includes the number corresponding to the first client, the target text message, the number corresponding to the second client, and the historical sending behavior information of the first client. The second client is the receiving client of the target text message.

[0006] Send the first authentication data packet.

[0007] In one possible design, the first authentication data packet further includes a random verification code, wherein the random verification code is provided by the authentication server.

[0008] In one possible design, the historical sending behavior information of the first client includes at least one of the following:

[0009] The n most recent text messages sent, the n most recent number of the receiving client, and the timestamp of the n most recent text messages sent, where n is a positive integer.

[0010] Secondly, embodiments of this application provide a method for sending SMS messages, which can be applied to an authentication server, the method comprising:

[0011] Receive a first authentication data packet, the first authentication data packet including the number corresponding to the first client, the target SMS, the number corresponding to the second client, and the historical sending behavior information of the first client, the first client being the sending client of the target SMS, and the second client being the receiving client of the target SMS;

[0012] Based on the pre-stored historical data of the first client, the historical sending behavior information of the first client is verified;

[0013] After the historical sending behavior information of the first client is verified, an authentication success message is sent to the SMS gateway.

[0014] In one possible design, the method further includes:

[0015] After the historical sending behavior information of the first client is verified, at least one of the following is stored:

[0016] The target SMS message, the time when the first client sent the target SMS message, and the number corresponding to the second client.

[0017] In one possible design, the first authentication data packet further includes a random verification code, which is pre-sent to the first client; before verifying the historical sending behavior information of the first client, the method further includes:

[0018] The random verification code in the first authentication data packet is verified.

[0019] In one possible design, the method further includes:

[0020] If the verification of the historical sending behavior information of the first client fails, an authentication failure message is sent to the SMS gateway.

[0021] Thirdly, embodiments of this application provide a method for sending SMS messages, which can be applied to an SMS gateway, the method comprising:

[0022] Receive the authentication data packet provided by the first client;

[0023] If an authentication pass message is received, the target SMS message in the authentication data packet of the first client is sent to the second client. The authentication pass message is used to indicate that the authentication data packet of the first client has passed the verification. The second client is the receiving client of the target SMS message.

[0024] If an authentication failure message is received, the authentication data packet of the first client is discarded.

[0025] Fourthly, embodiments of this application provide an electronic device that may include a processor and a memory;

[0026] The memory stores computer instructions;

[0027] The processor is configured to read the computer instructions and execute the method as described in the first aspect and any one thereof.

[0028] Fifthly, embodiments of this application provide an electronic device that may include a processor and a memory;

[0029] The memory stores computer instructions;

[0030] The processor is configured to read the computer instructions and execute the method as described in the second aspect and any one thereof.

[0031] Sixthly, embodiments of this application provide an electronic device that may include a processor and a memory;

[0032] The memory stores computer instructions;

[0033] The processor is configured to read the computer instructions and execute the method as described in the third aspect and any one thereof.

[0034] Furthermore, according to embodiments, for example, a computer program product for a computer is provided, which includes software code portions that, when the product is run on the computer, perform the steps of the methods defined above. The computer program product may include a computer-readable medium on which the software code portions are stored. Furthermore, the computer program product may be directly loaded into the computer's internal memory and / or sent via a network through at least one of an upload process, a download process, and a push process.

[0035] Another embodiment of this application provides a computer-readable storage medium storing computer-executable instructions for causing the computer to perform any of the methods described above.

[0036] In the technical solution provided in this application embodiment, the sending client can initiate verification to the authentication server by generating and sending authentication data packets during the SMS sending process. The authentication server can enhance the verification of the sending client by verifying the historical sending behavior information in the authentication data packets, preventing the sending client from being used as a "zombie" to send SMS messages without restriction. This improves SMS sending and receiving security and effectively combats spam SMS messages. Attached Figure Description

[0037] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0039] Figure 2 A flowchart illustrating a method for sending text messages provided in an embodiment of this application;

[0040] Figure 3 A flowchart illustrating a method for sending text messages provided in an embodiment of this application;

[0041] Figure 4 A flowchart illustrating a method for sending text messages provided in an embodiment of this application;

[0042] Figure 5 A flowchart illustrating a method for sending text messages provided in an embodiment of this application;

[0043] Figure 6 A flowchart illustrating a method for sending text messages provided in an embodiment of this application;

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

[0045] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0046] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0047] This application provides a method for sending text messages and an apparatus for implementing the method. The text message sending method provided in this application enhances the security capabilities of the text message system, preventing the sender's terminal from being used as a "zombie" to send spam messages. This application provides a zero-trust security mechanism that achieves secure text message sending and receiving through enhanced authentication.

[0048] Figure 1This document exemplifies an application scenario for sending text messages. The text message sending method provided in this application can be applied to a text messaging system, which may include at least one sending device, at least one receiving device, a text messaging gateway, and an authentication server. In this application, the electronic device or electronic terminal used by the sender can be simply referred to as the sending device. The sending device may have the text messaging client or text messaging application (hereinafter referred to as the text messaging component) provided in this application installed. When the text messaging component runs, it can implement the text message sending method provided in this application. The electronic device or electronic terminal used by the recipient can be simply referred to as the receiving device. The authentication server can verify the identity of the sending device. The text messaging gateway can send the text messages from the sending device to the designated receiving device.

[0049] Figure 2 An exemplary method for sending SMS messages is shown, which can be applied to a first client, wherein the first client is configured on a sending device. The SMS sending method may include the following steps:

[0050] S101, in response to the SMS sending command, generates the first authentication data packet.

[0051] In practice, the first authentication data packet is used by the authentication server to authenticate the sending device. This first authentication data packet may include the number corresponding to the first client, the target SMS message, the number corresponding to the second client, and the historical sending behavior information of the first client. The second client is the receiving client of the target SMS message.

[0052] The number corresponding to the first client can be the communication number of the sending device or an identity identifier. When the first client is run for the first time, the user can configure the number corresponding to the first client through binding, association, or other methods. Optionally, when the user triggers the first client for the first time, they need to enter their identity information, which may include the user's real name information, emergency contact information, etc.

[0053] S102, send the first authentication data packet.

[0054] In practice, the first client can directly send the first authentication data packet to the authentication server. Alternatively, the first client can directly send the first authentication data packet to the SMS gateway. The SMS gateway then forwards the first authentication data packet to the authentication server so that the authentication server can obtain it.

[0055] In one possible implementation, the historical sending behavior information of the first client in the first authentication data packet may include the SMS messages previously sent by the first client, the timestamps of the previously sent SMS messages, and the phone numbers of the receiving clients of the previously sent SMS messages. This facilitates the authentication server in verifying the historical sending behavior information of the first client, thereby authenticating the identity of the first client and preventing the sending device from being used as a "zombie" to avoid unrestricted SMS sending.

[0056] In some examples, the historical sending behavior information of the first client in the first authentication packet may include at least one of the following:

[0057] The most recent n SMS messages sent by the first client, the timestamps of the most recent n SMS messages sent by the first client, and the phone numbers of the receiving clients of the most recent n SMS messages. Here, n can be a positive integer.

[0058] In some possible designs, the first client can connect to the authentication server, such as through a communication connection. The authentication server can issue a random verification code (token) to the first client. For example, after the first client starts up and establishes a communication connection with the authentication server, the first client can receive the random verification code. As another example, after the random verification code expires, the first client can request a new random verification code from the authentication server again. In step S101, the first authentication data packet may also include the random verification code sent by the authentication server to the first client.

[0059] Optionally, the first authentication data packet may also include identity information data corresponding to the first client, such as the user's identity identifier.

[0060] In some examples, Figure 3 The diagram illustrates an example of an authentication data packet. See also... Figure 3 The authentication data packet can include multiple parts. S represents the number corresponding to the first client, T represents the timestamp of this SMS message, A represents the content of this SMS message (i.e., the target SMS), and D represents the number of the receiving client. D1, D2, and D3 represent the numbers of the receiving clients in the three most recent SMS messages sent by the first client, and T1, T2, and T3 represent the timestamps of the three most recent SMS messages sent by the first client. Token represents the random verification code sent by the authentication server to the first client. IDA represents the user identity information corresponding to the first client.

[0061] It should be noted that, Figure 3 The data shows the numbers of the receiving clients who sent the three most recent SMS messages from the first client, as well as the timestamps of the three most recent SMS messages sent by the first client. This is only used to illustrate the form of the authentication data packet and is not intended to limit the amount of historical sending behavior information of the first client.

[0062] After confirming that the SMS message has been successfully sent, the first client can store the message sending information, such as the timestamp of the message sending, the message content, and the recipient client's phone number. This information can be used to generate authentication data packets when sending SMS messages again.

[0063] In one possible implementation, in step S102, the first client can encrypt and transmit the first authentication data packet to the SMS gateway or authentication server.

[0064] Figure 4 An exemplary method for sending SMS messages is shown, which can be applied to the authentication server side. This method may include the following steps:

[0065] S201, Receive the first authentication data packet.

[0066] In practice, the authentication server can directly or indirectly receive the first authentication data packet sent by the first client. The first authentication data packet may include the number corresponding to the first client, the target SMS message, the number corresponding to the second client, and the historical sending behavior information of the first client. The first client is the sending client of the target SMS message, and the second client is the receiving client of the target SMS message. For a description of the first authentication data packet, please refer to the relevant descriptions in the foregoing embodiments; they will not be repeated here.

[0067] S202, verify the historical sending behavior information of the first client based on the historical data of the first client that has been stored in advance.

[0068] In practice, the authentication server can pre-store the historical data of the first client, such as the first client's historical successful sending behavior information, successfully sent SMS messages, timestamps of successfully sent SMS messages, and the receiving client's number of successfully sent SMS messages.

[0069] The authentication server can verify the first client's historical sending behavior information in the first authentication data packet received this time, based on the historical data stored by the first client. If the historical sending behavior information in the first authentication data packet matches the historical data of the first client stored by the authentication server, it indicates that the first client's historical sending behavior information has passed verification. If the historical sending behavior information in the first authentication data packet does not match the historical data of the first client stored by the authentication server, it indicates that the first client's historical sending behavior information has failed verification.

[0070] S203: After the historical sending behavior information of the first client is verified, an authentication pass message is sent to the SMS gateway.

[0071] After executing step S203, the authentication server can also store at least one of the following after the historical sending behavior information of the first client has been verified: the target SMS message, the time when the first client sent the target SMS message, and the number corresponding to the second client. This design updates the historical data of the first client to facilitate the verification of authentication data packets sent by the first client again.

[0072] In one possible design, when the first client is first triggered, it can establish a connection with the authentication server. The authentication server generates a random verification code corresponding to the first client and sends it to the first client. Alternatively, after the random verification code received by the first client expires, the first client can request a new random verification code from the authentication server. The authentication server can then provide a new random verification code to the first client based on its request.

[0073] Optionally, in step S201, the first authentication data packet may further include a random verification code. The authentication server can verify the random verification code in the first authentication data packet based on the pre-stored random verification code corresponding to the first client. If the two match, the random verification code passes verification. If the two do not match, the random verification code fails verification.

[0074] The authentication server can send an authentication success message to the SMS gateway after verifying the historical sending behavior information of the first client and the random verification code. This embodiment does not specifically limit the order of verification of the random verification code and verification of the historical sending behavior information. The verification process of the random verification code can occur before, after, or simultaneously with step S202.

[0075] In one possible design, the first authentication data packet may further include user identity information corresponding to the first client. Upon initial triggering, the first client can send its corresponding phone number and user identity information to the authentication server through registration or association. The authentication server can store the phone number and user identity information for each client. After step S201, the authentication server can further verify the user identity information of the first client. The authentication server can send an authentication success message to the SMS gateway after the user identity information, historical sending behavior information, and random verification code have all been verified successfully.

[0076] In one possible scenario, the authentication server can send an authentication failure message to the SMS gateway after the first client's historical sending behavior information fails verification. Alternatively, the authentication server can send an authentication failure message to the SMS gateway after the first client's random verification code fails verification. Or, the authentication server can send an authentication failure message to the SMS gateway after the first client's user identity information fails verification. Optionally, the authentication server can send an authentication failure message to the first client so that the first client knows whether the SMS was successfully sent.

[0077] In one possible implementation, the authentication server can monitor the SMS messages in the first authentication data packet, for example, using any existing SMS security monitoring method. This could involve monitoring the SMS messages in the first authentication data packet according to a preset policy. The preset policy could include policies regarding security monitoring indicators such as traffic, frequency, and keywords. If the SMS messages in the first authentication data packet fail the security monitoring, the authentication server can send an authentication failure message to the SMS gateway and the first client.

[0078] Optionally, the authentication server can retrieve the blacklist corresponding to the receiving client based on the number of the client receiving the SMS in the first authentication data packet. The authentication server can check whether the number of the first client is in the blacklist of the clients receiving the SMS (first blacklist) and / or whether it is in the blacklist configured by the system (second blacklist). If the number corresponding to the first client is in the first blacklist or the number corresponding to the first client is in the second blacklist, the authentication server can send an authentication failure message to the SMS gateway and the first client.

[0079] Optionally, if the number corresponding to the first client is not in the first blacklist and is not in the second blacklist, and the SMS in the first authentication data packet passes security monitoring, the historical sending behavior information in the first authentication data packet passes verification, the random verification code in the first authentication data packet passes verification, and the user identity information in the first authentication data packet passes verification, the authentication server can send an authentication pass message to the SMS gateway and the first client.

[0080] Figure 5 An exemplary flowchart of a method for sending text messages is shown, which can be applied to a text message gateway. The method may include the following steps:

[0081] S301 receives the authentication data packet provided by the first client.

[0082] S302, if an authentication pass message is received, the target SMS message in the authentication data packet of the first client is sent to the second client.

[0083] The authentication pass message indicates that the authentication data packet of the first client has passed verification, and the second client is the receiving client of the target SMS.

[0084] S303, if an authentication failure message is received, discard the authentication data packet of the first client.

[0085] In this embodiment, the SMS gateway executes a sending operation according to the instructions of the authentication server. The authentication success message may carry the number corresponding to the first client, indicating that the first client's authentication data packet has passed authentication, and that the first client's sending action constitutes successful identity and security verification. The SMS gateway can then forward the target SMS message from the first client's data packet to the second client, that is, forward the SMS message sent by the first client to the corresponding receiving client.

[0086] The SMS gateway can perform a discard operation as instructed by the authentication server. The authentication failure message can carry the number corresponding to the first client to indicate that the authentication data packet from the first client failed authentication. The SMS gateway can discard the authentication data packet provided by the first client received in step S301. Optionally, the SMS gateway can send an authentication failure message to the first client so that the first client is aware that the SMS delivery failed.

[0087] In one possible design, in step S302, the SMS gateway can decrypt the authentication data packet provided by the first client, and then send the SMS message in the authentication data packet to the receiving client.

[0088] Figure 6 An interactive diagram illustrating an SMS sending method is provided, which may include the following steps:

[0089] S401, the first client responds to the SMS sending command and generates the first authentication data packet.

[0090] S402, the first client sends the first authentication data packet.

[0091] The first client can send the first authentication data packet directly or indirectly to the authentication server. The first client can also send the first authentication data packet to the SMS gateway.

[0092] S403, the authentication server performs enhanced authentication on the first authentication data packet.

[0093] S404, Did the first authentication data packet pass enhanced authentication? If yes, proceed to S405; otherwise, proceed to S407.

[0094] S405, the authentication server performs security monitoring on the target SMS message in the first authentication data packet.

[0095] S406: Has the target SMS in the first authentication data packet passed security monitoring? If yes, proceed to S408; otherwise, proceed to S407.

[0096] Security monitoring of text messages can be carried out according to preset strategies, such as monitoring text message traffic, frequency, keywords, etc.

[0097] S407, the authentication server sends an authentication failure message for the first authentication data packet.

[0098] The authentication server sends an authentication failure message to the SMS gateway for the first authentication data packet. Optionally, the authentication server may send the authentication failure message to the first client directly or indirectly.

[0099] S408, the authentication server determines whether the number corresponding to the first client is in the blacklist. If yes, proceed to S407; otherwise, proceed to S409.

[0100] The blacklist in step S408 can be the blacklist of the receiving client of this SMS in the first authentication data packet, or the system's blacklist.

[0101] S409, the authentication server sends an authentication success message for the first authentication data packet.

[0102] The authentication server sends an authentication success message for the first authentication data packet to the SMS gateway. Optionally, the authentication server can directly or indirectly send the authentication success message for the first authentication data packet to the first client. The authentication server can also store the first client's number, the target SMS message, and the number of the client receiving the SMS message in the first authentication data packet, and update the first client's historical data to facilitate the verification of other authentication data packets from the first client.

[0103] After receiving the authentication success message from the first authentication data packet, the first client can store the SMS message and the number of the client receiving the SMS message in the first authentication data packet in order to generate other authentication data packets.

[0104] S410, if the SMS gateway receives the authentication pass message of the first authentication data packet, it will send the target SMS in the first authentication data packet to the second client.

[0105] The second client is the client that received this SMS message in the first authentication data packet.

[0106] S411, if the SMS gateway receives an authentication failure message for the first authentication data packet, it will discard the first authentication data packet.

[0107] Based on the same technical concept, this application also provides an electronic device capable of implementing the SMS sending method in the foregoing embodiments.

[0108] See Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. As shown in the figure, the device may include: a processor 701, a memory 702, and a bus interface 703.

[0109] The processor 701 is responsible for managing the bus architecture and general processing, while the memory 702 can store the data used by the processor 701 when performing operations.

[0110] The bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 701) and memory (memory 702). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface. Processor 701 is responsible for managing the bus architecture and general processing, and memory 702 can store data used by processor 701 during operation.

[0111] The processes disclosed in this application can be applied to or implemented by processor 701. During implementation, each step of the processing flow can be completed by integrated logic circuits in the hardware of processor 701 or by instructions in software form. Processor 701 can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, and can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution by the hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory 702, and processor 701 reads the information in memory 702 and, in conjunction with its hardware, completes the steps of the method flow in the embodiments of this application.

[0112] In one possible implementation, the electronic device can serve as a transmitting device. Processor 701 is configured to read computer instructions from memory 702 and execute them according to the obtained program.

[0113] In response to a text message sending command, a first authentication data packet is generated. The first authentication data packet includes the number corresponding to the first client, the target text message, the number corresponding to the second client, and the historical sending behavior information of the first client. The second client is the receiving client of the target text message.

[0114] Send the first authentication data packet.

[0115] Optionally, the first authentication data packet may further include a random verification code, wherein the random verification code is provided by the authentication server.

[0116] Optionally, the historical sending behavior information of the first client includes at least one of the following:

[0117] The n most recent text messages sent, the n most recent number of the receiving client, and the timestamp of the n most recent text messages sent, where n is a positive integer.

[0118] In another possible implementation, the electronic device can act as an authentication server. Processor 701 is used to read computer instructions from memory 702 and execute them according to the obtained program;

[0119] Receive a first authentication data packet, which may include the number corresponding to the first client, the target SMS message, the number corresponding to the second client, and the historical sending behavior information of the first client. The first client is the sending client of the target SMS message, and the second client is the receiving client of the target SMS message.

[0120] Based on the pre-stored historical data of the first client, the historical sending behavior information of the first client is verified;

[0121] After the historical sending behavior information of the first client is verified, an authentication success message is sent to the SMS gateway.

[0122] In one possible design, processor 701 is also used for:

[0123] After the historical sending behavior information of the first client is verified, at least one of the following is stored:

[0124] The target SMS message, the time when the first client sent the target SMS message, and the number corresponding to the second client.

[0125] In one possible design, the first authentication data packet further includes a random verification code, which is pre-sent to the first client; before verifying the historical sending behavior information of the first client, the method further includes:

[0126] The random verification code in the first authentication data packet is verified.

[0127] In one possible design, the method further includes:

[0128] If the verification of the historical sending behavior information of the first client fails, an authentication failure message is sent to the SMS gateway.

[0129] In another possible implementation, the electronic device can act as a text messaging gateway. Processor 701 is used to read computer instructions from memory 702 and execute them according to the obtained program;

[0130] Receive the authentication data packet provided by the first client;

[0131] If an authentication pass message is received, the target SMS message in the authentication data packet of the first client is sent to the second client. The authentication pass message is used to indicate that the authentication data packet of the first client has passed the verification. The second client is the receiving client of the target SMS message.

[0132] If an authentication failure message is received, the authentication data packet of the first client is discarded.

[0133] This application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the SMS sending method described in the above embodiments.

[0134] This application also provides a computer program product, which, when invoked by a computer, causes the computer to execute the SMS sending method described in the above embodiments.

[0135] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0136] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0137] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0138] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0139] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method of sending a short message, characterized by, The method applied to a first client comprises: In response to sending a short message instruction, a first authentication data packet is generated, the first authentication data packet comprising a number corresponding to the first client, a target short message, a number corresponding to a second client, and historical sending behavior information of the first client, the second client being a receiving client of the target short message, wherein the first client stores behavior information of any short message after determining that the any short message is successfully sent, the historical behavior information of the first client being generated based on the behavior information of the short messages stored by the first client, the historical sending behavior information of the first client being used for the authentication server to verify the historical sending behavior information of the first client based on historical data of the first client stored in advance, and after the verification is passed, the target short message is sent to the second client by a short message gateway; The first authentication data packet is sent.

2. The method of claim 1, wherein, The first authentication data packet further comprises a random verification code, wherein the random verification code is provided by the authentication server.

3. The method of claim 1 or 2, wherein, The historical sending behavior information of the first client comprises at least one of the following: The most recent n times of sent short messages, the most recent n times of numbers corresponding to receiving clients, and the most recent n times of timestamps of sent short messages, wherein n is a positive integer.

4. A method of sending a short message, characterized by The method applied to an authentication server comprises: A first authentication data packet is received, the first authentication data packet comprising a number corresponding to a first client, a target short message, a number corresponding to a second client, and historical sending behavior information of the first client, the first client being a sending client of the target short message, the second client being a receiving client of the target short message, the first authentication data packet being generated and sent by the first client, wherein the first client stores behavior information of any short message after determining that the any short message is successfully sent, and historical behavior information of the first client is generated based on the behavior information of the short messages stored by the first client; The historical sending behavior information of the first client is verified based on historical data of the first client stored in advance; After the historical sending behavior information of the first client is verified, a pass authentication message is sent to a short message gateway.

5. The method of claim 4, wherein, The method further comprises: After the historical sending behavior information of the first client is verified, at least one of the following is stored: The target short message, a time at which the target short message is sent by the first client, and the number corresponding to the second client.

6. The method of claim 4 or 5, wherein, The first authentication data packet further comprises a random verification code, the random verification code being sent to the first client in advance, and before the historical sending behavior information of the first client is verified, the method further comprises: The random verification code in the first authentication data packet is verified.

7. The method of claim 4 or 5, wherein, The method further comprises: If the historical sending behavior information of the first client is not verified, a fail authentication message is sent to the short message gateway.

8. A method of sending a short message, characterized by The method applied to a short message gateway comprises: receiving an authentication data packet provided by a first client, the authentication data packet comprising historical sending behavior information of the first client, wherein the historical sending behavior information of the first client is used for the authentication server to verify the historical sending behavior information of the first client according to historical data of the first client stored in advance; wherein the first client stores behavior information of any short message after determining that the any short message is successfully sent, and the historical behavior information of the first client is generated based on the behavior information of the short message stored by the first client; if an authentication pass message is received, sending a target short message in the authentication data packet of the first client to a second client, the authentication pass message being used to indicate that the authentication data packet of the first client passes verification, and the second client being a receiving client of the target short message, wherein the authentication pass message is sent by the authentication server; if an authentication fail message is received, discarding the authentication data packet of the first client.

9. An electronic device, comprising: comprising a processor and a memory; the memory, storing computer instructions; the processor, configured to read the computer instructions and execute the method according to any one of claims 1-8.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer executable instructions, and the computer executable instructions are used to make the computer execute the method according to any one of claims 1-8.

Images