Professional Documents
Culture Documents
W-Handover and Call Drop Problem Optimization Guide-20081223-A-3.3
W-Handover and Call Drop Problem Optimization Guide-20081223-A-3.3
Revision Records
Date Version Description Author
Cai Jianyong,
Completing V2.0 W-Handover and Call Drop
2005-02-01 2.0 Zang Liang, and
Problems.
Jiao Anqiang
According to V3.0 guide requirements, Jiao Anqiang
reorganizing and updating V2.0 guide, focusing
more on operability of on-site engineers. All traffic
statistics is from RNC V1.5. The update includes:
Updating flow chart for handover problem
optimization
Moving part of call drop due to handover problem
to handover optimization part
Specifying operation-related part to be more
applicable to on-site engineers
2006-03-16 3.0
Updating RNC traffic statistics indexes to V1.5
Integrating traffic statistics analysis to NASTAR of
the network performance analysis
Optimizing some cases, adding new cases, and
removing outdated cases and terms
Moving content about handover and call drop to the
appendix, and keeping operations related to them in
the body
Adding explanations to SRB&TRB and RL
FAILURE.
2006-04-30 Adding HSDPA-related description HSDPA Zhang Hao and
handover DT/CQT flow, definitions of traffic Li Zhen
3.1 statistics in HSDPA handover, HSDPA handover
problems. Adding algorithms and flows of HSDPA
handover.
2006-10-30 Adding V17-related handover description as below: Wang Dekai
Changes in signaling flow for H2D HHO
Changes in triggering events of H2D and D2H
D2H handover in HSDPA based on traffic and
3.11
timers
Updating description of HSDPA serving cell and
traffic statistics of HSDPA-DCH handover
Adding call drop indexes in HSDPA DT/statistics
Contents
Figures
Tables
Key words:
Abstract:
This document, aiming at network optimization of handover success rate and call drop rate, details
the specific network operation flow. In addition, it analyzes common problems during network
optimization.
CN Core Network
1 Introduction
This document aims to meet the requirements by on-site engineers on solving handover and
call drop problems and making them qualified during network optimization. It describes the
methods for evaluating network handover and call drop performance, testing methods,
troubleshooting methods, and frequently asked questions (FAQs).
The appendix provides fundamental knowledge, principles, related parameters, and data
processing tools about handover and call drop. This document serves to network KPI
optimization and operation and maintenance (O&M) and helps engineers to locate and solve
handover and call drop problems.
The RRM algorithms and problem implementation in this document are based on V16 RNC. If
some RRM algorithms are based on V17 RNC, they will be highlighted. HSUPA is introduced in
V18 RNC, so the algorithms related to HSUPA are based on RNC V18. The following sections
are updated:
1Introduction
5FAQs Analysis
6Summary
7Appendix
The traffic statistics analysis is based on RNC V1.5 counter. It will be updated upon the update
of RNC counters.
VP DT&Stat. 85%
Intra-frequency HHO
PS UL64K/DL 64K DT&Stat. 85%
success rate
PS UL64K/DL 144K DT&Stat. 80%
VP DT&Stat. 90%
Inter-frequency HHO
PS UL64K/DL 64K DT&Stat. 90%
success rate
PS UL64K/DL 144K DT&Stat. 87%
2.1 lists the HSDPA handover performance indexes and reference value.
HSDPA-HSDPA intra-frequency
PS (HSDPA) 99%
serving cell update
HSDPA-HSDPA inter-frequency
PS (HSDPA) 92%
serving cell update
Note: The HSDPA handover KPIs are to be updated after formal issue by WCDMA&GSM Performance
Research Department.
Note:
The HSUPA handover KPIs are unavailable and to be updated after formal issue by WCDMA&GSM
Performance Department.
Decide the specific value according to project requirements or contract requirements of commercial network
Voice DT&Stat.&CQT 2%
VP DT&Stat.&CQT 2.5%
PS planned full
DT&CQT 3%
coverage rate
PS Stat. 10%
PS (UL HSUPA/DL
DT 3%
HSDPA)
The values listed in 2.2 are only for reference. Decide the specific value according to project
requirements or contract requirements of commercial network.
The call drop rate of HSDPA is not defined yet, so engineers use call drop rate of PS
temporarily.
cell.
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:
− The Ec/Io recorded by UE is bad.
− The Best Server Ec/Io is good.
− No Best Server scramble is in the neighbor cell list of measurement control.
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)
Pilot Pollution
Pilot pollution is defined as below:
Definition of "excessive"
When judging whether excessive pilots exist at a point, the pilot number is the
judgment criteria. If the pilot number is more than a threshold, the pilots at a point
CPICH _ Number > ThN
are excessive. Namely,
Based on previous descriptions, pilot pollution exists if all the following conditions are met:
Set Th RSCP _ Absolute = −95 dBm , Th N = 3 , and Th RSCP _ Re lative = 5dB , the judgment standards
for pilot pollution are:
The number of pilots satisfying CPICH _ RSCP > − 95dBm is larger than 3.
(C P IC H_ R S C 1Pst − C P IC H_ R S C 4Pth ) < 5d B
Delayed handover
According to the signaling flow for CS services, the UE fails to receive active set update
command (physical channel reconfiguration command for intra-frequency HHO) due to
the following cause. After UE reports measurement message, the Ec/Io of original cell
signals decreases sharply. When the RNC sends active set update message, the UE
powers off the transmitter due to asynchronization. The UE cannot receive active set
update message. For PS services, the UE might also fail to receive active set update
message or perform TRB reset before handover.
Delayed handover might be one of the following:
− Turning corner effect: the Ec/Io of original cell decreases sharply and that of the
target cell increases greatly (an over high value appears)
− Needlepoint effect: The Ec/Io of original cell decreases sharply before it increases
and the Ec/Io of target cell increase sharply for a short time.
According to the signaling flow, the UE reports the 1a or 1c measurement report of
neighbor cells before call drop. After this the RNC receives the event and sends the
active set update message, which the UE fails to receive.
Ping-pong Handover
Ping-pong handover includes the following two forms
− The best server changes frequently. Two or more cells alternate to be the best server.
The RSCP of the best server is strong. The period for each cell to be the best server is
short.
− No primary pilot cell exists. Multiple cells exist with little difference of abnormal
RSCP. The Ec/Io for each cell is bad.
According to the signaling flow, when a cell is deleted, the 1A event is immediately
reported. Consequently the UE fails because it cannot receive the active set update
command.
Abnormal Equipment
Check the alarm console for abnormal alarms. Meanwhile analyze traced message, locate the
SHO problem by checking the failure message. For help, contact local customer service
engineers for confirm abnormal equipment.
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.
HHO Types
HHO includes the following types:
Intra-frequency HHO
The frequency of the active set cell before HHO is the same as that of the cell after
HHO. If the cell does not support SHO, HHO might occur. HHO caters for cross-RNC
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.
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.
Balanced load HHO
It aims to realize balanced load of different frequencies. Its judgment depends on
balanced load HHO.
Inter-frequency coverage usually exists in special scenarios, such as indoor coverage, so CQT
are used. The following section details the optimization flow for inter-frequency CQT.
Adjustment
The optimization flow for HHO is similar with that of SHO and the difference lies in parameter
optimization.
Confirming inter-frequency missing neighbor cell is similar to that of intra-frequency. When call
drop occurs, the UE does not measure or report inter-frequency neighbor cells. After call drop,
the UE re-camps on the inter-frequency neighbor cell.
HHO problems usually refer to delayed handover and Ping-pong handover.
Delayed HHO usually occurs outdoor, so call drop occurs when the UE is moving. There are
three solutions:
In the cell at the carrier coverage edge, when UE moves along the direction where no
intra-frequency neighbor cell lies, the CPICH Ec/No changes slowly due to the identical
attenuation rate of CPICH RSCP and interference. According to simulation, when
CPICH RSCP is smaller than the demodulation threshold (–100 dBm or so), the CPICH
Ec/No can still reach –12 dB or so. Now the inter-frequency handover algorithm based
on CPICH Ec/No is invalid. Therefore, for the cell at the carrier coverage edge, using
CPICH RSCP as inter-frequency measurement quantity to guarantee coverage is more
proper.
In the cell in the carrier coverage center, use CPICH RSCP as inter-frequency
measurement quantity, but CPICH Ec/No can better reflect the actual communication
quality of links and cell load. Therefore use CPICH Ec/No as inter-frequency
measurement quantity in the carrier coverage center (not the cell at the carrier coverage
edge), and RSCP as inter-frequency measurement quantity in the cell at the carrier
coverage edge.
In compression mode, the quality of target cell (inter-frequency or inter-RAT) is usually
measured and obtained. The mobility of MS leads to quality deterioration of the current
cell. Therefore the requirements on starting threshold are: before call drop due to the
quality deterioration of the current cell, the signals of the target cell must be measured
and reporting is complete. The stopping threshold must help to prevent compression
mode from starting and stopping frequently.
The RNC can distinguish CS services from PS services for inter-frequency
measurement. If the RSCP is smaller than –95 dBm, compression mode starts. If the
RSCP is greater than –90 dBm, compression mode stops. Adjust RSCP accordingly for
special scenarios.
Increase the CIO of two inter-frequency cells.
Flow Chat
3.1.3 shows the inter-RAT handover CQT flow.
Data Configuration
Inter-RAT handover fails due to incomplete configuration data, so pay attention to the following
data configuration.
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
− MISSING NEIGHBOR CELL
− LAC
− RNC ID
− CELL ID
According to the strategies of unilateral handover of inter-RAT handover, if the data
configuration is complete, the inter-RAT handover problems are due to delayed handover. A
frequently-used solution is increasing CIO, increasing the threshold for starting and stopping
compression mode, increasing the threshold to hand over to GSM.
Causes
The causes to call drop due to 3G-2G inter-RAT handover are as below:
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.
Type
According to the difference of handover on DPCH in HSDPA network, the HSDPA handover
includes:
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).
3.1.4 shows the DT/CQT flow for HSDPA handover.
The problems with handover of HSDPA subscribers are usually caused by the faulty handover
of R99 network, such as missing neighbor cell and improper configuration of handover
parameters. When the R99 network is normal, if the handover of HSDPA subscribers is still
faulty, the cause might be improper configuration of HSDPA parameters. Engineers can check
the following aspects:
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.
The DT/CQT flow for HSUPA handover is similar to that for HSDPA. For details, refer to DT/CQT
Flow for HSDPA Handover.
For the test of HSUPA service coverage and mobility-related tests (such as the test of success
rate of HSUPA serving cell update), perform DT to know the network conditions. For locating
HSUPA problems and the problems unrelated to mobility, perform CQT (in specified spot or
area).
Currently, the radio network controller (RNC) V18 supports only the broadcast mode of the
multimedia broadcast multicast service (MBMS); the MBMS user equipment (UE) moves only
between point-to-multipoint (PTM) cells.
The movement of the MBMS UE between PTM cells is similar to the movement of UE
performing PS services in the CELL-FACH state. The UE performs the handover between cells
through cell reselection and obtains a gain through soft combining or selective combining
between two cells to guarantee the receive quality of the service. The UE first moves to the
target cell and then sends a CELL UPDATE message to notify the serving radio network
controller (SRNC) that the cell where the UE stays is changed. The SRNC returns a CELL
UPDATE CONFIRM message. The UE receives an MBMS control message from the MCCH in
the target cell and determines whether the MBMS radio bearer to be established is consistent
with that of the neighboring cell. If they are consistent, the original radio bearer is retained. The
MBMS mobility optimization, which guarantees that the UE obtains better quality of service at
the edge of cells, covers the following aspects:
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.
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
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.
3.2.1 lists the detailed traffic statistics indexes to SHO (or softer handover) failure and
analysis.
The UE feeds back that the SHO (or softer handover) for RNC to add/delete
Synchronization
links is incompatible with other subsequent processes. The RNC
reconfiguration
guarantees serial processing upon flow processing. This cause is due to the
nonsupport
problematic UE.
The UE thinks the content of active set update for RNC to add/delete links is
Invalid configuration
invalid. This scenario seldom exists in commercial networks.
The RNC fails to receive response to active set update command for
adding/deleting links. This is a major cause to SHO (or softer handover)
No response from UE
failure. It occurs in areas with weak coverage and small handover area. RF
optimization must be performed in the areas.
The HHO traffic statistics includes outgoing HHO success rate and incoming HHO success rate:
Configuration The UE thinks it cannot support the command for outgoing HHO,
nonsupport because it is incompatible with HHO.
PCH failure The cause is probably weak coverage and strong interference.
Synchronization
The UE feeds back HHO is incompatible with other consequent processes
reconfiguration
due to compatibility problems of UE.
nonsupport
Cell update occurs upon outgoing HHO. These two processes lead to
Cell update
outgoing HHO failure.
The inter-RAT handover success rate includes voice inter-RAT handover success rate and PS
inter-RAT handover success rate.
Voice Inter-RAT Outgoing Handover Success Rate = Voice Inter-RAT Outgoing Handover
Success Times/Voice Inter-RAT Outgoing Handover Attempt Times
Voice Inter-RAT Outgoing Handover Success Times: when the RNC sends a RELOCATION
REQUIRED message.
Voice Inter-RAT Outgoing Handover Attempt Times: during CS inter-RAT outgoing, when the
RNC receives an IU RELEASE COMMAND message, with the reason value Successful
Relocation, or Normal Release.
PS Inter-RAT Outgoing Handover Success Rate = PS Inter-RAT Outgoing Handover Success
Times/PS Inter-RAT Outgoing Handover Implementation Times
PS Inter-RAT Outgoing Handover Success Times: the RNC sends a CELL CHANGE ORDER
FROM UTRAN message to UE.
PS Inter-RAT Outgoing Handover Implementation Times: when the RNC receives an IU
RELEASE COMMAND message, with the reason value Successful Relocation, or Normal
Release.
During CS inter-RAT outgoing handover process, when the RNC sends a RELOCATION
REQUIRED message to CN, if the current CS service is AMR voice service, count it as an inter-
RAT handover preparation. When the RNC receives the IU RELEASE COMMAND message
replied by CN, count it as inter-RAT outgoing handover success according to the SRNC cell
being used by UE.
If CS inter-RAT handover fails, check the failure statistics indexes listed in 3.2.3.
The previous two cases, despite incomplete handover, are normal nesting
flows.
SRNS relocation It corresponds to incorrect configuration of CN, so you must analyze the
expiration causes according to CN and BSS signaling tracing.
SRNS relocation
It corresponds to incorrect configuration of CN or BSS nonsupport, so you
failure in target
must analyze the causes according to CN and BSS signaling tracing.
CN/RNC/system
Other causes Analyze the causes according to CN and BSS signaling tracing.
SRNS relocation
It corresponds to incorrect configuration of CN or BSS nonsupport, so you
failure in target
must analyze the causes according to CN and BSS signaling tracing.
CN/RNC/system
SRNS relocation
The BSC fails to support some parameters of inter-RAT handover request,
nonsupport in
so you must analyze the causes according to CN and BSS signaling
target
tracing.
CN/RNC/system
Other causes Analyze the causes according to CN and BSS signaling tracing.
Analyze the problem further according to CHR logs and CN/BSS signaling
Other causes
tracing.
Transport layer
The corresponding transport link is abnormal.
cause
Other causes You must analyze the causes according to CN and BSS signaling tracing.
HSDPA-GPRS switch
The traffic statistics indexes are defined as below:
Success rate of reconfiguration from DCH to E-DCH in the cell (SHO, intra-
frequency HHO, and inter-frequency HHO) = successful times of handover from
DCH to E-DCH/attempt times of handover from DCH to E-DCH.
According to the air interface signaling recorded at the UE side, during connection, DT call drop
occurs when the UE receives:
The RRC Release message with the release cause Not Normal.
A generalized CDR consists of CN CDR and UTRAN CDR. RNO engineers focus on UTRAN
CDR, so the following sections focus on KPI index analysis at UTRAN side.
The related index at UTRAN side is the number of RAB for each service triggered by RNC. It
consists of the following two aspects:
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
PS CDR is calculated as below:
PS _ CDR =
∑ PSRabrelTriggedByRNC *100%
∑ PSRABSetupSuccess
The failure cause indexes are sorted in 4.1.2.
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.
Call drop occurs usually due to handover, which is described in chapter 3. The following
sections describe the call drop not due to handover.
Weak Coverage
For voice services, when CPICH Ec/Io is greater than –14 dB and RSCP is greater than –100
dBm (a value measured by scanner outside cars), the call drop is usually not due to weak
coverage. Weak coverage usually refers to weak RSCP.
4.2.1 lists the thresholds of Ec/Io and Ec (from an RNP result of an operator, just for reference).
Uplink or downlink DCH power helps to confirm the weak coverage is in uplink or downlink by
the following methods.
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:
Lack of NodeBs
Interference
Both uplink and downlink interference causes call drop.
In downlink, when the active set CPICH RSCP is greater than –85 dBm and the active set Ec/Io
is smaller than –13 dB, the call drop is probably due to downlink interference (when the
handover is delayed, the RSCP might be good and Ec/Io might be weak, but the RSCP of Ec/Io
of cells in monitor set are good). If the downlink RTWP is 10 dB greater than the normal value (–
107 to –105 dB) and the interference lasts for 2s–3s, call drop might occur. You must pay
attention to this.
Downlink interference usually refers to pilot pollution. When over three cells meets the handover
requirements in the coverage area, the active set replaces the best cell or the best cell changes
due to fluctuation of signals. When the comprehensive quality of active set is bad (CPICH Ec/Io
changes around –10 dB), handover failure usually causes SRB reset or TRB reset.
Uplink interference increases the UE downlink transmit power in connection mode, so the over
high BLER causes SRB reset, TRB reset, or call drop due to asynchronization. Uplink
interference might be internal or external. Most of scenario uplink interference is external.
Without interference, the uplink and downlink are balanced. Namely, the uplink and downlink
transmit power before call drop will approach the maximum. When downlink interference exists,
the uplink transmit power is low or BLER is convergent. When the downlink transmit power
reaches the maximum, the downlink BLER is not convergent. It is the same with uplink
interference. You can use this method to distinguish them.
Abnormality Analysis
If the previous causes are excluded, the call drop might due to problematic equipment. You
need to check the logs and alarms of equipment for further analysis. The causes might be as
below:
Based on various causes to call drop, the judgment tree for analyzing call drop is as shown in
4.2.3.
Preparing Data
The data to be prepared include:
If the signals of best server are stable, analyze RSCP and Ec/Io.
If the signals of best server fluctuate sharply, you must analyze the quick
variation of best server signals and the situation without best server. Consequently
you can analyze call drop due to ping-pong handover.
If both RSCP and Ec/Io are bad, call drop must be due to weak coverage.
The RNC CDR involves the number of RAB of each service triggered by RNC, including two
aspects:
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.
In traffic statistics analysis, you must analyze the major causes to call drop.
4.3.2 lists the major indexes for analyzing traffic statistics.
Table 1.1 Traffic statistics indexes for analyzing causes to call drop
Failure cause Analysis
OM interference The O&M tasks cause call drop.
The causes due to UTRAN in the cell lead to abnormal release of link. This
Causes due to UTRAN corresponds to abnormal process, so you must further analyze it based on
CHR.
Uplink RLC reset causes release of links, because the coverage quality
Uplink RLC reset
(including missing neighbor cell and over mall handover area) is bad.
Downlink SRB reset causes release of links, because the coverage quality
Downlink RLC reset
(including missing neighbor cell and over mall handover area) is bad.
Other causes You need to analyze the abnormal call drop based on RNC logs.
You can classify the previous indexes 4.3.2 by the classification of previous chapters. They fall
into air interface causes (RF and flow expiration) and not due to air interface causes (hardware
failure, transport failure, and subscribers' interference). Therefore you can have an overall
master of network and obtain the major causes impacting the network.
If the previous KPIs of the cell are normal, check the alarms. By this, you can exclude the
causes due to abnormal cells.
Analyzing traffic statistics indexes helps to expose potential problems. To locate and analyze
problems, you need to use DT and CHR. For problematic cells, the cell-oriented DT is
performed to trace the signaling flow at UE side and of RNC. For details, see 3.1.
UE transmit power
Uplink BLER
You must first trace single subscriber tracing message on RNC or M2000 and then record the
corresponding messages. For detailed tracing methods, see W-Equipment Room Operations
Guide. Usually analyzing call drop problems by message for tracing IMSI is enough.
According to single subscriber tracing messages, the call drop is defined as:
The call drop due to SRB reset is that the UE or RNC fails to receive signaling transmitted in
confirmation mode, and consequently SRT reset occurs, so the connection is released. SRB
reset occurs probably if the UE fails to receive the following messages in downlink:
Measurement control
RB reset
Measurement report
RB reconfiguration complete
Confirm that the UE receives these messages by tracing messaged at RNC side.
TRB reset usually occurs in PS services. It seldom occurs in voice and VP services. Confirm
TRB reset by the UE transmit power upon call drop and downlink code transmit power.
When only one link exists in active set, uplink asynchronization causes RL failure which
consequently causes lu release originated by RNC. Downlink asynchronization causes UE to
power off transmitter, which consequently causes uplink asynchronization. To judge whether
uplink asynchronization or downlink asynchronization causes release, you must analyze the UE
transmit power before call drop and downlink code transmit power monitored in real-time state.
Weak downlink coverage, strong downlink interference or uplink interference causes TRB reset.
If the retransmission times of data services are improperly configured, TRB reset occurs before
SRB reset upon delayed handover. Pay attention to this.
Abnormal call drop can neither be located from coverage and interference nor be explained by
TRB reset or SRB reset. It is caused by abnormal equipment or UE. For example, it might be
caused by the following factors:
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.
When the data is inadequate for locating call drop problems, you must start more detailed data
tracing. The best method is to perform CQT at call drop points to recheck problems for further
analysis.
The cell is in the preliminary congestion state and the channel power of the MBMS service is
reset to the minimum; or the cell is in the over-congestion state and the MBMS service with a
lower priority is released by force. The channel power can, however, be automatically recovered
to the maximum or the service can be re-established through periodic detection.
The UE is at the edge of the cells, and the neighboring cells are not configured for the cell in
which the UE is located. As a result, the UE is unable to obtain a gain through soft combining or
selective combining.
Run the DSP CELLMBMSSERVICE command to query the status of the current MBMS
service. If the MBMS service is not established successfully, the failure cause is displayed.
You can improve the coverage rate by optimizing the RF, adding NodeBs, or adjusting the
antennas. If the coverage does not improve, increase the maximum power of the MBMS traffic
channel. If a neighboring cell is not configured, configure it.
5 FAQs Analysis
5.1.1 Over High SHO Rate due to Improper SHO Relative Threshold
Description
The SHO rate in traffic statistics indexes is over high. More than two cells exist in active set
most of the time during DT and are in SHO state.
Analysis
Analyze the relative threshold of 1A and 1B event, namely, reporting range.
5.1.1 shows the SHO relative threshold
P C P IC H 1
P C P IC H 2
R e p o r t in g
ra n g e
R e p o r t in g
t e r m in a t e d
P e r io d ic P e r io d ic
re p o rt re p o rt
E v e n t - t r ig g e r e d
P C P IC H 3
re p o rt
According to 5.1.1, the greater the reporting range is, the more easily a neighbor cell is listed
into active set and the more difficult it is deleted from active set. This causes over high SHO
rate.
A general method is to configure the threshold of 1A and 1B different. Configure the threshold of
1A event small (such as 3 dB) and keep the threshold of 1B threshold the same (5 dB). In this
way, the cells with bad quality cannot be listed into active set easily and the cells with good
quality can be listed into active set. Therefore the SHO rate is lowered based on normal SHO.
Description
SHO hysteresis is serious in DT: though the signals of a neighbor cell are strong, the cell can be
listed into active set after a long time. If the DT car moves quickly, call drop occurs due to
delayed handover.
Analysis
Layer 3 filter reduces the impact by frequently-fluctuating signals and avoids ping-pong
handover.
The filter of measurement values is calculated as below:
Fn = (1 − a ) ⋅ Fn −1 + a ⋅ M n
Wherein,
Fn: the measurement resulted update after filter is processed.
Fn-1: the measurement result of last point after filter is processed.
Mn: the latest measurement value received in physical layer.
Table 1.1 Relationship between the filter coefficient and the corresponding tracing time
Filter coefficient 0 1 2 3 4 5 6 7 8 9 11
The distance between sites in dense urban areas is short and the handover time is short, so
you must reduce the tracing time, namely, the filter coefficient. The value 2 is usually proper for
filter coefficient of layer 3.
Description
The call drop point is related to signaling flow before call drop.
5.1.3 shows the signaling flow recorded by UE before call drop.
Analysis
Check the pilot test data from UE and scanner at call drop points. 5.1.3 shows the scrambles
recorded by UE active set and scanner before call drop. In 5.1.3, the measurement result of UE
active set and canner is inconsistent and the SC 170 of scanner does not exist in UE active set.
Figure 1.1 Scrambles recorded by UE active set and scanner before call drop
The cause might be missing neighbor cell or delayed handover. Check scrambles in UE active
set. 5.1.3 shows the scrambles in UE active set before call drop. No SC 170 cell exists in UE
monitor set, because this is possibly due to missing neighbor cell.
Continue to check the neighbor cell list sent by RNC to UE before call drop, as shown in 5.1.3
and 5.1.3. According to the latest measurement control before call drop, no SC 170 exists in the
neighbor cell list, because the call drop is due to missing neighbor cell of SC 6 and SC 170.
Figure 1.4 Analyzing signaling of UE intra-frequency measurement control before call drop
If only the UE recorded information during test, without scanner information, confirm that call
drop is due to missing neighbor cell by using the following method, as shown in 5.1.3:
Confirm the scrambles of all cells in active set and the scrambles of cells in
monitor set measured by UE before call drop.
Compare the scramble information of the cell where the UE camps on after
reselection after call drop and the scrambles in UE active set and monitor set before
call drop.
If the former scramble is not in the scramble list of active set and monitor set before
call drop, the call drop is probably due to missing neighbor cell.
Figure 1.5 Confirming missing neighbor cell without information from scanner
Solution
Add neighbor cells. Because the RNC updates measurement control according to the best cell
which is obtainable by searching for intra-frequency measurement report with 1D event before
measurement control is sent. Usually they are configured to bi-directional neighbor cells.
According to the protocol, the maximum number of neighbor cell is 32 and the host cell is also
included in these cells, so the actual intra-frequency neighbor cell is 31 at most. The intra-
frequency neighbor cells of S subject are based on data of 2G neighbor cells. In the dense
urban areas, the densely-located sites and combine make the intra-frequency neighbor cell list
large. If the intra-frequency neighbor cells reach or exceed 31, a necessary neighbor cell found
during optimization fails to be listed as an inter-frequency neighbor cell. For this, you must
delete some redundant neighbor cells.
You must be cautious to delete abundant neighbor cells. Deleting necessary neighbor cells
leads to call drop. Following the principles below:
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.
12531 12061 9
12531 12111 16
12531 12251 2
12531 12291 4
12531 12292 0
12531 12540 74
12531 14051 2
12531 14072 2
12531 14111 1
12531 56361 16
12531 56362 0
12531 56820 0
Search for the neighbor cells with few handover times and even no handovers, such as cell
12531–12292. 5.1.4 shows the location relationship of 2G redundant neighbor cells.
According to 5.1.4, multiple NodeBs are located between the cell 12531 and the cell 12292, so
the handover probability is small. Therefore, delete the neighbor cell relationship.
The judgment principles based on 2G statistics might have mistakes, so you must confirm that
no call drop occurs after deleting the neighbor cell relationship.
After network launch, the handover times in traffic statistics according to statistics reflects the
real handovers, so deleting abundant neighbor cells by using the handover times in traffic
statistics according to statistics is more reliable. You need to register the traffic statistics tasks of
two cells on traffic statistics console of RNC.
From 5.1.5, 5.1.5, 5.1.5, 5.1.5, and 5.1.5, though SC20 cell is planned to cover the area,
but the best ServiceCell is as listed in 5.1.5.
As shown in 5.1.5, the RSSI of the areas with pilot pollution is not large, about –100
dBm to –90 dBm. As shown in 5.1.5, the RSCP of Best ServiceCell is between –105
dBm to –100 dBm. The pilot pollution of the area is caused by no strong pilot, so you
can solve the problem by strengthening a strong pilot.
Analyzing RSCP Distribution of Related Cells
5.1.5 shows the RSCP of SC270 cell near Yuxing Rd.
The SC270 cell is planned to cover the area. 5.1.5 shows RSCP of RSCP distribution of
SC270 cell. The signals from SC270 cell are weak in the area with pilot pollution.
Solution
According to on-site survey, the residential area is densely distributed by 6-floor or 7-floor
buildings. The test route fails to cover the major streets, and is performed in narrow streets with
buildings around, so the signals are blocked. The suggestion is to adjust the azimuth of SC270
cell from 150° to 130° and the down tilt from 5° to 3°. This enhances the coverage of SC270
cell.
After analysis of DT data, the expected result after adjustment is that the coverage area by
SC270 cell increases and the coverage is enhanced.
5.1.5 shows the pilot pollution near Yuxing Rd. after optimization.
5.1.5 shows the best ServiceCell near Yuxing Rd. after optimization.
5.1.5 shows the RSCP of best ServiceCell near Yuxing Rd. after optimization.
Figure 1.3 RSCP of best ServiceCell near Yuxing Rd. after optimization
5.1.5 shows the RSCP of SC270 cell near Yuxing Rd. after optimization.
Figure 1.4 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.
- 10
EcNo
cel l 56
- 20 cel l 041
- 30
t i me
According to 5.1.6, the signals of original cell attenuate 10 dB sharply within 1s, and the signals
of target cell increase 10 dB. If the signals are weak before attenuation, and 1a event is
configured to easily-triggered state, the measurement report is sent according to traced
signaling of the UE, and the RNC receives the measurement report according to signaling
traced by the RNC.
When the RNC sends the active set update message, the UE cannot receive it due to weak
signals of original cell, so the signaling is reset, and call drop occurs. If 1a event is slowly
triggered (such as configuring great hysteresis or triggering time), TRB reset occurs before the
UE sends the measurement report.
5.1.6 shows an example of turning corner effect.
According to 5.1.6, before turning corner, the signals of active set scramble 104 and 168
attenuate to smaller than –17 dB, but that of 208 is strong (–8 dB). According to the signaling
traced by the RNC, and the UE reports the 1a event of the cell of scramble 208, and sends the
active set update message. The UE does not receive the completion message, so the call drop
occurs, as shown in 5.1.6.
Solution
To solve turning corner effect problems, do as follows:
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).
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.
5.1.7 shows the call drop distribution of PS384K intra-frequency hard handover (it is the best
cell). Wherein, call drop point drop4, drop5, drop6, drop7, drop15, and drop16 are caused by
needlepoint effect.
Solution
To solve problems caused by needlepoint effect, you can refer to the solution to turning corner
effect. The key to adjust antenna is not to enable original signals attenuate sharply and not to
enable target signals increase sharply. In addition, you can increase the retransmission times to
resist to attenuation of signals so that CDR is lowered.
Description
5.1.8 shows signal distribution of cell52 vs. cell88 (signal fluctuation in handover areas).
Figure 1.1 Signal distribution of cell152 vs. cell88 (signal fluctuation in handover areas)
After the UE hands over from cell 152 to cell 88, the signals of cell 152 are stronger than that of
cell 88. In 5.1.8, after the signals of cell 152 keep weaker than that of cell 88, the signals of cell
152 become stronger than that of cell 88 for continuous 2s.
Analysis
When the UE hands over from cell 152 to cell 88, and the signals of cell 152 become better than
that of cell 88. This is similar to the needlepoint effect in 5.1.7. Therefore quick change of best
server signals causes the same handover failures as the needlepoint effect causes, as follows:
Ho Failure
TRB Reset
To sole the problem, optimize RF engineering parameters and 1D event parameters to avoid
ping-pong handover.
Description
The UE keeps performing intra-frequency HHO at the cell border, so the call quality declines
and even call drop occurs.
Analysis
Reporting the 1D event triggers the inter-frequency HHO. The 1D event is reported when the
best cell changes, as shown in 5.2.1.
The UE is at the border of two cells, so the signals from the two cells are equivalently strong.
Signal fluctuation easily causes ping-pong handover to best cells. Frequent report 1D event
triggers inter-frequency HHO.
To avoid intra-frequency ping-pong HHO caused by 1D event triggered by frequent fluctuation of
signals if the channels are similar, you can increase the hysteresis, as shown in 5.2.1.
According to 5.2.1, the second times does not reach the hysteresis, so reporting 1D event is not
triggered.
Description
When the UE moves to an inter-frequency cell, it fails to start compression mode to start inter-
frequency measurement. It camps on the inter-frequency cell after disconnection.
Analysis
The cell mentioned previously is configured as the carrier central cell after querying cell
configuration. Namely, the 2D event, 2F event, and inter-frequency measurement all take Ec/No
as measurement quantity.
The measured value of pilot Ec/No depends on the following two aspects:
Downlink interference
The downlink interference in the WCDMA network includes the interference from downlink
signals of intra-frequency cells (the host cell and neighbor cells) and the background noise.
Wherein, the downlink interference strength of intra-frequency cells is impacted by path loss
and slow attenuation. It is similar to the attenuation that UE receives useful signals (such as
CPICH RSCP).
At the coverage edge of a carrier, when UE moves from the current cell to another cell, the
CPICH RSCP attenuates at the same speed as the attenuation of interference (the background
noise is not impacted by path loss, so the CPICH RSCP attenuates a little faster than
interference attenuates. However, the difference between the two speeds is close (depending
on the strength of background noise). Therefore the UE receives the signals the CPICH Ec/Io of
which changes slowly. According to the simulation and on-site test, When the CPICH RSCP is
about –110 dBm, the CPICH Ec/Io can reach about –12 dB.
If you take Ec/Io as the measurement quantity for 2D event, the 2D event will be triggered
before call drop. Therefore adopting Ec/Io as the measurement quantity for 2D event will not
trigger 2D event upon call drop of UE, so the inter-frequency measurement will not be started.
In this case, configure the cell to carrier coverage edge cell and take RSCP as the
measurement quantity for 2D/2F event so that inter-frequency measurement is originated in
time.
Description
In part of the office building of a commercial deployment, the UMTS-GSM dual-mode MS
performs frequent ping-pong reselection of cells between 3G and the 2G network in the idle
state. “2G” and “3G” flag are displayed in the screen of Siemens U15 and Moto A835 MSs.
“WCP” and “GCP” are displayed in the screen of the Qualcomm test MS frequently. The
reselection from the 3G network to the 2G network takes 1min on average. The reselection from
the 2G network to the 3G network takes 1–2 minutes on average. During the testing, the
location of the MS and the circumstance keep fixed.
Analysis
The reselection from the 3G network to the 2G network is as follows:
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:
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.
Solutions
In network optimization, the operator can take the following adjustment:
Description
The UE performing PS domain services hands off between the 3G network and the 2G network.
Analysis
For inter-RAT handoff of CS and PS, the services for CS and PS are different in handoff
between the 2G network and the 3G network.
Solutions
Unification of measurement target in the 3G network and the 2G network
When there are more than one 3G cells, the change of Ec/Io indicates the change of
3G cell quality. If the cell property is configured as “carrier center cell” and the
measurement target in 2D event is Ec/Io, the measurement target between 3G and
the 2G network is Ec/Io. The default parameter of 2D/2F with the measurement
target Ec/Io is –24 dB. The parameter can be adjusted to –12/–10 dB to avoid ping-
pong handoff.
In addition, the new 3GPP TS 05.08 protocol defines the RSCP (FDD_RSCP) that
can measure the 3G network in reselection from the 2G network to the 3G network.
Now only Ec/Io can be tested. The adjustment fits the 3G cells the cell property of
which is “carrier border cell”. However many current NEs does not support this.
Description
In the office building of a commercial deployment, when the UE originates a call in areas
covered by the 3G network and moves towards the areas covered by the 2G network, the call
drops easily. The call succeeds one or two times every ten times.
Analysis
The 2G neighbor cells configuration of the 3G network cells that cover the office building in the
WCDMA network parameters is examined. The 2G cells that cover office building need to be
confirmed in the 2G neighbor cells list. UMTS outdoor macrocells are used to perform 3G
coverage in the office building, the test route is switched by passing two iron doors. After the
operator opens the door, enters, and closes the door, the signal attenuates sharply. 5.3.3 shows
the UMTS signal distribution observed by a scanner.
The signal attenuates sharply, so the handoff is not performed in time, and then the call drops.
The key solution is to adjust the inter-RAT switching parameters. This leads to an earlier and
faster handoff.
The operator does as follows:
Change the cell independent offset (CIO) in the GSM neighbor cell from 0
dB to 5 dB. The UE hands off to the GSM cell more easily. Call still drops in test.
Change 2D RSCP Threshold from –95 dBm to –85 dBm to –75 dBm. The
inter-RAT measurement starts earlier. Call still drops in test.
Change GSM RSSI from –90 dBm to –95 dBm. The UE hands off to GSM
cells more easily. Call still drops in test.
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:
Increase the GSM RSSI handoff threshold. This increases the coverage of
the 2G network, but reduces the coverage of 3G network, therefore this step needs
consideration.
Increase 2D/2F threshold in compression mode to start compression mode earlier.
Example 1:
14:24:17(12): According to RB Setup, the UE accesses the network by PSC 417.
14:25:36(02): The UE does not report 2D measurement report until call drop. The RNC
does not send measurement control report.
Conform that no inter-RAT neighbor cells are configured by examining parameters. If
the cells are added, call drop problems are solved.
Example 2:
16:38:18(18): The UE reports 1D event of cell 273, and cell 273 becomes the best cell.
However, the BCCH 538 indoor 2G cell is not configured as an inter-RAT neighbor cell
of cell 273.
16:38:40(20): The UE keeps sending measurement reports, but detects that the signals of
other GSM neighbor cells are weak. Therefore the RNC does not start handover, and
then call drop occurs.
The cell of PSC273 and PSC 264 alternate to be the best server. Indoor GSM neighbor
cells are configured as the inter-RAT neighbor cells of the cell of PSC264, but the cell of
PSC273 is not configured with any neighbor cells. When the UE enters indoor, the cell
of PSC273 becomes the best server, so call drop occurs. After indoor GSM neighbor
cells are configured as the inter-RAT neighbor cells of the cell of PSC273, no call drop
occurs.
messages, the UE keeps sending the measurement report of Nonverified until call drop.
In S subject, for convenient configuration of parameters, the original 2G neighbor cell
information is used to configure inter-RAT neighbor cells. All the inter-RAT cells are configured
as the neighbor cells of 3G cells. Inter-RAT cell offset is configured to enable the UE to hand
over to the target cell and to disable the UE to hand over to the undesired cell.
If excessive neighbor cells are configured, the UE must spend more time on inter-RAT
measurement. The measurement internal of UE is limited, excessive neighbor cells delay UE to
measure available neighbor cells, so call drop occurs.
Example :
11:30:11(92): The RNC sends measurement control messages (23 inter-RAT neighbor
cells)
11:32:22(61): The UE keeps reporting to BSIC Nonverified cell until 2 minutes before
call drop.
Configure the inter-RAT neighbor cells to the needed four neighbor cells, the MotoA835
hands over successfully.
No Measurement Report by UE
If the UE does not send measurement report, the UE performs the same as when the neighbor
cells are missing. The phenomena are as follows:
Delayed Handover
According to signaling of the RNC, a normal inter-RAT handover takes 5s. The following are the
time needed by the RNC, longer than that on UE. If the walking speed is 3 km/h, it takes 4–5
meters. The time depends on different scenes.
16:21:06(30): The UE sends the 2D measurement report.
16:21:06(37): The RNC sends the Physical channel reconfiguration message.
16:21:07(46): The UE sends the Physical channel reconfiguration completion message.
16:21:09(72): The UE sends the inter-RAT measurement reports.
16:21:10(48): The system sends the UE HO FROM UTRAN CMD GSM message.
16:21:11(11): The RNC sends the Iu interface Release Command message.
When the UE moves outdoor to indoor with the 3G signals fluctuating sharply, call drop occurs
due to delayed handover. According to the signaling, the phenomena of delayed handover are
as follows:
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:
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).
Qualcomm handset in the same test period:
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:
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.
Qualcomm handset in the same test period:
17:08:59(29): The UE sends 2D measurement reports, and the RNC sends Physical
channel reconfiguration.
17:09:00(33): The RNC receives Physical channel reconfiguration completion, and sends
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?
signals of the original cell becomes weak. Therefore subsequent starting compression
mode and handover process cannot proceed normally.
Analysis:
Starting compression mode is affected by 2D event configuration of ID2 measurement
control sent by the network side. You can enable 2D event to be reported more quickly
by the following methods:
− Increasing the threshold of 2D event
− Reducing hysteresis
− Reducing delayed triggering time
Now the back system can configure different starting threshold of inter-RAT
compression mode for signaling, CS and PS services.
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
The DT data analysis software Analyzer provides the previous data.
According to the data before call drop, the Ec/Io of active set is smaller than –15 dB and the
RSCP is close or smaller than –110 dBm, so the call drop must be due to downlink weak
coverage. After call drop, the UE camps on the cell of SC 232 the quality of which is bad, so the
call drop must not be due to missing neighbor cell.
According to the 5.4.1, the transmit power of UE approaches 21 dBm and the downlink BLER
before call drop reaches 100% (due to the comprehensive effect by inner loop and outer loop,
the downlink code transmit power reaches the maximum. Confirm this by using the data for
tracing the performance of RNC). According to previous analysis, the uplink and downlink are
balanced. To sum up, the call drop is due to bad coverage.
Solution
To solve coverage problems, you must adjust engineering parameters of antennas or construct
new sites.
According to 5.4.2, 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.
5.4.2 shows the uplink interference information recorded by UE.
From the UE side, the downlink PCICH Ec and Ec/Io are good, but the uplink transmit power
approaches the maximum. Therefore it is probably an uplink problem.
Interference:
The problematic site is the site 90640. The cells involve the cell 24231 and 24232. The RTWP
of the cell fluctuates sharply.
Solution
Locate the sources of interference t solve uplink interference problems.
Summarizing call drop problems due to abnormal equipment is difficult. Generally abnormal CN,
RNC, NodeB, and UE will lead to call drop. Some call drop problems can be further analyzed
and located only in research and development (R&D) environment. The following paragraphs
described the call drops that occurred before. You can refer to them.
Abnormal UE
Failure to report 1a event by UE
Call drop occurs easily with a version of Qualcomm 6250 during test. According to
the analysis of data, the Ec/Io and RSCP recorded by scanner are good upon every
call drop. The signals of the active set recorded are weak, but there are cells with
qualified signals. According to the signaling flow, the UE does not send the 1a event
measurement report of the cell in monitor set, so finally call drop occurs. After the
UE is updated, the problem is solved.
HS-PDSCH
HS-SCCH
HS-DPCCH
The active set does not list the cells of SC 25 and SC 26. After call drop, the UE camps
on the cell of SC 26. Meanwhile, the quality of signals from the cell of SC 11 declines
sharply.
According to previous description, the call drop is probably due to missing neighbor cell.
For detailed analysis, see 5.1.
Solution
To solve the problem, add the corresponding neighbor cell.
Weak Coverage
After HSDPA technology is used, the downlink load of cell increases. This has some impact on
coverage radius of cell. If the load of original R99 cell is light, the coverage scope decreases
sharply after HSDPA technology is used. Pay attention to cell coverage and call drop problems
caused by decrement of handover areas after R99 network is upgraded to HSDPA network.
HS-DPCCH is used in uplink of HSDPA, so the HSDPA UE consumes more power than R99
UE, and consequently, the HSDPA UE at the cell edge reaches the maximum transmit power
more quickly than R99 UE at the cell edge. This is uplink power restriction.
The maximum transmit power of some R99 UEs and HSDPA UEs are the same, 24 dBm.
6 Summary
Based on related guides to handover and call drop, this guide is complete. It focuses on
operability by on-site engineers. In addition, it describes operation steps in details for the actual
handover and call drop problems in forms of flow chart.
The fundamental knowledge and preparation knowledge are placed in the appendix. Operations
are in the body.
V3.1 supplements HSDPA knowledge, including:
7 Appendix
7.1.1 RAB
RAB is the carrier at the subscriber plane. It is used in transmitting voice, data, and multimedia
services between UE and CN. The RAB assignment is originated by CN. It is a function of RNC.
RB is ratio bearer between SRNC and UE. It includes layer 2 and above. It is the service
provided to layer 2.
7.1.1 shows the UMTS QoS structure. It provides the part that RAN and RB play in the UMTS
network.
7.1.2 SRB
The SRB carries the signaling at U-Net interface. The TRB carries the services at the Uu
interface and it is the radio bearer at the user plane.
7.1.2 shows the structure of SRB and TRB at the user plane.
IUUP
TRB(AM)
Logic channels
MACC MACD
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)
7.2 RL FAILURE
When a cell sets up a new radio link, there is a process for uplink and downlink synchronization.
After UE succeeds in uplink synchronization, it powers on the transmitter, and then the NodeB
performs uplink synchronization. If the NodeB succeeds in synchronization, it sends the RNC an
RL RESTORE message. If it fails, it sends the RNC the RL FAILURE message. When the RNC
receives the RL FAILURE message or fails to receive RL RESTORE message, it releases the
resources related to the radio link. If the active set uses only one radio link, the RNC then
originates the release at signaling plane.
7.2 lists the timers and counters related to the synchronization and asynchronization.
Table 2.1 Timers and counters related to the synchronization and asynchronization
Parameter Parameter
Description
ID Name
Value range: D1, D2, D4, D10, D20, D50, D100, D200, D400,
D600, D800, and D1000
Actual value range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600,
800, and 1000
Constant
N312 Physical unit: none
312
Content: It indicates the maximum times continuous
synchronization indicators received from L1. The default value
is 1.
Recommended value: D1
Value range: D1, D2, D4, D10, D20, D50, D100, and D200
Actual value range: 1, 2, 4, 10, 20, 50, 100, and 200
Physical unit: none
Constant
N313
313 Content: It indicates the maximum times continuous
synchronization indicators received from L1. The default value
is 20.
Recommended value: D50
Value range: D0, D2, D4, D6, D8, D12, D16, and D20
Actual value range: 0, 2, 4, 6, 8, 12, 16, and 20
Physical unit: none
Content: When the principle of radio link failure is met, and the
radio bearer only related to T314 exists, start T314. When the
cell update is complete, stop T314. The default value is 12.
When the UE of CELL_DCH fails in radio links, start T314 (or
T314 Timer 314 T315), and send CELL UPDATE messages. Before T314 (or
T315) corresponding to services expires, if the radio link
reconfiguration configured by CELL UPDATE CONFIRM
message fails, resend CELL UPDATE messages to
reconfigure the radio link (related to T302 and N302). Based
on this, configure T314 > T302 × N302.
When T314 expires, the service RB of corresponding timers is
deleted.
Recommended value: D20
Value range: D0, D10, D30, D60, D180, D600, D1200, and
D1800
Actual value range: 0, 10, 30, 60, 180, 600, 1200, and 1800
Physical unit: s
Content: When the principle of radio link failure is met, and the
radio bearer only related to T315 exists, start T315. When the
cell update is complete, stop T314. The default value is 180.
T315 Timer 315 When the UE of CELL_DCH fails in radio links, start T315 (or
T314), and send CELL UPDATE messages. Before T315 (or
T314) corresponding to services expires, if the radio link
reconfiguration configured by CELL UPDATE CONFIRM
message fails, resend CELL UPDATE messages to
reconfigure the radio link (related to T302 and N302). Based
on this, configure T315 > T302 × N302.
When T315 expires, the service RB of corresponding timers is
deleted.
Recommended value: D30
Value range: D1, D2, D4, D10, D20, D50, D100, D200, D400,
D600, D800, and D1000
Actual value range: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600,
800, and 1000
Constant
N315 Physical unit: s
315
Content: It indicates the maximum times continuous
synchronization indicators received from L1. The default value
is 1.
Recommended value: D1
7.2 lists the timers and counters related to call drop at lub interface.
Table 2.2 Timers and counters related to call drop at lub interface
Recommended value: 5
Recommended value: 50
The conditions of SHO signaling flow for adding radio link are:
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.
The SRNC decides to set up a new radio link and the new cell to which the
link belongs is under the control of another RNC (DRNC). The SRNC sends DRNC a
Radio Link Setup Request message, and requires DRNC to prepare the
corresponding radio resources. The new radio link is the first link set up between UE
and DRNC, so a new lur signaling connection is required. The lur signaling
connection carries UE-related RNSAP signaling.
The Radio Link Setup Request message includes parameters as below:
− Cell ID
− TFS
− TFCS
− Frequency
− Uplink Scramble
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.
The SRNC sends UE the Active Set Update message on DCCH. The
message includes content on adding radio link.
The parameters include:
− Update type
− Cell ID
− Downlink scramble
− Power control information
− Adjacent cells
The UE configures the corresponding parameters according to RRC
signaling. It sends SRNC the RRC message, namely, Active Set Update Complete
message.
The conditions of SHO signaling flow for deleting radio link are:
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 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:
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.
Figure 1.1 SHO signaling flow for adding and deleting radio link
Decision to setup
new RL and
release old RL
Start RX
description
3. Radio Link Setup Response
NBAP NBAP
4. Radio Link Setup
Response
RNSAP RNSAP
5. ALCAP Iub Data Transport Bearer Setup ALCAP Iur Bearer Setup
7. Uplink Synchronisation
DCH-FP DCH-FP
Start TX
description
8. DCCH : Active Set Update Command
RRC RRC
[Radio Link Addition & Deletion]
Stop RX and TX
The SRNC decides to set up a new radio link and the new cell to which the
link belongs is under the control of another RNC (DRNC). The SRNC sends DRNC a
Radio Link Setup Request message, and requires DRNC to prepare the
corresponding radio resources. The new radio link is the first link set up between UE
and DRNC, so a new lur signaling connection is required. The lur signaling
connection carries UE-related RNSAP signaling.
The Radio Link Setup Request message includes parameters as below:
− Cell ID
− TFS
− TFCS
− Frequency
− Uplink Scramble
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.
The SRNC sends UE the Active Set Update message on DCCH. The
message includes content on adding and removing radio link.
The parameters include:
− Update type
− Cell ID
− Downlink scramble
− Power control information
− Adjacent cells
The UE configures the corresponding parameters according to RRC
signaling, deactivates the downlink receiver of the link to be deleted, actives the
downlink receiver to be added, and sends SRNC the Active Set Update Complete
message.
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 parameters
Layer 1 Layer 3
A filtering B filtering C Evaluation D
of reporting
C' criteria
In 7.3.4,
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.
Fn = (1 − a ) ⋅ Fn −1 + a ⋅ M n
Wherein,
− Fn: filtered updated measurement result
− Fn-1: filtered previous measurement result at last point
− Mn: the latest measured value received from physical layer
− α = 1/2(k/2). The k is from Filter coefficient, namely, the handover parameter
FilterCoef. FilterCoef is configured in intra-frequency, inter-frequency, and inter-RAT
handover measurement. When α is 1 (accordingly k = 0), there is no layer 3 filtering.
From previous measurement model, the filtering occurs before event judgment and
measurement report. In addition, the measured values in cell Measurement results and
Measurement results on RACH of UE's report are filtered. The layer 3 filtering controlled by
network layer caters for measurement event judgment and measurement report only. The cell
reselection when UE is in the idle mode and connection mode does not support layer 3 filter
controlled by network layer.
In the measurement report mechanism domain, the network requires UE to report the 1A event
(for example, the UE enters the Cell_DCH state), the UE sends the measurement report when a
primary pilot channel enters the reporting range. According to protocols, for 1A event, the UE
can report multiple cells of trigger event in a measurement report. The cells are included in the
list of trigger event. The UE sorts the cells good to bad in terms of quality (CPICH Ec/No). If less
than 3 cells are listed in the active set, the network judges to add links. If the active set is full of
cells, no operation is performed.
When the measured value meets the following formula, the UE judges that a primary pilot
channel is in the reporting range.
The path loss is:
NA
10 ⋅ LogM New ≤ W ⋅10 ⋅ Log ∑ M i + (1 − W ) ⋅10 ⋅ LogM Best + ( R − H 1a / 2),
i =1
For other measurement values:
NA
10 ⋅ LogM New ≥ W ⋅ 10 ⋅ Log ∑ M i + (1 − W ) ⋅10 ⋅ LogM Best − ( R − H 1a / 2),
i =1
In the previous formulas:
MBest is the measured value of the best cell in the active set.
Measurement
quantity
P CPICH 1
Reporting
range
P CPICH 2
P CPICH 3 Time-to-trigger
Reporting Time
event 1A
Usually, if the 1A event is triggered, the UE sends a measure report to UTRAN. The UTRAN
sends an Active Set Update message for updating active set. Probably No response is received
after UE sends measurement report (for example, due to limited capacity). The UE changes
from sending event-triggered report to periodic report. The measure report contains the
information about the cells in the active set and cells in the monitored set in reporting range.
Only when the cell is successfully listed in the active set and leaves the reporting range will UE
stop sending periodic reports.
P C P IC H 1
P C P IC H 2
R e p o r t in g
ra n g e
R e p o r tin g
t e r m in a te d
P e r io d ic P e r io d i c
re p o rt re p o rt
E v e n t - t r ig g e r e d
P C P IC H 3
re p o rt
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,
If more than one links are in the active set, the UE judges to delete the links.
NA
10 ⋅ LogMOld ≥ W ⋅ 10 ⋅ Log ∑ M i + (1 − W ) ⋅ 10 ⋅ LogM Best + ( R + H 1a / 2),
i =1
For Other measure values:
NA
10 ⋅ LogMOld ≤ W ⋅ 10 ⋅ Log ∑ M i + (1 − W ) ⋅ 10 ⋅ LogM Best − ( R + H 1b / 2),
i =1
In the previous formulas:
MBest is the measured value of the best cell in the active set.
UE sorts the cells in terms of measured value and then reports them.
In 3, the cells where the PCPICH 1, PCPICH 2, and PCPICH 3 serve are in the active set but
the cell where PCPICH 4 serves is not in the active set. If the cells in the active set reach or
exceeds the replacement threshold of active set, the event is used for replacing bad cells in the
active set.
When the 1C event is triggered, the UE reports the replacing cell and the cell to be replaced in
the event trigger list. The UE also sort the reported cells good to bad in terms of quality (CPICH
Ec/No). After the RNC receives the 1C event trigger list reported by UE, it replaces the cell to be
replaced with the replacing cell in the active set.
When channels have little difference, the 1D event might be triggered due to fluctuating signals.
This leads to unnecessary increase of signaling flow at the air interface. The hysteresis value
helps to avoid this, as shown in 4.
The second time fails to reach the hysteresis condition, so no 1D event report is triggered. This
parameter also applied in other events.
According to protocols, the 1D event can report only one triggered cell which can be in active
set or monitored set. Therefore the cells in the monitored set must be added to the active set. If
the active set is full, the system deletes a cell that is not the best cell. Consequently the system
adds the best cell to the active set. Finally the system marks the cell as the best cell.
The 1E event triggers measurement report of the cells not monitored when the UE fails to
receive the neighbor cell table.
The following HHO flow is based on the lur interface when the UE is in the CELL_DCH state.
Figure 1.1 Ordinary HHO flow (lur interface and CELL_DCH state)
The SRNC sends the Radio Link Setup Request message to request radio
link setup.
The parameters include target RNC identity, s-RNTI, cell ID, TFS, and TFCS.
The target RNC allocates RNTI and radio resources for RRC connection
and radio links. In addition, it sends the NBAP message, namely, the Radio Link
Setup Request message to the target NodeB.
The parameters include cell ID, TFS, TFCS, frequency, uplink scramble, power
control, and so on.
The target 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.
1. Relocation Required
RANAP RANAP
2. Relocation Required
RANAP RANAP
3. Relocation Request
RANAP RANAP
4. Relocation Request
RANAP RANAP
5. ALCAP Iu Data
Transport Bearer Setup
9. Relocation Request
RANAP Acknowledge RANAP
18. Relocation
Complete
RANAP RANAP
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 Setup Response message.
The parameters include cell ID, TFS, TFCS, frequency, uplink scramble, power
control, and so on.
or 10) When the RNC completes preparations, the RNC sends CN the
Relocation Required Acknowledge message.
or 15) or 16) When the target RNC detects UE, it sends two nodes of CN
the Relocation Detect message. When the UE switches from using the original radio
link to the new one, the source NodeB sends source RNC the Radio Link Failure
Indication message upon detection of RL error by source NodeB.
When the UE completes setting up RRC connection with target RNC and
the corresponding radio resources are allocated, it sends target RNC the RRC
message, the Physical Channel Reconfiguration Complete message.
or 19) After the UE succeeds in handing over to the target RNC and is
allocated with resources, the RNC sends all CNs the Relocation Complete message.
or 24) The original RNC sends CN the Lu Release Complete message for
confirming release.
Fundamental Concepts
The cell at the carrier coverage edge refers to the cell covered by a carrier in the most
peripheral areas. The cell features that no intra-frequency neighbor cells are present in a
direction of the cell.
The cells in the carrier center area are the rest cells. The cell features that intra-frequency
neighbor cells are present in all directions of the cell.
In the cell at the carrier coverage edge, when the UE moves towards the direction with no intra-
frequency neighbor cells, the CPICH Ec/No fluctuates slowly due to the same attenuating speed
of CPICH RSCP and interference. According to simulation, when the CPICH RSCP is lower
than the demodulation threshold (–110 dBm), the CPICH Ec/No can reach about –12 dB. Now
the inter-frequency handover algorithm based on CPICH Ec/No measurement is invalid.
Therefore, using CPICH RSCP as inter-frequency measurement quantity is more proper and
valid for cells at the carrier coverage edge.
The CPICH RSCP might serve as inter-frequency measurement quantity for cells in the carrier
center area, but the CPICH Ec/No is better to reflect the actual communication quality of links
and cell load.
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.
For a subscriber, if an RAB is mapped on the HS-DSCH of a cell, the cell becomes the HS-
DSCH serving cell for the subscriber, and the radio link of the cell is the HS-DSCH serving radio
link.
As the signals of HSDPA serving cell are weaker and weaker, the network switches the service
to a HSDPA cell with better signals, namely, the update of HSDPA serving cell. For the handover
of HSDPA subscribers, HS-DSCH serving cell update describes HS-DSCH handover, and
handover describes DCH handover.
If other cells do not support HSDPA, the system switches the service to R99 cells. An RAB is
mapped on the HS-DSCH of a cell only, so SHO is unavailable on HS-PDSCH bearing HSDPA,
but available on associated DCH. The HS-PDSCH does not support SHO, so the major impact
on mobility management (MM) after use of HSDPA is as below:
Measurement control
Measurement report
Handover judgment
Handover implementation
Bearer Re-arrangement
Description
When the HS-PDSCH serving cell is updated due to DPCH SHO, the UE reports the following
events listed in 7.6.4. The system will respond accordingly.
Table 1.1 Flow of serving cell update triggered by different events in SHO
Event Action
1D event, the best server is listed in Change the radio link ID by reconfiguring radio
active set link
1C event, the current HS-DSCH Update the HS-DSCH in active set to support
serving cell is the worst cell in active the best server of HS-DSCH, and then replace
set the cell
M eas uremen t
R ep orting
criteria
fulfilled
DC CH : M E ASU R E M EN T R EPO R T
Serving H-S
D SC H cell
chang e decision
C PH Y-RL-M odify-RE Q
(N BAP/R NSA P: R L R econfiguration Prepare)
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:
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.
− UE ID of HS-DSCH
The SRNC sends DRNC the RADIO LINK RECONFIGURATION COMMIT
message. The message contains the activation time of SRNC in CFN.
1 . R N S A P : R L R E C O N F IG U R A T IO N
2 . N B A P : R L R E C O N F IG U R A T IO N
PREPARE
PREPARE
3. N B A P : R L R E C O N F IG U R A T IO N R E AD Y
4. N B A P : R L R E C O N F IG U R APTRIOENP A R E
5. N B A P : R L R E C O N F IG U R A TIO N R E A D Y
6. R N S A P : R L R E C O N F IG U R A T IO N R E A D Y
7. R N S AP : R L R E C O N FIG U R ACTOIOMNM IT
8. N B A P : R L R E C O N F IG U R ACTO
IOMNM IT
9. R R C : P H Y S IC A L C H A N N E L R E C O N F IG U R A T IO N
1 0. R R C : P H Y S IC A L C H A N N E L R E C O N F IG U R A T IO N C O M P L E T E
The update process is based on that the DPCH and active set are fixed.
The inter-NodeB synchronization serving cell is updated as below:
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.
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.
I NTER_NODEB(ok) . t
mf
Figure 1.1 Inter-NodeB HS-DSCH cell update after radio link is added
Uu Target Node B Source Node B Iub Iur
UE DRNC SRNC
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(DCH) (DCH)
7. RNSAP: RL RECONFIGURATION
8. NBAP: RL RECONFIGURATION
REQUEST
REQUEST
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(HS-DSCH) (HS-DSCH)
ALCAP Iub Data Transport ALCAP Iur Data Transport Bearer release
Bearer release (HS-DSCH) (HS-DSCH)
Setting a newly-added radio link to HS-DSCH radio link involves two steps:
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 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.
Description
The combination of HHO and HS-PDSCH serving cell update is simple. Namely, they occur
simultaneously.
The intra- and inter-NodeB HHO with serving cell update have the same process. New radio link
is set up in new cell with HS-DSCH. Consequently, the physical channel is reconfigured, and old
link is deleted.
Handover Flow
7.6.5 shows the inter-NodeB HS-DSCH cell update during HHO (single step method).
Figure 1.1 Inter-NodeB HS-DSCH cell update during HHO (single step method)
Uu Target Node B Source Node B Iub Target Source Iur
UE DRNC DRNC SRNC
ALCAP Iub Data Transport Bearer setup ALCAP Iur Data Transport Bearer setup
(DCH + HS-DSCH) (DCH + HS-DSCH)
8. NBAP: RL DELETIONREQUEST
ALCAP Iub Data Transport ALCAP Iur Data Transport Bearer release
Bearer release (DCH + HS-DSCH) (DCH + HS-DSCH)
The inter-NodeB HS-DSCH cell during HHO (single step method) is updated as below:
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 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.
7.6.6 shows the signaling when DPCH intra-frequency HHO with HS-DSCH serving cell update.
Figure 1.2 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).
I NTER_NODEB(ok) . t
mf
7.6.7 shows the DPCH inter-frequency HHO with HS-DSCH serving cell update.
Figure 1.3 DPCH inter-frequency HHO with HS-DSCH serving cell update
In 7.6.7,
HSDPA_I NTER_FREQ_
HHO_WITH_TRAFFI C_OK_UE. t mf
Description
When the UE moves from a HSDPA cell to an R99 cell, the service that is born on HS-DSCH
channel is remapped on DCH to guarantee the continuity of service. The HS-DSCH set in
HSDPA cell is deleted.
7.6.8 shows the handover from HSDPA to R99.
The strategy for handover between HSDPA and R99 in V17 differs from that in V15 and V16. If
both an R99 cell and a HSDPA cell are available in the active set of the UE, the UE decides that
the service is borne over the HS-DSCH or over the DCH depending on whether the best cell
supports HSDPA or not.
In V17, four scenarios of handover between HSDPA and R99 exist as listed in 7.6.8.
Figure 1.1 DPCH SHO with handover from HSDPA to R99 (inter-NodeB)
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 23–26: 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 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.
In 7.6.8, in the handover from R99 to R5 HSDPA, after the UE reports 1A event, it first adds the
RL of HS-PDSCH, and then reconfigures the service born on DCH to HS-PDSCH.
The following attachment contains the previous signaling, according to V100R005C01B061.
SHO_R5t oR99&R99t o
R5( OK) _I nt er_NodeB. t mf
Figure 1.3 Inter-NodeB SHO with handover from HSDPA to R99 (V17)
In V17, the signaling flow for SHO from HSDPA to R99 is as follows:
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 39–44: R99 HHO occurs, the UE hands over to a new cell.
7.6.8 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.
HHO_R5ToR99( OK)
and R99t oR5_I nt ra_NodeB. t mf
In V17, the signaling flow for intra-frequency HHO from HSDPA to R99 is as follows:
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.
The handover between HSDPA and GPRS is similar to that of R99. For details, see the
Appendix 5.
7.6.9 shows the handover between HSDPA and GRPS.
hsdpa- 2G. t mf
Cell a(f1,HSDPA)
Cell a(f1,HSDPA)
The UE originates
an HSDPA service
request in Cell b.
Service request
DPCH link
HSDPA link
Cell a(f1,HSDPA)
Cell a(f1,HSDPA)
A 4A event occurs
due to increase of
traffic.
4A event
DPCH link
HSDPA link
In V17, the following types of inter-frequency direct retry of HSDPA are available:
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.
When the HSDPA is used, a new state appears compared with R99, the CELL_DCH state on
HS-DSCH.
The switch of channel type between HS-DSCH and FACH/DCH includes:
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.
RNC_2006- 10- 30
- 11- 31- 49_based on t r af f i cr ar
RNC_2006- 10- 30
- 11- 11- 05_based on t i mer D2H. r ar
If the HSUPA is used, the following two types of links may coexist between a subscriber and the
network:
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 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 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.
Report of
1D event
UE
UE
If the monitor set reports a 1D event, the HSUPA serving cell also is updated. For example, the
service is over the E-DCH in HSUPA 1 that works as the serving cell. The signals of HSUPA 2 in
the monitor set become stronger. In this case, the UE reports a 1D event and the RNC adds
HSUPA 2 to the active set. At last, the RNC updates the serving cell is updated by re-configuring
the physical channel. 7.7.3 shows the related signaling:
Figure 1.3 Signaling for HSUPA cell update triggered by a 1D event (reported by the monitor
set)
UE UE
Figure 1.2 Signaling for intra-frequency HHO between two HSUPA cells
UE UE
Figure 1.2 Signaling for inter-frequency HHO between two HSUPA cells
SHO from a HSUPA cell to a non- The RNC updates the active set based
HSUPA cell on the measurement report, and then
1
allocates the service from the E-DCH to
A 1A, 1C, or 1D event occurs. the DCH through RB reconfiguration.
Intra-frequency HHO from a The RNC allocates the service from the
2 HSUPA cell to a non-HSUPA cell E-DCH to the DCH through RB
A 1D event occurs. reconfiguration.
Cell 2 and Cell 1 are adjacent cells at the same frequency. If signals of Cell 2 become strong
enough to trigger a 1A or 1C event as the UE moves, the RNC adds Cell 2 to the active set. In
this case, non-HSUPA cells exist in the active set. The RNC allocates the service from the E-
DCH to the DCH through RB reconfiguration according to the HSUPA channel selection policy.
UE UE
Figure 1.3 Addition of an R99 cell when the service is on the E-DCH
Signals of the99
R cell in the monitor set
become stronger and the UE reports1Athe
event.
UE UE
Figure 1.2 Signaling for intra-frequency HHO from a HSUPA cell to a non-HSUPA cell
UE UE
Figure 1.2 Signaling for inter-frequency HHO from a HSUPA cell to a non-HSUPA cell
The UE moves from Cell 1 to Cell 2. Cell 2 and Cell 1 are adjacent cells at the same frequency.
The DPCH of Cell 1 bears the BE service of the UE. If signals of Cell 1 become weak enough to
trigger a 1B event as the UE moves, the UE reports the 1B event. In this case, the RNC delete
Cell 1 from the active set. All cells in the updated active set support the HSUPA. If the service is
fit for the E-DCH, the RNC allocates the service from the DCH to the E-DCH through RB
reconfiguration.
Report of 1b event
Figure 1.4 SHO from a non-HSUPA cell to a HSUPA cell (triggered by a 1B event)
HSUPA cell).
Cell1 Cell 2
Cell1 Cell2 Cell1
UE UE
UE
Figure 1.2 Signaling for intra-frequency HHO from a non-HSUPA cell to a HSUPA cell
The service is re
-allocated to the-EDCH through RB
reconfigruation
.
Cell1 Cell 2
Cell1 Cell2 Cell1 Cell2
UE UE
UE
The handover between different systems is caused by coverage or service. The use of the
HSUPA does not impact triggering conditions and decision of the handover between different
systems. Thus, the handover between a HSUPA cell and a GPRS cell is similar to that between
an R99 cell and a GPRS cell.
The signaling flow is as follows:
The RNC carries out handover from a HSUPA cell to a GPRS cell based on
the measurement report from the UE.
For details, see the related section earlier in this document.
The direct retry of the HSUPA can balance load between an R99 cell and a HSUPA cell at
different frequencies or between different HSUPA cells. Direct retry of the HSUPA includes the
following three scenarios:
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.
The HSUPA UE’s request for setup of the PS service is rejected by the
HSUPA cell.
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 1.1 Direct retry from a HSUPA cell to another HSUPA cell
After the HSUPA is used, a channel state is added: the CELL_DCH state of the E-DCH. The
HSUPA related switch between channel types involves switch between the CELL_FACH and
the CELL_DCH (DCH).
The direct retry algorithm might trigger switch between the CELL_FACH and the CELL_DCH
(DCH). In addition, a timer for periodic measurement is available in the system. Once the timer
expires, the system checks whether the current bearer mode conflicts with the bearer policy. If a
conflict exists, the system triggers switch between channel types.
Traffic triggers switch between the CELL_DCH (E-DCH) and the CELL_FACH. Measurement
reports (4A) sent by the UE trigger switch from the CELL_FACH to the CELL_DCH. The internal
measurement of the RNC triggers switch from the CELL_DCH(E-DCH) and the CELL_FACH
(According to the current protocol, the UE measurement report does not support measurement
of the E-DCH).
UE NodeB RNC
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.
After the UE completes related configuration according to new configuration
data, it sends RNC the PHYSICAL CHANNEL RECONFIG COMPLETE message.
Now the compression mode is available.
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.
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.
The message 16 and message 17 are to release the radio resources of NodeB.
What is different from normal releasing flow is that the air interface does not send
the RRC connection release message, because the UE is using WCDMA network.
Therefore the NodeB releases radio resources without informing UE of the release.
UE NodeB RNC
Rel ocat i o
RL set up r equeset
RL set up r esponse
Rel ocat i o
AC
7.9 shows the tracing signaling of handover from GSM to WCDMA
I nt er Syst em t o UTRAN H
RL Rest or e I ndi cat on
Handover Compl et e
Rel ocat i o
UTRAN Capaci t y I nf o
2010-05-12 UE Capaci t y I nf o Enqui r yPage 178 of 200
Huawei Confidential
W-Handover and Call Drop Problem Optimization Guide For Internal Use
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:
− Complete configuration: clearly provide parameters in each layer
− Pre-configuration (pre-defined): the system broadcast multiple sets of parameter
templates in the system information 16 and configure template number and necessary
parameter to UE. The UE listens to the system information of UTRAN and obtain the
parameter configuration according to template number.
− Pre-configuration (default): The protocol 25.331 provides 10 sets of default
parameters and specifies an identity to each default parameter. The RNC configures
the default identity and other necessary information to UE.
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
MSC/VLR
MSC/VLR(3G) (2G) GGSN HLR SGSN(3G) SG
SGSN Cnt x
Req
SGSN
SGSN
Figure 1.2 Flow of handover from WCDMA to GPRS (2) SGSN Cntxt R
Send Authentication Info
Send Authentication ACK
MSC/VLR(3 MSC/VLR(2
G) G) GGSN HLR SGSN(3G)SGSN Cntx
SGS
Cancel Loc ACK
SRNS D
Iu Re
Com
Iuforwar
Rel C
forward
Cancel Loc packecks
ACK PDP cntxt Req
Update
Update PDP cntxt Rsp
Insert Subscriber Data
Update
Insert GPRS
Subscriber Location
Data ACK
7.10 shows the tracing signaling of handover from WCDMA to GPRS.
Update Location
Cancel Location
W-Handover and Call Drop Problem Optimization Guide For Internal Use
The UE sends the measured 2D report, indicating the quality of the serving
cell is worse.
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.
GSM cells.
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.
Figure 1.1 Signaling flow for handover from GPRS to WCDMA (1)
MSC/V L R(2
MSC/V L R(3G) G G SN HLR SG SN(3G)
G)
I ni t
SGSN
SGSN
Send A uthen Info
Send A uthent A CK
SGSN
Update PDP cntxt Req forw
U pdate PD P cntxt Rsp
Update GPRS Loc
Cance l L oca tion
Cancel L oc A CK
Figure 1.2 Signaling flow for handover from GPRS to WCDMA (2)
MSC/VLR(2
MSC/VLR(3G) GGSN HLR SGSN(3G)
G)
Ins Subscriber Dat
Ins Subscrib Dat ACK
Update GPRS Loc ACK
Location Update Req
Update Location
Cancel Location
Cancel Location ACK
Insert Subscriber Data
Ins Subscriber Data ACK
Update Location ACK
Update Location Accept
Signaling Flow at UTRAN Side
TMSI as
The signaling flow at UTRAN side proceeds Reallocation
below: Complete
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.
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.
CIO indicates the cell individual offset, namely, the offset configured by the
inter-RAT cell.
The
starting/stopping
InterRATCSThdFOR2DEcNo, threshold for
InterRATPSThdFOR2DEcNo, inter-RAT
InterRATSigThdFOR2DEcNo , measurement –24, namely, –24 add cells by
InterRATCSThdFor2FEcNo, with Ec/No as the dBm executing
InterRATPSThdFOR2FEcNo, measurement ADD
InterRATSigThdFOR2FEcNo value (CS, PS, CELLINTER
and single FREQHO,
signaling) query cells
Hysteresis. The by executing
hysteresis and LST
inter-RAT quality CELLINTER
threshold decides FREQHO,
whether to trigger and modify
inter-RAT cells by
handover executing
HYSTTHD 4 MOD
judgment. It can
be smaller in CELLINTER
areas with small FREQHO
shadow fading. It
can be greater in
areas with great
shadow fading.
Set cells by
executing
The individual
ADD
offset of inter-
INTERRATN
RAT handover
CELL, query
cells. The UE
cells by
uses it with the
executing
initial measured
CellIndividalOffset 0 LST Cell
value of the cell
INTERRATN
as the
CELL, and
measurement
modify it by
result for
executing
handover
MOD
judgment of UE.
INTERRATN
CELL
Note:
7.12 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.
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.
Pay attention to several fields: MCC, MNC, LAI, RNC ID, CELL ID, downlink
frequency point, and scramble. Using system defaults is recommended for unlisted
fields.
− MCC: query it by running the command LST RNCBASIC on the corresponding RNC
client
− MNC: query it by running the command LST RNCBASIC on the corresponding
RNC client
− LAI: query it by running the command LST AC on the corresponding RNC client
− RNC ID: query it by running the command LST RNCBASIC on the corresponding
RNC client
− CELL ID: query it by running the command LST CELL on the corresponding RNC
client
Note:
The query result is decimal. It can be filled in the CELL ID field after it is converted to hex and
removed of the highest bit.
Downlink frequency point: query it by running the command LST CELL on the
corresponding RNC client and then inputting the corresponding CELL ID in the CELL
Scramble: query it by running the command LST CELL on the corresponding RNC
client and then inputting the corresponding CELL ID in the CELL
Configuring Target 3G Cells as the Inter-RAT Neighbor Cell of GSM
Configuring target 3G cells as the inter-RAT neighbor cell of GSM proceeds as below:
− Select setting cells dynamically
Note:
The target cell for handover from the 3G network can be the directional neighbor cell of GSM
only.
The configuration table for 3G system information includes the following parameters:
− Type of measurement reports: common measurement reports
− Number of best cells in the GSM band: the default value is 3
− Threshold for searching for 3G cells in the idle mode: the values range from 0 to 15
− Offset of FDD cell reselection: When the mean receiver level of 3G cells is
FDD_Qoffset greater than that of the serving cell, the UE can reselect 3G cells. 0 = –
∞ (always select a cell if acceptable), 1 = –28 dB, 2 = –24 dB, …, 15 = 28 dB. Select
0 for easy handover.
− The minimum Ec/No threshold for FDD cell reselect: level threshold for 3G cell
reselection: when the receiver level of 3G cell is greater than the FDD_Qmin, the cell
can be a candidate cell for reselection.
− Other default values
Configuring 2G Handover Parameters
7.13 shows the parameter configuration table for inter-RAT handover.
PLMN is the PLMN which provides equivalent services to subscribers. The network
side decides whether to tell the control list to UE. The MSC sends the list to UE upon
update acceptance and the UE saves it. When the UE reselects an inter-PLMN cell, it
reselects a cell from the list by priority.
− Configure the data at MTP layer and guarantee the signaling transmission between
the 2G MSC and the 3G MSC.
− Configure the data at SCCP layer. Configure the corresponding record of 2G MSC in
the GT table, SCCP SSN table, and SCCP DSP table.
− Configure the trunk data between MSCs in the same way as configuring common
data.
Necessary Data Configuration for RNC
Data Configuration for Supporting Roaming from WCDMA to GSM/GPRS
To support the roaming from WCDMA to GSM/GPRS, the UTRAN must complete
sending the following system information:
− Add GSM cells and configuration the following data:
MCC
MISSING NEIGHBOR CELL
LAC
CELL ID
NCC
BCC
FREQ_BAND
Frequency number
CIO
ADD GSMCELL: MCC="460", MNC="10", LAC="0x0fa0", CID="0x0102",
NCC=0, BCC=0, BCCHARFCN=60, BANDIND=DCS1800_BAND_USED,
RATCELLTYPE=GSM;
ADD INTERRATNCELL: CELLID=123, MCC="460", MNC="10", LAC="0x0fa0",
CID="0x0102", CELLINDIVIDALOFFSET=50, QOFFSET1SN=-50,
QRXLEVMIN=-58;
− Configure the measurement point for FACH to inter-frequency FDD measurement,
inter-frequency TDD measurement, or inter-RAT measurement. If inter-RAT roaming
is necessary, configure the measurement point for FACH to inter-RAT measurement;
otherwise, according to SIB11, the RNC will not send RNC information about GSM
neighbor cells.
MOD CELLMEAS: CELLID=123, INTERFREQINTERRATMEASIND=INTER_RAT,
FACHMEASIND=REQUIRE, FACHMEASOCCACYCLELENCOEF=3;
− Configure the SearchRAT of the GSM network by running the command MOD
CELLSELRESEL.
− After configuration of these information, the SsearchRAT contained in SIB3 is sent
and information about GSM neighbor cells contained in SIB11 are sent.
Data Configuration for Supportint Inter-RAT Handover from WCDMA to
GSM
To support the inter-RAT handover from WCDMA to GSM, configure the following
parameters:
− Add GSM cells and configuration the following data:
MCC
MISSING NEIGHBOR CELL
LAC
CELL ID
NCC
BCC
FREQ_BAND
Frequency number
CIO
− Configure inter-RAT measurement control by running the command MOD
CELLMEAS.