C.2 AoC Information mapping to charging Information Elements

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

Herby is a conceptual mapping advising how to populate the charging Information Element provided to the UE (as described in TS 24.647 [208] and ETSI TS 183 043 [213] as explicitly mentioned in the table C.2.1 below) out of the AoC Information.

Table C.2.1: AoC Information mapping

Information Element

Mapping guidance

Expressing Charging Rates
  • Price per time unit

When only one Rate Element with Unit Type = TIME exists
  • Free of charge

When only one Rate Element with Unit Type = MONEY and Unit Value = 0 exists
  • Flat rate

When only one Rate Element with Unit Type = MONEY and Unit Value > 0 exists
  • Not available

No Rate Elements provided

Charged Items
  • Basic communication

When the Rate Element contains Charge Reason Code = Usage or no Charge Reason Code is available.

NOTE: If no other Charged Items are applicable, Basic Communication shall be used as default value
  • Communication attempt

This parameter may be populated when the Rate Element contains Charge Reason Code = Communication Attempt Charge

NOTE: Alternatively, this information may be mapped into "Operation of service" (see below).
  • Communication setup

This parameter may be populated when the Rate Element contains Charge Reason Code= Set Up Charge

NOTE: Alternatively, this information may be mapped into "Operation of service" (see below).
  • Operation of service

This parameter may be populated depending on Service specific Information or when the Rate Element contains Charge Reason Code <> Usage.

NOTE: If this parameter is populated depending on the Charge Reason Code, Communication Attempt and Communication setup shall not be used.
  • pes_aoc-s_phase_duration

The value of Unit_Quota_Threshold is mapped into pes_aoc-s_phase_duration when the AoC Extended XML schema is needed (see ETSI TS 183 043 [213])

Recorded Charges

Accumulated cost in AoC Cost Information

NOTE 1: Other legacy Charging Information Elements (e.g. Special charging code, Special charging arrangement and Billing Identification) are not supported in IMS.

NOTE 2: In the case when the UNI interface can’t transfer the incremental cost, then the user part can calculate it by deducting the previous accumulated cost information from the current accumulated cost information.

‘Additionally, the parameters in table C.2.2 are not supported by the Ro interface but locally configurable by operators.

Table C.2.2: AoC Information mapping – not supported

Type of Charging

This parameter is part of the AoC UNI XML information described in TS 24.647 [208].

Granularity

This parameter is part of the AoC UNI XML information described in TS 24.647 [208].

Pes-transitioning behaviour

This parameter is part of the AoC Extended XML schema described in ETSI TS 183 043 [213].