Cisco Cisco Packet Data Gateway (PDG)
P-GW Changes in Release 17
▀ P-GW Enhancements for 17.4
▄ Release Change Reference, StarOS Release 17
356
CSCut53373, CSCuu63751, CSCuu64308 - PGW initiates UBR while no QoS
cahnge
Feature Changes
UBR Suppression Feature
Important:
The Update Bearer Request (UBR) Suppression feature is a license controlled feature. Please contact
your Cisco sales representative for more information.
As the bit rate is expressed in bps on Gx and kbps on GTP, P-GW does a round-off to convert a Gx request into a GTP
request. When P-GW receives RAR from PCRF with minimal bit rate changes (in bps), a UBR is sent, even if the same
QoS (in Kbps) is already set for the bearer. The UBR suppression feature enables P-GW to suppress such a UBR where
there is no update for any of the bearer parameters.
request. When P-GW receives RAR from PCRF with minimal bit rate changes (in bps), a UBR is sent, even if the same
QoS (in Kbps) is already set for the bearer. The UBR suppression feature enables P-GW to suppress such a UBR where
there is no update for any of the bearer parameters.
A new CLI has been added to the P-GW service configuration to enable UBR suppression. Once the CLI is configured,
P-GW suppresses the UBR if the bit rate is the same after the round-off.
P-GW suppresses the UBR if the bit rate is the same after the round-off.
When UBR has multiple bearer contexts, the bearer context for which the bit rate change is less than 1 kbps after round-
off is suppressed. If other parameters, such as QCI, ARP, and TFT, that might trigger UBR are changed and there is no
change in bit rates after round-off, then UBR is not suppressed. Suppression of UBR is applicable for UBR triggered by
CCA-I, RAR, and Modify Bearer Command.
off is suppressed. If other parameters, such as QCI, ARP, and TFT, that might trigger UBR are changed and there is no
change in bit rates after round-off, then UBR is not suppressed. Suppression of UBR is applicable for UBR triggered by
CCA-I, RAR, and Modify Bearer Command.
Previous Behavior: UBR was not suppressed, even if bit rates were the same.
New Behavior: If license is enabled and CLI is configured for UBR suppression, then UBR is suppressed if bit rates in
kbps are the same after round-off and all other parameters, such as QCI, ARP, and TFT, that might trigger UBR are also
unchanged.
kbps are the same after round-off and all other parameters, such as QCI, ARP, and TFT, that might trigger UBR are also
unchanged.
Command Changes
suppress-ubr no-bitrate-change
A new CLI command has been introduced to control UBR suppression. This CLI is disabled by default; UBR is
triggered, even if the Gx and GTP bit rates in kbps are the same after round-off.
triggered, even if the Gx and GTP bit rates in kbps are the same after round-off.
configure
context context_name
pgw-service <pgw-service-name>
egtp suppress-ubr no-bitrate-change
no egtp suppress-ubr no-bitrate-change
end
Notes:
suppress-ubr: Enables or disables suppression of UBR when there is no change in PCRF authorized bit rates.
By default, the UBR suppression feature is disabled.