In this section:

Overview

The SBC Core includes a signaling profile, NNI Profile, in support of the Inter-IMS Network to Network Interface (II-NNI) and interworking of charging parameters for SIP to/from SIP-I/T/GWGW/ISUP calls. The NNI Profile is attached to a ingress SIP Trunk Group. The following sections describe how the SBC performs SIP to SIP-I and SIP-I to SIP interworking based on the NNI Profile.

The II-NNI standard is commonly used in Japan telecom network.

The maximum number of 32 NNI profiles are supported.

SIP to SIP-I Interworking (Originating Carrier info and Orig-CA Interworking)

The SBC supports the following functionality only when a SIP message containing the "P-Charging-Vector" header is received and processed by the SBC on the SIP side of a SIP to SIP-I/T or a SIP to SIP-GWGW-SIP-I/T/ISUP call. 

The following call flows are supported when the call is originated from Mobile SIP side:

  • Mobile—“SIP”—SBC — “GWGW”—GSX —“ISUP”— PSTN
  • Mobile—“SIP"—SBC—“GWGW”—SBC—“SIP-I/T”—C5IMS
  • Mobile—“SIP”—SBC—“SIP-I/T”—C5IM
  • Mobile—“SIP”—SBC—“GWGW”—SBC—Other Carrier

When an NNI Profile is configured for a SIP Trunk Group and the SBC receives INVITE messages with P-Charging-Vector header (which contains ttc-charging-parameter) for this SIP Trunk Group, the SBC does not send these parameters as part of "P-Charging-Vector" header on the other side.

chargeAreaInformation (CAI)

If the received ttc-charging-parameter contains chargeAreaInformation (CAI) sub-parameter, the SBC includes the received CAI value in the policy request message towards PSX and also sends it in the ISUP IAM message body (as Message-Area-Information parameter - parameter code = 253) of SIP-I/T or over GW-GW message.

If the received ttc-charging-parameter does not contain CAI sub-parameter but configured it under NNI profile, the SBC includes the configured CAI value in the policy request message towards PSX and also sends it in the ISUP IAM message body (as Message-Area-Information parameter - parameter code = 253) of SIP-I/T or over GW-GW message.

carrierInformationTransfer (CARI)

If the received ttc-charging-parameter contains carrierInformationTransfer (CARI) sub-parameter with the category as "olec", the SBC includes the received CARI values in the policy request message towards PSX and also sends it in the ISUP IAM message body (as Carrier-Information-Transfer parameter - parameter code = 241) of SIP-I/T or over GW-GW message.

If the received ttc-charging-parameter does not contain (CARI) sub-parameter (or) received CARI value other than cat-olec and CARI value is configured in the NNI profile, SBC includes the configured CARI value in the policy request message towards PSX and also sends it in the ISUP IAM message body (as Carrier-Information-Transfer parameter - parameter code = 241) of SIP-I/T or over GW-GW message.

AdditionalPartyCategory (AUC)

If the received ttc-charging-parameter contains Additional Party category (AUC) values (additionalPartyCategoryFirst/Second), the SBC does not honor the received values. If additionalPartyCategoryFirst and additionalPartyCategorySecond values are configured under NNI Profile, the SBC sends it in the ISUP IAM message body (as ISUP Supplementary User Type parameter - parameter code = 243) of SIP-I/T or over GW-GW message.

ForwardCallIndicator (FCI)

If the received ttc-charging-parameter contains forwardCallIndicator (FCI) (both nationalCallIndicator and originatingIsdnIndicator values), the SBC includes the configured FCI values in the policy request message towards PSX and also sends it in the ISUP IAM message body (as part of ISUP Forward Call Indicator parameter) of SIP-I/T or over GW-GW message.

The SBC behavior when receiving "P-charging-vector" headers and carrierInformationTransfer parameters is explained in the following table.

Example

ChargeAreaInformation:

P-Charging-Vector: icicd-value=ABC;icid-generated-at=DEF;orig-ioi=GHI;ttc-charging-params="cai=32000"

Carrier information transfer as:

P-Charging-Vector: icicd-value=ABC;icid-generated-at=DEF;orig-ioi=GHI;ttc-charging-params="cai=32000;cari=iecind-3,cat-olec,code-0901"

Additional party category as:

P-Charging-Vector: icicd-value=ABC;icid-generated-at=DEF;orig-ioi=GHI;ttc-charging-params="cai=32000;cari=iecind-3,cat-olec,code-0901;auc=mobile_2-3;auc=fixed-1-2"

Forward Call Indicators as:

P-Charging-Vector: icicd-value=ABC;icid-generated-at=DEF;orig-ioi=GHI;ttc-charging-params="cai=32000;cari=iecind-3,cat-olec,code-0901;auc=mobile_2-3;auc=fixed-1-2;fci=nii-nat,oa-isdn"

Table 1: SBC handling of P-charging-vector headers using NNI Profile

ConditionsResult
  • The SBC receives:
    • P-charging-vector header
    • carrierInformationTransfer parameters
  • The carrierInformationTransfer  parameter contains "olec" category

The SBC takes the following actions:

  • Sets the value of carrierInformationTransfer as “iecind-3” (originating network).
  • Adds the parameters carrierCategory and  carrierInfo and populates carrierInformationTransfer category as "olec". The SBC then sends carrierInformationTransfer to the PSX and in the ISUP IAM message body of SIP-I/T or over GW-GW message.
  • Populates carrierIdCode as follows:
    • If received in a message (as part of "olec" category), populate using received value. 
    • If carrierIdCode is not received, the SBC populates it using the configured value from carrierCategoryAndInfo for olec data.
    • If neither received nor configured on Trunk Group, the SBC terminates further processing and does not interwork with carrierInformationTransfer parameter.
  • The SBC receives:
    • P-charging-vector header
  • The SBC does not receive carrierInformationTransfer parameters, or
  • carrierInformationTransfer parameter does not contain "olec" category

The SBC takes the following actions:

  • Sets the value of carrierInformationTransfer to “iecind-3” (originating network).

  • Adds the parameters carrierCategory and  carrierInfo and populates carrierInformationTransfer category  as "olec". The SBC then sends the carrierInformationTransfer to the PSX and in the ISUP IAM message body of SIP-I/T or over GW-GW message as per existing functionality.

  • Populates carrierIdCode as configured value.



SIP-I to SIP Interworking (Terminating Carrier info and Term-CA Interworking)

If the parameter chargeAreaInformation is received by the SBC from SIP-I/T side with either of ACM/CPG/ANM ISUP message body or over GW-GW message, the SBC uses it to populate the parameter chargeAreaInformation (of "P-Charging-Vector" header) and sends it in a SIP message as per existing functionality.

If the parameter carrierInformationTransfer is received by the SBC from SIP-I/T side with either of ACM/CPG ISUP message body or over GW-GW message and the parameter contains carrierCategory as "tlec", the SBC processes the parameter as follows:

  • Sets the value of Transit Carrier Indicator to “iecind-0” (terminating network).
  • Adds the parameters carrierCategory and  carrierInfo, and populates carrierInformationTransfer  category as "tlec". If the parameter carrierInformationTransfer does not contain "tlec", the carrierInformationTransfer of "P-Charging-Vector" header must not be set.
  • Sends the parameter carrierInformationTransfer in "P-Charging-Vector" header in a SIP message.

If the parameters additionalPartyCategoryFirst/Second are received by the SBC from SIP-I/T side with either ACM/CPG/ANM/CON ISUP message body or received over GW-GW message, the SBC uses them to populate additionalPartyCategoryFirst/Second parameters of "P-Charging-Vector" header and send them in a SIP message.

  • No labels