GSM Drive Test:

Prepared By: Ashish Chopra

Index

1. Introduction
1.1 Purpose
1.2 DRIVE TEST- A PART OF OPTIMIZATION
2. Drive Test Tools
2.1 Types of Tools Available
2.2 TEMS Investigation GSM
3. PROCEDURE
3.1 CONNECTION PROCEDURE
4. Modes Of Drive Test
4.1 Idle Mode
4.2 Dedicated Mode
4.3 Frequency Scanning
5 Types of Drive Test
5.1 Benchmarking
5.2 Integration, Verification or Cutover
5.3 Network Maintenance
5.4 Troubleshooting
6. Summary
1. INTRODUCTION

This is a general-purpose document on Methods and Procedures of RF drive test in a GSM

network.

1.1 PURPOSE:

Drive test is a method that is adopted to optimize a GSM network. Once a GSM network is
rolled out, based on network planning tool predictions, the network hardly resembles the
predictions. This happens because of complex nature of the underlying principle based on
which GSM wireless cellular network works. So, Network Operators / Service Providers task
becomes to bring the network back , as nearest as possible, towards the prediction. Through
the systematic process of collecting air interface data from the already built network, status of
the existing network gets recorded. This drive-tested data is processed off-line (through GSM
RF Post Processing Tool) to know the deviation from prediction. As per interpretation of Post
Processing result, configuration changes are performed on the network. Further drive tests are
conducted to record the modified network status. After a few iterations, as-built network is
brought very near to as-predicted network. It is said, under this condition, that the network is
optimized.
However, once optimization is reached the need for drive test does not end. A GSM
wireless cellular network does not remain optimized all through. Status change takes place
because of network expansion (in terms of addition of cell sites), competitors network changes,
change of man made ambience etc. Optimization (data collection through drive test) process
goes on to keep a live network optimized during its lifetime.

1.2 DRIVE TEST- A PART OF OPTIMIZATION:

The position of the drive test in the optimization process of a GSM Network is as shown in the
following block diagram.
Drive
Testing

Action Steps Post

Processing

Data
Analysis
 OPTIMIZATION PROCESS BLOCK DIAGRAM

The drive test is conducted with a goal of collecting measurement data of GSM network
as a function of location. The RF data collected in the drive test is compared with the corresponding
planned data by way of Post Processing. The next step is the Data Analysis, which results in the
recommendation of changes or Action Steps to be taken in network rf parameters. The drive test
needs to be conducted again after implementing the recommendations. This is how the drive test
helps in optimization life cycle of the network. Thus the drive test helps in creating and maintaining
a robust GSM network

2. DRIVE TEST TOOLS

2.1 TYPES OF TOOLS AVAILABLE:

The drive test tool is available as a product consisting of software and hardware components.
Some of the renowned vendors are Ericsson, Aircom, Agilent, Nokia, Sagem etc.

2.2 TEMS INVESTIGATION GSM 7.0 FROM ERICSSON:

The most popular and versatile tool used for Drive tests is TEMS Investigation. The latest version,
Investigation 7.1, supports GSM 850/900/1800/1900, GPRS, EDGE, HSPDA & UMTS.

The hardware required for Investigation 7.1 to run smoothly is given below.

1) A Laptop with 2GHz processor, 1GB of RAM, and soundcard.

2) Hardware Lock Key or Dongle, provided with the TEMS application.
3) 1x4 USB multiplexer.
4) TEMS handset and connecting cables, number of handsets depends on activity being carried
out.
5) GPS receiver with power supply.
6) Mobile power source for charging Laptop in a vehicle , either an inverter or mobile laptop
charger.
7) Frequency Scanner (Optional)

After installation of Investigation 7.1 it is advisable to install the drivers for the TEMS test
phones being used.
3. PROCEDURE:

3.1 CONNECTION PROCEDURE:

In order to connect the Drive test equipment also called kit the following procedure should be
followed.

a) Connect the USB cables to the TEMS test phones..

b) Connect the other end of the USB cables to USB ports on the laptop.
c) Connect the GPS to the laptop, either via USB or via serial port.
d) Insert the Dongle into a USB port.

Note*: If the laptop does not have a sufficient number of USB cables then a 1x4 USB
multiplexer may be used.

e) Switch on the laptop and open Investigation 7.0.

f) The tab named ‘ Control & Configuration’ contains a window called ‘ Port Identification’
g) Click on ‘Identify equipment’, a list of the connected equipment will be displayed.
h) Ensure that all the required equipment is displayed.
i) Click on connect all, this will cause the red mark against the equipment to turn green.
j) The tab named ‘ Overview ‘ contains the basic data to be monitored, including radio
parameters such as RxQual, Rxlevel, etc. The same tab also contains information about the
current channel being used such a CGI, timeslot, ARFCN, etc.
k) Click on logfiles and scroll down to recording properties, here give the path where the
logfiles have to be recorded. Clicking on the record button will allow the data to be
recorded into the desired path.

4. Modes Of Drive Test.

4.1 Idle Mode

Idle mode implies that the test mobile is kept in standby. In other words, no call or SMS is sent.
This mode of drive test is usually done in order to determine the coverage of a particular site or
network. The most important parameter to be monitored in Idle mode is RxLevel. The unit
displayed for this parameter is dBm.

Given below are the accepted values of RxLevel

-10 to –70 dBm Good

-71 to –90 dBm Average

-91 and lower extremely poor

Idle Mode drive test also allows us to monitor the C/I values on the BCCH.
When a new cell becomes the serving cell , the event is termed as a ‘Cell Reselection’.

4.2 Dedicated Mode

Dedicated mode implies that a call has been established by the test mobile. This may either be
an incoming call or outgoing call. The most frequently used number is a test number. The test
number allows us to imitate an actual call as experienced by a subscriber.

A dedicated mode drive test is done in order to verify a number of things. The most important
being call quality and call continuity( handover success).

The most important parameters to be monitored in dedicated mode are:

a) RxQual

0 to 4 Good

5 to 6 Acceptable

7 and above Extremely poor

b) SQI

-20 to 10 Poor

11 to 20 Averages

21 to 30 Good

Other parameters such as hopping C/I, MAIO, TA etc can also be monitored in dedicated mode.
When a new cell takes control of the call in dedicated mode, the event is termed a handover.

4.3 Frequency Scanning

Frequency scanning is the process of scanning multiple frequencies in order to collect data to
feed into a post processing tool. This can be accomplished either by using a scanner or a TEMS
handset with scanning properties.

Frequency scanning is independent of operator, i.e any frequency in any band may be scanned.

The post processing may take place using a number of applications, the description of which are
out of scope of this document.
5. Types of Drive Test

5.1 Benchmarking

Benchmarking is the process of comparing the performance of two or more networks.

Benchmarking may be conducted either for coverage (idle), quality (dedicated) or both.
This activity is usually outsourced to a third party in order to obtain unbiased results.

Benchmarking involves conducting extensive drive test throughout the entire network
with multiple TEMS handsets.

The multiple handsets contain SIM cards of different networks.

Example Case:

Client : Network A

Closest Competitor : Network B

Network A wishes to conduct a benchmarking activity with his closest competitor,

Network B in order to asses quality and coverage.
In order for us to carry out this activity we must use 4 TEMS handsets.

1st Handset : Network A (Idle)

2nd Handset : Network A (Dedicated)
3rd Handset : Network B (Idle)
4Th Handset : Network B (Dedicated)

Using the above configuration we can conduct both coverage and quality drive test
simultaneously for Networks A and B.

The logfiles obtained from this procedure are usually exported as Mapinfo .tab files and
presented for viewing to the client with the appropriate legend.

This activity gives the operator a clear picture of where his network needs to be
upgraded in order to meet the coverage and quality of his competitor.
 5.2 Integration, Verification or Cutover

Integration drive test are done in order to integrate a new site in an existing network.
Verification or cutover is done either when the parameters of a Base station are changed
or when a BTS is swapped for the of a different vendor or type.

The procedure involved in integration and verification is more or less the same, thus
both are clubbed into one category.

This activity should be carried using 2 TEMS handsets with SIM cards of the same
operator. In situations where a second handset is not available , one TEMS handset can
be used to verify and integrate the base station.

The basic procedure to be followed is described below.

a) Confirm from the OMCR that the site is ready. Do not assume that it is fully
functional only from the TEMS information.
b) Confirm BCCH and BSIC.
c) Confirm allocated MAIO , either by repeated calls or by asking OMCR to change
MAIO priorities.
d) Conduct MOC (mobile originating call) for 90 seconds by calling test number.
e) Conduct MTC (mobile terminating call) for 90 seconds by calling MS1 From MS2.
f) Send Test SMS to OMCR and BSS engg.
g) Confirm proper neighbor definition by testing handovers. These may be tested by
driving to different areas or by force latching onto the neighbors.
h) Conduct drive test in order to verify that the footprint of the site is as expected.

This procedure should be conducted for all sectors. All data should be recorded and
every parameter should be thoroughly verified before giving the site an “OK” status.

The above described procedure may be used to perform a cutover, integrate and verify the
parameters of a base station. However if the base station is being swapped, i.e . the type or
vendor of a base station is to be changed we must keep perform a Pre and Post drive in addition
to the above described procedure.

The Post drive should be conducted at least 24 hours after the cutover, while the Pre drive may
be conducted any time prior to swapping. These are conducted in order to ensure that the
parameters after the swap are not degraded in comparison to the parameters prior to the swap.

The procedure for conducting a Pre and Post drive are the same.
 The procedure is as follows:

a) Connect One Handset in Idle Mode and one handset in dedicated mode.
b) The handset in dedicated mode should be put on a loop to make 90 sec calls.
c) Drive around the vicinity till handovers and cell reselections with different base stations are
achieved.
d) Follow the above procedure for all sectors.

Given below is a sample Cutover form.

Date
Parameters PRE CUT POST REMARKS
SDCCH Pref
MAX TX BTS
RXLev Access Min
HO EXIST CONGEST

BCCH_1
BSIC_1
BCCH_2
BSIC_2
BCCH_3
BSIC_3
CGI_1
CGI_2
CGI_3

90 SEC MOC CALL

90 SEC MTC
SMS OMCR
SMS BTS ENGG
MAIO LOCKING
INTRA CELL HANDOVER
INTERCELL HANDOVER

FOOTPRINT

ENGG NAME
5.3 Network Maintenance

Network maintenance drives are carried out in order to ensure that the network is
working as per requirement and also to find faults in the network.

Particular routes are designed so that the major roads and areas of the circle are
encompassed into the drive test.

The TEMS handset is configured into a loop to keep calling the test number for a
particular duration, usually 120 seconds. This allows us to simulate a subscriber moving
through the city and making calls.

The repeated calls allow us to ensure that the different sites along the preplanned route
are capable of setting up calls. Call continuity ( handover success) is also continually
monitored by this activity.

In case of any events such as low level, poor quality, handover failure or call drop,
Another round should be made in order to verify whether the issue was random or
continual. A written record should be maintained of the events that have occurred during
the drive test and the concerned person should be informed of those events.

A major part of the network maintenance drive is to localize and particularize problems
in the network for troubleshooting.

Another byproduct of these drives are the percentage distribution reports.

These reports are extremely important from a management point of view as they
indicate the average quality of the network on a monthly, quarterly and yearly basis.

The procedure for generating these reports is as follows.

a) Export the required logfiles to .FMT or text format.

b) Open the exported file with Microsoft Excel.
c) Delete all columns except for Rx Qual Sub.
d) Create a pivot table as as with Value Vs. Count.
e) If the sum of the count from 0 to 5 is less than 95 %, aim for improvements along
that route.
 Example Pivot Table:

Count of All-RxQual Sub

All-RxQual Sub Total
0 51428 95%
1 473 1%
2 400 1%
3 454 1%
4 427 1%
5 367 1%
6 239 0%
7 358 1%
(blank)
Grand Total 54146

5.4 Troubleshooting

The drive test apparatus is also a very useful means of troubleshooting critical spots in
the network.
After the problem has been localized either via network maintenance or by using the
network statistics, a drive test may be carried out in order to rectify the fault. The
plethora of live information available readily allows an experienced RF enginner to
identify and rectify the network issue. This may be that of call drop, handover failure or
poor quality. By interacting with the OMCR and viewing parameters and changes
through TEMS, an RF engineer can resolve network issues and view the results
immediately.

6. Summary

This document has entailed the basics of conducting a drive test. The different modes, types and
procedures used to carry out a drive test are defined above. It should be remembered that these are
basic guidelines that should be followed; actual procedure depends on the customer and task
requirement.