Introduction to SMPP (Short Message Peer-to-peer)

Posted by TeleOss on January 30th, 2020

SMPP protocol, a shorthand for “Short Message Peer to Peer protocol,” is an open-source industry-standard protocol developed for providing a simple data transmission interface, where flexible data can be communicated from one Message Center to another. Examples of a Message Center include SMSC (Short Message Service Centre), USSD (GSM Unstructured Supplementary Services Data), and another form of Message Centers. It also provides an interface for other servers like E-mail Gateway and WAP Proxy Server.

SMPP works contrary to its own name, as it employs a client-server prototype. This connection is created as a ‘bind,' all the way from the client to the server. The bind is also a primary requirement to be obtained before SMS messages can be sent via the SMPP protocol since this bind command is in charge of determining the direction in which SMS messages will pass.

The SMPP protocol will especially be relevant for those of you who have the expertise in-house, such as domain experts, to manage the SMPP connection.

SMPP is a general standard laid down for SMS processes — regarding how large volumes of SMS can be sent in a very fast and reliable manner. It can be incorporated into businesses by huge marketing campaigns, SMS voting, news updating, warnings and so forth.

The following bulleted lists show the Digital Cellular technology the newly released SMPP v3.4 is compatible on.

1. iDEN

2. ANSI-136 (TDMA)

3. 1S-95 (CDMA)

4. GSM

   Through the implementation of SMPP protocol, ESME (External Short Message Entity) — an application system for SMS — can be used to activate a connection at the application layer with a Short Message Service Center (SMSC) across a X.25 or the popular TCP/IP network connection. Short messages can then be transmitted and received through this SMSC accordingly. The ESME may also use the SMPP protocol to cancel, replace, or query short protocol.

   SMPP also aids a full-featured set of 2-way SMS functions like:

   1. It sets the validity period for short message.

   2. Assign a service type with each SMS, such as voice mail.

   3. State the short message data encoding type

   4. Define the short message delivery priority.

   5. Select the mode of the message, such as forward, datagram, or store.

   6. Set the delivery time and date of the message.

   7. Deliver a short message (a registered one), in which a “delivery receipt” is sent for by the SMSC to the originator of the message.

   8. Delete or replace the short message saved on the SMSC

   9. Query the short message status while it is being saved on the SMSC.

   10. Messages may be received by the ESME through the SMSC from other SME'S, such as mobile stations.

   11. Send messages to a single or multiple end from an ESME through the SMSC.