10.2 Short message mobile originated

23.0403GPPRelease 17Technical realization of the Short Message Service (SMS)TS

The entities involved in this procedure is depicted in figure 17.

Figure 17: Interfaces involved in the Short message mobile originated procedure

GSM TS 43.002 [5]. X is the interface between an MSC or an SGSN and an SC as defined in clause 5.

Note that since the short message mobile originated procedure covers the functionality required at SM‑RL for transferring TPDUs from SC to MS, the procedure described covers both short message (SMS‑SUBMIT) and command (SMS‑COMMAND) transfer. The term "short message transfer" therefore in this clause, covers both cases.

In figure 18, sequence diagrams for the following basic situations of short message mobile terminated transfer attempt:

‑ Successful short message transfer;

‑ Short message transfer attempt failing due to error at the MSC or SGSN;

‑ Short message transfer attempt failing due to negative outcome of VLR information retrieval;

‑ Short message transfer attempt failing due to error at the SMS‑IWMSC;

‑ Short message transfer attempt failing due to error at the SC;

– Short Message transfer attempt successful due to the existence of an SMS Interworking agreement;

– Short Message transfer attempt failing due to non-existence of an SMS Interworking agreement;

– Short Message transfer attempt failing due to negative outcome of HLR information retrieval.

References to the relevant specifications of the different operations are given in clause 4.

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report

NOTE 1): Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2): This operation is not used by the SGSN.

Figure 18a): Successful short message transfer attempt

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report

NOTE 1): Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

Figure 18b): Short message transfer attempt failing due to error at the MSC or SGSN

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report
	: Unsuccessful operation invocation or message transfer incl. error report (or with missing confirmation)

NOTE 1): Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2): This operation is not used by the SGSN.

Figure 18c): Short message transfer attempt failing due to negative outcome of
VLR information retrieval

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report

NOTE 1): Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2): This operation is not used by the SGSN.

Figure 18d): Short message transfer attempt failing due to error at the SMS‑IWMSC

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report

NOTE 1): Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2): This operation is not used by the SGSN.

Figure 18e): Short message transfer attempt failing due to error at the SC

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report

NOTE 1: Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2: This operation is not used by the SGSN.

NOTE 3: HLR that terminated user belongs to.

After completing operation 2, SMS-IWMSC could check whether SMS interworking agreement exists or not based on IMSI. In this figure 18f case, there is an SMS interworking agreement between operators.

Figure 18f): Short Message transfer Successful due to the existence
of an SMS Interworking agreement

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report

NOTE 1: Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2: This operation is not used by the SGSN.

NOTE 3: HLR that terminated user belongs to.

NOTE 4: The lack of an SMS interworking agreement can not be conveyed in the Failure Report as a specific indication.

After completing operation 2, SMS-IWMSC could check whether SMS interworking agreement exists or not based on IMSI. In this figure18g case, there is no SMS Interworking agreement between operators.

Figure 18g): Short Message transfer attempt failing due to non-existence
of an SMS Interworking agreement

	: Operation invocation or message transfer
	: Successful operation invocation or message transfer including report
	: Error report

NOTE 1: Described in 3GPP TS 24.008 [12] and 3GPP TS 29.002 [15].

NOTE 2: This operation is not used by the SGSN.

NOTE 3: HLR that terminated user belongs to.

NOTE 4: The lack of an SMS interworking agreement can not be conveyed in the Failure Report as a specific indication.

If SMS-IWMSC receives an informSC Message, then this message shall be ignored by the SMS-IWMSC.

Figure 18h: Short Message transfer attempt failing due to negative outcome
of HLR information retrieval

If a failure report is indicated by the HLR after invocation of the "sendRoutingInfoForShortMsg" operation, the SMS‑IWMSC shall return the appropriate error information to the MSC/SGSN with the error cause coded as follows:

Return error from SendRoutingInfoForSM	Error mapping to ForwardShortMessage
system Failure	system Failure
data Missing	system Failure
Unexpected Data Value	system Failure
facility Not supported	SM Delivery Failure cause: invalid SME-address
unknown Subscriber	SM Delivery Failure cause: invalid SME-address
teleservice Not provisioned	SM Delivery Failure cause: invalid SME-address
Call barred	SM Delivery Failure cause: invalid SME-address
Absent Subscriber SM	SM Delivery Failure cause: invalid SME-address

Operation 2: sendRoutingInfoForShortMsg.

The operation is an interrogation of the HLR by the SMS-IWMSC to retrieve information necessary to forward the short message.

The outcome of the operation comprises either success, where the result contains the IMSI for terminated UE, or failure, which may be caused by several reasons.

Operation 7: Message transfer MS ‑> MSC or MS -> SGSN.

The operation is used to transfer a short message from the MS to the MSC or to the SGSN.

Operation 8: sendInfoForMO‑SMS.

The operation provides a means for the MSC to verify from the VLR that the mobile originated short message transfer does not violate supplementary services invoked or restrictions imposed using the network feature Operator Determined Barring.

A successful VLR response carries the MSIsdn of the originating MS being transferred to the SC at SM‑RL.

NOTE: This operation is not used by SGSN.

Operation 9: forwardShortMessage.

The operation provides a means for the MSC or for the SGSN to transfer a short message to the SMS‑IWMSC.

The procedure is required if the serving MSC or SGSN cannot access the SC directly, e.g. because it has no connection to SC (see clause 5).

The procedure works in tandem with the forwarding of the short message from the SMS‑IWMSC to the SC. Thus, the outcome of the operation comprises either success, i.e. that the message has been delivered to the SC; or a failure that may be caused by several reasons, e.g. failure in the transfer MSC ‑‑> SMS‑IWMSC or SGSN ‑‑> SMS‑IWMSC, SC does not comply.

Operation 10: Message transfer SMS‑IWMSC ‑> SC.

The operation is used to transfer a short message from an SMS‑IWMSC to an SC, and consists of:

‑ the transfer of a message containing the TPDU from the SMS‑IWMSC to the SC (see "10a. Message transfer" in figure 18); and

‑ the return of either a "Failure report" (see 10c. in figure 18) or a "Delivery report" (see 10b. in figure 18).

"Failure report" is returned to the MS when the SMS‑IWMSC has received indication from the network or the SC that the procedure was unsuccessful.