5.4 MMTel converged charging scenarios

32.2753GPPCharging managementMultiMedia Telephony (MMTel) chargingRelease 17Telecommunication managementTS

5.4.1 Basic principles

5.4.1.1 General

Converged charging may be performed by the MMTel AS interacting with CHF using Nchf specified in TS 32.290 [57] and TS 32.291 [58]. To provide the data required for the management activities outlined in TS 32.240 [1] (Credit-Control, accounting, billing, statistics etc.), the MMTel AS shall be able to perform converged charging for each of the MMTel supplementary service.

The CTFs implementing the MMTel converged charging functionality may apply:

– Immediate Event Charging (IEC) with Charging Data Request [Event] generated, or

– Session based charging SCUR, with Charging Data Request [Initial, Update, Termination] , or

– Post Event Charging (PEC) with Charging Data Request [Event].

The circumstances on which IEC, SCUR or PEC are applicable, depend on the MMTel supplementary service and/or operator’s policy.

Editor’s note: The use of ECUR is FFS.

Converged charging uses centralized or decentralized unit determination and centralized rating scenarios for event based convergent charging specified in TS 32.290 [57].

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 clauses.

A detailed formal description of the converged charging parameters defined in the present document is to be found in TS 32.291 [58].

A detailed formal description of the CDR parameters defined in the present document is to be found in TS 32.298 [51].

The selection of the CHF can be configured in the MMTel AS.

Editor’s note: The CHF selection mechanism using other means, e.g. SIP and user profile, is FFS.

5.4.1.2 Applicable Triggers for MMTel

5.4.1.2.1 General

When a charging event is issued towards the CHF, it includes details such as Subscriber identifier (e.g. IMPI).

Each trigger condition (i.e. chargeable event) defined for the MMTel converged charging functionality, is specified with the associated behaviour when they are met.

Table 5.4.1.2.1 summarizes the set of default trigger conditions, including their category and if they are possible to change, which shall be supported by the MMTel AS. For "immediate report" category, the table also provides the corresponding Charging Data Request [Initial, Udate, Termination] message sent towards the CHF.

Table 5.4.1.2.1: Default Trigger conditions for MMTel

Trigger Conditions		Trigger level	Converged Charging default category	Offline only charging default category	CHF allowed to change category	CHF allowed to enable and disable	Message when "immediate reporting" category
	Originating Identification Presentation (OIP)
Invite OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Originating Identification Restriction (OIR)
Invite OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Terminating Identification Presentation (TIP)
Invite OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Terminating Identification Restriction (TIR)
Invite OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Communication Hold (HOLD)
Update OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Communication Barring (CB)
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
	Message Waiting Indication (MWI)
Notify		–	Immediate	Immediate	Not Applicable	Not Applicable
	Conference (CONF)
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
Created		–	Immediate	Immediate	Not Applicable	Not Applicable
User joining		–	Immediate	Immediate	Not Applicable	Not Applicable
User leaving		–	Immediate	Immediate	Not Applicable	Not Applicable
Bye		–	Immediate	Immediate	Not Applicable	Not Applicable
	Completion of Communication sessions to Busy Subscriber (CCBS)
Notify		–	Immediate	Immediate	Not Applicable	Not Applicable
	Completion of Communications by No Reply (CCNR)
Notify		–	Immediate	Immediate	Not Applicable	Not Applicable
	Communications Diversion (CDIV)
Invite (OK)		–	Immediate	Immediate	Not Applicable	Not Applicable
Answer		–	Immediate	Immediate	Not Applicable	Not Applicable
Bye		–	Immediate	Immediate	Not Applicable	Not Applicable
	Communication Waiting (CW)
Invite OK		–	Immediate	Immediate	Not Applicable	Not Applicable
	Explicit Communication Transfer (ECT)
Refer		–	Immediate	Immediate	Not Applicable	Not Applicable
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
Answer		–	Immediate	Immediate	Not Applicable	Not Applicable
Release		–	Immediate	Immediate	Not Applicable	Not Applicable
	Flexible Alerting (FA)
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
Answer/Cancel		–	Immediate	Immediate	Not Applicable	Not Applicable
Bye		–	Immediate	Immediate	Not Applicable	Not Applicable
	Malicious Communication Identification (MCID)
Store		–	Immediate	Immediate	Not Applicable	Not Applicable
	Customized Alerting Tone (CAT)
Stop		–	Immediate	Immediate	Not Applicable	Not Applicable
	Closed User Group (CUG)
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
Answer		–	Immediate	Immediate	Not Applicable	Not Applicable
Bye		–	Immediate	Immediate	Not Applicable	Not Applicable
	Personal Network Management (PNM)
Invite		–	Immediate	Immediate	Not Applicable	Not Applicable
Answer		–	Immediate	Immediate	Not Applicable	Not Applicable
Bye		–	Immediate	Immediate	Not Applicable	Not Applicable
	Customized Ringing Signal (CRS)
Stop		–	Immediate	Immediate	Not Applicable	Not Applicable

Editor’s note: The use of IEC, PEC, ECUR and SCUR is FFS.

The CDR generation mechanism processed by the CHF upon receiving Charging Data Request [Event, Initial, Update, Termination] issued by the MMTel for these chargeable events, is specified in clause 5.4.3.

5.4.2 Message flows

5.4.2.1 Introduction

The flows described in the present document specify the converged charging service with IMS NF (e.g. IMS AS) as the NF Consumer for different charging scenarios. The messages associated with these charging scenarios are shown primarily for information and to illustrate the charging triggers.
They are not intended to be exhaustive of all the IMS message flows described in TS 24.228 [221].

Although each MMTel supplementary service is described by separated flows illustrating the dedicated trigger(s) for each MMTel supplementary service, the service may be combined with other MMTel supplementary services or IMS information.

The circumstances on which PEC, ECUR or SCUR are applied, depend on the MMTel supplementary service and/or operator’s policy.

5.4.2.2 Void

5.4.2.3 Void

5.4.2.4 Void

5.4.2.5 Void

5.4.2.6 MMTEL supplementary services – PEC

The message flows clause 5.2.2.1. except for figures 5.2.2.1.7.2.1, 5.2.2.1.9.1.1, and 5.2.2.1.9.2.1, are applicable with the following changes:

– CDF replaced with CHF.

– AS CDR replaced with CHF CDR.

– Charging Data Request [Start] replaced with Charging Data Request [Initial].

– Charging Data Request [Interim] replaced with Charging Data Request [Update].

– Charging Data Request [Stop] replaced with Charging Data Request [Termination].

5.4.2.7 MMTEL supplementary services – ECUR

The message flow in figure 5.3.2.1.4.1.1 is applicable with the following changes:

– OCS replaced with CHF.

– Addition of creation, updating, and closing of CHF CDR in CHF (OCS).

– Reserve Units Request [Initial] replaced with Charging Data Request [Initial].

– Reserve Units Request [Update] replaced with Charging Data Request [Update].

– Reserve Units Request [Termination] replaced with Charging Data Request [Termination].

5.4.2.8 MMTEL supplementary services – SCUR

The message flows clause 5.2.2.1. except the following figures 5.2.2.1.6.1.1, 5.2.2.1.6.2.1, 5.2.2.1.8.1, 5.2.2.1.10.1, 5.2.2.1.12.1, and 5.2.2.1.13.1, are applicable with the following changes:

– CDF replaced with CHF

– AS CDR replaced with CHF CDR

– Charging Data Request [Start] replaced with Charging Data Request [Initial]

– Charging Data Request [Interim] replaced with Charging Data Request [Update]

– Charging Data Request [Stop] replaced with Charging Data Request [Termination]

The message flows clause 5.3.2.1, except the figure 5.3.2.1.4.1.1, are applicable with the following changes:

– OCS replaced with CHF

– Addition of creation, updating, and closing of CHF CDR in CHF (OCS)

– Reserve Units Request [Initial] replaced with Charging Data Request [Initial].

– Reserve Units Request [Update] replaced with Charging Data Request [Update]

– Reserve Units Request [Termination] replaced with Charging Data Request [Termination]

5.4.3 CDR generation

5.4.3.1 Introduction

The CHF CDRs for MMTel 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, updating 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 MMTel charging CHF CDR is used to collect charging information related to MMTel chargeable events. The details of the triggers are specified in TS 32.260 [20].

5.4.4 Ga record transfer flows

Details of the Ga protocol application are specified in TS 32.295 [54].

5.4.5 Bi CDR file transfer

Details of the Bi protocol application are specified in TS 32.297 [52].