LTE FDD Cluster DT_Analysis Report

8/19/2019 LTE FDD Cluster DT_Analysis Report

1/23

LTE FDD Network Planning &

Optimization System-Demo Cluster Area

Optimization Report Budi Prasetyo CS NPO 19:55

1 Overview

1.1 Test Purposes

The major purposes of this evaluation are to learn about the present coverage quality andrunning performance of the network in demo areas. On the basis of the network’s actual

conditions, manage to solve the existing network problems and present suggestions for

performance optimiation especially the coverage and !" throughput performance.

1.2 Test Area

!emo #luster include $ sites , it is an urban area.

https://plus.google.com/105794217618082308448http://www.ltehandbooks.com/search/label/CS%20NPO?&max-results=6http://www.ltehandbooks.com/2015/11/lte-fdd-network-planning-optimization.htmlhttp://www.ltehandbooks.com/search/label/CS%20NPO?&max-results=6http://www.ltehandbooks.com/2015/11/lte-fdd-network-planning-optimization.htmlhttps://plus.google.com/105794217618082308448


2/23

2 Test ResultComparison

2.1 Test result overview

Table %&' test ()* before optimiation overview

Table %&% test result after optimiation overview

2.2 RSRP

++) !T result before optimiation

-igure %&' ++) !T result at &'/


3/23

++) !T result after optimiation

-igure %&% ++) !T result at &%%

-igure %&0 ++) #omparison


4/23

The ++) comparison shows that the percent of ++) poorer than &/1 d2m has decreasefrom 0'.3/4 to %.%54, the coverage become better.

2.3 SINR

*6+ !T result before optimiation

-igure %&$ *6+ !T result at &'/


5/23

*6+ !T result after optimiation

-igure %&1 *6+ !T result at &%%

-igure %& *6+ #omparison


6/23

The *6+ comparison shows that the percent of *6+ poorer than 1 d2 has decrease from

'0.0%4 to /.7$4, the *6+ become better.

2.4 MAC DL Throughput

89# !" Throughput !T result before optimiation

-igure %&3 89# !" Throughput at &'/


7/23

89# !" Throughput !T result after optimiation

-igure %&7 89# !" Throughput at &%%

-igure %&/ 89# !" Throughput #omparison


8/23

The 89# !" Throughput comparison shows that the percent of 89# !" Throughput less

than %58bps has decrease from '/.714 to ./4, the !" throughput become better.

3 Optimization Case

3.1 Random Access Failure Case Analysis

9nalying the !T log at &'/, we found that there are random access failure cases.

-igure 0&' +andom access failure case


9/23

#hecking the )+9#: parameters and found that the parameter setting are not reasonable;

neaby cells shoud not have the same prach#onfig*ndex


10/23

3.3 Handover Failure Case Analysis

3.3.1 Handover failure caused by bad SINR

:ere is one of the handover failure case analysis; => at soruce )#* $0 found )#* $5

stronge enough and send 8easurement +eport, but => did not receive handover

command?++# #onnection +econfiguration@ and then call drop.

-igure 0&% :andover failure case

The => send the 8easurement +eport when serving cell *6+ become very bad?&1. db@.


11/23

=> campus on a new )#* %0 after call drop. -rom these procedures we can consider this

handover and call drop are cause by bad *6+.

Optimiation suggestion; optimiation for *6+.

3.3.2 Handover failure caused by PCI 10 overshooting


12/23

=> catch a )#* '5 where is rather far away. )#* '5 is from site oravia+oofA(O111

=> failure handover to )#* %$ because )#* '5 overshooting and no neighbor relationshipfor this two )#*.


13/23

9nother case is similar caused by )#* '5 overshooting;

=> catch signal from )#* '5 far away.


14/23

Optimiation suggestion;

9dd % downtilt for oravia+oofA(O111A%.

3.3.3 Handover failure caused by PRACH parameter

-rom section 0.', we know that 155$A' and 155$A% have the same )+9#: setting, this can also

affect handover.

The ()* from >8 show that handover success rate is not good for cell 155$A' and 155$A%

ome handover also found related with these two sector during !T.


15/23

Optimiation suggestion;

9djust )9+9#: parameter as section 0.'

3.4 Coverage Case Analysis

3.4.1 Bolnica_SKP5004_3 adjust tilt from 0to 2

!owntilt 5 may eaily caused overshooting to other cell, and according to !T result, area close

to 2olnicaA()155$A0 is not good enough, adjust tilt from 5 to % can enforce the coverage.

-igure 0&0 coverage analysis case%


16/23

3.4.2 Divizija_SKO5073_3 adjust tilt from 0to 3

9ccording to !T result, !iviijaA(O1530A0 is overshooting to site 2olnica.

-igure 0&$ coverage analysis case0

3.5 RS Power Optimization

9fter tilt change, increase the cell + power can enforce the coverage.

Table 0&% parameters optimiation%


17/23

site !D cell na)e para)eter na)e old *alue ne+ *alue

5$$% -.E1&$$/Bolnica/1 cell0eferenceSinalPo+er 1$, 1',

5$$% -.E1&$$/Bolnica/( cell0eferenceSinalPo+er 1$, 1',

5$$% -.E1&$$/Bolnica/' cell0eferenceSinalPo+er 1$, 1',

5$2' -.E1&$$/Di*i3i4a/1 cell0eferenceSinalPo+er 1$, 1',

5$2' -.E1&$$/Di*i3i4a/( cell0eferenceSinalPo+er 1$, 1',

5$2' -.E1&$$/Di*i3i4a/' cell0eferenceSinalPo+er 1$, 1',

51,9 -.E1&$$/6078/' cell0eferenceSinalPo+er 1$, 1',

3.6 Handover Optimization

#omparing the ++) and *6+, most the road ++) is better than &/1 d2m, => can

easily catch signal from neaby site. Optimie the parameter timeToTrigger from 3?%1ms@

to ?'5ms@ can make the => fast handover to a stronger neighbor, thus can let the => stay

at the strongest ++) and *6+ cell.

Optimiation uggestion;

site !D para)eter na)e old *alue ne+ *alue co))ent

5$$% ti)e.o.rier 2 , )easCf!d"5$

5$2' ti)e.o.rier 2 , )easCf!d"5$

5151 ti)e.o.rier 2 , )easCf!d"5$

51,9 ti)e.o.rier 2 , )easCf!d"5$

FDD-FL-PingPong Issue Analysis

Budi Prasetyo CS NPO $1:((

Incident Description (Incident Phenomena)

1 OverviewIn one project, customer found that the user experience is not so good. UE can often

drop from 4G to 3G and also go back to 4G. It seems there is a 4G/3G ing!ong

issue.

https://plus.google.com/105794217618082308448http://www.ltehandbooks.com/search/label/CS%20NPO?&max-results=6http://www.ltehandbooks.com/2015/10/fdd-fl-pingpong-issue-analysis.htmlhttps://plus.google.com/105794217618082308448http://www.ltehandbooks.com/search/label/CS%20NPO?&max-results=6http://www.ltehandbooks.com/2015/10/fdd-fl-pingpong-issue-analysis.html


18/23

s discuss +ith custo)er; user e"perience %


19/23

*t the same time, &e check the same log for UE 3G signal, &e found that UE catch

3G signal exactl+ &hen it lost 4G signal. $hat means UE shift from 4G to 3G.

$his %gure sho& the "-* best (), the legend Invalid means that UE do not catch

3G signal.


20/23

2.2 Lost 4G issue Analysis

e analy3ed the lo and found that UE shift fro) %< to '< after t+o )essae:Measurement

Report and RRC Connection Release.

!n Measurement Report ; UE report -.E ser*in cell 0S0P>9( dB) and U.S neihor cell

0SCP>2( dB)

UE recei#ed RRC Connection Release, this message command UE redirection from 4G


21/23

to 3G at *(0 123.

2.3 Parameters Analysis

!n -.E radio para)eters tale UeRATMeasurement for rateasCf!d"1$,$; these t+o

para)eters：rsrpSr*.rd and rscpSysNr.rd：

rsrpSr*.rd：

solute Decision .hreshold of E>U.0N Ser*in Cell for 0S0P easure)ent dB)

rscpSysNr.rd：

solute Decision .hreshold of U.0N Syste) for 0SCP easure)ent dB)

.hese t+o para)eters )eans that +hen -.E ser*in cell 0S0P lo+er than rsrpSr*.rd and

U.S neihor cell 0SCP is hiher than rscpSysNr.rd; UE +ill hando*er redirection if UE ornet+or? does not support hando*er fro) -.E to U.S

e chec? BSE -.E net+or? para)eters; the *alue for these t+o para)eters are:

rsrpSr*.rd rscpSysNr.rd

solute Decision .hreshold of E>U.0N Ser*in Cell for

0S0P easure)ent dB)

solute Decision .hreshold of U.0N

Syste) for 0SCP easure)ent dB)

lon:>1%$G>%'HIdefault:>115 lon:>1($G>(%HIdefault:>95

>9$ >&,

.he thresholds )a?e UE easily shift fro) %< to 'Pon

suest chane rsrpSr*.rd fro) >9$ to >11$ and rscpSysNr.rd chane fro) >&, to >9$

Solution


22/23

3 Re-test After Parameters

Modification*fter changing parameters in the related sites, &e re!test the same road and found that

UE sta+ al&a+s in 4G.

UE ne*er shift to '< in the sa)e lo +hen +e re>test the sa)e road


23/23

Summary and Notes

4 Suggestion!n order to )a?e UE stay in %< loner and not so easily shift to '

Documents

LTE FDD Cluster DT_Analysis Report