SMS Basic :

• SMS (Short Message Service) is the transmission of short text messages to and from a
mobile phone, or any other device capable of generating the SMS. It is composed of a
maximum of 160 characters, each coded on 7 bits (GSM) or 140 bytes.
• End to end SMS delivery completes in two parts, First SMS submission in SMSC (Short
Message Service Centre) by originating subscriber, second Delivery of SMS to recipient
subscriber. So SMS is a Stored and Forward Service.
• Once a message is sent, it is received by a Short Message Service Centre (SMSC) of the
calling subscriber’s network, which then delivers it to the appropriate destination device.
In the GSM SMS delivery, SMS termination does not require the SMSC of the recipient
subscriber’s Operator. However In CDMA (Code Division Multiple Access) network or
GSM to CDMA SMS transfer, or in case of some services like Push SMS, the recipient
SMSC is also used for terminating the SMS to the recipient. In all these types of SMS
transfer, the air interface-signalling channel is extensively used for terminating the SMS
traffic.
• SMS uses the signaling channel (not dedicated), so it can be sent/received simultaneously
with the voice/data/fax service over a network.

SMS Text Length:

The “short” part refers to the maximum size of the text messages: 160 characters (letters,
numbers or symbols in the Latin alphabet). For other alphabets, such as Chinese, the maximum
SMS size is 70 characters.

Types of SMS :

With the growing convergence Technology of networks and services, SMS can be send from a
mobile phone, fixed phone, or even via the Internet. On the basis of originating and terminating
identities, SMS can be broadly classified into the following 4 categories : P2P, A2P, P2N & I2P.

• P2P (Person to Person) : In Person to Person (P2P) mode, the SMS is between two
individual subscribers. The SMSC or originating operator stores the SMS & sends it to
the recipient, either directly or in case of GSM to CDMA or CDMA to CDMA network,
through the SMSC of the terminating operator.
• A2P (Application/Advertiser to Person) : In Advertiser/Application to Person (A2P)
SMS mode, advertising agencies have a commercial agreement with one or more service
providers. Advertisers provide the messages and mobile numbers to an operator, who
then sends the messages in broadcast mode to the recipients. If the SMS transfer is on-
net, then SMS moves only within the network of one operator and hence there is no issue
of loading resources of other operators, but if the recipient subscriber is attached with
another operator, then the resources of the terminating operator are also used for
delivering of such SMSs. This type of SMS delivery is also termed as Push method.
• P2N (Person to Network) or P2A (Person to Application) : The Person to Network
(P2N) SMSs are usually an on-net service. In this type mode, the content provider usually
has a revenue share agreement with the service provider. The operator gives the content
provider a 4-5 digit short SMS code. The content provider then uses the short codes to
 provide different kinds of services like astrology information, ring tones, picture
downloads, tele-voting, games, etc. Operators charge premium rate for these SMS to the
short codes.
• I2P (Internet to Person) : The Internet to Person (I2P) arrangement allowed by some
operators with the provision of a web interface enables a person to send an SMS from the
Internet to mobile subscribers. They also accept SMS originating from the Internet
messaging web sites.

Basic SMS Network Element :

• SMSC
• HLR
• MSC
• VLR
• BSC
• BTS
• UE (User Equipment : Mobile/Laptop/Fixed Phone)

SMS is carried on a signaling channel of air interface from mobile handsets to the Base
Transceiver Station (BTS), and thereafter it is carried on the Signaling System 7 (SS7) signalling
channel throughout BSC, MSC/VLR, SMSC.

Basic SMS Call Flow :

End to end SMS transaction completes in 2 parts :

• Message submission by originating subscriber to its SMSC (Mobile Originating Part)

• Message delivery by SMSC to recipient Subscriber (Mobile terminating Part)

Basic end to end SMS call flow shown in following diagram :

SMS Originating Part – MO SM Submit :

• The SM is sent from the originating Mobile Station (MS) to the serving Mobile
Switching Center (MSC). The address of the SMSC where the SM should be submitted to
is stored on the SIM card of the subscriber and forwarded to the MSC with the message.
• The MSC forwards the SM to the SMSC. The SMSC returns a positive (ACK) or
negative (NACK) response indicating whether the message was successfully stored of
not.

SMS Terminating Part – MT SM Deliver :

• To delivers a SM SMSC has to find out the location (serving MSC) and the International
Mobile Subscriber Identity (IMSI) of the recipient subscriber first. This information
(routing information) is retrieved from the Home Location Register (HLR) of the
recipient subscriber based on the recipient number (MSISDN).
• HLR Provides routing Information to SMSC, which includes IMSI and serving MSC of
recipient number.
• Based on routing information SMSC delivers SM to the serving MSC and MSC forwards
it to the recipient Mobile Station.

SMS Delivery Report :

Successful Delivery – On successful delivery SMSC sends delivery report to the originator if
requested.
Failed Delivery – If SMS is not delivered to the recipient number SMSC send failure reason to
the originator.

• Permanent Error : For example – Unknown Subscriber

• Temporary Error : For example – Absent Subscriber

SMSC Retry : In case of temporary errors the SMSC schedules a next delivery attempt, called
SMSC retry.

Network Trigger : If the subscriber is not reachable (absent) the SMSC notifies the HLR that
there is a message waiting for the recipient number. When the HLR detects the presence of the
subscriber, it alerts the SMSC and SMSC forwards SM to the serving MSC.

Regular SMS Messages :

Send Routing Information for Short Message (SRI-SM):

Between Origin SMSC and Destination HLR, to retrieve the routing information needed for
routing the short message to the servicing MSC.

Mobile Originating Forward Short Message (MO Forward SM):

Between Origin MSC and Origin SMSC, to forward mobile originated short messages.

Mobile Terminating Forward Short Message (MT Forward SM):

Between Origin SMSC and Destination MSC, to forward mobile terminated short messages.

Send-Info-For-MO-SMS:

Between the Origin MSC and VLR, to request subscriber related information from the VLR.

Send-Info-For-MT-SMS:

Between the Destination MSC and VLR, to request subscriber related information from the
VLR.

Report Short Message Delivery Status:

Between Origin SMSC and Destination HLR, to set the Message Waiting Data into the HLR or
to inform the HLR of successful SM transfer after polling.

Alert Service Centre:

Between Destination HLR and Origin SMSC, to inform SMSC that a subscriber, whose
MSISDN is in the Message Waiting Data file, is active or the MS has memory available.
Inform Service Centre:

Between Destination HLR and Origin SMSC, to inform the SMSC which MSISDN number is
stored in the Message Waiting Data file, or to provide status on different messaging flags.

Ready For Short Message:

Between the Destination MSC and Destination VLR as well as between the Destination VLR
and the Destination HLR. The MSC initiates this service if a subscriber indicates memory
available situation. The VLR uses the service to indicate this to the HLR.

SMS Applications :

• Text message exchange between Mobile subscriber.

• Ring Tone
• Logo
• Stock Information
• Tele-Voting (TV Show)
• Vending machine Remote Management

1. Tiger

September 26, 2010 at 5:29 am

What is the difference between MAP opcode 44 (mt-forwardSM) and MAP opcode 46
(commonly called mo-forwardSM) which is capable of both MO (subscriber to SMSC)
and MT (SMSC to serving MSC)?

Why would one use opcode 44 when the same thing can be accomplished with opcode
46?

Thanks in advance.

2. Shri

October 6, 2010 at 5:38 pm

MT-Forward SM (opcode – 44) is used between the gateway MSC and the servicing
MSC or the SGSN to forward mobile terminated short message. MO-Forward SM
(opcode – 46) is used between the serving MSC or the SGSN and the SMS Interworking
MSC to forward mobile originated short messages.
The Mandatory MAP Parameters (Invoke ID, SM RP DA, SM RP OA, SM RP UI) in
 both messages are same that’s why in some cases (very rare) MO-Forward SM used in
place of MT-Forward SM. But conditional MAP Parameters are different in both
messages. “More Message to send” is available in MT_FSM as conditional parameter
and used to indicate whether or not the service centre has more short messages to send.
The information from the MMS indication received from the Service Centre is inserted in
this parameter. Similarly “IMSI” is available in MO_FSM as conditional parameter and
shall be included if the sending entity, whether MSC or SGSN, supports mobile number
portability. It means apart from SMS if other services (MMS/MNP) are involved these
messages (MO_FSM/MT_FSM) have different significance.

I hope it clarifies your query.

Thanks
Shri

3. kishsreeram

November 16, 2010 at 7:46 pm

Thank you

Appreciated:)

4. moein

November 27, 2010 at 9:36 am

What are the messages who have the application context=20 and are there any cases
where the SRT-for-SM issued without indicating the Op Code

5. cesar

December 3, 2010 at 5:58 am

why in the first SMS the SMSC send to HLR SRI but the next SMS doesnt ask to HLR
and the SMS send to directy to MSC/VLR.?

6. Shri

December 8, 2010 at 10:21 am

 @moein
Hi Moein,

Send Routing Info For SM (Invoke) message has the application context = 20
(dialoguePDU: ShortMsgGateway) . In standard SRI for SM, there is always MAP
Opcode = 45.

Thanks
Shri

7. Shri

December 8, 2010 at 10:23 am

@Cesar
Hi Cesar,

In first SMS, to get the MSC GT (where B number is roaming) and IMSI of B number,
SMSC sends SRI_SM to HLR. In case of SMS is not delivered in first attempt due to
absent subscriber, switched off or memory full, either SMSC will do retry to deliver SMS
or on the basis of Alert_Service_Centre message received from HLR, SMSC reinitiate
MT_FSM message, in both cases SMSC already have the serving MSC GT (where B
number is roaming), so it does not send SRI_SM to HLR but directly sends MT_FSM to
MSC/VLR.

Thanks
Shri

8. Tariq

December 14, 2010 at 2:38 am

i have a question , if HLR does not have the last VLR location of the mobile and then
someone send SMS to subscriber . if the VLR he is in send SM_Ready and message
delivered will HLR register this VLR address based on the SM_Ready message ?

9. Badr

December 24, 2010 at 8:11 am

Great article!
Thanks for sharing knowledg
10. Shri

December 27, 2010 at 3:03 pm

@ Tarik,
Hi Tarik,
If HLR does not have the last VLR location, it means subscriber is not updated or not
registered in HLR. In that case subscriber is not able to receive SMS as well as Voice
call. When HLR receives SRI_SM from SMSC (gateway MSC) for the subscriber whose
location is not updated in HLR, HLR simply responds to SMSC (SRI_SM_Resp) with
subscriber not reachable status. After receiving, subscriber not reachable status from
HLR, SMSC (gateway MSC) sends Report_SM_Delivery_Status to set the Message
waiting Data into the HLR. Once subscriber get network coverage, LU process will take
place and subscriber will updated into the HLR with current VLR. Now HLR sends
Alert_SC message (Subscriber available) to SMSC (gateway MSC) as MSISDN is stored
in Message waiting Data of HLR. After receiving Alert_SC message SMSC (gateway
MSC) again initiate SRI_SM to deliver SMS to subscriber.

Ready_SM (Ready for SM) message used between MSC to VLR and VLR to HLR or
SGSN to HLR. MSC (VLR) sends this message to HLR if a subscriber indicates memory
available situation, whose message waiting flag is active in the VLR, has radio contact in
the MSC.

So, in summary we can say a subscriber can not receive either SMS or Voice call if it is
not updated into the HLR. In that case first Location update will take place before any
other MAP message communication.

Hope, this clarifies your query.

Thanks
Shri

11. kvoulgar

January 31, 2011 at 8:15 pm

Great article!

I have a few questions with regards to the implementation and routing of SMSs.

Let’s assume that an SMS is sent from subscriber A (who is in network NW-A) to
subscriber B (in network NW-B).

1. How can NW-A identify which network to forward the SMS to?
 2. Am I correct to say that there are two ways of delivering the SMS, one where the
SMSC/IWG of NW-A routes the call directly to the serving MSC of subscriber B and one
where the NW-A SMSC forwards the SMS to the SMSC of NW-B, which subsequently
delivers the SMS to its subscriber? What does the choice between the two methods
depend on?

3. Is there any reason why NW-A needs to identify or know the MNC of NW-B?

Thanks a lot in advance for enlightening my ignorance

12. Shri

February 6, 2011 at 8:26 pm

@kvoulgar
Hi Kvoulgar,
Thanks for your comment and questions. Pls find the answers of your questions below:

1. How can NW-A identify which network to forward the SMS to?
Ans : At NW-A, MSISDN ranges (GT Levels) of NW-B (where SMS to be forwarded) is
already defined under AA19 agreement between both networks. When SMSC of NW-A
receives MO_FSM for the subscriber of NW-B, SMSC-A analyze B-MSISDN and
forwards SMS (SRI_SM and subsequently MT_FSM) to NW-B on the basis of routing
table configured at NW-A for B-MSISDN.
2. Am I correct to say that there are two ways of delivering the SMS, one where the
SMSC/IWG of NW-A routes the call directly to the serving MSC of subscriber B and one
where the NW-A SMSC forwards the SMS to the SMSC of NW-B, which subsequently
delivers the SMS to its subscriber? What does the choice between the two methods
depend on?
Ans : Yes you are right, it depends upon the implementation logic and methodology
adopted by the network for terminating SMS. Normally GSM to GSM having bilateral
agreement for SMS between two MNOs, SMSC/IWG of NW-A routes the SMS directly
to the serving MSC of subscriber B. whereas for SMS terminating from GSM network to
CDMA network, SMSC/IWG of NW-A forwards the SMS to the SMSC of NW-B. Apart
from these two scenarios, SMS-Hub scenario also is in practice where SMS Hub delivers
SMS from one network to another for those MNOs who don’t have bilateral agreement
for SMS.

3. Is there any reason why NW-A needs to identify or know the MNC of NW-B?
Ans : To identify the network to which subscriber B belongs, NW-A must know the
MNC of NW-B. MNC is required for billing settlement and reporting purpose.

Thanks
Shri
13. chapi

February 6, 2011 at 9:07 pm

Can you help me how to send SMS from a county no MNP to a county having MNP.
For instance operator A has direct relation with operator B in county having MNP , when
operator A request SRI_SM to operator B unfortunately the subscriber has changed to
another operator C which is county A has not direct relation with but through third party .
My question is how operator A receives return result for SRI_SM?
Operator A has to invoke SRI_SM second times through third party(Hub)or operator B
will forward the message (SRI_SM) to operator C then through Hub,
Thanks in advance.

14. Shri

February 19, 2011 at 5:48 pm

@Chapi
Hi Chapi
As Operator “A” has only bilateral relationship with Operator “B”, for all MSISDN series
of Operator “B”, operator “A” directly sends the SRI_SM request to Operator “B”. Since
Subscriber is ported into another Operator “C” and there is no bilateral relationship
between A and C, if B routes SRI_SM to C with CGPA of A at SCCP layer, C can not
able to response SRI_SM request as C can not recognize the calling party Address, so
either it will kill the message or returns UDTS to B, so SMS delivery is not possible.
Again, A can not invoke SRI_SM through SMS Hub as Subscriber number range belongs
to B and for B, A is not using SMS Hub and there is no mechanism in place by which A
get the idea about portability of subscriber in a country where A and B are providing
service.
To ensure successful SMS delivery in such type of situation, there should be some
arrangement in MNP implemented country. One of the most popular arrangements is to
receive international SMS only through SMS hubs having relationship with all the
operators of MNP implemented country. It is not necessary SMS hub is single there
might be more than one SMS hub but all the SMS hub must have relationship with all the
operators of MNP implemented country, so that GTs of SMS hub allowed to all the
operators and they can response SRI_SM request coming through these SMS hub.
Another mechanism is, all the operators perform sort of aggregation activity for incoming
SRI_SM request. For example, SRI_SM request coming from A to B for a subscriber
ported in to C, B routes SRI_SM request to C with CGPA of its own GT (replacing GT of
A) , so that C can response SRI_SM to B and B again routes SRI_SM_Resp to A with its
own GT ( replacing GT of C). Hope this help you understanding SMS delivery in a MNP
implemented country.
Thanks
Shri