ALU - UMTS QoS and Performance Monitoring

QoS & Performance Monitoring
Performance Monitoring Metrics
Mohamed Arshad MoAD RNE SSEAI

Kuala Lumpur November 2008
All Rights Reserved Alcatel-Lucent 2008
UTRAN Performance Monitoring
Performance Monitoring Process Dashboard Metrics 1. Accessibility 2. Retainability 3. Mobility 4. Congestion / Load 5. Quality 6. Traffic
2 | Performance Monitoring Overview | Nov 2008
UTRAN Performance Monitoring: how? Process
Set up the goals
Collect the observation data Analyze the collected data
Take the necessary actions Validate the actions taken
UTRAN Performance Monitoring Process

Counters Metrics Reports Hourly / Busy Hour, Daily, Weekly Alarm detection NEs (RNC, FddCell, SGSN, )
Monitoring Setup
Data Retrieve Definition
Engineering
Criteria Definition
Tools (PrOptima, scripts,)
Monitoring Process
Observation
O&M
!
Analysis
O&M
Correction
O&M
Validation
Dashboard Metrics
UTRAN Performance Monitoring Metrics Families
Following a summary of the families to be presented: Accessibility Retainability Mobility Congestion/load Quality Traffic
Accessibility
Network Accessibility Performance The objective of the Accessibility metrics is to evaluate the failure cases during all the steps allowing the user to access a particular service The first phase of a call establishment (speech or data) is the RRC connection. One RRC connection can lead to :
Several Iu SCCP connections ( multi service CS+PS, simultaneous CS + PS attach/detach, CS location update during a PS call), No RAB in case of signalling connections, 1 (or several RB sets) in case of one call (multi service).
The 3 main steps identified during the call establishment for the Performance Monitoring Activity are the following ones:
RRC Connection phase SCCP Connection phase RAB Assignment phase RRC Connection success rate Iu SCCP success rate RAB assignment success rate per requested RAB type
Call Establishment Flow

UE Node B
(Cell-DCH case)
RNC
CN
RRC Connection Request Radio Link Setup Request Radio Link Setup Response RRC Connection Setup RRC Connection Complete Measurement Control Init Direct Transfer SCCP Connection Request (Initial UE Message) SCCP Connection Confirm Authentication Procedure Ciphering Procedure RAB Assignment Request S.R.L.R. Procedure Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response
RRC Connection Phase
SCCP Connection Phase
RAB establishment Phase
RRC Connection Phase
Accessibility RRC Connection Is the logical connection between UE and UTRAN. It carries control plane information between UE and UTRAN. Each UE can have only one RRC connection at any time with the UTRAN.
UE
Node B
RNC
Circuit Domain
Physical channel
AAL2 bearer
SIG/AAL5
Core Network
Packet Domain
RRC (logical channel)
Call establishment flow RRC Connection
(Cell-DCH case)
RRC Connection Phase & Associated Counters

UE Node B RRC Connection Request Radio Link Setup Request Radio Link Setup Response RRC Connection Setup RRC Connection Complete #0403 RRC Connection Success #0404 RRC Connection Failure/reject RNC #0409 RRC Connection Request #0419 First RRC Connection Request
Counter Replaced in UA5.0 Screenings updated in UA5.0 No change
ID #0403 #0404 #0409 #0419
Definition RRC.SuccConnEstab: Number of RRC connections successfully established. RRC.FailConnEstab: Number of RRC connection establishment failures. RRC.AttConnEstab: Number of RRC connection request received. VS.FirstRrcConnectionRequest: Number of RRC Connection Request received by the RNC, without consider the ones that have been repeated by the mobile (if the mobile has not received RRC Connection Setup within T300) in the same cell.
Type CUM CUM CUM CUM
Location FddCell FddCell FddCell FddCell
Screening Establishment Cause Failure Cause Establishment Cause Establishment Cause
UA5.0: No update
RRC Connection success rate

RRC connection success rate (system view)
Success rate of the first step of accessibility. Computed at Cell and RNC Level Takes into account the RRC establishment repetitions that can be transparent for the user
RRC Connection success [ RRC screenings] RRC Connection requests [ RRC screenings] RRC connection success rate (users perception)
#0403.[RRC screenings] #0409. [RRC screenings]
Success rate of the first step of accessibility. Computed at Cell and RNC Level Does not take into account the RRC repetitions representative of the users perception
RRC Connection success [ RRC screenings] First RRC Connection requests [ RRC screenings]
These metrics can be computed per RRC establishment cause : Calls only CS calls, PS calls Registration,
#0403. [RRC screenings] #0419. [RRC screenings]
Not impacted by HSDPA
UA5.0: No update
RRC Connection success rate for calls only System view

Screening from 0 to 9: Originating / Terminating Traffic Classes and Emergency call Screening 14, Originating High Priority Signalling: 3GPP: used for Supplementary Services in CS, and to Modify/Deactivate a PDP Context in PS Screening 16, Call re-establishment: 3GPP: used for CS Call re-establishment, or Routing Area Update for the case of Directed Signalling Connection ReEstablishment Comment: it may be also used to re-establish PS call after an Always-On Step 2 downsize Screening 19, Terminating cause unknown: 3GPP: used by the UE whenever it responds to a paging message in which the paging cause has not been set (the "paging cause" IE is an optional field of the paging message)
Screening 0 1 2 3 4 5 6 7 8 9 10 11 12 Cause Originating Conversational call Originating Streaming call Originating Interactive call Originating Background call Originating Subscribed Traffic call Terminating Conversational call Terminating Streaming call Terminating Interactive call Terminating Background call Emergency call Inter-RAT cell re-selection Inter-RAT cell change order Registration Detach Originating High Priority Signaling Originating Low Priority Signaling Call re-establishment Terminating High Priority Signaling Terminating Low Priority Signaling Terminating cause unknown CS / PS CS / PS PS PS RAB Domain CS CS / PS PS PS PS CS CS / PS PS PS CS
CS RRC Connection success rate PS RRC Connection success rate
= =
#0403.[0, 5, 9] #0409.[0, 5, 9] #0403.[1-4, 6-8, 14, 16, 17,19] #0409.[1-4, 6-8, 14, 16, 17,19]
13 14 15 16 17 18 19
SCCP Connection Phase
Call establishment flow

Iu SCCP Connection
(Cell-DCH case)
SCCP Phase & Associated Counters

UE Node B Measurement Control Init Direct Transfer SCCP Connection Request (Initial UE Message) SCCP Connection Confirm Authentication Procedure Ciphering Procedure RNC CN
#0548 SCCP Connection Success #0502 SCCP Connection Unsuccess
ID #0502 #0548
Definition VS.IuSccpCnxUnsuccess: Number of unsuccessful SCCP connections at Iu interface VS.IuSccpCnxSuccess: Number of successful SCCP connections at Iu interface
Type CUM CUM
Location RNC RNC
Screening Core Domain + Originator CsReqByRNC PsReqByRNC CsReqByCN PsReqByCN
UA5.0: No update
Iu SCCP success rate

Separation of CS & PS domains results CS and Iu-PS to facilitate the troubleshooting based on the two interfaces: Iu-
The Iu SCCP success rate metric considers also signalling and can only be monitored at RNC level
Iu SCCP success Iu SCCP Cnx Success + Iu SCCP Cnx unsuccess

Iu SCCP
2500000
100.00%
2000000
99.98% A ttempts CS
1500000
99.96%
A ttempts PS Iu SCCP Success Ratio Success Ratio CS
1000000
99.94%
Success Ratio PS
500000
99.92%
0 01-A pr-06
99.90% 08-A pr-06 15-A pr-06 22-A pr-06
UA5.0: No update

0 Unsuccess on Iu-cs connection requested by Rnc. (ie: refusal from Core Network CS or SCCP layer or the Control Node (RNC) ) Unsuccess on Iu-cs connection requested by Core Network CS (ie: refusal from Rnc) Unsuccess on Iu-ps connection requested by Rnc. (ie: refusal from Core Network PS or SCCP layer or the Control Node (RNC)) Unsuccess on Iu-ps connection requested by Core Network PS (ie: refusal from Rnc).
Iu-SCCP Connection unsuccess screenings: #0502
1 2 3
With CS core network (connection requested by the RNC) With PS core network (connection requested by the RNC) With CS core network (connection requested by the core network) With PS core network (connection requested by the core network)
Iu-SCCP Connection success screenings: #0548
1 2 3
CS Iu SCCP success rate
#0548.[0,2] #0548.[0,2]+#0502.[0,1]
PS Iu SCCP success rate
#0548.[1,3] #0548.[1,3]+#0502.[2,3]
RAB Establishment Phase

(Cell-DCH case)
RAB Establishment Phase & Associated Counters

UE Node B #0671 RAB Establishment Request RNC RAB Assignment Request CN
S.R.L.R. Procedure Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response #0677 RAB Assignment Setup Unsuccess #0672 RAB Establishment Success Per Requested RAB Type #0673 RAB Establishment Success Per Granted RAB Type
ID #671 #672
Definition VS.RabEstablishmentRequestsPerRabType: Number of RAB establishment attempts. Screening selected according to request from CN VS.RabEstablishmentSuccessPerRequestedRabType: Number of successful RAB establishment, screened per requested RAB type. Screening selected according to request from CN VS.RabEstablishmentSuccessPerGrantedRabType: Number of successful RAB establishment, screened per granted RAB type. Screening selected according to combination granted by RNC VS.RabAssignmentSetupUnsuccess: Number of RAB that could not be established by the RNC.
Type CUM CUM
Location RNC RNC
Screening RAB Type RAB Type
#673 #677
CUM CUM
RNC RNC
RAB Type RAB Type
UA5.0 update: counters replaced
RAB Establishment success rate per requested RAB The allocated RAB is not necessary the one requested by the CN. The metric provides a view of the RAB assigned as seen by the CN
RAB Establishment success rate
RAB Establishment success RAB Establishment request
#0672. [RAB Type] #0671. [RAB Type]
Separation of CS domain services and PS domain services troubleshooting based on the user behaviour. The metric can also be computed per RAB type at RNC level.
to facilitate the
It can not be computed for HSDPA as HSDPA RAB is not requested by the Core Network.
#671, #672 and #677 are never pegged for the screenings with HSDPA
For HSDPA we will use RB setup success rate instead, or the volume of RAB granted
HSDPA RAB assignment success per granted HSDPA RAB = #0673[10 - 16]
RAB Establishment success rate per requested RAB

CS RAB Establishment Success Rate
100000 90000 80000 70000 60000 50000 40000 30000 20000 10000 0 15/03/2006 100.00% 99.00% 98.00% 97.00% 96.00% 95.00% 94.00% 93.00% 92.00% 91.00% 90.00% 12/04/2006 CS V ideo
Voice RAB Establishment success rate
= =
#0672.[1] #0671.[1]
22/03/2006 Requests CS V oice
29/03/2006 Requests CS V ideo
05/04/2006 CS V oice
Video RAB Establishment success rate
#0672.[2] #0671.[2]
PS RAB Establishment Success Rate

60000 50000 40000 30000 20000 10000 0 15/03/2006 100.00% 95.00% 90.00% 85.00% 80.00% 75.00% 70.00% 65.00% 60.00% 12/04/2006
PS RAB Establishment success rate
#0672.[0,5-9] #0671.[0,5-9]
22/03/2006
29/03/2006 Requests PS
05/04/2006
Success Rate PS

(Cell-DCH case)
RB Setup & Associated Counters

UE Node B RNC RAB Assignment Request CN
#0671 RAB Establishment Request S.R.L.R. Procedure Radio Bearer Setup Radio Bearer Setup Complete
#0691 RB Setup Request #0631 RB Establishment unsuccess
Internal RRM decision to assign resources
#0677 RAB Assignment Setup Unsuccess #0672 RAB Establishment Success Per Requested RAB Type
RAB Assignment Response #0687 RB Setup Success # 602 RB Setup Unsuccess
#0673 RAB Establishment Success Per Granted RAB Type
ID #0687 #0602 #0691 #0631
Definition VS.RadioBearerSetupSuccess: Number of Radio Bearers successfully setup. VS.RadioBearerSetupUnsuccess: Number of Radio Bearers not successfully setup. VS.RadioBearerSetupRequest: Number of Radio bearer setup decisions by the RNC (leading or not to a RB SETUP, ie. even if Call Admission Control rejects the setup) VS.RadioBearerEstablishmentUnsuccess: Number of Radio-Bearer establishments that have been rejected by the RNC (no RB Setup Request sent).
Location Reference FddCell Reference FddCell Reference Fddcell Reference Fddcell
Screening TargetCall Type Failure cause TargetCall Type Failure cause
Radio Bearer To be Setup success ratio This metric is the counterpart of RAB assignment success rate but at Cell level This metric can be computed at RNC level but will not include the RB setup on the neighbouring cells
RB To be Setup success ratio
RB Setup Success RB Setup Request
#0687.[TargetCall Type] #0691.[TargetCall Type]
Pure Voice RB to be Setup success rate success rate = (#0687.[1]) / (#0691.[1]) Pure Video RB to be Setup success rate success rate = (#0687.[2]) / (#0691.[2]) Pure PS RB to be Setup success rate success rate = (#0687.[0,4-14]) (#0691.[0,4-14]) Combined RB Setup success rate = (#0687.[0-14]) / (#0691.[0-14] HSDPA RB setup success rate = #0687.[14] / #0691.[14]
Call setup success rate at RNC Level
UA5.0 update: RAB counters replaced
Call setup success rate at RNC Level Indicator of the rate of successful call establishment vs call establishment attempts. The main phases considered in this metric are: RRC connection phase Iu SCCP phase RAB Assignment phase It is proposed to not take into account the Security Mode Command phase since it has been observed that it is more impacting the Signalling than User Traffic
Call Setup success rate
RRC Connection success rate
SCCP Connection Success rate
RAB Establishment success rate
First RRC success rate (calls only) Impacted by HSDPA for the RAB phase (seen with RB Setup)
users perception
Call setup success rate at RNC Level Separation of CS domain results and PS domain results troubleshooting based on user behaviour
CSSR
100.00% 95.00% 90.00% 85.00% 80.00% 75.00% 70.00% 65.00% 25-A pr-06
to facilitate the
02-May-06
09-May-06 CS V oice & Data PS Calls
16-May-06
23-May-06
CS Call Setup Success Rate = (CS RRC Connection success rate)*(CS SCCP Connection Success rate)*(CS RAB Assignment success rate) PS Call Setup Success Rate = (PS RRC Connection success rate)*(PS SCCP
Connection Success rate)*(PS RAB Assignment success rate) All Rights Reserved Alcatel-Lucent 2008
Call setup success rate Separation of Voice, Video and PS domain results troubleshooting based on user behaviour
Iu SCCP Phase is not considered in the dashboard RNC Level RAB
to facilitate the
Voice Call Setup Success Rate = (CS RRC Connection success rate)*(Voice RAB Assignment success rate) Video Call Setup Success Rate = (CS RRC Connection success rate)*(Video RAB Assignment success rate) PS Call Setup Success Rate = (PS RRC Connection success rate)*(PS RAB Assignment success rate)
Cluster and Cell Level
RB
Voice Call Setup Success Rate = (CS RRC Connection success rate)*(Voice RB Setup success rate) Video Call Setup Success Rate = (CS RRC Connection success rate)*(Video RB Setup success rate) PS Call Setup Success Rate = (PS RRC Connection success rate)*(PS RB Setup success rate)
2
Retainability Metrics
Network Retainability Performance The objective of the Retainability metrics is to evaluate the ability of the network to provide reliable service to the end user If and only if a call is dropped, the RNC sends the RANAP Iu Release Request message with the field abnormal reasons. Three approaches are described : Drop rate per RAB established
RNC level Cell level
Drops rate per normally released calls Drops per minute of RAB
Call Abnormal Release Flow & Associated Counters
Counter Replaced in UA5.0 Counter Removed in UA5.0 Screenings updated in UA5.0 No change
#0677 RAB Assignment setup unsuccess Node B RNC RAB Assignment Response CN #0672 RAB Establishment Success Per Requested RAB type #0673 RAB Establishment Success Per Granted RAB type
Issue detected
Iu Release Request Iu Release Command
#0576 Iu release request CS (cell) #0577 Iu release request PS (cell) #0572 Iu abnormal release request CS (cell)
Radio Link Deletion Request
#0573 Iu abnormal release request PS (cell) #0505 Iu release command CS
Radio Link Deletion Response
#0506 Iu release command PS

Iu Release Complete
#0571 Iu release complete CS
ID #0572 #0673 #0573
Definition VS.IuAbnormRelReqCs : Number of Iu CS release requests due to abnormal conditions. VS.RabEstablishmentSuccessPerGrantedRabType: Number of successful RAB establishment, screened per granted RAB type VS.IuAbnormRelReqPs : Number of Iu PS release requests due to abnormal conditions.
Type CUM CUM CUM
Location Reference Fddcell RNC Reference Fddcell
Screening TargetCall Type RAB type TargetCall Type
Call Drop Rate per RAB established RNC level Number of Iu abnormal release request versus the number of those specified RAB granted. This metric can also be computed for CS and PS but can not be splitted per RB, the results would be impacted by reconfigurations due to RB rate adaptation, IRM Scheduling, Call drop Rate
Number of drops Number of RAB success per granted RAB type
CS Call drop Rate
#0572.[CS TargetCall Type] #0673.[1-4]
Call Drop Rate per RAB established RNC level

For CS domain: separation of voice and video results to easily identify the CS service the most impacted For PS domain: the PS Retainability results are dependant on the number of PS RAB and so the results could be impacted by changing the Always-On Parameters
Call Drop Rate
3.00% 2.50% 2.00% 1.50% 400 1.00% 0.50% 0.00% 27-A pr-06 01-May-06 05-May-06 09-May-06 13-May-06 17-May-06 21-May-06 V oice Iu Rel. Reques t V ideo Iu Rel. Request V oice CDR 300 200 100 0 900 800 700 600 500
Call Drop Rate

4.00% 3.50% 3.00% 2.50% 2.00% 1.50% 1.00% 0.50% 0.00% 27-A pr-06 01-May-06 05-May-06 09-May-06 13-May-06 17-May-06 21-May-06 PS Iu Rel. Request PS CDR 1800 1600 1400 1200 1000 800 600 400 200 0
V oice CDR
CS CDR = (#0572.[0, 2-6])/#0673.[1- 4]) Voice CDR = (#0572.[2])/#0673.[1]) Video CDR = (#0572.[3])/#0673.[2]) PS RAB Drop Rate = #0573.[1-13])/(#0673.[0,5-16])
HSDPA Call drop rate = (#0573[12] / (#0673 .[10-16]) All Rights Reserved Alcatel-Lucent 2008
Call Abnormal Release Flow & Associated Counters

Node B RNC CN
Counter Replaced in UA5.0 Counter Removed in UA5.0 Screenings updated in UA5.0 No change
#1163 Downsizing Step 2 Success
Issue detected or User Inactivity

Iu Release Request Iu Release Command Radio Link Deletion Request Radio Link Deletion Response
#0572 Iu abnormal release request CS (cell) #0573 Iu abnormal release request PS (cell)
#0505 Iu release command CS #0506 Iu release command PS #0571 Iu release complete CS

Iu Release Complete
ID #0688 #1163 #0571 #0572 #0573
Definition VS.RadioBearerReleaseSuccess: Number of Radio Bearers successfully released. VS.DownsizingStep2Success: Number of successful always on downsizing step2. VS.IuReleaseCompleteCs: number of RANAP Iu Release Complete sent by RNC to CN on the Iu interface on CS domain. VS.IuAbnormalReleaseRequestCs: Number of Iu CS release requests due to abnormal conditions. VS.IuAbnormalReleaseRequestPs: Number of Iu PS release requests due to abnormal All Rights Reserved Alcatel-Lucent 2008 conditions.
Type CUM CUM CUM CUM CUM
Location Reference FddCell Reference FddCell Reference Fddcell Reference Fddcell Reference Fddcell
Screening TargetCall Type TargetCall Type TargetCall Type TargetCall Type TargetCall Type
Call Drop Rate per Released Calls Cell level Number of Iu abnormal release request versus the number of call released (either normally or abnormally). This metric can also be screened per CS, but for PS it must be computed globally, it can not be splitted per RB the results would be impacted by reconfigurations due to RB rate adaptation, IRM Scheduling . CS Call drop Rate at cell level
= =
Iu abnormal release requests CS Iu release complete CS

#0572.[CS TargetCall Type] #0571.[CS TargetCall Type]
CS Call drop Rate
Impacted by HSDPA
35 | Performance Monitoring Overview | Nov 2008 All Rights Reserved Alcatel-Lucent 2008
Included in PS metric
Call Drop Rate per Released Calls Cell level
Signalling Call drop Rate at cell level
(VS.IuAbnormalReleaseRequestCs [SRB TargetCallType + PS pure TargetCallType] + (VS.IuAbnormalReleaseRequestPs [SRB TargetCallType + CS pure TargetCallType]) ( VS.Iu release completeCs + VS.Iu release completePs)
PS Call drop Rate at cell level
Iu abnormal release requests PS Iu abnormal release requests PS + Downsizing Step 2 + Radio Bearer release success ( PS + FACH) #0573 ( PS TargetCallType)
PS Call drop Rate at cell level
#0573 (PS TargetCallType) + #1163 (PS TargetCallType) + #0688 (PS + FACH TargetCallType)
Impacted by HSDPA
Included in PS metric
Number of drops per minute of RAB RNC level

This metric can be screened per TargetCallType for CS, for PS it must be computed globally The metric allows to count the number of drops versus the duration of the RAB. It is based on :
ID #0692 #0572 #0573 Definition VS.DlAsConfIdAvgNbrEstablished: Indicates an average of the number of DlAsConfIds established per iRNC, based on time average over collection period. VS.IuAbnormalReleaseRequestCs/Ps: Number of Iu Cs/Ps release requests due to abnormal conditions. Type Load CUM Location Reference Fddcell Reference Fddcell Screening TargetCall Type TargetCall Type
Number of drops per min of RAB CS / PS
Iu abnormal release requests CS / PS Allocation time of the RAB
60*10* ( VS.IuAbnormalReleaseRequestCs/Ps [CS / PS TargetCallType]) VS.DlAsConfIdAvgNbrEstablished.CUM [CS / PS TargetCallType] Number of drops per min of HSDPA Call = 60*10*#0573[12] / #0692.Cum [14]
Mobility Metrics
UTRAN Performance Monitoring Mobility Metrics
Following a summary of the mobility metrics that will be considered: 3G-2G CS HHO 3G-2G PS HHO 3G-3G HHO 3G-3G SHO Mean Sector Per User
Network Mobility Performance The objective of the Mobility metrics is to evaluate the ability of the network to ensure UEs calls continuity The UE is ensuring the continuity of the call inside 3G network mainly based on macro diversity When there is lack of 3G coverage, the 2G network should be able to ensure the continuity with the Hard Handover from 3G to 2G procedure
3G-2G CS Handover
3G-2G CS Handover Successful case

UE Node B Measurement Report Relocation Required Decision for HHO Relocation Command Handover from UTRAN Command Handover Access Physical information Handover Complete Iu Release Command Radio Link Deletion Request Radio Link Deletion Response Iu Release Complete Released . RNC CN - CS BSS
3G2G CS HHO Preparation Phase
3G2G CS HHO Execution Phase
3G-2G CS Handover (Successful case) 3G2G CS HHO preparation success rate

UE Node B Measurement Report RNC
CN - CS #0164 3g to 2g ho detection from fddcell Relocation Required
BSS
Decision for HHO Relocation Command Handover from UTRAN Command #0154 HO from UTRAN command Handover Access Physical information Handover Complete Iu Release Command Radio Link Deletion Request Radio Link Deletion Response #0505 Iu Release Command Iu Release Complete Released #0557 Iu relocation command . #0556 Iu relocation required
ID #0556
Definition VS.IuRelocationRequired: Number of relocation required at Iu interface.
Type CUM
Location RNC
Screening 3Gto3GCs 3Gto3GPs 3Gto2GCs 3Gto3GCs 3Gto3GPs 3Gto2GCs
#0557
VS.IuRelocationCommands: Number of relocation commands at Iu interface.
CUM
RNC
3G2G CS HHO preparation success rate Metric to monitor during the 3G to 2G CS HHO, the preparation phase on the target side in order to evaluate the : failures from the target network when allocating the resources for the mobile (Relocation Preparation Failure) failures from 2G due to wrong neighbouring definition of 2G in 3G and opposite This metric can be only used at RNC level New : distinction between 3G3G and 3G2G is possible for this metric 3G2G CS HHO preparation success rate
Iu Relocation Command in CS domain Number of Iu Relocation Required in CS domain #0557.[2] #0556.[2]
3G2G CS HHO preparation success rate
Rate of 3G2G CS HHO detection leading to a HHO

For a deep investigation and troubleshooting the metric must be computed at Cell Level At Cell Level, when the Reference Cell belongs to the Serving iRNC, it allows to assess: the failures from the target network when allocating the resources for the mobile (Relocation Preparation Failure) failures from 2G due to wrong neighbouring definition of 2G in 3G and opposite call dropped after Relocation Required and before HO from UTRAN Command To cover also the cases when the Reference Cell belongs to a Drift iRNC, the metric must be computed at RNC Level
3G-2G CS Handover (Successful case) Rate of 3G2G CS HHO detection leading to a HHO
UE
Node B
Measurement Report
RNC
CN - CS #0164 3g to 2g ho detection from fddcell
BSS
#0165 3g to 2g ho detection from fddcell on Neighb Rnc

Relocation Required
Decision for HHO

Relocation Command Handover from UTRAN Command .
#0556 Iu relocation required

Handover Access Physical information Handover Complete
#0154 HO from UTRAN command #0155 HO from UTRAN command on Neighb Rnc
#0557 Iu relocation command
ID #0154 #0156 #0155 #0157 #0164 #0165
Definition VS.RrcHoFromUtranCommand / VS.RrcHoFromUtranCommandNeighbRnc : Number of Inter Rat handover from utran command sent by RNC with a reference cell for which the iRNC is serving / Drift. This is in the scope of 3G to 2G handover, CS only.
Type CUM
Location Reference FddCell Neighboring RNC
Screening HO cause
VS.3gto2gHoDetectionFromFddcell / VS.3gto2gHoDetectionFromFddcellNeighbRnc : Number of HO detection taken from fddcell at RRM level in RNC with a reference cell for which the iRNC is serving / Drift. This is in the scope of HO 3G to 2G initiation, for CS and PS.
CUM
Reference FddCell Neighboring RNC
HO cause
Rate of 3G2G CS HHO detection leading to a HHO

ID #0154 #0156 #0155 #0157 #0164 #0165 Counters VS.RrcHoFromUtranCmdTrigByEcNo VS.RrcHoFromUtranCmdTrigByRscp 1 VS.RrcHoFromUtranCmdTrigByEcNoNRnc 2 VS.RrcHoFromUtranCmdTrigByRscpNRnc 3 VS.3gto2gHoDetectionFromFddcell VS.3gto2gHoDetectionFromFddcellNeighbRnc No Resource Available (CAC Failure) Service Rescue PS Screening 0 Ho Cause Rescue CS
At Cell Level
Success Rate Cell Level
#0154.[0] + #0156.[0] #0164.[0]
At RNC Level
Success Rate RNC Level
#0154.[0] + #0156.[0] + #0155.[0] + #0157.[0] #0164.[0] + #0165.[0]
3G-2G CS Handover Failure on target system

UE Node B
Measurement Report Relocation Required Relocation Command Handover from UTRAN Command Handover failure on the target system Handover from UTRAN Failure Relocation Cancel
RNC
CN - CS
BSS
#0154 HO from UTRAN command #0155 HO from UTRAN command on Neighb Rnc
#0160 HO From UTRAN Failure #0161 HO From UTRAN Failure on Neighb Rnc
ID #0154 #0156 #0155 #0157 #0160 #0161
Definition VS.RrcHoFromUtranCommand / VS.RrcHoFromUtranCommandNeighbRnc : Number of Inter Rat handover from utran command sent by RNC with a reference cell for which the iRNC is serving / Drift. This is in the scope of 3G to 2G handover, CS only.
Type CUM
Screening Rescue CS
VS.RrcHoFromUtranFailure / VS.RrcHoFromUtranFailureNeighbRnc: Number of Inter Rat Handover from Utran failure received by RNC with a reference cell for which the iRNC is serving / Drift. This is in the scope of 3G to 2G handover, CS only.
CUM
Reference FddCell Neighboring RNC
Rescue CS Service CS CAC Failure
3G2G HHO CS execution failure rate 2G side

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 (2G side) metric is proposed to evaluate the 2G target cell synchronization failure. In case of high CS 3G2G HHO execution failure rate (2G side) performance 2G Network have to be detected Issues on the target
Failure Rate RNC Level Failure Rate Cell Level
= =
#0160.[0] + #0161.[0] #0154.[0] + #0156.[0] + #0155.[0] + #0157.[0] #0160.[0] #0154.[0] + #0156.[0]
If the RNC does not receive : the HO from UTRAN Failure RRC message from the UE neither the Iu release command with the cause successful 3g2g relocation from the CN, It means that occurred a failure at 3G side and the call is dropped during the 3G2G HHO execution This metric is at Cell Level
ID #0154 #0156 Definition VS.RrcHoFromUtranCommand: Number of Inter Rat handover from utran command sent by RNC with a reference cell for which the iRNC is serving. This is in the scope of 3G to 2G handover, CS only. #0160 VS.RrcHoFromUtranFailure: Number of Inter Rat Handover from Utran failure received by RNC with a reference cell for which the iRNC is serving. This is in the scope of 3G to 2G handover, CS only. VS.3gto2gOutHoSuccess: This measurement provides the number of successful 3G to 2G outgoing Handovers. CUM Reference FddCell 0: Rescue CS 1: Service CS 2: CAC Failure CUM Reference FddCell Rescue Cs / PS Service Cs / PS CAC Failure CS / PS Type CUM Location Reference FddCell Screening Rescue CS
#0167
This metric is the Rate of execution 3G2G handover failure due to call lost, and is computed at Cell Level
CS 3G2G HHO Execution failure rate (3G side) 3g to 2g Out Ho Success HO From UTRAN Command - HO From UTRAN failure
= 1=
1-
CS 3G2G HHO Execution failure rate (3G side)
#0167.[0] #0154.[0] + #0156 .[0] - #0160.[0]
Number of CS calls lost during 3G2G HHO
#0154.[0] + #0156 .[0] - #0160.[0] - #0167.[0]
3G2G Global CS HHO success rate

It evaluates success rate of the overall 3G2G CS HHO procedure (preparation + execution) by considering all the cases of failures (3G or 2G failures), and is computed at Cell Level If very low 3G2G Global CS HHO success rate , then identify in which steps, preparation, or execution, based on the previous metrics to determine the failure causes
Global HHO 3G2G CS success rate Global HHO 3G2G CS success rate
ID #0164 Definition
= =
3g to 2g Out Ho Success 3G2G HHO Detections #0167.[0] #0164.[0]

Type CUM Location Reference FddCell Screening HO cause
VS.3gto2gHoDetectionFromFddcell: Number of HO detection taken from fddcell at RRM level in RNC with a reference cell for which the iRNC is serving. This is in the scope of HO 3G to 2G initiation, for CS and PS. VS.3gto2gOutHoSuccess: This measurement provides the number of successfull 3G to 2G outgoing Handovers.
#0167
CUM
Reference FDDCell
Rescue Cs / PS Service Cs / PS CAC Failure CS / PS
3G-2G PS Handover
3G-2G PS Handover Successful case
UE
Node B Measurement Report
RNC Decision for HHO
3G SGSN
2G SGSN
Cell Change Order from UTRAN
#0164 3g to 2g ho detection from fddcell PS RA update request
#0162 Cell Change Order from UTRAN RA update response
SRNS Data Forward Command #0506 Iu Release Command PS Radio Link Deletion Request Radio Link Deletion Response Iu Release Complete Iu Release Command
3G-2G PS Handover Failure case

UE Node B RNC
#0164 3g to 2g ho detection from fddcell Measurement Report Decision for HHO #0162 Cell Change Order from UTRAN #0106 Cell Change Order from UTRAN Neigh RNC Cell Change Order from UTRAN #0163 Cell Change Order from UTRAN Failure #0108 Cell Change Order from UTRAN Failure N-RNC
Cell Change Order from UTRAN Failure
ID #0162
Definition IRATHO.AttOutPSUTRAN: Number of Inter Rat Cell Change Order from Utran sent by RNC with a reference cell for which the iRNC is serving. This is in the scope of 3G to 2G handover, PS only. VS.RrcCellChangeOrderNeighbRnc: Number of Inter Rat Cell Change Order form Utran sent by RNC with a reference cell for which the iRNC is drift. This is in the scope of 3G to 2G handover, PS only. IRATHO.FailOutPSUTRAN: Number of Inter Rat Cell Change Order failure received by RNC with a reference cell for which the iRNC is serving. This is in the scope of 3G to 2G handover, PS only. VS.RrcCellChangeOrderFailureNeighbRnc: Number of Inter Rat Cell Change Order failure received by RNC with a reference cell for which the iRNC is drift. This is in the scope of 3G to 2G handover, PS only.
Type CUM
Location Reference FddCell Neighboring RNC Reference FddCell Neighboring RNC
Screening 0: Rescue PS 1: Service PS 2: CAC Failure 0: Rescue PS 1: CAC Failure 0: Rescue PS 1: Service PS 2: CAC Failure 0: Rescue PS 1: CAC Failure
#0106
CUM
#0163
CUM
#0108
CUM
3G2G HHO PS execution failure rate 2G side
UA5.0 update: #105, 107 replaced; #106, 108 with new screenings
If the UE can not synchronize with the 2G target network during the 3G2G HHO execution phase, the UE sends the Cell Change Order from UTRAN Failure message to the RNC to come back on the 3G network The 3G2G PS HHO execution failure rate (2G side) metric is proposed to evaluate the 2G target cell synchronization failure. In case of high 3G2G HHO PS failure rate (2G) performance Network have to be detected Issues on the target 2G
Failure Rate RNC Level Failure Rate Cell Level
= =
#0163.[0] + #0108.[0] #0162.[0] + #0106.[0]

ID Counters IRATHO.AttOutPSUTRAN VS.RrcCellChangeOrderNeighbRnc IRATHO.FailOutPSUTRAN VS.RrcCellChangeOrderFailureNeighbRnc
#0163.[0] #0162.[0]
#0162 #0106 #0163 #0108
3G-3G Hard Handover
3G-3G Handover Successful case

UE Serving Node B Target Node B Serving RNC Target RNC Relocation Required
CN
Relocation preparation
SCCP Connection Request SCCP Connection Confirm Relocation Request Radio Link Setup Request Radio Link Setup Response Relocation Request Acknowledge Relocation Command #0537 Iu Relocation Requests failures PS Relocation Detect Relocation Complete Radio Link Deletion Request Radio Link Deletion Response Iu Release Complete Released Iu Release Command #0569 Iu Relocation Complete #0536 Iu Relocation Requests failures CS #0535 Iu Relocation Requests
Radio Bearer Reconfiguration Radio Bearer Reconfiguration Complete
Relocation execution
UA5.0 update: new screenings
HHO Incoming 3G3G CS preparation success ratio A first metric during the 3G to 3G HHO monitors the preparation phase success rate on the target side in order to evaluate the :
the failures from the target RNC when allocating the resources for the mobile (Relocation Preparation Failure) failures due to wrong neighbouring definition
The metric should be based on the following fddcell counters:

Number of relocation requests at Iu interface(# 0535) Number of relocation request failures on CS Iu interface(#0536) Number of relocation request failures on PS Iu interface (#0537)
HHO Incoming 3G3G CS/PS preparation success ratio = 1 - Iu Relocation Request Failures [CS/PS 3G-3G] Iu Relocation Requests [CS/PS 3G-3G]
UA5.0 update: new screenings, counter replaced
HHO Incoming 3G3G CS execution success ratio If there is no configuration in the target RNC that matches the number and type of radio bearer in the existing configuration (managed by the serving RNC) then the relocation is failed and a RELOCATION FAILURE is sent back to the Core Network. HHO incoming 3G3G execution success rate is based on the RNC counters
Number of relocation complete sent by the target RNC on the Iu (#0569) Number of relocation requests received by the target RNC at Iu interface(# 0535) Number of relocation request failures sent by the target RNC on Iu-CS (#0536) Number of relocation request failures sent by the target RNC on Iu-PS (#0537)
HHO Incoming 3G3G CS/PS execution success ratio = Iu Relocation complete [CS/PS] / (Iu Relocation Requests [CS/PS 3G-3G] - Iu relocation request failure CS/PS [3G3G])
Other Mobility Metrics HHO 3G3G Inter RNC outgoing success rate From the serving RNC point of view the metric HHO 3G3G Inter RNC outgoing success rate can be used based on the reference fddcell counters
The number of attempted outgoing relocation to another RNC in the same PLMN, which is not connected by an Iur (#0131) The number of successful outgoing relocation to another RNC in the same PLMN, which is not connected by an Iur (#0133)
HHO 3G3G Inter RNC outgoing success rate =

Outgoing Inter-RNC without IUR Handover Success/ Outgoing Inter-RNC without IUR Handover Attempt
Other Mobility Metrics HHO 3G3G Inter PLMN Outgoing HHO success rate
UA5.0 update: new screenings, counter replaced
In case of the target cell PLMN is different from source cell PLMN, the metric is based on the following reference cell counters
Number of attempted outgoing relocation toward another PLMN (#0128) Number of failed outgoing relocation toward another PLMN (#0129) Number of successful outgoing relocation toward another PLMN (#0166)
HHO 3G3G Inter PLMN Outgoing HHO success rate =

Outgoing Inter-PLMN Handover Success / Outgoing Inter-PLMN Handover Attempt
3G-3G Soft Handover
3G-3G Soft Handover

UE Node B RNC
Measurement Report RL Setup Request RL Setup Respond
Active Set Update Active Set Update Complete
#0415 Active Set Update Complete #0402 Active Set Update Unsuccess
ID #0415
Definition VS.RrcActiveSetUpdateCompleteProcedure: Number of successful RRC ACTIVE SET UPDATE procedure for which the cell is in the list of the active set before or after the AS execution. Incremented once per AS procedure for the cell. VS.RrcActiveSetUpdateUnsuccess: Number of unsuccessful RRC ACTIVE SET UPDATE due to procedure failure or timer expiry.
Type CUM
Location FddCell
Screening
#0402
CUM
FddCell
0: Failure 1: Timeout
3G-3G Soft Handover Success Rate

It evaluates success rate of the overall 3G-3G Soft & Softer Handover for each cell in the active set.
SHO 3G-3G success rate
= 1-
AS Update Unsuccess AS Update Unsuccess + AS Update Complete
SHO 3G-3G success rate
= 1-
#0402.[0 - 1] #0402.[0 - 1] + #0415
Mean Sector per User
UA5.0 update: counter replaced
Mean Sector Per User Average number of Radio Link per user / mobile Mean Sector Per User evaluates the efficiency of macro-diversity and detects eventual areas to be optimized. The metric is based on the following counter:
ID #0025 Definition VS.UeWithNRadioLinksEstCellsBts: This measurement provides the average number of mobiles having N Radio-inks in their Active Set, during an observation period. Minimum and maximum number of mobiles having N Radio-Links in their Active Set over the period are also provided. Type Load Location Reference FddCell Screening Number of radio links [1..6] NiRLiRciSBtsiA Bts
This metric can be monitored at Cell and RNC levels Mean Sector per User = weighted average of number of users having 1 RL = i*(#0025.[iRadioLinks].[Avg] / (#0025.Avg)
Mean Sector Per User
This metric can be monitored at Cell and RNC levels If the Mean Sector Per User is too low, check the macro-diversity algorithms and resources congestion If the Mean Sector Per user is too high, the macro-diversity algorithms & RF tuning have to be checked Mean Sector Per User
[(nb of UE with 1 RL) + (2*nb of UE with 2 RLs) + (3*nb of UE with 3 RLs) + (4*nb of UE with 4 RLs) + (5*nb of UE with 5 RLs) + (6*nb of UE with 6 RLs)] [(nb of UE with 1 RL) + (nb of UE with 2 RLs) + (nb of UE with 3 RLs) + (nb of UE with 4 RLs) + (nb of UE with 5 RLs) + (nb of UE with 6 RLs)]
Congestion / Load Metrics
Network Congestion Performance

The objective of the Congestion metrics is to evaluate the ability of the network to avoid the blocking in the network and to foresee further capacity issues Blocking represents the failures or rejections due to lack of resources: power, downlink codes, Uplink overload (UL RSSI), Iub Tx Link or any board overload (i.e. CEM, TMU). However the blocking could happen at different stages of the call: At call set-up At incoming HHO attempts At SHO attempts Following are the possible blocking families: RRC connection Radio link RAB setup RB setup SCCP establishment In the performance monitoring the RB Blocking rate is studied as it impacts directly the accessibility performance results
UA5.0 update: #404 with new screenings
RRC Connection Blocking

Causes for RRC Failures
Ratio of RRC connection reject vs number of RRC connection request This metric can be computed with the RRC Connection failure causes at cell and RNC level
0 1 2 3 4 5 6 7
timeout unavailable dl code resources unavailable dl power resources Unspecified RSSI Cell Fach Unspecified CAC Overload 3G to 2G Redirection for Emergency Calls RRC context CAC, pegged when CAC fails Unavailable RRC context resource, RRC context exhausted Unavailable FACH context resource, FACH context exhausted No answer from the NodeB Lack of C-RNTI UE Ec/No lower than qQualityMin
RRC connection Reject rate (system view)
#404(all causes except Time Out) 409.[RRC Call screenings]
9 10 11 12 13
ID #0403 #0404 #0409
Definition RRC.SuccConnEstab: Number of RRC connections successfully established. RRC.FailConnEstab: Number of RRC connection establishment failures. RRC.AttConnEstab: Number of RRC connection request received.
Type CUM CUM CUM
Location FddCell FddCell FddCell
Screening Establishment cause Failure cause Establishment cause
Accessibility: call establishment flow (Cell-DCH case) RAB Establishment Phase & Associated Counters
UE Node B RNC CN Counter Replaced in UA5.0 Screenings updated in UA5.0 No change
#0671 RAB Assignment Request
RAB Assignment Request
#0691 RB Setup Request #0631 RB Establishment unsuccess
S.R.L.R. Procedure Radio Bearer Setup Radio Bearer Setup Complete
Internal RRM decision to assign resources #0677 RAB assignment setup unsuccess #0672 RAB Assignment Success Per Requested RAB type #0673 RAB Assignment Success Per Granted RAB type
RAB Assignment Response #0687 RB Setup Success #0602 RB Setup Unsuccess
ID #0687 #0602 #0691 #0631
Definition VS.RadioBearerSetupSuccess: Number of Radio Bearers successfully setup. VS.RadioBearerSetupUnsuccess: Number of Radio Bearers not successfully setup. VS.RadioBearerSetupRequest: Number of Radio bearer setup decisions by the RNC (leading or not to a RB SETUP, ie. even if Call Admission Control rejects the setup) VS.RadioBearerEstablishmentUnsuccess: Number of Radio-Bearer establishments that have been rejected by the RNC (no RB Setup Request sent).
Location Reference FddCell Reference FddCell Reference Fddcell Reference Fddcell
Screening TargetCall Type Failure cause TargetCall Type Failure cause
UA5.0 update: #0625 replaced
Mean Radio Bearer Blocking rate

In case of sharp increase of Mean Radio Bearer blocking rate, congestion happens and Accessibility decreases (RAB Assignment success rate decreasing) If congestion happens, investigation on RB Establishment Unsuccess causes (#0631) must be assessed. Can be computed at Cell and RNC level
M ean Radio Bearer Blocking Rate
140000 120000 100000 10.00% 9.00% 8.00% 7.00% 6.00% 5.00% 60000 40000 20000 0 15/03/2006 4.00% 3.00% 2.00% 1.00% 0.00% 12/04/2006
Radio Bearer Blocking rate = RB establishment unsuccess / RB to be setup = #0631 / #0691
80000
22/03/2006
29/03/2006 RA B Requests
05/04/2006 RB Blocking Rate
Mean Radio Bearer Blocking rate

This metric can be split per failure cause (VS.RadioBearerEstablishmentUnsuccess) to monitor the blocking at different steps of Call admission Step1:
Screening 0: Invalid RAB parameters value.
1
Request RAB
RAB Matching Matched RABs RAB
Step 2 or 3:
Screening 1: Unavailable dl code resources Screening 2: Unavailable dl power resources Screening 6: Lack of RNC processing resources Screening 9: Lack of CID on the Iu Screening 10 : Lack of bandwidth on the Iu Screening 11 : Lack of CID on the Iur Screening 12: Lack of bandwidth on the Iur Screening 13 : Lack of CID on the Iub Screening 14 : Lack of bandwidth on the Iub
RAB to RB mapping Granted RB
Resource reservation & Call Admission Control Resource allocation
RL Reconfiguration RL Reconfigured
RB Setup RB Setup Success
Step4:
Screening 3: Unspecified
Radio Bearer Blocking rate = #0631 [1-3,6,9-14] / #0691
Screening 4 & 5
unused ; 7 & 8 not incremented
Cell color counters

RAB Blocking happens every time a RAB establishment or a RB reconfiguration procedure fails because of lack of resources (iRM CAC applies to PS call only). The congestion of the network can be seen thanks to iRM CAC metrics as it reveals the status of cell color (codes/ Power) or link color (Ec/No, RSCP) For a top N cells report, some counters can be used to assess the congestion by giving the number of cells having been red during a day
ID #1124 #1136 #1137 #1138 Definition VS.IRMTimeCellColorRed: Percentage of time during a collection period that a particular cell is considered red by iRM. VS.IrmPreemptionTimeCellColorCongested: Ratio of time a cell is considered to be congested by the Irm during a reporting period. VS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes: Ratio of time a cell is considered to be congested because of OVSF codes by the iRM during a reporting period. VS.IrmPreemptionTimeCellColorCongestedBecauseOfPower: Ratio of time a cell is considered to be congested because of power consumption by the iRM during a reporting period (Average value). VS.IrmTimeDlIubTransportColorRed: This measurement provides the ratio of time a cell is considered red for Downlink IubTransport by iRM during a reporting period Type Load Load Load Load Location FddCell Fddcell Fddcell Fddcell
#1182
Load
FDDCell
Impacted by HSDPA
Traffic Metrics
Network Traffic Monitoring

The objective of the Traffic metrics is to evaluate the traffic volume seen on the network in downlink and in uplink
Therefore the metric results are helpful to define the overall call model in the network (e.g. what is the main service used: PS, voice, video)
These inputs are also very useful complementary information to better understand the other performance results: accessibility, retainability, mobility & congestion
Average Number of calls RNC Level

The average number of calls (RAB established) is based on the counter:
ID #0675 Definition VS.NumberOfRabEstablished: This counter is the average number of RABs established of the "granted RAB type" in the RNS during a reporting period. The counter does not peg any iRM Scheduling downgrade, upgrade, Always ON. Type Load Location RNC Screening RAB type
This metric can only be monitored at RNC level Is screened per granted RAB Average number of Voice calls = #0675. Avg[1] Average number of Video calls = #0675.Avg[2] Average number of PS calls = #0675.Avg[0,5-16] Average number of HSDPA calls = #0675.Avg[10-16]
Average Number of calls Cell Level

The average number of calls (RAB established) at Cell Level is based on the counter:
ID #0692 #0693 Definition VS.DlAsConfIdAvgNbrEstablished: Indicates an average of the number of DlAsConfIds established per iRNC, based on time average over collection period. VS.UlAsConfIdAvgNbrEstablished: Indicates an average of the number of UlAsConfIds established per iRNC, based on time average over collection period. Type Load Load Location Reference FDDCell Reference FDDCell Screening DlAsConf UlAsConf
It is screened per AsConfId (UserService) Average number of Voice calls = #0692. Avg[1] Average number of Video calls = #0692.Avg[2] Average number of pure PS calls = #0692.Avg[4-15] Average number of HSDPA calls = #0692.Avg[14]
Uplink / Downlink PS Traffic RNC Level

The Uplink / Downlink PS Traffic metrics aims at providing the amount of data traffic This global information is interesting to correlate with eventual decrease of network performance results (e.g. congestion) These metrics are based on the following counters :
ID #1472 #1473 Definition VS.DedicatedUplinkKbytesRlc: Total count of uplink RLC payload (SDU) received on dedicated channels. VS.DedicatedDownlinkKbytesRlc: Total count of downlink RLC payload (SDU) sent on dedicated channels. Type CUM CUM Location RNC RNC Screening RBSet UL Bit rate RBSet DL Bit rate
These metrics can only be monitored at RNC level The RLC retransmissions are not counted DL PS Traffic per RNC = #1473. [0,6,7-13] UL PS Traffic per RNC = #1472. [0,6-11,12]
Screening 6: HSDPA Screening 12: HSUPA
Uplink / Downlink PS Traffic Cell Level

The amount of traffic can be monitored per UL/DL Bit rate and so identify the main bearers which convey the main traffic These metrics are based on the following counters :
ID #1484 #1485 Definition VS.DedicatedUplinkKbytesRlcActiveCells: Total number of Kbytes of RLC SDU received on uplink on dedicated channels for each cell of the active set. VS.DedicatedDownlinkKbytesRlcActiveCells: Total number of Kbytes of RLC SDU sent on downlink on dedicated channels for each cell of the active set. Type CUM CUM Location Fddcell Fddcell Screening RBSet UL Bit rate RBSet DL Bit rate
These metrics can only be monitored at Cell level The RLC retransmissions are not counted
DL PS Traffic per cell = #1485.[0,6,7-13] UL PS Traffic per cell = #1484.[0,6-11,12]
Screening 6: HSDPA Screening 12: HSUPA
Quality Metrics
Network Quality Performance The objective of the Quality metrics is to evaluate the ability of the network to provide quality transmission of the user requested services The focus is made on iRM pre-emption Always-On iRM Scheduling Downgrade / Upgrade
UA5.0 Update: new screenings
iRM pre-emption
iRM pre-emption feature, allows to reduce the allocated resources on the PS I/B RB of connected users according to user OLS priority as soon as a certain load (power / code shortage) is experienced iRM pre-emption monitoring metrics allow to evaluate the number of RB impacted by this feature
ID #1139 #1141 #1143 #1140 #1142 #1144 Definition VS.IrmPreemptionRbHigh/Medium/LowPriorityDowngraded: Number of times RB with High (gold) / Medium (silver) / Low (bronze) Priority is downgraded due to iRM pre-emption (cell color is congested). VS.IrmPreemptionRbHigh/Medium/LowPriorityRejected: Number of times RB with High (gold) / Medium (silver) / Low (bronze) Priority is released due to iRM pre-emption (cell color is congested). Type CUM Loc. RNC Screening dlRbSetId
CUM
RNC
dlRbSetId
These metrics are computed at RNC level per DlRBsetId Number of I/B RB downgraded by iRM Preemption = #1139 + #1141 + #1143 Number of I/B RB rejected by iRM Preemption = #1140 + #1142 + #1144 These results can be correlated with metrics which evaluate the user accessibility of the network like the call set up and the blocking rate, as this feature intends to decrease call blocking and free code and power at cell level
Screening HSDPA: 17,20
Always On
UE Node B RNC CN
S.R..L. R. procedure #685 Radio Bearer Reconfigure Request RRC / Radio Bearer Reconfiguration RRC / Radio Bearer Reconfiguration Complete # 684 Radio Bearer Reconfiguration Success # 1159 Downsizing Step1 Success # 1165 Upsizing Success
Downsizing (Step 1) / Upsizing
ID #1159 #1160 #1161 #1162 #1165 #1166 #1167 #1168
Definition VS.DownsizingStep1Success: Number of successful always on downsizing step1. VS.DownsizingStep1SuccessNeighbRnc: Number of successful always on downsizing step1 for calls having their primary cell located on a neighboring RNC. VS.DownsizingStep1Unsuccess: Number of unsuccessful always on downsizing step1. VS.DownsizingStep1UnsuccessNeighbRnc: Number of unsuccessful always on downsizing step1 for calls having their primary cell located on a neighboring RNC. VS.UpsizingSuccess: Number of successful upsizing from always on step1. VS.UpsizingSuccessNeighbRnc: Number of successful upsizing from always on step1 for calls having their primary cell located on a neighboring RNC. VS.UpsizingUnsuccess: Number of unsuccessful upsizing from always on step1. VS.UpsizingUnsuccessNeighbRnc: Number of unsuccessful upsizing from always on step1 for calls having their primary cell located on a neighboring RNC.
Type CUM CUM CUM CUM CUM CUM CUM CUM
Location Ref. FddCell Neighboring RNC Ref. FddCell Neighboring RNC Ref. FddCell Neighboring RNC Ref. FddCell Neighboring RNC
Screening dlAsConfId dlAsConfId dlAsConfId dlAsConfId dlAsConfId dlAsConfId dlAsConfId dlAsConfId
Always On
UE Node B RNC CN
# 577 Iu Release Request Ps Always On Downgrade
RANAP / RANAP /
IU Release Request IU Release Command
RRC / RRC Connection Release RRC / RRC Connection Release Complete

RANAP / IU Release Complete
# 506 Iu Release Command Ps .ReleaseDueToUtranGeneratedReason

SCCP Released
# 405 RrcConnectionRelease.UserInactivity Downsizing to Idle mode (Step 2)
# 676 VS.RabNormalRelease per granted RAB
ID #1163 #1164
Definition VS.DownsizingStep2Success: Number of successful always on downsizing step2. VS.DownsizingStep2SuccessNeighbRnc: Number of successful always on downsizing step2 for calls having their primary cell located on a neighboring RNC.
Type CUM CUM
Screening dlAsConfId dlAsConfId
Always On metrics Always-On feature allows to reduce or release the allocated resources when timer activity expires These metrics allows us to assess how adapted are the inactivity timers to the call profile The metrics can be computed at RNC or Cell level and are screened per DlAsConfId Downsizing step 2 vs downsizing step 1 (Source DlAsConfId) = (# 1163 + #1164) / (#1159 +#1160)
Impacted by HSDPA Included in global metric
Upsizing attempts (Target DlAsConfId) vs. downsizing step 1 (source DLAsconfid) = (#1165 +#1166+ #1167 +#1168 ) / (#1159 +#1160)
Available for HSDPA
iRM Scheduling downgrade metrics
on Transmitted Code Power criteria This is based on the number of successful / failed RB throughput downgrades based on TxCP encountered by the iRM scheduling(# 1149 / #1153) screened per DlAsConfId)
ID #1169 Definition VS.IRMSchedulingDowngradedSuccess: This measurement provides the number of success RB throughput downgrades based on TxCP encountered by the iRM scheduling feature. VS.IRMSchedulingDowngradedFailure: This measurement provides the number of failed RB throughput downgrades based on TxCP encountered by the iRM scheduling feature. Type CUM Location FDDCell (Reference) Screening DlAsConf
#1170
CUM
FDDCell (Reference)
DlAsConf
This metric is at fddcell level and can be computed per Radio Bearer.
Number of iRM Scheduling Downgrade on TxCP success rate =

#1169[source DlAsConfId] / (#1169 [source DlAsConfId] + #1170 [source DlAsConfId])
Not applicable for HSDPA
UA5.0 update: counters No replaced update since 4.1
iRM Scheduling Upgrade metrics

iRM scheduling upgrade, allows to upgrade a RB, which has been previously downgraded by iRM scheduling downgrade, based on Transmitted Code Power criteria Metrics are based on the following counters
ID #1131 Definition VS.IrmUpgradingActivation: Number of times iRM upgrading monitoring has been triggered for a call which has just been downgraded due to iRM Scheduling downgrading (bad radio conditions). VS.IrmUpgradingActivationDelayed: Number of times iRM upgrading monitoring has not been triggered immediately after a call has been downgraded due to iRM Scheduling downgrading (bad radio conditions). VS.IrmUpgradingCommand: Number of times iRM Scheduling Upgrading was performed (call has been downgraded before due to bad radio conditions and is now experiencing good radio conditions, ie. DL transmit power low enough). VS.IrmUpgradingDeactivation: Number of times iRM Scheduling Upgrading was deactivated while the DL transmitted power was monitored. VS.IrmUpgradingSuccessful: Number of times the iRM Upgrading was successfully executed (upgrading to a high or intermediate bit rate). Type CUM Location RNC Screening
#1132
CUM
RNC
#1174
CUM
RNC
high Bitrate Intermediate Bitrate
#1134 #1173
CUM CUM
RNC RNC dlAsConId
Percentage of calls attempted to upgrade = #1174 / #1131 iRM scheduling upgrade success rate = #1173 / #1174
Percentage of calls eligible to upgrade which are delayed = #1132 / #1131

BACK UP
RAB Allocation Procedure

Data Flow Diagram + Counters (1/3)
UE Node B RNC
1 2 3
CN - CS
RAB Assignment Request
CAC
Radio Link Reconfiguration Prepare Radio Link Reconfiguration Ready UP / DL Synchronization UP / UL Synchronization
5 6
AAL2 / ERQ AAL2 / ECF UP / Initialization UP / Initialization Ack.

7
Radio Link Reconfiguration Commit Radio Bearer Setup Radio Bearer Setup Complete
RAB Assignment Response

1 2 3 4
#0671 - RAB Assignment Request (RAB Type) #0631.0 - RB Establishment Unsuccess cause Invalid RAB parameters value #0691 - RB Setup Request (Downlink Access Stratum) #0631 - RB Establishment Unsuccess
1 - Unavailable code resource 2 - Unavailable Power resource 4 - Lack of bandwidth (replaced by screenings #10, #12 and #14 in UA04.2) 5 - Lack of CID (replaced by screenings #9, #11 and #13 in UA04.2) 6 - RNC Processing resources 9 - Lack of CID on IU (introduced in UA04.2) 10 - Lack of bandwidth on IU (introduced in UA04.2) 11 - Lack of CID on IUR (introduced in UA04.2) 12 - Lack of bandwidth on IUR (introduced in UA04.2) 13 - Lack of CID on IUB (introduced in UA04.2) 14 - Lack of bandwidth on IUB (introduced in UA04.2)
5 6
#0037 Radio Link Reconfiguration Request (Downlink Access Stratum) (introduced in UA04.2) #0031 - Radio Link Reconfiguration Success (Downlink Access Stratum) #0008 - Radio Link Reconfiguration Prepare Unsuccess
0 - Reception of RL Reconfiguration Failure 1 - Time-out 2 - Rrm refusal (ie: no more power available, no more code available, ...) 3 - I-Node refusal (replaced by screenings #6, #7 and #8 in UA04.2) 6 - Lack of CID on the Iub (introduced in UA04.2) 7 - Lack of bandwidth on the Iub (introduced in UA04.2) 8 - I-Node refusal (ie: other I-Node resource not available ...) (introduced in UA04.2)
#0631.3 - RB Establishment Unsuccess cause Unspecified

7 8
#0631.3 - RB Establishment Unsuccess cause Unspecified #0032 - Radio Link Reconfiguration Commit (Downlink Access Stratum) #0026 - Radio Link Reconfiguration Cancel (Downlink Access Stratum) #0672 - RAB Establishment Success (Requested RAB Type) #0673 - RAB Establishment Success (Granted RAB Type) #0677 - RAB Assignment Unsuccess (Requested RAB Type) #0687 - Radio Bearer Setup Success (Downlink Access Stratum) #0602 - Radio Bearer Setup Unuccess (Failure cause)
#0631.3 - RB Establishment Unsuccess cause Unspecified is also incremented if a drop (due to RLC errors or RL failure) occurs during the RAB Assignment procedure.
Additional Information RAB Counters

To monitor Success Rate of RAB per AsConf, only RNC Counters are available (with screening combined UL and DL RBSetId). On RNC, 4 families of RAB counters: #671 - Vs.RabEstablishmentRequestsPerRabType: screening selected according to request from SGSN #672 - Vs.RabEstablishmentSuccessPerRequestedRabType: screening selected according to request from SGSN #673 - Vs.RabEstablishmentSuccessPerGrantedRabType : screening selected according to combination granted by RNC #677 - Vs. RabAssignmentSetupUnsuccess: screening selected according to request from SGSN On Iu, SGSN cannot ask for an HSDPA RAB (SGSN cannot specify the Radio Bearer Type that will support the call in the RAB Assignment message) #671, #672 and #677 are never pegged for the screenings with HSDPA The screenings doesnt include the following combinations: UL128/DL64, UL128/DL256, UL128/DL384: they are all pegged as RabOther
Ratio of iRM CAC RAB granted / Downgraded/ rejected
RAB Blocking happens every time a RAB establishment or a bearer reconfiguration procedure fails because of lack of resources (iRM CAC applies to PS call only). The congestion of the network can be seen thanks to iRM CAC metrics as it reveals the status of cell color (codes / Power) or link color (Ec/No, RSCP) IRM CAC metrics are based on the following counters
ID #1111 #1114 #1117 #1112 #1115 #1118 #1113 #1116 #1119 Definition VS.IrmcacMaintainedHigh/Medium/LowPriority: Number of RAB assignments for high / medium / low priority users that are maintained as requested by iRM. VS.IrmcacDowngradedHigh/Medium/LowPriority: Number of RAB assignments for high / medium / low priority users that are downgraded by iRM. VS.IrmcacRejectedHigh/Medium/LowPriority: Number of RAB assignments for high / medium / low priority users that are rejected by iRM. Type CUM Location RNC Screening dlRbSetId
CUM
RNC
dlRbSetId
CUM
RNC
dlRbSetId
Ratio of iRM CAC RAB granted / Downgraded/ rejected

Ratio of RB PS maintained by iRM CAC Total number of RAB granted by the IRM CAC vs RAB maintained, downgraded or rejected by the iRM CAC . Ratio of RB PS Downgraded by iRM CAC Ratio of number of RAB downgraded by the iRM CAC vs RAB granted, downgraded or RAB rejected by the iRM CAC Ratio of RB PS Rejected by iRM CAC Ratio of number of RAB rejected by the iRM CAC vs RAB maintained, downgraded, or rejected by the iRM CAC IRM CAC metrics can be screened per PS Bearer type and is built at RNC level
Ratio of IRM CAC PS Granted = Ratio of IRM CAC PS Downgraded =
(#1111+ #1114+ #1117) / (#1111+ #1112+ #1113+ #1114+ #1115+ #1116+ #1117+ #1118+ #1119)
(#1112+ #1115+ #1118) / (#1111+ #1112+ #1113+ #1114+ #1115+ #1116+ #1117+ #1118+ #1119)
Ratio of IRM CAC PS Rejected=

(#1113 +#1116+#1119) / (#1111+ #1112+ #1113+ #1114+ #1115+ #1116+ #1117+ #1118+ #1119)
Uplink / Downlink PS Traffic Cell Level

Number of Kbytes of Uplink / Downlink RLC payload on dedicated channels per UL/DL Bit rate when cell is reference versus the traffic carried when cell is in the active set These metrics are based on the following counters :
ID #1486 #1487 Definition VS.DedicatedUplinkKbytesRlcReferenceCell: Total number of Kbytes of RLC SDU received on uplink on dedicated channels for the reference cell of the active set. VS.DedicatedDownlinkKbytesRlcReferenceCell: Total number of Kbytes of RLC SDU sent on downlink on dedicated channels for the reference cell of the active set. Type CUM CUM Location Reference Fddcell Reference Fddcell Screening Combined UL/DL Bit rate Combined UL/DL Bit rate
These metrics can only be monitored at Cell level The RLC retransmissions are not counted
Percentage of DL traffic when cell is reference Percentage of UL traffic when cell is reference
= =
#1487.[UL/DL Bit rate] #1485.[UL/DL Bit rate] #1486.[UL/DL Bit rate] #1484.[UL/DL Bit rate]
Throughput per Combined DL/UL max bit rate at RNC level

Throughput metrics are necessary to assess the quality of the network and can be correlated with congestion results Throughput DL at RNC level: volume of Kbytes related to average time of RAB allocation
These metrics are based on the following counters:

ID #1472 #1473 #0675 Definition VS.DedicatedUplinkKbytesRlc: Total count of uplink RLC payload (SDU) received on dedicated channels. VS.DedicatedDownlinkKbytesRlc: Total count of downlink RLC payload (SDU) sent on dedicated channels. VS.NumberOfRabEstablished: Average number of established RABs in the RNS during a reporting period. Type CUM CUM Load Location RNC RNC RNC Screening Combined UL/DL Bit rate Combined UL/DL Bit rate RAB type
Throughput can be monitored per UL/DL Bit rate at RNC level This metric includes the inactivity period (before the connection is AO downsized)
Throughput per Combined DL/UL max bit rate at RNC level

Throughput can be monitored per UL/DL Bit rate at RNC level
Available for HSDPA
Troughput DL / UL per Combined DL / UL max bit rate at RNC level (Kb/s) =
= 8 * 10 *
VS.DedicatedDown/UplinkKbytesRlc(UL/DL Bit rate) VS.NumberOfRabEstablished.Rab. Cum (UL/DL Rab type)
Counter #0675 is per granted RAB type and Number of Kbytes is per current RAB The following metric allows to consider the IRM schedule & RB adaptation & AO transitions
ID #692 #693 Definition VS.Dl/UlAsConfIdAvgNbrEstablished: Indicates an average of the number of DlAsConfIds / UlAsConfIds established per iRNC, based on time average over collection period. Type Load Location Reference FDDCell Screening DlAsConf UlAsConfId
Available for HSDPA
Troughput DL / UL per Combined DL / UL max bit rate at RNC level (Kb/s) =
= 8 * 10 *
VS.DedicatedDown/UplinkKbytesRlc(UL/DL Bit rate) VS.DlAsConfIdNbrestablished. Cum (DlAsconfId Screenings)

DL BLER data
The DL BLER PS gives a view of the quality of the network For DL, the metric is based on
ID #1489 #1490 Definition VS.DedicatedDownlinkPdusRlcReferenceCell: Total number of Downlink RLC PDU emitted on dedicated channels for the reference cell. VS.DedicatedDownlinkRetransmittedPdusRlcReferenceCell: number of downlink RLC PDU retransmitted on dedicated channels on the reference cell (for RLC AM bearer (so only for PS)). Location Reference Fddcell Reference Fddcell Screening Combined UL/DL Bit rate Combined UL/DL Bit rate
This metric is computed per RB at cell level
DL BLER PS = #1490 [PS DL Bit rate] / #1489[ PS DL Bit rate]

Available for HSDPA
UL BLER Voice The metric UL BLER (Voice) is based on the following counters:
ID #1506 # 1507 Definition VS.DedicatedUplinkVoiceABitsGoodFrames: Total number of frames with Class A bits Transport Block received with CRCi = 0 (no error). VS.DedicatedUplinkVoiceABitsBadFrames: Total number of frames with Class A bits Transport Block received with CRCi = 1 (error). Type CUM CUM Location RNC RNC
This metric is computed at RNC level UL BLER Voice = #1507 / ( #1507 + #1506)
www.alcatel-lucent.com

ALU - UMTS QoS and Performance Monitoring

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ALU - UMTS QoS and Performance Monitoring

Uploaded by

Copyright:

Available Formats

QoS & Performance Monitoring

Performance Monitoring Metrics

Mohamed Arshad MoAD RNE SSEAI

All Rights Reserved Alcatel-Lucent 2008

UTRAN Performance Monitoring

2 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

UTRAN Performance Monitoring: how? Process

Set up the goals

Collect the observation data Analyze the collected data

Take the necessary actions Validate the actions taken

3 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

UTRAN Performance Monitoring Process

Data Retrieve Definition

Tools (PrOptima, scripts,)

4 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

5 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

UTRAN Performance Monitoring Metrics Families

6 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

7 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

8 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

Call Establishment Flow

RRC Connection Phase

SCCP Connection Phase

RAB establishment Phase

9 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

RRC Connection Phase

10 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

RRC (logical channel)

11 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

Call establishment flow RRC Connection

RRC Connection Phase & Associated Counters

Counter Replaced in UA5.0 Screenings updated in UA5.0 No change

ID #0403 #0404 #0409 #0419

Type CUM CUM CUM CUM

Location FddCell FddCell FddCell FddCell

Screening Establishment Cause Failure Cause Establishment Cause Establishment Cause

12 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

RRC Connection success rate

#0403.[RRC screenings] #0409. [RRC screenings]

#0403. [RRC screenings] #0419. [RRC screenings]

All Rights Reserved Alcatel-Lucent 2008

Not impacted by HSDPA

RRC Connection success rate for calls only System view

CS RRC Connection success rate PS RRC Connection success rate

14 | Performance Monitoring Overview | Nov 2008

Not impacted by HSDPA

SCCP Connection Phase

15 | Performance Monitoring Overview | Nov 2008

All Rights Reserved Alcatel-Lucent 2008

Call establishment flow

SCCP Phase & Associated Counters

#0548 SCCP Connection Success #0502 SCCP Connection Unsuccess

Type CUM CUM