UTRAN Key Performance Indicators

20040515

1
 Introduction

 These slides focus only on initial UTRAN KPIs.

 There is a comprehensive list of raw counters
from which these initial KPIs are produced.
 The counters as well as KPIs will continuously be
redefined and updated.

2
 UTRAN 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

3
 Contents

Call Setup

Call Drop

Congestion

Handover

Traffic

4
 Call 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)

5
 RRC Setup Success Rate

 The formula of RRC Setup Success Rate:

RRC Setup Success Rate = RRC Connection Setup Success /
RRC 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

6
 RRC Connection Setup

UE NODEB SRNC

RRC RRC Connection Request RRC

NBAP Radio Link Setup Requset NBAP

NBAP Radio Link Setup Response NBAP

RRC RRC Connection Setup RRC

RRC RRC Connection Setup Complete RRC

7
 Example
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
is not good.
NodeB can’t receive RRC CONNECTION SETUP COMPLETE
The UE transmit power is not enough or the NodeB receive sensitivity is not
good.

8
 RAB 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

9
 RAB Setup Flow Chart

UE NodeB SRNC CN

RANAP RAB Assignment Request RANAP

NBAP RL Reconfig Prepare NBAP

NBAP RL Reconfig Ready NBAP

NBAP RL Reconfig Commit NBAP

RRC RB Setup RRC

RRC RB Setup Complete RRC

RANAP RAB Assignment Response RANAP

10
 Example

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%

11
 Contents

Call Setup

Call Drop

Congestion

Handover

Traffic

12
 Call 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

13
 Call 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%

14
 RNC-originated Iu connection release Flow Chart

SRNC CN

RANAP Iu Release Request RANAP

RANAP Iu Release Command RANAP

RANAP Iu Release Complete RANAP

15
 Example

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 Signaling 1.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

16
 Call 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

17
 Call 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%

18
 RNC-originated RAB release Cause

UE SRNC CN

RANAP RAB Release Request RANAP

RANAP Iu Release Command RANAP

RANAP Iu Release Complete RANAP

RRC RRC Connection Release RRC

RRC RRC Connection Release Complete RRC

19
 Example
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

20
 Contents

Call Setup

Call Drop

Congestion

Handover

Traffic

21
 Signaling Congestion Rate

 The formula of Signaling Congestion Rate:

Signaling Congestion Rate = RRC Connection Reject (Cause:
congestion) / RRC Connection Request × 100%

UE NodeB RNC

RRC RRC Connection Request RRC

RRC RRC Connection Reject (Cause : Congestion) RRC

22
 Traffic Congestion Rate

 Traffic Congestion Rate is calculated by counting

the RAB Assignment Setup Failure (cause:
congestion).
 Can be divided into two parts: CS&PS

23
 Traffic 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%

24
 Traffic Congestion Rate

SRNC CN

RANAP RAB Assignment Request RANAP

RANAP RAB Assignment Response (Failure cause: Congestion) RANAP

25
 Contents

Call Setup

Call Drop

Congestion

Handover

Traffic

26
 Soft (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%

27
 Soft (Softer) Handover Flow Chart

UE New NodeB SRNC

NBAP Radio Link Addition Request NBAP

NBAP Radio Link Addition Response NBAP

RRC DCCH : Active Set Update RRC

RRC DCCH : Active Set Update Complete RRC

28
 SHO Failure Causes

 When the UE handles the ACTIVE SET UPDATE message, the

abnormal cases may be occurred and the UE shall transmit an
ACTIVE SET 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
UPDATE COMPLETE or ACTIVE SET UPDATE FAILURE from UE,
RNC increases the SHO failure counter with the following cause ：
 No response from UE

29
 SHO Failure Flow Chart

UE New NodeB SRNC

NBAP Radio Link Addition Request NBAP

NBAP Radio Link Addition Response NBAP

RRC DCCH : Active Set Update RRC

RRC DCCH : Active Set Update Failure RRC

30
 Example

SHO_EVAL_REQ 5652

SHO 5511

SHO_SUCC 5500

SOFTERHO 1411

SOFTERHO_SUCC 1411

SHO_SUCC_RATE 99.8%

31
 Hard Handover Success Rate

 The formula of Hard Handover Success Rate:

Hard Handover Success Rate = Hard Handover Success / Hard

Handover request× 100%

32
 Hard Handover Flow Chart
UE Source NodeB Target NodeB SRNC

NBAP Radio Link Setup Request NBAP

NBAP Radio Link Setup Reponse NBAP

RRC DCCH : Physical Channel Reconfiguration RRC

NBAP Radio Link Failure Indication NBAP

RRC DCCH : Physical Channel Reconfiguration Complete RRC

NBAP Radio Link Deletion Request NBAP

NBAP Radio Link Delete Response NBAP

33
 Hard Handover Failure Cause
 The detail hard handover failure cause statistics include two hard handover
directions 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,

the abnormal cases may be occurred and the UE shall transmit an PHYSICAL
CHANNEL 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
RECONFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION
FAILURE from UE, RNC increases the hard handover failure counter with the
following cause ：
 No response received from UE

34
 Hard Handover Failure Flow Chart

Source NodeB Target NodeB SRNC

UE
(Outgoing the Cell) (Incoming the Cell)

NBAP Radio Link Setup Request NBAP

NBAP Radio Link Setup Reponse NBAP

RRC DCCH : Physical Channel Reconfiguration RRC

NBAP Radio Link Failure Indication NBAP

RRC DCCH : Physical Channel Reconfiguration Failure RRC

NBAP Radio Link Deletion Request NBAP

NBAP Radio Link Delete Response NBAP

35
 InterRAT Handover to GSM Success Rate

 The formula of InterRAT Handover to GSM Success Rate:

InterRAT Handover to GSM Success Rate = inter-RAT handover from

UTRAN to GSM success / inter-RAT handover from UTRAN to GSM
attempts × 100%

36
 InterRAT Handover to GSM Flow Chart
UE NodeB RNC 3G MSC 2G MSC BSS

RANAP Relocation Required RANAP

Prepare Handover

Handover Request

Handover Request Ack

Prepare Handover Response

RANAP Relocation Command RANAP

RRC Handover From Utran Command RRC

Handover Complete

RANAP Iu Release Command RANAP

RANAP Iu Release Complete RANAP

NBAP Radio Link Deletion Request NBAP

NBAP Radio Link Deletion Response NBAP

37
 InterRAT Handover to GSM Failure Cause
 When the UE handles the the HANDOVER FROM UTRAN COMMAND
message, 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

COMMAND from MSC, RNC increases the InterRAT handover to GSM
failure counter with the following cause ：
 InterRAT handover to GSM no response

38
 InterRAT Handover to GSM Failure Flow Chart

UE NodeB RNC 3G MSC 2G MSC BSS

RANAP Relocation Required RANAP

Prepare Handover

Handover Request

Handover Request Ack

Prepare Handover Response

RANAP Relocation Command RANAP

RRC Handover From Utran Command RRC

RRC Handover From Utran Failure RRC

39
 Example
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
40
 InterRAT Handover to GPRS Success Rate

 The formula of InterRAT Handover to GPRS Success Rate:

InterRAT Handover to GPRS Success Rate = interRAT handover from

UTRAN to GPRS success initiated by UTRAN / interRAT handover from
UTRAN to GPRS attempts initiated by UTRAN × 100%

41
 InterRAT Handover to GPRS Flow Chart - initiated by UTRAN

UE NodeB RNC 3G SGSN 2G SGSN BSS

RRC Cell Change Order From Utran RRC

Route Area Update Request

SGSN Context Request

RANAP SRNS Context Request RANAP

RANAP SRNS Context Response RANAP

SGSN Context Response

SGSN Context Ack

RANAP SRNS Data Forward Command RANAP

RANAP Forward Packet RANAP

Forward Packet

Update PDP Context Request

Update PDP Context Request

RANAP Iu Release Command RANAP

RANAP Iu Release Complete RANAP

NBAP Radio Link Deletion Request NBAP

NBAP Radio Link Deletion Response NBAP

Route Area Update Accept

42
 InterRAT Handover to GPRS Failure Cause

 When the UE handles the the CELL CHANGE ORDER FROM UTRAN
message, the abnormal cases may be occurred and the UE shall transmit
an CELL CHANGE ORDER FROM UTRAN FAILURE message with the
following failure causes ：
 Configuration unacceptable
 Physical channel failure
 Protocol error
 Unspecified

 If the time expired before RNC receives the message SRNS CONTEXT
REQUEST or IU RELEASE COMMAND from SGSN, RNC increases the
InterRAT handover to GPRS failure counter with the following cause ：
 InterRAT handover to GPRS no response

43
 InterRAT Handover to GPRS Failure Flow Chart

UE NodeB RNC 3G SGSN 2G SGSN BSS

RRC Cell Change Order From Utran RRC

RRC Cell Change Order From Utran Failure RRC

44
 Contents

Call Setup

Call Drop

Congestion

Handover

Traffic

45
 CS 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)

46
 PS 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

47
 PS 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

48
 Summary (1/3)
KPI Stage Failure Cause Level

- Congestion
RRC Setup Success Rate
- Unspecified

CN domain:
Call Setup - Parameter violation - CS
Success Rate - Non supported UTRAN capabilities - PS
- Relocation triggered QoS Classes:
RAB Setup Success Rate
- Transport connection failed to establish - Conversational
- Unavailable resources - Streaming
- Protocol error - Interactive
- Background

- OM intervention
- User inactivity
-CS
Signaling Plane - Repeated integrity checking failure
- PS
- UE generated signaling connection release
- RL out-of-synchronization

CN domain:
Call Drop Rate - CS
- PS
- OM intervention
QoS Classes:
User Plane - UTRAN generated reason
- Conversational
- RAB preempted
- Streaming
- Interactive
- Background

Signaling Congestion Rate RRC Connection Reject (Cause: congestion)

Congestion
Rate
- CS
Traffic Congestion Rate RAB Assignment Setup Failure (cause: congestion).
- PS

49
 Summary (2/3)
KPI Stage Failure Cause Level

Radio Link Addition

- Configuration unsupported
Soft & Softer - Incompatible simultaneous reconfiguration
Handover - Protocol error
Success Rate Radio Link Deletion - Invalid configuration
- No response from UE

- Configuration unsupported
- Physical channel failure
- Incompatible simultaneous reconfiguration
Hard Handover
- Protocol error
Success Rate
- Cell update occurred
- Invalid configuration
- No response received from UE

- Configuration unacceptable
InterRAT - Physical channel failure
Handover to - Protocol error
GSM Success - Inter-RAT protocol error
Rate - Unspecified
- InterRAT handover to GSM no response

- Configuration unacceptable
InterRAT
- Physical channel failure
Handover to
- Protocol error - initiated by UTRAN
GPRS Success
- Unspecified
Rate
- InterRAT handover to GSM no response

50
 Summary (3/3)
KPI Stage Failure Cause Level

QoS Classes:
- Conversational
- Streaming
CS Traffic Erlang
Bears
- AMR Voice
- CS 64K

QoS Classes:
- Conversational
PS Traffic Erlang - Streaming
- Interactive
- Background

QoS Classes:
- Conversational
PS Throughput Byte - Streaming
- Interactive
- Background

51
52