OWO300080 WCDMA Handover Problems Analysis ISSUE1.00

WCDMA Handover
Problem Analysis
www.huawei.com
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

Contents
1. Basic Concepts of Handover Problem Optimization
2. Soft Handover Problem Analysis
3. Hard Handover Problem Analysis
4. Inter-RAT Handover Problem Analysis
Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page2

Handover Problem Optimization Flow
Network Information Collection and
Optimization Target Definition
Performance Statistic Collection
DT and Signaling Analysis
Parameters Adjustment
Adjustment validation
N
Achieve Target ？
End

Handover performance benchmark
Index Service Statistics method Reference value
SHO success rate CS&PS DT&Stat. 99%
Voice DT&Stat. 90%
VP DT&Stat. 85%
Intra-f HHO success rate PS UL64K/DL 64K DT&Stat. 85%
PS UL64K/DL 144K DT&Stat. 80%
Voice DT&Stat. 92%
VP DT&Stat. 90%
Inter-f HHO success rate PS UL64K/DL 64K DT&Stat. 90%
Voice handover out DT&Stat. 95%
Inter-RAN HHO success rate
PS handover out DT&Stat. 92%
SHO ratio N/A DT 35%
SHO cost N/A Stat. 40%

Contents
4. Inter-RAN Handover Problem Analysis

Contents
2.1 SHO DT Optimization Flow
2.2 SHO Performance Statistics Optimization Flow
2.3 SHO Problem Analysis
2.4 SHO Problem Cases

SHO DT Optimization Flow

SHO DT Optimization Flow (Cont.)
1. Inputting Analysis Data
 Perform DT. Collect DT data, related signaling tracing, RNC
CHR, and RNC MML scripts
2. Obtaining When and Where the Problem Occurs

 During the test, SHO-caused call drop might occur or SHO might
fail, so record the location and time for the problem occurrence.
This prepares for further location and analysis

3. Missing Neighbor Cell
 During the early optimization, call drop is usually due to missing
neighbor cell. For intra-frequency neighbor cells, use the following
methods to confirm intra-frequency missing neighbor cell

4. Pilot Pollution
 Pilot pollution is defined as below:
 Excessive strong pilots exist at a point, but no one is strong enough to be a
dominant one
 “Strong pilot” is defined by RSCP. If CPICH _ RSCP  ThRSCP,_ this
Absolute pilot is a
strong pilot, ThRSCP = -95dBm

 “Excessive” is defined by the pilot number. If CPICH _ Number  Thpilots
, the N at
a point are excessive, ThsN = 3
 “no one is strong enough to be a dominant one” means
(CPICH _ RSCP1st  CPICH _ RSCP(ThN 1)th )  ThRSCP _ Re lative , whichis
lessthan5db

5. Improper Configuration of SHO Algorithm Parameters
 Delayed handover
 According to the signaling flow, the UE reports the 1a or 1c
measurement report of neighbor cells before call drop. After this the
RNC receives the event and sends the active set update message,
which the UE fails to receive
 Ping-pong handover
 The best server changes frequently or no primary pilot cell exists

6. Abnormal Equipment
 Check the alarm console for abnormal alarms. Meanwhile analyze
traced message, locate the SHO problem by checking the failure
message. For help, contact local customer service engineers for
confirm abnormal equipment
7. Re-performing Drive Test and Locating Problems

 If the problem is not due to previous causes, perform DT again and
collect DT data. Supplement data from problem analysis

8. Adjustment and Implementation

For handover problems caused by pilot pollution: the main solution is to adjust
antenna and feeder system

For call drop caused by delayed handover: adjust antennas and feeder system, or
modify handover algorithms parameters

For needle effect or turning corner effect: The main solution is to modify
handover algorithms parameters

For call drop caused by Ping-pong handover: adjust the antenna and feeder
system, or modify handover algorithms parameters

For abnormal equipment: cooperate with customer service engineers

Contents

SHO Performance Statistics Optimization
Flow

Main SHO failure indexes
Failure causes Analysis
Configuration The UE thinks the content of active set update for RNC to add/delete links does
nonsupport not support SHO. This scenario seldom exists in commercial networks.
Synchronization The UE feeds back that the SHO (or softer handover) for RNC to add/delete links
reconfiguration is incompatible with other subsequent processes. The RNC guarantees serial
nonsupport processing upon flow processing. This cause is due to the problematic UE.
The UE thinks the content of active set update for RNC to add/delete links is
Invalid configuration
invalid. This scenario seldom exists in commercial networks.
The RNC fails to receive response to active set update command for
adding/deleting links. This is a major cause to SHO (or softer handover) failure. It
No response from UE
occurs in areas with weak coverage and small handover area. RF optimization
must be performed in the areas.

Contents

SHO Problem Analysis
 High soft handover percentage
 SHO percentage should be kept among 30% ~ 40%
 The reasons for high soft handover percentage could be:
 Coverage problems ~ overshoot
 Improper parameters
– Threshold for 1A, 1B
– CIO
 Improper planning method
– High traffic in soft handover area

SHO Problem Analysis (Cont.)
 Soft handover success rate is low
 If the soft handover success rate is lower than 98%, it can be defined
soft handover success rate is low
 The reasons could be:
 Coverage problem
 Pilot pollution
 Improper parameter
– 1A, 1B, 1C, 1D
– Time to trigger
– CIO

 Call drop in soft handover
 RF problem
 Coverage problem
 Pilot pollution
 Missing neighbor cell
 Improper parameters
 Threshold for 1A and 1B
 Time to trigger
 CIO

 Imbalance in uplink and downlink coverage
 External interference and pilot pollution may influence the planned uplink
and downlink coverage
Uplink
coverage
A B
Downlink
coverage
 Soft handover decision is based on the downlink CPICH channel quality. In

this case, call drop may happen because uplink out of synchronization

Contents

SHO Case 1
 Description
 DT data – signaling trace
After call drop, begin

Call Drop to read system
information

SHO Case 1 (Cont.)
 Data analysis
 Check cell information from UE active set and cell information from scanner at call drop points.
From UE From Scanner
No SC 170
cell!!
Why?

SHO Case 1 (Cont.)
 Data analysis
 Checking monitor set
Check monitor set for the

scramble measured by
scanner
SC 170 is not in monitor set, so

the cause is probably missing
neighbor cell
 Missing neighbor cell
 Delayed handover

SHO Case 1 (Cont.)
 Data analysis
 Check the latest measurement control
Search for the latest intra-frequency

measurement control
Call drop
point

SHO Case 1 (Cont.)
Measurement ID is 1. It is Intra-
frequency measurement control
The primary scramble of

the cell is 6
Check the list of intra-frequency

neighbor cell in measurement control
and no SC 170

SHO Case 1 (Cont.)
 Solution
 Add neighbor cells in neighbor cell list

SHO Case 1 (Cont.)
 If only UE recorded information during test, without scanner information, confirm
that call drop is due to missing neighbor cell by using the following method:
After call drop, UE read

system information
Check the cell where UE

camps on after cell
selection and reselection
The UE camps on the cell of SC 170, which is inconsistent

with the primary pilot before call drop, so the call drop is
probably due to missing neighbor cell

SHO Case 2
 Description
 Following figure shows the pilot pollution point near Yuxing Rd.
 SC270 cell is suppose to cover the pilot pollution area
Here is pilot pollution area.

This area should be covered
by scrambling code 270.
Scrambling code 270

SHO Case 2 (Cont.)
 Data analysis

Following figure shows Best Service Cell near Yuxing Rd
The best cell changes

frequently in this
area.

SHO Case 2 (Cont.)
 Data analysis

Following figure shows the second best service cell near Yuxing Rd
The second best cell

changes frequently in
this area.

SHO Case 2 (Cont.)
 Data analysis
 Analyzing signal distribution of cells near pilot pollution point

Following figure shows the third best service cell near Yuxing Rd

SHO Case 2 (Cont.)
 Data analysis

Following figure shows the fourth best service cell near Yuxing Rd

SHO Case 2 (Cont.)
 Data analysis
 Composition of pilot pollution near Yuxing Rd
 Though SC270 cell is planned to cover the area, but the best Service Cell is as
listed in table
Best Service Cell SC
1st best Service Cell SC220
2nd best Service Cell SC270
3rd best Service Cell SC260
4th best Service Cell SC200

SHO Case 2 (Cont.)
 Analyzing RSSI and RSCP distribution near pilot pollution point
 As shown in left figure, the RSSI of the pilot pollution area is not large, about
-100dBm to -90dBm
 As shown in right figure, the RSCP of Best Service Cell is between -105dBm to
-100dBm
 The pilot pollution of the area is caused by no strong pilot

SHO Case 2 (Cont.)
 Following figure shows the RSCP of SC270 cell near Yuxing Rd
 The figure shows RSCP of RSCP distribution of SC270 cell. The signals from
SC270 cell is weak in the pilot pollution area

SHO Case 2 (Cont.)
 Solution
 Adjust the azimuth of SC270 cell from 150° to 130° and the down tilt from 5° to 3°. This
enhances the coverage of SC270 cell
 Confirm
 After analysis of DT data, the area is dominated by SC 270. And the pilot pollution disappear

Call drop area
SHO Case 3
 Description
 Several call drops
happened during
RF optimization
 From figure, the
call drop place is
at corner

SHO Case 3 (Cont.)
 Data analysis
 According to following figure, the signals of active set scramble 104 and 168 decreased to -17 dB
before the corner. But SC208 cell is very good, about -8 dB

SHO Case 3 (Cont.)
 Data analysis
 the signaling trace from RNC shows that UE report the 1A event for SC 208.
208 Then, RNC send
active set update.
update But UE can not receive it

SHO Case 3 (Cont.)
 This is a typical case of corner effect, and the solution could be
 Adjust 1A event parameter
 Decrease time to trigger
 Decrease the threshold
 Side effect
 Adjust CIO
 Increase CIO of best cell
 Side effect
 RF optimization
 Adjust antenna to avoid the signal fluctuation

SHO Case 3 (Cont.)
 Conclusion
 From DT, the typical phenomenon for corner effect can be shown as
this figure
 Source cell signal decrease sharply while target cell increase sharply.
Therefore, call drop happens because UE can not receive active set update

SHO Case 4
 Needlepoint Effect
 The needlepoint effect phenomenon
 Best cell signal decrease sharply, then go back very soon
 From signaling procedure, 1B event happen, then 1A event happen
 This figure shows the signal fluctuation character of needlepoint effect
Needle point-signal variance

SHO Case 4 (Cont.)
 Needlepoint effect and corner effect
 Needlepoint effect may not cause call drop
 Needlepoint effect only lasts a very short time, and this duration may not long enough to trigger
handover.
 Cause QoS deteriorate
 Corner effect cause call drop

 Source cell signal can not recover

SHO Case 4 (Cont.)
 The needlepoint effect cause call drop in the following situations:
 If needlepoint can not satisfy handover
 call drop may not happen, but QoS deteriorate, like high BLER
 High BLER cause TRB reset, then call drop
 If needlepoint can satisfy handover

 Source cell signal deteriorate, and UE can not receive active set update,
update then call
drop
 Second handover in needlepoint may cause call drop

SHO Case 4 (Cont.)
 Solution
 RF optimization
 Avoid source cell signal deteriorate sharply

Contents
4. Inter-RAN Handover Problem Analysis

Contents
3.1 HHO DT Optimization Flow
3.2 HHO Performance Statistics Optimization Flow
3.3 HHO Problem Analysis
3.4 HHO Problem Cases

HHO DT Optimization Flow

HHO DT Optimization Flow (Cont.)
 HHO problems usually refer to delayed handover and Ping-pong
handover:
 For Delayed HHO, the following solutions can be adopted
 Increase the threshold for starting compression mode
 Increase the CIO of two inter-frequency cells
 Decrease the target frequency handover trigger threshold of inter-
frequency coverage
 For solving Ping-pong HHO, the method could be
 Increasing HHO hysteresis and delay trigger time

HHO DT Optimization Flow (Cont.)
 The intra-frequency HHO optimization is similar to that of inter-
frequency:
 Decrease the hysteresis and delay trigger time of 1D event according
to local radio environment to guarantee timely handover

Contents

Main HHO failure indexes
HHO preparation failure
Radio link setup failure Analyze RL setup failure.
Other causes Analyze the problem further based on CHR logs.
Internal NodeB/Between NodeBs/Between RNCs HHO failure
The UE thinks it cannot support the command for outgoing HHO, because it is
Configuration nonsupport
incompatible with HHO.
PCH failure The cause is probably weak coverage and strong interference.
Synchronization reconfiguration The UE feeds back HHO is incompatible with other consequent processes due to
nonsupport compatibility problems of UE.
Cell update Cell update occurs upon outgoing HHO.
The UE thinks the command for outgoing HHO as invalid. This is a

Invalid configuration
compatibility problem of UE.
Other causes Analyze the problem further based on CHR logs.

Contents

HHO Problem Analysis
 Compress mode failure
 Inter-frequency handover and inter-RAT handover
 Without measurement report (2D) from UE
– Improper threshold for compress mode
 Without Physical channel reconfiguration complete (Compress mode)

– Improper compress mode method: SF/2 and Higher layer scheduling
 Ping-pong compress mode

– Improper parameters
– The difference between 2D and 2F is too small

HHO Problem Analysis (Cont.)
 No Physical Channel Reconfiguration (HHO Indication)
 Inter-frequency hard handover and inter-RAT hard handover
 Without Physical channel reconfiguration (handover) or Handover from
UTRAN to GSM
– Improper parameter
~ 2B, 2C
~ 3A, 3C

 No Physical Channel Reconfiguration (HHO Indication)
 Intra-frequency hard handover is triggered by 1D event
 If UE report 1D event
– Check “intra-frequency hard handover algorithm switch”
– Iur or Iub interface setup link failure
 If no 1D event report from UE

– Check neighbor cell list
– Improper 1D event parameter
– Check the SC in source RNC and target RNC

 Failure of receiving Physical Channel Reconfiguration
 Improper parameters
 Threshold, hysteresis or time-to-trigger
 Increase “maximum downlink transmission power”
 Failure of receiving Physical Channel Reconfiguration Complete
 Improve uplink coverage
 Decrease uplink interference
 Increase “maximum uplink transmission power” if possible

 Ping Pong Handover
 Improper handover parameters
 Increase handover decision threshold, but need to consider side-effect
 Adjust transmission environment to decrease the signal fluctuation

 Other Problems
 UE capability
 For example, some UE can not support intra-frequency hard handover
 Equipment compatibility
 Especially when the hard handover need the corporation among different
network element from different manufacture
 Transmission problem

Contents

HHO Case 1
 Description
 When the UE moves to an inter-frequency cell, it fails to handover
 It camps on the inter-frequency cell after disconnection
 Analysis
 From signaling procedure, it happened in compress mode
 UE did not trigger compress mode
 Check Measurement report
 2D event and 2F event reporting indicator is Ec/Io

HHO Case 1 (Cont.)
 Pilot Ec/Io depends on:
 CPICH RSCP strength
 Downlink interference
 The relation between Ec/Io can be represented as following figure:
RSCP
Ec/N0

HHO Case 1 (Cont.)
 Solution
 Change 2D and 2F event reporting indicators to RSCP
 Confirm
 After adjustment, UE initiate compress mode successfully
 Conclusion
 At center of carrier coverage, 2D and 2F event reporting indicators is Ec/Io
 At edge of carrier coverage, 2D and 2F event reporting indicators is RSCP

Contents

Contents
4.1 Inter-RAT Handover DT Optimization Flow
4.2 Inter-RAT Handover Performance Statistics Optimization Flow
4.3 Inter-RAT Handover Problem Analysis

Inter-RAT Handover DT Optimization
Flow

Flow (Cont.)
 Inter-RAT handover fails due to incomplete configuration data, so
pay attention to the following data configuration:
 GSM neighbor configuration is complete on RNC
 Add location area cell information near 2G MSC to location area cell
list of 3G MSC
 Add data of WCDMA neighbor cells on GSM BSS

Flow (Cont.)
 According to the strategies of unilateral handover of inter-RAT
handover, if the data configuration is complete, the inter-RAT
handover problems are due to delayed handover:
 A frequently-used solution is increasing CIO, increasing the
threshold for starting and stopping compression mode, increasing the
threshold to hand over to GSM.

Flow (Cont.)
 The causes to call drop due to 3G-2G inter-RAT handover are as below:
 After the 2G network modifies its configuration data, it does not inform the 3G
network of modification, so the data configured in two networks are inconsistent
 Missing neighbor cell causes call drop
 The signals fluctuate frequently so call drop occurs
 Handset problems causes call drop. For example, the UE fails to hand over back or to
report inter-RAT measurement report
 Excessive inter-RAT cell are configured (solve it by optimizing number of neighbor
cells)

Contents

Main Inter-RAT HHO failure indexes
RNC-level inter-RAT outgoing handover preparation failure
The CN does not respond the corresponding command for handover preparation request, because the CN
Expiration of waiting for SRNS
parameter configuration or the corresponding link connection is problematic. To solve this problem, analyze
relocation command
the causes according to CN and BSS signaling tracing.
SRNS relocation cancellation After the RNC requests handover preparation, it receives the release command from CN.
It corresponds to incorrect configuration of CN, so you must analyze the causes according to CN and BSS
SRNS relocation expiration
signaling tracing.
SRNS relocation failure in target It corresponds to incorrect configuration of CN or BSS nonsupport, so you must analyze the causes according
CN/RNC/system to CN and BSS signaling tracing.
It corresponds to incorrect configuration of MSC parameters without information like LAC of target cell, so
Unknown target RNC
you must check the parameter configuration. It occurs easily after adjustment of 2G networks.
It corresponds to incorrect configuration of MSC parameters or unavailable BSC resources, so you must
Unavailable resource
analyze the causes according to CN and BSS signaling tracing.
Other causes Analyze the causes according to CN and BSS signaling tracing.

Main Inter-RAT HHO failure indexes
(Cont.)
Cell-level inter-RAT outgoing handover preparation failure
The CN parameter configuration or the corresponding link connection is problematic, so you

SRNS relocation expiration
must analyze the causes according to CN and BSS signaling tracing.
SRNS relocation failure in target It corresponds to incorrect configuration of CN or BSS nonsupport, so you must analyze the
CN/RNC/system causes according to CN and BSS signaling tracing.
SRNS relocation nonsupport in target The BSC fails to support some parameters of inter-RAT handover request, so you must
CN/RNC/system analyze the causes according to CN and BSS signaling tracing.
Other causes Analyze the causes according to CN and BSS signaling tracing.
RNC-level/CELL-level inter-RAT outgoing handover failure
The UE fails to support the handover command in the network, so the UE is incompatible with
Configuration nonsupport
the handover command.
PCH failure The 2G signals are weak or the interference is strong so the UE fails to connect to the network.
Other causes Analyze the problem further according to CHR logs and CN/BSS signaling tracing.

Contents

Inter-RAT Handover Problem
Analysis
 The content of Inter-RAT handover problem analysis is similar
with that of inter-f handover problem analysis
 Due to inter-RAT handover involves multi network equipments
cooperation, so on-site engineers also need analyze CN and GBSS
signaling messages to locate problem

Thank you
www.huawei.com

OWO300080 WCDMA Handover Problems Analysis ISSUE1.00

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OWO300080 WCDMA Handover Problems Analysis ISSUE1.00

Uploaded by

Copyright:

Available Formats

WCDMA Handover

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

2. Soft Handover Problem Analysis

3. Hard Handover Problem Analysis

4. Inter-RAT Handover Problem Analysis

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page2

Performance Statistic Collection

DT and Signaling Analysis

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page3

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page5

2. Soft Handover Problem Analysis

3. Hard Handover Problem Analysis

4. Inter-RAN Handover Problem Analysis

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page6

2.2 SHO Performance Statistics Optimization Flow

2.3 SHO Problem Analysis

2.4 SHO Problem Cases

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page7

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page8

2. Obtaining When and Where the Problem Occurs

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page9

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page10

strong pilot, ThRSCP = -95dBm

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page11

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page12

7. Re-performing Drive Test and Locating Problems

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page13

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page14

2.2 SHO Performance Statistics Optimization Flow

2.3 SHO Problem Analysis

2.4 SHO Problem Cases

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page15

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page16

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page17

2.2 SHO Performance Statistics Optimization Flow

2.3 SHO Problem Analysis

2.4 SHO Problem Cases

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page18

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page19

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page20

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page21

 Soft handover decision is based on the downlink CPICH channel quality. In

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page22

2.2 SHO Performance Statistics Optimization Flow

2.3 SHO Problem Analysis

2.4 SHO Problem Cases

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page23

After call drop, begin

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page24

From UE From Scanner

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page25

Check monitor set for the

SC 170 is not in monitor set, so

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page26

Search for the latest intra-frequency

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page27

The primary scramble of

Check the list of intra-frequency

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page28

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page29

After call drop, UE read

Check the cell where UE

The UE camps on the cell of SC 170, which is inconsistent

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.Page30