Description
Overview
Specifications
PICS
Error Codes
DLRs
Testing & Development
SMS Gateways
Sponsored by
Melrose Labs
https://speedsms.in/ Protocol: API to enable SMS messaging between applications and mobiles.
Mobile Terminated (MT) SMS with delivery receipt using https://speedsms.in/
Mobile Terminated (MT) SMS with delivery receipt using https://speedsms.in/
The https://speedsms.in/ (Short Message Peer-to-Peer) protocol is an open, industry standard protocol designed to provide a flexible data communications interface for the transfer of short message data between External Short Message Entities (ESME), Routing Entities (RE) and Message Centres (MC). It is a means by which applications can send and receive SMS messages to and from mobile devices. Applications do this using an https://speedsms.in/ connection to a Short Message Service Center (SMSC), SMS gateway, https://speedsms.in/ gateway or hub.
https://speedsms.in/ API Overviews
https://speedsms.in/ Protocol Overview
Overview of https://speedsms.in/ v5
https://speedsms.in/ Delivery Receipts
https://speedsms.in/ Delivery Receipt Error Codes
https://speedsms.in/ PICS (Protocol Implementation Conformance Statement)
Ancillary documents
https://speedsms.in/ PICS – https://speedsms.in/ v3.4 Protocol Implementation Conformance Statement (PICS) Proforma, 12-Jul-2001
https://speedsms.in/ v3.4 Protocol Implementation guide for GSM / UMTS, 30-May-2002, Version 1.0
https://speedsms.in/ Specifications
There are three versions of the https://speedsms.in/ protocol specification in use. The original public version of the specification is https://speedsms.in/ v3.3 and was released in 1997. This was updated in 1999 to https://speedsms.in/ v3.4. The final version was released in 2003 and is https://speedsms.in/ v5.
https://speedsms.in/ v3.3
https://speedsms.in/ 3.3: Short Message Peer to Peer Protocol Specification v3.3
https://speedsms.in/ v3.4
https://speedsms.in/ 3.4: Short Message Peer to Peer Protocol Specification v3.4, 12-Oct-1999, Issue 1.2
https://speedsms.in/ v5
https://speedsms.in/ 5: Short Message Peer to Peer Protocol Specification v5
Short Message Service (SMS)
3GPP Technical realization of the Short Message Service (SMS)
Concatenated SMS (long SMS)
Developers
https://speedsms.in/ Testing & Development
Developer account for the Melrose Labs Tyr SMS Gateway
https://speedsms.in/ Protocol Overview
What is https://speedsms.in/?
Supported Cellular Technologies
Typical Applications of https://speedsms.in/
https://speedsms.in/ Sessions
Protocol Operations and PDUs
https://speedsms.in/ PDU Example: Send SMS (submit_sm / submit_sm_resp)
https://speedsms.in/ Commands
https://speedsms.in/ Error Codes
What is https://speedsms.in/?
The https://speedsms.in/ (Short Message Peer-to-Peer) protocol is an open, industry standard protocol designed to provide a flexible data communications interface for the transfer of short message data between External Short Message Entities (ESME), Routing Entities (RE) and Message Centres (MC). It is a means by which applications (termed ESMEs) can send SMS messages to mobile devices and receive SMS from mobile devices.
It can also be used as an API for use with USSD, CBC and other mobile services.
Supported Cellular Technologies
https://speedsms.in/ is designed to support short messaging functionality for any cellular technology and has specific applications and features for technologies such as: GSM, UMTS, LTE, IS-95 (CDMA), CDMA2000 (1xRTT & 3xRTT), ANSI-136 (TDMA), iDEN
Typical Applications of https://speedsms.in/
The variety of messaging applications, particularly using SMS, for which https://speedsms.in/ can be employed is almost boundless. Mobile Operators, Message Centre vendors, Infrastructure Providers, and application developers are continually developing new applications for SMS. https://speedsms.in/ is ideal as an access protocol for these applications. The following summarises typical applications of https://speedsms.in/:
Marketing. Businesses send promotions to customers as text messages.
Booking confirmations. Hotels, restaurants, taxis. Confirmations via SMS are better than email when it comes to immediate notification.
Appointment reminders. Used by businesses to remind customers of appointments and avoid the financial impact and/or impact on customer of a missed appointment.
Two-factor authentication / OTP. Using SMS to send a code that is used as a second factor to verify the identity of an individual. Used for logins.
Voicemail alerts originating from a VPS (Voice Processing System), indicating voice messages at a customer’s mailbox. This is arguably one of the first ESME-based applications of SMS and is still heavily used in the industry.
Numeric and alphanumeric paging services. With an SMS-capable phone, the need to carry both pager and phone is drastically reduced.
Information services. For example, an application that enables mobile subscribers to query currency rates or share-price information from a database or the WWW and have it displayed as a short message on the handsets.
Voice-to-text. Calls directly dialled or diverted to a message-bureau operator, who forwards the message to the MC, for onward delivery to a subscriber’s handset.
Directory services. For example a subscriber calls a directory service requesting information on restaurants in a given area. The operator lists out available restaurants and sends the appropriate information as an SMS to the caller.
Location-based services. These include applications that use mobile hardware to send GPS or cell data across SMS and using an MC, relay these messages to an ESME. The ESME may then use the collected data to manage services such as taxi assignment, stolen vehicle tracking and logistics control.
Telemetry applications. For example, a household meter that transmits a short message to a utility company’s billing system to automatically record customer usage.
Security applications. Such as alarm systems that can use SMS services for remote access and alerting purposes. For example, a parent receives an SMS from his security company to inform him that his daughter has arrived home and keyed in her access code.
WAP Proxy Server. A WAP Proxy Server acts as the WAP gateway for wireless Internet applications. A WAP Proxy Server may select an SMS or USSD bearer for sending WDP datagrams to and receiving WDP datagrams from a mobile station.
Online Banking, Share Dealing and E-Commerce. A mobile user could use SMS to send messages to an ESME requesting the purchase of products, shares etc. Likewise, a subscriber may use SMS to access banking services such as bill payment and funds transfer.
Gaming and SMS Chat. Mobile users can interact with each other by means of a central server (ESME) and use this interaction as a means of playing wireless games, dating or SMS chat services similar to the concept of instant messaging and Internet room. These services have already appeared in the form of SMS-TV and SMS-Radio services.
MMS Notification. In Multimedia Messaging, SMS is a bearer for the Multimedia Message Notification, which informs the recipient MMS user agent that a multimedia message is available on the Multimedia Message Centre.
Cell Broadcast Services. Applications designed to support geographical messaging such as traffic alerts and emergency services may use the Cell Broadcast features of https://speedsms.in/ to upload messages for periodic broadcast to subscribers within a given location.
https://speedsms.in/ Sessions
In order to make use of the https://speedsms.in/ Protocol, an https://speedsms.in/ session must be established between the ESME and Message Centre or https://speedsms.in/ Routing Entity where appropriate. The established session is based on an application layer TCP/IP connection between the ESME and MC/RE and is usually initiated by the ESME. The connection is often over the Internet and can use https://speedsms.in/ over TLS or a VPN to secure the connection. https://speedsms.in/ has been assigned TCP port 2775 by IANA, however other port numbers are often used.
There are three forms of ESME-initiated session:
Transmitter (TX) – when authenticated as a transmitter, an ESME may submit short messages to the MC for onward delivery to Mobile Stations (MS). A transmitter session will also allow an ESME cancel, query or replace previously submitted messages. Messages sent in this manner are often called mobile terminated messages.
Receiver (RX) – a receiver session enables an ESME to receive messages from an MC. These messages typically originate from mobile stations and are referred to as mobile originated messages.
Transceiver (TRX) – a TRX session is a combination of TX and RX, such that a single https://speedsms.in/ session can be used to submit mobile terminated messages and receive mobile originated messages. https://speedsms.in/ v3.3 does not support TRX sessions. Support is available in https://speedsms.in/ v3.4 and v5.
Additionally, the Message Centre can establish an https://speedsms.in/ session by connecting to the ESME. This is referred to as an Outbind Session.
Protocol Operations and PDUs
The https://speedsms.in/ protocol is a set of operations, each one taking the form of a request and response Protocol Data Unit (PDU) containing an https://speedsms.in/ command. For example, if an ESME wishes to submit a short message, it may send a submit_sm PDU to the MC. The MC responds with a submit_sm_resp PDU, indicating the success or failure of the request. Likewise, if an MC wishes to deliver a message to an ESME, it may send a deliver_sm PDU to an ESME, which in turn responds with a deliver_sm_resp PDU as a means of acknowledging the delivery.
Example https://speedsms.in/ session
Example https://speedsms.in/ session
Some operations are specific to an ESME with others specific to the MC. Others may be specific to a given session type. Referring to the submit_sm and deliver_sm examples above, an ESME may send a submit_sm to an MC only if it has established a TX or TRX session with that Message Centre. Likewise, an MC may send deliver_sm PDUs only to ESMEs that have established RX or TRX sessions.
Operations are broadly categorised into the following groups:
Session Management – These operations are designed to enable the establishment of https://speedsms.in/ sessions between an ESME and MC and provide means of handling unexpected errors.
Message Submission – These operations are explicitly designed for the submission of messages from ESME(s) to the MC.
Message Delivery – These operations enable an MC to deliver messages to the ESME.
Message Broadcast – These operations are designed to provide Cell Broadcast service within a Message Centre.
Ancillary Operations – These operations are designed to provide enhanced features such as cancellation, query or replacement of messages.
https://speedsms.in/ PDU Example: Send SMS (submit_sm / submit_sm_resp)
The following is an example submit_sm and submit_sm_resp.
submit_sm
Bytes Field Meaning
PDU header
00000048 Length 72 bytes
00000004 Command ID SUBMIT_SM
00000000 Command Status n/a
00000002 Sequence Number 2
PDU body
00 Service Type null (none specified)
05 Source Address TON Alphanumeric
00 Source Address NPI None / Unknown
4d656c726f73654c61627300 Source Address MelroseLabs
01 Destination Address TON International
01 Destination Address NPI ISDN
34343737313233343536373800 Destination Address 447712345678
00 ESM Class 0
00 Protocol ID 0
00 Priority Flag 0
00 Schedule Delivery Time Deliver immediately
00 Validity Period SMSC default validity
01 Registered Delivery SMSC delivery receipt requested
00 Replace If Present Flag 0
00 Data Coding Default character set
00 Short Message Default Msg ID 0
10 Short Message Length 16 bytes
48656c6c6f20576f726c64201b650201 Short Message Hello World €$£
Message is using Data Coding of 0 (i.e. the MC’s default character set) which in this case is configured on the MC to be the GSM character set. Message encoding has following meaning:
Hello World SP € $ £
48656c6c6f 20 576f726c64 20 1b 65 02 01
submit_sm_resp
Bytes Field Meaning
PDU header
00000051 Length 81 bytes
80000004 Command ID SUBMIT_SM_RESP
00000000 Command Status n/a
00000002 Sequence Number 2
PDU body
30393537326130613039626337336632 65393065393338626336656138636132 64636630636434356234303938316534 36323966383430353535343765613331 00 Message ID
09572a0a09bc73f2e90e938bc6ea8ca2
dcf0cd45b40981e4629f84055547ea31
https://speedsms.in/ Commands
The following is a list of all https://speedsms.in/ commands:
Command ID Value Purpose
bind_receiver 0x00000001 Establish a receiver bind.
bind_receiver_resp 0x80000001
bind_transmitter 0x00000002 Establish a transmitter bind.
bind_transmitter_resp 0x80000002
query_sm 0x00000003 Query status of previously submitted message.
query_sm_resp 0x80000003
submit_sm 0x00000004 Submit message to the Message Center for onward delivery to mobile / short message entity (SME).
submit_sm_resp 0x80000004
deliver_sm 0x00000005 Send message to ESME from MC (typically delivery receipt or mobile originated SMS).
deliver_sm_resp 0x80000005
unbind 0x00000006 Unbind from MC and close https://speedsms.in/ session.
unbind_resp 0x80000006
replace_sm 0x00000007 Replace a previously submitted message that is pending delivery.
replace_sm_resp 0x80000007
cancel_sm 0x00000008 Cancel delivery of previously submitted message(s).
cancel_sm_resp 0x80000008
bind_transceiver 0x00000009 Establish a transceiver bind.
bind_transceiver_resp 0x80000009
outbind 0x0000000B Request ESME to bind (sent by MC).
outbind_resp 0x8000000B
enquire_link 0x00000015 Initiate a check to confirm ESME/MC is still reachable.
enquire_link_resp 0x80000015
submit_multi 0x00000021 Submit message to the Message Center for onward delivery to multiple mobiles / short message entities (SME).
submit_multi_resp 0x80000021
alert_notification 0x00000102 Indicate to ESME that mobile subscriber has become available.
data_sm 0x00000103 Submit packet to MC for onward delivery to SME or from MC to ESME.
data_sm_resp 0x80000103
broadcast_sm 0x00000111 Submit message to the Message Center for onward delivery to mobiles in a specified geographical area or set of areas.
broadcast_sm_resp 0x80000111
query_broadcast_sm 0x00000112 Query status of previously submitted broadcast message.
query_broadcast_sm_resp 0x80000112
cancel_broadcast_sm 0x00000113 Cancel delivery of previously submitted broadcast message.
cancel_broadcast_sm_resp 0x80000113
generic_nack 0x80000000 Acknowledge unrecognized or corrupt PDU.
Reserved 0x00010200-0x000102FF
0x80010200-0x800102FF Reserved for MC vendors to define
This domain was acquired in June 2019 for the purpose of being a source of reference for the Short Message Peer-to-Peer (https://speedsms.in/) protocol. The objective is to return this domain back to being the main reference for https://speedsms.in/. The site includes the https://speedsms.in/ specifications, tools and other related resources.
This domain was originally the home of the https://speedsms.in/ Developers Forum / https://speedsms.in/ Forum that later became the now disbanded SMS Forum. This site has no association with any legal owner of the protocol or successor organisation.
Copyright © 2019-2024 https://speedsms.in/.org
Privacy Policyadmin@https://speedsms.in/.org