3GPP Charging

08/05/09 1
Outline
 3G charging logical architecture
 Charging functions
 CS domain
 PS domain
 IM Subsystem
 Service domain (MMS service)

08/05/09 2
 Charging Documents
Structure

32.200
Charging Principles
(charging stage 2)

32.205 32.215 32.225 32.235

Stage 3 Stage 3 Reserved for Stage 3
CS- domain PS- domain Stage 3 IMS Service- domain
(R5) (R4: MMS service)

08/05/09 3
3G charging logical
architecture
 Create CDR
 HLR
 GMSC Server
 VMSC Server
 CGF
 SCF (not included in current spec.)
 MMS Relay Server

08/05/09 4
 Service Domain
MMS
Relay
Server

PSTN
Gi Gp
CS Domain PS Domain
Mc CDR
MGW
GGSN
gsm
GMSC
SSF CDR
Server
Gc
C CDR
CAP
HLR Ga
D Gr CGF CDR
Gn
Billing
CAP gsm CGF System
SCF
SCF
SCF
CDR

VMSC gsm
VMSC SSF
Server CAP Ga CDR
Server
gprs
McMc MGW
MGW SSF SGSN

Gb IuPS
A IuCS
08/05/09 5
 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).
08/05/09 6
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)
08/05/09 7
Offline IMS Charging
architecture for non-roaming
scenario

08/05/09 8
 Online IMS Charging
architecture
Home(A) + Visited(A) Home(B) + Visited(B)

Correlation Correlation
Session Function Bearer Bearer Function Session
S­CSCF ISC Rb Rb ISC S­CSCF
S­CSCF Charging Charging Charging Charging S­CSCF
Function Account Function Function Account Function

Re Re
Rating Rating
Function Rc Rc Function
Charging
Re information Re
flow

AS(s) Ro Ro AS(s)
AS(s)
AS(s) Event Event
Charging Charging
Function Function

MRFC Ro Ro MRFC
MRFC SCCF SCCF MRFC
CPCF CPCF

SGSN
SGSN
CAP CAP SGSN
SGSN

Online Charging System Online Charging System

08/05/09 9
 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
providers
 Service Information

08/05/09 10
 Charging scenarios
Mobile to Land (outgoing) call
Incoming call to a roaming subscriber
Delivery of a mobile terminated short
message
Incoming call handled by CAMEL without
redirection
Etc.
08/05/09 11
B

1
Mobile to land call
ISDN/PSTN
 MSC-A:MOC record
for subscriber “A”
1  GMSC:outgoing
gateway record
HPLMN

GMSC HLR

A Billing
MSC-A System

08/05/09 B
A
12
 Incoming call to a roaming
subscriber
A

ISDN/PSTN  GMSC:incoming
gateway record
 HLR interrogation
1
CDR
3
HPLMN
4
VPLMN
 GMSC:outgoing
gateway record
 GMSC:roaming
2
GMSC HLR GMSC record inculde IMSI
A
of “B”
A 4  MSC-B:MTC record
Billing Billing
MSC-B
for the call to “B”
System System
B A  TAP record
4

B
B

08/05/09 13
Delivery of a mobile
terminated short message
HPLMN  MSC:SMT record
SMS-SC  HLR:HLR interrogation
record
1  GMSC:SMS gateway MT
record
2
SMS-
GMSC HLR

3 A

A
Billing
MSC-B System

BB
08/05/09 14
 Incoming call handled by
CAMEL without redirection
A
1
 GSMC: Incoming gateway
record, Terminating CAMEL
ISDN/PSTN
 MSC:MTC record
 HLR:HLR interrogation
1
record

3 2
GMSC/
gsmSCF gsmSSF HLR
4
(2)Interrogate HLR, fetch the T-
5 CSI
(3.1)GMSC request gsmSSF to
A
MSC-B/
gsmSSF
Billing pass CAMEL service key to
System
gsmSCF to indicate which
6
service logic it should apply
(3.2)gsmSCF interrogate HLR
B
T-CSI(A-B)
for subscriber information
(4)GMSC interrogate the HLR
08/05/09 15
to get current location
Packet-Switched Domain
 Specified in TS 32.215
 Charging Principles
 Charging scenarios

08/05/09 16
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
08/05/09 17
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

08/05/09 18
 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.
08/05/09 19
Charging scenarios
 Mobile to PDN Context
 Mobile to Mobile Context
 PDN to Mobile Context
 Mobile to PDN Context while
roaming, GGSN in HPLMN

08/05/09 20
Mobile to PDN Context
1

PDN

A
GGSN
B
CGF BS
1
SGSN

HPLMN

08/05/09 21
Mobile to PDN Context while
roaming via BG
1

PDN

Inter PLMN Backbone

1 1

1 1
GGSN BG BG
SGSN
A
A
CGF CGF

B B
A
C
BS BS
HPLMN VPLMN
08/05/09 22
IMS Subsystem
 Specified in TS 32.225
 Off-line Charging
 On-line Charging

08/05/09 23
Introduction
 Offline Charging
 IMS network elements report
accounting information
 CCF construct and format CDRs
 Online Charging
 AS and MRFC report accounting
information
 ECF uses charging event to support
OCS
08/05/09 24
08/05/09 25
 Home(A) + Visited(A) Home(B) + Visited(B)

Correlation Correlation
Session Function Bearer Bearer Function Session
S­CSCF ISC Rb Rb ISC S­CSCF
S­CSCF
S­CSCF Charging Charging Charging Charging
Function Account Function Function Account Function

Re Re
Rating Rating
Function Rc Rc Function
Charging
Re information Re
flow

AS(s) Ro Ro AS(s)
AS(s)
AS(s) Event Event
Charging Charging
Function Function

MRFC Ro Ro MRFC
MRFC SCCF SCCF MRFC
CPCF CPCF

SGSN
SGSN
CAP CAP SGSN
SGSN

Online Charging System Online Charging System

08/05/09 26
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

08/05/09 27
08/05/09 Session Establishment-Mobile Origination 28
 Visited Network Home Network

UE P-CSCF CCF S-CSCF CCF I-CSCF

(visited) (home)

1. INVITE

Cx Query with the HSS

1. INVITE

2. Accounting Request [Event]

Create I-CSCF CDR

3. Accounting Answer
Service Control

1. INVITE
1. INVITE

More SIP signalling

4. 200 OK
4. 200 OK

5. Accounting Request [Start] 4. 200 OK

4. 200 OK
7. Accounting Request [Start]

Open P-CSCF CDR

Open S-CSCF CDR

6. Accounting Answer 8. Accounting Answer

More SIP signalling

SIP Session established

08/05/09 Session Establishment - Termination 29

 Visited Network Home Network

UE P-CSCF CCF S-CSCF CCF

(visited) (home)

SIP Session ongoing

1. INVITE/ 1. INVITE/
UPDATE UPDATE

Service Control

1. INVITE/
UPDATE

More SIP signalling

2. 200 OK (Invite/Update)

Service Control
2. 200 OK (Invite/Update)
2. 200 OK (Invite/Update)
3. Accounting Request [Interim]
5. Accounting Request [Interim]

Update the P-CSCF CDR Update the S-CSCF CDR

6. Accounting Answer 4. Accounting Answer

SIP Session continues

08/05/09 Media Modification 30

 Visited Network Home Network

UE P-CSCF CCF S-CSCF CCF

(visited) (home)

1. BYE
1. BYE

Service Control
2. Accounting Request [Stop]
1. BYE

Close the P-CSCF CDR

4. Accounting Request [Stop]

3. Accounting Answer

Close the S-CSCF CDR

5. Accounting Answer

6. 200 OK
6. 200 OK
6. 200 OK

08/05/09 Session Release 31

 Visited Network Home Network

UE P-SCSF CCF S-CSCF CCF

(visited) (home)

SIP Session ongoing

1. Abort Session Request

2. Abort Session Answer

3. BYE

3. BYE
3. BYE

4. Accounting Request [Stop] 6. Accounting Request [Stop]

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

5. Accounting Answer 7. Accounting Answer

8. 200 OK

9. 200 OK

10. 200 OK

08/05/09 CCF Initiated Session Release 32

 AS (Voice CCF
S-CSCF
Mail)

SIP signalling

1. Invite

Voice mail service invoked.

2. 200 OK (Invite)
3. Accounting Request [Start]

Open an AS CDR

4. Accounting Answer

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

5. BYE

6. Accounting Request [Stop]

Close the AS CDR

7. Accounting Answer

08/05/09 AS as Mail Server 33

 On-line charging
 Basic principles
 Basic operation
 Charging scenarios

08/05/09 34
Online Charging(1/3)
 Based on charging event creation
 Immediate Event Charging (IEC)
 Accounting-Record-Type EVENT_RECORD
 Successful case and Scenarios
 Message Flow
 Error Cases and Scenarios
 Reception of SIP error messages
 Debit Units Operation Failure
 Duplicate Detection

08/05/09 35
 AS / MRFC ECF

1. Service Request

Debit Units Operation

2. ACR (EVENT_RECORD, RA, RSU)

4. Perform Event
3. Timer Tx Charging Control

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

6. Service Delivery

08/05/09 36
Online Charging(2/3)
 Event Charging with Unit Reservation
(ECUR)
 Accounting-Record-Type
START/INTERIM/STOP_RECORD
 Successful case and Scenarios
 Message Flow
 Error Cases and Scenarios
 Reception of SIP error messages
 Reserve Units and Debit Units Operation

Failure
08/05/09 37
 Duplicate Detection
 AS / MRFC ECF

1. Service Request

Reserve Units Operation

2. ACR (START_RECORD, Reserve Units Req.)

3. Perform Event
Charging Control

4. ACA (START_RECORD, Reserve Units Res.)

5. Service Delivery

Reserve Units and Debit Units Operations

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

7. Perform Event Charging Control

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

9. Service Delivery

Debit Units Operation

10. ACR (STOP_RECORD, Debit Units Req.)

11. Perform Event Charging Control

12. ACA (STOP_RECORD, Debit Units Res.)

08/05/09 38
Online Charging(3/3)
 Support of Tariff Switch
 Using Acct-Interim-Interval AVP
 Using the Tariff Switch Time AVP

08/05/09 39
 AS/MRFC ECF

1. ACR (START_Record, Reserve Units Req.)

2. ACA (START_Record, Reserve Units Res.)

{Tariff Switch Time, Granted Service Unit}

Unit Value (before

Tariff Switch Timer

Tariff Switch)
Granted Service Unit (Unit Value)

3. Tariff Change
Unit Value (before
Tariff Switch)

4. ACR (STOP_Record, Debit Units Req.)

{Used Service Unit (unit value, unit value after tariff

switch), time of tariff change}
5. ACA (STOP_Record, Debit Units Res.)
08/05/09 40
 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.
08/05/09 41
 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
08/05/09 42
 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  ECF
Request 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
08/05/09 Units Request".
"Reserve 43
 Immediate Event Charging
(1)Decentralized Unit Determination and
Centralized Rating
(2)Centralized Unit Determination and
Centralized Rating
(3)Decentralized Unit Determination and
Decentralized Rating

08/05/09 44
 UE-A ECF AS/MRFC
(SCCF, CPCF)

1. SIP Session established

(1)D
C
Credit Unit Control
2. Units
Determination

3. Debit Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control
6. Debit Units Response (Non-monetary Units)

7. Content/Service Delivery

8. Credit Unit Control (cont.)

9. Content/Service Delivery (cont.)

10. SIP Session released

08/05/09 45
 UE-A ECF AS/MRFC
(SCCF, CPCF)

(2)CC 1. SIP Session established

Credit Service Control

2. Debit Units Request (Service Key)

3. Units
Determination

4. Rating
Control

5. Account
Control
6. Debit Units Response (Non-monetary Units)

7. Content/Service Delivery

8. Credit Service Control (cont.)

9. Content/Service Delivery (cont.)

10. SIP Session released

08/05/09 46
 UE-A ECF AS/MRFC
(SCCF, CPCF)

(3)DD 1. SIP Session established

Credit Amount Control

2. Units
Determination

3. Rating
Control

4. Debit Units Request(Monetary Units)

5. Account
Control
6. Debit Units Response(Monetary Units)

7. Content/Service Delivery

8. Credit Amount Control (cont.)

9. Content/Service Delivery (cont.)

10. SIP Session released

08/05/09 47
 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

08/05/09 48
 UE-A ECF AS/MRFC
(SCCF, CPCF)

(1)DC 1. SIP Session established

2. Units
Determination

3. Reserve Units Request (Non-monetary Units)

4. Rating
Control

5. Account
Control

6.Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Reserved Units
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control

13. Debit Units Response (Non-monetary Units)

14. SIP Session released

08/05/09 49
 UEa ECF AS/MRFC
(SCCF, CPCF)

(2)CC 1. SIP Session established

2. Reserve Units Request (Service Key)

3. Units
Determination

4. Rating Control

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Non-monetary Units)

8. Granted Unit
Supervision

9. Content/Service Delivery

10. Debit Units Request (Non-monetary Units)

11. Rating
Control

12. Account
Control
13. Debit Units Response (Non-monetary Units)

14. SIP Session released

08/05/09 50
 UEa ECF AS/MRFC
(SCCF, CPCF)
(3)DD
1. SIP Session established

2. Units
Determination

3. Rating Control

4. Reserve Units Request (Monetary Units)

5. Account
Control

6. Reservation
Control
7. Reserve Units Response (Monetary Units)

8. Budget
Control

9. Content/Service Delivery

10. Debit Units Request (Monetary Units)

11. Account
Control

12. Debit Units Response (Monetary Units)

13. SIP Session released

08/05/09 51
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

08/05/09 52
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

08/05/09 53
Originator and Recipient MMS Relay Server are not the same
Originator Recipient
Originator Recipient
MMS Relay/ MMS Relay/
MMS UA MMS UA
Server Server
MM1_submit.REQ

MM1_submit.RES
A1

MM4_forward.REQ
A2 B1
MM4_forward.RES
A3
MM1_notification.
REQ
B2

MM1_notification.
RES
B3

MM1_retrieve.REQ

MM1_retrieve.RES
B4

MM1_acknowledge
B5 ment.REQ

MM4_delivery_report.REQ
A4 B6

MM4_delivery_report.RES
B7
MM1_delivery_ MM1_read_reply_
report.REQ A5
recipient.REQ
B8

MM4_read_reply_report.REQ
A6 B9

MM4_read_reply_report.RES
MM1_read_reply_ B10
originator.REQ
08/05/09 A7
54
MMS VAS Application
VASP Originator
MMS R/S
MM1_submit. REQ
MM7_deliver. REQ
1
MM7_deliver. RES
2

MM7_submit. REQ

MM7_submit. RES
3

MM1_notification. REQ

MM7_delivery_report. REQ
4
MM7_delivery_report. RES
5

MM71_submit. REQ

MM7_submit. RES 6

MM7_replace. REQ

MM7_replace. RES 7

MM7_cancel. REQ

MM7_cancel. RES 8

08/05/09 55