Navigation :

Rule Caching

N2SVCD rule engine caching may be specified to be used for service logic processing. This must be defined within the N2SVCD Lua service global variables IWF_CACHES.

Each cache definition is a single string that:

Must begin with a valid configuration location.
May also include a valid configuration item’s name within that location.
May also include a specific concept within that configuration item.

Any cache definition that does not provide all applicable parts will be treated as applying to all unspecified parts.

A simple IWF cache configuration might be:

    <global name="IWF_CACHES" type="array">
        <cache>VARIABLES.direction</cache>
        <cache>PRE_RATING</cache>
        <cache>NOTIFICATIONS.notf2</cache>
        <cache>EXTERNAL_ACTION_TYPES.ati_msisdn.hlr_gt_digits</cache>
    </global>

This would result in the following lookups being cached:

Only N2SVCD rule engine variable lookups for the variable named direction.
All pre-rating rules.
All parameters of the notification named notf2.
Only the hlr_gt_digits MAP parameter within the external action type named ati_msisdn.

Common Caches

The following cache definitions may be used regardless of input protocol:

1st Part	2nd Part	3rd Part	Target
`ADDITIONAL_AVPS`	<AVP name>	-	Diameter request additional AVP rules. Note that AVP names that occur more than once will never be cached.
`ERROR_HANDLING`	-	-	Error handling rules.
`EXTERNAL_ACTION_TYPES`	<external action type name>	Parameter	External action type definition rules for named external action type. Valid parameters are: `user_number` `match_number` `allow_match_sc` `allow_sc_user` `terminating` `suppress_edr` `gsm_scf_digits` `hlr_gt_digits` `hlr_ssn` `hlr_pc` `hlr_timer_secs` `msisdn_source` `imsi_source` `source_noa` `source_npi` `store_vlr` `store_mcc` `store_mnc` `hlr_sigtran_route` `gsm_scf_noa` `gsm_scf_npi` `hlr_ri` `hlr_gt_noa` `hlr_gt_np` `hlr_gt_tt` `hlr_timer_secs`
`NOTIFICATIONS`	<notification name>	Parameter	Notification definition rules for named notification. Valid parameters are: `to` `from` `protocol` `app` `flash`
`NOTIFICATION_APP_DEFAULT`	-	-	Notification default rules for `app` parameter.
`NOTIFICATION_FROM_DEFAULT`	-	-	Notification default rules for `from` parameter.
`NOTIFICATION_PROTO_DEFAULT`	-	-	Notification default rules for `proto` parameter.
`NOTIFICATION_TO_DEFAULT`	-	-	Notification default rules for `to` parameter.
`POST_RATING`	-	-	Post-rating rules.
`PRE_RATING`	-	-	Pre-rating rules.
`RATING_GROUPS`	-	-	Diameter request rating group rules.
`REQUESTED_TIMES`	-	-	Diameter request requested time rules.
`REQUESTED_UNITS`	-	-	Diameter request requested unit rules.
`RESULT_CODES`	-	-	Result-Code rules.
`SERVICE_CONTEXT_IDS`	-	-	Diameter request service context ID rules.
`SERVICE_IDENTIFIERS`	-	-	Diameter request service identifier rules.
`TRANSLATIONS`	-	-	Destination translation rules.
`VARIABLES`	<variable name>	-	N2SVCD rule engine variable rule.

There is no caching for Diameter response read AVPs, external actions, or currencies definitions.

CAMEL/INAP Call Caches

When using CAMEL/INAP call input, the following additional cache definitions may be used:

1st Part	2nd Part	3rd Part	Target
`TONES`	-	-	CAMEL/INAP tone rules.

There is no caching for announcements or FCI/SCI definitions. or currencies.

SIP Call Caches

When using SIP call input, the following additional cache definitions may be used:

1st Part	2nd Part	3rd Part	Target
`DIRECTION`	-	-	SIP call direction.

There is no caching for announcements or release reasons definitions.