23.2 The mobile originated short message transfer procedure
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
The mobile originated short message service procedure is used to forward a short message from a mobile subscriber to a Service Centre. The message flow for the mobile originated short message service procedure is shown in figure 23.2/1.
1) Short Message (3GPP TS 24.011 [37]).
2) MAP_SEND_INFO_FOR_MO_SMS (*).
3) MAP_SEND_INFO_FOR_MO_SMS_ACK (*).
4) TCAP BEGIN (**)
4a) TCAP CONTINUE (**)
4b) MAP_MO_FORWARD_SHORT_MESSAGE.
5) Short message (3GPP TS 23.040).
6) Short message Acknowledgement (3GPP TS 23.040).
7) MAP_MO_FORWARD_SHORT_MESSAGE_ACK.
8) Short Message Acknowledgement (3GPP TS 24.011 [37]).
(*) Messages 2) and 3) are not used by the SGSN.
(**) If
a)
the capacity of a message signal unit in the lower layers of the protocol is enough to carry the content of the MAP_OPEN request and the content of the MAP_MO_FORWARD_SHORT_MESSAGE request in a single TC message
and
b) the Interworking MSC operator and the serving node (MSC or SGSN) operator agreed not to use the TCAP handshake countermeasure against SMS fraud for messages exchanged between their networks (see 3GPP TS 33.204 [34a])
then
the TCAP handshake may be omitted.
Figure 23.2/1: Mobile originated short message transfer
In addition the following MAP services are used:
MAP_PROCESS_ACCESS_REQUEST (see clause 8.3); (*)
MAP_AUTHENTICATE (see clause 8.5); (*)
MAP_SET_CIPHERING_MODE (see clause 8.6); (*)
MAP_PROVIDE_IMSI (see clause 8.9); (*)
MAP_CHECK_IMEI (see clause 8.7);
MAP_FORWARD_NEW_TMSI (see clause 8.9); (*)
MAP_TRACE_SUBSCRIBER_ACTIVITY (see clause 9.1); (*)
MAP_READY_FOR_SM (see clause 12.4).
(*) These services are not used by the SGSN.