trial of Sys constant

484 activation on 1c
for retainability
improvement after anr
irat implementation
AT&T L.A. Market

Hector Pena
Ericsson Internal | 2011-10-19 | Page 1
background
› After the activation of IRAT ANR on L.A. and other AT&T
markets, retainability KPI´s degraded since previously when the
point of A2ThresholdRsrpPrim was reached, a blind Release
With Redirection (RwR) was executed to UMTS and the call was
considered successful even though there were not any counters
to verify the final outcome of the call.

› After the activation of IRAT ANR (or addition of any IRAT

neighbors) the B2 (non 2C sites) event was enabled and the UE
will search for suitable neighbors on other frequency bands
according to settings and priorities, since the A5B2timer was not
enabled on the ATT network, the UE would remain on this task
until it drops or finds a suitable neighbor.

Ericsson Internal | 2011-10-19 | Page 2

TRIAL / Proposed solution
› In order to give the UE a final opportunity before the call is
dropped, the proposal is to activate the System constant 484
(Rel. 12B) or parameter zzzTemporary3 (Rel. 13A), to enable
the “enhancedBadCovDetection” functionality and what this does
is to implement the “a2ThresholdRsrpSec” parameter as a
secondary “critical coverage” threshold for RSRP that when its
reached performs a blind Release with Redirection (RwR) to the
highest priority IRAT frequency.
› In this way we’ll have a normal B2 event where the UE searches
for other frequencies for a normal non-blind
handover/reselection, but in case that we reach a critical point of
poor coverage, a blind reselection will be allowed instead of
dropping the call.

Ericsson Internal | 2011-10-19 | Page 3

TRIAL / Proposed solution

The proposed solution/trial set the “a2ThresholdRsrpSec” threshold

2dB’s below the current “a2ThresholdRsrpPrim” effectively giving a 2 dB
window to search and execute a Non-blind Reselection/HO, and then if
needed perform a blind one in case critical coverage is reached.
Ericsson Internal | 2011-10-19 | Page 4
 A2ThresholdRsrpSec activation (enhancedBadCovDetection,
Sys constant 484/zzzTemporary3 on L13A) trial on 1C sites
for Retainability Improvement after IRAT neighbors addition

Accessibility / Retainability

5000000 99.80

4500000
99.75
4000000

%Accessibility / %Retainability
3500000
99.70
pmRrcConnEstabAtt

3000000

2500000 99.65

2000000
99.60
1500000

1000000
99.55
500000

0 99.50
7/16 7/17 7/18 7/19 7/22 7/23 7/24 7/25 7/26 7/29 7/30 7/31 8/1 8/2 8/5 8/6 8/7 8/8 8/9 8/12 8/13

Date “Functionality” Activation

FGA11 rollout
pmRrcConnEstabAtt %Accessibility %Retainability

CMAS Affectation
 A2ThresholdRsrpSec activation on 1C sites for
Retainability Improvement after IRAT neighbors
addition
IRAT / CSFB

80000 2.5

70000

2
60000

50000

%CSFB / %IRAT
1.5
#IRAT

40000

1
30000

20000
0.5

10000

0 0
7/16 7/17 7/18 7/19 7/22 7/23 7/24 7/25 7/26 7/29 7/30 7/31 8/1 8/2 8/5 8/6 8/7 8/8 8/9 8/12 8/13

Date
#IRAT %CSFB %IRAT “Functionality” Activation

Ericsson Internal | 2011-10-19 | Page 6

 SUMMARY/CONCLUSIONS:
• The system constant 484 activation (Now parameter
zzzTemporary3 on release L13A) provides an
improvement on retainability setting the new “purpose”
RSRP threshold A2ThresholdRsrpSec 2 dB’s below the
current A2ThresholdRsrpPrim; effectively giving a 2 dB
window to search for a suitable IRAT neighbor, and if not
found during this window executing a blind Release with
Redirection to the highest priority IRAT frequency in
order to give the call one last chance to continue.
• There’s an increase on the # of IRAT’s attempted, but
regarding the AT&T CQI metric we have a gain, due to
the higher weight of the Retainability KPI vs. IRAT (Note:
on this trial we did not measure the TNOL impact that is
also part of the CQI)

Ericsson Internal | 2011-10-19 | Page 7

Changes implemented for the trial

Ericsson Internal | 2011-10-19 | Page 8