6 Definition of AoC Information

32.2803GPPAdvice of Charge (AoC) serviceCharging managementRelease 17Telecommunication managementTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

6.0 General

The following clauses describe an overall AoC Information model that enables the modelling of the various data flowing to and from the AoC Function (ACF). The model is followed by a data structure to be used in the Ro and the Rf reference points. Suggested data mapping to the model is provided in the informative Annex B.

6.1 AoC Information model principles

The AoC Information model is a logical representation of the AoC data internal to the AoC Function (ACF).

The AoC Information model has to adhere to the following principles:

– CAI element mapping ability – The model shall allow the mapping of CAI elements into AoC tariff (according to TS 22.024 [203]).

– UE AoC data mapping ability – The AoC Information model shall allow the mapping of AoC into UE format (according to TS 24.647 [208]) respectively ETSI TS 183 043 [213] according to Annex C2)

– NNI data mapping ability – Be able to map incoming RTTI (according to TS 29.658 [209]) into the AoC Information model

– Protocol data mapping ability – The ability to map Debit / Reserve Units Request and Response (in TS 32.299 [50]) to the AoC Information model. i.e.:

– Input: Service ID – The model shall allow the charging domain selecting tariffs based on the Service ID for offline and online charging.

– Input: Service Units – The model shall allow representing tariffs based on all different unit types (monetary and non-monetary) of Requested Requested-Service-Units for online charging.

– Output: Cost Information – The model shall allow representing determined charges by the charging Domain in Cost Information for offline and online charging.

– Output: Ro data mapping ability – Be able to map information by the charging domain into the AoC Information model.

– Inter Operator Tariff schemes support – The AoC Information model shall support inter operators tariffs (based on TS 22.115 [101]); i.e. absolute add on charges and relative add on charges.

– AoC types – accommodate all AoC service types and AoC service obligatory type data.

6.2 AoC Information model

The AoC Information heading denotes the AoC obligatory type.

AoC Information comprises of two parts:

– the Cost Information e.g. AoC related accumulated and/or incremental cost;

– the Tariff Information for the requested service to be applied onward. A tariff switch time can occur.
The tariff in effect after the switch time can be added to the model.

Figure 6.2.1 depicts the AoC Information model.

The Tariff Information contains the current Tariff and may optionally denote the anticipated Tariff after a Tariff Switch Time.

The Tariff Information may be related to a tariff given by a 3^rd party provider. The Tariff may add additional tariff, change currency or place a mark-up (or discount) on top of the 3^rd party provider Tariff. Thus Tariff Information can be chained numerous of times, based on the business value chain.

Each Tariff defines a Currency Code for monetary tariffs or none when the tariff is metered in non monetary units.

A Tariff may be defined by using multi dimensional rating elements. Each dimension is identified through the Unit Type. Any combination of rating elements can be provided. If a tariff is a mark-up on top of a 3^rd party provider tariff no rating elements are provided in the tariff information model.

Each rating element is comprized of the Unit Type that describes the units to be measured, the number of units (Unit Value), what is the Cost (Cost Value) associated of consuming this number of units and for how many units this rate is applicable (Unit Threshold). Chaining rating elements of the same dimension is possible, as long as a Unit Threshold is provided. The last rating element in the chain may be provided without a Unit Threshold. A rating element without a Unit Threshold denotes that the rate is applicable as long as the Tariff is in effect.

Figure 6.2.1: AoC Information model

6.3 AoC data definition

6.3.1 Ro message contents

6.3.1.1 Summary of AoC message formats

The AoC Service uses the Debit / Reserve Units Request and Debit / Reserve Units Response messages defined in TS 32.299 [50]. AoC service can be used in a request type price enquiry or complementary to regular Debit Units Request as described in clause 5.3.1.

Table 6.3.1.1.1 describes the use of these messages for AoC.

Table 6.3.1.1.1: AoC messages reference table

Message	Source	Destination
Debit / Reserve Units Request	ACF	OCS
Debit / Reserve Units Response	OCS	ACF

6.3.1.2 Structure for the Debit / Reserve Units message formats

6.3.1.2.0 General

This clause describes the information elements used in the Debit / Reserve Units operation messages and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].

6.3.1.2.1 Debit / Reserve Units Request message

Table 6.3.1.2.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from the ACF as used for AoC service.

Table 6.3.1.2.1.1: Debit / Reserve Units Request message content

Information Element	Category	Description
Session Identifier	M	Described in TS 32.299 [50]
Originator Host	M	Described in TS 32.299 [50]
Originator Domain	M	Described in TS 32.299 [50]
Destination Domain	M	Described in TS 32.299 [50]
Operation Identifier	M	Described in TS 32.299 [50]
Operation Token	M	Described in TS 32.299 [50]
Operation Type	M	Described in TS 32.299 [50].
Operation Number	M	Described in TS 32.299 [50]
Destination Host	O_C	Described in TS 32.299 [50]
User Name	O_M	The field contains the Private User Identity described in IETF RFC 2486 [400]
Origination State	O_C	Described in TS 32.299 [50]
Origination Timestamp	O_C	Described in TS 32.299 [50]
Subscriber Identifier	O_M	This field contains the identification of the subscriber (i.e. MSISDN or SIP-URI) that uses the requested service.
Termination Cause	O_C	Described in TS 32.299 [50]
Requested Action	O_C	Described in TS 32.299 [50]
AoC Request Type	O_M	This field denotes if AoC Information is requested and what type of information is needed.
Multiple Operation	O_M	Described in TS 32.299 [50], only used if AoC services is used together with an online charging session.
Multiple Unit Operation	O_C	Described in TS 32.299 [50], only used if AoC services is used together with an online charging session.
Subscriber Equipment Number	O_C	Described in TS 32.299 [50]
Route Information	O_C	Described in TS 32.299 [50]
Service Information	O_M	Described in clause 6.3.2

6.3.1.2.2 Debit / Reserve Units Responsemessage

Table 6.3.1.2.2.1 illustrates the basic structure of a DCCA message as used for the ACF. This message is always used by the OCS as specified below, independent of the receiving ACF and the Debit / Reserve Units Request request type that is being replied to. Service Information is used to send back the AoC Information.

Table 6.3.1.2.2.1: Debit / Reserve Units Response message content

Information Element	Category	Description
Session Identifier	M	Described in TS 32.299 [50]
Operation Result	M	Described in TS 32.299 [50]
Originator Host	M	Described in TS 32.299 [50]
Originator Domain	M	Described in TS 32.299 [50]
Operation Identifier	M	Described in TS 32.299 [50]
Operation Type	M	Described in TS 32.299 [50]
Operation Number	M	Described in TS 32.299 [50]
Operation Failover	O_C	Described in TS 32.299 [50]
Multiple Unit Operation	O_C	Described in TS 32.299 [50]
Operation Failure Action	O_C	Described in TS 32.299 [50]
Redirection Host	O_C	Described in TS 32.299 [50]
Redirection Host Usage	O_C	Described in TS 32.299 [50]
Redirection Cache Time	O_C	Described in TS 32.299 [50]
Route Information	O_C	Described in TS 32.299 [50]
Failed parameter	O_C	Described in TS 32.299 [50]
Service Information	O_C	Described in TS 32.299 [50]

6.3.1.3 Rf message content related to AoC service

6.3.1.3.0 Introduction

The ACF generates charging data transferred to the CDF using the Charging Data transfer operation, as described in the TS 32.299 [50] and the category in the tables are used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].

The Charging Data Request and Charging Data Response are used for this ACF Charging data transfer.

6.3.1.3.1 Charging Data Request message

Table 6.3.1.3.1.1 illustrates the basic structure of a Charging Data Request message as used for ACF Charging data transfer.

Table 6.3.1.3.1.1: Charging Data Request message content

Information Element	Category	Description
Session Identifier	M	Described in 32.299 [50]
Originator Host	M	Described in 32.299 [50]
Originator Domain	M	Described in 32.299 [50]
Destination Domain	M	Described in 32.299 [50]
Operation Type	M	Described in 32.299 [50]
Operation Number	M	Described in 32.299 [50]
Operation Identifier	O_M	Described in 32.299 [50]
User Name	O_C	Described in 32.299 [50]
Destination Host	O_C	Described in 32.299 [50]
Operation Interval	O_C	Described in 32.299 [50]
Origination State	O_C	Described in 32.299 [50]
Origination Timestamp	O_C	This field contains the time when the operation is requested.
Proxy Information	O_C	Described in 32.299 [50]
Route Information	O_C	Described in 32.299 [50]
Operation Token	O_M	Described in 32.299 [50]
Service Information	O_M	This field holds the 3GPP specific AoC Information and is described in clause 6.3.2

6.3.1.3.2 Charging Data Response message

Table 6.3.1.3.2.1 illustrates the basic structure of a Charging Data Response message as used for ACF Charging data transfer.

Table 6.3.1.3.2.1: Charging Data Response message content

Information Element	Category	Description
Session Identifier	M	Described in 32.299 [50]
Operation Result	M	Described in 32.299 [50]
Originator Host	M	Described in 32.299 [50]
Originator Domain	M	Described in 32.299 [50]
Operation Type	M	Described in 32.299 [50]
Operation Number	M	Described in 32.299 [50]
Operation Identifier	O_M	Described in 32.299 [50]
User Name	O_C	Described in 32.299 [50]
Operation Interval	O_C	Described in 32.299 [50]
Origination State	O_C	Described in 32.299 [50]
Origination Timestamp	O_C	Described in 32.299 [50]
Proxy Information	O_C	Described in 32.299 [50]

6.3.2 Definition of Service Information

Table 6.3.2.1.1: Service Information structure

Information Element	Category	Description
Service Information	O_C	This is a structured field and holds the 3GPP specific parameter for AoC service.
IMS Information	O_C	Described in TS 32.260 [20]
Inter Operator Identifier	O_C	Described in TS 32.260 [20]
Originating IOI	O_C	Described in TS 32.260 [20]
Service ID	O_C	Used to identify the third party service
AoC Information	O_C	Described in clause 6.3.3

6.3.3 Definition of AoC Information

6.3.3.0 General

The AoC Information parameter used for AoC is provided in the Service Information parameter.

6.3.3.1 AoC Information assignment for Service Information

The components in the Service Information that are use for AoC can be found in table 6.3.2.1.1.

Table 6.3.3.1.1: AoC Information structure

Information Element	Category	Description
AoC Information	O_C	This is a structured field and holds the 3GPP specific parameter for AoC service.
Tariff Information	O_C	This is a structured field and holds the Tariff specific parameters. The details are defined in clause 6.3.2.2. It can chain inter operator tariff.
AoC Cost Information	O_C	This is a structured field and holds the AoC cost specific parameters. The details are defined in clause 6.3.2.3.
AoC Subscription Information	O_C	Used by the AoC functions to inform the OCS about the AoC Subscription and Formatting parameters received from the HSS. When used by ACF for Charging data transfer as described in clause 6.3.1.3, only "AoC service" is present.

6.3.3.2 Definition of the Tariff Information

Tariff information is provided within the AoC Information.

The detailed structure of the Tariff Information can be found in the table 6.3.3.2.1.

Table 6.3.3.2.1: Tariff Information structure

Information Element	Category	Description
Tariff Information	O_C	This is a grouped field with one of many tariffs
Current Tariff	M	Tariff as defined in table 6.3.2.2-2 for the current time period.
Tariff Time Change	O_C	The tariffs switch time.
Next Tariff	O_C	Tariff as defined in table 6.3.2.2-2 for the next time period.

The detailed structure of a Tariff can be found in the table 6.3.3.2-2.

Table 6.3.3.2.2: Tariff structure

Information Element	Category	Description
Tariff	Oc	This is a grouped field with one of many tariffs
Currency_Code	Oc	Omitted if non-monetary units is used
Scale_Factor	Oc	A scaling factor on the whole calculation. Could be used for example between HPLMN and VPLMN.
Value_Digits	O_M
Exponent	Oc
Rate_Element	Oc	Group of Cost per unit values of unit type.
Charge Reason Code	Oc	Indicates a specific charge type e.g. Usage, AddOn Charge, Set-Up-Charge or Communication-Attempt-Charge
Unit_Type	O_M	The measuring unit; e.g. time, uplink volume, special service units
Unit_Value	O_M	The number of consumed units that incur the charge.
Value_Digits	O_M
Exponent	Oc
Unit_Cost	O_M	The associated Cost (in currency code) to be charged per Unit_value
Value Digits	O_M
Exponent	Oc
Unit_Quota_Threshold	Oc	An upper limit for consumed units where the rate is still valid

For example:

1. A rate of 20c for each Megabyte (total volume) up to 10 Megabyte is depicted as Unit type – TOTAL-OCTETS, Unit Value – 1,048,576, Cost – 20 and Unit threshold – 10,485,760.

2. A rate of 30c per 60s : Cost_Value = 30, Unit_Value =60 assuming appropriate settings for currency and unit_type.

6.3.3.3 Definition of AoC Cost Information

Cost information is provided within the AoC Cost Information.
The AoC Cost Information is only used in CCA and Charging Data Request.

The detailed structure of the AoC Cost Information can be found in the table 6.3.3.3.1.

Table 6.3.3.3.1: Structure of AoC Cost Information

Information Element	Category	Description
Accumulated_Cost	Oc	The ammount charged since the beginning of the session
Value_Digits	O_M
Exponent	Oc
Incremental_Cost	Oc	The ammount charged since the last report.
Value_Digits	O_M
Exponent	Oc
Currency_Code	Oc	Ommited if the ammount is in non-monetary units units

6.4 AoC subscription and formatting parameters

AoC-related subscription and formatting parameters are stored in the HSS and retrieved via Sh (see TS 29.364 [211]).

There are two sets of parameters retrieved from the HSS:

– Subscription based – general parameters pertaining the service registered per subscriber

– Formatting based – UE presentation preferences parameters

The subscription parameters are listed in table 6.4.1. The formatting parameters are listed in table 6.4.2.

Table 6.4.1: AoC subscription parameters

Information Element	Description	Values
AoC Service	A paired list of AoC Service type and AoC Service obligatory type
AoC service type	Defines the type of AoC information to be provided to the subscriber.	AoC-S AoC-D AoC-E None
AoC service obligatory type	Defines whether AoC information is binding or non binding.	AoC for Information (AoCI) AoC for Charging (AoCC)
Preferred AoC currency	Defines the currency preferred by the subscriber	Currency

Table 6.4.2: AoC format parameter

Information Element

Description

Values

AoC format

Defines the format of the AoC information sent to the UE.

Monetary charging Information Element

Non-monetary charging Information Element

Charge Advice Information (CAI)

The following additional rules are applicable for AoC:

– Any combination of AoC service obligatory types and the AoC service types may co-exist.

Annex A (informative):
AoC use cases