Cisco Cisco Packet Data Interworking Function (PDIF)
P-GW Service Configuration Mode Commands
▀ egtp
▄ Command Line Interface Reference, StarOS Release 18
8060
By default, this command is configured to use rounded-up bitrate values.
cause-code temp-fail timeout sec retry retries
Enables EGTP Cause Code Handling for when the P-GW receives a temporary failure response from peer
(cause code 110). All transactions that were moved to pending queue because of temporary cause failure
would be reattempted after temporary failure timer expires.
After timer expiry, the P-GW informs PCRF about the transient failure. PCRF sends new RAR and
CBR/MBR/UBR would succeed.
(cause code 110). All transactions that were moved to pending queue because of temporary cause failure
would be reattempted after temporary failure timer expires.
After timer expiry, the P-GW informs PCRF about the transient failure. PCRF sends new RAR and
CBR/MBR/UBR would succeed.
timeout sec
: Specifies the time to wait (in seconds) before reattempting the Create Bearer Request
(CBR)/Modify Bearer Request (MBR)/Update Bearer Request (UBR).
sec
must be an integer from 1 to 100.
retry retries
: Specifies the maximum number of retries. The P-GW discards CBR/MBR/UBR after the
maximum number of retries are exceeded.
retries
must be an integer from 1 to 4.
modify-bearer-cmd-negotiate-qos
This configuration only impacts the PGW QoS negotiation behavior when PCRF is unreachable or event
trigger is not registered while handling Modify Bearer Command. By default, this configuration is disabled.
When enabled, P-GW will always enforce old QoS values authorized by the PCRF. When disabled, the P-
GW will always accept new QoS values (APN-AMBR/Def-EPS-Bearer-QoS) received in Modify Bearer
Command.
trigger is not registered while handling Modify Bearer Command. By default, this configuration is disabled.
When enabled, P-GW will always enforce old QoS values authorized by the PCRF. When disabled, the P-
GW will always accept new QoS values (APN-AMBR/Def-EPS-Bearer-QoS) received in Modify Bearer
Command.
overcharge-protection [ drop-all | transmit-all ]
Configures overcharging protection by temporarily not charging during loss of radio coverage. By default,
this configuration is disabled.
this configuration is disabled.
drop-all
: Configures overcharging protection to drop all packets received in LORC.
transmit-all
: Configures overcharging protection to send all packets received in LORC mode to S-GW.
sgw-restoration session-hold timeout seconds
Enables S-GW restoration functionality and configure session hold timeout on a P-GW service. By default, S-
GW restoration is disabled.
GW restoration is disabled.
seconds
must be an integer from 1 to 3600.
Default: 0 (disabled).
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.
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.
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.
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.
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.
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.
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.