Download - 19Jan_PM2_UMTS QoS Monitoring UA5
All Rights Reserved © Alcatel-Lucent 2008
WCDMA RNE Workshop
Performance Monitoring Metrics UA05
Mohamed Arshad
MoAD RNE SSEAI
Mumbai
January 2009
All Rights Reserved © Alcatel-Lucent 20092 | Performance Monitoring Overview | Jan 2009
UTRAN Performance Monitoring
Performance Monitoring Process
Dashboard Metrics
1. Accessibility
2. Retainability
3. Mobility
4. Congestion / Load
5. Quality
6. Traffic
All Rights Reserved © Alcatel-Lucent 20093 | Performance Monitoring Overview | Jan 2009
Set up the goals
Collect the observation data
Analyze the collected data
Take the necessary actions
Validate the actions taken
UTRAN Performance Monitoring: how?
Process
All Rights Reserved © Alcatel-Lucent 20094 | Performance Monitoring Overview | Jan 2009
Tools(PrOptima, scripts,…)
Data RetrieveDefinition
Criteria Definition• Hourly / Busy Hour, Daily, Weekly• Alarm detection
• NEs (RNC, FddCell, SGSN, …)Engineering
Mo
nit
ori
ng
S
etu
p• Counters • Metrics• Reports
Observation
Analysis
Correction
Validation
O&M
O&M
Mo
nit
ori
ng
Pro
cess
!
O&M
UTRAN Performance Monitoring
Process
All Rights Reserved © Alcatel-Lucent 20095 | Performance Monitoring Overview | Jan 2009
Dashboard Metrics
All Rights Reserved © Alcatel-Lucent 20096 | Performance Monitoring Overview | Jan 2009
Following a summary of the families to be presented:
� Accessibility
� Retainability
� Mobility
� Congestion/load
� Quality
� Traffic
UTRAN Performance Monitoring
Metrics Families
All Rights Reserved © Alcatel-Lucent 20097 | Performance Monitoring Overview | Jan 2009
1Accessibility
All Rights Reserved © Alcatel-Lucent 20098 | Performance Monitoring Overview | Jan 2009
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 � RRC Connection success rate
� SCCP Connection phase � Iu SCCP success rate
� RAB Assignment phase � RAB assignment success rate per requested RAB type
All Rights Reserved © Alcatel-Lucent 20099 | Performance Monitoring Overview | Jan 2009
Call Establishment Flow (Cell-DCH case)
UE Node B RNC CN
RRC Connection Request
RRC Connection CompleteRRC Connection Setup
Radio Link Setup RequestRadio Link Setup Response RRC Connection Phase
Measurement ControlInit 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 SetupRadio Bearer Setup Complete
RAB Assignment Response
SCCP Connection Phase
RAB establishment PhaseRAB establishment PhaseRAB establishment PhaseRAB establishment Phase
All Rights Reserved © Alcatel-Lucent 200910 | Performance Monitoring Overview | Jan 2009
RRC Connection Phase
All Rights Reserved © Alcatel-Lucent 200911 | Performance Monitoring Overview | Jan 2009
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.
Physical channel AAL2 bearer SIG/AAL5
RRC (logical channel)
Core Network
Circuit Domain
Packet Domain
UE Node B RNC
All Rights Reserved © Alcatel-Lucent 200912 | Performance Monitoring Overview | Jan 2009
UE
RRC Connection Request
RRC Connection CompleteRRC Connection Setup
Radio Link Setup RequestRadio Link Setup Response
#0409 RRC Connection Request
#0419 First RRC Connection Request
#0403 RRC Connection Success
#0404 RRC Connection Failure/reject
Call establishment flow (Cell-DCH case)
RRC Connection
RRC Connection Phase & Associated Counters
Node B RNC
Establishment CauseFddCellCUMVS.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.
#0419
Establishment CauseFddCellCUMRRC.AttConnEstab: Number of RRC connection request received. #0409
FddCell
FddCell
Location
Failure CauseCUMRRC.FailConnEstab: Number of RRC connection establishment failures.#0404
Establishment CauseCUMRRC.SuccConnEstab: Number of RRC connections successfully established.#0403
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200913 | Performance Monitoring Overview | Jan 2009
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
Not impacted by HSDPA
RRC connection success rate (user’s perception)
� 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 user’s perception
These metrics can be computed per RRC establishment cause :
� Calls only
� CS calls, PS calls
� Registration, …
RRC Connection success [ RRC screenings] ∑#0403.[RRC screenings]
RRC Connection requests [ RRC screenings] ∑#0409. [RRC screenings]=
RRC Connection success [ RRC screenings] ∑#0403. [RRC screenings]
First RRC Connection requests [ RRC screenings] ∑#0419. [RRC screenings]=
RRC Connection success rate
All Rights Reserved © Alcatel-Lucent 200914 | Performance Monitoring Overview | Jan 2009
Screening 16, Call re-establishment:
� 3GPP: used for CS Call re-establishment, or Routing Area Update
– for the case of ‘Directed Signalling Connection Re-
Establishment‘
� 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)
CS / PSTerminating – cause unknown19
Terminating Low Priority Signaling18
PSTerminating High Priority Signaling17
CS / PSCall re-establishment16
Originating Low Priority Signaling15
PSOriginating High Priority Signaling14
Detach13
Registration12
Inter-RAT cell change order11
Inter-RAT cell re-selection10
CSEmergency call9
PSTerminating Background call8
PSTerminating Interactive call7
CS / PSTerminating Streaming call6
CSTerminating Conversational call5
PSOriginating Subscribed Traffic call4
PSOriginating Background call3
PSOriginating Interactive call2
CS / PSOriginating Streaming call1
CSOriginating Conversational call0
RAB Domain
CauseScreening
CS / PSTerminating – cause unknown19
Terminating Low Priority Signaling18
PSTerminating High Priority Signaling17
CS / PSCall re-establishment16
Originating Low Priority Signaling15
PSOriginating High Priority Signaling14
Detach13
Registration12
Inter-RAT cell change order11
Inter-RAT cell re-selection10
CSEmergency call9
PSTerminating Background call8
PSTerminating Interactive call7
CS / PSTerminating Streaming call6
CSTerminating Conversational call5
PSOriginating Subscribed Traffic call4
PSOriginating Background call3
PSOriginating Interactive call2
CS / PSOriginating Streaming call1
CSOriginating Conversational call0
RAB Domain
CauseScreening
Not impacted by HSDPA
∑#0403.[0, 5, 9] ∑#0409.[0, 5, 9]
CS RRC Connectionsuccess rate =
∑#0403.[1-4, 6-8, 14, 16, 17,19]
∑#0409.[1-4, 6-8, 14, 16, 17,19]
PS RRC Connectionsuccess rate =
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
RRC Connection success rate for calls only
System view
All Rights Reserved © Alcatel-Lucent 200915 | Performance Monitoring Overview | Jan 2009
SCCP Connection Phase
All Rights Reserved © Alcatel-Lucent 200916 | Performance Monitoring Overview | Jan 2009
UE
Measurement ControlInit Direct Transfer
SCCP Connection Request (Initial UE Message)SCCP Connection Confirm
Authentication Procedure
Ciphering Procedure
#0548 SCCP Connection Success
#0502 SCCP Connection Unsuccess
Node B RNC CN
RNC
RNC
Location
CsReqByRNCPsReqByRNCCsReqByCNPsReqByCN
CUMVS.IuSccpCnxSuccess: Number of successful SCCP connections at Iu interface
#0548
Core Domain + OriginatorCUMVS.IuSccpCnxUnsuccess: Number of unsuccessful SCCP connections at Iu interface
#0502
ScreeningTypeDefinitionID
Call establishment flow (Cell-DCH case)
Iu SCCP Connection
SCCP Phase & Associated Counters
All Rights Reserved © Alcatel-Lucent 200917 | Performance Monitoring Overview | Jan 2009
Iu SCCP success rate
� Separation of CS & PS domains results � to facilitate the troubleshooting based on the two interfaces: Iu-
CS and Iu-PS
� 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 success rate
Iu SCCP
0
500000
1000000
1500000
2000000
2500000
01-Apr-06 08-Apr-06 15-Apr-06 22-Apr-0699.90%
99.92%
99.94%
99.96%
99.98%
100.00%
Attempts CS
Attempts PS
Iu SCCP Success Ratio
Success Ratio CS
Success Ratio PS
All Rights Reserved © Alcatel-Lucent 200918 | Performance Monitoring Overview | Jan 2009
Iu SCCP success rate
Not impacted by HSDPA
∑#0548.[0,2]
∑#0548.[0,2]+∑#0502.[0,1]
CS Iu SCCPsuccess rate = ∑#0548.[1,3]
∑#0548.[1,3]+∑#0502.[2,3]
PS Iu SCCPsuccess rate =
Iu-SCCP Connection unsuccess screenings:
#0502 Unsuccess on Iu-ps connection requested by Rnc. (ie: refusal from Core Network PS or SCCP layer or the Control Node (RNC))
2
Unsuccess on Iu-ps connection requested by Core Network PS (ie: refusal from Rnc). 3
Unsuccess on Iu-cs connection requested by Core Network CS (ie: refusal from Rnc)1
Unsuccess on Iu-cs connection requested by Rnc. (ie: refusal from Core Network CS or SCCP layer or the Control Node (RNC) )
0
With PS core network (connection requested by the core network)3
With CS core network (connection requested by the core network)2
Iu-SCCP Connection success screenings:
#0548
With PS core network (connection requested by the RNC)1
With CS core network (connection requested by the RNC)0
All Rights Reserved © Alcatel-Lucent 200919 | Performance Monitoring Overview | Jan 2009
RAB Establishment Phase
All Rights Reserved © Alcatel-Lucent 200920 | Performance Monitoring Overview | Jan 2009
UE Node B CN
RAB Assignment Request
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
#0671 RAB Establishment Request
Call establishment flow (Cell-DCH case)
RAB Establishment Phase
RAB Establishment Phase & Associated Counters
RNC
RAB TypeRNCCUMVS.RabAssignmentSetupUnsuccess: Number of RAB that could not be established by the RNC.#677
RAB TypeRNCCUMVS.RabEstablishmentSuccessPerGrantedRabType: Number of successful RAB establishment,
screened per granted RAB type. Screening selected according to combination granted by RNC
#673
RNC
RNC
Location
RAB TypeCUMVS.RabEstablishmentSuccessPerRequestedRabType: Number of successful RAB establishment,
screened per requested RAB type. Screening selected according to request from CN
#672
RAB TypeCUMVS.RabEstablishmentRequestsPerRabType: Number of RAB establishment attempts. Screening selected according to request from CN
#671
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200921 | Performance Monitoring Overview | Jan 2009
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
� Separation of CS domain services and PS domain services � to facilitate the
troubleshooting based on the user behaviour.
� The metric can also be computed per RAB type at RNC level.
� 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
RAB Establishment success ∑ #0672. [RAB Type]
RAB Establishment request ∑ #0671. [RAB Type]=RAB Establishment success rate =
HSDPA RAB assignment success per granted HSDPA RAB = ∑ #0673[10 - 16]
All Rights Reserved © Alcatel-Lucent 200922 | Performance Monitoring Overview | Jan 2009
∑ #0672.[1]
∑ #0671.[1]
Voice RAB Establishmentsuccess rate =
∑ #0672.[0,5-9]
∑ #0671.[0,5-9]
PS RABEstablishmentsuccess rate
=
∑ #0672.[2]
∑ #0671.[2]
Video RAB Establishmentsuccess rate =
RAB Establishment success rate per requested RAB
CS RAB Establishment Success Rate
0
10000
20000
30000
40000
50000
60000
70000
80000
90000
100000
15/03/2006 22/03/2006 29/03/2006 05/04/2006 12/04/2006
90.00%
91.00%
92.00%
93.00%
94.00%
95.00%
96.00%
97.00%
98.00%
99.00%
100.00%
Requests CS Voice Requests CS V ideo CS Voice CS Video
PS RAB Establishment Success Rate
0
10000
20000
30000
40000
50000
60000
15/03/2006 22/03/2006 29/03/2006 05/04/2006 12/04/2006
60.00%
65.00%
70.00%
75.00%
80.00%
85.00%
90.00%
95.00%
100.00%
Requests PS Success Rate PS
All Rights Reserved © Alcatel-Lucent 200923 | Performance Monitoring Overview | Jan 2009
UE Node B CN
RAB Assignment Request
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
#0671 RAB Establishment Request
Call establishment flow (Cell-DCH case)
RAB Establishment Phase
RB Setup & Associated Counters
RNC
Failure causeReference
Fddcell
CUMVS.RadioBearerEstablishmentUnsuccess: Number of Radio-Bearer establishments that
have been rejected by the RNC (no RB Setup Request sent).
#0631
TargetCall
Type
Reference
Fddcell
CUMVS.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)
#0691
Reference
FddCell
Reference
FddCell
Location
Failure causeCUMVS.RadioBearerSetupUnsuccess: Number of Radio Bearers not successfully setup.#0602
TargetCall
Type
CUMVS.RadioBearerSetupSuccess: Number of Radio Bearers successfully setup.#0687
ScreeningTypeDefinitionID
Internal RRM decision to assign resources
#0691 RB Setup Request
#0631 RB Establishment unsuccess
#0687 RB Setup Success
# 602 RB Setup Unsuccess
All Rights Reserved © Alcatel-Lucent 200924 | Performance Monitoring Overview | Jan 2009
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]
� 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
HSDPA RB setup success rate = #0687.[14] / #0691.[14]
RB To be Setup success ratio ==
Radio Bearer To be Setup success ratio
RB Setup SuccessRB Setup Request
∑ #0687.[TargetCall Type]
∑ #0691.[TargetCall Type]
All Rights Reserved © Alcatel-Lucent 200925 | Performance Monitoring Overview | Jan 2009
Call setup success rate at RNC Level
All Rights Reserved © Alcatel-Lucent 200926 | Performance Monitoring Overview | Jan 2009
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
� Impacted by HSDPA for the RAB phase (seen with RB Setup)
First RRC success rate (calls only) � user’s perception
Call Setup success rate *= RRC Connection
success rate
SCCP Connection
Success rate
RAB Establishment
success rate*
Call setup success rate at RNC Level
All Rights Reserved © Alcatel-Lucent 200927 | Performance Monitoring Overview | Jan 2009
� Separation of CS domain results and PS domain results � to facilitate the
troubleshooting based on user behaviour
Call setup success rate at RNC Level
� 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)
CSSR
65.00%
70.00%
75.00%
80.00%
85.00%
90.00%
95.00%
100.00%
25-Apr-06 02-May-06 09-May-06 16-May-06 23-May-06
CS Voice & Data PS Calls
All Rights Reserved © Alcatel-Lucent 200928 | Performance Monitoring Overview | Jan 2009
� Separation of Voice, Video and PS domain results � to facilitate the
troubleshooting based on user behaviour
� Iu SCCP Phase is not considered in the dashboard
� RNC Level � RAB
� Cluster and Cell Level � RB
Call setup success rate
� 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)
� 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)
All Rights Reserved © Alcatel-Lucent 200929 | Performance Monitoring Overview | Jan 2009
Retainability Metrics
2
All Rights Reserved © Alcatel-Lucent 200930 | Performance Monitoring Overview | Jan 2009
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
� Drops rate per normally released calls – Cell level
� Drops per minute of RAB
All Rights Reserved © Alcatel-Lucent 200931 | Performance Monitoring Overview | Jan 2009
#0576 Iu release request CS (cell)
#0577 Iu release request PS (cell)
#0572 Iu abnormal release request CS (cell)
#0573 Iu abnormal release request PS (cell)#0505 Iu release command CS
#0506 Iu release command PS
Node B RNC CN
Radio Link Deletion Response
Iu Release Request
Iu Release Command
Radio Link Deletion Request
Iu Release Complete
#0571 Iu release complete CS
Issue detected
Call Abnormal Release
Flow & Associated Counters
RAB Assignment Response
#0677 RAB Assignment setup unsuccess
#0672 RAB Establishment Success Per
Requested RAB type
#0673 RAB Establishment Success Per Granted
RAB type
TargetCall
Type
Reference
Fddcell
CUMVS.IuAbnormRelReqPs : Number of Iu PS release requests due to abnormal conditions.#0573
RNC
Reference
Fddcell
Location
RAB typeCUMVS.RabEstablishmentSuccessPerGrantedRabType: Number of successful RAB
establishment, screened per granted RAB type
#0673
TargetCall
Type
CUMVS.IuAbnormRelReqCs : Number of Iu CS release requests due to abnormal conditions.#0572
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200932 | Performance Monitoring Overview | Jan 2009
Number of drops
Number of RAB success per granted RAB type
Call dropRate =
∑ #0572.[CS TargetCall Type]
∑ #0673.[1-4]
CS Call dropRate =
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, …
All Rights Reserved © Alcatel-Lucent 200933 | Performance Monitoring Overview | Jan 2009
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…
� 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])
Call Drop Rate per RAB established – RNC level
Call Drop Rate
0.00%
0.50%
1.00%
1.50%
2.00%
2.50%
3.00%
27-Apr-06 01-May-06 05-May-06 09-May-06 13-May-06 17-May-06 21-May-060
100
200
300
400
500
600
700
800
900
Voice Iu Rel. Request V ideo Iu Rel. Request Voice CDR Voice CDR
Call Drop Rate
0.00%
0.50%
1.00%
1.50%
2.00%
2.50%
3.00%
3.50%
4.00%
27-Apr-06 01-May-06 05-May-06 09-May-06 13-May-06 17-May-06 21-May-06
0
200
400
600
800
1000
1200
1400
1600
1800
PS Iu Rel. Request PS CDR
All Rights Reserved © Alcatel-Lucent 200934 | Performance Monitoring Overview | Jan 2009
#0505 Iu release command CS
#0506 Iu release command PS
Node B RNC CN
Radio Link Deletion Response
Iu Release Request
Iu Release Command
Radio Link Deletion Request
Iu Release Complete
#0571 Iu release complete CS
Issue detected or User Inactivity
Call Abnormal Release
Flow & Associated Counters
TargetCall
Type
Reference FddcellCUMVS.IuReleaseCompleteCs: number of RANAP Iu Release Complete sent by RNC to CN
on the Iu interface on CS domain.
#0571
TargetCall
Type
Reference FddcellCUMVS.IuAbnormalReleaseRequestCs: Number of Iu CS release requests due to abnormal
conditions.
#0572
TargetCall
Type
Reference FddcellCUMVS.IuAbnormalReleaseRequestPs: Number of Iu PS release requests due to abnormal
conditions.
#0573
Reference FddCell
Reference FddCell
Location
TargetCall
Type
CUMVS.DownsizingStep2Success: Number of successful always on downsizing step2.#1163
TargetCall
Type
CUMVS.RadioBearerReleaseSuccess: Number of Radio Bearers successfully released.#0688
ScreeningTypeDefinitionID
#0572 Iu abnormal release request CS (cell)
#0573 Iu abnormal release request PS (cell)
#1163 Downsizing Step 2 Success
All Rights Reserved © Alcatel-Lucent 200935 | Performance Monitoring Overview | Jan 2009
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 ….
Iu abnormal release requests CS
Iu release complete CS
CS Call dropRate at cell level =
∑ #0572.[CS TargetCall Type]
∑ #0571.[CS TargetCall Type]
CS Call dropRate =
All Rights Reserved © Alcatel-Lucent 200936 | Performance Monitoring Overview | Jan 2009
Iu abnormal release requests PS Iu abnormal release requests PS +
Downsizing Step 2 + Radio Bearer release success ( PS + FACH)
PS Call drop
Rate at cell level =
Impacted by HSDPA
Included in PS metric
∑ #0573 ( PS TargetCallType)
∑ #0573 (PS TargetCallType) +
∑ #1163 (PS TargetCallType) +
∑ #0688 (PS + FACH TargetCallType)
PS 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)
Signalling Call drop Rate at cell level =
Call Drop Rate per Released Calls – Cell level
All Rights Reserved © Alcatel-Lucent 200937 | Performance Monitoring Overview | Jan 2009
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 :
Number of drops per minute of RAB – RNC level
Iu abnormal release requests CS / PS
Allocation time of the RAB
Number of drops per min of RAB CS / PS =
Number of drops per min of HSDPA Call = 60*10*#0573[12] / #0692.Cum [14]
60*10* (∑∑∑∑ VS.IuAbnormalReleaseRequestCs/Ps [CS / PS TargetCallType])∑∑∑∑ VS.DlAsConfIdAvgNbrEstablished.CUM [CS / PS TargetCallType]
Reference
Fddcell
Reference
Fddcell
Location
TargetCall
Type
CUMVS.IuAbnormalReleaseRequestCs/Ps: Number of Iu Cs/Ps release requests due to abnormal
conditions.
#0572
#0573
TargetCall
Type
LoadVS.DlAsConfIdAvgNbrEstablished: Indicates an average of the number of DlAsConfIds
established per iRNC, based on time average over collection period.
#0692
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200938 | Performance Monitoring Overview | Jan 2009
Mobility Metrics
3
All Rights Reserved © Alcatel-Lucent 200939 | Performance Monitoring Overview | Jan 2009
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
UTRAN Performance Monitoring
Mobility Metrics
All Rights Reserved © Alcatel-Lucent 200940 | Performance Monitoring Overview | Jan 2009
Network Mobility Performance
� The objective of the Mobility metrics is to evaluate the ability of the network to
ensure UE’s 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
All Rights Reserved © Alcatel-Lucent 200941 | Performance Monitoring Overview | Jan 2009
3G-2G CS Handover
All Rights Reserved © Alcatel-Lucent 200942 | Performance Monitoring Overview | Jan 2009
3G-2G CS Handover
Successful case
UE Node B RNC CN - CS
Handover from UTRAN Command
BSS
Relocation Command
Radio Link Deletion Request
Radio Link Deletion Response
Relocation Required
Physical information
Measurement Report
Handover Access
Handover Complete
Iu Release Command
Iu Release Complete
Decision for HHO
Released
….
3G2G CS HHO Preparation Phase3G2G CS HHO Preparation Phase3G2G CS HHO Preparation Phase3G2G CS HHO Preparation Phase
3G2G CS HHO Execution Phase3G2G CS HHO Execution Phase3G2G CS HHO Execution Phase3G2G CS HHO Execution Phase
All Rights Reserved © Alcatel-Lucent 200943 | Performance Monitoring Overview | Jan 2009
UE Node B RNC CN - CS
Handover from UTRAN Command
BSS
Relocation Command
Radio Link Deletion Request
Radio Link Deletion Response
Relocation Required
Physical information
Measurement Report
Handover Access
Handover Complete
Iu Release Command
Iu Release Complete
Decision for HHO
Released
….
#0164 3g to 2g ho detection from fddcell
#0556 Iu relocation required
#0557 Iu relocation command
#0154 HO from UTRAN command
#0505 Iu Release Command
3G-2G CS Handover (Successful case)
3G2G CS HHO preparation success rate
RNC
RNC
Location
3Gto3GCs
3Gto3GPs
3Gto2GCs
CUMVS.IuRelocationCommands: Number of relocation commands at Iu interface.#0557
3Gto3GCs
3Gto3GPs
3Gto2GCs
CUMVS.IuRelocationRequired: Number of relocation required at Iu interface.#0556
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200944 | Performance Monitoring Overview | Jan 2009
Iu Relocation Command in CS domain
Number of Iu Relocation Required in CS domain
3G2G CS HHOpreparation success rate =
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
#0557.[2]
#0556.[2]
3G2G CS HHOpreparation success rate =
All Rights Reserved © Alcatel-Lucent 200945 | Performance Monitoring Overview | Jan 2009
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
Rate of 3G2G CS HHO detection leading to a HHO
All Rights Reserved © Alcatel-Lucent 200946 | Performance Monitoring Overview | Jan 2009
UE Node B RNC CN - CS
Handover from UTRAN Command
BSS
Relocation Command
Relocation Required
Physical information
Measurement Report
Handover Access
Handover Complete
Decision for HHO….
#0164 3g to 2g ho detection from fddcell
#0165 3g to 2g ho detection from fddcell on Neighb Rnc
#0556 Iu relocation required
#0557 Iu relocation command
#0154 HO from UTRAN command#0155 HO from UTRAN command on Neighb Rnc
3G-2G CS Handover (Successful case)
Rate of 3G2G CS HHO detection leading to a HHO
Reference FddCell
Neighboring RNC
Reference FddCell
Neighboring RNC
Location
HO causeCUMVS.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.
#0164
#0165
HO causeCUMVS.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.
#0154
#0156
#0155
#0157
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200947 | Performance Monitoring Overview | Jan 2009
∑ #0154.[0] + #0156.[0] + #0155.[0] + #0157.[0]
∑ #0164.[0] + #0165.[0]
∑ #0154.[0] + #0156.[0]
∑ #0164.[0]
At RNC Level
Success RateCell Level =
Success RateRNC Level =
At Cell Level
Rate of 3G2G CS HHO detection leading to a HHO
VS.RrcHoFromUtranCmdTrigByEcNoNRnc#0155
VS.RrcHoFromUtranCmdTrigByRscp#0156
VS.RrcHoFromUtranCmdTrigByEcNo#0154
VS.RrcHoFromUtranCmdTrigByRscpNRnc#0157
VS.3gto2gHoDetectionFromFddcell#0164
VS.3gto2gHoDetectionFromFddcellNeighbRnc#0165
CountersID
Rescue PS1
Service2
No Resource Available (CAC
Failure)
3
Rescue CS0
Ho CauseScreening
All Rights Reserved © Alcatel-Lucent 200948 | Performance Monitoring Overview | Jan 2009
3G-2G CS Handover
Failure on target system
UE Node B RNC CN - CS BSS
Handover from UTRAN Command
Relocation Command
Relocation Required
Measurement Report
Handover failure on the target system
Handover from UTRAN Failure
…
Relocation Cancel
#0160 HO From UTRAN Failure#0161 HO From UTRAN Failure on Neighb Rnc
#0154 HO from UTRAN command#0155 HO from UTRAN command on Neighb Rnc
Reference FddCell
Neighboring RNC
Reference FddCell
Neighboring RNC
Location
Rescue CS
Service CS
CAC Failure
CUMVS.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.
#0160
#0161
Rescue CSCUMVS.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.
#0154
#0156
#0155
#0157
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200949 | Performance Monitoring Overview | Jan 2009
∑ #0160.[0]
∑ #0154.[0] + #0156.[0]
∑ #0160.[0] + ∑ #0161.[0]
∑ #0154.[0] + #0156.[0] + #0155.[0] + #0157.[0]
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 � Issues on the target
2G Network have to be detected
Failure RateRNC Level =
Failure RateCell Level =
3G2G HHO CS execution failure rate
2G side
All Rights Reserved © Alcatel-Lucent 200950 | Performance Monitoring Overview | Jan 2009
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
3G2G HHO CS execution failure rate
3G side
0: Rescue CS
1: Service CS
2: CAC Failure
Reference
FddCell
CUMVS.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.
#0160
Reference
FddCell
Reference
FddCell
Location
Rescue Cs / PS
Service Cs / PS
CAC Failure CS / PS
CUMVS.3gto2gOutHoSuccess: This measurement provides the number of successful
3G to 2G outgoing Handovers.
#0167
Rescue CSCUMVS.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.
#0154
#0156
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200951 | Performance Monitoring Overview | Jan 2009
CS 3G2G HHO Execution failure
rate (3G side)= 1-
3g to 2g Out Ho Success
HO From UTRAN Command - HO From UTRAN failure
CS 3G2G HHO Execution failure
rate (3G side)= 1-
∑ #0154.[0] + #0156 .[0] - #0160.[0] - #0167.[0] Number of CS calls
lost during 3G2G HHO =
This metric is the Rate of execution 3G2G handover failure due to call lost, and is
computed at Cell Level
3G2G HHO CS execution failure rate
3G side
∑ #0167.[0]
∑ #0154.[0] + #0156 .[0] - #0160.[0]
All Rights Reserved © Alcatel-Lucent 200952 | Performance Monitoring Overview | Jan 2009
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
3g to 2g Out Ho Success
3G2G HHO Detections
Global HHO 3G2GCS success rate =
∑ #0167.[0]
∑ #0164.[0]
Global HHO 3G2GCS success rate =
Rescue Cs / PS
Service Cs / PS
CAC Failure CS / PS
Reference
FDDCell
CUMVS.3gto2gOutHoSuccess: This measurement provides the number of
successfull 3G to 2G outgoing Handovers.
#0167
Reference
FddCell
Location
HO causeCUMVS.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.
#0164
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200953 | Performance Monitoring Overview | Jan 2009
3G-2G PS Handover
All Rights Reserved © Alcatel-Lucent 200954 | Performance Monitoring Overview | Jan 2009
3G-2G PS Handover
Successful case
UE Node B RNC 3G SGSN
Cell Change Order from UTRAN
2G SGSN
Radio Link Deletion Request
Radio Link Deletion Response
RA update response
Measurement Report
RA update request
Iu Release Command
Iu Release Complete
Decision for HHO
….
#0164 3g to 2g ho detection from fddcell PS
#0162 Cell Change Order from UTRAN
#0506 Iu Release Command PSSRNS Data Forward Command
All Rights Reserved © Alcatel-Lucent 200955 | Performance Monitoring Overview | Jan 2009
3G-2G PS Handover
Failure case
UE Node B RNC
Cell Change Order from UTRAN
Measurement Report
Decision for HHO
#0164 3g to 2g ho detection from fddcell
#0162 Cell Change Order from UTRAN#0106 Cell Change Order from UTRAN Neigh RNC
#0163 Cell Change Order from UTRAN Failure#0108 Cell Change Order from UTRAN Failure N-RNCCell Change Order from UTRAN Failure
0: Rescue PS
1: Service PS
2: CAC Failure
Reference
FddCell
CUMIRATHO.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.
#0163
0: Rescue PS
1: CAC Failure
Neighboring
RNC
CUMVS.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.
#0108
Neighboring
RNC
Reference
FddCell
Location
0: Rescue PS
1: CAC Failure
CUMVS.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.
#0106
0: Rescue PS
1: Service PS
2: CAC Failure
CUMIRATHO.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.
#0162
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200956 | Performance Monitoring Overview | Jan 2009
3G2G HHO PS 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 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 �Issues on the target 2G
Network have to be detected
#0163.[0] + #0108.[0]
#0162.[0] + #0106.[0]
Failure RateRNC Level =
#0163.[0] #0162.[0]
Failure RateCell Level =
VS.RrcCellChangeOrderNeighbRnc#0106
IRATHO.FailOutPSUTRAN#0163
VS.RrcCellChangeOrderFailureNeighbRnc#0108
IRATHO.AttOutPSUTRAN#0162
CountersID
All Rights Reserved © Alcatel-Lucent 200957 | Performance Monitoring Overview | Jan 2009
3G-3G Hard Handover
All Rights Reserved © Alcatel-Lucent 200958 | Performance Monitoring Overview | Jan 2009
UE Serving Node B
Serving RNC
CN
Radio Bearer Reconfiguration
Relocation RequestRadio Link Setup Request
Radio Link Setup Response
Relocation Required
SCCP Connection Request
Target Node B
Target RNC
SCCP Connection Confirm
Relocation Request Acknowledge
Relocation Command
Radio Bearer Reconfiguration CompleteRelocation Detect
Relocation Complete
Iu Release CommandRadio Link Deletion Request
Radio Link Deletion ResponseIu Release Complete
Released
#0535 Iu Relocation Requests
#0536 Iu Relocation Requests failures CS
#0537 Iu Relocation Requests failures PS
Relocation preparation
Relocation execution
#0569 Iu Relocation Complete
3G-3G Handover
Successful case
All Rights Reserved © Alcatel-Lucent 200959 | Performance Monitoring Overview | Jan 2009
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]
All Rights Reserved © Alcatel-Lucent 200960 | Performance Monitoring Overview | Jan 2009
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])
All Rights Reserved © Alcatel-Lucent 200961 | Performance Monitoring Overview | Jan 2009
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
All Rights Reserved © Alcatel-Lucent 200962 | Performance Monitoring Overview | Jan 2009
Other Mobility Metrics
HHO 3G3G Inter PLMN Outgoing HHO success rate
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
All Rights Reserved © Alcatel-Lucent 200963 | Performance Monitoring Overview | Jan 2009
3G-3G Soft Handover
All Rights Reserved © Alcatel-Lucent 200964 | Performance Monitoring Overview | Jan 2009
3G-3G Soft Handover
UE Node B RNC
Active Set Update
Measurement Report
#0415 Active Set Update Complete#0402 Active Set Update UnsuccessActive Set Update Complete
FddCell
FddCell
Location
0: Failure
1: Timeout
CUMVS.RrcActiveSetUpdateUnsuccess: Number of unsuccessful RRC ACTIVE SET UPDATE due
to procedure failure or timer expiry.
#0402
CUMVS.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.
#0415
ScreeningTypeDefinitionID
RL Setup Request
RL Setup Respond
All Rights Reserved © Alcatel-Lucent 200965 | Performance Monitoring Overview | Jan 2009
∑ #0402.[0 - 1]
∑ #0402.[0 - 1] + #0415
SHO 3G-3Gsuccess rate =
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.
1 -
AS Update Unsuccess
AS Update Unsuccess + AS Update Complete
SHO 3G-3Gsuccess rate = 1 -
All Rights Reserved © Alcatel-Lucent 200966 | Performance Monitoring Overview | Jan 2009
Mean Sector per User
All Rights Reserved © Alcatel-Lucent 200967 | Performance Monitoring Overview | Jan 2009
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:
� 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)
Reference
FddCell
Location
Number of
radio links
[1..6]
NiRLiRciSBtsiABts
LoadVS.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.
#0025
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200968 | Performance Monitoring Overview | Jan 2009
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
[(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)]
Mean Sector Per User =
All Rights Reserved © Alcatel-Lucent 200969 | Performance Monitoring Overview | Jan 2009
Congestion / Load Metrics
4
All Rights Reserved © Alcatel-Lucent 200970 | Performance Monitoring Overview | Jan 2009
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
All Rights Reserved © Alcatel-Lucent 200971 | Performance Monitoring Overview | Jan 2009
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
#404(all causes except Time Out)
Σ409.[RRC Call screenings]
RRC connection Reject rate
(system view)=
RRC Connection Blocking
Unspecified3
unavailable dl code resources1
unavailable dl power resources2
timeout0
Cell Fach Unspecified CAC5
Overload6
3G to 2G Redirection for Emergency Calls7
RRC context CAC, pegged when CAC fails8
Unavailable FACH context resource, FACH context exhausted10
Unavailable RRC context resource, RRC context exhausted9
Lack of C-RNTI12
No answer from the NodeB11
UE Ec/No lower than qQualityMin13
RSSI4
Causes for RRC Failures
Establishment causeFddCellCUMRRC.AttConnEstab: Number of RRC connection request received. #0409
FddCell
FddCell
Location
Failure causeCUMRRC.FailConnEstab: Number of RRC connection establishment failures.#0404
Establishment causeCUMRRC.SuccConnEstab: Number of RRC connections successfully established.#0403
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200972 | Performance Monitoring Overview | Jan 2009
UE Node B RNC CN
RAB Assignment Request
S.R.L.R. Procedure
Radio Bearer Setup
Radio Bearer Setup Complete
RAB Assignment Response
#0677 RAB assignment setup unsuccess#0672 RAB Assignment Success Per Requested RAB type#0673 RAB Assignment Success Per Granted RAB type
#0671 RAB Assignment Request
#0687 RB Setup Success
#0602 RB Setup Unsuccess
Accessibility: call establishment flow (Cell-DCH case)
RAB Establishment Phase & Associated Counters
TargetCall TypeReference
Fddcell
CUMVS.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)
#0691
Failure causeReference
Fddcell
CUMVS.RadioBearerEstablishmentUnsuccess: Number of Radio-Bearer establishments that
have been rejected by the RNC (no RB Setup Request sent).
#0631
Reference
FddCell
Reference
FddCell
Location
Failure causeCUMVS.RadioBearerSetupUnsuccess: Number of Radio Bearers not successfully setup.#0602
TargetCall TypeCUMVS.RadioBearerSetupSuccess: Number of Radio Bearers successfully setup.#0687
ScreeningTypeDefinitionID
Internal RRM decision to assign resources
#0691 RB Setup Request
#0631 RB Establishment unsuccess
All Rights Reserved © Alcatel-Lucent 200973 | Performance Monitoring Overview | Jan 2009
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
Radio Bearer Blocking rate
= RB establishment unsuccess /
RB to be setup
= ∑#0631 / ∑#0691
Mean Radio Bearer Blocking Rate
0
20000
40000
60000
80000
100000
120000
140000
15/03/2006 22/03/2006 29/03/2006 05/04/2006 12/04/2006
0.00%
1.00%
2.00%
3.00%
4.00%
5.00%
6.00%
7.00%
8.00%
9.00%
10.00%
RAB Requests RB Blocking Rate
All Rights Reserved © Alcatel-Lucent 200974 | Performance Monitoring Overview | Jan 2009
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.
� 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
� Step4:
� Screening 3: Unspecified
� Screening 4 & 5 � unused ; 7 & 8 not incremented
RAB Matching
RAB to RB mapping
Request RAB
Resource reservation&
Call Admission Control
Matched RAB
Granted RB
Resource allocation
RL Reconfiguration
RB Setup
1
2
3
4
5
RL Reconfigured
RB SetupSuccess
RAB Matching
RAB to RB mapping
Request RAB
Resource reservation&
Call Admission Control
Matched RABs
Granted RB
Resource allocation
RL Reconfiguration
RB Setup
RL Reconfigured
RB SetupSuccess
1
2
3
4
5
Radio Bearer Blocking rate
= ∑#0631 [1-3,6,9-14] / ∑#0691
All Rights Reserved © Alcatel-Lucent 200975 | Performance Monitoring Overview | Jan 2009
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).
Impacted by HSDPA
FddcellLoadVS.IrmPreemptionTimeCellColorCongestedBecauseOfPower: Ratio of time a cell is considered to be
congested because of power consumption by the iRM during a reporting period (Average value).
#1138
FddcellLoadVS.IrmPreemptionTimeCellColorCongestedBecauseOfOvsfCodes: Ratio of time a cell is considered to be
congested because of OVSF codes by the iRM during a reporting period.
#1137
FDDCellLoadVS.IrmTimeDlIubTransportColorRed: This measurement provides the ratio of time a cell is considered
red for Downlink IubTransport by iRM during a reporting period
#1182
Fddcell
FddCell
Location
LoadVS.IrmPreemptionTimeCellColorCongested: Ratio of time a cell is considered to be congested by the Irm
during a reporting period.
#1136
LoadVS.IRMTimeCellColorRed: Percentage of time during a collection period that a particular cell is
considered red by iRM.
#1124
TypeDefinitionID
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
All Rights Reserved © Alcatel-Lucent 200976 | Performance Monitoring Overview | Jan 2009
Traffic Metrics
5
All Rights Reserved © Alcatel-Lucent 200977 | Performance Monitoring Overview | Jan 2009
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
All Rights Reserved © Alcatel-Lucent 200978 | Performance Monitoring Overview | Jan 2009
The average number of calls (RAB established) is based on the counter:
� 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]
This metric can only be monitored at RNC level
Is screened per granted RAB
Average Number of calls
RNC Level
Load
Type
RAB type
Screening
RNCVS.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.
#0675
LocationDefinitionID
All Rights Reserved © Alcatel-Lucent 200979 | Performance Monitoring Overview | Jan 2009
Average Number of calls
Cell Level
� 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]
The average number of calls (RAB established) at Cell Level is based on the counter:
It is screened per AsConfId (UserService)
Reference
FDDCell
Reference
FDDCell
Location
UlAsConfLoadVS.UlAsConfIdAvgNbrEstablished: Indicates an average of the number of UlAsConfIds
established per iRNC, based on time average over collection period.
#0693
DlAsConfLoadVS.DlAsConfIdAvgNbrEstablished: Indicates an average of the number of DlAsConfIds
established per iRNC, based on time average over collection period.
#0692
ScreeningTypeDefinitionID
All Rights Reserved © Alcatel-Lucent 200980 | Performance Monitoring Overview | Jan 2009
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 :
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
RNC
RNC
Location
RBSet DL Bit
rate
CUMVS.DedicatedDownlinkKbytesRlc: Total count of downlink RLC payload (SDU) sent on
dedicated channels.
#1473
RBSet UL Bit
rate
CUMVS.DedicatedUplinkKbytesRlc: Total count of uplink RLC payload (SDU) received on
dedicated channels.
#1472
ScreeningTypeDefinitionID
Screening 12: HSUPA
All Rights Reserved © Alcatel-Lucent 200981 | Performance Monitoring Overview | Jan 2009
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 :
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]
Fddcell
Fddcell
Location
RBSet DL Bit
rate
CUMVS.DedicatedDownlinkKbytesRlcActiveCells: Total number of Kbytes of RLC SDU sent on
downlink on dedicated channels for each cell of the active set.
#1485
RBSet UL Bit
rate
CUMVS.DedicatedUplinkKbytesRlcActiveCells: Total number of Kbytes of RLC SDU received
on uplink on dedicated channels for each cell of the active set.
#1484
ScreeningTypeDefinitionID
Screening 6: HSDPA
Screening 12: HSUPA
All Rights Reserved © Alcatel-Lucent 200982 | Performance Monitoring Overview | Jan 2009
Quality Metrics
6
All Rights Reserved © Alcatel-Lucent 200983 | Performance Monitoring Overview | Jan 2009
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
All Rights Reserved © Alcatel-Lucent 200984 | Performance Monitoring Overview | Jan 2009
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
RNC
RNC
Loc.
dlRbSetIdCUMVS.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).
#1140
#1142
#1144
CUM
Type
dlRbSetIdVS.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).
#1139
#1141
#1143
ScreeningDefinitionID
These metrics are computed at RNC level per DlRBsetId
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
Number of I/B RB downgraded by iRM Preemption = #1139 + #1141 + #1143
Number of I/B RB rejected by iRM Preemption = #1140 + #1142 + #1144 Screening HSDPA: 17,20
All Rights Reserved © Alcatel-Lucent 200985 | Performance Monitoring Overview | Jan 2009
Always – On
UE Node B RNC CN
RRC / Radio Bearer Reconfiguration
RRC / Radio Bearer Reconfiguration Complete
S.R..L. R. procedure
Downsizing (Step 1) / Upsizing
#685 Radio Bearer Reconfigure Request
# 684 Radio Bearer Reconfiguration Success # 1159 Downsizing Step1 Success# 1165 Upsizing Success
dlAsConfIdRef. FddCellCUMVS.UpsizingSuccess: Number of successful upsizing from always on step1.#1165
dlAsConfIdNeighboring
RNC
CUMVS.DownsizingStep1UnsuccessNeighbRnc: Number of unsuccessful always on downsizing
step1 for calls having their primary cell located on a neighboring RNC.
#1162
dlAsConfIdRef. FddCellCUMVS.DownsizingStep1Unsuccess: Number of unsuccessful always on downsizing step1.#1161
dlAsConfIdNeighboring
RNC
CUMVS.DownsizingStep1SuccessNeighbRnc: Number of successful always on downsizing step1 for
calls having their primary cell located on a neighboring RNC.
#1160
dlAsConfIdNeighboring
RNC
CUMVS.UpsizingSuccessNeighbRnc: Number of successful upsizing from always on step1 for calls
having their primary cell located on a neighboring RNC.
#1166
dlAsConfIdRef. FddCellCUMVS.UpsizingUnsuccess: Number of unsuccessful upsizing from always on step1.#1167
Neighboring
RNC
Ref. FddCell
Location
dlAsConfIdCUMVS.UpsizingUnsuccessNeighbRnc: Number of unsuccessful upsizing from always on step1 for
calls having their primary cell located on a neighboring RNC.
#1168
CUM
Type
dlAsConfIdVS.DownsizingStep1Success: Number of successful always on downsizing step1.#1159
ScreeningDefinitionID
All Rights Reserved © Alcatel-Lucent 200986 | Performance Monitoring Overview | Jan 2009
Always – On
UE Node B RNC CN
RRC / RRC Connection Release
RRC / RRC Connection Release Complete
RANAP / IU Release Request
RANAP / IU Release Command
RANAP / IU Release Complete
SCCP Released
Downsizing to Idle mode (Step 2)
# 676 VS.RabNormalRelease per granted RAB
# 577 Iu Release Request Ps Always On Downgrade
# 506 Iu Release Command Ps .ReleaseDueToUtranGeneratedReason
# 405 RrcConnectionRelease.UserInactivity
Neighboring RNC
Reference
FddCell
Location
dlAsConfIdCUMVS.DownsizingStep2SuccessNeighbRnc: Number of successful always on downsizing
step2 for calls having their primary cell located on a neighboring RNC.
#1164
CUM
Type
dlAsConfIdVS.DownsizingStep2Success: Number of successful always on downsizing step2.#1163
ScreeningDefinitionID
All Rights Reserved © Alcatel-Lucent 200987 | Performance Monitoring Overview | Jan 2009
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 DlAsConfIdDownsizing step 2 vs downsizing step 1 (Source DlAsConfId) =
(# 1163 + #1164) / (#1159 +#1160)
Upsizing attempts (Target DlAsConfId) vs. downsizing step 1 (source DLAsconfid) =
(#1165 +#1166+ #1167 +#1168 ) / (#1159 +#1160) Available for HSDPA
Impacted by HSDPA
Included in global metric
All Rights Reserved © Alcatel-Lucent 200988 | Performance Monitoring Overview | Jan 2009
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)
� 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
FDDCell (Reference)
FDDCell (Reference)
Location
DlAsConfCUMVS.IRMSchedulingDowngradedFailure: This measurement provides the
number of failed RB throughput downgrades based on TxCP encountered by
the iRM scheduling feature.
#1170
CUM
Type
DlAsConfVS.IRMSchedulingDowngradedSuccess: This measurement provides the
number of success RB throughput downgrades based on TxCP encountered by
the iRM scheduling feature.
#1169
ScreeningDefinitionID
All Rights Reserved © Alcatel-Lucent 200989 | Performance Monitoring Overview | Jan 2009
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
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
Not applicable for HSDPA
RNCCUMVS.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).
#1132
high Bitrate
Intermediate
Bitrate
RNCCUMVS.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).
#1174
RNCCUMVS.IrmUpgradingDeactivation: Number of times iRM Scheduling Upgrading was deactivated
while the DL transmitted power was monitored.
#1134
RNC
RNC
Location
dlAsConIdCUMVS.IrmUpgradingSuccessful: Number of times the iRM Upgrading was successfully executed
(upgrading to a high or intermediate bit rate).
#1173
CUM
Type
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).
#1131
ScreeningDefinitionID
All Rights Reserved © Alcatel-Lucent 200990 | Performance Monitoring Overview | Jan 2009
www.alcatel-lucent.com