Ec/No Criteria for CS IRAT

RF Optimization Central-1
25 October 2016
Overview

Current Strategy Proposed Strategy

RSCP Based CS IRAT Ec/No OR RSCP Based CS IRAT

Coverage Based Coverage/Quality Based

Capacity Based CS Offloading Quality Based CS Offloading

Trigger CS IRAT Handovers beyond -14 Ec/No

Gains Challenges
• User CS Call does not suffer due • WB AMR 12.65 Codec in UMTS vs
to poor Ec/No NB AMR 7.4 Codec in GSM
• CS IRAT HOSR Improved by 0.3 - • HO Blocking
0.5 PP
EcNo Comparison BH vs Non BH
C-1 Region Ec/No Behavior

Ec/No (0 to -12) Ec/No (0 to -12)

loaded Hours (06:00 – 00:00 hrs) Un-Loaded Hours (00:00 – 06:00 hrs)

TP BH Dedicated Mode EcNo TP Non-BH Dedicated Mode EcNo

19%
93%

3 GEM Approval Meeting

Trial Technical Details & OSS Benchmark
RNC-128 in C-1 region had maximum share of poor Ec/No samples (< -12), and it was attempted first. Later on, trial was done on
RNC-120 to benchmark DT results in Lahore as well.
index MO Name Level Parameter Name Configuration value (CS Only) Suggestion value (CS Only) Parameter Description
1 UInterEcNoEvMeasforG Profile threshUsedFreq -13;-8 -14;-12 2D/2F for CS IRAT
2 URatEcNoEvMeasforG Profile thresh -9;-24;-24;-24 -13;-24;-24;-24 3A for CS IRAT (3G Ec/No)
3 URatEcNoEvMeasforG Profile threshSys -90;-95;-95;-115 -95;-95;-90;-115 3A for CS IRAT (2G Levels)
4 UUtranCellFDD Cell nonIntraMeasQuan 1 2 Defines whether to consider Ec/No
5 UInterEcNoEvMeasforG Profile hysteresis 4;4 0;0 Hysteresis for IRAT HOs
6 UInterEcNoEvMeasforG Profile trigTime 12;12 12;12 640 msec trigger time
threshUsedFreq & thresh for PS are set at -24 (max possible) in order to avoid Ec/No based PS IRAT Handovers.

CS Traffic
4.3%
CS IRAT HOSR 40000 MPD
0.52% 39000 2.5%
92.50% 39152 335
38000
92.42% 330
37000 331
92.00% 37462 325
36000
91.90% 320 323
Pre Post
91.50% 315
Pre Post Pre Post

RNC128
25-07-16
CS IRAT HO Attempts Throughput Per User
0.65%
210% 935
400000 Non-HS TCP Utilization
300000 371158 0.8%
934
26.0% 930
200000
25.5% 25.9%
100000 928
119679 25.0%
0 925
Pre Post 24.5% Pre Post
24.7%
24.0%
Pre Post

RNC Pre Dates Post dates

128 20 to 24 Jul 26 to 29 Jul
Trial Technical Details & OSS Benchmark
RNC-128 in C-1 region had maximum share of poor Ec/No samples (< -12), and it was attempted first. Later on, trial was done on
RNC-120 to benchmark DT results in Lahore as well.
index MO Name Level Parameter Name Configuration value (CS Only) Suggestion value (CS Only) Parameter Description
1 UInterEcNoEvMeasforG Profile threshUsedFreq -13;-8 -14;-12 2D/2F for CS IRAT
2 URatEcNoEvMeasforG Profile thresh -9;-24;-24;-24 -13;-24;-24;-24 3A for CS IRAT (3G Ec/No)
3 URatEcNoEvMeasforG Profile threshSys -90;-95;-95;-115 -95;-95;-90;-115 3A for CS IRAT (2G Levels)
4 UUtranCellFDD Cell nonIntraMeasQuan 1 2 Defines whether to consider Ec/No
5 UInterEcNoEvMeasforG Profile hysteresis 4;4 0;0 Hysteresis for IRAT HOs
6 UInterEcNoEvMeasforG Profile trigTime 12;12 12;12 640 msec trigger time
threshUsedFreq & thresh for PS are set at -24 (max possible) in order to avoid Ec/No based PS IRAT Handovers.

CS Traffic
14.2%
CS IRAT HOSR 65000 MPD
0.24% 60000 2%
94.00% 440
55000 59624
93.90% 93.97% 435
50000 435
93.80% 51151 430
45000
93.70% 425
93.73% Pre Post 426
93.60% 420
Pre Post Pre Post

RNC120
09-08-16
CS IRAT HO Attempts Throughput Per User
2%
109% 980
400000 Non-HS TCP Utilization
300000 978
0.6% 970
289801 25.0%
200000
960
100000 24.5% 24.8% 960
119679
0 950
24.0% 24.2% Pre Post
Pre Post
23.5%
Pre Post

RNC Pre Dates Post dates

120 4 to 8 Aug 10 to 14 Aug
Central-1 Region OSS KPIs Benchmarking

CS Traffic 3G CS Traffic 2G
7617 7301
300000 2600000
CS IRAT HOSR 2595000 Payload (GB)
295000 297201 2595249
0.34% 2590000 6.3%
93.60% 290000 110000
289584
2585000 2587948
93.40%
285000 2580000 105000 106966
93.20% 93.39%
Pre Post Pre Post 100000
93.00% 100559
93.05%
92.80% Similar Difference 95000
Pre Post Pre Post

CS IRAT HO Attempts Non-HS TCP Utilization

109% Stable
400000 23.7%
300000 Central-1 23.6%
200000 289801 Region 23.5% 23.6%
100000 10-10-16 23.4%
119679 23.5%
0 23.3%
Pre Post Pre Post

Call Re-establishment Attempts Throughput Per User

3%
MPD 3G MPD 2G 933
Stable
15000
14800 10.4% 11.6% 932
14828 400 380
14600 932
380 360 932
14400 365
382 931
14200 14368 360 340 931
14000 340 320 931
346 327 Pre Post
Pre Post
320 300
Pre Post Pre Post

Fewer Calls reaching call

reestablishment condition

Pre Dates Post dates

1 to 7 Oct 13 to 19 Oct
 7
91
92
93
94

91.5
92.5
6/10/2016
6/12/2016 93.5
CS IRAT- Central I

6/14/2016
6/16/2016
6/18/2016
6/20/2016

GEM Approval Meeting

6/22/2016
6/24/2016
6/26/2016
6/28/2016
6/30/2016
7/2/2016
7/4/2016
7/6/2016
7/8/2016
7/10/2016
7/12/2016
7/14/2016
7/16/2016
7/18/2016
7/20/2016
7/22/2016
7/24/2016
7/26/2016
7/28/2016
7/30/2016
8/1/2016
8/3/2016
8/5/2016
8/7/2016
8/9/2016
8/11/2016
8/13/2016
8/15/2016
8/17/2016
8/19/2016
8/21/2016
8/23/2016
8/25/2016
8/27/2016
8/29/2016
8/31/2016
9/2/2016
9/4/2016
9/6/2016
9/8/2016
9/10/2016
9/12/2016
9/14/2016
CS 3G to 2G Handover Success Rate (%)

9/16/2016
3G to 2G HOSR :: Central-1

9/18/2016
9/20/2016
9/22/2016
9/24/2016
9/26/2016
9/28/2016
9/30/2016
10/2/2016
10/4/2016
10/6/2016
10/8/2016
10/10/2016
10/12/2016
10/14/2016
10/16/2016
10/18/2016
10/20/2016
10/22/2016
10/24/2016
Drive Test

• Route: Telenor RHQ DHA Lahore – Manga, Multan Rd (RNC 120)

• Equipment: Nemo Outdoor, Galaxy S5 (HD CALL Supportive)
• Mode: Unlocked Mode 2min call with 20 sec interval

• Analysis
• Ec/No
• RxQuality
• MOS PESQ
• Technology Share
Drive Test Results – Technology Share (Dedicated Mode)

POST DT
PRE DT

Almost 44% shift in Technology share in Dedicated Mode

Drive Test Results – Ec/No (Dedicated Mode)

POST DT
PRE DT

~9% reduction in bad EcNo samples < -12

Drive Test Results – Rx Quality

POST DT
PRE DT

More than 92% of 2G RxQual samples in Excellent Quality Range (0-3)

Drive Test Results – Rx Quality vs Ec/No

3G EcNo

2G RxQual

2G RxQual in Post DT is pretty decent in comparison with Ec/No patches in Pre DT

Drive Test Results – MOS PESQ

POST DT
PRE DT

~Avg. MOS dropped from 3.90 -> 3.77

Debate done in slides ahead
MOS Degradation Issue

• RxQual observed to be quite good where Ec/No suffered, therefore, improved user
experience could be perceived in broader sense.

• Keeping in view the MOS degradation in DT, it is noteworthy that UMTS layer samples
utilized WB AMR FR (12.65 kbps – HD Voice) for almost 98% of Drive Test Route, while
2G layer utilized AMR HR (7.4 kbps) for almost 100% of the Drive Test.

• However, statistical analysis shows that WB AMR FR 12.65 Codec usage is only ~7% and
AMR HR (7.4 kbps) is around 90%

• It is already established that WB AMR MOS gains upto 30% in comparison with NB AMR.

• It is, therefore, safe to state that 93% of the UMTS traffic that is utilizing NB AMR FR is
not likely to encounter MOS degradation.
Way Forward & Recommendations

• Another testing with non-HD capable handset to further tune EcNo threshold (if
needed) to locate a point where 3G MOS degrades more than 2G MOS

• All networks in Pakistan are following this strategy except CMPak (Zong) as it has least
spectral loading.

• It is recommended to roll out the feature nationwide as it ensures that a 3G CS Call user
does not suffer due to poor Network Quality (Ec/No).

• CS IRAT Improvement results are also pretty encouraging.

• It is recommended NOT to roll out this feature on cells where 2G layer has HO Blocking
or Poor Quality issues.

• Other Regions are encouraged to try for other parametric values for Ec/No based IRAT
HO Thresholds/Hysteresis/Trigger Time.
Thank you