11 Charging

29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS

11.1 General

The accounting information to be supported over the Ici is described in 3GPP TS 32.260 [29] and 3GPP TS 32.240 [183]. It shall be configurable by the operator to use or not the accounting mechanisms provided by the IBCF.

11.2 Inter-operator accounting

For inter-operator accounting, the procedures related to the P-Charging-Vector header field specified in 3GPP TS 24.229 [5] shall be supported over the II-NNI as further specified below.

NOTE 1: The "icid-value" header field parameter identifying a dialog or a transaction outside a dialog is included in the P-Charging-Vector header field as specified in 3GPP TS 24.229 [5]. The "icid-value" header field parameter value of a SIP response to a SIP request is identical to the "icid-value" of the SIP request.

For the roaming II-NNI:

– the P-Charging-Vector header field in the REGISTER requests, initial SIP requests and stand-alone SIP requests, containing the type 1 "orig-ioi" with the entry which identifies the visited network; and

– the P-Charging-Vector header field in the REGISTER responses (except the 100 (Trying) response), SIP responses (except the 100 (Trying) response) to initial SIP requests and SIP stand-alone requests, containing type 1 "orig-ioi" and type 1 "term-ioi" header field parameters with the entries which identify the visited network and the home network respectively;

shall be supported.

NOTE 2: Operator network identifiers populated in the type 1 "orig-ioi" and type 1 "term-ioi" header field parameters need to be exchanged by inter-operator agreements in advance.

For the II-NNI between IMS home networks:

– the P-Charging-Vector header field in the SIP requests containing the type 2 "orig-ioi" with the entry which identifies the home originating network; and

– the P-Charging-Vector header field in the SIP responses (except the 100 (Trying) response) containing the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters with the entries which identify the home originating network and the home terminating network respectively;

may be supported based on inter-operator agreements.

If the roaming architecture for voice over IMS with local breakout is used, for the II-NNI between the caller’s visited network and the callee’s home network except for the roaming II-NNI:

– the P-Charging-Vector header field in the SIP requests containing the type 2 "orig-ioi" with the entry which identifies the visited originating network; and

– the P-Charging-Vector header field in the SIP responses (except the 100 (Trying) response) containing the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters with the entries which identify the visited originating network and the home terminating network respectively;

may be supported based on inter-operator agreements.

NOTE 3: Operator network identifiers populated in the type 2 "orig-ioi" and type 2 "term-ioi" header field parameters need to be exchanged by inter-operator agreements in advance.

For the II-NNI for the transit scenario:

– the P-Charging-Vector header field in the SIP requests and responses (except the 100 (Trying) response) containing the "transit-ioi" header field parameter with the entry(ies) which identify the transit network(s);

may be supported based on inter-operator agreements.

NOTE 4: Operator network identifiers populated in the value(s) of "transit-ioi" header field parameter need to be exchanged by inter-operator agreements in advance.

11.3 Transfer of IP multimedia service tariff information

In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), transfer of IP multimedia service tariff information as specified in 3GPP TS 29.658 [186] may be supported on the II-NNI between two IMS networks. The support of transfer of IP multimedia service tariff information is based on agreement between operators.

If transfer of IP multimedia service tariff information is supported, the "application/vnd.etsi.sci+xml" MIME body with the Content-Disposition header field set to either "render" with the "handling" parameter set to "optional" or to "signal" with the "handling" parameter set to "required" or "optional" based on operator agreement in 18x responses to the INVITE request and in the INFO request shall be supported at the II-NNI.