6.3 IMS charging specific parameters
32.2603GPPCharging managementIP Multimedia Subsystem (IMS) chargingRelease 17Telecommunication managementTS
6.3.1 Definition of IMS charging information
6.3.1.0 General
The IMS Information parameter used for IMS charging is provided in the Service Information parameter.
6.3.1.1 IMS charging information assignment for Service Information
The components in the Service Information that are use for IMS charging can be found in Table 6.3.1.1.1.
Table 6.3.1.1.1: Service Information used for IMS charging
Information Element |
Category |
Description |
Provided by IMS NE |
|
Service Information |
OM |
This is a structured field and holds the 3GPP specific parameter as defined in TS 32.299 [50]. For IMS Charging the IMS Information is used. |
All |
|
Subscriber Identifier |
OM |
Described in TS 32.299 [50] and contains the Public User Identity/Identities, if offline charging applies. |
Not in IBCF nor I-CSCF nor MGCF nor BGCF nor TF |
|
IMS Information |
OM |
This is a structured field and holds the IMS specific parameters. The details are defined in clause 6.3.1.2. |
All |
|
PS Information |
OC |
This is a structured field and holds PS specific parameters. The complete structure is defined in TS 32.251 [11]. |
All |
|
GGSN Address |
OC |
This field holds the IP-address of the Node that generated the access Charging ID, as described in [1]. |
Not in I-CSCF nor MGCF nor BGCF nor IBCF |
|
User Location Info |
OC |
This field contains the network provided location information for 3GPP accesses, if available. |
Not in MGCF nor BGCF nor TF |
|
MS Time Zone |
OC |
This field indicates the offset between universal time and local time in steps of 15 minutes of where the MS currently resides. |
Not in MGCF |
|
Subscriber Equipment Number |
OC |
This field contains the identification of the mobile device (i.e., IMEI) that the subscriber is using. Note: In TS 32.251 [11], this is identified as User Equipment Info within PS Information. |
P-CSCF, S-CSCF, AS |
|
3GPP PS Data Off Status |
Oc |
This field holds the 3GPP PS Data Off Status associated with the registration, as defined in TS 23.228 [201], when available. |
AS |
|
VCS Information |
OC |
This is a structured field and holds VCS specific parameters. The complete structure is defined in TS 32.276 [36]. |
MGCF,AS |
|
ISUP Cause |
OC |
This indicates the reason the call was released. |
MGCF |
|
VLR Number |
OC |
This identifies the international E.164 address of the VLR serving the user. |
AS |
|
MSC Address |
OC |
This identifies the international E.164 address of the MSC that generated the network call reference number. |
AS |
6.3.1.2 Definition of the IMS Information
IMS specific charging information is provided within the IMS Information. The fields of the IMS Information which are differently covered in several IMS network nodes are indicated by the node specific type.
The detailed structure of the IMS Information can be found in table 6.3.1.2.1.
Table 6.3.1.2.1: Structure of the IMS Information
Information Element |
Category |
Description |
Provided by IMS NE |
---|---|---|---|
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. |
All |
Node Functionality |
M |
This field contains the function of the node. |
All |
Role of Node |
OM |
This field specifies whether the IMS node is serving the Originating or the Terminating party. |
Not in MRFC |
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. |
All |
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. |
AS |
Session Priority |
OC |
This field contains the priority of the session. |
All |
Calling Party Address |
OM |
This field holds the address (SIP URI or Tel URI) URI of the party (Public User Identity or Public Service Identity) initiating a session or requesting a service. |
All |
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. |
All |
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. |
S-CSCF, I-CSCF, AS, MGCF, BGCF, TF, TRF |
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. |
S-CSCF, I-CSCF, AS, MGCF, BGCF, TF, TRF |
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. |
AS |
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. |
S-CSCF, P-CSCF, E-CSCF, AS,MRFC, TF, TRF, ATCF |
Called Asserted Identity |
OC |
The address of the final asserted identity. Present if the final asserted identity is available in the SIP 2xx response. |
S-CSCF, |
Called Identity Change |
OC |
Terminating identity address change and associated time stamp. |
S-CSCF, P‑CSCF, E‑CSCF, AS, TF, TRF, ATCF |
Called Identity Change Time Stamp |
OC |
Time stamp of SIP UPDATE or SIP RE-INVITE with changed terminating identity information. |
S-CSCF, P‑CSCF, E‑CSCF, AS, TF, TRF, ATCF |
Called Identity |
OC |
Changed terminating identity information received in a SIP UPDATE or SIP RE-INVITE. |
S-CSCF, P‑CSCF, E‑CSCF, AS, TF, TRF, ATCF |
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. |
S-CSCF, P-CSCF, I-CSCF, IBCF |
Time Stamps |
OC |
This field holds the time of the SIP Request and the time of the response to the SIP Request. |
All |
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. |
S-CSCF, |
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. |
All |
IMS Charging Identifier |
OM |
This field holds the IMS Charging Identifier (ICID) as generated by a IMS node for a SIP session. |
All |
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. |
P-CSCF, AS, ATCF |
Related IMS Charging Identifier Generation Node |
OC |
This field holds the identifier of the server that generated the Related IMS charging identifier. |
P-CSCF, AS, ATCF |
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. |
Not in E-CSCF nor I-CSCF nor ATCF |
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. |
Not in I-CSCF nor BGCF |
SDP Session Description |
OC |
This field holds the content of an "attribute-line" (i=, c=, b=, k=, a=, etc.) related to a session. |
Not in I-CSCF |
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. |
Not in I-CSCF nor BGCF |
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. |
P-CSCF |
Server Capabilities |
OC |
This field contains the server capabilities as described in 3GPP TS 29.229 [205]. |
I-CSCF |
Trunk Group ID |
OC |
This field identifies the incoming and outgoing PSTN legs. |
MGCF |
Bearer Service |
OC |
This field holds the used bearer service for the PSTN leg. |
MGCF |
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. |
MRFC |
Service Specific Info |
OC |
This field contains service specific data if and as provided by an AS. |
AS |
Message Bodies |
OC |
This field holds information about the Message body, Content-Type, Content-Length, Content-Disposition and Originator if available. |
Not in I-CSCF |
Access Network Information |
OC |
This field contains the content of one P-header P-Access-Network-Info, if available. |
Not in TF nor TRF |
Additional Access Network Information |
OC |
This field contains the content of an additional SIP P-header "P-Access-Network-Info", if available. |
Not in TF nor TRF |
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. |
Not in TF nor TRF |
Access Transfer Information |
OC |
This field contains information related to the session transfer. |
AS, ATCF |
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. |
S-CSCF, |
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. |
S-CSCF, |
IMS Application Reference ID |
OC |
This field contains the IMS application reference identifier if received in the SIP Request. |
P-CSCF |
Cause Code |
OC |
This field contains the cause value. |
All |
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 |
All |
Real Time Tariff Information |
OC |
This field holds the tariff/add-on charge received. |
S-CSCF, IBCF, MGCF, AS |
Online Charging Flag |
OC |
This field indicates the Online Charging Request was sent based on the provided ECF address from the SIP P-header "P-Charging-Function-Addresses". NOTE: No proof that online charging action has been taken |
S-CSCF, |
Account Expiration |
OC |
This field indicates the subscriber account expiration date and time of day. |
OCS |
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. |
AS, ATCF |
NNI Information |
OC |
This field holds information about the NNI used for interconnection and roaming. |
P-CSCF, S-CSCF, BGCF, AS |
From Address |
OM |
Contains the information from the SIP From header. |
Not in TRF |
IMS Emergency Indication |
OC |
This field indicates the registration is an emergency registration or the IMS session is an IMS emergency session |
P-CSCF, S-CSCF, I-CSCF |
IMS Visited Network Identifier |
OC |
Contains the information from the SIP P-Visited-Network-ID header. |
P-CSCF, |
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. |
P-CSCF, S-CSCF, IBCF, TRF, ATCF, TF |
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. |
P-CSCF, S-CSCF, I-CSCF, ATCF, TF |
Instance Id |
OC |
This field uniquely identifies the device (fixed or mobile) of the served user. |
P-CSCF, S-CSCF, AS |
TAD Identifier |
OC |
This field indicates the type of access network (CS or PS) through which the session shall be terminated. |
AS |
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. |
All |
6.3.2 Detailed message format for offline charging
The following clause specifies per Operation Type the charging data that are sent by each of the IMS Network Elements for:
– IMS session and IMS event (S/I/S/E)
S-CSCF, E-CSCF, P-CSCF, MGFC, AS, IBCF, TRF, ATCF, TF
– IMS session only (S/I/S)
MRFC
– IMS event only (E)
I-CSCF, BGCF
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 IMS offline charging.
Table 6.3.2.1: Supported fields in Charging Data Request message
Information Element |
Node Type |
S-CSCF |
E-CSCF |
P-CSCF |
I-CSCF |
MRFC |
MGCF |
BGCF |
AS |
IBCF |
TF |
TRF |
ATCF |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
E |
S/I/S |
S/I/S/E |
E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Originator Node |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Originator Domain |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Destination Domain |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Operation Type |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Operation Number |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Operation Identifier |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
User Name (see note1) |
SISE |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
SISE |
|
Destination Host |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Operation Interval |
SIS- |
SIS- |
SIS- |
– |
SIS |
SIS- |
‑ |
SIS- |
SIS- |
SIS- |
SIS- |
SIS- |
|
Origination State |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Origination Timestamp |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Proxy Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Route Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Operation Token |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Subscriber Identifier |
SISE |
SISE |
SISE |
– |
SIS |
– |
– |
SISE |
– |
– |
SISE |
SISE |
|
Service Information with PS, IMS and VCS Information |
|||||||||||||
Event Type |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Role of Node |
SISE |
SISE |
SISE |
E |
— |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Node Functionality |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
User Session Id |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Outgoing Session ID |
– |
– |
– |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
|
Session Priority |
S–E |
S–E |
S–E |
E |
S– |
S–E |
E |
S–E |
S–E |
S–E |
S–E |
S–E |
|
Calling Party Address |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Called Party Address |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Number Portability routing information |
S–E |
– |
– |
E |
– |
S–E |
E |
S–E |
– |
S–E |
S–E |
– |
|
Carrier Select routing information |
S–E |
– |
– |
E |
– |
S–E |
E |
S–E |
– |
S–E |
S–E |
– |
|
Alternate Charged Party Address |
– |
– |
– |
– |
– |
– |
– |
S— |
– |
– |
– |
– |
|
Requested Party Address |
S–E |
S–E |
– |
– |
S– |
– |
– |
SISE |
– |
S–E |
S–E |
SISE |
|
Called Asserted Identity |
S–E |
S–E |
S–E |
– |
S– |
– |
– |
S–E |
– |
S–E |
S–E |
S–E |
|
Called Identity Change |
-I– |
-I– |
-I– |
– |
– |
– |
– |
-I– |
– |
-I– |
-I– |
-I– |
|
Called Identity Change Time Stamp |
-I– |
-I– |
-I– |
– |
– |
– |
– |
-I– |
– |
-I– |
-I– |
-I– |
|
Called Identity |
-I– |
-I– |
-I– |
– |
– |
– |
– |
-I– |
– |
-I– |
-I– |
-I– |
|
Associated URI |
—E |
– |
—E |
E |
– |
– |
– |
– |
—E |
– |
– |
– |
|
Time stamps |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Application server Information |
SISE |
SISE |
– |
– |
SIS |
– |
– |
– |
– |
SISE |
SISE |
– |
|
Inter Operator Identifiers |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Transit IOI List |
SISE |
– |
SISE |
– |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
– |
|
IMS Charging Identifier |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Related IMS Charging Identifier |
– |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
SISE |
|
Related IMS Charging Identifier Generation Node |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
SISE |
||
Early Media Description |
S–E |
S–E |
S–E |
– |
S– |
S–E |
– |
S–E |
S–E |
S–E |
S–E |
S–E |
|
SDP Session Description |
SI-E |
SI-E |
SI-E |
– |
SI-E |
SI-E |
– |
SI-E |
SI-E |
SI-E |
SI-E |
SI-E |
|
SDP Media Component |
SI-E |
SI-E |
SI-E |
– |
SI-E |
SI-E |
– |
SI-E |
SI-E |
SI-E |
SI-E |
SI-E |
|
GGSN Address |
SI– |
SI– |
SI– |
– |
SI– |
SI– |
– |
SI– |
– |
– |
– |
SI– |
|
User Location Info |
SISE |
SISE |
SISE |
E |
SIS |
– |
– |
SISE |
SISE |
– |
SISE |
SISE |
|
MS Time Zone |
SISE |
SISE |
SISE |
E |
SIS |
– |
– |
SISE |
SISE |
– |
SISE |
SISE |
|
Served Party |
– |
– |
SISE |
– |
– |
– |
– |
– |
– |
– |
– |
– |
|
Server Capabilities (see note 1) |
– |
– |
– |
E |
– |
– |
– |
– |
– |
– |
– |
– |
|
Trunk Group ID |
– |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
– |
– |
|
Bearer Service |
– |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
– |
– |
|
Service Id |
– |
– |
– |
– |
SIS |
– |
– |
– |
– |
– |
– |
– |
|
Service Specific Info (see note 1) |
– |
– |
– |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
|
Message Bodies (see note 2) |
SISE |
SISE |
SISE |
– |
– |
SISE |
– |
SISE |
SISE |
SISE |
SISE |
SISE |
|
Cause Code |
–SE |
–SE |
–SE |
E |
–S |
–SE |
E |
–SE |
–SE |
–SE |
–SE |
–SE |
|
Reason Header |
–SE |
–SE |
–SE |
E |
–S |
–SE |
E |
–SE |
–SE |
–SE |
–SE |
–SE |
|
ISUP Cause |
– |
– |
– |
– |
– |
–SE |
– |
– |
– |
– |
– |
– |
|
Access Network Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
– |
– |
SISE |
|
Additional Access Network Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
– |
– |
SISE |
|
Cellular Network Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
– |
– |
SISE |
|
VLR Number |
– |
– |
– |
– |
– |
– |
– |
S–E |
– |
– |
– |
– |
|
MSC Address |
– |
– |
– |
– |
– |
– |
– |
S–E |
– |
– |
– |
– |
|
IMS Communication Service ID |
S–E |
S–E |
S–E |
– |
– |
– |
– |
S–E |
S–E |
S–E |
S–E |
S–E |
|
IMS Application Reference ID |
– |
– |
S–E |
– |
– |
– |
– |
– |
– |
– |
– |
– |
|
Real Time Tariff Information |
SI-E |
– |
– |
– |
– |
SI-E |
– |
SI-E |
SI-E |
– |
– |
– |
|
Initial IMS Charging Identifier |
– |
– |
– |
– |
– |
– |
– |
SISE |
– |
– |
– |
SISE |
|
NNI Information |
S–E |
– |
S–E |
– |
– |
– |
E |
S –E |
S–E |
S–E |
S–E |
–S- |
|
From Address |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
– |
SISE |
|
Access Network Info Change |
-I– |
-I– |
-I– |
– |
-I– |
-I– |
– |
-I– |
-I– |
– |
– |
– |
|
Access Transfer Information |
– |
– |
– |
– |
– |
– |
– |
SI– |
– |
– |
– |
SI– |
|
IMS Emergency Indication |
SISE |
– |
SISE |
E |
– |
– |
– |
– |
– |
– |
– |
– |
|
IMS Visited Network Identifier |
SISE |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
|
Route Header Received |
S–E |
– |
S–E |
E |
– |
– |
– |
– |
S–E |
S–E |
S–E |
S–E |
|
Route Header Transmitted |
S–E |
– |
S–E |
E |
– |
– |
– |
– |
– |
S–E |
– |
S—E |
|
Subscriber Equipment Number |
SISE |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
|
Instance Id |
SISE |
– |
SISE |
– |
– |
– |
– |
SISE |
– |
– |
– |
– |
|
TAD Identifier |
– |
– |
– |
– |
– |
– |
– |
S— |
– |
– |
– |
– |
|
3GPP PS Data Off Status |
– |
– |
– |
– |
– |
– |
– |
E |
– |
– |
– |
– |
|
FE Identifier List |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
SISE |
|
NOTE 1: Only present if available in the CTF of the IMS node. NOTE 2: Present only if Messages Bodies is included in the SIP message that triggered the Charging Data Request. NOTE 3: Only present if Charging Data Request is triggered on a SIP message (e.g. SIP INVITE, SIP UPDATE). NOTE 4: To be determined for presence in IBCF. NOTE 5: Only present if Charging Data Request is triggered on SIP REGISTER 200 OK. |
Table 6.3.2.2 illustrates the basic structure of the supported fields in the Charging Data Response message for IMS offline charging.
Table 6.3.2.2: Supported fields in Charging Data Response message
Information Element |
Node Type |
S-CSCF |
E-CSCF |
P-CSCF |
I-CSCF |
MRFC |
MGCF |
BGCF |
AS |
IBCF |
TRF |
ATCF |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Supported Operation Types |
S/I/S/E |
S/I/S/E |
S/I/S/E |
E |
S/I/S |
S/I/S/E |
E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
S/I/S/E |
|
Session Identifier |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Originator Node |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Originator Domain |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Destination Domain |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Operation Type |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Operation Number |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Operation Identifier |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
User Name |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Operation Interval |
SI– |
SI– |
SI– |
– |
SI- |
SI– |
– |
SI– |
SI– |
SI– |
SI– |
|
Origination State |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Origination Timestamp |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Proxy Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
|
Route Information |
SISE |
SISE |
SISE |
E |
SIS |
SISE |
E |
SISE |
SISE |
SISE |
SISE |
6.3.3 Detailed message format for online charging
The following table specifies per Operation Type the charging data that are sent by each of the IMS Network Elements for:
– IMS session and IMS event (I/U/T/E)
IMS-GWF, AS
– IMS session only (I/U/T)
MRFC
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. IUT or E) as indicated in the table heading. The omission of an Operation Type for a particular field is marked with "-" (i.e. IU-E). Also, when an entire filed is not allowed in a node the entire cell is marked as "-".
Note that not for all structured fields the individual field members are listed in the table. Detailed descriptions of the fields are provided in TS 32.299 [50].
Table 6.3.3.1 illustrates the basic structure of the supported fields in the Debit / Reserve Units Request for IMS online charging.
Table 6.3.3.1: Supported fields in Debit / Reserve Units Request message
Information Element |
Node Type |
IMS-GWF |
MRFC |
AS |
||||
Supported Operation Types |
I/U/T/E |
I/U/T |
I/U/T/E |
|||||
Session Identifier |
IUTE |
IUT |
IUTE |
|||||
Originator Host |
IUTE |
IUT |
IUTE |
|||||
Originator Domain |
IUTE |
IUT |
IUTE |
|||||
Destination Domain |
IUTE |
IUT |
IUTE |
|||||
Operation Identifier |
IUTE |
IUT |
IUTE |
|||||
Operation Token |
IUTE |
IUT |
IUTE |
|||||
Operation Type |
IUTE |
IUT |
IUTE |
|||||
Operation Number |
IUTE |
IUT |
IUTE |
|||||
Destination Host |
IUTE |
IUT |
IUTE |
|||||
User Name |
IUTE |
– |
IUTE |
|||||
Origination State |
IUTE |
IUT |
IUTE |
|||||
Origination Timestamp |
IUTE |
IUT |
IUTE |
|||||
Subscriber Identifier |
IUTE |
IUT |
IUTE |
|||||
Termination Cause |
—T- |
—T |
—T- |
|||||
Requested Action |
—E |
– |
—E |
|||||
Multiple Operation |
IUTE |
IUT |
IUTE |
|||||
Multiple Unit Operation |
IUTE |
IUT |
IUTE |
|||||
Service Units Requested |
IU-E |
IU- |
IU-E |
|||||
Service Units Used |
-UT- |
-UT |
-UT- |
|||||
Subscriber Equipment Number |
IUTE |
IUT |
IUTE |
|||||
Proxy Information |
IUTE |
IUT |
IUTE |
|||||
Route Information |
IUTE |
IUT |
IUTE |
|||||
Extended Information |
IUTE |
IUT |
IUTE |
|||||
Service Information with PS and IMS Information |
||||||||
Event Type |
IUTE |
IUT |
IUTE |
|||||
Role Of Node |
IUTE |
– |
IUTE |
|||||
Node Functionality |
IUTE |
IUT |
IUTE |
|||||
User Session Id |
IUTE |
IUT |
IUTE |
|||||
Outgoing Session ID |
– |
– |
IUTE |
|||||
Session Priority |
I–E |
I– |
I–E |
|||||
Calling Party Address |
IUTE |
IUT |
IUTE |
|||||
Called Party Address |
IUTE |
IUT |
IUTE |
|||||
Number Portability routing information |
I–E |
– |
I–E |
|||||
Carrier Select routing information |
I–E |
– |
I–E |
|||||
Requested Party Address |
I–E |
I– |
I–E |
|||||
Called Asserted Identity |
-U-E |
-U- |
-U-E |
|||||
Called Identity Change |
-U– |
– |
-U– |
|||||
Called Identity Change Time Stamp |
-U– |
– |
-U– |
|||||
Called Identity |
-U– |
– |
-U– |
|||||
Associated URI |
—E |
– |
– |
|||||
Time Stamps |
IUTE |
IUT |
IUTE |
|||||
Application Server Information |
IUTE |
IUT |
– |
|||||
Inter Operator Identifier |
IUTE |
IUT |
IUTE |
|||||
Transit IOI List |
IUTE |
IUT |
IUTE |
|||||
IMS Charging Identifier |
IUTE |
IUT |
IUTE |
|||||
Related IMS Charging Identifier |
– |
– |
IUTE |
|||||
Related IMS Charging Identifier Generation Node |
– |
– |
IUTE |
|||||
SDP Session Description |
IU– |
IU- |
IU– |
|||||
SDP Media Component |
IU– |
IU- |
IU– |
|||||
GGSN Address |
IU– |
IU- |
IU– |
|||||
User Location Info |
IUTE |
IUT |
IUTE |
|||||
MS Time Zone |
IUTE |
IUT |
IUTE |
|||||
Served Party |
– |
– |
– |
|||||
Server Capabilities |
– |
– |
– |
|||||
Trunk Group ID |
– |
– |
– |
|||||
Bearer Service |
– |
– |
– |
|||||
Service Id |
– |
IUT |
– |
|||||
Service Specific Info |
– |
– |
– |
|||||
Messages Bodies |
IUTE |
– |
IUTE |
|||||
Cause Code |
–TE |
–T |
–TE |
|||||
Reason Header |
–TE |
–T |
–TE |
|||||
Access Network Information |
IUTE |
IUT |
IUTE |
|||||
Additional Access Network Information |
IUTE |
IUT |
IUTE |
|||||
Cellular Network Information |
IUTE |
IUT |
IUTE |
|||||
IMS Communication Service ID |
I–E |
– |
I—E |
|||||
Tariff Information |
-U– |
– |
-U– |
|||||
Initial IMS Charging Identifier |
– |
– |
IUTE |
|||||
From Address |
IUTE |
IUT |
IUTE |
|||||
Access Network Info Change |
– |
– |
– |
|||||
Access Transfer Information |
– |
– |
-U– |
|||||
IMS Emergency Indication |
– |
– |
– |
|||||
IMS Visited Network Identification |
IUTE |
– |
IUTE |
|||||
Route Header Received |
– |
– |
– |
|||||
Route Header Transmitted |
– |
– |
– |
|||||
Instance Id |
IUTE |
– |
IUTE |
|||||
3GPP PS Data Off Status |
– |
– |
E |
Table 6.3.3.2 illustrates the basic structure of the supported fields in the Debit / Reserve Units Response for IMS online charging.
Table 6.3.3.2: Supported fields in Debit / Reserve Units Response message
Information Element |
Node Type |
IMS-GWF |
MRFC |
AS |
Supported Operation Types |
I/U/T/E |
I/U/T |
I/U/T/E |
|
Session Identifier |
IUTE |
IUT |
IUTE |
|
Operation Result |
IUTE |
IUT |
IUTE |
|
Originator Host |
IUTE |
IUT |
IUTE |
|
Originator Domain |
IUTE |
IUT |
IUTE |
|
Operation Identifier |
IUTE |
IUT |
IUTE |
|
Operation Type |
IUTE |
IUT |
IUTE |
|
Operation Number |
IUTE |
IUT |
IUTE |
|
Operation Failover |
IUTE |
IUT |
IUTE |
|
Multiple Unit Operation |
IUTE |
IUT |
IUTE |
|
Announcement Information |
IU– |
– |
IU– |
|
Operation Failure Action |
– |
– |
– |
|
Redirection Host |
– |
– |
– |
|
Redirection Host Usage |
– |
– |
– |
|
Redirection Cache Time |
– |
– |
– |
|
Proxy Information |
– |
– |
– |
|
Route Information |
– |
– |
– |
|
Failed parameter |
– |
– |
– |
|
Extended Information |
IUTE |
IUT |
IUTE |
|
Service Information with IMS Information |
||||
Account Expiration |
– |
– |
IUTE |
6.3.4 Formal IMS charging parameter description
6.3.4.1 IMS charging information for CDRs
The detailed definitions, abstract syntax and encoding of the IMS CDR parameters are specified in TS 32.298 [51].
6.3.4.2 IMS charging information for charging events
The detailed charging event parameter definitions are specified in TS 32.299 [50].