6.4 Data description for IMS converged charging
32.2603GPPCharging managementIP Multimedia Subsystem (IMS) chargingRelease 17Telecommunication managementTS
6.4.1 Message contents
6.4.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, Update, Termination].
Table 6.4.1.1.1 describes the use of these messages for converged charging.
Table 6.4.1.1.1: Converged charging messages reference table
Message |
Source |
Destination |
Charging Data Request |
IMS Node |
CHF |
Charging Data Response |
CHF |
IMS Node |
6.4.1.2 Structure for the converged charging message formats
6.4.1.2.1 Charging Data Request message
Table 6.4.1.2.1.1 illustrates the basic structure of a Charging Data Request message as used for IMS converged charging.
Table 6.4.1.2.1.1: Charging Data Request message contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
OC |
Described in TS 32.290 [45] |
Subscriber Identifier |
OM |
Described in TS 32.290 [45] |
NF Consumer Identification |
M |
Described in TS 32.290 [45] |
NF Functionality |
M |
Described in TS 32.290 [45] |
NF Name |
OC |
Described in TS 32.290 [45] |
NF Address |
OC |
Described in TS 32.290 [45] |
NF PLMN ID |
OC |
Described in TS 32.290 [45] |
Invocation Timestamp |
M |
Described in TS 32.290 [45] |
Invocation Sequence Number |
M |
Described in TS 32.290 [45] |
Retransmission Indicator |
OC |
Described in TS 32.290 [45] |
One-time Event |
OC |
Described in TS 32.290 [45] |
One-time Event Type |
OC |
Described in TS 32.290 [45] |
Service Specification Information |
OC |
Described in TS 32.290 [45] |
Supported Features |
OC |
Described in TS 32.290 [45] |
Notify URI |
OC |
Described in TS 32.290 [45] |
Triggers |
OC |
This field is described in TS 32.290 [45] and holds the IMS specific triggers described in clause 5.4 |
Multiple Unit Usage |
OC |
Described in TS 32.290 [45] |
Rating Group |
M |
Described in TS 32.290 [45] |
Requested Unit |
OC |
Described in TS 32.290 [45] |
Used Unit Container |
OC |
Described in TS 32.290 [45] |
Triggers |
OC |
This field is described in TS 32.290 [45] and holds the IMS specific triggers described in clause 5.4 |
IMS Charging Information |
OM |
This field holds the IMS specific information described in clause 6.4.2.2 |
Editor’s Note: The full structure of the charging data request is FFS.
6.4.1.2.2 Charging Data Response message
Table 6.4.1.2.2.1 illustrates the basic structure of a Charging Data Response message as used for IMS converged charging.
Table 6.4.1.2.2.1: Charging Data Response Message Contents
Information Element |
Category |
Description |
---|---|---|
Session Identifier |
OC |
Described in TS 32.290 [45] |
Invocation Timestamp |
M |
Described in TS 32.290 [45] |
Invocation Result |
OC |
Described in TS 32.290 [45] |
Result code |
OC |
Described in TS 32.290 [45] |
Failed parameter |
OC |
Described in TS 32.290 [45] |
Failure Handling |
OC |
Described in TS 32.290 [45] |
Invocation Sequence Number |
M |
Described in TS 32.290 [45] |
Session Failover |
OC |
Described in TS 32.290 [45] |
Triggers |
OC |
Described in TS 32.290 [45] |
Multiple Unit information |
OC |
Described in TS 32.290 [45] |
Result Code |
OC |
Described in TS 32.290 [45] |
Rating Group |
OM |
Described in TS 32.290 [45] |
Granted Unit |
OC |
Described in TS 32.290 [45] |
Validity Time |
OC |
Described in TS 32.290 [45] |
Announcement Information |
OC |
Described in TS 32.281 [41] |
Final Unit Indication |
OC |
Described in TS 32.290 [45] |
IMS Charging Information |
OM |
This field holds the IMS specific information described in clause 6.4.2.2. |
Editor’s Note: The full structure of the charging data response is FFS.
6.4.1a Ga message contents
Refer to clause 5.4.5 for further information.6.4.1b CDR description on the Bi interface
6.4.1b.1 General
This clause describes the CHF CDR content and format generated of IMS converged charging for IMS nodes (i.e. MRFC, IMS-GWF and SIP AS).
The following tables provide a brief description of each CDR parameter of CHF CDR. 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.4.1b.2 IMS converged charging CHF CDR data
The fields of IMS converged charging CHF CDR are specified in table 6.4.1b.2.1.
Table 6.4.1b.2.1: IMS converged charging CHF record data
Field |
Category |
Description |
---|---|---|
Record Type |
M |
CHF record. |
Recording Network Function ID |
OM |
This field holds the name of the recording entity, i.e. the CHF id. |
Subscriber Identifier |
OM |
This field holds the Subscription Permanent Identifier (SUPI) of the served party. This fields should be present except for emergency session. The detail of SUPI is specified in clause 5.9.2 of TS 23.501 [200] |
NF Consumer Information |
M |
This field holds the information of the IMS nodes that used the charging service. |
NF Functionality |
M |
This field contains the function of the node (i.e. MRFC, IMS-GWF and SIP AS) |
NF Name |
OC |
This field holds the name of the IMS Nodes used. |
NF Address |
OC |
This fields holds the IP Address of the IMS Nodes used. |
NF PLMN ID |
OC |
This field holds the PLMN identifier (MCC MNC) of the IMS Nodes. |
List of Multiple Unit Usage |
OM |
This field holds a list of changes in charging |
Rating Group |
OM |
This filed holds the rating group. |
Used Unit Container |
OC |
This field holds the used units and information connected to the reported units. |
Service Identifier |
OC |
This field holds the Service Identifier. |
Triggers |
OC |
This field holds the reason for closing the used unit container. |
Trigger Timestamp |
OC |
This field holds the timestamp of the trigger. |
Time |
OC |
This field holds the amount of used time. |
Service Specific Unit |
OC |
This field holds the amount of used service specific units. |
Event Time Stamps |
OC |
This field holds the timestamps of the event reported in the Service Specific Units, if the reported units are event based. |
Rating Indicator |
OC |
This field indicates if the units have been rated or not. |
Local Sequence Number |
M |
This field holds the container sequence number. |
Record Opening Time |
M |
Time stamp when the CHF opens the records. |
Duration |
M |
Described in TS 32.298 [57]. |
Record Sequence Number |
C |
Described in TS 32.298 [57]. |
Cause for Record Closing |
M |
Described in TS 32.298 [57]. |
Diagnostics |
OM |
Described in TS 32.298 [57]. |
Local Record Sequence Number |
OM |
Described in TS 32.298 [57]. |
Record Extensions |
OC |
Described in TS 32.298 [57]. |
IMS Charging Information |
OM |
This field holds the IMS specific information defined in clause 6.4.2.2. |
6.4.2 Definition of the IMS converged charging information
6.4.2.1 General
The Charging Information parameter used for IMS converged charging is provided in the following clauses.
6.4.2.2 Definition of IMS charging information
IMS specific charging information used for IMS converged charging is provided within the IMS charging Information.
Table 6.4.2.2.1: Structure of IMS Charging Information
Information Element |
Category |
Description |
Event Type |
OC |
This field holds the SIP Method, the content of the SIP "Event" header and the content of the SIP "expires" header when present in the SIP request. |
IMS Node Functionality |
OM |
This field contains the function of the IMS node. |
Role of Node |
OM |
This field specifies whether the IMS node is serving the Originating or the Terminating party. |
User Information |
OM |
Group of user information. |
User Identifier |
OC |
This field contains the public identification of the user (i.e. GPSI). |
User Equipment Info |
OC |
This field uniquely identifies the device (fixed or mobile) of the served user, can be based on SIP instance id. |
User Location Info |
OC |
This field indicates details of where the UE is currently located (access-specific user location information). For MA PDU session, this field holds the user location associated to the 3GPP access |
UE Time Zone |
OC |
This field holds the Time Zone of where the UE is located, if available where the UE currently resides. |
3GPP PS Data Off Status |
OC |
This field holds the 3GPP Data off Status when UE’s 3GPP Data Off status is Activated or Deactivated. |
ISUP Cause |
OC |
This indicates the reason the call was released. |
Serving Node Address |
OC |
This field holds the IP-address of the Node that generated the access Charging ID. |
VLR Number |
OC |
This identifies the international E.164 address of the VLR serving the user. |
MSC Address |
OC |
This identifies the international E.164 address of the MSC that generated the network call reference number. |
User Session ID |
OM |
This field holds the session identifier. For a SIP session the Session-ID contains the SIP Call ID. When the AS acts as B2BUA, the incoming session is identified. |
Outgoing Session ID |
OC |
When the AS acts as B2BUA, the outgoing side session is identified by the Outgoing Session ID which contains the SIP Call ID. |
Session Priority |
OC |
This field contains the priority of the session. |
Calling Party Addresses |
OM |
This field holds the addresses (SIP URI or Tel URI) URI of the party (Public User Identity or Public Service Identity) initiating a session or requesting a service. |
Called Party Address |
OM |
For SIP transactions, except for registration, this field holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction is posted. For registration transactions, this field holds the Public User ID under registration. |
Number Portability routing information |
OC |
This field includes information on number portability after DNS/ENUM request from IMS node in the calling user’s home network. |
Carrier Select routing information |
OC |
This field includes information on carrier select after DNS/ENUM request from IMS node in the calling user’s home network. |
Alternate Charged Party Address |
OC |
The address of an alternate party that is identified by the AS at session initiation, and is charged in place of the calling party. |
Requested Party Address |
OC |
For SIP transactions this field initially holds the address of the party (Public User ID or Public Service ID) to whom the SIP transaction was originally posted. This field is only present if different from the Called Party Address parameter. |
Called Asserted Identities |
OC |
The addresses of the final asserted identity. Present if the final asserted identity is available in the SIP 2xx response. |
Called Identity Change |
OC |
Terminating identity address change and associated time stamp. |
Called Identity |
OC |
Changed terminating identity information received in a SIP UPDATE or SIP RE-INVITE. |
Called Identity Change Time Stamp |
OC |
Time stamp of SIP UPDATE or SIP RE-INVITE with changed terminating identity information. |
Associated URI |
OC |
This field holds a non-barred public user identity (SIP URI or Tel URI) associated to the public user identity under registration and is present for registration transactions. |
Time Stamps |
OC |
This field holds the time of the SIP Request and the time of the response to the SIP Request. |
Application Server Information |
OC |
This field holds the SIP URI(s) of the AS(s) addressed during the session and the called party number (SIP URI, E.164), if an AS determines it. |
Inter Operator Identifier |
OC |
This field holds the identification of the network neighbours (originating and terminating) as exchanged via SIP signalling if available. This field may occur several times. |
IMS Charging Identifier |
OM |
This field holds the IMS Charging Identifier (ICID) as generated by a IMS node for a SIP session. |
Related IMS Charging Identifier |
OC |
This field holds the Related IMS charging identifier when the session is the target access leg in case of access transfer. |
Related IMS Charging Identifier Generation Node |
OC |
This field holds the identifier of the server that generated the Related IMS charging identifier. |
Transit IOI List |
OC |
This field holds the identification of the involved transit networks as exchanged via SIP signalling if available. This field may occur several times. When received from the AS, each occurrence of this field represents transit networks inbound to or outbound from the S-CSCF. |
Early Media Description |
OC |
This field holds session and media parameters related to media components set to active during the SIP session establishment and before a final successful or unsuccessful SIP answer to the initial SIP INVITE request is received. Once a media component is set to active, subsequent status changes shall be registered. Since several SDP negotiations may occur during the SIP session establishment, this field may occur several times. |
SDP Session Description |
OC |
This field holds the content of an "attribute-line" (i=, c=, b=, k=, a=, etc.) related to a session. |
SDP Media Component |
OC |
This is a grouped field comprising several sub-fields associated with one media component. Since several media components may exist for a session in parallel these sub-fields may occur several times. |
Served Party IP Address |
OC |
This field holds the IP address of either the calling or called party, depending on whether the P-CSCF is in touch with the calling or the called party. |
Server Capabilities |
OC |
This field contains the server capabilities as described in 3GPP TS 29.229 [205]. |
Trunk Group ID |
OC |
This field identifies the incoming and outgoing PSTN legs. |
Bearer Service |
OC |
This field holds the used bearer service for the PSTN leg. |
Service Id |
OC |
This field identifies the service the MRFC is hosting. For conferences the conference ID is used as the value of this parameter. |
Message Bodies |
OC |
This field holds information about the Message body, Content-Type, Content-Length, Content-Disposition and Originator if available. |
Access Network Information |
OC |
This field contains the content of the first P-header P-Access-Network-Info, if available. |
Additional Access Network Information |
OC |
This field contains the content of an additional SIP P-header "P-Access-Network-Info", if available. |
Cellular Network Information |
OC |
This field contains the content of one SIP "Cellular-Network-Info" header, when the UE supporting one or more cellular radio access technologies but using a non-cellular IP-CAN, such as untrusted WLAN access, provides this header field to relay information to its service provider about the radio cell identity of the cellular radio access network on which the UE most recently camped. |
Access Transfer Information |
OC |
This field contains information related to the session transfer. |
Access Network Info Change |
OC |
This field is a grouped field describing the subsequent SIP P-header "P-Access-Network-Info" changes and associated time stamp. |
IMS Communication Service ID |
OC |
This field contains the IMS communication service identifier if received in the P-Asserted-Service header in the SIP request for all applicable IMS nodes downstream from the S‑CSCF serving the Originating party. This field contains the IMS communication service identifier if received in the "+g.3gpp.icsi-ref" header field parameter of the Feature-Caps header in the SIP response for all applicable IMS nodes upstream from the S‑CSCF serving the Originating party. |
IMS Application Reference ID |
OC |
This field contains the IMS application reference identifier if received in the SIP Request. |
Cause Code |
OC |
This field contains the cause value. |
Reason Header |
OC |
This field contains SIP reason header included in BYE or CANCEL method, Reliability of this information is not guaranteed if the SIP or CANCEL is originated outside of the trust domain which is determined by the Operator on a "per parameter basis". Since several Reason Header may exist for a SIP message, these sub-fields may occur several times |
Initial IMS Charging Identifier |
OC |
This field holds the Initial IMS charging identifier (ICID) as generated by the IMS node for the initial SIP session created for IMS service continuity. |
NNI Information |
OC |
This field holds information about the NNI used for interconnection and roaming. |
From Address |
OM |
Contains the information from the SIP From header. |
IMS Emergency Indication |
OC |
This field indicates the registration is an emergency registration or the IMS session is an IMS emergency session |
IMS Visited Network Identifier |
OC |
Contains the information from the SIP P-Visited-Network-ID header. |
SIP Route header received |
OC |
Contains the information in the topmost route header in a received initial SIP INVITE or non-session related SIP MESSAGE request. |
SIP Route header transmitted |
OC |
Contains the information in the route header representing the destination in a transmitted initial SIP INVITE or non-session related SIP MESSAGE request. |
TAD Identifier |
OC |
This field indicates the type of access network (CS or PS) through which the session shall be terminated. |
FE Identifier List |
OC |
This element contains one or more IM CN subsystem functional entity addresses and/or AS and application identifiers where the IM CN subsystem functional entity does create charging information for the related CDR of this IM CN subsystem functional entity. |
6.4.2.3 Detailed message format for converged charging
The following clause specifies per Operation Type the charging data that are sent by IMS node for IMS 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 (i.e. IUT or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. I-TE). Also, when an entire field is not allowed in a node the entire cell is marked as "-".
Table 6.5.3.1 defines the basic structure of the supported fields in the Charging Data Request message for IMS converged charging.
Table 6.4.2.3.1: Supported fields in Charging Data Request message
Information Element |
Node Type |
IMS Node |
---|---|---|
Supported Operation Types |
IUTE |
|
Session Identifier |
-UTE |
|
Subscriber Identifier |
IUTE |
|
NF Consumer Identification |
IUTE |
|
Invocation Timestamp |
IUTE |
|
Invocation Sequence Number |
IUTE |
|
Retransmission Indicator |
IUT- |
|
Notify URI |
IU– |
|
Supported Features |
IU-E |
|
Service Specification Information |
IUTE |
|
Triggers |
-UT- |
|
Multiple Unit Usage |
IUT E |
|
Rating Group |
IUT E |
|
Requested Unit |
IU– |
|
Used Unit Container |
-UT E |
|
Triggers |
-UT E |
|
IMS Charging Information |
IUTE |
|
Event Type |
IUTE |
|
IMS Node Functionality |
IUTE |
|
Role of Node |
IUTE |
|
User Information |
IUTE |
|
User Identifier |
IUTE |
|
User Equipment Info |
IUTE |
|
User Location Info |
IUTE |
|
UE Time Zone |
IUTE |
|
3GPP PS Data Off Status |
—E |
|
ISUP Cause |
–TE |
|
Serving Node Address |
IU– |
|
VLR Number |
I–E |
|
MSC Address |
I–E |
|
User Session ID |
IUTE |
|
Outgoing Session ID |
IUTE |
|
Session Priority |
I–E |
|
Calling Party Address |
IUTE |
|
Called Party Address |
IUTE |
|
Number Portability routing information |
I–E |
|
Carrier Select routing information |
I–E |
|
Alternate Charged Party Address |
IUTE |
|
Requested Party Address |
I–E |
|
Called Asserted Identity |
-U-E |
|
Called Identity Change |
-U– |
|
Called Identity |
-U– |
|
Called Identity Change Time Stamp |
-U– |
|
Associated URI |
—E |
|
Time Stamps |
IUTE |
|
Application Server Information |
IUTE |
|
Inter Operator Identifier |
IUTE |
|
IMS Charging Identifier |
IUTE |
|
Related IMS Charging Identifier |
IUTE |
|
Related IMS Charging Identifier Generation Node |
IUTE |
|
Transit IOI List |
IUTE |
|
Early Media Description |
I–E |
|
SDP Session Description |
IU– |
|
SDP Media Component |
IU– |
|
Served Party IP Address |
IUTE |
|
Server Capabilities |
IUTE |
|
Trunk Group ID |
IUTE |
|
Bearer Service |
IUTE |
|
Service Id |
IUT- |
|
Message Bodies |
IUTE |
|
Access Network Information |
IUTE |
|
Additional Access Network Information |
IUTE |
|
Cellular Network Information |
IUTE |
|
Access Transfer Information |
IU– |
|
Access Network Info Change |
-U– |
|
IMS Communication Service ID |
-U– |
|
IMS Application Reference ID |
I–E |
|
Cause Code |
–TE |
|
Reason Header |
–TE |
|
Initial IMS Charging Identifier |
IUTE |
|
NNI Information |
I-TE |
|
From Address |
IUTE |
|
IMS Emergency Indication |
IUTE |
|
IMS Visited Network Identifier |
IUTE |
|
SIP Route header received |
I–E |
|
SIP Route header transm-tted |
I–E |
|
TAD Identifier |
IU– |
|
FE Identifier List |
IUTE |
Table 6.4.2.3.1 defines the basic structure of the supported fields in the Charging Data Response message for IMS converged charging.
Table 6.4.2.3.2: Supported fields in Charging Data Response message
Information Element |
Node Type |
IMS Node |
---|---|---|
Supported Operation Types |
IUTE |
|
Session Identifier |
IUTE |
|
Invocation Timestamp |
IUTE |
|
Invocation Result |
IUTE |
|
Invocation Sequence Number |
IUTE |
|
Session Failover |
I— |
|
Triggers |
– |
|
Multiple Unit information |
I–E |
|
Result Code |
IU-E |
|
Rating Group |
IU– |
|
Granted Unit |
IU– |
|
Validity Time |
IU– |
|
Final Unit Indication |
IU– |
6.4.2.4 Formal IMS converged charging parameter description
6.4.2.4.1 IMS charging CHF CDR parameters
The detailed definitions, abstract syntax and encoding of the IMS charging CHF CDR parameters are specified in TS 32.298 [51].
6.4.2.2.2 IMS charging resources attributes
The detailed definitions of resources attributes used for IMS charging are specified in TS 32.291 [58].
Annex A (informative):
Bibliography
This Annex is a placeholder for documents which are not explicitly cited in this specification.
Annex B (informative):
Message flows for service termination by OCS