3GPP Charging Principles

112/04/08 1

3GPP Charging

112/04/08 2

Outline

3G charging logical architecture Charging functions CS domain PS domain IM Subsystem Service domain (MMS service)

112/04/08 3

Charging Documents Structure

32.200

Charging Principles(charging stage 2)

32.205

Stage 3CS- domain

32.215

Stage 3PS- domain

32.225

Reserved for

Stage 3 IMS(R5)

32.235

Stage 3

Service- domain(R4: MMS service)

112/04/08 4

3G charging logical architecture

Create CDR HLR GMSC Server VMSC Server CGF SCF (not included in current spec.) MMS Relay Server

112/04/08 5

Gn Billing System

GGSN

VMSC Server

SGSN

CS Domain PS Domain

CDR

CDR

CDR

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

CDR

CAP

CAP

CDR

Service Domain

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

CDR

CAP

CAP

CDR

Service Domain

Gr

C

D

Gc

IuPS IuCS A IuPS IuCS Gb Gb A

Gp

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

Ga

CGF

MGW

GMSC Server

MGW

HLR

SCF

CDR

Mc

Mc

MMS Relay Server

CDR

CAP

CAP

CDR

Service Domain

Gn Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

CGF

MGW

GMSC Server

MGW

HLR

CDR

Mc

Mc

MMS Relay Server

Gn

Gi PSTN

Billing System

GGSN

VMSC Server

SGSN

PS Domain

CDR

CDR

CDR

Ga

Ga

CGF

MGW

GMSC Server

MGW

HLR

gsm SCF

CDR

Mc

Mc

MMS Relay Server

CDR

CAP

CAP

CAP

CDR

Service Domain

Gr

C Gc

IuPS IuCS A IuPS IuCS A

Gp

gsm SSF

gprs SSF

gsm SSF

112/04/08 6

Charging functions

Charging Gateway Function (CGF) ： within the Packet-Switched domain, provides a mechanism to transfer charging information from the SGSN and GGSN nodes to the network operator‘s chosen Billing Systems

Charging Collection Function (CCF) ： main functionalities for IMS are in principle equivalent to the Charging Gateway Functions (CGF) that are used in the PS domain 。

Session Charging Function (SCF) ： is responsible for Session Charging including the session control such as e.g. session termination.

Bearer Charging Function (BCF) ： performs the Bearer Charging.

Event Charging Function (ECF) ： performs event-based charging (content charging).

112/04/08 7

ECF Content Provider Charging Function (CPCF) ：

manages the account that is maintained for the content provider. Upon receipt of a charging request from the AS/MRFC, the CPCF processes the request and relays it to the SCCF.

Subscriber Content Charging Function (SCCF) ：handles content charging requests that are made when the subscriber accesses the content. Upon such a content charging request, the SCCF may for example request the Correlation Function to check or to debit the subscriber's account. Content charging requests are received from the Content Provider Charging Function (CPCF)

112/04/08 8

Offline IMS Charging architecture for non-roaming scenario

112/04/08 9

Online IMS Charging architecture

Charging information

flow

ISC

SGSNSGSN CAP

Online Charging System

Home(A) + Visited(A)

Re

Rb

Ro

Ro

Re

Rc

MRFCMRFC

AS(s)AS(s)

ISC

SGSNSGSNCAP


Home(B) + Visited(B)

Re

Rb

Ro

Ro

Re

Rc

Account

Correlation FunctionBearer

Charging FunctionAccount

Correlation Function Bearer

Charging Function

RatingFunction

RatingFunction

S-CSCFS-CSCF S-CSCFS-CSCF

AS(s)AS(s)

MRFCMRFC SCCF

CPCF

SCCF

CPCF

SessionCharging Function


EventCharging Function


112/04/08 10

Circuit-Switched Domain

Specified in TS 32.205 Charging Principles

Provide CDRs Inter-PLMN accounting Visitors from other PLMN Roaming Fixed network operator and other service provid

ers Service Information

112/04/08 11

Charging scenariosMobile to Land (outgoing) callIncoming call to a roaming subscriberDelivery of a mobile terminated short messageIncoming call handled by CAMEL without redirectionEtc.

112/04/08 12

Mobile to land call MSC-A:MOC record for s

ubscriber “A” GMSC:outgoing gatewa

y record

B

1

1

A

ISDN/PSTN

HPLMN

GMSC

MSC-A

HLR

BillingSystem

1

BA

B

1

1

A

ISDN/PSTN

HPLMN

GMSCGMSC

MSC-AMSC-A

HLRHLR

BillingSystemBilling

System

1

BBA

112/04/08 13

Incoming call to a roaming subscriber

GMSC:incoming gateway record

HLR interrogation CDR

GMSC:outgoing gateway record

GMSC:roaming record inculde IMSI of “B”

MSC-B:MTC record for the call to “B”

TAP record

HPLMN

GMSC HLR

BillingSystem

A

2

3

4

A

VPLMN

GMSC

MSC-BBilling

System

BB

4

A

1

ISDN/PSTN

1

4

AB

HPLMN

GMSCGMSC HLRHLR


System

A

2

3

4

A

VPLMN

GMSCGMSC

MSC-BMSC-BBilling

SystemBilling

System

BBB

4

A

1

ISDN/PSTN

1

4

AB

112/04/08 14

Delivery of a mobile terminated short message

MSC:SMT record HLR:HLR interrogation

record GMSC:SMS gateway MT

record

HPLMN

SMS-GMSC

MSC-B

HLR

BillingSystem

BB

A

2

SMS-SC

1

3

A

HPLMN

SMS-GMSC

MSC-BMSC-B

HLRHLR


System

BBB

A

2

SMS-SCSMS-SC

1

3

A

112/04/08 15

Incoming call handled by CAMEL without redirection

GSMC: Incoming gateway record, Terminating CAMEL

MSC:MTC record HLR:HLR interrogation record

(2)Interrogate HLR, fetch the T-CSI

(3.1)GMSC request gsmSSF to pass CAMEL service key to gsmSCF to indicate which service logic it should apply

(3.2)gsmSCF interrogate HLR for subscriber information

(4)GMSC interrogate the HLR to get current location

ISDN/PSTN

B

MSC-B/gsmSSF

GMSC/gsmSSF

gsmSCF

A

Billing System

A

1

2

5

T-CSI(A-B)

3

1

6

4HLR

ISDN/PSTN

B

MSC-B/gsmSSF

GMSC/gsmSSF

gsmSCF

A

Billing System

A

1

2

5

T-CSI(A-B)

3

1

6

4HLR

112/04/08 16

Packet-Switched Domain

Specified in TS 32.215 Charging Principles Charging scenarios

112/04/08 17

Charging Principles Charging Information

Usage of the radio interface, usage duration and etc.

Charging for SMS SGSN provide an S-SMO-CDR, S-SMT-CDR

Charging support for CAMEL Charging Data Collection

S-CDR,G-CDR,M-CDR,S-SMO-CDR,S-SMT-CDR

112/04/08 18

Charging Principles (cont.) Charging Data Record Generation

Data volume limit, time, max number of charging conditions changes

Trigger for S-CDR Qos Change, Tariff Time Change, CDR closure

Trigger for M-CDR Mobility Change

Tirgger for G-CDR

112/04/08 19

CDR generation

Charging Data in the SGSN (S-CDR); Charging Data in the GGSN (G-CDR); Mobile Station Mobility Management Data in SGSN (M-CDR); SMS Mobile Originated Data in SGSN (S-SMO-CDR); SMS Mobile Terminated Data in SGSN (S-SMT-CDR); Mobile Originated location request in SGSN (LCS-MO-CDR); etc.

112/04/08 20

Charging scenarios

Mobile to PDN Context Mobile to Mobile Context PDN to Mobile Context Mobile to PDN Context while

roaming, GGSN in HPLMN

112/04/08 21

PDN

SGSN

GGSN

CGF

HPLMN

1

1

1

A

BBS

Mobile to PDN Context

112/04/08 22

Mobile to PDN Context while roaming via BG

PDN

1

1

BS

GGSN

CGF

HPLMN

Inter PLMN Backbone

1

BG

A

C

1

B

SGSN

BG

CGF

VPLMN

1

A

BS

1

B

A

112/04/08 23

IMS Subsystem

Specified in TS 32.225 Off-line Charging On-line Charging

112/04/08 24

Introduction

Offline Charging IMS network elements report accounting

information CCF construct and format CDRs

Online Charging AS and MRFC report accounting informati

on ECF uses charging event to support OCS

112/04/08 25

112/04/08 26

Charging information

flow

ISC

SGSNSGSN CAP


Home(A) + Visited(A)

Re

Rb

Ro

Ro

Re

Rc

MRFCMRFC

AS(s)AS(s)

ISC

SGSNSGSNCAP


Home(B) + Visited(B)

Re

Rb

Ro

Ro

Re

Rc

Account

Correlation FunctionBearer

Charging FunctionAccount

Correlation Function Bearer

Charging Function

RatingFunction

RatingFunction

S-CSCFS-CSCF S-CSCFS-CSCF

AS(s)AS(s)

MRFCMRFC SCCF

CPCF

SCCF

CPCF





112/04/08 27

Offline Charging Based on CDRs collection Successful case and Scenarios

Message Flow Error Cases and Scenarios

Reception of SIP error messages CCF Connection Failure No Reply from CCF Duplicate Detection CCF Detected Failure

112/04/08 28Session Establishment-Mobile Origination

112/04/08 29

UE P-CSCF S-CSCF CCF (visited)

Visited Network

CCF (home)

Home Network

I-CSCF

1. INVITE

Cx Query with the HSS

2. Accounting Request [Event]

3. Accounting Answer

Create I-CSCF CDR

Service Control

1. INVITE

1. INVITE 1. INVITE

4. 200 OK

4. 200 OK

5. Accounting Request [Start]


Open P-CSCF CDR

4. 200 OK



Open S-CSCF CDR

4. 200 OK

SIP Session established

More SIP signalling

More SIP signalling

Session Establishment - Termination

112/04/08 30

1. INVITE/ UPDATE


Visited Network

CCF (home)

Home Network

Service Control

2. 200 OK (Invite/Update)

3. Accounting Request [Interim]


Update the S-CSCF CDR


5. Accounting Request [Interim]


Update the P-CSCF CDR


1. INVITE/ UPDATE

Service Control

1. INVITE/ UPDATE

SIP Session continues

SIP Session ongoing

More SIP signalling

Media Modification

112/04/08 31


Visited Network

CCF (home)

Home Network

1. BYE

Service Control

6. 200 OK 6. 200 OK

6. 200 OK

1. BYE 1. BYE

2. Accounting Request [Stop]


Close the P-CSCF CDR



Close the S-CSCF CDR

Session Release

112/04/08 32

UE P-SCSF S-CSCF CCF (visited)

Visited Network

CCF (home)

Home Network



Close the P-CSCF CDR Close the S-CSCF CDR

SIP Session ongoing

1. Abort Session Request

2. Abort Session Answer

3. BYE

3. BYE 3. BYE

8. 200 OK

9. 200 OK

10. 200 OK



CCF Initiated Session Release

112/04/08 33

S-CSCF CCF



AS (Voice Mail)

Voice mail service invoked.

Open an AS CDR

2. 200 OK (Invite)

Voice mail session (playing announcements, etc.)… When voice mail ends, tearing down session

SIP signalling

5. BYE


Close the AS CDR


1. Invite

AS as Mail Server

112/04/08 34

On-line charging

Basic principles Basic operation Charging scenarios

112/04/08 35

Online Charging(1/3) Based on charging event creation Immediate Event Charging (IEC)

Accounting-Record-Type EVENT_RECORD Successful case and Scenarios


Reception of SIP error messages Debit Units Operation Failure Duplicate Detection

112/04/08 36

AS / MRFC ECF

2. ACR (EVENT_RECORD, RA, RSU)

5. ACA (EVENT_RECORD, GSU, [CI])

Debit Units Operation

1. Service Request

6. Service Delivery

4. Perform Event Charging Control 3. Timer Tx

112/04/08 37

Online Charging(2/3) Event Charging with Unit Reservation

(ECUR) Accounting-Record-Type

START/INTERIM/STOP_RECORD Successful case and Scenarios


Reception of SIP error messages Reserve Units and Debit Units Operation Failure Duplicate Detection

112/04/08 38

ECF AS / MRFC

10. ACR (STOP_RECORD, Debit Units Req.)

12. ACA (STOP_RECORD, Debit Units Res.)

11. Perform Event Charging Control

Debit Units Operation

2. ACR (START_RECORD, Reserve Units Req.)


4. ACA (START_RECORD, Reserve Units Res.)

Reserve Units and Debit Units Operations

1. Service Request

5. Service Delivery

9. Service Delivery


8. ACA (INTERIM_RECORD, Debit units+Reserve units Req.)

6. ACR (INTERIM_RECORD, Debit units+Reserve units Req.)

Reserve Units Operation

112/04/08 39

Online Charging(3/3)

Support of Tariff Switch Using Acct-Interim-Interval AVP Using the Tariff Switch Time AVP

112/04/08 40

AS/MRFC ECF

Ta

riff

Sw

itch T

ime

r

1. ACR (START_Record, Reserve Units Req.)

2. ACA (START_Record, Reserve Units Res.)

3. Tariff Change

Un

it V

alu

e (

be

fore

T

ari

ff S

witc

h)

Un

it V

alu

e (

be

fore

T

ari

ff S

witc

h)

4. ACR (STOP_Record, Debit Units Req.)

5. ACA (STOP_Record, Debit Units Res.)

{Tariff Switch Time, Granted Service Unit}

{Used Service Unit (unit value, unit value after tariff switch), time of tariff change}

Gra

nte

d S

erv

ice

Unit (

Un

it V

alu

e)

112/04/08 41

Basic principles Unit determination ： refers to the calculation of

the number of non-monetary units (service units, data volume, time and events) that shall be assigned prior to starting service delivery.

Rating ： refers to the calculation of a price out of the non-monetary units calculated by the unit determination function.

Both can be implemented centralized, i.e. on the ECF, or decentralized, that is, on the AS/MRFC.

Two cases for online event charging can be distinguished: immediate event charging and event charging with unit reservation.

112/04/08 42

Basic principle (cont.) immediate event charging, granting units to

the AS/MRFC is performed in a single operation that also includes the deduction of the corresponding monetary units from the subscriber's account.

event charging with unit reservation includes also the process of requesting, reserving and possibly returning units. The deduction of the corresponding monetary units then occurs upon conclusion of the event charging transaction

112/04/08 43

Basic Operations "Debit Units Request"; sent from AS/MRFC ECF

After receiving a service request from the subscriber, the AS/MRFC sends a Debit Units Request to the ECF. The AS/MRFC may either specify a service identifier (centralised unit determination) or the number of units requested (decentralised unit determination)

"Debit Units Response"; sent from ECF AS/MRFC The ECF replies with a Debit Units Response, which informs the AS/MRFC of the number of units granted as a result of the Debit Units Request

"Reserve Units Request"; sent from AS/MRFC ECFRequest to reserve a number of units for the service to be provided by an AS/MRFC.

"Reserve Units Response"; sent from ECF AS/MRFC Response from the ECF which informs the AS/MRFC of the number of units that were reserved as a result of the "Reserve Units Request".

112/04/08 44

Immediate Event Charging

(1)Decentralized Unit Determination and Centralized Rating

(2)Centralized Unit Determination and Centralized Rating

(3)Decentralized Unit Determination and Decentralized Rating

112/04/08 45

9. Content/Service Delivery (cont.)

8. Credit Unit Control (cont.)

7. Content/Service Delivery

10. SIP Session released

1. SIP Session established

ECF (SCCF, CPCF)

AS/MRFC UE-A

6. Debit Units Response (Non-monetary Units)

3. Debit Units Request (Non-monetary Units)

5. Account Control

4. Rating Control

Credit Unit Control

2. Units Determination

(1)DC

112/04/08 46


8. Credit Service Control (cont.)




ECF (SCCF, CPCF)

AS/MRFC UE-A


2. Debit Units Request (Service Key)

5. Account Control

4. Rating Control

Credit Service Control


(2)CC

112/04/08 47


8. Credit Amount Control (cont.)




ECF (SCCF, CPCF)

AS/MRFC UE-A

6. Debit Units Response(Monetary Units)

4. Debit Units Request(Monetary Units)

5. Account Control

3. Rating Control

Credit Amount Control


(3)DD

112/04/08 48

Event charging with reservation unit

(1)Decentralized Unit Determination and Centralized Rating

(2)Centralized Unit Determination and Centralized Rating

(3)Decentralized Unit Determination and Decentralized Rating

112/04/08 49




ECF (SCCF, CPCF)

AS/MRFC

3. Reserve Units Request (Non-monetary Units)

7. Reserve Units Response (Non-monetary Units)

UE-A

5. Account Control



12. Account Control

4. Rating Control

6.Reservation Control

8. Reserved Units Supervision


11. Rating Control

(1)DC

112/04/08 50



ECF (SCCF, CPCF)

AS/MRFC UEa


2. Reserve Units Request (Service Key)



4. Rating Control

7. Reserve Units Response (Non-monetary Units)

5. Account Control

8. Granted Units Supervision

12. Account Control

6. Reservation Control


11. Rating Control

(2)CC

112/04/08 51



ECF (SCCF, CPCF)

AS/MRFC UEa


4. Reserve Units Request (Monetary Units)

10. Debit Units Request (Monetary Units)


3. Rating Control

7. Reserve Units Response (Monetary Units)

5. Account Control

8. Budget Control

11. Account Control

6. Reservation Control

12. Debit Units Response (Monetary Units)

(3)DD

112/04/08 52

Application Services (MMS) Specified in TS 32.235 Charging Principles

Usage of the MMS resources Storage duration Usage of the general Packet-Switched

domain resources Etc.

Charging scenarios

112/04/08 53

Charging scenarios

Originator and Recipient MMS Relay Server are the same

Originator and Recipient MMS Relay Server are not the same

MMBox management MMS VAS Application

112/04/08 54

Originator and Recipient MMS Relay Server are not the same

Originator MMS UA

Recipient MMS Relay/

Server Recipient MMS UA

MM1_submit.REQ

MM4_forward.REQ

MM1_notification. REQ

MM1_notification. RES

MM4_forward.RES

MM1_retrieve.REQ

MM1_retrieve.RES

MM1_acknowledge ment.REQ

MM4_read_reply_report.REQ

MM1_read_reply_ originator.REQ

MM1_submit.RES

Originator MMS Relay/

Server

MM4_delivery_report.REQ

MM1_delivery_ report.REQ MM1_read_reply_

recipient.REQ

MM4_read_reply_report.RES

A1

A2

A3

B1

B2

B3

B4

B5

B6 A4

MM4_delivery_report.RES B7

A5

B8

B9 A6

B10

A7

112/04/08 55

VASP

MM7_deliver. REQ

Originator MMS R/S

MM7_submit. REQ

3

MM7_submit. RES

MM7_delivery_report. REQ

MM7_replace. REQ

7 MM7_replace. RES

MM1_submit. REQ

2 MM7_deliver. RES

5

MM7_delivery_report. RES

MM71_submit. REQ

6 MM7_submit. RES

MM7_cancel. REQ

8 MM7_cancel. RES

MM1_notification. REQ

1

4

MMS VAS Application

3GPP Charging Principles

Documents

charging principles

charging scenariosmobile

content charging requests

event charging function

bearer charging function

charging documents structure32

charging gateway functions

gateway function cgf