3GPP TS V9.8.0 ( )

Transcription

1 TS V9.8.0 ( ) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Diameter charging applications (Release 9) The present document has been developed within the 3 rd Generation Partnership Project ( TM ) and may be further elaborated for the purposes of. The present document has not been subject to any approval process by the Organizational Partners and shall not be implemented. This Specification is provided for future development work within only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the TM system should be obtained via the Organizational Partners' Publications Offices.

2 2 TS V9.8.0 ( ) Keywords UMTS, charging, management, protocol, GPRS, IP, multimedia, MMS Postal address support office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: Fax: Internet Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. 2011, Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members is a Trade Mark of ETSI registered for the benefit of its Members and of the Organizational Partners LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association

3 3 TS V9.8.0 ( ) Contents Foreword Scope References Definitions, symbols and abbreviations Definitions Symbols Abbreviations Architecture Considerations High level architecture Charging related transfer requirements charging applications requirements Offline Charging Scenarios Basic Principles Event based charging Session based charging Basic Operation Online Charging scenarios Basic principles Charging Scenarios Immediate Event Charging Decentralized Unit Determination and Centralized Rating Centralized Unit Determination and Centralized Rating Decentralized Unit Determination and Decentralized Rating Furter Options Event charging with Reservation Decentralized Unit Determination and Centralized Rating Centralized Unit Determination and Centralized Rating Decentralized Unit Determination and Decentralized Rating Session charging with Reservation Decentralized Unit Determination and Centralized Rating Centralized Unit Determination and Centralized Rating Decentralized Unit Determination and Decentralized Rating Basic Operations Other requirements Re-authorization Threshold based re-authorization triggers Termination action Account Expiration Charging Applications Protocol Aspects Basic Principles for Diameter Offline Charging Event based charging Session based charging Offline charging error cases - Diameter procedures CDF Connection Failure No Reply from CDF Duplicate Detection CDF Detected Failure Message Contents for Offline Charging Summary of Offline Charging Message Formats General Structure for the Accounting Message Formats Accounting-Request Message Accounting-Answer Message... 51

4 4 TS V9.8.0 ( ) 6.3 Basic Principles for Diameter Online charging Online Specific Credit Control Application Requirements Diameter Description on the Ro reference point Basic Principles Immediate Event Charging (IEC) Event Charging with Unit Reservation (ECUR) Session Charging with Unit Reservation (SCUR) Error Cases and Scenarios Duplicate Detection Reserve Units and Debit Units Operation Failure Support of Tariff Changes during an Active User Session Support of Tariff Changes using the Tariff Switch Mechanism Support of Tariff Changes using Validity Time AVP Support of Re-authorisation Support of Failure Handling Support of Failover Credit Pooling Message formats for Online Charging Summary of Online Charging Message Formats General Structure for the Credit Control Message Formats Credit-Control-Request Message Credit-Control-Answer Message Re-Auth-Request Message Re-Auth-Answer Message Capabilities-Exchange-Request Message Capabilities-Exchange-Answer Message Device-Watchdog-Request Message Device-Watchdog-Answer Message Disconnect-Peer-Request Message Disconnect-Peer-Answer Message Abort-Session-Request Message Abort-Session -Answer Message Other procedural description of the charging applications Re-authorization Idle timeout Change of charging conditions Reporting quota usage Quota consumption Threshold based re-authorization triggers Termination action Quota consumption time Service Termination Envelope reporting Combinational quota Online control of offline charging information Bindings of the operation to protocol application Bindings of Charging Data Transfer to Accounting Bindings of Debit / Reserve Units to Credit-Control Summary of used Attribute Value Pairs Diameter AVPs Accounting-Input-Octets Accounting-Input-Packets Accounting-Output-Octets Accounting-Ouput-Packets Acct-Application-Id AVP Auth-Application-Id AVP Called-Station-Id Event-Timestamp AVP Multiple-Services-Credit-Control Rating-Group AVP... 81

5 5 TS V9.8.0 ( ) Result-Code AVP Service-Context-Id AVP Service-Identifier AVP Used-Service-Unit AVP User-Name AVP Vendor-Id AVP specific AVPs Access-Network-Information AVP Account-Expiration AVP Accumulated-Cost AVP Adaptations AVP Additional-Content-Information AVP Additional-Type-Information AVP Address-Data AVP Address-Domain AVP Address-Type AVP Addressee-Type AVP AF-Correlation-Information AVP Alternate-Charged-Party-Address AVP AoC-Cost-Information AVP AoC-Format AVP AoC-Information AVP AoC-Request-Type AVP AoC-Service AVP AoC-Service-Obligatory-Type AVP AoC-Service-Type AVP AoC-Subscription-Information AVP Applic-ID AVP Application-provided-Called-Party-Address AVP Application-Server AVP Application-Server-Information AVP Associated-Party-Address AVP Associated-URI AVP Authorised-QoS AVP Aux-Applic-Info AVP Base-Time-Interval AVP Bearer-Service AVP Called-Asserted-Identity AVP Called-Party-Address AVP Calling-Party-Address AVP Carrier-Select-Routing-Information AVP Cause-Code AVP CG-Address AVP Change-Condition AVP Change-Time AVP Charged-Party AVP A Charging-Characteristics-Selection-Mode AVP Class-Identifier AVP Client-Address Content-Class AVP Content-Disposition AVP Content-Length AVP Content-Size AVP Content-Type AVP A CSG-Access-Mode AVP B CSG-Membership-Indication AVP Current-Tariff AVP CUG-Information Data-Coding-Scheme AVP DCD-Information AVP Deferred-Location-Event-Type AVP Delivery-Report-Requested AVP

6 6 TS V9.8.0 ( ) Destination-Interface AVP Diagnostics AVP Domain-Name AVP DRM-Content AVP Dynamic-Address-Flag AVP Early-Media-Description AVP Envelope AVP Envelope-End-Time AVP Envelope-Reporting AVP Envelope-Start-Time AVP Event AVP Event-Charging-TimeStamp AVP Event-Type AVP Expires AVP File-Repair-Supported AVP GGSN-Address AVP IM-Information AVP Incremental-Cost AVP Interface-Id AVP Interface-Port AVP Interface-Text AVP Interface-Type AVP IMS-Charging-Identifier AVP IMS-Communication-Service-Identifier AVP IMS-Information AVP IMSI-Unauthenticated-Flag AVP Incoming-Trunk-Group-ID AVP Inter-Operator-Identifier AVP LCS-APN AVP LCS-Client-Dialed-By-MS AVP LCS-Client-External-ID AVP LCS-Client-ID AVP LCS-Client-Name AVP LCS-Client-Type AVP LCS-Data-Coding-Scheme AVP LCS-Format-Indicator AVP LCS-Information AVP LCS-Name-String AVP LCS-Requestor-ID AVP LCS-Requestor-ID-String AVP Local-Sequence-Number AVP Location-Estimate AVP Location-Estimate-Type AVP Location-Type AVP Low-Balance-Indication AVP MBMS GW-Address AVP MBMS-Information AVP MBMS-User-Service-Type AVP Media-Initiator-Flag AVP Media-Initiator-Party AVP Message-Body AVP Message-Class AVP Message-ID AVP Message-Size AVP Message-Type AVP MM-Content-Type AVP MMBox-Storage-Requested AVP MMS-Information AVP MMTel-Information AVP Next-Tariff AVP Node-Functionality AVP Node-Id AVP

7 7 TS V9.8.0 ( ) Number-Of-Diversions AVP Number-Of-Messages-Sent AVP Number-Of-Participants AVP Number-Of-Received-Talk-Bursts AVP Number-Of-Talk-Bursts AVP Number-Portability-Routing-Information AVP Offline-Charging AVP Online-Charging-Flag AVP Originating-IOI AVP Originator AVP Originator-Address AVP Originator-Interface AVP Originator-Received-Address AVP Originator-SCCP-Address A Outgoing-Session-Id AVP Outgoing-Trunk-Group-ID AVP Participants-Involved AVP Participant-Group AVP Participant-Access-Priority AVP Participant-Action-Type AVP PDG-Address AVP PDG-Charging-Id AVP PDN-Connection-ID AVP PDP-Address AVP PDP-Context-Type AVP PoC-Change-Condition AVP PoC-Change-Time AVP PoC-Controlling-Address AVP PoC-Event-Type AVP PoC-Group-Name AVP PoC-Information AVP PoC-Server-Role AVP PoC-Session-Id AVP PoC-Session-Initiation-Type AVP PoC-Session-Type AVP PoC-User-Role AVP PoC-User-Role-IDs AVP PoC-User-Role-info-Units AVP Positioning-Data AVP Preferred-AoC-Currency AVP Priority AVP PS-Append-Free-Format-Data AVP PS-Free-Format-Data AVP PS-Furnish-Charging-Information AVP PS-Information AVP Quota-Consumption-Time AVP Quota-Holding-Time AVP Read-Reply-Report-Requested AVP Reason-Code AVP Real-Time-Tariff-Information AVP Received-Talk-Burst-Time AVP Received-Talk-Burst-Volume AVP Recipient-Address AVP Recipient-Info AVP Recipient-Received-Address AVP Recipient-SCCP-Address Refund-Information AVP Remaining-Balance AVP Reply-Applic-ID AVP Reply-Path-Requested AVP Reporting-Reason AVP Requested-Party-Address AVP

8 8 TS V9.8.0 ( ) Role-Of-Node AVP Scale-Factor AVP SDP-Answer-Timestamp AVP SDP-Media-Component AVP SDP-Media-Description AVP SDP-Media-Name AVP SDP-Offer-Timestamp AVP SDP-Session-Description AVP SDP-TimeStamps AVP SDP-Type AVP Served-Party-IP-Address AVP Void Service-Data-Container AVP Service-ID AVP Service-Generic-Information AVP Service-Information AVP Service-Mode AVP Service-Specific-Data AVP Service-Specific-Info AVP Service-Specific-Type AVP Service-Type AVP Serving-Node-Type AVP SGSN-Address AVP SGW-Change AVP SIP-Method AVP SIP-Request-Timestamp AVP SIP-Request-Timestamp-Fraction AVP SIP-Response-Timestamp AVP SIP-Response-Timestamp-Fraction AVP SM-Discharge-Time AVP SM-Message-Type AVP SM-Protocol-Id AVP SM-Status AVP SM-User-Data-Header AVP SMS-Information AVP SMS-Node AVP SM-Service-Type AVP SMSC-Address AVP Start-Time AVP Stop-Time AVP Submission-Time AVP Subscriber-Role AVP Supplementary-Service AVP Talk-Burst-Exchange AVP Talk-Burst-Time AVP Talk-Burst-Volume AVP Tariff-Information AVP Tariff-XML AVP Terminating-IOI AVP Time-First-Usage AVP Time-Last-Usage AVP Time-Quota-Mechanism Time-Quota-Threshold AVP Time-Quota-Type AVP Time-Stamps AVP Time-Usage AVP Traffic-Data-Volumes AVP Token-Text AVP Trigger AVP Trigger-Type AVP Trunk-Group-ID AVP Type-Number AVP

9 9 TS V9.8.0 ( ) Unit-Cost AVP Unit-Quota-Threshold AVP A User-CSG-Information AVP User-Participating-Type AVP User-Session-Id AVP Volume-Quota-Threshold AVP WAG-Address AVP WAG-PLMN-Id AVP WLAN-Information AVP WLAN-Radio-Container AVP WLAN-Session-Id AVP WLAN-Technology AVP WLAN-UE-Local-IPAddress AVP Accesses specific AVPs Annex A (informative): Bibliography Annex B (informative): Change history

10 10 TS V9.8.0 ( ) Foreword This Technical Specification has been produced by the 3 rd Generation Partnership Project (). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

11 11 TS V9.8.0 ( ) 1 Scope The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network-charging architecture and principles are specified in TS [1], which provides an umbrella for other charging management documents that specify. The content of the CDRs' per domain and subsystem (offline charging); The content of real-time charging messages per domain / subsystem (online charging); The functionality of online and offline charging for those domains and subsystems; The interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events). The complete document structure for these TSs is defined in TS [1]. The present document specifies in detail the Diameter based offline and online charging applications for networks. It includes all charging parameters, scenarios and message flows.. All terms, definitions and, abbreviations used in the present document, that are common across TSs, are defined in TR [100]. Those that are common across charging management in GSM/UMTS domains, services or subsystems are provided in the umbrella document TS [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document. Furthermore, requirements that govern the charging work are specified in TS [101]. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] TS : "Telecommunication management; Charging management; Charging Architecture and Principles". [2]-[99] Void. [100] TR : Vocabulary for Specifications [101] TS : "Service aspects; Charging and billing". [102]-[199] Void. [200] TS : "End to end quality of service concept and architecture". [201] TS : "IP Multimedia Subsystem (IMS); Stage 2". [202] TS : "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3." [203] TS : "Policy control over Go interface". [204] TS : "Cx and Dx Interfaces based on the Diameter protocol; Protocol Details".

12 12 TS V9.8.0 ( ) [205] Void. [206] TS : " specific codes and identifiers". [207] TS : "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". [208] TS : " Multimedia Messaging Service (MMS); Functional description; Stage 2". [209] OMA "Multimedia Messaging Service; Encapsulation Protocol". [210] OMNA WSP Content Type Numbers [211] OMA-CP-POC: "OMA PoC Control Plane" [212] : " system to Wireless Local Area Network (WLAN) interworking; Stage 3". [213] TS : "MM10 interface based on Diameter protocol; Stage 3". [214] TS : "Policy and Charging Control over Rx reference point; Stage 3". [215] TS : "Policy and Charging Control over Gx reference point". [216] TS : "Technical realization of Short Message Service (SMS)". [217] TS : "Value Added Services (VAS) for Short Message Service (SMS) requirements". [218] TS : "Policy and Charging control architecture". [219] TS : " Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol. [220] TS : "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". [221] TS : "Sh Interface based on the Diameter protocol;protocol details". [222] TS : "SIP Transfer of IP Multimedia Service Tariff Information". [223] OMA-DDS-Charging_Data: "Charging Data". [224] TS : "Numbering, Addressing and Identification". [225] TS : "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". [226] TS : "Evolved GPRS Tunnelling Protocol for Control Plane (GTPv2-C); Stage 3". [227] TS : "Universal Geographical Area Description (GAD)". [228] - [400] Void. [401] IETF RFC 3588: "Diameter Base Protocol". [402] IETF RFC 4006: "Diameter Credit Control Application" [403] IETF RFC 5580: "Carrying Location Objects in RADIUS" [404] IETF RFC 3455, "Private Extensions to the Session Initiation Protocol (SIP) for the 3 rd Generation Partnership Projects ()". [405] IETF RFC 3261: "SIP: Session Initiation Protocol". [406] IETF RFC 4566: "SDP: Session Description Protocol". [407] IETF RFC 4005: "Diameter Network Access Server Application".

13 13 TS V9.8.0 ( ) [408] IETF RFC 3264: An Offer/Answer Model with the Session Description Protocol (SDP). NOTE: The above reference will need to be updated to reference the assigned RFC number, once the draft achieves RFC status within the IETF.

14 14 TS V9.8.0 ( ) 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: middle tier (charging) TS: term used for the charging TSs that specify the domain / subsystem / service specific, online and offline, charging functionality. These are all the TSs in the numbering range from TS to TS , e.g. TS [10] for the CS domain, or TS [30] for the MMS service. Currently, there is only one "tier 1" TS in, which is the TS that specifies the charging architecture and principles. Finally, there are a number of top tier TSs in the 32.29x numbering range ([50] ff) that specify common charging aspects such as parameter definitions, encoding rules, the common billing domain interface or common charging applications. offline charging: charging mechanism where charging information does not affect, in real-time, the service rendered online charging: charging mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with session/service control is required 3.2 Symbols For the purposes of the present document, the following symbols apply: Rf Ro 3.3 Abbreviations Offline Charging Reference Point between a 3G network element and the CDF. Online Charging Reference Point between a 3G network element and the OCS. For the purposes of the present document, the following abbreviations apply: ACA ACR AoC AS ASA ASR AVP CCA CCR CDF CDR CEA CER CGI CI CSG CSG ID DBPA DCD DPA DPR DRM DWA DWR ECGI ECUR FQDN FUI ACcounting Answer ACcounting Request Advice of Charge Application Server Abort Session Answer Abort Session Request Attribute Value Pair Credit Control Answer Credit Control Request Charging Data Function Charging Data Record Capabilities Exchange Answer Capabilities Exchange Request Cell Global Identification Cost-Information Closed Subscriber Group Closed Subscriber Group Identity Diameter Base Protocol Accounting Dynamic Content Delivery Disconnect Peer Answer Disconnect Peer Request Digital Rights Management Device Watchdog Answer Device Watchdog Request E-UTRAN Cell Global Identifier Event Charging with Unit Reservation Fully Qualified Domain Name Final-Unit-Indication

15 15 TS V9.8.0 ( ) HSGW GSU IEC IM IMS MSCC OCS RAA RAI RAR SAI SDP TAI HRPD Serving GateWay Granted-Service-Unit Immediate Event Charging Instant Messaging IP Multimedia Subsystem Multiple Services Credit Control Online Charging System Re-Auth Answer Routeing Area Identity Re-Auth Request Service Area Identifier Session Description Protocol Tracking Area Identity 4 Architecture Considerations 4.1 High level architecture The Rf and the Ro are reference points from the Charging Trigger Function (CTF) to the Charging Data Function (CDF) and the Online Charging Function (OCF) respectively, and are intended for the transport of charging events. Rf is used for offline charging whereas Ro is used for online charging. The following figures depict the position of the Rf and Ro reference points within the overall online and offline charging architecture. network CN Domain Rf Service nodes Subsystem C T F C C Rf Ga Bx D G F F Rf Billing Domain CTF: CDF: CGF: BD: Charging Trigger Function Charging Data Function Charging Gateway Function Billing Domain. This may also be a billing mediation device / post-processing system. Figure 4.1.1: Logical ubiquitous offline charging architecture

16 16 TS V9.8.0 ( ) network CN Domain Ro Service nodes Subsystem C T F Ro O Ga C Bo C G F F Ro Billing Domain CTF: OCF: CGF: BD: Charging Trigger Function Online Charging Function Charging Gateway Function Billing Domain. This may also be a billing mediation device / post-processing system. Figure 4.1.2: Logical ubiquitous online charging architecture Different mappings of the ubiquitous offline charging functions, CTF, CDF and CGF, onto physical implementations are possible. Further details of the configuration refer tots [1]. Details of the implementation options per domain / subsystem / service (usually a subset of the overall possible variants described above) are specified in the respective middle tier TS Charging related transfer requirements Each CTF would have CDF and OCF address list to which it can send its charging events and/or charging requests. The list will be organized in address priority order. If the primary charging function is not available (e.g., out of service) then the CTF shall send the charging information to the secondary charging function and so on. Within the scope of this release, each network element that generates charging information will send the information only to the charging entities of the same PLMN, and not to charging entities in other PLMNs. Each CDF in the PLMN may know of other CDFs' network addresses (e.g., for redundancy reasons, to be able to recommend another CDF address with the Redirection Request message). This is achieved by OAM&P configuration facilities that will enable each CDF to have a configurable list of peer CDF addresses.

17 17 TS V9.8.0 ( ) 5 charging applications requirements 5.1 Offline Charging Scenarios Basic Principles Offline charging for both events and sessions between CTF and the CDF is performed using the Rf reference point as defined in TS [1]. Two basic scenarios are used: Event based Charging; Session based Charging.

18 18 TS V9.8.0 ( ) Event based charging In the following scenario, CTF asks the CDF to store event related charging data. UE-A CDF CTF 1. Request for resource usage 2. Content/Service Delivery 3. Charging Data Generation Event Based Charging 4.Charging Data Request (Event Related Charging Data) 5. Process Request 6.Charging Data Response Figure : 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.

19 19 TS V9.8.0 ( ) Session based charging In the following scenario, CTF asks the CDF to store session related charging data. UE-A CDF CTF 1. Request for resource usage 2. Session Ongoing 3.Charging Data Generation Session Based Charging 4.Charging Data Request (Session Related Charging Data) 5. Process Request 6.Charging Data Response 7.Charging Data Generation 8.Charging Data Request (Session Related Charging Data) 9. Process Request 10.Charging Data Response 8. Credit Unit Control (cont.) 11. Session released 12.Charging Data Generation 13.Charging Data Request (Session Related Charging Data) 14. Process Request 15.Charging Data Response Figure : 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

20 20 TS V9.8.0 ( ) 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.

21 21 TS V9.8.0 ( ) 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 and table describe the content of these operations. Table : Charging Data Request Content Charging Data Request 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 O M The field corresponds to the unique operation identification. User Name O C The field contains the identification of the service user. Operation Interval O C O C Origination State Origination Timestamp O C This field contains the time when the operation is requested. Proxy Information O C This field contains the parameter of the proxy. Route Information O C This field contains the parameter of the route. Operation Token O M This field identifies the domain, subsystem or service and release. Service information O M This parameter holds the individual service specific parameters as defined in the corresponding middle tier TS. Table : Charging Data Response Content Charging Data Response 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 O M The field corresponds to the unique operation identification. Operation Interval O C Error Reporting Host O C 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 O C Origination Timestamp O C This field contains the time when the operation is requested. Proxy Information O C This field contains the parameter of the proxy.

22 22 TS V9.8.0 ( ) 5.2 Online Charging scenarios Online charging for both events and sessions between CTF and the OCF is performed using the Ro reference point. The Ro reference point supports integrity protection and authentication for the case that the CTF is outside the operator domain Basic principles There are two sub-functions for online charging that affect online charging principles and require a more detailed description: rating and unit determination. Both rating and unit determination can be implemented centralized, i.e. on the OCF, or decentralized, that is, on the CTF. 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. With Centralized Unit Determination, the OCF determines the number of non-monetary units that a certain service user can consume based on a service identifier received from the CTF. With the Decentralized Unit Determination approach, the CTF determines itself how many units are required to start service delivery, and requests these units from the OCF. After checking the service user's account balance, the OCF returns the number of granted units to the CTF. The CTF is then responsible for the supervision of service delivery. Particularly, the CTF shall limit service delivery to the corresponding number of granted units. Rating refers to the calculation of a price out of the non-monetary units calculated by the unit determination function. With the Centralized Rating approach, the CTF and the OCF exchange information about non-monetary units. The OCF translates these units into monetary units. With the Decentralized Rating approach, the corresponding rating control is performed within the CTF. Consequently, CTF and OCF exchange information about monetary units. Three cases for online charging can be distinguished: immediate event charging (IEC), event charging with unit reservation (ECUR) and session charging with unit reservation (SCUR). These cases are further described in TS [1].

23 23 TS V9.8.0 ( ) Charging Scenarios In order to perform event charging via Ro, the scenarios between the involved entities UE-A, OCF and CTF need to be defined. The charging flows shown in this subclause include scenarios with immediate event charging and event charging with reservation. In particular, the following cases are shown: 1 Immediate Event Charging a) Decentralized Unit Determination and Centralized Rating b) Centralized Unit Determination and Centralized Rating c) Decentralized Unit Determination and Decentralized Rating 2 Event charging with Reservation a) Decentralized Unit Determination and Centralized Rating b) Centralized Unit Determination and Centralized Rating c) Decentralized Unit Determination and Decentralized Rating 3 Session charging with Reservation a) Decentralized Unit Determination and Centralized Rating b) Centralized Unit Determination and Centralized Rating c) Decentralized Unit Determination and Decentralized Rating The combination of Centralized Unit Determination with Decentralized Rating is not possible Immediate Event Charging

24 24 TS V9.8.0 ( ) Decentralized Unit Determination and Centralized Rating In the following scenario, CTF asks the OCF to assign a defined number of units. UE-A OCF CTF 1. Request for resource usage 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.) 10. Session released Figure : Immediate Event Charging with Centralized Rating and Decentralized Unit Determination 1. Request for resource usage: UE-A requests the desired resource from the network element. 2. Units Determination: depending on the requested service the CTF determines the number of units accordingly. 3. Debit Units Request: the CTF requests the OCF to assign the defined number of units. 4. Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represents the price for the number of units determined in item Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the calculated amount from the subscriber's account. 6. Debit Units Response: the OCF informs the CTF of the number of granted units. 7. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the number of granted units. 8. Credit Unit Control (cont.): this function block is optional and a replication of items 2 to Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the occurrence of item Session released: Session is released.

25 25 TS V9.8.0 ( ) Centralized Unit Determination and Centralized Rating In the following scenario, CTF asks the OCF to assign units based on the service identifier specified by the CTF. UE-A OCF CTF 1. Request for resource usage 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. Session released Figure : Immediate Event Charging with Centralized Rating and Centralized Unit Determination 1. Request for resource usage: The UE-A requests the desired resource or content from the network element. 2. Debit Units Request: depending on the service requested by the UE-A, the CTF selects the service identifier and forwards the Debit Units Request to the OCF. 3. Units Determination: the OCF determines the number of non-monetary units needed for the content/service delivery, based on the received service key. 4. Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represent the price for the number of units determined in item Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the calculated amount from the subscriber's account. 6. Debit Units Response: the OCF informs the CTF of the number of granted units. This includes the case where the number of units granted indicates the permission to render the service that was identified by the received service key. 7. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the number of granted units. 8. Credit Service Control (cont.): this function block is optional and a replication of items 2 to 6.

26 26 TS V9.8.0 ( ) 9. Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the occurrence of item Session released: the session is released.

27 27 TS V9.8.0 ( ) Decentralized Unit Determination and Decentralized Rating In the following scenario, the CTF asks the OCF to assure the deduction of an amount of the specified number of monetary units from the subscriber's account. UE-A OCF CTF 1. Request for resource usage Credit Amount Control 2. Units Determination 4. Debit Units Request(Monetary Units) 3. Rating Control 5. Account Control 6. Debit Units Response(Monetary Units) 7. Content/Service Delivery 8. Credit Amount Control (cont.) 9. Content/Service Delivery (cont.) 10. Session released Figure : Immediate Event Charging with Decentralized Rating and Decentralized Unit Determination 1. Request for resource usage: The UE-A requests the desired content from the network element. 2. Units Determination: depending on the service requested by the UE-A, the CTF determines the number of units accordingly. 3. Rating Control: the CTF calculates the number of monetary units that represent the price for the number of units determined in item Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the calculated number of monetary units from the subscriber's account. 5. Account Control: provided that the user's credit balance is sufficient, the OCF triggers the deduction of the calculated amount from the subscriber's account. 6. Debit Units Response: the OCF indicates to the CTF the number of deducted monetary units. 7. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the number of units as specified in items 2 and Credit Amount Control (cont.): this function block is optional and a replication of items 2 to Content/Service Delivery (cont.): the continuation of content delivery occurs in correspondence with the occurrence of item Session released: the session is released.

28 28 TS V9.8.0 ( ) Furter Options In addition to the flows that are specified in the previous subclauses, the Debit Unit operation may alternatively be carried out concurrently with service delivery, or after completion of service delivery.

29 29 TS V9.8.0 ( ) Event charging with Reservation Decentralized Unit Determination and Centralized Rating In the following scenario, the CTF requests the reservation of units prior to service delivery. An account debit operation is carried out following the conclusion of service delivery. UE-A OCF CTF 1. Request for resource usage 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. Session released Figure : Event Charging with Reservation / Decentralized Unit Determination and Centralized Rating 1. Request for resource usage: The UE-A requests the desired content/service from the NE. 2. Units Determination: depending on the requested service the CTF determines the number of units accordingly. 3. Reserve Units Request: the CTF requests the OCF to reserve the number of units determined in item Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represents the price for the number of units determined in item Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation. 6. Reservation Control: if the user's account balance is sufficient then the corresponding reservation is made.

30 30 TS V9.8.0 ( ) 7. Reserve Units Response: the OCF informs the CTF of the reserved number of units. 8. Reserved Units Supervision: simultaneously with the service delivery, the CTF monitors the consumption of the reserved units. 9. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the reserved number of units. 10. Debit Units Request: the CTF requests the OCF to assure the deduction of an amount corresponding to the consumed number of units from the subscriber's account. In the case that no further units are required for this service, an appropriate indication triggering the release of the remaining reservation is given. 11. Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from the subscriber's account. 12. Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account. 13. Debit Units Response: the OCF informs the CTF of the actually deducted units. 14. Session Release: the session is released.

31 31 TS V9.8.0 ( ) Centralized Unit Determination and Centralized Rating In the following scenario, the CTF requests the OCF to reserve units based on the service identifier specified by the CTF. An account debit operation is carried out following the conclusion of service delivery. UEa OCF CTF 1. Request for resource usage 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 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. Session released Figure : Event Charging with Reservation / Centralized Unit Determination and Centralized Rating 1. Request for resource usage: The UE-A requests the desired content from the CTF. 2. Reserve Units Request: depending on the service requested by the UE-A, the CTF selects the service identifier and forwards the Reserve Units Request to the OCF. 3. Units Determination: the OCF determines the number of non-monetary units needed for the content/service delivery, based on the received service key. 4. Rating Control: assisted by the rating entity the OCF calculates the number of monetary units that represent the price for the number of units determined in item Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation. 6. Reservation Control: if the user's account balance is sufficient, then the corresponding reservation is made. 7. Reserve Units Response: the OCF informs the CTF of the reserved number of units. This includes the case where the number of units reserved indicates the permission to render the service that was identified by the received service key.

32 32 TS V9.8.0 ( ) 8. Granted Units Supervision: simultaneously with the service delivery, the CTF monitors the consumption of the reserved units. 9. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the reserved number of units. 10. Debit Units Request: the CTF provides according to previous Reserve Units Response the request to deduct the amount of units corresponding to the consumed number of units. 11. Rating Control: assisted by the rating entity the OCF calculates the number of monetary units to deduct from the subscriber's account. 12. Account Control: the OCF triggers the deduction of the calculated amount from the subscriber's account. 13. Debit Units Response: the OCF informs the CTF of the actually deducted units. 14. Session Released: the session is released.

33 33 TS V9.8.0 ( ) Decentralized Unit Determination and Decentralized Rating In the following scenario, the CTF request the OCF to assure the reservation of an amount of the specified number of monetary units from the subscriber's account. An account debit operation that triggers the deduction the amount from the subscriber's account is carried out following the conclusion of service delivery. UEa OCF CTF 1. Request for resource usage 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. Session released Figure : Event Charging with Reservation / Centralized Unit Determination and Centralized Rating 1. Request for resource usage: The UE-A requests the desired content from the CTF. 2. Units Determination: depending on the service requested by the UE-A, the CTF determines the number of units accordingly. 3. Rating Control: the CTF calculates the number of monetary units that represent the price for the number of units determined in item Reserve Units Request: the CTF requests the OCF to assure the reservation of an amount corresponding to the calculated number of monetary units from the subscriber's account. 5. Account Control: the OCF checks whether the user's account balance is sufficient for the requested reservation. 6. Reservation Control: if the user's credit balance is sufficient, then the corresponding reservation is made. 7. Reserve Units Response: the OCF informs the CTF of the reserved number of monetary units. 8. Budget Control: simultaneously with the service delivery, the CTF monitors the consumption of the granted amount. 9. Content/Service Delivery: the CTF delivers the content/service at once, in fractions or in individually chargeable items, corresponding to the number of units.