Navigation :

FCI/SCI Messages

As part of handling defined action rules for CUG handling, error handling, billing bypass, and Diameter Result-Code processing, a pre-configured FurnishChargingInformation or SendChargingInformation message may be sent. Such messages are configured with a name so that they may be invoked by the applicable action rules.

Both FCI and SCI messages may only be sent along with a Connect or Continue operation, and therefore may only be specified against action rules that allow the call to continue in this fashion. If more than one FCI or SCI is selected to be sent (e.g. if both CUG handling and Diameter Result-Code processing apply and specify such a message, only the most recently-specified case will apply.

A sample FCI/SCI configuration might be:

    <application name="<application instance name>" module="DsgScpApp">
      ...
      <config>
        ...
        <fcis>
          <fci name="fci-x">012f000700000044000000460003642102886145ffffffffffff800800021fffffffffffffff6421700739ffffffffffffff</fci>
        </fcis>

        <scis>
          <sci name="sci-100">0164</sci>
          <sci name="sci-101">0165</sci>
          <sci name="sci-101.camel">0166</sci>
        </scis>

In the above, four FCI/SCI messages are defined and would have the following configuration:

Name	Applies To	Data
`fci-x`	(all)	(freeform hexadecimal data as configured)
`sci-100`	(all)	Charging characteristics `0x0164`, party to charge `01`.
`sci-101`	(all)	Charging characteristics `0x0165`, party to charge `01`.
`sci-101.camel`	Any CAMEL variant	Charging characteristics `0x0166`, party to charge `01`.

Configuration Details

Each fci or sci can support the following attributes:

Attribute	Type	Description
`name`	String	[Required] The unique name for this FCI/SCI message. Used in rule actions to specify the message to send. If the message only applies to a particular INAP variant (as listed in the SSP Model `inap` parameter), the variant identifier may be appended to the message name after a period, e.g. `name.camel2`. Note that the special variant `camel` applies to all CAMEL variants, i.e. `camel1`, `camel2`, `camel3`, and `camel4`.
(data)	Hexadecimal String	The hexadecimal data of the message. For SCI messages, this is the content of the `sCIBillingChargingCharacteristics` field, and the `partyToCharge.sendingSideID` accompanying it is always set to `01`. For FCI messages, this is the entire `FCIBillingChargingCharacteristics` field. In the latter case, some INAP variants (e.g. CAMEL) specify that this field is further divided into sub-fields, e.g. `fCIBCCCAMELsequence1`, as per the example below.

FCI Data

As indicated in the FCI/SCI configuration details, the FCI data value is used as the entire FCI payload within the FCIBillingChargingCharacteristics field.

Other INAP variants, such as CAMEL, have this parameter subdivided into other fields. As an example, if CAMEL2 were used with the FCI definition data of a00f80081234567890abcdefa103800101, this would decode to:

a0 0f                       # constructed, tag 0 (fCIBCCCAMELsequence1), length 15
  80 08                     # primitive, tag 0 (freeFormatData), length 8
    12 34 56 78 90 ab cd ef # value
  a1 03                     # constructed, tag 1 (partyToCharge), length 3
      80 01                 # primitive, tag 0 (sendingSideID), length 1
        01                  # value