Optimization and Log File Analysis in GSM

Optimization And Log File Analysis In GSM


1.

INTRODUCTION
Every alive Network needs to be under continues control to maintain/improve
the performance. Optimization is basically the only way to keep track of the network
bylooking deep into statistics and collecting/analyzing drive test data. It is keeping an eyeon
its growth and modifying it for the future capacity enhancements. It also helpsoperation and
maintenance for troubleshooting purposes.Successful Optimization reuires!
" #ecognition and understanding of common reasons for call failure
" $apture of #% and digital parameters of the call prior to drop
" &nalysis of call flow' checking messages on both forward and reverselinks to establish
(what happened)' where' and why.Optimization will be more effective and successful if you
are aware of what you aredoing. *he point is that you should now where to start' what to do
and how to do.
1.1.Purpose and Scope of Optimization
*he optimization is to intend providing the best network uality using availablespectrum as
efficiently as possible. *he scope will consist all below+
" %inding and correcting any e,isting problems after site implementation andintegration.
" -eeting the network uality criteria agreed in the contract
.
" Optimization will be continuous and iterative process of improving overallnetwork uality
." Optimization can not reduce the performance of the rest of the network.
"&rea of interest is divided in smaller areas called clusters to make optimizationand follow up
processes easier to handle
1.2. Optimization Process
Optimization process can be e,plained by below step by step description!
1.2.1.Problem nal!sis
&nalyzing performance retrieve tool reports and statistics for the worst performing .S$s
and/or Sites
/iewing &#0 #eports for .S$/Site performance trends
E,amining 1lanning tool $overage predictions&nalyzing previous drive test data
2iscussions with local engineers to prioritize problems$hecking
$ustomer $omplaints reported to local engineers
1.2.2. C"ec#s Prior to ction
$luster definitions by investigating .S$ borders' main cities' freeways'ma3or roads
Investigating customer distribution' customer habits 4voice/data usage5
#unning specific traces on Network to categorize problems
$hecking trouble ticket history for previous problems
$hecking any fault reports to limit possible hardware problems prior totest
1.2.$. Dri%e Testin&
1reparing &ction 1lan
2efining drive test routes
$ollecting #SSI 6og files
Scanning freuency spectrum for possible interference sources
#e7driving uestionable data
.
1.2.'. Sub(ects to In%esti&ate
Non7working sites/sectors or *#8s
In7active #adio network features like freuency hopping
2isabled 91#S
Overshooting sites 7 coverage overlaps
$overage holes
$/I' $/& analysis
:igh Interference Spots
2rop $alls
$apacity 1roblems
Other Interference Sources
-issing Neighbors
One7way neighbours
1ing71ong :andovers
Not happening handovers
&ccessibility and #etainability of the Network Euipment
1erformance%aulty
Installations
1.2.).fter t"e Test
1ost processing of data
1lotting #8 6evel and 0uality Information for overall picture of the driven area
Initial 2iscussions on drive test with 6ocal engineers
#eporting urgent problems for immediate action
&nalyzing Network feature performance after new implementations
*ransferring comments on parameter implementations after new changes
1.2.*. Recommendations
2efining missing neighbor relations
1roposing new sites or sector additions with .efore ; &fter coverage plots
1roposing antenna azimuth changes
1roposing antenna tilt changes
1roposing antenna type changes
.*S Euipment/%ilter change
#e7tuning of interfered freuencies
.SI$ changes
&d3usting :andover margins 41ower .udget' 6evel' 0uality' <mbrella:Os5
&d3usting accessibility parameters 4#8 6ev &cc -in' etc..5
$hanging power parameters
&ttenuation &dds/#emovals
-:&/*-& adds