Example: air traffic controller

Short Message Peer-to-Peer Protocol Specification …

SMS FORUM. Short Message Peer-to-Peer Protocol Specification Version SMS FORUM. Short Message peer to peer Protocol Specification 19-February-2003. 1999-2003 SMS Forum. COPYRIGHT. All rights reserved. This document or any part thereof may not, without the prior written consent of SMS Forum, be copied, reprinted or reproduced in any material form including, but without prejudice to the foregoing and not by way of exception photocopying, transcribing, transmitting or storing in any medium or translating into any language, in any form or by any means, including but not limited to, electronic, mechanical, xerographic, optical, magnetic, digital or other methodology. DISCLAIMER. WHILST THE GREATEST CARE HAS BEEN TAKEN TO ENSURE THE ACCURACY OF. THE INFORMATION AND DATA CONTAINED HEREIN, SMS FORUM DOES NOT. WARRANT THE ACCURACY OR SUITABILITY OF SAME FOR ANY SPECIFIC USE. SMS. FORUM EXPRESSLY DISCLAIMS ALL AND ANY LIABILITY TO ANY PERSON, WHETHER. A PURCHASER OR OTHERWISE, IN RESPECT OF ANY CONSEQUENCES OF.

www.smsforum.net SMPP V5.0 SMS Forum 2 of 166 SMS FORUM Short Message Peer to Peer Protocol Specification v5.0 19-February-2003 1999-2003 SMS Forum.

Tags:

  Short, Message, Peer, Short message peer to peer

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Advertisement

Transcription of Short Message Peer-to-Peer Protocol Specification …

1 SMS FORUM. Short Message Peer-to-Peer Protocol Specification Version SMS FORUM. Short Message peer to peer Protocol Specification 19-February-2003. 1999-2003 SMS Forum. COPYRIGHT. All rights reserved. This document or any part thereof may not, without the prior written consent of SMS Forum, be copied, reprinted or reproduced in any material form including, but without prejudice to the foregoing and not by way of exception photocopying, transcribing, transmitting or storing in any medium or translating into any language, in any form or by any means, including but not limited to, electronic, mechanical, xerographic, optical, magnetic, digital or other methodology. DISCLAIMER. WHILST THE GREATEST CARE HAS BEEN TAKEN TO ENSURE THE ACCURACY OF. THE INFORMATION AND DATA CONTAINED HEREIN, SMS FORUM DOES NOT. WARRANT THE ACCURACY OR SUITABILITY OF SAME FOR ANY SPECIFIC USE. SMS. FORUM EXPRESSLY DISCLAIMS ALL AND ANY LIABILITY TO ANY PERSON, WHETHER. A PURCHASER OR OTHERWISE, IN RESPECT OF ANY CONSEQUENCES OF.

2 ANYTHING DONE OR OMITTED TO BE DONE BY ANY SUCH PERSON IN PARTIAL OR. TOTAL RELIANCE UPON THE WHOLE OR ANY PART OF THE CONTENTS OF THIS. PUBLICATION OR ANY DERIVATIVE THEREOF. THE INFORMATION CONTAINED HEREIN IS BELIEVED TO BE ACCURATE AND. RELIABLE. HOWEVER, SMS FORUM ACCEPTS NO RESPONSIBILITY FOR ITS' USE BY. ANY MEANS OR IN ANY WAY WHATSOEVER. SMS FORUM SHALL NOT BE LIABLE. FOR ANY EXPENSES, COSTS OR DAMAGE THAT MAY RESULT FROM THE USE OF. THE INFORMATION CONTAINED HOWSOEVER ARISING IN THIS DOCUMENT OR ANY. DERIVATIVE THEREOF. NOTE 1: THE INFORMATION CONTAINED IN THE WITHIN DOCUMENT AND ANY. DERIVATIVE THEREOF IS SUBJECT TO CHANGE WITHOUT NOTICE. NOTE 2: THE CORPORATE NAME OF SMS FORUM IS NORTHGROVE LIMITED, COMPANY NUMBER 309113, REGISTERED OFFICE GARDNER HOUSE, WILTON. PLACE, DUBLIN 2. SMPP SMS Forum 2 of 166. SMS FORUM. Table Of Contents 1 Introduction ..12. Scope Of This Document ..13. Glossary ..13. References ..14. SMPP Overview ..16. Protocol Versions ..17. Supported Cellular Typical Applications of SMPP.

3 19. SMPP Sessions ..20. Protocol Operations and Session Management Operations ..21. Message Submission Message Delivery Message Broadcast Operations ..23. Anciliary Submission Operations ..23. Anciliary Broadcast Operations ..24. 2 SMPP Sessions ..25. Application Layer Establishing a SMPP Session States ..26. Bound_TX ..26. Closed ..28. Outbound ..28. Operation Sample Example Transmitter Session ..31. Example Receiver Session ..32. Example Transceiver Session ..33. Example Transmitter Session (Cell Broadcast Entity) ..34. Example Outbind PDU The PDU Sequence Number ..36. Why use Monotonically Increasing Sequence numbers?..37. Sequence Numbers Across Sessions ..37. Synchronous Vs. Asynchronous ..37. Why Asynchronous? ..39. Session Error Handling ..41. Handling Connection Operation Failure ..42. Flow Control and Congestion Session Security and Leased Secure Transport Layer ..45. Secure VPN ..45. Secure Forward and Backward Compatibility ..47. Forward Compatibility ..47. Backward 3 SMPP Parameter and PDU Parameter Type NULL Settings.

4 51. SMPP Parameter Field Size SMPP SMS Forum 3 of 166. SMS FORUM. General PDU PDU Format ..53. Command_status ..54. Standard Parameters ..54. TLV Parameters ..54. A sample 4 SMPP PDU Session Management Operations ..56. Bind Operation ..56. bind_transmitter Syntax ..56. bind_transmitter_resp Syntax ..57. bind_receiver Syntax ..58. bind_receiver_resp Syntax ..59. bind_transceiver bind_transceiver_resp outbind Syntax..61. unbind Syntax ..61. unbind_resp Syntax ..62. Enquire Link Operation ..63. enquire_link enquire_link_resp Alert Notification Operation ..64. alert_notification Syntax ..64. Generic NACK generic_nack Message Submission submit_sm Operation ..66. submit_sm submit_sm_resp data_sm data_sm Syntax ..69. data_sm_resp Syntax ..70. submit_multi Operation ..71. submit_multi Syntax ..71. submit_multi_resp Syntax ..74. Message Submission Request TLVs ..75. Message Submission Response TLVs ..77. Source and Destination International and National Alphanumeric NPI ..78. ESME Addresses.

5 78. Message Replace operation in submit_sm ..79. Message Message Types ..79. Scheduled ..80. Message Modes ..81. Default Message Mode ..81. Store and Forward Message Mode ..81. Datagram Message Transaction Message Message Delivery Operations ..85. deliver_sm Operation ..85. SMPP SMS Forum 4 of 166. SMS FORUM. deliver_sm deliver_sm_resp Syntax ..87. data_sm Message Delivery Request Message Delivery Response Delivery Message MC Delivery Receipt ..90. Intermediate Notification ..91. SME Delivery SME Manual/User Acknowledgement ..91. Conversation Abort ..91. Message Broadcast broadcast_sm broadcast_sm Syntax ..92. broadcast_sm_resp Syntax ..96. Broadcast Request Optional Broadcast Response Optional Message Replacement with broadcast_sm ..99. Ancillary Submission Operations ..100. cancel_sm Operation ..100. cancel_sm cancel_sm_resp query_sm query_sm Syntax ..102. query_sm_resp Syntax ..103. replace_sm replace_sm Syntax ..104. replace_sm_resp Syntax ..106. Message Replacement Ancillary Broadcast query_broadcast_sm query_broadcast_sm Syntax.

6 107. Query Broadcast Request Optional TLVs ..108. query_broadcast_sm_resp Syntax ..108. Query Broadcast Response Optional cancel_broadcast_sm Operation ..110. cancel_broadcast_sm Cancel Broadcast Optional TLVs ..111. cancel_broadcast_sm_resp PDU Field Definitions ..113. addr_ton, source_addr_ton, dest_addr_ton, esme_addr_ton ..113. addr_npi, source_addr_npi, dest_addr_npi, esme_addr_npi ..113. address_range ..114. UNIX Regular Expressions ..114. command_status, error_status_code ..116. esme_addr ..124. esm_class ..125. no_unsuccess ..129. number_of_dests ..129. SMPP SMS Forum 5 of 166. SMS FORUM. registered_delivery ..130. scheduled_delivery_time, validity_period, scheduled_delivery_time ..131. validity_period ..131. Absolute Time Relative Time service_type ..133. sm_default_msg_id ..134. sm_length ..134. source_addr ..134. system_id ..134. system_type ..134. PDU TLV TLV TLV Length ..137. TLV TLV Definitions ..137. additional_status_info_text ..137. alert_on_message_delivery.

7 137. billing_identification ..138. broadcast_area_identifier, Broadcast Area Format types ..138. broadcast_area_success ..139. broadcast_channel_indicator ..139. broadcast_end_time ..142. broadcast_error_status ..142. broadcast _frequency broadcast_message_class ..143. broadcast_rep_num ..144. callback_num ..145. callback_num_atag ..146. callback_num_pres_ind ..146. congestion_state ..147. dest_addr_np_country ..148. dest_addr_np_information ..148. dest_addr_np_resolution ..148. dest_addr_subunit ..149. dest_bearer_type ..149. dest_network_id ..149. dest_network_type ..150. dest_telematics_id ..151. dest_port ..151. display_time ..151. dpf_result ..152. its_reply_type ..152. SMPP SMS Forum 6 of 166. SMS FORUM. more_messages_to_send ..154. ms_msg_wait_facilities ..155. ms_validity ..156. number_of_messages ..157. privacy_indicator ..158. qos_time_to_live ..159. sar_msg_ref_num ..159. sar_segment_seqnum ..160. sar_total_segments ..160. set_dpf ..161. sms_signal ..161. source_addr_subunit.

8 161. source_node_id ..164. source_port ..164. source_subaddress ..165. source_telematics_id ..165. user_message_reference ..166. user_response_code ..166. SMPP SMS Forum 7 of 166. SMS FORUM. List Of Tables Table 1-1 Glossary 13. Table 1-2 References 16. Table 1-3 SMPP Protocol Versions 18. Table 1-4 Session Management Operations 22. Table 1-5 Message Submission Operations 23. Table 1-6 Message Delivery Operations 23. Table 1-7 Message Broadcast Operations 23. Table 1-8 Anciliary Submission Operations 24. Table 1-9 Anciliary Broadcast Operations 24. Table 2-1 Operation Matrix 30. Table 2-2 SMPP Session Timers 41. Table 3-1 SMPP PDU Parameter Types 50. Table 3-2 SMPP PDU Parameter Type NULL Settings 51. Table 3-3 SMPP PDU Parameter Type Size Notation 52. Table 3-4 SMPP PDU Format 53. Table 3-5 SMPP PDU Format 53. Table 4-1 bind_transmitter PDU 57. Table 4-2 bind_transmitter_resp PDU 57. Table 4-3 bind_receiver PDU 58. Table 4-4 bind_receiver_resp PDU 59. Table 4-5 bind_transceiver PDU 60.

9 Table 4-6 bind_transceiver_resp PDU 60. Table 4-7outbind PDU 61. Table 4-8 unbind PDU 61. Table 4-9 unbind_resp PDU 62. Table 4-10 enquire_link PDU 63. Table 4-11 enquire_link_resp PDU 63. Table 4-12 alert_notification PDU 64. Table 4-13 generic_nack PDU 65. Table 4-14 submit_sm PDU 68. Table 4-15 submit_sm_resp PDU 68. Table 4-16 data_sm PDU 70. Table 4-17 data_sm_resp PDU 70. Table 4-18 submit_multi PDU 73. Table 4-19 submit_multi_resp PDU 74. Table 4-20 Message Submission Request TLVs 77. Table 4-21 Message Submision Response TLVs 77. Table 4-22 deliver_sm PDU 87. Table 4-23 deliver_sm_resp PDU 88. Table 4-24 Message Delivery Request TLVs 89. Table 4-25 Message Delivery Response TLVs 90. Table 4-26 broadcast_sm PDU 95. Table 4-27 broadcast_sm_resp PDU 96. Table 4-28 Broadcast Request Optional TLVs 98. Table 4-29 Broadcast Response Optional TLVs 99. Table 4-30 cancel_sm PDU 101. Table 4-31 cancel_sm_resp PDU 102. Table 4-32 query_sm PDU 103. Table 4-33 query_sm_resp PDU 103.

10 Table 4-34 replace_sm PDU 105. Table 4-35 replace_sm_resp PDU 106. Table 4-36 Message Replacement TLVs 106. Table 4-37 query_broadcast_sm PDU 108. Table 4-38 Query Broadcast Optional TLVs 108. Table 4-39 query_broadcast_sm_resp PDU 109. Table 4-40 cancel_broadcast_sm PDU 111. Table 4-41 cancel_broadcast_sm_resp PDU 112. SMPP SMS Forum 8 of 166. SMS FORUM. Table 4-42 TON Values 113. Table 4-43 NPI Values 113. Table 4-44 command_id Values 116. Table 4-45 command_status Values 122. Table 4-46 data_coding Values 123. Table 4-47 dest_flag Values 124. Table 4-48 esm_class Bit Values 125. Table 4-49 interface_version Values 126. Table 4-50 message_state Values 128. Table 4-51 priority_flag Values 129. Table 4-52 registered_delivery Values 130. Table 4-53 replace_if_present Values 131. Table 4-54 Absolute UTC Time Format 132. Table 4-55 Relative Time Format 132. Table 4-56 service_type Values 133. Table 4-57 sm_default_msg_id Values 134. Table 4-58 sm_length Values 134. Table 4-59 TLV Tag Value Ranges 135.


Related search queries