The SBC Core supports P-Charging-Function-Addresses header as part of P-CSCF functionality. This header carries the charging function information.

This P-Charging-Function-Address header contains the following fields:

  • ccf—the charging data function addresses used for offline billing
  • ecf—the charging data function addresses used for online billing

SBC Provisioning

  • As a P-CSCF, the SBC ignores and removes P-Charging-Function-Addresses, if present, when it receives any request/response from UE or when it sends any request/response to UE.
  • As a P-CSCF, the SBC stores the values received in P-Charging-Function-Addresses header in a request or response from the IMS core in the initial dialog-establishing request or a stand-alone transaction.

    Storing of P-Charging-Function-Addresses is controlled by a provisioning flag (storePChargingFuncAddr) associated with Ingress TG with respect to Request and Response message (Core side).
  • As a P-CSCF, the SBC inserts previously saved P-Charging-Function-Addresses headers before forwarding the message to IMS core when it receives any request or response from UE.

    Insertion of P-Charging-Function-Addresses is controlled by a provisioning flag (addPChargingFuncAddr) associated with Egress TG with respect to Request and Response message (Core side).

CDR Processing

The SBC saves the P-Charging-Function-Addresses header with the ccf-value and ecf values to the CDR in ingress and egress protocol specific variants fields. The P-Charging-Function-Addresses header is not received or created for INVITE. P-CSCF stores the P-Charging-Function-Addresses header in 200 OK response for REGISTER, and then adds this stored value in the outgoing INVITE towards the IMS Core.