Cisco Cisco ASR 5000
LORC Subscriber Overcharging Protection for S4-SGSN
▀ Configuring Subscriber Overcharging Protection
▄ SGSN Administration Guide, StarOS Release 18
Configuring Subscriber Overcharging Protection
Important:
In order for the Subscriber Overcharging Protection feature to be most effective, the operator should
first enable sending the Release Access Bearer Request and next configure the cause codes for the SGSN for matching
with received codes which enables the SGSN to include the Abnormal Release of Radio Link (ARRL) bit in the Release
Access Bearer Request.
with received codes which enables the SGSN to include the Abnormal Release of Radio Link (ARRL) bit in the Release
Access Bearer Request.
Important:
For details about all the commands listed in the Configuration sections below, refer to the Command
Line Interface Reference, StarOS Release 17.
Enabling Release Access Bearer Request
The operator can control the sending of 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.
subscribers in 3G and on Ready-to-Standby or Radio-Status-Bad for non-ISR subscribers in 2G.
Use commands similar to those illustrated below to enable sending of the Release Access Bearer Request:
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 ]
end
Notes:
on-iu-release
: This optional keyword instructs the SGSN to send Release Access Bearer upon Iu-Release in
a 3G network so that Release Access Bearer will be initiated for non-ISR and non-DT subscribers upon Iu-
Release. For ISR and DT subscribers, Release Access Bearer will be initiated unconditionally.
Release. For ISR and DT subscribers, Release Access Bearer will be initiated unconditionally.
on-ready-to-standby
: This optional keyword instructs the SGSN to send Release Access Bearer on Ready-
to-Standby transition in a 2G network so that Release Access Bearer will be initiated for non-ISR subscribers
on Ready-to-Standby transition. For ISR subscribers, Release Access Bearer will be initiated unconditionally.
on Ready-to-Standby transition. For ISR subscribers, Release Access Bearer will be initiated unconditionally.
If no optional keywords are included with the
release-access-bearer
command, then the S4-SGSN applies
Release Access Bearer for both 2G and 3G networks.
Configuring the Causes to Include ARRL in Release Access Bearer Request
In support of the subscriber overcharging protection functionality, the operator must configure all cause codes on the
SGSN. If the SGSN receives a cause code via Iu/Gb interfaces that matches one of the cause codes configured on the
SGSN, then the SGSN includes the ARRL (Abnormal Release of Radio Link) bit in the Release Access Bearer Request.
SGSN. If the SGSN receives a cause code via Iu/Gb interfaces that matches one of the cause codes configured on the
SGSN, then the SGSN includes the ARRL (Abnormal Release of Radio Link) bit in the Release Access Bearer Request.