Cisco Cisco ASR 5000 Technical Manual
potentially utilize the entire APN AMBR, e.g. when the other Non GBR bearers do not carry any
traffic. The PGW enforces the APN AMBR in downlink and uplink direction.
traffic. The PGW enforces the APN AMBR in downlink and uplink direction.
With Gx enabled, PGW honors PCRF authorized APN-AMBR values always. If an APN-AMBR
value is not received in the Gx reauthorization with PCRF, then the last received APN-AMBR
values from PCRF is enforced by PGW
value is not received in the Gx reauthorization with PCRF, then the last received APN-AMBR
values from PCRF is enforced by PGW
In Cisco ASR5x00 PGW, APN-AMBR enforcement can be enabled on per-APN basis using “ CLI
in APN config mode on PGW.
in APN config mode on PGW.
Syntax
Usage:
Use this command to enforce the AMBR for the APN on bearers that do not have a Guaranteed
Bit Rate (GBR).
Bit Rate (GBR).
Example:
The following command sets the downlink burst rate to use an auto-readjust duration of 2 seconds
and lowers the IP precedence of violating packets:
and lowers the IP precedence of violating packets:
Note: For more details on this CLI please refer to PGW config guide
Default-Bearer QOS enforcement support
Default-Bearer QOS represents the QOS that is applied to the traffic flowing over Default-Bearer in
a PDN. Default-Bearer QOS info contains the QCI and the ARP. Default-Bearer being a non-GBR
bearer there is no bearer-level Data rates associated with its bearer-level QOS. APN-AMBR is
applicable to default bearer and is shared with other non-GBR bearers of that subscriber for that
APN.
a PDN. Default-Bearer QOS info contains the QCI and the ARP. Default-Bearer being a non-GBR
bearer there is no bearer-level Data rates associated with its bearer-level QOS. APN-AMBR is
applicable to default bearer and is shared with other non-GBR bearers of that subscriber for that
APN.
PGW enforces the Default-Bearer QOS that is authorized by PCRF or Local-Policy. If no Gx or
Local-Policy is enabled, then the requested Default-Bearer QOS is enforced at PGW. The PGW
support for enforcing Default-bearer is similar to the APN-AMBR enforcement support, with
corresponding event-triggers for Default-Bearer QOS (DEFAULT-EPS-BEARER-QOS-CHANGE
event-trigger or some other) over Gx or Local-Policy.
Local-Policy is enabled, then the requested Default-Bearer QOS is enforced at PGW. The PGW
support for enforcing Default-bearer is similar to the APN-AMBR enforcement support, with
corresponding event-triggers for Default-Bearer QOS (DEFAULT-EPS-BEARER-QOS-CHANGE
event-trigger or some other) over Gx or Local-Policy.
SDF (PCC-rule) Level enforcement support
Cisco ASR5x00 PGW supports PCEF functionality which is compliant with the 3
rd
Generation
Partnership Project (3GPP) based PCC framework based on 3GPP spec TS 23.203 & TS 29.212.
As part of PCEF functionality support, PGW supports Policy and Charging Control at SDF or PCC-
rule level and has support for Gx interface for interaction with PCRF server. PGW supports PCEF
based Bearer-Binding of PCC rules for IPCAN session type 3GPP-EPS. Below is the PCC
framework architect that Cisco ASR5x00 PGW is compliant with:
As part of PCEF functionality support, PGW supports Policy and Charging Control at SDF or PCC-
rule level and has support for Gx interface for interaction with PCRF server. PGW supports PCEF
based Bearer-Binding of PCC rules for IPCAN session type 3GPP-EPS. Below is the PCC
framework architect that Cisco ASR5x00 PGW is compliant with: