Cisco Cisco Packet Data Gateway (PDG)
AAA Changes in Release 16
▀ AAA Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
56
In scenarios where Rf (OFCS) and Gy (OCS) have different usage information for a subscriber session, it is possible
that the subscriber is not aware of any potential overages until billed (scenario when Rf is more than Gy) or subscriber
believes he has already used up the quota whereas his actual billing might be less (scenario when Gy is more than Rf).
In an attempt to align both the Rf and Gy reported usage values, older release 12.3 introduced capabilities to provide a
way to get the reported values on both the interfaces to match as much as possible. However, some of the functionalities
were deferred and this feature implements the additional enhancements.
that the subscriber is not aware of any potential overages until billed (scenario when Rf is more than Gy) or subscriber
believes he has already used up the quota whereas his actual billing might be less (scenario when Gy is more than Rf).
In an attempt to align both the Rf and Gy reported usage values, older release 12.3 introduced capabilities to provide a
way to get the reported values on both the interfaces to match as much as possible. However, some of the functionalities
were deferred and this feature implements the additional enhancements.
In release 15.0 when time/volume quota on the Gy interface gets exhausted, Gy triggers “Service Data Volume Limit”
and “Service Data Time Limit”. Now in 16.0 via this feature, this behavior is CLI controlled. Based on the CLI the
behavior will be decided whether to send the ACR-Interim immediately or to cache the containers for future
transactions.
and “Service Data Time Limit”. Now in 16.0 via this feature, this behavior is CLI controlled. Based on the CLI the
behavior will be decided whether to send the ACR-Interim immediately or to cache the containers for future
transactions.
If the CLI for the event-triggers received via Gy is not configured, then those ACR-Interims will be dropped.
Previous Behavior: Earlier whenever the volume/time-limit event triggers are generated, ACR-Interims were sent out
immediately.
immediately.
New Behavior: Now, CLI configuration options are provided in policy accounting configuration to control the various
Rf messages (ACRs) triggered for sync on this feature.
Rf messages (ACRs) triggered for sync on this feature.
This release supports the following enhancements:
Caches containers in scenarios when ACR-I could not be sent and reported to OFCS.
Triggers ACR to the OFCS when the CCR to the OCS is sent instead of the current implementation of waiting
for CCA from OCS.
If an ACR-I could not be sent to the OFCS, the PCEF caches the container record and sends it in the next transaction to
the OFCS.
the OFCS.
Command Changes
trigger-type
This is a new command used to enable/disable the event triggers for Rf-Gy interaction.
configure
context context_name
policy accounting policy_name
trigger-type { gy-sdf-time-limit { cache | immediate } | gy-sdf-unit-limit {
cache | immediate } | gy-sdf-volume-limit { cache | immediate } } +
cache | immediate } | gy-sdf-volume-limit { cache | immediate } } +
{ default | no } trigger-type
end
Notes:
This CLI configuration will either enable PCEF to send an ACR-Interim immediately or cache the container
records for reporting in a future transaction. If there is no such configuration for that event-trigger, then the
ACR-Interims will be dropped.
ACR-Interims will be dropped.
When the subscriber disconnects while in Assume Positive mode, then the CLI configuration enables the PCEF
to send an ACR-Stop with PS-level change condition “Normal Release” and container level “Service Specific
Unit Limit”. The presence of the “Service Specific Unit Limit” change condition at the container level
Unit Limit”. The presence of the “Service Specific Unit Limit” change condition at the container level