An Overview of SMS - Kinkar Choudhury

Slide titleIn CAPITALS

50 pt

Slide subtitle 32 pt

SMS

An Overview of SMS

Slide title 40 pt


Text 24 pt

Bullets level 2-520 pt

© Kinkar Choudhury Ericsson Confidential SMS 2009-08-302

Topic What is SMS ? Call flow of SM?

– MO call flow (Use of SCA)– MT call flow (Use of GT)– The GT of SMSC may be used as SCA but GT and SCA should be different

SM to short code (ESME)– MO Call flow (Use of SMPP)– MT call flow (Use of GT)– An Overview of SMPP– Concept of SMS Gate Way

Prepaid billing– From MSC– From SGSN

Postpaid billing– Using SMSC CDR– Using MSC CDR

How 160 characters are coming in the SM?– 7 bit coding – 8 bit coding

Concept of DCS Concept of PID Difference between Normal SM & Flash Messages What happen if more than 160 characters are sent ? Question & Answer

Slide title 40 pt


Text 24 pt



What is SM?

SM means Short Message It is a popular VAS service in Telecom There are several VAS services based on

SMS

Slide title 40 pt


Text 24 pt



MO SMS Flow

MS VMSC VLR SMS-C

Short Message (RP_data)

MAP Send Info for MO_SMS

MAP Send Info for MO_SMS Ack

MAP MO Forward Short Message (RP_data)

MAP MO Forward Short Message Ack (RP_Ack)

Short Message Acknowledgement (RP_Ack)

(SCA is used to submit SM to SMSC)

Slide title 40 pt


Text 24 pt



MS VMSC VLR SMS-C

MT SMS Flow

HLR

MAP Send Routing Info for SM

MAP Send Routing Info for SM AckMAP MT forwarded short message (RP_data)

MAP Send info for MT SMS

MAP Page

Paging

Page Response

MAP Process Access Request Ack

MAP Send info for MT SMS Ack


Short Message Ack (RP_Ack)

.MAP MT FSM Ack

(Used SMSC GT to response the SRI)

Slide title 40 pt


Text 24 pt



The GT of SMSC may be used as SCA but GT and SCA should be different Suppose Two Circles are served by one SMSC All the Subscriber used SMSC GT as the SCA Gradually Subscriber base increased, and one more

SMSC is needed .

– What will happen then?That’s why for different circle different

SCA is used

Slide title 40 pt


Text 24 pt



MO SMS Flow to Short code

MS VMSC VLR SMS-C








(B-party number is a short code)

ESME

Submit_SM

Submit_SM Ack

Slide title 40 pt


Text 24 pt



MS VMSC VLR SMS-C

MT SMS Flow (Response from Short Code)

HLR

MAP Send Routing Info for SM

MAP Send Routing Info for SM Ack

MAP MT forwarded short message (RP_data)

MAP Send info for MT SMS

MAP Page

Paging

Page Response

MAP Process Access Request Ack

MAP Send info for MT SMS Ack


Short Message Ack (RP_Ack)

MAP MT FSM Ack

ESME

Submit_SM

Submit_SM Ack

Slide title 40 pt


Text 24 pt



Over view of SMPP

Short Message Peer to Peer Protocol 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, such as a Short Message Service Centre (SMSC), GSM Unstructured Supplementary Services Data (USSD) Server or other type of Message Center and a SMS application system, such as a WAP Proxy Server, EMail Gateway or other Messaging Gateway.

Slide title 40 pt


Text 24 pt



SMPP Overview

SMPP supports a full featured set of two-way messaging functions such as:-

Transmit messages from an ESME to single or multiple destinations via the SMSC

An ESME may receive messages via the SMSC from other ESME’s (e.g. mobile stations).

Query the status of a short message stored on the SMSC Cancel or replace a short message stored on the SMSC Send a registered short message (for which a ‘delivery receipt’ will

be returned by the SMSC to the message originator) Schedule the message delivery date and time Select the message mode, i.e. datagram or store and forward Set the delivery priority of the short message Define the data coding type of the short message Set the short message validity period

Slide title 40 pt


Text 24 pt



SMPP Overview (Mode of SMPP)

Slide title 40 pt


Text 24 pt



SMPP Overview

Slide title 40 pt


Text 24 pt



Concept of SMS Gate Way Generally SMSC only support SMPP and CIMD

protocol for talking with ESME But all ESME does not support SMPP protocol Some time there is a limitation of SMPP account in the

SMSC so much more ESME would not be added– Concept of SMS Gw come, which mainly a protocol

converter – SMPP is converted to HTTP– More ESME can be added– The ESME’s which mainly support HTTP can be added.– Some time SMSes can be charged through SMS Gw

Slide title 40 pt


Text 24 pt



Prepaid billing of SMSMS MSC/SSF VLR SCF/CCN







SMSCSDP

IDP

Final Report

Interogation_ackRRBCSM,Continue

Event_report BCSM

Reserved money

Deduct money

Interrogation

Retrive_ack

Release

Slide title 40 pt


Text 24 pt



Prepaid billing of SMSMS SGSN VLR SCF/CCN

Short Message






SMSCSDP

IDP

Final Report

Interogation_ackRRBCSM,Continue

Event_report BCSM

Reserved money

Deduct money

Interrogation

Retrive_ack

Release

Slide title 40 pt


Text 24 pt



Postpaid subscriber billing

MS VMSC VLR SMS-C








SMS-C EMM

CDR of Postpaid subs FTP

CDR of Postpaid subs FTP

Slide title 40 pt


Text 24 pt



How 160 characters are coming in the SM? Total Size of a SMS data field is 140 byte So total bits are 140 * 8 =1120 bits There are two type of coding schema

– 7 bit coding– 8 bit coding

Normal SIM / MS can do only 7 bit coding So total bits after coding is

– 1120/7=160– 1 character is taking 1 bit– So total characters are 160

Slide title 40 pt


Text 24 pt



Concept of DCS The TP-Data-Coding-Scheme field, defined in GSM 03.40, indicates the data

coding scheme of the TP-UD (Transfer Protocol Data Unit) field, and may indicate a message class. The octet is used according to a coding group which is indicated in bits 7..4. The octet is then coded as follows:

Bit 7XX4 00xx : General Data Coding indication 0100 to1011: Reserved coding groups 1100 : Discard Message 1101 : Store Message 1110 : Store Message 1111: Data coding/message class (Specific coding) Bit 3 is reserved, set to 0. Bit 2 Message coding: Bit 0 Default alphabet 1 8-bit data ( 8-bit data indicates that the TP-UD has user-defined coding.) Bit1 Bit 0 Message Class: 0 0 Class 0 0 1 Class 1 default meaning: ME-specific. 1 0 Class 2 SIM-specific message. 1 1 Class 3 default meaning: TE specific (see GSM TS 07.05)

Slide title 40 pt


Text 24 pt



Concept of PID The Protocol-Identifier is the information element by which the SM-TL either refers to the

higher layer protocol being used, or indicates interworking with a certain type of telematicdevice.

The Protocol-Identifier information element makes use of a particular field in the message types SMSSUBMIT, SMS-DELIVER and SMS-COMMAND TP-Protocol-Identifier (TP-PID).

The TP-Protocol-Identifier parameter serves the purposes indicated above. It consists of one octet, and the bits in the octet are used as follows:

• In the case where bit 7 = 0, bit 6 = 1, bits 5 to 0 are used as defined below5xxxx0

000000 Short Message Type 0000001 Replace Short Message Type 1000010 Replace Short Message Type 2000011 Replace Short Message Type 3000100 Replace Short Message Type 4000101 Replace Short Message Type 5000110 Replace Short Message Type 6000111 Replace Short Message Type 7

001000..011110 Reserved011111 Return Call Message100000..111111 Reserved

•The SC (Service Centre) may reject messages with a TP-Protocol-Identifier containing a reserved value or one which is not supported.

Slide title 40 pt


Text 24 pt



Difference between Normal SM & Flash Messages Normal SM is a SM which made for handsets PID value indicate that it should store in the MS/SIM But in the case of Flash Message

– Message to SIM– PID value indicate that it should not store in the MS/SIM– Normally 8 bit coding is done

Slide title 40 pt


Text 24 pt



What happen if more than 160 characters are sent ? If a Command Packet is longer than 140 octets (including the Command Header), it shall be

concatenated according to TS 23.040 [3]. In this case, the entire Command Packet including the Command Header shall be assembled, and then separated into its component concatenated parts. The first Short Message shall contain the concatenation User Data Header and the Command Packet Identifier in the UDH in no particular order. Subsequent Short Messages shall contain only the concatenation User Data Header. The concatenation Header contains a Reference number that will allow the Receiving Entity to link individual Short Messages together to re-assemble the original Command Packet before unpacking the Command Packet.

Slide title 40 pt


Text 24 pt



Question & Answer

Slide title 40 pt


Text 24 pt



An Overview of SMS - Kinkar Choudhury

Technology

sms ackmap mo

mt sms ack short message

mt sms ackshort message

sm ackmap mt

flow of sm

data short message ack

ptslide subtitle

datashort message ack