OMA DDS Charging Data V1!0!20110201 A

Charging Data
Approved Version 1.0 01 Feb 2011
Open Mobile Alliance OMA-DDS-Charging_Data-V1_0-20110201-A
2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
[OMA-Template-DataDefSpec-20110101-I]
OMA-DDS-Charging_Data-V1_0-20110201-A
Page 2 (46)
Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html. Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance specification, and is subject to revision or removal without notice. You may use this document or any part of the document for internal or educational purposes only, provided you do not modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document. Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the OMA IPR Declarations list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form. NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPRS REPRESENTED ON THE OMA IPR DECLARATIONS LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL. THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.
Page 3 (46)
Contents
1. 2. SCOPE ................................................................................................................................................................................ 6 REFERENCES .................................................................................................................................................................. 7 2.1 NORMATIVE REFERENCES .......................................................................................................................................... 7 2.2 INFORMATIVE REFERENCES ....................................................................................................................................... 7 3. TERMINOLOGY AND CONVENTIONS ...................................................................................................................... 8 3.1 CONVENTIONS ............................................................................................................................................................. 8 3.2 DEFINITIONS................................................................................................................................................................ 8 3.3 ABBREVIATIONS .......................................................................................................................................................... 8 4. INTRODUCTION ............................................................................................................................................................. 9 5. 6. JUSTIFICATION ............................................................................................................................................................ 10 OMA CHARGING DATA DESCRIPTION ................................................................................................................. 11 6.1 MESSAGE STRUCTURES ............................................................................................................................................ 11 6.1.1 Offline Charging Requests ................................................................................................................................. 11 6.1.2 Offline Charging Responses .............................................................................................................................. 15 6.1.3 Online Charging Requests ................................................................................................................................. 16 6.1.4 Online Charging Responses ............................................................................................................................... 22 6.2 OMA CHARGING DATA ELEMENTS ......................................................................................................................... 26 6.2.1 Access Network Information ............................................................................................................................. 26 6.2.2 AoC Request Type ............................................................................................................................................. 26 6.2.3 Application Charging Identifier ......................................................................................................................... 26 6.2.4 Application Service Type................................................................................................................................... 26 6.2.5 Application Server Id ......................................................................................................................................... 26 6.2.6 Application Session Id ....................................................................................................................................... 26 6.2.7 Calling Party Address ........................................................................................................................................ 27 6.2.8 Called Party Address.......................................................................................................................................... 27 6.2.9 Cause Code ........................................................................................................................................................ 27 6.2.10 Check Balance Result ........................................................................................................................................ 27 6.2.11 Content ID.......................................................................................................................................................... 27 6.2.12 Content Length .................................................................................................................................................. 27 6.2.13 Content Provider ID ........................................................................................................................................... 27 6.2.14 Content Type...................................................................................................................................................... 27 6.2.15 Correlation Id ..................................................................................................................................................... 27 6.2.16 Cost Information ................................................................................................................................................ 27 6.2.17 Cost Unit ............................................................................................................................................................ 27 6.2.18 Currency Code ................................................................................................................................................... 27 6.2.19 Delivery Status ................................................................................................................................................... 28 6.2.20 Event Timestamp ............................................................................................................................................... 28 6.2.21 Expires ............................................................................................................................................................... 28 6.2.22 Exponent ............................................................................................................................................................ 28 6.2.23 Granted Service Unit.......................................................................................................................................... 28 6.2.24 Group Name ....................................................................................................................................................... 28 6.2.25 Input Octets ........................................................................................................................................................ 28 6.2.26 Inter-Operator Id ................................................................................................................................................ 28 6.2.27 Low Balance Indication ..................................................................................................................................... 28 6.2.28 Message Body .................................................................................................................................................... 28 6.2.29 Money ................................................................................................................................................................ 28 6.2.30 Multiple Services Credit Control ....................................................................................................................... 28 6.2.31 Number of Messages Successfully Exploded .................................................................................................... 28 6.2.32 Number of Messages Successfully Sent ............................................................................................................ 29 6.2.33 Number of Participants ...................................................................................................................................... 29 6.2.34 Originating IOI .................................................................................................................................................. 29 6.2.35 Output Octets ..................................................................................................................................................... 29
Page 4 (46)
7. 8.
6.2.36 Participant Group ............................................................................................................................................... 29 6.2.37 Rating Group ...................................................................................................................................................... 29 6.2.38 Reporting Reason ............................................................................................................................................... 29 6.2.39 Request Type ..................................................................................................................................................... 29 6.2.40 Requested Action ............................................................................................................................................... 29 6.2.41 Requested Service Unit ...................................................................................................................................... 30 6.2.42 Result Code ........................................................................................................................................................ 30 6.2.43 Role of Node ...................................................................................................................................................... 30 6.2.44 Role of User ....................................................................................................................................................... 30 6.2.45 Service Context Id.............................................................................................................................................. 30 6.2.46 Service Identifier ................................................................................................................................................ 31 6.2.47 Service Key ........................................................................................................................................................ 31 6.2.48 Service Specific Units ........................................................................................................................................ 31 6.2.49 Session Failover ................................................................................................................................................. 31 6.2.50 Session Id ........................................................................................................................................................... 31 6.2.51 SIP Method ........................................................................................................................................................ 31 6.2.52 SIP Request Timestamp ..................................................................................................................................... 31 6.2.53 SIP Response Timestamp .................................................................................................................................. 31 6.2.54 Subscription Id ................................................................................................................................................... 31 6.2.55 Subscription Data ............................................................................................................................................... 31 6.2.56 Subscription Type .............................................................................................................................................. 32 6.2.57 Tariff Change Usage .......................................................................................................................................... 32 6.2.58 Tariff Time Change............................................................................................................................................ 32 6.2.59 Terminating IOI ................................................................................................................................................. 32 6.2.60 Termination Cause ............................................................................................................................................. 32 6.2.61 Time ................................................................................................................................................................... 32 6.2.62 Total Number of Messages Exploded ................................................................................................................ 32 6.2.63 Total Number of Messages Sent ........................................................................................................................ 32 6.2.64 Total Octets ........................................................................................................................................................ 32 6.2.65 Trigger ............................................................................................................................................................... 32 6.2.66 Trigger Type ...................................................................................................................................................... 32 6.2.67 Unit Value .......................................................................................................................................................... 32 6.2.68 Used Service Unit .............................................................................................................................................. 32 6.2.69 User Equipment Info .......................................................................................................................................... 33 6.2.70 User Equipment Info Type ................................................................................................................................. 33 6.2.71 User Equipment Info Value ............................................................................................................................... 33 6.2.72 Validity Time ..................................................................................................................................................... 33 6.2.73 Value Digits ....................................................................................................................................................... 33 6.2.74 AoC Request Type ............................................................................................................................................. 33 6.2.75 AoC Information ................................................................................................................................................ 33 6.2.76 Tariff Information .............................................................................................................................................. 33 6.2.77 AoC Cost Information........................................................................................................................................ 33 6.2.78 Current Tariff ..................................................................................................................................................... 33 6.2.79 Next Tariff ......................................................................................................................................................... 33 6.2.80 Accumulated Cost .............................................................................................................................................. 34 6.2.81 Incremental Cost ................................................................................................................................................ 34 OPERATIONAL CONSIDERATIONS ........................................................................................................................ 35 BINDING TO DIAMETER ............................................................................................................................................ 36 8.1 DIAMETER COMMANDS ON CH-1 ............................................................................................................................. 36 8.1.1 Accounting Request Command ......................................................................................................................... 36 8.1.2 Accounting Answer Command .......................................................................................................................... 36 8.2 DIAMETER COMMANDS ON CH-2 ............................................................................................................................. 37 8.2.1 Credit-Control Request Command..................................................................................................................... 37 8.2.2 Credit-Control Answer Command ..................................................................................................................... 37 8.3 MAPPING OF OMA CHARGING DATA ELEMENTS TO AVPS ................................................................................... 38 8.4 SUMMARY OF AVPS USED ......................................................................................................................................... 40
Page 5 (46)
8.5 OMA SPECIFIC AVP USAGE .................................................................................................................................... 43 8.5.1 Acct-Application-Id AVP .................................................................................................................................. 43 8.5.2 Accounting-Record-Type AVP.......................................................................................................................... 43 8.5.3 Auth-Application-Id AVP .................................................................................................................................. 44 8.5.4 CC-Request-Type AVP ..................................................................................................................................... 44 8.5.5 DCD-Information AVP ...................................................................................................................................... 44 8.5.6 IM-Information AVP ......................................................................................................................................... 44 8.5.7 Multiple-Services-Credit-Control AVP ............................................................................................................. 44 8.5.8 Requested-Action AVP ...................................................................................................................................... 45 8.5.9 Service-Context-Id AVP .................................................................................................................................... 45 8.5.10 Service-Generic-Information AVP .................................................................................................................... 45 8.5.11 Service-Information AVP .................................................................................................................................. 45 APPENDIX A. CHANGE HISTORY (INFORMATIVE) .............................................................................................. 46 A.1 APPROVED VERSION 1.0 HISTORY ........................................................................................................................... 46
Tables
Table 1: OMA Charging Data Elements in Offline Charging Requests ............................................................................. 15 Table 2: OMA Charging Data Elements in Offline Charging Responses ........................................................................... 15 Table 3: OMA Charging Data Elements in Online Charging Requests ............................................................................. 21 Table 4: OMA Charging Data Elements in Online Charging Responses ........................................................................... 26 Table 5: Application Service Type Values ............................................................................................................................. 26 Table 6: Role of Node Values .................................................................................................................................................. 30 Table 7: Role of User Values ................................................................................................................................................... 30 Table 8: Service Context Id Values ........................................................................................................................................ 30 Table 9: Service Identifier Values .......................................................................................................................................... 31 Table 10: Mapping of OMA Charging Data Elements to Diameter AVPs ......................................................................... 40 Table 11: Summary of AVPs used on CH-1 and CH-2......................................................................................................... 43
Page 6 (46)
1. Scope
This Data Definition Specification serves as the centralised catalogue of all OMA Charging Data Elements defined for the OMA Offline Charging Interface (CH-1) and the OMA Online Charging Interface (CH-2). It also specifies the mapping of OMA Charging Data Elements to protocol fields used in the OMA-specified protocol bindings for the CH-1 and CH-2 interfaces.
Page 7 (46)
2. References
2.1 Normative References
OMA Offline Charging Interface, Open Mobile Alliance. OMA-TS-Charging_Offline-V1_1, URL: http://www.openmobilealliance.org/ OMA Online Charging Interface, Open Mobile Alliance. OMA-TS-Charging_Online-V1_1, URL: http://www.openmobilealliance.org/ Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt Diameter Base Protocol, P. Calhoun, J. Loughney, E. Guttman, G. Zorn, J. Arkko. September 2003, URL: http://www.ietf.org/rfc/rfc3588.txt Diameter Credit-Control Application, H. Hakala, L. Mattila, J-P. Koskinen, M. Stura, J. Loughney. August 2005, URL: http://www.ietf.org/rfc/rfc4006.txt Multimedia Messaging Service (MMS); MM10 Interface based on Diameter Protocol, 3GPP TS29.140, URL: http://www.3gpp.org Policy and Charging Control over Rx Reference Point, 3GPP TS29.214, URL: http://www.3gpp.org Telecommunication management; Charging management; Diameter Charging Applications, 3GPP TS32.299 , URL: http://www.3gpp.org [CHRG_OFFLINE] [CHRG_ONLINE] [RFC2119] [RFC3588] [RFC4006] [TS29.140] [TS29.214] [TS32.299]
2.2
Informative References
Dictionary for OMA Specifications, Open Mobile Alliance, OMA-ORG-Dictionary, URL:http://www.openmobilealliance.org/
[OMADICT]
Page 8 (46)
3. Terminology and Conventions

3.1 Conventions
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC2119]. All sections and appendixes, except Scope and Introduction, are normative, unless they are explicitly indicated to be informative.
3.2
CH-1 CH-2
Definitions
Offline Charging Interface Online Charging Interface
3.3
3GPP ACA ACR AVP CCA CCR DDS IM IMEI IMSI IOI MAC MIME MSCC MSISDN OMA RFC SIP URI
Abbreviations
3rd Generation Partnership Project ACcounting Answer ACcounting Request Attribute Value Pair Credit Control Answer Credit Control Request Data Definition Specification Instant Messaging International Mobile Equipment Identity International Mobile Subscriber Identity Inter Operator Identification Media Access Control Multipurpose Internet Mail Extensions Multiple Service Credit Control Mobile Subscriber ISDN Open Mobile Alliance Request for Comments Session Initiation Protocol Universal Resource Identification
Page 9 (46)
4. Introduction
This specification includes both normative and informative sections. OMA Charging Data Elements and protocol bindings that relate to the basic functionality of the Charging Enabler framework and the interfaces themselves are normatively defined in the interface specifications of the OMA Charging Enabler, and listed here only for completeness. Charging Data Elements and bindings that have been defined to carry charging information related to OMA Service Enablers or other Charging Enabler Users are normatively defined in this specification. Whereas the present document is not OMA Service Enabler specific, it generally supports data definitions pertaining to each charging enabler user. Other OMA specifications (such as enabler-specific charging specifications) may contain references to OMA Charging Data Elements defined in this data specification, and these other specifications may specify how the Data Elements are used and applied within the service/application context of these specifications, but the normative control over the naming, numbering, hierarchy position, and generic descriptions of the Data Elements remains in this specification.
Page 10 (46)
5. Justification
The OMA Charging Enabler specifies an extensible framework for OMA Charging Interfaces and the associated charging behaviour. Charging information exchanged over these interfaces consists of Charging Data Elements that contain information related to Charging Events. Already from the beginning of the specification work for the OMA Charging Enabler, it has been foreseen that different applications and services have varying needs regarding charging information that describes the charging events that they generate, and therefore extensions to charging information structures will be needed over time as new OMA enablers, applications and services emerge. As these extensions do not change the basic functionality and behaviour of the Charging Enabler framework itself, it is not necessary to release a new version of the OMA Charging Enabler each time new Charging Data Elements and/or protocols bindings are specified. In order to maintain consistency of the charging interfaces and to encourage re-use and generalisation, new Charging Data Elements must be created in a coordinated way. Also from the developers point of view, there should be one centralised catalogue where the complete functionality of the OMA Charging Enabler can be found.
Page 11 (46)
6. OMA Charging Data Description

The OMA Charging Interfaces support two charging models, an Event-based charging model and a Session-based charging model. The resulting charging information flows between the Charging Enabler User and the Charging Enabler are described in the Technical Specifications for Offline Charging [CHRG_OFFLINE] and respectively for Online Charging [CHRG_ONLINE]. The messages exchanged in these flows can be categorised into Charging Requests and Charging Responses, and the structure of these messages is defined in this chapter.
6.1
Message Structures
The following tables list the OMA Charging Data Elements applicable for Charging Requests and Charging Responses. The Category column indicates whether the element is mandatory or optional. The Level column allows the reader to clearly identify the hierarchy of data elements. Lets take the example of a data element A (level n) followed by data elements B and C (both being on level n+1). This means that element A comprises of element B and element C.
6.1.1
Hierarchy Level
Offline Charging Requests

OMA Charging Data Element Category Description
1 1 1
Request Type Event Timestamp Service Context Id
Mandatory Optional Mandatory
This data element indicates the type of the Charging Request message. This data element records the time at which the reported event occurred. This data element contains a value to identify the service/enabler specification in the context of which the charging events must be interpreted. Data elements such as Service Identifier, Service Specific Units, contain service specific values that are defined within a particular service context identified in this data element.
Information related to OMA service usage 1 Application Server Id Optional This data element can be used to identify the application server providing the service and/or generating the charging information. This data element can be used to identify the application-level session to which the charging information relates. Note that the Session Id data element identifies the charging session between a charging enabler user and a charging enabler. This data element can be used to carry information related to the success status of service delivery. This data element identifies the end users subscription This data element identifies which type of identifier is carried by the subscription-Id e.g.: email, MSISDN, IMSI, SIP URI...
Application Session Id
Optional
1 1 2
Delivery Status Subscription Id Subscription Type
Optional Optional Mandatory
Page 12 (46)
Hierarchy Level
OMA Charging Data Element
Category
Description
2 1
Subscription Data Correlation Id
Mandatory Optional
This data element identifies the end user. This data element contains information to correlate offline charging requests generated by different service components of the application. This data element indicates the length of the used time in seconds. This data element specifies the monetary amount in the given currency. The Currency Code data element should be included when this data element is included. This data element describes a value for instance a monetary value. It consists of Value Digits and Exponent. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies which currency is used in a monetary value described by the Money data element. This data element contains the number of used octets that can be/have been received from the end user. This data element contains the number of used octets that can be/have been sent to the end user. This data element specifies the number of servicespecific units (e.g. number of events, points) in a selected service. The service specific units always refer to the service identified in the Service Identifier data element This data element contains the identifier of a specific service within the given service context, e.g. operation type. This data element can be used to identify the particular service item delivered. This data element indicates the identity and capability of the terminal the end-user is using. User Equipment Info Type defines the type of user equipment information contained in User Equipment Info Value, e.g. IMEI or MAC. This data element contains the identity of the user equipment.
1 1
Time Money
Optional Optional
Unit Value
Mandatory
3 3 2
Value Digits Exponent Currency Code
Mandatory Optional Optional
1 1 1
Input Octets Output Octets Service Specific Units
Optional Optional Optional
Service Identifier
Optional
1 1 2
Service Key User Equipment Info User Equipment Info Type
Optional Optional Mandatory
User Equipment Info Value
Mandatory
Page 13 (46)
Hierarchy Level
Category
Description
1 2 2 2
Message Body Content Type Content Length Content Disposition
Optional Mandatory Mandatory Optional
This grouped data element contains information related to content exchanged in a message. This data element identifies the type of content, for example using MIME types. This data element identifies the length of content. This data element indicates how the message body or a message body part is to be interpreted (e.g. session, render), This data element indicates the originating party of the message body. This grouped data element contains information on a participant to a service-level session. This data element identifies an individual participant to a service-level session. This data element can be used to identify the role of the node generating the charging event in the service event, e.g. sending, receiving, controlling and participating. This data element can be used to identify the role of the user which the charging event relates to in the service event, e.g. session owner or participant. This data element can be used to differentiate between the different roles of a node within service events, e.g. the sending and receiving roles of participating and controlling functions. This data element can be used to indicate the number of parties involved in the service event, e.g. participating a session. This data element can be used to identify the party initiating the service event, e.g. the sender of a message. The initiating party is usually indicated in the Subscription Id data element in its role as the charged party. However, the charged party may also be some other party while the actual initiating party still needs to be identified. This data element can be used to identify the receiving party of a communication or the party that is the target of an operation (other than the initiator). This data element can be used to indicate the identifier of a group related to the event, e.g. a predefined distribution group in a messaging service. This data element holds an identifier that enables the correlation of various records pertaining to the same
2 1 2 1
Originator Participant Group Called Party Address Role of Node
Optional Optional Optional Optional
Role of User
Optional
Application Service Type
Optional
Number Of Participants
Optional
Calling Party Address
Optional
Called Party Address
Optional
Group Name
Optional
Application Charging Identifier
Optional
Page 14 (46)
Hierarchy Level
Category
Description
session. 1 2 2 1 1 Inter-Operator Id Originating IOI Terminating IOI Access Network Information Total Number of Messages Sent Optional Mandatory Mandatory Optional Optional The IOI identifies both originating and terminating networks involved in a session/transaction. Identifies the originating network. Identifies the terminating network. This data element can be used to carry information related to the access network used if available. This data element can be used to indicate the number of individual messages sent by the user. However, the number does not necessarily correspond to the number of message actually delivered. This data element can be used to indicate the total number of messages exploded by the IM server. This data element indicates the number of individual messages sent by the user that were successfully delivered to at least one recipient. This data element can be used to indicate the total number of messages exploded by the IM server that were successfully delivered. This data element can be used to identify the SIP Method triggering the charging event. The Expires data element indicates the relative time after which the SIP message expires. This data element can be used to indicate the returned SIP status code for the service request. This data element can be used to carry timestamps of a service delivery operation. This data element can be used to carry a timestamp related to the start of a service delivery operation. This data element holds the miliseconds fraction in relation to SIP Request Timestamp. This data element can be used to carry a timestamp related to the end of a service delivery operation. This data element holds the miliseconds fraction in relation to SIP Response Timestamp. This data element will be used as identifier sets by the Content Provider, and unique within the DCD Service Providers domain. This data element will be used as the globally unique identity of the content provider within the DCD
1 1
Total Number of Messages Exploded Number of Messages Successfully Sent
Optional Optional
Number of Messages Successfully Exploded SIP Method Expires Cause Code Time Stamps 2 2 2 2 SIP Request Timestamp SIP Request Timestamp Fraction SIP Response Timestamp SIP Response Timestamp Fraction Content ID
Optional
1 1 1 1
Optional Optional Optional Optional Optional Optional Optional Optional Optional
Content provider ID
Optional
Page 15 (46)
Hierarchy Level
Category
Description
Server Domain. Table 1: OMA Charging Data Elements in Offline Charging Requests
6.1.2
Hierarchy Level
Offline Charging Responses

1 1 1
Result Code Request Type Event Timestamp
Mandatory Mandatory Optional
This data element indicates the result of a particular request. This data element indicates the type of the corresponding Charging request message. This data element records the time at which the reported event occurred.
Table 2: OMA Charging Data Elements in Offline Charging Responses
Page 16 (46)
6.1.3
Hierarchy Level
Online Charging Requests

Session Id
Mandatory
This data element is used to identify a specific session. All messages pertaining to a specific session must use the same value. This data element contains a value to identify the service/enabler specification in the context of which the Charging Events must be interpreted. Data elements such as Service Identifier, Service Specific Units, contain service specific values that are defined within a particular service context identified in this data element. This data element contains the reason for sending the online charging request message This data element records the time at which the reported event occurred. This data element identifies the end user's subscription This data element identifies which type of identifier is carried by the subscription-Id e.g.: email, MSISDN, IMSI, SIP URI... This data element identifies the end user. This data element indicates the reason why a session was terminated on the access device. This data element contains the requested action being sent by Charging Enabler User when Request Type is set to EVENT_REQUEST. This data element indicates the use of Multiple Services Credit Control data element. This data element contains a list of data elements from a single Charging Enabler User that is providing multiple services. This data element contains the amount of requested units from the point before the service became active or, if interim interrogations are used during the session, from the point when the previous measurement ended. This data element indicates the length of the requestedtime in seconds. This data element specifies the monetary amount in the given currency. The Currency Code field should be included when This data element is included. This data element describes a value for instance a
Service Context Id
Mandatory
1 1 1 2
Request Type Event Timestamp Subscription Id Subscription Type
Mandatory Optional Optional Mandatory
2 1 1
Subscription Data Termination Cause Requested Action
Mandatory Optional Optional
1 1
Multiple Service Indicator Multiple Services Credit Control
Optional Optional
Requested Service Unit
Optional
3 3
Time Money
Optional Optional
Unit Value
Mandatory
Page 17 (46)
Hierarchy Level
Category
Description
monetary value. It consists of Value Digits and Exponent. 5 5 4 3 Value Digits Exponent Currency Code Total Octets Mandatory Optional Optional Optional This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies which currency is used in a monetary value described by the Money field. This data element contains the total number of requested octets, regardless of the direction (sent or received). This data element contains the number of requested octets that can be/have been received from the end user. This data element contains the number of requested octets that can be/have been sent to the end user. This data element specifies the number of servicespecific units (e.g. number of events, points) given in a selected service. The service specific units always refer to the service identified in the Service Identifier field This data element contains the amount of used units measured from the point when the service became active or, if interim interrogations are used during the session, from the point when the previous measurement ended. This data element specifies the reason for usage reporting for one or more types of quota for a particular category. This data element identifies the reporting period for the used service unit, i.e. before, after or during tariff change. This data element indicates the length of the used time in seconds. This data element specifies the monetary amount in the given currency. The Currency Code field should be included when This data element is included. This data element describes a value for instance a monetary value. It consists of Value Digits and Exponent. This data element contains the significant digits of a Unit Value without any decimal point.
Input Octets
Optional
3 3
Output Octets Service Specific Units
Optional Optional
Used Service Unit
Optional
Reporting Reason
Optional
Tariff Change Usage
Optional
3 3
Time Money
Optional Optional
Unit Value
Mandatory
Value Digits
Mandatory
Page 18 (46)
Hierarchy Level
Category
Description
5 4 3 3 3 3
Exponent Currency Code Total Octets Input Octets Output Octets Service Specific Units
Optional Optional Optional Optional Optional Optional
This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies which currency is used in a monetary value described by the Money field. This data element contains the total number of used octets regardless of the direction (sent or received). This data element contains the number of used octets that can be/have been received from the end user. This data element contains the number of used octets that can be/have been sent to the end user. This data element specifies the number of servicespecific units (e.g., number of events, points) given in a selected service. The service specific units always refer to the service identified in the Service Identifier field This data element contains the identifier of a specific service within the given service context, e.g. operation type. This data element contains the identifier of a rating group. This data element specifies the reason for usage reporting for one or more types of quota for a particular category. This data element contains the trigger types. This data element indicates a single re-authorisation event type. This is a grouped data element that can be used to indicate the identity and capability of the terminal the end-user is using. User Equipment Info Type defines the type of user equipment information contained in User Equipment Info Value, e.g. IMEI or MAC. Contains the identity of the user equipment.
Service Identifier
Optional
2 2
Rating Group Reporting Reason
Optional Optional
2 3 1
Trigger Trigger Type User Equipment Info
Optional Optional Optional
User Equipment Info Type
Mandatory
User Equipment Info Value
Mandatory
Information related to OMA service usage 1 Application Server Id Optional This data element can be used to identify the application server providing the service and/or generating the charging information. This data element can be used to identify the application-level session to which the charging information relates. Note that the Session Id data element identifies the charging session between a
Optional
Page 19 (46)
Hierarchy Level
Category
Description
charging enabler user and a charging enabler. 1 1 1 Delivery Status Service Key Correlation Id Optional Optional Optional This data element can be used to carry information related to the success status of service delivery. This data element can be used to identify the particular service item delivered. This data element contains information to correlate charging requests generated for different service components of the application. This data element denotes if AoC Information is requested and what type of information is needed. This grouped data element contains information related to content exchanged in a message. This data element identifies the type of content, for example using MIME types. This data element identifies the length of content. This data element indicates how the message body or a message body part is to be interpreted (e.g. session, render), This data element indicates the originating party of the message body. This grouped data element contains information on a participant to a service-level session. This data element identifies an individual participant to a service-level session. This data element can be used to identify the role of the node generating the charging event in the service event, e.g. sending, receiving, controlling and participating. This data element can be used to identify the role of the user which the charging event relates to in the service event, e.g. session owner or participant. This data element can be used to differentiate between the different roles of a node within service events, e.g. the sending and receiving roles of participating and controlling functions. This data element can be used to indicate the number of parties involved in the service event, e.g. participating a session. This data element can be used to identify the party initiating the service event, e.g. the sender of a message. The initiating party is usually indicated in the Subscription Id data element in its role as the
1 1 2 2 2
AoC Request Type Message Body Content Type Content Length Content Disposition
Optional Optional Mandatory Mandatory Optional
2 1 2 1
Originator Participant Group Called Party Address Role of Node
Optional Optional Optional Optional
Role of User
Optional
Application Service Type
Optional
Number of participants
Optional
Optional
Page 20 (46)
Hierarchy Level
Category
Description
charged party. However, the charged party may also be some other party while the actual initiating party still needs to be identified. 1 Called Party Address Optional This data element can be used to identify the receiving party of a communication or the party that is the target of an operation (other than the initiator). This data element can be used to indicate the identifier of a group related to the event, e.g. a predefined distribution group in a messaging service. This data element holds an identifier that enables the correlation of various records pertaining to the same session. The IOI identifies both originating and terminating networks involved in a session/transaction. Identifies the originating network. Identifies the terminating network. This data element can be used to carry information related to the access network used if available. This data element can be used to indicate the number of individual messages sent by the user. However, the number does not necessarily correspond to the number of message actually delivered. This data element can be used to indicate the total number of messages exploded by the IM server. This data element indicates the number of individual messages sent by the user that were successfully delivered to at least one recipient. This data element can be used to indicate the total number of messages exploded by the IM server that were successfully delivered. This data element can be used to identify the SIP Method triggering the charging event. The Expires data element indicates the relative time after which the SIP message expires. This data element can be used to indicate the returned SIP status code for the service request. This data element can be used to carry timestamps of a service delivery operation. This data element can be used to carry a timestamp related to the start of a service delivery operation. This data element holds the miliseconds fraction in
Group Name
Optional
Application Charging Identifier
Optional
1 2 2 1 1
Inter-Operator Id Originating IOI Terminating IOI Access Network Information Total Number of Messages Sent
Optional Mandatory Mandatory Optional Optional
1 1
Total Number of Messages Exploded Number of Messages Successfully Sent
Optional Optional
Number of Messages Successfully Exploded SIP Method Expires Cause Code Time Stamps 2 2 SIP Request Timestamp SIP Request Timestamp Fraction
Optional
1 1 1 1
Optional Optional Optional Optional Optional Optional
Page 21 (46)
Hierarchy Level
Category
Description
relation to SIP Request Timestamp. 2 2 1 SIP Response Timestamp SIP Response Timestamp Fraction Content ID Optional Optional Optional This data element can be used to carry a timestamp related to the end of a service delivery operation. This data element holds the miliseconds fraction in relation to SIP Response Timestamp. This data element will be used as identifier sets by the Content Provider, and unique within the DCD Service Providers domain. This data element will be used as the globally unique identity of the content provider within the DCD Server Domain.
Content Provider ID
Optional
Table 3: OMA Charging Data Elements in Online Charging Requests
Page 22 (46)
6.1.4
Hierarchy Level
Online Charging Responses

Session Id
Mandatory
This data element identifies a specific session. All messages pertaining to a specific session must use the same value. This data element indicates the result of a particular request. This data element contains the reason for sending the online charging request message. This data element contains a list of data elements from a single Charging Enabler User that is providing multiple services. This data element contains the amount of units that the Diameter credit-control client can provide to the end user until the service must be released or the new Request must be sent. This data element indicates the time in seconds since January 1, 1900, 00:00 UTC until the tariff of the service will be changed. This data element indicates the length of the granted time in seconds. This data element specifies the monetary amount in the given currency. The Currency Code field should be included when This data element is included. This data element describes a value for instance a monetary value. It consists of Value Digits and Exponent. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies which currency is used in a monetary value described by the Money field. This data element contains the total number of granted octets regardless of the direction (sent or received). This data element contains the number of granted octets that can be/have been received from the end user. This data element contains the number of granted octets that can be/have been sent to the end user. This data element specifies the number of service-
1 1 1
Result Code Request Type Multiple Services Credit Control
Mandatory Mandatory Optional
Granted Service Unit
Optional
Tariff Time Change
Optional
3 3
Time Money
Optional Optional
Unit Value
Mandatory
5 5 4 3
Value Digits Exponent Currency Code Total Octets
Mandatory Optional Optional Optional
Input Octets
Optional
3 3
Output Octets Service Specific Units
Optional Optional
Page 23 (46)
Hierarchy Level
Category
Description
specific units (e.g., number of events, points) given in a selected service. The service specific units always refer to the service identified in the Service Identifier field 2 Service Identifier Optional This data element contains the identifier of a service. The specific service the request relates to is uniquely identified by the combination of Service-Context-Id and Service-Identifier. This data element contains the identifier of a rating group. This data element contains the validity time of the granted service units. The value field of the Validity Time field is given in seconds. This data element is used to return the cost information of a service, which the Charging Enabler User can transfer transparently to the end user.
2 2
Rating Group Validity Time
Optional Optional
Cost Information
Optional
Page 24 (46)
Hierarchy Level
Category
Description
Unit Value
Mandatory
The Unit Value element contains the cost estimate (always type of money) of the service, in the case of price enquiry, or the accumulated cost estimation, in the case of credit-control session. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies which currency is used in a monetary value described by the Unit Value field. Cost Unit specifies the applicable unit to the Cost Information element when the service cost is a cost per unit (e.g., cost of the service is $1 per minute). The Cost Unit can be minutes, hours, days, kilobytes, megabytes, etc. This data element contains the result of the balance check. It is applicable only when the Requested Action element indicates BALANCE_CHECK in the corresponding request message. This data element indicates a low balance threshold with regard to the designated service usage. This indication can be used, e.g. to advise the end-user about a need to replenish the account balance. This data element contains the detailed information for Advice of Charge and holds sub-elements. This data element specifies the AoC cost specific parameters. AoC-Cost-Information is used only in the Credit Control Answer. This data element specifies the amount charged since the beginning of the session This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element specifies the amount charged since the last report. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. Ommited if the amount is in non-monetary units units
3 3 2 2
Value Digits Exponent Currency Code Cost Unit
Mandatory Optional Mandatory Optional
Check Balance Result
Optional
Low Balance Indication
Optional
1 2
AoC Information AoC Cost Information
Optional Optional
3 4 4 3 4 4 3
Accumulated Cost Value Digits Exponent Incremental Cost Value Digits Exponent Currency Code
Optional Mandatory Optional Optional Mandatory Optional Optional
Page 25 (46)
Hierarchy Level
Category
Description
2 3 4 5 5 4 5 5 5 5 6 6 5 3 3 2 3 4 4 3
Tariff Information
Optional Mandatory Optional Mandatory Optional Optional Mandatory Optional Optional Optional Mandatory Optional Optional Optional Optional Optional Optional Optional Optional Optional
This data element specifies the Tariff specific parameters. This data element specifies the Tariff for the current time period. This data element holds simple multiplication factor in the same format as Unit-Value. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element holds simple rate element of one dimension. This data element specifies the type of units considered to be pooled into a credit pool. This data element identifies if the Rate-Element corresponds to a specific NNI charge type. This data element specifies the units as decimal value. This data element holds monetary value. This data element contains the significant digits of a Unit Value without any decimal point. This data element contains the 10-x exponent that should be applied to the Value Digits. This data element contains a threshold value in service specific units This data element specifies the tariffs switch time. This data element specifies the Tariff for the next time period. This data element holds the subscription and formatting parameters. This data element holds the pair of AoC Service type and AoC Service obligatory type. This data element holds the information if the AoC information is binding or not. This data element defines the type of AoC information to be provided to the subscriber. This data element holds the format on how the AoC information shall be sent to the user.
Current Tariff Scale Factor Value Digits Exponent Rate Element CC Unit Type Reason Code Unit Value Unit Cost Value Digits Exponent Unit Quota Threshold Tariff Time Change Next Tariff AoC Subscription Information AoC Service AoC Service Obligatory Type AoC Service Type AoC Format
Page 26 (46)
Hierarchy Level
Category
Description
3 Preferred AoC Currency
Optional
This data element indicates the preferred currency code that the AoC function would like to get the AoC information.
Table 4: OMA Charging Data Elements in Online Charging Responses
6.2
6.2.1 6.2.2 6.2.3 6.2.4
OMA Charging Data Elements

Access Network Information AoC Request Type Application Charging Identifier Application Service Type
This section describes the usage and values related to specific OMA Charging Data Elements in alphabetical order.
This data element can be used to carry information related to the access network used if available.
This data element denotes if AoC Information is requested and what type of information is needed.
This data element holds an identifier that enables the correlation of various records pertaining to the same session
This data element can be used to differentiate between the different roles of a node within service events, e.g. the sending and receiving roles of participating and controlling functions.
Service Context Name Value Description
SIMPLE_IM
SENDING RECEIVING RETRIEVAL INVITING LEAVING JOINING
100 101 102 103 104 105 Table 5: Application Service Type Values
6.2.5
Application Server Id
This data element can be used to identify the application server providing the service and/or generating the charging information.
6.2.6
This data element can be used to identify the application-level session to which the charging information relates. Note that the Session Id data element identifies the charging session between a charging enabler user and a charging enabler.
Page 27 (46)
6.2.7
This data element can be used to identify the party initiating the service event, e.g. the sender of a message. The initiating party is usually indicated in the Subscription Id data element in its role as the charged party. However, the charged party may also be some other party while the actual initiating party still needs to be identified.
6.2.8
Called Party Address
This data element can be used to identify the receiving party of a communication or the party that is the target of an operation (other than the initiator). This data element identifies an individual participant to a service-level session.
6.2.9 6.2.10
Cause Code Check Balance Result
This data element can be used to indicate the returned status code for the service request.
This data element contains the result of the balance check. It is applicable only when the Requested Action element indicates BALANCE_CHECK in the corresponding request message.
6.2.11
Content ID
This data element will be used as identifier sets by the Content Provider, and unique within the DCD Service Providers domain.
6.2.12 6.2.13 6.2.14 6.2.15
Content Length Content Provider ID Content Type Correlation Id
This data element identifies the length of content.
This data element will be used as the globally unique identity of the content provider within the DCD Server Domain.
This data element identifies the type of content, for example using MIME types.
This data element contains information to correlate charging requests generated by different service components of the application.
6.2.16
Cost Information
This data element is used to return the cost information of a service, which the Charging Enabler User can transfer transparently to the end user.
6.2.17 6.2.18
Cost Unit Currency Code
This data element is used to display a human readable string to the end user.
This data element specifies which currency is used in a monetary value described by the Money data element.
Page 28 (46)
6.2.19 6.2.20 6.2.21 6.2.22 6.2.23
Delivery Status Event Timestamp Expires Exponent Granted Service Unit
This data element can be used to carry information related to the success status of service delivery.
This data element records the time at which the reported event occurred.
The Expires data element indicates the relative time after which the message expires.
This data element contains the 10x exponent that should be applied to the Value Digits.
This data element contains the amount of units that the Charging Enabler User can provide to the end user until the charging session will be released or a new Charging Request must be sent.
6.2.24
Group Name
This data element can be used to indicate the identifier of a group related to the event, e.g. a pre-defined distribution group in a messaging service.
6.2.25 6.2.26 6.2.27
Input Octets Inter-Operator Id Low Balance Indication
This data element contains the number of requested, granted, or used octets that can be/have been received from the end user.
The IOI identifies both originating and terminating networks involved in a session/transaction.
This data element indicates a low balance threshold with regard to the designated service usage. This indication can be used, e.g. to advise the end-user about a need to replenish the account balance.
6.2.28 6.2.29
Message Body Money
This grouped data element contains information related to content exchanged for service usage.
This data element specifies the monetary amount in the given currency. The Currency Code data element should be included when this data element is included.
6.2.30
Multiple Services Credit Control
Multiple Services Credit Control enables handling multiple services independently within a single online charging session. This data element contains a list of data elements from a single Charging Enabler User that is providing multiple services.
6.2.31
Number of Messages Successfully Exploded
This data element indicates the total number of messages that were successfully distributed to recipients.
Page 29 (46)
6.2.32
Number of Messages Successfully Sent
This data element indicates the number of individual messages sent by the user that were successfully delivered to at least one recipient.
6.2.33 6.2.34 6.2.35 6.2.36 6.2.37 6.2.38 6.2.39
Number of Participants Originating IOI Output Octets Participant Group Rating Group Reporting Reason Request Type
This data element can be used to indicate the number of parties involved in the service event, e.g. participating a session.
Identifies the originating network.
This data element contains the number of requested, granted, or used octets that can be/have been sent to the end user.
This grouped data element contains a list of participants to a service-level session.
This data element contains the identifier of a rating group.
This data element specifies the reason for usage reporting for one or more types of quota for a particular category.
This data element indicates the type of the Charging Request message, or in a Charging Response message, the corresponding request that the response relates to.
Charging Model Values Description
Offline (CH-1)
Online (CH-2)
EVENT_RECORD START_RECORD INTERIM_RECORD STOP_RECORD EVENT_REQUEST INITIAL_REQUEST UPDATE_REQUEST TERMINATION_REQUEST
6.2.40
Requested Action
This data element indicates the type of Event-based Online Charging Request being sent by Charging Enabler User when Request Type is set to EVENT_REQUEST (refer to [CHRG_ONLINE]).
Values Description
DIRECT_DEBTING REFUND_ACCOUNT CHECK_BALANCE PRICE_ENQUIRY
Indicates a Debit Request Indicates a Refund Request Indicates a Balance Check Request Indicates a Price Enquiry Request
Page 30 (46)
6.2.41
Requested Service Unit
This data element contains the amount of requested units from the point before the service became active or, if interim interrogations are used during the session, from the point when the previous measurement ended.
6.2.42 6.2.43
Result Code Role of Node
This data element indicates the result of a particular request.
This data element can be used to identify the role of the node generating the charging event in the service event, e.g. sending, receiving, controlling and participating.
SIMPLE_IM
PARTICIPATING_FUNCTION CONTROLING_FUNCTION
0 1
Table 6: Role of Node Values
6.2.44
Role of User
This data element can be used to identify the role of the user which the charging event relates to in the service event, e.g. session owner or participant.
SIMPLE_IM
NORMAL_PARTICIPANT SESSION_OWNER
4 3
Table 7: Role of User Values
6.2.45
Service Context Id
This data element contains a value to identify the service/enabler specification in the context of which the charging events must be interpreted. Data elements such as Service Identifier, Service Specific Units, contain service specific values that are defined within a particular service context identified in this data element.
Value OMA Specification Description
BCAST@openmobilealliance.org
OMA-TS-BCAST_Services-V1_0
SIMPLE_IM@openmobilealliance.org
OMA-TS-SIMPLE_IM_Charging-V1_0
DCD@openmobilealliance.org
OMA-TS-DCD_Charging-V1_0
CPM@openmobilealliance.org
OMA-TS-CPM_Charging-V1_0
This value is used to identify charging activities associated with the OMA Broadcast Services enabler. This value is used to identify charging activities associated with the OMA Instant Messaging using SIMPLE enabler. This value is used to identify charging activities associated with the OMA Dynamic Content Delivery enabler. This value is used to identify charging activities associated with the OMA Converged IP Messaging enabler.
Table 8: Service Context Id Values
Page 31 (46)
6.2.46
Service Identifier
This data element contains the identifier of a specific service within the given service context, e.g. operation type. The specific service the request relates to is uniquely identified by the combination of Service-Context-Id and Service-Identifier.
BCAST
SIMPLE_IM
SUBSCRIBE SUBSCRIPTION_UPDATE UNSUBSCRIBE TOKEN_PURCHASE SERVICE_INTERACTION PAGER_MODE LARGE_MESSAGE_MODE SESSION_MODE CONVERSATION_HISTORY
100 101 102 103 104 200 201 202 203
Table 9: Service Identifier Values
6.2.47 6.2.48
Service Key Service Specific Units
This data element can be used to identify the particular service item delivered.
This data element specifies the number of service-specific units (e.g. number of events, points) in a selected service. The service specific units always refer to the service identified in the Service Identifier data element.
6.2.49
Session Failover
This data element contains an indication to the Charging Enabler User whether or not a failover handling is to be used when necessary.
6.2.50 6.2.51 6.2.52 6.2.53 6.2.54 6.2.55
Session Id SIP Method SIP Request Timestamp SIP Response Timestamp Subscription Id Subscription Data
This data element is used to identify a specific session. All messages pertaining to a specific session must use the same value.
This data element can be used to identify the SIP Method triggering the charging event.
This data element can be used to carry a timestamp related to the start of a service delivery operation.
This data element can be used to carry a timestamp related to the end of a service delivery operation.
This data element identifies the end users subscription
This data element identifies the end user.

Page 32 (46)
6.2.56 6.2.57 6.2.58 6.2.59 6.2.60 6.2.61 6.2.62 6.2.63
Subscription Type Tariff Change Usage Tariff Time Change Terminating IOI Termination Cause Time Total Number of Messages Exploded Total Number of Messages Sent
This data element identifies which type of identifier is carried by the Subscription Id e.g.: email, MSISDN, IMSI, SIP URI...
This data element identifies the reporting period for the used service unit, i.e. before, after or during tariff change.
This data element indicates the time until the tariff of the service will be changed.
This data element identifies the terminating network.
This data element indicates the reason why a session was terminated on the access device.
This data element indicates the length of the requested, granted, or used time in seconds.
This data element indicates the total number of messages distributed to recipients.
This data element indicates the total number of individual messages sent by the sender. However, the number does not necessarily correspond to the number of message actually delivered to recipients.
6.2.64
Total Octets
This data element contains the total number of requested, granted, or used octets, regardless of the direction (sent or received).
6.2.65 6.2.66 6.2.67 6.2.68
Trigger Trigger Type Unit Value Used Service Unit
This data element contains the trigger types.
This data element indicates a single re-authorisation event type.
This data element describes a value, for example a monetary value. It consists of Value Digits and Exponent.
This data element contains the amount of used units measured from the point when the service became active or, if interim interrogations are used during the session, from the point when the previous measurement ended.
Page 33 (46)
6.2.69 6.2.70
User Equipment Info User Equipment Info Type
This data element indicates the identity of the equipment the end-user is using.
User Equipment Info Type defines the type of user equipment information contained in User Equipment Info Value, e.g. IMEI or MAC.
6.2.71 6.2.72 6.2.73 6.2.74
User Equipment Info Value Validity Time Value Digits AoC Request Type
This data element contains the identity of the user equipment.
This data element contains the validity time of the granted service units.
This data element contains the significant digits of the number.
This data element denotes if AoC Information is requested and what type of information is needed. It can be one of the following values: AoC_NOT_REQUESTED AoC_FULL AoC_COST_ONLY AoC_TARIFF_ONLY 0 1 2 3
6.2.75 6.2.76 6.2.77
AoC Information Tariff Information AoC Cost Information
This data element contains the detailed information for Advice of Charge and holds sub-elements.
This data element specifies the Tariff specific parameters.
This data element specifies the AoC cost specific parameters. AoC-Cost-Information is used only in the Credit Control Answer.
6.2.78 6.2.79
Current Tariff Next Tariff
Tariff for the current time period.
Tariff for the next time period.
Page 34 (46)
6.2.80 6.2.81
Accumulated Cost Incremental Cost
The ammount charged since the beginning of the session
The ammount charged since the last report.
Page 35 (46)
7. Operational Considerations
This Data Definition Specification serves as the single source of all information related to OMA Charging Data Elements and their protocol bindings, and it is centrally managed by the Mobile Commerce and Charging (MCC) Working Group. This DDS is published under an independent OMA Reference Release in order to de-couple its release cycles from the OMA Charging Enabler and the individual OMA Service Enablers. This enables OMA to publish new Charging Data Elements with short lead times as different OMA Work Items require them, and avoids publishing unnecessary minor/technical releases of the Charging Enabler.
Page 36 (46)
8. Binding to Diameter
8.1
8.1.1
Diameter Commands on CH-1

Accounting Request Command
The ACR command is sent from the Charging Enabler User to the Charging Enabler in order to send charging information for the requested resource usage. This command is used for both Event Based and Session Based requests. The distinction is made accordingly to the value carried in the Accounting-Record-Type AVP (see Section 8.5.2).
<ACR> ::= < Diameter Header: 271, REQ, PXY > < { { { { { [ [ [ [ [ [ [ [ [ [ * [ * [ [ [ * [ Session-Id > Origin-Host } Origin-Realm } Destination-Realm } Accounting-Record-Type } Accounting-Record-Number } Acct-Application-Id ] Vendor-Specific-Application-Id ] User-Name ] Accounting-Sub-Session-Id ] Acct-Session-Id ] Acct-Multi-Session-Id ] Acct-Interim-Interval ] Accounting-Realtime-Required ] Origin-State-Id ] Event-Timestamp ] Proxy-Info ] Route-Record ] Service-Context-Id ] Service-Information ] AVP ]
8.1.2
Accounting Answer Command
The ACA command is sent from the Charging Enabler to the Charging Enabler User in response to an ACR command and is used in order to acknowledge the reception of the charging data. This command is used for both Event Based and Session Based responses. The distinction is made accordingly to the value carried in the Accounting-Record-Type AVP (see Section 8.5.2). The value of this AVP will be the same one contained in the same AVP of the corresponding request.
<ACA> ::= < Diameter Header: 271, PXY > < { { { { { [ [ [ [ [ [ [ [ [ [ [ * [ * [ Session-Id > Result-Code } Origin-Host } Origin-Realm } Accounting-Record-Type } Accounting-Record-Number } Acct-Application-Id ] Vendor-Specific-Application-Id ] User-Name ] Accounting-Sub-Session-Id ] Acct-Session-Id ] Acct-Multi-Session-Id ] Error-Reporting-Host ] Acct-Interim-Interval ] Accounting-Realtime-Required ] Origin-State-Id ] Event-Timestamp ] Proxy-Info ] AVP ]
Page 37 (46)
8.2
8.2.1
Diameter Commands on CH-2

Credit-Control Request Command
The CCR command is sent from the Charging Enabler User to the Charging Enabler in order to request credit authorization for resource usage. This command is used for both Event Based and Session Based requests. The distinction is made accordingly to the value carried in the CC-Request-Type AVP (see Section 8.5.4).
<Credit-Control-Request> ::= < Diameter Header: 272, REQ, PXY > < { { { { { { { [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ Session-Id > Origin-Host } Origin-Realm } Destination-Realm } Auth-Application-Id } Service-Context-Id } CC-Request-Type } CC-Request-Number } Destination-Host ] User-Name ] CC-Sub-Session-Id ] Acct-Multi-Session-Id ] Origin-State-Id ] Event-Timestamp ] Subscription-Id ] Service-Identifier ] Termination-Cause ] Requested-Service-Unit ] Requested-Action ] AoC-Request-Type ] Used-Service-Unit ] AoC-Request-Type ] Multiple-Services-Indicator ] Multiple-Services-Credit-Control ] Service-Parameter-Info ] CC-Correlation-Id ] User-Equipment-Info ] Proxy-Info ] Route-Record ] Service-Information ] AVP ]
* * * * * *
8.2.2
Credit-Control Answer Command
The CCA command is sent from the Charging Enabler to the Charging Enabler User in response to a CCR command and is used in order to authorize and allocate credit for resource usage. This command is used for both Event Based and Session Based responses. The distinction is made accordingly to the value carried in the CC-Request-Type AVP (see Section 8.5.4). The value of this AVP will be the same one contained in the same AVP of the corresponding request.
<Credit-Control-Answer> ::= < Diameter Header: 272, PXY > < { { { { { { [ [ [ [ Session-Id > Result-Code } Origin-Host } Origin-Realm } Auth-Application-Id } CC-Request-Type } CC-Request-Number } User-Name ] CC-Session-Failover ] CC-Sub-Session-Id ] Acct-Multi-Session-Id ]
Page 38 (46)
[ Origin-State-Id ] [ Event-Timestamp ] [ Granted-Service-Unit ] *[ Multiple-Services-Credit-Control ] [ Cost-Information ] [ Low-Balance-Indication ] [ Final-Unit-Indication ] [ Check-Balance-Result ] [ Credit-Control-Failure-Handling ] [ Direct-Debiting-Failure-Handling ] [ Validity-Time] *[ Redirect-Host] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] * [ Route-Record ] * [ Failed-AVP ] [ Service-Information ] *[ AVP ]
8.3
Mapping of OMA Charging Data Elements to AVPs

OMA Charging Data Element Diameter AVP
The following table describes the mapping of the OMA Charging Data Elements to the Diameter AVPs. Access Network Information AoC Request Type Application Charging Identifier Accumulated Cost AoC Cost Information AoC Information AoC Request Type Application Server Id Application Service Type Application Session Id Called Party Address Calling Party Address Cause Code CC Unit Type Check Balance Result Content Disposition Content ID Content Length Content provider ID Content Type Correlation Id Cost Information Cost Unit Current Tariff Currency Code Delivery Status Destination Host Destination Realm Access-Network-Charging-Identifier-Value AoC-Request-Type[CH-2] IMS-Charging-Identifier Accumulated-Cost AoC-Cost-Information AoC-Information AoC-Request-Type Application-Server-Id Application-Service-Type Application-Session-Id Called-Party-Address Calling-Party-Address Cause-Code CC-Unit-Type [CH-2] Check-Balance-Result [CH-2] Content-Disposition Content-ID Content-Length Content-provider-ID Content-Type Billing-Information Cost-Information [CH-2] Cost-Unit [CH-2] Current-Tariff Currency-Code Delivery-Status Destination-Host [CH-2] Destination-Realm
Page 39 (46)
Diameter AVP
Event Timestamp Expires Exponent Granted Service Unit Group Name Incremental Cost Input Octets Inter-Operator Identifier Low Balance Indication Message Body Money Multiple Service Indicator Multiple Services Credit Control Next Tariff Number of Messages Successfully Exploded Number of Messages Successfully Sent Number of participants Originating IOI Originator Output Octets Participant Group Rate Element Rating Group Reason Code Reporting Reason Request Type Requested Action Requested Service Unit Result code Role of Node Role of User Scale Factor Service Context Id Service Identifier Service Key Service Specific Units Session Failover Session Id SIP Method SIP Request Timestamp SIP Request Timestamp Fraction SIP Response Timestamp
Event-Timestamp Expires Exponent Granted-Service-Unit [CH-2] PoC-Group-Name Incremental-Cost Accounting-Input-Octets [CH-1] CC-Input-Octets [CH-2] Inter-Operator-Identifier Low-Balance-Indication [CH-2] Message-Body CC-Money Multiple-Service-Indicator [CH-2] Multiple-Services-Credit-Control [CH-2] Next-Tariff Number-of-Messages-Successfully-Exploded Number-of-Messages-Successfully-Sent Number-of-Participants Originating-IOI Originator Accounting-Output-Octets [CH-1] CC-Output-Octets [CH-2] Participant-Group Rate-Element [CH-2] Rating-Group [CH-2] Reason-Code [CH-2] Reporting-Reason [CH-2] Accounting-Record-Type [CH-1] CC-Request-Type [CH-2] Requested-Action [CH-2] Requested-Service-Unit [CH-2] Result-Code PoC-Server-Role PoC-User-Role Scale-Factor [CH-2] Service-Context-Id Service-Identifier Service-Key CC-Service-Specific-Units CC-Session-Failover [CH-2] Session-Id SIP-Method SIP-Request-Timestamp SIP-Request-Timestamp-Fraction SIP-Response-Timestamp
Page 40 (46)
Diameter AVP
SIP Response Timestamp Fraction Subscription Id Subscription Data Subscription Type Tariff Change Usage Tariff Information Tariff Time Change Terminating IOI Termination Cause Time Stamps Time Total Number of Messages Exploded Total Number of Messages Sent Total Octets Trigger Type Unit Cost Unit Quota Threshold Unit Value Used Service Unit User Equipment Info User Equipment Info Type User Equipment Info Value Validity Time Value Digits
SIP-Response-Timestamp-Fraction Subscription-Id Subscription-Id-Data Subscription-Id-Type Tariff-Change-Usage [CH2] Tariff-Information [CH-2] Tariff-Time-Change [CH-2] Terminating-IOI Termination-Cause [CH-2] Time-Stamps Acct-Session-Time [CH-1] CC-Time [CH-2] Total-Number-of-Messages-Exploded Total-Number-of-Messages-Sent CC-Total-Octets [CH-2] Trigger-Type Unit-Cost [CH-2] Unit-Quota-Threshold [CH-2] Unit-Value [CH-2] Used-Service-Unit [CH-2] User-Equipment-Info User-Equipment-Info-Type User-Equipment-Info-Value Validity-Time Value-Digits [CH-2]
[CH-1] indicates usage on the offline interface; [CH-2] indicates usage on the online interface. Table 10: Mapping of OMA Charging Data Elements to Diameter AVPs
8.4
Summary of AVPs used
The following table lists the Diameter AVPs specifically re-used by OMA for the Offline Charging interface (CH-1) and for the Online Charging interface (CH-2). The table contains the following information: AVP Name: The name used in Diameter. AVP Code: The AVP Code used in the Diameter AVP Header. Used in ACR: Indicates if it is mandatory, optional or not used in the ACR command. Used in ACA: Indicates if it is mandatory, optional or not used in the ACA command. Used in SI: Indicates if it is mandatory, optional or not used in the Service-Information AVP. Used in CCR: Indicates if it is mandatory, optional or not used in the CCR command. Used in MSCC CCR: Indicates if it is mandatory, optional or not used in the Multiple-Services-Credit-Control AVP in the CCR command. Used in CCA: Indicates if it is mandatory, optional or not used in the CCA command.
Page 41 (46)
Used in MSCC CCA: Indicates if it is mandatory, optional or not used in the Multiple-Services-Credit-Control AVP in the CCA command. AVP Defined: A reference to where this AVP is defined. Value Type: The Diameter format of the AVP data as defined in Basic or Derived AVP Data Format. AVP Flag Rules: The rules for how the AVP Flags in the AVP Header may be set. May Encrypt: Indicates if the AVP may be encrypted or not.
Used In: AVP Code CCR MSCC CCA MSCC Reference Value Type ACR ACA CCR CCA AVP Flag Rules Should not Must not Must May
AVP Vendor ID
May Encrypt
AVP Name
SI
AccessNetworkCharging IdentifierValue AccountingInputOctets AccountingOutputOctets AccountingRecordNumber AccountingRecordType AcctApplicationId AcctInterimInterval AcctSessionTime Accumulated-Cost AoC-Cost-Information AoC-Format AoC-Information AoC-Request-Type AoC-Service AoC-Service-Obligatory-Type AoC-Service-Type AoC-Subscription-Information ApplicationServerId ApplicationServiceType ApplicationSessionId AuthApplicationId BillingInformation CalledPartyAddress CallingPartyAddress CauseCode CCInputOctets CCMoney CCOutputOctets CCRequestNumber CCRequestType CCServiceSpecificUnits CCSessionFailover CCTime CCTotalOctets CCUnitType CheckBalanceResult Content-Disposition Content-ID ContentLength Content-provider-ID ContentType CostInformation CostUnit CreditControlFailureHandling
10415 0 0 0 0 0 0 0 10415 10415 10415 10415 10415 10415 10415 10415 10415 10415 10415 10415 0 10415 10415 10415 10415 0 0 0 0 0 0 0 0 0 0 0 10415 10415 10415 10415 10415 0 0 0
503 363 364 485 480 259 85 46 2052 2053 2310 2054 2055 2311 2312 2313 2314 2101 2102 2103 258 1115 832 831 861 412 413 414 415 416 417 418 420 421 454 422 828 2116 827 2117 826 423 424 427
M M O O
M M O O
O O O O O O O O O O O O O O O O O O O O O M O O O O O
O M M M
O O O O O O
M M M O O O O
O O O O O O O O
[TS29.214] [RFC4005] [RFC4005] [RFC3588] [8.5.11] [8.5.11] [RFC3588] [RFC4005] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [8.5.11] [TS29.140] [TS32.299] [TS32.299] [TS32.299] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [8.5.11] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [RFC4006] [RFC4006] [RFC4006]
OctetString Unsigned64 Unsigned64 Unsigned32 Enumerated Unsigned32 Unsigned32 Unsigned32 Grouped Grouped Enumerated Grouped Enumerated Grouped Enumerated Enumerated Grouped UTF8String Enumerated Unsigned32 Unsigned32 UTF8String UTF8String UTF8String Integer32 Unsigned64 Grouped Unsigned64 Unsigned32 Enumerated Unsigned64 Enumerated Unsigned32 Unsigned64 Enumerated Enumerated UTF8String UTF8String Unsigned32 UTF8String UTF8String Grouped UTF8String Enumerated
V,M M M M M M M M V,M V,M V.M V,M V.M V,M V.M V.M V,M V,M V,M V,M M V,M V,M V,M V,M M M M M M M M M M M M V,M V,M V,M V,M V,M M M M
P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P
V V V V V V V V V V V V V V V V V V V V V V
Y Y Y Y Y N Y Y N N N N N N N N N Y Y Y N Y N N N Y Y Y Y Y Y Y Y Y Y Y N Y N Y N Y Y Y
Page 42 (46)
Used In: AVP Code CCR MSCC CCA MSCC Reference Value Type ACR ACA CCR CCA
AVP Flag Rules Should not Must not Must May
AVP Vendor ID
May Encrypt
AVP Name
SI
Current-Tariff CurrencyCode DCD-Information DeliveryStatus DestinationHost DestinationRealm DirectDebitingFailureHandling EventTimestamp Expires Exponent FailedAVP FinalUnitAction FinalUnitIndication GrantedServiceUnit GSUPoolIdentifier GSUPoolReference IMInformation IMSChargingIdentifier InterOperatorIdentifier Incremental-Cost LowBalanceIndication MessageBody MultipleServicesCreditControl MultipleServicesIndicator Next-Tariff NumberOfMessages SuccessfullyExploded NumberOfMessages SuccessfullySent NumberofParticipants Originating IOI OriginHost OriginRealm OriginStateId Originator ParticipantGroup PoCGroupName PoCServerRole PoCUserRole Preferred-AoC-Currency ProxyHost ProxyInfo ProxyState QuotaConsumptionTime QuotaHoldingTime Rate-Element RatingGroup Reason-Code RedirectAddressType RedirectHost RedirectHostUsage RedirectMaxCacheTime RedirectServer RedirectServerAddress ReportingReason RequestedAction
10415 0 10415 10415 0 0 0 0 10415 0 0 0 0 0 0 0 10415 10415 10415 10415 10415 10415 0 0 10415 10415 10415 10415 10415 0 0 0 10415 10415 10415 10415 10415 10415 0 0 0 10415 10415 10415 0 10415 0 0 0 0 0 0 10415 0
2056 425 2115 2104 293 283 428 55 888 429 279 449 430 431 453 457 2110 841 838 2062 2020 889 456 455 2057 2111 2112 885 839 264 296 278 864 1260 859 883 1252 2315 280 284 33 881 871 2058 432 2316 433 292 261 262 434 435 872 436
M O M M O M O M
O M M O M O M
M O O O O O O O O O O O O O O O O O O O O O O O
O M O O O M M O M O M O
M O O O
O O O O M M M O M O O O
M O O O O O O O O O M O M
[TS32.299] [RFC4006] [8.5.11] [TS32.299] [RFC3588] [RFC3588] [RFC4006] [RFC3588] [TS32.299] [RFC4006] [RFC3588] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [8.5.7] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [8.5.7] [RFC4006] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [RFC3588] [RFC3588] [RFC3588] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [RFC3588] [RFC3588] [RFC3588] [TS32.299] [TS32.299] [TS32.299] [RFC4006] [TS32.299] [RFC4006] [RFC3588] [RFC3588] [RFC3588] [RFC4006] [RFC4006] [TS32.299] [8.5.11]
Grouped Unsigned32 Grouped UTF8String DiamIdent DiamIdent Enumerated Time Unsigned32 Integer32 Grouped Enumerated Grouped Grouped Unsigned32 Grouped Grouped UTF8String Grouped Grouped Grouped Grouped Grouped Enumerated Grouped Unsigned32 Unsigned32 Unsigned32 UTF8String DiamIdent DiamIdent Unsigned32 UTF8String Grouped UTF8String Enumerated Grouped Unsigned32 DiamIdent Grouped OctetString Unsigned32 Unsigned32 Grouped Unsigned32 Enumerated Enumerated DiamURI Enumerated Unsigned32 Grouped UTF8String Enumerated Enumerated
V,M M V,M V,M M M M M V,M M M M M M M M V,M V,M V,M V,M V,M V,M M M V,M V,M V,M V,M V,M M M M V,M V,M V,M V,M V,M V,M M M M V,M V,M V,M M V,M M M M M M M V,M M
P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P
V V V V V V V V V V V V V V V V V P,V P,V P,V V V V V V V V V
N Y Y Y N N Y N N Y N Y Y Y Y Y Y N N N N N Y Y N Y Y N N N N N N N N Y Y N N N N N N N Y N Y N N N Y Y N Y
Page 43 (46)
Used In: AVP Code CCR MSCC CCA MSCC Reference Value Type ACR ACA CCR CCA
AVP Flag Rules Should not Must not Must May
AVP Vendor ID
May Encrypt
AVP Name
SI
RequestedServiceUnit ResultCode RouteRecord Scale-Factor ServiceContextId ServiceGenericInformation ServiceIdentifier ServiceInformation ServiceKey SessionId SIPMethod SIPRequestTimestamp SIP-Request-Timestamp-Fraction SIPResponseTimestamp SIP-Response-Timestamp-Fraction SubscriptionId SubscriptionIdData SubscriptionIdType Tariff-Change-Usage Tariff-Information TariffTimeChange TerminatingIOI TerminationCause TimeQuotaThreshold Time-Stamps TotalNumberOfMessages Exploded TotalNumberOfMessagesSent Trigger TriggerType Unit-Cost UnitQuotaThreshold UnitValue UsedServiceUnit UserEquipmentInfo UserEquipmentInfoType UserEquipmentInfoValue UserName ValidityTime ValueDigits VolumeQuotaThreshold
0 0 0 10415 0 10415 0 10415 10415 0 10415 10415 10415 10415 10415 0 0 0 0 10415 0 10415 0 10415 10415 10415 10415 10415 10415 10415 10415 0 0 0 0 0 0 0 0 10415
437 268 282 2059 461 1256 439 873 1114 263 824 834 2301 835 2302 443 444 450 452 2060 451 840 295 868 833 2113 2114 1264 870 2061 1226 445 446 458 459 460 1 448 447 869
O O O M O
M M O
O O O O O O O O O O M M O O O O O O O O O O M M M
O M O M O M M O O M M O
O O O O M O M
M O O M
O O O O O O O O M O M O
[RFC4006] [RFC3588] [RFC3588] [TS32.299] [8.5.11] [8.5.11] [RFC4006] [TS32.299] [TS29.140] [RFC3588] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [TS32.299] [RFC4006] [TS32.299] [RFC3588] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [TS32.299] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [RFC4006] [RFC3588] [RFC4006] [RFC4006] [TS32.299]
Grouped Unsigned32 DiamIdent Grouped UTF8String Grouped Unsigned32 Grouped UTF8String UTF8String UTF8String Time Unsigned32 Time Unsigned32 Grouped UTF8String Enumerated Enumerated Grouped Time UTF8String Enumerated Unsigned64 Grouped Unsigned32 Unsigned32 Grouped Enumerated Grouped Unsigned32 Grouped Grouped Grouped Enumerated OctetString UTF8String Unsigned32 Integer64 Unsigned64
M M M V,M M V,M M V,M V,M M V,M V,M V,M V,M V,M M M M M V,M M V,M M V,M V,M V,M V,M V,M V,M V,M V,M M M M M M V,M
P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P,M P,M P,M P P P P
V V P,V V V V V V V V V V V V V V V V V V
Y N N N Y Y Y N Y Y N N N N N Y Y Y Y N Y N N N N Y Y N N N N Y Y Y Y Y Y Y Y N
Table 11: Summary of AVPs used on CH-1 and CH-2
8.5
8.5.1 8.5.2
OMA Specific AVP Usage

Acct-Application-Id AVP Accounting-Record-Type AVP
Since the protocol used on CH-1 is Diameter Accounting, this AVP shall contain the value of 3 as defined in [RFC3588].
The Accounting-Record-Type AVP (AVP Code 480) is of type Enumerated and contains the type of accounting record being sent. The following values are currently defined for the Accounting-Record-Type AVP: EVENT_RECORD (value 1) for an
Page 44 (46)
Event Based request, START_RECORD (value 2), INTERIM_RECORD (value 3) and STOP_RECORD (value 4) for a Session Based request.
8.5.3 8.5.4
Auth-Application-Id AVP CC-Request-Type AVP
Since the protocol used on CH-2 is Diameter Credit Control, this AVP shall contain the value of 4 as defined in [RFC4006].
The CC-Request-Type AVP (AVP Code 416) is of type Enumerated and contains the reason for sending the credit-control request message. It MUST be present in all Credit-Control-Request messages. The following values are defined for the CCRequest-Type AVP: EVENT_REQUEST (value 4) for an Event Based request, INITIAL_REQUEST (value 1), UPDATE_REQUEST (value 2) and TERMINATION_REQUEST (value 3) for a Session Based request.
8.5.5
DCD-Information AVP
The DCD-Information AVP (AVP code 2115) is of type Grouped. Its purpose is to allow the transmission of service information elements used for DCD services.
<DCD-Information> ::= < AVP Header: 2115 > [ Content-ID] [ Content-provider-ID]
8.5.6
IM-Information AVP
The IM-Information AVP (AVP code 2110) is of type Grouped. Its purpose is to allow the transmission of service information elements used for IM services.
<IM-Information> ::= < AVP Header: 2110 > [ [ [ [ Total-Number-Of-Messages-Sent ] Total-Number-Of-Messages-Exploded ] Number-Of-Messages-Successfully-Sent ] Number-Of-Messages-Successfully-Exploded ]
8.5.7
Multiple-Services-Credit-Control AVP
The Multiple-Services-Credit-Control AVP (AVP code 456) is of type Grouped as specified in [RFC4006]. It contains additional 3GPP and OMA specific charging parameters.
<Multiple-Services-Credit-Control> ::= < AVP Header: 456 > [ [ * [ [ * [ [ * [ [ [ [ [ [ [ Granted-Service-Unit ] Requested-Service-Unit ] Used-Service-Unit ] Tariff-Change-Usage ] Service-Identifier ] Rating-Group ] G-S-U-Pool-Reference ] Validity-Time ] Result-Code ] Final-Unit-Indication ] Time-Quota-Threshold ] Volume-Quota-Threshold] Quota-Holding-Time ]
Page 45 (46)
[ Quota-Consumption-Time ] * [ Reporting-Reason ] [ Trigger ] *[ AVP ]
8.5.8
Requested-Action AVP
The Requested-Action AVP (AVP Code 436) is of type Enumerated and contains the requested action being sent by CreditControl-Request command where the CC-Request-Type is set to EVENT_REQUEST. The following values are defined for the Requested-Action AVP: DIRECT_DEBITING (value 0) for a Direct Debit Request, REFUND_ACCOUNT (value 1) for a Refund Request, CHECK_BALANCE (value 2), and PRICE_ENQUIRY (value 3) for a Price Enquiry Request.
8.5.9
Service-Context-Id AVP
This AVP is of type UTF8String and contains a unique identifier of the Diameter credit-control service specific document that applies to the request. This is an identifier allocated by the service provider, by the service element manufacturer, or by a standardization body, and must uniquely identify a given Diameter credit-control service specific document. The format of the Service-Context-Id is: extensions.Release.service-context @ domain The OMA specific value for domain is openmobilealliance.org. The OMA specific values for the service-context SHALL be derived from the service enabler names. The service enabler MAY use the Release to indicate the OMA Release of the enabler e.g. 1 for version 1.0. Extensions MAY be used to indicate a sub-release or to indicate other implementation details as required. For valid values see section 6.2.45.
8.5.10
Service-Generic-Information AVP
The Service-Generic-Information AVP (AVP code 1256) is of type Grouped refer [TS32.299]. Its purpose is to allow the transmission of additional OMA service/enabler specific information elements which are common to different service/enablers.
<Services-Generic-Information> ::= < AVP Header: 1256 > [ [ [ [ Application-Server-ID ] Application-Service-Type ] Application-Session-ID ] Delivery-Status ]
8.5.11
Service-Information AVP
The Service-Information AVP (AVP code 873) is of type Grouped. Its purpose is to allow the transmission of additional OMA service/enabler specific information elements. The complete ABNF syntax is defined and maintained in [TS32.299]. The format and content of the fields inside the OMA specific Service-Information AVP are specified in the documents which are applicable for the specific service/enabler. Note that the formats of the fields are service/enabler-specific, i.e. the format will be different for the various services/enablers.
Page 46 (46)
Appendix A.
A.1
Reference
Change History
Date
01 Feb 2011
(Informative)
Description
Status changed to Approved by TP: OMA-TP-2011-0018-INP_Charging_Data_V1_0_RRP_for_Final_Approval
Approved Version 1.0 History
OMA-DDS-Charging_Data-V1_0

OMA DDS Charging Data V1!0!20110201 A

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OMA DDS Charging Data V1!0!20110201 A

Enviado por

Direitos autorais:

Formatos disponíveis

Charging Data

Approved Version 1.0 01 Feb 2011

Open Mobile Alliance OMA-DDS-Charging_Data-V1_0-20110201-A

3. Terminology and Conventions

6. OMA Charging Data Description

Offline Charging Requests

Request Type Event Timestamp Service Context Id

Mandatory Optional Mandatory

Delivery Status Subscription Id Subscription Type

Optional Optional Mandatory

OMA Charging Data Element

Subscription Data Correlation Id

Value Digits Exponent Currency Code

Mandatory Optional Optional

Input Octets Output Octets Service Specific Units

Optional Optional Optional

Service Key User Equipment Info User Equipment Info Type

Optional Optional Mandatory

User Equipment Info Value

OMA Charging Data Element

Message Body Content Type Content Length Content Disposition

Optional Mandatory Mandatory Optional

Originator Participant Group Called Party Address Role of Node

Optional Optional Optional Optional

Application Service Type

Calling Party Address

Called Party Address

Application Charging Identifier

OMA Charging Data Element

Total Number of Messages Exploded Number of Messages Successfully Sent

Optional Optional Optional Optional Optional Optional Optional Optional Optional

OMA Charging Data Element

Offline Charging Responses

Result Code Request Type Event Timestamp

Mandatory Mandatory Optional

Table 2: OMA Charging Data Elements in Offline Charging Responses

Online Charging Requests

Request Type Event Timestamp Subscription Id Subscription Type

Mandatory Optional Optional Mandatory

Subscription Data Termination Cause Requested Action

Mandatory Optional Optional

Multiple Service Indicator Multiple Services Credit Control

Requested Service Unit

OMA Charging Data Element

Output Octets Service Specific Units

Used Service Unit

Tariff Change Usage

OMA Charging Data Element

Optional Optional Optional Optional Optional Optional

Rating Group Reporting Reason

Trigger Trigger Type User Equipment Info

Optional Optional Optional

User Equipment Info Type

User Equipment Info Value

OMA Charging Data Element

Optional Optional Mandatory Mandatory Optional

Originator Participant Group Called Party Address Role of Node

Optional Optional Optional Optional

Application Service Type

Calling Party Address

OMA Charging Data Element

Application Charging Identifier

Optional Mandatory Mandatory Optional Optional