Cisco Cisco Packet Data Gateway (PDG)
GGSN Changes in Release 17
GGSN Changes in Release 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
183
CSCui40177 - GGSN to send micro chkpt for ue initiated and network initiated
update
Feature Changes
Micro Checkpointing support for ue and network initiated updates
Currently GGSN uses full checkpoints when any bearer parameter like QoS change, SGSN change, or RAT change
happens. In such cases GGSN shall use micro checkpoints for the parameters that are changed. This change is needed
for session recovery checkpoints as well as ICSR checkpoints.
happens. In such cases GGSN shall use micro checkpoints for the parameters that are changed. This change is needed
for session recovery checkpoints as well as ICSR checkpoints.
For GGSN -- UE initated update and network initiated update (excluding inter tech handoff and coa ) should send
microcheckpoint.
microcheckpoint.
CSCul17195 - GTP echo and GTP message retry shall be configured separately
Feature Changes
Separate Configuration for GTP-C Echo and GTP-C Non-echo Messages
Previous Behavior: Previously, GTP echo and GTP message retry “timer” could be configured separately. However,
the
the
max-retry number
configuration was the same.
New Behavior: Now,
max-retry number
can be configured separately for GTP echo and GTP message, similar to
“timer” configuration.
Customer Impact: This new behavior allows different configurations for GTP-C echoes as compared to the non-echo
messages.
messages.
See CSCum66168 for additional changes.
CSCum17169 - Per APN, and QCI, GTP-C v2 responses
Feature Changes
Per APN and QCI GTP-C v2 Response
This feature collects the eGTP-C cause codes as bulkstats and categorizes them to Per APN per QCI. Operator can
derive KPI based on the bulkstat counters per QCI for a particular APN (for example: IMS APN and VoLTE APN).
derive KPI based on the bulkstat counters per QCI for a particular APN (for example: IMS APN and VoLTE APN).
Supporting more granular statistics/bulkstats on APN (up to 2,000 APNs are supported) has an impact on system
performance and this occurs for bulkstats. Stats need to be obtained at regular intervals for a few minutes. Each of these
retrievals can lead to gigabytes of information to be gathered and consolidated. Due to this issue, a restricted/controlled
usage of granular bulkstats is introduced. If the operator uses the configuration, then it is possible to enable which APN
is used to collect granular statistics and in those granular statistics which particular statistics are collected.
performance and this occurs for bulkstats. Stats need to be obtained at regular intervals for a few minutes. Each of these
retrievals can lead to gigabytes of information to be gathered and consolidated. Due to this issue, a restricted/controlled
usage of granular bulkstats is introduced. If the operator uses the configuration, then it is possible to enable which APN
is used to collect granular statistics and in those granular statistics which particular statistics are collected.
Previous Behavior: In general, the current bulkstats APN configuration gathers the bulkstat data for the all APNs.
There is no option to restrict gathering of bulkstats for selective APN(s).
There is no option to restrict gathering of bulkstats for selective APN(s).