Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 17
SGSN Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
497
New Behavior: The lawful interception capacity is now increased to 160000 intercepts.
Customer Impact: Additional CPU is required to simultaneously intercept more number of users, therefore the overall
throughput supported by the chassis may drop. The average throughput per user on the LI interface may reduce when
many users are being intercepted simultaneously. Additional memory is required at the Session Manager to store the
intercepts.
throughput supported by the chassis may drop. The average throughput per user on the LI interface may reduce when
many users are being intercepted simultaneously. Additional memory is required at the Session Manager to store the
intercepts.
CSCtz09826 - Need a cli to control ‘Release Access Bearers Request’
Feature Changes
Configurable RAB Cause
To enhance the S4-SGSN functionality of the LORC Subscriber Overcharging Protection now extended to the S4
interface (refer to CSCts82739), a new CLI command enables the operator to configure the Release Access Bearer cause
code to be included with the ARRL (Abnormal Release of Radio Link) bit in the Release Access Bearer Request.
interface (refer to CSCts82739), a new CLI command enables the operator to configure the Release Access Bearer cause
code to be included with the ARRL (Abnormal Release of Radio Link) bit in the Release Access Bearer Request.
Previous Behavior: Upon RNC failure or Iu-Release, the SGSN preserves non-GBR PDPs (interactive or background)
by default.
by default.
In the case of either DT (direct tunnel) or ISR for 3G, the SGSN already supported the sending of Release
Access Bearer Request on Iu-Release.
By default, in 2G upon Ready-to-Standby the SGSN preserved non-GBR PDPs (interactive or background).
For ISR, the S4-SGSN already sent Release Access Bearer Request on Ready-to-Standby state transition.
New Behavior: With a new CLI command (see section below), the S4-SGSN can send Release Access Bearer Request
on Iu-Release for non-DT and non-ISR subscribers in 3G and on Ready-to-Standby or Radio-Status-Bad for non-ISR
subscribers in 2G. And in compliance with 3GPP TS 23.060 v11.7.0, the S4-SGSN now optionally sends Release
Access Bearer Request to the S-GW to remove the downlink user plane on the S4 interface for non-DT and non-ISR
scenario.
on Iu-Release for non-DT and non-ISR subscribers in 3G and on Ready-to-Standby or Radio-Status-Bad for non-ISR
subscribers in 2G. And in compliance with 3GPP TS 23.060 v11.7.0, the S4-SGSN now optionally sends Release
Access Bearer Request to the S-GW to remove the downlink user plane on the S4 interface for non-DT and non-ISR
scenario.
Command Changes
release-access-bearer
This new S4-SGSN-specific command,
release-access-bearer
in the Call-Control Profile configuration mode,
provides the operator with CLI configuration control to enable or disable the sending of Release Access Bearer Request:
Release Access Bearer initiation on Iu-Release in a 3G network - using the new optional keyword
on-iu-
release
,
Release Access Bearer initiation on Ready-to-Standby in a 2G network - using the new optional keyword
on-
ready-to-standy
.
configure
call-control-profile profile_name
release-access-bearer [ on-iu-release | on-ready-to-standby ]
remove release-access-bearer [ on-iu-release | on-ready-to-standby ]