7.5.2 Handling of mobile originating SMS

23.0783GPPCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4Release 17Stage 2TS

7.5.2.1 Handling of mobile originating SMS in the originating MSC or SGSN

The functional behaviour of the originating MSC or SGSN is specified in 3GPP TS 29.002 [34] and 3GPP TS 23.060 [15]. The procedures specific to CAMEL are specified in this subclause:

– Procedure CAMEL_O_SMS_INIT;

– Procedure CAMEL_O_SMS_SUBMITTED;

– Procedure CAMEL_O_SMS_FAILURE.

A CAMEL Service may be invoked for the following Mobile Originated short message types:

– Short Message Submission (TPDU type = SMS-SUBMIT)

– Short Message Command (TPDU type = SMS-COMMAND)

Refer to 3GPP TS 23.040 [14] for a description of the various TPDU types and to 3GPP TS 24.011 [31] for a description of the protocol elements of the Short Message Relay Layer (RPDUs).

7.5.2.1.1 Actions of the MSC or SGSN on receipt of Int_Error

The MSC or SGSN checks the default SMS Handling parameter in MO‑SMS‑CSI.

If the default SMS handling is ‘releaseTransaction’, a A_RP_ERROR is sent to the MS. The MSC or SGSN then releases all resources and the procedure CAMEL_O_SMS_INIT ends.

If the default SMS handling is ‘continueTransaction’, the MSC or SGSN continues processing without CAMEL support.

7.5.2.1.2 Actions of the MSC or SGSN on receipt of Int_Continue_SMS

The MSC or SGSN continues processing with modified SM parameters. The MSC or SGSN shall transparently modify the SMS parameters with the received information. Parameters which are not included in the Int_Continue_SMS signal are unchanged.

7.5.2.1.3 Actions of the MSC or SGSN on receipt of Int_Connect_SMS

The MSC or SGSN continues processing with modified SM parameters. The MSC or SGSN shall transparently modify the SMS parameters with the received information. Barring is checked with the modified parameters. Parameters which are not included in the Int_Connect_SMS signal are unchanged.

7.5.2.1.4 Actions of the MSC or SGSN on receipt of Int_Release_SMS

A_RP_ERROR is sent to the MS and the Short Message is deleted. The SMS cause received in the Int_Release_SMS signal is used. The MSC or SGSN then releases all resources and the procedure CAMEL_O_SMS_INIT ends.

7.5.2.1.5 Allocation of SMS Reference Number

During the CAMEL handling of a Mobile Originated Short Message, the MSC or SGSN shall allocate an SMS Reference Number. This SMS Reference Number shall be placed in the SMS-MO Call Detail Record, together with the MSC Address or SGSN Number. This SMS Reference Number shall also be sent to the gsmSCF in the Initial DP SMS Information Flow, together with the MSC Address or SGSN Number. The combination of SMS Reference Number and MSC Address or SGSN Number forms a globally unique pair. This pair may be used for correlation of CDRs produced in the MSC or SGSN with CDRs produced in the gsmSCF.

An SMS Reference Number shall be generated and placed in the SMS-MO Call Detail Record, for every Short Message, including the case when a Short Message forms part of a set of concatenated Short Messages.

7.5.2.2 Handling of A_MM_Release and A_LLC_Release

If the radio link with the subscriber is lost during the handling of a CAMEL procedure in the MSC or SGSN, then the MSC or SGSN sends signal A_MM_Release_ind or A_LLC_Release_ind to that procedure. This results in the termination of that CAMEL procedure. (Refer to 3GPP TS 29.002 [34] for details.)

7.5.2.3 Handling of time-out from SMSC

If the MSC or SGSN does not receive a confirmation from the SMSC after submission of a Short Message, then the MSC or SGSN calls procedure CAMEL_O_SMS_FAILURE. (Refer to 3GPP TS 29.002 [34] for details.)

Figure 7.5-1: Procedure CAMEL_O_SMS_INIT (sheet 1)

Figure 7.5-2: Procedure CAMEL_O_SMS_INIT (sheet 2)

Figure 7.5-3: Procedure CAMEL_O_SMS_INIT (sheet 3)

Figure 7.6-1: Procedure CAMEL_O_SMS_SUBMITTED (sheet 1)

Figure 7.7-1: Procedure CAMEL_O_SMS_FAILURE (sheet 1)

7.5.2.4 Handling of mobile originating SMS in the VLR

The functional behaviour of the VLR is specified in 3GPP TS 29.002 [34] The handling specific to CAMEL is specified in the following procedure:

– Procedure CAMEL_MO_SMS_VLR.

Figure 7.8-1: Procedure CAMEL_MO_SMS_VLR (sheet 1)