GSM KPI Analysis and Optimization

Key Performance Indicators (KPI) are a measure of successful network performance and its
quality.
KPIs can be used for the following tasks:

• To monitor and optimize the radio network performance in order to provide better
subscriber quality or to achieve better use of installed network resources

• To detect unacceptable performance related issues in the cellular network immediately.
This will enable the operator to take rapid actions in order to preserve the quality of the
existing network services.

• To Provide radio frequency planners with the detailed information. This will help them
configure the network parameters for optimum use.

 Typically KPI can be categorized into following subcategories:

• Accessibility
• Retainability
• Integrity
• Availability
• Mobility

RF drive test/testing basics

This page describes RF drive test/testing and provide link to RF drive
test/testing tools.
Basics of RF drive test/testing
RF Drive test/testing is the procedure to evaluate performance of wireless
modem/system while driving(or in motion).
The wireless modem or system may include any wireless standards such as
GSM, WCDMA, HSPA, UMTS, LTE, WIMAX, WLAN etc. It helps perform various
measurements as listed below.
RF Drive test measurements
RF drive test measurements may include but not limited to following. -Dropped
call
-handover with same Radio Access Technology(RAT) for example GSM.
-Handover between two RATs, for example between GSM and WCDMA.
-varification of different call quality levels by changing different parameters.
-RF Signal strength measurement.
-sector swapping either full Swap or partial Swap
-Edge and GPRS testing with short and long PS call.
-Short and long duration CS call.
-Idle and connected mode tests.
-Checking RLC throughput as per system requirement/limit.
RF Drive test planning
For RF drive testing particular route and proper SIM with multiple or single RAT
support is required (common RATs are GSM,WCDMA,LTE) . GPS support is
needed in the setup for finding the route of the RF drive test/testing.
RF Drive test typical set up

As shown in the figure, UE(User Equipment) with Antenna is connected with

Laptop having RF drive test software. GPS feature should be incorporated to
support in driving as per planned proper route. External harddisk is used to store
huge amount of data for long duration tests to avoid crash.

RF Drive test data analysis

After acquiring the data for short and long call durations, the logs need to be
analyzed by respective domain experts (GSM, LTE, WCDMA) for finding root
cause of the various problems observed/recorded during drive tests. Typical
problems observed can be call drop, handover/handoff failure, coverage limit
issues, quality limit failures, blocked Call issues as well as data link failure etc.
Engineers usually use MapInfo software tools to prepare thematic Diagrams to
represent received signal level, dropped calls, receiver quality, blocked calls and
Handover failures.
Rf Drive Testing Procedures

Drive Test Procedure

Drive-testing plays an important role in creating and maintaining a strong GSM network. In mobile
communication system drive testing should be used to collect real-time RF information from the
field.Generally this is done using a vehicle, but it can also be carried out on foot where circumstances
dictate (like inside a building for IBS Testing ).In any case, keeping mobile phone network optimized is
vital. Changes in the environment continually affect network performance. Operator can’t afford to have
unhappy subscribers because there are holes in their coverage or because interference is causing
dropped or blocked calls. To migrate to new technologies and applications operators need a drive-test
system that will expand with their needs.

The Purpose of Drive Testing

Drive testing is principally applied in both the planning and optimization stage of network development.
However, there are other purposes for which drive testing can be used:
·       To provide path loss data for initial site survey work
·       To verify the propagation prediction during the initial planning of the network.
·       To verify the network system parameters.
·       To provide the initial test parameters used in Benchmarking.
·       To verify the performance of the network after changes have been made e.g. when a new
·       TRX is added; the removal or addition of a new site; any power adjustments or changes
·       to the antenna; any changes in clutter or traffic habits.
·       To measure any interference problems such as coverage from neighboring countries.
·       To locate any RF issues relating to traffic problems such as dropped or blocked calls.
·       To locate any poor coverage areas.
·       To monitor the network against a slow degradation over time, as well as monitoring the network
·       After sudden environmental conditions, such as windstorm or electrical storms.
·       To monitor the performance of a competitor’s network.
When to Drive Test
Drive testing can take place during the day or at night and is dependant upon the Operator’s
requirements and subscriber habits. Drive testing during the day will imitate the conditions as seen by
subscribers, but may clog up the network if call analysis is being performed. Drive testing during the
night will allow a greater area to be surveyed due to the reduction in vehicular traffic jam. It will also
allow for certain test signals to be transmitted and tested, particularly when setting up a new site,
without interrupting normal operation. However, night-time testing does not imitate the conditions
experienced by subscribers. For planning purposes, drive testing is typically performed at night and for
maintenance purposes, drive testing is performed during the day.
Where to Drive Test
Some areas of a network will have greater performance problems than others. Drive testing should not
be regular throughout the whole network, but should be weighted towards areas where there are
significant RF problems. There may be other areas of the network that require temporary coverage
during a certain time of the year e.g. an exhibition centre or a sports stadium. These areas should be
examined and planned in greater detail. Sometime operators can perform drive test for their customary
check for a certain city or some specific clusters of a city.

Types of drive Test

Drive test can be performed in very many ways. Different types of drive test fulfill different types of
requirement from the customer.
1.     Single site Drive Test
2.     Cluster Drive Test
3.     Acceptance Drive Test
4.     Site Swapping Drive Test
5.     Benchmarking Drive Test
6.     Functionality Test
7.     Walk Test for IBS
Tools ( Drive Test Kit )
Drive testing needs some distinctive type of tools, like some special mobile phones and software. The
followings are list of tools generally required for drive test:
Hardware:
1. Drive test vehicle
Four wheeler vehicles are perfect for drive test to access important but tough access roads or
muddy roads.
2. Power Inverter
This device inverts DC power to AC power. We can use it to invert vehicle’s DC power to AC
power to ensure uninterrupted power supply to the laptop and other electronic devices during
DT.
3. Laptop computer
DT laptop should be with good condition and configuration, like high speed processor and
especially RAM volume should be more for smooth drive testing.
4. Mobile phones and phone charger
Special mobile phones designed with field measurement features. How many mobile phone
should we use during DT depends on the types of DT. Some testing requires one phone and
some other requires two or more. Chargers are also compulsory to keep the phone always
charged.
5. Data cables
Data cable depends upon the model of the mobile phone. Every mobile phone has its own data
cable to transfer measured data to the software installed in the laptop.
6. External antennas
Every mobile phone should be connected with external antenna during DT. Generally when we
use mobile phones inside the car during DT, there is an enormous possibility to get poor field
data. External antenna can minimize this problem. Usually it is attached on top of the vehicle
using a magnetic base.
7. Car GPS
GPS generally used for positioning purpose. In DT, positioning is very important both for
visualization (current position during DT) and analytical point of view. Car GPS also attached on
top of the vehicle like external antenna and connected with laptop through cable.
8. Dongle ( Key for DT software )
One of the most important hardware for drive test is Dongle. Every drive test software needs
this key to run during DT. Except this key all the drive testing features of DT software will be
disabled, until the key is not attached with the laptop. Physically it looks very similar as pen drive.
9. USB Hub
Sometime when we need to work with two or more mobile phones then we need more USB
ports, but our laptop ports are limited. So we have to use USB hub or PCMC USB card, which
will provide us more USB ports to connect more equipment.
Software and necessary files:
1. Data collection Software
This is the software through which field data will be collected. With this software we can analyze
the field data also. This software should be licensed from the vendor company for proper
authorization. Every software has a key to work properly. The most popular software for data
collection is “TEMS Investigation” from ERICSSON.

2. Digital Map
During drive test digital map is necessary for finding the way to reach the selected site/cluster
and do DT according to some predefined routes. We can load the digital map of the whole
region or we can load the map of some specific roads that need drive test. This map comprises
all the accessible DT routs.

3. Cell file
We must load the cellfile into the data collection software. A cellfile contains all the necessary
information related to the site, like ID of that site, assigned frequencies of that site, direction of
the antennas of that site etc. Whenever we load the cellfile we can see the position of that site in
the digital map. Then we can easily find out our required sites form the map and also the roads
to be covered for that site.

4. MapInfo
MapInfo allowed us to include mapping functionality into DT software. We can easily plot our
sites position, routes, and building drawings (for indoor test) with this software. MapInfo has the
ability to combine and display, on a single map, data from a variety of sources that are in
different formats and projections. The software is capable of overlaying vector layers on the
same map.
FIG: MapInfo Software

5. Drivers
All the mobile phones and GPS need driver software to synchronize with the drive test software.
Every equipment drivers must be installed properly in the laptop otherwise they will not work
properly
Introduction & Complete TUTORIAL 3G Rf-Optimization
AND Log-File Analysis

<<CLICK BELOW FOR COMPLETE TUTORIAL>>

>>> CLICK THIS LINK FOR COMPLETE TUTORIAL<<<
Rf-Optimization AND Log-File Analysis
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 by

Get paid to share your links!

looking deep into statistics and collecting/analyzing drive test data. It is keeping an eye
 on its growth and modifying it for the future capacity enhancements. It also helps

operation and maintenance for troubleshooting purposes.

Successful Optimization requires:

• Recognition and understanding of common reasons for call failure

• Capture of RF and digital parameters of the call prior to drop

• Analysis of call flow, checking messages on both forward and reverse

links to establish “what happened”, where, and why.

Optimization will be more effective and successful if you are aware of what you are

doing. The point is that you should now where to start, what to do and how to do.

Purpose and Scope of Optimization

The optimization is to intend providing the best network quality using available

spectrum as efficiently as possible. The scope will consist all below;

• Finding and correcting any existing problems after site implementation and

integration.

• Meeting the network quality criteria agreed in the contract.

• Optimization will be continuous and iterative process of improving overall

network quality.

• Optimization can not reduce the performance of the rest of the network.

• Area of interest is divided in smaller areas called clusters to make optimization

and follow up processes easier to handle.

Optimization Process
Optimization process can be explained by below step by step description:
Problem Analysis
·       Analyzing performance retrieve tool reports and statistics for the worst performing BSCs and/or Sites
·       Viewing ARQ Reports for BSC/Site performance trends

·       Examining Planning tool Coverage predictions

·       Analyzing previous drive test data

·       Discussions with local engineers to prioritize problems

·       Checking Customer Complaints reported to local engineers

 Checks Prior to Action
·       Cluster definitions by investigating BSC borders, main cities, freeways,major roads

·       Investigating customer distribution, customer habits (voice/data usage)

·       Running specific traces on Network to categorize problems

·       Checking trouble ticket history for previous problems

·       Checking any fault reports to limit possible hardware problems prior to test
Drive Testing
·       Preparing Action Plan

·       Defining drive test routes

·       Collecting RSSI Log files

·       Scanning frequency spectrum for possible interference sources

·       Re–driving questionable data

<<CLICK BELOW FOR COMPLETE TUTORIAL>>
>>>CLICK THIS LINK FOR COMPLETE TUTORIAL<<<
Subjects to Investigate

·       Non–working sites/sectors or TRXs

·       In–active Radio network features like frequency hopping

·       Disabled GPRS

·       Overshooting sites – coverage overlaps

·       Coverage holes

·       C/I, C/A analysis

·       High Interference Spots

·       Drop Calls

·       Capacity Problems

·       Other Interference Sources

·       Missing Neighbors

·       One–way neighbors

·       Ping–Pong Handovers
·       Not happening handovers

·       Accessibility and Retainability of the Network

·       Equipment Performance

·       Faulty Installations

After the Test

·       Post processing of data

·       Plotting RX Level and Quality Information for overall picture of the driven area

·       Initial Discussions on drive test with Local engineers

·       Reporting urgent problems for immediate action

·       Analyzing Network feature performance after new implementations

·       Transferring comments on parameter implementations after new changes

Recommendations

·       Defining missing neighbor relations

·       Proposing new sites or sector additions with Before & After coverage plots

·       Proposing antenna azimuth changes

·       Proposing antenna tilt changes

·       Proposing antenna type changes

·       BTS Equipment/Filter change

·       Re–tuning of interfered frequencies

·       BSIC changes

·       Adjusting Handover margins (Power Budget, Level, Quality, Umbrella

·       HOs)

·       Adjusting accessibility parameters (RX Lev Acc Min, etc..)

·       Changing power parameters

·       Attenuation Adds/Removals

·       MHA/TMA adds

Tracking

·       Re–driving areas after implementing recommendations

·       Create a tracking file to follow–up implementation of recommendations

Other Optimization Tips

·       Verifying performance of new sites

·       Verifying handovers

·       Verifying data after Re–Homes

·       Investigating GPRS performance

·       Verifying Sectorizations

·       Collecting DTI Scan files

·       Verifying coverage

·       Verifying propagation model by importing DTI scan files to Planet

·       Periodic Consistency Checks

·       Frequency Planning Check

·       Analyzing cell access parameters

·       Analyzing Handover parameters

·       Analyzing Power control parameters

·       Analyzing Frequency Hopping parameters (HSN, MAIO)

·       Implementing/analyzing optional features

·       Keep helping local engineers with emergency cases

·       Benchmarking