Siemens
Contents
1
2
Generalities
Message Flows
TM3110EU01TM_0002
3
11
Siemens
TM3110EU01TM_0002
Siemens
Generalities
TM3110EU01TM_0002
Siemens
For a GPRS attached MS, it is possible to send and receive short messages via
GPRS radio channels. An MS that is GPRS attached and not IMSI attached transfers
SMs via GPRS channels. MSs that are both GPRS attached and IMSI attached
transfer SMs via GPRS channels or via non-GPRS control channels (if non-GPRS
control channels are used, then paging for MT SMS may run via the SGSN).
Short
An SMS transmission via SGSN (packet switched operation) is normally more radio
efficient than via MSC, i.e. via circuit switched connections. Therefore, the SMS
capability of SGSN is realized to provide the possibility to transfer short messages
between GPRS MS and SMS center via an SGSN.
To support short message transfer across the GSM radio interface the short
message control (SM-C) as well as the short message relay (SM-R) function are
implemented in the SGSN according to GSM standards. The communication and
transport, respectively, of short messages between SM-C and SM-R function that is
based on corresponding peer protocols.
The figure on the right reflects:
l
the SM relay protocol (SM-RP) between SM-R function on the MS and SGSN site.
Related to the SM-C and SM-R functionality the SGSN supplies the relay function
which delivers/receives short message user information elements (transfer protocol
data unit (TPDU)) and handles as well the notification to/from MAP/TCAP. The SMRP and SM-CP are necessary for the transmission of short message TPDUs. The
short message TPDUs will be put into SM-RP messages, which will be transmitted
with SM-CP messages to the peer entity. The LLC entity put the SM-CP messages
into unconfirmed information (UI) frames for the transmission to the peer entity.
TM3110EU01TM_0002
Siemens
SI E
M EN
S
NIXDOR
F
BSS
SMS
SMS
SMS-RP
SMS-RP
SMS-CP
SMS-CP
LLC
LLC
Relay
RLC
RLC
BSSGP
BSSGP
MAC
MAC
Network
Service
Network
Service
GSM RF
Frame
Relay
GSM RF
MS
Um
BSS
MAP
MAP
TCAP
TCAP
SCCP
SCCP
MTP
MTP
Frame
Relay
Gb
SGSN
SMS-SC
Gd
SMS GMSC
/IW-MSC
TM3110EU01TM_0002
Siemens
To meet the capability of SMS service by the SGSN the following interfaces are
introduced:
l
Gd-interface: the interface between SGSN and SMS Gateway MSC (SMSGMSC)/SMS Interworking MSC (SMS-IWMSC) The SMS GMSC/IWMSC supports
the SMS MAP services.
Gr-interface: the interface between SGSN and HLR is extended by a special MAP
service (MAP v3 is needed).
Both interfaces are CCS7 - interfaces, except the interface between SC and SMS
GMSC, which is not defined by the standardization.
TM3110EU01TM_0002
Siemens
HLR
Gr
C
s
Um
Gb
specified
by
operator
Gd
BSS
MS
BSS
SGSN
SMS GMSC
SMS IWMSC
SM SC
TM3110EU01TM_0002
Siemens
With short message service mobile originated, the MS wants to send a short
message (SM), and transfers the SM to the SGSN via RP, CP, and LLC. The SGSN
checks the MS subscription data, and determines that the MS is allowed to originate
a SMS. Now, SGSN forwards the SM to a SMS interworking MSC (SMS IWMSC).
SMS IWMSC passes the SM to the addressed SM-SC. After sending the SM, the SM
SC returns a Delivery Report to the SMS IWMSC indicating successful delivery of the
SM. SMS IWMSC returns a Forward Short Message Result message to the SGSN
indicating successful delivery of the SM. Then, the SGSN returns a Delivery Report
to the MS indicating successful delivery of the SM.
For short message service mobile terminated, the Short Message Service Center
(SM SC) determines, it has to send a SM to a MS. Therefore, the SM SC forwards
the SM to a SMS gateway MSC (SMS GMSC). The SMS GMSC examines the
destination MS address, and sends a Send Routing Info For Short Message to the
relevant HLR. The HLR returns with Send Routing Info For Short Message Result to
the SMS GMSC. The result may contain the MS's current SGSN Number, the MSC
Number, or both. If the result does not contain an SGSN Number (i.e., the HLR
knows that the MS is not reachable via an SGSN), and if the result does contain an
MSC Number, then non-GPRS SMS delivery procedures are followed. If the result
contains an SGSN Number, the SMS transfer proceeds according to the following
events. The SMS-GMSC forwards the SM to the SGSN. The SGSN transfers the SM
to the MS on the RP, CP, LLC layers, as defined in GSM 04.11 and GSM 04.64. After
successful delivery, the SGSN returns a Forward Short Message Result message to
the SMS GMSC indicating successful delivery of the SM. As a result, the SMSGMSC returns a Delivery Report to the SM SC indicating successful delivery of the
SM.
NOTE: SMS delivery via the SGSN is normally more radio resource efficient than
SMS delivery via the MSC/VLR. The preferred delivery path is selected by SMSGMSC operator-specific action.
TM3110EU01TM_0002
Siemens
HLR
Gr
C
s
Msg Transfer
Forward SM
Message Transfer
Um
Gb
specified
by
operator
Gd
BSS
Gr
C
SRI for SM
HLR
s
Forward SM
Message Transfer
Msg Transfer
Um
Gb
specified
by
operator
Gd
BSS
MS
BSS
SGSN
SMS GMSC
SMS IWMSC
SM SC
TM3110EU01TM_0002
Siemens
10
TM3110EU01TM_0002
Siemens
Message Flows
TM3110EU01TM_0002
11
Siemens
The TP-Destination Address indicating the Mobile Station to which the SM is sent.
The RP-Destination Address as the Service Center Address to which the message
is forwarded by the SGSN.
The SGSN sends a CP-Ack back to the MS indicating the successful receipt of the
CP-Data message.
After receiving a SMS-SUBMIT-REPORT from the SC, the SGSN sends this report to
the MS in a RP-Ack within a CP-Data. The SMS-SUBMIT-REPORT may contain the
SM in the TP-User Data.
In case of an error a SMS-SUBMIT REPORT for RP-Error is sent back to the MS in a
RP-Error contained in a CP-Data.
Finally a CP-Ack is sent from MS to SGSN.
NOTE: An active PDP Context is not affected or disturbed in any way by the SMSSubmission.
12
TM3110EU01TM_0002
Siemens
Subscriber attached
MS
SM
SGSN
UI(CP-DATA(RP-DATA(SMS-SUBMIT(TP-USERDATA))))
to SC
UI(CP-ACK)
UI(CP-DATA(RP-ACK(SMS-SUBMIT-REPORT)))
from SC
UI(CP-ACK)
TM3110EU01TM_0002
13
Siemens
14
TM3110EU01TM_0002
Siemens
MS
SMS IWMSC
SGSN
SM
MO_FORWARD_SM
SM SC
SM
SM ACK
MO_FORWARD_SM_ACK
SM ACK
TM3110EU01TM_0002
15
Siemens
The mobile terminated short message transfer procedure is used for forwarding a
short message or several short messages from a Service Center to a mobile
subscriber. The short message handling function of the SMS GMSC will request
routing information when a mobile terminated short message is received from a
Service Center. The GMSC sends the SEND_ROUTING_INFO_FOR_SM request to
the HLR containing the subscriber data of the mobile subscriber. As a result, the HLR
supports the SMS GMSC with the actual SGSN address for the mobile station.
When initiating the dialogue with the SGSN, the SMS Gateway MSC must provide
the IMSI of the subscriber to whom the short message is directed. The IMSI is
included in the MAP message MT_FORWARD_SHORT_MESSAGE. When receiving
the MT_FORWARD_SHORT_MESSAGE from the SMS GMSC, the SGSN requests
its subscriber database to find out where the subscriber have to be paged or if the
subscriber has an active context.
If forwarding of the short message to the MS is initiated, the SGSN awaits the result
before one of the following responses is sent back to the GMSC. This could be either
an acknowledge if the short message has been successfully delivered to the mobile
subscriber or an SM delivery failure error containing a parameter indicating the
error: e.g. there is a MS protocol error or the MS memory capacity is exceeded.
16
TM3110EU01TM_0002
Siemens
MS
SGSN
SMS GMSC
HLR
SM SC
SM
SRI_FOR_SM
SRI_FOR_SM_ACK
MO_FORWARD_SM
PAGE PS
PAGE Resp.
SM
SM ACK
MO_FORWARD_SM_ACK
SM ACK
TM3110EU01TM_0002
17
Siemens
18
TM3110EU01TM_0002
Siemens
Subscriber attached
MS
SM
SGSN
UI(CP-DATA(RP-DATA(SMS-DELIVER(TP-USERDATA))))
from SC
UI(CP-ACK)
UI(CP-DATA(RP-ACK(SMS-DELIVER-REPORT)))
to SC
UI(CP-ACK)
TM3110EU01TM_0002
19
Siemens
20
TM3110EU01TM_0002