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
Product name
WCDMA RNP
Product version
Confidentiality level
For internal use only
Total 201 pages
3.3
Prepared by
Reviewed by
Reviewed by
Date
Jiao Anqiang
Xie Zhibin, Dong Yan, Hu
Wensu, Wan Liang, Yan
Lin, Ai Hua, Xu Zili, and
Hua Yunlong
2006-03-16
Date
Date
Wang Chungui
Approved by
Date
2009-10-10
Page 1 of 201
Revision Records
Date
Version
2005-02-01
2.0
Description
Author
Cai
Jianyong,
According
to
V3.0
guide
handover
problem
optimization
Moving part of call drop due to handover problem
to handover optimization part
Specifying operation-related part to be more
2006-03-16
3.0
2006-04-30
Adding
HSDPA-related
description
2009-10-10
Page 2 of 201
Date
Version
2006-10-30
Description
Author
2007-08-09
2008-12-15
2009-10-10
3.2
3.3
Zhang Hao
WangDekai /
Yearly review
Hu Wensu
Page 3 of 201
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
2008-12-22
Page4 , Total201
2008-12-22
Page5 , Total201
2008-12-22
Page6 , Total201
Figures
Figure 3-1 SHO DT data analysis flow ................................................................................................ 21
Figure 3-2 Optimization flow for HHO CQT ......................................................................................... 26
Figure 3-3 Inter-RAT handover CQT flow............................................................................................ 28
Figure 3-4 DT/CQT flow for HSDPA handover .................................................................................... 31
Figure 3-5 Movement of the MBMS UE between PTM cells ................................................................ 32
Figure 3-6 Analysis flow for handover traffic statistics data.................................................................. 35
Figure 3-7 Voce inter-RAT outgoing handover flow ............................................................................. 38
Figure 4-1 Flow chart for analyzing call drop ...................................................................................... 46
Figure 4-2 Judgment tree for call drop causes .................................................................................... 49
Figure 4-3 Flow for analyzing call tracing............................................................................................ 53
Figure 5-1 SHO relative threshold ...................................................................................................... 57
Figure 5-2 Signaling flow recorded by UE before call drop .................................................................. 58
Figure 5-3 Scrambles recorded by UE active set and scanner before call drop ................................... 59
Figure 5-4 Scrambles in UE active set before call drop ....................................................................... 60
Figure 5-5 UE intra-frequency measurement control point before call drop ......................................... 61
Figure 5-6 Analyzing signaling of UE intra-frequency measurement control before call drop................ 61
Figure 5-7 Confirming missing neighbor cell without information from scanner .................................... 62
Figure 5-8 Location relationship of 2G redundant neighbor cells ......................................................... 64
Figure 5-9 Pilot pollution near Yuxing Rd. ........................................................................................... 65
Figure 5-10 Best ServiceCell near Yuxing Rd. .................................................................................... 65
Figure 5-11 The 2nd best ServiceCell near Yuxing Rd. ....................................................................... 66
Figure 5-12 The 3rd best ServiceCell near Yuxing Rd. ........................................................................ 66
Figure 5-13 The 4th best ServiceCell near Yuxing Rd. ........................................................................ 67
Figure 5-14 Composition of pilot pollution near Yuxing Rd. ................................................................. 67
Figure 5-15 RSSI near Yuxing Rd....................................................................................................... 68
Figure 5-16 RSCP of Best ServiceCell near Yuxing Rd. ...................................................................... 68
Figure 5-17 RSCP of SC270 cell near Yuxing Rd................................................................................ 69
2008-12-22
Page7 , Total201
2008-12-22
Page8 , Total201
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
2008-12-22
Page9 , Total201
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
2008-12-22
Page10 , Total201
Tables
Table 2-1 Handover performance indexes and reference values ......................................................... 16
Table 2-2 HSDPA handover performance indexes and reference value ............................................... 17
Table 2-3 HSUPA handover performance indexes and reference value ............................................... 17
Table 2-4 CDR index and reference value........................................................................................... 19
Table 3-1 SHO failure indexes ............................................................................................................ 36
Table 3-2 HHO failure indexes ............................................................................................................ 36
Table 3-3 Traffic statistics indexes of CS inter-RAT handover preparation failure ................................. 38
Table 3-4 Traffic statistics indexes of PS inter-RAT outgoing handover failure ..................................... 39
Table 4-1 Types of CDR indexes......................................................................................................... 45
Table 4-2 Thresholds of EcIo and Ec .................................................................................................. 46
Table 4-3 Traffic statistics indexes for analyzing causes to call drop .................................................... 51
Table 5-1 Relationship between the filter coefficient and the corresponding tracing time...................... 58
Table 5-2 2G handover times.............................................................................................................. 63
Table 5-3 Best servers and other cells ................................................................................................ 67
Table 7-1 Timers and counters related to the synchronization and asynchronization.......................... 104
Table 7-2 Timers and counters related to call drop at lub interface .................................................... 107
Table 7-3 Flow of serving cell update triggered by different events in SHO ........................................ 132
Table 7-4 Scenarios of handover between HSDPA and R99 (V17) .................................................... 144
Table 7-5 Handover between two HSUPA cells ................................................................................. 158
Table 7-6 Handover between a HSUPA cell and a non-HSUPA cell ................................................... 163
Table 7-7 Parameters of handover from 3G to 2G ............................................................................. 190
2008-12-22
Page11 , Total201
Abstract:
This document, aiming at network optimization of handover success rate and call drop rate, details
the specific network operation flow. In addition, it analyzes common problems during network
optimization.
Full Spelling
AMR
Adaptive MultiRate
CHR
CDR
DCCC
RAN
RNP
SRB
TRB
SHO
Soft Handover
HHO
Hard Handover
PCH
Physical Channel
CN
Core Network
O&M
MNC
MCC
LAC
CIO
HSUPA
E-DCH
E-AGCH
2008-12-22
Page12 , Total201
E-RGCH
2008-12-22
Page13 , Total201
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:
l
Actually handover is closely relevant to call drop. Handover failure probably leads to call drop.
Therefore handover-caused call drop is arranged in handover success rate optimization part.
The CDR optimization includes all related to call drop except handover-caused call drop.
This document does not include usage of related tools.
This document includes the following 12 chapters:
l
1 Introduction
5 FAQs Analysis
6 Summary
7 Appendix
2008-12-22
Page14 , Total201
The traffic statistics analysis is based on RNC V1.5 counter. It will be updated upon the update
of RNC counters.
2008-12-22
Page15 , Total201
Index
Service
Statistics method
CS&PS
DT&Stat.
99%
Voice
DT&Stat.
90%
VP
DT&Stat.
85%
PS UL64K/DL 64K
DT&Stat.
85%
PS UL64K/DL 144K
DT&Stat.
80%
PS UL64K/DL 384K
DT&Stat.
75%
Voice
DT&Stat.
92%
VP
DT&Stat.
90%
PS UL64K/DL 64K
DT&Stat.
90%
PS UL64K/DL 144K
DT&Stat.
87%
PS UL64K/DL 384K
DT&Stat.
85%
DT&Stat.
95%
PS handover out
DT&Stat.
92%
SHO ratio
N/A
DT
35%
SHO cost
N/A
Stat.
40%
Intra-frequency
success rate
Inter-frequency
success rate
Inter-RAT
success rate
2008-12-22
HHO
HHO
handover
Page16 , Total201
Table 2-2 lists the HSDPA handover performance indexes and reference value.
Service
Reference value
PS (HSDPA)
99%
PS (HSDPA)
92%
PS (HSDPA)
99%
PS (HSDPA)
90%
PS (HSDPA)
85%
PS (HSDPA)
92%
HSDPA-HSDPA
serving cell update
intra-frequency
HSDPA-HSDPA
serving cell update
inter-frequency
Note: The HSDPA handover KPIs are to be updated after formal issue by WCDMA&GSM Performance
Research Department.
Service
Reference value
PS (HSUPA)
PS (HSUPA)
Success rate of
DCH-to-E-DCH
reconfiguration in SHO
mode (including replacing
and deleting)
PS (HSUPA)
Success rate of
E-DCH-to-DCH
reconfiguration in SHO
mode (including replacing
and deleting)
PS(HSUPA)
PS (HSUPA)
2008-12-22
Page17 , Total201
Service
PS (HSUPA)
Success rate of
DCH-to-E-DCH
reconfiguration in single-link
mode (the second step of
inter- or intra-frequency
HHO from a non-HSUPA
cell to a HSUPA cell)
PS (HSUPA)
PS (HSUPA)
Success rate of
inter-frequency HHO from a
HSUPA cell to a
non-HSUPA cell
PS (HSUPA)
Success rate of
HSUPA-to-GPRS inter-RAT
handover
PS (HSUPA)
92%
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
2008-12-22
Page18 , Total201
CDR
Service
Statistics
method
Reference
value
Voice
DT&Stat.&CQT
2%
VP
DT&Stat.&CQT
2.5%
PS planned full
coverage rate
DT&CQT
3%
DT
3%
PS
Stat.
10%
PS (UL HSUPA/DL
HSDPA)
DT
3%
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.
2008-12-22
Page19 , Total201
2008-12-22
Page20 , Total201
2008-12-22
Page21 , Total201
Check the active set Ec/Io recorded by UE before call drop and Best Server Ec/Io
recorded by Scanner. Check whether the Best Server scramble recorded by
Scanner is in the neighbor cell list of intra-frequency measurement control before call
drop. The cause might be intra-frequency missing neighbor cell if all the following
conditions are met:
If the UE reconnects to the network immediately after call drop and the scramble of
the cell that UE camps on is different from that upon call drop, missing neighbor cell
is probable. Confirm it by measurement control (search the messages back from call
drop for the latest intra-frequency measurement control message. Check the
neighbor cell list of this measurement control message)
Missing neighbor cell causes call drop. Redundant neighbor cells impacts network performance
and increases the consumption of UE intra-frequency measurement. If this problem becomes
more serious, the necessary cells cannot be listed. Therefore pay attention to redundant
neighbor cells when analyzing handover problems. For redundant neighbor cells, see 5 .
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 "excessive"
When judging whether excessive pilots exist at a point, the pilot number is the
judgment criteria. If the pilot number is more than a threshold, the pilots at a point
are excessive. Namely,
(Th + 1)
N
the No.
strong pilot is smaller than a threshold, no best server strong
enough exists in the point. Namely,
2008-12-22
Page22 , Total201
Based on previous descriptions, pilot pollution exists if all the following conditions are met:
l
is more
Th
than N .
l
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.
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.
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.
2008-12-22
Page23 , Total201
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.
For abnormal equipment, consult customer service engineer for abnormal equipment
and transport layer on alarm console. If alarms are present on alarm console,
cooperate with customer service engineers.
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.
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.
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.
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
2008-12-22
Page24 , Total201
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
2008-12-22
Page25 , Total201
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:
l
The compression mode starts before inter-frequency or inter-RAT handover. Measure the
quality of inter-frequency or inter-RAT cell by compression mode. Compression mode
starts if the CPICH RSCP or Ec/Io meets the conditions. RSCP is usually the triggering
condition.
The parameter "inter-frequency measurement quantity" decides to use CPICH Ec/No or
Ec/Io as the measurement target for inter-frequency handover. When setting
"inter-frequency measurement quantity", check that the cell is at the carrier coverage
edge or in the carrier coverage center. If intra-frequency neighbor cells lie in all direction
of the cell, the cell is defined as in the carrier coverage center. If no intra-frequency cell
lies in a direction of the cell, the cell is defined as at the carrier coverage edge.
2008-12-22
Page26 , Total201
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
For Ping-pong HHO problems, solve them by increasing HHO hysteresis and delay trigger time.
The intra-frequency HHO optimization is similar to that of inter-frequency. Decrease the
hysteresis and delay trigger time of 1D event according to local radio environment to guarantee
timely handover.
2008-12-22
Page27 , Total201
Data Configuration
Inter-RAT handover fails due to incomplete configuration data, so pay attention to the following
data configuration.
l
Frequency number
2008-12-22
Page28 , Total201
Add location area cell information near 2G MSC to location area cell list of 3G MSC.
The format of location area identity (LAI) is MCC + MNC + LAC. Select LAI as LAI
type. Select Near VLR area as LAI class and add the corresponding 2G MSC/VLR
number. The cell GCI format is: MCC + MNC + LAC + CI. Select GCI as LAI type.
Select Near VLR area as LAI class and add the corresponding 2G MSC/VLR
number.
Add data of WCDMA neighbor cells on GSM BSS. The data includes:
Downlink frequency
Primary scramble
Main indicator
MCC
LAC
RNC ID
CELL ID
Causes
The causes to call drop due to 3G-2G inter-RAT handover are as below:
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.
Handset problems causes call drop. For example, the UE fails to hand over back or
to report inter-RAT measurement report.
Improperly configured LAC causes call drop (solve it by checking data configuration).
2008-12-22
Page29 , Total201
According to different technologies used in the serving cell before and after handover, HSDPA
handover includes:
l
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.
2008-12-22
Page30 , Total201
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.
Whether the protection time length of HSDPA handover is proper. Now the baseline
value is 0s. Set it by running SET HOCOMM.
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.
Whether the protection time length of D2H handover is proper. Now the baseline
value is 2s. Set it by running SET HOCOMM.
2008-12-22
Page31 , Total201
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
2008-12-22
Page32 , Total201
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
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.
Guarantee that the transmission time difference of the UE between different links
meets the requirement of soft combing or selective combining*.
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
2008-12-22
Page33 , Total201
2008-12-22
Page34 , Total201
Check the SHO success rate of entire network and cell in busy hour. If they are not
qualified, analyze the problematic cells in details.
Sort the SHO (or softer handover) failure times of the cell by TOP N and locate the
cells with TOP N failure times. List the specific indexes of failure causes. If locating
specific causes from traffic statistics is impossible, analyze the corresponding CHR.
Table 3-1 lists the detailed traffic statistics indexes to SHO (or softer handover) failure
and analysis.
2008-12-22
Page35 , Total201
Analysis
Configuration nonsupport
The UE thinks the content of active set update for RNC to add/delete links
does not support SHO. This scenario seldom exists in commercial networks.
Synchronization
reconfiguration
nonsupport
The UE feeds back that the SHO (or softer handover) for RNC to add/delete
links is incompatible with other subsequent processes. The RNC
guarantees serial processing upon flow processing. This cause is due to the
problematic UE.
Invalid configuration
The UE thinks the content of active set update for RNC to add/delete links is
invalid. This scenario seldom exists in commercial networks.
No response from UE
The RNC fails to receive response to active set update command for
adding/deleting links. This is a major cause to SHO (or softer handover)
failure. It occurs in areas with weak coverage and small handover area. RF
optimization must be performed in the areas.
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 .
Upon HHO failure, pay attention to indexes related to internal NodeB, between NodeBs, and
between RNCs.
Table 3-2 lists the HHO failure indexes.
Analysis
Other causes
Configuration
nonsupport
PCH failure
Synchronization
reconfiguration
nonsupport
2008-12-22
Page36 , Total201
Cell update
Cell update occurs upon outgoing HHO. These two processes lead to
outgoing HHO failure.
Invalid configuration
Other causes
2008-12-22
Page37 , Total201
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.
Analysis
SRNS relocation
cancellation
The previous two cases, despite incomplete handover, are normal nesting
flows.
SRNS relocation
expiration
SRNS relocation
failure in target
CN/RNC/system
2008-12-22
Page38 , Total201
target
Unavailable
resource
Other causes
SRNS relocation
failure in target
CN/RNC/system
SRNS relocation
nonsupport
in
target
CN/RNC/system
Other causes
PCH failure
Other causes
Analyze the problem further according to CHR logs and CN/BSS signaling
tracing.
Analysis
PCH failure
Radio
network
layer cause
Transport
cause
2008-12-22
layer
Page39 , Total201
You must analyze the causes according to CN and BSS signaling tracing.
HSDPA-GPRS switch
In the DCCC or RAB MODIFY process, if the RNC decides to switch the channel in the
cell, it sends the UE the RF RECONFIGURATION message. According to the channel
state of the UE before and after reconfiguration, the RNC counts the previous indexes in
the HSDPA serving cell.
2008-12-22
Page40 , Total201
In the DCCC or RAB MODIFY process, if the RNC decides to switch the channel in the
cell, it sends the UE the RF RECONFIGURATION message. According to the channel
state of the UE before and after reconfiguration, the RNC counts the attempt times of
switch from DCH to HS-DSCH in the HSDPA serving cell. In the DCCC or RAB
MODIFY process, if the RNC receives the RB RECONFIGURATION COMEPLTE
message from UE, and the reconfiguration enables UE to switch from the DCH to
HS-DSCH in the same cell, the RNC counts the successful times of switch from DCH to
HS-DSCH in the HSDPA serving cell.
l
The traffic statistics does not include the index, and the index will be supplemented later.
The causes to failure and analysis methods will be summarized later.
Success rate of SHO between HSUPA cells (including adding, replacing, and
deleting) = attempt times of active set update/complete times of active set update.
Success rate of SHO serving cell update between HSUPA cells = successful times
of SHO serving cell update/attempt times of SHO serving cell update.
2008-12-22
Page41 , Total201
Success rate of reconfiguration from E-DCH to DCH in the cell (including adding and
replacing) = successful times of handover from E-DCH to DCH in SHO
mode/attempt times of handover from E-DCH to DCH in SHO mode.
Success rate of intra-frequency HHO serving cell between HSUPA cells = successful
times of intra-frequency HHO serving cell between HSUPA cells/attempt times of
intra-frequency HHO serving cell between HSUPA cells.
Success rate of intra-frequency HHO from E-DCH to DCH from a HSUPA cell to a
non-HSUPA cell = successful times of intra-frequency HHO from E-DCH to
DCH/attempt times of intra-frequency HHO from E-DCH to DCH.
Success rate of inter-frequency HHO serving cell update between HSUPA cells =
successful times of inter-frequency HHO serving cell update between HSUPA
cells/attempt times of inter-frequency HHO serving cell update between HSUPA
cells.
2008-12-22
Page42 , Total201
2008-12-22
Page43 , Total201
The RRC Release message with the release cause Not Normal.
After the service is set up, the RNC sends CN the RAB RELEASE REQUEST
message.
After the service is set up, the RNC sends CN the IU RELEASE REQUEST
message. Afterwards, it receives the IU RELEASE COMMAND sent by CN.
Upon statistics, sort them by specific services. Meanwhile, traffic statistics includes the cause to
release of RAB of each service by RNC.
CS CDR is calculated as below:
CS _ CDR =
CSRabrelTriggedByRNC *100%
CSRABSetupSuccess
2008-12-22
Page44 , Total201
PS _ CDR =
PSRabrelTriggedByRNC *100%
PSRABSetupSuccess
Cause
RF
Due to air
interface
Expiration
of process
timer
Hardware
failure
Not due to
air
interface
Transport
layer failure
Subscribers
are
released by
force
by
MML
O&M intervention
The definition of RAN traffic statistics call drop is according to statistics of lu interface signaling,
including the times of RNC's originating RAB release request and lu release request. The DT
call drop is defined according to the combination of messages at air interface and from
non-access lay and cause value. They are inconsistent.
2008-12-22
Page45 , Total201
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).
2008-12-22
Bit rate of
service
12.2
DL EbNo
8.7
EcIo
thresholds
13.3
Ec thresholds
103.1
Page46 , Total201
CS 64
64
5.9
11.9
97.8
PS 64
64
5.1
12.7
98.1
PS 128
128
4.5
13.3
95.3
PS 384
384
4.6
10.4
90.6
Uplink or downlink DCH power helps to confirm the weak coverage is in uplink or downlink by
the following methods.
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.
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
The over great indoor penetration loss causes weak coverage. Incorrectly configured sectors or
disabling of NodeB will occur, so at the call drop point, the coverage is weak. You must
distinguish them.
Interference
Both uplink and downlink interference causes call drop.
In downlink, when the active set CPICH RSCP is greater than 85 dBm and the active set Ec/Io
is smaller than 13 dB, the call drop is probably due to downlink interference (when the
handover is delayed, the RSCP might be good and Ec/Io might be weak, but the RSCP of Ec/Io
of cells in monitor set are good). If the downlink RTWP is 10 dB greater than the normal value
(107 to 105 dB) and the interference lasts for 2s3s, call drop might occur. You must pay
attention to this.
Downlink interference usually refers to pilot pollution. When over three cells meets the handover
requirements in the coverage area, the active set replaces the best cell or the best cell changes
due to fluctuation of signals. When the comprehensive quality of active set is bad (CPICH Ec/Io
changes around 10 dB), handover failure usually causes SRB reset or TRB reset.
Uplink interference increases the UE downlink transmit power in connection mode, so the over
high BLER causes SRB reset, TRB reset, or call drop due to asynchronization. Uplink
interference might be internal or external. Most of scenario uplink interference is external.
Without interference, the uplink and downlink are balanced. Namely, the uplink and downlink
transmit power before call drop will approach the maximum. When downlink interference exists,
2008-12-22
Page47 , Total201
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
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.
2008-12-22
Page48 , Total201
Preparing Data
The data to be prepared include:
l
2008-12-22
Page49 , Total201
If the signals of best server are stable, analyze RSCP and Ec/Io.
If the signals of best server fluctuate sharply, you must analyze the quick variation of
best server signals and the situation without best server. Consequently you can
analyze call drop due to ping-pong handover.
If both RSCP and Ec/Io are bad, call drop must be due to weak coverage.
When the cell in UE active set is inconsistent with the best cell according to scanner, call
drop must be due to missing neighbor cell and delayed handover.
When the cell in UE active set is consistent with the best cell according to scanner, call
drop must be due to uplink interference or must be abnormal.
2008-12-22
Page50 , Total201
After a service is established successfully, the RNC sends CN the RAB RELEASE
REQUEST message.
VS.RAB.Loss.PS.64K / VS.RAB.SuccEstPS.64
VS.RAB.Loss.PS.128K / VS.RAB.SuccEstPS.128
VS.RAB.Loss.PS.384K / VS.RAB.SuccEstPS.384
Based on analysis of previous indexes, you can obtain the performance of various services and
rates in the network, as well as SHO/HHO call drop. More important, you can obtain the cells
with bad indexes and periods.
Table 4-3 Traffic statistics indexes for analyzing causes to call drop
Failure cause
Analysis
OM interference
Causes due
preemption
RAB
The causes due to UTRAN in the cell lead to abnormal release of link. This
corresponds to abnormal process, so you must further analyze it based on
CHR.
Uplink RLC reset causes release of links, because the coverage quality
(including missing neighbor cell and over mall handover area) is bad.
Downlink SRB reset causes release of links, because the coverage quality
(including missing neighbor cell and over mall handover area) is bad.
Uplink
failure
2008-12-22
synchronization
Page51 , Total201
Downlink synchronization
failure
No response of UU port
Other RF causes
Abnormal GTPU
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.
UE transmit power
Uplink BLER
2008-12-22
Page52 , Total201
The former corresponds to call drop caused by TRB reset. The latter corresponds to call drop
caused by SRB reset. By searching for the previous two messages, you can obtain the call drop
time and the signaling message before call drop for further analysis.
2008-12-22
Page53 , Total201
Measurement control
RB reset
Measurement report
RB reconfiguration complete
Confirm that the UE receives these messages by tracing messaged at RNC side.
2008-12-22
Page54 , Total201
Abrupt breakdown of UE
Analyze abnormal transmission by analyzing CHR or checking alarms. Confirm that the NodeB
equipment is abnormal by querying NodeB state. Locate abnormal UE problems by analyzing
data recorded by UE.
2008-12-22
Page55 , Total201
FAQs Analysis
Analysis
Analyze the relative threshold of 1A and 1B event, namely, reporting range.
Figure 5-1 shows the SHO relative threshold
2008-12-22
Page56 , Total201
PCPICH 1
PCPICH 2
Reporting
range
Reporting
terminated
Periodic
report
Periodic
report
Event-triggered
report
PCPICH 3
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.
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.
2008-12-22
Page57 , Total201
Table 5-1 Relationship between the filter coefficient and the corresponding tracing time
Filter coefficient
11
Intra-frequency
tracing time (s)
0.2
0.4
0.6
1.4
4.2
8.4
17
The distance between sites in dense urban areas is short and the handover time is short, so
you must reduce the tracing time, namely, the filter coefficient. The value 2 is usually proper for
filter coefficient of layer 3.
2008-12-22
Page58 , Total201
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.
2008-12-22
Page59 , Total201
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.
2008-12-22
Page60 , Total201
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:
2008-12-22
Page61 , Total201
Confirm the scrambles of all cells in active set and the scrambles of cells in monitor
set measured by UE before call drop.
Compare the scramble information of the cell where the UE camps on after
reselection after call drop and the scrambles in UE active set and monitor set before
call drop.
If the former scramble is not in the scramble list of active set and monitor set before
call drop, the call drop is probably due to missing neighbor cell.
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.
2008-12-22
Page62 , Total201
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.
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.
NCELL
HOCOUNT
12531
10121
417
12531
10161
3262
12531
10162
2070
12531
10301
381
12531
10321
265
12531
12061
12531
12101
961
12531
12111
16
12531
12251
12531
12291
12531
12292
12531
12330
1082
12531
12391
1063
12531
12451
17019
12531
12532
16030
12531
12540
74
12531
12591
926
12531
12592
20994
12531
14051
12531
14072
12531
14091
211
12531
14111
2008-12-22
Page63 , Total201
12531
14460
321
12531
56361
16
12531
56362
12531
56820
12531
56910
206
Search for the neighbor cells with few handover times and even no handovers, such as cell
1253112292. 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.
2008-12-22
Page64 , Total201
Figure 5-9 shows the pilot pollution point near Yuxing Rd. SC270 cell is planned to
cover the area with pilot pollution.
Figure 5-9 Pilot pollution near Yuxing Rd.
2008-12-22
Page65 , Total201
2008-12-22
Page66 , Total201
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.
Table 5-3 Best servers and other cells
Best ServiceCell
Primary
Others
SC220
SC270
3 best ServiceCell
SC200
SC200
rd
2008-12-22
Page67 , Total201
Figure 5-16 shows the RSCP of Best ServiceCell near Yuxing Rd..
Figure 5-16 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
Figure 5-17 shows the RSCP of SC270 cell near Yuxing Rd.
2008-12-22
Page68 , Total201
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.
2008-12-22
Page69 , Total201
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.
2008-12-22
Page70 , Total201
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.
2008-12-22
Page71 , Total201
cell56 vs cell041
EcNo
0
-10
cell56
cell041
-20
-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
2008-12-22
Page72 , Total201
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.
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).
2008-12-22
Page73 , Total201
If the needlepoint lasts for a short period, unable to meet the handover conditions
and to affect call drop, it will lead to deterioration of quality of service (QoS), such as
over great BLER exists in downlink.
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.
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.
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.
2008-12-22
Page74 , Total201
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.
2008-12-22
Page75 , Total201
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:
l
Ho Failure
TRB Reset
To sole the problem, optimize RF engineering parameters and 1D event parameters to avoid
ping-pong handover.
2008-12-22
Page76 , Total201
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.
2008-12-22
Page77 , Total201
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
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
2008-12-22
Page78 , Total201
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.
2008-12-22
Page79 , Total201
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.
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).
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).
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.
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.
2008-12-22
Page80 , Total201
Solutions
In network optimization, the operator can take the following adjustment:
l
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.
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.
2008-12-22
Page81 , Total201
The start parameters in compression mode and reselection threshold from the 2G
network to the 3G network is adjusted.
Solutions
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
2008-12-22
Change the cell independent offset (CIO) in the GSM neighbor cell from 0 dB to 5 dB.
The UE hands off to the GSM cell more easily. Call still drops in test.
Change 2D RSCP Threshold from 95 dBm to 85 dBm to 75 dBm. The inter-RAT
measurement starts earlier. Call still drops in test.
Change GSM RSSI from 90 dBm to 95 dBm. The UE hands off to GSM cells more
easily. Call still drops in test.
Page82 , Total201
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.
Change the cell location property from carrier border to carrier center (the
associated measurement changes from RSCP to Ec/Io). Change 2D Ec/Io Threshold
from 24 dB to 10 dB. Call still drops in test.
Change Inter RAT handover trigger time from 5000ms to 2000ms. The UE performs
inter-RAT more quickly. Call drop is improved.
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
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.
2008-12-22
Page83 , Total201
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.
Example 1:
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.
2008-12-22
Page84 , Total201
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.
10:53:23(29): The RNC sends the Relocation Require message due to the No Resource
Available message.
10:53:23(71): The CN replies the Relocation Failure message due to the No Resource
Available message.
The RNC keeps sending Relocation Require message due to No Resource Available
message until call drop, and is rejected. The actual LAC is 21000. After adjustment, the
UE succeeds in handover.
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
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.
2008-12-22
Page85 , Total201
Example :
l
Delayed Handover
According to signaling of the RNC, a normal inter-RAT handover takes 5s. The following are the
time needed by the RNC, longer than that on UE. If the walking speed is 3 km/h, it takes 45
meters. The time depends on different scenes.
2008-12-22
The NodeB does not report RL failure, but SRB reset occurs.
Page86 , Total201
Other situations: 3G signaling is normal, but actually the call drops. You can only
know whether the UE confronts call drop problems by checking the UE call drop
recorded in test.
Example 1:
l
Moto handset:
15:26:27(87): The RNC sends Physical channel reconfiguration (active set contains
PSC201 and PSC16).
15:26:30(30): The UE report BCCH 844 BSIC Nonverified, and the level is 87 dBm.
15:26:31(26): The UE report BCCH 844 BSIC verified, and the level is 88 dBm.
15:26:32(13): The RNC sends the HO CMD message.
15:26:34(25): The UE sends inter-RAT measurement reports, but does not hand over.
This is because the UE does not receive HO CMD sent by the RNC, or the UE fails in
accessing the 2G network. The CN sends lu Release due to treloccomplete expire
(normally successful relocation causes lu Release, and the UE succeeds in accessing the
2G network).
l
15:26:27(43): The RNC sends Physical channel reconfiguration (active set contains
PSC201 and PSC16).
15:26:30(90): The UE report BCCH 844 BSIC verified, and the level is 79 dBm.
15:26:32(13): The RNC sends HO CMD, and the handover succeeds.
Here is the entrance to parking yard of Taigu Shopping Hall. Before call drop, the Moto handset
indexes as follows:
l
In addition, according to comparison of two terminals, they are different in measuring GSM level
(Qualcomm 6250 uses an external antenna, while Moto A835 uses a built-in camera). This
affects the inter-RAT measurement.
Example 2:
l
Moto handset:
17:08:59(61): The UE sends 2D measurement reports, and the RNC sends Physical
channel reconfiguration.
17:09:00(78): The RNC receives Physical channel reconfiguration completion, and sends
measurement control messages.
17:09:04(35): The NodeB is out of synchronization, so call drop occurs, and no
inter-RAT the measurement report is sent.
17:09:20(89): The RNC originates Iu Release due to Radio Connection with UE lost.
l
17:08:59(29): The UE sends 2D measurement reports, and the RNC sends Physical
channel reconfiguration.
2008-12-22
Page87 , Total201
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.
Example 1:
14:06:18(75): The best server PSC201 report 2D event (meanwhile, PSC16 is in the
active set).
14:06:18(82): The RNC sends Physical channel reconfiguration.
14:06:18(95): The UE reports 1D event of PSC16 cell.
14:06:19(95): The RNC receives Physical channel reconfiguration completion from UE,
and it sends inter-RAT measurement control message of PSC201 cell, and interfrequency and intra-frequency measurement control of PSC16 cell.
14:06:20(94): The UTRAN sends 1B event to the UE to delete PSC 201.
14:06:21(45): The RNC sends inter-RAT measurement control to the cell of PSC16 (3s
delay compared with 1D event).
14:06:22(83): The UE reports the GSM cell 852 (BSIC Verify) according to the new
measurement control, and the RSSI is 79 dBm. The RNC does not process the report (to
prevent UE from handing over to incorrect cell, the RNC must process UE measurement
report 3s after sending new measurement control)
14:06:28(94): NodeB is out of synchronization, so call drop occurs.
Example 2: Qualcomm handset:
14:53:08(63): The UE sends 2D measurement reports, and the RNC sends Physical
channel reconfiguration (the cell 144 is the best server)
14:53:09(67): The RNC receives Physical channel reconfiguration completion, and sends
measurement control messages.
14:53:16(58): The UE sends 1D measurement reports, and cell 137 becomes the best
server. Therefore the RNC sends the measurement control messages of best server 137,
including inter-RAT neighbor cells (the neighbor cell list is different from that of cell
144)
2008-12-22
Page88 , Total201
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?
14:07:37(38): The UE reports BCCH the measurement report of cell 852, Nonverified
BSIC.
14:07:38(38): The TimeToTrigger of Nonverified is 1s, and after 1s, the RNC sends
Relocation to CN.
14:07:38(38): The UE sends BCCH the measurement reports of cell 852, verified BSIC.
14:07:38(74): The CN replies that Relocation Prepare fails (no radio resources).
14:07:38(78): The UE sends the measurement report before failure, so the RNC again
originates Relocation to CN.
14:07:40(12): The CN replies Relocation to RNC, and RNC sends HO CMD to UE.
14:07:40(79): However, the UE replies HO FAIL.
Late, the UE keeps deleting cell 201 which is the best server, so the RNC does not process the
request. The 3G signals are weak, so call drop occurs.
Description:
The UE cannot hand over from the 3G network to the 2G network smoothly. In details,
the UE originates a call in 3G coverage areas or uses PS services, and then enters 2G
coverage areas. However, it fails in handing over to 2G networks, so call drop occurs.
Analyze the signaling process at RNC side, and check the causes to handover failure.
The causes include:
2008-12-22
The network side fails in receiving 2D report from UE, so compression mode is not
started. Consequently 2G cells are not measured, and then asynchronization or
SRB/TRB reset cause call drop.
The network side receives 2D report, but compression mode is not started. The reason
is that the network side sends a PHY_CH_RECFG message, but the UE fails in
sending ACK message or PHY_CH_RECFG_CMP, so SRB is reset, and call drop
occurs.
The network side receives Verified measurement reports. After it sends UE the
handover messages, the UE fails in receiving it, so call drop occurs (also for other
reasons).
Page89 , Total201
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:
Reducing hysteresis
Now the back system can configure different starting threshold of inter-RAT
compression mode for signaling, CS and PS services.
2008-12-22
Page90 , Total201
Scrambles, Ec/Io, and RSCP of cells in active set before call drop
Transmit power of UE, BLER of transport channel, and call drop time
2008-12-22
Page91 , Total201
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.
2008-12-22
Page92 , Total201
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.
2008-12-22
Page93 , Total201
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.
2008-12-22
Page94 , Total201
Solution
Locate the sources of interference t solve uplink interference problems.
Abnormal UE
l
2008-12-22
Page95 , Total201
measurement report of the cell in monitor set, so finally call drop occurs. After the
UE is updated, the problem is solved.
l
2008-12-22
Page96 , Total201
HS-PDSCH
HS-SCCH
HS-DPCCH
When the R99 subscribers have handover problems, the HSDPA subscribers cannot smoothly
hand over. Therefore, when the HSDPA subscribers fail to hand over, engineers need to check
R99 handover. If R99 subscribers have handover problems, solve the problems as previously
mentioned. The call drop problems currently in test is usually caused by R99 problems.
The active set does not list the cells of SC 25 and SC 26. After call drop, the UE camps
on the cell of SC 26. Meanwhile, the quality of signals from the cell of SC 11 declines
sharply.
According to previous description, the call drop is probably due to missing neighbor cell.
For detailed analysis, see 5.1 .
2008-12-22
Page97 , Total201
Solution
While the HHO occurs on ADCH, the HS-PDSCH serving cell is updated.
When the HHO occurs on ADCH:
The maximum transmit power of some R99 UEs and HSDPA UEs are the same, 24 dBm.
l
In test, before call drop the Ec/Io of active set before call drop is below 15 dB, and the
RSCP is below 110 dBm. After call drop, the UE camps on a new cell, where the Ec/Io
is also above 15 dB and RSCP is above 110 dBm. The transmit power of UE before
call drop approaches 24 dBm (terminal is data card E620), so the problems is caused by
weak coverage.
l
Solution
2008-12-22
Page98 , Total201
The signaling flow for HSDPA service handover is more complex than that of R99 service
handover. In some occasions, the handover parameters are differently configured for these two
networks. For example, in turning corner, the UE is required to respond messages from UTRAN
more quickly; in ping-pong handover areas, the protection time is longer.
2008-12-22
Page99 , Total201
2008-12-22
Page100 , Total201
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
The traffic statistics of HSDPA is to be supplemented. HSDPA networks are not commercially
used in a large scale, so more cases will be supplemented.
The SHO ratio analysis will be supplemented after enough RNO experienced are collected.
2008-12-22
Page101 , Total201
Appendix
2009-10-10
Huawei Confidential
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.
SRB1 for all messages sent on the DCCH that uses unconfirmed RLC
SRB2 for all messages sent on the DCCH that uses confirmed RLC (excluding initial
direct transfer and uplink/downlink direct transfer)
SRB3/SRB4 for confirming downlink and uplink direct transfer messages of RLC
transferred on DCCH
The SRB reset involves the SRB in the AM mode. The AM mode uses the
confirmation-retransmission method. The sender will perform polling to check periodically that
the receiver has received the PDU with a method. After sending PDU, the sender sends a
polling frame and waits for the ACK frame from the receiver. If the waiting timer expires and the
sender fails to receive the ACK frame, it keeps sending PDU. If it still fails to receive the ACK
frame after sending for maximum retransmitting times, it triggers RLC AM entity reset or
discards the PDU to be sent. Discarding PCU is not configured now and only triggering RLC AM
entity occurs. This is the RB reset.
During RLC AM entity reset, the sender sends a RESET frame to the receiver and waits for
RESET ACK frame. If the timer expires, the sender will resend the frame. After sending for
maximum retransmission times, the sender will report "unreasonable error" to a high layer and
stop resending. SRB leads to triggering the release process at signaling plane. TRB leads to
triggering the release process at user.
2009-10-10
Huawei Confidential
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
ID
Parameter
Name
Description
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
T302
Timer 302
N302
Constant
302
Content:
This
parameter
indicates
the
maximum
retransmission times of sending CELL UPDATE/URA
UPDATE messages. The default value is 3.
Recommended value: 3
2009-10-10
Huawei Confidential
Timer 312
N312
Constant
312
T313
Timer 313
N313
Constant
313
2009-10-10
Huawei Confidential
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.
T314
Timer 314
T315
Timer 315
N315
Constant
315
Physical unit: s
Content: It indicates the maximum times continuous
synchronization indicators received from L1. The default value
is 1.
Recommended value: D1
2009-10-10
Huawei Confidential
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
Parameter ID
Parameter Name
Description
Value range: 1256
Actual value range: 1256
Physical unit: none
NINSYNCIND
Times of
continuous
synchronization
indicator
NOUTSYNCIND
Times of
continuous
asynchronization
indicator
2009-10-10
Huawei Confidential
TRLFAILURE
2009-10-10
Huawei Confidential
The UE sets up a new radio link through new NodeB and new RNC.
The UE can set up only one link with UTRAN, so there is no macro diversity
combination/splitting.
2009-10-10
Huawei Confidential
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.
2009-10-10
Cell ID
Huawei Confidential
TFS
TFCS
Frequency
Uplink Scramble
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
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)
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.
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.
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.
The SRNC sends UE the Active Set Update message on DCCH. The message
includes content on adding radio link.
The parameters include:
2009-10-10
Update type
Cell ID
Downlink scramble
Adjacent cells
Huawei Confidential
2009-10-10
Huawei Confidential
The SRNC decides to delete a radio link. The SRNC sends UE the Active Set
Update message on DCCH. This message includes the content about deleting radio
link.
The parameters include update type and cell ID.
The UE deactivates the downlink receiver of radio link to be deleted and sends
SRNC the Active Set Update Complete message.
The SRNC sends the Radio Link Deletion Request to DRNC on through.
The parameters include cell ID and transport layer addressing information.
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.
The NodeB deactivates radio resources and sends DRNC the NBAP message,
namely, the Radio Link Deletion Response message.
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 sets up a new radio link through new NodeB and new RNC.
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.
2009-10-10
Huawei Confidential
Figure 7-5 SHO signaling flow for adding and deleting radio link
UE
Node B
Drift RNS
Node B
Serving RNS
Drift
RNC
Serving
RNC
Decision to setup
new RL and
release old RL
RNSAP
NBAP
RNSAP
NBAP
Start RX
description
NBAP
NBAP
RNSAP
DCH-FP
6. Downlink Synchronisation
DCH-FP
7. Uplink Synchronisation
DCH-FP
RNSAP
DCH-FP
Start TX
description
8. DCCH : Active Set Update Command
RRC
RRC
[Radio Link Addition & Deletion]
9. DCCH : Active Set Update Complete
RRC
RRC
NBAP
NBAP
Stop RX and TX
NBAP
NBAP
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
2009-10-10
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
Huawei Confidential
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:
2009-10-10
Cell ID
TFS
TFCS
Frequency
Uplink Scramble
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
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)
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.
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.
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.
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
Adjacent cells
Huawei Confidential
The SRNC 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.
The NodeB deactivates radio resources and sends SRNC the NBAP message,
namely, the Radio Link Deletion Response message.
The SRNC starts releasing lur/lub data bearer thought the ALCAP protocol.
parameters
Layer 1
filtering
Layer 3
filtering
parameters
C
C'
Evaluation
of reporting
criteria
In Figure 7-6,
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.
Point C is the measurement result for event judgment after upper layer filtering.
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,
2009-10-10
Huawei Confidential
From previous measurement model, the filtering occurs before event judgment and
measurement report. In addition, the measured values in cell Measurement results and
Measurement results on RACH of UE's report are filtered. The layer 3 filtering controlled by
network layer caters for measurement event judgment and measurement report only. The cell
reselection when UE is in the idle mode and connection mode does not support layer 3 filter
controlled by network layer.
1.
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
NA
2009-10-10
MBest is the measured value of the best cell in the active set.
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.
Huawei Confidential
Measurement
quantity
P CPICH 1
Reporting
range
P CPICH 2
P CPICH 3
Time-to-trigger
Reporting
event 1A
Time
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.
2009-10-10
Huawei Confidential
PCPICH 1
PCPICH 2
Reporting
range
Reporting
terminated
Periodic
report
Periodic
report
Event-triggered
report
2.
PCPICH 3
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.
NA
NA
MBest is the measured value of the best cell in the active set.
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.
2009-10-10
Huawei Confidential
3.
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.
2009-10-10
Huawei Confidential
4.
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.
2009-10-10
Huawei Confidential
5.
The 1E event triggers measurement report of the cells not monitored when the UE fails to
receive the neighbor cell table.
6.
2009-10-10
Huawei Confidential
2009-10-10
Huawei Confidential
Figure 7-14 Ordinary HHO flow (lur interface and CELL_DCH state)
2009-10-10
The SRNC sends the Radio Link Setup Request message to request radio link setup.
The parameters include target RNC identity, s-RNTI, cell ID, TFS, and TFCS.
The target RNC allocates RNTI and radio resources for RRC connection and radio
links. In addition, it sends the NBAP message, namely, the Radio Link Setup
Request message to the target NodeB.
The parameters include cell ID, TFS, TFCS, frequency, uplink scramble, power
control, and so on.
Huawei Confidential
The target NodeB allocates radio link resources, starts physical-layer receiver, and
sends the target NodeB the Radio Link Setup Response message.
The parameters include signaling termination and transport layer addressing for lub
data transmission and bearer.
The target RNC starts setting up lub data transmission and bearer according to
ALCAP protocol. The request contains that the AAL2 bound ID is for binding lub data
transmission and bearer, as well as transport channel DCH. The NodeB confirms the
request.
When the target RNC completes preparations, it sends SRNC the Radio Link Setup
Response message.
The SRNC starts setting up lub data transmission and bearer according to ALCAP
protocol. The request contains that the AAL2 bound ID is for binding lub data
transmission and bearer, as well as transport channel DCH. The RNC confirms the
request.
When the UE switches from using the original link to using the new one, the original
NodeB detects that the original link fails in synchronization. Then the original NodeB
sends the NBAP message, namely, the Radio Link Failure Indication message to the
source RNC.
The SRNC sends the original SRNC the RNSAP message, namely, the Radio Link
Failure Indication.
When the UE completes setting up RRC connection with target RNC and the related
radio resources are allocated, the UE sends SRNC the RRC message, namely, the
Physical Channel Reconfiguration Complete message.
The SRNC sends source RNC the RNSAP message, the Radio Link Deletion
Request message. This requires the RNC to release the corresponding resources
used by original link.
The source RNC sends original NodeB the NBAP message, the Radio Link Deletion
Request message.
The parameters include cell ID and transport layer addressing information.
The source NodeB releases radio resources used by original link and sends source
RNC the NBAP message, the Radio Link Deletion Response message.
The source RNC starts releasing lur data transmission and bearer according to the
ALCAP protocol.
When the source RNC completes releasing lur data transmission and bearer, it
sends SRNC the RNSAP message, the Radio Link Deletion Response message.
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.
2009-10-10
Huawei Confidential
N ode B
S o u rc e
Node B
T a rg et
RNC
S o u rc e
RAN A P
RNC
T a rg e t
S G S N /M S C
M S C /S G S N
1 . R el oc at io n R e q u ir ed
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
N BA P
N BAP
6 . R a d io L i n k S etu p Re q u est
NBAP
7 . R a d io L i n k S etu p R esp o n se
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
A ck n ow l ed g e
RA N A P
RA N AP
1 0 . Re lo ca ti on R eq u est
A ck n ow l ed g e
RAN A P
1 1 . Re lo ca ti on C o m m a n d
RA N A P
RR C
1 3 . D C C H : P h ysic al C h a n n el R econ fi g u ra t io n N ot e 1
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 4 . R elo ca ti on
D et ect
RR C
RA NA P
RA N A P
1 5 . R elo ca ti on D etec t
RA NA P
RA NA P
N BAP
RR C
1 6 . R a d i o L i n k F a il u re In d ica t io n
RA NA P
N BAP
RRC
RA NA P
1 8 . R e loc a tio n
C om p let e
RA N AP
2 0 . Iu R elea se C om m a n d
RAN A P
RA N AP
RA N A P
2 1 . Iu R ele a se C om m an d
RA N A P
RA NA P
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 AP
2 4 . Iu R elea se C om p le te
RA N A P
RAN A P
2009-10-10
or 2) The SRNC sends the Relocation required message to the nodes of the source
CN and the target CN.
The transmission and bearer at the lur interface is set up at the target RNC and CN.
or 7) or 8) The target RNC allocates RNTI and radio resources for RRC connection
and radio links, and then sends target NodeB the NBAP message, the Radio Link
Setup Request message. The target NodeB allocates radio link resources starts
physical layer receiver, and sends target RNC the NBAP message, the Radio Link
Huawei Confidential
2009-10-10
or 10) When the RNC completes preparations, the RNC sends CN the Relocation
Required Acknowledge message.
or 12) The CN completes preparations and sends SRNC the Relocation Command
message.
The SRNC sends UE the RRC message, the Physical Channel Reconfiguration
message.
or 15) or 16) When the target RNC detects UE, it sends two nodes of CN the
Relocation Detect message. When the UE switches from using the original radio link
to the new one, the source NodeB sends source RNC the Radio Link Failure
Indication message upon detection of RL error by source NodeB.
When the UE completes setting up RRC connection with target RNC and the
corresponding radio resources are allocated, it sends target RNC the RRC message,
the Physical Channel Reconfiguration Complete message.
or 19) After the UE succeeds in handing over to the target RNC and is allocated with
resources, the RNC sends all CNs the Relocation Complete message.
The lu transmission and bearer between the original RNC and CN is released.
or 24) The original RNC sends CN the Lu Release Complete message for confirming
release.
Huawei Confidential
The intra-frequency neighbor cells belong to different RNCs, but no lur interface is
between the RNCs.
The handover of high-speed PS Best Effort service which exceeds the speed
threshold. The reason is that SHO takes excessive forward capacity.
The 1D event is a judgment evidence for the intra-frequency HHO, namely, the triggering cell of
1D event is the target cell for handover.
2009-10-10
Huawei Confidential
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.
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.
2009-10-10
Huawei Confidential
Without violating the coverage handover rules, engineers must give priority to the
HSDPA-supported cells for a service. For example, if multiple radio links are present for SHO,
and only partial cells support HSDPA, the HSDPA service can be used in the non-superior cells.
If the subscriber only for service that is carried on HSDPA, the RNC enable the UE to camps on
HSDPA-supporting cell by direct retry and blind handover.
2009-10-10
Huawei Confidential
Measurement control
Measurement report
Handover judgment
Handover implementation
At measurement control and measurement report stage, the handover messages for HSDPA
are similar to these of R99 and R4.
The signaling related to HSDPA in HSDPA handover includes:
During NBAP:
l
Bearer Re-arrangement
At UU interface:
2009-10-10
Huawei Confidential
Table 7-3 Flow of serving cell update triggered by different events in SHO
Event
Action
2009-10-10
Huawei Confidential
UE-RLC
UE-MAC
UE-L1
Iub/Iur
Node B-L1
Node B -MAC
SRNC-L1
SRNC-MAC
SRNC-RLC
SRNC-RRC
Measurement
CPHY-Measurement-IND
Reporting
criteria
fulfilled
DCCH: MEASUREMENT REPORT
Serving HSDSCH 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)
DCCH: PHYSICAL CHANNEL RECONFIGURATION
CPHY-RL-Modify-REQ
Assume that the parameters like transport channel and radio bearer are fixed.
The update does not involve MAC layer, so the entity of MAC-hs needs no reconfiguration.
The intra-NodeB synchronization serving cell is updated as below:
2009-10-10
When the SRNC decides to update the HS-DSCH serving cell, it sends DRNC the
RADIO LINK RECONFIGURATION PREPARE message. The message contains the
identity of target HS-DSCH serving cell.
The serving NodeB sends the RADIO LINK RECONFIGURATION READY message.
The DRNC sends SRNC the RADIO LINK RECONFIGURATION READY message.
The message contains the following information:
UE ID of HS-DSCH
Huawei Confidential
The SRNC sends DRNC the RADIO LINK RECONFIGURATION COMMIT message.
The message contains the activation time of SRNC in CFN.
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.
Activation time
UE ID of HS-DSCH
2009-10-10
Huawei Confidential
Iur
Iub
DRNC
SRNC
1. RNSAP: RL RECONFIGURATION
PREPARE
2. NBAP: RL RECONFIGURATION
PREPARE
The update process is based on that the DPCH and active set are fixed.
The inter-NodeB synchronization serving cell is updated as below:
2009-10-10
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.
The DRNC sends the source NodeB the RADIO LINK RECONFIGURATION
PREPARE message.
UE ID of HS-DSCH
Huawei Confidential
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.
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.
Activation time
UE ID of HS-DSCH
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
V100R005C01B061):
the
attachment
below
(the
corresponding
RNC
version
is
INTER_NODEB(ok).t
mf
2009-10-10
Huawei Confidential
Figure 7-18 Inter-NodeB HS-DSCH cell update after radio link is added
Uu
Target Node B
Source Node B
Iur
Iub
UE
SRNC
DRNC
7. RNSAP: RL RECONFIGURATION
REQUEST
8. NBAP: RL RECONFIGURATION
REQUEST
Setting a newly-added radio link to HS-DSCH radio link involves two steps:
l
After radio link is added, the inter-NodeB HS-DSCH cell is updated as below:
2009-10-10
The SRNC decides to add new radio link. The radio link will be the HS-DSCH link.
The SRNC sends DRNC the RADIO LINK ADDITION REQUEST message. The
message indicates DRNC to set up a radio link without HS-DSCH resource.
The DRNC allocates resources for the new radio link. It sends the RADIO LINK
SETUP REQUEST message to the target NodeB. The message contains the
information to set up DPCH. It indicates the target NodeB to set up new radio link.
The target NodeB allocates resources. It receives information at the physical layer of
the new DPCH. It responds the RADIO LINK SETUP RESPONSE message.
The DRNC responds the RADIO LINK SETUP RESPONSE message to SRNC. The
DCH transport bearer is set up.
Huawei Confidential
The SRNC sends UE the ACTIVE SET UPDATE message. The message contains
the new radio link ID.
The UE adds the new radio link to active set, and then responds the ACTIVE SET
UPDATE COMPLETE message to SRNC.
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.
UE ID of HS-DSCH
The HS-DSCH transport bearer to target NodeB is set up. The SRNC sends the
RADIO LINK RECONFIGURATION COMMIT message to DRNC. The message
contain the activation time in CFN.
The DRNC sends the RADIO LINK RECONFIGURATION COMMIT message to the
source NodeB and the target NodeB. In the specified activation time, the source
NodeB stops sending HS-DSCH information to UE, and then the target NodeB starts
sending HS-DSCH information to the UE.
2009-10-10
Activation time
UE ID of HS-DSCH
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.
Huawei Confidential
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
UE
Target
DRNC
Iur
Source
DRNC
SRNC
The inter-NodeB HS-DSCH cell during HHO (single step method) is updated as below:
2009-10-10
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.
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.
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
Huawei Confidential
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:
UE ID
Activation time
UE ID of HS-DSCH
In the specified time, the UE deletes the current active set, and sets up DPCH link to
target cell, RESET MAC-hs, and after it synchronize with target cell at the physical
layer, it starts receiving and sending DPCH data, and receiving HS-DSCH data of
target cell. The UE responds the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message to SRNC.
The SRNC sends the RADIO LINK DELETION REQUEST message to source
DRNC. The message indicates the cell to be deleted.
The target DRNC sends the RADIO LINK DELETION REQUEST message to source
NodeB.
The source NodeB releases original radio link resource, and responds the RADIO
LINK DELETION RESPONSE message to source DRNC.
2009-10-10
Huawei Confidential
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
2009-10-10
Huawei Confidential
Figure 7-21 DPCH inter-frequency HHO with HS-DSCH serving cell update
In Figure 7-21,
l
Messages 112143: 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.
HSDPA_INTER_FREQ_
HHO_WITH_TRAFFIC_OK_UE.tmf
2009-10-10
Huawei Confidential
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.
2009-10-10
Huawei Confidential
Scenario
RNC Processing
2009-10-10
Huawei Confidential
Figure 7-24 DPCH SHO with handover from HSDPA to R99 (inter-NodeB)
2009-10-10
Message 19: the UE sends the 1A measurement report to RNC. The report indicates
that the signals from R99 cell are stronger than the signals required by threshold.
Therefore the R99 cell requires being added to active set.
Messages 20, 21, and 22: the RNC sets up a radio link to NodeB.
Messages 2326: the RNC sends UE the active set update message, and the
associated DCH can receive the message in two RLs. After the UE receives the
message, it sends the active set update complete message, which the RNC can
receive in two RLs.
Messages 27 and 28: the network sends UE a new measurement control message,
updated measurement parameters, and neighbor cell list.
Messages 29 and 30: the RNC informs NodeB of perform dedicated measurement in
new link.
Huawei Confidential
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.
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.
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.
2009-10-10
Huawei Confidential
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 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 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.
2009-10-10
Huawei Confidential
RNC_2006-10-30-09
-59-11_H2D SHO.rar
Message 31: the UE reports 1A event, requiring network side to add the link for R99
cell.
Message 32: the network side prohibits SHO and neglects 1A event. The UE reports
1D event.
Messages 3944: R99 HHO occurs, the UE hands over to a new cell.
Figure 7-30 shows the intra-frequency HHO with handover form R99 to R5 (intra-NodeB).
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.
2009-10-10
Huawei Confidential
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 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
2009-10-10
Huawei Confidential
Message 3666: the UE sends measurement report. The report indicates that the
inter-frequency HHO threshold is met. The UE reconfigures the service to be born on
R99 DCH in RB reconfiguration, and then R99 HHO occurs.
2009-10-10
Huawei Confidential
Messages 92121: the UE sends measurement report, and the inter-frequency HHO
threshold is met. The inter-frequency HHO occurs. The service is born on HS-DSCH
in RB reconfiguration in target cell, and the inter-frequency HHO from DCH to
HS-PDSCH is complete.
2009-10-10
Huawei Confidential
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
2009-10-10
Huawei Confidential
In V17, the following types of inter-frequency direct retry of HSDPA are available:
l
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
2009-10-10
Huawei Confidential
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.
l
Suppose an R5 has an inter-frequency R5 cell with the same coverage. The UE that
supports HSDPA originates a request for setup of a service that is fit for HSDPA or
originates an RAB reconfiguration request (channel type) in an R5 cell. If the request is
rejected by the local cell, the request is sent to the other R5 cell through an
inter-frequency direct retry.
l
The current service that is fit for the HS-DSCH is over the DCH for some reason (such
as admission rejection), the UE supports HSDPA but the best cell does not. An
inter-frequency R5 cell with the same coverage is available. In this case, the system
re-allocates the service from the DCH to the HS-DSCH in the inter-frequency R5 cell
with the same coverage if the data traffic of the UE increases (the RNC receives a 4A
event measurement report).
l
The current service that is fit for the HS-DSCH is over the DCH for some reason (such
as admission rejection), the UE supports HSDPA but the best cell does not. An
inter-frequency R5 cell with the same coverage is available. In this case, the system
re-allocates the service from the DCH to the HS-DSCH in the inter-frequency R5 cell
with the same coverage if the channel type fit for service mapping has conflicted with
the type of the current serving channel for a period of time (as specified by the HSDPA
direct retry timer).
To set the expiry time of the timer, run the command SET
COIFTIMER:HRetryTimerLen=5000;.
The signaling is to be supplemented.
2009-10-10
Huawei Confidential
One cause to handover between HS-DSCH and DCH is coverage. This case
includes that UE moves from an R99 cell to a HSDPA cell or from a HSDPA cell to a
R99 cell.
If the service set up by UE fits for HS-DSCH, the RNC triggers switch of channel type after the
HSDPA cell is added to actives set of UE. The RNC reallocate the data service to HS-DSCH.
This is due to mobility of UE.
l
2009-10-10
Huawei Confidential
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.
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.
The following attachment contains D2H switch signaling, according to V17C01B060:
RNC_2006-10-30
-11-31-49_based on trafficrar
l
Scenario 2: The timer triggers D2H switch in the case of inter-frequency direct retry.
See 7.6.10 .
To set the expiry time of the timer, run the command SET
COIFTIMER:HRetryTimerLen=5000;.
The following attachment contains signaling in the case that the timer triggers D2H switch in a
cell, according to V17C01B060:
RNC_2006-10-30
-11-11-05_based on timer D2H.rar
2009-10-10
Huawei Confidential
HSUPA link: Each UE can have only one HSUPA link with the network. Different
from the HSDPA, the HSUPA supports SHO. The HSUPA handover requires
management of the HSUPA serving cell.
DPCH link: The handover functions supported by the DPCH link are the same as
those supported by the R99 system, including SHO, HHO, and handover between
systems
Serving E-DCH Cell: The UE receives AG scheduling from the serving E-DCH cell.
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.
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 all cells in the active set support the HSUPA, the E-DCH bears the uplink services.
In other cases, the DCH bears the uplink services.
If all cells in the active set belong to the SRNC, the E-DCH bears the uplink services.
In other cases, the DCH bears the uplink services (The lur interface in phase 1 of the
product does not support the HSUPA).
For these reasons, if a new cell added to the active set does not support the HSUPA or the new
cell belongs to the DRNC, the channel type changes from the E-DCH to the DCH. In some
cases, the channel type changes from the the DCH to the E-DCH.
2009-10-10
Huawei Confidential
Scenario
Intra-frequency
HSUPA cells
SHO
Rules
between
two
Intra-frequency
HSUPA cells
HHO
between
two
between
two
A 1D event occurs.
Inter-frequency
HSUPA cells
3
HHO
2009-10-10
Huawei Confidential
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
2009-10-10
Huawei Confidential
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)
2009-10-10
Huawei Confidential
Figure 7-40 Signaling for intra-frequency HHO between two HSUPA cells
2009-10-10
Huawei Confidential
Figure 7-42 Signaling for inter-frequency HHO between two HSUPA cells
2009-10-10
Huawei Confidential
Scenario
Rules
2009-10-10
Huawei Confidential
2009-10-10
Huawei Confidential
2009-10-10
Huawei Confidential
Figure 7-45 Addition of an R99 cell when the service is on the E-DCH
2009-10-10
Huawei Confidential
Figure 7-47 Signaling for intra-frequency HHO from a HSUPA cell to a non-HSUPA cell
2009-10-10
Huawei Confidential
2009-10-10
Huawei Confidential
Figure 7-49 Signaling for inter-frequency HHO from a HSUPA cell to a non-HSUPA cell
2009-10-10
Huawei Confidential
Figure 7-51 SHO from a non-HSUPA cell to a HSUPA cell (triggered by a 1B event)
2009-10-10
Huawei Confidential
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
2009-10-10
Huawei Confidential
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.
The RNC carries out handover from a HSUPA cell to a GPRS cell based on the
measurement report from the UE.
2009-10-10
Huawei Confidential
In the R99 cell, the UE originates a service that is fit for the E-DCH.
The traffic of the UE that is over the FACH in the R99 cell increases and the service
is fit for the E-DCH.
A service that should have been set up over the E-DCH according to the service
mapping rules is over the DCH of the R99 cell. The system periodically checks the
services that conflict with the bearer policy and attempts to retry the services to the
E-DCH.
The system periodic measurement uses the HSDPA retry timer (ms). The related MML is SET
COIFTIMER.
2009-10-10
The HSUPA UEs request for setup of the PS service is rejected by the HSUPA cell.
Huawei Confidential
The switch from the FACH to the E-DCH in the case of traffic increase is rejected by
the HSUPA cell.
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
2009-10-10
Huawei Confidential
During the measurement report stage, the UE sends the measurement control
message to the network.
During the handover judgment stage, the network decides to handover according
measurement report.
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).
2009-10-10
Huawei Confidential
Figure 7-60 shows the tracing signaling of handover from WCDMA to GSM
2009-10-10
When the UE moves outwards at the edge of a cell in the WCDMA network and the
conditions for report 2D event meet the RNC configuration, the UE sends a
measurement report of occurrence of 2D event. This report indicates that the signals
at the serving frequency in the WCDMA network are weak and other frequencies or
signals of other systems are required.
Huawei Confidential
2009-10-10
After the NodeB prepares resources, it sends the RL RECONFIG READY message
to the RNC.
The RNC sends PHYSICAL CHANNEL RECONFIG message to UE and prepare for
starting compression mode. This includes the activation time, the sampling
sequence of compression mode and related parameters of sampling sequence of
compression mode. The parameters include TGCFN, TGMP, TGSN, TGL, TGD,
TGPL, RPP, ITP, compression mode method, downlink compression frame type,
and power control parameters in compression mode.
After the RNC confirmed that the UE has received the PHYSICAL CHANNEL
RECONFIG message, it sends NodeB the RL RECONFIG COMMIT message,
indicating the time for NodeB to start compression mode.
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.
The UE sends a measurement report, indicating the BSCI confirmation of GSM cells.
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).
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.
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.
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.
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.
Huawei Confidential
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.
2009-10-10
Huawei Confidential
Figure 7-62 shows the tracing signaling of handover from GSM to WCDMA
2009-10-10
Huawei Confidential
The RNC allocates radio resources for the SRNS relocation and configures NodeB
during RL SETUP process. The NodeB start transmitting and receiving radio signals.
After the NodeB sets up RL, it replies the RL SETUP RESPONSE message.
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:
2009-10-10
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.
Huawei Confidential
2009-10-10
After the NodeB detects uplink synchronization, it sends RNC the RL RESTORE IND
message.
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.
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.
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.
Huawei Confidential
2009-10-10
Huawei Confidential
Figure 7-65 shows the tracing signaling of handover from WCDMA to GPRS.
2009-10-10
Huawei Confidential
2009-10-10
The UE sends the measured 2D report, indicating the quality of the serving cell is
worse.
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.
After the NodeB prepares resources, it sends RNC the RL RECONFIG READY
message.
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.
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.
The UE sends a measurement report, indicating the BSCI confirmation of GSM cells.
Huawei Confidential
2009-10-10
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.
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.
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.
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.
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.
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.
After data is transmitted, the CN sends RNC the IU RELEASE COMMAND message,
indicating RNC to release the sources of the UE.
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.
Huawei Confidential
Figure 7-66 Signaling flow for handover from GPRS to WCDMA (1)
2009-10-10
Huawei Confidential
Figure 7-67 Signaling flow for handover from GPRS to WCDMA (2)
2009-10-10
The UE reselects a UTRAN cell. During the reselection of UTRAN cell, the UE
originates the RRC connection setup process, with the reason INTERRAT
CELLRESELECTION.
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.
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.
The RNC allocates related resources and informs NodeB by sending RL SETUP
message.
The RNC sends UE the RB SETUP REQUEST message to UE. The message
contains the downlink sequence number of PDCP.
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.
Huawei Confidential
2009-10-10
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.
Huawei Confidential
(formula 1)
Wherein,
l
CIO indicates the cell individual offset, namely, the offset configured by the
inter-RAT cell.
After the Trigger-Timer starts and before it expires, the Trigger-Timer is stopped and the network
keeps waiting for receiving inter-RAT measurement report if the following condition is met:
Mother_RAT + CIO < Tother_RAT - H/2
(formula 2)
2009-10-10
Huawei Confidential
Parameter
FilterCoef
Filter coefficient
at layer 3 of
inter-RAT
measurement
D3
GsmRSSICSThd,
GsmRSSIPSThd,
GsmRSSISIGThd
The
judgment
threshold
for
inter-RAT
handover
HystThd
Inter-RAT
handover
hysteresis
4, namely, 2 dB
TimeToTrigForVerify
The
time
to
trigger
delay
verified
by
inter-RAT
0, namely, 0s
TimeToTrigForNonVerify
Non-verified
delay trigger time
65535,
namely,
handover
to
non-verified
GSM
cell is prohibited.
PenaltyTimeForSysHo
Inter-RAT
handover penalty
time
InterRatCSThdFor2DRSCP,
InterRatPSThdFor2DRSCP,
InterRatSigThdFor2DRSCP,
InterRatCSThdFor2FRSCP,
InterRatPSThdFor2FRSCP,
InterRatSigThdFor2FRSCP
2009-10-10
Default
configuration
Meaning
The
starting/stopping
threshold
for
inter-RAT
measurement
with RSCP as the
measurement
value (CS, PS,
and
single
signaling)
Huawei Confidential
MML
Command
s for
modifying
and
querying
Applic
ation
scope
For RNCs:
inter-RAT
handover
algorithm
parameter:
set RNCs by
executing
SET
INTERRATH
O,
query
RNCs
by
executing
LST
INTERRATH
O.
For
cells:
inter-RAT
handover
algorithm
parameter:
add cells by
executing
ADD
CELLINTER
RATHO,
query cells
by executing
LST
CELLINTER
RATHO, and
modify cells
by executing
MOD
CELLINTER
RATHO
For RNCs:
set RNCs by
executing
SET
INTERFREQ
HO
and
query RNCs
by executing
LST
INTERFREQ
HO.
For
RNC/
Cell
RNC/
Cell
cells:
InterRATCSThdFOR2DEcNo,
InterRATPSThdFOR2DEcNo,
InterRATSigThdFOR2DEcNo ,
InterRATCSThdFor2FEcNo,
InterRATPSThdFOR2FEcNo,
InterRATSigThdFOR2FEcNo
The
starting/stopping
threshold
for
inter-RAT
measurement
with Ec/No as the
measurement
value (CS, PS,
and
single
signaling)
24,
dBm
HYSTTHD
Hysteresis. The
hysteresis
and
inter-RAT quality
threshold decides
whether to trigger
inter-RAT
handover
judgment. It can
be smaller in
areas with small
shadow fading. It
can be greater in
areas with great
shadow fading.
CellIndividalOffset
The
individual
offset
of
inter-RAT
handover
cells.
The UE uses it
with the initial
measured value
of the cell as the
measurement
result
for
handover
judgment of UE.
namely,
24
add cells by
executing
ADD
CELLINTER
FREQHO,
query cells
by executing
LST
CELLINTER
FREQHO,
and modify
cells
by
executing
MOD
CELLINTER
FREQHO
Set cells by
executing
ADD
INTERRATN
CELL, query
cells
by
executing
LST
INTERRATN
CELL, and
modify it by
executing
MOD
INTERRATN
CELL
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.
2009-10-10
Huawei Confidential
Add the matching record of 3G MSC/VLR code corresponding to RNC IDs in the list
of cell in the location area. The RNC ID is in the format of: MCC + MNC + LAC +
RNC-ID. Select GCI as the type of location area. Select Near VLR area as the
property of location area.
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.
Change the supported MAP version to PHASE 2PLUS in the MAP function flow
configuration table.
Configure the data at the MTP layer and guarantee the signaling transmission
between the 2G MSC and the 3G MSC.
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.
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.
l
Figure 7-68 shows the data configuration of target 3G cell in the location area cell table.
2009-10-10
Huawei Confidential
GCI code
Figure 7-69 shows the data configuration of neighbor cell configuration table.
2009-10-10
Huawei Confidential
GCI code
Neighbor cells
Fill from the neighbor cell 1 to the neighbor 2. The content to be filled in the
neighbor cell 1 is the LAI + RNC ID of target 3G cell for handover. Query the LAI of
target 3G cell by running the command LST AC. Query the RNC ID by running the
command LST RNCBASIC.
To support the roaming from GSM to WCDMA, the GSM BSS must complete sending
the following system information:
Add the information about inter-RAT cell measurement and roaming control in the
idle mode. The information contains the following parameters:
Qsearch_I: the level threshold for searching for 2G cells in the idle mode
FDD_Qoffset: the level offset of 3G cell reselection
FDD_Qmin: the level threshold of 3G cell reselection
The previous information contained in the system information 2ter and 2quater is sent
to UE.
To support the handover from GSM to WCDMA, the GSM BSS must complete sending
the following system information:
2009-10-10
Huawei Confidential
Primary scramble
Diversity indicator
MCC
MNC
LAC
RNC ID
CELL ID
2009-10-10
Huawei Confidential
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
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 proceeds as below:
2009-10-10
Huawei Confidential
& Note:
The target cell for handover from the 3G network can be the directional neighbor cell of GSM
only.
2009-10-10
Modify the parameters for inter-RAT system information, as shown in Figure 7-72.
Huawei Confidential
The configuration table for 3G system information includes the following parameters:
Threshold for searching for 3G cells in the idle mode: the values range from 0 to 15
Offset of FDD cell reselection: When the mean receiver level of 3G cells is
FDD_Qoffset greater than that of the serving cell, the UE can reselect 3G cells. 0 =
(always select a cell if acceptable), 1 = 28 dB, 2 = 24 dB, , 15 = 28 dB.
Select 0 for easy handover.
The minimum Ec/No threshold for FDD cell reselect: level threshold for 3G cell
reselection: when the receiver level of 3G cell is greater than the FDD_Qmin, the cell
can be a candidate cell for reselection.
Figure 7-73 shows the parameter configuration table for inter-RAT handover.
2009-10-10
Huawei Confidential
2G/3G cell handover priority selection: select 3G cell for handover as priority
2G cell selection threshold: the greater the threshold is, the difficult the handover to
2G is. The recommended value is 63.
RSCP threshold for handover to a better 3G cell: the smaller the value is, the difficult the
handover to 3G is. The recommended value is 10.
Ec/No threshold for handover to a better 3G cell: the smaller the value is, the difficult the
handover to 3G is. The recommended value is 10.
Statistics time for a better 3G cell: the recommended value is 5.
The lasting time for handover to a better 3G cell: the smaller the value is, the easier and
faster the handover is. Pay attention to frequent handover. The recommended value is 4.
l
2009-10-10
Add the cell information about location area near the 2G MSC to the list of cells of
3G MSC location area. LAI = MCC + MISSING NEIGHBOR CELL + LAC. Select
LAI as the type of location area. Select Near VLR area as the property of location
area. Add the corresponding 2G MSC/VLR code. GCI = MCC + MNC + LAC + CI.
Select GCI as the type of location area. Select Near VLR area as the property of
location area. Add the corresponding 2G MSC/VLR code.
If inter-PLMN cell reselection is necessary, the MSC must configure the equivalent
PLMN list: ADD EPLMN, and add the inter-PLMN MCC and MNC. The equivalent
Huawei Confidential
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.
2009-10-10
Configure the SearchRAT of the GSM network by running the command MOD
CELLSELRESEL.
Huawei Confidential
To support the inter-RAT handover from WCDMA to GSM, configure the following
parameters:
2009-10-10
Huawei Confidential