5.1 Offline charging scenarios

32.2993GPPCharging managementDiameter charging applicationsRelease 17Telecommunication managementTS

5.1.1 Basic principles

5.1.1.0 Introduction

Offline charging for both events and sessions between CTF and the CDF is performed using the Rf reference point as defined in TS 32.240 [1].

Two basic scenarios are used:

– Event based charging;

– Session based charging.

5.1.1.1 Event based charging

In scenario figure 5.1.1.1.1, CTF asks the CDF to store event related charging data.

Figure 5.1.1.1.1: Event based charging

1) Request for resource usage: UE-A requests the desired resource from the Network Element.

2) Content/Service Delivery: the Network Element delivers the content/service.

3) Charging Data Generation: the CTF generates charging data related to service delivery.

4) Record Charging Data Request: the CTF requests the CDF to store event related charging data for CDR generation purposes.

5) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.

6) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

5.1.1.2 Session based charging

In scenario figure 5.1.1.2.1, CTF asks the CDF to store session related charging data.

Figure 5.1.1.2.1: Session based charging

1) Request for resource usage: UE-A requests the desired session from the Network Element.

2) Session ongoing: the Network Element establish the session.

3) Charging Data Generation: the CTF generates charging data related to session.

4) Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.

5) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.

6) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

7) Charging Data Generation: the CTF generates charging data related to session due of e.g. intermediate timer expiry.

8) Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.

9) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.

10) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

11) Session release: the session is released.

12) Charging Data Generation: the CTF generates charging data related to session due of session termination.

13) Record Charging Data Request: the CTF requests the CDF to store session related charging data for CDR generation purposes.

14) Process Request: CDF stores received information. Whether the CDR is generated or not depends on CDR generation configuration.

15) Record Charging Data Response: the CDF informs the CTF that charging data was stored.

5.1.2 Basic operation

Event and session based Charging are performed by the use of the "Charging Data Transfer" operation:

– "Charging Data Request"; sent from CTF  CDF
After detecting a chargeable event, the CTF sends a Charging Data Request to the CDF.

– "Charging Data Response"; sent from CDF  CTF
The CDF replies with a Charging Data Response, which informs the CTF that charging data was received.

Table 5.1.2.1 and table 5.1.2.2 describe the content of these operations.

Table 5.1.2.1: Charging Data Request content

Information Element

Category

Description

Session Identifier

M

This field identifies the operation session.

Originator Host

M

This field contains the identification of the source point of the operation and the realm of the operation originator.

Originator Domain

M

This field contains the realm of the operation originator.

Destination Domain

M

This field contains the realm of the operation destination.

Operation Type

M

This field defines the transfer type: event for event based charging and start, interim, stop for session based charging.

Operation Number

M

This field contains the sequence number of the transferred messages.

Operation Identifier

OM

The field corresponds to the unique operation identification.

User Name

OC

The field contains the identification of the service user.

Destination Host

OC

This field contains the identification of the destination point of the operation.

Operation Interval

OC

This field contains the proposal for instructions to produce records continuously during a session.

Origination State

OC

This field contains the state associated to the source point of the operation.

Origination Timestamp

OC

This field contains the time when the operation is requested.

Proxy Information

OC

This field contains the parameter of the proxy.

Route Information

OC

This field contains the parameter of the route.

Operation Token

OM

This field identifies the domain, subsystem or service and release.

Service information

OM

This parameter holds the individual service specific parameters as defined in the corresponding ‘middle tier’ TS.

Table 5.1.2.2: Charging Data Response content

Information Element

Category

Description

Session Identifier

M

This field identifies the operation session.

Operation Result

M

This field identifies the result of the operation.

Originator Host

M

This field contains the identification of the source point of the operation and the realm of the operation originator.

Originator Domain

M

This field contains the realm of the operation originator.

Operation Type

M

This field defines the transfer type: event for event based charging and start, interim, stop for session based charging.

Operation Number

M

This field contains the sequence number of the transferred messages.

Operation Identifier

OM

The field corresponds to the unique operation identification.

Operation Interval

OC

This field contains the instructions to produce records continuously during a session.

Error Reporting Host

OC

If proxies exist between the accounting client and the accounting server this field contains the identity of the proxy that sent a response other than 2001 (Success).

Origination State

OC

This field contains the state associated to the source point of the service.

Origination Timestamp

OC

This field contains the time when the operation is requested.

Proxy Information

OC

This field contains the parameter of the proxy.