Suppression of short message service communications from a trusted domain

1. One or more nontransitory computer-readable media having computer-executable instructions embodied thereon that, when executed, perform a method for suppressing Short Message Service (SMS) communications from a Short Message peer-to-peer (SMPP) client, the method comprising:

detecting an undesired SMS communication that is communicated to the server by way of the SMPP client;

communicating a challenge to the SMPP client from the server;

when a challenge response is not received at the server, throttling communications received from the SMPP client; and

when the challenge response is received at the server, verifying the validity of the challenge response based on an algorithm previously supplied to the SMPP client.

2. The media of claim 1 , wherein verifying the validity of the challenge response includes utilizing an algorithm associated with the SMPP client to verify that a response provided by the SMPP client corresponds with a value achieved by the algorithm associated with the SMPP client.

3. The media of claim 1 , wherein detecting an undesired SMS communication is based on a threshold of undesired SMS communications.

4. The media of claim 3 , wherein the threshold is based on a number of the undesired SMS communications.

5. The media of claim 3 , wherein the threshold is based on resources consumed as a result of the undesired SMS communications.

6. A method for suppressing Short Message Service (SMS) communications from a Short Message peer-to-peer (SMPP) client, the method comprising:

detecting an undesired SMS communication that is communicated to the server by way of the SMPP client;

communicating a challenge to the SMPP client from the server;

when a challenge response is received at the server, verifying the validity of the challenge response based on an algorithm previously supplied to the SMPP client;

when the challenge response is valid, then determining a status of the SMPP client; and

determining whether to throttle communications received from the SMPP client based on the status of the SMPP client.

7. The method of claim 6 , further comprising when the challenge response is not received at the server, throttling communications received from the SMPP client.

8. The method of claim 6 , wherein verifying the validity of the challenge response includes utilizing an algorithm associated with the SMPP client to verify that a response provided by the SMPP client corresponds with a value achieved by the algorithm associated with the SMPP client.

9. The method of claim 6 , wherein detecting an undesired SMS communication is based on a threshold of undesired SMS communications.

10. The method of claim 9 , wherein the threshold is based on a tolerance of one or more recipients of the undesired SMS communications.

11. The method of claim 9 , wherein the threshold is based on resources consumed as a result of the undesired SMS communications.

12. A method for suppressing Short Message Service (SMS) communications from a Short Message peer-to-peer (SMPP) client, the method comprising:

providing a selected response algorithm to the SMPP client from a server, wherein the selected response algorithm is utilized by the SMPP client to generate a challenge response that verifies the identity of the SMPP client upon the receipt of a challenge from the server;

detecting an undesired SMS communication (SPAM) from a SPAM originator that is communicated to the server by way of the SMPP client;

identifying a source identifier of the SPAM originator, wherein the source identifier uniquely identifies the SPAM originator;

communicating the challenge to the SMPP client from the server;

when the challenge response is received at the server and the challenge response is incorrect, throttling communications received from the SMPP client;

when the challenge response is received at the server and the challenge response is correct, communicating the source identifier to the SMPP client from the server;

when a source identifier response is not received from the SMPP client in response to communicating the source identifier, then throttling communications received from the SMPP client;

when the source identifier response is received from the SMPP client, then determining a status of the SMPP client based on the source identifier response; and

determining whether to throttle communications received from the SMPP client based on the status of the SMPP client.

13. The method of claim 12 , wherein the status of the SMPP client includes at least one of,

A) being in a process of verifying the source identifier,

B) the source identifier is verified,

C) the source identifier is not verified and the SMPP client will handle the SPAM, and

D) the source identifier is not verified and the server should handle the SPAM.

14. The method of claim 12 , wherein detecting the SPAM includes detecting a threshold amount of SPAM from the SPAM originator that is communicated to the server by way of the SMPP client.

15. The method of claim 12 , wherein the challenge response is determined to be correct or incorrect based on an algorithm previously supplied to the SMPP client.

16. The method of claim 12 , wherein the challenge response is determined to be correct or incorrect by verifying whether a response provided by the SMPP client corresponds with a value achieved by an algorithm associated with the SMPP client.

17. The method of claim 12 , wherein detecting an undesired SMS communication is based on a threshold of undesired SMS communications.

18. The method of claim 17 , wherein the threshold is based on

A) a number of the undesired SMS communications or

B) resources consumed as a result of the undesired SMS communications.