RF Optimization and Trouble Shooting

by driver test

RF optimization and trouble shooting

Network deployment phase, tuning
After commercial launch, optimization, KPI target and trouble shooting

What can do by driver test analysis

RF coverage
RF quality
Air interface signal analysis, Uu
Parameter setting, SC, neighbour list, power setting

Tools
Data collection tool
Log file analysis tool
Together with OSS trace, UETR, CTR, etc. for deep analysis

Driver Test Workshop

Dropped and Blocked Call Analysis

RF related issues and reasons

Poor Coverage
Poor CPICH RSCP and/or CPICH Ec/No, not suitable for a proper connection

Bad Radio Environment

Best Server is Missing, Interference, Pilot Pollution

Poor uplink coverage

insufficient UE Tx power

Congestion
No more available radio resources, RBS reaches the maximum Power in DL.

Poor dominance
best cell changes too frequently resulting in too many SHO events

Driver Test Workshop

Dropped and Blocked Call Analysis

RF related issues and reasons, continued

Missing Neighbours
Better cell that is not declared as a neighbour

Fast change of RF conditions

e.g. turning a corner

Not Radio
Radio conditions are good

Equipment Fault
TEMS Investigation/UE Blocking or Freezing and/or SW is crashing

Driver Test Workshop

Dropped Call Analysis Steps

RSCP & Ec/Io decreases before drop for both scanner and UE,
check for coverage problems
Before the drop, the Ec/Io (and RSCP) decreases for UE only,
scanner shows no decrease, the following considerations are
useful:
Soft handover errors, Best server of UE is not the same as that of
scanner

Missing neighbors, UE camps on a new cell after the drop, the

new cell is not in the neighbor list of previous cell.

Can check: does the UE measure this neighbor?

Driver Test Workshop

Dropped Call Analysis Steps, Cont.

Dominate cell, Are there too many and too fast changes of best server
making difficult for UE to perform measurements and SHO in time

Check UE Tx power, increase to max before the dropping call

while Ec/Io level remains good?
Dropped due to uplink coverage limitation, If the Tx power increase is
gradual and UE is far from site.
UE may not very far from site if the increase is sudden, check the
uplink load
- If the uplink load is high, it may be caused by traffic(checking statistics), or site
fault
- If uplink load is not high, problem could be due to possible power control failure.

Driver Test Workshop

Dropped Call Analysis Steps, Cont.

Signals before the dropped call shall be analyzed if the above

checking can not find the reasons

If the dropped call is not RF related and the RF conditions at

the location of the drop appear to be good, no further work is
needed as part of the RF Optimization.

Recording the location of the drop for future analysis

Driver Test Workshop

Dropped call, Poor Coverage

61888 (SC = 205)

RSCP=-127dBm
62096 (SC = 293)
Ec/No=-32dB

Driver Test Workshop

Dropped, Bad Radio Environment

Driver Test Workshop

Dropped call, Missing neighbour

61888 (SC = 205)

62096 (SC = 293)

Cell 248
Cell 464

Driver Test Workshop

Dropped, Congestion

Driver Test Workshop

10

Dropped, Not Radio

Driver Test Workshop

11

Blocked call, Bad Radio condition

49046 (SC = 387)

48007 (SC = 451)

Driver Test Workshop

12

Blocked call, missing neighbours

49046 (SC = 387)

48007 (SC = 451)

Driver Test Workshop

13

Blocked, Resources Unavailable

Driver Test Workshop

14

Blocked call, Equipment Fault (UE)

49046 (SC = 387)

48007 (SC = 451)

Driver Test Workshop

15

Blocked, Not allowed PLMN

Driver Test Workshop

16

Blocked, Unanswered RRC requests

Driver Test Workshop

17