Professional Documents
Culture Documents
W-Handover and Call Drop Problem Optimization Guide: (For Internal Use Only)
W-Handover and Call Drop Problem Optimization Guide: (For Internal Use Only)
Product name
Confidentiality level
WCDMA RNP
Product version
Total 202 pages
3.3
W-Handover
and
Optimization Guide
Call
Drop
Prepared by
Jiao Anqiang
Date
Reviewed by
Date
Reviewed by
Wang Chungui
Date
2006-03-16
Problem
Approved by
Date
Version
Description
2005-02-01
2.0
Completing
Problems.
2006-03-16
3.0
2006-04-30
3.1
V2.0
Author
W-Handover
and
Call
Drop
Cai Jianyong,
Zang Liang, and
Jiao Anqiang
Date
Version
Description
Author
2007-08-09
2008-12-15
3.11
3.2
Zhang Hao
3.3
WangDekai /
Hu Wensu
Contents
2.1 Handover Performance Indexes 15
2.2 Call Drop Performance Indexes 18
3.1 DT/CQT Index Optimization Flow 19
3.1.1 SHO DT Index Optimization Flow 19
3.1.2 HHO CQT Flow 23
3.1.3 Inter-RAT Handover CQT Flow 26
3.1.4 DT/CQT Flow for HSDPA Handover 28
3.1.5 DT/CQT Flow for HSUPA Handover 31
3.1.6 SHO Ratio Optimization 31
3.1.7 MBMS Mobility Optimization 31
3.2 Traffic Statistics Analysis Flow 33
3.2.1 Analysis Flow for SHO Traffic Statistics 34
3.2.2 Analysis Flow of HHO Traffic statistics 35
3.2.3 Traffic Statistics Analysis Flow for Inter-RAT Handover 36
3.2.4 Traffic Statistics Analysis for HSDPA Handover 39
3.2.5 Traffic Statistics Analysis for HSUPA Handover 40
3.3 SHO Cost Optimization 42
4.1 Definition of Call Drop and Traffic Statistics Indexes 43
4.1.1 Definition of DT Call Drop 43
4.1.2 Descriptions of Traffic Statistics Indexes 43
4.2 DT/CQT Optimization Flow 44
4.2.1 Call Drop Cause Analysis 45
4.2.2 Frequently-adjusted Non-handover Algorithm Parameters 47
4.2.3 Judgment Tree for Call Drop Causes 48
4.3 Traffic Statistics Analysis Flow 49
4.3.1 Analyzing RNC CDR 50
4.3.2 Analyzing Causes to Call Drop 50
4.3.3 Check Cells 51
4.3.4 Further DT for Relocating Problems 51
4.4 Optimization Flow for Tracing Data 51
4.4.1 Obtaining Single Subscriber Tracing Message 52
4.4.2 Obtaining Information about Call Drop Point 53
Figures
Tables
Handover performance indexes and reference values 15
HSDPA handover performance indexes and reference value 16
HSUPA handover performance indexes and reference value 16
CDR index and reference value 18
SHO failure indexes 35
HHO failure indexes 35
Traffic statistics indexes of CS inter-RAT handover preparation failure 37
Traffic statistics indexes of PS inter-RAT outgoing handover failure 38
Types of CDR indexes 44
Thresholds of EcIo and Ec 45
Traffic statistics indexes for analyzing causes to call drop 50
Relationship between the filter coefficient and the corresponding tracing time 58
2G handover times 63
Best servers and other cells 67
Timers and counters related to the synchronization and asynchronization 105
Timers and counters related to call drop at lub interface 108
Flow of serving cell update triggered by different events in SHO 133
Scenarios of handover between HSDPA and R99 (V17) 145
Handover between two HSUPA cells 159
Handover between a HSUPA cell and a non-HSUPA cell 164
Parameters of handover from 3G to 2G 191
Abstract:
This document, aiming at network optimization of handover success rate and call drop rate, details the
specific network operation flow. In addition, it analyzes common problems during network
optimization.
Full Spelling
AMR
Adaptive MultiRate
CHR
CDR
DCCC
RAN
RNP
SRB
TRB
SHO
Soft Handover
HHO
Hard Handover
PCH
Physical Channel
CN
Core Network
O&M
MNC
MCC
LAC
CIO
HSUPA
E-DCH
E-AGCH
E-RGCH
1 Introduction
This document aims to meet the requirements by on-site engineers on solving handover and
call drop problems and making them qualified during network optimization. It describes the
methods for evaluating network handover and call drop performance, testing methods,
troubleshooting methods, and frequently asked questions (FAQs).
The appendix provides fundamental knowledge, principles, related parameters, and data
processing tools about handover and call drop. This document serves to network KPI
optimization and operation and maintenance (O&M) and helps engineers to locate and solve
handover and call drop problems.
The RRM algorithms and problem implementation in this document are based on V16 RNC.
If some RRM algorithms are based on V17 RNC, they will be highlighted. HSUPA is
introduced in V18 RNC, so the algorithms related to HSUPA are based on RNC V18. The
following sections are updated:
1Introduction
2Handover and Call Drop Performance Indexes
3Handover Index Optimization
4CDR Index Optimization
5FAQs Analysis
6Summary
7Appendix
The traffic statistics analysis is based on RNC V1.5 counter. It will be updated upon the
update of RNC counters.
1. Handover
performance
indexes
and
reference
values
Ind
ex
SHO
rate
success
Intra-frequency
HHO success
rate
Statisti
cs
method
Servi
ce
Referen
ce value
CS&PS
DT&Stat.
99%
Voice
DT&Stat.
90%
VP
DT&Stat.
85%
PS UL64K/DL
64K
DT&Stat.
85%
PS UL64K/DL
144K
DT&Stat.
80%
PS UL64K/DL
384K
DT&Stat.
75%
Voice
DT&Stat.
92%
VP
DT&Stat.
90%
PS UL64K/DL
64K
DT&Stat.
90%
PS UL64K/DL
144K
DT&Stat.
87%
PS UL64K/DL
384K
DT&Stat.
85%
Voice
out
DT&Stat.
95%
PS handover out
DT&Stat.
92%
SHO ratio
N/A
DT
35%
SHO cost
N/A
Stat.
40%
Inter-frequency
HHO success
rate
Inter-RAT
handover
success rate
handover
2.1 lists the HSDPA handover performance indexes and reference value.
2. HSDPA
handover
performance
indexes
and
reference value
Index
HSDPA-HSDPA intra-frequency
serving cell update
Reference
value
Service
PS (HSDPA)
99%
Index
Reference
value
Service
HSDPA-HSDPA inter-frequency
serving cell update
PS (HSDPA)
92%
HSDPA-R99
handover
intra-frequency
PS (HSDPA)
99%
HSDPA-R99
handover
inter-frequency
PS (HSDPA)
90%
85%
HSDPA-to-GPRS
handover
92%
inter-RAT
PS (HSDPA)
Note: The HSDPA handover KPIs are to be updated after formal issue by WCDMA&GSM Performance
Research Department.
3. HSUPA
handover
performance
indexes
and
reference value
Index
Reference
value
Service
PS (HSUPA)
PS (HSUPA)
Index
PS (HSUPA)
PS(HSUPA)
PS (HSUPA)
PS (HSUPA)
PS (HSUPA)
PS (HSUPA)
PS (HSUPA)
PS (HSUPA)
Note:
Reference
value
Service
92%
The HSUPA handover KPIs are unavailable and to be updated after formal issue by WCDMA&GSM
Performance Department.
Decide the specific value according to project requirements or contract requirements of commercial
network
Referen
ce
value
Voice
DT&Stat.&CQT
2%
VP
DT&Stat.&CQT
2.5%
DT&CQT
3%
DT
3%
PS
Stat.
10%
PS (UL HSUPA/DL
HSDPA)
DT
3%
PS planned
coverage rate
CDR
Statisti
cs
metho
d
Servi
ce
full
The values listed in 2.2 are only for reference. Decide the specific value according to project
requirements or contract requirements of commercial network.
The call drop rate of HSDPA is not defined yet, so engineers use call drop
rate of PS temporarily.
2. SHO
DT
analysis flow
data
Obtaining When
Problem Occurs
and
Where
the
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.
Check the active set Ec/Io recorded by UE before call drop and Best
Server Ec/Io recorded by Scanner. Check whether the Best Server
scramble recorded by Scanner is in the neighbor cell list of intrafrequency measurement control before call drop. The cause might be
intra-frequency missing neighbor cell if all the following conditions
are met:
Pilot Pollution
Pilot pollution is defined as below:
Definition
of
strong
pilot
Whether a pilot is strong depends on the absolute strength of the
pilot, which is measured by RSCP. If the pilot RSCP is greater than a
threshold,
the
pilot
is
a
strong
pilot.
Namely,
.
Definition
of
"excessive"
When judging whether excessive pilots exist at a point, the pilot
number is the judgment criteria. If the pilot number is more than a
threshold, the pilots at a point are excessive. Namely,
Definition
of
"no
best
server
strong
enough"
When judging whether a best server strong enough exist, the
judgment criteria is the relative strength of multiple pilots. If the
strength different of the strongest pilot and the No.
strong
pilot is smaller than a threshold, no best server strong enough exists
in the point. Namely,
Based on previous descriptions, pilot pollution exists if all the following conditions are met:
is more
Set
for pilot pollution are:
, and
is larger
Improper Configuration
Algorithm Parameters
of
SHO
Delayed handover
According to the signaling flow for CS services, the UE fails to receive active set update
command (physical channel reconfiguration command for intra-frequency HHO) due to
the following cause. After UE reports measurement message, the Ec/Io of original cell
signals decreases sharply. When the RNC sends active set update message, the UE powers
off the transmitter due to asynchronization. The UE cannot receive active set update
message. For PS services, the UE might also fail to receive active set update message or
perform
TRB
reset
before
handover.
Delayed handover might be one of the following:
Turning corner effect: the Ec/Io of original cell decreases sharply and that of the target cell
increases greatly (an over high value appears)
Needlepoint effect: The Ec/Io of original cell decreases sharply before it increases and the
Ec/Io of target cell increase sharply for a short time.
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
Ping-pong handover includes the following two forms
Handover
The best server changes frequently. Two or more cells alternate to be the best server. The
RSCP of the best server is strong. The period for each cell to be the best server is short.
No primary pilot cell exists. Multiple cells exist with little difference of abnormal RSCP. The
Ec/Io for each cell is bad.
According to the signaling flow, when a cell is deleted, the 1A event is immediately
reported. Consequently the UE fails because it cannot receive the active set update
command.
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.
Reperforming
Drive
Locating Problems
Test
and
If the problem is not due to previous causes, perform DT again and collect DT data.
Supplement data from problem analysis.
HHO Types
HHO includes the following types:
Intra-frequency HHO
The frequency of the active set cell before HHO is the same as that of the cell after HHO.
If the cell does not support SHO, HHO might occur. HHO caters for cross-RNC intrafrequency handover without lur interface, limited resources at lur interface, and handover
controlled by PS service rate threshold of handover cell. The 1D event of intra-frequency
measurement events determines intra-frequency HHO.
Inter-frequency HHO
The frequency of the active set cell before HHO is different from that of the cell after
HHO. HHO helps to carry out balanced load between carriers and seamless proceeding.
Start compression mode to perform inter-frequency measurement according to UE
capability before inter-frequency HHO. HHO judgment for selecting cell depends on
period measurement report.
Adjustment
The optimization flow for HHO is similar with that of SHO and the difference lies in parameter
optimization.
Confirming inter-frequency missing neighbor cell is similar to that of intra-frequency. When
call drop occurs, the UE does not measure or report inter-frequency neighbor cells. After call
drop, the UE re-camps on the inter-frequency neighbor cell.
HHO problems usually refer to delayed handover and Ping-pong handover.
Delayed HHO usually occurs outdoor, so call drop occurs when the UE is moving. There are
three solutions:
Ec/Io as the measurement target for inter-frequency handover. When setting "interfrequency measurement quantity", check that the cell is at the carrier coverage edge or in
the carrier coverage center. If intra-frequency neighbor cells lie in all direction of the cell,
the cell is defined as in the carrier coverage center. If no intra-frequency cell lies in a
direction of the cell, the cell is defined as at the carrier coverage edge.
In the cell at the carrier coverage edge, when UE moves along the direction where no
intra-frequency neighbor cell lies, the CPICH Ec/No changes slowly due to the identical
attenuation rate of CPICH RSCP and interference. According to simulation, when CPICH
RSCP is smaller than the demodulation threshold (100 dBm or so), the CPICH Ec/No
can still reach 12 dB or so. Now the inter-frequency handover algorithm based on
CPICH Ec/No is invalid. Therefore, for the cell at the carrier coverage edge, using CPICH
RSCP as inter-frequency measurement quantity to guarantee coverage is more proper.
In the cell in the carrier coverage center, use CPICH RSCP as inter-frequency
measurement quantity, but CPICH Ec/No can better reflect the actual communication
quality of links and cell load. Therefore use CPICH Ec/No as inter-frequency
measurement quantity in the carrier coverage center (not the cell at the carrier coverage
edge), and RSCP as inter-frequency measurement quantity in the cell at the carrier
coverage
edge.
In compression mode, the quality of target cell (inter-frequency or inter-RAT) is usually
measured and obtained. The mobility of MS leads to quality deterioration of the current
cell. Therefore the requirements on starting threshold are: before call drop due to the
quality deterioration of the current cell, the signals of the target cell must be measured and
reporting is complete. The stopping threshold must help to prevent compression mode
from
starting
and
stopping
frequently.
The RNC can distinguish CS services from PS services for inter-frequency measurement.
If the RSCP is smaller than 95 dBm, compression mode starts. If the RSCP is greater
than 90 dBm, compression mode stops. Adjust RSCP accordingly for special scenarios.
Flow Chat
3.1.3 shows the inter-RAT handover CQT flow.
1. Inter-RAT handover
CQT flow
Data Configuration
Inter-RAT handover fails due to incomplete configuration data, so pay attention to the
following data configuration.
Frequency number
Add location area cell information near 2G MSC to location area cell
list of 3G MSC. The format of location area identity (LAI) is MCC +
MNC + LAC. Select LAI as LAI type. Select Near VLR area as LAI
class and add the corresponding 2G MSC/VLR number. The cell
GCI format is: MCC + MNC + LAC + CI. Select GCI as LAI type.
Select Near VLR area as LAI class and add the corresponding 2G
MSC/VLR number.
Add data of WCDMA neighbor cells on GSM BSS. The data
includes:
Downlink frequency
Primary scramble
Main indicator
MCC
LAC
RNC ID
CELL ID
Causes
The causes to call drop due to 3G-2G inter-RAT handover are as below:
Type
According to the difference of handover on DPCH in HSDPA network, the HSDPA handover
includes:
Flow
When a problem occurs, check R99 network. If there is similar problem with R99 network,
solve it (or, check whether the R99 network causes HSDPA service problems, such as weak
coverage, missing neighbor cell. Simplify the flow).
3.1.4 shows the DT/CQT flow for HSDPA handover.
The problems with handover of HSDPA subscribers are usually caused by the faulty
handover of R99 network, such as missing neighbor cell and improper configuration of
handover parameters. When the R99 network is normal, if the handover of HSDPA
subscribers is still faulty, the cause might be improper configuration of HSDPA parameters.
Engineers can check the following aspects:
2. Movement of the
MBMS UE between
PTM cells
The movement of the MBMS UE between PTM cells is similar to the movement of UE
performing PS services in the CELL-FACH state. The UE performs the handover between
cells through cell reselection and obtains a gain through soft combining or selective
combining between two cells to guarantee the receive quality of the service. The UE first
moves to the target cell and then sends a CELL UPDATE message to notify the serving radio
network controller (SRNC) that the cell where the UE stays is changed. The SRNC returns a
CELL UPDATE CONFIRM message. The UE receives an MBMS control message from the
MCCH in the target cell and determines whether the MBMS radio bearer to be established is
consistent with that of the neighboring cell. If they are consistent, the original radio bearer is
retained. The MBMS mobility optimization, which guarantees that the UE obtains better
quality of service at the edge of cells, covers the following aspects:
3. Analysis flow
handover traffic
statistics data
for
Check the SHO success rate of entire network and cell in busy hour.
If they are not qualified, analyze the problematic cells in details.
Sort the SHO (or softer handover) failure times of the cell by TOP N
and locate the cells with TOP N failure times. List the specific
1. SHO
failure
indexes
Failure causes
Analysis
Configuration nonsupport
The UE thinks the content of active set update for RNC to add/delete links does not
support SHO. This scenario seldom exists in commercial networks.
Synchronization
reconfiguration nonsupport
The UE feeds back that the SHO (or softer handover) for RNC to add/delete links is
incompatible with other subsequent processes. The RNC guarantees serial
processing upon flow processing. This cause is due to the problematic UE.
Invalid configuration
The UE thinks the content of active set update for RNC to add/delete links is
invalid. This scenario seldom exists in commercial networks.
No response from UE
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
occurs in areas with weak coverage and small handover area. RF optimization must
be performed in the areas.
Outgoing
HHO
Success
Incoming
HHO
Success
Upon HHO failure, pay attention to indexes related to internal NodeB, between NodeBs, and
between RNCs.
3.2.2 lists the HHO failure indexes.
2. HHO failure
indexes
Failure
cause
Analysis
Other causes
Configuration
nonsupport
PCH failure
Synchronization
reconfiguration
nonsupport
The UE feeds back HHO is incompatible with other consequent processes due to
compatibility problems of UE.
Cell update
Cell update occurs upon outgoing HHO. These two processes lead to outgoing HHO
failure.
Invalid configuration
The UE thinks the command for outgoing HHO as invalid. This is a compatibility
problem of UE.
Other causes
1. Voce inter-RAT
outgoing
handover
flow
During CS inter-RAT outgoing handover process, when the RNC sends a RELOCATION
REQUIRED message to CN, if the current CS service is AMR voice service, count it as an
inter-RAT handover preparation. When the RNC receives the IU RELEASE COMMAND
message replied by CN, count it as inter-RAT outgoing handover success according to the
SRNC cell being used by UE.
If CS inter-RAT handover fails, check the failure statistics indexes listed in 3.2.3.
1. Traffic
statistics
indexes of CS
inter-RAT
handover
preparation
failure
Failure
cause
Analysis
After the RNC requests handover preparation, it receives the release command
from CN. This includes the following two cases:
SRNS
cancellation
relocation
The previous two cases, despite incomplete handover, are normal nesting
flows.
SRNS
expiration
relocation
Unavailable resource
Other causes
relocation
SRNS
relocation
nonsupport in target
CN/RNC/system
Other causes
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.
PS Inter-RAT
Rate
Handover
Success
After the RNC sends the CELL CHANGE ORDER FROM UTRAN message, the PS interRAT outgoing handover fails if it receives the CELL CHANGE ORDER FROM UTRAN
FAILURE message. You must check the indexes listed in 3.2.3.
1. Traffic
statistics
indexes of PS
inter-RAT
outgoing
handover
failure
Failur
e
cause
Analysis
The UE fails to support the handover command of the network, because the
UE is incompatible with the command.
PCH failure
Radio
cause
network
layer
Other causes
You must analyze the causes according to CN and BSS signaling tracing.
counts the successful times of outgoing intra-frequency HHO from HS-DSCH to DCH in
the
cell.
Success
rate
of
H-to-R99
inter-frequency
switch
update
The RNC algorithm is unavailable now, so this index is unavailable.
After the service is set up, the RNC sends CN the RAB RELEASE
REQUEST message.
After the service is set up, the RNC sends CN the IU RELEASE
REQUEST message. Afterwards, it receives the IU RELEASE
COMMAND sent by CN.
Upon statistics, sort them by specific services. Meanwhile, traffic statistics includes the cause
to release of RAB of each service by RNC.
CS CDR is calculated as below:
2. Types of CDR
indexes
CD
R
type
RF
Due
to
interface
Corresponding
process
Cause
signaling
air
Expiration
process timer
of
Hardware failure
RB RECFG
Expiration of PHY/TRCH/SHO/ASU
HHO failure
The transport failure between RNC and
NodeB. NCP reports failure.
FP synchronization failure.
Transport
failure
layer
Subscribers are
released by force
by MML
O&M intervention
The definition of RAN traffic statistics call drop is according to statistics of lu interface
signaling, including the times of RNC's originating RAB release request and lu release
request. The DT call drop is defined according to the combination of messages at air
interface and from non-access lay and cause value. They are inconsistent.
2. Flow
chart
for
analyzing call drop
Weak Coverage
For voice services, when CPICH Ec/Io is greater than 14 dB and RSCP is greater than
100 dBm (a value measured by scanner outside cars), the call drop is usually not due to
weak coverage. Weak coverage usually refers to weak RSCP.
4.2.1 lists the thresholds of Ec/Io and Ec (from an RNP result of an operator, just for
reference).
1. Thresholds of
EcIo and Ec
B
i
t
r
a
t
e
o
f
s
e
r
v
i
c
e
S
e
r
v
i
c
e
D
L
EcI
o
thr
esh
old
s
E
b
N
o
Ec
thr
esh
old
s
CS 12.2
12.2
8.7
13.3
103.1
CS 64
64
5.9
11.9
97.8
PS 64
64
5.1
12.7
98.1
PS 128
128
4.5
13.3
95.3
PS 384
384
4.6
10.4
90.6
Uplink or downlink DCH power helps to confirm the weak coverage is in uplink or downlink
by the following methods.
downlink is restricted first. If the uplink and downlink is badly unbalanced, interference
probably exists in the restricted direction.
A simple and direct method for confirming coverage is to observe the data collected by
scanner. If the RSCP and Ec/Io of the best cell is low, the call drop is due to weak coverage.
Weak coverage might be due to the following causes:
Lack of NodeBs
Incorrectly configured sectors
NodeB failure due to power amplifier failure
The over great indoor penetration loss causes weak coverage. Incorrectly configured sectors
or disabling of NodeB will occur, so at the call drop point, the coverage is weak. You must
distinguish them.
Interference
Both uplink and downlink interference causes call drop.
In downlink, when the active set CPICH RSCP is greater than 85 dBm and the active set
Ec/Io is smaller than 13 dB, the call drop is probably due to downlink interference (when the
handover is delayed, the RSCP might be good and Ec/Io might be weak, but the RSCP of
Ec/Io of cells in monitor set are good). If the downlink RTWP is 10 dB greater than the
normal value (107 to 105 dB) and the interference lasts for 2s3s, call drop might occur.
You must pay attention to this.
Downlink interference usually refers to pilot pollution. When over three cells meets the
handover requirements in the coverage area, the active set replaces the best cell or the best
cell changes due to fluctuation of signals. When the comprehensive quality of active set is
bad (CPICH Ec/Io changes around 10 dB), handover failure usually causes SRB reset or
TRB reset.
Uplink interference increases the UE downlink transmit power in connection mode, so the
over high BLER causes SRB reset, TRB reset, or call drop due to asynchronization. Uplink
interference might be internal or external. Most of scenario uplink interference is external.
Without interference, the uplink and downlink are balanced. Namely, the uplink and downlink
transmit power before call drop will approach the maximum. When downlink interference
exists, the uplink transmit power is low or BLER is convergent. When the downlink transmit
power reaches the maximum, the downlink BLER is not convergent. It is the same with
uplink interference. You can use this method to distinguish them.
Abnormality Analysis
If the previous causes are excluded, the call drop might due to problematic equipment. You
need to check the logs and alarms of equipment for further analysis. The causes might be as
below:
Preparing Data
The data to be prepared include:
If the signals of best server are stable, analyze RSCP and Ec/Io.
If the signals of best server fluctuate sharply, you must analyze the
quick variation of best server signals and the situation without best
server. Consequently you can analyze call drop due to ping-pong
handover.
Analyzing RSCP and Ec/Io of Best
cell
Observe the RSCP and Ec/Io of best cell according to scanner.
If both RSCP and Ec/Io are bad, call drop must be due to weak
coverage.
If RSCP is normal but Ec/Io is bad (delayed handover is excluded,
intra-frequency neighbor cell interference), call drop must be due to
downlink interference.
If both RSCP and Ec/Io are normal,
When the cell in UE active set is inconsistent with the best cell according to scanner, call
drop must be due to missing neighbor cell and delayed handover.
When the cell in UE active set is consistent with the best cell according to scanner, call
drop must be due to uplink interference or must be abnormal.
VS.RAB.Loss.PS.64K / VS.RAB.SuccEstPS.64
VS.RAB.Loss.PS.128K / VS.RAB.SuccEstPS.128
VS.RAB.Loss.PS.384K / VS.RAB.SuccEstPS.384
Based on analysis of previous indexes, you can obtain the performance of various services
and rates in the network, as well as SHO/HHO call drop. More important, you can obtain the
cells with bad indexes and periods.
1. Traffic
statistics
indexes
for
analyzing
causes to call
drop
Failure
cause
OM interference
Causes due
preemption
Analysis
to
RAB
High-priority preemption causes release of CS links. This kind of call drop occurs
when the load and resources are limited. Performing expansion depends on the times
of occurrence.
The causes due to UTRAN in the cell lead to abnormal release of link. This
Uplink RLC reset causes release of links, because the coverage quality (including
missing neighbor cell and over mall handover area) is bad.
Downlink SRB reset causes release of links, because the coverage quality (including
missing neighbor cell and over mall handover area) is bad.
Uplink
failure
synchronization
Downlink synchronization
failure
No response of UU port
The UE air interface fails to respond the command transmitted by system, because
the coverage is bad.
Other RF causes
The RNC detects that AAL2 Path at CS lu interface is abnormal, so the system
originates an abnormal release. The problem might be due to abnormal transport
equipment. Immediate normal release during RB establishment is counted by
statistics as abnormal release as the cause.
Abnormal GTPU
The RNC detects the GTPU at PS lu interface is abnormal, so the system originates
an abnormal release. The problem is due to equipment failure.
Other causes
You need to analyze the abnormal call drop based on RNC logs.
You can classify the previous indexes 4.3.2 by the classification of previous chapters. They
fall into air interface causes (RF and flow expiration) and not due to air interface causes
(hardware failure, transport failure, and subscribers' interference). Therefore you can have
an overall master of network and obtain the major causes impacting the network.
Analyzing traffic statistics indexes helps to expose potential problems. To locate and analyze
problems, you need to use DT and CHR. For problematic cells, the cell-oriented DT is
performed to trace the signaling flow at UE side and of RNC. For details, see 3.1.
2. Flow
for analyzing
call tracing
release
release
(the
message
is
(the
message
is
The former corresponds to call drop caused by TRB reset. The latter corresponds to call
drop caused by SRB reset. By searching for the previous two messages, you can obtain the
call drop time and the signaling message before call drop for further analysis.
The call drop due to SRB reset is that the UE or RNC fails to receive signaling transmitted in
confirmation mode, and consequently SRT reset occurs, so the connection is released. SRB
reset occurs probably if the UE fails to receive the following messages in downlink:
Measurement report
Active set update complete
Physical channel reconfiguration complete
Transport channel reconfiguration complete
RB reconfiguration complete
Confirm that the UE receives these messages by tracing messaged at RNC side.
The cell is in the preliminary congestion state and the channel power of the
MBMS service is reset to the minimum; or the cell is in the over-congestion
state and the MBMS service with a lower priority is released by force. The
channel power can, however, be automatically recovered to the maximum
or the service can be re-established through periodic detection.
The UE is at the edge of the cells, and the neighboring cells are not
configured for the cell in which the UE is located. As a result, the UE is
unable to obtain a gain through soft combining or selective combining.
Run the DSP CELLMBMSSERVICE command to query the status of the
current MBMS service. If the MBMS service is not established
successfully, the failure cause is displayed.
You can improve the coverage rate by optimizing the RF, adding NodeBs, or adjusting the
antennas. If the coverage does not improve, increase the maximum power of the MBMS
traffic channel. If a neighboring cell is not configured, configure it.
5 FAQs Analysis
5.1 SHO Problems
5.1.1 Over High SHO Rate due to Improper SHO Relative Threshold
Description
The SHO rate in traffic statistics indexes is over high. More than two cells exist in active set
most of the time during DT and are in SHO state.
Analysis
Analyze the relative threshold of 1A and 1B event, namely, reporting range.
5.1.1 shows the SHO relative threshold
1. SHO
threshold
relative
According to 5.1.1, the greater the reporting range is, the more easily a neighbor cell is listed
into active set and the more difficult it is deleted from active set. This causes over high SHO
rate.
Description
SHO hysteresis is serious in DT: though the signals of a neighbor cell are strong, the cell can
be listed into active set after a long time. If the DT car moves quickly, call drop occurs due to
delayed handover.
Analysis
Layer 3 filter reduces the impact by frequently-fluctuating signals and avoids ping-pong
handover.
The filter of measurement values is calculated as below:
Wherein,
Fn: the measurement resulted update after filter is processed.
Fn-1: the measurement result of last point after filter is processed.
Mn: the latest measurement value received in physical layer.
a = (1/2)(k/2). The k is from Filter coefficient, namely, FilterCoef. If K = 0 and a = 1, there is
no layer 3 filter.
The filter coefficient ranges from 0 to 6 (integers). The greater it is, the stronger the capability
of smoothing burr is and the weaker the capability of tracing signals is. You must make a
balance.
According to simulation, 5.1.2 lists the relationship between the filter coefficient and the
corresponding tracing time.
1. Relationship
between
the
filter coefficient
and
the
corresponding
tracing time
Filter
coefficient
11
Intrafrequency
tracing time
(s)
0.2
0.4
0.6
1.4
4.2
8.4
17
The distance between sites in dense urban areas is short and the handover time is short, so
you must reduce the tracing time, namely, the filter coefficient. The value 2 is usually proper
for filter coefficient of layer 3.
Description
The call drop point is related to signaling flow before call drop.
5.1.3 shows the signaling flow recorded by UE before call drop.
1. Signaling
flow
recorded
by
UE
before call drop
Analysis
Check the pilot test data from UE and scanner at call drop points. 5.1.3 shows the scrambles
recorded by UE active set and scanner before call drop. In 5.1.3, the measurement result of
UE active set and canner is inconsistent and the SC 170 of scanner does not exist in UE
active set.
1. Scrambles recorded
by UE active set and
scanner before call
drop
The cause might be missing neighbor cell or delayed handover. Check scrambles in UE
active set. 5.1.3 shows the scrambles in UE active set before call drop. No SC 170 cell exists
in UE monitor set, because this is possibly due to missing neighbor cell.
2. Scrambles in UE
active set before call
drop
Continue to check the neighbor cell list sent by RNC to UE before call drop, as shown in
5.1.3 and 5.1.3. According to the latest measurement control before call drop, no SC 170
exists in the neighbor cell list, because the call drop is due to missing neighbor cell of SC 6
and SC 170.
3. UE intra-frequency
measurement control
point before call drop
4. Analyzing signaling
of UE intra-frequency
measurement control
before call drop
If only the UE recorded information during test, without scanner information, confirm that call
drop is due to missing neighbor cell by using the following method, as shown in 5.1.3:
Confirm the scrambles of all cells in active set and the scrambles of
cells in monitor set measured by UE before call drop.
Compare the scramble information of the cell where the UE camps
on after reselection after call drop and the scrambles in UE active set
and
monitor
set
before
call
drop.
If the former scramble is not in the scramble list of active set and
monitor set before call drop, the call drop is probably due to missing
neighbor cell.
Check
the
neighbor
cell
list.
This applies for solving call drop due to missing neighbor cell on
site.
5. Confirming missing
neighbor cell without
information
from
scanner
Solution
Add neighbor cells. Because the RNC updates measurement control according to the best
cell which is obtainable by searching for intra-frequency measurement report with 1D event
before measurement control is sent. Usually they are configured to bi-directional neighbor
cells.
1. 2G handover
times
Assist_GSM_HO_Count
SERVCELL
NCELL
HOCOUNT
12531
10121
417
12531
10161
3262
12531
10162
2070
12531
10301
381
12531
10321
265
12531
12061
12531
12101
961
12531
12111
16
12531
12251
12531
12291
12531
12292
12531
12330
1082
12531
12391
1063
12531
12451
17019
12531
12532
16030
12531
12540
74
12531
12591
926
12531
12592
20994
12531
14051
12531
14072
12531
14091
211
12531
14111
12531
14460
321
12531
56361
16
12531
56362
12531
56820
12531
56910
206
Search for the neighbor cells with few handover times and even no handovers, such as cell
1253112292. 5.1.4 shows the location relationship of 2G redundant neighbor cells.
2. Location relationship
of
2G
redundant
neighbor cells
According to 5.1.4, multiple NodeBs are located between the cell 12531 and the cell 12292,
so the handover probability is small. Therefore, delete the neighbor cell relationship.
The judgment principles based on 2G statistics might have mistakes, so you must confirm
that no call drop occurs after deleting the neighbor cell relationship.
After network launch, the handover times in traffic statistics according to statistics reflects the
real handovers, so deleting abundant neighbor cells by using the handover times in traffic
statistics according to statistics is more reliable. You need to register the traffic statistics
tasks of two cells on traffic statistics console of RNC.
3. The
2nd
ServiceCell
Yuxing Rd.
best
near
4. The
3rd
ServiceCell
Yuxing Rd.
best
near
5. The
4th
ServiceCell
Yuxing Rd.
best
near
6. Composition of pilot
pollution near Yuxing
Rd.
From 5.1.5, 5.1.5, 5.1.5, 5.1.5, and 5.1.5, though SC20 cell is planned to cover the area,
but the best ServiceCell is as listed in 5.1.5.
1. Best
servers
and other cells
Best
ServiceCell
1st best ServiceCell
Primary
SC220
Others
SC270
SC200
SC200
8. RSCP
of
ServiceCell
Yuxing Rd.
Best
near
As shown in 5.1.5, the RSSI of the areas with pilot pollution is not large, about 100 dBm
to 90 dBm. As shown in 5.1.5, the RSCP of Best ServiceCell is between 105 dBm to
100 dBm. The pilot pollution of the area is caused by no strong pilot, so you can solve the
problem by strengthening a strong pilot.
The SC270 cell is planned to cover the area. 5.1.5 shows RSCP of RSCP distribution of
SC270 cell. The signals from SC270 cell are weak in the area with pilot pollution.
Solution
According to on-site survey, the residential area is densely distributed by 6-floor or 7-floor
buildings. The test route fails to cover the major streets, and is performed in narrow streets
with buildings around, so the signals are blocked. The suggestion is to 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.
After analysis of DT data, the expected result after adjustment is that the coverage area by
SC270 cell increases and the coverage is enhanced.
5.1.5 shows the pilot pollution near Yuxing Rd. after optimization.
5.1.5 shows the best ServiceCell near Yuxing Rd. after optimization.
5.1.5 shows the RSCP of best ServiceCell near Yuxing Rd. after optimization.
3. RSCP
of
ServiceCell
Yuxing Rd.
optimization
5.1.5 shows the RSCP of SC270 cell near Yuxing Rd. after optimization.
best
near
after
According to the DT data, the pilot pollution near Yuxing Rd. after optimization is eliminated,
the signals from SC270 cell after optimization are stronger, and the SC270 becomes the best
ServiceCell. This complies with the expected result.
According to 5.1.6, the signals of original cell attenuate 10 dB sharply within 1s, and the
signals of target cell increase 10 dB. If the signals are weak before attenuation, and 1a event
is configured to easily-triggered state, the measurement report is sent according to traced
signaling of the UE, and the RNC receives the measurement report according to signaling
traced by the RNC.
When the RNC sends the active set update message, the UE cannot receive it due to weak
signals of original cell, so the signaling is reset, and call drop occurs. If 1a event is slowly
triggered (such as configuring great hysteresis or triggering time), TRB reset occurs before
the UE sends the measurement report.
5.1.6 shows an example of turning corner effect.
According to 5.1.6, before turning corner, the signals of active set scramble 104 and 168
attenuate to smaller than 17 dB, but that of 208 is strong (8 dB). According to the signaling
traced by the RNC, and the UE reports the 1a event of the cell of scramble 208, and sends
the active set update message. The UE does not receive the completion message, so the
call drop occurs, as shown in 5.1.6.
Solution
To solve turning corner effect problems, do as follows:
Based on previous analysis, the first method prevails. If it fails, use the second method. If the
second method fails, use the third method (the third method is the best solution, especially in
areas where you can adjust antenna easily).
1. Needle
pointsignal variance
Observe the needlepoint effect by scramble distribution diagram of the best cell recorded by
Scanner. If two antennas cover two streets respectively, at the crossing point, needlepoint
effect occurs easily.
5.1.7 shows the call drop distribution of PS384K intra-frequency hard handover (it is the best
cell). Wherein, call drop point drop4, drop5, drop6, drop7, drop15, and drop16 are caused by
needlepoint effect.
Solution
To solve problems caused by needlepoint effect, you can refer to the solution to turning
corner effect. The key to adjust antenna is not to enable original signals attenuate sharply
and not to enable target signals increase sharply. In addition, you can increase the
retransmission times to resist to attenuation of signals so that CDR is lowered.
Description
5.1.8 shows signal distribution of cell52 vs. cell88 (signal fluctuation in handover areas).
1. Signal distribution of
cell152 vs. cell88
(signal fluctuation in
handover areas)
After the UE hands over from cell 152 to cell 88, the signals of cell 152 are stronger than that
of cell 88. In 5.1.8, after the signals of cell 152 keep weaker than that of cell 88, the signals
of cell 152 become stronger than that of cell 88 for continuous 2s.
Analysis
When the UE hands over from cell 152 to cell 88, and the signals of cell 152 become better
than that of cell 88. This is similar to the needlepoint effect in 5.1.7. Therefore quick change
of best server signals causes the same handover failures as the needlepoint effect causes,
as follows:
Description
The UE keeps performing intra-frequency HHO at the cell border, so the call quality declines
and even call drop occurs.
Analysis
Reporting the 1D event triggers the inter-frequency HHO. The 1D event is reported when the
best cell changes, as shown in 5.2.1.
1. Reporting 1D event
The UE is at the border of two cells, so the signals from the two cells are equivalently strong.
Signal fluctuation easily causes ping-pong handover to best cells. Frequent report 1D event
triggers inter-frequency HHO.
To avoid intra-frequency ping-pong HHO caused by 1D event triggered by frequent
fluctuation of signals if the channels are similar, you can increase the hysteresis, as shown in
5.2.1.
2. Increasing hysteresis
to reduce frequently
reporting of 1D event
According to 5.2.1, the second times does not reach the hysteresis, so reporting 1D event is
not triggered.
Description
When the UE moves to an inter-frequency cell, it fails to start compression mode to start
inter-frequency measurement. It camps on the inter-frequency cell after disconnection.
Analysis
The cell mentioned previously is configured as the carrier central cell after querying cell
configuration. Namely, the 2D event, 2F event, and inter-frequency measurement all take
Ec/No as measurement quantity.
The measured value of pilot Ec/No depends on the following two aspects:
CPICH Ec/Io of which changes slowly. According to the simulation and on-site test, When the
CPICH RSCP is about 110 dBm, the CPICH Ec/Io can reach about 12 dB.
1. Attenuation
relationship of RSCP
and Ec/No
If you take Ec/Io as the measurement quantity for 2D event, the 2D event will be triggered
before call drop. Therefore adopting Ec/Io as the measurement quantity for 2D event will not
trigger 2D event upon call drop of UE, so the inter-frequency measurement will not be
started.
In this case, configure the cell to carrier coverage edge cell and take RSCP as the
measurement quantity for 2D/2F event so that inter-frequency measurement is originated in
time.
Description
In part of the office building of a commercial deployment, the UMTS-GSM dual-mode MS
performs frequent ping-pong reselection of cells between 3G and the 2G network in the idle
state. 2G and 3G flag are displayed in the screen of Siemens U15 and Moto A835 MSs.
WCP and GCP are displayed in the screen of the Qualcomm test MS frequently. The
reselection from the 3G network to the 2G network takes 1min on average. The reselection
from the 2G network to the 3G network takes 12 minutes on average. During the testing,
the location of the MS and the circumstance keep fixed.
Analysis
The reselection from the 3G network to the 2G network is as follows:
In the cells that satisfy the previous conditions, the UE select the cell
of best quality as the target cell to be reselected.
Therefore, the key parameter in from the 2G network to 3G is FDD_Qmin. The default
configuration is 12 dB.
Solutions
In network optimization, the operator can take the following adjustment:
Description
The UE performing PS domain services hands off between the 3G network and the 2G
network.
Analysis
For inter-RAT handoff of CS and PS, the services for CS and PS are different in handoff
between the 2G network and the 3G network.
Description
In the office building of a commercial deployment, when the UE originates a call in areas
covered by the 3G network and moves towards the areas covered by the 2G network, the
call drops easily. The call succeeds one or two times every ten times.
Analysis
The 2G neighbor cells configuration of the 3G network cells that cover the office building in
the WCDMA network parameters is examined. The 2G cells that cover office building need to
be confirmed in the 2G neighbor cells list. UMTS outdoor macrocells are used to perform 3G
coverage in the office building, the test route is switched by passing two iron doors. After the
operator opens the door, enters, and closes the door, the signal attenuates sharply. 5.3.3
shows the UMTS signal distribution observed by a scanner.
The signal attenuates sharply, so the handoff is not performed in time, and then the call
drops. The key solution is to adjust the inter-RAT switching parameters. This leads to an
earlier and faster handoff.
The operator does as follows:
Change the cell independent offset (CIO) in the GSM neighbor cell
from 0 dB to 5 dB. The UE hands off to the GSM cell more easily.
Call still drops in test.
Change 2D RSCP Threshold from 95 dBm to 85 dBm to 75
dBm. The inter-RAT measurement starts earlier. Call still drops in
test.
Change GSM RSSI from 90 dBm to 95 dBm. The UE hands off to
GSM cells more easily. Call still drops in test.
Change 2D Trigger Time from 640ms to 320ms to 0ms. The interRAT measurement starts more easily. Call still drops in test. Change
the parameter back to 640ms.
Change the cell location property from carrier border to carrier
center (the associated measurement changes from RSCP to Ec/Io).
Change 2D Ec/Io Threshold from 24 dB to 10 dB. Call still drops
in test.
Change Inter RAT handover trigger time from 5000ms to 2000ms.
The UE performs inter-RAT more quickly. Call drop is improved.
Recover the parameter changed in Step 5 as it was.
1. Indoor 3G
distribution
RSCP
Solutions
The operator checks as follows:
Example 1:
14:24:17(12): According to RB Setup, the UE accesses the network by PSC 417.
14:25:36(02): The UE does not report 2D measurement report until call drop. The RNC
does not send measurement control report.
Conform that no inter-RAT neighbor cells are configured by examining parameters. If the
cells are added, call drop problems are solved.
Example 2:
16:38:18(18): The UE reports 1D event of cell 273, and cell 273 becomes the best cell.
However, the BCCH 538 indoor 2G cell is not configured as an inter-RAT neighbor cell
of cell 273.
16:38:40(20): The UE keeps sending measurement reports, but detects that the signals of
other GSM neighbor cells are weak. Therefore the RNC does not start handover, and then
call drop occurs.
The cell of PSC273 and PSC 264 alternate to be the best server. Indoor GSM neighbor
cells are configured as the inter-RAT neighbor cells of the cell of PSC264, but the cell of
PSC273 is not configured with any neighbor cells. When the UE enters indoor, the cell of
PSC273 becomes the best server, so call drop occurs. After indoor GSM neighbor cells
are configured as the inter-RAT neighbor cells of the cell of PSC273, no call drop occurs.
If excessive neighbor cells are configured, the UE must spend more time on inter-RAT
measurement. The measurement internal of UE is limited, excessive neighbor cells delay UE
to measure available neighbor cells, so call drop occurs.
Example :
11:30:11(92): The RNC sends measurement control messages (23 inter-RAT neighbor
cells)
11:32:22(61): The UE keeps reporting to BSIC Nonverified cell until 2 minutes before
call drop.
Configure the inter-RAT neighbor cells to the needed four neighbor cells, the MotoA835
hands over successfully.
No Measurement Report by UE
If the UE does not send measurement report, the UE performs the same as when the
neighbor cells are missing. The phenomena are as follows:
16:38:07(19): The RNC receives Physical channel reconfiguration completion, and then
sends measurement control messages.
16:38:08(75): The cell of PSC 492 reports 1D and becomes the best server. It sends new
measurement control messages after 1.5s.
16:39:19(73): The system does not receive the UE inter-RAT measurement report before
call drop.
Delayed Handover
According to signaling of the RNC, a normal inter-RAT handover takes 5s. The following are
the time needed by the RNC, longer than that on UE. If the walking speed is 3 km/h, it takes
45 meters. The time depends on different scenes.
16:21:06(30): The UE sends the 2D measurement report.
16:21:06(37): The RNC sends the Physical channel reconfiguration message.
16:21:07(46): The UE sends the Physical channel reconfiguration completion message.
16:21:09(72): The UE sends the inter-RAT measurement reports.
16:21:10(48): The system sends the UE HO FROM UTRAN CMD GSM message.
16:21:11(11): The RNC sends the Iu interface Release Command message.
When the UE moves outdoor to indoor with the 3G signals fluctuating sharply, call drop
occurs due to delayed handover. According to the signaling, the phenomena of delayed
handover are as follows:
The NodeB does not report RL failure, but SRB reset occurs.
Moto handset:
15:26:27(87): The RNC sends Physical channel reconfiguration (active set contains
PSC201 and PSC16).
15:26:30(30): The UE report BCCH 844 BSIC Nonverified, and the level is 87 dBm.
15:26:31(26): The UE report BCCH 844 BSIC verified, and the level is 88 dBm.
15:26:32(13): The RNC sends the HO CMD message.
15:26:34(25): The UE sends inter-RAT measurement reports, but does not hand over. This
is because the UE does not receive HO CMD sent by the RNC, or the UE fails in
accessing the 2G network. The CN sends lu Release due to treloccomplete expire
(normally successful relocation causes lu Release, and the UE succeeds in accessing the
2G network).
Moto handset:
17:08:59(61): The UE sends 2D measurement reports, and the RNC sends Physical
channel reconfiguration.
17:09:00(78): The RNC receives Physical channel reconfiguration completion, and sends
measurement control messages.
17:09:04(35): The NodeB is out of synchronization, so call drop occurs, and no inter-RAT
the measurement report is sent.
17:09:20(89): The RNC originates Iu Release due to Radio Connection with UE lost.
Description:
The UE cannot hand over from the 3G network to the 2G network smoothly. In details,
the UE originates a call in 3G coverage areas or uses PS services, and then enters 2G
coverage areas. However, it fails in handing over to 2G networks, so call drop occurs.
Analyze the signaling process at RNC side, and check the causes to handover failure. The
causes include:
The network side fails in receiving 2D report from UE, so compression mode is not started.
Consequently 2G cells are not measured, and then asynchronization or SRB/TRB reset cause
call drop.
The network side receives 2D report, but compression mode is not started. The reason is that
the network side sends a PHY_CH_RECFG message, but the UE fails in sending ACK
message or PHY_CH_RECFG_CMP, so SRB is reset, and call drop occurs.
The network side receives Verified measurement reports. After it sends UE the handover
messages, the UE fails in receiving it, so call drop occurs (also for other reasons).
The above cases are due to delayed starting of compression mode, so the quality of
signals of the original cell becomes weak. Therefore subsequent starting compression
mode and handover process cannot proceed normally.
Analysis:
Starting compression mode is affected by 2D event configuration of ID2 measurement
control sent by the network side. You can enable 2D event to be reported more quickly by
the following methods:
Reducing hysteresis
1. Analyzing weak
signals
Scrambles, Ec/Io, and RSCP of cells in active set before call drop
Scrambles and Ec/Io of cells in monitor set
Transmit power of UE, BLER of transport channel, and call drop
time
The DT data analysis software Analyzer provides the previous data.
According to the data before call drop, the Ec/Io of active set is smaller than 15 dB and the
RSCP is close or smaller than 110 dBm, so the call drop must be due to downlink weak
coverage. After call drop, the UE camps on the cell of SC 232 the quality of which is bad, so
the call drop must not be due to missing neighbor cell.
According to the 5.4.1, the transmit power of UE approaches 21 dBm and the downlink
BLER before call drop reaches 100% (due to the comprehensive effect by inner loop and
outer loop, the downlink code transmit power reaches the maximum. Confirm this by using
the data for tracing the performance of RNC). According to previous analysis, the uplink and
downlink are balanced. To sum up, the call drop is due to bad coverage.
Solution
To solve coverage problems, you must adjust engineering parameters of antennas or
construct new sites.
1. Uplink interference
according to RNC
signaling
The UE receives the CC connect message sent by RNC and then replies with CC connect
Acknowledge message which the RNC fails to receive.
The following paragraphs describe the signals before and after call drop.
5.4.2 shows the uplink interference information recorded by UE.
3. Uplink interference
information recorded
by UE
From the UE side, the downlink PCICH Ec and Ec/Io are good, but the uplink transmit power
approaches the maximum. Therefore it is probably an uplink problem.
Interference:
The problematic site is the site 90640. The cells involve the cell 24231 and 24232. The
RTWP of the cell fluctuates sharply.
Solution
Locate the sources of interference t solve uplink interference problems.
Abnormal UE
Failure
to
report
1a
event
by
UE
Call drop occurs easily with a version of Qualcomm 6250 during
test. According to the analysis of data, the Ec/Io and RSCP recorded
by scanner are good upon every call drop. The signals of the active
set recorded are weak, but there are cells with qualified signals.
According to the signaling flow, the UE does not send the 1a event
measurement report of the cell in monitor set, so finally call drop
occurs. After the UE is updated, the problem is solved.
Missing
of
messages
recorded
by
UE
When Moto A835 records signaling messages, it loses some
signaling before call drop easily. This leads to incorrect judgment of
call drop problems. The signaling before call drop is key for
analyzing call drop. If it is missing, you must analyze call drop
problems based on the combination of messages form UE and
information about RNC.
Abnormal
Moto
handset
due
to
continuous
CQT
After tens of or hundreds of CQTs, the calling or called Moto
handset is likely to confront problems, so calls fail. After reset of the
handset, it becomes normal. There is another problem. When the
handset is called, it does not ring and consequently call drop occurs.
However, the screen displays an unanswered call. To avoid this, reset
the handset after continuous CQT.
Failure to hand over from the 3G network to the 2G network
The 3G signals received by a Sony-Ericsson handset attenuate
slowly at the subway entrance and finally no signals are received.
The 2G signals are received at the subway entrance and inside
subways. Therefore, the handset fails to hand over to the 2G
HS-PDSCH
HS-SCCH
HS-DPCCH
DPCH as associated channel.
When the R99 subscribers have handover problems, the HSDPA subscribers cannot
smoothly hand over. Therefore, when the HSDPA subscribers fail to hand over, engineers
need to check R99 handover. If R99 subscribers have handover problems, solve the
problems as previously mentioned. The call drop problems currently in test is usually caused
by R99 problems.
The active set does not list the cells of SC 25 and SC 26. After call drop, the UE camps on
the cell of SC 26. Meanwhile, the quality of signals from the cell of SC 11 declines
sharply.
According to previous description, the call drop is probably due to missing neighbor cell.
For detailed analysis, see 5.1.
Solution
To solve the problem, add the corresponding neighbor cell.
If the 2D/2F and handover threshold is improperly configured, ping-pong handover occurs,
and consequently QoS declines.
Handover
GPRS
between
HSDPA
and
Weak Coverage
After HSDPA technology is used, the downlink load of cell increases. This has some impact
on coverage radius of cell. If the load of original R99 cell is light, the coverage scope
decreases sharply after HSDPA technology is used. Pay attention to cell coverage and call
drop problems caused by decrement of handover areas after R99 network is upgraded to
HSDPA network.
HS-DPCCH is used in uplink of HSDPA, so the HSDPA UE consumes more power than R99
UE, and consequently, the HSDPA UE at the cell edge reaches the maximum transmit power
more quickly than R99 UE at the cell edge. This is uplink power restriction.
The maximum transmit power of some R99 UEs and HSDPA UEs are the
same, 24 dBm.
Description and analysis
In test, before call drop the Ec/Io of active set before call drop is below 15 dB, and the
RSCP is below 110 dBm. After call drop, the UE camps on a new cell, where the Ec/Io
is also above 15 dB and RSCP is above 110 dBm. The transmit power of UE before call
drop approaches 24 dBm (terminal is data card E620), so the problems is caused by weak
coverage.
Solution
To solve the problem, adjust engineering parameters or construct sites.
Call
Drop
due
to
Improper
Configuration of Parameters
The call drops due to strong uplink interference if all the following conditions are met:
6 Summary
Based on related guides to handover and call drop, this guide is complete. It focuses on
operability by on-site engineers. In addition, it describes operation steps in details for the
actual handover and call drop problems in forms of flow chart.
The fundamental knowledge and preparation knowledge are placed in the appendix.
Operations are in the body.
V3.1 supplements HSDPA knowledge, including:
7 Appendix
7.1 SRB&TRB Reset
7.1.1 RAB
RAB is the carrier at the subscriber plane. It is used in transmitting voice, data, and
multimedia services between UE and CN. The RAB assignment is originated by CN. It is a
function of RNC.
RB is ratio bearer between SRNC and UE. It includes layer 2 and above. It is the service
provided to layer 2.
7.1.1 shows the UMTS QoS structure. It provides the part that RAN and RB play in the
UMTS network.
7.1.2 SRB
The SRB carries the signaling at U-Net interface. The TRB carries the services at the Uu
interface and it is the radio bearer at the user plane.
7.1.2 shows the structure of SRB and TRB at the user plane.
7.2 RL FAILURE
When a cell sets up a new radio link, there is a process for uplink and downlink
synchronization. After UE succeeds in uplink synchronization, it powers on the transmitter,
and then the NodeB performs uplink synchronization. If the NodeB succeeds in
synchronization, it sends the RNC an RL RESTORE message. If it fails, it sends the RNC
the RL FAILURE message. When the RNC receives the RL FAILURE message or fails to
receive RL RESTORE message, it releases the resources related to the radio link. If the
active set uses only one radio link, the RNC then originates the release at signaling plane.
7.2 lists the timers and counters related to the synchronization and asynchronization.
1. Timers
and
counters related
to
the
synchronization
and
asynchronizatio
n
Paramete
r ID
T302
Paramete
r Name
Timer 302
Description
N302
Constant 302
T312
Timer 312
N312
Constant 312
T313
Timer 313
Constant 313
T314
Timer 314
Timer 315
N315
Constant 315
1000
Physical unit: s
Content: It indicates the maximum
times continuous synchronization
indicators received from L1. The
default value is 1.
Recommended value: D1
7.2 lists the timers and counters related to call drop at lub interface.
1. Timers
and
counters related
to call drop at
lub interface
Paramete
r ID
Paramete
r Name
Description
NINSYNCIND
Times of continuous
synchronization
indicator
NOUTSYNCIND
Times of continuous
asynchronization
indicator
TRLFAILURE
1. Signaling flow
adding radio link
for
The SRNC decides to set up a new radio link and the new cell to
which the link belongs is under the control of another RNC (DRNC).
The SRNC sends DRNC a Radio Link Setup Request message, and
requires DRNC to prepare the corresponding radio resources. The
new radio link is the first link set up between UE and DRNC, so a
Cell ID
TFS
TFCS
Frequency
Uplink Scramble
Cell ID
TFS
TFCS
Frequency
Update type
Cell ID
Downlink scramble
Adjacent cells
The SRNC decides to delete a radio link. The SRNC sends UE the
Active Set Update message on DCCH. This message includes the
content
about
deleting
radio
link.
The parameters include update type and cell ID.
The UE deactivates the downlink receiver of radio link to be deleted
and sends SRNC the Active Set Update Complete message.
The SHO signaling flow for adding and deleting radio link proceeds as below:
The SRNC decides to set up a new radio link and the new cell to
which the link belongs is under the control of another RNC (DRNC).
The SRNC sends DRNC a Radio Link Setup Request message, and
requires DRNC to prepare the corresponding radio resources. The
new radio link is the first link set up between UE and DRNC, so a
new lur signaling connection is required. The lur signaling
connection
carries
UE-related
RNSAP
signaling.
The Radio Link Setup Request message includes parameters as
below:
Cell ID
TFS
TFCS
Frequency
Uplink Scramble
Cell ID
TFS
TFCS
Frequency
Update type
Cell ID
Downlink scramble
Adjacent cells
Intra-frequency
Model
Measurement
When the UE is in CELL_DCH connection mode (for example, voice talk starts), the RNC
sends the MEASUREMENT CONTROL command to command UE to measure and report
events (the event threshold, hysteresis, delay trigger time are included in signaling). When
the best cell is updated (including occurrence of intra-frequency HHO and inter-frequency
HHO), the measurement control of 1X (including 1A, 1B, 1C, and 1D) event must be
updated.
7.3.4 shows the WCDMA measurement model according to protocol 25.302.
1. Measurement model
In 7.3.4,
= 1/2(k/2). The k is from Filter coefficient, namely, the handover parameter FilterCoef.
FilterCoef is configured in intra-frequency, inter-frequency, and inter-RAT handover
measurement. When is 1 (accordingly k = 0), there is no layer 3 filtering.
From previous measurement model, the filtering occurs before event judgment and
measurement report. In addition, the measured values in cell Measurement
results and Measurement results on RACH of UE's report are filtered. The layer 3 filtering
controlled by network layer caters for measurement event judgment and measurement report
only. The cell reselection when UE is in the idle mode and connection mode does not
support layer 3 filter controlled by network layer.
Intra-frequency
Events
Measurement
In the measurement control message, the UTRAN indicates the events to trigger
measurement report. The intra-frequency measurement report events are marked by "1X".
1. 1A event: a Primary Pilot Channel Is in Reporting Range
In the measurement report mechanism domain, the network requires UE to report the 1A
event (for example, the UE enters the Cell_DCH state), the UE sends the measurement
report when a primary pilot channel enters the reporting range. According to protocols, for 1A
event, the UE can report multiple cells of trigger event in a measurement report. The cells
are included in the list of trigger event. The UE sorts the cells good to bad in terms of quality
(CPICH Ec/No). If less than 3 cells are listed in the active set, the network judges to add
links. If the active set is full of cells, no operation is performed.
When the measured value meets the following formula, the UE judges that a primary pilot
channel is in the reporting range.
The path loss is:
1. Example 1A event
and trigger delay
Usually, if the 1A event is triggered, the UE sends a measure report to UTRAN. The UTRAN
sends an Active Set Update message for updating active set. Probably No response is
received after UE sends measurement report (for example, due to limited capacity). The UE
changes from sending event-triggered report to periodic report. The measure report contains
the information about the cells in the active set and cells in the monitored set in reporting
range. Only when the cell is successfully listed in the active set and leaves the reporting
range will UE stop sending periodic reports.
2. Periodic
report
triggered by 1A event
If more than one links are in the active set, the UE judges to delete
the links.
If only one links is in the active set, the UE performs no operation.
The path loss is:
3. Example of 1C event
In 3, the cells where the PCPICH 1, PCPICH 2, and PCPICH 3 serve are in the active set but
the cell where PCPICH 4 serves is not in the active set. If the cells in the active set reach or
exceeds the replacement threshold of active set, the event is used for replacing bad cells in
the active set.
When the 1C event is triggered, the UE reports the replacing cell and the cell to be replaced
in the event trigger list. The UE also sort the reported cells good to bad in terms of quality
(CPICH Ec/No). After the RNC receives the 1C event trigger list reported by UE, it replaces
the cell to be replaced with the replacing cell in the active set.
4. 1D Event: the Best Cell Changes
4. Example 1D event
When channels have little difference, the 1D event might be triggered due to fluctuating
signals. This leads to unnecessary increase of signaling flow at the air interface. The
hysteresis value helps to avoid this, as shown in 4.
5. Restriction from
hysteresis
to
measurement report
The second time fails to reach the hysteresis condition, so no 1D event report is triggered.
This parameter also applied in other events.
According to protocols, the 1D event can report only one triggered cell which can be in active
set or monitored set. Therefore the cells in the monitored set must be added to the active
set. If the active set is full, the system deletes a cell that is not the best cell. Consequently
the system adds the best cell to the active set. Finally the system marks the cell as the best
cell.
6. Example of 1E event
The 1E event triggers measurement report of the cells not monitored when the UE fails to
receive the neighbor cell table.
6. 1F Event: the Measured Value of Primary Pilot Channel
Is Lower than the Absolute Threshold Value
6 shows an example event.
7. Example of 1F event
The SRNC sends the Radio Link Setup Request message to request
radio
link
setup.
The parameters include target RNC identity, s-RNTI, cell ID, TFS,
and TFCS.
The target RNC allocates RNTI and radio resources for RRC
connection and radio links. In addition, it sends the NBAP message,
namely, the Radio Link Setup Request message to the target NodeB.
The parameters include cell ID, TFS, TFCS, frequency, uplink
scramble, power control, and so on.
The target NodeB allocates radio link resources, starts physical-layer
receiver, and sends the target NodeB the Radio Link Setup Response
message.
The parameters include signaling termination and transport layer
addressing for lub data transmission and bearer.
The target RNC starts setting up lub data transmission and bearer
according to ALCAP protocol. The request contains that the AAL2
bound ID is for binding lub data transmission and bearer, as well as
transport channel DCH. The NodeB confirms the request.
When the target RNC completes preparations, it sends SRNC the
Radio Link Setup Response message.
The SRNC starts setting up lub data transmission and bearer
according to ALCAP protocol. The request contains that the AAL2
bound ID is for binding lub data transmission and bearer, as well as
transport channel DCH. The RNC confirms the request.
The SRNC send UE the Physical Channel Reconfiguration message.
When the UE switches from using the original link to using the new
one, the original NodeB detects that the original link fails in
synchronization. Then the original NodeB sends the NBAP message,
namely, the Radio Link Failure Indication message to the source
RNC.
The SRNC sends the original SRNC the RNSAP message, namely,
the Radio Link Failure Indication.
When the UE completes setting up RRC connection with target RNC
and the related radio resources are allocated, the UE sends SRNC the
RRC message, namely, the Physical Channel Reconfiguration
Complete message.
The SRNC sends source RNC the RNSAP message, the Radio Link
Deletion Request message. This requires the RNC to release the
corresponding resources used by original link.
The source RNC sends original NodeB the NBAP message, the
Radio
Link
Deletion
Request
message.
1. Ordinary
HHO flow
inter-CN
The transmission and bearer at the lur interface is set up at the target
RNC and CN.
or 7) or 8) The target RNC allocates RNTI and radio resources for
RRC connection and radio links, and then sends target NodeB the
NBAP message, the Radio Link Setup Request message. The target
NodeB allocates radio link resources starts physical layer receiver,
and sends target RNC the NBAP message, the Radio Link Setup
Response
message.
The parameters include cell ID, TFS, TFCS, frequency, uplink
scramble, power control, and so on.
or 10) When the RNC completes preparations, the RNC sends CN
the Relocation Required Acknowledge message.
or 12) The CN completes preparations and sends SRNC the
Relocation Command message.
The SRNC sends UE the RRC message, the Physical Channel
Reconfiguration message.
or 15) or 16) When the target RNC detects UE, it sends two nodes of
CN the Relocation Detect message. When the UE switches from
using the original radio link to the new one, the source NodeB sends
source RNC the Radio Link Failure Indication message upon
detection of RL error by source NodeB.
When the UE completes setting up RRC connection with target RNC
and the corresponding radio resources are allocated, it sends target
RNC the RRC message, the Physical Channel Reconfiguration
Complete message.
or 19) After the UE succeeds in handing over to the target RNC and
is allocated with resources, the RNC sends all CNs the Relocation
Complete message.
or 21) The CN sends SRNC the Lu Release Command message.
The lu transmission and bearer between the original RNC and CN is
released.
or 24) The original RNC sends CN the Lu Release Complete
message for confirming release.
Fundamental Concepts
The cell at the carrier coverage edge refers to the cell covered by a carrier in the most
peripheral areas. The cell features that no intra-frequency neighbor cells are present in a
direction of the cell.
The cells in the carrier center area are the rest cells. The cell features that intra-frequency
neighbor cells are present in all directions of the cell.
In the cell at the carrier coverage edge, when the UE moves towards the direction with no
intra-frequency neighbor cells, the CPICH Ec/No fluctuates slowly due to the same
attenuating speed of CPICH RSCP and interference. According to simulation, when the
CPICH RSCP is lower than the demodulation threshold (110 dBm), the CPICH Ec/No can
reach about 12 dB. Now the inter-frequency handover algorithm based on CPICH Ec/No
measurement is invalid. Therefore, using CPICH RSCP as inter-frequency measurement
quantity is more proper and valid for cells at the carrier coverage edge.
The CPICH RSCP might serve as inter-frequency measurement quantity for cells in the
carrier center area, but the CPICH Ec/No is better to reflect the actual communication quality
of links and cell load.
Starting/Stopping
Measurement
Inter-frequency
The inter-frequency measurement might use the compression mode which impacts the link
quality and system capacity, so starting the inter-frequency measurement is not
recommended. The inter-frequency measurement in only recommended if needed. Reporting
2D and 2F events determines starting/stopping inter-frequency measurement on V1.2 RNCs.
When the UE enters the CELL_DCH state or the best cell changes, if the inter-frequency
handover algorithm switch is enabled and the best cell is present in the list of inter-frequency
neighbor cells, the measurement of 2D and 2F events is configured. The absolute threshold
for 2D and 2F events is the staring/stopping inter-frequency measurement. The CPICH
Ec/No or RSCP measurement quantity and threshold is respectively used according to the
position property (as previously mentioned, there are carrier coverage center and carrier
coverage edge) of the best cell in the active set:
Note:
No dedicated control strategy in compression mode is available, so it is
recommended that the inter-frequency handover caters for the compulsory
handover caused by in continuous coverage by carrier. Now you can only
consider starting compression mode at the carrier coverage edge. In the
carrier coverage center, forbid the compression mode from starting by
configuring parameters (set the absolute threshold of 2D event to the
minimum value) and forbid inter-frequency HHO.
By Different Handover
Associated DPCH
Types
on
According to different handover on the associated DPCH in HSDPA network, the HSDPA
handover includes the following types:
of
Cells
for
HSDPA
By location of cells for HSDPA handover, the HSDPA handover includes the following types:
Measurement control
Measurement report
Handover judgment
Handover implementation
New measurement control
The serving cell update of HSDPA subscribers is with DCH handover.
When the serving cell is updated,
At UU interface:
Description
When the HS-PDSCH serving cell is updated due to DPCH SHO, the UE reports the
following events listed in 7.6.4. The system will respond accordingly.
1. Flow of serving
cell
update
triggered
by
different events
in SHO
Event
Action
HS-DSCH
Serving
Cell
Update
(intra-NodeB) upon Fixed Active Set
of UE
7.6.4 shows the intra-NodeB synchronization serving cell update.
1. Intra-NodeB
synchronization
serving cell update
Assume that the parameters like transport channel and radio bearer
are fixed.
The update does not involve MAC layer, so the entity of MAC-hs needs no reconfiguration.
The intra-NodeB synchronization serving cell is updated as below:
UE ID of HS-DSCH
Activation time
UE ID of HS-DSCH
1. Inter-NodeB
synchronization
serving cell update
The update process is based on that the DPCH and active set are fixed.
The inter-NodeB synchronization serving cell is updated as below:
UE ID of HS-DSCH
Activation time
UE ID of HS-DSCH
starts receiving the data from target HS-DSCH cell. It responds the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message to SRNC. The HS-DSCH transport bearer to source NodeB
is released.
The signaling is in the attachment below (the corresponding RNC version is
V100R005C01B061):
1. Inter-NodeB
HSDSCH cell update
after radio link is
added
Setting a newly-added radio link to HS-DSCH radio link involves two steps:
The SRNC decides to add new radio link. The radio link will be the
HS-DSCH link. The SRNC sends DRNC the RADIO LINK
ADDITION REQUEST message. The message indicates DRNC to
set up a radio link without HS-DSCH resource.
The DRNC allocates resources for the new radio link. It sends the
RADIO LINK SETUP REQUEST message to the target NodeB. The
message contains the information to set up DPCH. It indicates the
target NodeB to set up new radio link.
The target NodeB allocates resources. It receives information at the
physical layer of the new DPCH. It responds the RADIO LINK
SETUP RESPONSE message.
The DRNC responds the RADIO LINK SETUP RESPONSE
message to SRNC. The DCH transport bearer is set up.
The SRNC sends UE the ACTIVE SET UPDATE message. The
message contains the new radio link ID.
The UE adds the new radio link to active set, and then responds the
ACTIVE SET UPDATE COMPLETE message to SRNC.
The SRNC sends the RADIO LINK RECONFIGURATION
REQUEST message to DRNC. The message indicates the target HSDSCH cell.
Assume that the target HS-DSCH and source HS-DSCH are
controlled by different NodeBs. The DRNC sends the RADIO LINK
RECONFIGURATION message to source NodeB. The message
indicates NodeB to perform synchronized radio link reconfiguration,
excluding the resource of original HS-DSCH radio link.
The
source
NodeB
responds
the
RADIO
RECONFIGURATION READY message to DRNC.
LINK
RADIO
LINK
UE ID of HS-DSCH
The HS-DSCH transport bearer to target NodeB is set up. The SRNC
sends the RADIO LINK RECONFIGURATION COMMIT message
to DRNC. The message contain the activation time in CFN.
The DRNC sends the RADIO LINK RECONFIGURATION
COMMIT message to the source NodeB and the target NodeB. In the
specified activation time, the source NodeB stops sending HS-DSCH
information to UE, and then the target NodeB starts sending HSDSCH information to the UE.
The
SRNC
sends
the
PHYSICAL
CHANNEL
RECONFIGURATION message to UE. The message contains the
following information:
Activation time
UE ID of HS-DSCH
In the specified time, the UE resets MAC-hs. It stops receiving HSDSCH data from source HS-DSCH cell, and starts receiving HSDSCH data from target HS-DSCH cell. The UE responds the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
message to SRNC. The transport bearer to source NodeB is released.
7.6.5 HS-PDSCH Serving Cell Update due to DPCH HHO
Description
The combination of HHO and HS-PDSCH serving cell update is simple. Namely, they occur
simultaneously.
The intra- and inter-NodeB HHO with serving cell update have the same process. New radio
link is set up in new cell with HS-DSCH. Consequently, the physical channel is reconfigured,
and old link is deleted.
Handover Flow
7.6.5 shows the inter-NodeB HS-DSCH cell update during HHO (single step method).
1. Inter-NodeB
HSDSCH cell update
during HHO (single
step method)
The inter-NodeB HS-DSCH cell during HHO (single step method) is updated as below:
UE ID
The
SRNC
sends
UE
the
PHYSICAL CHANNEL
RECONFIGURATION message. The message contains the
following information:
Activation time
UE ID of HS-DSCH
In the specified time, the UE deletes the current active set, and sets
up DPCH link to target cell, RESET MAC-hs, and after it
synchronize with target cell at the physical layer, it starts receiving
and sending DPCH data, and receiving HS-DSCH data of target cell.
The
UE
responds
the
PHYSICAL
CHANNEL
RECONFIGURATION COMPLETE message to SRNC.
The SRNC sends the RADIO LINK DELETION REQUEST
message to source DRNC. The message indicates the cell to be
deleted.
The target DRNC sends the RADIO LINK DELETION REQUEST
message to source NodeB.
The source NodeB releases original radio link resource, and responds
the RADIO LINK DELETION RESPONSE message to source
DRNC.
The source DRNC responds RADIO LINK DELETION RESPONSE
message to SRNC. The DCH and HS-DSCH transport bearer
resource to source NodeB are released.
7.6.6 DPCH Intra-frequency HHO with HS-DSCH Serving Cell Update
7.6.6 shows the signaling when DPCH intra-frequency HHO with HS-DSCH serving cell
update.
2. DPCH
intrafrequency HHO with
HS-DSCH
serving
cell update
The flows for intra-frequency HHO and HS-PDSCH serving cell update are simple. They
occur simultaneously. After the UE reports 1D event, the physical channel reconfiguration
triggers the HHO of DPCH and HS-DSCH serving cell update.
The following attachment includes the signaling, according to V100R005C01B061).
3. DPCH
interfrequency HHO with
HS-DSCH
serving
cell update
In 7.6.7,
Description
When the UE moves from a HSDPA cell to an R99 cell, the service that is born on HS-DSCH
channel is remapped on DCH to guarantee the continuity of service. The HS-DSCH set in
HSDPA cell is deleted.
7.6.8 shows the handover from HSDPA to R99.
1. handover
HSDPA to R99
from
2. Intra-frequency
handover from R99 to
R5
The strategy for handover between HSDPA and R99 in V17 differs from that in V15 and V16.
If both an R99 cell and a HSDPA cell are available in the active set of the UE, the UE
decides that the service is borne over the HS-DSCH or over the DCH depending on whether
the best cell supports HSDPA or not.
In V17, four scenarios of handover between HSDPA and R99 exist as listed in 7.6.8.
1. Scenarios
of
handover
between
HSDPA
and
R99 (V17)
No
.
Scenario
If the UE moves to an R
cell from a HSDPA cell:
1
A 1B or 1C event occurs a
the new best cell does n
support HSDPA.
A 1B or 1C event occurs a
the new best cell suppo
HSDPA.
4
Intra-frequency
SHO
HSDPA Cell and R99 Cell
Between
7.6.8 shows DPCH SHO with handover from HSDPA to R99 (inter-NodeB).
In 7.6.8, in the handover from R99 to R5 HSDPA, after the UE reports 1A event, it first adds
the RL of HS-PDSCH, and then reconfigures the service born on DCH to HS-PDSCH.
The following attachment contains the previous signaling, according to V100R005C01B061.
3. Inter-NodeB
SHO
with handover from
HSDPA to R99 (V17)
In V17, the signaling flow for SHO from HSDPA to R99 is as follows:
The UE reports a 1A event of the R99 cell (message 18), and the R99 cell is added to the
active set.
The UE reports a 1D event of the R99 cell (message 26), and the R99 changes into the best
cell.
The RNC hands over the UE from the HSDPA cell to the R99 cell (message 34).
In V17, the signaling flow for SHO from R99 to HSDPA is similar to that for SHO from HSDPA
to R99:
The UE reports a 1A event of the HSDPA cell, and the HDSPA cell is added to the active set.
The UE reports a 1D event of the HDSPA cell, and the HSDPA cell changes into the best cell.
The RNC hands over the UE from the R99 cell to the HSDPA cell.
The following attachment contains the signaling for handover from HSDPA to R99, according
to V17C01B060.
1. Intra-frequency HHO
with handover from
R5 to R99
2. Intra-frequency HHO
with handover form
R99 to R5
Intra-frequency HHO occurs on DPCH while the handover from R99 to R5 occurs. The intrafrequency HHO of R99 occurs, and then the service is reconfigured from DCH to HS-PDSCH
in the new HSDPA cell.
The following attachment contains the signaling, according to V100R005C01B061.
3. Intra-frequency HHO
with handover from
R5 to R99 (V17)
In V17, the signaling flow for intra-frequency HHO from HSDPA to R99 is as follows:
The UE reports a 1A event of the R99 cell (messages 18 to 22). The RNC does not perform
any processing because the SHO is not supported.
The UE reports a 1D event of the R99 cell (message 23), and the R99 cell changes into the
best cell.
The RNC hands over the UE from the HSDPA cell to the R99 cell through HHO (line 34).
This step differs from that in the earlier versions. In earlier versions, the RNC re-allocates the
service from HSDPA to R99, and then hands over the service to another R99 cell through
intra-frequency HHO.
The signaling flow for intra-frequency HHO from R99 to HSDPA in V17 is the same as that in
the earlier versions.
The following attachment contains the preceding signaling, according to V17C01B060.
1. Inter-frequency HHO
from HS-PDSCH to
DCH
2. Inter-frequency HHO
from DCH to HSPDSCH
Messages 92121: the UE sends measurement report, and the interfrequency HHO threshold is met. The inter-frequency HHO occurs.
The service is born on HS-DSCH in RB reconfiguration in target
cell, and the inter-frequency HHO from DCH to HS-PDSCH is
complete.
The following attachment contains the signaling, according to V100R005C01B061.
In the signaling flow for inter-frequency HHO from HSDPA to R99 in V17, only the HHO from
a HSDPA cell to an R99 cell differs from that in the earlier version. In earlier versions, the
RNC re-allocates the service from HSDPA to R99, and then hands over the service to
another R99 cell through intra-frequency HHO. In V17, the handover from the HSDPA cell to
the R99 cell completes in one step.
The signaling flow for inter-frequency HHO from R99 to HSDPA in V17 is the same as that in
the earlier versions.
The signaling is to be implemented.
3. Handover
between
HSDPA and GPRS
Inter-frequency
direct retry
HSDPA during setup of a service
of
When the R99 cells and HSDPA cells cover the same geographic area, the system allocates
all data services to the HS-DSCH of HSDPA cells. When the UEs originate to access the
network from R99 or HSDPA cells, it can share the HSDPA resource of HSDPA cells
however it is an R99 UE or a HSDPA UE. Thus, it can use resource better.
Inter-frequency
direct
triggered by 4A events
retry
When an R99 cell and a HSDPA cell cover the same geographic area, the system allocates
the data traffic to the HS-DSCH of the HSDPA cell through direct retry if a 4A event occurs
due to increase of data traffic of the UE in the R99 cell.
In this case, the R99 cell shares HSDPA resources with the HSDPA cell. Thus, the resources
are better used.
In V17, the following types of inter-frequency direct retry of HSDPA are available:
Scenario 1
An R99 cell overlaps with an inter-frequency R5 cell with the same coverage. If the
UE that supports HSDPA originates a request for setup of a service that is fit for
HSDPA in the R99 cell, the service is sent to the R5 cell through direct retry during
RAB setup.
Scenario 2
An R5 cell has an inter-frequency R99 cell with the same coverage.
If the UE that supports HSDPA originates a request for setup of a service that HSDPA
cannot bear in the R5 cell, or the UE that does not support HSDPA originates a request
for setup of a service on HSDPA in the R5 cell, the request is sent to the R99 cell
through direct retry during RAB setup.
The service setup here must be the first service setup of the UE or the
existing services are over the FACH. Thus, the new service does not impact
the existing services.
Inter-frequency direct retry in the case admission rejection
Suppose an R5 has an inter-frequency R5 cell with the same coverage. The UE that
supports HSDPA originates a request for setup of a service that is fit for HSDPA or
originates an RAB reconfiguration request (channel type) in an R5 cell. If the request is
rejected by the local cell, the request is sent to the other R5 cell through an interfrequency direct retry.
The current service that is fit for the HS-DSCH is over the DCH for some reason (such as
admission rejection), the UE supports HSDPA but the best cell does not. An interfrequency R5 cell with the same coverage is available. In this case, the system reallocates the service from the DCH to the HS-DSCH in the inter-frequency R5 cell with
the same coverage if the data traffic of the UE increases (the RNC receives a 4A event
measurement report).
the
timer,
run
the
command
SET
2. Switch
type
of
channel
Whereas, the data service is more active (the network receives the 4a event of service
measurement quantity), the UE is triggered to switch from CELL_FACH state to HS-DSCH.
The attachment below contains the signaling.
Scenario 2: A 4A event triggers D2H switch between two cells at different frequencies but
with the same coverage. See 7.6.10.
In V17, the switch between HS-DSCH and DCH might occur in any of the following cases:
Scenario 2: A 4A event triggers D2H switch between two cells at different frequencies but
with the same coverage. See 7.6.10.
If the rate of service on the current DCH equals to 384 Kbps, no 4A event
occurs. In this case, a timer is needed to trigger the D2H switch.
Scenario 2: The timer triggers D2H switch in the case of inter-frequency direct retry. See
7.6.10.
To set the expiry time of the
COIFTIMER:HRetryTimerLen=5000;.
timer,
run
the
command
SET
The following attachment contains signaling in the case that the timer triggers D2H switch in
a cell, according to V17C01B060:
HSUPA link: Each UE can have only one HSUPA link with the
network. Different from the HSDPA, the HSUPA supports SHO. The
HSUPA handover requires management of the HSUPA serving cell.
DPCH link: The handover functions supported by the DPCH link are
the same as those supported by the R99 system, including SHO,
HHO, and handover between systems
HSUPA Serving Cell
The E-DCH active set has three types of RL:
If all cells in the active set support the HSUPA, the E-DCH bears the
uplink services. In other cases, the DCH bears the uplink services.
If all cells in the active set belong to the SRNC, the E-DCH bears the
uplink services. In other cases, the DCH bears the uplink services
(The lur interface in phase 1 of the product does not support the
HSUPA).
For these reasons, if a new cell added to the active set does not support the HSUPA or the
new cell belongs to the DRNC, the channel type changes from the E-DCH to the DCH. In
some cases, the channel type changes from the the DCH to the E-DCH.
1. Handover
between
two
HSUPA cells
No
.
Scenario
No
.
Scenario
1. Intra-frequency SHO
between two HSUPA
cells
If the monitor set reports a 1D event, the HSUPA serving cell also is updated. For example,
the service is over the E-DCH in HSUPA 1 that works as the serving cell. The signals of
HSUPA 2 in the monitor set become stronger. In this case, the UE reports a 1D event and
the RNC adds HSUPA 2 to the active set. At last, the RNC updates the serving cell is
updated by re-configuring the physical channel. 7.7.3 shows the related signaling:
1. Intra-frequency HHO
between two HSUPA
cells
the compression mode and performs inter-frequency measurement. If the target cell meets
the handover requirements and the E-DCH allows the service setup, the RNC allocates the
UE from Cell 1 to Cell 2 by re-configuring the physical channel and sets up the HSUPA link of
the UE on the E-DCH of Cell 2.
1. Inter-frequency HHO
between two HSUPA
cells
1. Inter-RNC
handover
HSUPA
1. Handover
between
a
HSUPA
cell
and a nonHSUPA cell
No
.
Scenario
Rules
3. Addition of an R99
cell when the service
is on the E-DCH
1. Intra-frequency HHO
from a HSUPA cell to
a non-HSUPA cell
requirements, the RNC hands over the UE from Cell 1 to Cell 2 (HHO) through RB
reconfiguration.
1. Inter-frequency HHO
from a HSUPA cell to
a non-HSUPA cell
1. Intra-frequency HHO
from a non-HSUPA
cell to a HSUPA cell
1. Inter-frequency HHO
from a non-HSUPA
cell to a HSUPA cell
In the R99 cell, the UE originates a service that is fit for the E-DCH.
The traffic of the UE that is over the FACH in the R99 cell increases
and the service is fit for the E-DCH.
A service that should have been set up over the E-DCH according to
the service mapping rules is over the DCH of the R99 cell. The
system periodically checks the services that conflict with the bearer
policy and attempts to retry the services to the E-DCH.
The system periodic measurement uses the HSDPA retry timer (ms). The related MML
is SET COIFTIMER.
timer expires, the system checks whether the current bearer mode conflicts with the bearer
policy. If a conflict exists, the system triggers switch between channel types.
Traffic triggers switch between the CELL_DCH (E-DCH) and the CELL_FACH. Measurement
reports (4A) sent by the UE trigger switch from the CELL_FACH to the CELL_DCH. The
internal measurement of the RNC triggers switch from the CELL_DCH(E-DCH) and the
CELL_FACH (According to the current protocol, the UE measurement report does not
support measurement of the E-DCH).
2. Switch
between
HSUPA channel types
>
measurement
report
>
handover
judgment
>
handover
2. Tracing signaling of
handover
from
WCDMA to GSM
1. Signaling
flow
for handover
from
GSM to WCDMA
2. Tracing signaling of
handover from GSM
to WCDMA
The UE listens to the system information of UTRAN and obtain the parameter configuration
according to template number.
Pre-configuration (default): The protocol 25.331 provides 10 sets of default parameters and
specifies an identity to each default parameter. The RNC configures the default identity and
other necessary information to UE.
Handover
form
The inter-RAT handover from WCDMA to GRPS caters for the handover from WCDMA PS
domain service to GPRS system. The RNC initiatively commands UE to reselect an interRAT cell with signaling, which triggers inter-RAT handover. If the traffic flow for slow-speed
PS services, the UE might be in CELL PCH or URA PCH state, the UE can perform interRAT handover by initiatively originating cell reselection according to system information.
1. Flow of handover
from WCDMA to
GPRS (1)
2. Flow of handover
from WCDMA to
GPRS (2)
3. Tracing signaling of
handover
from
WCDMA to GPRS
If restoring the PDP context is not required, the RNC directly receives the IU RELEASE
COMMAND at the IU interface.
If restoring the PDP context is required, the UE obtains the SRNS CONTEXT information
from the source RNC. The source RNC will receive the SRNS CONTEXT REQUEST
message with mainly an RAB ID.
1. Signaling
flow
for handover
from
GPRS to WCDMA (1)
2. Signaling
flow
for handover
from
GPRS to WCDMA (2)
1. Parameters of
handover from
3G to 2G
P
a
r
a
m
e
t
e
r
M
e
a
n
i
n
g
Default
configuratio
n
FilterCoef
Filter
coefficient at
layer 3 of
inter-RAT
measurement
D3
GsmRSSICSThd
,
GsmRSSIPSThd,
GsmRSSISIGTh
d
The judgment
threshold for
inter-RAT
handover
HystThd
Inter-RAT
handover
4, namely, 2 dB
M
M
L
C
o
m
m
a
n
d
s
f
o
r
m
o
d
if
y
i
n
g
a
n
d
q
u
e
r
y
i
n
g
For RNCs: interRAT handover
algorithm
parameter:
set
RNCs
by
executing SET
INTERRATHO,
query RNCs by
executing LST
INTERRATHO.
For cells: interRAT handover
algorithm
parameter: add
cells
by
executing ADD
A
p
p
l
i
c
a
t
i
o
n
s
c
o
p
e
RNC/Cell
hysteresis
TimeToTrigForV
erify
The time to
trigger delay
verified
by
inter-RAT
0, namely, 0s
TimeToTrigForN
onVerify
Non-verified
delay trigger
time
PenaltyTimeForS
ysHo
Inter-RAT
handover
penalty time
InterRatCSThdF
or2DRSCP,
InterRatPSThdFo
r2DRSCP,
InterRatSigThdF
or2DRSCP,
InterRatCSThdF
or2FRSCP,
InterRatPSThdFo
r2FRSCP,
InterRatSigThdF
or2FRSCP
The
starting/stoppi
ng threshold
for inter-RAT
measurement
with RSCP as
the
measurement
value (CS, PS,
and
single
signaling)
InterRATCSThd
FOR2DEcNo,
InterRATPSThdF
OR2DEcNo,
InterRATSigThd
FOR2DEcNo ,
InterRATCSThd
For2FEcNo,
InterRATPSThdF
OR2FEcNo,
InterRATSigThd
FOR2FEcNo
The
starting/stoppi
ng threshold
for inter-RAT
measurement
with Ec/No as
the
measurement
value (CS, PS,
and
single
signaling)
HYSTTHD
Hysteresis.
The hysteresis
and inter-RAT
quality
threshold
decides
whether
to
trigger interRAT handover
judgment.
It
can be smaller
CELLINTERRA
THO, query cells
by
executing
LST
CELLINTERRA
THO,
and
modify cells by
executing MOD
CELLINTERRA
For RNCs: set
RNCs
by
executing SET
INTERFREQHO
and query RNCs
by
executing
LST
INTERFREQHO
.
For cells: add
cells
by
executing ADD
CELLINTERFR
EQHO,
query
cells
by
executing LST
CELLINTERFR
EQHO,
and
modify cells by
executing MOD
CELLINTERFR
EQHO
RNC/Cell
in areas with
small shadow
fading. It can
be greater in
areas
with
great shadow
fading.
CellIndividalOffs
et
The individual
offset of interRAT handover
cells. The UE
uses it with the
initial
measured
value of the
cell as the
measurement
result
for
handover
judgment
of
UE.
Set cells by
executing ADD
INTERRATNCE
LL, query cells
by
executing
LST
INTERRATNCE
LL, and modify
it by executing
MOD
INTERRATNCE
LL
Cell
Note:
7.12 lists the starting/stopping threshold of compression mode and interRAT handover threshold in terms of signaling, CS, and PS.
The new protocol CR defines that the UE will not report the not verified
GSM measurement.
7.13 shows the data configuration of target 3G cell in the location area cell table.
1. Data configuration in
the location area cell
table
GCI code
GCI code
Neighbor cells
Fill from the neighbor cell 1 to the neighbor 2. The content to be filled in the neighbor cell
1 is the LAI + RNC ID of target 3G cell for handover. Query the LAI of target 3G cell by
running the command LST AC. Query the RNC ID by running the command LST
RNCBASIC.
Add data of WCDMA cells, including downlink frequency, primary scramble, diversity
indicator, MCC, MNC, LAC, RNC ID, and CELL ID.
Add the information about inter-RAT cell measurement and roaming control in the idle mode.
The information contains the following parameters:
Qsearch_I: the level threshold for searching for 2G cells in the idle mode
FDD_Qoffset: the level offset of 3G cell reselection
FDD_Qmin: the level threshold of 3G cell reselection
The previous information contained in the system information 2ter and 2quater is sent to UE.
Primary scramble
Diversity indicator
MCC
MNC
LAC
RNC ID
CELL ID
1. Configuration table
for external 3G cells
Pay attention to several fields: MCC, MNC, LAI, RNC ID, CELL ID, downlink
frequency point, and scramble. Using system defaults is recommended for unlisted fields.
MCC: query it by running the command LST RNCBASIC on the corresponding RNC client
MNC: query it by running the command LST RNCBASIC on the corresponding RNC client
LAI: query it by running the command LST AC on the corresponding RNC client
RNC ID: query it by running the command LST RNCBASIC on the corresponding RNC
client
CELL ID: query it by running the command LST CELL on the corresponding RNC client
Note:
The query result is decimal. It can be filled in the CELL ID field after it is
converted to hex and removed of the highest bit.
Downlink frequency point: query it by running the command LST CELL on the
corresponding RNC client and then inputting the corresponding CELL ID in the CELL
Scramble: query it by running the command LST CELL on the corresponding RNC client
and then inputting the corresponding CELL ID in the CELL
2. Configuration table
for
GSM inter-RAT
neighbor cells
Note:
The target cell for handover from the 3G network can be the directional
neighbor cell of GSM only.
3. Configuration table
for 2G reselection
parameters
The configuration table for 3G system information includes the following parameters:
Threshold for searching for 3G cells in the idle mode: the values range from 0 to 15
Offset of FDD cell reselection: When the mean receiver level of 3G cells is FDD_Qoffset
greater than that of the serving cell, the UE can reselect 3G cells. 0 = (always select a cell
if acceptable), 1 = 28 dB, 2 = 24 dB, , 15 = 28 dB. Select 0 for easy handover.
The minimum Ec/No threshold for FDD cell reselect: level threshold for 3G cell reselection:
when the receiver level of 3G cell is greater than the FDD_Qmin, the cell can be a candidate
cell for reselection.
4. Parameter
configuration
for inter-RAT
handover
table
2G/3G cell handover priority selection: select 3G cell for handover as priority
2G cell selection threshold: the greater the threshold is, the difficult the handover to 2G is.
The recommended value is 63.
RSCP threshold for handover to a better 3G cell: the smaller the value is, the difficult the
handover to 3G is. The recommended value is 10.
Ec/No threshold for handover to a better 3G cell: the smaller the value is, the difficult the
handover to 3G is. The recommended value is 10.
Statistics time for a better 3G cell: the recommended value is 5.
The lasting time for handover to a better 3G cell: the smaller the value is, the easier and
faster the handover is. Pay attention to frequent handover. The recommended value is 4.
Add the cell information about location area near the 2G MSC to the list of cells of 3G MSC
location area. LAI = MCC + MISSING NEIGHBOR CELL + LAC. Select LAI as the type of
location area. Select Near VLR area as the property of location area. Add the corresponding
2G MSC/VLR code. GCI = MCC + MNC + LAC + CI. Select GCI as the type of location
area. Select Near VLR area as the property of location area. Add the corresponding 2G
MSC/VLR code.
If inter-PLMN cell reselection is necessary, the MSC must configure the equivalent PLMN
list: ADD EPLMN, and add the inter-PLMN MCC and MNC. The equivalent PLMN is the
PLMN which provides equivalent services to subscribers. The network side decides whether
to tell the control list to UE. The MSC sends the list to UE upon update acceptance and the
UE saves it. When the UE reselects an inter-PLMN cell, it reselects a cell from the list by
priority.
Configure the data at MTP layer and guarantee the signaling transmission between the 2G
MSC and the 3G MSC.
Configure the data at SCCP layer. Configure the corresponding record of 2G MSC in the GT
table, SCCP SSN table, and SCCP DSP table.
Configure the trunk data between MSCs in the same way as configuring common data.
Configure the measurement point for FACH to inter-frequency FDD measurement, interfrequency TDD measurement, or inter-RAT measurement. If inter-RAT roaming is necessary,
configure the measurement point for FACH to inter-RAT measurement; otherwise, according
to SIB11, the RNC will not send RNC information about GSM neighbor cells.
MOD CELLMEAS: CELLID=123, INTERFREQINTERRATMEASIND=INTER_RAT,
FACHMEASIND=REQUIRE, FACHMEASOCCACYCLELENCOEF=3;
Configure the SearchRAT of the GSM network by running the command MOD
CELLSELRESEL.
After configuration of these information, the SsearchRAT contained in SIB3 is sent and
information about GSM neighbor cells contained in SIB11 are sent.
2011-04-11