02 - 6541 - E01 - Interworking WCDMA To GSM PDF

Content
GSM / WCDMA / LTE Interworking

 Interworking GSM to WCDMA
 Interworking WCDMA to GSM
 Interworking LTE to GSM + WCDMA
 Interworking GSM + WCDMA to LTE
02-1 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

Content
Interworking WCDMA to GSM
 Features and Parameters
 Performance Measurements and KPIs

Content
Features and Parameters
 Introduction
 RAN Parameter Objects for Mobility from 3G to 2G
 Cell Reselection from 3G to 2G
 Urgent ISHO from 3G to 2G
 Non urgent ISHO from 3G to 2G
Performance Measurements and KPIs

Introduction
Motivation for mobility from 3G to 2G
Low conditions on air interface
GSM 900 offers better coverage than WCDMA 2GHz
High RL power consumption in case of low coverage

or high interference level reduces capacity within 3G
WCDMA 2GHz
Traffic balancing
Shift away CS voice traffic from 3G to 2G GSM 900
More capacity available for PS data within 3G

ISHO for
CS voice
3G load
2G load

Introduction
2G neighbors for 3G
In general there are the following types of neighbors
• Intra-frequency
• Inter-frequency
• Inter-system
There are the following types of inter-system neighbors

• 2G
• LTE
The maximum number of inter-system neighbors (2G + LTE) per WCDMA cell is 32
3G neighbor intrafreq 1 3G neighbor interfreq 1 2G/LTE neighbor 1
3G neighbor intrafreq 2 3G neighbor interfreq 2 2G/LTE neighbor 2
3G neighbor intrafreq n 3G neighbor interfreq n 2G/LTE neighbor n ≤ 32

Content
 Introduction
 RNC Parameter Database Objects
 Inter-System Handover Path Object
 Inter-System Adjacency Object
 Inter-System Frequency Measurement Control Object
 WCEL Object

RNC Database Parameter Objects
WSG WANE RNC WLCSE

CMOB WSMLC
IUCS/IUPS IUR
IPQM
COCO
IPNB WBTS WRAB
TQM
ADJD
FMCS ADJS HOPS
FMCI
WCEL ADJI HOPI
FMCG ADJG HOPG
ADJL HOPL

RNC Database Parameter Objects
• RNC = Radio Network Controller • COCO = Radio Network Connection Configuration
• WBTS = WCDMA Base Station • CMOB = Congestion Management OBject
• WCEL = WCDMA Cell • WANE = WCDMA Authorized Network
• ADJ = Adjacency for WCDMA cell • WSG = WCDMA subscriber group
– ADJS = intra-frequency adjacency • WLCSE = WCDMA Location service entity
– ADJI = inter-frequency adjacency • WSMLC = WCDMA Serving Mobile Location
– ADJG = inter-system adjacency GSM Center
– ADJL = inter-system adjacency LTE • IPNB = IP NodeB
– ADJD = detected adjacency • IPQM = IP transmission QoS
• HOP = Handover Path • TQM = Transmission Quality Management
– HOPS, HOPI, HOPG, HOPL • WRAB = WCEL RAB parameters
• FMC = Frequency Measurement Control
FMCS, FMCI, FMCG

Inter-system Handover Path Object
Purpose
HOPG parameters specify requirements to be fulfilled by adjacent 2G cells, so
that they can be used as target cells for
Cell reselection
Inter-system handover
HOPGId = 1
Parameters can be specified using templates Macro cell, RT service
Each template has an identifier set by HOPGId HOPGId
Parameter 1 = ...= 2
The maximum number of HOPG templates is 100 Macro ...
cell, NRT service
nHOPGId
= ...1 = ...= 3
Parameter
Parameter
Templates can be specified e.g. per
Micro...cell, RT service
Cell type (macro, micro…)
nHOPGId
= ...1 = ...= 4
Parameter
Parameter
Service type (RT, NRT) Micro ...
cell, NRT service
Parameter
Parameter n = ...1 = ...
...
Parameter n = ...

Inter-system Handover Path Object
List of parameters

Inter-system Adjacency Object
Purpose
ADJG parameters specify
IDs of adjacent 2G cells
HOPG templates to be applied to adjacent 2G cells
To each adjacent 2G cell two HOPG templates can be assigned for

RT services with parameter RTHopgIdentifier
NRT services with parameter NRTHopgIdentifier
RTHopgIdentifier = 3
NRTHopgIdentifier = 4 RTHopgIdentifier = 1
NRTHopgIdentifier = 2

List of parameters

Rules for planning of 2G adjacencies
2G neighbor lists can be based upon existing BSC 2G neighbor list if 3G and 2G
sites are co-sited
If an operator has both GSM900 and DCS1800 cells then inter-system neighbors
can be defined for one band only
Inter-system neighbor lists are transmitted in SIB11 and dedicated measurement
control messages
The RNC instructs the UE to measure the RxLev of all 2G neighbors, but to verify
the BSIC for one specific neighbor only

Combined 2G neighbor lists in SHO
When a UE is in intra-RNC SHO the neighbor lists belonging to each of the active set cells are
combined
Neighbor lists are not combined for inter-RNC SHO (no support of inter-system neighbor signaling
across Iur)
The RNC generates a new inter-system neighbor list after an active set update procedure, if
compressed mode is not running
In compressed mode the neighbor list valid at the time to trigger the HHO is taken

Combined 2G neighbor lists in SHO
Combining of 2G neighbors is done according the following order
1. Neighbours common to three active set cells
2. Neighbours common to controlling cell and a second active set cell (non controlling cell with highest
CPICH Ec/Io)
3. Neighbours common to two active set cells
4. Neighbours defined for only one active set cell (controlling cell)
5. Neighbours defined only for second ranked cell (according CPICH Ec/Io)
6. Neighbours defined only for the third ranked cell (according CPICH Ec/Io)
If the total number of cells to be measured exceeds the maximum value of 32 during
any step then handover control stops the combined neighbor list generation

Inter-system Frequency Measurement
Control Object
Purpose
FMCG parameters specify
ISHO trigger
How to measure adjacent 2G cells in compressed mode FMCGId = 1
Parameters can be specified using templates Macro cell, RT service

FMCGId
Parameter 1 = ...= 2
Each template has an identifier set by FMCGId
Macro ...
cell, NRT service
The maximum number of FMCG templates is 100
nFMCGId
= ...1 = ...= 3
Parameter
Parameter
Templates can be specified e.g. per Macro
... cell, HSDPA
Cell type (macro, micro…) nFMCGId
= ...1 = ...= 4
Parameter
Parameter
Macro cell,
... HSDPA+AMR
Service type (RT, NRT, HSDPA, HSDPA+AMR)
Parameter
Parameter n = ...1 = ...
If inter-system measurements shall be carried out
HSDPA is switched back to DCH ...
Parameter n = ...

Control Object
List of parameters

Control Object
List of parameters

WCEL Object
Purpose for inter-system mobility
WCEL parameters specify
Trigger of adjacent cell measurements in idle mode
FMCG templates to be applied in 3G cells
To each 3G cell four FMCG templates can be assigned for
RT services with parameter RTFmcgIdentifier
NRT services with NRTFmcgIdentifier
HSDPA services with parameter HSDPAFmcgIdentifier
HSDPA+AMR multi-RAB services with parameter RTwithHSDPAFmcgIdentifier
RTFmcgIdentifier = 1
NRTFmcgIdentifier = 2
HSDPAFmcgIdentifier = 3
RTwithHSDPAFmcgIdentifier = 4

Content
 Introduction
 Cell Reselection and RRC Activity States
 Measurement of Adjacent Cells
 Ranking of Adjacent Cells – S Criterion
 Ranking of Adjacent Cells – R Criterion

Cell Reselection and RRC Activity States
Cell reselection is performed in the following RRC activity states
RRC idle
Cell_PCH state
Cell_FACH state
RRC Connected
Cell_DCH Cell_FACH
No mobility to LTE No mobility to LTE
Cell_PCH URA_PCH
Cell reselection to LTE Cell reselection to LTE
RRC idle
Cell reselection to LTE
Measurement of Adjacent Cells
In general measurements of adjacent cells for cell reselection triggered
by CPICH Ec/Io of serving cell
Ec/Io < Qqualmin + Sintrasearch → UE measures intra-frequency neighbors
Ec/Io < Qqualmin + Sintersearch → UE measures also inter-frequency neighbors
Ec/Io < Qqualmin + SseachRAT → UE measures also 2G neighbors
Qqualmin + Qqualmin + Qqualmin +

SsearchRAT Sintersearch Sintrasearch
Intra-
frequency
No need to
Intra-frequency Intra- measure
Inter-
Inter-frequency frequency neighbour
frequency
cells
Inter-RAT
EC/N0 = -14 dB -10 dB -8 dB

QqualMin Ssearch_RAT SinterSearch SintraSearch
WCEL WCEL WCEL WCEL
-24...0 dB, -18 dB 0...20 dB, 4 dB 0..20 dB, 8 dB 0..20 dB, 10 dB
Ranking of Adjacent Cells – S Criterion
Adjacent cells measured by the UE enter a ranking list, if for these S > 0
Intra-frequency adjacency → both Ec/Io AND RSCP checked
S (Ec/Io) = Ec/Io – AdjsQqualmin
S (RSCP) = RSCP – AdjsQrxlevmin
Inter-frequency adjacency → both Ec/Io AND RSCP checked
S (Ec/Io) = Ec/Io – AdjiQqualmin
S (RSCP) = RSCP – AdjiQrxlevmin
Inter-system adjacency → RxLev checked only
S = RxLev – AdjgQrxlevmin
AdjsQqualMin AdjsQrxlevMin
HOPS HOPS
-24...0 dB, -18 dB -119..-25 dBm, -115 dBm
AdjiQqualMin AdjiQrxlevMin
HOPI HOPI S>0?
-24...0 dB, -18 dB -119..-25 dBm, -115 dBm
AdjgQrxlevMin Adjacent cell

HOPG
-115..-25 dBm, -101 dBm

Ranking of Adjacent Cells – R Criterion
If there are adjacent 2G cells with S > 0 → 1st ranking according coverage
Serving cell
Qhyst1/Qhyst1PCH/Qhyst1FACH
Rs = RSCP + Qhyst1 WCEL
Qhyst1 makes server optionally more attractive 0.. 40 dB, 0 dB
Qhyst1 can be set individually for idle, Cell_PCH and Cell_FACH state
Adjacent cell Adjs/Adji/AdjgQoffset1
Rn = RSCP (or RxLev) – Qoffset1 ADJS/ADJI/ADJG
Qoffset1 makes adjacency optionally more or less attractive -50..50 dB, 0 dB
S>0
Rs = RSCP + Qhyst1
Rn= RSCP (or Rxlev) - Qoffset1
No Yes
Rn (GSM) > Rs (WCDMA)
See next slide Cell re-selection to GSM

cell with highest R
Ranking of Adjacent Cells – R Criterion
If a 3G cell is on top of 1st ranking list → 2nd ranking according Ec/Io
Serving cell
Qhyst2/Qhyst2PCH/Qhyst2FACH
Rs = Ec/Io + Qhyst2 WCEL
Qhyst2 makes server optionally more attractive 0.. 40 dB, 2 dB
Qhyst2 can be set individually for idle, Cell_PCH and Cell_FACH state
Adjacent cell Adjs/AdjiQoffset2
Rn = Ec/Io – Qoffset2 ADJS/ADJI
-50..50 dB, 0 dB
Qoffset2 makes adjacency optionally more or less attractive
The cell of highest R is selected

Content
 Introduction
 Urgent ISHO Process
 Urgent ISHO Trigger
 Compressed Mode
 Inter-System Measurements
 Target Cell Selection
 ISHO Cancellation

Urgent ISHO Process
Urgent ISHO means, that the UE must be shifted from 3G to 2G
because of low performance on the air interface
UE informs RNC about bad performance of active set

(e.g. too low CPICH EC/I0 or RSCP)
RNC commands UE to perform intersystem

measurements in compressed mode
UE reports RNC about performance of active set and best

intersystem adjacent cells
RNC selects optimum target cell and commands UE to enter it

Urgent ISHO Trigger
To trigger urgent ISHO, five different causes are offered by Nokia
All of them can be activated / deactivated individually
1) Low measured 1 and 2 are triggered, when 2) Low measured

CPICH Ec/No (Event 1F) all active cells report 1F CPICH RSCP (Events 1F)
FMCG GSMcauseCPICHEcNo FMCG GSMcauseCPICHrscp
3) UE power approaches maximum Measurement 4) DL DPCH approaches

allowed power (event 6A) maximum allowed power
Trigger
FMCG GSMcauseTxPwrUL FMCG GSMcauseTxPwrDL
4 is triggered, when one
cell reports
5) Quality deterioration report Values for all parameter

from UL outer loop PC
0 (not used) / 1 (used)
FMCG GSMcauseUplinkQuality

Trigger Ec/Io
Event 1F
RNC commands the UE to measure inter-frequency / inter-system adjacencies if event 1F occurs
For all active cells Ec/Io becomes less than an absolute threshold during a time hysteresis
If both inter-frequency and inter-system HO is enabled, inter-system measurements are

performed only after an unsuccessful IFHO attempt
Event 1E
RNC commands the UE to stop inter-frequency / inter-system measurements if event 1E occurs
For one active cell Ec/Io becomes better than an absolute threshold during a cancel time
Hereby the following conditions must be fulfilled
• IFHO → unsuccessful attempt
• ISHO → unsuccessful attempt or ISHO cancellation activated
UE applies filtering of the Ec/Io measurements specified by the Ec/Io filter

coefficient

Trigger Ec/Io
Ec/Io
Cell 1 EcNoFilterCoefficient
FMCS, 200…1600 ms, 600 ms
Cell 2
All active
1E: HHoEcNoCancel cells bad
FMCS, -24…0 dB, -9 dB 1F: HHoEcNoThreshold
FMCS, -24…0 dB, -12 dB
Cell 3
Time
1E: HHoEcNoCancelTime 1F: HHoEcNoTimeHysteresis

FMCS, 0..5000 ms, 1280 ms FMCS, 0..5000 ms, 100 ms

Trigger Ec/Io
Possible scenario for event 1F
Different HhoEcNoThreshold for different services
RT -12 dB
NRT R99 -14 dB
NRT HS -16 dB
No ISHO
ISHO for RT only
ISHO for RT and NRT R99
ISHO for all services

Trigger RSCP
Event 1F
RNC commands the UE to measure inter-frequency / inter-system adjacencies if event 1F occurs
For all active cells RSCP becomes less than an absolute threshold during a time hysteresis

Event 1E
RNC commands the UE to stop inter-frequency / inter-system measurements if event 1E occurs
For one active cell RSCP becomes better than an absolute threshold during a cancel time
UE applies filtering of the RSCP measurements specified by the RSCP filter

coefficient

Trigger RSCP
RSCP
HhoRscpFilterCoefficient
FMCS, 200…1600 ms, 200 ms
Cell 2
All active
1E: HHoRSCPCancel cells bad
FMCS, -115…-25 dBm, -102 dBm 1F: HHoRSCPThreshold
FMCS, -115…-25 dBm, -105 dBm
Cell 3
Time
1E: HHoRSCPCancelTime 1F: HHoRSCPTimeHysteresis

FMCS, 0..5000 ms, 1280 ms FMCS, 0..5000 ms, 100 ms

Trigger UE Power
Event 6A
RNC commands the UE to measure inter-frequency / inter-system adjacencies if event 6A occurs
• The UE power exceeds an absolute threshold
• There is no time hysteresis
The power threshold can be set individually
• Per type of service (AMR, CS data, PS RT, PS NRT)
• IFHO and ISHO
• The threshold is set relative to the maximum UE power in the cell
Priority of IFHO and ISHO
• The threshold exceeded first defines, which type of HHO has higher priority
• If there is the same threshold both for IFHO and ISHO, IFHO has higher priority
Dependence on bit rate
In case of high bit rate > HhoMaxAllowedBitRateUL dynamic link adaptation is performed instead
of HHO
HhoMaxAllowedBitRateUL
WCEL, 32…512 kbps, 32 kbps

Trigger UE Power
Event 6B
RNC commands the UE to stop inter-frequency / inter-system measurements if event 6B occurs
The UE power falls below the absolute threshold again during a hysteresis time
UE applies filtering of the power measurements specified by the UE power filter

coefficient

Trigger UE Power
UE power
UEtxPowerMaxDPCH GSMUETxPwrFilterCoeff
WCEL, -50…33 dBm, 24 dBm FMCG, 10…480 ms, 10 ms
min (UEtxPowerMaxDPCH, UE power class)
UE Power Threshold
GSMUETxPwrThrAMR/CS/RtPS/NrtPS
6A FMCG, -10…0 dB, -3/-3/-1/-3 dB
6B
time to trigger immediately time
GSMUETxPwrTimeHyst
FMCG, 0…5000 ms, 1280 ms

Trigger UE Power
Possible scenarios for event 6A (analogue for DL radio link power)
First downgrade of R99 bit rate / AMR codec
If bit rate ≤ HhoMaxAllowedBitRateUL / AMR codec at minimum, than ISHO
triggered
384 kbps
12.2 AMR
128 kbps
7.95 AMR
64 kbps
32 kbps ISHO
5.9 AMR
4.75 AMR

Trigger DL Radio Link Power
Too high RL power
RNC commands the UE to measure inter-frequency / inter-system adjacencies if for one active cell
the following event occurs
• DL RL power exceeds an absolute threshold
The power threshold can be set individually
• Per type of service (AMR, CS data, PS RT, PS NRT)
• IFHO and ISHO
• The threshold is set relative to the maximum DL RL power determined by admission control
Priority of IFHO and ISHO
• The threshold exceeded first defines, which type of HHO has higher priority
• If there is the same threshold both for IFHO and ISHO, IFHO has higher priority
In case of high bit rate > HhoMaxAllowedBitRateDL dynamic link adaptation is performed instead of
HHO HhoMaxAllowedBitRateDL

Acceptable DL RL power again
RNC commands the UE to stop inter-frequency / inter-system measurements if the following
event occurs
• DL RL power falls below an absolute threshold again
• The cancel threshold is set relative to the triggering threshold

DL RL power GSMDLTxPwrThrAMR/CS/RtPS/NrtPS
FMCG, -10…0 dB, -3/-3/-1/-3 dB
Maximum allowed power on DPCH
DL RL Power Threshold
DLDPCHTxPwrClOfffset
Trigger HHO FMCG, -6…0 dB, -3 dB
time
immediately
Cancel HHO
immediately

Trigger UL Quality
UL SIR target at maximum
RNC commands the UE to measure inter-frequency / inter-system adjacencies if the following
event occurs
• Outer loop PC sends quality deterioration report
• Quality deterioration reporting must be enabled with EnableULQualDetRep
• The reporting period is set with ULQualDetRepThreshold

In case of high bit rate > HhoMaxAllowedBitRateUL dynamic link adaptation is performed instead
of HHO
EnableULQualDetRep ULQualDetRepThreshold
RNC, 0…1, 0 = disabled RNC, 0.5…10 s, 0.5 s
HhoMaxAllowedBitRateUL

Trigger UL Quality
UL SIR target not at maximum anymore
RNC commands the UE to stop inter-frequency / inter-system measurements if the following
event occurs
Outer loop PC does not send quality deterioration report any more

Trigger UL Quality
1st Quality deterioration report from PC to HC inside RNC

UL SIR target
2nd Quality deterioration report (as long SIR target at maximum
the message is periodically repeated)
Max SIR target
SIR
SIR
Min SIR target
ULQualDetRepThreshold time
RNC, 0.5…10 s, 0.5 s

Compressed Mode
Purpose
Used to create gaps in transmission during which adjacent cell measurements on another
frequency can be made
Gaps can be created using single or double frame approach (Nokia supports both)
Activation
Compressed mode enabled with CMmasterSwitch
CMmasterSwitch
RNC, 0…1, 0 = enabled
Instantaneous power
Measurement gap
/ data rate
Compressed
frame
Normal frame Normal frame

Compressed Mode
Consequences
Same data amount sent in a shorter time
→ more power needed during CM (both in UE and BTS)
 affects WCDMA Coverage (total coverage reduction < 2.1 dB)
Fast Power control information might be lost during gap
→ higher Eb/No required
 affects WCDMA Capacity (capacity degradation < 2%)
Compressed frames may be lost if power control not set correctly
 affects WCDMA Quality
In case of inter-system measurements HSPA is switched back to DCH (in case of inter-frequency
measurements HSDPA still is available)

Compressed Mode Methods
Length of gap
3, 4, 5, 7 timeslots
Single-frame method
TGL
radio frame radio frame
Length of gap
Double-frame method 3, 4, 5, 7, 10, or 14 timeslots
TGL
radio frame radio frame
Minimum transmitted time slots per frame  8

Spreading factor halving
Doubles temporarily physical channel data rate
• 3 dB more UE power required
• High occupation of codes with low SF
• If CM blocked due to lack of free code, secondary scrambling code might be allowed with
AltScramblingCodeCM
Method applied to following services
• AMR
• CS and PS RT data
• Multi RAB, if one RAB is RT
In case of spreading factor halving single frame method is used
AltScramblingCodeCM
WCEL, 0…1, 0 = allowed

Higher layer scheduling
DCH user data rate reduced
• No extra power consumption
• No extra code occupation
• HLS ¾ data rate or HLS ½ data rate possible with HLSModeSelection
Method applied to following services
PS NRT data only
Single or double frame method in dependence on data rate reduction
• ¾ → double frame
• ½ → single frame
HLSModeSelection
RNC, 0…1, 0 = HLS ½

Compressed Mode Limitations
DL/UL
power
Overload
No new UE can be in CM
Critical load
PtxOffset/ MaxNumberUECmHO
PrxOffset One new UE in CM still allowed
RNC, 0…255, 16
PtxTarget/
MaxNumberUEHSPACmHO
PrxTarget
RNC, 0…127, 10
New UEs can be switched to CM if

Load < Pxx_Target (both on UL and DL) AND
Total number of UEs in CM < MaxNumberUECmHO AND
Number of UEs with HSDPA in CM < MaxNumberUEHSPACmHO
Load

Inter-system Measurements
Process
After HO triggering RNC sends RRC ”Measurement Control” message to UE
• List of 2G cells to be measured
• Compressed mode settings
UE RRC ”Measurement control ” message RNC

(GSM RSSI measurements)
Now UE performs reporting about measured 2G cells

• Periodic reporting
• Maximum of 6 strongest cells according RxLev reported
• No filtering
UE RNC
RRC ”Measurement report”
RRC ”Measurement report”
RNC processing of UE measurements

• Sliding averaging window applied to dBm values
• Averaged RxLev values taken to select ISHO target
Timing Aim of GSMNcellSearchPeriod
Wait until enough measurements of 2G cells are available for
RNC to identify target cell
Value N means, that N measurement reports need to arrive in
RNC commands WBTS RNC to decide
and UE to perform CM
GSMNcellSearchPeriod GSMMaxMeasPeriod
FMCG, 0…20, 0 = not used FMCG, 1…120, 6
RNC starts sliding window Size of sliding window

Trigger
no IFHO allowed IFHO allowed
T=0 t
GSMMeasAveWindow
FMCG, 1…32, 6
Size of sliding window
If no target cell found, procedure may restart

if trigger occurs again after
GSMMeasRepInterval GSMMinMeasInterval
FMCG, 0.5…4 s, 0.5 s FMCG, 1…60 s, 2 s
Periodic reporting
BSIC verification
After selection of target GSM cell, RNC sends to UE again RRC “Measurement Control” message,
but now including details to measure BSIC
UE stops RSSI measurements and applies compressed mode settings used for BSIC decoding
Measurement reports again sent periodically to RNC
If UE cannot decode BSIC during given period, BSIC measurement operation is aborted
ISHO trigger Target cell found ISHO command
WCDMA RSSI measurements BSIC verification

TRSSI depends on TBSIC depends on
Numbers of GSM cells in Transmission gap pattern
RRC ”Measurement control ” message neighbor cell list
(BSIC decoding) for BSIC decoding
Reporting interval
RNC
Sliding averaging window
Transmission gap pattern

for RSSI measurements

Target Cell Selection
Coverage criterion
Best 2G cell must fulfill following criterion
AVE_RXLEV_NCell(n) > AdjgRxLevMinHO(n) + max (0, AdjgTxPwrMaxTCH(n) - P_max)
AVE_RXLEV _Ncell(n) = averaged GSM carrier RSSI value of GSM neighbor n
AdjgRxLevMinHO(n) = minimum required RSSI level of GSM neighbor n
AdjgTxPwrMaxTCH(n) = maximum Tx power level an UE may use in GSM neighbor n
P_MAX = maximum UE power capability
Priority criterion
If several GSM cells fulfill equation above, these are ranked based on priorities defined with
AdjgPriorityCoverage
The cell with highest priority is selected, even if it does not offer the best coverage
AdjgPriorityCoverage
HOPG, 0…7, 0

AVE_RXLEV_NCell(n) > AdjgRxLevMinHO(n) + max(0, AdjgTxPwrMaxTCH(n) - P_max)
GSM cell
AdjgRxLevMinHO AdjgTxPwrMaxTCH
HOPG, -110…-47 dBm, -95 dBm ADJG, 0…43 dBm, -
AdjgRxLevMinHO(n)
DL good enough
max(0, AdjgTxPwrMaxTCH(n) - P_max)

UE has not enough power

ISHO Cancellation
Idea
Avoid unnecessary ISHO, if air interface improves again
• Update of active set
• Improvement of actual active set itself
Feature must be activated with ISHOCancellation (otherwise ISHO cancellation is possible after
unsuccessful attempt only)
UE RNC
Activate CM and measurements UE or RAN trigger

starts ISHO
UE measures GSM
but also Intra-
frequency Reporting event relevant for cancellation: 1A,1C,1E, 6B
or RAN internal
event allows
cancellation (DL RL
power, UL SIR target)
Cancel CM and measurements
ISHOCancellation
RNC, 0…1, 0 = disabled
ISHO Cancellation
Process
ISHO measurements take place several seconds
During that time conditions in WCDMA layer may change directly or by active set update
Cancel pending ISHO process → reduced system load
Less UEs in compressed mode
Less signaling traffic
Limitations
No cancellation as long measurement phase is running
Number of cancellation per UE and active set must be less than MaxNumISHOClPerAS
MaxNumISHOClPerAS
RNC, 1…5, 1

Content
 Introduction
 Non urgent ISHO process
 Non urgent ISHO trigger
 Selection of ISHO candidates
 Inter-system measurements
 Target cell selection

Non Urgent ISHO Process
Air interface performance good enough, but one of the following problems
High load within 3G → load based ISHO
2G matches running service better than 3G → service based ISHO
Load based
Constant monitoring of load
handover
HO
triggers
Service based Periodical check
handover
Selection of Execute
Handover
connections to be Measurements handover
decision
handed over

Non urgent ISHO can be enabled per type of service
SLHOUseBackgroundPSNRTData
SLHOUseInteractivePSNRTData
SLHOUseStreamPSRTData
SLHOUseStreamCSNTData (CS non-transparent data)
SLHOUseConvPSRTData (e.g. video conference)
SLHOUseConvPSSpeech (e.g. VoIP)
SLHOUseConvCSTData (CS transparent data)
SLHOUseConvCSSpeech (AMR)
SLHOUseXXX
RNC, 0 = no HO or 1 = load based HO or 2 = service based HO or 3 = both, 0

Example
Service type HO type
Conversational, CS speech Load & Service HO
Conversational, CS transparent data Load & Service HO
Conversational, PS speech Load HO
Conversational, PS RT data Load HO
Streaming, CS non-transparent data Service HO
Streaming, PS RT data Service HO
Interactive, PS NRT data None
Background, PS NRT data None

Load Trigger
Overview
NRT rejection rate on UL

Total interference on UL
Spreading code usage (DL

NRT rejection rate on DL
HW / logical resource
Total power on DL
Hard blocking
Due to BTS / AAL2
usage
only)
PS NRT If ONE of the reasons is
Total DL power / Lack of DL HW / logical fulfilled cell is in
capacity
UL interference spreading resource load based handover
request state
load codes limitation
rejection rate

Load Trigger
DL power / UL interference
Cell put into load based hand over state, if R99 load comes to close to the load target
• PrxTotalnonHSPA > PrxTarget + LHOPwrOffsetUL
• PtxTotalnonHSPA > PtxTarget + LHOPwrOffsetDL
If HSPA is present, the load target due to dynamic HSPA power is used
The load is evaluated every RRI period
LHOPwrOffsetUL LHOPwrOffsetDL
WCEL, -10…0 dB, -0.7 dB WCEL, -30…0 dB, -1.5 dB

Load Trigger
NRT capacity request rejection rate
Cell put into load based hand over state, if NRT capacity request rejection rate exceeds threshold
• CapaReqRejRateUL > LHOCapaReqRejRateUL
• CapaReqRejRateDL > LHOCapaReqRejRateDL
To avoid unwanted load based ISHO due to very few events, the rejection rate is modified by the
margin LHONRTTrafficBaseLoad
The rejection rate is evaluated every second
RejectedRequestsCellUL
CapaReqRejRateUL =
(AllCapacityRequestsCellUL + LHONRTTrafficBaseLoad)
RejectedRequestsCellDL
CapaReqRejRateDL =
(AllCapacityRequestsCellDL + LHONRTTrafficBaseLoad)
LHOCapaReqRejRateUL LHOCapaReqRejRateDL LHONRTTrafficBaseLoad

WCEL, 0…100 %, 70% WCEL, 0…100 %, 70% WCEL, 0…255, 10

Load Trigger
Code tree occupation
Cell put into load based hand over state, if code tree occupation exceeds threshold
Code tree occupation > LHOResRateSC
The code tree occupation is evaluated every RRI period
The occupation is considered for SF 128
LHOResRateSC
WCEL, 0…100 %, 80%
C3 (0)=(…)
C 2 (0)=(1,1,1,1)
C3 (1)=(…)
C1 (0)=(1,1)
C3 (2)=(…)
C 2 (1)=(1,1,-1,-1)
C3 (3)=(…)
C 0 (0)=(1)
C3 (4)=(…)
C 2 (2)=(1,-1,1,-1)
C3 (5)=(…)
C1 (1)=(1,-1)
C3 (6)=(…)
C 2 (3)=(1,-1,-1,1)
C3 (7)=(…)
Code Order Code Order Code Order Code Order
0 (SF 1) 1 (SF 2) 2 (SF 4) 3 (SF 8)

Load Trigger
Blocking rate due to BTS and AAL2
Cell put into load based hand over state, if blocking rate due to BTS and AAL2 exceeds threshold
Blocking rate > LHOHardBlockingRatio
To avoid unwanted load based ISHO due to very few events, the blocking rate is modified by the
margin LHOHardBlockingBaseLoad
The rejection rate is evaluated every second
NumberOfSamplesHardBlocking
Blocking rate =
(AllSamplesHWhuntDuringMeasPeriod + LHOHardBlockingBaseLoad)
WSP capacity IuB AAL2 capacity
LHOHardBlockingRatio LHOHardBlockingBaseLoad
WCEL, 0…100 %, 50% WCEL, 0…255, 10

Load Trigger
Activation / deactivation of load based handover state
LHO state "ON" LHOs Activation of new LHO state "OFF"

Indication broadcasted started LHOs stopped Indication broadcasted
LHO phase t
Averaging of load with If load state remains Averaging of load with If load remains low for
sliding window for the time sliding window the time
LHOWinSizeOnXXX LHOHystTimeXXX, LHOWinSizeOffXXX LHODelayOffXXX, cell
ISHOs are started no longer in load based
If one threshold If load below all handover state
exceeded, cell in load thresholds again, no
based handover state further ISHOs are started
LHOWinSizeOnXXX LHOHystTimeXXX LHOWinSizeOffXXX LHODelayOffXXX

WCEL, 0…60 s, WCEL, 0…10 s, 2 s WCEL, 0…60 s, 15 s WCEL, 0…255 s, 30 s
0 s = trigger disabled

Load Trigger
Activation / deactivation of load based handover state
For each load trigger there is a set of the four parameters just discussed
• High DL power or UL interference → XXX = Interference
• High NRT capacity rejection rate → XXX = CapaReqRejRate
• High code tree occupation → XXX = ResRateSC
• High blocking due to BTS and AAL2 → XXX = HardBlocking

Service Based ISHO
No specific trigger
RNC just checks periodically according ServHOPeriodInterRAT, whether there
are ISHO candidates present
ServHOPeriodInterRAT
WCEL, 0…120 s, 0 s = service based ISHO disabled
WCDMA cell
HO candidates

Selection of ISHO Candidates
Maximum number of ISHO candidates
For each type of ISHO a maximum number of UEs can be selected as handover candidates
• Load based handover → maximum number of candidates = LHOnumbUEinterRAT
• Service based handover → maximum number of candidates = ServHOnumbUEinterRAT
Not all candidates might be set into compressed mode
• Maximum number of UEs in compressed mode due to load / service based handover
limited by MaxNumberUEcmSLHO (R99 service running) or MaxNumberUEHSPAcmNCHO
(HSDPA running)
• If both types of handover shall be performed in the cell simultaneously, load based
handover has higher priority
LHOnumbUEinterRAT ServHOnumbUEinterRAT
WCEL, 0…32, 0 = load based ISHO disabled WCEL, 0…32, 1
MaxNumberUEcmSLHO MaxNumberUEHSPAcmNCHO
WCEL, 0…32, 6 WCEL, 0…31, 5

Role of network layering
UE can be candidate if the following conditions are fulfilled
• UE not in preferred RAT or hierarchical WCDMA layer
• Preferred RAT or hierarchical WCDMA layer is available
Preferred layer defined in combined service priority list
• Preferred layer is priority 1 layer in the list
• Priority 2 and 3 layers are can be selected in load based HO procedure, but not in
service based one
Availability of target layer depends on
• Definition of target cells in neighbour list
• Load of the target cells

Load based handover LHO
1. connections for which S-RNC is this RNC

2. connections not performing HO
measurements
3. connections without previous LHO attempts in

this cell within a certain period
Steps 1-5 always performed
4. NRT connections lasting longer than LHOminNrtDchAllocTime
LHOminNrtDchAllocTime RNC, 0…60 s, 20 s
5. connections which are not in preferred RAT or

WCDMA hierarchical cell layer
6. connections which cause highest load in the

cell depending on the load trigger
7. connections not requiring
compressed mode Steps 6-8 only performed, if more
connections than maximum
8. random selection of allowed number of candidates
remaining after steps 1-7
Service based handover ServHO
1. connections for which S-RNC is this RNC

2. connections not performing HO
measurements
3. connections without previous ServHO

attempts in this cell within a certain period
Steps 1-5 always performed
4. RRC connections being in CELL_DCH
5. connections which are not in preferred RAT or

WCDMA hierarchical cell layer
6. connections not requiring

compressed mode Steps 6-7 only performed, if more
connections than maximum
7. random selection of
allowed number of candidates
remaining after steps 1-6

Role of network layering
Algorithm shown on the previous pages performed in three steps
Phase 1
Connections with Priority 1 target layer available selected as candidates (if no such
connections present, no service based HO is performed)
Phase 2
Connections with Priority 2 target layer available selected as candidates
Phase 3
Connections with Priority 3 target layer available selected as candidates
If even after 3rd phase no RRC connection can be selected, no load / service based HO
procedures are performed

Construction of combined service priority list
Combined service priority list constructed from following input
• Layer priority defined within core network (MSC, SGSN)
• Layer priority defined within RNC
Iu interface service Target System

priority information Combined for SLHO
Service Priority Preferred RAT or
list Hierarchical
RNC based service WCDMA layer
priority handover profile
table

Layer priority defined within RNC
Preferred layer can be specified per type of service
SLHOProfileBackgroundPSNRTData
SLHOProfileInteractivePSNRTData
SLHOProfileStreamPSRTData
SLHOProfileStreamCSNTData (CS non-transparent data)
SLHOProfileConvPSRTData (e.g. video conference)
SLHOProfileConvPSSpeech (e.g. VoIP)
SLHOProfileConvCSTData (CS transparent data)
SLHOProfileConvCSSpeech (AMR)
SLHOProfileXXX
RNC, not defined / GSM / WCDMA / WCDMA micro / WCDMA macro, not defined

Layer priority defined within RNC (example)
Service type Preferred system/layer

Conversational, CS speech GSM
Conversational, CS-T data WCDMA
Conversational, PS speech WCDMA
Conversational, PS RT data WCDMA
Streaming, CS-NT data WCDMA macro
Streaming, PS RT data WCDMA macro
Interactive, PS NRT data WCDMA micro
Background, PS NRT data Not defined

Layer priority defined within core network
Iu interface service priority information
• Defines target system for load / service based handover
• Information is RAB based and optional
Service handover information element received from Iu interface via RANAP RAB ASSIGNMENT
REQUEST provides the following alternatives
1. Handover to GSM should be performed (GSM higher priority)
2. Handover to GSM should not be performed (WCDMA higher priority)
3. Handover to GSM shall not be performed (only WCDMA)
Nokia settings
• Always = 2 within SGSN
• Settable within MSC for the services speech, CS data < 32 K and CS data ≥ 32 K

Combined service priority list
Service priority defined within core network has higher priority than that defined within RNC
• If service priority defined within core network not available → service priority defined
within RNC used
• If service priority defined within core network available → service priority defined within
core network used
• If both core and RNC define WCDMA as preferred layer, RNC definition (macro or micro
layer preferred) used

Combined service priority list – core network service priority not available
RNC based service
Combined service priority list
priority information
GSM 1. GSM Priority 1 = Preferred Layer for RAB in

2. GSM
• Service based HO
3. WCDMA
WCDMA 1. • 1st phase of load based HO
2. WCDMA Priority 2 layer for RAB in
3. GSM
• 2nd phase of load based HO procedure
WCDMA macro 1. WCDMA macro layer
Priority 3 Layer for RAB in
2. WCDMA
3. GSM • 3rd phase of load based HO procedure

WCDMA micro 1. WCDMA micro layer
2. WCDMA
3. GSM
Not defined 1.
2. WCDMA
3. GSM

Combined service priority list – core network service priority available
Handover to GSM should not be performed Handover to GSM should be performed
RNC based service Combined service RNC based service Combined service
priority information priority list priority information priority list
GSM 1. GSM 1. GSM
2. WCDMA 2. GSM
3. GSM 3. WCDMA
WCDMA 1. WCDMA 1. GSM
2. WCDMA 2. GSM
3. GSM 3. WCDMA
WCDMA macro 1. WCDMA macro layer WCDMA macro 1. GSM
2. WCDMA 2. WCDMA macro layer
3. GSM 3. WCDMA
WCDMA micro 1. WCDMA micro layer WCDMA micro 1. GSM
2. WCDMA 2. WCDMA micro layer
3. GSM 3. WCDMA
Not defined 1. Not defined 1. GSM
2. WCDMA 2. GSM
3. GSM 3. WCDMA

Traffic balancing example Combined service
priority list
Shift PS NRT traffic to WCDMA Micro layer
1. WCDMA micro
• SLHOUseInteractivePSNRTData = ‘Load & Service based HO’ layer
• SLHOprofileInteractivePSNRTdata = ‘WCDMA micro layer’ 2. WCDMA
3. GSM
• Service Handover IE: Handover to GSM should not be performed
Shift PS RT traffic to WCDMA Macro layer
• SLHOUseInteractivePSRTData = ‘Load & Service based HO’ 1. WCDMA

macro layer
• SLHOprofileInteractivePSRTdata = ‘WCDMA macro layer’ 2. WCDMA
• Service Handover IE: Handover to GSM should not be performed 3. GSM
Shift AMR traffic to GSM layer due to load
• SLHOUseConvCSSpeech = ‘Load based HO’ 1. GSM
• SLHOprofileConvCSspeech= ‘GSM’ 2. GSM
3. WCDMA
• Service Handover IE: Handover to GSM should be performed

Traffic balancing example
1. WCDMA 1. WCDMA 1. GSM Service based HO /
micro layer macro layer
2. GSM 1st phase load based HO
2. WCDMA 2. WCDMA
3. WCDMA 2nd phase load based HO
3. GSM 3. GSM
PS PS
AMR WCDMA
NRT RT
Macro
1st 2nd 1st
WCDMA
Micro
No HO for PS RT, as already
in preferred layer
GSM

Compressed mode performed by the same way as for urgent ISHO
Timing of inter-system measurements very similar as for urgent ISHO
After an unsuccessful ISHO attempt compressed mode can be started again after the time
GSMMinMeasInterval
After an successful load / service based ISHO for the same RRC connection the next attempt can
be started after the time GSMMinSLHOInterval
GSMMinMeasInterval
FMCG, 1…60 s, 2 s
GSMMinSLHOInterval
FMCG, 1…120 s, 30 s

Coverage criterion
Best 2G cell must fulfill following criterion
AVE_RXLEV_NCell(n) > AdjgMinRxLevNCHO(n) + max (0, AdjgTxPwrMaxTCH(n) - P_max)
AVE_RXLEV _Ncell(n) = averaged GSM carrier RSSI value of GSM neighbor n
AdjgMinRxLevNCHO(n) = minimum required RSSI level of GSM neighbor n
AdjgTxPwrMaxTCH(n) = maximum Tx power level an UE may use in GSM neighbor n
P_MAX = maximum UE power capability
Priority criterion
If several GSM cells fulfill equation above, these are ranked based on priorities defined with
AdjgPrioritySLHO
The cell with highest priority is selected, even if it does not offer the best coverage
AdjgPrioritySLHO
HOPG, 0…7, 0

AVE_RXLEV_NCell(n) > AdjgMinRxLevNCHO(n) + max(0, AdjgTxPwrMaxTCH(n) -
P_max)
GSM cell
AdjgMinRxLevNCHO AdjgTxPwrMaxTCH
HOPG, -110…-47 dBm, -95 dBm ADJG, 0…43 dBm, -
AdjgMinRxLevNCHO(n)
DL good enough
max(0, AdjgTxPwrMaxTCH(n) - P_max)

UE has not enough power

Role of Load
Exact load of target GSM cell not checked by source RNC in case of service or load based ISHO
Target BSC checks load situation and rejects handover if necessary
Than relocation to GSM unsuccessful and RANAP Relocation Preparation Failure received from CN
If HO to GSM cell has failed → SLHO prevented during the time AdjgPenaltyTimeNCHO
AdjgPenaltyTimeNCHO
HOPG, 0…60 s, 10 s

Content

Signaling Flow for ISHO
Monitoring of Urgent ISHO from 3G to 2G
Monitoring of Non Urgent ISHO from 3G to 2G
Monitoring of Relocation between RNC and BSC
Monitoring Example

Signalling Flow for ISHO - CS
UE BTS RNC MSC
RRC: Measurement Report (e.g. event 1F)
NBAP: RL reconfig. prepare
NBAP: RL reconfig. ready
NBAP: RL reconfig. commit UE put into
compressed mode
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete
NBAP: CM command
RRC: Measurement Control RxLev
RRC: Measurement Report measurements
NBAP: CM command
RRC: Measurement Control BSIC verification
mandatory to avoid
RRC: Measurement Report interruption of AMR call
RANAP Relocation required
RANAP Relocation command ISHO
RRC: HO from UTRAN Command execution
RANAP Iu release command
RANAP Iu release complete
Signalling Flow for ISHO - CS
UE BTS RNC SGSN
RRC: Measurement Report (e.g. event 1F)
NBAP: RL reconfig. ready
NBAP: RL reconfig. commit UE put into

compressed mode
RRC: Physical Channel Reconfiguration Complete
NBAP: CM command
RRC: Measurement Control RxLev
RRC: Measurement Report measurements
RRC: Cell Change Order from UTRAN
RANAP SRNS Context Request

BSIC verification not mandatory for NRT
Data transfer can be interrupted when ISHO RANAP SRNS Context Response
moving to 2G execution
RANAP SRNS Data Forward Command
RANAP Iu release command

Content
► Features and Parameter
► Performance Measurements and KPIs
 Signaling Flow for ISHO
 Monitoring of Urgent ISHO from 3G to 2G
Counter Structure
Compressed Mode Counter
HHO Counter
HHO KPI
 Monitoring of Non Urgent ISHO from 3G to 2G
 Monitoring of Relocation between RNC and BSC
 Monitoring Example

Counter Structure
No cell found UTRAN failure

counters counters
Target cell found

HHO attempt UE failure
counters counters
Measurement
ISHO trigger
CM started
Unsuccessfull
ISHO counters
RRC drop
counters
No counter triggered, if
GSMMaxMeasPeriod expires AND
less than GSMNCellSearchPeriod
reports received by RNC
Successfull
ISHO counters

Compressed Mode Counter
UE BTS RNC If CM rejected by AC
RRC: Measurement Report (e.g. event 1F) M1002C361
REQ_COM_UL_REJ_SYS_HHO_SRNC
M1002C362
REQ_COM_DL_REJ_SYS_HHO_SRNC
If CM accepted by BTS
M1005C135 REC_PREP_SRNC_READY
NBAP: RL reconfig. ready Otherwise check RL reconfiguration
failure counters
If CM commanded by RNC to BTS

NBAP: RL reconfig. commit M1005C126 REC_COMM_SYNCH_SRNC
Otherwise check RNC HW counters
If CM commanded by RNC to UE
M1006C59
PHY_CH_RECONF
Otherwise check RNC HW counters
If CM accepted by UE
RRC: Physical Channel Reconfiguration Complete M1006C60
PHY_CH_RECONF_COMP
Otherwise check air interface and IMEI
Any of the failures mentioned here
M1010C2 IS_COM_MOD_STA_NOT_POS_RT
M1010C40 IS_COM_MOD_STA_NOT_POS_NRT

Compressed Mode Counter
CM failed due to
RNC
CM failed due to
RNC
CM failed due to
M1005C135 UE or air interface
M1005C126
M1006C59
M1006C60
CM accepted by CM commanded CM commanded CM accepted by

BTS by RNC to BTS by RNC to UE UE

HHO Counter
HHO Trigger
If CM can start, the following counters are updated
M1010C3 (M1010C41) IS_HHO_W_CMOD_UL_DCH_Q_(N)RT
M1010C4 (M1010C42) IS_HHO_W_CMOD_UE_TX_PWR_(N)RT
M1010C5 (M1010C43) IS_HHO_W_CMOD_DL_DPCH_(N)RT
M1010C6 (M1010C44) IS_HHO_W_CMOD_CPICH_RSCP_(N)RT
M1010C7 (M1010C45) IS_HHO_W_CMOD_CPICH_ECNO_(N)RT
Typical cause distribution for urgent HHO
• Ec/Io and RSCP about 90%
• UE power on UL and RL power on DL about 5-10%
• UL SIR target at maximum about 1%

HHO Counter
HHO Trigger Example RT
UL SIR target UE power RL power RSCP Ec/Io
Cell ID 1010C3 1010C4 1010C5 1010C6 1010C7
Ec/Io strongly
dominating trigger
for RT

HHO Counter
HHO Trigger Example NRT
UL SIR target UE power RL power RSCP Ec/Io
Cell ID 1010C41 1010C42 1010C43 1010C44 1010C45
Ec/Io almost only
trigger for NRT

HHO Counter
Detection of adjacent cell
If an adjacent cell can be found, the following counters are updated
M1010C18 (M1010C56)IS_HHO_ATT_UL_DCH_Q_(N)RT
M1010C22(M1010C60) IS_HHO_ATT_UE_TX_PWR_(N)RT
M1010C26(M1010C64) IS_HHO_ATT_DL_DPCH_PWR_(N)RT
M1010C30 (M1010C68)IS_HHO_ATT_CPICH_RSCP_(N)RT
M1010C34 (M1010C72)IS_HHO_ATT_CPICH_ECNO_(N)RT
Requirements for update
• 2G cell with sufficient coverage in any case
• 2G cell with readable BSIC for RT RAB
Typically for about 90% of all urgent HHO an adjacent cell is available

HHO Counter
If no adjacent cell can be found, the following counters are updated
M1010C13 (M1010C51) IS_HHO_NO_CELL_UL_DCH_Q_(N)RT
M1010C14 (M1010C52) IS_HHO_NO_CELL_UE_TX_PWR_(N)RT
M1010C15 (M1010C53) IS_HHO_NO_CELL_DL_DPCH_(N)RT
M1010C16 (M1010C54) IS_HHO_NO_CELL_CPICH_RSCP_(N)RT
M1010C17 (M1010C55) IS_HHO_NO_CELL_CPICH_ECNO_(N)RT

HHO Counter
Detection of adjacent cell example
Total adjacency found /
total CM started RT Total adjacency found /
Total CM Total CM total CM started NRT
Cell ID started RT Cell found ratio started NRT Cell found ratio
Often no adjacency
found both for RT
and NRT

HHO Counter
Access to adjacent cell
Access to 2G is treated as successfully, if the Iu Release Command is sent by the core network
Than the following counters are updated
M1010C19 (M1010C57) SUCC_IS_HHO_UL_DCH_Q_(N)RT
M1010C23 (M1010C61) SUCC_IS_HHO_UE_TRX_PWR_(N)RT
M1010C27 (M1010C65) SUCC_IS_HHO_DL_DPCH_PWR_(N)RT
M1010C31 (M1010C69) SUCC_IS_HHO_CPICH_RSCP_(N)RT
M1010C35 (M1010C73) SUCC_IS_HHO_CPICH_ECNO_(N)RT
Typically for about 90% of all urgent HHO 2G can be accessed successfully

HHO Counter
Access to adjacent cell Example
Total Iu release command /
Total adjacency total adjacency found RT /
Cell ID found RT / NRT NRT
ISHO success ratio
Very high ISHO
success for RT, but
very low for NRT

HHO Counter
Drop during urgent ISHO
In case of a failure during a pending urgent ISHO process the UE cannot escape bad air interface
performance
If therefore a RAB drops due to the cause Radio Connection with UE Lost, one of the following
counters is updated
M1010C21 (M1010C59) CON_DROP_IS_HHO_UL_DCH_Q_(N)RT
M1010C25 (M1010C63) CON_DROP_IS_HHO_UE_TRX_PWR_(N)RT
M1010C29 (M1010C67) CON_DROP_IS_HHO_DL_DPCH_PWR_(N)RT
M1010C33 (M1010C71) CON_DROP_IS_HHO_CPICH_RSCP_(N)RT
M1010C37 (M1010C75) CON_DROP_IS_HHO_CPICH_ECNO_(N)RT
The counters are not updated, if a RAB drops due to a non radio cause

HHO Counter
Dropped
Adjacent cell
not found
Dropped
2G not accessed
Measurements
started
Adjacent cell
found
2G accessed

HHO Counter
ISHO cancellation
If a pending urgent ISHO process is cancelled, one of the following counters is updated
M1010C203(M1010C209) CANC_ISHO_CPICH_ECNO_(N)RT
M1010C204(M1010C210) CANC_ISHO_CPICH_RSCP_(N)RT
M1010C205(M1010C211) CANC_ISHO_TX_PWR_(N)RT
M1010C206(M1010C212) CANC_ISHO_DL_DPCH_(N)RT
M1010C207(M1010C213) CANC_ISHO_ADD_(N)RT
M1010C208(M1010C214) CANC_ISHO_REPL_(N)RT

HHO Counter
ISHO cancellation example RT
Ec/Io RSCP UE power RL power Event 1A Event 1C
Cell ID 1010C203 1010C204 1010C205 1010C206 1010207 1010208
ISHO for RT mostly

cancelled due to
event 1E
Sometimes due to
active set update

HHO Counter
ISHO cancellation example NRT
Ec/Io RSCP UE power RL power Event 1A Event 1C
Cell ID 1010C209 1010C210 1010C211 1010C212 1010213 1010214
ISHO for NRT almost

cancelled due to event
1E only
Seldom due to active
set update

HHO KPI
Overall urgent ISHO success rate
Urgent_ISH O_success_rate  successful _urgent_IS HOs

Urgent_ISH O_attempts
Check of access to 2G only

Attempt and success counted in all source cells
Usually considered separately for RT and NRT

Multi-RAB with at least one RT RAB counted as RT RAB

HHO KPI
Overall urgent ISHO success rate
Σ SUCC_IS_HH O_UL_DCH_Q _RT  SUCC_IS_HH O_UE_TRX_P WR_RT
 SUCC_IS_HH O_DL_DPCH_ PWR_RT  SUCC_IS_HH O_CPICH_RS CP_RT
 SUCC_IS_HH O_CPICH_EC NO_RT
Urgent_ISH O_Success_RT 
 IS_HHO_ATT _UL_DCH_Q_ RT  IS_HHO_ATT _UE_TRX_PW R_RT
 IS_HHO_ATT _DPCH_PWR_ RT  IS_HHO_ATT _CPICH_RSC P_RT
 IS_HHO_ATT _CPICH_ECN O_RT
Analogue KPI for NRT

HHO KPI
Overall ISHO success rate including all trigger
ISHO_succe ss_rate  successful _ISHOs

ISHO_attem pts

HHO KPI
Overall ISHO success rate including all trigger
Σ SUCC_IS_HH O_UL_DCH_Q _RT  SUCC_IS_HH O_UE_TRX_P WR_RT
 SUCC_IS_HH O_DL_DPCH_ PWR_RT  SUCC_IS_HH O_CPICH_RS CP_RT
 SUCC_IS_HH O_CPICH_EC NO_RT  SUCC_IS_HH O_IM_IMS_R T
 SUCC_IS_HH O_EMERG_CA LL  SUCC_IS_HH O_LB_CAPA_ DL_RT
 SUCC_IS_HH O_LB_CAPA_ UL_RT  SUCC_IS_HH O_LB_PRX_T OT_RT
 SUCC_IS_HH O_LB_PTX_T OT_RT  SUCC_IS_HH O_LB_RES_L IM_RT
 SUCC_IS_HH O_LB_RSVR_ SC_RT  SUCC_IS_HH O_SB_RT
 SUCC_IS_HH O_WPS_RT  SUCC_GANHO _AMR_RT
 SUCC_ISHO_ CELL_SHUTD OWN_RT  SUCC_ISHO_ CELL_BLOCK _RT
ISHO_Succe ss_RT 
 IS_HHO_ATT _UL_DCH_Q_ RT  IS_HHO_ATT _UE_TRX_PW R_RT
 IS_HHO_ATT _DPCH_PWR_ RT  IS_HHO_ATT _CPICH_RSC P_RT
 IS_HHO_ATT _CPICH_ECN O_RT  IS_HHO_ATT _IM_IMS_RT
 IS_HHO_ATT _EMERG_CAL L  IS_HHO_ATT _LB_CAPA_D L_RT
 IS_HHO_ATT _LB_CAPA_U L_RT  IS_HHO_ATT _LB_PRX_TO T_RT
 IS_HHO_ATT _LB_PTX_TO T_RT  IS_HHO_ATT _LB_RES_LI M_RT
 IS_HHO_ATT _LB_RSVR_S C_RT  IS_HHO_ATT _SB_RT
 IS_HHO_ATT _UL_DCH_WP S_RT  ATT_GANHO_ AMR_RT
 ATT_ISHO_C ELL_SHUTDO WN_RT  ATT_ISHO_C ELL_BLOCK_ RT

But for NRT no ISHO of emergency call, of WPS user and no ISHO to GAN
HHO KPI
ISHO success rate per neighbor
ISHO attempts per adjacency
• No attempts to distant cell → might be removed from neighbor list
• No attempts to nearby cell → check whether BCCH frequency and BSIC is declared
correctly in RNC and BSC data base
ISHO success per adjacency
• High failure rate (several 10%) → besides air interface performance check for BCCH-
BSIC clash
• 100% failure rate → check for inconsistency between RNC, BSC and core network data
bases (e.g. CI, LAC and RAC declarations)
Attempt and success per adjacency monitored by AutoDef SHO counters (M1015)
• Sum over all types of services, RT and NRT
• Sum over all HHO trigger, urgent and non urgent ones
 HO_ADJ_INTER_SYS_HHO_COMPL
ISHO_success_per_ADJG_RNC 
 HO_ADJ_INTER_SYS_HHO_ATT

Content
Counter Structure
Compressed Mode Counter
HHO Counter
HHO KPI

Counter Structure and Compressed
Mode Counter
Exactly the same types of counters as for urgent ISHO

Compressed mode analysed exactly by the same counters as for urgent ISHO

HHO Counter
HHO Trigger
If CM can start, the following counters are updated
M1010C101 (M1010C106) IS_HHO_W_CM_LB_PRX_TOT_(N)RT
M1010C102 (M1010C107) IS_HHO_W_CM_LB_PTX_TOT_(N)RT
M1010C189 (M1010C108) IS_HHO_W_CM_LB_CAPA_UL_(N)RT
M1010C190 (M1010C109) IS_HHO_W_CM_LB_CAPA_DL_(N)RT
M1010C103 (M1010C110) IS_HHO_W_CM_LB_RSVR_SC_(N)RT
M1010C104 (M1010C111) IS_HHO_W_CM_LB_RES_LIM_(N)RT
M1010C105 (M1010C112) IS_HHO_W_CM_SB_(N)RT

HHO Counter
If an adjacent cell can be found, the following counters are updated
M1010C137 (M1010C142) IS_HHO_ATT_LB_PRX_TOT_(N)RT
M1010C138 (M1010C143) IS_HHO_ATT_LB_PTX_TOT_(N)RT
M1010C195 (M1010C144) IS_HHO_W_CM_LB_CAPA_UL_(N)RT
M1010C196 (M1010C145) IS_HHO_W_CM_LB_CAPA_DL_(N)RT
M1010C139 (M1010C146) IS_HHO_ATT_LB_RSVR_SC_(N)RT
M1010C140 (M1010C147) IS_HHO_ATT_LB_RES_LIM_(N)RT
M1010C141 (M1010C148) IS_HHO_ATT_SB_(N)RT
Requirements for update
• 2G cell with sufficient coverage in any case
• 2G cell with readable BSIC for RT RAB

HHO Counter
If no adjacent cell can be found, the following counters are updated
M1010C125 (M1010C142) IS_HHO_NOCELL_LB_PRX_TOT_(N)RT
M1010C126 (M1010C143) IS_HHO_NOCELL_LB_PTX_TOT_(N)RT
M1010C193 (M1010C144) IS_HHO_NOCELL_LB_CAPA_UL_(N)RT
M1010C194 (M1010C145) IS_HHO_NOCELL_LB_CAPA_DL_(N)RT
M1010C127 (M1010C146) IS_HHO_NOCELL_LB_RSVR_SC_(N)RT
M1010C128 (M1010C147) IS_HHO_NOCELL_LB_RES_LIM_(N)RT
M1010C129 (M1010C148) IS_HHO_NOCELL_SB_(N)RT

HHO Counter
Access to adjacent cell
Access to 2G is treated as successfully, if the Iu Release Command is sent by the core network
Than the following counters are updated
M1010C149 (M1010C154) SUCC_IS_HHO_LB_PRX_TOT_(N)RT
M1010C150 (M1010C155) SUCC_IS_HHO_LB_PTX_TOT_(N)RT
M1010C197 (M1010C156) SUCC_IS_HHO_LB_CAPA_UL_(N)RT
M1010C198 (M1010C157) SUCC_IS_HHO_LB_CAPA_DL_(N)RT
M1010C151 (M1010C158) SUCC_IS_HHO_LB_RSVR_SC_(N)RT
M1010C152 (M1010C159) SUCC_IS_HHO_LB_RES_LIM_(N)RT
M1010C153 (M1010C160) SUCC_IS_HHO_SB_(N)RT

HHO Counter
Drop during non urgent ISHO
If during a pending non urgent ISHO a RAB drops due to the cause Radio Connection with UE
Lost, one of the following counters is updated
M1010C173 (M1010C178) CONDR_IS_HHO_LB_PRX_TOT_(N)RT
M1010C174 (M1010C179) CONDR_IS_HHO_LB_PTX_TOT_(N)RT
M1010C201 (M1010C180) SUCC_IS_HHO_LB_CAPA_UL_(N)RT
M1010C202 (M1010C181) CONDR_IS_HHO_LB_CAPA_DL_(N)RT
M1010C175 (M1010C182) CONDR_IS_HHO_LB_RSVR_SC_(N)RT
M1010C176 (M1010C183) CONDR_IS_HHO_LB_RES_LIM_(N)RT
M1010C177 (M1010C184) CONDR_IS_HHO_SB_(N)RT
The counters are not updated, if a RAB drops due to a non radio cause

HHO KPI
Overall non urgent ISHO success rate
Non_urgent _ISHO_succ ess_rate  successful _non_urgen t_ISHOs

non_urgent _ISHO_atte mpts
Check of access to 2G only

Attempt and success counted in all source cells
Usually considered separately for RT and NRT

Multi-RAB with at least one RT RAB counted as RT RAB

HHO KPI
Overall non urgent ISHO success rate
Σ SUCC_IS_HH O_LB_CAPA_ DL_RT
 SUCC_IS_HH O_LB_CAPA_ UL_RT  SUCC_IS_HH O_LB_PRX_T OT_RT
 SUCC_IS_HH O_LB_PTX_T OT_RT  SUCC_IS_HH O_LB_RES_L IM_RT
 SUCC_IS_HH O_LB_RSVR_ SC_RT  SUCC_IS_HH O_SB_RT
Non_Urgent _ISHO_Succ ess_RT 
 IS_HHO_ATT _LB_CAPA_D L_RT
 IS_HHO_ATT _LB_CAPA_U L_RT  IS_HHO_ATT _LB_PRX_TO T_RT
 IS_HHO_ATT _LB_PTX_TO T_RT  IS_HHO_ATT _LB_RES_LI M_RT
 IS_HHO_ATT _LB_RSVR_S C_RT  IS_HHO_ATT _SB_RT

Content
Principles
Relocation preparation (CS ISHO)
Relocation execution (CS ISHO)
PS ISHO

Principles
Signaling flow example (outgoing relocation)
RNC Core BSC UE
Source Target
RANAP Relocation required

RANAP Relocation request
SETUP PHASE
RANAP Relocation request ACK
RANAP Relocation command
RNSAP Relocation commit
RANAP Relocation detect

ACCESS PHASE
RANAP Relocation complete
RANAP Iu release
ACTIVE PHASE

Principles
Outgoing and incoming relocation
Relocation monitored by relocation signaling measurement counters M1009
• Usually considered relocation between adjacent RNCs
• In case of ISHO the target RNC object identifier is BSC
Outgoing and incoming relocation monitored separately
• Outgoing relocation shall terminate with RRC connection release with cause “SRNC
relocation”
• Incoming relocation shall terminate with RRC connection setup with cause “SRNC
relocation”

Relocation Preparation (CS ISHO)
Types of counters
Preparation counter give the following information
• Number of preparation requests
• Number of successful preparations
• Number of preparation failures per cause
Radio network layer cause

Transport network layer cause
All failures
Etc….
Requests Successes

Relocation Preparation (CS ISHO)
Counter matrix
Outgoing Incoming
Preparation requests C235 C243
Successful preparations C236 C244
Preparation failure cause
Radio network layer C237 C245
Transport network layer C238 C246
NAS C239 C247
Protocol C240 C248
Miscellaneous C241 C249
Non standard C242 C250

Relocation Execution (CS ISHO)
Correct completion
Only considered for outgoing ISHO (3G to 2G)
• Target BSC sends RANAP relocation complete message
• Counted by C259
Completion of incoming ISHO (2G to 3G) counted by BSC

Relocation Execution (CS ISHO)
Erroneous completion
If any error occurs either during preparation or execution, the relocation is cancelled due to one of
the following causes
Radio network layer C251
Transport network layer C252
Trelocoverall expired C253
Trelocprep expired C254
NAS C255
Protocol C256
Miscellaneous C257
Non standard C258
Only considered for outgoing ISHO (3G to 2G)
Erroneous completion of incoming ISHO (2G to 3G) counted by BSC

PS ISHO
There are few specific counters only
C272 for successful resource allocation for data forwarding via Iu
C273 for SRNC context request from SGSN
C274 for SRNC context response by source RNC
C275 for SRNC data forward command from SGSN

Content
Flow of investigation
Trigger analysis
Failure analysis – no target cell found
Failure analysis – target cell not accessed

Monitoring Example
Flow chart
Too low No No action
success rate needed
Top N cells Yes
CM Start No Low No
ISHO No Low ISHO
Not Measurement
Success ?
Possible? success ?
Yes
Yes
Yes Missing or wrong 2G
Missing ADJG or
Bad Neighbor parameter in 2G MSC or
Check admission planning ? SGSN (BCCH, LAC, CellID)
control rejection
TCP and RTWP
Wrong 2G Ncell Poor GSM
Parameter (BSIC) Coverage 2G Ncell Half Rate in 2G
Or BSIC collision Congestion Ncell ?
Too low ISHO triggering

Non-optimum
threshold or
Compressed mode
Too strict ADJG
parameter set
minimum threshold
Monitoring Example
Urgent ISHO trigger
Blue = RSCP triggered

Red = Ec/Io triggered
Black = DL RL power triggered
UE power triggered = 0
UL SIR target triggered = 0
HHO mostly triggered by

event 1F
Event 1F again mostly due to
low coverage, but not quality

Monitoring Example
Urgent ISHO trigger – RSCP under 1F conditions
Usually very low coverage

under event 1F conditions
Consistent with counter

statistics

Monitoring Example
Urgent ISHO trigger – Ec/Io under 1F conditions
Usually acceptable Ec/Io even

under event 1F conditions
Consistent with counter

statistics

Monitoring Example
Urgent ISHO failure – no target cell found
Each point represents

one cell
100% target cell found
80% target cell found

Monitoring Example
Urgent ISHO failure – no target cell found
In several source cells often failure

to find target cell
If frequently no target cell can be

found
Check neighbor plan
Check settings for minimum

required coverage

Monitoring Example
Urgent ISHO failure – target cell not accessed
Much less critical to access

target cell
If target cell frequently cannot

be accessed
Check relocation counters

02 - 6541 - E01 - Interworking WCDMA To GSM PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 - 6541 - E01 - Interworking WCDMA To GSM PDF

Uploaded by

Copyright:

Available Formats

Content

GSM / WCDMA / LTE Interworking

02-1 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-2 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-3 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

High RL power consumption in case of low coverage

More capacity available for PS data within 3G

02-4 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

There are the following types of inter-system neighbors

3G neighbor intrafreq 2 3G neighbor interfreq 2 2G/LTE neighbor 2

3G neighbor intrafreq n 3G neighbor interfreq n 2G/LTE neighbor n ≤ 32

02-5 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-6 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

WSG WANE RNC WLCSE

IPNB WBTS WRAB

FMCS ADJS HOPS

FMCG ADJG HOPG

02-7 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-8 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-9 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-10 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

HOPG templates to be applied to adjacent 2G cells

To each adjacent 2G cell two HOPG templates can be assigned for

NRT services with parameter NRTHopgIdentifier

02-11 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-12 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-13 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-14 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

3. Neighbours common to two active set cells

02-15 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

How to measure adjacent 2G cells in compressed mode FMCGId = 1

Parameters can be specified using templates Macro cell, RT service

02-16 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-17 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-18 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

NRT services with NRTFmcgIdentifier

HSDPA services with parameter HSDPAFmcgIdentifier

HSDPA+AMR multi-RAB services with parameter RTwithHSDPAFmcgIdentifier

02-19 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

Performance Measurements and KPIs

02-20 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

Ec/Io < Qqualmin + Sintersearch → UE measures also inter-frequency neighbors

Ec/Io < Qqualmin + SseachRAT → UE measures also 2G neighbors

Qqualmin + Qqualmin + Qqualmin +

EC/N0 = -14 dB -10 dB -8 dB

AdjgQrxlevMin Adjacent cell

02-23 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

See next slide Cell re-selection to GSM

02-25 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

02-26 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

UE informs RNC about bad performance of active set

RNC commands UE to perform intersystem

UE reports RNC about performance of active set and best

RNC selects optimum target cell and commands UE to enter it

1) Low measured 1 and 2 are triggered, when 2) Low measured

3) UE power approaches maximum Measurement 4) DL DPCH approaches

5) Quality deterioration report Values for all parameter

02-28 TA-TC 6541 E01 www.techcom.de Copyright © All rights reserved

If both inter-frequency and inter-system HO is enabled, inter-system measurements are

Hereby the following conditions must be fulfilled

• IFHO → unsuccessful attempt

• ISHO → unsuccessful attempt or ISHO cancellation activated

UE applies filtering of the Ec/Io measurements specified by the Ec/Io filter