Rule Caching
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.
- May also include a specific sub-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>
<cache>EXTERNAL_ACTION_TYPES.diam1.send_avps.Cost-Information</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_digitsMAP parameter within the external action type namedati_msisdn. - Population of the
send_avps->Cost-InformationAVP within the external action type nameddiam1.
Common Caches
The following cache definitions may be used regardless of input protocol:
| 1st Part | 2nd Part | 3rd Part | 4th Part | Target |
|---|---|---|---|---|
ADDITIONAL_AVPS_ROOT |
AVP name | - | - | Diameter additional AVP rules at the root of the request. Note that AVP names that occur more than once will never be cached. |
ADDITIONAL_AVPS_MSCC |
AVP name | - | - | Diameter additional AVP rules within the Multiple-Services-Credit-Control AVP. Note that AVP names that occur more than once will never be cached. |
ERROR_HANDLING |
- | - | - | Error handling rules. |
EXTERNAL_ACTION_TYPES |
External action name | Parameter | AVP name (Diameter actions only) |
External action type definition rules for named external action type. |
NOTIFICATIONS |
Notification name | Parameter | - | Notification definition rules for named notification. |
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.