P3 Score Improvement Through Parameter Optimization
P3 Score Improvement Through Parameter Optimization
By:
Shehraz Shaikh/s00363887
Abstract:
Operator V has been in the third position after Operator T and Operator O in
the 2014 and 2015 benchmarks and stepped up the game in 2016 with
Huawei Country A as a partner in working towards improving OPERATOR
V’s User Experience and thereby translating into a higher score in 2016 P3
CommsDay Mobile Benchmark.
OPERATOR V’s strong point has been UL throughput, however, it always lost points on DL
throughput, CS call setup delay, qualifiers resulting in a snowball effect and coming out 3 rd in
most of these categories and overall scores.
This report describes the approach of using Optimization parameters and techniques in
improving KPIs such as Service access delay, DL/UL Throughput, etc.
Huawei performed P3 like benchmark tests (in two major cities) all through the year of 2016 in
each of the Quarters. Q1 results were deeply analyzed and certain focus areas were selected
for optimization.
CS Benchmark Analysis:
CSFB KPIs and breakdown analysis showed OPERATOR V’s short comings in many areas, few
are listed below:
PS KPIs and breakdown analysis showed OPERATOR V’s short comings in many areas, few
are listed below:
• Call setup failures/Drops due to coverage/quality (NCCI/ACP project was setup for
overall RF tuning)
• Poor CA performance with low DL grants.
• Poor throughput during handover (large number of handovers in network due to poor RF
tuning).
• Poor 10%ile and average throughput performance.
• Transmission bandwidth limitation/Packet loss/DNS Failures.
Adding onto the above actions, CN team implemented LAC/TAC mapping. Also, Flash CSFB
with RIM was implemented to save delay between LTE RRC Release and UMTS RRC Request.
These actions and good improvement in RF conditions due to RF tuning using ACP
compounded into good improvement in CSFB delay for both 4G-4G and 4G-3G scenarios.
Cross procedure cases were identified from the P3 log analysis which were affecting CS call setup and
causing unqualified call setup. Few of the cross procedure actions were performed and KPIs were
observed for validation as reproducing failures may not be possible in normal testing scenarios.
Good improvement in Paging and Cell Update SR noted along with improved CS/PS Drop rate.
Reduction in RRC and RAB attempts due to Paging and CU overlap optimization as users stay in PCH.
Overall traffic/User number/throughput is maintained.
The main cause for UE to remain in UMTS after the CS call was due to the UE crossing RNC border and
then remaining in UMTS until idle mode and then reselecting back to LTE. When the UE crosses the
RNC border the information that the UE is a CSFB UE is not transferred to the DRNC. Related switches
were enabled and cross border U2L/FR issue was eliminated. Few areas still had UEs being released in
UMTS due to the U2L/FR strategy (non LTE co-located UMTS cells not enabled with U2L/FR).
Further, the U2L Redirection parameters were tuned for quicker return to LTE for PS users that handed
over to UMTS (punishment timer & periodic timer changed from 20s to 10s, Hysteresis 3C=0) and Low
activity trigger for users performing D2F or D2P.
As seen from the above DT results, border area U2L issue has been eliminated. Samples for Calls
starting from UMTS still exist due to no Fast Return enabled in U900 cells and sites with no co-located
Large increase in attempts for U2L redirection noted with other KPIs being stable. Parameters were
rolled out and overall LTE %age increased.
Paging capacity was noted to be available and there was no congestion due to layered paging being
previously rolled out. However, unreasonable LAC borders needed optimization.
Area was studied and LAC/TAC border was moved away from busy areas. Board capacity and RNC
load needs to be reviewed before planning out the areas.
Several call drops reasons were noted to be due to missing neighbors from P3 logs analysis. A sample
analysis is below. Suggest to perform neighbor audit and deploy SON related features if available.
Few samples of call setup failures were detected due to incorrect RACH settings. Incorrect baseline
setting can lead to unnecessary failures. On further indoor testing, more setup failures were found due to
Huawei Confidential 10 | P a g e
low UL Tx Power for the test UEs. 1. PreambleRetransMax was modified to 32 to improve the possibility
to receive RRC CONN REQ message and the issues were resolved.
During one of the rounds of testing, large numbers of drops were noted for 2 handsets in a test car and
the handsets in other car were noted to have low drops as expected. Typical scenario for the drop was
as follows; when NODEB detected an uplink synchronization failure (uplink quality bad), NODEB sent a
RL FAIL IND to RNC and triggered call re-establishment with RL ACT CMD message, but there was no
cell update report from UE with new radio link for the call re-establishment in 5 seconds and the call was
released. Call drops occurred in good DL RF conditions at reasonable TP distances. It was suspected
that the antenna system in the problem car had incorrect settings causing poor sensitivity in UL for the 2
handsets. Issue was raised to P3.
Huawei Confidential 11 | P a g e
2.1.6 MOS improvement
Overall MOS for all operators in Country A is good, however, OPERATOR V MOS values were noted to
have slightly abnormal behavior where the trend suddenly changes at a certain point. Following steps
were taken to narrow down the issue
a. Drive test analysis was analyzed and the issue was noted to be across the entire drive area.
b. Top worst VQI cells were analyzed for any issues.
c. Detailed DT was performed with different locations and scenarios. Testing was performed using
different handsets.
d. From tests performed between different handsets, operator V test handset was noted to have the
issue while handset from other operators had good performance.
e. Issue was narrowed down to the software version of Operator V.
f. Handset vendor provided an updated version and the issue was resolved.
Huawei Confidential 12 | P a g e
2.2 PS Parameter tuning
PS parameters tuning was mainly based on LTE related parameters as UE remains most times in LTE
rather than UMTS. CA performance, MIMO and throughput during handover were the main focus for
optimization.
Below mentioned parameters were implemented and throughput during and after handover were
improved.
Implementation was done in an area with several handovers with mixed coverage scenarios (good
coverage and poor coverage). Comparison table below shows different KPIs and the improvement they
brought.
Results were evident from KPIs as well, below charts show some of the KPIs and the impact of the
Huawei Confidential 13 | P a g e
parameters on them.
• DT and KPIs such as MIMO Rank2 %age, MCS and Throughput show improvement with the
trials.
• Overall, no KPI degradation noted.
LTE CA performance in the network was noted be poor with large number of Scell configurations while
low activation or delayed attempts.
Huawei Confidential 14 | P a g e
Active Buffer length and delay settings were default (9KB/50ms) making it difficult to activate Scell and
PCell would handle all the data traffic. Few recommendations were trialed and implemented.
With the above setting SCell activation rate increases and more users can perform DL based on CA.
After implementing CA Instant Activation Strategy, more small packets will be transmitted with SCC
activated, which will cause the “CA User DL Throughput” KPI decrease, the reason is: Throughput =
Traffic Volume / Traffic Time, more small packets are taken into account will cause the Traffic Time
Huawei Confidential 15 | P a g e
increased more significantly compared to the Traffic Volume. However, the user experience will be
improved due to the user has more chance to be scheduled in the MAC layer.
At the beginning of 2016, OPERATOR V network was ready to be trialed and deployed with 3CC as it
had 3 carriers of LTE with up to 40MHz of total bandwidth in most of the cities. Band combinations of
B3/B3/B5 and B1/B3/B5 were available and compatible handsets such as Samsung Note 5 and Galaxy
S7 were recently launched, also handsets from other vendors were now being available and increasing
the requirement of 3CC to be provided to users.
Above PCC/SCC strategy with CA Group based configuration was trialed and deployed in early 2016
bringing in a good boost to the DL throughput KPI.
In OPERATOR V network, SCell DL Grants were noted to always be low with almost all RBs being
available from the carrier. There were no limitations on the server side of the transmission bandwidth as
the PCell DL Grants were at healthy levels. DRX receive DTX Process Optimization was trialed and
improvements in DL grants for SCell were very evident.
Huawei Confidential 16 | P a g e
From DT, Obvious increase in DL throughput was noted in the SINR 0 to 15 ranges (most test samples)
with similar RB counts as Pre data and much higher DL RB grants. This change was double confirmed
with a rollback of the switch and the grant/throughput levels returned to previous levels. These changes
were verified from network KPIs as well, as follows.
Huawei Confidential 17 | P a g e
KPIs show clear increase in SCell traffic and Throughput with increase rBler due to increased
retransmissions for UEs that were actually on DRx and not moved to DRx due to wait timer introduced
by the switch. Overall good results were observed and the optimization was rolled out over the network
resulting in better utilizing the Scell in a CA activated scenario.
PS data qualifier, especially for webpage download was noted to have poor performance. On initial
analysis, large number of DNS failures was suspected to be causing the failures.
Most of the qualifier failures were due to timeout (max download duration is 10s). 10.143.147.147 is the
main DNS server and if DNS fails or has no reply, secondary server 10.143.147.148 is sent a DNS
request. The trend for almost all failures was that the main server did not send a response and then the
secondary server was requested after 5s, effectively halving the download time available for webpage
Huawei Confidential 18 | P a g e
download. Sample failure session shown below,
P3 logs were analyzed and few areas where repeated failures occurred were selected for testing and
tests were performed at off-peak and peak hours. No failures were observed for off-peak, however peak
hours tests showed large number of DNS failures.
PCAP traces from PGW/eNB/UE were compared and end to end check for DNS messages was done,
identifying that all DNS requests were received by the PGW in the UL from UE via eNB to PGW and the
PGW responds to the request but is not received by either the eNB or the UE. This observation was
shared with OPERATOR V CN and Transmission teams and it was found that transmission capacity
from the Hub site towards a very large number of sites in the metro area were reaching full capacity
during peak hours and required expansion.
Several qualifier failures were found for data stream DL and file DL scenarios with a wireshark message
called TCP window full. It occurs when Wireshark has identified that the current packet has the exact
payload size that will fill up the receive buffer on the receiving end (based on the latest seen "Window
Size" on a packet from that receiver in the current TCP session). These cases were escalated to
OPERATOR V transmission team and they found bandwidth limitation being the cause.
Huawei Confidential 19 | P a g e
Comparing the Q1 and Final Benchmark results for Data stream DL throughput, good improvement in
throughput was observed.
It was identified that the DSCP settings for UMTS had a higher priority compared to LTE in the current
network scenario where incase high utilization of transmission bandwidth occurs, LTE packets will be
dropped in favor of UMTS. This is still under and study and is planned to be corrected by OPERATOR V.
Huawei Confidential 20 | P a g e
Other cases:
From DT logs, eNB X was identified to have call drops for LTE. Further checking the KPIs found large
number of drops due to MME reasons (eUTRAN generated drops).
Further analyzing using FMA it was found that UE is reporting other PCIs in MR but no handover occurs.
On checking the neighbor list, no neighbors except for own eNB cells were added and the ANR switches
were OFF. ANR was switched ON and the issue was fixed.
Other Activities:
CS related parameters/switches/features:
Huawei Confidential 21 | P a g e
PS related parameters/switches/features:
Huawei Confidential 22 | P a g e
3. Result
Huawei Confidential 23 | P a g e
A great partnership between Huawei and OPERATOR V along with relentless hard work by both parties
resulted in outstanding results in the final benchmarks. OPERATOR V was termed #1 in most cities with
best performance in both Voice and Data with the best year on year improvement compared all other
competitors.
The approach of building a strong base and adding on top enhancements translated to a consistent
performance in all test scenarios in every clutter area of the network, proving that the tried and tested
bottom top method is bound to provide results.
P3 Results for 2016 testing in County A is shown here. Based on scoring, Operator V network scoring
has improved 57% in 2 years and close the gap with other 2 operators.
The main target for Operator V was to achieve best score in major where it has most of its customers.
This target was well achieved with Operator V score being highest for almost all major cities.
Huawei Confidential 24 | P a g e
4. Suggestion
The above details of parameter optimization activities on top of detailed re-planning, layering
strategies, transmission expansions, capacity expansions accelerated the improvements in
Operator V network in order to achieve the results. However, each network is unique and it has
its own challenges and difficulties. In order to optimize network for P3 purposes, the best
starting point is to understand area where it is possible to gain points based on gap analysis and
improve rather than blindly start optimizing everything. The approach has to be holistic and not
narrow.
P3 tests user experience and thereby P3 optimization is different than improving network KPI
and not necessary that activities above improve network KPI. Customer expectations have to
be set and managed to avoid unnecessary rework.
Finally, it is team work that pays off and both internal and external parties need to work in sync
towards the target.
Huawei Confidential 25 | P a g e