The document discusses the Short Message Peer to Peer (SMPP) protocol, which is an open standard for exchanging short message data between SMS message centers and external client applications. It describes how SMPP uses requests and responses to facilitate communication between an External Short Message Entity (ESME) and an SMSC. Key aspects of SMPP covered include the session and binding procedures, protocol data units, operations, and error handling.

1. SMPP SMSC Communication Protocol Nuruddin Ashr [email_address]

2. About Presenter Work on mobile messaging company Author of open source smpp library http://code.google.com/p/jsmpp

3. SMS (Short Message Service) Send/exchange message between mobile station (mobile phone) SMSC (Short Message Service Center) Route the message to mobile phone or other entities

4. SMS (Short Message Service) Message exchange between mobile stations SMSC Message for B Message for B Message for A Message for A Mobile station A Mobile station B

5. SMS (Short Message Service) Message exchange between ESME and mobile stations SMSC Other Entity Mobile Stations Messages Messages Protocol?

6. SMSC Protocol To communicate with SMSC, we need SMSC Protocol SMSC Protocol developed by SMSC Vendor

7. SMSC Protocol To communicate with SMSC, we need SMSC Protocol SMSC Protocol developed by SMSC Vendor So it's proprietary :-(

8. SMSC Protocol Logica CMG EMI (External Machine Interface) UCP (Universal Computer Protocol) SMPP (Short Message Peer to Peer) Protocol Nokia CIMD (Computer Interface to Message Distribution) Airwide Solutions OIS (Open Interface Specification) SMS2000

9. SMSC Protocol Why use SMPP...?

10. SMPP: introduction The Short Message Peer to Peer (SMPP) protocol is an open, industry standard protocol designed to provide a flexible data communications interface for transfer of short message data between a Message Center .

11. SMPP: history Now is open protocol – SMS Forum Widely used SMPP Version SMPP v3.3 (developed by Aldiscon) SMPP v4.0 (developed by Logica) SMPP v3.4 (SMPP Developer Forums – Open Protocol) SMPP v5.0 (SMS Forum)

12. Typical Application Mobile Commerce Mobile Banking E-Mail Gateway Information Service Notification/Security Application Cell Broadcast Directory Service Telemetry Application

13. Typical Application SMS Chat Polling Application Gaming/Quiz More explaination: SMPP Protocol Spesification v3.4 page 12 SMPP Protocol Spesification v5.0 page 19

14. Protocol Overview SMSC Other Entity Mobile Stations Messages Messages Protocol? SMSC ESME SME Messages Messages SMPP

15. Protocol Overview ESME = External Short Message Entity SME = Short Message Entity SMSC ESME SME Messages Messages SMPP Mobile Network

16. Protocol Overview: SMPP Short Message Peer to Peer (SMPP) protocol is an open message-transfer protocol that enables short message entities ( SME s) outside the mobile network to interface with an SMSC . Non-mobile entities that submit messages to, or receive messages from an SMSC are known as External Short Message Entities ( ESME s).

17. Protocol Overview SMSC ESME SME Messages Messages SMPP Mobile Network TCP/IP or X.25 network connection

18. Protocol Overview Based on request and response The SMPP protocol defines Set of operations and Protocol Data Units ( PDU s) Data

19. Protocol Overview Every SMPP operation consist of a request and associated response (but some have exception). ESME SMSC Request Response

20. Protocol Overview Messages exchange category Messages sent from the ESME ( Transmitter ) to the SMSC Messages sent from the SMSC to the ESME ( Receiver ) Messages sent from the ESME ( Transceiver ) to the SMSC and messages sent from the SMSC to the ESME ( Transceiver )

21. Protocol Overview SMSC ESME ESME ESME Transmitter Transceiver Receiever

22. SMPP Session Session initiated by ESME Session states: OPEN (Network connection established) BOUND_TX (ESME issuing a bind_transmitter PDU) BOUND_RX (ESME issuing a bind_receiver PDU) BOUND_TRX (ESME issuing a bind_transceiver PDU) UNBOUND (only on SMPP v5.0) CLOSED (Network connection closed)

23. SMPP Session: transmitter (TX) ESME SMSC Network connection bind_transmitter bind_transmitter_resp Send short messages

24. SMPP Session: receiver (RX) ESME SMSC Network connection bind_receiver bind_receiver_resp Receive short messages

25. SMPP Session: transceiver (TRX) ESME SMSC Network connection bind_transceiver bind_transceiver_resp Send and receive short messages

26. SMPP Session Question: How if SMSC want to send messages but there is no valid SMPP session? Use outbind operation

27. SMPP Session The purpose of the outbind operation is to allow the SMSC signal an ESME to originate a bind_receiver request to the SMSC.

28. SMPP Session: using outbind ESME SMSC Network connection outbind bind_receiver Receive short messages bind_receiver_resp

29. SMPP PDU: overview Protocol Data Units Set of bytes 8 bit = 1 byte = 1 octet PDU Header always mandatory

30. SMPP PDU: command length Represent whole bytes length of the SMPP command

31. SMPP PDU: command id Unique command identifier bind_transmitter, bind_transmitter_resp submit_sm, submit_sm_resp Request 0x00000001 having response 0x80000001

32. SMPP PDU: command status Indicate success or failure of SMPP request Command status on request PDU always zero Non-zero command status can be happen on response PDU

33. SMPP PDU: sequence number Sequence number is an incremental number Increase monotonically for each submitted SMPP request PDU Having range 0x00000001 - 0x7FFFFFFF

34. SMPP PDU: deeper Header is mandatory Some PDU has no body Some PDU has no optional parameters Optional parameters are OPTIONAL

35. SMPP PDU: optional parameter

36. Typical Session Sequence: TX Synchronous Asynchronous Response - request pair indicated by same sequence number

37. Typical Session Sequence: RX

38. Typical Session Sequence: TRX

39. Error Handling Response should be receive in a specified interval time ( transaction time ) Response have a non-zero command_status If an error found on PDU Header , generick_nack PDU should be send

40. SMPP Timers Session initiation timer Session timer (enquire link timer) Inactivity timer Transaction timer (response timer)

41. Data Type Integer Value with defined number of octets C-Octet String Series of ASCII characters Terminated with NULL character C-Octet String (Decimal) Same as C-Octet String But numeric characters only (0 - 9)

42. Data Type C-Octet String (Hex) Same as C-Octet String But hexadecimal characters only (0 - F)

43. SMPP Operations See the SMPP Specification :-P

44. References Short Message Peer to Peer Protocol Spesification v3.4 Short Message Peer to Peer Protocol Spesification v5.0 http://www.developershome.com/sms/howToReceiveSMSUsingPC4.asp http://en.wikipedia.org/wiki/Short_message_peer-to-peer_protocol