Cisco Cisco Packet Data Gateway (PDG)
P-GW Service Configuration Mode Commands
egtp ▀
Command Line Interface Reference, StarOS Release 18 ▄
8059
egtp
Configures handling of eGTP related procedures.
Product
P-GW
SAEGW
Privilege
Administrator
Mode
Exec > Global Configuration > Context Configuration > P-GW Service Configuration
configure > context context_name > pgw-service service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-pgw-service)#
Syntax
egtp { bitrates-rounded-down-kbps | cause-code temp-fail timeout sec retry retries |
modify-bearer-cmd-negotiate-qos | overcharge-protection [ drop-all | transmit-all ] |
sgw-restoration session-hold timeout seconds| suppress-ubr no-bitrate-change }
modify-bearer-cmd-negotiate-qos | overcharge-protection [ drop-all | transmit-all ] |
sgw-restoration session-hold timeout seconds| suppress-ubr no-bitrate-change }
default egtp { cause-code temp-fail | modify-bearer-cmd-negotiate-qos | overcharge-
protection | sgw-restoration session-hold }
protection | sgw-restoration session-hold }
no egtp { bitrates-rounded-down-kbps | cause-code temp-fail | modify-bearer-cmd-
negotiate-qos | overcharge-protection | sgw-restoration session-hold| suppress-ubr no-
bitrate-change }
negotiate-qos | overcharge-protection | sgw-restoration session-hold| suppress-ubr no-
bitrate-change }
default
Resets the command to the default setting.
no
Disables the configuration statement.
bitrates-rounded-down-kbps
Bit rate granularity provided by different interfaces was not originally aligned in 3GPP specifications. For
example, the PCRF provided bits per second on the Gx and the GTP utilized kilobits per second. Due to the
conversion of bps to kbps, there were scenarios where the rounding off could have resulted in the incorrect
allocation of MBR/GBR values.
When this keyword is disabled, a bitrate value sent on GTP interface will be rounded up if the conversion
from bps (received from Gx) to kbps results in a fractional value. However, the enforcement of bitrate value
(AMBR, MBR, GBR) values will remain the same. Once the value (in kbps) that is sent towards the Access
side, it needs to be rounded up. Also,
example, the PCRF provided bits per second on the Gx and the GTP utilized kilobits per second. Due to the
conversion of bps to kbps, there were scenarios where the rounding off could have resulted in the incorrect
allocation of MBR/GBR values.
When this keyword is disabled, a bitrate value sent on GTP interface will be rounded up if the conversion
from bps (received from Gx) to kbps results in a fractional value. However, the enforcement of bitrate value
(AMBR, MBR, GBR) values will remain the same. Once the value (in kbps) that is sent towards the Access
side, it needs to be rounded up. Also,
show subscribers pgw-only full all
will show the APN-
AMBR in terms of bps.
When enabled, the previous behavior of rounded-down kpbs bitrate (AMBR, MBR, BGR) values being sent
towards the Access side is enforced. In addition,
When enabled, the previous behavior of rounded-down kpbs bitrate (AMBR, MBR, BGR) values being sent
towards the Access side is enforced. In addition,
show subscribers pgw-only full all
displays in
terms of kpbs.