3GPP Charging Documents Structure and Principles | CDR Creation, Function Overview

1. 3GPP Charging

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

3. Charging Documents Structure

4. 3G charging logical architecture • Create CDR • HLR • GMSC Server • VMSC Server • CGF • SCF (not included in current spec.) • MMS Relay Server

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

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)

8. Offline IMS Charging architecture for non-roaming scenario

9. Online IMS Charging architecture

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 providers • Service Information

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

12. MSC-A:MOC record for subscriber “A” GMSC:outgoing gateway record Mobile to land call

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

14. Delivery of a mobile terminated short message • MSC:SMT record • HLR:HLR interrogation record • GMSC:SMS gateway MT record

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

16. Packet-Switched Domain • Specified in TS 32.215 • Charging Principles • Charging scenarios

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

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

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.

20. Charging scenarios • Mobile to PDN Context • Mobile to Mobile Context • PDN to Mobile Context • Mobile to PDN Context while roaming, GGSN in HPLMN

21. Mobile to PDN Context

22. Mobile to PDN Context while roaming via BG

23. IMS Subsystem • Specified in TS 32.225 • Off-line Charging • On-line Charging

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

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

28. Session Establishment-Mobile Origination

29. Session Establishment - Termination

30. Media Modification

31. Session Release

32. CCF Initiated Session Release

33. AS as Mail Server

34. On-line charging Basic principles Basic operation Charging scenarios

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

37. 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 • Duplicate Detection

39. Online Charging(3/3) • Support of Tariff Switch • Using Acct-Interim-Interval AVP • Using the Tariff Switch Time AVP

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.

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

43. Basic Operations • "Debit Units Request"; sent from AS/MRFC  ECFAfter 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".

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

45. (1)DC

46. (2)CC

47. (3)DD

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

49. (1)DC

50. (2)CC