You are on page 1of 20

CS Voice Service Prioritization on F1/F2

Gujrat City Cluster


05,October 2018
ZTE CMPAK :: Central

Background:

Objective::To prioritized CS Voice service on F1/F2 in CMPak network,


users while PS traffic on all 3 carriers Gauging the impact of new strategy
on CS call mobility in DT Mode and also on PS KPIs.

Method::
Cluster Selection: Gujrat City Cluster is taken as a trial cluster for CS Voice
service prioritization. The Cluster has both Dual Carrier and Tri Carrier
sites to facilitate an apple to apple comparison of DT results before and
after the trial.

Tri-carrier Sites = 5 Sites


Dual Carrier Sites = 2 sites

Strategy: For CS call two different cell groups were defined with different
service priority and Low priority group was assigned to F7 while high
priority group was appended with F1/F2 carrier cells.

In IDLE mode UE will be shifted from F7 to F1/F2 throughput –ve Offset


and PS users will be balanced from F1/F2 to F7 using Load Balance
technique based on HSPA user number
ZTE CMPAK :: Central

Field Testing :
Objective::To gauge the impact of CS prioritization on F1/F2 Trial in field

Methodology::
CS Mode:
In pre-testing, an Automode CS call was established on F7 carrier and UE was traversed towards the boundary of Dual Carrier
sites.
In post-testing, Automode CS call was most of the time established on F1/F2 due IDLE mode parameter modification but not
always. The UE was then traversed towards Dual Carrier site and mobility behavior was captured.
Pre
PS Mode:
Automode PS Data establishment.

Testing Summary::Before implementing the trial, CS call got dragged beyond the dual carrier site to a distance until coverage
based Handover criterion of RSCP <-100 dBm was met and then inter-frequency handover was performed to dual carrier site.
While in Post Trial scenario, most of the time call was timely handed over to Dual Carrier site due to soft handover algorithm.

Observations ::
 EcNo was degraded in Post DT due increase load on F1/F2 from F7
 No improvement in CS Drop Call Ratio is observed because no call was dropped in pre scenario due to existence of
coverage based handover relations.
 RSCP was slightly improved due to timely HO (Soft HO) if call established on F1/F2
 DL throughput was degraded in Post DT due to degraded EcNo
ZTE CMPAK :: Central

Executive Drive Test Summary :

DT KPIs Summary 3G CS Statistical Summary

Short Call Pre Short Call Post


Coverage PRE POST Call Statistics
Values/Count Values/Count
Avg. RSCP (dBm) -80.56 -77.51 Number of Call
20 29
Attempts
Number of Successful
20 29
Quality Calls
-9.5 -10.6
Number of Call Dropped 0 0
Avg. EcNo (dBm)
Blocked Calls 0 0

Throughput CS CSSR 100% 100%


4217.8 3688.1 CS Call Drop Rate 0% 0%
Avg. DL Throughput (Kbps) Call Setup Time(s) 5.37 4.99
ZTE CMPAK :: Central

Drive Test Plots: ZONG 3G RSCP


PRE AS RSCP Post AS RSRP

• RSCP in Post Scenario improved due to timely soft handover triggering without any call dragging
ZTE CMPAK :: Central

Drive Test Plots: ZONG 3G EcNo


PRE AS EcNo Post AS EcNo

• AS EcNo seems a bit degraded due to increase load on F1/F2 from F7 and carrier imbalacing
ZTE CMPAK :: Central

Drive Test Plots: ZONG 3G Throughput


PRE DL Throughput Post DL Throughput

• DL Throughout degraded due to bad EcNo in PS Mode


ZTE CMPAK :: Central

Drive Test Plot : Call Analysis (PRE-POST)


PRE Cell Dragging issue Post Cell dragging issue resolved

• Cell dragging issue observed in pre drive while in post the is rectified.
ZTE CMPAK :: Central

Drive Test Plot : Call Analysis (POST Only)


Post Call established on F1 i Post Call established at F7

• Due to –ve offset from F7 to F1/F2 , UE quickly reselect to • Some call do established on F7 also
F1/F2 and most of the calls are established on F1/F2
ZTE CMPAK :: Central

TabularKPIs Benchmark:
DAY AVG Busy Hour
3G Major KPI's Reasoning
PRE(24-26 Sep) POST(1-3 Oct) % Delta PRE(24-26 Sep) POST(1-3 Oct) % Delta

RRC Setup Success Ratio (%) 99.81% 99.77% -0.04% 99.76% 99.72% -0.04% RRC degraded due bad EcNo on F2 & F1 as we pushed traffic from F7 to F1/F2

RAB Setup Success Ratio (%) 99.97% 99.97% 0.00% 99.95% 99.95% 0.00% Marginal Imapct
PS Call Drop Ratio (%) 1.14% 1.24% 9.38% 1.31% 1.40% 7.14% PS CDR degraded due to increase load on F1/F2 from F7 and carrier imbalance issue
CS Service Drop Ratio (%) 0.20% 0.20% 0.00% 0.27% 0.21% -23.17% Slight improvement observed on BH but stable on Day Level avg
PS Traffic-(GB) 289.83 284.62 -1.80% 17.03 17.77 0.00% Slight degraded due to increase in Soft HOSR attempts with NBR while HSDPA almost same
CS AMR Traffic(Erl) 640.72 612.38 -4.42% 41.25 37.70 -8.59% Slight degraded due to increase in Soft HOSR attempts with NBR while users almost same
SoftHandover Success Rate(%) 99.97% 99.97% 0.00% 99.98% 99.97% -0.01% Same Trend
CS W2G Inter - RAT HO out Success Ratio (%) 98.5% 98.2% -0.4% 96.75% 98.02% 1.32% Marginal Imapct
Inter frequency Hard handover SR% 96.81 90.94 -6.06% 96.35 89.26 -7.36% Inter Freq HOSR Degraded with decrease HHO attempts while the failures were stable
The best Cell Average HSDPA Users 110.46 110.10 -0.33% 159.54 164.33 3.00% Same Trend
Cell_DCH Users 194.62 193.18 -0.74% 266.35 265.92 -0.16% Same Trend
HSDPA User Average Throughput (Kbps) 1109.12 863.54 -22.14% 808.13 582.13 -27.97% HSDPA user Throughput degraded due to increase load on F1/F2 from F7 and carrier
imbalance
Cell DL Average Thrpughput (kbps) 2204.91 2201.00 -0.18% 2008.96 2086.46 3.86% Marginal Impact
HSUPA User average throughput(kbps) 239.67 248.67 3.76% 198.00 221.67 11.95% Same Trend
Cell Freq RTWP(dBm) -102.32 -102.32 0.00% -101.23 -100.94 -0.28% Marginal Impact
Cell TCP Utilization Ratio(%) 48.49% 47.37% -2.30% 55.87% 56.04% 0.32% Same Trend

PRE DATE: 24-25-26 September 2018


POST DATE: 01-02-03 October 2018
CS-BH: 1900hrs
PS-BH:2200hrs
ZTE CMPAK :: Central

3G KPI’s Trend :: Carrier Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Carrier Level


ZTE CMPAK :: Central

3G Load Balance KPI’s Trend :: Carrier Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Cluster Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Cluster Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Cluster Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Cluster Level


ZTE CMPAK :: Central

3G KPI’s Trend :: Cluster Level


ZTE CMPAK :: Central

Observations and Conclusions:


The following observations have been made from CS Service Prioritization Trial in Gujrat City Cluster

Drive Test Result Perspective

 In Pre Trial scenario, DT call was getting dragged for a longer time until RSCP meets the Inter Freq HO Criteria of 100dBm. While in post Scenario,
mostly DT calls are timely handed over to the next dual carrier cell due to SOFT HOSR Process.

 In Post DT most of the time UE quickly reselect to F1/F2 from F7 due to which mostly CS Call established on F1/F2 but not always. Some call may
established on F7 which cause same dragging issue in post DT

 In Pre and Post both scenarios, no call drop was occurring because inter-frequency coverage based Handover Relations are already defined which save
the call from being dropped. However, EcNo slightly degraded in post DT due to increase load on F1/F2 from F7

KPI’s Result Perspective

 After Trial CS traffic was reduced on F7 and shared with F1/F2 but not completely became zero which is required

 PS Traffic was reduced on F7 and shared with F1/F2 from F7 due to idle mode parameters modification but coming back to F7 through load balance
based on HSPA number which is under discussion with Chinese expert

 RRC, PS CDR and HSDPA user throughput was degraded due to increased load on F1/F2 carriers, carrier imbalance and bad EcNo

 Inter Freq HOSR was degraded due to decrease in Inter Freq HO Attempts while the failures were almost stable

Below Conclusions can be drawn from overall trial aspects.

 From DT Point of view, a little improvement in call dragging issue but not completely resolved
 From KPI point of view, we have degradation in KPI’s e.d RRC, PS CDR and Throughput caused bad user experience
 In view of above points, CS Service Prioritization Trial is recommended to be reverted back to utilize all the carriers and improve the KPI’s
Thank you

You might also like