Cisco Cisco Packet Data Gateway (PDG)
On S-GW failure indication, P-GW shall check if S-GW Restoration feature is enabled or not. If enabled,
P-GW shall maintain all the affected sessions for session-hold timeout. After session-hold timeout, P-GW
shall clear all the sessions which are not recovered yet.
P-GW shall maintain all the affected sessions for session-hold timeout. After session-hold timeout, P-GW
shall clear all the sessions which are not recovered yet.
suppress-ubr no-bitrate-change
Enables the P-GW to suppress the Update Bearer Request (UBR) message UBR if the bit rate is the same
after the round-off.
after the round-off.
As the bit rate is expressed in bps on Gx and kbps on GTP, the P-GW does a round-off to convert a Gx request
into a GTP request. When the P-GW receives a RAR from the 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 the P-GW to suppress such a UBR where there is no update for any of the bearer parameters.
into a GTP request. When the P-GW receives a RAR from the 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 the P-GW to suppress such a UBR where there is no update for any of the bearer parameters.
When the 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 an
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.
kbps after round-off is suppressed. If other parameters, such as QCI, ARP, and TFT, that might trigger an
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.
Default: disabled. This means that the UBReq should be triggered even if the Gx and GTP bit-rates in kbps
are same after round-off.
are same after round-off.
If the no option is used, it will disable this feature. That is, the UBReq should be triggered even if the Gx and
GTP bit-rates in kbps are same after round-off.
GTP bit-rates in kbps are same after round-off.
There is no separate default keyword for this feature. Use the no option to revert to the default behavior.
The UBR Suppression Feature is a licensed-controlled feature. Contact your Cisco account or service
representative for detailed licensing requirements.
representative for detailed licensing requirements.
Important
Usage Guidelines
Use this command to configure the behavior of the P-GW/SAEGW for eGTP procedures.
Examples
The following command sets the temporary failure timer to 30 seconds and 2 retries:
egtp cause-code temp-fail timeout 30 retry 2
The following command configures the P-GW to accept new QoS values from the modify bearer command
while the PCRF is not reachable:
while the PCRF is not reachable:
egtp modify-bearer-cmd-negotiate-qos
The following command enables S-GW restoration functionality and configures session hold timeout on a
P-GW service:
P-GW service:
sgw-restoration session-hold timeout seconds
Command Line Interface Reference, Modes I - Q, StarOS Release 19
1668
P-GW Service Configuration Mode Commands
egtp