06 Mobility

RANKPI Training
Mobility Measurements
1 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
Agenda
• Soft Handover
• Detected Set Reporting measurements and handover
• Relocation KPIs – RAN1136
• Inter-frequency and Inter-System Handover
• ISHO KPIs
• AutoDef measurements on ADJx
• A-DCH Mobility
• HSPA Serving Cell Change
• HSDPA Serving Cell Change Enhancements
• Layering Measurements
• Coverage/Quality UE Measurements
• LTE Interworking

Soft Handover

Soft Handover Counters
Provide an indication of soft(er) handover performance (counters do not always

discriminate between soft and softer handover) .
The Handover control (HC) RRM entity in the SRNC manages user mobility
in call (CELL_DCH) by ensuring that UE is always served by the optimal
cell(s) in order to ensure quality, minimise interference and optimise the
available capacity.
The SHO measurements are carried out in the controlling RNC (CRNC), that is either an SRNC
or a DRNC - depending on the counter.
Care required when building a KPI by aggregating counters to avoid double or triple counting
radio links, cluster/RNC formulas are different from cell ones.
Most M1007 counters are updated to all cells in the active set. Exceptions:
• Event 6G/6F counters are updated to the cell, that triggered the event
• CPICH EcNo distribution counters are updated to the best cell in the report, either AS cell
or triggering non-AS cell

SHO area
Ec/No
DropWindow
AddWindow
distance
Cell A Cell B
Soft handover area

The size depends on specific RNP parameters’ setting (e.g. Addition Window,
Drop Window).
Soft Handover Counters (M1007C10) CELL_ADD_REQ_ON_SHO_FOR_RT
(M1007C11) CELL_DEL_REQ_ON_SHO_FOR_RT
(M1007C12) CELL_REPL_REQ_ON_SHO_FOR_RT
(M1007C27) CELL_ADD_REQ_ON_SHO_FOR_NRT
BTS RNC (M1007C28) CELL_DEL_REQ_ON_SHO_FOR_NRT
UE
(M1007C29) CELL_REPL_REQ_ON_SHO_FOR_NRT
RRC: Measurement Report (e1a / e1c) All counters are NOT incremented in case there is parallel
process prevention due to previous SHO procedure on going
Decision to for the UE from which the request is received
set up new RL
NBAP: Radio Link Setup Request – for Soft Handover
various M1002 counters triggered
NBAP: Radio Link Addition Request – for Softer Handover
various M1005 counters triggered
Start TX/RX
NBAP: Radio Link Setup Response M1007C71 or C72 triggered in case of
NBAP: Radio Link Addition Response RL Setup/Add Failure due to BTS or AAL2
ALCAP:ERQ
ALCAP:ECF
Received message RRC: Active Set Update Complete.
RRC: Active Set Update
Triggers: M1007C15 SUCC_UPDATES_ON_SHO_FOR_RT
RRC: Active Set Update Complete
Received message RRC: Active Set Update Complete.
or: RRC: Active Set Update Failure
Triggers: M1007C32
SUCC_UPDATES_ON_SHO_FOR_NRT
Received message RRC: Active Set Update Failure triggers:

M1007C16/33 UNSUCC_UPDATES_ON_SHO_FOR_RT/NRT
These counters also trigger if RRC: Active Set Update Complete is not
received
SHO retries
When the SRNC receives a periodic RRC: MEASUREMENT REPORT message from the UE, and the
message is triggered due to event 1A/1C, and the previous cell addition/replacement request for the UE
has failed (no ASU sent) and this request is made for the same cell(s)
M1007C13 CELL_ADD_FAIL_ON_SHO_FOR_RT or
M1007C14 CELL_REPL_FAIL_ON_SHO_FOR_RT or
M1007C30 CELL_ADD_FAIL_ON_SHO_FOR_NRT or
M1007C31 CELL_REPL_FAIL_ON_SHO_FOR_NRT or
These counters are updated in every cell belonging to the active set when the message is received
(before possible active set changes)
When RNC receives a periodic measurement report triggered by event 1B to the RNC in order to
remove a cell from the active set, counter:
M1007C36 CELL_DEL_FAIL_ON_SHO_FOR_RT or
M1007C37 CELL_DEL_FAIL_ON_SHO_FOR_NRT is incremented
This situation can happen when the RNC is prevented to delete the existing branch from the active set
before any other branch has achieved synchronisation
(NBAP: Synchronisation Indication is received)
The counters are updated in every cell that is in the active set on the SRNC side when the RNC
receives the measurement report

Active Set measurements
M1007C0(C19) ONE_CELL_IN_ACTIVE_SET_FOR_(N)RT
M1007C1(C20) TWO_CELL_IN_ACTIVE_SET_FOR_(N)RT
M1007C2(C21) THREE_CELL_IN_ACTIVE_SET_FOR_(N)RT
Period of time when the cell belongs to an active set whose size is one, two or
three. Unit: 100ms.
Incremented by SRNC in every cell within the Active Set when the Active Set has
changed
Updated when call is released.
These counters do not discriminate between soft and softer handover, so the cells in
the AS could belong to the same or different Node B.

Call setup in cell A.
Cell A Cell B
After 40sec Event 1A (addition): Active Set has changed.
(CellA) ONE_CELL_IN_ACTIVE_SET incremented + 40sec
Cell A Cell B
After 60sec Event 1B (deletion): Active Set has changed.
(Cell A) TWO_CELL_IN_ACTIVE_SET incremented +60sec

(Cell B) TWO_CELL_IN_ACTIVE_SET incremented +60sec
Cell A Cell B
After 20sec Call release.
(Cell B) ONE_CELL_IN_ACTIVE_SET incremented + 20sec
Cell A Cell B
Fair calculation of Average AS size (cell level)
Simple example
ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT 

TWO _ CELL _ IN _ ACT _ SET _ RT / NRT  2 
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT  3
ONE _ CELL _ IN _ ACT _ SET _ RT / NRT 
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT 
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT
1 cell in 2 cells in
Active Set Active Set
Cell 1 1 1
cell 1
Cell 2 0 1
Average active set size (cell 1) = (1+1x2) /2 = 1.5

Average active set size (cell 2) = (1x2) /1 = 2 cell 2

Fair calculation of Average AS size (RNC level,
RNC192b)
Simple example
ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT 
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT 
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT
ONE _ CELL _ IN _ ACT _ SET _ RT / NRT 
TWO _ CELL _ IN _ ACT _ SET _ RT / NRT / 2 
THREE _ CELL _ IN _ ACT _ SET _ RT / NRT / 3
1 in Active 2 in Active cell 1

Set Set
Cell 1 1 1
Cell 2 0 1 cell 2
Sum 1 2
(RNC)
Total number of UEs= 1 + 2/2 = 2
Average active set size (RNC) = (1+2)/2 = 1.5

Soft Handover Overhead
SHO_Overhead= 100% * (Average Active Set Size – 1)
Active Set Update Success Rate

Cell Level Formula:
SUCC_UPDATES_ON_SHO
CELL_ADD_REQ_ON_SHO  CELL_DEL_REQ_ON_SHO  CELL_REPL_ REQ_ON_SHO

Detected Set Reporting measurements and handover

DSR overview
• DSR comes as two optional features:

– RAN1191 to provide basic functionality and measurement possibilities
– RAN1266 to provide handover functionality to detected cells
• RAN 1266 provides new adjacency object ADJD
• Additional “second class” neighbors can be defined as ADJD
• Existing M1007, M1008 and M1013 counters are updated
• New measurement M1028 to collect CPICH statistics on detected
cells not part of ADJS or ADJD

Detected Set Reporting and Measurements
RAN1191
d) Based on the received 1A/1C reports
a) RNC activates Detected Set the RNC updates the following counters for
reporting via RRC: RNC Detected Set cells:
MEASUREMENT CONTROL - average CPICH RSCP
- average CPICH Ec/No
Average CPICH RSCP

Average CPICH Ec/No
CPICH RSCP Iub
CPICH Ec/No
PRACH propagation
b) UE sends the Intra Frequency NodeB Delay (RAS06)
report (1A/1C: CPICH RSCP) for
Detected Set WCELLS
c) UE sends the Intra Frequency WBTS calculates the propagation delay at
report (1A/1C: CPICH Ec/no) for RRC setup and sends it via
Detected Set WCELLS in order to RRC:RRC CONNECTION REQUEST to
request SHO RNC

SHO based on Detected Set Reporting: Functionality
UE RNC
Activate DSR
UE measures AS,
neighbor list
Reporting event on other cell
and other cells
Check other cell
against missing
Update AS with ADJD cell neighbors
and ADJDs
Update neighbor list

Relocation KPIs – RAN1136

RAN1136
Previous releases  only one counter type that included all cases
New feature  split into more detailed counters  possible to monitor relocations
separately by traffic classes and operation types.
New counters have an impact on
- RRC (Radio Resource Controller) and RAB (Radio Access Bearer) accessibility KPIs
- releases caused by relocations can be filtered from the current RRC and RAB accessibility
counters.
With introduction of „separate counters for relocation“, some legacy KPIs do not include
RRC and RAB setups triggered by incoming mobility procedures
• Incoming SRNS Relocations (calls from other RNCs)
• Incoming Hard Handovers (calls from other RNC or system)
• Existing KPI formulas unchanged – trigger for counters changed
• Mobility relocations are measured separately
This feature does not require activation

Separate counters for relocation
Benchmark RNC areas an

traffic capability, RAN L3

RAN1136
Functional description
• The counters are provided by source and target RNCs based on RANAP and RRC procedures.
• Outgoing relocation counters in a source RNC are complemented with a separate counter for RAB
active releases. They are classified by:
• Traffic Classes:
- CS Voice, CS Conversational data, CS Streaming data
- PS Streaming, PS Interactive, PS Background
• Operation types:
- SRNS relocation, Inter-RNC HHO (UE-involved), Inter-RAT HHO
- RAB counters for setup attempts and access completions are separated by traffic class and CN domain.
- The RNC transfers the new relocation counters to NetAct by using the current M1001 Service Level
Measurement NetAct builds up new reports for relocation.
• Triggering points:
Incoming relocation counters:
- relocation Request [RANAP]: RRC and RAB relocation setup attempts
- relocation Complete [RANAP]: RRC and RAB relocation access completions
Outgoing relocation counters:
- Iu Release Complete [RANAP]: RAB Active release counters

Impacts on key performance indicators
KPI name
Number of outgoing relocations per TC
Number of outgoing relocations per operation type
Number of incoming relocations per TC (measured by RAB)
The key performance indicators without a given KPI ID can be found in separate NetAct reports
and they are not described in the WCDMA RAN customer documentation.

Relocation Counter
Additionally to already implemented counters for RAN1136: Separate Counters for
Relocations M1001C651 … C658 and C644 … C650, C801, C802, C804 …C807, C819,
C826, C 828 a new M1009 Relocation Counter is in RU30 implemented:
M1009C287 RELOC IN REJECT DUE TO OVERLOAD

Description: The number of incoming relocations that are rejected because the maximum
amount of simultaneous relocation procedures is reached. This counter covers UE-not-
involved SRNS relocation, UE-involved inter-RNC hard handover and incoming inter-system
handover. Also one of relocation type specific M1009 incoming relocation counters is
updated along with this counter.
Updated: When the RNC sends RANAP: RELOCATION FAILURE message to the core
network due to maximum number of simultaneous relocation procedures reached. Logical
type: Sum Trigger type: Event; Unit: Integer number

Inter-frequency and Inter-System Handover

Inter-frequency and Inter-System Handover
• Counter structure for IFHO and ISHO are very similar
• Some differences exist in trigger reasons:
– Capability based IFHO
– GAN HO
– Emergency ISHO
– WSP
– Directed Retry

Capability based IFHO M1008C262 ATT_HCAP_IFHO_MEAS : The number of HSPA capability based IFHO
measurement start attempts. Updated: When the handover control decides to start inter-
UE BTS RNC frequency measurement.
RRC: Measurement Control

RRC: Measurement Report (intra freq.)
HC Decides M1008C263 FAIL_HCAP_IFHO_MEAS : The number of HSPA capability

to start the based IFHO measurement start failures. Updated: When the inter-frequency
measurement start command is rejected by L3 with other than an "ongoing
CM parallel procedures" reason.
NBAP: Radio Link Reconfiguration Prepare
M1008C264 NOT_START_HCAP_IFHO_NO_CELL : The number of times when no cell
NBAP: Radio Link Reconfiguration Ready good enough was found for HSPA capability based IFHO. Updated: When the inter-
NBAP: Radio Link Reconfiguration Commit frequency measurement does not produce any handover candidate cells and the
measurement is stopped.
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete M1008C265 ATT_HCAP_INTRA_IFHO : The number of Intra-RNC HSPA capability
based IFHO attempts. Updated: When the handover control starts an intra-RNC inter-
frequency handover attempt.
RRC: Measurement Report
M1008C266 ATT_HCAP_INTER_IFHO : The number of Inter-RNC HSPA capability
RRC: Measurement Report based IFHO attempts. This counter includes also handover attempts to I-HSPA cells.
NBAP: Compressed Mode Command Updated: When the handover control starts an inter-RNC inter-frequency handover
Failure attempt.
RRC: Radio Bearer Reconfiguration

RRC: Radio Bearer Reconfiguration Complete M1008C267 SUCC_HCAP_INTRA_IFHO : The number of successful Intra-RNC
HSPA capability based IFHOs. Updated: When the RNC receives RRC: RADIO
BEARER RECONFIGURATION COMPLETE or RRC: PHYSICAL CHANNEL
RECONFIGURATION COMPLETE from the UE indicating a successful intra-
RNC hard handover.
M1008C268 SUCC_HCAP_INTER_IFHO : The number of successful Inter-RNC

HSPA capability based IFHOs. This counter includes also handovers to I-HSPA
cells. Updated: When the RNC receives RANAP: IU RELEASE COMMAND from
the core network indicating a successful inter-frequency handover to another
RNC or I-HSPA.

Capability based IFHO M1008C269 FAIL_HCAP_INTRA_IFHO_UTRAN : The number of failed Intra-RNC
HSPA capability based IFHOs due to UTRAN. Updated: When the intra-RNC inter-
UE RNC frequency handover fails due to some other than a UE related reason. This can be
BTS for example NBAP: RADIO LINK SETUP FAILURE or Iub transmission allocation
RRC: Measurement Control failure.
M1008C270 FAIL_HCAP_INTER_IFHO_UTRAN : The number of failed Inter-RNC
RRC: Measurement Report (intra freq.)
HSPA capability based IFHOs due to UTRAN. This counter includes also failed
handovers to I-HSPA cells. Updated: When the inter-RNC inter-frequency handover
HC Decides to fails due to some other than a UE related reason. This can be for example RANAP:
RELOCATION PREPARATION FAILURE.
start the CM
NBAP: Radio Link Reconfiguration Ready M1008C271 FAIL_HCAP_INTRA_IFHO_UE_NACK : The number of failed Intra-RNC
HSPA capability based IFHOs due to UE rejection. Updated: When the intra-RNC inter-
NBAP: Radio Link Reconfiguration Commit frequency handover fails due to UE responding with RRC: RADIO BEARER
RRC: Physical Channel Reconfiguration RECONFIGURATION FAILURE or RRC: PHYSICAL CHANNEL RECONFIGURATION
FAILURE.
RRC: Physical Channel Reconfiguration Complete
M1008C272 FAIL_HCAP_INTER_IFHO_UE_NACK : The number of failed Inter-RNC
RRC: Measurement Control HSPA capability based IFHOs due to UE rejection. This counter includes also failed
handovers to I-HSPA cells. Updated: When the inter-RNC inter-frequency handover fails
due to UE responding with RRC: TRANSPORT CHANNEL RECONFIGURATION
RRC: Measurement Report FAILURE or RRC: PHYSICAL CHANNEL RECONFIGURATION FAILURE.
NBAP: Compressed Mode Command
M1008C273 FAIL_HCAP_INTRA_IFHO_UE_LOST : The number of failed
RRC: Radio Bearer Reconfiguration Intra-RNC HSPA capability based IFHOs due to UE being lost. Updated:
When the UE does not respond to RRC: RADIO BEARER
RRC: Radio Bearer Reconfiguration Failure
RECONFIGURATION or RRC: PHYSICAL CHANNEL
RECONFIGURATION sent by the RNC and the user plane is released.
M1008C274 FAIL_HCAP_INTER_IFHO_UE_LOST : The number of failed
RRC: Radio Bearer Reconfiguration Complete Inter-RNC HSPA capability based IFHOs due to UE being lost. This counter
includes also failed handovers to I-HSPA cells. Updated: When the UE does
not respond to RRC: TRANSPORT CHANNEL RECONFIGURATION or
RRC: PHYSICAL CHANNEL RECONFIGURATION sent by the RNC and
the RNC does not receive RANAP: IU RELEASE COMMAND from the core
network, but a timer expires in the RNC triggering user plane release.

Intra System Hard Handover Measurements due to
shut down
Inter freq HHO attempts and successful cases forced due to the cell shut down procedure (e.g. due to
the power saving feature)
Inter freq HHO attempts and successful cases forced by normal priority block resource procedure
M1008C286 INTER FREQ HO ATTEMPTS FORCED BY CELL SHUTDOWN FOR NRT

M1008C287 INTER FREQ HO ATTEMPTS FORCED BY CELL SHUTDOWN FOR RT
M1008C288 SUCCESSFUL INTER FREQ HO FORCED BY CELL SHUTDOWN FOR NRT
M1008C289 SUCCESSFUL INTER FREQ HO FORCED BY CELL SHUTDOWN FOR RT
M1008C290 INTER FREQ HO ATTEMPTS FORCED BY BLOCK RESOURCE FOR NRT
M1008C291 INTER FREQ HO ATTEMPTS FORCED BY BLOCK RESOURCE FOR RT
M1008C292 SUCCESSFUL INTER FREQ HO FORCED BY BLOCK RESOURCE FOR NRT
M1008C293 SUCCESSFUL INTER FREQ HO FORCED BY BLOCK RESOURCE FOR RT
27 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009 *) feature in RU20EP

ISHO Introduction
The ISHO measurement is carried out in the serving

RNC (SRNC).
The object of the measurement is the source cell from

which the handover is attempted.
In case UE is in SHO, the object of the measurement

is the best cell of the Active Set during the handover
decision (i.e. the cell with the biggest CPICH Ec/No
value in the latest RRC message, during the handover
decision moment)
• the only exception is counter
IS_COM_MOD_STA_NOT_POS_(N)RT) where
the object is the best active set cell during the
compressed mode preparation phase, and not
during the handover decision moment.

Counter structure for ISHO procedure
No Cell Found UTRAN Failure

Counters Counter
Target cell found

HHO Attempt UE Failure
Counters Counter
Measurement
Inter-system HO
(Compressed
trigger
Mode start )
Unsuccessfull
ISHO Counters
This structure exists Successfull

ISHO Counters
for CM and non-CM No counter is triggered, if
cases MaxMeasTime expires and enough
reports have not been received
as specified by NCellSearchPeriod RRC Drop
Counters

12 possible trigger reasons
2. Quality deterioration report
from UL outer loop PC
1. DL DPCH approaches its
trigger internal in RNC
maximum allowed power
BTS trigger
Measurement 4. UE Tx power approaches its

3. Low measured absolute maximum allowed power
CPICH Ec/No trigger
event 6A/6D
event 1E/1F
UE trigger
UE trigger
5 . Low measured absolute

CPICH RSCP
6 . Emergency ISHO (US feature)
events 1E/1F
7 . IMSI based HO
UE trigger The triggerning 8. Load based HO
reasons must be 9. Service based HO
enabled:
[FMCG] 10. WPS (US feature)
GSMcause…
11. GAN HO
12. Directed Retry

Signalling procedure for RT (GBR)
Example: NBAP and RRC (compressed mode included) signalling for a 1

CS service inter-system handover
UE Node B RNC CN
ISHO triggering (12
RRC: Measurement Report reasons are possible)
NBAP: Radio Link Reconfiguration Ready
Initial
2
NBAP: Radio Link Reconfiguration Commit Compressed
RRC: Physical Channel Reconfiguration Mode
Configuration
NBAP: Compressed Mode Command 3
GSM RSSI
Measurement 3a
RRC: Measurement Control GSM BSIC 4
Identification
RANAP: Relocation Required
RRC: Handover from UTRAN Command RANAP: Relocation Command
RANAP: IU Release Command
5 RANAP: IU Release Complete

6
Signalling procedure for NRT (non-GBR)
Example: NBAP and RRC (compressed mode included) signalling for a

PS service inter-system handover CN
UE Node B RNC
RRC: Measurement Control ISHO triggering (12
RRC: Measurement Report reasons are possible)

NBAP: Radio Link Reconfiguration Ready
Initial Compressed
NBAP: Radio Link Reconfiguration Commit Mode Configuration
RRC: Physical Channel Reconfiguration
RRC: Measurement Control GSM RSSI
RRC: Measurement Report Measurement
RRC: Cell Change Order from UTRAN
RANAP: SRNS Context Request
RANAP: SRNS Context Response

RANAP: SRNS Data Forward Command
RANAP: IU Release Command
RANAP: IU Release Complete

Analyzing Trigger reasons (M1010)
1
Coverage & Quality trigger:
M1010C3 NBR of started Inter Syst HO HHO Meas w CM due to UL DCH Qual
M1010C4 NBR of started Inter Syst HO HHO Meas w CM due to UL Tx Pwr
M1010C5 NBR of started Inter Syst HO HHO Meas w CM due to DL DPCH Pwr
M1010C6 NBR of started Inter Syst HO HHO Meas w CM due to CPICH RSCP
M1010C7 NBR of started Inter Syst HO HHO Meas w CM due to CPICH EcNo
M1010C80 NBR of started Inter Syst HO HHO Meas w CM due to IMSI
M1010C94 NBR of started Inter Syst HO HHO Meas w CM due to EMERG Call
Load trigger:
M1010C101 NBR of started Inter Syst HO HHO Meas w CM due to Prx Total
M1010C102 NBR of started Inter Syst HO HHO Meas w CM due to Ptx Total
M1010C103 NBR of started Inter Syst HO HHO Meas w CM due Res SC rate
M1010C104 NBR of started Inter Syst HO HHO Meas w CM due HW/Log Res
Service trigger:
M1010C105 NBR of started Inter Syst HO HHO Meas w CM due Service HO
All above counters for RT services using CM

same counters for NRT

How many UEs in Compressed Mode ?
DL/UL
power
No new UE can be in CM here
One new UE in CM can be

allowed
PtxOffset/
if the limit is not reached
PrxOffset
PtxTarget/
PrxTarget
New UEs can be switched to CM when:
Pxx_Total < Pxx_Target &
# of UEs in CM <
MaxNumbUECMcoverHO
Load
CM preparation
2
If BTS can accept the CM it will respond back with the NBAP: RL
Reconfiguration Ready which is calculated by:
M1005C135 REC_PREP_SRNC_READY
After receiving NBAP: RL Reconfiguration Ready message from

BTS the RNC will send NBAP: RL Reconfiguration Commit
message which is counted by:
M1005C126 REC_COMM_SYNCH_SRNC
After sending RL Reconfiguration Commit to BTS the RNC will send

the Physical Channel Reconfiguration message to inform UE about
the CM , these are counted by:
M1006C59 PHY_CH_RECONF
In case the UE responds back with the Physical Channel

reconfiguration Complete the counter:
M1006C60 PHY_CH_RECONF_COMP

Compressed mode counters
If compressed mode can start the following counters are incremented :
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
If compressed mode can NOT start (before sending Measurement Control) the
following counter is incremented: 3
M1010C2 (M1010C40)IS_COM_MOD_STA_NOT_POS_(N)RT
The counters are updated if:
1) Admission Control rejects compressed mode request: If Compressed Mode
cannot be started due to AC rejecting the request counters: M1002C361
REQ_COM_UL_REJ_SYS_HHO_SRNC or M1002C362
REQ_COM_DL_REJ_SYS_HHO_SRNC
2) ISHO is a parallel procedure (especially NRT)
3) Compressed mode can not start due to radio link (or physical channel)
reconfiguration failure (BTS or UE reasons)

M1015: BSIC verification time
3a
M1015C4 BSIC_VERIF_TIME :
Description: Sum of BSIC verification times. This counter, divided by the denominator
M1015C5 provides the average BSIC verification time. BSIC verification time is the elapsed
time between measurement control (BSIC verification required) and the measurement report
(BSIC verified). If verification is not received, then the counter is not updated. Updated:
Updated when the measurement report (BSIC verified) is received after measurement control
(BSIC verification required). If verification is not successful, then the counter is not updated.
M1015C5 BSIC_DENOM :
The number of successful BSIC Verifications. This counter is used as a denominator for
M1015C4 when calculating the average BSIC verification time. Updated: Updated by value 1
when the BSIC verification is successful.
M1015C4 has a known bug to

show values 10 times too low.
Correction available with RU10
CD1

Counters on measurement result
If, before expiring the max measurement interval, the

RNC has found a suitable cell (both RxLev and BSIC
phases), one of the following counters is updated:
M1010C18 IS_HHO_ATT_UL_DCH_Q_RT
4
M1010C22 IS_HHO_ATT_UE_TX_PWR_RT
M1010C26 IS_HHO_ATT_DL_DPCH_PWR_RT
M1010C30 IS_HHO_ATT_CPICH_RSCP_RT
M1010C34 IS_HHO_ATT_CPICH_ECNO_RT
The counters are triggered when the RNC sends the

RANAP: RELOCATION REQUIRED message to the MSC
Only the SRNC can update the counters.
5
The counters are updated in the BEST cell of the active set
If the RNC has not found any suitable cell, one of the following counters is
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

ISHO complete counters
6
When the source RNC receives the RANAP message

“IU RELEASE COMMAND” from the core network, one of the following
counter is triggered:
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
The counter is triggered in the same cell where the ISHO attempt has
been updated.

ISHO KPIs

Main ISHO KPIs (RNC_302e and 303e)
 SUCC _ IS _ HHO _ xxx _ RT

IS _ RT _ HHO _ SR  Allcauses
 IS _ HHO _ ATT _ xxx _ RT

Allcauses
 SUCC _ IS _ HHO _ xxx _ NRT

IS _ NRT _ HHO _ SR  Allcauses
 IS _ HHO _ ATT _ xxx _ NRT

Allcauses
Build from M1010 counters

Updated KPI Inter-System mobility RT (and NRT)
100*
sum([SUCC_IS_HHO_UL_DCH_Q_RT]+ [SUCC_IS_HHO_UE_TRX_PWR_RT]+
[SUCC_IS_HHO_DL_DPCH_PWR_RT]+ [SUCC_IS_HHO_CPICH_RSCP_RT]+ ISHO success rate KPIs
[SUCC_IS_HHO_CPICH_ECNO_RT]+ [SUCC_IS_HHO_IM_IMS_RT] +
includes:
[SUCC_IS_HHO_EMERG_CALL] + [SUCC_IS_HHO_LB_CAPA_DL_RT]+
[SUCC_IS_HHO_LB_CAPA_UL_RT]+ [SUCC_IS_HHO_LB_PRX_TOT_RT] +
[SUCC_IS_HHO_LB_PTX_TOT_RT] + [SUCC_IS_HHO_LB_RES_LIM_RT] +
[SUCC_IS_HHO_LB_RSVR_SC_RT] + [SUCC_IS_HHO_SB_RT] +
• Cell shutdown
[SUCC_IS_HHO_WPS_RT] + [SUCC_GANHO_AMR_RT] + • Coverage reasons
[SUCC_ISHO_CELL_SHUTDOWN_RT] + [SUCC_ISHO_CELL_BLOCK_RT])
/
• Emergency Call (US)
sum([IS_HHO_ATT_UL_DCH_Q_RT]+ [IS_HHO_ATT_UE_TRX_PWR_RT]+ • Load based HO
[IS_HHO_ATT_DPCH_PWR_RT]+ [IS_HHO_ATT_CPICH_RSCP_RT]+
[IS_HHO_ATT_CPICH_ECNO_RT]+ [IS_HHO_ATT_IM_IMS_RT] + • Service based HO
[IS_HHO_ATT_EMERG_CALL] + [IS_HHO_ATT_LB_CAPA_DL_RT]+ • IMSI based HO
[IS_HHO_ATT_LB_CAPA_UL_RT]+ [IS_HHO_ATT_LB_PRX_TOT_RT] +
[IS_HHO_ATT_LB_PTX_TOT_RT] + [IS_HHO_ATT_LB_RES_LIM_RT] + • HO to GAN
[IS_HHO_ATT_LB_RSVR_SC_RT] + [IS_HHO_ATT_SB_RT] +
[IS_HHO_ATT_UL_DCH_WPS_RT]+ [ATT_GANHO_AMR_RT] +
[ATT_ISHO_CELL_SHUTDOWN_RT] + [ATT_ISHO_CELL_BLOCK_RT] -
[IS_HHO_ATT_2ND_BEST_CELL_RT] - [IS_HHO_ATT_3RD_BEST_CELL_RT] )

KPI for ISHO triggering reasons
Build from M1010C3 ff:
IS _ HHO _ W _ CMOD _ xxx _( N ) RT

xxx _ Cause_percentage  [%]
 IS _ HHO _ W _ CMOD _ xxx _( N ) RT
Allcauses
Important information to diffentiate between quality and coverage reasons and

understand the network limiting factors:
• CPICH coverage
• Pilot pollution
• UL/DL Service (DPCH) coverage
Same KPI can be built in case Inter-System Handover procedure started without
Compressed mode (dual receiver UEs). IS_HHO_WO_CMOD_XXX_(N)RT

ISHO Cancellation
UE RNC
Activate CM and measurements UE or RAN trigger

UE measures GSM starts ISHO
but also Intra-
Reporting event relevant for cancellation: 1A,1C,1E, 6B .. or RAN internal
frequency
event allow
cancellation
Cancel CM and measurements

ISHO Cancellation
M1010C203 CANC_ISHO_CPICH_ECNO_RT or Updated when the RNC receives
M1010C209 CANC_ISHO_CPICH_ECNO_NRT such a measurement report from
the UE or WBTS that triggers the
M1010C204 CANC_ISHO_CPICH_RSCP_RT or cancellation of inter-system HHO
M1010C210 CANC_ISHO_CPICH_RSCP_NRT measurement.
M1010C205 CANC_ISHO_TX_PWR_RT or
M1010C211 CANC_ISHO_TX_PWR_NRT
M1010C206 CANC_ISHO_DL_DPCH_RT or
M1010C212 CANC_ISHO_DL_DPCH_NRT
M1010C207 CANC_ISHO_ADD_RT or
M1010C213 CANC_ISHO_ADD_NRT
M1010C208 CANC_ISHO_REPL_RT or
M1010C214 CANC_ISHO_REPL_NRT

AutoDef measurements on ADJx

Adjacency Based Measurements
Each cell has its own neighbouring cell list initially defined by radio Network Planning. This
is a list of those neighbouring cells where the handover can be made.
The results of neighbour cell measurements can be used to optimise those lists. The
benefits of optimised lists are better call quality and shorter handover delays.
• To find strong candidates that are missing from actual definition
• To locate and delete unused adjacencies
• Identify and optimise badly performing adjacencies RNC
Serving
BTS
UEs

Adjacency Based Measurements Counters
M1013 Autodef SHO
• M1013C0 Number of Intra Frequency SHO attempts
– Counter is Updated when SRNC starts a Branch Addition or Branch Replacement procedure.
• M1013C1 Number of completed Intra Frequency SHO
– Counter is updated when SRNC successfully ends the Branch Addition or Branch Replacement procedure.
M1014 Autodef IFHO

• M1014C0 Number of Inter Frequency HHO attempts
– Counter is updated when SRNC starts inter-frequency HHO
• M1014C1 Number of completed Inter Frequency HHO
– Counter is updated when SRNC successfully ends inter-frequency HHO
M1015 Autodef ISHO

• M1015C0 Number of Inter System HHO attempts
– Counter is updated when SRNC starts inter-system HHO
• M1015C1 Number of completed Inter System HHO
– Counter is update when SRNC receives RANAP:IU RELEASE COMMAND from core network after successful
Inter System HHO

SHO Success Ratio RNC2 border with RNC3
Data from 01 April 2008 (Optimizer tool)

SHO Success Ratio RNC2 WCELs border with RNC3
Data from 03 April 2008 (Optimizer tool) – after parameter
changes

Adjacency Based Measurements Counters
For each measurements (SHO, IFHO and

ISHO) Statistic show:
• # of HO attempts
• # of HO completed (successful)
to source and target cell objects
Measurement is carried out in SRNC
HO completion is considered successful if
the SRNC during the handover decision
does not detect any errors (errors in the
source RNC side or failure messages from
RRC/Iu/Iur/Iub interfaces)
Object identifiers for M1013 and M1014

Source-RNC/Source-CID
Target-RNC/Target-CID
MCC/MNC
Object identifiers for M1015 (ISHO)
Source-RNC/Source-CID
GSM-LAC/GSM-CID
MCC/MNC

SHO / IFO / ISHO Share
HO Share provides distribution of HO attempts from the source cell
• Useful detect neighbour relations which has exceptional amount of attempts
It is possible to get the total number of outgoing HO attempts from the Autodef HO
measurements by taking a sum over all the adjacencies reported for a source cell
• SHO HO Share (M1013 AutoDef SHO)

100 * sum( SHO _ ADJ _ INTRA _ FREQ _ SHO _ ATT )
SHO _ Share _ RNC _ 903a 
Sum _ over _ all _ adja _ from _ the _ cell (SHO _ ADJ _ INTRA _ FREQ _ SHO _ ATT )
• IFHO HO Share (M1014 AutoDef IFHO)

100 * sum( HHO _ ADJ _ INTER _ FREQ _ HHO _ ATT )
IFHO _ Share _ RNC _ 904a 
Sum _ over _ all _ adja _ from _ the _ cell ( HHO _ ADJ _ INTER _ FREQ _ HHO _ ATT )
• ISHO HO Share (M1015 AutoDef ISHO)

100 * sum( HO _ ADJ _ INTER _ SYS _ HHO _ ATT )
ISHO _ Share _ RNC _ 905a 
Sum _ over _ all _ adja _ from _ the _ cell ( HO _ ADJ _ INTER _ SYS _ HHO _ ATT )

HO Success per Adjacency (ADJS / ADJI / ADJG)
The HO success rate per adjacency can be calculated by using formulas below
• Can be used to detect badly performing neighbours
SHO Success per Adjacency (M1013 AutoDef SHO)

100 * sum( SHO _ ADJ _ INTRA _ FREQ _ SHO _ COMPL)
SHO _ success _ per _ ADJS _ RNC _ 900a 
sum( SHO _ ADJ _ INTRA _ FREQ _ SHO _ ATT )
IFHO Success per Adjacency (M1014 AutoDef IFHO)

100 * sum( HHO _ ADJ _ INTER _ FREQ _ HHO _ COMP)
IFHO _ success _ per _ ADJI _ RNC _ 901a 
sum( HHO _ ADJ _ INTER _ FREQ _ HHO _ ATT )
ISHO Success per Adjacency (M1015 AutoDef ISHO)

100 * sum( HO _ ADJ _ INTER _ SYS _ HHO _ COMPL)
ISHO _ success _ per _ ADJG _ RNC _ 902a 
sum( HO _ ADJ _ INTER _ SYS _ HHO _ ATT )

A-DCH Mobility

A-DCH Mobility performance
Associated DCH for HSDPA maybe in SHO when optional feature
HSDPA Mobility is enabled
Measurement is M1007 Soft Handover

A-DCH Mobility performance counters & KPI
M1007C53 CELL ADDITION REQUEST ON SHO FOR HSDPA MOBILITY

Event 1A M1007C56 CELL ADDITION FAILURE ON SHO FOR HSDPA MOBILITY
M1007C54 CELL DELETION REQUEST ON SHO FOR HSDPA MOBILITY
Event 1B M1007C57 CELL DELETION FAILURE ON SHO FOR HSDPA MOBILITY
M1007C55 CELL REPLACEMENT REQUEST ON SHO FOR HSDPA MOBILITY

Event 1C M1007C58 CELL REPLACEMENT FAILURE ON SHO FOR HSDPA MOBILITY
M1007C59 SUCCESSFUL ACTIVE SET UPDATES ON SHO FOR HSDPA MOBILITY

M1007C60 UNSUCCESSFUL ACTIVE SET UPDATES ON SHO FOR HSDPA MOBILITY
M1007C48 ONE CELL IN THE ACTIVE SET FOR HSDPA MOBILITY

M1007C49 TWO CELL IN THE ACTIVE SET FOR HSDPA MOBILITY
Durations M1007C50 THREE CELL IN THE ACTIVE SET FOR HSDPA MOBILITY
M1007C51 SOFTER HANDOVER DURATION ON THE SRNC SIDE FOR HSDPA MOBILITY
( M1007C59 )
A-DCH mobility success rate = 100% *
( M1007C53 + M1007C54 + M1007C55 )

HSPA Serving Cell Change

HSPA Serving Cell Change HSDPA counters
Trigger causes for cell change can be analyzed:
M1008C213 HS-DSCH Serving Cell Changes started due to CPICH Ec/N0
M1008C214 HS-DSCH Serving Cell Changes started due to UL SIR error
M1008C215 HS-DSCH Serving Cell Changes started due to Active Set Update
M1008C216 HS-DSCH Serving Cell Changes started due to other reason
Counters indicating failures for cell change

M1008C217 HS-DSCH Serving Cell Changes failed due to UE
M1008C218 HS-DSCH Serving Cell Changes failed due to BTS
M1008C219 HS-DSCH Serving Cell Changes failed due to Transport
M1008C220 HS-DSCH Serving Cell Changes failed due to AC
M1008C221 HS-DSCH Serving Cell Changes failed due to other reason
M1008C224 HS-DSCH Serving Cell Changes prevented due to Timer
Counters indicating successful Serving Cell change

M1008C222 HS-DSCH Serving Cell Changes Intra BTS Serving Cell Changes Successful
M1008C223 HS-DSCH Serving Cell Changes Inter BTS Serving Cell Changes Successful

HSPA Serving Cell Change E-DCH counters
Trigger causes for cell change can be analyzed:
M1008C239 E-DCH Serving Cell Changes started
Counters indicating successful Serving Cell change
M1008C240 E-DCH Intra BTS Serving Cell Change successful

M1008C241 E-DCH Inter BTS Serving Cell Change successful
Counters indicating Channel Type switch to DCH during Serving

Cell Change
M1008C242 E-DCH Downgraded to DCH in Serving Cell Change HS-DSCH Serving Cell

E-DCH Soft Handover Mobility (M1007)
Durations
M1007C63 ONE CELL IN E-DCH ACTIVE SET DURATION

M1007C64 TWO CELLS IN E-DCH ACTIVE SET DURATION
M1007C65 THREE CELLS IN E-DCH ACTIVE SET DURATION
M1007C66 SOFTER HO DURATION ON THE SRNC SIDE FOR HSUPA MOBILITY
Attempts
M1007C67 CELL ADDITION ATTEMPT REQ BY UE TO E-DCH AS

M1007C68 CELL ADDITION SUCCESS TO EDCH ACTIVE SET
M1007C69 CELL NOT ADDED TO E-DCH ACTIVE SET BUT ADDED TO DCH AS
M1007C70 CELL ADDITION ATTEMPT RETRY TO E-DCH AS

HSDPA Serving Cell Change KPI
HSDPA Serving Cell Change Success Rate over the reporting period in the Source
Cell. This KPI is based on Intra System HHO measurement (M1008).
RNC_733b: HSDPA Serving Cell Change Success Rate over the reporting period in the
Source Cell
HSDPA SCC success rate = 100-100* sum([SCC_FAILED_DUE_TO_UE]+
[SCC_FAILED_DUE_TO_BTS] + [SCC_FAILED_DUE_TO_TRANSM]+
[SCC_FAILED_DUE_TO_AC]+ [SCC_FAILED_DUE_TO_OTHER]) /
sum([SCC_STARTED_CPICH_ECNO]+ [SCC_STARTED_UL_SIR_ERROR]+
[SCC_STARTED_ACTIVE_SET_UPD]+ [SCC_STARTED_OTHER_REASON])
100-100* sum([M1008C217]+ [M1008C218]+ [M1008C219]+ [M1008C220]+ [M1008C221]) /

sum([M1008C213]+ [M1008C214]+ [M1008C215]+ [M1008C216])
( M1008C240 + M1008C241 )
E-DCHSCC success rate = * 100%
( M1008C239 )

HSDPA Serving Cell Change Enhancements

Serving Cell Change – RU20 and RU30
RU20 (standard feature)
• In SHO area HS UE sends periodic measurement reports to RNC
• RNC evaluates reports to decide about serving cell change
• Problems
• High signaling traffic due to periodic reporting
• If F-DPCH used, serving cell change command of RNC might not be decoded by UE, as
SRB on HS-PDSCH less robust than on DPDCH
RU30 (enhanced feature) RAN1911
• No periodic reporting in SHO area any more, but serving cell change triggered by
event 1D
• Better robustness for SRB on HS-PDSCH
• RNC sends pre-information about potential target cells during active set update already
• Serving cell change commands transmitted both in source and target cell

Enhanced Serving Cell Change – Pre-configuration
• Serving cell change command transmitted both in source and target cell
• In source cell via HS-PDSCH
• In target cell via HS-SCCH
• UE informed during active set update about
• Codes used for HS-SCCH in target cell
• Activation time offset (time to monitor target cell after sending event 1D report)
UE Source Node B Target Node B SRNC

RRC: Measurement Report (event 1a or 1c)
NBAP: Radio Link Setup (Pre-configuration Info)
RRC: Active Set Update (Pre-configuration Info)
RRC: Active Set Update Complete


Enhanced Serving Cell Change – Execution
• Serving cell change initiated by UE with event 1D report (then UE starts to monitor
target cell)
• After both source and target cell are prepared for serving cell change, to the UE are
sent
• RRC radio bearer configuration from RNC as usual (via HS-PDSCH in source cell)
• HS-SCCH order from target Node B (via HS-SCCH in target cell)
• If UE detects HS-SCCH order only, it still goes to target cell
• The UE informs the RNC about the completion of the process with RRC radio bearer
reconfiguration complete

Enhanced Serving Cell Change – Execution
UE Source Node B Target Node B SRNC
SCC Evaluation
RRC: Measurement Report (event 1d, CFN)
SCC Decision
NBAP: Radio Link Reconfiguration Preparation

NBAP: Radio Link Reconfiguration Preparation
NBAP: Radio Link Reconfiguration Commit

NBAP: Radio Link Reconfiguration Commit
L1: HS-SCCH Order
RRC: Radio Bearer Reconfiguration
UE moves to Target Cell RNC re-directs application data
RRC: Radio Bearer Reconfiguration Complete

Layering Measurements

Layering – RU20
Non HSPA HSPA

Redirection or
capable UE capable UE
handover at:
Directed RRC Connection HSDPA cell RRC connection
Setup for HSDPA Layer DCH cell setup only
HSDPA cell Same / different Connection setup or

HSPA Layering for UEs in HSDPA cell band
Common Channels transition FACH to DCH
DCH cell
Redirection with HSDPA load balancing
i-HSPA cell
Same / different
HSPA Capability Based band HSPA cell
Anytime during CELL_DCH
Handover HSPA cell or on HSPA traffic inactivity
DCH cell DCH cell

Layering – RU30
Support of more mobility scenarios
• HSPA capable UE with CS RAB in HSDPA cell moved to DCH cell (extension of RAN 502 and RAN 1011)
• Target and source cell load checked prior HSDPA inactivity triggered HO (extension of RAN 1596)
• Load based HO triggered by HSPA traffic overload (extension of RAN140)
Load sharing / balancing between HSPA cells / bands
• Better frequency resource utilization by directing UE to different frequency bands or layers in multi-band
networks
• Supports of service versus band strategy in multi-band networks (e.g. 2.1 GHz and 900 MHz)
More HO trigger
• UE capability
• Service type
• Load
• Distance
More criteria for target cell selection
• UE capability
• Service type
• Frequency band
• Load of target / source cell load
• Distance of UE from source / target cell

Load Balancing without Compressed Mode
• Compressed mode not needed for the following scenarios extending re-direction
• Blind HO at RAB setup
• Layering in state change
• As target can be used a cell of the following category
• Intra or inter BTS
• Intra RNC
• Same or other frequency band
• Not in overload state (discussed later)
• Higher priority than source cell (discussed later)
DCH/HSPA cell (band Z) DCH/HSPA cell (band Z)
DCH/HSPA cell (band Y, RF2) DCH/HSPA cell (band Y, RF1)
DCH/HSPA cell (band X)
Redirection / blind IFHO to

higher priority layer cell at
Connection setup or
Transition FACH/PCH/URA  DCH

Load Balancing without Compressed Mode
• Priority of target cell influenced by configurable preferences

• Carrier preference for pairs
• UE Capability
• Used or requested service / RAB
• Frequency band preference for multi-band UE
• High or low band preference based on UE distance from source cell
• HSDPA load
• HSDPA cell power per user
• Unused DL cell power

Load Balancing with Compressed Mode
• Compressed mode needed for the following scenarios
• HSDPA inactivity triggered
• Mobility triggered
• The same categories of target cells can be used as for load balancing without
compressed mode
• The priority of target cells depends on the same criteria as for load balancing without
compressed mode
• Load balancing with compressed mode is not carried out, if a CS RAB is running
DCH/HSPA cell (band Z) DCH/HSPA cell (band Z)
DCH/HSPA cell (band Y, RF2) DCH/HSPA cell (band Y, RF1)

HS-
DCH/HSPA cell (band X)
DSCH
HS-
Compressed mode IF handover DSCH
to higher priority layer cell on
HSDPA traffic inactivity (instead
transition to FACH) or
Mobility

MBLB Counters
Counter ID Counter name Measurement
M1006C234 RB SETUP ATTEMPT WITH BLIND HO M1006 RRC signalling

M1006C235 RB SETUP SUCCESSFUL WITH BLIND HO M1006 RRC signalling
M1006C236 RB SETUP FAIL BLIND HO DUE TO UE NACK WITHOUT MEAS M1006 RRC signalling
M1006C237 RB SETUP FAIL BLIND HO DUE TO UE NACK WITH MEAS M1006 RRC signalling
M1006C238 RB SETUP FAIL BLIND HO DUE TO UE LOST WITHOUT MEAS M1006 RRC signalling
M1006C239 RB SETUP FAIL BLIND HO DUE TO UE LOST WITH MEAS M1006 RRC signalling
M1006C240 ATTEMPTED INTER-BTS LAYER CHANGES IN PCH/FACH TO DCH M1006 RRC signalling
M1006C241 SUCCESSFUL INTER-BTS LAYER CHANGES IN PCH/FACH TO DCH M1006 RRC signalling
M1006C242 FAILED INTER-BTS LAYER CHANGES IN PCH/FACH TO DCH M1006 RRC signalling

MBLB Counters
M1008C296 MBLB IFHO ATTEMPTS WITH UE BAND CAPA M1008 Intra System Hard Handover
M1008C297 MBLB IFHO ATTEMPTS WITH SERVICE AND UE FEATURE CAPA M1008 Intra System Hard Handover
M1008C298 MBLB IFHO ATTEMPTS WITH RSCP M1008 Intra System Hard Handover
M1008C299 MBLB IFHO ATTEMPTS WITH LOAD M1008 Intra System Hard Handover
M1008C300 SUCCESSFUL MBLB IFHO M1008 Intra System Hard Handover
M1008C301 FAILED MBLB IFHO DUE TO UTRAN M1008 Intra System Hard Handover
M1008C302 FAILED MBLB IFHO DUE TO UE NACK M1008 Intra System Hard Handover
M1008C303 FAILED MBLB IFHO DUE TO UE LOST M1008 Intra System Hard Handover
M1008C304 MBLB IFHO ATTEMPTS DUE FAST MOVING UE M1008 Intra System Hard Handover
M1008C305 NOT STARTED MBLB IFHO DUE TO NO CELL GOOD ENOUGH M1008 Intra System Hard Handover
M1008C306 IFHO MEAS START ATTEMPTS DUE TO MBLB M1008 Intra System Hard Handover
M1008C307 IFHO MEAS START FAILURES DUE TO MBLB M1008 Intra System Hard Handover
MBLB - Multi-band load balancing

RAN2135 Layering in RRC Connection Release
- new in RU40
• allows the operator to define the preferred idle mode layer in RRC connection release, in order to
push the UE to this layer
• introduces the connected-mode mechanism that pushes the UE to perform idle-mode camping on a
particular carrier
• Idle-mode camping is controlled with the cell reselection parameters.
• preferred layer is defined by the operator with the cell-level parameter in order to push the UE to this
preferred idle mode layer - could be another band or another carrier within the same band
New Counter:
M1006C269 RRC CONN RELEASE WCDMA REDIRECTION RRC signalling (RNC)
• If the RAN2717: Smart LTE Layering feature is activated in the same cell as the RAN2135: Layering in
RRC Connection Release feature:
 the decision to direct the UE to the LTE is made first
 if the decision is not to direct the UE to LTE, then the decision defined by the RAN2135: Layering
in RRC Connection Release feature is made next.

Coverage/Quality UE Measurements

Ec/No Measurements
M1033C0 RRC CPICH ECNO CLASS 0 M1033 CPICH Quality

Number of EC/I0 values reported by UEs falling into a certain interval

value < -18 dB
-18 dB <= value < -16 dB
-16 dB <= value < -14 dB
Continue in steps of 2 dB
-2 dB <= value

RSCP Measurements
Counter ID Counter name Measurement Number of RSCP values reported by
UEs falling into a certain interval
M1033C10 RRC CPICH RSCP CLASS 0 M1033 CPICH Quality
value < -113 dBm
M1033C12 RRC CPICH RSCP CLASS 2 M1033 CPICH Quality -113 dBm <= value < -110 dBm
M1033C13 RRC CPICH RSCP CLASS 3 M1033 CPICH Quality -110 dBm <= value < -107 dBm
M1033C14 RRC CPICH RSCP CLASS 4 M1033 CPICH Quality Continue in steps of 3 dB until
-89 dBm <= value <= -86 dBm
M1033C17 RRC CPICH RSCP CLASS 7 M1033 CPICH Quality -86 dBm <= value <= -80 dBm
M1033C18 RRC CPICH RSCP CLASS 8 M1033 CPICH Quality Continue in steps of 6 dB until
M1033C19 RRC CPICH RSCP CLASS 9 M1033 CPICH Quality -50 dBm <= value

LTE Interworking

RAN2067 – LTE Interworking
• Functionality of LTE Interworking (LTEIW) (RAN2067)
- enables cell reselection from 3G to LTE and provides support for packet switched inter-
system handover (PS ISHO) from LTE to 3G.
• Motivation:
- in the LTE rollout phase the coverage is typically limited, and UEs easily run out of the LTE coverage,
- especially in an idle mode
• Functional description
- enables the LTE cell reselection when the UE is in an idle mode, Cell_PCH state, or URA_PCH state
in the WCDMA layer.
- operator sets cell-based camping priority for the LTE-capable UEs - if coverage is available, the UE
selects to camp on the LTE in accordance with operator's preferences
- WCDMA, LTE, and GSM are prioritized with eight distinct absolute priorities
- in an idle mode, URA_PCH state, and Cell_PCH states, the UE camped in WCDMA measures
periodically all higher priority RATs
- also lower priority RATs are measured when the WCDMA quality decreases below the threshold
- the operator sets absolute priorities for WCDMA and LTE
- the operator also defines thresholds below which the reselection is executed and measurements on
lower priority RATs are started.

LTE Interworking – Measurements
M1001, M1009
M1001C704 INTER SYSTEM LTE HHO FAIL DUE TO CONFIG
M1009C276 LTE PS HHO IN PREP REQ

M1009C277 LTE PS HHO IN PREP SUCC
M1009C278 LTE PS HHO IN PREP FAIL DUE TO RNL
M1009C279 LTE PS HHO IN PREP FAIL DUE TO TRANS
M1009C280 LTE PS HHO IN PREP FAIL DUE TO NAS
M1009C281 LTE PS HHO IN PREP FAIL DUE TO PROT
M1009C282 LTE PS HHO IN PREP FAIL DUE TO MISC
M1009C283 LTE PS HHO IN PREP FAIL DUE TO NON STAN
M1009C284 LTE PS HHO IN DETECT
M1009C285 LTE PS HHO IN COMPLETE
M1009C286 LTE CS HHO IN PREP FAIL DUE TO RNL

RNC_2103a Incoming LTE PS ISHO preparation
Success Ratio – new in RU40
• Measurement 1009: L3 Relocation signalling
KPI formula KPI formula with short names:
100*sum([M1009C277]) 100*sum([LTE_PS_IN_PREP_SUCC])
/ /
sum([M1009C276]) sum([LTE_PS_IN_PREP_REQ])
KPI class: Mobility / Handover

Unit: %
Object summary levels: Network, RNC
Time summary levels: Total; week; weeklyBH; day; dailyBH; hour

RNC_2104a Incoming LTE PS ISHO relocation
complete Success Ratio – new in RU40
• Measurement 1009: L3 Relocation signalling
KPI formula KPI formula with short names:
100*sum([M1009C285]) 100*sum([LTE_PS_IN_COMPLETE])
/ /
sum([M1009C276]) sum([LTE_PS_IN_PREP_REQ])

Unit: %
Object summary levels: Network, RNC

RAN2717: Smart LTE Layering – new in RU40 1/2
• introduces support for the redirection of LTE-capable UE that is in Cell_DCH state from WCDMA to LTE
• RRC CONNECTION RELEASE message with the redirection to LTE command is used for moving
active UE to the LTE layer
The causes for redirection of the UE in Cell_DCH state to the LTE layer:
1. RRC state change away from Cell_DCH - user inactivity or call release
• redirection to LTE is not triggered, if state change is caused by RAB release for emergency call
2. Channel-type switch from HSDPA to DCH for the UE with only PS services - from HSDPA to DCH
because e. g. lack of cell resources or fading WCDMA coverage.
3. CS call release – redirection is checked when CS RAB is released and the UE would stay in
CELL_DCH state (the UE has at least one active PS RAB after CS RAB release).
• redirection to LTE is not triggered, if the released RAB is used for emergency call

RAN2717: Smart LTE Layering – new in RU40 2/2
New Counters:
M1006C262 RRC CONN RELEASE LTE REDIR DUE TO INACTIVITY M1006 RRC signalling (RNC)
M1006C263 RRC CONN RELEASE LTE REDIR DUE TO CH TYPE SWITCH M1006 RRC signalling (RNC)
M1006C264 LTE REDIRECTIONS PREVENTED BY TIMER M1006 RRC signalling (RNC)
M1006C291 RRC CONN RELEASE LTE REDIR DUE TO CS CALL RELEASE M1006 RRC signalling (RNC)
• If the RAN2717: Smart LTE Layering feature is activated in the same cell as the RAN2135: Layering in
RRC Connection Release feature:
 the decision to direct the UE to the LTE is made first
 if the decision is not to direct the UE to LTE, then the decision defined by the RAN2135: Layering
in RRC Connection Release feature is made next.

RNC_5464a RRC connection releases with LTE
redirection – new in RU40
• This KPI shows the number of RRC Connection Releases with redirection to LTE
triggered by Smart LTE Layering feature
• Measurement 1006: RRC signalling
KPI formula: KPI formula with short names:

sum([M1006C262]+ sum([RRC_REL_LTE_REDIR_INACT]+
[M1006C263]+ [RRC_REL_LTE_REDIR_CH_SWI]+
[M1006C291]) [RRC_REL_LTE_REDIR_CS_REL])

Unit: Integer number
Object summary levels: Network; City; Area; RNC; WBTS; Cluster of cells; Cell

RAN2435: SRVCC from LTE and CSFB with HO 1/2
– new in RU40
Single radio voice call continuity (SRVCC) from LTE:
• allows for voice over IP (VoIP) call handover from the LTE to the WCDMA as a normal CS voice call
• also CS Fallback (CSFB) from LTE function is supported
Functionality:
• an existing voice call in LTE is detected by the UTRAN as an incoming inter-system relocation request
from LTE to WCDMA in the CS domain
• multi-RAB (CS + PS RABs) handover from LTE to WCDMA is supported and all non-voice services are
handed over to the PS domain.
• CS fallback (CSFB) is initiated in the LTE layer when the UE is in connected mode with PS connection
allocated and CS call needs to be established but VoIP is not supported in LTE
• from the RNC point of view CS fallback is a PS ISHO from LTE
• the radio access bearer (RAB) for CS voice is set up in the WCDMA layer after inter-system handover
• CS fallback allows LTE deployment as a data-only network.
• SRVCC and CSFB are based on relocation procedure.

RAN2435: SRVCC from LTE and CSFB with HO 2/2
– new Counters
M1009C286 LTE CS HHO IN PREP FAIL DUE TO RNL (not new) L3 Relocation signalling (RNC)
M1009C288 LTE CS HHO IN PREP REQ L3 Relocation signalling (RNC)
M1009C289 LTE CS HHO IN PREP SUCC L3 Relocation signalling (RNC)
M1009C290 LTE CS HHO IN PREP FAIL DUE TO TRANS L3 Relocation signalling (RNC)
M1009C291 LTE CS HHO IN PREP FAIL DUE TO NAS L3 Relocation signalling (RNC)
M1009C292 LTE CS HHO IN PREP FAIL DUE TO PROT L3 Relocation signalling (RNC)
M1009C293 LTE CS HHO IN PREP FAIL DUE TO MISC L3 Relocation signalling (RNC)
M1009C294 LTE CS HHO IN PREP FAIL DUE TO NON STAN L3 Relocation signalling (RNC)
M1009C295 LTE CS HHO IN DETECT L3 Relocation signalling (RNC)
M1009C296 LTE CS HHO IN COMPLETE L3 Relocation signalling (RNC)
M1009C297 LTE CS FALLBACK IN PREP REQ L3 Relocation signalling (RNC)
M1009C298 LTE CS FALLBACK IN PREP SUCC L3 Relocation signalling (RNC)
M1009C299 LTE CS FALLBACK IN PREP FAIL DUE TO RNL L3 Relocation signalling (RNC)
M1009C300 LTE CS FALLBACK IN PREP FAIL DUE TO TRANS L3 Relocation signalling (RNC)
M1009C301 LTE CS FALLBACK IN PREP FAIL DUE TO NAS L3 Relocation signalling (RNC)
M1009C302 LTE CS FALLBACK IN PREP FAIL DUE TO PROT L3 Relocation signalling (RNC)
M1009C303 LTE CS FALLBACK IN PREP FAIL DUE TO MISC L3 Relocation signalling (RNC)
M1009C304 LTE CS FALLBACK IN PREP FAIL DUE TO NON STAN L3 Relocation signalling (RNC)
M1009C305 LTE CS FALLBACK IN DETECT L3 Relocation signalling (RNC)
M1009C306 LTE CS FALLBACK IN COMPLETE L3 Relocation signalling (RNC)
M1009C307 LTE CS FALLBACK HIGH PRIO IN PREP REQ L3 Relocation signalling (RNC)
M1009C308 LTE CS FALLBACK HIGH PRIO IN PREP FAIL L3 Relocation signalling (RNC)
Thank You !

06 Mobility

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

06 Mobility

Uploaded by

Copyright:

Available Formats

RANKPI Training

2 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

3 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Provide an indication of soft(er) handover performance (counters do not always

4 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Soft handover area

Received message RRC: Active Set Update Failure triggers:

7 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

8 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

After 40sec Event 1A (addition): Active Set has changed.

(CellA) ONE_CELL_IN_ACTIVE_SET incremented + 40sec

After 60sec Event 1B (deletion): Active Set has changed.

(Cell A) TWO_CELL_IN_ACTIVE_SET incremented +60sec

After 20sec Call release.

(Cell B) ONE_CELL_IN_ACTIVE_SET incremented + 20sec

ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT / NRT 

Average active set size (cell 1) = (1+1x2) /2 = 1.5

10 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

1 in Active 2 in Active cell 1

Total number of UEs= 1 + 2/2 = 2

Average active set size (RNC) = (1+2)/2 = 1.5

11 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

SHO_Overhead= 100% * (Average Active Set Size – 1)

Active Set Update Success Rate

12 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

13 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

• DSR comes as two optional features:

14 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Average CPICH RSCP

15 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Update neighbor list

16 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

17 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

This feature does not require activation

Benchmark RNC areas an

19 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

20 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Number of outgoing relocations per TC

Number of outgoing relocations per operation type

Number of incoming relocations per TC (measured by RAB)

21 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

M1009C287 RELOC IN REJECT DUE TO OVERLOAD

22 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

23 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

24 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC: Measurement Control

HC Decides M1008C263 FAIL_HCAP_IFHO_MEAS : The number of HSPA capability

RRC: Radio Bearer Reconfiguration

M1008C268 SUCC_HCAP_INTER_IFHO : The number of successful Inter-RNC

25 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

26 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

M1008C286 INTER FREQ HO ATTEMPTS FORCED BY CELL SHUTDOWN FOR NRT

27 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009 *) feature in RU20EP

The ISHO measurement is carried out in the serving

The object of the measurement is the source cell from

In case UE is in SHO, the object of the measurement

28 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

No Cell Found UTRAN Failure

Target cell found

This structure exists Successfull

29 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Measurement 4. UE Tx power approaches its

5 . Low measured absolute