Policy Flashcards
Triggers
Entry points when invoking the Rule Engine
Rule Groups
A set of Rules that are evaluated in sequence by the Rule Engine
The evaluation of Rules that are part of a Rule Group stops at the first rule that is matching its defined conditions
Several Rule Groups can be associated to a Trigger which are all evaluated in sequence
Rule Groups can be nested (invoking a Rule Group from a Rule of another Rule Group)
Rules
Logical constructions of type IF (condition/conditions) THEN (action/actions)
Conditions are logical expression that are evaluating Criteria Attributes
Actions are software functions to be executed having or not parameters that will drive their execution.
Rule Variables
Local variable inside a Trigger that can be evaluated in conditions and be set in actions.
Rule System Version (RSV)
A Rule Engine’s environment composed of a set of Rule Groups associated to Triggers having inside Rules and/or Rule Variables and/or Default Actions.
A RSV is stored in the SPS DB from where it can be loaded into the Rule Engine’s cache memory.
Several RSVs can exist in the SPS DB, but only one will be loaded at a certain time in the Rule Engine’s cache, the so called active RSV.
SPS-Policy provides tailored policy based on a wide variety of inputs. Some of the inputs include:
- subscription type
- type of device
- location; based on MCCMNC, GGSN IP address, cell tower
- configured device data
- time of day/day of week
- usage related policies
- OCS Spending Limits updates
When SPS-Policy reacts to an event, such as an incoming Diameter message, there is an
opportunity to provide a customized policy decision using the SPS-Policy rules. When the event
occurs, such as an incoming Rx message from an application, SPS-Policy evaluates the rules
associated with the event. The rules have access to a wide variety of information on which to base
the policy decision, including the following:
• AVPs from a message can be evaluated using customized rules resulting in unique policy
decisions
• subscriber-related data; internal SPR record, or a cache/retrieved external SPR record
• existing IP-CAN session (if present) and its attributes
• existing Sy session (if present), OCS counters and their states
• existing AF session (if present), media types and flows
• custom data fields