1.

Mobile Originated (MS - SMSC, SM-SUBMIT PDU)

2. MObile Terminated (SMSC - MS, SM-DELIVER PDU)
SMS payload length is 140 bytes => (140 - 8bit, 160 - 7bit, 70 - unicode chars)
SCA - Sevice Center Address
PDU Type - submit/deliver and other parameter indicators, 1 byte and each bit re
presents 1 info.
MR - Message Reference
DA - Destination Address
OA - Originator Address
PID - protocol Identifier indicate SMSC how to process the message (eg. fax)
VP - validity period (this parameter availability is based on PDU Type bit)
UDL - User Data Length.
UD - User Data.
UDHI - User Data Heder inclusion in User data part.
VPF - Validity period format
MMS - more message to send
SRI - status report indication
RP - Reply path
SRR - status report request
RD - Reject duplicates
PDu Type For SM-MO = RP + UDHI + SRR + VPF + 0 + RD + 01 (submit)
PDU Type For SM-MT = RP + UDHI + SRI + 0 + 0 + MMS + 00 (deliver)
SM-MO Service ( SM-Submit PDU)
SCA (1-10 bytes) + PDU Type (1) + MR(1) + DA (2-12) + PID (1) + DCS (1) + VP(0/
1/7) + UDL(1) + UD
SM-MT Service ( SM-Deliver PDU)
SCA (1-10 bytes) + PDU Type (1) + OA (2-12) + PID (1) + DCS (1) + SCTS (7) + UD
L(1) + UD
Specifications :
In early versions of MAPV2 the forward short message procedure is used for both
mobile originated and mobile terminated short messages. The direction of (MO/MT)
is determined by examining the parameter SM-PR-DA which in case of MT SM conta
ins IMSI of the receiver. In later version of MAP2, MO-FWD-SMS and MT-FWD-SMS ar
e handling.
PDUS
User Error - unknown subscriber, absent subscriber, facility not supported, call
barred, Illegal subscriber, Illegal device, SM delivery failure, Subscriber bus
y for MT SMS.
MAP-SEND-ROUTING-INFO-FOR-SM (GSM) / SMSRequest (IS-41) (GMSC -> HLR / IMSCGW > SMSC)
Request - MSISDN, priority, service center address
Response - IMSI, MSC number, LMSI, User Error, Provider Error.
MAP-FORWARD-SHORT-MESSAGE (GSM, <=MAPV2.0) (MSC <-> SMSC)
Request - SM_RP_DA, SM_RP_OA, SM_RP_UI, MMS

Response - User Error, Provider Error

MAP-REPORT-SM-DELIVERY-STATUS (GMSC/SMSC -> HLR)
is used to set the Message Waiting Data in HLR or to inform HLR of succe
ssful SM transfer after polling.
Request - MSISDN, Service Center Address, SMS Delivery outcome.
Response- MSISDNAlert, User Error(- msg waiting list full), Provider Err
or.
MAP-READY-FOR-SM service (MSC -> VLR, VLR -> HLR)
If the mobile were to have been temporarily unreachable earlier and beca
me reachable now,
the VMSC/VLR would have any way sent MAP_READY_FOR_SM to HLR, triggering
the alert procedures.
Request - IMSI, TIMSI, Alert reason
Response - User Error, Provider Error.
MAP-ALERT-SERVICE-CENTRE (HLR ->IMSC)
If HLR detectes that a subscriber whose MSISDN in Msg waiting Data file,
is active or MS has memory available, HLR initiates this msg.
Request - MSISDN, Service Center Address.
Response - User Error, Provider Error.
MAP-INFORM-SERVICE-CENTRE (HLR - GMSC)
is initiated by HLR to GMSC, to inform Service center which MSISDN is st
ored in message waiting data file.
Request, Response - MSISDN-Alert, MWD Status.
MAP-SEND-INFO-FOR-MT-SMS (MSC -> VLR)
Request - SM_RP_DA, MSISDN
Response - User error, Provider error
MAP-SEND-INFO-FOR-MO-SMS (MSC -> VLR)
Request - Service Center Address, MSISDN
Response - User error, Provider error
MAP-MT-FORWARD-SHORT-MESSAGE (SMSC - MSC)
MAP-MO-FORWARD-SHORT-MESSAGE (MSC - SMSC)
MAP-MT-FORWARD-SM-FOR-VGCS

SME protocols to interact with message center are : UCP (universal computer prot
ocol), CIMD (computer interface to msg distribution.), SMPP
CALL FLOWS
==========
1. Both are With in Network.
2. MO subscriber is in roaming
3. MT subscriber is in roaming
4. Both are of different Network
How we will get B Party HLR address.

044 4070 4007