Note: State Variables replace User State Conditions. When upgrading from an earlier release that used State Variable, the properties for User State Conditions are automatically mapped to the corresponding State Variable values. Therefore, the subscriber property is mapped to the subscriber remote state variable and the pool property is mapped to the pool state variable.
State Variables are set within a policy action to be used at a later time during policy rule execution (in either conditions or actions). The names of these variables are not predefined and are determined at the time of creation. State variables have a scope which determines how long the value persists after it is set. The scopes are:
- Subscriber Remote State Variable — This state variable exists remotely in an SPR as long as the subscriber exists in the SPR. Using this variable requires that an SPR/HSS be configured that is capable of storing this variable.
- Pool State Variable — This variable is associated with a quota pool (of multiple subscribers). This variable is stored remotely in an SPR and exists as long as the pool exists in the SPR. Using this variable requires that an SPR/HSS be configured that is capable of storing this variable.
- Subscriber Local State Variables — This variable exists locally on the MPE and has a value as long as the associated subscriber has at least one session on that MPE. After the last session is terminated these variables no longer have value and will no longer be available for use in policies.
- Session State Variables — This variable has a value that is saved as long as the session the variable is associated with is still valid. After the session is terminated, this variable no longer has value and will no longer be available for use in policies.
- Policy Evaluation State Variables — This variable are available for the lifetime of a policy evaluation cycle (the process of evaluating all the policies for a single request or context)