wcdma rno huawei umts kpi
TRANSCRIPT
11
UTRAN Key Performance Indicators
20040515
UTRAN Key Performance Indicators
20040515
22
IntroductionIntroduction
These slides focus only on initial UTRAN KPIs.
There is a comprehensive list of raw counters fro
m which these initial KPIs are produced.
The counters as well as KPIs will continuously be
redefined and updated.
33
UTRAN KPI OverviewUTRAN KPI Overview
Call Setup Success Rate
Call Drop Rate of Signaling Plane
Call Drop Rate of User Plane
Signaling Congestion Rate
Traffic Congestion Rate
Soft Handover Success Rate
Hard Handover Success Rate
Inter-RAT Hard Handover Success Rate
44
ContentsContents
Call Setup
Call Drop
Congestion
Handover
Traffic
55
Call Setup Success RateCall Setup Success Rate
Formula of Call Setup Success Rate:
Call Setup Success Rate = RRCSetupSuccRate ×
RABSetupSuccRate ×100%
Can be divided into two parts: CS&PS
For four types of QoS:
Conversational (e.g. voice and video)
Streaming (e.g. streaming video or audio)
Interactive (e.g. browsing)
Background (e.g. emails or file download)
66
RRC Setup Success RateRRC Setup Success Rate
The formula of RRC Setup Success Rate:
RRC Setup Success Rate = RRC Connection Setup Success / RR
C Connection Request × 100%
RRC Setup Reject Causes:
Congestion (Walsh, Power, CE, etc.)
Unspecified (mostly transmission or NodeB problem)
Other RRC Setup failure reason
UE can’t receive RRC CONNECTION SETUP
NodeB can’t receive RRC CONNECTION SETUP COMPLETE
77
RRC Connection SetupRRC Connection Setup
UE SRNC
RRC RRC
RRC
RRC
RRC
RRCRRC Connection Setup Complete
NODEB
NBAP NBAP
NBAP NBAP
Radio Link Setup Requset
Radio Link Setup Response
RRC Connection Request
RRC Connection Setup
88
ExampleExample
RRC_REQ 3332
RRC_REJ 2
RRC_REJ_CONG 0
RRC_SETUP 3330
RRC_SETUP_SUCC 3184
RRC_SETUP_SUCC_RATE 95.56%
UE can’t receive RRC CONNECTION SETUP
The downlink channel transmit power is not enough or the UE receive sensitivity i
s not good.
NodeB can’t receive RRC CONNECTION SETUP COMPLETE
The UE transmit power is not enough or the NodeB receive sensitivity is not goo
d.
99
RAB Setup Success RateRAB Setup Success Rate
The formula of RAB Setup Success Rate:
RAB Setup Success Rate = RAB Assignment Success / RAB
Assignment Request × 100%
Can be divided into two parts, for four types of QoS
RAB Setup Failure Causes: Parameter violation
Non supported UTRAN capabilities
Relocation triggered
Transport connection failed to establish
Unavailable resources
Protocol error
1010
RAB Setup Flow Chart RAB Setup Flow Chart
UE SRNCNodeB CN
RANAP RANAPRAB Assignment Request
RRCRRC
RRC
RB Setup
RRCRB Setup Complete
RANAP RANAPRAB Assignment Response
NBAP NBAPRL Reconfig Prepare
NBAP NBAP
NBAP NBAP
RL Reconfig Ready
RL Reconfig Commit
1111
ExampleExample
RB_SETUP 1057
RB_SETUP_SUCC 1054
CS_RAB_REQ_SETUP_CONV 982
CS_RAB_SETUP_SUCC_CONV 979
PS_RAB_REQ_SETUP_BKG 75
PS_RAB_SETUP_SUCC_BKG 75
CS_RAB_SETUP_SUCC_RATE_CONV 99.69%
PS_RAB_REL_SUCC_RATE_BKG 100.00%
RB_SETUP_SUCC_RATE_CONV 99.72%
1212
ContentsContents
Call Setup
Call Drop
Congestion
Handover
Traffic
1313
Call Drop Rate of Signaling PlaneCall Drop Rate of Signaling Plane
Call Drop Rate of Signaling Plane is calculated by
counting RNC-originated Iu connection release.
Can be divided into two parts: CS&PS
RNC-originated Iu connection release Causes: OM intervention
User inactivity
Repeated integrity checking failure
UE generated signaling connection release
RL out-of-synchronization
1414
Call Drop Rate of Signaling PlaneCall Drop Rate of Signaling Plane
The formula of Call Drop Rate of CS Signaling Plane:
Call Drop Rate of CS Signaling Plane = RNC-originated CS Domain
Iu Connection Release / RNC-originated CS Domain Iu Connection
Setup Success× 100%
The formula of Call Drop Rate of PS Signaling Plane:
Call Drop Rate of PS Signaling Plane = RNC-originated PS Domain
Iu Connection Release / RNC-originated PS Domain Iu Connection
Setup Success× 100%
1515
RNC-originated Iu connection release Flow ChartRNC-originated Iu connection release Flow Chart
SRNC CN
RANAP RANAP
RANAP RANAP
RANAP RANAP
Iu Release Request
Iu Release Command
Iu Release Complete
1616
ExampleExample
RNC_CS_IU_REL 50 RNC_PS_IU_REL 51
RNC_CS_IU_REL_DUP_INTEG 0 RNC_PS_IU_REL_DUP_INTEG 0
RNC_CS_IU_REL_OM 0 RNC_PS_IU_REL_OM 0
RNC_CS_IU_REL_RL_FAIL 26 RNC_PS_IU_REL_RL_FAIL 18
RNC_CS_IU_REL_SIG_REL 5 RNC_PS_IU_REL_SIG_REL 22
RNC_CS_IU_REL_UE_INACT 0 RNC_PS_IU_REL_UE_INACT 0
RNC_CS_IU_SETUP 3085 RNC_PS_IU_SETUP 251
Call Drop Rate of CS Signaling1.62
%Call Drop Rate of PS Signaling 20.32%
For Call Drop Rate of PS Signaling, the main reason is wrong APN configuration in UE
For RL_FAIL, need optimize poor coverage and neighbors, 3G-2G handover
also can improve this indicator
1717
Call Drop Rate of User PlaneCall Drop Rate of User Plane
Call Drop Rate of User Plane is calculated by
counting RNC-originated RAB releases.
Can be divided into two parts, for four types of
QoS
RNC-originated RAB release Causes:
OM intervention
UTRAN generated reason
RAB preempted
1818
Call Drop Rate of User PlaneCall Drop Rate of User Plane
The formula of Call Drop Rate of CS User Plane:
Call Drop Rate of CS User Plane = RNC-originated CS Domain RAB
Release / RNC-originated CS Domain RAB Setup Success × 100%
The formula of Call Drop Rate of PS User Plane:
Call Drop Rate of PS User Plane = RNC-originated PS Domain RAB
Release / RNC-originated PS Domain RAB Setup Success × 100%
1919
RNC-originated RAB release CauseRNC-originated RAB release Cause
UE SRNC CN
RANAP RANAP
RANAPRANAP
RRC
RANAP
RAB Release Request
Iu Release Command
RANAP Iu Release Complete
RRC
RRC RRC
RRC Connection Release
RRC Connection Release Complete
2020
ExampleExample
CS_RAB_SETUP_SUCC_CONV 979
PS_RAB_SETUP_SUCC_BKG 75
RNC_CS_RAB_REL_REQ_CONV 4
RNC_PS_RAB_REL_REQ_BKG 4
Call Drop Rate of CS User Plane 0.41%
Call Drop Rate of PS User Plane 5.33%
For CS/PS_RAB_REL, need optimize poor coverage and neighbors, 3G-2G handover
also can improve this indicator
2121
ContentsContents
Call Setup
Call Drop
Congestion
Handover
Traffic
2222
Signaling Congestion RateSignaling Congestion Rate
The formula of Signaling Congestion Rate:
Signaling Congestion Rate = RRC Connection Reject (Cause:
congestion) / RRC Connection Request × 100%
UE RNCNodeB
RRC RRCRRC Connection Request
RRC RRC Connection Reject (Cause : Congestion) RRC
2323
Traffic Congestion RateTraffic Congestion Rate
Traffic Congestion Rate is calculated by counting
the RAB Assignment Setup Failure (cause:
congestion).
Can be divided into two parts: CS&PS
2424
Traffic Congestion RateTraffic Congestion Rate
The formula of CS Traffic Congestion Rate:
CS Traffic Congestion Rate = CS Domain RAB Assignment Setup
Failure (Congestion) / CS Domain RAB Assignment Setup Request
× 100%
The formula of PS Traffic Congestion Rate:
PS Traffic Congestion Rate = PS Domain RAB Assignment Setup
Failure (Congestion) / PS Domain RAB Assignment Setup Request
× 100%
2525
Traffic Congestion RateTraffic Congestion Rate
SRNC CN
RANAP RANAPRAB Assignment Request
RANAP RANAPRAB Assignment Response (Failure cause: Congestion)
2626
ContentsContents
Call Setup
Call Drop
Congestion
Handover
Traffic
2727
Soft (Softer) Handover Success RateSoft (Softer) Handover Success Rate
The formula of Soft (Softer) Handover Success Rate:
Soft (Softer) Handover Success Rate = Soft (Softer) Handover
Success / Soft (Softer) Handover Request× 100%
2828
Soft (Softer) Handover Flow ChartSoft (Softer) Handover Flow Chart
UE New NodeB SRNC
NBAP NBAP
NBAP NBAP
RRC RRC
RRCRRC DCCH : Active Set Update Complete
Radio Link Addition Request
DCCH : Active Set Update
Radio Link Addition Response
2929
SHO Failure CausesSHO Failure Causes
When the UE handles the ACTIVE SET UPDATE message, the abnor
mal cases may be occurred and the UE shall transmit an ACTIVE SE
T UPDATE FAILURE message with the following failure causes : Configuration unsupported
Incompatible simultaneous reconfiguration
Protocol error
Invalid configuration
If the time expired before RNC receives the message ACTIVE SET U
PDATE COMPLETE or ACTIVE SET UPDATE FAILURE from UE, R
NC increases the SHO failure counter with the following cause : No response from UE
3030
SHO Failure Flow ChartSHO Failure Flow Chart
UE New NodeB SRNC
NBAP NBAP
NBAP NBAP
RRC RRC
RRCRRC DCCH : Active Set Update Failure
Radio Link Addition Request
DCCH : Active Set Update
Radio Link Addition Response
3131
ExampleExample
SHO_EVAL_REQ 5652
SHO 5511
SHO_SUCC 5500
SOFTERHO 1411
SOFTERHO_SUCC 1411
SHO_SUCC_RATE 99.8%
3232
Hard Handover Success RateHard Handover Success Rate
The formula of Hard Handover Success Rate:
Hard Handover Success Rate = Hard Handover Success / Hard
Handover request× 100%
3333
Hard Handover Flow ChartHard Handover Flow Chart
UE Target NodeBSource NodeB SRNC
RRC
NBAPNBAP Radio Link Setup Request
NBAP NBAPRadio Link Setup Reponse
RRCDCCH : Physical Channel Reconfiguration
NBAPNBAP Radio Link Failure Indication
RRC RRCDCCH : Physical Channel Reconfiguration Complete
NBAP NBAPRadio Link Deletion Request
NBAP NBAPRadio Link Delete Response
3434
Hard Handover Failure CauseHard Handover Failure Cause The detail hard handover failure cause statistics include two hard handover direction
s on the cell object : outgoing hard handover initiated by RNC in each original cell.
incoming hard handover in the target cell initiated by RNC
When the UE handles the PHYSICAL CHANNEL RECONFIGURATION message, th
e abnormal cases may be occurred and the UE shall transmit an PHYSICAL CHAN
NEL RECONFIGURATION FAILURE message with the following failure cause: Configuration unsupported
Physical channel failure
Incompatible simultaneous reconfiguration
Protocol error
Cell update occurred
Invalid configuration
If the time expired before RNC receives the message PHYSICAL CHANNEL RECO
NFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION FAILU
RE from UE, RNC increases the hard handover failure counter with the following cau
se : No response received from UE
3535
Hard Handover Failure Flow ChartHard Handover Failure Flow Chart
UETarget NodeB
(Incoming the Cell)Source NodeB
(Outgoing the Cell)
SRNC
RRC
NBAPNBAP Radio Link Setup Request
NBAP NBAPRadio Link Setup Reponse
RRCDCCH : Physical Channel Reconfiguration
NBAPNBAP Radio Link Failure Indication
RRC RRCDCCH : Physical Channel Reconfiguration Failure
NBAP NBAPRadio Link Deletion Request
NBAP NBAPRadio Link Delete Response
3636
InterRAT Handover to GSM Success RateInterRAT Handover to GSM Success Rate
The formula of InterRAT Handover to GSM Success Rate:
InterRAT Handover to GSM Success Rate = inter-RAT handover from U
TRAN to GSM success / inter-RAT handover from UTRAN to GSM attem
pts × 100%
3737
InterRAT Handover to GSM Flow ChartInterRAT Handover to GSM Flow Chart
UE NodeB RNC
NBAP NBAP
NBAP NBAP
RRC RRC
Handover Complete
Radio Link Deletion Request
Handover From Utran Command
Radio Link Deletion Response
3G MSC 2G MSC BSS
RANAP RANAPRelocation Required
RANAP RANAPRelocation Command
RANAP RANAPIu Release Command
RANAP RANAPIu Release Complete
Prepare Handover
Handover Request
Handover Request Ack
Prepare Handover Response
3838
InterRAT Handover to GSM Failure CauseInterRAT Handover to GSM Failure Cause
When the UE handles the the HANDOVER FROM UTRAN COMMAND me
ssage, the abnormal cases may be occurred and the UE shall transmit an
HANDOVER FROM UTRAN FAILURE message with the following failure
causes : Configuration unacceptable
Physical channel failure
Protocol error
Inter-RAT protocol error
Unspecified
If the time expired before RNC receives the message IU RELEASE COMM
AND from MSC, RNC increases the InterRAT handover to GSM failure cou
nter with the following cause : InterRAT handover to GSM no response
3939
InterRAT Handover to GSM Failure Flow ChartInterRAT Handover to GSM Failure Flow Chart
UE NodeB RNC
RRC RRC
RRC Handover From Utran Failure
Handover From Utran Command
3G MSC 2G MSC BSS
RANAP RANAPRelocation Required
RANAP RANAPRelocation Command
Prepare Handover
Handover Request
Handover Request Ack
Prepare Handover Response
RRC
4040
ExampleExample
CS_INTRAT_HO_OUT_PREP 60
CS_INTRAT_HO_OUT_PREP_SUCC 54
CS_INTRAT_HO_OUT_ATT 54
CS_INTRAT_HO_OUT_SUCC 48
CS_INTRAT_HO_OUT_SUCC_RATE(%) 88.89%
CS_INTRAT_HO_OUT_FAIL_CFG_UNSUPP 0
CS_INTRAT_HO_OUT_FAIL_INTER_RAT_PROTCL 0
CS_INTRAT_HO_OUT_FAIL_NO_RSP 0
CS_INTRAT_HO_OUT_FAIL_PHYCH_FAIL 6
CS_INTRAT_HO_OUT_FAIL_PROTCL 0
CS_INTRAT_HO_OUT_FAIL_RELOC_ABORT 0
CS_INTRAT_HO_OUT_FAIL_UNSPEC 0
Need optimize 3G-2G neighbors and configuration (RNC&CN), 3G-2G handover
parameters for example: Report interval/Inter-RAT handover trigger time/GSM RSSI
threshold/ Hysteresis
4141
InterRAT Handover to GPRS Success RateInterRAT Handover to GPRS Success Rate
The formula of InterRAT Handover to GPRS Success Rate:
InterRAT Handover to GPRS Success Rate = interRAT handover from U
TRAN to GPRS success initiated by UTRAN / interRAT handover from U
TRAN to GPRS attempts initiated by UTRAN × 100%
4242
InterRAT Handover to GPRS Flow Chart - initiated by UTRANInterRAT Handover to GPRS Flow Chart - initiated by UTRAN
UE NodeB RNC
NBAP NBAP
NBAP NBAP
RRC RRC
Route Area Update Request
Radio Link Deletion Request
Cell Change Order From Utran
Radio Link Deletion Response
3G SGSN 2G SGSN BSS
RANAP RANAPSRNS Context Request
RANAP RANAPSRNS Context Response
RANAP RANAPSRNS Data Forward Command
RANAP RANAPIu Release Complete
SGSN Context Request
Update PDP Context Request
Update PDP Context Request
SGSN Context Response
SGSN Context Ack
RANAP RANAPForward Packet
Forward Packet
RANAP RANAPIu Release Command
Route Area Update Accept
4343
InterRAT Handover to GPRS Failure CauseInterRAT Handover to GPRS Failure Cause
When the UE handles the the CELL CHANGE ORDER FROM UTRAN me
ssage, the abnormal cases may be occurred and the UE shall transmit an
CELL CHANGE ORDER FROM UTRAN FAILURE message with the follo
wing failure causes : Configuration unacceptable
Physical channel failure
Protocol error
Unspecified
If the time expired before RNC receives the message SRNS CONTEXT RE
QUEST or IU RELEASE COMMAND from SGSN, RNC increases the Inter
RAT handover to GPRS failure counter with the following cause : InterRAT handover to GPRS no response
4444
InterRAT Handover to GPRS Failure Flow ChartInterRAT Handover to GPRS Failure Flow Chart
UE NodeB RNC
RRC RRCCell Change Order From Utran
3G SGSN 2G SGSN BSS
RRC RRCCell Change Order From Utran Failure
4545
ContentsContents
Call Setup
Call Drop
Congestion
Handover
Traffic
4646
CS TrafficCS Traffic
One Erlang is defined as the one 12.2K CS AMR call lasting
for one hour. The traffic of other different services are
derived by converting to equivalent 12.2K CS AMR call.
CS Traffic for two types of QoS:
CS Conversational Traffic (i.e. voice and video)
CS Streaming Traffic (e.g. streaming video or audio)
CS Traffic for two types of Service:
CS AMR Traffic (Voice)
CS CONV 64k Traffic (Video Phone)
4747
PS TrafficPS Traffic
The traffic of different services are derived by
converting to equivalent 12.2K CS AMR call.
PS Traffic for four types of QoS:
PS Conversational Traffic
PS Streaming Traffic
PS Interactive
Background Traffic
4848
PS ThroughputPS Throughput
PS Throughput for four types of QoS (in Bytes)
PS UL Conversational services Throughput
PS UL Streaming services Throughput
PS UL Interactive services Throughput
PS UL Background services Throughput
PS DL Conversational services Throughput
PS DL Streaming services Throughput
PS DL Interactive services Throughput
PS DL Background services Throughput
4949
Summary (1/3)Summary (1/3)KPI Stage Failure Cause Level
Call Setup Success Rate
RRC Setup Success Rate
- Congestion - Unspecified
RAB Setup Success Rate
- Parameter violation - Non supported UTRAN capabilities - Relocation triggered - Transport connection failed to establish - Unavailable resources - Protocol error
CN domain: - CS- PSQoS Classes:- Conversational- Streaming- Interactive- Background
Call Drop Rate
Signaling Plane
- OM intervention - User inactivity - Repeated integrity checking failure - UE generated signaling connection release - RL out-of-synchronization
-CS- PS
User Plane - OM intervention - UTRAN generated reason - RAB preempted
CN domain: - CS- PSQoS Classes:- Conversational- Streaming- Interactive- Background
Congestion Rate
Signaling Congestion Rate RRC Connection Reject (Cause: congestion)
Traffic Congestion Rate RAB Assignment Setup Failure (cause: congestion). - CS - PS
5050
KPI Stage Failure Cause Level
Soft & Softer Handover
Success Rate
Radio Link Addition - Configuration unsupported - Incompatible simultaneous reconfiguration - Protocol error - Invalid configuration - No response from UE
Radio Link Deletion
Hard Handover Success Rate
- Configuration unsupported - Physical channel failure - Incompatible simultaneous reconfiguration - Protocol error - Cell update occurred - Invalid configuration - No response received from UE
InterRAT Handover to GSM Su
ccess Rate
- Configuration unacceptable - Physical channel failure - Protocol error - Inter-RAT protocol error - Unspecified - InterRAT handover to GSM no response
InterRAT Handover to GPRS S
uccess Rate
- Configuration unacceptable - Physical channel failure - Protocol error - Unspecified - InterRAT handover to GSM no response
- initiated by UTRAN
Summary (2/3)Summary (2/3)
5151
Summary (3/3)Summary (3/3)
KPI Stage Failure Cause Level
CS Traffic Erlang
QoS Classes:- Conversational- StreamingBears- AMR Voice- CS 64K
PS Traffic Erlang
QoS Classes:- Conversational- Streaming- Interactive- Background
PS Throughput Byte
QoS Classes:- Conversational- Streaming- Interactive- Background
5252