GSM Drive Test & Network Optimization

STTTelkom, 17-18 November 2006

TEMS INVESTIGATION GSM

How do we use it

Page - 2

TEMS Measurement & Analyzing Process

Preparations

Collect Data

Analyze

Report

Clear objective Why should this measurement be done

Check equipment Get input files Prepare route External Antenna?

Save logfile Take notes Monitor

Find problem areas Find solutions

Give answer to objective

Changes in Network

What should be changed?

Page - 3

Measurement Will Depend on Objective

?
Clear objective Why should this measurement be done

Preparations
Check equipment Get input files Prepare route External antenna?

Possible Objectives
Coverage analysis Trouble shooting Scanning Verify network changes

Page - 4

Performing Measurements with TEMS

Drive Test Large areas Specific areas Walk Test Scanning

Page - 5

Drive Test

- Large area
INPUT INPUT
Acceptance New sites on air Frequency Re-plan BSC Re-homing

MEASUREMENT
Drive defined route/area Record Logfile Long / Short calls Assure no data loss

OUTPUT
Plots & Report - Signal Strength - Quality Trouble Report / Area for further investigation

Page - 6

Drive Test

- Specific area
INPUT
Statistics Customer complain Large area drive test Trouble Report

Measurement
Manipulate

OUTPUT
Trouble Report - Identified problem - Solution

- Forced handover
- Lock on to Frequency - Layer 3 messages Analysis on-spot Rectify & Verify on-spot

Page - 7

Walk Test

INPUT
Statistics Customer complain Micro cell planning Indoor cell planning

Measurement
Add file marks (GPS) Scanning

OUTPUT
Trouble Report Planning Report - Antenna location - Frequency

* TEMS Light is the preferred tool for indoor cell planning

Page - 8

Scanning

INPUT
Finding a new frequency Area Network Scanning

Measurement
TEMS INV in scanning mode Set ARFCN to scan

OUTPUT
Received SS on different ARFCN plot New frequency

Page - 9

ANALYZING TEMS MEASUREMENTS

Post-Processing TEMS Logfiles

TEMS Logfiles

Geographical Presentation

Statistics Report

Analysis

Page - 11

Problem Cases
Low Signal Strength Interference Handover Call Setup Failure Dropped Call Misc.

Page - 12

Signal Strength Case

TEMS Logfiles

INPUT
Large area DT

Post-Processing Analysis

Specific area DT

Identify areas with low signal strength e.g. SS < -100dBm (outdoor)

Look at RxLev distribution (for acceptance)

Compare with design level or new requirements

Page - 13

Signal Strength Case Possible Reasons

Shadowed Antenna
Antenna Direction Antenna Height / down tilt

Output Power
Missing Neighbor Relation Site Location

Faulty Hardware e.g. antenna

Cell is down
Page - 14

Signal Strength Case

Analysis
Shadowed Antenna
Visit site Check antenna installation Is there a better antenna position at same site?

Output Power
Check output power Parameters
BSPWRT - NON BCCH FREQ BSPWRB - BCCH FREQ

Faulty Hardware
Check alarm & BTS Error log Visit site

Height/down Tilt
Add reduce down tilt? Can antenna be placed lower or higher to give better coverage?

Missing Neighbor
Is the call dragged?
Is low SS due to missing neighbor relations

Site Location
Possible to move site? New antenna location at same site? Is it necessary to expand and build a new site?
Page - 15

Signal Strength Case Possible Solutions

Change parameter BSPWR , BSPWRT.
Add neighbor relation. Physical changes:

Antenna direction
Antenna height, tilt or position New site as last option.

Page - 16

Interference Case
TEMS Logfiles

INPUT
Large area DT

Post-Processing Analysis

Specific area DT

Identify areas with Rxqual > 5 Identify source using Map and STS New drive test around problem area?

Page - 17

Interference Case

Logfile analysis
From logfile & map: What channel group suffer from interference? HOP or Non HOP? Check Current channel information in TEMS INV, hopping channel and hopping frequency.

Where does the interference come from? Cell name?

Study map and logfile, look for co-channel or adjacent channel interference. Does the interference lead to lower SQI? Look at SQI measurement during high RxQual.

Page - 18

Types of Interference

Co - Channel interference Adjacent Interference

BCCH 600 BCCH 595

CASE 1 CASE 2

High site

BCCH 590 BCCH 590

BCCH 590 BCCH 590

Page - 19

Interference Case

Possible Reasons
Poor frequency plan No dominant cell --> low C/I ---> increased Rxqual Frequency Hopping is off External interference e.g. jammer

Example of high Rxqual due to low Signal Strength

Page - 20

Interference Case

Possible solutions

Enable Frequency Hopping or add frequencies to Hopping group.

Enable BTS Power Control, MS power control and make it less aggressive.
Change frequency of interferer or interfered cell:

Possible to find new frequency by using TEMS Scanning.

Down tilt or change antenna of interferer. Redo frequency plan.

Add new site.

Page - 21

Handover Case
INPUT Large area DT Specific area DT
Look for:

Post-Processing Analysis

Repeated handover (Ping Pong)

Repeated Intra-cell handover

Handover failure, Unrealistic handover
Page - 22

Repeated Handover (Ping Pong)

- Examples

Page - 23

Repeated Handover (Ping Pong)

- Possible Reason 1
Merry-go-round Handover, Offset > Hysterisis

Page - 24

Repeated Handover (Ping Pong)

- Possible Reason 2

Offset only in one direction e.g A-B for Inter BSC relation
BSC 1 BSC 2

CELL A

CELL B

A -> B OFFSET = -5dB

No B -> A OFFSET

Page - 25

Repeated Handover (Ping Pong)

Other Possible Reasons

No dominant server Locating penalty settings e.g. PSSBQ, PTIMBQ No dominant Server Too small hysterisis setting

Page - 26

Repeated Handover (Ping Pong)

Possible Solutions
Antenna direction Antenna Tilts Plan for new site Change Locating Parameter e.g. KHYST or LHYST

Page - 27

Repeated Handover (Ping Pong)

Possible Solution
Change Parameter, KHYST or LHYST

Hysterisis

CELL A

CELL B

Handover From A to B

Page - 28

Handover Case

Handover Reversion

Check layer 3 message

Handover command BSC correct? Check reason for handover SS, RXQUAL Target cell?

Page - 29

Handover Reversion

Common Reason
Duplicates of BSIC BCCH combinations in neighboring list

Handover command?
610_12 606_33 610_31 610_31

Serving cell Neighbor cell 1

608_32 608_32

Neighbor cell 2

Road

Page - 30

Handover Reversion

Other Reasons
Uplink interference in target cell Downlink interference at MS Solutions Interference Investigation Statistics Scanning

Page - 31

Handover Case

Repeated Intra-cell Handover

Possible Reasons
Wrong intra-cell handover settings External Uplink Interference Possible Solutions Consider to change parameters: SSOFFSETUL, SSOFFSETDL QOFFSETUL, QOFFSETDL A wrong setting of parameters will cause unnecessary IHO Turn off Intra-cell Handover?
Page - 32

Handover Case

Unrealistic Handover

Page - 33

Unrealistic Handover

Reason & Solution

Possible Reasons
Wrong locating settings, in Serving or Target cell Note: Could be on purpose e.g. Dual Band network with HCS

Solution Fix locating settings e.g. MSRXSUFF, BSRXSUFF

Page - 34

Call Setup Failure

Page - 35

Call Setup Failure Input Activities, Initial Tuning

Activities
Initial Tuning (Acceptance Test) Measurement Type Large Area Drive Test Short Call Sequences

Troubleshooting (Customer complaint etc.)

Post-Processing Output Statistics Report Geographical Report showing failure positions

Page - 36

Call Setup Failure Input Activities, Troubleshooting

Input Activities
Measurement Type
Initial Tuning (Acceptance Test)
Small Area Drive Test Lock on problem cells BCCH Force handover to the cell

Troubleshooting (Customer complaint etc.)

Post-Processing Output
Geographical Report (if necessary)

Page - 37

Call Setup Failure Analysis

- Initial Tuning Scenario

Check the TEMS statistics report (Blocked Call) if there is Call Setup Failure. If yes, identify the problem cells and which logfile from geographical report. Replay the logfile and jump to the Blocked Call event. Check if there is any successful call setup to the problem cell.

Page - 38

Call Setup Failure Analysis

- Initial Tuning Scenario cont.

Review the layer 3 messages to check at which sequence the failure occur (random access, SDCCH, TCH assignment etc.). Is there any traffic (SDCCH & TCH) in the cell, SDCCH & TCH seizures, congestion etc. Check fault report

Page - 39

Call Setup Failure Analysis

- Troubleshooting Scenario

Before performing drive test, check STS report & fault report. If can not identify the problem, perform drive test. During measurement, lock the BCCH of the problem cell. Review the layer 3 messages to check at which sequence the failure occur (random access, SDCCH, TCH assignment etc.).
Page - 40

Call Setup Failure Analysis

- Possible reasons with ranking

Low Signal Strength Interference High Congestion on SDCCH High Congestion on TCH Transmission Fault Faulty TRU/Hardware Central Processor Overload Software File Congestion Cell is not defined in MSC.
Page - 41

Call Setup Failure Analysis

- Possible solutions

Low signal strength Signal strength analysis. Interference Interference analysis. High Congestion on SDCCH:
Define more SDCCHs. Activate adaptive configuration of logical channel feature and immediate assignment to TCH.

High Congestion on TCH:

Add capacity/Tune coverage array. Activate assignment to worse cell.

Page - 42

Failed Call Setup (Blocked Call) Example

Multiple Channel Requests. Successful Random Access after the third try. Congestion in SDCCH.

Page - 43

Dropped Call Case

- Input

Statistics Report Note from drive test.

Page - 44

Dropped Call Case

- Analysis

From plot, identify which & where in logfile the dropped call occurs. In the log file, Jump the drop call event. Check if there is a disrupt in the recording. If yes could be a false drop due to TEMS mobile disconnection during recording!!!

Page - 45

Dropped Call Case

- Analysis (cont)

Check the Radio environment just before drop:

If High Rxqual for a longer period of time and RLINKT expire Interference problem. If Low SS DL, SSDL < MSSENS ( -104dBm) low signal strength problem. If TA > 63 too far from the cell.

If DL radio is good, check the TX power. If there is MS power down regulation when the MS is close to the cell. If full power suspect uplink interference or antenna, TMA problem. Verify or isolate the problem using STS (Drop call and reasons).
Page - 46

The End
GSM Drive Test & Network Optimization

Page - 47