5.3.2 R_o message flows

32.2743GPPCharging managementRelease 17Short Message Service (SMS) chargingTelecommunication managementTS

5.3.2.1 Simple submission

This clause contains message flows for the different operation models IEC (figure 5.3.2.1.1) and ECUR (figure 5.3.2.1.2).

Figure 5.3.2.1.1: Online charging in simple submission for IEC

1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM.

2) The SMS node triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the origination procedures.

Figure 5.3.2.1.2: Online charging in simple submission for ECUR

1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM.

2) The SMS node triggers a Reserve Units Request [Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the origination procedures.

6) The SM transaction is successfully acknowledged.

7) The SMS node triggers a Reserve Units Request [Terminate] message to the OCS reporting the successful event transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Reserve Units Response message to the SMS node.

5.3.2.2 Enhanced submission

The enhanced submission procedures are similar to the simple submission procedures using ECUR. However, the trigger for Reserve Units Request (Terminate) may be based on unsuccessful handling, e.g. negative acknowledgement and with or without successful storage of the message for future redelivery attempts. See failure scenarios defined in clause 5.3.2.7.

5.3.2.3 Delivery report

The origination of delivery reports use the same procedures as the simple submission procedures as described within clause 5.3.2.1. The delivery report itself is contained within a new SM.

5.3.2.4 Origination retry

This clause contains message flows for the different operation models IEC (figure 5.3.2.4.1) and ECUR (figure 5.3.2.4.2) for redelivery attempts in the origination direction.

Figure 5.3.2.4.1: Online charging in origination redelivery attempt for IEC

1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.

2) The SMS node triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the origination procedures.

Figure 5.3.2.4.2: Online charging in origination redelivery attempt for ECUR

1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.

2) The SMS node triggers a Reserve Units Request[Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the origination or termination procedures.

6) The SM transaction is successfully acknowledged.

7) The SMS node triggers a Reserve Units Request[Terminate] message to the OCS reporting the successful event transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Reserve Units Response message to the SMS node.

5.3.2.5 Termination charge

Figure 5.3.2.5.1: Online charging in termination for IEC

1) The SMS node receives an incoming SM-SUBMIT from an application destined for a mobile recipient.

NOTE: This scenario differs from simple submission charging as described in clause 5.3.2.1 in that typically the mobile recipient (instead of originator or both parties) will be charged for such a short message.

2) The SMS node triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the termination procedures.

Figure 5.3.2.5.2: Online charging in termination for ECUR

1) The SMS node receives an incoming SM-SUBMIT from an application destined for a mobile recipient.

NOTE: This scenario differs from simple submission charging as described in clause 5.3.2.1 in that typically the mobile recipient (instead of originator or both parties) will be charged for such a short message.

2) The SMS node triggers a Reserve Units Request [Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the termination procedures.

6) The SM transaction is successfully acknowledged.

7) The SMS node triggers a Reserve Units Request [Terminate] message to the OCS reporting the successful event transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Reserve Units Response message to the SMS node.

5.3.2.6 Termination charge retry

Figure 5.3.2.6.1: Online charging in termination redelivery attempt for IEC

1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.

2) The SMS node triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the termination procedures.

Figure 5.3.2.6.2: Online charging in termination redelivery attempt for ECUR

1) An SMS node internal trigger occurs to attempt a redelivery of a previously failed and stored SM.

2) The SMS node triggers a Reserve Units Request[Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the termination procedures.

6) The SM transaction is successfully acknowledged.

7) The SMS node triggers a Reserve Units Request[Terminate] message to the OCS reporting the successful event transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Reserve Units Response message to the SMS node.

5.3.2.7 Unsuccessful transaction

Unsuccessful transaction after IEC

Figure 5.3.2.7.1 only applies where a refund action is required for unsuccessful delivery.

Figure 5.3.2.7.1: Unsuccessful transaction after IEC

1) The SMS node receives a trigger to attempt delivery of an SM. This may be for origination, termination or redelivery attempt.

2) The SMS node triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for origination or termination procedures.

6) The SM transaction is acknowledged as an unsuccessful transaction (either via explicit signalling or an internal trigger).

7) The SMS node triggers a Debit Units Request (Refund Account) message to the OCS.

8) The OCS performs the appropriate refund processing based on the received request.

9) The OCS responds with a Debit Units Response (Refund Account) message to the SMS node.

Unsuccessful transaction in ECUR

Figure 5.3.2.7.2: Unsuccessful transaction for ECUR

1) The SMS node receives a trigger occurs to attempt delivery of an SM. This may be for origination, termination or redelivery attempt.

2) The SMS node triggers a Reserve Units Request[Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS node.

5) If authorized, the SMS node continues the SM processing as appropriate for the origination or termination procedures.

6) The SM transaction is acknowledged as an unsuccessful transaction (either via explicit signalling or an internal trigger).

7) The SMS node triggers a Reserve Units Request[Terminate] message to the OCS reporting the used unit for the service to zero. This characterizes the unsuccessful event transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Reserve Units Response message to the SMS node.

5.3.2.8 IMS/SMS Interworking Messages Charging

This clause contains message flows for the different operation models IEC (figure 5.3.2.8.1) and ECUR (figure 5.3.2.8.2) for IMS/SMS Interworking messages in the origination direction.

Figure 5.3.2.8.1: Online charging in origination IMS/SMS Interworking Messages for IEC

1) The IP-SM-GW receives an incoming SIP MESSAGE.

2) The IP-SM-GW parses the SIP MESSAGE.

3) The IP-SM-GW triggers a Debit Units Request message to the OCS.

4) The OCS performs the appropriate credit processing based on the received Debit Units Request.

5) The OCS responds with a Debit Units Response message to the IP-SM-GW.

6) IP-SM-GW converts the SIP MESSAGE to 1 or n (n>=1) short messages.

7) If authorized, the IP-SM-GW forwards the segmented short messages.

Figure 5.3.2.8.2: Online charging in origination IMS/SMS Interworking Messages for ECUR

1) The IP-SM-GW receives an incoming SIP MESSAGE.

2) The IP-SM-GW parses the SIP MESSAGE.

3) The IP-SM-GW triggers a Reserve Units Request[Initial] message to the OCS.

4) The OCS performs the appropriate credit processing based on the received Reserve Units Request.

5) The OCS responds with a Reserve Units Response message to the IP-SM-GW.

6) IP-SM-GW converts the SIP MESSAGE to 1 or n (n>=1) short messages.

7) If authorized, the IP-SM-GW forwards segmented short messages.

8) All the short messages transactions are successfully acknowledged.

9) The IP-SM-GW triggers a Reserve Units Request[Terminate] message to the OCS reporting the successful event transaction.

10) The OCS performs the appropriate credit processing based on the received request.

11) The OCS responds with a Reserve Units Response message to the IP-SM-GW.

5.3.2.9 Simple Submission with SM service request

This clause contains message flows for operation models IEC (figure 5.3.2.9-1) where application of a SM service is subject to charging independent from the SM submission.

Editors Note: Simple SM submission with SM service request for operation model ECUR is FFS.

Figure 5.3.2.9.1: Online charging in simple submission with SM service request for IEC

1) Depending on which SMS mechanism (i.e. SMS or SMSIP) is in operation, the SMS node receives an incoming SM-Submit or a MAP-Forward-SM which includes a SM service request (such as forwarding or SM copy).

2) The SMS node triggers a Debit Units Request message to the OCS for the SM submission.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message for the SM submission to the SMS node.

5) If normal SM processing is authorized in step 4, the SMS Node analyzes the SM and detects that a SM service shall be applied that is subject to charging.

6) If a SM service subject to charging is detected in step 5, the SMS node triggers an additional Debit Units Request message to the OCS for the requested SM service.

7) The OCS performs the appropriate credit processing based on the received request.

8) The OCS responds with a Debit Units Response message for the requested SM service to the SMS node.

9) If authorized in step 7, the SMS node applies the requested SM service.

NOTE 1: Depending on the nature of the requested SM service, "service application" may involve creating additional messages (for example in case of a SM copy service). This is deemed part of step 9 and not otherwise shown in this diagram.

10) If authorized in step 4, the SMS node continues the SM processing as appropriate for the origination procedures.

NOTE 2: Authorization of SM processing is independent of the authorization for application of a SM service.
I.e. if authorization is for SM processing is granted in step 4 but authorization for SM service is refused in step 8 SM processing appropriate for the originating service continues without applying the requested SM service.

5.3.2.10 Void

5.3.2.11 Device Triggering using T4

5.3.2.11.1 SMS submission to SMS-SC for Device Triggering

This clause contains the message flows for the scenario where the MTC-IWF submits a request to SMS-SC for SM transfer towards the UE for Device Triggering purpose, in IEC operation model (figure 5.3.2.11.1.1):

Figure 5.3.2.11.1.1: Online charging – SMS submission to SMS-SC for Device Triggering – IEC

1) The SMS-SC receives an incoming "Device Trigger Request" from an MTC-IWF over T₄, destined to a UE recipient.

2) The SMS-SC triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Debit Units Response message to the SMS-SC.

5) The SMS-SC returns "Device Trigger Answer" with appropriate result associated to the reception of the trigger request: successfully received by SMS-SC or failed due to error at SMS-SC.

5.3.2.11.2 SMS Delivery from SMS-SC for Device Triggering

This clause contains message flows for the different operation models IEC (figure 5.3.2.11.2.1) and ECUR (figure 5.3.2.11.2.2) for delivery attempts from SMS-SC for SM transfer towards the UE for Device Triggering.

Figure 5.3.2.11.2.1: Online charging SMS Delivery retry from SMS-SC for Device Triggering – IEC

1) The SMS-SC decides to forward "SMS Deliver" message towards the receiving party, based on same trigger as step 1 of Figure 5.2.2.4.2.1.

2) The SMS-SC triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the internal trigger.

4) The OCS responds with a Debit Units Response message to the SMS-SC.

5) If authorized, the SMS-SC continues the SM processing for delivering the short message to the UE.

6) The SMS-SC receives "SMS Deliver Answer" message as the delivery success of the SM transfer.

7) The SMS-SC sends "Delivery Report Request" to MTC-IWF with appropriate result associated to the successful delivery of the device trigger to the UE.

8) The MTC-IWF acknowledges by sending "Delivery Report Answer".

Figure 5.3.2.11.2.2: Online charging SMS Delivery retry from SMS-SC for Device Triggering – ECUR

1) The SMS-SC decides to forward "SMS Deliver" message towards the receiving party, based on same trigger as step 1 of Figure 5.2.2.4.2.1.

2) The SMS-SC triggers a Reserve Units Request [Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS-SC.

5) If authorized, the SMS-SC continues the SM processing for delivering the short message to the UE.

6) The SMS-SC receives "SMS Deliver Answer" message as the delivery success of the SM transfer.

7) The SMS-SC triggers a Debit Units Request[Terminate] message to the OCS reporting the successful transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Debit Units Response message to the SMS-SC.

10) The SMS-SC sends "Delivery Report Request" to MTC-IWF with appropriate result associated to the successful delivery of the device trigger to the UE.

11) The MTC-IWF acknowledges by sending "Delivery Report Answer".

5.3.2.11.3 Unsuccessful SMS Delivery from SMS-SC for Device Triggering

This clause contains message flows for the different operation models IEC (figure 5.3.2.11.3.1) and ECUR (figure 5.3.2.11.3.2) for unsuccessful delivery from SMS-SC of a SM towards the UE for Device Triggering.

Figure 5.3.2.11.3.1: Online charging unsuccessful SMS Delivery from SMS-SC for Device Triggering after IEC

1) The SMS-SC decides to forward "SMS Deliver" message towards the receiving party, based on same trigger as step 1 of Figure 5.2.2.4.2.1.

2) The SMS-SC triggers a Debit Units Request message to the OCS.

3) The OCS performs the appropriate credit processing based on the internal trigger.

4) The OCS responds with a Debit Units Response message to the SMS-SC.

5) If authorized, the SMS-SC continues the SM processing for delivering the short message to the UE.

6) The SMS-SC receives "SMS Deliver Answer" message as the delivery failure of the SM transfer attempt, or an internal trigger indicating failure.

7) The SMS-SC triggers a Debit Units Request (Refund Account) message to the OCS.

8) The OCS performs the appropriate refund processing based on the received request.

9) The OCS responds with a Debit Units Response (Refund Account) message to the SMS-SC.

Figure 5.3.2.11.3.2: Online charging Unsuccessful SMS Delivery from SMS-SC for Device Triggering after ECUR

1) The SMS-SC decides to forward "SMS Deliver" message towards the receiving party, based on same trigger as step 1 of Figure 5.2.2.4.2.1.

2) The SMS-SC triggers a Reserve Units Request [Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS-SC.

5) If authorized, the SMS-SC continues the SM processing for delivering the short message to the UE.

6) The SMS-SC receives "SMS Deliver Answer" message as the delivery failure of the SM transfer attempt, or an internal trigger indicating failure.

7) The SMS-SC triggers a Debit Units Request[Terminate] message to the OCS reporting the used unit for the service to zero, as a failed transaction.

8) The OCS performs the appropriate credit processing based on the received request.

9) The OCS responds with a Debit Units Response message to the SMS-SC.

5.3.2.11.4 SMS submission to SMS-SC for Device Triggering – Replace procedure

Figure 5.3.2.11.4.1 describes the scenario where the MTC-IWF submits a request to SMS-SC for a replace procedure of Device Triggering, in IEC operation model:

Figure 5.3.2.11.4.1: Online charging – SMS submission to SMS-SC for replace Device Triggering

1) The SMS-SC receives an incoming "Device Trigger Request" indicating "Replace" from an MTC-IWF over T₄.

2) The SMS-SC determines the trigger message identified by the External Identifier or MSISDN, SCS Identifier, and old trigger reference number in the received Device Trigger Replace message, is pending at SMS-SC: the new trigger message replaces the previous one.

3) The SMS-SC triggers a Debit Units Request message to the OCS.

4) The OCS performs the appropriate credit processing based on the received replace request.

5) The OCS responds with a Debit Units Response message to the SMS-SC.

6) The SMS-SC returns "Device Trigger Answer" with appropriate result of the successful or unsuccessful replace procedure.

7) In case of successful replace, the new SM to be delivered uses the same procedure as per clause 5.3.2.11.2.

5.3.2.11.5 SMS submission to SMS-SC for Device Triggering – Recall procedure

Figure 5.3.2.11.5.1 describes the scenario where the MTC-IWF submits a request to SMS-SC for a recall procedure for Device Triggering:

Figure 5.3.2.11.5.1: Online charging – SMS submission to SMS-SC for recall Device Triggering

1) The SMS-SC receives an incoming "Device Trigger Request" indicating "Recall" from an MTC-IWF over T₄.

2) The SMS-SC determines the trigger message identified by the External Identifier or MSISDN, SCS Identifier, and old trigger reference number in the received Device Trigger Recall message, is pending at SMS-SC: the old trigger message is deleted.

3) The SMS-SC triggers a Debit Units Request message to the OCS.

4) The OCS performs the appropriate credit processing based on the received recall request.

5) The OCS responds with a Debit Units Response message to the SMS-SC.

6) The SMS-SC returns "Device Trigger Answer" with appropriate result of the recall procedure. In case in step 2 there was no pending Device trigger message, a failure is reported.

5.3.2.12 MSISDN-less SMS MO via T4

5.3.2.12.1 Introduction

The message flows associated to the MSISDN-less SMS MO via T4, describe the triggers occurring in the SMS-SC Node. As specified in TS 23.682 [17], the SMS delivery procedures to SMS-SC and SMS delivery report from SMS-SC are per TS 23.040 [12], therefore involving SMS-GMSC/SMS-IWMSC depending on the scenario. However, per this TS 23.040 [12], the interface between the SMS-GMSC/SMS-IWMSC and the SMS-SC is out of scope of 3GPP, therefore SMS-GMSC/SMS-IWMSC are assumed as internal to SMS-SC for the charging flows with triggers description.
The network does not perform any storing and forwarding functionality for MO-SMS.

Only ECUR operation model is applicable to MSISDN-less SMS MO via T4.

NOTE: As specified in TS 23.682 [17], the external identifier associated to the transaction is not available before the when the MO payload delivery response is received by the SMS-SC, therefore the IEC operation model is considered as not relevant for successful scenario.

5.3.2.12.2 MSISDN-less SMS MO via T4 – successful case

Figure 5.3.2.12.2.1 describes the scenario where MSISDN-less UE originates SMS-MO destined to a recipient SCS/AS using MSISDN-less SMS MO via T4 procedure, in ECUR operation model:

Figure 5.3.2.12.2.1: Online charging MSISDN-less SMS MO via T4 – successful case

1) The SMS-SC receives a "SMS Submit" incoming message originated by a MSISDN-less UE to deliver small data to SCS/AS.

2) The SMS-SC triggers a Reserve Units Request[Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response message to the SMS-SC.

5) If authorized, the SMS-SC sends the "MO payload delivery Request" message to the MTC-IWF address (as pre-configured in the SMS-SC for this SCS/AS), with the SMS payload and the destination SME address (long/short code of the SCS/AS).

6) The MTC-IWF retrieves the external ID from the HSS (based on the IMSI of the UE and application port ID).

7_8) The MTC-IWF forwards the SMS to the SCS/AS (received destination SME), and receives the successful answer.

9) The MTC-IWF returns the success indication to SMS-SC, along with the external identifier associated to this transaction.

10) The SMS-SC triggers a Debit Units Request[Terminate] message to the OCS.

11) The OCS performs the appropriate credit processing based on the received request.

12) The OCS responds with a Debit Units Response message to the SMS-SC.

13) The SMS-SC indicates success back to UE.

5.3.2.12.3 MSISDN-less SMS MO via T4 – error cases

5.3.2.12.3.1 MSISDN-less SMS MO via T4 – failure at submission to SMS-SC

Figure 5.3.2.12.3.1.1 describes the scenario where MSISDN-less UE originates SMS-MO destined to a recipient SCS/AS using MSISDN-less SMS MO via T4 procedure, and failure at submission to SMS-SC:

Figure 5.3.2.12.3.1.1: Online charging MSISDN-less SMS MO via T4 – failure at submission

1) The SMS-SC receives a "SMS Submit" incoming message originated by a MSISDN-less UE to deliver small data to SCS/AS.

2) The SMS-SC triggers a Reserve Units Request[Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request and identified the transaction is not authorized.

4) The OCS responds with a Reserve Units Response [Initial, NOK] message to the SMS-SC.

5) The SMS-SC indicates failure back to UE, and will not initiate any message towards the MTC-IWF due to this failed attempt.

5.3.2.12.3.2 MSISDN-less SMS MO via T4 – failure at the MTC-IWF

Figure 5.3.2.12.3.2.1 describes the scenario where MSISDN-less UE originates SMS-MO destined to a recipient SCS/AS using MSISDN-less SMS MO via T4 procedure, and failure at the MTC-IWF:

Figure 5.3.2.12.3.2.1; Online charging MSISDN-less SMS MO via T4 – failure at the MTC-IWF

1) The SMS-SC receives a "SMS Submit" incoming message originated by a MSISDN-less UE to deliver small data to SCS/AS.

2) The SMS-SC triggers a Reserve Units Request [Initial] message to the OCS.

3) The OCS performs the appropriate credit processing based on the received request.

4) The OCS responds with a Reserve Units Response [Initial] message to the SMS-SC.

5) If authorized, the SMS-SC sends the "MO payload delivery Request" message to the MTC-IWF address (as pre-configured in the SMS-SC for this SCS/AS), with the SMS payload and the destination SME address (long/short code of the SCS/AS).

6) Failure in handling the submitted SMS-MO in the MTC-IWF, including failure submission to the SCS/AS step 7 and 8 in Figure 5.3.2.11.2.1.

7) The MTC-IWF returns the failure delivery indication to SMS-SC.

8) The SMS-SC triggers a Debit Units Request [Terminate] message to the OCS, reporting the used unit for the service to zero.

9) The OCS performs the appropriate credit processing based on the received request.

10) The OCS responds with a Debit Units Response message to the SMS-SC.

11) The SMS-SC indicates failure back to UE.