Cisco Cisco ASR 5000
LORC Subscriber Overcharging Protection for S4-SGSN
▀ Feature Description
▄ SGSN Administration Guide, StarOS Release 18
Feature Description
Subscriber Overcharging Protection prevents subscribers from being overcharged when a loss of radio coverage
(LORC) occurs.
(LORC) occurs.
Important:
In order for the Subscriber Overcharge Protection feature to be most effective, the SGSN supports
initiation of Release Access Bearer Request on Iu-Release for all subscribers (even for non-ISR and non-DT cases).
Refer to the section on Release Access Bearer Requests below for details.
Refer to the section on Release Access Bearer Requests below for details.
LORC Subscriber Overcharge Protection on the S4-SGSN
LORC is standardized in 3GPP release 12.0 specifications. According to 3GPP TS 23.401, the SGSN includes the
ARRL (Abnormal Release of Radio Link) Indication in Release Access Bearer Request messages if the Iu-Release
procedure is due to an abnormal release of the radio link.
ARRL (Abnormal Release of Radio Link) Indication in Release Access Bearer Request messages if the Iu-Release
procedure is due to an abnormal release of the radio link.
It should be noted that 3GPP has not defined LORC for UMTS / GPRS access in an EPS network. Currently, it is
defined only for E-UTRAN access. However, the SGSN can use the defined 3GPP mechanism to achieve PDN pause of
charging in UMTS / GPRS access as well.
defined only for E-UTRAN access. However, the SGSN can use the defined 3GPP mechanism to achieve PDN pause of
charging in UMTS / GPRS access as well.
With this feature the S4-SGSN should include the ARRL (Abnormal Release of Radio Link) bit in indication flags IE of
Release Access Bearer Request when Iu-Release occurs due to the cause 'Radio Connection With UE Lost (46)' in 3G.
Release Access Bearer Request when Iu-Release occurs due to the cause 'Radio Connection With UE Lost (46)' in 3G.
Also the S4-SGSN should include the ARRL (Abnormal Release of Radio Link) bit in indication flags IE of Release
Access Bearer Request when Radio Status Bad ia received in 2G.
Access Bearer Request when Radio Status Bad ia received in 2G.
The operator configures all cause codes on the SGSN so 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 bit in the Release Access
Bearer Request.
matches one of the cause codes configured on the SGSN, then the SGSN includes the ARRL bit in the Release Access
Bearer Request.
Release Access Bearer Requests
3G (UMTS):
Upon RNC failure or Iu-Release, the SGSN preserves non-GBR (i.e., non-guaranteed bit rate) PDPs (interactive /
background) by default. From release 15.0 onwards, for DT and ISR cases the SGSN supports sending Release Access
Bearer Request on Iu-Release. In accordance with TS 23.060 v11.7.0, the SGSN can optionally send a Release Access
Bearers Request to the S-GW to remove the downlink user plane on S4 for non-DT and non-ISR subscribers.
background) by default. From release 15.0 onwards, for DT and ISR cases the SGSN supports sending Release Access
Bearer Request on Iu-Release. In accordance with TS 23.060 v11.7.0, the SGSN can optionally send a Release Access
Bearers Request to the S-GW to remove the downlink user plane on S4 for non-DT and non-ISR subscribers.
As part of this feature, the operator can configure the S4-SGSN to send Release Access Bearer Request on Iu-Release
for non-DT and non-ISR subscribers. For DT and ISR subscribers, Release Access Bearer Initiation functions as it has
done prior to this feature’s implementation.
for non-DT and non-ISR subscribers. For DT and ISR subscribers, Release Access Bearer Initiation functions as it has
done prior to this feature’s implementation.
2G (GPRS):
Upon Ready-to-Standby, the SGSN preserves non-GBR (i.e., non-guaranteed bit rate) PDPs (interactive / background)
by default. From release 15.0 onwards, for ISR cases the S4-SGSN supports sending Release Access Bearer Request on
Ready-to-Standby state transition. In accordance with 3GPP TS 23.060 v11.7.0, the SGSN optionally sends a Release
Access Bearers Request to the S-GW to remove the downlink user plane on S4 for non-ISR subscriberes.
by default. From release 15.0 onwards, for ISR cases the S4-SGSN supports sending Release Access Bearer Request on
Ready-to-Standby state transition. In accordance with 3GPP TS 23.060 v11.7.0, the SGSN optionally sends a Release
Access Bearers Request to the S-GW to remove the downlink user plane on S4 for non-ISR subscriberes.
As part of this feature, the operator can configure the S4-SGSN to send Release Access Bearer Request on Ready-to-
Standby or Radio Status Bad for non-ISR subscribers. For ISR subscribers, Release Access Bearer Initiation is
independent and functions as it has done prior to this feature’s implementation.
Standby or Radio Status Bad for non-ISR subscribers. For ISR subscribers, Release Access Bearer Initiation is
independent and functions as it has done prior to this feature’s implementation.