Mobile Communication

SMSC Access protocols

Mobile Communication SMSC Access protocols

SMAP:

Access protocols initially developed to allow interactions between SMSCs and external SMEs are binary protocols.

An external SME may communicate directly with a SMSC via SMAP protocol <only if the SME has native support for SMAP>

Alternatively, a SMS gateway can fit between the external SME and the SMSC, <this allows an easier path>

Mobile Communication SMSC Access protocols

SMAP: <short message application protocol>

SMAP is an application protocol independent from underlying transport protocols. However HTTP presents its self as a suitable candidate for transporting SMAP operation requests and results <formatted in XML>.

There are four Operational modes available with SMAP:

• Immediate Mode

• Client Session Mode

• Peer-to-peer Mode

• Batch Code

Mobile Communication SMSC Access protocols

SMAP: <short message application protocol>

Client Session Mode:

In this mode the external SME first establishes a session with the gateway prior to requesting operations to be processed by the SMSC. The gateway may also establish such session for message delivery to an external SME

Mobile Communication SMSC Access protocols

SMAP: <short message application protocol>

Immediate Mode:

In this mode the External SME does NOT maintain a session with the gateway. Each operation contains the application context. This mode is used for message submissions only.

Mobile Communication SMSC Access protocols

SMAP: <short message application protocol>

Peer to Peer session mode:

In this mode it allows a bi-directional session to be established between the external SME and the SMSC.

Message submissions and deliveries can be performed over a single bi-directional session.

Mobile Communication SMSC Access protocols

SMAP: <short message application protocol>

Batch Mode:

In this mode, the gateway receives a set of SMAP operations to be processed, from external SME.

The gateway processes each operation in turn and builds a set of results. The set of results is also provided in a batch to the external SME. The batch mode is usually used when an interactive session is not required or would be unsuitable due to timeout issues.

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

“SMPP is a asynchronous protocol, therefore external SMEs do not wait for results of previously submitted instructions”

In order to interact with an SMSC via the SMPP protocol, an external SME first establishes a session. The transport of operations requests over this session is usually performed over TCP/IP or X.25 connections.

For a TCP/IP application, port 2775 is used for SMPP

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

Operations over SMPP can be have four groups:

• Session management

• message Submission

• Message Delivery

• Ancillary operations

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

Session management

These operations enable the establishment of SMPP sessions between external SME and the SMSC, In this category, operations also provide a means of handling unexpected errors.

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

Message Submission

These operations allow external SMEs to submit messages to the SMSC

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

Message delivery

These operations enable the SMSC to deliver messages to external SME’s

Mobile Communication SMSC Access protocols

SMPP: <Short Message Peer to Peer>

Ancillary operations

These operations provide a set of features, example Cancellation, query or replacement