Mobility Monitoring

Do not delete this graphic elements in here:
Section 7
Mobility Monitoring
Module 1
3JK10061AAAAWBZZA Edition 1.1
9300 WCDMA
UA06 R99 QoS Analysis and Traffic Load Monitoring
TMO18046 D0 SG DENI3.0
All Rights Reserved Alcatel-Lucent @@YEAR

Section 7 Pager 1
Blank Page
72
Mobility Monitoring
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load Monitoring
This page is left blank intentionally
Document History
Edition
Date
Author
Remarks
01
2008-12-01
El Abed, Achrafe
First edition
01.1
2008-03-18
Chatila, Rayan
Charneau, Jean-Noel
Corrections of counters and indicators

numbers, names and formulae
Addition of new UA6 counters allowing to
monitor the CS Inter-RAT HHO preparation
success rate per Cell
Addition of Inter-Freq IntraRNC+InterRNC with
Iur counters

Section 7 Pager 2
Module Objectives
Upon completion of this module, you should be able to:

Describe the mobility metric family

Illustrate the call flows associated with the metric family
Identify counters and locate them in the call flow procedure
Define metrics and recognize its key counters
Analyze each metric
73
Mobility Monitoring

Section 7 Pager 3
Module Objectives [cont.]
74
Mobility Monitoring

Section 7 Pager 4
Table of Contents
Switch to notes view!
1 Mobility Overview
Mobility overview
2 SHO Monitoring and Troubleshooting
SHO overview
SHO preparation Softer HO Cell Addition - Counters (1/2)
SHO preparation Softer HO Cell Addition - Metrics
SHO preparation Soft HO Cell Addition - Counters (1/2)
SHO preparation Soft HO Cell Addition - Metrics
SHO execution - Active Set Update - Counters
SHO execution - Metrics
SHO Analysis & Troubleshooting (1/2)
3 HHO 3G-2G Monitoring
3G-2G CS Handover Success - counters
3G-2G Global CS HHO Success Rate
3G-2G CS Handover Preparation Success - counters
3G-2G CS HO Preparation Success
3G-2G CS Handover Preparation Failure - counters
3G-2G CS HO Preparation Failure Rate
3G-2G CS Handover Execution Success - counters
3G-2G CS HO Execution Success Rate
3G-2G CS Handover Execution Failure - counters
75
3G-2G CS Handover: FDDCell Counter
Tree (Rescue case)
Mobility Monitoring
9300 WCDMA3G-2G
UA06 R99 QoS
Traffic Load Monitoring
CSAnalysis
HOandExecution
Failure Rate (reversion to 3G)
3G-2G CS HO Execution Failure Rate (call drop)
3G-3G HHO InterRNC no Iur Preparation Success - counters
3G-3G HHO InterRNC no Iur Preparation Failure - counters
3G-3G HHO InterRNC no Iur - Preparation Success Rate
3G-3G HHO InterRNC no Iur Execution Success - counters
3G-3G HHO InterRNC no Iur Execution Success Rate
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Success
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Rate
3G-3G Inter-frequency HHO - Intra-RNC Success - counters
3G-3G Inter-frequency HHO - Intra-RNC Failure - counters
3G-3G Inter-frequency HHO - Intra-RNC Failure Rate
5 HHO 3G-2G Analysis & Troubleshooting
CS 3G-2G Mobility Analysis & Troubleshooting
Summary
Action to improve the Preparation phase
Actions to improve the Execution phase
Self-Assessment on the Objectives
End of Module

Section 7 Pager 5
Page
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Table of Contents [cont.]

Switch to notes view!
76
Mobility Monitoring

Section 7 Pager 6
1 Mobility Overview
77
Mobility Monitoring

Section 7 Pager 7
1 Mobility Overview
Mobility overview
The Network Mobility analysis consists of:

In connection mode:
3G2G Mobility analysis:
aims at evaluating the inter RAT (3G to 2G) HO performance results and at indicating
where are the failures in the 2G or in the 3G
3G3G Mobility analysis:

Intra-freq mobility (SHO) analysis: estimates the trade-off between quality (reduce
interference and call drops) and capacity (avoid congestion)
Inter frequency mobility: for Traffic Management (segmentation or load balancing)
In idle mode:
Mobile traces
Study RRC counters/RRC transitions (RRC panel)
To be distinguished between CS and PS domain
78
Mobility Monitoring

Section 7 Pager 8
79
Mobility Monitoring

Section 7 Pager 9
SHO overview
SHO management Active Set management
Different SHO procedures

Adding a new cell into the Active Set
In the same Node-B Softer HO
In different Node-Bs Soft HO
Withdrawing a cell out of the Active Set

As most of the telecom procedure between UE and UTRAN, a Soft or Softer

Handover Cell Addition can be split between
SHO preparation phase
Allocation of the necessary radio resources in the cell to be added in the AS
CAC internal to the RNC
Establishment of the new RL

Involving RNC and Node-B
SHO execution phase

Active Set Update procedure
Involving RNC and UE (Node-B acting as a relay)
7 10
Mobility Monitoring

Section 7 Pager 10

UE
Node B
RNC
Measurement Report (Event 1a or 1c)
#55
Radio Link Addition
to be performed
CAC
OK
S
UCCES
Radio Link Addition Request

Radio Link Addition Response
#49
Radio Link Addition
success
FDDCell Counters
UE
Node B
RNC

CAC
NOK
RNC CAC Failure
7 11
FAILU
RE
#39.[2-7]
Radio Link Addition
unsuccess
Mobility Monitoring
VS.RadioLinkAdditionRequest - #55
Number of internal events that would lead to a radio link addition request.
A set of subcounters screened on: Target type of call for Radio Link Reconfiguration
Sub-Counter #0: Other
Sub-Counter #1: Signalling Only
Sub-Counter #2: CS speech
Sub-Counter #3: CS Speech + PS DCH
Sub-Counter #4: CS Speech + HSDPA
Sub-Counter #5: CS Speech + PS DCH + PS HSDPA
Sub-Counter #6: CS Speech + PS DCH + PS DCH
Sub-Counter #7: CS Data
Sub-Counter #8: CS data + PS DCH
Sub-Counter #9: Cs Data + PS HSDPA
Sub-Counter #10: CS streaming
Sub-Counter #11: PS DCH DL / DCH UL
Sub-Counter #12: PS HSDPA DL / E-DCH UL
Sub-Counter #13: PS HSDPA DL / DCH UL
Sub-Counter #14: PS HSDPA DL / DCH UL + E-DCH UL Sub-Counter #15: PS DCH + PS DCH

Sub-Counter #16: PS DCH + PS HSDPA
VS.RadioLinkAdditionSuccess - #49
Number of radio-links successfully added on a NBAP point of view, screened by Downlink Access Stratum
configuration.
Screening: same as for #55
VS.RadioLinkAdditionUnsuccess - #39
Number of failures radio link reconfiguration preparation

Sub-Counter #0: RADIO_LINK_ADDITION_FAILURE
Sub-Counter #1: Timeout
Sub-Counter #2: Rrm refusal
Sub-Counter #3: INode refusal
Sub-Counter #4: NodeB (CEM) lack of L1 resources
Sub-Counter #5: Lack of Transport Identifier (CID or UDP Port) on the Iub
Sub-Counter #6: Lack of bandwidth on the Iub
Sub-Counter #7: Iub Layer Congestion
All Rights
Reserved
Alcatel-Lucent
@@YEAR
Sub-Counter #8: NodeB out of order (No
answer)
(Screening
8 is not implemented,
is Always zero in V6.0.)
Section 7 Pager 11

UE
Node B
RNC
FAILU

CAC
OK

Radio Link Addition Failure
Node-B Failure
RE
#39.[0]
Radio Link Addition
unsuccess
FDDCell Counters
UE
Node B
RNC
CAC
OK
FAILU
RE

#39.[1]
Radio Link Addition
unsuccess
No answer
from Node-B
timer expiry
7 12
Mobility Monitoring
VS.RadioLinkAdditionUnsuccess #39
Number of unsuccessfull radio link setup
A set of subcounters screened on:
Sub-Counter #0: RADIO_LINK_ADDITION_FAILURE
Sub-Counter #2: RRM refusal
Sub-Counter #8: NodeB out of order (No answer)

Section 7 Pager 12
SHO preparation Softer HO Cell Addition - Metrics
FDDCell metric
URL027_CR
Radio
RadioLink
LinkAddition
Addition
Success
Rate
Success Rate
#49.[all]
=
#55.[all]
FDDCell metric
URL037_CR
Radio Link Addition

Blocking Rate
7 13
#39.[all except 1]
=
#55.[all]
Mobility Monitoring

Section 7 Pager 13

UE
Node B 1
Node B 2
RNC
#54
Radio Link Setup
to be performed
CAC
OK
#48
Radio Link Setup
success
Radio Link Setup Request
SS
SUCCE
Radio Link Setup Response
FDDCell Counters
UE
Node B 1
Node B 2
RNC
FAILU

CAC
NOK
RNC CAC Failure

7 14
RE
#38.[2-7]
Radio Link Setup
unsuccess
Mobility Monitoring
VS.RadioLinkSetupRequest - #54
Number of internal events that would lead to a radio link setup request
A set of subcounters screened on: Target type of call for Radio Link Reconfiguration
Sub-Counter #0: Other
Sub-Counter #1: Signalling Only
Sub-Counter #2: CS speech
Sub-Counter #3: CS Speech + PS DCH
Sub-Counter #4: CS Speech + HSDPA
Sub-Counter #5: CS Speech + PS DCH + PS HSDPA
Sub-Counter #6: CS Speech + PS DCH + PS DCH
Sub-Counter #7: CS Data
Sub-Counter #8: CS data + PS DCH
Sub-Counter #9: Cs Data + PS HSDPA
Sub-Counter #10: CS streaming
Sub-Counter #11: PS DCH DL / DCH UL
Sub-Counter #12: PS HSDPA DL / E-DCH UL
Sub-Counter #13: PS HSDPA DL / DCH UL
Sub-Counter #14: PS HSDPA DL / DCH UL + E-DCH UL
Sub-Counter #15: PS DCH + PS DCH
Sub-Counter #16: PS DCH + PS HSDPA
VS.RadioLinkSetupSuccess - #48
Number of radio-links successfully setup on a NBAP point of view, screened by Downlink Access Stratum
configuration. Screening: same as for #54
VS.RadioLinkSetupUnsuccess - #38
Number of unsuccessful radio link setup
Sub-Counter #0: RADIO_LINK_RECONFIGURATION_FAILURE
Sub-Counter #1: Timeout nbap
Sub-Counter #8: NodeB out of order (No answer) (Screening 8 is not implemented, is Always zero in V6.0.)
Section 7 Pager 14

UE
Node B 1
Node B 2
RNC
FAILU
RE
CAC
OK
#38.[0]
Radio Link Setup
unsuccess
Radio Link Setup Request

Node-B Failure
Radio Link Setup Failure
FDDCell Counters
UE
Node B 1
Node B 2
RNC
FAILU
RE
CAC
OK

No answer
from Node-B
timer expiry
7 15
Mobility Monitoring
VS.RadioLinkSetupUnsuccess - #38
Number of radio links failed in setup on a NBAP point of view.
screened by detecting event:
Sub-Counter #0: RADIO_LINK_SETUP_FAILURE
Sub-Counter #8: NodeB out of order (No answer)

Section 7 Pager 15
#38.[1]
Radio Link Setup
unsuccess
SHO preparation Soft HO Cell Addition - Metrics
FDDCell metric
Radio
RadioLink
LinkSetup
Setup
Success
Rate
Success Rate
URL005_CR
#48.[all]
=
#48.[all] + #38.[all]
FDDCell metric
Radio Link Setup

Blocking Rate
7 16
URL036_CR
#38.[all except 1]
=
#54.[all]
Mobility Monitoring

Section 7 Pager 16
SHO execution - Active Set Update - Counters

UE
Node B
RNC
Measurement Report (event)
SS
SUCCE
Active Set Update

Active Set Update Complete
#415
FDDCell Counters
UE
Node B
RNC
FAILU
RE

UE
Active Set Update
Node B
RNC
Active Set Update Failure

Active Set Update
No answer from UE
#402[0]
#402[1]
7 17
timer expiry
Mobility Monitoring
VS.RrcActiveSetUpdateCompleteProcedure #415
This measurement provides the number of successful RRC Active Set Update procedures, for which the
cell is
the in the list of the active set before or after the Active Set Update execution (even if it is added or
removed due to this procedure). It is incremented once per procedure, whatever the number of cells.
VS.RrcActiveSetUpdateUnsuccess #402
This measurement provides the number of failed RRC ACTIVE SET UPDATE procedures managed by a RNC,
for
each cell controlled by the RNC. The measurement attached to a given cell is incremented for a failed
addition or removal of this cell from the active set.
Screenings:
0 : RRC ACTIVE SET UPDATE FAILURE reception
1 : Time-out

Section 7 Pager 17
SHO execution - Metrics

FDDCell metric
USHO007_CR
#402.[all]
SHO
SHOFailure
FailureRate
Rate
=
#402.[all] + #415
What is, for any UE, the Average number of its RLs or its Average Active Set size
when this cell is the Primary cell for this UE ?
Reference FDDCell metric
URL016_CR
Mean
Mean Sector
Sector #25.[0].Avg + 2x(#25.[1].Avg+#25.[2].Avg) + 3x(#25.[3].Avg+) +
==
per
per User
User
#25.[all screenings].Avg
Average number of Radio Links in the AS of UEs having this cell as their Primary
Average number of UEs having this cell as their Primary
7 18
Mobility Monitoring
VS.UeWithNRadioLinksEstCellsBts - #25
Distribution of the number of mobiles having N Radio-Links in their Active Set
A set of subcounters screened on: Number of radio links
Sub-Counter #0 : 1 Radio Link
Sub-Counter #1 : 2 RL (Reference Cell + 1 RL on the same BTS)
Sub-Counter #2 : 2 RL (Reference Cell + 1 RL on another BTS)
Sub-Counter #3 : 3 RL (Reference Cell + 2 RL on the same BTS)
Sub-Counter #4 : 3 RL (Reference Cell + 1 RL on the same BTS + 1 RL on another BTS)
Sub-Counter #12 : 6 RL or more (Reference Cell + 2 RL on the same BTS + 3 or more RL on another
BTS)
Sub-Counter #13 : 6 RL or more (Reference Cell + 1 RL on the same BTS + 4 or more RL on another
BTS)
Sub-Counter #14 : 6 RL or more (Reference Cell + 5 or more RL on another BTS)

Section 7 Pager 18

SHO Mobility Analysis
RNC level
High SPU
RL016
Low SPU
RL016
SHO Analysis
RNC level
7 19
Check SHO Parameters settings

Check Radio Design
Mobility Monitoring
Issue characterization:
Can it affect certain/all services (CS, PS,etc)
Certain/all Network elements, Top N cells
Certain/all period of time, since when
Certain failure causes
After certain event (upgrade, feature activation, configuration changes in Iur, reparentings?
(*) New counters

Section 7 Pager 19

SHO Analysis
RNC level
Top worst cells

Few cells?
Correlate with
Node B alarms
Top worst cells
RL Setup
Blocking Rate
URL036_CR > Th
Inter RNC SHO analysis
RL Addition
Blocking Rate
URL037_CR > Th
s
succes
itionUnuses]
d
d
A
L
R
ca
[failure
ccess
pUnsu es]
s
RL Setu
u
a
c
[failure
RRM Capacity Analysis

Cell level
CEM & Iub Capacity Analysis

Node B level
RRM Capacity Analysis
Cell level
High Iur Radio link failures
(setup/addition)
All cells? Or set of cells
No
Yes
Check configuration for the set of cells
Correlate with events that affect Iur:
i.e configuration changes like reparenting
7 20
Capacity analysis cell level
Mobility Monitoring

Section 7 Pager 20
7 21
Mobility Monitoring

Section 7 Pager 21
3G-2G CS Handover Success - counters

Reference
FDDCell Counters
Decision for
3G->2G HHO
UE
Node B
RNC
CN
BSS
Measurement Report
#164[0] 3G to 2G HO detection
#1839 Iu relocation attempt
Relocation Required
Relocation Command
Handover from UTRAN Command

Handover Access
Physical information
Handover Complete
Iu Release Command
RL Deletion Reqt
successful 3G to 2G
RL Deletion Respe
relocation
#167[0]
successful 3G to 2G outgoing HO
7 22
preparation
execution
Iu Release Complete
Released
#1841[0] successful 3G to 2G outgoing HO
#505[1] successful 3G to 2G outgoing HO
Mobility Monitoring
VS.3gto2gHoDetectionFromFddcell #164:
This measurement provides the number of RRM decisions for a 3G TO 2G handover performed by a RNC,
screened by reference cell from which the UEs have left the 3G Network, when these cells are controlled by the
considered RNC. This measurement considers both CS and PS handovers.
0 --> Rescue CS
2 --> Service
1 --> Rescue PS
3 --> No resource available (CAC failure)
VS.3gto2gOutHoSuccess #167:
This measurement provides the number of successful 3G to 2G outgoing Handovers. It is incremented at the
reception of an Iu_Release_Command with cause Successful 3G to 2G Relocation
Screening:
Sub-Counter #0 : rescue CS
Sub-Counter #1 : rescue PS
Sub-Counter #2 : service CS
Sub-Counter #3 : Service PS
Sub-Counter #4 : No resource available CS (CAC)
Sub-Counter #5 : No resource available PS
(CAC)
VS.IuReleaseCommandCs - #505: This measurement provides the total number of Iu Release Command CS
received by the RNC. It is incremented at the reception of an Iu_Release_Command for some cause values.
Screening: per Iu Release Command cause
0 : Normal end of communication (3GPP RANAP cause 83)
1 : Successful relocation
2 : UTRAN generated reason (3GPP RANAP cause 15 or Iu_Release_Request sent by RNC)
3 : Other cause (all other 3GPP RANAP causes)
4 : Relocation Cancelled (3GPP RANAP cause
10)
5 : O&M Intervention (3GPP RANAP cause 113)
6 : Unspecified Failure (3GPP RANAP cause
115)
7 : User Inactivity (3GPP RANAP cause 16)
8 : No Remaining RAB (3GPP RANAP cause 31)
9 : Successful 3G/3G relocation (3GPP RANAP cause 11)
IRATHO.SuccOutCS - #1841
Successful outgoing CS 3G to 2G handover (CS Inter-RAT handover).
Sub-Counter #0: Rescue CS
Sub-Counter #2: No resource available CS (CACSection
failure)
7 Pager 22
Sub-Counter #1: Service CS
3G-2G Global CS HHO Success Rate

The 3G2G Global CS HHO success rate evaluates success rate of the
overall 3G2G CS HHO procedure by considering all the cases of failures
(3G or 2G failures).
UHO3G2G019_C_Cs
CS
CS3G-2G
3G-2GHHO
HHO
Radio
Success
Radio SuccessRate
Rate
(Rescue)
(Rescue)
#167.[0]
#164.[0]
UHO3G2G019_R_Cs
RNC metric
CS
CS3G-2G
3G-2GHHO
HHO
Radio
Success
Radio SuccessRate
Rate =
(Rescue)
(Rescue)
7 23
cell(#167.[0]) + Nrnc(#168.[0])
cell(#164.[0]) + Nrnc(#165.[0])
Mobility Monitoring
VS.3gto2gOutHoSuccessNrnc - #168
Number of successful outgoing Hard Handovers from 3G to 2G when reference cell is on drift
RNC
A set of subcounters screened on: HO reason for which a 3G to 2G Relocation was initiated.
Sub-Counter #1 : rescue PS
Sub-Counter #2 : No resource available CS (CAC failure)
Sub-Counter #3 : No resource available PS (CAC failure)
VS.3gto2gHoDetectionFromFddcellNeighbRnc - #165
Number of RRM decisions for a 3G TO 2G handover performed by a RNC, screened by
neighboring RNC grouping reference cells from which the UEs have left the 3G Network. This
measurement considers both CS and PS handovers.
A set of subcounters screened on: Reason for initiating the 3G to 2G HO
Sub-Counter #0 : Rescue CS
Sub-Counter #1 : Rescue PS
Sub-Counter #2 : No resource available (CAC failure)

Section 7 Pager 23
3G-2G CS Handover Preparation Success - counters

Reference FDDCell counter
#164[0] 3G to 2G HO detection
#1839 Iu relocation attempt
UE
Node B
RNC
CN
BSS
Measurement Report
Relocation Required
RNC counter
#556[2] Iu relocation required
.
Relocation Command
#557[2] Iu relocation command
#154[0] #156[0]
HO from UTRAN command
Reference FDDCell counter
7 24
RNC counter
Mobility Monitoring
#154 VS.RrcHoFromUtranCmdTrigByEcNo
Number of Inter Rat handover from utran command sent by RNC with a reference cell for which the RNC
is serving and the handover has been initiated because of Ec/No:
#156 VS.RrcHoFromUtranCmdTrigByRscp
Number of Inter-RAT handover from Utran command sent by RNC with a reference cell for which the RNC
is serving, and the handover has been initiated because of RSCP criteria:
#158 VS.RrcHoFromUtranCmdTrigRnc
Number of Inter-RAT handover from Utran command sent by RNC with a reference cell for which the RNC
is serving, and the handover has been initiated because of CAC failure events or Service events, NOT
because of Alarm radio condition.
#556 VS.IuRelocationRequired
A set of subcounters screened on: Per type of core and type of relocation
Sub-Counter #0 : 3G-3G CS, UE involved
Sub-Counter #1 : 3G-3G PS, UE involved
Sub-Counter #2 : 3G-2G CS
Sub-Counter #3 : 3G-3G CS, UE not involved
Sub-Counter #4 : 3G-3G PS, UE not involved
#557 VS.IuRelocationCommands
Same screenings as for #556

Section 7 Pager 24
3G-2G CS HO Preparation Success

The main metrics used to monitor the CS HHO 3G to 2G

preparation phase on the target side are:
Failures from the target network when allocating the resources for
the mobile (Relocation Preparation Failure)
Failures from 2G due to wrong neighboring definition of 2G in 3G &
opposite
Call dropped after Relocation Required & before HO from UTRAN
Command.
7 25
Mobility Monitoring

Section 7 Pager 25
3G-2G CS Handover Preparation Failure - counters

EXERCISE: Find the two counters in the catalogue
Decision for HHO
UE
Node B
RNC
CN
BSS
Measurement Report
1st
case
Relocation Required
#???
#568[2] Relocation cancel
Relocation Cancel
TRELOCprep
expiry
No answer from CN to Relocation Required

Decision for HHO
2nd
case
Measurement Report
#558[6-9]
#???
#???
#1845[0-11]
Relocation preparation failure
Relocation Required
Relocation Preparation
Failure
CN answers NACK to Relocation Required

7 26
Mobility Monitoring
Handover failure
on the 2G side
TRELOCprep = Timer RELOcation preparation

Section 7 Pager 26
Handover
failure
3G-2G CS HO Preparation Failure Rate

UHO3G2G018_R_Cs
RNC metric
3G-2G
3G-2GCS
CSHO
HOPreparation
Preparationfailure
failurerate
rate
(Rescue+CAC
failure+Service)
(Rescue+CAC failure+Service)
#558.[5-9]
#556.[2]
FDDCell metric
3G-2G
3G-2GCS
CSHO
HOPreparation
Preparation
#164[all] (#154+#156+#158.[all])
=
failure
rate
failure rate
#164[all]
(Rescue+CAC
(Rescue+CACfailure+Service)
failure+Service)
FDDCell metric
3G-2G
3G-2GCS
CSHO
HOPreparation
Preparation
failure
rate
=
failure rate
(Rescue+CAC
(Rescue+CACfailure+Service)
failure+Service)
7 27
#1845.[all]
#1839
#1843
#1839
Mobility Monitoring
VS.IuRelocationCmdFailuresCs - #558
Number of relocation Preparation failures on CS Iu interface
A set of subcounters screened on: IU Relocation command failure causes
Sub-Counter #5 : 3G to 2G UE involved. Relocation timeout
Sub-Counter #6 : 3G to 2G UE involved. Relocation already in progress
Sub-Counter #7 : 3G to 2G UE involved. Relocation failure in target system
Sub-Counter #8 : 3G to 2G UE involved. Relocation unable to establish
Sub-Counter #9 : 3G to 2G UE involved. Other relocation failure
VS.IuRelocationRequired - #556
Number of relocation required at Iu interface
IRATHO.FailRelocPrepOutCS - #1845
Failed relocation preparations for UMTS to GSM handover on the reference cell from network point of view per failure cause
Sub-Counter #0: Relocation Cancelled (10)
Sub-Counter #1: Requested Ciphering and/or Integrity Protection Algorithms not Supported (12)
Sub-Counter #2: Relocation Failure in Target CN/RNC or Target system (29)
Sub-Counter #3: Relocation not supported in Target RNC or Target System (44)
Sub-Counter #4: Relocation Target not allowed (50)
Sub-Counter #5: No Radio Resources Available in Target Cell (53)
Sub-Counter #6: Traffic Load in The Target Cell Higher Than in the Source Cell (57)
Sub-Counter #7: Abstract Syntax Error (Reject) (100)
Sub-Counter #8: O&M Intervention (113)
Sub-Counter #9: No Resource Available (114)
Sub-Counter #10: Unspecified Failure (115)
Sub-Counter #11: Expiry of the timer TRELOCprep

Section 7 Pager 27
3G-2G CS Handover Execution Success - counters

UE
Node B
RNC
CN
BSS
Relocation Command
#154[0] #159[0]
HO from UTRAN command
Handover Access
Physical information
Handover Complete
Iu Release Command
RL Deletion Reqt
successful 3G to 2G
Reference
RL Deletion Respe
relocation
FDDCell Counters
Iu Release Complete
Released
#167[x] , #168[x]
successful 3G to 2G outgoing handovers
7 28
Mobility Monitoring

Section 7 Pager 28
3G-2G CS HO Execution Success Rate

CS 3G-2G HHO
Execution Success Rate
UHO3G2G020_C_Cs
#167.[0,2,4]
=
#154[0] + #156 [0] + #158 [0,1]
RNC metric
CS 3G-2G HHO
Execution
=
Success Rate
UHO3G2G020_R_Cs
cell(#167.[0,2,4]) + Nrnc(#168.[0,2])
#154 + #155 + #156 + #157 + #158 + #159
7 29
Mobility Monitoring

Section 7 Pager 29
3G-2G CS Handover Execution Failure - counters

UE
Node B
RNC
1st
case
Relocation Command
BSS
HO Request Ack
Handover failure on the target system

Handover from UTRAN Failure
#160[x] ; #161[x]
HO From UTRAN Failure
Relocation Cancel
UE fails to connect to 2G and reverts to 3G
2nd
case
CN - CS
Relocation Command
TRelocOveral
UE fails to connect to 2G
and fails to reverts to 3G
expiry
Iu Release Request
HHO Drop
#576[5] HHO drop

7 30
HO Request Ack
Reference
FDDCell Counters
Mobility Monitoring
VS.RrcHoFromUtranFailure - #160
Number of RRC HANDOVER FROM UTRAN FAILURE messages (3G to 2G handover for
CS or CS+PS) received by an RNC, acting as serving RNC, for each cell controlled by this
RNC.
A set of subcounters screened on: HO reason for which the RRC / HANDOVER_
FROM_UTRAN_COMMAND message is sent
VS.RrcHoFromUtranFailureNeighbRnc - #161
Number of RRC HANDOVER FROM UTRAN FAILURE (3G to 2G handover for CS or
CS+PS) messages received by an RNC acting as serving, for each neighboring RNC.
A set of subcounters screened on: HO reason for which the RRC / HANDOVER_
FROM_UTRAN_COMMAND message is sent
VS.IuReleaseReqCs - #576
Number of RANAP/IU_RELEASE_REQUEST sent by RNC to CoreNetwork CS
Sub-Counter #5 : Abnormal condition with cause TRelocOveral expiry

Section 7 Pager 30
3G-2G CS Handover: FDDCell Counter Tree (Rescue case)

Request
VS.3gto2gHoDetectionFromFddcell
#164[0]
VS.RrcHoFromUtranCommand
Preparation failure
Attempt
#164[0] [#154+#156]
[#154+#156]
Execution failure
Success
[#154+#156] #167[0]
#167[0]
VS.RadioBearerSetupUnsuccess
HO from UTRAN Failure

#160[0]
HHO drop
[#154+#156]- #167[0] - #160[0]
7 31
Mobility Monitoring

Section 7 Pager 31
3G-2G CS HO Execution Failure Rate (reversion to 3G)

UHO3G2G002_C_Cs
#160[0,1,2]
CS
CS3G-2G
3G-2GHO
HOExecution
ExecutionFailure
FailureRate
Rate =
#154[0] + #156[0] + #158[0,1]
RNC metric
CS
CS3G-2G
3G-2GHO
HO
Execution
Failure
Execution FailureRate
Rate
7 32
UHO3G2G002_R_Cs
cell(#160[0,1,2]) + Nrnc(#161[0,1])
#154 + #155 + #156 + #157 + #158 + #159
Mobility Monitoring
2G Synchronization failure and reversion to 3G:

If the UE can not synchronize with the 2G target network during the 3G2G HHO execution phase, the UE
sends the HO from UTRAN Failure message to the RNC to come back on the 3G network.
The CS 3G2G HHO Execution Failure Rate metric is proposed to evaluate the 2G target cell
synchronization failure.
Notes:
Reference FDDCell metric:
CS 3G-2G HO Execution Failure Rate (2G synchronization failure) = VS.RrcHoFromUtranFailure /
(VS.RrcHoFromUtranCmdTrigByEcNo +
VS.RrcHoFromUtranCmdTrigByRscp +
VS.RrcHoFromUtranCmdTrigRnc)
RNC Metric:
CS 3G-2G HO Execution Failure Rate (2G synchronization failure) =
(VS.RrcHoFromUtranFailure + VS.RrcHoFromUtranFailureNeighbRnc ) /
(VS.RrcHoFromUtranCmdTrigByEcNo + VS.RrcHoFromUtranCmdTrigByEcNoNrnc +
VS.RrcHoFromUtranCmdTrigByRscp + VS.RrcHoFromUtranCmdTrigByRscpNrnc +
VS.RrcHoFromUtranCmdTrigRnc + VS.RrcHoFromUtranCmdTrigRncNrnc)

Section 7 Pager 32
3G-2G CS HO Execution Failure Rate (call drop)
UHO3G2G024_C_Cs
Number of CS 3G2G
=
HHO drops
#154 + #156 + #158 - #160[all] - #505[1]
UHO3G2G022_C_Cs
CS 3G2G HHO
Execution Failure Rate
because of 3G Reason
#154 + #156 + #158 - #160[all] - #167[0,2,4]
=
#154 + #156 + #158 - #160[all]
3G-2G CS HO which leads

either to a Success or to a Drop
7 33
Mobility Monitoring
1.
The number of calls lost during a 3G-2G HO is:

Number of HO From UTRAN Command sent to UE
Number of HO From UTRAN Failure received from UE
Number of HO success to 2G
2.
CS 3g-2G HO Execution Failure rate (call lost):

The HO Failures to 2G with UE successfully reverting to 3G are not taken into account.
Call lost:
If the RNC does not receive the HO from UTRAN Failure RRC message from the UE or the Iu release
command with the cause successful 3g2g relocation from the CN, there is failure at 3G side (the
call is dropped during the 3G2G HHO).
The CS 3G2G HHO Execution Failure Rate because of 3G Reason metric is proposed to evaluate the calls
dropped during the 3G2G CS HHO.

Section 7 Pager 33
7 34
Mobility Monitoring

Section 7 Pager 34
3G-3G HHO InterRNC no Iur Preparation Success - counters

UE
Node B
RNC 1
CN
RNC 2
Measurement Report
#556[x]
Iu relocation required
Relocation Required
Relocation Request
RNC counter
#535[x]
Iu relocation request
FDDCell counter
Relocation Request Ack
#557[x]
Iu relocation command
Relocation Command
not counted
RNC counter
7 35
Source side
Target side
Outgoing HHO
Incoming HHO
Mobility Monitoring
#556 VS.IuRelocationRequired
Sub-Counter #0 : 3G-3G CS, UE involved
Sub-Counter #1 : 3G-3G PS, UE involved
Sub-Counter #3 : 3G-3G CS, UE not involved
Sub-Counter #4 : 3G-3G PS, UE not involved
#557 VS.IuRelocationCommands
Same screenings as for #556
VS.IuRelocationRequests - #535
Number of relocation request at Iu interface
A set of subcounters screened on: Per type of relocation and CN Domain
Sub-Counter #0 : CS 3G-3G Relocation
Sub-Counter #1 : PS 3G-3G Relocation
Sub-Counter #2 : CS 2G-3G Relocation
Sub-Counter #3 : CS 3G-3G Relocation, UE not involved
Sub-Counter #4 : PS 3G-3G Relocation, UE not involved

Section 7 Pager 35
3G-3G HHO InterRNC no Iur Preparation Failure - counters

UE
Node B
RNC 1
CN
RNC 2
Measurement Report
Relocation Required
Relocation Request
FDDCell counters
#536[x] for CS, #537[x] for PS
Iu relocation request failure
Relocation Preparation
Failure
#558[x]
Iu relocation
preparation failure
RNC counter
7 36
Relocation Request
Failure
Source side
Target side
Outgoing HHO
Incoming HHO
Mobility Monitoring
VS.IuRelocationCmdFailuresCs - #558
Number of relocation Preparation failures on CS Iu interface
A set of subcounters screened on: IU Relocation command failure causes
Sub-Counter #0 : 3G to 3G UE involved. Relocation timeout
Sub-Counter #1 : 3G to 3G UE involved. Relocation already in progress
Sub-Counter #2 : 3G to 3G UE involved. Relocation failure in target system
Sub-Counter #3 : 3G to 3G UE involved. Relocation unable to establish
Sub-Counter #4 : 3G to 3G UE involved. Other relocation failure
VS.IuRelocationRequestFailuresCs - #536
Number of relocation requests failures on CS Iu interface
Sub-Counter #0 : 3G-3G UE involved. Relocation timeout
Sub-Counter #1 : 3G-3G UE involved. Relocation failure in target system
Sub-Counter #2 : 3G-3G UE involved. Relocation unable to establish
Sub-Counter #3 : 3G-3G UE involved. Other relocation failure
Sub-Counter #8 : 3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for the entering CS
reloc.
Sub-Counter #10 : 3G-3G UE involved. Unavailable IU CNX context resources. Pegged when the IU
connexion contexts are exhausted for the entering CS reloc.
IuRelocationRequestFailuresPs - #537
Number of relocation requests failures on PS Iu interface
Sub-Counter #0: 3G-3G UE involved. Relocation time out
Sub-Counter #1: 3G-3G UE involved. Relocation failure in target system
Sub-Counter #2: 3G-3G UE involved. Relocation unable to establish
Sub-Counter #3: 3G-3G UE involved.
Other
relocation
failure @@YEAR
All Rights
Reserved
Alcatel-Lucent
1.1when CAC fails for then entering PS
Sub-Counter #4: 3G-3G UE involved. 3JK10061AAAAWBZZA
RRC Context CAC.Edition
Pegged
Section 7 Pager 36
reloc.
3G-3G HHO InterRNC no Iur - Preparation Success Rate

FDDCell metric
UHO3G3G002_CR_Cs
CS 3G-3G HHO
Incoming
=
Preparation
Success Rate
#535.[0,3] - #536.[0-3,8,10,12-15]
#535.[0,3]
FDDCell metric
PS 3G-3G HHO
Incoming
=
Preparation
Success Rate
RNC metric
UHO3G3G007_R_Cs
CS 3G-3G HHO
Outgoing
=
Preparation
Success Rate
#557.[0,3]
#556.[0,3]
7 37
UHO3G3G004_CR_Ps
#535.[1,4] - #537.[0-3,8,10,12-15]
#535.[1,4]
RNC metric
UHO3G3G007_R_Ps
PS 3G-3G HHO
Outgoing
=
Preparation
Success Rate
#557.[1,4]
#556.[1,4]
Mobility Monitoring
Due to the counters implementation, the 3G3G HHO Preparation success rate is available at RNC level
only for Source side and at Cell level for Target side.

Section 7 Pager 37
3G-3G HHO InterRNC no Iur Execution Success - counters

UE
Node B
RNC 1
CN
RNC 2
Measurement Report
Relocation Required
Relocation Request
Relocation Request Ack
Relocation Command
Radio Bearer Reconfiguration
Radio Bearer Reconfiguration Complete
Relocation Detect
#505[9] & #552[9] for CS

#506[9] & #553[9] for PS
Iu relocation command
Relocation Complete
FDDCell & Neighboring RNC

counters
RL Deln Reqt
RL
Deln
Iu Release Command
#569[x]
Iu relocation complete
Respe
Iu Release Complete
7 38
RNC counter
Mobility Monitoring
VS.IuRelocationCompletes - #569
Number of relocation completes at Iu interface
A set of subcounters screened on: Per type of relocation and CN domain
Sub-Counter #1 : 3G-3G PS
VS.IuReleaseCommandCs - #505
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC from CS domain.
Sub-Counter #9: Successful 3G3G relocation
VS.IuReleaseCommandPsNRnc - #553
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-PS interface when the
reference cell is located on a Drift RNC.
VS.IuReleaseCommandPs - #506
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC from PS domain.
VS.IuReleaseCommandCsNRnc - #552
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC on the IU-CS interface when the
reference cell is located on a Drift RNC.

Section 7 Pager 38
3G-3G HHO InterRNC no Iur Execution Success Rate

RNC metric
UHO3G3G003_R_Cs
CS
CS3G-3G
3G-3GHHO
HHOIncoming
Incoming =
Execution
ExecutionSuccess
SuccessRate
Rate
#569.[0]
cell(#0535.[0,3] - #536.[0-3,8,10,12-15])
RNC metric
UHO3G3G005_R_Ps
PS
PS3G-3G
3G-3GHHO
HHOIncoming
Incoming =
Execution
Success
Execution SuccessRate
Rate
# 569.[1]
cell(#535.[1,4] - #537.[0-3,8,10,12-15])
RNC metric
UHO3G3G003_R_Cs
CS
CS3G-3G
3G-3GHHO
HHOOutgoing
Outgoing =
Execution
Success
Rate
cell(#505.[9]) + Nrnc(#552.[9])
#557.[0,3]
RNC metric
UHO3G3G009_R_Ps
CS
CS3G-3G
3G-3GHHO
HHOOutgoing
Outgoing=
Execution
Success
Rate
7 39
cell(#506.[9]) + Nrnc(#553.[9])
#557.[1,4]
Mobility Monitoring

Section 7 Pager 39
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Success

Reference
FDDCell Counters
S
PS+C
UE
Target
Node B
Source
Node B
RNC
Measurement Report
RL Setup Request
RL Setup Response
RB Reconfiguration
Decision for
HHO
#174[x]
Outgoing inter-freq
HHO attempt
#176[x]
Incoming inter-freq
HHO attempt
RB Reconfiguration complete
RL Deletion Request
RL Setup Deletion Response
#175[x]
Outgoing inter-freq
HHO success
#177[x]
Incoming inter-freq
HHO success
7 40
Mobility Monitoring
VS.OutGoInterFreqHoAtt - #174
Number of hard handovers attempted from this cell to another inter-frequency cell located either in the
same RNC or in a neighbouring RNC (a Iur link is setup towards the inter-frequency cell).
Sub-Counter #0: Rescue
Sub-Counter #1: Service
Sub-Counter #2: No resource available (CAC failure)
VS. IncomInterFreqHoAtt - #176
Number of hard handovers attempted to this cell from another inter-frequency cell located either in the
same RNC or in a neighbouring RNC (a Iur link is setup towards the inter-frequency cell).
same screenings as #174
VS.OutGoInterFreqHoSuc - #175
Number of successful hard handovers from this cell located on the serving RNC to another interfrequency cell located either in the same RNC or in a neighbouring RNC (a Iur link is setup towards the
inter-frequency cell).
VS.IncomInterFreqHoSuc - #177
Number of successful hard handovers to this cell located on the serving RNC from another interfrequency cell located either in the same RNC or in a neighbouring RNC (a Iur link is setup towards the
inter-frequency cell).

Section 7 Pager 40
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Rate

3G3G
3G3GInter-freq
Inter-freqHHO
HHO
Outgoing
Failure
Outgoing FailureRate
Rate
# 175.[all]
#174.[all]
3G3G
3G3GIntra-RNCHHO
Intra-RNCHHO
Incoming
IncomingFailure
FailureRate
Rate
7 41
#177.[all]
#176.[all]
Mobility Monitoring

Section 7 Pager 41
3G-3G Inter-frequency HHO - Intra-RNC Success - counters

S
PS+C
UE
Target
Node B
Source
Node B
RNC
Decision for
HHO
Measurement Report
RL Setup Request
RL Setup Response
#170[x]
Outgoing intraRNC
inter-freq HHO attempt
RB Reconfiguration
#172[x]
RB Reconfiguration complete
Incoming intraRNC
inter-freq HHO attempt
RL Deletion Request
RL Setup Deletion Response
Reference
FDDCell Counters
7 42
Mobility Monitoring
VS.IntraRncOutInterFreqHoAttempt - #170
Number of Intra RNC outgoing Hard Handovers attempted from this cell to another cell using another
frequency in the same RNC
A set of subcounters screened on: Reason for initiating the Intra RNC HHO
Sub-Counter #0 : HO without CM measurements
Sub-Counter #1 : HO with CM measurements
Sub-Counter #2 : HSDPA capable mobile to HSDPA layer
Sub-Counter #3 : HSDPA capable mobile to non-HSDPA layer
Sub-Counter #4 : Non-HSDPA capable mobile to non-HSDPA layer
VS.IntraRncIncInterFreqHoAttempt - #172
Number of Intra RNC Hard Handovers attempted to this cell from another cell in the same RNC on a
different frequency.
A set of subcounters screened on: Reason for initiating the Intra RNC HHO
Sub-Counter #0 : HO with CM measurements Inter-Band
Sub-Counter #1 : HO with CM measurements
Sub-Counter #2 : HSDPA capable mobile to HSDPA layer
Sub-Counter #3 : HSDPA capable mobile to non-HSDPA layer
Sub-Counter #4 : Non-HSDPA capable mobile to non-HSDPA layer
Inter-freq inter-Band HHO are counted in sub-counters s0, intra-band in sub-counters s1.
Sub-counters s2, s3 and s4 are pegged when RRC Traffic Segmentation is performed.
Incremented for both CS and PS cases.

Section 7 Pager 42
3G-3G Inter-frequency HHO - Intra-RNC Failure - counters

UE
Source
Node B
Target
Node B
RNC
Decision for
HHO
Measurement Report
RL Setup Request
RL Setup Failure
S
PS+C
UE
#171[x]
Outgoing intraRNC
inter-freq HHO failure
#173[x]
Source
Node B
Target
Node B
RNC
Incoming intraRNC
inter-freq HHO failure
Measurement Report
RL Setup Request
RL Setup Response
RB Reconfiguration
Reference
FDDCell Counters
RB Reconfiguration Failure
7 43
Mobility Monitoring
VS.IntraRncOutInterFreqHoFail - #171
Number of Intra RNC Hard Handovers attempted from this cell to another cell using another frequency in
the same RNC that failed to complete succesfully.
A set of subcounters screened on: Failure reason for Intra RNC HHO
Sub-Counter #0 : HO with CM measurement Inter-Band
Sub-Counter #1 : HO with measurements NodeB failure
Sub-Counter #2 : HO with measurements Failure on RRC
Sub-Counter #3 : HO with CM measurement Not enough resources
Sub-Counter #4 : HO with CM measurement NodeB failure
Sub-Counter #5 : HO with CM measurement Failure on RRC
VS.IntraRncIncInterFreqHoFail - #173
Number of Intra RNC Hard Handovers attempted to this cell from another using another frequency
in the same RNC that failed to complete succesfully.
A set of subcounters screened on: Failure reason for Intra RNC HHO
Sub-Counter #0 : HO with CM measurement Inter-Band
Sub-Counter #1 : HO with measurements NodeB failure
Sub-Counter #2 : HO with measurements Failure on RRC
Sub-Counter #3 : HO with CM measurement Not enough resources
Sub-Counter #4 : HO with CM measurement NodeB failure
Sub-Counter #5 : HO with CM measurement Failure on RRC
Sub-counters s1 and s2 are always equal to zero.
Inter-freq intra-Band HHO failures are counted in sub-counters s3, s4 and s5.
Inter-freq inter-Band HHO failures are all counted in sub-counters s0.
Section 7 Pager 43
3G-3G Inter-frequency HHO - Intra-RNC Failure Rate

UHO3G3G012_CR
3G3G
3G3GIntra-RNC
Intra-RNCInter-freq
Inter-freq
HHO
Incoming
Failure
HHO Incoming FailureRate
Rate
#172.[1]
UHO3G3G011_CR
3G3G
3G3GIntra-RNC
Intra-RNCInter-freq
Inter-freq
HHO
Outgoing
Failure
HHO Outgoing FailureRate
Rate
7 44
# 173.[1-5]
#171.[1-5]
#170.[1]
Mobility Monitoring

Section 7 Pager 44
7 45
Mobility Monitoring

Section 7 Pager 45

CS 3G2G Mobility Analysis
Network level
Counters
Preparation part

RNC level
Counters

Network level
Low rate execution part 2G side

RNC level
Counters
3G 2G CS HHO Success Rate < Th
UHO3G2G019_R_Cs
HO3G2G003 and HO3G2G004
to monitor the detection.
CS 3G2GPreparation
Analysis Cell level
Counters
CTG Analysis
3G2G HHO CS preparation
failure rate
UHO3G2G018_R_Cs
CS 3G2GPreparation
Analysis Selected Cells
CTG Analysis
Determine the RNC with

High UHO3G2G018_R_Cs
CS 3G2G Preparation Analysis

RNC level
7 46
Mobility Monitoring

Section 7 Pager 46
3G-2G HHO CS execution

success rate
UHO3G2G020_R_Cs
Determine the RNC with

Low UHO3G2G020_R_Cs
CS 3G2G Execution Analysis

RNC level
3G-2G CS HHO Preparation Analysis & Troubleshooting

Preparation 3G2G CS HHO Analysis
RNC level
To determine the rejection causes
(Refer to 3GPP TS 25.413):
#0558 Iu relocation command
failures CS
High CS 3G2G Rejection

Success rate
3G2G HHO CS preparation

failure rate
UHO3G2G018_R_Cs

Success rate
due to unable to establish
due to Time out
Check Outage in Transmission Network

Preparation 3G2G HHO Failures
Between 3G CN and 2G network
TOP N Cells
Check the Neighbouring cells

definition
Counter
Sub-c ounters

Success rate
due to Failure in Target System

TOP N Cells
Check the 2G Neighbouring

Cells capacity Analysis
Counter
To determine the worst N cells with a

representative number of Preparation
3G2G HHO Failures:
the highest number of #0109 -#0101
VS.3gto2gHoDetectionFromFddcell VS.RrcHoFromUtranCommand

Success rate
due to Other Reasons

TOP N Cells
Check the Outage in

the 2G target network identified
Sub-c ounters
558
VS.IuRelocationCmdFailuresCs.3Gto2GRelocTimeoutUeInv
1845
IRATHO.FailRelocPrepOutCS.TRELOCprep_exp
558
VS.IuRelocationCmdFailuresCs.3Gto2GAlreadyInProgrUeInv
1845
IRATHO.FailRelocPrepOutCS.TrLdHighTarCell
558
VS.IuRelocationCmdFailuresCs.3Gto2GFailTargetUeInv
1845
IRATHO.FailRelocPrepOutCS.FailTarSys
558
VS.IuRelocationCmdFailuresCs.3Gto2GUnableToEstabUeInv
1845
IRATHO.FailRelocPrepOutCS.NoResAvr
558
VS.IuRelocationCmdFailuresCs.3Gto2GOtherUeInv
1845
IRATHO.FailRelocPrepOutCS.NoRRTarCell
7 47
Mobility Monitoring

Section 7 Pager 47
3G-2G CS HHO Execution Analysis & Troubleshooting

3G2G CS HHO Execution Analysis
RNC level
To determine the
worst N cells with a
representative
number of HO From
UTRAN Failures:
the highest number
of CS HO From
UTRAN Failure
Low HHO 3G2G CS execution

success rate
UHO3G2G020_R_Cs
To determine the
worst N cells with a
representative
number of HO From
UTRAN Failures:
the highest number
of CS Calls drop
due to CS 3G2G
HHO
3G-2G HHO CS execution failure rate (reversion to 3G)

UHO3G2G002_R_Cs
3G-2G HHO CS execution failure rate (call drop)

UHO3G2G022_R_Cs
3G-2G HHO CS execution failure rate (reversion to 3G)

TOP N Cells
UHO3G2G002_C_Cs
3G-2G HHO CS execution failure rate (call drop)

TOP N Cells
UHO3G2G022_C_Cs
Target 2G neighboring cells

RF condition analysis
7 48
Check the setting

of 3G2G CS HHO
Algorithm Parameters
Mobility Monitoring
The 1st step is to identify the days and the RNCs with too bad Global CS 3G2G HHO performances
This analysis can be completed with CTg in the cell that are selected for investigation through counter metrics and
can be trigger for further investigations

Section 7 Pager 48
Summary
Could you list the main causes for HHO preparation/execution

failures ?
What actions could improve HHO preparation/execution
performances ?
7 49
Mobility Monitoring

Section 7 Pager 49
Action to improve the Preparation phase
The 3G2G HHO Preparation Failure causes are the following ones:
Failure in 2G target cell (congestion, outage)
Wrong definition of 3G neighbouring identifiers (cells, LAC) in 2G network
Wrong definition of 2G neighbouring identifiers (cells, LAC) in 3G network
Timeout in the procedure (mainly on 2G side as 3G is just relaying messages)
Call dropped between Iu Relocation Required and HO from UTRAN Command
Any failure from the RNC and/or BTS during the procedure
When the 3G2G HHO Preparation Success rate is very low, it means that
the failure causes are not occasional ones:
Either wrong definition of 3G neighboring identifiers (cells, LAC) in 2G network
Or wrong definition of 2G neighboring identifiers (cells, LAC,) in 3G network
7 50
Mobility Monitoring

Section 7 Pager 50
Actions to improve the Execution phase
The 3G2G HHO Execution Failure causes are the following ones:
Mobile synchronization issue with 2G target cell
Radio issue to access the 2G target cell
Call Dropped (3G side) after HO from UTRAN command
When the 3G2G HHO Execution Success rate is very low, it means that the
failures are not due to some mobiles but rather to a radio issue on the 2G
target cell
7 51
Mobility Monitoring

Section 7 Pager 51

Please be reminded to fill in the form

for this module
The form can be found in the first part
of this course documentation
7 52
Mobility Monitoring

Section 7 Pager 52
End of Module
Module 1
7 53
Mobility Monitoring

Section 7 Pager 53

Mobility Monitoring

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mobility Monitoring

Transféré par

Droits d'auteur :

Formats disponibles

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

Corrections of counters and indicators

All Rights Reserved Alcatel-Lucent @@YEAR

Describe the mobility metric family

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

Module Objectives [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

Table of Contents [cont.]

All Rights Reserved Alcatel-Lucent @@YEAR

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

The Network Mobility analysis consists of:

3G3G Mobility analysis:

To be distinguished between CS and PS domain

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 SHO Monitoring and Troubleshooting

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 SHO Monitoring and Troubleshooting

SHO management  Active Set management

Different SHO procedures

Withdrawing a cell out of the Active Set

As most of the telecom procedure between UE and UTRAN, a Soft or Softer

CAC internal to the RNC

Establishment of the new RL

Involving RNC and Node-B

SHO execution phase

All Rights Reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent @@YEAR

2 SHO Monitoring and Troubleshooting

SHO preparation Softer HO Cell Addition - Counters (1/2)

Measurement Report (Event 1a or 1c)

Radio Link Addition Request

Measurement Report (Event 1a or 1c)

RNC CAC Failure

All Rights Reserved Alcatel-Lucent @@YEAR

Sub-Counter #1: Signalling Only

Sub-Counter #2: CS speech

Sub-Counter #3: CS Speech + PS DCH

Sub-Counter #4: CS Speech + HSDPA

Sub-Counter #5: CS Speech + PS DCH + PS HSDPA

Sub-Counter #6: CS Speech + PS DCH + PS DCH

Sub-Counter #7: CS Data

Sub-Counter #8: CS data + PS DCH

Sub-Counter #9: Cs Data + PS HSDPA

Sub-Counter #10: CS streaming

Sub-Counter #11: PS DCH DL / DCH UL

Sub-Counter #12: PS HSDPA DL / E-DCH UL

Sub-Counter #13: PS HSDPA DL / DCH UL

Sub-Counter #14: PS HSDPA DL / DCH UL + E-DCH UL Sub-Counter #15: PS DCH + PS DCH

Number of failures radio link reconfiguration preparation

2 SHO Monitoring and Troubleshooting

SHO preparation Softer HO Cell Addition - Counters (2/2)

SHO management Active Set management