Mobility Monitoring
-
Upload
alselawi-ahmad -
Category
Documents
-
view
8 -
download
0
description
Transcript of Mobility Monitoring
-
Section 7 Pager 1
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
Do not delete this graphic elements in here:
7All Rights Reserved Alcatel-Lucent @@YEAR
Module 13JK10061AAAAWBZZA Edition 1.1
Section 7Mobility Monitoring
9300 WCDMAUA06 R99 QoS Analysis and Traffic Load Monitoring
TMO18046 D0 SG DENI3.0
-
Section 7 Pager 2
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 2
Blank Page
This page is left blank intentionally
Corrections of counters and indicatorsnumbers, names and formulaeAddition of new UA6 counters allowing to monitor the CS Inter-RAT HHO preparationsuccess rate per CellAddition of Inter-Freq IntraRNC+InterRNC withIur counters
Chatila, RayanCharneau, Jean-Noel
2008-03-1801.1
First editionEl Abed, Achrafe2008-12-0101
RemarksAuthorDateEdition
Document History
-
Section 7 Pager 3
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 3
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
-
Section 7 Pager 4
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 4
Module Objectives [cont.]
This page is left blank intentionally
-
Section 7 Pager 5
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 5
Table of Contents
Switch to notes view!Page
1 Mobility Overview 7Mobility overview 8
2 SHO Monitoring and Troubleshooting 9SHO overview 10SHO preparation Softer HO Cell Addition - Counters (1/2) 11SHO preparation Softer HO Cell Addition - Counters (2/2) 12SHO preparation Softer HO Cell Addition - Metrics 13SHO preparation Soft HO Cell Addition - Counters (1/2) 14SHO preparation Soft HO Cell Addition - Counters (2/2) 15SHO preparation Soft HO Cell Addition - Metrics 16SHO execution - Active Set Update - Counters 17SHO execution - Metrics 18SHO Analysis & Troubleshooting (1/2) 19SHO Analysis & Troubleshooting (1/2) 20
3 HHO 3G-2G Monitoring 213G-2G CS Handover Success - counters 223G-2G Global CS HHO Success Rate 233G-2G CS Handover Preparation Success - counters 243G-2G CS HO Preparation Success 253G-2G CS Handover Preparation Failure - counters 263G-2G CS HO Preparation Failure Rate 273G-2G CS Handover Execution Success - counters 283G-2G CS HO Execution Success Rate 293G-2G CS Handover Execution Failure - counters 303G-2G CS Handover: FDDCell Counter Tree (Rescue case) 313G-2G CS HO Execution Failure Rate (reversion to 3G) 323G-2G CS HO Execution Failure Rate (call drop) 33
4 HHO 3G-3G Monitoring 343G-3G HHO InterRNC no Iur Preparation Success - counters 353G-3G HHO InterRNC no Iur Preparation Failure - counters 363G-3G HHO InterRNC no Iur - Preparation Success Rate 373G-3G HHO InterRNC no Iur Execution Success - counters 383G-3G HHO InterRNC no Iur Execution Success Rate 393G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Success 403G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Rate 413G-3G Inter-frequency HHO - Intra-RNC Success - counters 423G-3G Inter-frequency HHO - Intra-RNC Failure - counters 433G-3G Inter-frequency HHO - Intra-RNC Failure Rate 44
5 HHO 3G-2G Analysis & Troubleshooting 45CS 3G-2G Mobility Analysis & Troubleshooting 46CS 3G-2G Mobility Analysis & Troubleshooting 47CS 3G-2G Mobility Analysis & Troubleshooting 48Summary 49Action to improve the Preparation phase 50Actions to improve the Execution phase 51Self-Assessment on the Objectives 52End of Module 53
-
Section 7 Pager 6
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 6
Table of Contents [cont.]
Switch to notes view!
This page is left blank intentionally
-
Section 7 Pager 7
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 7
1 Mobility Overview
-
Section 7 Pager 8
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 8
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
-
Section 7 Pager 9
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 9
2 SHO Monitoring and Troubleshooting
-
Section 7 Pager 10
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 10
2 SHO Monitoring and Troubleshooting
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)
-
Section 7 Pager 11
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 11
2 SHO Monitoring and Troubleshooting
SHO preparation Softer HO Cell Addition - Counters (1/2)
Measurement Report (Event 1a or 1c)
Radio Link Addition Request
Radio Link Addition Response
UE Node B RNC
CACOK
#55Radio Link Additionto be performed
#49Radio Link AdditionsuccessSUCCES
S
FAILUREMeasurement Report (Event 1a or 1c)UE Node B RNC
CACNOK
#39.[2-7]Radio Link Additionunsuccess
RNC CAC Failure
FDDCell Counters
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
Sub-Counter #8: NodeB out of order (No answer) (Screening 8 is not implemented, is Always zero in V6.0.)
-
Section 7 Pager 12
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 12
2 SHO Monitoring and Troubleshooting
SHO preparation Softer HO Cell Addition - Counters (2/2)
Measurement Report (Event 1a or 1c)UE Node B RNC
CACOK
#39.[0]Radio Link Additionunsuccess
Radio Link Addition Request
FAILURE
Radio Link Addition Failure
UE Node B RNC
CACOK
#39.[1]Radio Link Additionunsuccess
Radio Link Addition Request
FAILURE
timer expiry
Node-B Failure
No answer from Node-B
FDDCell Counters
VS.RadioLinkAdditionUnsuccess #39
Number of unsuccessfull radio link setup
A set of subcounters screened on:
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
Sub-Counter #8: NodeB out of order (No answer)
-
Section 7 Pager 13
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 13
2 SHO Monitoring and Troubleshooting
SHO preparation Softer HO Cell Addition - Metrics
Radio Link Addition Success Rate
Radio Link Addition Success Rate
#49.[all]#55.[all]
=
URL027_CRFDDCell metric
URL037_CRFDDCell metric#39.[all except 1]
#55.[all]=
Radio Link Addition Blocking Rate
-
Section 7 Pager 14
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 14
2 SHO Monitoring and Troubleshooting
SHO preparation Soft HO Cell Addition - Counters (1/2)
SUCCESS
FAILURE
Measurement Report (Event 1a or 1c)
Radio Link Setup Request
Radio Link Setup Response
UE Node B 1 RNC
CACOK
#54Radio Link Setupto be performed
#48Radio Link Setupsuccess
Node B 2
Measurement Report (Event 1a or 1c)UE Node B 1 RNC
CACNOK #38.[2-7]
Radio Link Setupunsuccess
Node B 2
RNC CAC Failure
FDDCell Counters
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 #2: Rrm refusal
Sub-Counter #3: Iub Layer Congestion
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: INode refusal
Sub-Counter #8: NodeB out of order (No answer) (Screening 8 is not implemented, is Always zero in V6.0.)
-
Section 7 Pager 15
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 15
2 SHO Monitoring and Troubleshooting
SHO preparation Soft HO Cell Addition - Counters (2/2)
FAILURE
FAILURE
Node-B Failure
No answer from Node-B
Measurement Report (Event 1a or 1c)
Radio Link Setup Request
Radio Link Setup Failure
UE Node B 1 RNC
CACOK
#38.[0]Radio Link Setupunsuccess
Node B 2
Measurement Report (Event 1a or 1c)UE Node B 1 RNC
CACOK
#38.[1]Radio Link Setupunsuccess
Node B 2
timer expiry
Radio Link Addition Request
FDDCell Counters
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 #1: Timeout
Sub-Counter #2: Rrm refusal
Sub-Counter #3: Iub Layer Congestion
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: INode refusal
Sub-Counter #8: NodeB out of order (No answer)
-
Section 7 Pager 16
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 16
2 SHO Monitoring and Troubleshooting
SHO preparation Soft HO Cell Addition - Metrics
Radio Link Setup Success Rate
Radio Link Setup Success Rate
#48.[all]#48.[all] + #38.[all]
=
URL005_CRFDDCell metric
URL036_CRFDDCell metric
#38.[all except 1]#54.[all]
=Radio Link Setup Blocking Rate
-
Section 7 Pager 17
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 17
#402[0]
2 SHO Monitoring and Troubleshooting
SHO execution - Active Set Update - Counters
Active Set Update
Measurement Report (event)
#415
UE Node B RNC
Active Set Update Complete
SUCCESS
FAILURE
Active Set Update
Measurement Report (event)UE Node B RNC
Active Set Update FailureActive Set Update
Measurement Report (event)UE Node B RNC
No answer from UE
FDDCell Counters
#402[1] timer expiry
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 18
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 18
#25.[0].Avg + 2x(#25.[1].Avg+#25.[2].Avg) + 3x(#25.[3].Avg+) + #25.[all screenings].Avg
Mean Sector per User =Mean Sector per User =
2 SHO Monitoring and Troubleshooting
SHO execution - Metrics
SHO Failure Rate SHO Failure Rate #402.[all]
#402.[all] + #415=
USHO007_CRFDDCell metric
URL016_CRReference FDDCell metric
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
What is, for any UE, the Average number of its RLs or its Average Active Set sizewhen this cell is the Primary cell for this UE ?
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 #5 : 3 RL (Reference Cell + 2 RL on another BTS)
Sub-Counter #6 : 4 RL (Reference Cell + 2 RL on the same BTS + 1 RL on another BTS)
Sub-Counter #7 : 4 RL (Reference Cell + 1 RL on the same BTS + 2 RL on another BTS)
Sub-Counter #8 : 4 RL (Reference Cell + 3 RL on another BTS)
Sub-Counter #9 : 5 RL (Reference Cell + 2 RL on the same BTS + 2 RL on another BTS)
Sub-Counter #10 : 5 RL (Reference Cell + 1 RL on the same BTS + 3 RL on another BTS)
Sub-Counter #11 : 5 RL (Reference Cell + 4 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 19
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 19
2 SHO Monitoring and Troubleshooting
SHO Analysis & Troubleshooting (1/2)
SHO Mobility AnalysisRNC level
High SPURL016
SHO Analysis RNC level
Check SHO Parameters settingsCheck Radio Design
Low SPURL016
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 20
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 20
RRM Capacity AnalysisCell level
RL AdditionBlocking Rate
URL037_CR > Th
RL AdditionUnsucce
ss
[failure causes]
Top worst cells
Few cells?
Correlate with Node B alarms
2 SHO Monitoring and Troubleshooting
SHO Analysis & Troubleshooting (1/2)
SHO AnalysisRNC level
CEM & Iub Capacity AnalysisNode B level
RRM Capacity Analysis Cell level
RL SetupBlocking Rate
URL036_CR > Th
RL SetupUnsucces
s
[failure causes]
Top worst cells
High Iur Radio link failures(setup/addition)
All cells? Or set of cells
Inter RNC SHO analysis
Capacity analysis cell level
Check configuration for the set of cellsCorrelate with events that affect Iur:
i.e configuration changes like reparenting
Yes
No
-
Section 7 Pager 21
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 21
3 HHO 3G-2G Monitoring
-
Section 7 Pager 22
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 22
3 HHO 3G-2G Monitoring
3G-2G CS Handover Success - counters
UE Node B RNC CN
Handover from UTRAN Command
BSS
Relocation Command
RL Deletion ReqtRL Deletion Respe
Relocation Required
Physical information
Measurement Report
Handover Access
Handover CompleteIu Release Commandsuccessful 3G to 2G
relocation
Iu Release Complete
Decision for 3G->2G HHO
Released
.
#167[0]successful 3G to 2G outgoing HO
preparation
execution
Reference FDDCell Counters
#1841[0] successful 3G to 2G outgoing HO#505[1] successful 3G to 2G outgoing HO
#164[0] 3G to 2G HO detection#1839 Iu relocation attempt
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 #1: Service CS
Sub-Counter #2: No resource available CS (CAC failure)
-
Section 7 Pager 23
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 23
3 HHO 3G-2G Monitoring
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).
CS 3G-2G HHO Radio Success Rate (Rescue)
CS 3G-2G HHO Radio Success Rate (Rescue)
#167.[0]#164.[0]
=
UHO3G2G019_C_CsReference FDDCell metric
CS 3G-2G HHO Radio Success Rate (Rescue)
CS 3G-2G HHO Radio Success Rate (Rescue)
cellcellcellcell(#167.[0]) + NrncNrncNrncNrnc(#168.[0]) cellcellcellcell(#164.[0]) + NrncNrncNrncNrnc(#165.[0])
=
RNC metric UHO3G2G019_R_Cs
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 #0 : rescue CS
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 24
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 24
3 HHO 3G-2G Monitoring
3G-2G CS Handover Preparation Success - counters
UE Node B RNC CN
Handover from UTRAN Command
BSS
Relocation Command
Relocation RequiredMeasurement Report
.
#164[0] 3G to 2G HO detection#1839 Iu relocation attempt
#556[2] Iu relocation required
#557[2] Iu relocation command#154[0] #156[0]HO from UTRAN commandReference FDDCell counter
RNC counter
RNC counter
Reference FDDCell counter
#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:
Sub-Counter #0 : rescue CS
#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:
Sub-Counter #0 : rescue CS
#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.
Sub-Counter #0 : service CS Sub-Counter #1 : No resource available (CAC failure)
#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 25
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 25
3 HHO 3G-2G Monitoring
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.
-
Section 7 Pager 26
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 26
#???#???#558[6-9] #1845[0-11]Relocation preparation failure
#568[2] Relocation cancel#???
3 HHO 3G-2G Monitoring
3G-2G CS Handover Preparation Failure - counters
Relocation RequiredMeasurement Report
Relocation Cancel
TRELOCprepexpiry
No answer from CN to Relocation Required
Decision for HHO
Relocation Preparation Failure
Relocation RequiredMeasurement Report
Decision for HHOHandover failure on the 2G side
Handoverfailure
CN answers NACK to Relocation Required
UE Node B RNC CN BSS
EXERCISE: Find the two counters in the catalogue
1st case
2nd case #???
TRELOCprep = Timer RELOcation preparation
-
Section 7 Pager 27
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 27
3 HHO 3G-2G Monitoring
3G-2G CS HO Preparation Failure Rate
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
#558.[5-9]#556.[2]=
RNC metric UHO3G2G018_R_Cs
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
#164[all] (#154+#156+#158.[all])#164[all]=
FDDCell metric
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
3G-2G CS HO Preparation failure rate(Rescue+CAC failure+Service)
#1845.[all]#1839
=
FDDCell metric
#1843#1839
=
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
A set of subcounters screened on: Per type of core and type of relocation
Sub-Counter #2 : 3G-2G CS
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 28
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 28
3 HHO 3G-2G Monitoring
3G-2G CS Handover Execution Success - counters
UE Node B RNC CN
Handover from UTRAN Command
BSS
Relocation Command
#154[0] #159[0]HO from UTRAN command
RL Deletion ReqtRL Deletion Respe
Physical informationHandover Access
Handover CompleteIu Release Commandsuccessful 3G to 2G
relocation
Iu Release CompleteReleased
Reference FDDCell Counters
#167[x] , #168[x]successful 3G to 2G outgoing handovers
-
Section 7 Pager 29
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 29
3 HHO 3G-2G Monitoring
3G-2G CS HO Execution Success Rate
#167.[0,2,4]#154[0] + #156 [0] + #158 [0,1]
=
UHO3G2G020_C_CsReference FDDCell metric
CS 3G-2G HHO Execution Success Rate
cellcellcellcell(#167.[0,2,4]) + NrncNrncNrncNrnc(#168.[0,2]) #154 + #155 + #156 + #157 + #158 + #159
=
RNC metric
CS 3G-2G HHO Execution Success Rate
UHO3G2G020_R_Cs
-
Section 7 Pager 30
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 30
#576[5] HHO drop
3 HHO 3G-2G Monitoring
3G-2G CS Handover Execution Failure - counters
Handover from UTRAN Command Relocation Command
Handover failure on the target systemHandover from UTRAN Failure
Relocation Cancel
UE fails to connect to 2G and reverts to 3G
#160[x] ; #161[x]HO From UTRAN Failure
UE Node B RNC CN - CS BSS
1st case
HO Request Ack
2nd case
Handover from UTRAN Command Relocation Command
UE fails to connect to 2G and fails to reverts to 3G
HO Request Ack
TRelocOveral
Iu Release Request
HHO Drop
expiryReference
FDDCell Counters
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
Sub-Counter #0 : rescue CS
Sub-Counter #1 : service CS
Sub-Counter #2 : No resource available (CAC failure)
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
Sub-Counter #0 : rescue CS
Sub-Counter #1 : No resource available (CAC failure)
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 31
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 31
3 HHO 3G-2G Monitoring
3G-2G CS Handover: FDDCell Counter Tree (Rescue case)
Preparation failure#164[0] [#154+#156]
VS.3gto2gHoDetectionFromFddcell
VS.RrcHoFromUtranCommand
Request#164[0]
Execution failure[#154+#156] #167[0]
Success#167[0]
VS.RadioBearerSetupUnsuccess
HO from UTRAN Failure#160[0]
HHO drop[#154+#156]- #167[0] - #160[0]
Attempt[#154+#156]
-
Section 7 Pager 32
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 32
3 HHO 3G-2G Monitoring
3G-2G CS HO Execution Failure Rate (reversion to 3G)
CS 3G-2G HO Execution Failure Rate
CS 3G-2G HO Execution Failure Rate
cellcellcellcell(#160[0,1,2]) + NrncNrncNrncNrnc(#161[0,1])#154 + #155 + #156 + #157 + #158 + #159
=
RNC metric UHO3G2G002_R_Cs
CS 3G-2G HO Execution Failure RateCS 3G-2G HO Execution Failure Rate#160[0,1,2]
#154[0] + #156[0] + #158[0,1]=
Reference FDDCell metric UHO3G2G002_C_Cs
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 33
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 33
3 HHO 3G-2G Monitoring
3G-2G CS HO Execution Failure Rate (call drop)
= #154 + #156 + #158 - #160[all] - #505[1]
Reference FDDCell metric UHO3G2G024_C_Cs
=
3G-2G CS HO which leads either to a Success or to a Drop
Reference FDDCell metric UHO3G2G022_C_Cs
Number of CS 3G2G HHO drops
CS 3G2G HHO Execution Failure Rate because of 3G Reason #154 + #156 + #158 - #160[all]
#154 + #156 + #158 - #160[all] - #167[0,2,4]
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 34
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 34
4 HHO 3G-3G Monitoring
-
Section 7 Pager 35
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 35
4 HHO 3G-3G Monitoring
3G-3G HHO InterRNC no Iur Preparation Success - counters
UE Node B RNC 1 CN RNC 2
Relocation Command
Relocation Required
Measurement Report
#556[x]Iu relocation required
#557[x]Iu relocation command
#535[x]Iu relocation request
FDDCell counter
RNC counter Relocation Request
Relocation Request Ack
RNC counter
not counted
Source side
Outgoing HHO
Target side
Incoming HHO
#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
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 36
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 36
4 HHO 3G-3G Monitoring
3G-3G HHO InterRNC no Iur Preparation Failure - counters
UE Node B RNC 1 CN RNC 2
Relocation PreparationFailure
Relocation Required
Measurement Report
#558[x]Iu relocationpreparation failure
#536[x] for CS, #537[x] for PSIu relocation request failure
FDDCell counters
Relocation Request
Relocation Request Failure
RNC counter
Source side
Outgoing HHO
Target side
Incoming HHO
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
Sub-Counter #4: 3G-3G UE involved. RRC Context CAC. Pegged when CAC fails for then entering PS
reloc.
-
Section 7 Pager 37
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 37
4 HHO 3G-3G Monitoring
3G-3G HHO InterRNC no Iur - Preparation Success Rate
#557.[0,3]#556.[0,3]
=
RNC metricCS 3G-3G HHO Outgoing Preparation Success Rate
UHO3G3G007_R_Cs
#557.[1,4]#556.[1,4]
=
RNC metricPS 3G-3G HHO Outgoing Preparation Success Rate
UHO3G3G007_R_Ps
#535.[0,3] - #536.[0-3,8,10,12-15] #535.[0,3]
=
FDDCell metric
CS 3G-3G HHO Incoming Preparation Success Rate
UHO3G3G002_CR_Cs
#535.[1,4] - #537.[0-3,8,10,12-15] #535.[1,4]
=
FDDCell metricPS 3G-3G HHO Incoming Preparation Success Rate
UHO3G3G004_CR_Ps
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 38
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 38
4 HHO 3G-3G Monitoring
3G-3G HHO InterRNC no Iur Execution Success - counters
UE Node B RNC 1 CN RNC 2
Relocation Command
Relocation Required
Measurement Report
#569[x]Iu relocation complete
FDDCell & Neighboring RNC counters
Relocation Request
Relocation Request Ack
RNC counter
Radio Bearer Reconfiguration
Radio Bearer Reconfiguration CompleteRelocation Detect
Relocation CompleteIu Release Command
RL Deln Reqt
RL Deln Respe
#505[9] & #552[9] for CS#506[9] & #553[9] for PS Iu relocation command
Iu Release Complete
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 #0 : 3G-3G CS
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.
Sub-Counter #9: Successful 3G3G relocation
VS.IuReleaseCommandPs - #506
Number of RANAP/IU_RELEASE_COMMAND messages received by RNC from PS domain.
Sub-Counter #9: Successful 3G3G relocation
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.
Sub-Counter #9: Successful 3G3G relocation
-
Section 7 Pager 39
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 39
4 HHO 3G-3G Monitoring
3G-3G HHO InterRNC no Iur Execution Success Rate
CS 3G-3G HHO Incoming Execution Success Rate
CS 3G-3G HHO Incoming Execution Success Rate
#569.[0] cellcellcellcell(#0535.[0,3] - #536.[0-3,8,10,12-15])
=
RNC metric UHO3G3G003_R_Cs
PS 3G-3G HHO Incoming Execution Success Rate
PS 3G-3G HHO Incoming Execution Success Rate
# 569.[1] cellcellcellcell(#535.[1,4] - #537.[0-3,8,10,12-15])
=
RNC metric UHO3G3G005_R_Ps
CS 3G-3G HHO Outgoing Execution Success Rate
CS 3G-3G HHO Outgoing Execution Success Rate
cellcellcellcell(#505.[9]) + NrncNrncNrncNrnc(#552.[9])#557.[0,3]=
RNC metric UHO3G3G003_R_Cs
CS 3G-3G HHO Outgoing Execution Success Rate
CS 3G-3G HHO Outgoing Execution Success Rate =
RNC metric UHO3G3G009_R_Ps
cellcellcellcell(#506.[9]) + NrncNrncNrncNrnc(#553.[9])#557.[1,4]
-
Section 7 Pager 40
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 40
4 HHO 3G-3G Monitoring
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Success
Measurement Report
Decision for HHO
#174[x]Outgoing inter-freq
HHO attempt#176[x]Incoming inter-freq
HHO attemptRB Reconfiguration
UE SourceNode B
RNCTarget Node B
RL Setup RequestRL Setup Response
RB Reconfiguration complete
RL Deletion Request
RL Setup Deletion Response
Reference FDDCell CountersPS+CS
#175[x]Outgoing inter-freq
HHO success#177[x]Incoming inter-freq
HHO success
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 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.IncomInterFreqHoSuc - #177
Number of successful hard handovers to this cell located on the serving RNC 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
-
Section 7 Pager 41
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 41
4 HHO 3G-3G Monitoring
3G-3G Inter-freq HHO IntraRNC+InterRNC with Iur - Rate
3G3G Inter-freq HHO Outgoing Failure Rate
3G3G Inter-freq HHO Outgoing Failure Rate
# 175.[all] #174.[all]
Reference FDDCell metric
=
3G3G Intra-RNCHHO Incoming Failure Rate
3G3G Intra-RNCHHO Incoming Failure Rate
#177.[all] #176.[all]
Reference FDDCell metric
=
-
Section 7 Pager 42
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 42
4 HHO 3G-3G Monitoring
3G-3G Inter-frequency HHO - Intra-RNC Success - counters
Measurement Report
Decision for HHO
#170[x]Outgoing intraRNCinter-freq HHO attempt#172[x]Incoming intraRNCinter-freq HHO attempt
RB Reconfiguration
UE SourceNode B
RNCTarget Node B
RL Setup RequestRL Setup Response
RB Reconfiguration complete
RL Deletion Request
RL Setup Deletion ResponseReference
FDDCell Counters
PS+CS
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 43
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 43
4 HHO 3G-3G Monitoring
3G-3G Inter-frequency HHO - Intra-RNC Failure - counters
Measurement Report
#171[x]Outgoing intraRNCinter-freq HHO failure#173[x]Incoming intraRNCinter-freq HHO failure
RB Reconfiguration
UE SourceNode B
RNCTarget Node B
RL Setup RequestRL Setup Failure
RB Reconfiguration Failure
Reference FDDCell Counters
Measurement Report
UE SourceNode B
RNCTarget Node B
RL Setup RequestRL Setup Response
Decision for HHO
PS+CS
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 44
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 44
4 HHO 3G-3G Monitoring
3G-3G Inter-frequency HHO - Intra-RNC Failure Rate
3G3G Intra-RNC Inter-freq HHO Incoming Failure Rate
3G3G Intra-RNC Inter-freq HHO Incoming Failure Rate
# 173.[1-5] #172.[1]
Reference FDDCell metric UHO3G3G012_CR
=
3G3G Intra-RNC Inter-freq HHO Outgoing Failure Rate
3G3G Intra-RNC Inter-freq HHO Outgoing Failure Rate
#171.[1-5] #170.[1]
Reference FDDCell metric UHO3G3G011_CR
=
-
Section 7 Pager 45
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 45
5 HHO 3G-2G Analysis & Troubleshooting
-
Section 7 Pager 46
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 46
5 HHO 3G-2G Analysis & Troubleshooting
CS 3G-2G Mobility Analysis & Troubleshooting
CS 3G2G Mobility Analysis Network level
Counters
CS 3G2G Mobility Analysis RNC levelCounters
CS 3G2GPreparation Analysis Cell level
Counters
CS 3G2G Mobility Analysis RNC levelCounters
CS 3G2GPreparation Analysis Selected Cells
CTG Analysis
Preparation part Low rate execution part 2G side
CTG Analysis
CS 3G2G Mobility Analysis Network level
3G 2G CS HHO Success Rate < ThUHO3G2G019_R_Cs
3G-2G HHO CS executionsuccess rate
UHO3G2G020_R_Cs3G2G HHO CS preparation
failure rateUHO3G2G018_R_Cs
CS 3G2G Preparation Analysis RNC level
CS 3G2G Execution Analysis RNC level
Determine the RNC with High UHO3G2G018_R_Cs
Determine the RNC with Low UHO3G2G020_R_Cs
HO3G2G003 and HO3G2G004 to monitor the detection.
-
Section 7 Pager 47
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 47
5 HHO 3G-2G Analysis & Troubleshooting
3G-2G CS HHO Preparation Analysis & Troubleshooting
Preparation 3G2G CS HHO Analysis RNC level
3G2G HHO CS preparationfailure rate
UHO3G2G018_R_Cs
High CS 3G2G RejectionSuccess rate
due to Time out
Check Outage in Transmission NetworkBetween 3G CN and 2G network
Check the Outage in the 2G target network identified
High CS 3G2G RejectionSuccess rate
due to unable to establish
Check the Neighbouring cells definition
High CS 3G2G RejectionSuccess rate
due to Failure in Target System
To determine the rejection causes (Refer to 3GPP TS 25.413):
#0558 Iu relocation command failures CS
Preparation 3G2G HHO Failures TOP N Cells
Check the 2G NeighbouringCells capacity Analysis
High CS 3G2G RejectionSuccess rate
due to Other Reasons
Preparation 3G2G HHO FailuresTOP N Cells
To determine the worst N cells with a representative number of Preparation 3G2G HHO Failures:the highest number of #0109 -#0101VS.3gto2gHoDetectionFromFddcell -
VS.RrcHoFromUtranCommand
Preparation 3G2G HHO Failures TOP N Cells
Counter Sub-counters
558 VS.IuRelocationCmdFailuresCs.3Gto2GRelocTimeoutUeInv
558 VS.IuRelocationCmdFailuresCs.3Gto2GAlreadyInProgrUeInv
558 VS.IuRelocationCmdFailuresCs.3Gto2GFailTargetUeInv
558 VS.IuRelocationCmdFailuresCs.3Gto2GUnableToEstabUeInv
558 VS.IuRelocationCmdFailuresCs.3Gto2GOtherUeInv
Counter Sub-counters
1845 IRATHO.FailRelocPrepOutCS.TRELOCprep_exp
1845 IRATHO.FailRelocPrepOutCS.TrLdHighTarCell
1845 IRATHO.FailRelocPrepOutCS.FailTarSys
1845 IRATHO.FailRelocPrepOutCS.NoResAvr
1845 IRATHO.FailRelocPrepOutCS.NoRRTarCell
-
Section 7 Pager 48
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 48
To determine the worst N cells with a
representative number of HO From
UTRAN Failures:the highest number
of CS HO From UTRAN Failure
5 HHO 3G-2G Analysis & Troubleshooting
3G-2G CS HHO Execution Analysis & Troubleshooting
3G2G CS HHO Execution Analysis RNC level
Low HHO 3G2G CS executionsuccess rate
UHO3G2G020_R_Cs
3G-2G HHO CS execution failure rate (reversion to 3G)UHO3G2G002_R_Cs
Target 2G neighboring cells RF condition analysis
Check the setting of 3G2G CS HHO
Algorithm Parameters
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
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 (call drop)UHO3G2G022_R_Cs
The 1st step is to identify the days and the RNCs with too bad Global CS 3G2G HHO performancesThis 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 49
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 49
5 HHO 3G-2G Analysis & Troubleshooting
Summary
Could you list the main causes for HHO preparation/execution
failures ?
What actions could improve HHO preparation/execution
performances ?
-
Section 7 Pager 50
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 50
5 HHO 3G-2G Analysis & Troubleshooting
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
-
Section 7 Pager 51
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 51
5 HHO 3G-2G Analysis & Troubleshooting
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
-
Section 7 Pager 52
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 52
Self-Assessment on the Objectives
Please be reminded to fill in the formSelf-Assessment on the Objectivesfor this module
The form can be found in the first partof this course documentation
-
Section 7 Pager 53
All Rights Reserved Alcatel-Lucent @@YEAR
3JK10061AAAAWBZZA Edition 1.1
All Rights Reserved Alcatel-Lucent @@YEAR
9300 WCDMA UA06 R99 QoS Analysis and Traffic Load MonitoringMobility Monitoring
7 53
End of ModuleModule 1