Methods, devices, electronic equipment and storage media for sending short messages

Abstract

This application provides a method, apparatus, electronic device, and storage medium for sending short messages, relating to the field of communication technology. The method for sending short messages includes: in response to a short message sent by a sending device, determining a target area where the short message recipient is located; using an ID labeling strategy corresponding to the target area to label the sender ID, obtaining a labeling result; and sending the short message to the recipient device when the labeling result indicates that the short message needs to be sent. The technical solution of this application, by first labeling the sender ID and then sending the corresponding short message to the recipient device only when the labeling result indicates that the short message needs to be sent, can effectively intercept some sender IDs and short messages sent using those sender IDs. Furthermore, using an ID labeling strategy corresponding to the target area to label the sender ID has better applicability to the target area.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, electronic device and storage medium for sending short messages. Background Technology

[0002] The sender ID (Identity Document, account) is a name displayed on the recipient's device that identifies the sender of a short message. It is an effective way to identify the brand of the short message sender to the recipient.

[0003] When sending SMS messages using sender IDs, some criminals impersonate well-known brands to send messages and harm the recipients' interests. Therefore, how to intercept SMS messages sent using unauthorized sender IDs has become a pressing technical problem for SMS service platforms. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for sending short messages, so as to more effectively intercept short messages sent using sender ID.

[0005] In a first aspect, embodiments of this application provide a method for sending short messages, including:

[0006] In response to a short message sent by the sending device, determine the target area where the short message recipient is located;

[0007] Using the ID labeling strategy corresponding to the target region, the sender ID of the short message is labeled to obtain the labeling results;

[0008] When the annotation result indicates that a short message needs to be sent, a short message is sent to the receiving device.

[0009] Secondly, embodiments of this application provide a short message sending device, comprising:

[0010] The target area determination module is used to determine the target area where the SMS recipient is located in response to an SMS sent by the sending device.

[0011] The annotation module is used to annotate the sender ID using the ID annotation strategy corresponding to the target area, and obtain the annotation results;

[0012] The SMS sending module is used to send an SMS to the receiving device when the annotation result indicates that an SMS needs to be sent.

[0013] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory. When the processor executes the computer program, it implements the short message sending method provided in any embodiment of this application.

[0014] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the short message sending method provided in any embodiment of this application.

[0015] Compared with the prior art, this application has the following advantages:

[0016] The technical solution of this application, after determining the target area where the SMS recipient is located, uses an ID labeling strategy corresponding to the target area to label the sender ID of the SMS, obtaining the labeling result. Only when the labeling result indicates that an SMS needs to be sent will the corresponding SMS be sent to the recipient's device. By first labeling the sender ID and then sending the corresponding SMS to the recipient's device only when the labeling result indicates that an SMS needs to be sent, the solution can effectively intercept certain sender IDs and SMS messages sent using those sender IDs.

[0017] In addition, since the technical solution of this application first determines the target area where the SMS recipient is located, and then uses the ID labeling strategy corresponding to the target area to label the sender ID after determining the target area, the technical solution of this application has better applicability to the target area.

[0018] The above overview is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of this application will become readily apparent from the accompanying drawings and the following detailed description. Attached Figure Description

[0019] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the various drawings denote the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings depict only some embodiments disclosed in this application and should not be construed as limiting the scope of this application.

[0020] Figure 1 This is a schematic diagram illustrating an application scenario of a short message sending method provided in this application embodiment;

[0021] Figure 2 This is a flowchart illustrating a method for sending short messages provided in an embodiment of this application;

[0022] Figure 3This is a flowchart illustrating an interception and detection method provided in an embodiment of this application;

[0023] Figure 4 This is a flowchart illustrating an annotation method provided in an embodiment of this application;

[0024] Figure 5 This is a flowchart illustrating a sender ID detection method provided in an embodiment of this application.

[0025] Figure 6 This is a schematic diagram of the structural framework of a short message sending device provided in the embodiments of this application; and

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

[0027] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other forms than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0028] To more clearly demonstrate the SMS sending method provided in the embodiments of this application, we first introduce the application scenario of the SMS sending method provided in the embodiments of this application. The SMS sending method provided in the embodiments of this application can be applied to the scenario of sending SMS messages from country A to country B. The following details... Figure 1 This paper will introduce the application scenarios of the short message sending method provided in the embodiments of this application. Figure 1 This is a schematic diagram illustrating an application scenario of a short message sending method provided in this application embodiment. Wherein, Figure 1 In the diagram, 101 represents the sending device, 102 represents the SMS service platform, and 103 represents the receiving device. Furthermore, country B is one that supports sending SMS messages using the sender ID.

[0029] When a short message sender located in country A wants to send a short message to a short message recipient located in country B using a sender ID, they need to first determine whether country B requires the short message sender to register a sender ID in country B. If country B requires the short message sender to register a sender ID in country B, the short message sender must first register a sender ID for sending short messages to country B, and only after registration is completed can they use the registered sender ID to send short messages.

[0030] If Country B does not require SMS senders to register a sender ID in Country B beforehand, or does not require them to do so, then SMS senders can first register a sender ID for sending SMS messages to Country B, and then use the registered sender ID to send SMS messages after registration. Alternatively, SMS senders can choose not to register a sender ID and instead directly enter the desired sender ID during the SMS sending process.

[0031] After the SMS sender composes the SMS message to be sent using the sender ID on the sender device 101, the sender device 101 will control the sender device 101 to send the SMS message. After receiving the control command triggered by the SMS sender, the sender device 101 will send the SMS message to the SMS service platform 102 of country A.

[0032] After receiving a short message from the sender device 101, the short message service platform 102 responds to the message by determining the target area of ​​the message recipient. Specifically, the short message service platform 102 can determine the target area of ​​the message recipient based on the country / region code corresponding to the message recipient. When sending a short message to a message recipient located in country B, the short message service platform 102 can determine that the target area of ​​the message recipient is country B based on the country / region code corresponding to the message recipient.

[0033] After determining that the target region of the SMS recipient is country B, the SMS service platform 102 will first use the ID interception policy corresponding to country B to intercept and detect the sender ID of the SMS. After the sender ID passes the interception detection, the SMS service platform 102 will further use the ID labeling policy corresponding to country B to label the sender ID, obtain the labeling result, and send the SMS to the recipient device 103 when the labeling result indicates that an SMS needs to be sent.

[0034] After receiving a short message from the short message service platform 102, the receiving device 103 will display the sender ID through the human-computer interaction interface.

[0035] It should be noted that after intercepting and detecting the sender ID of a short message, if the sender ID fails the interception detection, the short message service platform 102 will refuse to send the short message to the receiving device 103. Additionally, if the sender ID passes the interception detection, but the sender ID is labeled using the ID labeling strategy corresponding to country B, and the labeling result indicates that the short message should be refused, the short message service platform 102 will also refuse to send the short message to the receiving device 103.

[0036] The method for sending short messages provided in this application embodiment first uses the ID interception strategy corresponding to country B to intercept and detect the sender ID of the short message after determining that the recipient of the short message is located in country B. Then, it uses the ID labeling strategy corresponding to country B to label the sender ID that passes the interception and detection, obtains the labeling result, and sends the corresponding short message to the recipient device only when the labeling result indicates that a short message needs to be sent.

[0037] By intercepting and detecting the sender IDs of short messages, a portion of these sender IDs and short messages sent using those IDs can be blocked. Sender IDs that pass the interception detection are marked, and only when the marking result indicates that a short message needs to be sent will the corresponding short message be sent to the receiving device. This further blocks some sender IDs and short messages sent using those IDs. Therefore, the short message sending method provided in this embodiment can more effectively block short messages sent using unauthorized sender IDs.

[0038] Furthermore, since the SMS sending method provided in this embodiment first determines the country B where the SMS recipient is located, and uses the ID interception strategy corresponding to country B when intercepting and detecting the SMS sender ID, and uses the ID labeling strategy corresponding to country B when labeling the sender ID, the SMS sending method provided in this embodiment adopts a personalized SMS interception strategy for country B, thus making the SMS sending method provided in this embodiment more applicable to country B.

[0039] It should be noted that the above-described application scenarios of the SMS sending method provided in the embodiments of this application are for the purpose of facilitating understanding of the SMS sending method provided in the embodiments of this application, and are not intended to limit the SMS sending method provided in the embodiments of this application. The SMS sending method provided in the embodiments of this application can also be applied to other scenarios, such as: applying it to a scenario of sending SMS from country A to region C, or applying it to a scenario of sending SMS within country A, etc. Specifically, the application scenarios of the SMS sending method in the embodiments of this application are not specifically limited.

[0040] This application provides a method for sending short messages, such as... Figure 2 As shown, the method may include the following steps S201-S203:

[0041] Step S201: In response to the short message sent by the sending device, determine the target area where the short message recipient is located.

[0042] In this embodiment of the application, the full name of the so-called short message is SMS (Short Message Service) message, or simply SMS.

[0043] The target region refers to the area that supports sending SMS messages using the sender ID. The target region can be a country or a region. The sender ID is a name displayed on the receiving device to identify the sender of the SMS message. Specifically, after receiving an SMS message sent using the sender ID, the receiving device will display the sender ID on its corresponding configured human-machine interface.

[0044] It should be noted that in some countries or regions that support sending SMS messages using sender ID, the sender may need to register the sender ID in that country or region first. Therefore, before sending SMS messages using sender ID in, or before sending SMS messages to, those countries or regions, the sender needs to register the sender ID for sending SMS messages in that country or region. Only after registration is completed can the registered sender ID be used to send SMS messages.

[0045] Additionally, in some countries or regions that support sending SMS messages using sender IDs, it may not be mandatory for SMS senders to register their sender IDs beforehand. Therefore, before sending SMS messages using sender IDs in or to those countries or regions, senders can register their sender IDs in those countries or regions. After registration, the registered sender ID can be used to send SMS messages. Alternatively, senders can choose not to register their sender IDs and instead directly enter the desired sender ID during the message sending process.

[0046] In this embodiment, the sending device refers to an electronic device used by the SMS sender that supports sending and receiving SMS messages. The receiving device refers to an electronic device used by the SMS receiver that supports sending and receiving SMS messages. The term "electronic device" generally refers to smart electronic devices such as mobile phones.

[0047] In one implementation, determining the target region where the SMS recipient is located is achieved as follows: First, obtain the country / region code corresponding to the SMS recipient. Then, determine the country or region corresponding to the country / region code as the target region.

[0048] Country codes are a unique set of abbreviations or symbols used to identify a country or region. Therefore, using the country code of the SMS recipient to determine the target area simplifies the process and makes the target area more accurate.

[0049] It should be noted that the execution entity of the short message sending method provided in this application embodiment is generally a short message service platform pre-configured in the area where the short message is sent. This short message service platform can support functions such as submitting, storing and forwarding short messages.

[0050] The region where the SMS message is sent can refer to the target region or a region other than the target region. When the region where the message is sent refers to the target region, the communication channel for the SMS message is generally a local communication channel. When the region where the message is sent refers to a region other than the target region, the communication channel for the SMS message is generally an international communication channel.

[0051] The method for sending short messages provided in this application embodiment requires further execution of step S202 after determining the target area where the short message recipient is located.

[0052] Step S202: Using the ID labeling strategy corresponding to the target area, the sender ID of the short message is labeled to obtain the labeling result.

[0053] The so-called ID labeling strategy refers to a pre-configured strategy for a target area, used to label whether a short message sent using the sender's ID should be sent.

[0054] According to the purpose of the annotation results, the annotation results can be divided into: annotation results used to indicate that short messages need to be sent through a specified communication channel, annotation results used to indicate that short messages need to be refused to be sent, and annotation results used to indicate that short messages need to be sent through a normal communication channel.

[0055] In one implementation, the sender ID of a short message is labeled using an ID labeling strategy corresponding to the target region to obtain a labeling result. This includes: first, using an ID interception strategy corresponding to the target region to intercept and detect the sender ID; then, when the sender ID passes the interception detection, the sender ID is labeled using the ID labeling strategy to obtain a labeling result.

[0056] An ID interception policy refers to a pre-configured strategy for a target region to block unauthorized sender IDs. Specifically, the ID interception policy detects and blocks sender IDs belonging to the sender ID blacklist corresponding to the target region, and also blocks sender IDs belonging to the sender ID whitelist corresponding to the target region after special character removal. When a sender ID is detected and blocked by the ID interception policy, sending SMS messages using that sender ID to the receiving device must be prohibited.

[0057] The SMS sending method provided in this embodiment first uses an ID interception strategy corresponding to the target region to intercept and detect the sender ID of the SMS. Only when the sender ID passes the interception detection is an ID labeling strategy further used to label the sender ID, obtaining the labeling result. By first using the ID interception strategy corresponding to the target region to intercept and detect the sender ID of the SMS, it is possible to initially intercept some sender IDs and SMS messages sent using the corresponding sender IDs, thereby further improving the interception of SMS messages sent using unauthorized sender IDs.

[0058] In addition, since the ID interception strategy corresponding to the target region is used to intercept and detect the sender ID of the short message, the ID interception strategy has better applicability to the target region.

[0059] In one implementation, reference is made to Figure 3 The implementation method of intercepting and detecting the sender ID of a short message using the ID interception strategy corresponding to the target area can include the following steps S301-308:

[0060] Step S301: Check whether the sender ID belongs to the sender ID blacklist corresponding to the target area.

[0061] The so-called sender ID blacklist is a list of IDs that are collected and marked for violations in a target area. Short messages sent using violating sender IDs in the sender ID blacklist must be prohibited from being sent to the receiving device.

[0062] The term "illegal sender ID" includes, but is not limited to, sender IDs that impersonate others, or sender IDs that have sent illegal or fraudulent text messages.

[0063] Step S302: When it is detected that the sender ID does not belong to the sender ID blacklist corresponding to the target area, check whether the sender ID belongs to the sender ID whitelist corresponding to the target area.

[0064] Specifically, when it is detected that the sender ID does not belong to the sender ID blacklist corresponding to the target area, it is necessary to first obtain the sender ID whitelist corresponding to the target area, and then further check whether the sender ID belongs to the sender ID whitelist.

[0065] A sender ID whitelist generally refers to a list of compliant sender IDs entered and marked by a sender ID monitoring agency. This agency is a pre-built monitoring network for a specific target region, used to monitor whether sender IDs meet the region's specified conditions. A compliant sender ID is one that has been entered into the sender ID monitoring agency and identified as meeting the specified conditions. These specified conditions may refer to registration by the SMS sender and manual review by the sender ID monitoring agency.

[0066] Step S303: When it is detected that the sender ID belongs to the sender ID whitelist, it is determined that the sender ID passes the interception detection.

[0067] In this embodiment, during the interception and detection of SMS sender IDs, if the sender ID is detected to be a compliant sender ID in the sender ID whitelist, then the sender ID is determined to have passed the interception and detection. When the sender ID is a compliant sender ID in the sender ID whitelist, it is determined that the sender ID has passed the interception and detection. This method can easily and accurately determine whether a sender ID can pass the interception and detection, thereby ensuring the efficiency and accuracy of the interception and detection, and thus more effectively intercepting SMS messages sent using unauthorized sender IDs.

[0068] Step S304: When it is detected that the sender ID does not belong to the sender ID whitelist, special characters are removed from the sender ID to obtain the processed sender ID.

[0069] During the process of intercepting and detecting the sender ID of a short message, if the sender ID is not a compliant sender ID in the sender ID whitelist, special characters need to be removed from the sender ID to obtain the processed sender ID.

[0070] In one implementation, the process of removing special characters from the sender ID to obtain the processed sender ID can be as follows:

[0071] First, convert the sender ID (string type) into a character array. For example, convert the sender ID "abcd1234" into the following character array: "a", "b", "c", "d", "1", "2", "3", "4".

[0072] Then, iterate through the characters in the character set and check if there are any special characters. For example, after converting the sender ID "abcd1@234" into the character set "a", "b", "c", "d", "@", "1", "2", "3", "4", check if there are any special characters in "a", "b", "c", "d", "@", "1", "2", "3", "4".

[0073] Special characters are symbols that are used less frequently and are difficult to input directly in most cases, in addition to traditional or commonly used symbols. For sender IDs, traditional or commonly used symbols are generally letters and numbers, while characters such as "!", "@", "#", "&", and "*" can generally be considered special characters. In practical applications, some symbols can be pre-configured as special characters. For example, only "!", "@", and "#" can be configured as special characters.

[0074] Finally, if special characters are detected in the character group, the special characters in the character group are excluded, and the remaining characters in the character group are used to reconstruct the sender ID into a string type to obtain the processed sender ID.

[0075] For example, if the characters "!", "@", "#", "&", and "*" are considered special characters, then in the character group "a", "b", "c", "d", "@", "1", "2", "3", "4", the character "@" is a special character. In this case, the character "@" needs to be excluded from the character group "a", "b", "c", "d", "@", "1", "2", "3", "4" to obtain a new character group "a", "b", "c", "d", "1", "2", "3", "4". After obtaining the new character group "a", "b", "c", "d", "1", "2", "3", "4", the characters in the new character group need to be further reassembled into a string type sender ID "abcd1234", and the string type sender ID "abcd1234" is determined as the processed sender ID.

[0076] In one implementation, the process of removing special characters from the sender ID to obtain the processed sender ID can also be as follows: input the sender ID into a trained ID processing model, obtain the sender ID that does not contain special characters output by the ID processing model, and determine the sender ID that does not contain special characters as the processed sender ID.

[0077] The so-called ID processing model is a model pre-trained based on sender ID samples and corresponding annotation results. It is used to remove special characters from the sender ID to be processed in order to obtain a sender ID that does not contain special characters.

[0078] Step S305: Check whether the processed sender ID belongs to the sender ID whitelist.

[0079] Step S306 determines that the sender ID passes the interception detection when it is detected that the processed sender ID does not belong to the sender ID whitelist.

[0080] Step S307: When it is detected that the processed sender ID belongs to the sender ID whitelist, it is determined that the sender ID has not passed the interception detection.

[0081] In one implementation, the process of detecting whether the processed sender ID belongs to the sender ID whitelist can be as follows: First, determine whether there is an ID in the sender ID whitelist that is the same as the processed sender ID. Then, if there is an ID that is the same as the processed sender ID, determine that the processed sender ID belongs to the sender ID whitelist.

[0082] Specifically, the processed sender ID can be compared sequentially with compliant sender IDs in the sender ID whitelist. If the processed sender ID matches any compliant sender ID in the sender ID whitelist, it is assumed that an ID identical to the processed sender ID exists in the sender ID whitelist. If the processed sender ID does not match any of the compliant sender IDs in the sender ID whitelist, it is assumed that no ID identical to the processed sender ID exists in the sender ID whitelist.

[0083] If an ID identical to the processed sender ID exists in the sender ID whitelist, it proves that the sender ID is suspected of impersonating a compliant sender ID by adding special characters. Identifying sender IDs suspected of impersonation as failing the interception detection can effectively block some unauthorized sender IDs and SMS messages sent using those IDs.

[0084] Step S308: When it is detected that the sender ID belongs to the sender ID blacklist corresponding to the target area, it is determined that the sender ID has not passed the interception detection.

[0085] In one implementation, refer to Figure 4 The implementation method of using the ID labeling strategy corresponding to the target area to label the sender ID of the short message and obtain the labeling result can include the following steps S401-409:

[0086] Step S401: In the pre-configured relationship list for the target area, determine whether there is a target correspondence relationship where the short message sender's identity identifier and sender ID match.

[0087] The relationship list refers to the mapping between specified identity identifiers and specified sender IDs. The specified sender IDs include compliant sender IDs from the sender ID whitelist. In other words, for each compliant sender ID in the sender ID whitelist, the mapping between it and the corresponding sender's identity identifier must be recorded and maintained in the relationship management module. The relationship management module is a module configured for the target region to manage the relationship list.

[0088] Furthermore, for sender IDs that are neither compliant nor non-compliant, the mapping relationship management module can also record and maintain the correspondence between them and the corresponding sender's identity. However, in recording and maintaining this mapping relationship, it is necessary to indicate that this type of sender ID is not a compliant sender ID.

[0089] Step S402: If there is a target correspondence in the relationship list configured for the target area that matches the identity identifier and sender ID of the short message sender, check whether the sender ID belongs to the sender ID whitelist corresponding to the target area.

[0090] Step S403: When it is detected that the sender ID belongs to the sender ID whitelist, the sender ID is marked as the ID that needs to send a short message through the specified communication channel, and the first marking result is obtained. The first marking result is used to indicate that a short message needs to be sent through the specified communication channel.

[0091] If a target correspondence exists in the mapping relationship and the sender ID is on the sender ID whitelist, it is sufficient to prove that the SMS sender used its own sender ID, and that sender ID is a compliant sender ID. In other words, the SMS sender used its own compliant sender ID to send the SMS. In this case, determining that the SMS needs to be sent through a designated communication channel can improve the SMS delivery success rate and the user experience for the SMS sender.

[0092] Step S404: If the target relationship does not exist in the relationship list, check whether the sender ID belongs to the sender ID whitelist.

[0093] Step S405: When it is detected that the sender ID belongs to the sender ID whitelist, the sender ID is marked as an ID that needs to be refused to send SMS messages, and a second marking result is obtained. The second marking result is used to indicate that SMS messages need to be refused to send.

[0094] If a target mapping does not exist in the mapping table, but the sender ID is on the sender ID whitelist, it proves that the SMS sender did not use their own sender ID, even though that sender ID is a compliant sender ID. That is, the SMS sender impersonated someone else's compliant sender ID to send the SMS. In this case, rejecting the SMS is necessary, effectively blocking SMS messages sent using someone else's compliant sender ID, and also improving the accuracy of blocking SMS messages sent using unauthorized sender IDs.

[0095] Step S406: When it is detected that the sender ID does not belong to the sender ID whitelist, special characters are removed from the sender ID to obtain the processed sender ID.

[0096] In one implementation, the process of removing special characters from the sender ID to obtain the processed sender ID can be as follows: First, the string-type sender ID is converted into a character group of type characters. Then, the characters in the character group are traversed, and it is checked whether there are any special characters in the character group. Finally, if special characters are detected in the character group, the special characters are removed, and the remaining characters in the character group are used to reconstruct the string-type sender ID to obtain the processed sender ID.

[0097] Step S407: Check whether the processed sender ID belongs to the sender ID whitelist.

[0098] In one implementation, the process of detecting whether the processed sender ID belongs to the sender ID whitelist can be as follows: First, determine whether there is an ID in the sender ID whitelist that is the same as the processed sender ID. Then, if there is an ID that is the same as the processed sender ID, determine that the processed sender ID belongs to the sender ID whitelist.

[0099] Step S408: When it is detected that the processed sender ID does not belong to the sender ID whitelist, the sender ID is marked as an ID that needs to send a short message through a normal communication channel, and a third marking result is obtained. The third marking result is used to indicate that a short message needs to be sent through a normal communication channel.

[0100] If the sender ID passes the interception detection, as long as there is no ID in the sender ID whitelist that matches the processed sender ID, it can be proven that although the SMS sender did not use a compliant sender ID to send the SMS, they also did not impersonate someone else's compliant sender ID to send the SMS. In this case, it is determined that the SMS should be sent through a normal communication channel, thus ensuring the success rate of SMS delivery.

[0101] Step S409: When it is detected that the processed sender ID belongs to the sender ID whitelist, the sender ID is marked as an ID that needs to be refused to send SMS messages, and the fourth marking result is obtained. The fourth marking result is used to indicate that SMS messages need to be refused to send.

[0102] If the sender ID passes the interception detection, but there is no ID in the sender ID whitelist that matches the processed sender ID, it can be proven that the sender ID is suspected of impersonating a compliant sender ID by adding special characters. In this case, it is determined that the SMS should be refused, which can effectively block some sender IDs and SMS messages sent using the corresponding sender ID.

[0103] In one implementation, refer to Figure 5 The process of checking whether the processed sender ID belongs to the sender ID whitelist can be as follows: Figure 5 As shown, Figure 5 An implementation of a sender ID detection method provided in this application embodiment may include the following steps S501-505:

[0104] Step S501: In the sender ID whitelist, determine whether there is an ID that is the same as the processed sender ID.

[0105] Step S502: If an ID with the same name as the processed sender ID exists, determine that the processed sender ID belongs to the sender ID whitelist.

[0106] Step S503: If there is no ID that is the same as the processed sender ID, convert the processed sender ID into an ID with a preset character format to obtain the converted sender ID.

[0107] The preset character format includes, but is not limited to, a character format containing only uppercase letters or a character format containing only lowercase letters. For example, if the sender ID is "abcd1234" and the preset character format is a character format containing only uppercase letters, the converted sender ID will be "ABCD1234".

[0108] Step S504: Convert the target sender ID in the sender ID whitelist into an ID in a preset character format to obtain the converted sender ID whitelist.

[0109] Convert all target sender IDs in the sender ID whitelist into IDs with a preset character format to obtain the converted sender ID whitelist. For example, convert all target sender IDs into sender IDs containing only uppercase letters, or convert all target sender IDs into sender IDs containing only lowercase letters.

[0110] Step S505: If there is an ID in the converted sender ID whitelist that is the same as the converted sender ID, then determine that the processed sender ID belongs to the sender ID whitelist.

[0111] Specifically, the converted sender ID can be compared sequentially with the sender IDs in the converted sender ID whitelist. If the converted sender ID matches any sender ID in the converted sender ID whitelist, then the processed sender ID is considered to belong to the sender ID whitelist.

[0112] Please refer to again Figure 2 After labeling the sender ID and obtaining the labeling results, step S203 needs to be executed further.

[0113] Step S203: When the annotation result indicates that a short message needs to be sent, a short message is sent to the receiving device.

[0114] In this embodiment, according to the purpose of the annotation results, the annotation results can be divided into: annotation results indicating that a short message needs to be sent through a specified communication channel, annotation results indicating that a short message needs to be refused to be sent, and annotation results indicating that a short message needs to be sent through a normal communication channel. When the annotation result indicates that a short message needs to be sent, the communication channel configured for the annotation result needs to be determined first, and then the short message is sent to the receiving device based on the communication channel. Specifically,

[0115] When the annotation result indicates that a short message needs to be sent via a specified communication channel, the short message must be sent to the receiving device via the specified communication channel. When the annotation result indicates that a short message needs to be sent via a normal communication channel, the short message must be sent to the receiving device via a normal communication channel.

[0116] In this embodiment, the designated communication channel refers to an SMS sending channel allocated to compliant sender IDs in the sender ID whitelist, dedicated to sending SMS messages sent using compliant sender IDs. The ordinary communication channel refers to an SMS sending channel allocated to ordinary sender IDs that are neither compliant nor non-compliant sender IDs, used to send SMS messages sent using ordinary sender IDs.

[0117] The SMS sending method provided in this embodiment, after determining the target area where the SMS recipient is located, uses an ID labeling strategy corresponding to the target area to label the sender ID of the SMS, obtaining a labeling result. Only when the labeling result indicates that an SMS needs to be sent will the corresponding SMS be sent to the recipient's device. Labeling the sender ID and only sending the corresponding SMS to the recipient's device when the labeling result indicates that an SMS needs to be sent can effectively intercept some sender IDs and SMS messages sent using those sender IDs.

[0118] In addition, since the SMS sending method provided in this application embodiment first determines the target area where the SMS recipient is located, and after determining the target area, it uses the ID labeling strategy corresponding to the target area to label the sender ID, the technical solution of this application has better applicability to the target area.

[0119] Based on the same technical concept, embodiments of this application also provide a short message sending device, such as... Figure 6 As shown, the device may include:

[0120] The target area determination module 601 is used to determine the target area where the short message recipient is located in response to the short message sent by the sending device; the labeling module 602 is used to label the sender ID of the short message using the ID labeling strategy corresponding to the target area, and obtain the labeling result; the short message sending module 603 is used to send the short message to the receiving device when the labeling result indicates that the short message needs to be sent.

[0121] In one embodiment, the annotation module 602 includes: an interception detection submodule, used to intercept and detect the sender ID using the ID interception strategy corresponding to the target region; and an annotation submodule, used to annotate the sender ID using the ID annotation strategy when the sender ID passes the interception detection, thereby obtaining an annotation result. In one embodiment, the interception detection submodule is specifically used to detect whether the sender ID belongs to the sender ID whitelist corresponding to the target region when it is detected that the sender ID does not belong to the sender ID blacklist corresponding to the target region; and to determine that the sender ID passes the interception detection when it is detected that the sender ID belongs to the sender ID whitelist corresponding to the target region.

[0122] In one implementation, the interception and detection submodule is further configured to, when it is detected that the sender ID does not belong to the sender ID whitelist, remove special characters from the sender ID to obtain the processed sender ID; detect whether the processed sender ID belongs to the sender ID whitelist; and determine that the sender ID passes the interception and detection when it is detected that the processed sender ID does not belong to the sender ID whitelist.

[0123] In one embodiment, the annotation module 603 is specifically used to detect whether the sender ID belongs to the sender ID whitelist corresponding to the target area when there is a target correspondence in the relationship list configured for the target area that matches the identity identifier and sender ID of the sender of the short message. The relationship list includes the correspondence between the specified identity identifier and the specified sender ID. When it is detected that the sender ID belongs to the sender ID whitelist, the sender ID is marked as the ID that needs to send the short message through the specified communication channel, and a first annotation result is obtained. The first annotation result is used to indicate that the short message needs to be sent through the specified communication channel.

[0124] In one embodiment, the annotation module 603 is further configured to detect whether the sender ID belongs to the sender ID whitelist when there is no target corresponding relationship in the relationship list; when the sender ID is detected to belong to the sender ID whitelist, the sender ID is marked as an ID that needs to be refused to send SMS messages, and a second annotation result is obtained, which is used to indicate that SMS messages need to be refused to send.

[0125] In one embodiment, the annotation module 603 is further configured to, when it is detected that the sender ID does not belong to the sender ID whitelist, perform special character removal processing on the sender ID to obtain the processed sender ID; detect whether the processed sender ID belongs to the sender ID whitelist; when it is detected that the processed sender ID does not belong to the sender ID whitelist, annotate the sender ID as an ID that needs to be sent via a normal communication channel to obtain a third annotation result, which is used to indicate that a short message needs to be sent via a normal communication channel.

[0126] In one embodiment, the annotation module 603 is further configured to annotate the sender ID as an ID that needs to be refused when it detects that the processed sender ID belongs to the sender ID whitelist, thereby obtaining a fourth annotation result, which is used to indicate that the sending of the SMS needs to be refused.

[0127] In one embodiment, the interception detection module 602 includes: a sender ID whitelist detection subunit, used to determine whether there is an ID in the sender ID whitelist that is the same as the processed sender ID; when there is an ID that is the same as the processed sender ID, it is determined that the processed sender ID belongs to the sender ID whitelist.

[0128] In one embodiment, the sender ID whitelist detection subunit is further configured to convert the processed sender ID into a preset character format ID to obtain a converted sender ID when no ID with the same name as the processed sender ID exists; convert the target sender ID in the sender ID whitelist into a preset character format ID to obtain a converted sender ID whitelist; and determine that the processed sender ID belongs to the sender ID whitelist when an ID with the same name as the converted sender ID exists in the converted sender ID whitelist.

[0129] In one embodiment, the short message sending module 604 is specifically used to determine the communication channel configured for the annotation result when the annotation result indicates that a short message needs to be sent; and to send a short message to the receiving device based on the communication channel.

[0130] Based on the same technical concept, embodiments of this application also provide an electronic device, such as... Figure 7 As shown, the electronic device includes a memory 710 and a processor 720. The memory 710 stores a computer program that can run on the processor 720. When the processor 720 executes the computer program, it implements the method described in the above embodiments. The number of memories 710 and processors 720 can be one or more.

[0131] The electronic device also includes:

[0132] The communication interface 730 is used to communicate with external devices and perform data exchange and transmission.

[0133] If the memory 710, processor 720, and communication interface 730 are implemented independently, they can be interconnected via a bus to communicate with each other. This bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 7 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0134] Optionally, in a specific implementation, if the memory 710, processor 720, and communication interface 730 are integrated on a single chip, then the memory 710, processor 720, and communication interface 730 can communicate with each other through an internal interface.

[0135] This application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the method provided in this application.

[0136] This application also provides a chip, which includes a processor for calling and executing instructions stored in a memory, causing a communication device on which the chip is installed to perform the method provided in this application.

[0137] This application also provides a chip, including: an input interface, an output interface, a processor, and a memory. The input interface, output interface, processor, and memory are connected through an internal connection path. The processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the application embodiment.

[0138] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting Advanced Reduced Instruction Set Machines (ARM) architecture.

[0139] Further, optionally, the aforementioned memory may include read-only memory and random access memory, and may also include non-volatile random access memory. The memory may be volatile or non-volatile, or may include both. Non-volatile memory may include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may include random access memory (RAM), which serves as an external cache. Many forms of RAM are available by way of example, but not limitation. Examples include Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0140] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another.

[0141] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of those different embodiments or examples.

[0142] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.

[0143] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process. Furthermore, the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functionality involved.

[0144] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0145] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware, the program being stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiments.

[0146] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. This storage medium can be a read-only memory, a disk, or an optical disk, etc.

[0147] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope disclosed in this application, and these should all be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for sending a short message, characterized in that, include: In response to a short message sent by the sending device, determine the target area where the short message recipient is located; Using the ID labeling strategy corresponding to the target area, the sender ID of the short message is labeled to obtain the labeling result; When the annotation result indicates that the short message needs to be sent, the short message is sent to the receiving device; The step of using the ID labeling strategy corresponding to the target region to label the sender ID of the short message and obtain the labeling result includes: If, in the relationship list configured for the target region, there exists a target correspondence that matches the sender's identity identifier and the sender ID of the short message, it is checked whether the sender ID belongs to the sender ID whitelist corresponding to the target region; the relationship list includes the correspondence between a specified identity identifier and a specified sender ID; When it is detected that the sender ID belongs to the sender ID whitelist, the sender ID is marked as an ID that needs to send the short message through the specified communication channel, and a first marking result is obtained; the first marking result is used to indicate that the short message needs to be sent through the specified communication channel; The method further includes: When it is detected that the sender ID does not belong to the sender ID whitelist corresponding to the target area, special characters are removed from the sender ID to obtain the processed sender ID; Detect whether the processed sender ID belongs to the sender ID whitelist; When it is detected that the processed sender ID does not belong to the sender ID whitelist, the sender ID is marked as an ID that needs to be sent through the normal communication channel, and a third marking result is obtained; the third marking result is used to indicate that the short message needs to be sent through the normal communication channel.

2. The method for sending short messages according to claim 1, characterized in that, The step of using the ID labeling strategy corresponding to the target region to label the sender ID of the short message and obtain the labeling result includes: The sender ID is intercepted and detected using the ID interception strategy corresponding to the target area; When the sender ID passes the interception detection, the sender ID is labeled using the ID labeling strategy to obtain the labeling result.

3. The method for sending short messages according to claim 2, characterized in that, The step of using the ID interception strategy corresponding to the target region to intercept and detect the sender ID includes: When it is detected that the sender ID does not belong to the sender ID blacklist corresponding to the target area, it is detected whether the sender ID belongs to the sender ID whitelist corresponding to the target area; When it is detected that the sender ID belongs to the sender ID whitelist, it is determined that the sender ID passes the interception detection.

4. The method for sending short messages according to claim 3, characterized in that, The method further includes: When it is detected that the sender ID does not belong to the sender ID whitelist, special characters are removed from the sender ID to obtain the processed sender ID; Detect whether the processed sender ID belongs to the sender ID whitelist; If it is detected that the processed sender ID does not belong to the sender ID whitelist, it is determined that the sender ID has passed the interception detection.

5. The method for sending short messages according to claim 1, characterized in that, The method further includes: If the target corresponding relationship does not exist in the relationship list, check whether the sender ID belongs to the sender ID whitelist; When it is detected that the sender ID belongs to the sender ID whitelist, the sender ID is marked as an ID that needs to be refused to send the SMS, and a second marking result is obtained; the second marking result is used to indicate that the SMS needs to be refused to send.

6. The method for sending short messages according to claim 1, characterized in that, The method further includes: When it is detected that the processed sender ID belongs to the sender ID whitelist, the sender ID is marked as an ID that needs to be refused to send the short message, and a fourth marking result is obtained; the fourth marking result is used to indicate that the short message needs to be refused to send.

7. The method for sending short messages according to claim 4, characterized in that, The step of detecting whether the processed sender ID belongs to the sender ID whitelist includes: In the sender ID whitelist, determine whether there is an ID that is the same as the processed sender ID; If an ID with the same name as the processed sender ID exists, it is determined that the processed sender ID belongs to the sender ID whitelist.

8. The method for sending short messages according to claim 7, characterized in that, The method further includes: If no ID exists that is identical to the processed sender ID, the processed sender ID is converted into an ID in a preset character format to obtain the converted sender ID. Convert the target sender ID in the sender ID whitelist into an ID with a preset character format to obtain the converted sender ID whitelist; If an ID identical to the converted sender ID exists in the whitelist of senter IDs, then the processed sender ID is determined to belong to the whitelist of senter IDs.

9. The method for sending short messages according to claim 1, characterized in that, Sending the short message to the receiving device includes: When the annotation result indicates that the short message needs to be sent, determine the communication channel configured for the annotation result; Based on the communication channel, the short message is sent to the receiving device.

10. A device for sending short messages, characterized in that, include: The target area determination module is used to determine the target area where the SMS recipient is located in response to an SMS sent by the sending device. The annotation module is used to annotate the sender ID of the short message using the ID annotation strategy corresponding to the target area, and obtain the annotation result; The short message sending module is used to send the short message to the receiving device when the annotation result indicates that the short message needs to be sent; Specifically, the annotation module is used to detect whether the sender ID belongs to the sender ID whitelist corresponding to the target area when there is a target correspondence in the relationship list configured for the target area that matches the sender's identity identifier and the sender ID of the short message; the relationship list includes the correspondence between a specified identity identifier and a specified sender ID; when the sender ID is detected to belong to the sender ID whitelist, the sender ID is annotated as the ID that needs to send the short message through the specified communication channel, and a first annotation result is obtained; the first annotation result is used to indicate that the short message needs to be sent through the specified communication channel; The annotation module is further configured to, when detecting that the sender ID does not belong to the sender ID whitelist corresponding to the target area, perform special character removal processing on the sender ID to obtain a processed sender ID; detect whether the processed sender ID belongs to the sender ID whitelist; when detecting that the processed sender ID does not belong to the sender ID whitelist, annotate the sender ID as an ID that needs to send short messages through a normal communication channel to obtain a third annotation result, the third annotation result being used to indicate that short messages need to be sent through a normal communication channel.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory, wherein the processor, when executing the computer program, implements the method for sending a short message as described in any one of claims 1-9.

12. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method for sending a short message according to any one of claims 1-9.

Images