Professional Documents
Culture Documents
W-Handover and Call Drop Problem Optimization Guide: Huawei Technologies Co., Ltd. All Rights Reserved
W-Handover and Call Drop Problem Optimization Guide: Huawei Technologies Co., Ltd. All Rights Reserved
Revision Records
Date Version Description Author
Cai Jianyong,
Completing V2.0 W-Handover and Call Drop
2005-02-01 2.0 Zang Liang, and
Problems.
Jiao Anqiang
According to V3.0 guide requirements, Jiao Anqiang
reorganizing and updating V2.0 guide, focusing
more on operability of on-site engineers. All traffic
statistics is from RNC V1.5. The update includes:
Updating flow chart for handover problem
optimization
Moving part of call drop due to handover problem
to handover optimization part
Specifying operation-related part to be more
applicable to on-site engineers
2006-03-16 3.0
Updating RNC traffic statistics indexes to V1.5
Integrating traffic statistics analysis to NASTAR of
the network performance analysis
Optimizing some cases, adding new cases, and
removing outdated cases and terms
Moving content about handover and call drop to the
appendix, and keeping operations related to them in
the body
Adding explanations to SRB&TRB and RL
FAILURE.
2006-04-30 Adding HSDPA-related description HSDPA Zhang Hao and
handover DT/CQT flow, definitions of traffic Li Zhen
3.1 statistics in HSDPA handover, HSDPA handover
problems. Adding algorithms and flows of HSDPA
handover.
Contents
1 Introduction ............................................................................................................................. 14
2 Handover and Call Drop Performance Indexes ...................................................................... 16
2.1 Handover Performance Indexes ...................................................................................... 16
2.2 Call Drop Performance Indexes ....................................................................................... 19
3 Handover Index Optimization ................................................................................................. 20
3.1 DT/CQT Index Optimization Flow..................................................................................... 20
3.1.1 SHO DT Index Optimization Flow........................................................................... 20
3.1.2 HHO CQT Flow ..................................................................................................... 24
3.1.3 Inter-RAT Handover CQT Flow .............................................................................. 27
3.1.4 DT/CQT Flow for HSDPA Handover ...................................................................... 29
3.1.5 DT/CQT Flow for HSUPA Handover ...................................................................... 32
3.1.6 SHO Ratio Optimization ......................................................................................... 32
3.1.7 MBMS Mobility Optimization .................................................................................. 32
3.2 Traffic Statistics Analysis Flow ......................................................................................... 34
3.2.1 Analysis Flow for SHO Traffic Statistics ................................................................. 35
3.2.2 Analysis Flow of HHO Traffic statistics ................................................................... 36
3.2.3 Traffic Statistics Analysis Flow for Inter-RAT Handover .......................................... 37
3.2.4 Traffic Statistics Analysis for HSDPA Handover ..................................................... 40
3.2.5 Traffic Statistics Analysis for HSUPA Handover ..................................................... 41
3.3 SHO Cost Optimization.................................................................................................... 43
4 CDR Index Optimization .......................................................................................................... 44
4.1 Definition of Call Drop and Traffic Statistics Indexes ........................................................ 44
4.1.1 Definition of DT Call Drop ...................................................................................... 44
4.1.2 Descriptions of Traffic Statistics Indexes ................................................................ 44
4.2 DT/CQT Optimization Flow .............................................................................................. 45
4.2.1 Call Drop Cause Analysis ...................................................................................... 46
4.2.2 Frequently-adjusted Non-handover Algorithm Parameters...................................... 48
4.2.3 Judgment Tree for Call Drop Causes ..................................................................... 49
4.3 Traffic Statistics Analysis Flow ......................................................................................... 50
4.3.1 Analyzing RNC CDR.............................................................................................. 51
4.3.2 Analyzing Causes to Call Drop............................................................................... 51
4.3.3 Check Cells ........................................................................................................... 52
4.3.4 Further DT for Relocating Problems ....................................................................... 52
4.4 Optimization Flow for Tracing Data .................................................................................. 52
4.4.1 Obtaining Single Subscriber Tracing Message ....................................................... 53
4.4.2 Obtaining Information about Call Drop Point .......................................................... 53
4.4.3 Analyzing Call Drop due to SRB Reset .................................................................. 54
4.4.4 Analyzing Call Drop due to TRB Reset................................................................... 54
4.4.5 Analyzing Abnormal Call Drop ............................................................................... 54
4.4.6 Performing CQT to Recheck Problems .................................................................. 55
Figures
Figure 7-14 Ordinary HHO flow (lur interface and CELL_DCH state) ................................................ 124
Figure 7-15 Ordinary inter-CN HHO flow .......................................................................................... 126
Figure 7-16 Intra-NodeB synchronization serving cell update............................................................ 133
Figure 7-17 Inter-NodeB synchronization serving cell update............................................................ 135
Figure 7-18 Inter-NodeB HS-DSCH cell update after radio link is added ........................................... 137
Figure 7-19 Inter-NodeB HS-DSCH cell update during HHO (single step method) ............................ 139
Figure 7-20 DPCH intra-frequency HHO with HS-DSCH serving cell update ..................................... 141
Figure 7-21 DPCH inter-frequency HHO with HS-DSCH serving cell update ..................................... 142
Figure 7-22 handover from HSDPA to R99 ....................................................................................... 143
Figure 7-23 Intra-frequency handover from R99 to R5 ...................................................................... 143
Figure 7-24 DPCH SHO with handover from HSDPA to R99 (inter-NodeB) ....................................... 145
Figure 7-25 DPCH SHO with handover from R99 to HSDPA............................................................. 146
Figure 7-26 Inter-NodeB SHO with handover from HSDPA to R99 (V17) .......................................... 147
Figure 7-27 Intra-frequency HHO with handover from R5 to R99 ...................................................... 148
Figure 7-28 Intra-frequency HHO with handover form R99 to R5 ...................................................... 148
Figure 7-29 Intra-frequency HHO with handover from R5 to R99 (V17)............................................. 149
Figure 7-30 Inter-frequency HHO from HS-PDSCH to DCH .............................................................. 150
Figure 7-31 Inter-frequency HHO from DCH to HS-PDSCH .............................................................. 151
Figure 7-32 Handover between HSDPA and GPRS .......................................................................... 152
Figure 7-33 Flow for direct retry during setup of a service ................................................................. 153
Figure 7-34 Direct retry triggered by traffic........................................................................................ 153
Figure 7-35 Switch of channel type................................................................................................... 155
Figure 7-36 Intra-frequency SHO between two HSUPA cells............................................................. 159
Figure 7-37 Signaling for HSUPA cell update triggered by a 1D event ............................................... 159
Figure 7-38 Signaling for HSUPA cell update triggered by a 1D event (reported by the monitor set) .. 160
Figure 7-39 Intra-frequency HHO between two HSUPA cells ............................................................ 160
Figure 7-40 Signaling for intra-frequency HHO between two HSUPA cells ........................................ 161
Figure 7-41 Inter-frequency HHO between two HSUPA cells ............................................................ 161
Figure 7-42 Signaling for inter-frequency HHO between two HSUPA cells ........................................ 162
Figure 7-43 Inter-RNC HSUPA handover .......................................................................................... 163
Figure 7-44 SHO from a HSUPA cell to a non-HSUPA cell ................................................................ 165
Figure 7-45 Addition of an R99 cell when the service is on the E-DCH.............................................. 166
Figure 7-46 Intra-frequency HHO from a HSUPA cell to a non-HSUPA cell ....................................... 167
Figure 7-47 Signaling for intra-frequency HHO from a HSUPA cell to a non-HSUPA cell ................... 167
Figure 7-48 Inter-frequency HHO from a HSUPA cell to a non-HSUPA cell ....................................... 168
Figure 7-49 Signaling for inter-frequency HHO from a HSUPA cell to a non-HSUPA cell ................... 169
Figure 7-50 SHO from a non-HSUPA cell to a HSUPA cell ................................................................ 170
Figure 7-51 SHO from a non-HSUPA cell to a HSUPA cell (triggered by a 1B event) ......................... 170
Figure 7-52 Intra-frequency HHO from a non-HSUPA cell to a HSUPA cell ....................................... 171
Figure 7-53 Signaling for intra-frequency HHO from a non-HSUPA cell to a HSUPA cell ................... 171
Figure 7-54 Inter-frequency HHO from a non-HSUPA cell to a HSUPA cell ....................................... 172
Figure 7-55 Direct retry from an R99 cell to a HSUPA cell................................................................. 173
Figure 7-56 Direct retry from a HSUPA cell to an R99 cell................................................................. 173
Figure 7-57 Direct retry from a HSUPA cell to another HSUPA cell.................................................... 174
Figure 7-58 Switch between HSUPA channel types .......................................................................... 174
Figure 7-59 Signaling flow for handover from WCDMA to GSM......................................................... 176
Figure 7-60 Tracing signaling of handover from WCDMA to GSM ..................................................... 176
Figure 7-61 Signaling flow for handover from GSM to WCDMA ........................................................ 179
Figure 7-62 Tracing signaling of handover from GSM to WCDMA ..................................................... 180
Figure 7-63 Flow of handover from WCDMA to GPRS (1)................................................................. 183
Figure 7-64 Flow of handover from WCDMA to GPRS (2)................................................................. 183
Figure 7-65 Tracing signaling of handover from WCDMA to GPRS ................................................... 184
Figure 7-66 Signaling flow for handover from GPRS to WCDMA (1) ................................................. 186
Figure 7-67 Signaling flow for handover from GPRS to WCDMA (2) ................................................. 187
Figure 7-68 Data configuration in the location area cell table ............................................................ 193
Figure 7-69 Data configuration of neighbor cell configuration table ................................................... 194
Figure 7-70 Configuration table for external 3G cells ........................................................................ 196
Figure 7-71 Configuration table for GSM inter-RAT neighbor cells .................................................... 197
Figure 7-72 Configuration table for 2G reselection parameters ......................................................... 198
Figure 7-73 Parameter configuration table for inter-RAT handover .................................................... 199
Tables
Key words:
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.
CN Core Network
O&M Operation and maintenance
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:
The traffic statistics analysis is based on RNC V1.5 counter. It will be updated upon the update
of RNC counters.
VP DT&Stat. 85%
Intra-frequency HHO
PS UL64K/DL 64K DT&Stat. 85%
success rate
PS UL64K/DL 144K DT&Stat. 80%
PS UL64K/DL 384K DT&Stat. 75%
Voice DT&Stat. 92%
VP DT&Stat. 90%
Inter-frequency HHO
PS UL64K/DL 64K DT&Stat. 90%
success rate
PS UL64K/DL 144K DT&Stat. 87%
PS UL64K/DL 384K DT&Stat. 85%
Table 2-2 lists the HSDPA handover performance indexes and reference value.
HSDPA-HSDPA intra-frequency
PS (HSDPA) 99%
serving cell update
HSDPA-HSDPA inter-frequency
PS (HSDPA) 92%
serving cell update
Note: The HSDPA handover KPIs are to be updated after formal issue by WCDMA&GSM Performance
Research Department.
Success rate of –
DCH-to-E-DCH
reconfiguration in single-link
mode (the second step of PS (HSUPA)
inter- or intra-frequency
HHO from a non-HSUPA
cell to a HSUPA cell)
Note:
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
Voice DT&Stat.&CQT 2%
VP DT&Stat.&CQT 2.5%
PS planned full
DT&CQT 3%
coverage rate
PS Stat. 10%
PS (UL HSUPA/DL
DT 3%
HSDPA)
The values listed in Table 2-4 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.
Pilot Pollution
Pilot pollution is defined as below:
l Excessive strong pilots exist at a point, but no one is strong enough to be primary
pilot.
According to the definition, when setting rules for judging pilot pollution, confirm the following
content:
l 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
CPICH _ RSCP > ThRSCP _ Absolute
strong pilot. Namely, .
l 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
CPICH _ Number > ThN
are excessive. Namely,
l 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
(Th + 1)
N
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:
Set ThRSCP _ Absolute = −95dBm , Th N = 3 , and ThRSCP _ Re lative = 5dB , the judgment standards
for pilot pollution are:
l The number of pilots satisfying CPICH _ RSCP > −95dBm is larger than 3.
l 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.
l Ping-pong Handover
Ping-pong handover includes the following two forms
− 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.
l For call drop caused by delayed handover, adjust antennas to expand the handover
area, set the handover parameters of 1a event, or increase CIO to enable handover
to occur in advance. The sum of CIO and measured value is used in event
evaluation process. The sum of initially measured value and CIP, as measurement
result, is used to judge intra-frequency handover of UE and acts as cell border in
handover algorithm. The larger the parameter is, the easier the SHO is and UEs in
SHO state increases, which consumes resources. If the parameter is small, the SHO
is more difficult, which might affects receiving quality.
l For needle effect or turning corner effect, setting CIO to 5 dB is proper, but this
increases handover ratio. For detailed adjustment, see SHO-caused call drop of
FAQs Analysis.
l For call drop caused by Ping-pong handover, adjust the antenna to form a best
server or reduce Ping-pong handover by setting the handover parameter of 1B event,
which enables deleting a cell in active set to be more difficult. For details, increase
the 1B event threshold, 1B hysteresis, and 1B delay trigger time.
HHO Types
HHO includes the following types:
l 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
intra-frequency 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.
l 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.
l Balanced load HHO
It aims to realize balanced load of different frequencies. Its judgment depends on
balanced load HHO.
Inter-frequency coverage usually exists in special scenarios, such as indoor coverage, so CQT
are used. The following section details the optimization flow for inter-frequency CQT.
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:
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.
l Increase the CIO of two inter-frequency cells.
Flow Chat
Figure 3-3 shows the inter-RAT handover CQT flow.
Data Configuration
Inter-RAT handover fails due to incomplete configuration data, so pay attention to the following
data configuration.
l GSM neighbor configuration is complete on RNC. The configuration includes:
− Mobile country code (MCC)
− Mobile network code (MNC)
− Location area code (LAC)
− GSM cell identity (CELL ID)
− Network color code (NCC)
− Base station color code (BCC)
− Frequency band indicator (FREQ_BAND)
− Frequency number
− Cell independent offset (CIO)
Guarantee the correctness of the previous data and GSM network.
l 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.
l Add data of WCDMA neighbor cells on GSM BSS. The data includes:
− Downlink frequency
− Primary scramble
− Main indicator
− MCC
− MISSING NEIGHBOR CELL
− LAC
− RNC ID
− CELL ID
According to the strategies of unilateral handover of inter-RAT handover, if the data
configuration is complete, the inter-RAT handover problems are due to delayed handover. A
frequently-used solution is increasing CIO, increasing the threshold for starting and stopping
compression mode, increasing the threshold to hand over to GSM.
Causes
The causes to call drop due to 3G-2G inter-RAT handover are as below:
l After the 2G network modifies its configuration data, it does not inform the 3G
network of modification, so the data configured in two networks are inconsistent.
l Missing neighbor cell causes call drop.
Type
According to the difference of handover on DPCH in HSDPA network, the HSDPA handover
includes:
l SHO or softer handover of DPCH, with HS-PDSCH serving cell update
Methods
For HSDPA service coverage test and mobility-related test (such as HHO on DPCH with
HS-PDSCH serving cell update, handover between HSDPA and R99, and inter-RAT handover),
perform DT to know the network conditions.
For location of HSDPA problems and non-mobility problems, perform CQT (in specified point or
small area).
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).
Figure 3-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:
l Whether the HSDPA function of target cell is enabled and the parameters are
correctly configured. Engineers mainly check the words of cell and whether the
power is adequate, whether the HS-SCCH power is low. These parameters might
not directly cause call drop in handover, but lead to abnormal handover and lowered
the user experience.
l Whether the protection time length of HSDPA handover is proper. Now the baseline
value is 0s. Set it by running SET HOCOMM.
l Whether the threshold for R99 handover is proper. The handover flow for HSDPA is
greatly different from that of R99, so the handover of R99 service may succeed while
the HSDPA handover may fail. For example, in H2D handover, when the UE reports
1b event, it triggers RB reconfiguration in the original cell, reconfigures service
bearer to DCH, and updates the cell in active set. If the signals of the original cell
deteriorate quickly now, the reconfiguration fails.
l Whether the protection time length of D2H handover is proper. Now the baseline
value is 2s. Set it by running SET HOCOMM.
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:
l Optimize cell reselection parameters to guarantee that the UE can be reselected to
the best cell in time.
l Guarantee that the power of the FACH in each cell is large enough to meet the
coverage requirement of the MBMS UE at the edge of the cells.
l Guarantee that the transmission time difference of the UE between different links
meets the requirement of soft combing or selective combining*.
l Guarantee that the power, codes, transmission, and CE resources of the target cell
are not restricted or faulty, and that the MBMS service is successfully established.
The UE can simultaneously receive the same MBMS service from two PTM cells and combine
the received MBMS service. The UE supports two combining modes:
Soft combining: The transmission time difference between the current cell and the neighboring
cell is within (one TTI + 1) timeslots and the TFCI in each transmission time interval (TTI) is the
same.
Selective combining: The transmission time difference between the current cell and the
neighboring cell is within the reception time window stipulated by the radio link controller (RLC).
The SCCPCH is decoded and the transmission blocks are combined in the RLC PDU phase
The UE feeds back that the SHO (or softer handover) for RNC to add/delete
Synchronization
links is incompatible with other subsequent processes. The RNC
reconfiguration
guarantees serial processing upon flow processing. This cause is due to the
nonsupport
problematic UE.
The UE thinks the content of active set update for RNC to add/delete links is
Invalid configuration
invalid. This scenario seldom exists in commercial networks.
The RNC fails to receive response to active set update command for
adding/deleting links. This is a major cause to SHO (or softer handover)
No response from UE
failure. It occurs in areas with weak coverage and small handover area. RF
optimization must be performed in the areas.
l Perform DT to re-analyze problems. The traffic statistics data provides the trend and
possible problems. Further location and analysis of problems involves DT and CHR
to the cell. DT is usually performed on problematic cells and signaling flow at the UE
side and of RNC is traced. For details, see 3.1.3 .
Configuration The UE thinks it cannot support the command for outgoing HHO,
nonsupport because it is incompatible with HHO.
PCH failure The cause is probably weak coverage and strong interference.
Synchronization
The UE feeds back HHO is incompatible with other consequent processes
reconfiguration
due to compatibility problems of UE.
nonsupport
Cell update occurs upon outgoing HHO. These two processes lead to
Cell update
outgoing HHO failure.
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 Table 3-3.
SRNS relocation It corresponds to incorrect configuration of CN, so you must analyze the
expiration causes according to CN and BSS signaling tracing.
SRNS relocation
It corresponds to incorrect configuration of CN or BSS nonsupport, so you
failure in target
must analyze the causes according to CN and BSS signaling tracing.
CN/RNC/system
Other causes Analyze the causes according to CN and BSS signaling tracing.
SRNS relocation
It corresponds to incorrect configuration of CN or BSS nonsupport, so you
failure in target
must analyze the causes according to CN and BSS signaling tracing.
CN/RNC/system
SRNS relocation
The BSC fails to support some parameters of inter-RAT handover request,
nonsupport in
so you must analyze the causes according to CN and BSS signaling
target
tracing.
CN/RNC/system
Other causes Analyze the causes according to CN and BSS signaling tracing.
Analyze the problem further according to CHR logs and CN/BSS signaling
Other causes
tracing.
Transport layer
The corresponding transport link is abnormal.
cause
Other causes You must analyze the causes according to CN and BSS signaling tracing.
l The RRC Release message with the release cause Not Normal.
l Any of the CC Disconnect, CC Release Complete, CC Release message with the
release cause Not Normal Clearing, Not Normal, or Unspecified.
l After the service is set up, the RNC sends CN the RAB RELEASE REQUEST
message.
l 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:
CS _ CDR =
∑ CSRabrelTriggedByRNC *100%
∑ CSRABSetupSuccess
PS CDR is calculated as below:
PS _ CDR =
∑ PSRabrelTriggedByRNC *100%
∑ PSRABSetupSuccess
The failure cause indexes are sorted in Table 4-1.
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.
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.
Table 4-2 lists the thresholds of Ec/Io and Ec (from an RNP result of an operator, just for
reference).
Uplink or downlink DCH power helps to confirm the weak coverage is in uplink or downlink by
the following methods.
l If the uplink transmission power reaches the maximum before call drop, the uplink
BLER is weak or NodeB report RL failure according to single subscriber tracing
recorded by RNC, the call drop is probably due to weak uplink coverage.
l If the downlink transmission power reaches the maximum before call drop and the
downlink BLER is weak, the call drop is probably due to weak downlink coverage.
In a balanced uplink and downlink without uplink or downlink interference, both the uplink and
downlink transmit power will be restricted. You need not to judge whether uplink or 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:
l Lack of NodeBs
l Incorrectly configured sectors
l 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 2s–3s, 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:
l An abnormal NodeB causes failure of synchronization, so links keeps being added
and deleted.
l The UE does not report 1a measurement report so call drop occurs.
You need to focus on the call drop due to abnormal testing UE, which occurs easily during CQT.
Namely, the data recorded in DT does not contain the information reported by UE for a period.
Preparing Data
The data to be prepared include:
l Data files collected by DT
l Single subscriber tracing recorded by RNC
l CHR recorded by RNC
Table 4-3 Traffic statistics indexes for analyzing causes to call drop
Failure cause Analysis
OM interference The O&M tasks cause call drop.
The causes due to UTRAN in the cell lead to abnormal release of link. This
Causes due to UTRAN corresponds to abnormal process, so you must further analyze it based on
CHR.
Uplink RLC reset causes release of links, because the coverage quality
Uplink RLC reset
(including missing neighbor cell and over mall handover area) is bad.
Downlink SRB reset causes release of links, because the coverage quality
Downlink RLC reset
(including missing neighbor cell and over mall handover area) is bad.
Other causes You need to analyze the abnormal call drop based on RNC logs.
You can classify the previous indexes Table 4-3 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.
l RB reconfiguration complete
Confirm that the UE receives these messages by tracing messaged at RNC side.
5 FAQs Analysis
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.
Figure 5-1 shows the SHO relative threshold
PCPICH 1
PCPICH 2
Reporting
range
Reporting
terminated
Periodic Periodic
report report
Event-triggered
PCPICH 3
report
According to Figure 5-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.
A general method is to configure the threshold of 1A and 1B different. Configure the threshold of
1A event small (such as 3 dB) and keep the threshold of 1B threshold the same (5 dB). In this
way, the cells with bad quality cannot be listed into active set easily and the cells with good
quality can be listed into active set. Therefore the SHO rate is lowered based on normal SHO.
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:
Fn = (1 − a) ⋅ Fn −1 + a ⋅ M n
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.
Table 5-1 Relationship between the filter coefficient and the corresponding tracing time
Filter coefficient 0 1 2 3 4 5 6 7 8 9 11
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.
Figure 5-2 shows the signaling flow recorded by UE before call drop.
Analysis
Check the pilot test data from UE and scanner at call drop points. Figure 5-3 shows the
scrambles recorded by UE active set and scanner before call drop. In Figure 5-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.
Figure 5-3 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. Figure 5-4 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.
Continue to check the neighbor cell list sent by RNC to UE before call drop, as shown in Figure
5-5 and Figure 5-6. 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.
Figure 5-6 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 Figure 5-7:
l Confirm the scrambles of all cells in active set and the scrambles of cells in monitor
set measured by UE before call drop.
l 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.
l Check the neighbor cell list.
This applies for solving call drop due to missing neighbor cell on site.
Figure 5-7 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.
l Before deleting neighbor cells, check the revision record of neighbor cells. Check
that the cells to be deleted are not the ones that were added during previous DT and
optimization.
l After deleting neighbor cells, perform comprehensive test, including DT and CQT in
important indoor spots. From this, you can check the variation of traffic statistics
result of the corresponding cells. The traffic statistics result includes setup success
rate, CDR, and handover success rate. Ensure there is no abnormality. Otherwise
restore the configuration.
If no reliable 3G handover times can serve as judgment at the network construction stage, you
can estimate the handover probability by using the handover times of 2G neighbor cells.
Table 5-2 lists the 2G handover times.
12531 56820 0
12531 56910 206
Search for the neighbor cells with few handover times and even no handovers, such as cell
12531–12292. Figure 5-8 shows the location relationship of 2G redundant neighbor cells.
According to Figure 5-8, 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.
From Figure 5-10, Figure 5-11, Figure 5-12, Figure 5-13, and Figure 5-14, though SC20
cell is planned to cover the area, but the best ServiceCell is as listed in Table 5-3.
Figure 5-16 shows the RSCP of Best ServiceCell near Yuxing Rd..
As shown in Figure 5-15, the RSSI of the areas with pilot pollution is not large, about
–100 dBm to –90 dBm. As shown in Figure 5-16, 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.
l Analyzing RSCP Distribution of Related Cells
Figure 5-17 shows the RSCP of SC270 cell near Yuxing Rd.
The SC270 cell is planned to cover the area. Figure 5-17 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.
Figure 5-18 shows the pilot pollution near Yuxing Rd. after optimization.
Figure 5-19 shows the best ServiceCell near Yuxing Rd. after optimization.
Figure 5-20 shows the RSCP of best ServiceCell near Yuxing Rd. after optimization.
Figure 5-20 RSCP of best ServiceCell near Yuxing Rd. after optimization
Figure 5-21 shows the RSCP of SC270 cell near Yuxing Rd. after optimization.
Figure 5-21 RSCP of SC270 cell near Yuxing Rd. after optimization
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.
cell56 vs cell041
-10 cell56
EcNo
-20 cell041
-30
time
According to Figure 5-22, 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.
Figure 5-23 shows an example of turning corner effect.
According to Figure 5-23, 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 Figure 5-24.
Solution
To solve turning corner effect problems, do as follows:
l Configure the CIO between two cells with turning corner effect to add the target cell
more easily. The CIO only affects the handover between two cells, with less impact,
however, it impacts handover. The configuration leads to an increase of handover
ratio.
l Adjust antenna to enable the antenna of target cell cover the turning corner. This
helps avoid fast variance of signals, and avoid call drop. Actually experiences help
judge whether the adjustment of engineering parameters can cover the turning
corner, so using this method is difficult.
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).
l If handover occurs in the target cell, and the signals of the original cell is over weak,
so the UE cannot receive active set update messages, and consequently call drop
occurs.
l If the needlepoint lasts for a short period, and the handover conditions are difficult to
meet, so the signaling or service RB reset occurs due to weak downlink signals
before handover. Finally, call drop occurs.
l If the target cell completes handover, and becomes a cell in the active set, call drop
occurs because the cell can exit the active set before completing a handover with
the needlepoint disappearing quickly.
Compared with turning corner effect, the needlepoint effect is more risky due to two handovers,
and failure of one of the two causes call drop. The needlepoint lasts for a short period, so call
drop may not occur if QoS is lowered (for example, configure a greater retransmission times).
The turning corner effect causes an absolute call drop because the signals of original cell will
not recover after turning corner.
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.
Figure 5-26 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
Figure 5-27 shows signal distribution of cell52 vs. cell88 (signal fluctuation in handover areas).
Figure 5-27 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 Figure 5-27, 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 Figure 5-28.
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 Figure 5-29.
According to Figure 5-29, 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:
l CPICH RSCP strength
l Downlink interference
The downlink interference in the WCDMA network includes the interference from downlink
signals of intra-frequency cells (the host cell and neighbor cells) and the background noise.
Wherein, the downlink interference strength of intra-frequency cells is impacted by path loss and
slow attenuation. It is similar to the attenuation that UE receives useful signals (such as CPICH
RSCP).
At the coverage edge of a carrier, when UE moves from the current cell to another cell, the
CPICH RSCP attenuates at the same speed as the attenuation of interference (the background
noise is not impacted by path loss, so the CPICH RSCP attenuates a little faster than
interference attenuates. However, the difference between the two speeds is close (depending
on the strength of background noise). Therefore the UE receives the signals the 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.
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 1–2 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:
l When the pilot signal quality Ec/Io in 3G cells minus Qqualmin is less than the
inter-RAT measurement start threshold SsearchRAT, the UE started to measure the
2G neighbor cell.
l When the quality of signal in 2G neighbor cells satisfies the cell reselection criteria
and lasts for Treselection, the UE selects 2G cells.
3G RSCP is below –90 dBm at the borders of 3G network. However the 2G RSCP ranges from
–60 dBm to –70 dBm with signals of good quality. Therefore, once the UE starts to measure the
2G neighbor cells and the signal in the cell fails to be better in Treselection, the UE reselects the
2G cells.
The key parameter in reselection from the 3G network to the 2G network in test is SsearchRAT.
The rational configuration of the reselection delay timing parameter Treselection helps solve
ping-pong reselection.
The reselection from the 2G network to the 3G network is as follows:
l When the signal strength of 2G serving cell satisfies the inter-RAT start threshold
Qsearch_I, the 3G neighbor cells are measured. From optimized 3G strategy, the
current configuration is 7 (always start).
l When the signal strength RSCP of the 3G cell minus the current RLA_C (the
average signal strength in 2G serving and non-serving cells) is greater than
FDD_Qoffest, and it lasts 5s, the 3G cell can serve as the target cell to be reselected.
The current FDD_Qoffset is 7 (always reselect 3G cells).
l When the signal quality Ec/Io of the 3G cell is greater than or equal to FDD_Qmin
threshold, the 3G cell can serve as the target cell to be reselected.
l 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:
l The operator increases the interval between SsearchRAT and FDD_Qmin.
According to the default parameters, if 3G CPICH Ec/Io is greater than –12 dB in the
GSM system, the UE reselects the 3G network. If 3G CPICH Ec/Io is less than or
equal to –14 dB, the UE reselects the GSM network from 3G network. In the current
parameters configuration, the signal fluctuation of 3G CPICH Ec/Io decides the
frequency of cell reselection. If the signal fluctuation is over 1 dB, the ping-pong
reselection occurs. In field test of 3G cells, if Ec/Io is less than –14 dB, the UE drops
off the network easily, so the SsearchRAT cannot be less, and FDD_Qmin can be
increased. The value range of FDD_Qmin is over small, so it can be only set to its
maximum value –13 dB. Since the protocol of September 2003, the value range of
FDD_Qmin is increased through CR GP-032221 (see 5.2 for details). If the UE is
updated according to GP-032221, the FDD_Qmin is increases completely. If
FDD_Qmin is set to –8 dB, compared with the start measurement threshold –14 dB
of reselection from the 3G network to 2G network, FDD_Qmin has a space of 6 dB.
In this way, the ping-pong reselection caused by signal fluctuation is less likely.
l Treselection is increased. If the default configuration is 1s, the Treselection can be
set to 5s. In this way, the reselection between the 3G network and the 2G network is
reduced.
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.
l In CS service, after handoff from the 3G network to the 2G network and after release
of services in the 2G network, the UE reside again in the 3G cell through reselection
from the 2G network to the 3G network or reselection of PLMN.
l In PS service, after the reselection from the 3G network to the 2G network started by
the network, the UE re-accesses the 2G network. In services transmission, the UE
performing PS services may return to the 3G network through reselection between
the 2G network and the 3G network. According to the analysis of 3.1 , in the
reselection of the cells performing PS domain services from the 2G network to 3G
network, the actual working factor is the configuration of FDD_Qmin (measuring
Ec/Io). If Ec/Io is greater than FDD_Qmin, the UE reselects 3G network. Whether the
UE has handed off from the 3G network to the 2G network is judged through
measuring RSCP in condition of the cell as a border cell. Measuring RSCP cannot
assure that Ec/Io is greater than FDD_Qmin, so no mechanism can avoid ping-pong
handoff.
The solutions lie in as follows:
l The measurement target of 2G and the 3G network is unified. If this cannot be
performed, the following method is adopted.
l The start parameters in compression mode and reselection threshold from the 2G
network to the 3G network is adjusted.
Solutions
l Unification of measurement target in the 3G network and the 2G network
When there are more than one 3G cells, the change of Ec/Io indicates the change of
3G cell quality. If the cell property is configured as “carrier center cell” and the
measurement target in 2D event is Ec/Io, the measurement target between 3G and
the 2G network is Ec/Io. The default parameter of 2D/2F with the measurement
target Ec/Io is –24 dB. The parameter can be adjusted to –12/–10 dB to avoid
ping-pong handoff.
In addition, the new 3GPP TS 05.08 protocol defines the RSCP (FDD_RSCP) that
can measure the 3G network in reselection from the 2G network to the 3G network.
Now only Ec/Io can be tested. The adjustment fits the 3G cells the cell property of
which is “carrier border cell”. However many current NEs does not support this.
l Adjustment of start parameters in compression mode and reselection threshold from
2G to 3G network
The adjustment fits the 3G cells the property of which is “carrier border cell”. Only 3G
Ec/Io can be measured in reselection from the 2G network to 3G network. The
start/stop threshold in compression mode can be lowered to –105/–100 dBm.
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. Figure 5-31
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:
l 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.
l Change 2D RSCP Threshold from –95 dBm to –85 dBm to –75 dBm. The inter-RAT
measurement starts earlier. Call still drops in test.
l Change GSM RSSI from –90 dBm to –95 dBm. The UE hands off to GSM cells more
easily. Call still drops in test.
l Change 2D Trigger Time from 640ms to 320ms to 0ms. The inter-RAT measurement
starts more easily. Call still drops in test. Change the parameter back to 640ms.
l 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.
l Change Inter RAT handover trigger time from 5000ms to 2000ms. The UE performs
inter-RAT more quickly. Call drop is improved.
l Recover the parameter changed in Step 5 as it was.
l Change Inter RAT handover trigger time from 2000ms to 1000ms. The UE performs
inter-RAT handoff more quickly. Call drop is solved.
The adjustment results in that the change to the parameter Inter RAT handover trigger time is
the most effective to complete inter-RAT handoff.
Solutions
The operator checks as follows:
l Check that 2G neighbor cells are validly configured.
l Reduce TimeToTrigForVerify (TimeToTrigForNonVerify needs no change. The
current protocol defines that the UE needs not to report on NonVerify) to make UE
hand off to the 2G network more quickly.
l Increase GSM CIO. This increases the possibility of handoff to the 2G network, but
increases the coverage of the 2G network and reduces the coverage of 3G,
therefore this step need consideration.
l Increase the GSM RSSI handoff threshold. This increases the coverage of the 2G
network, but reduces the coverage of 3G network, therefore this step needs
consideration.
Increase 2D/2F threshold in compression mode to start compression mode earlier.
l 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.
l 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.
After the RNC sends Physical channel reconfiguration and inter-RAT measurement control
messages, the UE keeps sending the measurement report of Nonverified until call drop.
In S subject, for convenient configuration of parameters, the original 2G neighbor cell
information is used to configure inter-RAT neighbor cells. All the inter-RAT cells are configured
as the neighbor cells of 3G cells. Inter-RAT cell offset is configured to enable the UE to hand
over to the target cell and to disable the UE to hand over to the undesired cell.
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:
l The signals of 3G cell is weak
l Ec is smaller than –110 dBm.
l Ec/Io smaller than –10 dB.
l A 2G testing UE detects that the 2G signals of indoor DAS are strong
l The UE does not hand over.
Check the signaling to confirm whether the UE send measurement report messages. If you
compare it with terminals of other types, confirming the problem is easier and more accurate.
Example :
l Moto A835 handset:
16:38:05(99): The UE sends 2D measurement reports.
16:38:06(06): The RNC sends Physical channel reconfiguration (active sets contains
PSC46, PSC492, and PSC36)
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.
l Qualcomm 6250 handset
16:38:42(16): The UE sends 2D measurement reports.
16:38:42(49): The RNC sends Physical channel reconfiguration (active set contains
PSC46 and PSC492)
16:38:43(43): The RNC receives Physical channel reconfiguration completion message,
and it sends measurement control messages.
16:38:47(74): The UE report BCCH 847 BSIC Verified, and the level is –67 dBm.
16:38:48(88): The RNC sends HO CMD message, so the handover succeeds.
In the test of handover between outdoor 3G to indoor 2G DAS, the Moto A835 handset does not
send inter-RAT the measurement report for multiple times. The IOT engineers think that the
version of out handset is not updated, and they recommend updating handset version.
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 4–5
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:
l During the handover process, the RNC originates lu Release because:
− The NodeB reports RL Failure.
− The NodeB does not report RL failure, but SRB reset occurs.
17:09:00(33): The RNC receives Physical channel reconfiguration completion, and sends
measurement control messages.
17:07:58(81): The RNC receives the measurement report from UE, BCCH 853, and the
level is –61dBm.
17:08:00(25): The RNC sends HO CMD.
17:08:00(90): The CN sends Iu Release Command (successful relocation).
Actually, call drop occurs during handover.
Now the starting threshold of compression mode is as high as –95 dBm. Do not change it to
avoid impact on other parts of the network so that the handover occurs earlier.
14:53:16(62): The RNC does not receive the measurement report from UE, and ensures
that the cell ID is in the list of neighbor cells of cell 144. The RNC does not process the
reports
14:53:19(99): The RNC originates Iu Release.
If different interRATCellID is used in inter-RAT measurement control, will the RNC avoid this
problem?
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.
l 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:
− Increasing the threshold of 2D event
− Reducing hysteresis
− Reducing delayed triggering time
Now the back system can configure different starting threshold of inter-RAT
compression mode for signaling, CS and PS services.
l 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 Figure 5-32, 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.
According to Figure 5-33, the RNC sends a CC Connect message, but the UE does not
respond to the CC Connect message. This causes the call drop.
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.
Figure 5-35 shows the 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
l 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.
l 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.
l 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.
l 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 network. The Moto handset and Nokia handset can succeed in handover.
The handover failure is probably due to excessive 2G neighbor cells are configured.
After excessive 2G neighbor cells are deleted and only one 2G neighbor cell is kept,
the Sony-Ericsson handset succeeds in handover. When two 2G neighbor cells with
the same frequency and different BSIC exists, the handset will stop handover
because it is not specified with the BSIC and the target 2G neighbor cell when it is
sending the measurement report.
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 .
l Solution
To solve the problem, add the corresponding neighbor cell.
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.
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:
l DT/CQT flow for HSDPA handover
7 Appendix
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.
Figure 7-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.
Figure 7-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.
Table 7-1 lists the timers and counters related to the synchronization and asynchronization.
Table 7-1 Timers and counters related to the synchronization and asynchronization
Parameter Parameter
Description
ID Name
Value range: D100, D200, D400, D600, D800, D1000, D1200,
D1400, D1600, D1800, D2000, D3000, D4000, D6000, and
D8000
Actual value range: 100, 200, 400, 600, 800, 1000, 1200,
1400, 1600, 1800, 2000, 3000, 4000, 6000, and 8000
Physical unit: ms
Content: When the UE sends CELL UPDATE/URA UPDATE
T302 Timer 302 messages, start timer T302. When the UE receives CELL
UPDATE CONFIRM/URA UPDATE CONFIRM messages,
stop time T302.
When T302 expires,
If V302 ≤ N302, the UE resends CELL UPDATE/URA
UPDATE messages.
If not, the UE enters idle mode.
Recommended value: D2000
Value range: D0, D2, D4, D6, D8, D12, D16, and D20
Actual value range: 0, 2, 4, 6, 8, 12, 16, and 20
Physical unit: none
Content: When the principle of radio link failure is met, and the
radio bearer only related to T314 exists, start T314. When the
cell update is complete, stop T314. The default value is 12.
When the UE of CELL_DCH fails in radio links, start T314 (or
T314 Timer 314 T315), and send CELL UPDATE messages. Before T314 (or
T315) corresponding to services expires, if the radio link
reconfiguration configured by CELL UPDATE CONFIRM
message fails, resend CELL UPDATE messages to
reconfigure the radio link (related to T302 and N302). Based
on this, configure T314 > T302 × N302.
When T314 expires, the service RB of corresponding timers is
deleted.
Recommended value: D20
Value range: D0, D10, D30, D60, D180, D600, D1200, and
D1800
Actual value range: 0, 10, 30, 60, 180, 600, 1200, and 1800
Physical unit: s
Content: When the principle of radio link failure is met, and the
radio bearer only related to T315 exists, start T315. When the
cell update is complete, stop T314. The default value is 180.
T315 Timer 315 When the UE of CELL_DCH fails in radio links, start T315 (or
T314), and send CELL UPDATE messages. Before T315 (or
T314) corresponding to services expires, if the radio link
reconfiguration configured by CELL UPDATE CONFIRM
message fails, resend CELL UPDATE messages to
reconfigure the radio link (related to T302 and N302). Based
on this, configure T315 > T302 × N302.
When T315 expires, the service RB of corresponding timers is
deleted.
Recommended value: D30
Value range: D1, D2, D4, D10, D20, D50, D100, D200, D400,
D600, D800, and D1000
Actual value range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600,
800, and 1000
Constant
N315 Physical unit: s
315
Content: It indicates the maximum times continuous
synchronization indicators received from L1. The default value
is 1.
Recommended value: D1
Table 7-2 lists the timers and counters related to call drop at lub interface.
Table 7-2 Timers and counters related to call drop at lub interface
Recommended value: 5
Recommended value: 50
− TFS
− TFCS
− Frequency
− Uplink Scramble
l According to radio resources, the DRNC judge whether the requested radio resource
can be met. If yes, the DRNC send the NBAP message, namely, Radio Link Setup
Request, to NodeB to which the DRNC belongs. After this, the NodeB starts to
receive messages in uplink.
The Radio Link Setup Request message includes parameters as below:
− Cell ID
− TFS
− TFCS
− Frequency
l The NodeB allocates radio resources as required. If it succeeds, the NodeB reports
an NBAP message, namely, the Radio Link Setup Response message, to DRNC.
The Radio Link Setup Response message includes two parameters: signaling
termination and transport layer addressing information (AAL2 addressing, AAL2
bound ID for data transmission and bearer)
l The DRNC sends the Radio Link Setup Response message to SRNC through
RNSAP.
The Radio Link Setup Response message includes two parameters: transport layer
addressing information (AAL2 addressing, AAL2 bound ID for transmitting and
carrying data) and information about adjacent cells.
l The SRNC starts lur/lub data transmission and bearer through the ALCAP protocol.
The request includes AAL2 bound ID for binding lub data transmission and bearer,
and DCH.
l or 7) The NodeB and SRNC set up synchronization of data transmission and bearer
by exchanging the corresponding DCH FP frame Downlink Synchronization and
Uplink Synchronization. The NodeB starts downlink transmission.
l The SRNC sends UE the Active Set Update message on DCCH. The message
includes content on adding radio link.
The parameters include:
− Update type
− Cell ID
− Downlink scramble
− Power control information
− Adjacent cells
l The UE configures the corresponding parameters according to RRC signaling. It
sends SRNC the RRC message, namely, Active Set Update Complete message.
l 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.
l The UE deactivates the downlink receiver of radio link to be deleted and sends
SRNC the Active Set Update Complete message.
l The SRNC sends the Radio Link Deletion Request to DRNC on through.
The parameters include cell ID and transport layer addressing information.
l The DRNC sends NodeB the NBAP message, namely, the Radio Link Deletion
Request message. The NodeB stops receiving and sending.
The parameters include cell ID and transport layer addressing information.
l The NodeB deactivates radio resources and sends DRNC the NBAP message,
namely, the Radio Link Deletion Response message.
l The SRNC starts releasing lur/lub data bearer through the ALCAP protocol.
7.3.3 Analyzing Signaling Flow for Adding and Deleting Radio Link
The conditions of SHO signaling flow for adding and deleting radio link are:
l The UE has one or more radio links with SRNC.
l The UE sets up a new radio link through new NodeB and new RNC.
l Delete the previous link connecting UE and SRNC through the NodeB which belongs
to SRNC.
The UE can set up only one link with UTRAN, so there is no macro diversity
combination/splitting.
Figure 7-5 SHO signaling flow for adding and deleting radio link
Decision to setup
new RL and
release old RL
Start RX
description
NBAP 3. Radio Link Setup Response NBAP
4. Radio Link Setup
Response
RNSAP RNSAP
5. ALCAP Iub Data Transport Bearer Setup ALCAP Iur Bearer Setup
7. Uplink Synchronisation
DCH-FP DCH-FP
Start TX
description
8. DCCH : Active Set Update Command
RRC RRC
[Radio Link Addition & Deletion]
Stop RX and TX
Steps of SHO signaling Flow for Adding and Deleting Radio Link
The SHO signaling flow for adding and deleting radio link proceeds as below:
l 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
l According to radio resources, the DRNC judge whether the requested radio resource
can be met. If yes, the DRNC send the NBAP message, namely, Radio Link Setup
Request, to NodeB to which the DRNC belongs. After this, the NodeB starts to
receive messages in uplink.
The Radio Link Setup Request message includes parameters as below:
− Cell ID
− TFS
− TFCS
− Frequency
l The NodeB allocates radio resources as required. If it succeeds, the NodeB reports
an NBAP message, namely, the Radio Link Setup Response message, to DRNC.
The Radio Link Setup Response message includes two parameters: signaling
termination and transport layer addressing information (AAL2 addressing, AAL2
bound ID for data transmission and bearer)
l The DRNC sends the Radio Link Setup Response message to SRNC through
RNSAP.
The Radio Link Setup Response message includes two parameters: transport layer
addressing information (AAL2 addressing, AAL2 bound ID for transmitting and
carrying data) and information about adjacent cells.
l The SRNC starts lur/lub data transmission and bearer through the ALCAP protocol.
The request includes AAL2 bound ID for binding lub data transmission and bearer,
and DCH.
l or 7) The NodeB and SRNC set up synchronization of data transmission and bearer
by exchanging the corresponding DCH FP frame Downlink Synchronization and
Uplink Synchronization. The NodeB starts downlink transmission.
l The SRNC sends UE the Active Set Update message on DCCH. The message
includes content on adding and removing radio link.
The parameters include:
− Update type
− Cell ID
− Downlink scramble
− Power control information
− Adjacent cells
parameters parameters
Layer 1 Layer 3
A filtering B filtering C Evaluation D
of reporting
C' criteria
In Figure 7-6,
l Point A is the direct measurement result of physical layer.
l Point B is the filtered measurement result at physical layer and it is also the
measurement result provided to upper layer from physical layer.
l Point C is the measurement result for event judgment after upper layer filtering.
l FilterCoef is filtering factor of measured values and weights the measurement results
of physical layer at different points. It is used in event report and period report. The
filtering of measured values is calculated as below:
Fn = (1 − a ) ⋅ Fn −1 + a ⋅ M n
Wherein,
− Fn: filtered updated measurement result
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:
NA
10 ⋅ LogM New ≤ W ⋅10 ⋅ Log ∑ M i + (1 − W ) ⋅10 ⋅ LogM Best + ( R − H 1a / 2),
i =1
For other measurement values:
NA
10 ⋅ LogM New ≥ W ⋅10 ⋅ Log ∑ M i + (1 − W ) ⋅10 ⋅ LogM Best − ( R − H 1a / 2),
i =1
In the previous formulas:
l MNew is the measurement result of cells in the reporting range.
l Mi is the measurement result of cells in the active set.
l NA is the number of cells in the active set.
l MBest is the measured value of the best cell in the active set.
l W is the weighting factor.
l R is the reporting range, with signal strength as an example. It is equal to the signal
strength of the best cell in the active set minus a value.
l H1a is the hysteresis of 1A event.
Measurement
quantity
P CPICH 1
Reporting
range
P CPICH 2
P CPICH 3 Time-to-trigger
Reporting Time
event 1A
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.
PCPICH 1
PCPICH 2
Reporting
range
Reporting
terminated
Periodic Periodic
report report
Event-triggered
PCPICH 3
report
When the following formulas are met, the UE judges that a primary pilot channel leaves the
reporting range. For 1B event and for event-triggered cells,
l If more than one links are in the active set, the UE judges to delete the links.
l If only one links is in the active set, the UE performs no operation.
The path loss is:
NA
10 ⋅ LogM Old ≥ W ⋅ 10 ⋅ Log ∑ M i + (1 − W ) ⋅ 10 ⋅ LogM Best + ( R + H 1a / 2),
i =1
For Other measure values:
NA
10 ⋅ LogM Old ≤ W ⋅ 10 ⋅ Log ∑ M i + (1 − W ) ⋅ 10 ⋅ LogM Best − ( R + H 1b / 2),
i =1
In the previous formulas:
l MBest is the measured value of the best cell in the active set.
l W is the weighting factor.
l R is the reporting range.
l H1a is the hysteresis of 1B event.
If multiple cells meet the reporting conditions at the same time, and reach the trigger delay, the
UE sorts the cells in terms of measured value and then reports them.
In Figure 7-9, 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.
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 Figure 7-11.
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.
The 1E event triggers measurement report of the cells not monitored when the UE fails to
receive the neighbor cell table.
Figure 7-14 Ordinary HHO flow (lur interface and CELL_DCH state)
l 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.
l 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.
l When the target RNC completes preparations, it sends SRNC the Radio Link Setup
Response message.
l 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.
l The SRNC send UE the Physical Channel Reconfiguration message.
l 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.
l The SRNC sends the original SRNC the RNSAP message, namely, the Radio Link
Failure Indication.
l 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.
l 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.
l The source RNC sends original NodeB the NBAP message, the Radio Link Deletion
Request message.
The parameters include cell ID and transport layer addressing information.
l The source NodeB releases radio resources used by original link and sends source
RNC the NBAP message, the Radio Link Deletion Response message.
l The source RNC starts releasing lur data transmission and bearer according to the
ALCAP protocol.
l When the source RNC completes releasing lur data transmission and bearer, it
sends SRNC the RNSAP message, the Radio Link Deletion Response message.
l The SRNC starts releasing lur data transmission and bearer according to the ALCAP
protocol. The request includes AAL2 bound ID for binding lur data transmission and
bearer and the transport channel DCH. The release request is confirmed by the
target RNC.
1 . R el oc at io n R e q u ir ed
RAN A P RA NA P
2 . R elo ca ti on R eq u i red
RAN A P RAN A P
3 . R elo ca ti on R eq u est
RA NA P RA N AP
4 . Re loc a ti on Re q u est
RA NA P RA NA P
5 . A L C A P Iu D a t a
T ra n sp or t B ea rer S et u p
6 . R a d io L i n k S etu p Re q u est
N BA P NBAP
7 . R a d io L i n k S etu p R esp o n se
N BAP NBA P
8 . A L C A P Iu b D at a T ra n sp or t B ea rer S et u p
9 . Re lo ca ti on Re q u est
RA N AP A ck n ow l ed g e RA N A P
1 0 . Re lo ca ti on R eq u est
A ck n ow l ed g e
RAN A P RA NA P
1 1 . Re lo ca ti on C o m m a n d
RA N A P RA N A P
1 2 . R elo ca ti on C o m m a n d
RA NA P RAN A P
1 5 . R elo ca ti on D etec t RA NA P
RA NA P
1 6 . R a d i o L i n k F a il u re In d ica t io n
N BAP N BAP
1 8 . R e loc a tio n
C om p let e
RA NA P RA N A P
2 0 . Iu R elea se C om m a n d
RAN A P RA NA P
2 1 . Iu R ele a se C om m an d
RA N AP RA N AP
2 2 . A L C A P Iu D at a T ra n sp ort B ea rer
Re lea se
2 3 . Iu R el ea se C o m p l ete
RAN A P RA N A P
2 4 . Iu R elea se C om p le te
RA N AP RAN A P
l 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.
l or 21) The CN sends SRNC the Lu Release Command message.
l The lu transmission and bearer between the original RNC and CN is released.
l 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.
l If the quality of measurement quantity is worse than the starting threshold, the 2D
event is reported and then the periodic inter-frequency measurement is started
through judgment.
l If the quality of active set is higher than the stopping threshold, the 2F event is
triggered and inter-frequency measurement is stopped.
& 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.
Description
When the HS-PDSCH serving cell is updated due to DPCH SHO, the UE reports the following
events listed in Table 7-3. The system will respond accordingly.
Table 7-3 Flow of serving cell update triggered by different events in SHO
Event Action
1D event, the best server is listed in Change the radio link ID by reconfiguring radio
active set link
Update the serving cell in active set, and
1B event, the HS-DSCH serving cell
perform DCH SHO to delete the cell
is to be deleted
corresponding to 1B event
1C event, the current HS-DSCH Update the HS-DSCH in active set to support
serving cell is the worst cell in active the best server of HS-DSCH, and then replace
set the cell
1D event, the active set is full, the Replace the second worst cell in active set, and
cell to be replaced is the serving cell update the serving cell
Measurement
CPHY-Measurement-IND
Reporting
criteria
fulfilled
DCCH: MEASUREMENT REPORT
Serving HS-
DSCH cell
change decision
CPHY-RL-Modify-REQ
(NBAP/RNSAP: RL Reconfiguration Prepare)
CPHY-RL-Modify-CNF
(NBAP/RNSAP: RL Reconfiguration Ready)
CPHY-RL-Commit-REQ
(NBAP/RNSAP: RL Reconfiguration Commit)
CPHY-RL-Modify-REQ
l The SRNC sends DRNC the RADIO LINK RECONFIGURATION COMMIT message.
The message contains the activation time of SRNC in CFN.
l The DRNC sends the serving NodeB the RADIO LINK RECONFIGURATION
COMMIT message. The message contains its activation time. At the activation time,
the NodeB commands the source HS-DSCH cell to stop sending HS-DSCH data to
UE. The target HS-DSCH cell sends UE the HS-DSCH data.
l The SRNC sends UE the PHYSICAL CHANNEL RECONFIGURATION message.
The message contains the following information:
− Activation time
− MAC-HS RESET indicator
− Link ID of the serving HS-DSCH
− HS-SCCH set indicator
− UE ID of HS-DSCH
l In the specified activation time, the UE resets HS-DSCH. It stops receiving
HS-DSCH data from the source HS-DSCH cell, and starts receiving HS-DSCH data
from target HS-DSCH cell. The UE responds SRNC the PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message.
1. RNSAP: RL RECONFIGURATION
2. NBAP: RL RECONFIGURATION
PREPARE
PREPARE
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(HS-DSCH) (HS-DSCH)
ALCAP Iub Data Transport ALCAP Iur Data Transport Bearer release
Bearer release (HS-DSCH) (HS-DSCH)
The update process is based on that the DPCH and active set are fixed.
The inter-NodeB synchronization serving cell is updated as below:
l a) After SRNC decides to update HS-DSCH cell, it sends DRNC the RADIO LINK
RECONFIGURATION PREPARE message. The message contains the identity of
HS-DSCH target cell.
l The DRNC sends the source NodeB the RADIO LINK RECONFIGURATION
PREPARE message.
l The NodeB responds RADIO LINK RECONFIGURATION READY message. The
message contains the indicator of RESET MAC-hs after reconfiguration.
l After setting up the HS-DSCH transport bearer to the target NodeB, the SRNC
sends the RADIO LINK RECONFIGURATION COMMIT to DRNC, including the
activation time of SRNC in CRN.
l The DRNC sends the RADIO LINK RECONFIGURATION COMMIT message to the
source NodeB and target NodeB. The message contains its activation time. In the
activation time, the source NodeB stops and target NodeB starts sending HS-DSCH
data.
l The SRNC sends UE the PHYSICAL CHANNEL RECONFIGURATION message to
UE. The message contains the following information:
− Activation time
− MAC-hs RESET indicator
− Link ID of the serving HS-DSCH
− HS-SCCH set indicator
− UE ID of HS-DSCH
l In the specified activation time, the UE resets MAC-hs. It stops receiving the
HS-DSCH data from the source HS-DSCH cell, and 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):
INTER_NODEB(ok).t
mf
Figure 7-18 Inter-NodeB HS-DSCH cell update after radio link is added
Uu Target Node B Source Node B Iub Iur
UE DRNC SRNC
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(DCH) (DCH)
7. RNSAP: RL RECONFIGURATION
8. NBAP: RL RECONFIGURATION
REQUEST
REQUEST
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(HS-DSCH) (HS-DSCH)
ALCAP Iub Data Transport ALCAP Iur Data Transport Bearer release
Bearer release (HS-DSCH) (HS-DSCH)
Setting a newly-added radio link to HS-DSCH radio link involves two steps:
l Add a new link to active set
l The HS-DSCH transmits to the new radio link
After radio link is added, the inter-NodeB HS-DSCH cell is updated as below:
l 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.
l 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.
l The target NodeB allocates resources. It receives information at the physical layer of
the new DPCH. It responds the RADIO LINK SETUP RESPONSE message.
l The DRNC responds the RADIO LINK SETUP RESPONSE message to SRNC. The
DCH transport bearer is set up.
l The SRNC sends UE the ACTIVE SET UPDATE message. The message contains
the new radio link ID.
l The UE adds the new radio link to active set, and then responds the ACTIVE SET
UPDATE COMPLETE message to SRNC.
l The SRNC sends the RADIO LINK RECONFIGURATION REQUEST message to
DRNC. The message indicates the target HS-DSCH cell.
l 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.
l The source NodeB responds the RADIO LINK RECONFIGURATION READY
message to DRNC.
l The DRNC sends the RADIO LINK RECONFIGURATION REQUEST message to
target NodeB. The message indicates target NodeB to perform synchronized radio
link reconfiguration to allocate resources to target HS-DSCH link.
l The target NodeB responds the RADIO LINK RECONFIGURATION READY
message.
l The DRNC sends the RADIO LINK RECONFIGURATION READY message to
SRNC. The message contains the following information:
− HS-SCCH set information
− Scramble of target HS-SCCH cell
− UE ID of HS-DSCH
l 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.
l 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 HS-DSCH information to the UE.
l The SRNC sends the PHYSICAL CHANNEL RECONFIGURATION message to UE.
The message contains the following information:
− Activation time
− MAC-hs RESET indicator
− Link ID of the HS-DSCH
− HS-SCCH code set
− UE ID of HS-DSCH
l In the specified time, the UE resets MAC-hs. It stops receiving HS-DSCH data from
source HS-DSCH cell, and starts receiving HS-DSCH 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.
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
Figure 7-19 shows the inter-NodeB HS-DSCH cell update during HHO (single step method).
Figure 7-19 Inter-NodeB HS-DSCH cell update during HHO (single step method)
Uu Target Node B Source Node B Iub Target Source Iur
UE DRNC DRNC SRNC
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(DCH + HS-DSCH) (DCH + HS-DSCH)
ALCAP Iub Data Transport ALCAP Iur Data Transport Bearer release
Bearer release (DCH + HS-DSCH) (DCH + HS-DSCH)
The inter-NodeB HS-DSCH cell during HHO (single step method) is updated as below:
l The SRNC decides to perform HHO and update HS-DSCH cell. It sends the RADIO
LINK SETUP REQUEST message to target DRNC. The message indicates the
target cell for HHO and the information to set up HS-DSCH resource in target
HS-DSCH cell.
l The DRNC allocates resources for new radio link. It sends the RADIO LINK SETUP
REQUEST message to target NodeB. The message contains the information to set
up DPCH and that to set up HS-DSCH.
l The target NodeB allocates resources to set up DPCH link. It starts receiving data
from physical layer. It responds the RADIO LINK SETUP RESPONSE message. The
message contains the information about HS-SCCH code set, and HS-DSCH flow
control.
l The DRNC responds the RADIO LINK SETUP RESPONSE message to SRNC. The
DCH and DSCH transport bearer is set up at lub and lur interface. The message
contains the following information:
− HS-SCCH code set
− HS-DSCH flow control
− UE ID
l The SRNC sends UE the PHYSICAL CHANNEL RECONFIGURATION message.
The message contains the following information:
− Activation time
− DPCH of target cell
− MAC-hs RESET indicator
− Link ID of the HS-DSCH
− HS-SCCH code set
− UE ID of HS-DSCH
l 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.
l The SRNC sends the RADIO LINK DELETION REQUEST message to source
DRNC. The message indicates the cell to be deleted.
l The target DRNC sends the RADIO LINK DELETION REQUEST message to source
NodeB.
l The source NodeB releases original radio link resource, and responds the RADIO
LINK DELETION RESPONSE message to source DRNC.
Figure 7-20 DPCH intra-frequency 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).
INTER_NODEB(ok).t
mf
Figure 7-21 DPCH inter-frequency HHO with HS-DSCH serving cell update
In Figure 7-21,
l Message 98: the UE sends RNC the 2D measurement report.
l Messages 99–105: the UE and NodeB starts compression mode.
l Messages 112–143: the UE sends the measurement report. The report meets the
HHO threshold. The flow for physical channel reconfiguration occurs. HHO is
complete. The HS-PDSCH serving cell is updated.
The following attachment contains the signaling, according to V100R005C01B061.
HSDPA_INTER_FREQ_
HHO_WITH_TRAFFIC_OK_UE.tmf
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.
Figure 7-22 shows the handover from HSDPA to R99.
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 Table 7-4.
Figure 7-24 DPCH SHO with handover from HSDPA to R99 (inter-NodeB)
l Messages 31 and 32: the R99 cell is listed in active set, so the HS-PDSCH
parameters need changing. RL is reconfigured, and HS-PDSCH parameters are
changed.
l Message 33: the physical channel is reconfigured, and physical parameters of
HSPDA are changed.
l Message 40: the UE sends 1D measurement report, and the R99 cell becomes the
best server. Now the HS-PDSCH serving cell remains the same.
l Message 44: the UE sends 1B measurement report.
l Message 50: the RB is reconfigured, and the service is reconfigured from
HS-PDSCH to DCH.
l Messages 56–60: the RL of original HS-PDSCH is deleted from active set.
Figure 7-25 shows the DPCH SHO with handover from R99 to HSDPA.
In Figure 7-25, 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.
SHO_R5toR99&R99to
R5(OK)_Inter_NodeB.tmf
Figure 7-26 Inter-NodeB SHO with handover from HSDPA to R99 (V17)
In V17, the signaling flow for SHO from HSDPA to R99 is as follows:
l The UE accesses a HSDPA cell.
− 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:
l The UE accesses an R99 cell.
− 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.
RNC_2006-10-30-09
-59-11_H2D SHO.rar
l Message 32: the network side prohibits SHO and neglects 1A event. The UE reports
1D event.
Intra-frequency HHO occurs on DPCH while the handover from R99 to R5 occurs. The
intra-frequency HHO of R99 occurs, and then the service is reconfigured from DCH to
HS-PDSCH in the new HSDPA cell.
HHO_R5ToR99(OK)
and R99toR5_Intra_NodeB.tmf
In V17, the signaling flow for intra-frequency HHO from HSDPA to R99 is as follows:
l The UE accesses a HSDPA cell.
− 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.
RNC_2006-10-30-10
-41-35_H2D intraHHO.rar
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.
hsdpa-2G.tmf
In V17, the following types of inter-frequency direct retry of HSDPA are available:
l Inter-frequency direct retry of HSDPA during setup of a service
− 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.
In V17, the switch between HS-DSCH and DCH might occur in any of the following cases:
l The reason for handover between HS-DSCH and DCH is coverage. This case
includes that the UE moves from an R99 cell to a HSDPA cell or from a HSDPA cell
to a R99 cell.
l D2H channel type switch triggered by traffic
− Scenario 1: A 4A event triggers D2H channel type switch in a cell.
The current service that is fit for the HS-DSCH is over the DCH for some reason
(such as admission rejection). Both the UE and the best cell support HSDPA. The rate
of the service on the current DCH is lower than 384 Kbps. In this case, the system
re-allocates the service from the DCH to the HS-DSCH in the best cell if the data
traffic of the UE increases (the RNC receives a 4A event measurement report).
− 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.
RNC_2006-10-30
-11-31-49_based on trafficrar
RNC_2006-10-30
-11-11-05_based on timer D2H.rar
l Serving E-DCH RLS: It refers to a cell set that contains at least the serving E-DCH
cell. The UE can receive serving RGCH from such cells and perform softer
combination. That is, the cells in the serving E-DCH RLS and the serving E-DCH cell
belong to the same NodeB.
l Non-Serving RL: It means cells that belong to the E-DCH active set but to the
serving E-DCH RLS. The UE can receive RGCH from these cells.
The UE can receive the AGCH message from only one cell. This cell is the serving cell of the
HSUPA. According to the protocol, the HSUPA serving cell and HSDPA serving cell for a
subscriber must be the same one. If the best cell in the active set changes due to changes of
the radio environment, the serving cell changes. That is, the serving cell is updated.
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. Figure 7-38 shows the related signaling:
Figure 7-38 Signaling for HSUPA cell update triggered by a 1D event (reported by the monitor
set)
Figure 7-40 Signaling for intra-frequency HHO between two HSUPA cells
Figure 7-42 Signaling for inter-frequency HHO between two HSUPA cells
SHO from a HSUPA cell to a The RNC updates the active set based
non-HSUPA cell on the measurement report, and then
1
allocates the service from the E-DCH to
A 1A, 1C, or 1D event occurs. the DCH through RB reconfiguration.
Intra-frequency HHO from a The RNC allocates the service from the
2 HSUPA cell to a non-HSUPA cell E-DCH to the DCH through RB
A 1D event occurs. reconfiguration.
Figure 7-45 Addition of an R99 cell when the service is on the E-DCH
Figure 7-47 Signaling for intra-frequency HHO from a HSUPA cell to a non-HSUPA cell
Figure 7-49 Signaling for inter-frequency HHO from a HSUPA cell to a non-HSUPA cell
Figure 7-51 SHO from a non-HSUPA cell to a HSUPA cell (triggered by a 1B event)
a DCH to another DCH, and then perform RB reconfiguration from the DCH to the E-DCH in the
HSUPA cell).
Figure 7-53 Signaling for intra-frequency HHO from a non-HSUPA cell to a HSUPA cell
E-DCH. If the E-DCH of the target cell allows setup of the service, the RNC allocates the
service to the E-DCH through RB reconfiguration.
l The switch from the FACH to the E-DCH in the case of traffic increase is rejected by
the HSUPA cell.
l The switch from the DCH to the E-DCH is rejected by the HSUPA cell.
Figure 7-57 Direct retry from a HSUPA cell to another HSUPA cell
l During handover implementation, the UE and network follow the signaling flow and
respond according to signaling.
When dual-mode UE moves at the edge of WCDMA system and might perform inter-RAT
handover, the WCDMA RNC informs UE of starting inter-RAT measurement. After the UE
performs inter-frequency measurement and reports measurement result, the RNC judges
whether to start signaling flow for inter-frequency handover according to measurement result.
The WCDMA system uses code division multiple access (CDMA) technology for access, so the
connected UE in all time works with a specified frequency. When the dual-mode UE needs to
perform inter-RAT measurement and keeps a conversation, it and the WCDMA system might
start compression mode (if the UE has a transceiver, the starting compression mode is
compulsory. If the UE has two transceivers, the UE can test GSM cells without starting
compression mode).
Figure 7-60 shows the tracing signaling of handover from WCDMA to GSM
l The RNC immediately sends the measurement control message, which commands
UE to perform inter-RAT measurement. The message includes measurement
parameters like the list of GSM cells, the information about frequency of cells,
measurement filter coefficient.
l After the handover conditions are met according to judgment, the RNC sends a
SRNS relocation request to CN. The request includes SRNS relocation type (the UE
must participate in inter-RAT handover), reason for SRNS relocation (usually
relocation desirable for radio reasons), source PLMN, source SAI, and target CGI
(including PLMN and LAC).
l After the GSM side allocates related resources, the CN sends RNC the
RELOCATION COMMAND, which includes the IE layer 3 information. The IE
contains the related resources allocated by GSM network.
l The RNC sends UE the HANDOVER FROM UTRAN COMMAND message. The
message includes the RAB ID, activation time, GSM frequency, and GSM messages
in forms of BIT string.
l The UE powers off the transmitter according to GSM configuration, so no signals are
in uplink. Consequently the NodeB sends the SIR ERROR report. This message is
optional in the flow.
l After the UE accesses the GSM network, the CN sends the IU RELEASE
COMMAND message to inform RNC of releasing resources used by UE in the
WCDMA network.
l The RNC immediately sends CN the IU RELEASE COMPLETE message. The
message 16 and message 17 are to release the radio resources of NodeB. What is
different from normal releasing flow is that the air interface does not send the RRC
connection release message, because the UE is using WCDMA network. Therefore
the NodeB releases radio resources without informing UE of the release.
Figure 7-62 shows the tracing signaling of handover from GSM to WCDMA
l The RNC allocates radio resources for the SRNS relocation and configures NodeB
during RL SETUP process. The NodeB start transmitting and receiving radio signals.
l After the NodeB sets up RL, it replies the RL SETUP RESPONSE message.
l The RNC allocates radio resources and other parameter packets. The parameter
packets include U-RNTI, RAB, transport layer information, and physical layer
information. The parameters are configured to UE in three forms:
− Complete configuration: clearly provide parameters in each layer
− Pre-configuration (pre-defined): the system broadcast multiple sets of parameter
templates in the system information 16 and configure template number and necessary
parameter to UE. 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.
l The RNC sends the previous information through the IU interface RELOCATION
REQUEST ACKNOWLEDGE message (in the IE RNC Container) to CN which
forwards the information to the source BSS. The source BSS sends the information
to UE. According to the default parameter identity configured by RNC, the UE
obtains related access parameters in the pre-configuration (default) in the system
information. After this, the UE synchronizes to NodeB directly and later sends data in
uplink.
l After the NodeB detects uplink synchronization, it sends RNC the RL RESTORE IND
message.
l After the RNC receives RL RESTORE IND message sent by NodeB, it sends CN the
RELOCATION DETECT message, indicating that the UE has already handed over
from the 2G network to the 3G network. The message does not contain other
contents.
l The UE sends RNC the HANDOVER TO UTRAN COMPLETE message, indicating
the completion of handover. The message might also contain the encrypted
sequence number and its activation time for each CN field.
l After the RNC receives the HANDOVER TO UTRAN COMPLETE message from UE,
it immediately sends UE the UTRAN MOBILITY INFORMATION message. This
message contains the values of timers used by UE, related information about CN
field, UE ID, and so on.
l After the RNC receives the HANDOVER TO UTRAN COMPLETE message from UE,
it sends UE the UTRAN MOBILITY INFORMATION while it sends CN the
RELOCATION COMPLETE message which contains nothing. After the RNC
receives the confirmation message from UE according to the 17th message, the
handover flow from the 2G network to 3G network is complete. The following
messages are about the measurement control process of UE and NodeB, and about
the UE's query of capacity.
Figure 7-65 shows the tracing signaling of handover from WCDMA to GPRS.
l The UE sends the measured 2D report, indicating the quality of the serving cell is
worse.
l The RNC sends NodeB the RL RECONFIG PREPARE message, indicating NodeB
to prepare for starting compression mode. The message contains the sampling
sequence of compression mode and related parameters of sampling sequence of
compression mode, including TGSN, TGL, TGD, TGPL, compression mode method,
downlink compression frame type, and power control parameters in compression
mode.
l After the NodeB prepares resources, it sends RNC the RL RECONFIG READY
message.
l The RNC sends UE the PHYSICAL CHANNEL RECONFIG message, indicating UE
to prepare for starting compression mode. The message contains TGCFN, TGMP,
TGSN, TGL, TGD, TGPL, RPP, ITP, compression mode method, downlink
compression frame type, and power control parameters in compression mode.
l After the RNC confirms that the UE has received the PHYSICAL CHANNEL
RECONFIG message, it sends NodeB the RL RECONFIG COMMIT message,
indicating the time for start compression mode.
l After the UE completes related configuration according to the new configuration data,
it sends RNC the PHYSICAL CHANNEL RECONFIG COMPLETE message. This
indicates that the compression mode is ready.
l The RNC immediately sends the measurement control and commands UE to
perform inter-RAT measurement. The message contains the list of GSM cells, the
information about frequency of cells, measurement filter coefficient.
l After the conditions are met according to judgment, the RNC originates the SRNS
relocation flow and sends UE the CELL CHANGE ORDER FROM UTRAN message.
The message indicates UE to handover to the GPRS network by originating cell
reselection. The message contains the IEs of target cell like BSIC and BAND IND
(900 or 1800), BCCH ARFCN, and NC mode.
l Because the UE need to reselect a GRPS cell, it powers off the transmitter to
WCDMA network. The NodeB sends the SIR ERROR report, which is optional in the
flow.
l Because the UE need to reselect a GRPS cell, it powers off the transmitter to
WCDMA network. The NodeB sends the RL FAILURE report, which is optional in the
flow.
l After the UE accesses the inter-RAT cell,
− 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.
l The RNC sends CN the SRNC CONTEXT RESPONSE message, indicating the
GTP of each RAB ID and the uplink and downlink sequence number of PDCP.
l The CN sends RNC the SRNS DATA FORWARD COMMAND message, indicating
user plane to transmit data. By the message, the CN informs RNC of target transport
layer address and tunnel ID of each RAB data forward.
l After data is transmitted, the CN sends RNC the IU RELEASE COMMAND message,
indicating RNC to release the sources of the UE.
l The RNC sends CN the IU RELEASE COMPLETE message. The message 18 and
message 19 are to release the radio resources of NodeB. What is different from
normal releasing flow is that the air interface does not send the RRC connection
release message, because the UE is using WCDMA network. Therefore the NodeB
releases radio resources without informing UE of the release.
Figure 7-66 Signaling flow for handover from GPRS to WCDMA (1)
Figure 7-67 Signaling flow for handover from GPRS to WCDMA (2)
l After the RNC connection is set up, the UE initiatively originates the INIT DT process
and sets up the SCCP connection at IU interface and the signaling connection in the
CN NAS layer. Later the UE NAS layer and CN NAS layer exchange messages by
DT process.
l The CN commands the RNC to allocate related resources by sends the RAB
ASSIGNMENT REQUEST message at the IU interface. The message contains the
RAB ID, QoS, uplink and downlink sequence number of GPT-U, and sequence
number of PDCP.
l The RNC allocates related resources and informs NodeB by sending RL SETUP
message.
l The RNC sends UE the RB SETUP REQUEST message to UE. The message
contains the downlink sequence number of PDCP.
l The UE sends RNC the RB SETUP COMPLETE message. The message contains
the downlink sequence number of PDCP. The RNC configure the uplink sequence
number of PDCP from CN and the downlink sequence number from UE to the PDCP
sample corresponding to the specified RAB.
l While the traffic flow is being restored, the RNC PDCP sample should drop CN' data
packet of which the sequence number of downlink PDCP is smaller than the
sequence number of downlink PDCP replied by UE. The UE should drop the data
packet of which the sequence number of uplink PDCP is smaller than the sequence
number of uplink PDCP configured by UTRAN/CN.
Set cells by
executing
The individual
ADD
offset of
INTERRATN
inter-RAT
CELL, query
handover cells.
cells by
The UE uses it
executing
with the initial
CellIndividalOffset 0 LST Cell
measured value
INTERRATN
of the cell as the
CELL, and
measurement
modify it by
result for
executing
handover
MOD
judgment of UE.
INTERRATN
CELL
& Note:
Table 7-7 lists the starting/stopping threshold of compression mode and inter-RAT 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.
l Add the corresponding LAI record and the corresponding 3G MSC/VLR code. LAI =
MCC + MNC + LAC. Select Near VLR area as the property of location area.
l Change the supported MAP version to PHASE 2PLUS in the MAP function flow
configuration table.
l Configure the data at the MTP layer and guarantee the signaling transmission
between the 2G MSC and the 3G MSC.
l Configure the data at the SCCP layer, configure the corresponding record of the 3G
MSC in the GT list, SCCP SSN list, and SCCP DSP list, and guarantee the
transmission of MAP handover-related signaling between MSCs.
l Configure inter-MSC trunk data like configuring common data.
The following paragraphs take Huawei 2G MSC as example. For the MSC, two tables are used
for data configuration: location area cell table and neighbor cell table.
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
l Configuring Target 3G Cells as the Inter-RAT Neighbor Cell of GSM
Configuring target 3G cells as the inter-RAT neighbor cell of GSM proceeds as below:
− Select setting cells dynamically
& Note:
The target cell for handover from the 3G network can be the directional neighbor cell of GSM
only.
The configuration table for 3G system information includes the following parameters:
− Type of measurement reports: common measurement reports
− Number of best cells in the GSM band: the default value is 3
− 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.
− Other default values
l Configuring 2G Handover Parameters
Figure 7-73 shows the parameter configuration table for inter-RAT handover.
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.
l Necessary Data Configuration for RNC
Data Configuration for Supporting Roaming from WCDMA to GSM/GPRS
To support the roaming from WCDMA to GSM/GPRS, the UTRAN must complete
sending the following system information:
− Add GSM cells and configuration the following data:
MCC
MISSING NEIGHBOR CELL
LAC
CELL ID
NCC
BCC
FREQ_BAND
Frequency number
CIO
ADD GSMCELL: MCC="460", MNC="10", LAC="0x0fa0", CID="0x0102",
NCC=0, BCC=0, BCCHARFCN=60, BANDIND=DCS1800_BAND_USED,
RATCELLTYPE=GSM;
ADD INTERRATNCELL: CELLID=123, MCC="460", MNC="10", LAC="0x0fa0",
CID="0x0102", CELLINDIVIDALOFFSET=50, QOFFSET1SN=-50,
QRXLEVMIN=-58;
− Configure the measurement point for FACH to inter-frequency FDD measurement,
inter-frequency 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.