02 RN31572EN30GLA0 KPI Definition

7/29/2019 02 RN31572EN30GLA0 KPI Definition

http://slidepdf.com/reader/full/02-rn31572en30gla0-kpi-definition 1/75

Soc Classification level

1 © Nokia Siemens Networks RN31572EN30GLA0

KPI definition

3G RANOP RU30





Course Content

KPI definition

Performance monitoring

Air interface optimization

Traffic monitoring

Capacity enhancement





Module Objectives

• Describe the principles of 3G optimization

• Give an overview about the performance measurements and newfeatures offered by RU30

• Discuss the purpose of the most important KPIs (setup, access,

drop, mobility and throughput performance) and the factors impacting

them

At the end of the module you will be able to:





KPI Definition

Principles of 3G network optimization

Principles of performance measurements and KPI classification

KPI construction






Optimization strategy

Quality & Key Performance

Performanceindicators

RANparameters

Counters(OSS/NetAct)

RRM/Field/installation Cell CoverageCell Capacity

Radio/Signaling

capabilities

Transmission

capacity

Core/Mobility

performance

HWcapability





Target issues for optimizations are e.g. To achieve coverage and capacity RAN improvements by tuning of interference situations within the network

Therefore check RRM to ensure that the RAN offers planned coverage for each targeted service

Evaluate high capacity i.e. low blocking for new calls and handovers

Observe network performance by overall counters (NetAct, RNC counters)

Define quality indicators and compare KPI’s by triggering points

Check overall Quality of Service at RAN, transmission and core

Optimize the use of available capacity by priorities

Continuously monitoring/adjusting how the available resources are used inaccordance with user requests !

Optimization strategy






Key perform ance indicator imp rovement

Performance evaluationFailure causesEvent /Action item

P ERFORMANCE

Targets

C OUNTER

D escriptive statistics

Key P erformance indicator Signaling / Traffic RT/NRT

RRC / RAB / CORE

C OUNTER

statistics

Targets

fulf i l led ? Evaluat ion

Failure causes

Uu / WBTS /

AAL2 / RNC

Indicat ion

KPI

Targets

Event / Action item /improvement

No activ ities

Optimisation

Signaling / user plane


Yes No





Operator can define several KPIs:

Blocking rate (e.g. for RRC 0.5%, RT RAB 1%, NRT RAB 0.1%, PS session 5%)

Call drop rate (e.g. for RT RAB 0.5%, NRT RAB 2%)

Handover success rate (e.g. for SHO 95%, for ISHO 80%)

Report statistics generated by vendor MML commands (WBTS, RNC)

Evaluated for accessibility, retainability, usage, mobility and integrity (BLER)

Graphical representation of statistics (e.g. NetAct Report Suite)

In addition reporting and monitoring by probes


Quality benchmark





100%*KPI attempts)all_setup_ (e.g.all_call_events Number_of_

ups)l_call_set.successfuresult(e.gh_desired_ events_wit Number_of_

KPI counts events

Operator must specify target value to

evaluate performance

Limited qualitative analysis only, as nodetailed failure causes

Arithmetic mean only, but no discussionof statistical scatter


KPI principle and definition





The KPIs to be monitored for the RAN could be e.g.

Cell availability

Call Setup Success Rate CSSR

Packet session setup success rate (NRT, HSDPA, HSUPA)

Call Drop rate

SHO / ISHO / HSPA serving cell change success rate

In NOLS

WCDMA RAN Key Performance Indicators

RNC counter description

NetAct data base description for RNC measurements

Key Performance Indicator Changes Measurement Changes


KPI principle and definition





KPI Definition



KPI construction





BS

RNC 3G MSC

3G SGSN

GGSN Firewall

FMT

GPRS

Backbone

Internet

PS data

server

PSTN

CS data

server Modem

RAN KPI

Principles of performance measurements

RAN KPI classification – according functionality

The RAN KPI can be classified into the following categories

Accessibility

Retainability

Usage

Mobility

Integrity (BLER)





Relocation

RNC1SRNC

UEBTS2

BTS1

RNC2DRNC

Accessibility:RRC Setup & Access Rate

RAB Setup & Acc ess Rate

Call Setup Success Rate

XRetainability:RRC Drop Rate

RAB Drop Rate

Mobility:SHO Success Rate

SHO Overhead

Usage:Average UL Load

Average DL Load

X Pre-emption






RNC radio network counter

# 1xxx

W-BTS counter (HSPA, CE, CQI) #

50xx / 51xx

AXC counter #

52xxRNC PDH counter #

1xx

RNC signalling counter (SCCP) #

2xx

RNC ATM /IP transport counter #

5xx/8xxRNC DSP counter #

6xx

RNC multi-controller counter

(CPU) # 2xxx


RAN KPI classification – according network element





M1000 Cell resourceM1001 Service level

M1002 Traffic

M1003 L3 signaling at Iu

M1004 L3 signaling at Iur

M1005 L3 signaling at Iub

M1006 RRC signalingM1007 Soft handover

M1008 Intra-system hard handover

M1009 L3 relocation signaling

M1010 Inter-system handover

M1011 Location services

M1012 Service area broadcastM1013 Autodef SHO

M1014 Autodef IFHO

M1015 Autodef ISHO

M1016 RCPM OLPCM1017 RCPM RLC

M1018 RCPM UEQ

M1021 Iu-PC Interface

M1022 Packet call

M1023 Cell throughput

M1024 RCPM OLPC WCELM1025 RCPM OLPC RNC

M1026 RCPM RLC WCEL

M1027 RCPM RLC RNC

M1028 Autodef SHO DSR

M1031 WBTS Resource

M1032 CS Voice HSPA User PlaneM1033 CPICH Quality (EC /I0 and RSCP statistics)

New counters and performance measurements RU30

RNC radio network part measurements with new counters

new measurements






M5000 HSPA in WBTS MeasurementM5001 WBTS HW Resource Measurement

M5002 Cell Throughput in WBTS Measurement

M5003 Frame Protocol in WBTS Measurement

M5004 Signaling Load in WBTS Measurement

M5005 HSPA in WBTS Extension Measurement (number of DC HSPA users, PIC state)

M5006 WBTS R99 HW Measurement (CE for R99 and AMR over HSPA)M5101 FTM PDH Interface Measurement

M5102 FTM SDH Interface Measurement

M5105 FTM ATM Interface Measurement

M5106 FTM ATM VC Connection Measurement

M5107 FTM ATM VC Connection Measurement

M5110 FTM Ethernet Link MeasurementM5113 FTM Pseudowire MPLS Measurement

M5114 FTM PSN Tunnel IP Measurement

W-BTS part measurements with new counters

new measurements






M5115 AAL2 Scheduling Performance in BTS MeasurementM5116 FTM Timing over Packet Measurement

M5117 FTM IP Statistics Measurement

M5118 FTM PHB Statistics Measurement

M5119 FTM CES over PSN Interface Measurement

M5120 FTM CES over PSN pseudowire tunnel Measurement

M5121 FTM CES over PSN Pseudowire MeasurementM5122 FTM IPSec Measurement

M5123 FTM VLAN PHB Statistics Measurement

M5124 FTM VLAN IP Statistics Measurement

M5125 FTM VLAN Statistics Measurement

M5126 FTM TWAMP Statistics Measurement

M5127 PPP Multi Link Statistics MeasurementM5128 PPP Single Link Statistics Measurement

W-BTS part measurements with new counters

new measurements






RNC transport and HW part measurements with new counters

new measurements145 PDH Statistics

208 MTP Signalling link availability

209 MTP signalling link performance

210 MTP signalling link utilization

211 MTP signalling point status

212 MTP Signalling link set and route set availability

213 MTP Signalling traffic report of signalling points

214 MTP Signalling traffic report of user parts

215 MTP matrix signalling traffic

216 SCCP signalling point

217 SCCP subsystem

218 SCCP local subsystem availability

219 SCCP single meters

513 STM-1 Interface

514 IMA Logical Interface

516 SONET/SDH Protection Group meas

528 ATM layer performance

529 ATM Virtual Path Connection

530 ATM Virtual Channel Connection

531 ATM Route Load

532 ATM Interface533 ATM VCC Bundle

546 SAAL signalling protocol at UNI

547 AAL5 Protocol Measurement in DMX

548 AAL2 signalling protocol at UNI

549 AAL5 Protocol Meas. in CHORUS






RNC transport and HW part measurements with new counters

new measurements550 AAL2 path CAC resource

552 AAL2 signalling at NNI

553 AAL2 Scheduling Performance in RNC

563 TCP/IP Protocol

564 Ethernet Interface Performance

565 IP measurement on IP interface

566 UDP measurement on IP interface

567 IP QoS measurement

568 IP Based Route measurement

592 Unit Load

594 WAC overload control

608 Availability Performance609 DSP service statistics

610 L2 Resource Utilization (multi-controller)

612 DSP state changes

615 DSP Resource Utilization

617 DSP load

661 M3UA Association Set

800 AAL2 Resource Reservation

801 Iu-PS Performance

802 RNC capacity usage803 RNC RTP/RTCP

804 RNC IP CAC

2002 CPU Usage (multi-controller)

2004 Networking Logical (multi-controller)

2007 Node Level CPU load (multi-controller)





Performance monitoring Feature Number Automatic object list update RAN1438

User management for online monitoring RAN2290


New performance measurement features RU30






New HW and SW features in RU30

Frequency domain equalizer RAN1702

HSUPA interference cancellation receiver RAN1308

Dynamic HSDPA BLERRAN2171

Multi band load balancing and blind inter-frequency HORAN2172

Enhanced serving cell changeRAN1911

Dual cell HSDPA with MIMO and 64QAMRAN1907

4Rx diversityRAN1269

MIMO and 64QAMRAN1912

Flexi 3 sector RF module 1900 MHzRAN1575

HS Cell_FACH on DLRAN1637

New Feature RAN





KPI Definition



KPI construction- KPI Factors

- Access and setup

- Drop (Retainability)

- Mobility

-Throughput





IMPACT of network

performance

BTS, RNC, PS Core, CSCore performance

Performance of UE andfield measurement tools

Quality of networkimplementation

Application servers, IPbackbone performanceQuality of network operation

and maintenance

KPI factors

Factors affecting KPIs

f





KPI factors

Factors affecting KPIs

Many factors and network elements can affect network performance, e.g.

Quality of network equipment, both hardware and software (BTS, RNC, PS and CS

core, transmission equipment)

Performance of UE and field measurement tools (inter-operability, sensitivity of measurement parameters, level of accuracy)

Quality of network planning and optimization (coverage, interference, parameter tuning, capacity dimensioning, site acquisition)

Quality of network implementation (site and network equipment installation,

integration and commissioning)

Quality of network operation and maintenance

Multi-vendor environment (application servers, IP backbone, core versus RAN)

Measurement method (test setup, service dependency, cluster or system level,clutter type)

KPI f t





Server

RNC

W-BTS

UE

Power controlRACH process

UE power consumptionUE power spikingUE Sensitivity

UE Measurement performance

Cell reselectionSHORelocationInter-RAT mobility

UE IP configurationSupport of robust IP

header compression

KPI factors

UE impact on performance

UE feature supportCell_PCH64 QAMMIMODual cell HSPA

KPI f t





KPI factors

UE impact on performance

The functionalities of different UEs are not similar, there are differences in

Power control and RACH process

SRNC relocation support

Cell FACH/PCH performance

Cell reselection and inter-RAT mobility

Throughput (e.g. during SHO)

UE power consumption

UE power spiking

UE Measurement performance (cell reselection, Cell_DCH, ISHO)

UE Sensitivity

Data card throughput

Malfunctioning of certain UEs will naturally cause drops in setup or active phase

KPI D fi iti





KPI Definition




- Access and setup


- Mobility

-Throughput

KPI constr ction RRC set p





UE

RRC: Connection Request

RRC Connection Setup phaseResource Reservation in RNC, BTS, Transmission

RRC: Connection Setup

RRC Connection Access phaseRNC waits reply from UE

RRC: Connection Setup Complete

BTS RNC CN

KPI construction – RRC setup

Definition RRC connection (service level measurements M1001)

RRC setupsuccess rate

KPI construction RRC setup





ion_setupsce_connector_RRC_voiattempts_f

on_setupse_connectif_RRC_voicfailures_oion_setupsce_connector_RRC_voiattempts_f tesuccess_raRRC_setup_


RRC setup success rate (voice)

REP = repetitive attempt due to

RRC connection rejectNOT treated as fault, if user finally gets service

REL = cell reselection during setup

UE does not respond to RNC in 1st

cellBut requests service again in 2nd cell

Emergency calls redirected to GSM

RG_CALLTP_REJ_EMERRC_CONN_S

L_MT_CONVRRC_ACC_REL_MO_CONVRRC_ACC_REYL_EMERGENCRRC_ACC_REYP_EMERGENCRRC_ATT_REP_MT_CONVRRC_ATT_REP_MO_CONVRRC_ATT_RE

CALL_ATTSEMERGENCY_ ALL_ATTSMTC_CONV_CALL_ATTSMOC_CONV_CΣ

L_MT_CONVRRC_ACC_REL_MO_CONVRRC_ACC_REYL_EMERGENCRRC_ACC_RE

CALL_FAILSEMERGENCY_ CALL_ATTSEMERGENCY_

ALL_FAILSMTC_CONV_CALL_ATTSMTC_CONV_C

ALL_FAILSMOC_CONV_CALL_ATTSMOC_CONV_CΣ

tesuccess_raRRC_setup_






PR_SIGNL_MT_HIGH_ RRC_ACC_RE-PR_SIGNL_MO_HIGH_ RRC_ACC_RE

L_MT_BACKGRRC_ACC_REL_MT_INTER RRC_ACC_RE

L_MO_BACKGRRC_ACC_REL_MO_INTER RRC_ACC_RE

P_MT_BACKGRRC_ATT_REP_MO_BACKGRRC_ATT_RE

PR_SIGNP_MT_HIGH_ RRC_ATT_RE-PR_SIGNP_MO_HIGH_ RRC_ATT_RE

P_MT_INTER RRC_ATT_REP_MO_INTER RRC_ATT_RE

CALL_ATTSMTC_BACKG_ CALL_ATTSMTC_INTER_ ATTSRIOR_SIGN_ MTC_HIGH_P

ATTSRIOR_SIGN_ MOC_HIGH_PCALL_ATTSMOC_BACKG_ CALL_ATTSMOC_INTER_ Σ

PR_SIGNL_MT_HIGH_ RRC_ACC_RE- PR_SIGNL_MO_HIGH_ RRC_ACC_RE

L_MT_BACKGRRC_ACC_REL_MT_INTER RRC_ACC_RE

L_MO_BACKGRRC_ACC_REL_MO_INTER RRC_ACC_RE

FAILSRIOR_SIGN_ MTC_HIGH_P-ATTSRIOR_SIGN_ MTC_HIGH_P

FAILSRIOR_SIGN_ MOC_HIGH_P-ATTSRIOR_SIGN_ MOC_HIGH_P

CALL_FAILSMTC_BACKG_ CALL_ATTSMTC_BACKG_

CALL_FAILSMTC_INTER_ CALL_ATTSMTC_INTER_

CALL_FAILSMOC_BACKG_ CALL_ATTSMOC_BACKG_

CALL_FAILSMOC_INTER_ CALL_ATTSMOC_INTER_ Σ

tesuccess_raRRC_setup_


RRC setup success rate (NRT)

Analogue to voice

Includes interactive, background and high priority signaling services

Does not include emergency calls







RRC setup success rate (example)

Typical target for RRC setup success rate 99.5%

Little resources needed

High processing gain due to SF256 / SF128 on DL / UL for SRB

KPI construction RAB setup





RRC: Initial Direct Transfer (service request)

RANAP: Initial UE MessageDirect transfer (Call Proceeding)

RANAP: RAB AssignmentRequest

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RAB Connection Setup phaseResource Reservation in RNC, BTS, Transmission

RANAP: RAB AssignmentResponse

Direct transfer (Alerting)

Direct transfer (Connect)

Direct transfer (Connect Acknowledge)

RAB Connection Access phaseRNC waits reply from UE

UE BTS RNC CN

KPI construction – RAB setup

Definition RAB connection (service level measurements M1001)

RAB setup

success rat







RAB setup success rate (voice)

shmentsAB_establior_voice_R attempts_f

ments _establish _voice_RABsuccessfultesuccess_raRAB_setup_

T_CS_VOICERAB_STP_AT

EMP_CS_VOICRAB_ACC_COtesuccess_raRAB_setup_







RAB setup success rate (NRT)

Analogue to voice

Includes interactive and background services

High priority signaling services have on RAB level traffic class background

T_PS_BACKGRAB_STP_AT

T_PS_INTER RAB_STP_AT

GMP_PS_BACK RAB_ACC_CO

R MP_PS_INTERAB_ACC_CO

tesuccess_raRAB_setup_







RAB setup success rate (example)

Typical target for voice RAB setup success rate 99%

Little additional resources beyond RRC needed

Still high processing gain due to SF128 / SF64 on DL / UL for RB







RAB setup success rate (example)

Typical target for NRT RAB setup success rate 99.9%

Hardly any additional resources beyond RRC needed

RAB setup with DCH0/0, i.e. only signaling, no service allocation

KPI construction – call setup success rate





shmentsAB_establior_voice_R attempts_f

ments _establish _voice_RABsuccessful*


on_setupse_connectif_RRC_voicfailures_o


AMR_CSSR

CSSR = RRC setup SR * RAB setup SR

RRC: Connection Request


UE RNC

+

CoreUE

Both setup phases

must be successful


Complete

Service Request

RANAP RAB assignment

Procedure between core

and RNC

KPI construction call setup success rate

For NRT call analogue treatment



KPI construction – packet session setup





UE

RRC: Capacity Request

PS Session Setup phaseResource Reservation in RNC, BTS, Transmission

RRC: Radio Bearer Reconfiguration

PS Session Access phase

RNC waits reply from UE

RRC: Radio Bearer Reconfiguration Complete

BTS RNC

p p

Definition packet session setup (packet call measurements M1022)

PS session setupsuccess rate

UE in Cell_FACH or with DCH 0/0

UE in Cell_DCH with data r ate > 0 kbit/s (R99 or HS)






sallocationor_PS_DCH_ attempts_f

locations _PS_DCH_alsuccessful

PS_SSSR

RAB established

PS decides about Cell_DCH or Cell_FACH

p p

R99 packet session setup success rate

100%*

_DCH_BGR PS_ATT_DCH

+ _DCH_INTPS_ATT_DCH D_ALLO_BGR D_D_REQ_D_

+D_ALLO_INTD_D_REQ_D_

PS_SSSR

Request in DL: DCH Allocated in DL: DCH

Request in UL: DCH Allocated in UL: DCH

KPI contains interactive and background, but not PS streaming and conversational services






p p

R99 packet session setup success rate (example)

Typical target for packet session SSR 90% / 95% for data rate > / ≤ 64 kbps

High amount of resources needed especially for high data rate

Low processing gain especially for high data rate due to SF8 / SF4 on DL / UL






R SCH_DCH_BGPS_ATT_HSD+TSCH_DCH_INPS_ATT_HSDRESCH_DCH_STPS_ATT_HSD

GR SCH_EDCH_BPS_ATT_HSD+ NTSCH_EDCH_IPS_ATT_HSDTRESCH_EDCH_SPS_ATT_HSD

GR S_D_ALLO_BHS_D_REQ_H+ NTS_D_ALLO_IHS_D_REQ_HTRES_D_ALLO_SHS_D_REQ_H

GR S_D_ALLO_BHS_E_REQ_H NTS_D_ALLO_IHS_E_REQ_HTRES_D_ALLO_SHS_E_REQ_H

GR S_E_ALLO_BHS_E_REQ_H+ NTS_E_ALLO_IHS_E_REQ_HTRES_E_ALLO_SHS_E_REQ_H

p_SSHSPDA_Setu

ns _allocatioor_HS_DSCHattempts_f

llocations _HS_DSCH_asuccessful

p_SR HSDPA_Setu

RAB established

PS decides about HS-DSCH, DCH or FACH

p p

HSDPA session setup success rate

Three combinations

• HSDPA + HSUPA requested → both allocated

• HSDPA + HSUPA requested → at least HSDPA allocated • HSDPA requested only → HSDPA allocated

KPI contains streaming, interactive and background service

An analogue KPI for conversational service does not exist






HSDPA session setup success rate (example)

Typical target for HSDPA session setup success rate 90%

HSDPA session setup more often successful than R99 packet session setup

For HSDPA guarantee of 5 codes and reservation of CEs per packet scheduler






GR SCH_EDCH_BPS_ATT_HSD+ NTSCH_EDCH_IPS_ATT_HSDTRESCH_EDCH_SPS_ATT_HSD

GR S_E_ALLO_BHS_E_REQ_H+ NTS_E_ALLO_IHS_E_REQ_HTRES_E_ALLO_SHS_E_REQ_H p_SSHSUPA_Setu

tionsDCH_allocaor_Eattempts_f

tionsDCH_alloca _Esuccessful

p_SR HSUPA_Setu

RAB established

PS decides about HS-DSCH, E-DCH, DCH or FACH

HSUPA session setup success rate

One combination only

HSDPA + HSUPA requested → both allocated

KPI contains streaming, interactive and background service






HSUPA session setup success rate (example)

Typical target for HSUPA session setup success rate 90%

KPI Definition








- Access and setup


- Mobility

-Throughput

KPI construction – call drop rate





Radio link drop

Soft drop, RRC or RAB connection might still survive

UE BTS RNC CN

Types of drops

RRC drop

Hard drop, all RAB drop as well

RAB drop

Hard drop, but RRC connection might still survive

RAB drop = call drop






uresue_to_failreleases_deasesnormal_rel

uresue_to_failreleases_d

CDR

Call drop rate (service level measurements M1001)

Dropped calls = calls which do not terminate due to one of the following reasons

• Normal release

• Relocation

• Preemption

Possible causes for call drops are e.g.

• Lack of coverage

• Interference

• SHO failure

• Missing neighbor • Relocation failure






E_UEIL_CS_VOICRAB_ACT_FAE_RNCIL_CS_VOICRAB_ACT_FA

E_IUR IL_CS_VOICRAB_ACT_FAE_BTSIL_CS_VOICRAB_ACT_FA

E_RADIOIL_CS_VOICRAB_ACT_FAE_IUIL_CS_VOICRAB_ACT_FA

_GANHOL_CS_VOICERAB_ACT_RE _ISHOL_CS_VOICERAB_ACT_RE

_HHOL_CS_VOICERAB_ACT_RE

_P_EMPL_CS_VOICERAB_ACT_RE _SRNCL_CS_VOICERAB_ACT_RE

EMP_CS_VOICRAB_ACT_COΣ

E_UEIL_CS_VOICRAB_ACT_FAE_RNCIL_CS_VOICRAB_ACT_FA

E_IUR IL_CS_VOICRAB_ACT_FAE_BTSIL_CS_VOICRAB_ACT_FA

E_RADIOIL_CS_VOICRAB_ACT_FAE_IUIL_CS_VOICRAB_ACT_FA

_P_EMPL_CS_VOICERAB_ACT_REΣ

CDR_voice

Call drop rate for voice

KPI considers cell where call terminates

Call might have been started in another cell

Preemption treated as drop, as user looses service

Normal release

Relocation / preemption

IFHO

ISHO to GSM / WLAN

Drops

Drops

Preemption






Call drop rate for voice (example)

Typical target for voice call drop rate 0.5%

CS call drop rate usually lower than PS one due to larger cell range and

bigger SHO overhead






Call drop rate for NRT

No preemption for NRT calls

No inter-RAT mobility considered for NRT callsKPI considers drop of active RAB only

If non active RAB drops, both standard failure counters andRAB_ACT_FAIL_PS_XX_PCH counters are updated

Normal release

Relocation

Drops

Drops interactive

G_UEIL_PS_BACK RAB_ACT_FAR_UEIL_PS_INTERAB_ACT_FA

G_RNCIL_PS_BACK RAB_ACT_FAR_RNCIL_PS_INTERAB_ACT_FA

G_IUR IL_PS_BACK RAB_ACT_FAR_IUR IL_PS_INTERAB_ACT_FA

G_BTSIL_PS_BACK RAB_ACT_FAR_BTSIL_PS_INTERAB_ACT_FA

G_RADIOIL_PS_BACK RAB_ACT_FAR_RADIOIL_PS_INTERAB_ACT_FA

G_IUIL_PS_BACK RAB_ACT_FAR_IUIL_PS_INTERAB_ACT_FA

_SRNCL_PS_BACKGRAB_ACT_RE _SRNCL_PS_INTER RAB_ACT_RE

GMP_PS_BACK RAB_ACT_COR MP_PS_INTERAB_ACT_CO

R_PCHIL_PS_INTERAB_ACT_FAG_PCHIL_PS_BACK RAB_ACT_FA

G_UEIL_PS_BACK RAB_ACT_FAG_RNCIL_PS_BACK RAB_ACT_FA

G_IUR IL_PS_BACK RAB_ACT_FAG_BTSIL_PS_BACK RAB_ACT_FA

G_RADIOIL_PS_BACK RAB_ACT_FAG_IUIL_PS_BACK RAB_ACT_FAR_UEIL_PS_INTERAB_ACT_FAR_RNCIL_PS_INTERAB_ACT_FA

R_IUR IL_PS_INTERAB_ACT_FAR_BTSIL_PS_INTERAB_ACT_FA

R_RADIOIL_PS_INTERAB_ACT_FAR_IUIL_PS_INTERAB_ACT_FA

CDR_NRT

Drops background

Drops în Cell/URA_PCH






Call drop rate for NRT (example)

Typical target for NRT call drop rate 2%

PS call drop rate usually higher than CS one due to higher RSCP

requirements and lower SHO overhead


HSDPA t i bilit (t ffi t M1002)





o_failuresases_due_tHSDPA_relesPA_releasenormal_HSD

sPA_releasenormal_HSDion_SR HSDPA_sess

ion_SR HSDPA_sess1 _rateHSDPA_drop

HSDPA retainability (traffic measurements M1002)

HSDPA retainability deals with transition from HS-DSCH to DCH or FACH,not with release of HS RAB

Causes for normal transitions are• Inactivity

• Preemption

• Mobility to non HS cell

If a failure occurs, the RNC tries to shift the user to Cell_FACH, i.e. to

keep the RRC and RAB connection runningHSDPA drop thus is soft drop


HSDPA t i bilit





DSCH_BGR L_FAIL_HS_ REL_ALLO_R DSCH_INTL_FAIL_HS_ REL_ALLO_R

DSCH_BGR TH_FAIL_HSREL_ALLO_ODSCH_INTTH_FAIL_HSREL_ALLO_O

H_BGR ORM_HS_DSCREL_ALLO_NH_INTORM_HS_DSCREL_ALLO_NΣ

H_BGR ORM_HS_DSCREL_ALLO_NH_INTORM_HS_DSCREL_ALLO_NΣion_SR HSDPA_sess

HSDPA retainability

Two types of failure counter given only

• Radio link failure

• Other failure

An analogue KPI can be defined for streaming service

An analogue KPI for conversional service does not exist


HSDPA t i bilit





HSDPA retainability

Typical target for HSDPA drop rate 1%

HSDPA usually more robust than R99 as more power available for

the radio link

KPI Definition

P i i l f 3G t k ti i ti








- Access and setup


- Mobility

-Throughput

KPI construction – SHO success rate

Definition SHO success rate (SHO measurements M1007)





UE

RRC: Measurement Report (Event 1A / 1B / 1C)

Setup phaseResource Reservation in RNC, BTS, Transmission

(only Event 1A / 1C)

RRC: Active Set Update

Access phaseRNC waits reply from UE

RRC: Active Set Update Complete

BTS RNC

Definition SHO success rate (SHO measurements M1007)

SHO success rate


SHO success rate





_1ct_requestsreplacemensts_1bdrop_requeequests_1aaddition_r

t_updates _active_sesuccessful

s_rateSHO_succes

CELL A

CELL B

CELL C

SHO success rate

KPI checks reliability of SHO only

Problems like cell overlap or specific adjacencies discussed later

Attempt and success counted in all source cells


SHO success rate





FOR_NRTEQ_ON_SHO_ CELL_DEL_R _FOR_NRTREQ_ON_SHOCELL_REPL_

FOR_NRTEQ_ON_SHO_ CELL_ADD_R FOR_RTEQ_ON_SHO_ CELL_DEL_R

_FOR_RTREQ_ON_SHOCELL_REPL_ FOR_RTEQ_ON_SHO_ CELL_ADD_R

FOR_NRTES_ON_SHO_ SUCC_UPDATFOR_RTES_ON_SHO_ SUCC_UPDATs_RateSHO_Succes

SHO success rate

Number of successful active set updates in comparison to initial addition /deletion / replacement requests

Periodic reports are excluded (can occur e.g. in case of busy RNC not reactingimmediately to initial request)


SHO success rate (example)





SHO success rate (example)

NRT

RT

Typical target for SHO success rate 95%

CS more robust against low coverage / quality at cell edge than PS

Therefore higher SHO success rate

KPI construction – ISHO success rate

Definition ISHO success rate (ISHO measurements M1010)





UE

RRC: Measurement Report (Event 1F)

RRC: Physical Channel Reconfiguration

RRC: Physical Channel Reconfiguration Complete

BTS RNC

Definition ISHO success rate (ISHO measurements M1010)

ISHOsuccess

rate

UE put intocompressed mode

RRC: Measurement Control

RRC: Measurement ReportRxLev

measurements

RRC: Measurement Control

RRC: Measurement Report BSIC verification

MSC

RANAP Relocation required

RANAP Relocation command

RRC: HO from UTRAN Command

ISHOattempt


ISHO success rate





ISHO divided into two phases

• Inter-system measurements

• Inter-system handover execution

• Attempt and success counted in all source cells

RT and NRT ISHO differ in nature

Counter and KPI are implemented separately for RT and NRT

In case of multi-RAB with at least one RT RAB counted as RT ISHO

ISHO may fail due to e.g.

• Missing target cell• Target cell has not enough coverage

• Target cell strongly interfered

• Configuration problem

or_ISHOsattempts_f

_ISHOssuccessfulss_rateISHO_succe

ISHO success rate


ISHO per trigger





S O pe t gge

Attempt and success not only counted per RT / NRT, but also per trigger

•UL SIRTarget

•UL UE power (event 6A)

•DL RL power

•CPICH RSCP (event 1F)

•CPICH Ec /I0 (event 1F)

•IMSI based

•Emergency call

•Load based RTWP

•Load based TCP

•Load based HW / logical resources

•Load based code resources

•Services based


ISHO success rate RT





RTELL_BLOCK_ ATT_ISHO_CWN_RTELL_SHUTDOATT_ISHO_C

AMR_RTATT_GANHO_ S_RT _UL_DCH_WPIS_HHO_ATT

_SB_RTIS_HHO_ATTC_RT _LB_RSVR_SIS_HHO_ATT

M_RT _LB_RES_LIIS_HHO_ATTT_RT _LB_PTX_TOIS_HHO_ATT

T_RT _LB_PRX_T OIS_HHO_ATTL_RT _LB_CAPA_UIS_HHO_ATT

L_RT _LB_CAPA_DIS_HHO_ATTL _EMERG_CALIS_HHO_ATT

_IM_IMS_RTIS_HHO_ATTO_RT _CPICH_ECNIS_HHO_ATT

P_RT _CPICH_RSCIS_HHO_ATTRT _DPCH_PWR_ IS_HHO_ATT

R_RT _UE_TRX_PWIS_HHO_ATTRT _UL_DCH_Q_ IS_HHO_ATT

_RTCELL_BLOCK SUCC_ISHO_ OWN_RTCELL_SHUTDSUCC_ISHO_

_AMR_RTSUCC_GANHOO_WPS_RTSUCC_IS_HH

O_SB_RTSUCC_IS_HHSC_RTO_LB_RSVR_ SUCC_IS_HH

IM_RTO_LB_RES_LSUCC_IS_HHOT_RTO_LB_PTX_TSUCC_IS_HH

OT_RTO_LB_PRX_TSUCC_IS_HHUL_RTO_LB_CAPA_ SUCC_IS_HH

DL_RTO_LB_CAPA_ SUCC_IS_HHLLO_EMERG_CASUCC_IS_HHTO_IM_IMS_R SUCC_IS_HH NO_RTO_CPICH_ECSUCC_IS_HH

CP_RTO_CPICH_RSSUCC_IS_HHPWR_RTO_DL_DPCH_ SUCC_IS_HH

WR_RTO_UE_TRX_PSUCC_IS_HH _RTO_UL_DCH_QSUCC_IS_HHΣ

ss_RTISHO_Succe

Analogue for NRT

For NRT no ISHO of emergency call, of WPS user and no ISHO to GAN

Attempt counter updated, if measurements successful, i.eGSM cell with sufficient RxLevand readable BSIC available

Success counter updated, if relocation from RNC to BSCsuccessful


ISHO success rate (example)





NRT

RT

( p )

Typical target for ISHO success rate 90%/80% for RT/NRT

CS more robust against low coverage / quality at cell edge than PS

Therefore higher ISHO success rate

KPI construction – serving cell change success rate

Definition SCC success rate (intra-system HHO measurements M1008)





UE

RRC: Measurement Report (e.g. Ec/Io)

NBAP Radio Link Reconfiguration Procedure

BTSSource

BTSTarget

SCC

successrate

RRC: Radio Bearer Reconfiguration

RNC

NBAP Radio LinkReconfiguration

Procedure

RRC: Radio Bearer Reconfiguration Complete

Setup phaseResource Reservation in RNC, BTS, Transmission

Access phaseRNC waits reply from UE


Definition SCC success rate (intra-system HHO measurements M1008)





ASOND_OTHER_RESCC_STARTEET_UPDD_ACTIVE_SSCC_STARTE

RROR D_UL_SIR_ESCC_STARTENOD_CPICH_ECSCC_STARTE

SFULBTS_SUCCESSCC_INTER_ SFULBTS_SUCCESSCC_INTRA_ s_rateSCC_succes

Attempt counted per trigger in source cell

•CPICH Ec/I0

•UL SIR error

•Active set update

•Other reason

Success counted in target cell

•Intra BTS target

•Inter BTS target (data in source BTS buffer lost)


SCC success rate (example)





Typical target for serving cell change success rate 95%

KPI Deifnition







KPI construction

- KPI Factors

- Access and setup


- Mobility

-Throughput

KPI construction – cell throughput

R99 throughput sent / received by RNC on DL / UL per cell





60ATIONPERIOD_DUR 10008 _DATA_VOLNRT_DCH_DL RNCatThroughputAveraged-MACDLNRTR99

(cell throughput measurements M1023)

Transmission of MAC-d PDUs over DCH

Counter give data volume in byte

KPI give throughput in Kbit/s

60ATIONPERIOD_DUR 1000

8 _DATA_VOLNRT_DCH_UL RNCatThroughputAveraged-MACULNRTR99



KPI construction – BTS throughput

HSDPA throughput arriving at / transmitted by BTS





60 ATION PERIOD_DUR1000 S S_MACD_BIT RECEIVED_H hroughput Arriving_t

(HSPA in BTS measurements M5000)

60 ATION PERIOD_DUR1000

BITS D_HS_MACD_ -DISCARDE S S_MACD_BIT RECEIVED_H ut d_throughpTransmitte

Arrival and transmission of MAC-d PDUs over HS-DSCH

Counter gives data volume in Kbit

KPI give throughput in Mbit/s Discarded due to buffer overflow

KPI construction – layer 1 re-transmission

Transmission rate (HSPA in BTS measurements M5000)





sd_MACd_PDUtransmittenumber_of_

ionsetransmissy_with_n_r d_correctls_deliveref_MACd_PDU1)number_o(n

on_rateTransmissi n

Example

100 PDUs with no re-transmission

16 PDUs with 1 re-transmission

3 PDUs with 2 re-transmissions

1 PDU with 3 re-transmissions

Transmission rate = (100 * 1 + 16 * 2 + 3 * 3 + 1 * 4) / (100 + 16 + 3 + 1)

Transmission rate = 145 / 120 = 1.21

1.21 transmissions over the air for 1 PDU 21% re-transmission overhead



KPI construction – layer 1 re-transmission

Re-transmission overhead (example)





Typical target for re-transmission overhead 10%

Too high or too low re-transmissions reduce system capacity

02 RN31572EN30GLA0 KPI Definition

Documents

Transcript of 02 RN31572EN30GLA0 KPI Definition