5.4 SMS converged online and offline charging scenarios
32.2743GPPCharging managementRelease 17Short Message Service (SMS) chargingTelecommunication managementTS
5.4.1 Basic principles
5.4.1.1 General
Converged charging may be performed by the SMSF interacting with CHF using Nchf specified in TS 32.290 [19] and TS 32.291 [20]. In order to provide the data required for the management activities outlined in TS 32.240 [2] (Credit-Control, accounting, billing, statistics etc.), the SMSF shall be able to perform converged charging for each of the SMS transactions.
The SMSF shall be able to perform convergent charging by interacting with CHF, for charging data related to SMS over NAS. The Charging Data Request and Charging Data Response are exchanged between the SMSF and the CHF, based on PEC, IEC or ECUR scenarios specified in TS 32.290 [19]. The Charging Data Request is issued by the SMSF towards the CHF when certain conditions (chargeable events) are met.
Converged charging uses centralized or decentralized unit determination and centralized rating scenarios for convergent charging IEC and ECUR specified in TS 32.290 [19].
The contents and purpose of each charging event that triggers interaction with CHF, as well as the chargeable events that trigger them, are described in the following sub-clauses.
A detailed formal description of the converged charging parameters defined in the present document is to be found in TS 32.291 [20].
A detailed formal description of the CDR parameters defined in the present document is to be found in TS 32.298 [3].
The chargeable events or messages exchanged between the SMSF and the other nodes are described with generic names
(i.e SMS submit, SMS deliver), to reflect SMS reception or sending by/from the SMSF, independently from the protocol conveying the SMS.
5.4.1.2 Applicable Triggers in the SMSF
5.4.1.2.1 General
When a charging event is issued towards the CHF, it includes details such as Subscriber identifier (e.g. SUPI).
Each trigger condition (i.e. chargeable event) defined for the SMS over NAS converged charging functionality, is specified with the associated behaviour when they are met.
When a MO or MT SMS is sent through the SMSF, and the converged charging is activated, the SMSF invokes a Charging Data Request [Initial] towards the CHF to get authorization to start in ECUR mode. In IEC mode, the Charging Data Request [Event] is sent towards the CHF.
Table 5.4.1.2.1 summarizes the set of default trigger conditions and their category which shall be supported by the SMSF. For "immediate report" category, the table also provides the corresponding Charging Data Request [Initial, Event, Termination] message sent from SMSF towards the CHF.
Table 5.4.1.2.1: Default Trigger conditions in SMSF
|
Trigger Conditions |
Trigger level |
Default category |
CHF allowed to change category |
CHF allowed to enable and disable |
Message when "immediate reporting" category |
|---|---|---|---|---|---|
|
SMS Submit |
– |
Immediate |
Not Applicable |
Not Applicable |
IEC: Charging Data Request [Event] ECUR: Charging Data Request [Initial] |
|
SMS to deliver |
– |
Immediate |
Not Applicable |
Not Applicable |
IEC: Charging Data Request [Event] ECUR: Charging Data Request [Termination] |
|
SMS Submit Answer |
– |
Immediate |
Not Applicable |
Not Applicable |
PEC: Charging Data Request [Event] |
|
SMS Deliver Answer |
– |
Immediate |
Not Applicable |
Not Applicable |
PEC: Charging Data Request [Event] |
For converged charging, the following details of chargeable events and corresponding actions in the SMSF are defined in Table 5.4.1.2.2:
Table 5.4.1.2.2: Chargeable events and their related actions in SMSF
|
Chargeable event |
Conditions |
SMSF action |
|---|---|---|
|
SMS Submit |
IEC: Charging Data Request [Event] ECUR: Charging Data Request [Initial] with a possible request quota for later use |
|
|
SMS to deliver |
IEC: Charging Data Request [Event] ECUR: Charging Data Request [Termination], indicating that charging session is terminated |
|
|
SMS Submit Answer |
PEC: Charging Data Request [Event] |
|
|
SMS Deliver Answer |
PEC: Charging Data Request [Event] |
The CDR generation mechanism processed by the CHF upon receiving Charging Data Request [Event, Initial, Termination] issued by the SMSF for these chargeable events, is specified in clause 5.4.3.
5.4.1.3 CHF selection
The CHF to be used by the SMSF can be:
– Discovered via NRF upon SMS activation from AMF to SMSF.
– SMSF locally provisioned in charging characteristics.
The option depends on Operator’s policies.
When CHF selection by SMSF is performed via NRF based discovery:
– For UE determined by SMSF as served by the same PLMN as the SMSF (i.e. non-roaming scenario), the CHF of the PLMN can be discovered based on the UE identifier.
– For UE determined by SMSF in V-PLMN as an in-bound roamer (i.e. roaming scenario), the CHF of the V-PLMN can be discovered based on the PLMN Id of the UE H-PLMN.
5.4.2 Message flows
5.4.2.1 Introduction
The different scenarios below focus on the different messages from/to the SMS Node and corresponding interaction with the CHF, based on scenarios specified in TS 23.502 [202] clause 4.13.3.
5.4.2.2 SMS Submission – IEC
Figure 5.4.2.2.1 describes the scenario where a SMS is submitted to the SMSF for IEC mode
Figure 5.4.2.2.1: SMS submission to SMSF for IEC
1. Initial procedures: see applicable flows.
2. The SMSF receives a "SMS Submit" incoming message originated by a UE.
2ch-a. The SMSF sends Charging Data Request[Event] to CHF for the received MO SMS.
2ch-b. The CHF creates a CDR for this MO SMS.
2ch-c. The CHF acknowledges by sending Charging Data Response[Event] to the SMSF.
3. The SMSF returns "SMS Submit Answer" with appropriate result successful or unsuccessful reception of the SM by the SMSF.
4. Forward SMS per applicable flows.
The table 5.4.2.2.1 describes the correspondence between the message in this scenario, and the message in the different Network scenario for which it is applicable.
Table 5.4.2.2.1: Messages mapping
|
Message |
Message in Network scenario |
Reference |
|---|---|---|
|
2. SMS submit |
2b. Nsmsf_SMService_UplinkSMS (SMS body) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
6b. Nsmsf_SMService_UplinkSMS (Delivery report) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
|
3. SMS submit answer |
2c. Namf_Communication_N1N2MessageTransfer (CP Ack) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
6c. Namf_Communication_N1N2MessageTransfer (CP Ack) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
|
4. Forward SMS |
3. Forward MO |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
7. Delivery report |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
5.4.2.3 SMS Delivery – IEC
Figure 5.4.2.3.1 describes the scenario where a SMS is delivered from the SMSF for IEC mode
Figure 5.4.2.3.1 SMS delivery from SMSF for IEC
1. "SMS to deliver" received by SMSF: see applicable flows.
1ch-a. The SMSF sends Charging Data Request[Event] to CHF for the SMS.
1ch-b. The CHF creates a CDR for this SMS.
1ch-c. The CHF acknowledges by sending Charging Data Response[Event] to the SMSF.
2. UE reachability criteria met.
3. The SMSF forwards the "SMS Deliver" message.
4. The SMSF receives "SMS Deliver Answer" message as the delivery success or failure of the SM transfer attempt.
The table 5.4.2.3.1 describes the correspondence between the message in this scenario, and the message in the different Network scenario for which it is applicable.
Table 5.4.2.3.1: Messages mapping
|
Message |
Message in Network scenario |
Reference |
|---|---|---|
|
1. SMS to deliver |
3. Forward MT SM |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
5. Submit report |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
|
3. SMS deliver |
5. Namf_Communication_N1N2MessageTransfer (SMS body) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
6a. Namf_Communication_N1N2MessageTransfer (Submit Report) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
|
4. SMS deliver answer |
5d. Nsmsf_SMService_UplinkSMS (CP Ack) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
6d. Nsmsf_SMService_UplinkSMS (CP Ack) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
5.4.2.4 SMS Submission – ECUR
Figure 5.4.2.4.1 describes the scenario where a SMS is submitted to the SMSF for ECUR mode.
Figure 5.4.2.4.1: Converged charging SMS Submission using ECUR
1. Initial procedures: see applicable flows.
2. The SMSF receives a "SMS Submit" incoming message originated by a UE.
2ch-a. The SMSF sends Charging Data Request [Initial] to CHF for authorization.
2ch-b. The CHF opens CDR for this SMS submission.
2ch-c. The CHF acknowledges by sending Charging Data Response [Initial] to the SMSF
3. The SMSF returns "SMS Submit Answer" with appropriate result successful or unsuccessful reception of the SM by the SMSF.
4. Forward SMS per applicable flows.
5. "Report SMS" received by SMSF: see applicable flows.
5ch-a. The SMSF sends Charging Data Request [Termination] to the CHF for terminating the charging associated with SMS submission.
5ch-b. The CHF closes the CDR for this SMS submission.
5ch-c. The CHF acknowledges by sending Charging Data Response [Termination] to the SMSF.
6. The SMSF forwards the "SMS Report" message towards the UE.
7. The SMSF receives "SMS Report answer" message as the delivery success or failure of the SM transfer attempt.
8. Termination procedures: see applicable flows
The table 5.4.2.4.1 describes the correspondence between the message in this scenario, and the message in the different Network scenario for which it is applicable.
Table 5.4.2.4.1: Messages mapping
|
Message |
Message in Network scenario |
Reference |
|---|---|---|
|
2. SMS Submit |
2b. Nsmsf_SMService_UplinkSMS (SMS body) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
3. SMS Submit answer |
2c. Namf_Communication_N1N2MessageTransfer (CP Ack) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
4. Forward SMS |
3. Forward MO |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
5. Report SMS |
5. Submit report |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
6. SMS Report |
6a. Namf_Communication_N1N2MessageTransfer (Submit Report) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
|
7. SMS Report answer |
6d. Nsmsf_SMService_UplinkSMS (CP Ack) |
TS 23.502[202] Figure 4.13.3.3-1: MO SMS over NAS |
5.4.2.4a SMS Delivery – ECUR
Figure 5.4.2.4a.1 describes the scenario where a SMS is delivered from the SMSF for ECUR mode.
Figure 5.4.2.4a.1: Converged charging SMS Delivery using ECUR
1. Initial procedures: see applicable flows.
2. "SMS to deliver" received by SMSF: see applicable flows.
2ch-a. The SMSF sends Charging Data Request [Initial] to CHF for authorization.
2ch-b. The CHF opens CDR for this SMS delivery.
2ch-c. The CHF acknowledges by sending Charging Data Response [Initial] to the SMSF
3. The SMSF forwards the "SMS Deliver" message towards the UE.
4. The SMSF receives "SMS Deliver Answer" message as the delivery success or failure of the SM transfer attempt.
5. The SMSF receives a "SMS Report" incoming message originated by a UE.
5ch-a. The SMSF sends Charging Data Request [Termination] to the CHF for terminating the charging associated with SMS delivery.
5ch-b. The CHF closes the CDR for this SMS delivery.
5ch-c. The CHF acknowledges by sending Charging Data Response [Termination] to the SMSF.
3. The SMSF returns "SMS Report answer" with appropriate result successful or unsuccessful reception of the SM by the SMSF.
4. Report SMS per applicable flows.
8. Termination procedures: see applicable flows
The table 5.4.2.4a.1 describes the correspondence between the message in this scenario, and the message in the different Network scenario for which it is applicable.
Table 5.4.2.4a.1: Messages mapping
|
Message |
Message in Network scenario |
Reference |
|---|---|---|
|
1. SMS to deliver |
3. Forward MT SM |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
3. SMS Deliver |
5. Namf_Communication_N1N2MessageTransfer (SMS body) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
4. SMS Deliver answer |
5d. Nsmsf_SMService_UplinkSMS (CP Ack) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
5. SMS Report |
6b. Nsmsf_SMService_UplinkSMS (Delivery report) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
6. SMS Report answer |
6c. Namf_Communication_N1N2MessageTransfer (CP Ack) |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
|
7. Report SMS |
7. Delivery report |
TS 23.502[202] Figure 4.13.3.6-1: MT SMS over NAS in CM_IDLE state via 3GPP access |
5.4.2.5 SMS Submission – PEC
Figure 5.4.2.5.1 describes the scenario where a SMS is submitted to the SMSF for PEC mode
Figure 5.4.2.5.1: SMS submission to SMSF – PEC
1. Initial procedures: see applicable flows in table 5.4.2.2.1.
2. The SMSF receives a "SMS Submit" incoming message.
3. The SMSF returns "SMS Submit Answer" with appropriate result successful or unsuccessful reception of the SM by the SMSF.
3ch-a. The SMSF sends Charging Data Request [Event] to CHF for the SMS.
3ch-b. The CHF creates a CDR for this SMS.
3ch-c. The CHF acknowledges by sending Charging Data Response [Event] to the SMSF.
4. Forward SMS per applicable flows table 5.4.2.2.1.
5.4.2.6 SMS Delivery – PEC
Figure 5.4.2.6.1 describes the scenario where a SMS is delivered from the SMSF for PEC mode
Figure 5.4.2.6.1 SMS delivery from SMSF – PEC
1. "SMS to deliver" received by SMSF: see applicable flows in table 5.4.2.3.1.
2. UE reachability criteria met.
3. The SMSF forwards the "SMS Deliver".
4. The SMSF receives "SMS Deliver Answer" message as the delivery success or failure of the SM transfer attempt.
4ch-a. The SMSF sends Charging Data Request [Event] to CHF for the SMS.
4ch-b. The CHF creates a CDR for this SMS.
4ch-c. The CHF acknowledges by sending Charging Data Response [Event] to the SMSF.
5.4.3 CDR generation
5.4.3.1 Introduction
The CHF CDRs for SMS charging are generated by the CHF to collect charging information that they subsequently transfer to the Charging Gateway Function (CGF).
The following clauses describe in details the conditions for generating, opening and closing the CHF CDR, which shall be supported by the CHF.
5.4.3.2 Triggers for CHF CDR
5.4.3.2.1 General
A SMS charging CHF CDR is used to collect charging information related to SMS chargeable events for PEC, IEC and ECUR.
5.4.3.2.2 Triggers for CHF CDR generation
A CHF CDR is generated by the CHF for each received Charging Data Request[Event].
5.4.3.2.3 Triggers for CHF CDR opening
A CHF CDR shall be opened when the CHF receives Charging Data Request[Initial].
5.4.3.2.4 Triggers for CHF CDR closure
The CHF CDR shall be closed when the CHF receives Charging Data Request[Termination].
5.4.4 Ga record transfer flows
Details of the Ga protocol application are specified in TS 32.295 [6].
5.4.5 Bsm CDR file transfer
Details of the Bsm protocol application are specified in TS 32.297 [5].