of OC, PCRF uses one or a combination of the following key parameters:
There is no unique
identifier available for identification of OC for a particular subscriber
session. In release 20, a new Diameter AVP "Override-Control-Name" is defined
in the Override-Control grouped AVP. The OC name specified in the AVP is used
as the unique key to identify OC for any further updates like OC modification
To meet the new AVP
keyword has been added to the existing
override-control CLI command under rulebase
configuration. If the
with-oc-name CLI is configured in rulebase, only OCs with
Override-Control-Name AVP are supported and the OCs without name are rejected.
Override-Control-Name AVP is received when the
override-control CLI command is configured i.e. OC
install is supported without OC name, appropriate error is reported in error
logs, OC is dropped and OC failure statistics is incremented. Similarly if
with-oc-name CLI is configured and OC is received without the
name AVP, appropriate error is reported, OC is dropped and OC failure
statistics is incremented. On receiving an OC without name, installed OC list
(without name) is searched for secondary identification criteria. If no OC with
same rule/charging-action/exclude rule list is found, it is installed as a
Also, for OCs with
the name, operator can add rule/charging-action/exclude rule to the existing OC
in the same category. That means, the rules can be added to a rule level OC, CA
names can be added to a CA level OC, and exclude rules can be added to a
wildcard or CA level OC.
OCs received with
Override-Control-Name AVP are uniquely identified by the OC name. When the
Override-Control-Name AVP is not present in Override-Control AVP, the OCs are
identified based on the secondary identification criteria, i.e., the list of
rule names, charging-action names, and exclude-rule names as these were the
criteria before this feature change.
change, the feature to support OC name will be controlled based on the
configuration of new rulebase. After rulebase change OC will be accepted as per
the CLI configured in new rulebase. This is the only scenario where for a
single call session, OC can be installed with both OC name and without OC name.
upgrade is done on a standby setup where same rulebase is configured with the
with-oc-name, then no calls are dropped and OC installation
status will remain the same as before upgrade. If new call is established after
upgrade and OC is installed with OC-name then this will be applied on new call.
downgrade, OC-name will be dropped and OCs will be recreated assuming
Rule/CA/Exclude rule name list as the primary key for unique identification.