TEMS 2G Drive Test Log Analysis 2011

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

6/5/2013 Motorola Internal Use Only 2
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
Neighbor list without definition file
6/5/2013
Motorola Internal Use Only
Preparation (2)
Frequency Plan & Configuration map Software:TEMS, FICS, GEP, VOT Hardware: TEMS, GPS, Portable PC Test Problem Sheet Route Map
6/5/2013
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
TEMS Introduction
Interface Functions
6/5/2013
Log File Process

TEMS Log File FICS .FMT Excel VB .NP/.TXT NetPlan Route Map
6/5/2013
.CSV
.STA
Much shorter cycle time by VOT and GEP.
VOT/GEP
7
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
6/5/2013
Poor Coverage Unreasonable Serving Area Interference Handover Failure Handover Loss UL Drop Drop Call Sudden Power Drop MS Power Rapid Increase
8
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
Undecoded BCCH (2)
6/5/2013
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
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

6/5/2013
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
Motorola Internal Use Only 12
No Handover (2)
6/5/2013
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 Refer to GSM BSS Statistics Analysis Handbook
Delay Handover (2)
6/5/2013
15
Ping Pong Handover (1)

Description:
Lot of handovers between cells Time between Handover is around hreqt*hreqave of such HO cause
Reason:
Improper hardware calibration Hardware fault UL/DL interference Negative handover Different coverage footprint for antennas of a cell
6/5/2013
16
Ping Pong Handover (2)
6/5/2013
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
Negative Handover (2)

-59dBm before HO -66dBm after HO
6/5/2013
19
OverShooting (1)
Description:
Cell shoots at far distance but that location has closer cells around
Reason:

6/5/2013
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
OverShooting (2)
6/5/2013
21
High Overlapping (1)

Description:
Cells have major rxlevel difference within 5dB
Reason:
Overshooting Too many cells in that area Poor antenna downtilt
6/5/2013
22
High Overlapping (2)

-65dBm
Over Lapping Area
-65dBm
-65dBm
-65dBm
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
6/5/2013
24
No Dominant Server (2)
6/5/2013
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 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
Reason:

6/5/2013
Poor Coverage (2)
6/5/2013
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
6/5/2013
28
Unreasonable Serving Area (2)

Cell ID:101
BCCH: 35
Cell ID:102 BCCH: 40
Cell ID:103 BCCH: 45
6/5/2013
29
Interference (1)
Description:
High rxlevel with rxquality
Reason:

6/5/2013
Channel interference Not using dominant server No handover Turn the corner with delay handover
Interference (2)
6/5/2013
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:

6/5/2013
Channel interference Poor coverage External interference at UL, like wideband repeator Refer to GSM BSS Statistics Analysis Handbook
Handover Failure (2)
6/5/2013
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:
Channel interference Poor coverage External interference at UL, like wideband repeator Refer to GSM BSS Statistics Analysis Handbook
6/5/2013
34
Handover Loss (2)
6/5/2013
35
UL Drop (1)
Description:
BSS doesnt receive UL SACCH for link_fail times BSS stops transmitting DL power
Reason:
External interference Channel interference Faulty ancillary. UL path loss >>> DL path loss Refer to GSM BSS Statistics Analysis Handbook
6/5/2013
36
UL Drop (2)
6/5/2013
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 Refer to GSM BSS Statistics Analysis Handbook
6/5/2013
38
Drop Call (2)
6/5/2013
39
Sudden Power Drop (1)

Description:
Dedicated ARFCN has significant non-power control rxlevel difference from rxlevel of BCCH
Reason:
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
6/5/2013
Sudden Power Drop (2)
6/5/2013
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
MS Power Rapid Increase (2)
UL power rapid increase from 19 to 5 suddenly
6/5/2013
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
6/5/2013
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
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
6/5/2013
46
How NPM Help?

Provide cell statistics for VOT display Provide BSS and system level 23 key statistics Provide detail troubleshooting statistics
6/5/2013
47

TEMS 2G Drive Test Log Analysis 2011

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

TEMS 2G Drive Test Log Analysis 2011

Uploaded by

Copyright:

Available Formats

System Optimisation Group China GSM Core Engineering

August 11, 2000 Jim Luan, Lin Mubao

System Optimisation Group China GSM Core Engineering

Drive Test Procedure

Statistics Analysis Problem Finding

System Optimisation Group China GSM Core Engineering

Neighbor list with definition file

Neighbor list without definition file

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

For Special Problem

System Optimisation Group China GSM Core Engineering

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Log File Process

Much shorter cycle time by VOT and GEP.

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

TEMS .log file Analysis

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Undecoded BCCH (1)

System Optimisation Group China GSM Core Engineering

Undecoded BCCH (2)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

BSIC Undecode in Other Site

System Optimisation Group China GSM Core Engineering

Incorrect external neighbor

System Optimisation Group China GSM Core Engineering

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Delay Handover (1)

System Optimisation Group China GSM Core Engineering

Delay Handover (2)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Ping Pong Handover (1)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Ping Pong Handover (2)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

Negative Handover (1)

System Optimisation Group China GSM Core Engineering

Negative Handover (2)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

System Optimisation Group China GSM Core Engineering

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

High Overlapping (1)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

High Overlapping (2)

Over Lapping Area

System Optimisation Group China GSM Core Engineering

No Dominant Server (1)

Motorola Internal Use Only

System Optimisation Group China GSM Core Engineering

No Dominant Server (2)

Motorola Internal Use Only