для Cisco Cisco Tunnel Terminating Gateway (TTG)
GGSN Changes in Release 17
GGSN Changes in Release 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
189
Total subscribers matching specified criteria: Identifies the total number of subscribers matching criteria for
restoration priority value associated with the PND connection.
show bulkstats variables
The show bulkstats variables statistics are modified to display the following new variables for SAEGW schema in case
of colocation with GGSN.
of colocation with GGSN.
ggsn-pdns-restore-priority-1
ggsn-pdns-restore-priority-2
ggsn-pdns-restore-priority-3
ggsn-pdns-restore-priority-4
ggsn-pdns-restore-priority-5
ggsn-pdns-restore-priority-6
ggsn-pdns-restore-priority-7
ggsn-pdns-restore-priority-8
The new variable in the show bulkstat variables schema for displaying the associated schema.
current-pdn-restore-priority-1
CSCum42664 - Bit Rate mapping across Gx and GTP based interfaces
Feature Changes
Bit Rate Mapping Across Gx and GTP-based Interfaces
Bit rate granularity provided by different interfaces was not 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.
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.
With this feature, 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.
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.
Previous Behavior: Previously, rounded-down kpbs bitrate (AMBR, MBR, BGR) values were being sent towards the
Access side.
Access side.
New Behavior: Bitrate granularity is still maintained per the current interface specifications but 3GPP provides explicit
guidance that whenever the conversion from bps to kbps results in decimal values, the node converting should round the
value up.
guidance that whenever the conversion from bps to kbps results in decimal values, the node converting should round the
value up.
Introduced a new CLI command under GGSN service
[no] gtpc bit-rates-rounded-down-kbps
to control the
behavior of rounding-up. The CLI command will enable/disable the old behavior of rounding down. By default, this
CLI command is configured to use rounded-up bitrate values. Depending on how the CLI is configured, either rounded-
up (Ceil) or rounded-down bitrate value will be sent on GTP interface towards the Access side.
CLI command is configured to use rounded-up bitrate values. Depending on how the CLI is configured, either rounded-
up (Ceil) or rounded-down bitrate value will be sent on GTP interface towards the Access side.
Customer Impact: This feature provides for more consistent behavior and ensures correct bandwidth is allocated for
bearers.
bearers.