Cisco Cisco Packet Data Gateway (PDG) Guía De Administador
Gx Interface Support
Rel. 9 Gx Interface ▀
Cisco ASR 5x00 Home Agent Administration Guide ▄
169
reported) with the accumulated usage at IP-CAN session level (if enabled) and at service data flow level (if
enabled) This is the default behavior.
enabled) This is the default behavior.
In the case of standard implementation, this must be enabled by CLI configuration.
Important:
The Usage Reporting on Revalidation Timeout feature is available by default in non-standard
implementation of Volume Reporting over Gx. In 10.2 and later releases, this is configurable in the standard
implementation. This is not supported in 10.0 release for standard based volume reporting.
implementation. This is not supported in 10.0 release for standard based volume reporting.
Once the usage is reported, the usage counter is reset to zero. The PCEF continues to track data usage from the zero
value after the threshold is reached and before a new threshold is provided by the PCRF. If a new usage threshold is not
provided by the PCRF in the acknowledgement of an IP-CAN Session modification where its usage was reported, then
usage monitoring does not continue in the PCEF for that IP CAN session and and the usage accumulated between the
CCR-CCA will be discarded.
value after the threshold is reached and before a new threshold is provided by the PCRF. If a new usage threshold is not
provided by the PCRF in the acknowledgement of an IP-CAN Session modification where its usage was reported, then
usage monitoring does not continue in the PCEF for that IP CAN session and and the usage accumulated between the
CCR-CCA will be discarded.
For information on how to configure the Volume Reporting over Gx feature, see the
ICSR Support for Volume Reporting over Gx (VoRoGx)
In releases prior to 15.0, post the ICSR switchover, any existing session for which the PCRF has enabled volume
reporting used to continue indefinitely until the session is terminated or until CCR-U is sent for a given trigger, without
having the volume counted via Gx.
reporting used to continue indefinitely until the session is terminated or until CCR-U is sent for a given trigger, without
having the volume counted via Gx.
To summarize, after an ICSR switchover, volume reporting over Gx is no longer done for existing sessions. Also,
volume usage is not synced to standby chassis.
volume usage is not synced to standby chassis.
In 15.0 and later releases, volume threshold and volume usage are synced to standby chassis to support volume
reporting over Gx for existing sessions post switchover.
reporting over Gx for existing sessions post switchover.
Without this support it cannot cause a subscriber to use higher speeds than what s/he is supposed to get, if volume
reporting is for example used to enforce fair usage; the operator may already consider this a revenue loss. It will also
severely impact roaming subscribers who are supposed to get a notification and be blocked/redirected once the limits set
by the EU roaming regulation are reached. If a session continues now without being blocked, the operator is not allowed
to charge for data beyond the limit and will have a significant and real revenue loss (roaming partner may still charge
for the data used on their SGSNs).
reporting is for example used to enforce fair usage; the operator may already consider this a revenue loss. It will also
severely impact roaming subscribers who are supposed to get a notification and be blocked/redirected once the limits set
by the EU roaming regulation are reached. If a session continues now without being blocked, the operator is not allowed
to charge for data beyond the limit and will have a significant and real revenue loss (roaming partner may still charge
for the data used on their SGSNs).