Tems Investigation GSM: Howdoweuseit
Tems Investigation GSM: Howdoweuseit
Tems Investigation GSM: Howdoweuseit
GSM
How do we use it
2002-03-11 1
Performing TEMS Measurements
2002-03-11 2
TEMS Measurement & Analyzing Process
Clear objective Check equipment Save logfile Find problem Give answer
areas to objective
Why should this Get input files Take notes
measurement be Find solutions
Prepare route Monitor
done
External Antenna?
2002-03-11 3
Measurement Will Depend on Objective
? Preparations
Possible Objectives
2002-03-11 4
Performing Measurements with TEMS
Drive Test
Large areas
Specific areas
Walk Test
Scanning
2002-03-11 5
Drive Test
- Large area
INPUT
INPUT MEASUREMENT OUTPUT
2002-03-11 6
Drive Test
- Specific area
2002-03-11 7
Walk Test
2002-03-11 8
Scanning
2002-03-11 9
ANALYZING TEMS MEASUREMENTS
2002-03-11 10
Post-Processing TEMS Logfiles
Geographical
TEMS Presentation
Logfiles
Statistics
Report
Analysis
2002-03-11 11
Problem Cases
Low Signal Strength
Interference
Handover
Call Setup Failure
Dropped Call
Misc.
2002-03-11 12
Signal Strength Case
TEMS
INPUT Logfiles
Identify areas with low signal strength e.g. SS < -100dBm (outdoor)
Look at RxLev distribution (for acceptance)
Compare with design level or new requirements
2002-03-11 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
2002-03-11 14
Signal Strength Case
Analysis
Visit site Check output power Check alarm & BTS Error
Check antenna installation Parameters log
Add reduce down tilt? Is the call dragged? Possible to move site?
Can antenna be placed Is low SS due to missing New antenna location at
lower or higher to give neighbor relations same site? Is it necessary to
better coverage? expand and build a new
site?
2002-03-11 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.
2002-03-11 16
Interference Case
TEMS
INPUT Logfiles
2002-03-11 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.
2002-03-11 18
Types of Interference
Co - Channel interference
Adjacent Interference
BCCH 590
BCCH 590
BCCH 590
BCCH 590
2002-03-11 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
2002-03-11 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.
2002-03-11 21
Handover Case
INPUT
Look for:
2002-03-11 23
Repeated Handover (Ping Pong)
- Possible Reason 1
Offset only in one direction e.g A-B for Inter BSC relation
BSC 1 BSC 2
BSC BSC
CELL A CELL B
2002-03-11 25
Repeated Handover (Ping Pong)
Other Possible Reasons
No dominant Server
No dominant server
Locating penalty settings e.g.
PSSBQ, PTIMBQ
Too small hysterisis setting
2002-03-11 26
Repeated Handover (Ping Pong)
Possible Solutions
Antenna direction
Antenna Tilts
2002-03-11 27
Repeated Handover (Ping Pong)
Possible Solution
Hysterisis
CELL A CELL B
Handover
From A to B
2002-03-11 28
Handover Case
Handover Reversion
2002-03-11 29
Handover Reversion
Common Reason
Handover command?
BSC
610_12
606_33
610_31 610_31
Serving cell
Neighbor cell 2
Neighbor cell 1
608_32
608_32
Road
2002-03-11 30
Handover Reversion
Other Reasons
Uplink interference in target cell
Downlink interference at MS
Solutions
Interference Investigation
Statistics
Scanning
2002-03-11 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?
2002-03-11 32
Handover Case
Unrealistic Handover
2002-03-11 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
2002-03-11 34
Call Setup Failure
2002-03-11 35
Call Setup Failure
Input Activities, Initial Tuning
Activities
Measurement Type
Large Area Drive Test
Initial Tuning
Short Call Sequences
(Acceptance Test)
2002-03-11 36
Call Setup Failure
Input Activities, Troubleshooting
Input Activities
Measurement Type
Small Area Drive Test
Initial Tuning Lock on problem cells BCCH
(Acceptance Test) Force handover to the cell
2002-03-11 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.
2002-03-11 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
2002-03-11 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.).
2002-03-11 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.
2002-03-11 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.
2002-03-11 42
Failed Call Setup (Blocked Call) Example
2002-03-11 43
Dropped Call Case
- Input
Statistics Report
Note from drive test.
2002-03-11 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!!!
2002-03-11 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).
2002-03-11 46