Você está na página 1de 9

CSI-Network Service Optimization

NOKIA SIEMENS NETWORK


Siemens Business Park
Jl. MT Haryono Kav.58 60 Jakarta
12780 - Indonesia


This document contains methodology of drive test
especially in sumbagsel area. The purpose of this
document is as standard guideline for drive tester in doing
drive test.

DRIVE TEST METHODOLOGY
Sumbagsel Area
Drive Test Methodology

I. Introduction
Drive test is one of method to measure quality of open air interface. Many information of drive
test can be used for planning and optimization process such as actual coverage achievement
(compare with 95% coverage probability), quality of air interface (Rx Quality, SQI, FER, C/I), capacity
(Blocking rate), Retainability (Drop call, HOSR) etc. KPI drive test become one of criteria for
acceptance of new site.
II. Equipment and Tools
Equipment and tools for drive test are listed below:
1. Laptop Preinstalled with Windows XP and TEMS Investigation Software
2. TEMS Investigation toolkit (HP TEMS, Charger HP and Data Cable)
3. Area Map and Updated Cell File
4. Inverter
5. GPS (Global Positioning System)

III. Drive Test Preparation
Due to not of all sites are located in near area, some preparation must be done by drive tester
in order to get the good result of drive test. Following things must be paid attention before we do
drive test:
1. Make sure that site is on full configuration OMC info
2. There is no Disabled HW alarm (PLN, VSWR, CU disabled) OMC Info
3. Site is Full Power OMC Info PWRRED = 0
4. There is no HW Problem OMC Info : Perftest Result
5. Make sure that you have get MIF/Coverage Plot from Tornado
6. Check azimuth, height, and tilting of antenna. Is it suitable with DBCR or not?
7. If it is needed, take photo for surround environment (hilly terrain, mountain, river etc) and drive
test route Maybe we need it for Justification Report

IV. Drive Test Mode
For acceptance of new site, 3 kinds of drive test are done. That are idle mode locked, dedicated
mode locked and dedicated mode unlocked.
4.1. Idle Locked Mode
Idle mode locked drive test is done with no call is established along drive test route. The
objective of idle mode drive test is to know actual coverage of site. The step to do idle mode locked
drive test as follow:
- Connect all equipment to laptop via TEMS Investigation Software
- Lock idle connection to ARFCN of sector that will be drive tested
- Start recording log file
- Move from the site until the end edge of coverage plot prediction or edge of service block for
inner city area
- Stop recording file

4.2. Dedicated Locked Mode
Dedicated locked mode drive test is done with call establishment to test call number along drive
test route and connection is pushed to certain ARFCN. The objective of dedicated mode is to measure
quality of air interface (RxQual, SQI) and site performance (Drop call rate, CSSR). The step to do
dedicated mode locked drive test as follow:
- Connect all equipment to laptop via TEMS Investigation Software
- Lock idle connection to ARFCN of sector that will be drive tested
- Disable Handover on dedicated connection
- Start recording log file
- Make call to test number (999 for Telkomsel) continuously without sequence
- Move from the site until the end edge of coverage plot prediction or edge of service block for
inner city area without any dropped call.
- Stop recording file


4.3. Dedicated Unlocked Mode
Dedicated unlocked mode drive test is done with call establishment to test call number along
drive test route. The objective of dedicated mode is to measure quality of air interface (RxQual, SQI)
and especially HOSR performance. The step to do dedicated mode locked drive test as follow:
- Connect all equipment to laptop via TEMS Investigation Software
- Lock idle connection to ARFCN of sector that will be drive tested
- Start recording log file
- Make call to test number (999 for Telkomsel) continuously without sequence
- Move from the site until the end edge of coverage plot prediction or edge of service block for
inner city area without any dropped call.
- Stop recording file

V. Drive Test Troubleshooting
Ideally, the drive testers do on site evaluation to decide whether DT result is in acceptable value
or not? If the result of dive test is not in acceptable value following step can be done as quick
solution:
If the RxLevel is bad near site in idle mode, please describe the situation (if theres a hill/valley,
trees, building, or any other obstacles). Take a picture to justify the condition
If the RxLevel is bad in dedicated mode but was good in idle mode, check the power control
whether it is turned off or not. Please turn it off if SFH isnt applied by asking OMC.
If the RxLevel is bad compared with coverage plot, please check the antenna tilting, antenna
azimuth and terrain condition. Inform all of this information in DT Report.
If sector of site that will be drive tested face to the sea and there is other coverage that face to
the sea, dedicated mode must be in locked mode.
If the SQI is bad, please check used Speech codec whether it is in FullRate, HalfRate, and EFR.
Ideally EFR gives the best SQI value. So, try to get Full rate or EFR speech code when drive test.
If RxQual is bad, please check whether hopping is active or not from Hopping Channel value in
Current Channel Window in TEMS. If no hopping is active, there is possibility of Interference
on BCCH channel. Do scan channel in idle mode to get info from where interference come from.
If there is many intracell handover, please check used TRX from TCH ARFCN on Current
Channel window in TEMS. Many intracell handover occurred due bad quality on current used
channel. Try to lock bad TRX by asking OMC and do re-drive test again.

Appendix
How to Plot DT Result on Coverage Plot
Service block is used as border dedicated coverage. Ideally, handover to other suitable site will occur
at near of border service block. For calculation of RxLev acceptance, the result of drive test is
compared with coverage plot:
1. Service Block Target site to be drive tested is Kertapati DCS

Figure 1 : Service block of Kertapati DCS







2. Coverage Plot of Kertapati DCS

Figure 2 : Coverage Plot of Kertapati DCS

3. Service Block is mapped to Coverage Plot of Kertapati DCS

Figure 3 : Coverage Plot mapped to Service block


4. Result of Idle Locked Drive Test of Kertapati DCS (RxLev Sub) end of drive test is at the border
of service block

Figure 4 : RxLev idle locked of Kertapati DCS

5. Result of Idle Locked Drive Test of Kertapati DCS (RxLev Sub) compared with Coverage Plot

Figure 5 : RxLev compare to Coverage plot


Drive Test Flow Result

Acceptance Value of KPI Drive Test
1. RxLev Sub result table inside Service Block compare to Coverage Plot:

2. Statistical dedicated drive test

3. RxQual 0-5


4. SQI >=18

Você também pode gostar