System Engineering (Drive Test)

July, 14, 2002

Purpose of Drive Test

-Verify the RF coverage plan

-Fine tune the radio predication model. -Check integration of new sites -Handovers -Interference levels (C/I ) -Audit competitor network

What you need?

Basic Requirement -Test Mobile : a. Dual-Band SH888, or b. Single-Band GH688 -SIM-Card : Test SIM -GPS : Supports NMEA-0183 Standard -PCMCIA card : I/O card -Software : Program Disk ( TEMS ) -Local Map : Indicating all site-mark, with BCCH / Bsic values -Frequency Plan : With Neighbor-Lists -File : Cell Definition File -Transportation : Car with cigarette lighter Accessories -Cigarette lighter with Inverter

TEMS Preference Setup

Use sub values if DTX is enabled

Turn on neighbor rxlev display

TEMS Preference setup - DL DTX

Preference: Full value Preference :Sub value

TA: 1 ( 550m ) -> 2 (1100m ) * Estimated distance from serving cell DTX fully occupied

Cell Definition File

Get the OMCR file and then use the frequency summary to merge as the .CEL file. Cell Definition File ( format ):
2 TEMS_-_Cell_names CELL ARFCN BSIC LAT LON MCC MNC LAC CI CI_N_1 LAC_N_1 CI_N_2 LAC_N_2 CI_N_3 LAC_N_3

Checking Layer 3 Message for missing neighbors

Type 5ter info for 900 when serving cell in GSM Type 5 info for 1800 when serving cell in DCS

Servers Neighbor list scanning frequencies

Frequency Scanning for missing neighbor

When you find some missing neighbors!

Scan Tool / Scan Tool Monitor / Scan Tool Graph

Cell Selection to confirm the neighbor handover

You can input any frequency if you want the mobile to clamp on. Confirm problem: H/W(TCU), neighbor list, BSS or MSC database or interference.

Drive Test notification

-When testing a new site, take a round-circle using the site as centerpoint. -Its not a coverage-test, stop at the problem-spot for investigation if possible. -Drop down the environmental condition influencing the RF propagation. -Go through the same road in both direction. -Realize the rule of handover between two cells. -For dual-band system, clarify the algorithm type of GSM/DCS. -Only down-link information can be consulted from TEMS

Layer 3 Message - Mobile originate call example

On RACH

On AGCH
On SDCCH, CM service request for mobile origination, Paging response for mobile termination

Assign to TCH

Layer 3 Message - Channel release

Immediately on the same cell after Channel release for location update request if the originated call at different LAC.

Location update complete

Trouble shooting note - Normal power control is not hardware problem

The downlink power dropped from -38dBm to about 70dBm at the first 3 seconds of mobile origination, properly it is Power control, you need to confirm with system engineer!

Also it may be rapid power down or uplink power control!

Trouble shooting note - Non BCCH power level

When you find the using channel have lower power level than the neighbor rxlev it may be:
1. DL DTX on but havent use SUB value for display 2.Downlink Power control

3. H/W problem with different Tx power level on different TCU.

Non BCCH RTF Channel may not be detected once after the mobile go back to idle mode or in BCCH channel. The only way to know the actual BCCH power during the dedicated mode non-bcch drive test is to add test neighbor.

Trouble shooting note - Direct retry or BPM 1

Handover command instead of TCH Assignment Command !

Example1 ( Cant decode BSIC )

Nothing can be seen

Event: Handover is eager to trigger, but no nearby-neighbor can be decoded for this phenomenon. Suggestion: DL Interference or GCLK problem (Motorola Equip).

Example2 ( No dominant serving cell )

* All the followings are using Hopping-Channels

Poor RxQuality

Dominant Cell ( with RxQualit = 0 )

Event: Poor RxQuality when using hopping channels Suggestion: Coverage overlapping,no dominant cell. Frequency plan, antenna downtilt, handover database setting.

Example3 ( Test Neighbor )

Serving Cell

Test Neighbor

The same

Test Neighbor is used for checking the power-down function of the cell.

Example4 ( Without test neighbor )

Event: Even the two-strongest neighbor cells is with signal-strength higher than the serving cell, but no handover is taken to the any one of the two neighbor-cells. Facts: Since we are using the hopping channel as the serving element, its actual BCCH value may be higher than that of the neighbor-cells ( -66 dBm / -74 dBm ). -Remember, for the same cell:
-TxPower_Bcch => TxPower_HoppingChannel

Example5 ( Handover Failure / Drop Call)

Event: After handover to a strong-signal cell ( -40dB ), drop-call occurs immediately. Suggestion: With reference to the poor RxQuality when hand-in, It may possibly interfered by another co-Bcch signal. Check nearby-cells with any same Bcch value, or need to check the target-cell hardware.

Example6 ( Missing Neighbor )

Cell-A: it is missing Cell-C as neighbor, so it handover to Cell-B

Cell-B: Handover Failure, as this is Not the best Serving cell, so that it continuos to hand to Cell C.

Cell-C: it is the neighbor of CellB, but not that of Cell-A. RxQuality shows a best value after clamping on it.

Suggestion: Re-check the neighbor-list of Cell-A, see whether Cell-C is missing.