1.SMS Interworking in Traditional Network 1.1.mobile Originated - SMS
1.SMS Interworking in Traditional Network 1.1.mobile Originated - SMS
1.SMS Interworking in Traditional Network 1.1.mobile Originated - SMS
Submit-SM –The short message is submitted from the SME to the SMSC server.
sendRoutingInfo-ForSM – After completing the internal processing ,the SMSC
interrogates the HLR and receives the routing in formations for the mobile subscriber. This
local operation code is used by the SMSGateway-MSC during the MT-SMS procedure
(mobileterminating SMS) in order to deliver a short message to the MSC as to which area
the subscriber roams. This request for routing information from the SMS Gateway MSC
contains the MSISDN of the subscriber, while the result contains the ISDN number
(routing address) of the destination MSC. This address is used by the SCCP to forward the
short message in a forwardSM message.
ForwardSM – The SMSC after accruing routing informations forwards the SMS to the
MSC where the subscriber roams. The MO-SMS procedure (mobile originating SMS) as
well as the MT-SMS procedure (mobile terminating SMS) is used in both cases to carry a
short message between the MSC where the subscriber roams and the MSC, which has a
connection to the SMS Service Center (= SMS Interworking MSC).
MSC transfer the short message to the UE
The MSC Returns to the SMSC the outcome of the message transfer
If requested by the SME, the SMSC returns the status report indicating the delivery of the
message.
IMS Architecture
The Home Subscriber Server (HSS), or User Profile Server Function (UPSF), is a master
user database that supports the IMS network entities that actually handle calls. It contains the
subscription-related information (user profiles), performs authentication and authorization of the
user, and can provide information about the user's physical location. It is similar to the GSM Home
Location Register (HLR) and Authentication Centre (AUC).An SLF (Subscriber Location
Function) is needed to map user addresses when multiple HSSs are used. Both the HSS and the
SLF communicate through the Diameter protocol.
Several roles of Session Initiation Protocol (SIP) servers or proxies, collectively called Call
Session Control Function (CSCF), are used to process SIP signaling packets in the IMS.
Proxy-CSCF (P-CSCF)
It’s a SIP proxy that is the first point of contact for the IMS terminal. It can be
located either in the visited network (in full IMS networks) or in the home network (when the
visited network isn't IMS compliant yet). Some networks may use a Session Border Controller for
this function. The terminal discovers its P-CSCF with either DHCP, or it is assigned in the PDP
Context (in General Packet Radio Service (GPRS).
Serving-CSCF (S-CSCF)
It’s the central node of the signaling plane. It is a SIP server, but performs session control
too. It is always located in the home network. It uses Diameter Cx and Dx interfaces to the HSS to
download and upload user profiles — it has no local storage of the user. All necessary information
is loaded from the HSS.
I-CSCF (Interrogating-CSCF)
It’s another SIP function located at the edge of an administrative domain. Its IP address is
published in the Domain Name System (DNS) of the domain (using NAPTR and SRV type of
DNS records), so that remote servers can find it, and use it as a forwarding point (e.g. registering)
for SIP packets to this domain. The I-CSCF queries the HSS using the Diameter Cx interface to
retrieve the user location (Dx interface is used from I-CSCF to SLF to locate the needed HSS
only), and then routes the SIP request to its assigned S-CSCF.
SME
SMSC
C'
GMSC /
CGF/CDF HSS
SMS-IWMSC
E/Gd
Rf Sh Cx
OCS IP-SM-GW MAP
Ro
ISC
IMS core
Gm
UE
IP-Short-Message-Gateway (IP-SM-GW)
The IP-SM-GW shall provide the protocol interworking for delivery of the short message
between the IP-based UE and the SMSC. The message is routed to the SMSC for delivery to the
SMS-based user or the message is received from the SMSC of an SMS-based UE for delivery to an
IP-based UE. There are two possibilities for delivery of the SMS message: it can either be carried
encapsulated in an IMS message, or it can be carried as a text body of an IMS Immediate Message.
4. IP-SM-GW
IP address is
preconfigured
6. MAP_SRI_FOR_SM ack
7. MAP_MT_Forward_Short_Message
8. Perform domain
selection. Deliver
SMS in CS; query
HLR
9. MAP_SRI_FOR_SM Request
MAP query from IP-SM-
10. MAP_SRI_FOR_SM Resp GW to HSS to retrieve
MSC/SGSN address
12.
MAP_MT_Forward_Short_Message
15. MAP_MT_Forward_Short_Message_ACK
HSS returns the preconfigured IP-SM-GW address in response to a MAP SRI query from
the SMS-GMSC. The SMS-GMSC forwards the SMS message to the IP-SM-GW, which performs
domain selection.If the selected domain is CS, the performs another MAP SRI query to the HSS in
order to obtain the MSC/SGSN address, and then delivers the SMS in the CS domain.
3. MAP_SRI_FOR_SM Req
4. IP-SM-GW
IP address is
preconfigured
6. MAP_SRI_FOR_SM ack
7. MAP_MT_Forward_Short_Message
8. Perform domain
selection. Deliver
SMS in IMS
9. SIP MESSAGE
10. SIP MESSAGE
HSS returns the preconfigured IP-SM-GW address in response to a MAP SRI query from
the SMS-GMSC. The SMS-GMSC forwards the SMS message to the IP-SM-GW, which performs
domain selection.If the selected domain for SMS delivery is IMS, the IP-SM-GW performs
transport level conversion of SMS message into SIP MESSAGE and delivers the SMS in IMS
domain.