Drive Test Analysis

System Optimisation Group
China GSM Core Engineering
August 11, 2000
Jim Luan, Lin Mubao

Drive Test Procedure

Preparation
Drive Test
FICS
Netplan
VOT/GEP
Statistics Analysis
Problem Finding
02/01/12
Motorola Internal Use Only

Preparation (1)
Definition File
Without it, it is impossible to observe overshooing neighbors
GenDef7.exe can convert FP to definition file
Neighbor list with

definition file
02/01/12
Neighbor list
without definition
file

Preparation (2)
Frequency Plan & Configuration map

Software:TEMS, FICS, GEP, VOT
Hardware: TEMS, GPS, Portable PC
Test Problem Sheet
Route
Map
02/01/12

Drive Test
For Benchmark
2 minutes per call
10 15 minutes a log files
Force to appropriate band (GSM only, DCS
only or Dual)
For Special Problem

Planning route
No limitation
02/01/12

TEMS Introduction
Interface
Functions
02/01/12

Log File Process

TEMS Log File
FICS
.FMT
Excel VB
.NP/.TXT
NetPlan
Route Map
02/01/12
.CSV
.STA
Much shorter
cycle time by VOT
and GEP.
VOT/GEP

TEMS .log file Analysis

Below lists common problems which can be observed from Drive Test Log.
Undecoded BCCH
BSIC Undecode in Other Site
No Handover
Delay Handover
Ping Pong Handover
Negative Handover
Overshooting
High Overlapping
No Dominant Server
02/01/12
Poor Coverage
Unreasonable Serving Area
Interference
Handover Failure
Handover Loss
UL Drop
Drop Call
Sudden Power Drop
MS Power Rapid Increase

Undecoded BCCH (1)

Description:
BSICs cant be decoded in 5s
Usually consider 3 strongest neighbors
Reason:
GCLK shift, only decode same site BSICs
Channel interference
Non-BCCH carrier, no dedicated spectrum for
BCCH
02/01/12

Undecoded BCCH (2)
02/01/12
10

BSIC Undecode in Other Site

Description:
BSIC in same site can be decoded but not for
other sites
Handover can only happen in intra-site basis
It is similar to former Undecoded BCCH case
Reason:
GCLK shift
GCLK recalibration is required
No one monitors OMC-R alarms
02/01/12
11

No Handover (1)
Description:
Neighbor BSIC is decoded and COMMON handover requirement is
fulfilled but there is never a handover
Reason:
Missing neighbor
No such neighbor in CM database
Incorrect external neighbor

Target cells LAC/BCCH/BSIC in add_neighbor is different from those in
equip_rtf
Engineer modifies external neighbor at MMI, not through GUI
Never use OMC-R Proxy Cell to propagate external neighbor information
02/01/12
N < hreqt. Great HO_MARGIN. Improper algorithm 1-7 setting

Missing_rpt =1
Serving cell overshoots/covers too far away
Refer to GSM BSS Statistics Analysis Handbook
12

No Handover (2)
02/01/12
13

Delay Handover (1)

Description:
Neighbor BSIC is decoded but handover occurs in
much later time
Reason:
All possible neighbors suffer blocking
Large hreqt * hreqave
qual_power_flag is enabled, full BTS/MS power must
be reached before handover
Large handover_recognized_period and bssmap_t7
setting
02/01/12
14

Delay Handover (2)
02/01/12
15

Ping Pong Handover (1)

Description:
Lot of handovers between cells
Time between Handover is around hreqt*hreqave of
such HO cause
Reason:
02/01/12
Improper hardware calibration

Hardware fault
UL/DL interference
Negative handover
Different coverage footprint for antennas of a cell
16

Ping Pong Handover (2)
02/01/12
17

Negative Handover (1)

Description:
Serving cell hands over to a weaker neighbor
Reason:
ho_only_max_power is enabled
qual_margin_flag is disabled
ho_margin_usage_flag is enabled with negative
ho_margin_rxqual/rxlev
Negative HO_MARGIN
Micro-cellular algorithms are enabled, especially type 5
02/01/12
18

Negative Handover (2)

-59dBm
before
HO
02/01/12
-66dBm
after
HO
19

OverShooting (1)
Description:
Cell shoots at far distance but that location has
closer cells around
Reason:
02/01/12
Overshooting cell has small downtilt, 0 degree!

Overshooting cell has too high altitude
Closer cells have overshooting as well
BSIC of closer cells cant be decoded
20

OverShooting (2)
02/01/12
21

High Overlapping (1)

Description:
Cells have major rxlevel difference within
5dB
Reason:
Overshooting
Too many cells in that area
Poor antenna downtilt
02/01/12
22

High Overlapping (2)

-65dBm
-65dBm
Over Lapping Area
-65dBm
-65dBm
02/01/12
23

No Dominant Server (1)

Description:
Rxlevel of best neighbors are close to that of
serving cell
Reason:
Poor antenna downtilt
Lack of near-by site
02/01/12
24

No Dominant Server (2)
02/01/12
25

Poor Coverage (1)

Description:
Low rxlevel with rxquality

In rural area, rxlevel is less than 15 (-95dBm)
In city center, rxlevel is less than 35 (-85dBm)
Different location has different threshold, noise level is the key
point
Reason:
02/01/12
Lack of cell site

BSIC of dominant server cant be decoded
Dominant server has blocking or cell-bar
Handover problem. E.g. missing & incorrect neighbor, negative
handover, no & delay handover
26

Poor Coverage (2)
02/01/12
27

Unreasonable Serving Area (1)

Description:
Coverage area of the cell is incoherent to the
antenna direction
Reason:
Wrong cable connection to antennas
Incorrect record of antenna orientation
Incorrect ANTENNA_SELECT
02/01/12
28

Unreasonable Serving Area (2)

Cell ID:101
BCCH: 35
02/01/12
Cell ID:102
Cell ID:103
BCCH: 40
BCCH: 45
29

Interference (1)
Description:
High rxlevel with rxquality
Reason:
02/01/12
Not using dominant server
No handover
Turn the corner with delay handover
30

Interference (2)
02/01/12
31

Handover Failure (1)

Description:
MS fails to reach target cell, so return to source cell
MS sends HO FAILURE and UL-SABM to source cell
and there is response
Reason:
02/01/12
Poor coverage
External interference at UL, like wideband repeator
32

Handover Failure (2)
02/01/12
33

Handover Loss (1)

Description:
MS fails to reach target cell, but cant return to source
cell
MS sends HO FAILURE and UL-SABM to source cell
but no response
Reason:
02/01/12
Poor coverage
External interference at UL, like wideband repeator
34

Handover Loss (2)
02/01/12
35

UL Drop (1)
Description:
BSS doesnt receive UL SACCH for link_fail times
BSS stops transmitting DL power
Reason:
02/01/12
External interference
Faulty ancillary. UL path loss >>> DL path loss
36

UL Drop (2)
02/01/12
37

Drop Call (1)

Description:
DL case: Radio_link_timeout counter decreases to 0
UL case: link_fail counter decreases to 0
Layer 2: BSS/MS send SABM/DISC in every T200 for
N200+1 times, and no response from recipient
Reason:
All cases in this presentation
02/01/12
38

Drop Call (2)
02/01/12
39

Sudden Power Drop (1)

Description:
Dedicated ARFCN has significant non-power control
rxlevel difference from rxlevel of BCCH
Reason:
02/01/12
No/improper TX power calibration

Faulty ancillary. E.g. combiner, filter..
Different cable lengths from BTS to antennas
Due to air combing, so antennas have different
coverage footprints
40

Sudden Power Drop (2)
02/01/12
41

MS Power Rapid Increase (1)

Description:
MS rapidly increases its TX power due to
Optimised Power Control or
UL SACCH multiframes arent received for link_fail link_about_to_fail times
Reason:
Sudden UL interference, e.g. wideband repeator,
channel interference
Too much rapid power down
l_rxlev_ul_p is too small
02/01/12
42

MS Power Rapid Increase (2)
UL power rapid
increase from 19 to
5 suddenly
02/01/12
43

How GEP Help?

Help to identify below problem in VISUAL basis
Co-channel interference
Adjacent-Channel interference
Mutual neighbor
Missing neighbor
Unreasonable neighbor
Incorrect external neighbor
02/01/12
44

How VOT Help?

Help to identify below problem in VISUAL basis
Ping pong HO
Overshooting
No dominant server
Poor coverage
Unreasonable serving area
Interference
HO failure
HO loss
Drop call
02/01/12
45

How CM Extractor Help?

Extract most BSS parameter for reference
Cell e.g. hreqave,hreqt,N,P
BTS e.g. antenna_select
RTF check any incorrect external neighbor
Neighbor e.g. ho_margin, delay_timer
02/01/12
46

How NPM Help?

Provide cell statistics for VOT display
Provide BSS and system level 23 key statistics
Provide detail troubleshooting statistics
02/01/12
47

Drive Test Analysis

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Drive Test Analysis

Uploaded by

Copyright:

Available Formats

System Optimisation Group

China GSM Core Engineering

August 11, 2000

Jim Luan, Lin Mubao

System Optimisation Group

Drive Test Procedure

Motorola Internal Use Only

System Optimisation Group

Neighbor list with

Motorola Internal Use Only

System Optimisation Group

Frequency Plan & Configuration map

Motorola Internal Use Only

System Optimisation Group

For Special Problem

Motorola Internal Use Only

System Optimisation Group

Motorola Internal Use Only

System Optimisation Group

Log File Process

Motorola Internal Use Only

System Optimisation Group

TEMS .log file Analysis

Motorola Internal Use Only

System Optimisation Group

Undecoded BCCH (1)

Motorola Internal Use Only

System Optimisation Group

Undecoded BCCH (2)

Motorola Internal Use Only

System Optimisation Group

BSIC Undecode in Other Site

Motorola Internal Use Only

System Optimisation Group

Incorrect external neighbor

N < hreqt. Great HO_MARGIN. Improper algorithm 1-7 setting

System Optimisation Group

Motorola Internal Use Only

System Optimisation Group

Delay Handover (1)

Motorola Internal Use Only

System Optimisation Group

Delay Handover (2)

Motorola Internal Use Only

System Optimisation Group

Ping Pong Handover (1)

Improper hardware calibration

Motorola Internal Use Only

System Optimisation Group

Ping Pong Handover (2)

Motorola Internal Use Only

System Optimisation Group

Negative Handover (1)

Motorola Internal Use Only

System Optimisation Group

Negative Handover (2)

Motorola Internal Use Only

System Optimisation Group

Overshooting cell has small downtilt, 0 degree!

System Optimisation Group

Motorola Internal Use Only

System Optimisation Group

High Overlapping (1)

Motorola Internal Use Only