5.1 SMS charging principles
32.2743GPPCharging managementRelease 17Short Message Service (SMS) chargingTelecommunication managementTS
5.1.1 General principles
The Short Message Service (SMS) comprises 5 main operational scenarios:
– Person to Person: The message is sent by a UE as originator and received by a UE as destination.
– Person to Application: The message is sent by a UE as originator and received by a third party application as destination.
– Application to Person: The message is sent by a third party application as originator and received by a UE as destination.
– Application to Application: The message is sent by a third party application as originator and received by another third party application as destination.
– Device Triggering: the message is sent on behalf of an application as originator and received by a device as destination.
– MSISDN-less UE to Application via T4: the message is sent by a MSISDN-less UE as originator and received by a third party application as destination (e.g. SCS/AS) in MSISDN-less MO-SMS via T4 scenario.
In addition SMS nodes may apply services such as Value Added Services (VAS) specified in TS 22.142 [16], services defined in industry standard protocols for SM submission from applications in a fixed network (protocols such as SMPP, UCP/EMI, OIS, CIMD, etc.) or vendor specific services as endorsed by TS 23.040 [7]. As such, the SMS node collects charging information such as:
– the destination and source addresses applied for an SM;
– an indication of origination or termination handling;
– identification of the node(s) and connection(s) involved in the SM transaction;
– SM validity period;
– in scenarios involving an application / VASP, the charging information describes the identification of the application / VASP;
– requested SM service type.
5.1.2 Segmentation and concatenation
Information about concatenated messages should be sent to the charging systems in order to apply the appropriate charging models. The charging system may be required to be stateful to process information about segmented messages.
5.1.3 Triggers for generation of charging information
The following service level events shall, based on operator configuration, trigger the generation of charging information:
– Simple submission, except for device triggering – based on reception at the SMS node.
– Enhanced submission – based on completion of the transaction handling at the SMS node.
– Origination retry – based on the enhanced submission where the initial handling fails and a redelivery attempt is initiated.
– Delivery, except for device triggering – based on delivery from the SMS node.
– Delivery report – reports based on the delivery to Person.
– Termination – Application to Person scenario only.
– Termination retry – Application to Person scenario only – reattempt delivery of an SM to a terminating entity;
– SM Service request.
– SMS via T4 related events specified in clause 5.1.4.
Depending on the charging model applied, a "refund" may be necessary for unsuccessful delivery in online charging.
See clause 5.2 and 5.3 for detailed procedures associated with the triggers above for offline charging and online charging respectively.
5.1.4 SMS via T4
For the following TS 23.682 [17] procedures using T4 interface and relying on SMS capability, online and offline charging functionalities are based on SMS-SC reporting chargeable events associated with the corresponding functionalities:
– Device Triggering Function;
– MSISDN-less MO-SMS via T4.
For Device Triggering functionality, following chargeable events are considered:
– Device Trigger submitted to the SMS-SC from MTC-IWF, for request, replace and recall;
– SMS Delivery from the SMS-SC for Device Triggering towards the UE – based on delivery from the SMS node;
– SMS Delivery from the SMS-SC for Device Triggering towards the UE – based on completion of the transaction handling at the SMS node;
The protocol description for Device Triggering functionality is detailed in TS 29.337 [18].
For MSISDN-less MO-SMS via T4 functionality, allowing MSISDN-less UE to send small data to an SCS/AS (i.e. destination SME) using SMS-MO, the completion of the transaction at the SMS-SC is considered, since SMS-SC store and forward capability for MO-SMS is not used. Instead, the SMS-MO received by the SMS-SC through MO submission TS 23.040 [12]) procedures, is directly forwarded to the MTC-IWF through appropriate protocol for further transfer to the recipient SCS/AS. Also, the SMS-MO delivery answer status from MTC-IWF received by the SMS-SC is directly conveyed back to the UE.
For MSISDN-less MO-SMS via T4 functionality, the chargeable event considered is:
– MO-SMS via T4 submission – based on Delivery response from the MTC-IWF.
The protocol description for MSISDN-less MO-SMS via T4 functionality is detailed in TS 29.338 [200].
5.1.5 NR REDCAP Charging
For SMS converged online and offline charging scenarios, the SMSF provides for NR RedCap UE using NR the RAT Type NR_REDCAP, according to clause 5.41 of 3GPP TS 23.501 [201].