Professional Documents
Culture Documents
Objectives
70%
60%
50%
qQualMin + sSearchRAT ~ -14dB
[%]
40%
30%
• To define optimum re-selection
20%
thresholds it is important to
10%
understand Ec/Io and RSCP
0%
performance profiles for T-Mobile UK
> -4 -4 to - -6 to - -8 to - -10 to -12 to -14 to -16 to -18 to <-21 network
6 8 10 -12 -14 -16 -18 -21
Ec/No [dB]
• Bin sizes important
50%
40%
30%
20%
10%
0%
> -60 -60 to - -70 to - -80 to - -90 to - -100 to - -112 to - < -115
70 80 90 100 112 115
Ec/No [dB]
RSCP (dBm)
-8 -40
EcNo level can be seen to -10 Ec/No (dB) -60
drop much faster -12
-80
-14
compared to RSCP -16
-100
-18 -120
-20 -140
14:14:52.867
14:15:20.097
14:15:55.097
14:16:30.097
14:17:05.098
14:17:41.099
14:18:16.090
14:18:52.091
14:19:28.093
Time
Compare levels
of all GSM cells UE can select WCDMA cell if the level of the
to WCDMA serving GSM and non-serving GSM cells has been
Check quality
of neighbour
WCDMA cells, no UE will re-select WCDMA cell in case it's
priorities between
quality is acceptable:
WCDMA
neighbours CPICH Ec/No Minimum_FDD_Threshold
QqualMin + Ssearch_RAT
= -14dB
QqualMin = -18dB
t
Camping in 3G Camping in 2G Camping in 3G
1f SC332
EcNo=-13dB, 2G Coverage
RSCP=-
113dBm.
Co-Azimuthed:
3G N3G = N2G + Cell2G
2G
2G
UL Quality
Downlink DPCH power UE Tx power CPICH RSCP CPICH Ec/I0
deterioration
UE Reports
GSM RSSI measurements
No GSM cell
meets HO condition ?
Yes
No Is BSCI verification
required for PS call ?
Yes
Initiate Compressed Mode
Configure GSM measurements
UE Reports
GSM BSIC measurements
Initiate Handover
21 © Nokia Siemens Networks Presentation / Author / Date
ISHO 3G -> 2G - AMR Signalling Flow
UE Node RNC CN
B RRC: Measurement
Control ISHO triggering (5
RRC: Measurement Report reasons are
NBAP: Radio Link Reconfiguration possible)
NBAP: Radio Link Reconfiguration Prepare
Ready Initial Compressed
NBAP: Radio Link Reconfiguration Mode
Commit
RRC: Physical Channel Configuration
Reconfiguration
RRC: Physical Channel Reconfiguration
Complete
NBAP: Compressed Mode
Command
RRC: Measurement GSM RSSI
Control Measureme
RRC: Measurement Report
nt
NBAP: Compressed Mode
Command
RRC: Measurement GSM BSIC
Control Identification
RRC: Measurement Report
RANAP: Relocation
Required
RRC: Handover from UTRAN RANAP: Relocation
Command Command
RANAP: IU Release
Command
RANAP: IU Release
Complete
• BSIC verification always performed for AMR calls – no interrupt in voice call
22 © Nokia Siemens Networks Presentation / Author / Date
ISHO 3G -> 2G - PS Signalling Flow
U Node RNC CN
E B RRC: Measurement
Control
RRC: Measurement Report ISHO triggering (5 reasons are
possible)
RANAP: IU Release
Command
RANAP: IU Release
Complete
• In most cases BSIC verification is not required (data interrupt as UE moves to 2G)
• PS makes use of RRC: CELL CHANGE ORDER FROM UTRAN message
23 © Nokia Siemens Networks Presentation / Author / Date
Compressed Mode
Procedure
• RNC informs UE of CM pattern and 2G neighbour list in RRC:
RNC commands the selected
UEs to enter compressed mode Measurement Control message
and provides compressed mode • 3GPP states that the UE must be capable of recording a
parameters and neighbour list minimum number of GSM RSSI measurement samples per
transmission gap
During the DL reception gap UE
can make measurements from 2G • GSM RSSI measurements are made without acquiring GSM
network synchronisation
• UE reports on strongest 6 GSM neighbours at periodic
UE measures RSSI of GSM
interval defined by GSMMeasRepInterval
neighbours and reports these to
RNC periodically • RNC applies a sliding averaging window to the
measurements provided by the UE
RNC commands UE to decode • RNC instructs UE to perform BSIC verification (AMR=always,
BSIC of cell with strongest RSSI PS=as required) using new CM pattern
• BSIC verification needs synchronisation to GSM frame
RNC makes HO decision
IS-HO trigger Target Cell found IS-HO
command
33%
22% 22%
UE does not read any 2G sys info
UE reads 2G sys info but does not send RACH (no cell re-
sel)
0%
UE reads 2G sys info and sends RACH but does not est.
connection (no cell re-sel)
UE reads 2G sys info and completes 2G cell re-sel but
does not send RACH
UE reads 2G sys info and completes 2G cell re-sel and
sends RACH but does not est. connection
56%
32 © Nokia Siemens Networks Presentation / Author / Date
ISHO Failure - No Cell Found Failure Example
Tstart = 17:22:41.7
MW = 12 s
Tstop = 17:22:53.7
POOR GSM
COVERAGE
4 No suitable cell
4 Ta
Ta= activation time Trssi
3
Trssi= RSSI delay time. By default, the 2.0 Tbsic
2 1.3
network only requires the first RSSI 1 Thandover
measurements to choose the best GSM 1
0.2 Total delay
TBSIC=target
Time cell.
for UE to decode the BSIC of the 0
chosen cell
Tactivation
3 2.6 Trssi
2.5 Total
Ta= activation time
2
seconds
Trssi= RSSI delay time. By default, the network only 1.4
1.5 1.2
requires the first RSSI measurements to choose
the best GSM target cell. 1
0.5
0
25
• Tests made with Nokia 7600 UE
20
• The general trend is that the GSM 15
RSSI measurement delay increases
10
as the length of the 2G neighbour list
5
increases. There is however quite a
large scatter 0
0.0 1.0 2.0 3.0 4.0 5.0 6.0
Delay to the first GSM RSSI Measurement (seconds)
• The object of the measurement is the source cell from which the handover is
attempted.
• In case of multiple cells in the AS the object of the measurement is the best cell
of the Active Set during the handover decision (except for
IS_COM_MOD_STA_NOT_POS_(N)RT) where the object is the best active
set cell during the compressed mode preparation phase
• From the measurement point of view the ISHO is divided into two phases:
• Inter-system measurement
• Inter-system handover
41
• Separate counters
© Nokia Siemens Networks
for RT and NRT services
Presentation / Author / Date
Counters for Triggering
Reasons
If compressed mode can NOT start (before sending
RNC Measurement Control to UE) the following counter is
RRC: Measurement Report incremented:
IS_COM_MOD_STA_NOT_POS_(N)RT
CHECK TRAFFIC TABLE
RRC: Measurement Control The counter is updated when: COUNTERS
If the RNC does not find a suitable cell, one of the following
RNC counters are updated:
IS_HHO_NO_CELL_UL_DCH_Q_(N)RT
RRC: ”Measurement report”
(3,4,5) IS_HHO_NO_CELL_UE_TX_PWR_(N)RT
IS_HHO_NO_CELL_DL_DPCH_(N)RT
RRC: ”Measurement Control” IS_HHO_NO_CELL_CPICH_RSCP_(N)RT
IS_HHO_NO_CELL_CPICH_ECNO_(N)RT
RRC: ”Measurement report”
These counters are updated when either:
RRC: ”Measurement report”
• No suitable GSM target cell is found in terms of RSSI
(RxLev)
RRC: ”Measurement report” • Target cell is suitable (RSSI) but BSIC verification fails
And;
Maximum number of measurement reports have been
Triggered in the referncereceived
cell when:
1) GsmMaxMeasPeriod measurement reports are received with an rx level
not suitable
2) GsmMaxMeasPeriod measurement reports are received with a BSIC not
verified
-GsmMaxMeasPeriod = 12
IS_HHO_W_CMOD_DL_DPCH_RT = +1
IS_HHO_NO_CELL_DL_DPCH_RT = +1
The counters are updated in the best cell of the active set
GSM neighbour
IS _ HHO _ W _ CMOD _ xxx _( N ) RT IS _ HHO _ WO _ CMOD _ xxx _( N ) RT
Allcauses Allcauses
planning
KPI is useful for cell
level
47 © Nokia Siemens Networks Presentation / Author / Date
Call Duration and ISHO procedure triggered
• Monitoring how often ISHO procedure is started ISHO Triggering threshold tuning
AVG_RAB_HL D_TM_CS_VOICE/ 6000
Minutes_per_ISHO_procedure_RT
IS_HHO_CMOD_RT IS_COM_MOD_STA_NOT_POS_RT
Allcauses, with& withoutCM
• The KPI on cell level does not take into account user mobility. It does make sense on
cluster/RNC level only
• The KPI can help operators in understanding the ISHO strategy
• Same KPI for NRT
(AVG_DCH_HLD_TM_PS_INTER+AVG_DCH_HLD_TM_PS_BACKG at numerator)
• Service level counter at denominator shall be used because allocation duration
counters (Traffic table) incremented in all the cells within Active Set
• Accuracy of the Indicator affected by:
• the number of ISHO procedures which have no ISHO counter incremented (e.g. drop during
CM, see previous slide)
• number of not successful ISHO procedures during the same call due to e.g. wrong ADJ
parameter, rough mobiles etc. KPI is useful for cluster level and
cell level as well
48 © Nokia Siemens Networks Presentation / Author / Date
ISHO Attempt UTRAN Failure RT
RNC
RRC: ”Measurement report”
(3,4,5)
It’s important to know which is the most frequent
RRC: ”Measurement Control” triggering reason:
IS _ HHO _ W _ CMOD _ xxx _( N ) RT
xxx _ Cause _ perc
IS _ HHO _ W _ CMOD _ xxx _( N ) RT
Allcauses
RRC: ”Measurement report” The counter is triggered when the source RNC receives a
failure message from the mobile with the failure cause
RRC: ”Measurement report”
“configuration unacceptable”.
UE Failure
Counter
RRC: ”Measurement report” The counter is triggered in the same cell where the ISHO
attempt has been updated.
Handover Command
Cell Change Order (PS) Reason for failure:
• Physical channel failure (the UE is not able to establish
Handover Failure x – in the target RAT – the phy. Channel indicated in the
Cell Change Failure
handover command)
ISHO Unsuccess
• Protocol error
Counters • Inter-Rat protocol error
• Unspecified
52 © Nokia Siemens Networks Presentation / Author / Date
Successful ISHO
RNC When the source RNC receives the RANAP message “IU
RRC: ”Measurement report” RELEASE COMMAND” from the core network, one of the
(3,4,5) following counter is triggered:
RRC: ”Measurement Control” SUCC_IS_HHO_UL_DCH_Q_(N)RT
SUCC_IS_HHO_EU_TX_PWR_(N)RT
SUCC_IS_HHO_DL_DPCH_PWR_(N)RT
RRC: ”Measurement report”
SUCC_IS_HHO_CPICH_RSCP_(N)RT
RRC: ”Measurement report” SUCC_IS_HHO_CPICH_ECNO_(N)RT
Handover Command
For RT:
TRelocOverall (def. 8s, from Relocation Command to
CN Iu Release Command) expires.
RRC Drop
Counters IU Release Request
For NRT:
Cell Change Order (PS)
RRC-TmrlRCC = T309+ InterRATCellReselTmrOffset
expires
where: CN
IU Release Request
RRC Drop
Counters T309 parameter = 5 s (SIB1)
InterRATCellReselTmrOffset is hidden parameter 3s
55 © Nokia Siemens Networks Presentation / Author / Date
KPI for ISHO Failure Rate
IS_HHO_CMOD_NRT IS_COM_MOD_STA_NOT_POS_NRT
Allcauses, with& withoutCM
Nbr _ Success _ RT
Overall _ ISHO _ Fail _ Rate _ RT 1
IS_HHO_CMOD_RT IS_COM_MOD_STA_NOT_POS_RT
Allcauses, with& withoutCM
• ISHO success rate on Beckton3 (URKKT03) had always been poor (<80%) with
UTRAN_NOT_ABLE_EXEC_ISHO_RT the largest failure counter (>90% increments on
<6 cells)
UTRAN_NOT_ABLE_EXEC_ISHHO_RT counter
according to customer documentation
PROCEDURE IS
STARTED.....
3 RELOCATION IS REQUIRED TO
MSC...
Timer TRelocPrep (6s) is started
(XX=AMR,CS,NrtPS,RtPS)
3. Decision Algorithm
AdjgTxPwrMaxTCH
AdjgRxLevMinHO (n)
1. Triggering GsmMeasAveWindow
2. GSM measuring
3. Decision Handover Execution
2G-to-3G back prevention
GsmMinHoInterval
1. Triggering process:
• Parameters that belong to this process defines the starting of the GSM measurements:
filters, hysteresis, timers and thresholds
2. GSM Measurement reporting process
• Following parameters control the reporting of the GSM measurements
• GsmMinMeasInterval: Establish minimum time between successive GSM
measurements
• GsmMaxMeasPeriod: Maximum duration of the GSM measurements in CM
• GsmMeasRepInterval: Reporting period of the GSM measurements during CM
3. Decision process:
• Parameters that participate in the selection of the best target cell:
• AdjgRxLevMinHO(n): Minimum RX level of the GSM cell to do handover
4. ISHO cancellation parameters:
• Cancellation parameters are built for CPICH EcNO and CPICH RSCP triggering
functionality only
65 © Nokia Siemens Networks Presentation / Author / Date
ISHO Triggering Process
• Each triggering procedure makes use of filters, hysteresis and thresholds which
are used to control the inter-system handover behaviour
• The purpose of the hysteresis and filters is to improve the accuracy of the
measurements
• The purpose of the thresholds is to control 3G boundary of the different
services
• Each 3G cell had in average 4 GSM neighbour cells.
• By modifying the network configuration (blocking of cells etc), the radio conditions
in each route was aconditioned so that the need for an inter-system handover
was due to the triggering condition studied
• For example, when the UE Tx power trigger was studied, the radio
conditions along the routes were modified so that the uplink path was the
critical one, in this way the IS-HO performance was not affected by other
reasons e.g. poor CPICH EcNo
• During the tests the following traces were recorded:
-The coordinates where the CM starts
66 -Unsuccessful/successful
© Nokia Siemens Networks ISHO events
Presentation / Author / Date
ISHO Triggering Process – Ec/Io Threshold
Different CPICH EcNo thresholds were used with setting 3:
The results show that a threshold= -3 dB is large enough to provide a good performance.
Clearly, the IS-HO performance at the threshold GsmDlTxPrwAMR =–3 dB is the best: excellent
performance (100 % success rate) at medium speeds but degradation occurs at high speed (route
6).
HHoRscpFilterCoefficient 200 ms
HHoRscpTimeHysteresis 100 ms
HHoRscpCancelTime 640 ms
UL Tx Power GsmUETxPwrThrAMR -3 dB
GsmUETxPwrFilterCoeff 10ms
GsmUETxPwrTimeHyst 320ms
DL DCH GsmDLTxPwrThrAMR -3 dB
Cancelation threshold
Trigger threshold
Compressed mode is
reactivated automatically by
8s 10 s the network af ter the
Unsuccessful ISHO GsmMinMeasInterval timer
75 © Nokia Siemens Networks Presentation / Author / Date expires
Handover Decision Process Optimisation
• The Inter-system handover decision process need to be optimized so that the network
selects the best GSM target cell which compliance with the following formula:
• The cancellation thresholds 3dB above the triggering works the best
• Values of the cancellation filters (HHoEcNoCancelTime and
HHoRscpCancelTime) depend actually on coverage i.e. in case of fast
changes then the filters values should be relatively long to avoid possible ping-
pong (initiate IS-HO, cancel, initiate and so on…)
• In case some such ping-pong noted then longer cancellation filters should be
tried
Optimized values
CPICH EcNo
HHoEcNoCancel 3dB above EcNo threshold
HHoEcNoCancelTime 640 ms
CPICH RSCP
HHoRscpCancel 3dB above RSCP threshold
HHoRscpCancelTime 640 ms
kBps
10
kBps
25
3 8
20
2.7 6
2 2.7 15
4 10
1 2.7
2 5
0 0 0
1 Service downgrade due to coverage and CM between
10 to 17 % 1 good and poor 3G coverage areas 1
Summary