Rf Interface Support
▀ Configuring Rf Interface Support
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
476
Depending on the triggers configured, the containers will either be cached or released. In the case of GGSN/P-
GW, the containers will be cached when the event trigger is one of the following:
QOS_CHANGE
FLOW_INFORMATION_CHANGE
LOCATION_CHANGE
SERVING_NODE_CHANGE
SERVICE_IDLE
SERVICE_DATA_VOLUME_LIMIT
SERVICE_DATA_TIME_LIMIT
IP_FLOW_TERMINATION
TARIFF_CHANGE
If the event trigger is one of the following, the containers will be released:
VOLUME_LIMIT
TIME_LIMIT
RAT_CHANGE
TIMEZONE_CHANGE
PLMN_CHANGE
Important:
Currently, SDF and flow level accounting are supported in P-GW.
The following assumptions guide the behavior of P-GW, GGSN, S-GW, HSGW and CCF for Change-Condition
triggers:
Data in the ACR messages due to change conditions contain the snapshot of all data that is applicable to the
interval of the flow/session from the previous ACR message. This includes all data that is already sent and has
not changed (e.g. SGSN-Address).
All information that is in a PDN session/flow up to the point of the Change-Condition trigger is captured
(snapshot) in the ACR-Interim messages. Information about the target S-GW/HSGW/Time-Zone/ULI/3GPP2-
BSID/QoS-Information/PLMN Change/etc will be in subsequent Rf messages.
When multiple change conditions occur, the precedence of reporting change conditions is as follows for S-GW
and HSGW only:
Normal/Abnormal Release (Stop)
Management Intervention (Stop)
RAT Change
UE Timezone Change
Serving Node PLMN Change
Max Number of Changes in Charging conditions
Volume Limit
Time Limit
