System Optimisation Group

China GSM Core Engineering

August 11, 2000

Jim Luan, Lin Mubao

System Optimisation Group
China GSM Core Engineering

Drive Test Procedure
Preparation
Drive Test
FICS
Netplan

VOT/GEP

Statistics Analysis

Problem Finding
02/01/12

Motorola Internal Use Only

2

System Optimisation Group
China GSM Core Engineering

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

Motorola Internal Use Only

3

System Optimisation Group
China GSM Core Engineering

Preparation (2)





Frequency Plan & Configuration map
Software:TEMS, FICS, GEP, VOT
Hardware: TEMS, GPS, Portable PC
Test Problem Sheet
Route
Map

02/01/12

Motorola Internal Use Only

4

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 5 .

System Optimisation Group China GSM Core Engineering TEMS Introduction • Interface • Functions 02/01/12 Motorola Internal Use Only 6 .

STA Much shorter cycle time by VOT and GEP.NP/.FMT Excel VB .System Optimisation Group China GSM Core Engineering Log File Process TEMS Log File FICS . VOT/GEP Motorola Internal Use Only 7 .CSV .TXT NetPlan Route Map 02/01/12 .

System Optimisation Group China GSM Core Engineering TEMS . • • • • • • • • • 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 Motorola Internal Use Only 8 .log file Analysis Below lists common problems which can be observed from Drive Test Log.

no dedicated spectrum for BCCH 02/01/12 Motorola Internal Use Only 9 . only decode same site BSICs – Channel interference – Non-BCCH carrier.System Optimisation Group China GSM Core Engineering Undecoded BCCH (1) Description: – BSICs can’t be decoded in 5s – Usually consider 3 strongest neighbors Reason: – GCLK shift.

System Optimisation Group China GSM Core Engineering Undecoded BCCH (2) 02/01/12 Motorola Internal Use Only 10 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 11 .

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 . not through GUI • Never use OMC-R Proxy Cell to propagate external neighbor information – – – – 02/01/12 N < hreqt.System Optimisation Group China GSM Core Engineering 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 cell’s LAC/BCCH/BSIC in add_neighbor is different from those in equip_rtf • Engineer modifies external neighbor at MMI. Great HO_MARGIN.

System Optimisation Group China GSM Core Engineering No Handover (2) 02/01/12 Motorola Internal Use Only 13 .

full BTS/MS power must be reached before handover – Large handover_recognized_period and bssmap_t7 setting – Refer to GSM BSS Statistics Analysis Handbook 02/01/12 Motorola Internal Use Only 14 .System Optimisation Group China GSM Core Engineering 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.

System Optimisation Group China GSM Core Engineering Delay Handover (2) 02/01/12 Motorola Internal Use Only 15 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 16 .

System Optimisation Group China GSM Core Engineering Ping Pong Handover (2) 02/01/12 Motorola Internal Use Only 17 .

especially type 5 02/01/12 Motorola Internal Use Only 18 .System Optimisation Group China GSM Core Engineering 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.

System Optimisation Group China GSM Core Engineering Negative Handover (2) -59dBm before HO 02/01/12 -66dBm after HO Motorola Internal Use Only 19 .

System Optimisation Group China GSM Core Engineering 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 can’t be decoded Motorola Internal Use Only 20 .

System Optimisation Group China GSM Core Engineering OverShooting (2) 02/01/12 Motorola Internal Use Only 21 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 22 .

System Optimisation Group China GSM Core Engineering High Overlapping (2) -65dBm -65dBm Over Lapping Area -65dBm -65dBm 02/01/12 Motorola Internal Use Only 23 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 24 .

System Optimisation Group China GSM Core Engineering No Dominant Server (2) 02/01/12 Motorola Internal Use Only 25 .

no & delay handover Motorola Internal Use Only 26 . noise level is the key point Reason: – – – – 02/01/12 Lack of cell site BSIC of dominant server can’t be decoded Dominant server has blocking or cell-bar Handover problem.System Optimisation Group China GSM Core Engineering Poor Coverage (1) Description: – – – – Low rxlevel with rxquality In rural area. rxlevel is less than 35 (-85dBm) Different location has different threshold. missing & incorrect neighbor. negative handover. E. rxlevel is less than 15 (-95dBm) In city center.g.

System Optimisation Group China GSM Core Engineering Poor Coverage (2) 02/01/12 Motorola Internal Use Only 27 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 28 .

System Optimisation Group China GSM Core Engineering Unreasonable Serving Area (2) Cell ID:101 BCCH: 35 02/01/12 Cell ID:102 Cell ID:103 BCCH: 40 BCCH: 45 Motorola Internal Use Only 29 .

System Optimisation Group China GSM Core Engineering Interference (1) Description: – High rxlevel with rxquality Reason: – – – – 02/01/12 Channel interference Not using dominant server No handover Turn the corner with delay handover Motorola Internal Use Only 30 .

System Optimisation Group China GSM Core Engineering Interference (2) 02/01/12 Motorola Internal Use Only 31 .

so return to source cell – MS sends HO FAILURE and UL-SABM to source cell and there is response Reason: – – – – 02/01/12 Channel interference Poor coverage External interference at UL. like wideband repeator Refer to GSM BSS Statistics Analysis Handbook Motorola Internal Use Only 32 .System Optimisation Group China GSM Core Engineering Handover Failure (1) Description: – MS fails to reach target cell.

System Optimisation Group China GSM Core Engineering Handover Failure (2) 02/01/12 Motorola Internal Use Only 33 .

like wideband repeator Refer to GSM BSS Statistics Analysis Handbook Motorola Internal Use Only 34 .System Optimisation Group China GSM Core Engineering Handover Loss (1) Description: – MS fails to reach target cell. but can’t return to source cell – MS sends HO FAILURE and UL-SABM to source cell but no response Reason: – – – – 02/01/12 Channel interference Poor coverage External interference at UL.

System Optimisation Group China GSM Core Engineering Handover Loss (2) 02/01/12 Motorola Internal Use Only 35 .

UL path loss >>> DL path loss Refer to GSM BSS Statistics Analysis Handbook Motorola Internal Use Only 36 .System Optimisation Group China GSM Core Engineering UL Drop (1) Description: – BSS doesn’t receive UL SACCH for link_fail times – BSS stops transmitting DL power Reason: – – – – 02/01/12 External interference Channel interference Faulty ancillary.

System Optimisation Group China GSM Core Engineering UL Drop (2) 02/01/12 Motorola Internal Use Only 37 .

System Optimisation Group China GSM Core Engineering 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 02/01/12 Motorola Internal Use Only 38 .

System Optimisation Group China GSM Core Engineering Drop Call (2) 02/01/12 Motorola Internal Use Only 39 .

filter.. so antennas have different coverage footprints Motorola Internal Use Only 40 . E. combiner. Different cable lengths from BTS to antennas Due to air combing.System Optimisation Group China GSM Core Engineering 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.g.

System Optimisation Group China GSM Core Engineering Sudden Power Drop (2) 02/01/12 Motorola Internal Use Only 41 .

e.System Optimisation Group China GSM Core Engineering MS Power Rapid Increase (1) Description: – MS rapidly increases its TX power due to • Optimised Power Control or • UL SACCH multiframes aren’t received for link_fail link_about_to_fail times Reason: – Sudden UL interference. channel interference – Too much rapid power down – l_rxlev_ul_p is too small 02/01/12 Motorola Internal Use Only 42 . wideband repeator.g.

System Optimisation Group China GSM Core Engineering MS Power Rapid Increase (2) UL power rapid increase from 19 to 5 suddenly 02/01/12 Motorola Internal Use Only 43 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 44 .

System Optimisation Group China GSM Core Engineering 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 Motorola Internal Use Only 45 .

g.g.g.System Optimisation Group China GSM Core Engineering How CM Extractor Help? Extract most BSS parameter for reference • Cell – e. ho_margin. antenna_select… • RTF – check any incorrect external neighbor • Neighbor – e.P… • BTS – e. delay_timer… 02/01/12 Motorola Internal Use Only 46 . hreqave.N.hreqt.

System Optimisation Group China GSM Core Engineering How NPM Help? • Provide cell statistics for VOT display • Provide BSS and system level 23 key statistics • Provide detail troubleshooting statistics 02/01/12 Motorola Internal Use Only 47 .