6. Definition of charging information

32.2543GPPCharging managementExposure function Northbound Application Program Interfaces (APIs) chargingRelease 17Telecommunication managementTS

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

6.1 Data description for Northbound API offline charging

6.1.1 Rf message contents

6.1.1.1 General

The Exposure Function API offline charging uses the Charging Data Transfer messages Charging Data Request and Charging Data Response defined in TS 32.299 [50].

The Charging Data Request can be of type event and includes all charging information. The Charging Data Response is an acknowledgement of the Charging Data Request.

Table 6.1.1.1.1 describes the use of these messages for offline charging.

Table 6.1.1.1.1: Offline charging messages reference table

Message	Source	Destination
Charging Data Request	SCEF	CDF
Charging Data Response	CDF	SCEF

The following clauses describe the different fields used in the Charging Data messages and the category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1].

6.1.1.2 Charging data request message

Table 6.1.1.2.1 illustrates the basic structure of a Charging Data Request message from the SCEF as used for Exposure Function API offline charging.

Table 6.1.1.2.1: Charging Data Request message contents

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 Type	M	Described in TS 32.299 [50]
Operation Number	M	Described in TS 32.299 [50]
Operation Identifier	O_C	Described in TS 32.299 [50]
User Name	O_C	Described in TS 32.299 [50]
Destination Host	O_C	Described in TS 32.299 [50]
Operation Interval	O_C	Described in TS 32.299 [50]
Origination State	O_C	Described in TS 32.299 [50]
Origination Timestamp	O_C	Described in TS 32.299 [50]
Proxy Information	O_C	Described in TS 32.299 [50]
Route Information	O_C	Described in TS 32.299 [50]
Operation Token	O_M	This field identifies the Exposure Function API domain service.
Service Information	O_M	This field holds the Exposure Function API specific information described in clause 6.3.

NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].

6.1.1.3 Charging data response message

Table 6.1.1.3.1 illustrates the basic structure of a Charging Data Response message as used for Exposure Function API offline charging.

Table 6.1.1.3.1: Charging Data Response message contents

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 Type	M	Described in TS 32.299 [50]
Operation Number	O_C	Described in TS 32.299 [50]
Operation Identifier	O_C	Described in TS 32.299 [50]
Operation Interval	O_C	Described in TS 32.299 [50]
Error Reporting Host	O_C	Described in TS 32.299 [50]
Origination State	O_C	Described in TS 32.299 [50]
Origination Timestamp	O_C	Described in TS 32.299 [50]
Proxy Information	O_C	Described in TS 32.299 [50]

NOTE: Detailed descriptions of the information elements are provided in TS 32.299 [50].

6.1.2 Ga message contents

Refer to clause 5.2.4 for further information.

6.1.3 CDR description on the Bea interface

6.1.3.1 General

The following standard CDRs content and format are considered:

– EA-SCE-CDR generated for exposure function API from the SCEF.

For each of the CDR types, a parameter table, which gives a short description of the parameters, is provided. The category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [1]. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [51].

6.1.3.2 Exposure Function API charging data (EA-SCE-CDR)

Exposure function API record shall be produced for each API invocation to the SCEF. The fields in the record are specified in table 6.1.3.2.1.

Table 6.1.3.2.1: Exposure function API from SCEF charging data (EA-SCE-CDR)

Field	Category	Description
Record Type	M	SCEF exposure function API record.
Retransmission	O_c	This parameter, when present, indicates that information from retransmitted Accounting Requests has been used in this CDR.
Service Context Id	OM	This parameter indicates the CDR is applicable to exposure function API service.
Node Id	O_M_M	Name of the recording entity.
SCEF ID	M	This parameter holds the identity of the SCEF used for this API invocation.
SCEF Address	O_c	This parameter holds the IP address of SCEF.
API Identifier	M	This field holds the identity of API for each API invocation.
TLTRI	O_c	This field holds the T8 Long Term Transaction Reference ID.
SCS/AS Address	M	This field holds the IP address of SCS/AS
Event Timestamp	M	This field holds the time stamp of the event reported.
API Invocation Timestamp		This field holds the time stamp when the API invocation request is submitted to the SCEF from SCS/AS.
API Direction	O_c	This field holds the direction to indicate the API invocation or API notification.
API Network Service Node	O_c	This field holds the identifier of the network element (e.g. SGSN, RCAF)that triggers the API notification as defined in TS 23.682 [243].
API Content	O_c	This field holds the API content (e.g. location, Monitoring Type) used in the T8 transaction for the API invocation request, if available.
API Size	O_c	This field holds the size of API payload.
API Result Code	O_c	This field holds the result of API Invocation.
External Identifier	O_c	This field holds the external Identifier identifying the served party associated to the IMSI or MSISDN or External Group ID, if available.
Local Record Sequence Number	O_M	Consecutive record number created by this node. The number is allocated sequentially including all CDR types.
Record Extensions	O_c	A set of network operator/manufacturer specific extensions to the record. Conditioned upon the existence of an extension.

6.2 Data description for Northbound API online charging

6.2.1 Ro message contents

6.2.1.0 Introduction

The SCEF generates Debit / Reserve Units information that can be transferred from the CTF to the OCF. For this purpose, SCEF online charging utilizes the Debit Units and Reserve Units procedure that is specified in the 3GPP Debit / Reserve Units operation in TS 32.299 [50].

6.2.1.1 Summary of message formats

Table 6.2.1.1.1 describes the use of these messages for SCEF online charging.

Table 6.2.1.1.1: SCEF online charging messages contents

Command-Name	Source	Destination
Debit / Reserve Units Request	SCEF	OCF
Debit / Reserve Units Response	OCF	SCEF

This clause describes the different fields used in the Debit / Reserve Units Request and Debit / Reserve Units Reponses 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].

Detailed descriptions of the fields are provided in TS 32.299 [50].

6.2.1.2 Structure for the Credit-Control message formats

6.2.1.2.1 Debit/Reserve Units Request message

Table 6.2.1.2.1.1 illustrates the basic structure of a Debit / Reserve Units Request message from SCEF as used for exposure function API online charging.

Table 6.2.1.2.1.1: Debit / Reserve Units Request message contents for exposure function API

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_C	Described in TS 32.299 [50]
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. SCS/AS Identifier) that uses the requested service.
Termination Cause	O_C	Described in TS 32.299 [50]
Requested-Action	O_C	This field contains the requested action, used for IEC only.
Multiple Operation	O_M	This field indicate the occurrence of multiple operations.
Multiple Unit Operation	O_C	This field contains the parameter for the quota management.
Proxy Information	O_C	This field contains the parameter of the proxy.
Route Information	O_C	This field contains the parameter of the route.
Service Information	O_M	This field holds the SCEF specific parameter and is described in clause 6.3.

6.2.1.2.2 Debit / Reserve Units Response message

Table 6.2.1.2.2.1 illustrates the basic structure of a Debit / Reserve Units Response message as used for SCEF charging.

This message is always used by the OCS as specified below, independent of the receiving SCEF and the operation type that is being replied to.

Table 6.2.1.2.2.1: Debit / Reserve Units Response message contents for exposure function API

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]
Multiple Unit Operation	O_C	Described in TS 32.299 [50]
Operation Failure Action	O_C	Described in TS 32.299 [50]
Operation Event 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]
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.2a Data description for NEF converged charging

6.2a.1 Message contents

6.2a.1.1 General

The Charging Data Request and Charging Data Response are specified in TS 32.290 [57] and include charging information. The Charging Data Request can be of type [Event, Initial, Termination].

Table 6.2a.1.1.1 describes the use of these messages for converged charging.

Table 6.2a.1.1.1: Converged charging messages reference table

Message	Source	Destination
Charging Data Request	NEF	CHF
Charging Data Response	CHF	NEF

6.2a.1.2 Structure for the converged charging message formats

6.2a.1.2.1 Charging Data Request message

Table 6.2a.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for NEF converged charging.

Table 6.2a.1.2.1.1: Charging Data Request message contents

Information Element	Category	Description
Session Identifier	O_C	Described in TS 32.290 [57]
Subscriber Identifier	O_M	Described in TS 32.290 [57], and holds the identifier of the AF
NF Consumer Identification	M	Described in TS 32.290 [57]
Invocation Timestamp	M	Described in TS 32.290 [57]
Invocation Sequence Number	M	Described in TS 32.290 [57]
Retransmission Indicator	–	This field is not applicable.
One-time Event	O_C	This field indicates, if included, that this is a one-time event and that there will be no update or termination.
One-time Event Type	O_C	Described in TS 32.290 [57].
Notify URI	–	This field is only applicable for the notification of abort charging..
Triggers	O_C	This field is described in TS 32.290 [57] and holds the NEF specific triggers described in clause 5.4.1.x
Multiple Unit Usage	O_C	This field contains the parameters for the quota management request and/or usage reporting.
Rating Group	M	Described in TS 32.290 [57]
Requested Unit	O_C	Described in TS 32.290 [57]
Used Unit Container	O_C	Described in TS 32.290 [57]
NEF API Charging Information	O_M	This field holds the NEF API specific information described in clause 6.3.1.4

6.2a.1.2.2 Charging Data Response message

Table 6.2a.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for NEF converged charging.

Table 6.2a.1.2.2.1: Charging Data Response message content

Information Element	Category	Description
Session Identifier	O_C	Described in TS 32.290 [57]
Invocation Timestamp	M	Described in TS 32.290 [57]
Invocation Result	O_C	Described in TS 32.290 [57]
Invocation Sequence Number	M	Described in TS 32.290 [57]
Session Failover	O_C	Described in TS 32.290 [57]
Triggers	–	This field is notapplicable.
Multiple Unit Information	O_C	This field holds the parameters for the quota management information.
Result Code	O_C	Described in TS 32.290 [57]
Rating Group	O_M	Described in TS 32.290 [57]
Granted Unit	O_C	Described in TS 32.290 [57]
Validity Time	O_C	Described in TS 32.290 [57]

6.2a.2 G_a message contents

Refer to clause 5.4.4.

6.2a.3 CDR description on the B_ea interface

6.2a.3.1 General

This clause describes the CDR content and format generated for NEF converged charging.

The following tables provide a brief description of each CDR parameter. The category in the tables is used according to the charging data configuration defined in clause 5.4 of TS 32.240 [2]. Full definitions of the CDR parameters, sorted by the name in alphabetical order, are provided in TS 32.298 [3].

6.2a.3.2 NEF charging CHF CDR data

If enabled, CHF CDRs for NEF charging shall be produced for NEF chargeable events.

The fields of NEF charging CHF CDR are specified in table 6.2a.3.2.1.

Table 6.2a.3.2.1: NEF charging CHF record data

Field	Category	Description
Record Type	M	Described in TS 32.298 [3]
Recording Network Function ID	O_M	Described in TS 32.298 [3]
Subscriber Identifier	M	This field contains the identification of the API user (e.g. SCS Identifier)
NF Consumer Information	O_C	This field holds the information of the NEF that used the charging service
Triggers	O_C	This field is described in TS 32.298 [3] and holds the NEF specific triggers described in clause 5.4.1.2
List of Multiple Unit Usage	O_M	Described in TS 32.298 [3]
Record Opening Time	O_C	Described in TS 32.298 [3]
Duration	M	Described in TS 32.298 [3]
Record Sequence Number	O_C	Described in TS 32.298 [3]
Cause for Record Closing	M	Described in TS 32.298 [3]
Local Record Sequence Number	O_M	Described in TS 32.298 [3]
Record Extensions	O_C	Described in TS 32.298 [3]
NEF API Charging Information	O_M	This field holds the NEF specific information defined in clause 6.3.1.4

6.3 Northbound API charging specific parameters

6.3.1 Definition of Northbound API charging information

6.3.1.1 Exposure Function API charging information assignment for Service Information

The components in the Service Information that are used for Exposure Function API charging can be found in table 6.3.1.1.1.

Table 6.3.1.1.1: Service Information used for Exposure Function API charging

Information Element	Category	Description
Service Information	O_M	This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50].
Subscriber Identifier	O_M	This field contains the identification of the user (i.e. SCS Identifier).
IMS Information	O_M	This is a structured field and holds IMS specific parameters. The complete structure is defined in TS 32.260 [20].
Node Functionality	O_c	This IE Identifies the type of record.
Exposure Function API Information	O_M	This is a structured field and holds the Exposure Function API specific parameters. The details are defined in clause 6.3.1.2.

6.3.1.2 Definition of the Exposure Function API Information

Exposure Function API specific charging information is provided within the Exposure Function API Information. The fields of the Exposure Function API Information are indicated with the SCEF from which the information is sent.

The detailed structure of the Exposure Function API Information can be found in table 6.3.1.2.1.

Table 6.3.1.2.1: Structure of the Exposure Function API Information

Information Element	Category	Description
Supported Features	O_c	This field holds the list of features supported by the SCEF, CDF or OCF as defined in clause 6.3.1.3.
External Identifier	O_c	This parameter holds the external Identifier identifying the served party associated to the IMSI or MSISDN or External Group ID, if available
SCEF ID	O_c	This parameter holds the Diameter identity of the SCEF used for API invocation.
SCEF Address	O_c	This parameter holds the IP address of SCEF.
API Identifier	O_M	This parameter holds the identity of API
SCS/AS Address	O_M	This parameter holds the IP address of SCS/AS which invoke the API via T8 interface
TLTRI	O_c	This parameter holds T8 Long Term Transaction Reference ID is which refers to long term transaction (e.g. NIDD Configuration, Group Message Request, Monitoring Event configuration) between the SCEF and the SCS/AS when using T8 interface.
Event Timestamp	M	This field holds the time stamp of the event reported.
API Invocation Timestamp	O_c	This parameter holds the time stamp when API Invocation request was submitted to the SCEF from SCS/AS.
API Direction	O_c	This field holds the direction to indicate the API invocation or API notification.
API Network Service Node	O_c	This field holds the identifier the network element (e.g. SGSN, RCAF) that triggers the API notification, as defined in 23.682 [243].
API Content	O_c	This parameter holds the API content (e.g. Location, Monitoring Type) used in the T8 transaction for the API invocation request, if available.
API Size	O_c	This parameter holds size of API payload.
API Result Code	O_c	This parameter holds the result of API Invocation.

6.3.1.3 Supported features

The Supported features information that is used for Exposure Function API charging is based on the information defined for the supported features mechanism specified in clause 6.5.x of TS 32.299 [50].

The following table defines the features applicable for the feature lists with a Feature-List-ID of 1.

Table 6.3.1.3.1: Features of Feature-List-ID 1 used in Exposure Function API charging

Feature bit

Feature

Description

Online/Offline

NAPS-CH

This feature indicates the support Exposure Function API charging.

Both

Feature bit: The order number of the bit within the Feature-List AVP where the least significant bit is assigned number "0".

Feature: A short name that can be used to refer to the bit and to the feature, e.g. "EPS".

Feature in this table is always mandatory since it relates to the charging functionality of a network feature.

Description: A clear textual description of the feature.

6.3.1.4 Definition of the NEF API Information

6.3.1.4.1 Definition of the NEF API Charging Information

Network Exposure Function API specific charging information is provided within the NEF API Charging Information. The detailed structure of the NEF API Charging Information can be found in table 6.3.1.4.1.

Table 6.3.1.4.1: Structure of the NEF API Charging Information

Information Element	Category	Description
External Individual Identifier	O_C	This parameter holds the external Identifier or the MSISDN associated to the GPSI of the individual UE, if available.
External Group Identifier	O_C	This parameter holds the external identifier for a group of individual UE(s), if available.
Internal Group Identifier	O_C	The internal Identifier identifying a group of individual UE(s).
API Direction	M	This field holds the direction to indicate if it is an API invocation from an AF or notification to an AF.
API Target Network Function	O_C	This field holds the identifier of the network function that either is the destination of the API invocation or triggers the notification.
API Result Code	O_C	This parameter holds the result of API Invocation.
API Name	M	This field holds the name of the API invoked.
API Reference	O_C	This field holds the reference to the definition of the format of the API invocation, this can be a URI or refence to the standard where it’s specified
API Content	O_C	This field holds the actual content of the API invocation, in the format described by the API Reference

Editor’s note: The full list of information elements is FFS.

6.3.2 Detailed message format for offline charging

The following clause specifies per Operation Type the charging data that are sent by SCEF for Exposure Function API offline charging.

The Operation Types are listed in the following order: S (Start)/I (Interim)/S (Stop)/E (Event). Therefore, when all Operation Types are possible it is marked as SISE. If only some Operation Types are allowed for a node, only the appropriate letters are used (i.e. SIS or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. SI-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".

Table 6.3.2.1 illustrates the basic structure of the supported fields in the Charging Data Request message for Exposure Function API offline charging.

Table 6.3.2.1: Supported fields in Charging Data Request message

Information Element	Node Type	SCEF
Information Element	Supported Operation Types	S/I/S/E
Session Identifier		—E
Originator Host		—E
Originator Domain		—E
Destination Domain		—E
Operation Type		—E
Operation Number		—E
Operation Identifier		—E
User Name		—E
Destination Host		—E
Operation Interval		—E
Origination State		—E
Origination Timestamp		—E
Proxy Information		—E
Route Information		—E
Operation Token		—E
Subscriber Identifier		—E
Service Information with IMS Information and Exposure Function API Information
Supported Features		—E
Node Functionality		—E
External Identifier		—E
SCEF ID		—E
SCEF Address		—E
TLTRI		—E
API Identifier		—E
SCS/AS Address		—E
Event Timestamp		—E
API Invocation Timestamp		—E
API Direction		—E
API Network Service Node		—E
API Content		—E
API Size		—E
API Result Code		—E

Table 6.3.2.2 illustrates the basic structure of the supported fields in the Charging Data Response message for Exposure function API offline charging.

Table 6.3.2.2: Supported fields in Charging Data Response message

Information Element	Node Type	SCEF
Information Element	Supported Operation Types	S/I/S/E
Session Identifier		—E
Operation Result		—E
Originator Host		—E
Originator Domain		—E
Operation Type		—E
Operation Number		—E
Operation Identifier		—E
Operation Interval		—E
Error Reporting Host		—E
Origination State		—E
Origination Timestamp		—E
Proxy Information		—E
Session Identifier		—E
Service Information with Exposure Function API Information
Supported Features		—E

6.3.3 Detailed message format for online charging

The Operation types are listed in the following order: I [initial] /U [update]/ T [terminate]/E [event]. Therefore, when all Operation types are possible it is marked as IUTE. If only some Operation types are allowed for a node, only the appropriate letters are used (i.e. IT or E) as indicated in the table heading. The omission of an Operation type for a particular field is marked with "-" (i.e. I-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".

Table 6.3.3.1 illustrates the basic structure of the supported fields in the Debit / Reserve Units Request for exposure function API online charging.

Table 6.3.3.1: Supported fields in Debit / Reserve Units Request message

Information Element	Service Type	SCEF
Information Element	Supported Operation Types	I/U/T/E
Session Identifier		—E
Originator Host		—E
Originator Domain		—E
Destination Domain		—E
Operation Identifier		—E
Operation Token		—E
Operation Type		—E
Operation Number		—E
Destination Host		—E
User Name		—E
Origination State		—E
Origination Timestamp		—E
Subscriber Identifier		—E
Termination Cause		—E
Requested Action		—E
Multiple Operation		—E
Multiple Unit Operation		—E
Proxy Information		—E
Route Information		—E
Service Information		—E
Service Information with IMS and Exposure Function API Information
Supported Features		—E
Node Functionality		—E
SCEF Node		—E
SCEF Address		—E
SCS/AS Address		—E
API Identifier		—E
TLTRI		—E
Event Timestamp		—E
API Invocation Timestamp		—E
API Direction		—E
API Network Service Node		—E
API Content		—E
API Size		—E
API Result Code		—E
External Identifier		—E

Table 6.3.3.2 illustrates the basic structure of the supported fields in the Debit / Reserve Units Response for exposure function API online charging.

Table 6.3.3.2: Supported fields in Debit / Reserve Units Response Message

Information Element	Node Type	SCEF
Information Element	Supported Operation Types	I/U/T/E
Session Identifier		—E
Operation Result		—E
Originator Host		—E
Originator Domain		—E
Operation Identifier		—E
Operation Type		—E
Operation Number		—E
Operation Failover		—E
Multiple Unit Operation		—E
Operation Failure Action		—E
Redirection Host		—E
Redirection Host Usage		—E
Redirection Cache Time		—E
Route Information		—E
Failed parameter		—E
Service Information		—E
Service Information with Exposure Function API Information
Supported Features		I—

6.3.4 Detailed message format for converged charging

The Operation types are listed in the following order: I [Initial] / U (Update)/T [Termination]/E [event]. Therefore, when all Operation types are possible it is marked as IUTE. If only some Operation types are allowed for a node, only the appropriate letters are used (e.g. IUT or E) as indicated in the table heading. The omission of an Operation type for a particular field is marked with "-" (e.g. I-E). Also, when an entire field is not allowed in a node the entire cell is marked as "-".

Table 6.3.4.1 illustrates the basic structure of the supported fields in the Charging Data Request for exposure function API online charging.

Table 6.3.4.1: Supported fields in Charging Data Request message

Information Element	Node Type	NEF
Information Element	Supported Operation Types	I/T/U/E
Session Identifier		ITE
Subscriber Identifier		ITE
NF Consumer Identification		ITE
Invocation Timestamp		ITE
Invocation Sequence Number		ITE
Retransmission Indicator		—
One-time Event		–E
One-time Event Type		–E
Notify URI		I–
Triggers		ITE
Multiple Unit Usage		ITE
NEF API Charging Information
External Individual Identifier		ITE
External Group Identifier		ITE
Internal Group Identifier		ITE
API Direction		ITE
API Target Network Function		ITE
API Result Code		ITE
API Name		ITE
API Reference		ITE
API Content		ITE

Table 6.3.4.2 illustrates the basic structure of the supported fields in the Charging Data Response for exposure function API converged charging.

Table 6.3.4.2: Supported fields in Charging Data Response Message

Information Element	Node Type	NEF
Information Element	Supported Operation Types	I/U/T/E
Session Identifier		ITE
Invocation Timestamp		ITE
Invocation Result		ITE
Invocation Sequence Number		ITE
Session Failover		ITE
Triggers		—
Multiple Unit Information		I-E

6.4 Bindings for Northbound API offline charging

This clause aims to describe the mapping between the Service Information fields, AVPs, Ies and CDR parameters for exposure function API online and offline charging.

Table 6.4.1 describes the mapping of the Diameter Accounting AVP, Ies and CDR to the CDR parameters of EA-SCE-CDR.

Table 6.4.1: Bindings of CDR Parameters, Information Elements and AVPs

CDR Parameter	Information Element	AVP
Service Context Id	Service Context Id	Service-Context-Id
	Service Information	Service-Information
	IMS Information	IMS-Information
Record Type	Node Functionality	Node-Functionality
	API invocation Information	API-invocation-Information
–	Supported Features	Supported-Features
External Identifier	External Identifier	External-Identifier
SCEF ID	SCEF ID	SCEF-ID
SCEF Address	SCEF Address	SCEF-Address
SCS/AS Address	SCS/AS Address	SCS/AS- Address
API Identifier	APIIdentifier	API-Identifier
TLTRI	TLTRI	TLTRI
Event Timestamp	Event Timestamp	Event-Timestamp
API Invocation Timestamp	API Invocation Timestamp	API-Invocation-Timestamp
API Direction	API Direction	API-Direction
API Network Service Node	API Network Service Node	API-Network-Service-Node
API Content	API Content	API -Content
API Size	API Size	API-Size
API Result Code	API Result Code	API-Result-Code

6.5 Bindings for NEF Northbound API converged charging

This mapping between the Information Elements, resource attributes and CHF CDR parameters for NEF Northbound API converged charging is described in clause 7 of TS 32.291 [58].

Annex A (normative):
Charging characteristics