01 KPI Definition PDF

Module 1 KPI overview
3G RANOP RU20
Soc Classification level
1 Nokia Siemens Networks Presentation / Author / Date
Module 1 KPI overview
Course Content
KPI overview
Performance monitoring
Air interface and neighbor optimization
Capacity & traffic optimization
Paging and inter-RNC optimization
KPI overview
Principles of 3G network optimizations
Principles of performance measurements and KPI classification
Examples for KPI construction
- KPI Factors
- Call Setup Failure Rate,
- Call Setup success rate
- Blocking Rate,
- Call Drop Rate,
- HO Failure Rate
- HO Failure Rate
Reporting suites
- Classes of counters,
- main existing KPI
Appendix
- examples of statistics
Module Objectives
Describe 3G RAN main classification and principles of
optimization
List measurements & KPIs & proposed target value to them
Describe the affecting network performance counters
Describe the content in RU20 reporting suite
At the end of the module you will be able to:
Principles of 3G network optimization
Optimization strategy
Quality & Key Performance
Performance RAN counters
Radio/Signaling
capabilities
TRANSMISSION
capacity
CORE/Mobility
performance
HW
Performance
indicators
RAN
parameters
counters
(OSS/NetAct)
RRM/Field/installation
Cell Coverage Cell Capacity
HW
(Capability)
Target issues for optimizations are to Target issues for optimizations are to
assume coverage and capacity RAN improvements by tuning of interference
situations within networks
Therefore check RRM to ensure the RAN offers:
- planned coverage for each targeted service
- Calculate high capacity i.e. low blocking (new calls, handovers)
Optimization strategy
- Calculate high capacity i.e. low blocking (new calls, handovers)
Observe NW performance by overall counters (NetACT, RNC counters)
Define quality indicators and compare KPIs by triggering points
Check overall Quality of Service (QoS) at RAN, transmission and core
- Optimize the use of available capacity (priorities)
By continuously monitoring/adjusting how the available resources are used
in accordance with user requests !
Key performance indicators (KPI) improvements
CAUSE
Index/level
COUNTER
Descriptive statistics
COUNTER
statistics
Index/level/ thresholds
Performance evaluation
event/
Action item
Index/level
/thresholds
Key
Performance indication
Signaling/Traffic: RT/NRT
RRC/RAB/CORE
3G Causes
Vendor issue Evaluations
Uu; WBTS,
AAL2, RNC
Indication
KPI
event/Action item/improvement
No activities
Optimisation/hysteretic
Signaling/user plane
Operator define several KPIs:
DCR (= drop call rate)
handover success rate 98 %,
blocking rate 2 %
% of samples having FER > 5%
Quality benchmark
Operator Features & SW reports statistics by vendor MML
commands (WBTS, RNC) evaluated by:
Accessibility, Retainability, Usage, Mobility, Integrity (BLER)
In addition reporting and monitoring by probes
Tools:
Equipment plus planning tools e.g. NetAct (NSN)
% 100 *
) _ _ _ . . ( _ _ _
) _ _ . . ( _ _ _ _ _
attempts setup call all g e events all of Number
setups call successful g e result desired with events of Number
KPI =
KPI counts events:
Does not evaluate performance
KPI definition & principle
No/limited qualitative analysis
Does not discuss statistical errors
Arithmetic mean only
No scatter
The KPIs to be monitored from the RAN could be:
Cell availability
Call Setup Success Rate (CSSR)
Call Drop rate
SHO/ISHO/HSPA SCC success rate
Packet Session setup/success rate (NRT, HSDPA, HSUPA)
KPI definition & principle
In NOLS:
RNC counter description
NetAct DB description for RNC measurements
WCDMA RAN Key Performance Indicators
Key Indicator Changes
Measurement Changes
*NOLS = Nokia Online Service
SCC = Serving Cell Change
Counter strategy - where to find & how to assume
RNC ATM/TP RNC ATM/TP
part counter part counter
# 500/800 # 500/800
groupe groupe
RNC radio network part RNC radio network part counter # counter #
1000 group 1000 group
WW--BTS part BTS part
counter/ counter/
# 5000 group # 5000 group
HSPA/CQI HSPA/CQI
Scenario descriptions Scenario descriptions
KPI found from RAN PAR
Description:
The number of RRC active failures due to RAB RRC active failures due to RAB failure failure
Cause:
When a radio interface failure occurs, and the failure causes the release of
the RRC connection and RAB establishments.
I uB
1. Detect fault based by counters
2. Check documentation of NED
3. Compare and evaluate KPI listing (Excel data or/and KPI)
4. Link/Evaluate RAN Parameter
5. Check situation within call flow situation at signaling plane
6. See OSS or/trace results at interfaces e.g. Iub/Iu
KPI strategy: Scenario descriptions
10 / ) 1121 ] [ Re ( _ ) ( = i r cTotalWbPw uu dBm i RTWP
Load related = Received Total Wideband Power (KPI)
M1000C0 C9
Example: Detect incremented counters Example: Detect incremented counters
Search counters
Average Uplink
R99 Load
Detect increment counters out of KPI, due to UL faults Detect increment counters out of KPI, due to UL faults
average ( sum(M1000C0 * M1000C1 +
M1000C2*M1000C3 + M1000C4 * M1000C5 +
M1000C6 * M1000C7+ M1000C8 * M1000C9) /
(M1000C1 + M1000C3 +M1000C5 + M1000C7 +
M1000C9)) dBm
RAN KPI formula
*NED = NSN Electronic Dictionary
Use counter tables from NED/PDF dictionary Use counter tables from NED/PDF dictionary
Move to RAN Parameter and/or EXCEL data Move to RAN Parameter and/or EXCEL data
Match KPI and tune RAN parameter Match KPI and tune RAN parameter
Match KPI and tune RAN parameter Match KPI and tune RAN parameter
RNC radio network part counter RNC radio network part counter # 1xxx # 1xxx
RNC ATM /TP part counter RNC ATM /TP part counter # 5xx/8xx # 5xx/8xx
WW--BTS part counter/ BTS part counter/ # 5xxx # 5xxx
HSPA/CQI HSPA/CQI
Use counter tables from NED/PDF dictionary Use counter tables from NED/PDF dictionary
HSPA/CQI HSPA/CQI
Example of new counters for RU20
Separate counters for relocation
RNC radio network RNC radio network W W- -BTS part counter/ BTS part counter/ RNC radio network RNC radio network W W- -BTS part counter/ BTS part counter/
Source RNC
Target RNC
More detailed
monitoring of
SRNS relocations
relocation counters
- in-coming/outgoing new counters
- new existing Service Level (M1001)
measurement
Separate counters for relocation
Counters- where to find ?
# 500/800 # 500/800
groupe groupe
I uB
RNC radio network RNC radio network
part counter # part counter #
W W- -BTS part counter/ BTS part counter/
HSPA/CQI HSPA/CQI
Counters- where to find ?
# 500/800 # 500/800
groupe groupe
I uB
RNC radio network RNC radio network
part counter # part counter #
W W- -BTS part counter/ BTS part counter/
HSPA/CQI HSPA/CQI
Channel Element utilisation in WBTS
RAB bit rate counters
Ethernet QoS monitoring for BTS
New updated KPIs
New counters per RRM feature
Thank You !
KPI overview
Thank You !
Improvement of NW Improvement of NW
KPI accomplished KPI accomplished
KPI overview
- KPI Factors
- Blocking Rate,
- Call Drop Rate,
- HO Failure Rate
- HO Failure Rate
Reporting suites
- main existing KPI
Principles of performance measurements
The RAN KPI can be classified into the following categories :
Accessibility
Retainability
Usage
Mobility
Integrity (BLER)
RAN KPI
RAN KPI Classification
Counter and KPI functions/issues
Integrity (BLER)
BS
RNC
3G MSC
3G SGSN
GGSN
Firewall
FMT
GPRS
Backbone
Internet
PS data
server
PSTN
CS data
server
Modem
Illustration on RAN KPI
SRNC
Relocation
RNC
RNC
Accessibility:
RRC Setup & Access Rate
RAB Setup & Access Rate
Call Setup Success Rate
PS setup success rate
Usage:
Cell Availability
Ave. Uplink Load
Ave. Downlink Load
SRNC
UE
BTS2
BTS1
PS setup success rate
(NRT,HSDPA, HSUPA)
X
Retainability:
RRC Drop Rate
RAB Drop Rate
PS success rate (NRT,
HSDPA, HSUPA)
Mobility:
SHO/ISHO Success Rate
SHO Overhead
HDSPA/HSUPA SCC
success rate
Ave. Downlink Load
HSDPA Throughput
Cell Throughput X
Pre-emption
* SCC = Serving Cell Change
RU20 New Counters and Measurements
Id Measurement
M513 STM-1 interface
M514 IMA logical interface
M516 SONET/SDH Protection Group
M528 ATM layer performance
M529 ATM Virtual Path Connection
M530 ATM Virtual Channel Connection
M531 ATM Route Load
M532 ATM Interface
M546 SAAL signalling at UNI
M547 AAL5 protocol in DMX
M548 AAL2 signalling protocol at UNI
M549 AAL5 protocol in chorus
M550 AAL2 path CAC resource
M552 AAL2 signalling at NNI
M553 AAL2 Scheduling Performance in RNC
Platform measurements
Id Measurement
M1000 Cell resource
M1001 Service level
M1002 Traffic
M1003 L3 signalling at Iu
M1004 L3 signalling at Iur
M1005 L3 signalling at Iub
M1006 RRC signalling
M1007 Soft handover
M1008 Intra-system hard handover
M1009 L3 relocation signalling
M1010 Inter-system handover
M1011 Location services
M1012 Service area broadcast
M1013 Autodef SHO
M1014 Autodef IFHO
RNW measurements
Id Measurement
M5000 HSDPA in WBTS
M5001 WBTS HW Resource
M5002 Cell Throughput WBTS
M5003 Frame Protocol WBTS
M5101 FTM PDH Interface
M5102 FTM SDH Interface
M5105 FTM ATM Interface
M5106 FTM ATM VC Connection
M5107 FTM ATM VP Connection
M5110 FTM Ethernet Link
M5113 FTM Pseudowire MPLS
M5114 FTM PSN Tunnel IP
M5115 FTM AAL2 Scheduling Performance
M5116 FTM Timing over Packet Measurement
M5117 FTM IP statistics measurement
M5118 FTM PHB statistics measurement
WBTS measurements
M553 AAL2 Scheduling Performance in RNC
M563 TCP/IP Protocol
M592 Unit load
M594 WAC overload control
M608 Availability performance
M609 DSP Service statistics
M612 DSP state changes measurement
M615 DSP resource utilization
M617 DSP load measurement
M800 AAL2 Resource Reservation
M801 Iu-PS Performance
M802 SW License Key controlled Capacity
M803 RNC_RTP_RTCP, IP based Iu-CS
M804 RNC IP CAC, IP based IU
M1014 Autodef IFHO
M1015 Autodef ISHO
M1016 RCPM OLPC
M1017 RCPM RLC
M1018 RCPM UEQ
M1020 A-GPS Server Interface
M1021 Iupc Interface
M1022 Packet Call
M1023 Cell Throughput
M1024 RCPM OLPC WCEL measurement
M1025 RCPM OLPC RNC measurement
M1026 RCPM RLC WCEL measurement
M1027 RCPM RLC RNC measurement
M1028 AutoDef SHO DSR
M1031 WBTS Resource
New RU10 Measurement
New RU20 Measurement
New RU20 Counters
M5118 FTM PHB statistics measurement
Id Measurement
M5201 AXC PDH
M5202 AXC SDH
M5203 AXC IMA group
M5204 AXC IMA link
M5205 AXC ATM Interface
M5206 AXC ATM VC Connection
M5207 AXC ATM VP Connection
M5208 AXC AAL2 performance
M5209 AXC AAL5 performance
M5210 AXC Ethernet link
M5211 AXC Sonet/SDH protection group
M5212 AXC ATM Performance
M5213 AXC Pseudowire MPLS measurement
M5214 AXC PSN Tunnel IP
M5215 AAL2 scheduling performance in BTS
M5216 AXC Timing over Packet Measurement
M5217 AXC IP Statistics
M5218 AXC PHB statistics
AXC measurements
Performance monitoring Feature Number RU20
RAB Bit Rate Counters * RAN1509
Activation of the required license
Position Information in Subscriber Trace Report** RAN1311
Activating RAN1311: Position
Information in Subscriber Trace Report
Channel Element Utilization in WBTS* RAN1312
Activation of the required license
Separate Counters for Outgoing Relocations* RAN1136 No activation needed
New PM features in RU20 New PM features in RU20
Separate Counters for Outgoing Relocations* RAN1136 No activation needed
Ethernet QoS Monitoring in BTS RAN1713 No activation needed
*Discussed in detail in appendix slides 76-90
**Position information in subscriber trace report feature:
-The position info of the traced subscriber is included in the trace reports
-More efficient optimization & planning
-Helps to avoid the drive-tests
New RU20 features
Dual Iub for Ultrasite WCDMA BTS RAN1633
New Feature RAN
Continuous Packet Connectivity RAN1644
HSDPA 64QAM RAN1643
Flexible RLC (DL) RAN1638
HSUPA 2 ms TTI RAN1470
Fractional DPCH RAN1201
Power Saving Mode for BTS RAN955
Broadcast of A-GPS Assistance Data RAN876
HSPA 72 Users Per Cell RAN1686
Continuous Packet Connectivity RAN1644
LTE interworking RAN2067
Dual-Cell HSDPA 42Mbps RAN1906
Multiple BSIC Identification RAN1758
CS Voice Over HSPA RAN1689
MIMO RAN1642
Principles of performance measurements (1/2)
Poor CSSR could be a result of
Poor coverage or dominance or interference issues in Radio interface
Capacity issues in Radio or Iub interface
Configuration issues in WBTS (parameters or HW)
CSSR is essentially RRC Setup Success * RAB Setup Success
(or successful PS session setups in case of PS call)
CSSR covers all the steps from the initial RRC connection request from the UE to the
network, through the RRC setup phase and the RAB setup phase, and until user data
is starting to get transferred.
The CSSR formulas are for different traffic classes like:
CS voice calls (RNC 565 f)
CS video calls (RNC 566e)
PS RT Streaming Calls (RNC 575 d)
PS NRT Calls (Interactive & Background) (RNC 576d)
*CSSR = Call Setup Success Rate
Principles of performance measurements (2/2)
CSSR KPI for CS voice from end user perspective (RNC 565f)
)) _ _ _ _ (
) _ _ _ _ ( (
*
) _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ (
) _ _ _ _
_ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ ( ( * 100
_
VOICE CS ATT STP RAB sum
VOICE CS COMP ACC RAB sum
CALL EMERG REJ STP CONN RRC CONV MT REL ACC RRC
CONV MO REL ACC RRC EMERGENCY REL ACC RRC
EMERGENCY REP ATT RRC CONV MT REP ATT RRC
CONV MO REP ATT RRC ATTS CALL EMERGENCY
ATTS CALL CONV MTC ATTS CALL CONV MOC sum
CONV MT REL ACC RRC
FAILS CALL EMERGENCY ATTS CALL EMERGENCY
FAILS CALL CONV MTC ATTS CALL CONV MTC
FAILS CALL CONV MOC ATTS CALL CONV MOC sum
CSSR AMR

+
+

+
+
=
RRC part
RAB part
RRC request repetitions done by UE after RRC reject are excluded from denominator (not
necessarily seen as failures from the user's perspective)
Emergency calls re-directed to GSM layer are excluded from denominator
The occurred cell re-selections are subtracted both from the numerator and denominator
because they are not considered as call attempts from mobile end-user point of view. The UE
has made a new RRC connection via another cell and Attempts-counter is updated in the new
cell for the new attempt.
) _ _ _ _ _ _ _ _ _ CALL EMERG REJ STP CONN RRC CONV MT REL ACC RRC
RRC part
RAB part
*CSSR = Call Setup Success Rate
*MOC, MTC, cell reselection during RRC setup, redirection to GSM
_CE MAX_AVAIL M5001C0
_CE MIN_AVAIL M5001C1
CE AVE_AVAIL_ M5001C2
E_DL MAX_USED_C M5001C3
In memory of counter # In memory of counter #
RNC radio network part counter RNC radio network part counter # 1xxx # 1xxx
RNC ATM /TP part counter # 5xx/8xx
WW--BTS part counter/ BTS part counter/ # 5xxx # 5xxx
HSPA/CQI HSPA/CQI
Counter scenario description within network elements
M5001 WBTS Baseband processing
CE_UL MAX_USED_ M5001C4
E_DL MIN_USED_C M5001C5
CE_UL MIN_USED_ M5001C6
E_DL AVG_USED_C M5001C7
E_UL AVG_USED_C M5001C8
M1005 L3 on IuB at RNC
M1005C0 : RL_STP_ATT_FOR_FIRST_RL
M1005C5 : RL_STP_SUCC_FOR_FIRST_RL
M1005C179: SETUP_FAIL_FIRST_RL_MISC
Thank You !
KPI overview
New New
classifications classifications
Thank You !
KPI overview
- KPI Factors
- Call Setup failure rate,
- Blocking Rate,
- Call Drop Rate,
- HO Failure Rate
- HO Failure Rate
- Statistic examples
Reporting suites
- main existing KPI
Examples for KPI construction - factors
Factors affecting KPI
IMPACT of network
BTS, RNC, PS Core, CS Core
performance
Performance of UE and
field measurement tools
IMPACT of network
performance
Quality of network
implementation
Application servers, IP Backbone
performance Quality of network
operation and
maintenance
Although parameter optimisation can provide short term gains they do
not correct underlying network problems. (E.g. SHO <> Dominance)
Many factors and network elements can affect the network
performance. Here are some of the main examples:
Quality of network equipment, both hardware and software BTS, RNC, PS
Core, CS Core and transmission equipment
Performance of UE and field measurement tools inter-operability,
sensitivities of measurement parameters, level of accuracy
Quality of network planning and optimization coverage, interference,
parameter tuning, capacity dimensioning
Factors affecting KPI
parameter tuning, capacity dimensioning
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
Measurement method test setup, service dependent, cluster or system level,
area type (dense urban, urban, suburban, rural).
Impact on different performance by each UE
Server
RNC
W-BTS
SRNC SRNC
UE power UE power
consumption consumption
UE power UE power
spiking spiking
Data throughputs Data throughputs
UE Sensitivity UE Sensitivity
Server
UE
UE Measurement UE Measurement
performance performance
(cell_DCH, cell (cell_DCH, cell
reselection, ISHO reselection, ISHO
Power control Power control
(RACH process) (RACH process)
SRNC SRNC
relocation relocation
support, Cell support, Cell
FACH/PCH FACH/PCH
performance performance
Cell reselection/ Cell reselection/
inter RAT cell reselection inter RAT cell reselection
Throughput (during SHO) Throughput (during SHO)
The functionality of different UEs are not similar, there are differences in
Power control (RACH process)
SRNC relocation support
Cell FACH/PCH performance
Cell reselection/inter RAT cell reselection
Throughput (during SHO)
UE power consumption
UE impact on performance
UE power spiking
UE Measurement performance (cell_DCH, cell reselection, ISHO)
UE Sensitivity
Data card throughputs
The malfunctioning of certain UEs will naturally cause drops in setup of
active phase
BTS UE RNC CN
RRC: RRC connection Request
RRC: RRC connection Setup
RRC SETUP phase
(Resource Reservation in RNC)
RRC ACCESS phase
(RNC waits for Reply from UE)
RRC: RRC connection Setup Complete
R
R
C

S
e
t
u
p

t
i
m
e
RRC ACCESS fails if the UE does not reply to RRC: RRC
CONNECTION SETUP message with the RRC: RRC CONNECTION
SETUP COMPLETE message in given time, if the BTS reports a radio
link synchronisation failure or in an RNC internal failure occurs
RRC SETUP fails if some of the needed resources (RNC, BTS, AIR,
Transport) are not available. When an RRC setup failure occurs the
RNC sends an RRC: RRC CONNECTION REJECT message to UE
KPI construction - Call Setup Failure Rate
RRC Connection Setup & Access and Active negative
R
A
B

e
s
t
a
b
l
i
s
h
m
e
n
t
RRC: Initial Direct Transfer
RANAP: Initial UE Message
RANAP: Iu Release Command
UE-CN Signalling
(E.g. RAB Establishment and Release)
RRC: RRC connection Release
RRC: RRC connection Release Complete
Release RRC resources in RNC, BTS,
Transport
RRC ACTIVE phase
link synchronisation failure or in an RNC internal failure occurs
RRC ACTIVE fails when an interface related (Iu, Iur , Iub, or Radio) or
RNC internal failure occurs, and the failure causes the release of the
RRC Connection. When an RRC active failure occurs, the RRC send
a RANAP: IU RELEASE REQUEST to all involved CNs and waits for
RANAP: IU RELEASE COMMAND message (s)
RRC ACTIVE release cause can be either ISHO, IFHO, SRSN
relocation or pre-emption
R
A
B

e
s
t
a
b
l
i
s
h
m
e
n
t
KPI construction - call setup failure rate
sum ( RAB failure counters)
sum ( RAB failure counters + RAB active Complete)
RAB failure rate = 100 % *
Call Completion drop rate - CDR
sum ( RAB failure counters)
CCSR = 100 % - 100 % *
CCSR for a specific service is calculated based on RAB Counters:
In NSN Nokia RAN there are negative counters used to get success ratio:
*CCSR = Call Completion Success Rate
Service level count (AMR)
CSSR = RRC setup SR * CSSR = RRC setup SR * RAB setup SR RAB setup SR
RRC: RRC connection Request
RRC SETUP phase
(Resource Reservation in RNC)
RRC ACCESS phase
(RNC waits for Reply from UE)
Complete
UE RNC
+
RNC UE
Both setup
must be successful
ents establishm RAB voice for attempts
ents establishm RAB voice successful
setups connection voice RRC for attempts
setups connection voice RRC of failures
setups connection voice RRC for attempts
CSSR AMR
_ _ _ _
_ _ _
*
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_
=
UE
RRC: Connection Request
RRC Connection Setup phase
Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup
RRC Connection Access phase
RNC waits reply from UE
RRC: RRC Connection Completed
RRC: Initial Direct Transfer cm service request
DIRECT TRANSFER (Call
BTS
RNC CN
Call Set-up
Definition RRC - RAB
KPI construction - call setup success rate
Proceeding)
RANAP: RAB Assignment
Request
RRC: Radio Bearer Set-up
RRC: Radio Bearer Setup
Complete
RAB Connection Setup phase
Response
DIRECT TRANSFER (Alerting)
DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect
Acknowledge)
RAB Connection Access phase
Call Set-up
Success
Rate
Call Set-up
Time
)) _ _ _ _ (
) _ _ _ _ ( (
*
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ (
) _ _ _ _
_ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ ( ( * 100
_
CONV MT REL ACC RRC
CSSR AMR

+
+

+
+
=
RAB part
AMR CSSR from end user perspective (RNC 565f)
RRC part
RAB part
UE
RNC
relation
RNC UE
RRC setup RRC setup
RAB setup RAB setup
*MOC, MTC, cell reselection during RRC setup, redirection to GSM
s allocation DCH PS for attempts
s allocation DCH PS successful
SSSR PS
_ _ _ _
_ _ _
_ =
Service level evaluations (PS/Release 99)
KPI construction packet call setup success rate
Packet Call: SSSR - Rel99
RAB established
PS decides about Cell_DCH or Cell_FACH
*SSSR = Session Setup Success Ratio
Service level evaluations (PS/Release 5/6)
KPI construction Rel 99 & HSPA
HSDPA Accessibility HSDPA Accessibility
Successfully establishments: Successfully establishments:
Cell_DCH states Cell_DCH states
HS HS--DSCH states DSCH states
Packet Call: SSSR HSPA
HS HS--DSCH states DSCH states
HS HS--DSCH + E DSCH + E--DCH states DCH states
RNC
Iub
WBTS
MAC-hs
Uu
UE
*SSR = Setup
Success Ratio
PS by selections DSCH HS
ents establishm DSCH HS
ity accessibil HSDPA
_ _ _
_
_
=
Service level evaluations (Traffic measurement)
KPI construction HSDPA accessibility (1/2)
PS decides to allocate HS-DSCH
But HS-DSCH really established ?
HSDPA Accessibility
% 100
TAL_INT _IUB_HS_TO SETUP_FAIL M1002C417 CH_INT _BTS_HS_DS SETUP_FAIL M1002C416
H_INT _UE_HS_DSC SETUP_FAIL M1002C415 CH_INT _RNC_HS_DS SETUP_FAIL M1002C413
H_RET_BGR REJ_HS_DSC M1002C402 H_RET_INT REJ_HS_DSC M1002C401
ERS_BGR X_HSDPA_US DCH_SEL_MA M1002C476 ERS_INT X_HSDPA_US DCH_SEL_MA M1002C475
R CH_FLOW_BG ALLO_HS_DS M1002C389 T CH_FLOW_IN ALLO_HS_DS M1002C385
R CH_FLOW_BG ALLO_HS_DS M1002C389 T CH_FLOW_IN ALLO_HS_DS M1002C385
605 _
+ +
+ +
+ +
+ +
+ +
+
= b RNC
Rejections (radio
resources, too
much HSDPA users
KPI construction HSDPA accessibility (2/2)
Successful establishment
*M1002C401 failed
allocation for HS-DSCH due
to lack of resources for the UL
DCH return channel for
interactive services
ERS_BGR) X_HSDPA_US DCH_SEL_MA 476 1002 ERS_INT X_HSDPA_US DCH_SEL_MA 475 1002
TAL_BGR _IUB_HS_TO SETUP_FAIL M1002C425 CH_BGR _BTS_HS_DS SETUP_FAIL M1002C424
H_BGR _UE_HS_DSC SETUP_FAIL M1002C423 CH_BGR _RNC_HS_DS SETUP_FAIL M1002C421
TAL_INT _IUB_HS_TO SETUP_FAIL M1002C417 CH_INT _BTS_HS_DS SETUP_FAIL M1002C416
+ +
+ +
+ +
+ +
C M C M
Setup
failures
The accessibility of all started allocations for HS-DSCH for NRT Traffic from user point of view
The number of times when HS-DSCH channel has been established divided by the number of
times when HS-DSCH channel has been selected by cell specific PS
Also the times that HS-DSCH channel selection fails due to UE and the times the HS_DSCH
would have been selected but the number of possible HS-DSCH users were exceeded are
included in the formula
*Note that M1002C475 & M1002C476 are 2
times in the formula - wrong
failures to due releases HSDPA releases HSDPA normal
releases HSDPA normal
rate success session HSDPA
_ _ _ _ _ _
_ _
_ _ _
+
=
rate drop session HSDPA rate success session HSDPA _ _ _ 1 _ _ _ =
KPI construction HSDPA Retainability
Current RNC_609a HSDPA Retainability for NRT Traffic
% 100
SCH_BGR _FAIL_HS_D EL_ALLO_RL M1002C482R SCH_INT _FAIL_HS_D EL_ALLO_RL M1002C479R
SCH_BGR H_FAIL_HSD EL_ALLO_OT M1002C411R SCH_INT H_FAIL_HSD EL_ALLO_OT M1002C408R
H_BGR ORM_HS_DSC REL_ALLO_N M1002C410 H_INT ORM_HS_DSC REL_ALLO_N M1002C407
H_BGR ORM_HS_DSC REL_ALLO_N M1002C410 H_INT ORM_HS_DSC REL_ALLO_N M1002C407
609 _
+ +
+ + +
+ +
+
= a RNC
HSDPA Retainability (HSDPA only) HSDPA Retainability (HSDPA only)
Failure classified into two categories: Failure classified into two categories:
Radio link failure Radio link failure
Other failure Other failure
Note that this KPI is
independent on the
setup success ratio !!
Current RNC_609a HSDPA Retainability for NRT
Traffic. The normal transition from HS-DSCH to
FACH/DCH are considered as a normal HS-DSCH
release (including transitions due to mobility and pre-
emption)
The fallbacks and other possible normal release
counters are not separately included in the formula,
as they are already included in the Normal release
counters
KPI construction HSDPA Retainability
counters
Failure classified into two categories Failure classified into two categories
Radio link failure Radio link failure
Other failure Other failure
+
+
+ +
+
=
+ NT S_D_ALLO_I HS_D_REQ_H M1022C25 RE _D_ALLO_ST S_D_REQ_HS M1022C192H +
GR S_D_ALLO_B HS_E_REQ_H M1022C24 + NT S_D_ALLO_I HS_E_REQ_H M1022C23
TRE S_D_ALLO_S HS_E_REQ_H 191 1022 GR S_E_ALLO_B HS_E_REQ_H M1022C22
+ NT S_E_ALLO_I HS_E_REQ_H M1022C21 RE _E_ALLO_ST S_E_REQ_HS M1022C190H
e[%] Perspectiv User from Ratio Success Setup HSDPA RNC_914c
C M
Packet Call: SSSR HSDPA allocation
Corrected
formula !
+ +
+
+
T_CELL _D_ALLO_IN HS_E_REQ_D M1022C217 R_CELL _D_ALLO_BG HS_E_REQ_D M1022C218
- R_CELL _D_ALLO_ST HS_E_REQ_D 219 10022 T_CELL _D_ALLO_IN HS_D_REQ_D M1022C220
R_CELL _D_ALLO_BG HS_D_REQ_D M1022C221 - _CELL D_ALLO_STR S_D_REQ_D_ M1022C222H
- R SCH_DCH_BG PS_ATT_HSD M1022C6 + T SCH_DCH_IN PS_ATT_HSD M1022C5
RE SCH_DCH_ST PS_ATT_HSD 182 1022 GR SCH_EDCH_B PS_ATT_HSD M1022C4
+ NT SCH_EDCH_I PS_ATT_HSD M1022C3 RE CH_EDCH_ST S_ATT_HSDS M1022C181P
GR S_D_ALLO_B HS_D_REQ_H M1022C26
+ NT S_D_ALLO_I HS_D_REQ_H M1022C25 RE _D_ALLO_ST S_D_REQ_HS M1022C192H +
C M
C M
D = DCH, E = E-DCH
UE wants to get at least
HS-DSCH R5 resource
*SSSR = Session Setup Success Ratio
Remove
DCH
allocations
when BTS
not
supporting
HSDPA
Cell resource/ cell actual availability
KPI construction - Call Blocking Rate
Working state
CPICH of cell is visible
SC, RSCP... can be measured
RNC_183c Cell Availability KPI counts Cell availability from user point of view: RNC_183c Cell Availability KPI counts Cell availability from user point of view:
Due to introduction of RAN955 Power Saving Mode for BTS
RNC_183c, Cell Availability
( )
( ) DB RNW IN EXIST WCELL AVAIL sum
STATE WO IN WCELL AVAIL sum
ty Availabili Cell
_ _ _ _ _
_ _ _ _ * 100
_ =
This replace old Cell
Availability KPI
based on Code Tree
Due to introduction of RAN955 Power Saving Mode for BTS
new official note was added. New official note informs that the
duration of power saving mode is included in the duration of
the working state.
M1000C178 AVAILABILITY WCELL IN WORKING STATE
# of samples when WCELL is in WO State. Counter M1000C180 is
always updated along with this counter
Counter is updated with the value 1 once in 5 seconds when the
WCELL is in WO State
M1000C180 AVAILABILITY WCELL EXIST IN RNW DATABASE
# of samples when WCELL is configured in the database. This
Cell resource/ cell actual availability
# of samples when WCELL is configured in the database. This
counter is used as a denominator for cell availability calculation
Counter is updated with the value 1 one in approx. 5 seconds
when the WCELL is configured in the radio network database
( )
=
USER BY BLOCKED WCELL AVAIL
DB RNW IN EXIST WCELL AVAIL
sum
STATE WO IN WCELL AVAIL sum
state BLU excluding ty Availabili Cell
_ _ _ _
_ _ _ _ _
_ _ _ _ * 100
_ _ _ _
Cell resource/ cell availability
KPI construction - Call Blocking Rate (by user)
M1000C179 AVAILABILITY WCELL BLOCKED BY USER
# of samples when WCELL is BLU State. Counter
M1000C180 is always updated along with this counter
Counter is updated with the value 1 once in approx. 5 seconds
when the WCELL is in BLU state
Cell resource/ cell availability
Blocked by user:
There is also Optional Cell availability KPI which counts
Cell Availability from network point of view. Situation
where WCELL is blocked by User are excluded from
the formula.
RNC_727a Cell Availability KPI, excluding blocked by
user state (BLU), Counts Cell availability from network
point of view:
Blocked by user:
OPERATOR has blocked ATM link between Node B and
RNC related to the cell. No NBAP signaling between Node
B and RNC related to the cell. Some maintenance done
for the cell
Cell availability
RNC196
Cell available has same level as in RU10
RU20 PCD2.0
RU10
WN6.0
No change in Cell availability
PCD3.0 CD0.0
Peaks down are due to
SW upgrades
failures to due releases releases normal
failures to due releases
CDR
_ _ _ _
_ _ _
+
=
Service level evaluations
KPI construction - Call Drop Rate
Dropped call: Dropped call:
All calls, which not All calls, which not
terminate with a terminate with a
normal release normal release
No retain ability No retain ability
Call Drop Rate (CDR Call Drop Rate (CDR)
Call is dropped if one (or more) of the following RAB, RB or RL, drops.
PS call drop is different than the other call type drops, RAB service can
still exits even if the RB and/or RL drops
Call drop could be a reason of coverage or interference issues, SHO
problems, missing neighbour, inter RNC problems, just to mention some
Service level evaluations
Call Drop rate (CDR) is calculated based on RAB activation failures, it can
be defined separately for different services
Normal RAB releases are taken into account
Drops during the signalling are not included
RAB Success = 100 RAB Success = 100 -- 100*(failures /success) 100*(failures /success)
KPI evaluation events R99/SHO
KPI construction - SHO Failure vs. success Rate
c requests t replacemen b requests drop a requests addition
updates set active successful
rate success SHO
1 _ _ 1 _ _ 1 _ _
_ _ _
_ _
+ +
=
Here only the reliability of the feature itself is Here only the reliability of the feature itself is
checked. Problems like overlapping cells or checked. Problems like overlapping cells or
specific adjacencies are not discussed yet specific adjacencies are not discussed yet
CELL A
CELL B
CELL C
SHO success rate
SHO success rate KPI (195a) is informing how many successful Active set updates we will
have compared to initial Addition/Replacement/Deletion requests.
This formula is excluding periodical reports, which might occur if for example RNC is busy
and cannot process immediately initial request.
) _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _ _ _ _ ( * 100
_
NRT FOR SHO ON REQ DEL CELL NRT FOR SHO ON REQ REPL CELL
NRT FOR SHO ON REQ ADD CELL RT FOR SHO ON REQ DEL CELL
RT FOR SHO ON REQ REPL CELL RT FOR SHO ON REQ ADD CELL sum
NRT FOR SHO ON UPDATES SUCC RT FOR SHO ON UPDATES SUCC sum
Success SHO
+ +
+ +
+
+
=
RNC BTS
RRC: Active Set Update
Decision to
set up new RL
RRC: Measurement Report (e1a / e1c)
NBAP: Radio Link Setup Response
Start TX/RX
ALCAP:ERQ
ALCAP:ECF
RRC: Active Set Update Complete
UE
NBAP: Radio Link Setup Request for Soft Handover
NBAP: Radio Link Addition Request for Softer Handover
NBAP: Radio Link Addition Response
RNC BTS
Decision to
set up new RL
Start TX/RX
ALCAP:ERQ
ALCAP:ECF
UE
REQ_ON_SHO CELL_REPL_
EQ_ON_SHO CELL_DEL_R
EQ_ON_SHO CELL_ADD_R
ES_ON_SHO SUCC_UPDAT
+
+
NUMBER OF SUCCESSFUL AS UPDATE NUMBER OF SUCCESSFUL AS UPDATE
FOR THE CELL UNDER OBSERVATI ON FOR THE CELL UNDER OBSERVATI ON
TOTAL NUMBER OF NOT PERI ODOI CAL TOTAL NUMBER OF NOT PERI ODOI CAL
MEASUREMENT REPORT (1A,1B,1C) MEASUREMENT REPORT (1A,1B,1C)
RECEI VED BY THE CELL UNDER OBSERVATI ON RECEI VED BY THE CELL UNDER OBSERVATI ON
UPDATED FOR ALL THE CELLS WI THI N AS WHEN MEAS. REPORT I S RECEI VE UPDATED FOR ALL THE CELLS WI THI N AS WHEN MEAS. REPORT I S RECEI VED D
+
+
ISHOs for attempts
ISHOs successful
rate success ISHO
_ _
_
_ _ =
KPI evaluation events R99/ISHO
KPI construction - ISHO success rate
ISHO Success Rate
CN
UE Node B RNC
RRC: Measurement Report (intra-frequency) 1F event
RRC: Measurement Control
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete
NBAP: Compressed Mode Command
ISHO
triggering
Initial
Compressed
Mode
Configuration
Example NBAP and RRC compressed mode signalling for a CS service inter-system HO
RRC: Measurement Report
(adjacent GSM cells, RxLev)
RRC: Handover from UTRAN Command
GSM BSIC
Verification
GSM RSSI
Measurement
RANAP: Relocation Required
RANAP: Relocation Command
RANAP: IU Release Command
RANAP: IU Release Complete
IS_HHO_Att_xx
Updated KPIs for RU20
RNC_298e, ISHO Attempts RT
RNC_299d, ISHO Attempts NRT
RNC_300g, Inter System RT Hard Handover Success Ratio
RNC_301e, Inter System NRT Hard Handover Sucs. Ratio
Formulas were updated due to introduction of RAN955 Power
Saving Mode for BTS. New counters* were added into the KPIs
formulas.
*Example: counter M1010 C226 The number of
ISHO attempts for RT due to cell shutdown (forced
ISHO for remaining UEs)
Inter System Handover
RNC196
RNC196
ISHO Success Rates decreased after PCD3.0 installation (correction announced)
ISHO Attempts NRT increased about 50% (under analysis)
RU10
WN6.0 PCD3.0
RU20 PCD2.0
CD0.0
ISHO Attempts NRT
increased
ISHO Success rates
decreased - SOLVED
HSDPA Data Volume and Throughput
Transferred data volume at Iub can be calculated as:
[ ] Mbit b RNC
1000
S S_MACD_BIT RECEIVED_H M5000C126_
608 _

=
HSDPA MAC-d net throughput at BTS [kbit/s] can be calculated as:
[ ]
[ ]
s Mbit d RNC /
s 60 ation period_dur 1000
TS HS_MACD_BI DISCARDED_ - S S_MACD_BIT RECEIVED_H
606 _

=
Kbit / 1000 gives Mbit
Measurement period given in minutes * 60 gives measurement
period in seconds
Mbit / measurement period gives Mbit / s
Thank You !
KPI overview
Thank You !
This is my wife
At least she knows how to DROP
KPI overview
- KPI Factors
- Blocking Rate,
- Call Drop Rate,
- HO Failure Rate
- HO Failure Rate
Reporting suites
- main existing KPI
Appendix
Reporting suite
Component
The RAN Reporting Suite Component is
designed to provide information for Service &
Network Planning, Service Creation, Service &
Network Monitoring and Business
Management
Predefined reports are available off-the-shelf
and are grouped in various RAN reporting
categories
categories
It is running on top of NetAct, on regional &
global cluster.
2. Pre-defined Reports Overview (1) RU10
Full Report Set
New RU10
Modified RU10
System Program RNC Level RSRAN000
System Program Cell Level RSRAN084
RNC Capacity RSRAN068
RNC capacity usage RSRAN085
Node B Capacity RSRAN066
Cell Capacity RSRAN067
Iub Capacity RSRAN087
Cell Power RSRAN086
NRT DCH Allocations Statistics RSRAN097
NRT Radio Bearer Statistics RSRAN013
1. System Program
2. Capacity
Service/Session Accessibility Analysis RSRAN073
Service/Session Accessability Detailed Analysis RSRAN105
Service/Session Retainability Analysis RSRAN079
Service/Session Retainability Detailed Analysis RSRAN106
RAB Holding Times RSRAN021
Service Summary RSRAN003
Allocated Traffic Amounts (R99 + HSPA) RSRAN070
Cell Data Volume and Throughput at RNC RSRAN077
Traffic Summary RSRAN026
Used CE Capacity per RB Type in RNC RSRAN022
Utilization Shares of Total Traffic Allocation Amounts RSRAN071
Packet Call RSRAN101
Traffic Model NW Dimensioning RSRAN088
Iur Traffic - L3 RSRAN100
Iub Traffic - Frame Protocol layer RSRAN096
3. Service Level
4. Traffic
Capacity content was improved and extended
Service reports updated
Traffic content extended
2. Pre-defined Reports Overview (2)
RU10 Full Report Set
New RU10
Modified RU10
Active Set Size for NRT, RT Traffic RSRAN078
HSPA Serving Cell Change RSRAN033
HSPA Inter-Freq HHO RSRAN089
IFHO Adjacencies RSRAN044
InterSystem Handover per Cause RSRAN019
InterSystem Handover Performance RSRAN023
InterSystem Handover Reasons RSRAN018
ISHO Adjacencies RSRAN045
Load Based HO Related Resources RSRAN047
Load Based IFHO/ISHO Performance RSRAN048
Load Based IFHO/ISHO Triggering RSRAN049
Service Based IFHO/ISHO Performance RSRAN050
SHO Adjacencies RSRAN046
Soft Handover Performance RSRAN028
5. Mobility and Handover
NBAP Signalling RSRAN027
RRC Signalling RSRAN038
PRACH Propagation Delay RSRAN104
HSPA Overview RSRAN092
HSPA Scheduling RSRAN091
CQI Distribution RSRAN039
HSPA Code and Modulation Usage RSRAN034
HSPA Power Distribution RSRAN074
Channel Switching and HSPA Layering RSRAN075
UE Power Headroom RSRAN090
MAC-hs Efficiency RSRAN040
MAC-hs Retransmissions by Code and Modulation Usage RSRAN041
Number of HSPA Users and UE capability RSRAN051
6. Signalling
7. HSPA
Mobility content was updated
Signaling content extended with new
PRACH delay report
HSPA content was improved, extended
and updated
RU10 Full Report Set
New RU10
Modified RU10
ATM Interface Traffic Load RSRAN081
IP Interface Throughput RSRAN099
ATM VCC Traffic Load RSRAN083
ATM VPC Traffic Load RSRAN082
FTM Packet Transport Performance RSRAN076
FTM Performance RSRAN072
Iu-PS Throughputs RSRAN064
Iu-PS Throughputs (GTP + NP8S1 or NP2GE int) RSRAN104
Iu-CS RSRAN094
M3UA RSRAN093
ATM Iub Throughput RSRAN080
IP Iub Throughput (BTS pov) RSRAN095
8. Transport
Traffic on AAL5 RSRAN031
Traffic on ATM Layer RSRAN029
Traffic on Physical Medium SubLayer RSRAN030
IP Transport Resource Reservations RSRAN098
ATM Transport Resource Reservations RSRAN069
DSP Resource Usage RSRAN102
DSP State Changes RSRAN103
9. Hardware
Transport content extended to support new
IP based interfaces
New Hardware utilization monitoring
content created
RU20 (Version RS 5.3.1)
New RU20
Modified RU20
Removed RU20
System Program RNC Level RSRAN000
System Program Cell Level RSRAN084
RNC Capacity RSRAN068
RNC capacity usage RSRAN085
Node B Capacity RSRAN066
Cell Capacity RSRAN067
Iub Capacity RSRAN087
Cell Power RSRAN086
NRT DCH Allocations Statistics RSRAN097
1. System Program
2. Capacity
3. Service Level
Capacity Reports
improved with HSPA
users sampled from
WBTS. Some minor
corrections done!
Service reports updated
Traffic Model NW
Dimensioning: some
Service/Session Accessability Detailed Analysis RSRAN105
Service/Session Retainability Analysis RSRAN079
Service/Session Retainability Detailed Analysis RSRAN106
RAB Holding Times RSRAN021
Service Summary RSRAN003
Allocated Traffic Amounts (R99 + HSPA) RSRAN070
Cell Data Volume and Throughput at RNC RSRAN077
Traffic Summary RSRAN026
Used CE Capacity per RB Type in RNC RSRAN022
Utilization Shares of Total Traffic Allocation Amounts RSRAN071
Packet Call RSRAN101
Traffic Model NW Dimensioning RSRAN088
Iur Traffic - L3 RSRAN100
Iub Traffic - Frame Protocol layer RSRAN096
4. Traffic
Dimensioning: some
KPIs corrected
RU20
New RU20
Modified RU20
Active Set Size for NRT, RT Traffic RSRAN078
HSPA Serving Cell Change RSRAN033
HSPA Inter-Freq HHO RSRAN089
IFHO Adjacencies RSRAN044
InterSystem Handover per Cause RSRAN019
InterSystem Handover Performance RSRAN023
InterSystem Handover Reasons RSRAN018
ISHO Adjacencies RSRAN045
Load Based HO Related Resources RSRAN047
Load Based IFHO/ISHO Performance RSRAN048
Load Based IFHO/ISHO Triggering RSRAN049
Service Based IFHO/ISHO Performance RSRAN050
SHO Adjacencies RSRAN046
Soft Handover Performance RSRAN028
5. Mobility and Handover
HSPA reports updated
according to RU20 CPC,
HSPA 72 Users Per Cell
and HSUPA 2 ms TTI
features
NBAP Signalling RSRAN027
RRC Signalling RSRAN038
PRACH Propagation Delay RSRAN104
HSPA Overview RSRAN092
HSPA Scheduling RSRAN091
CQI Distribution RSRAN039
HSPA Code and Modulation Usage RSRAN034
HSPA Power Distribution RSRAN074
Channel Switching and HSPA Layering RSRAN075
UE Power Headroom RSRAN090
MAC-hs Efficiency RSRAN040
MAC-hs Retransmissions by Code and Modulation Usage RSRAN041
Number of HSPA Users and UE capability RSRAN051
6. Signalling
7. HSPA
RU20
New RU20
Modified RU20
ATM Interface Traffic Load RSRAN081
IP Interface Throughput RSRAN099
ATM VCC Traffic Load RSRAN083
ATM VPC Traffic Load RSRAN082
FTM Packet Transport Performance RSRAN076
FTM Performance RSRAN072
Iu-PS Throughputs RSRAN064
Iu-PS Throughputs (GTP + NP8S1 or NP2GE int) RSRAN104
Iu-CS RSRAN094
M3UA RSRAN093
8. Transport
IP Iub Throughput (BTS pov) RSRAN095
Traffic on AAL5 RSRAN031
Traffic on ATM Layer RSRAN029
Traffic on Physical Medium SubLayer RSRAN030
IP Transport Resource Reservations RSRAN098
ATM Transport Resource Reservations RSRAN069
DSP Resource Usage RSRAN102
DSP State Changes RSRAN103
8. Hardware
RU20 System Program modifications
There are several KPI modifications in System Program reports
New KPIs
Modified KPIs
Microsoft Office
Excel Worksheet
RNC_5058a PS NRT Serv Dur min
RNC_1906a R99 PS att #
RNC_5059a NRT Dur min
RNC_5066a Intra-RNC HHO Att, CS #
RNC_5067a Intra-RNC HHO Att, PS #
RNC_1879b Avg HSDPA end usr thp kbps
RNC_1883b HSUPA Act Cell Thp kbps
RNC_5068a MTC Share %
RNC_231d RAB SR AMR Voice %
RNC_737b Min per Drop Voice min
RNC_232e RAB SR UDI %
RNC_232e RAB SR UDI %
RNC_738b Min per Drop UDI min
RNC_615c PS NRT RAB SR NW %
RNC_736b PS NRT RAB SR, User %
RNC_619b RAB SR Stream %
RNC_740b M-RAB att #
RNC_741b M-RAB stp and acc SR %
RNC_742b M-RAB SR %
RNC_298e ISHO att RT #
RNC_299d ISHO att NRT #
RNC_300g RT SR %
RNC_301e NRT SR %
RNC_302d RT DR %
RNC_303d NRT DR %
RNC_607d HSDPA MAC-hs efficiency %
RNC_918b HSUPA SCC SR %
RNC_280c Total CS traffic E
RNC_5051b Iu-PS Data per drop, IP Mbit
RNC_5050b Iu-PS Data per drop, ATM Mbit
RNC_943a R99 Setup SR, NRT %
RNC_5007a R99 Setup SR, RT %
RNC_944a R99 SR NRT %
RNC_5015a R99 SR RT %
RNC_5000b HSDPA res acc RT %
RNC_5010a HSDPA res retain RT %
RNC_5002a HSUPA res acc RT %
RNC_5012a HSUPA res retain RT %
Deleted KPIs
RU20 Other KPI corrections/improvements
RSRAN068 RNC Capacity
Iub data traffic KPI group was changed to be based upon Frame Protocol
metrics;
Following KPIs were corrected
RNC_986b PS Data in DL
RNC_985b PS Data in UL
RNC_1064a CS Data moved to Iu-PS (R99+HSPA) traffic group
RNC_982b HSDPA Throughput moved to Traffic Profile group
RNC_982b HSDPA Throughput moved to Traffic Profile group
RSRAN088 - Traffic Model NW Dimensioning
Following KPIs were corrected:
RNC_1867b CS Voice
RNC_1868b CS Data Conv
RNC_1869b CS Data Stream
RSRAN066 - Node B Capacity
Introduced three new KPI groups to monitor Channel Element Utilization
Ratios:
CE Utilization Ratio DL;
CE Utilization Ratio UL
CE HSPA Utilization Ratio.
New KPI group to monitor amount of HSPA user in WBTS:
Number of HSPA Users
Number of HSPA Users
RSRAN067 Cell Capacity
Introduced a new KPI group to monitor common channel load:
Common chn avg load
RSRAN044 - IFHO Adjacencies
RSRAN045 - ISHO Adjacencies
RSRAN046 - SHO Adjacencies
Improvements were introduced to achieve:
Neighbour classification of each adjacent pair;
All neighbour adjacent pair are shown even if no handover events exist;
Easy identification of candidate adjacencies for neighbour configuration.
RSRAN092 HSPA Overview
HSUPA usage KPI group extend to support new features:
HSUPA 2ms TTI
Continuous Packet Connectivity group provide information about:
CPC User Share;
User Inactivity ratio;
Average CPC Users;
HSUPA transmitted power
Thank You !
KPI overview
Reporting suites
Thank You !
First high level report First high level report
New states and New states and
one new user one new user
KPI overview
- KPI Factors
- Blocking Rate,
- Call Drop Rate,
- HO Failure Rate
- HO Failure Rate
Reporting suites
- main existing KPI
Appendix
Target issues for performance optimizations are to Target issues for performance optimizations are to
assume and evaluate counter values by detecting of failures and success
figures, threshold values and increment target parameters with impact of
3G RAN and transmission actual quality impacts to assume performance
situations
Therefore check counters to ensure the RAN/Core QoS:
Counter strategy
Therefore check counters to ensure the RAN/Core QoS:
- Detect fault based by counters within performance measurements
- Assume NED (Nokia electronic dictionary), PDF data
- Match Excel data or/and KPI description with KPI
- Move to RAN Parameter setting and trace at interfaces e.g. Iub/Iur/Iu.
Coverage counters (more classes than before) to see sudden change in UL/DL
interference (Tx Carrier Power, Tx code power, UL Received Total Wideband Power
(RTWP)*
Improvement in Mobility
SHO branch setup fail due to BTS/iub
Voice RAB Setup fail Iur_TR / Iu_cs
Counter strategy: Useful RU20 counters in Basic Optimization
DCH setup failure for NRT in Iur
Relocation success in target RNC
ISHO : HHO RRSI & BSIC time & Isho cancellation
SHO based on DSR (Detected Set Reporting)
SHO Overhead based on CPICH EcNo difference
Intra/Inter-Frequency Inter RNC Hard HO/ISHO (RRC active release)
*Example counters: M1000C320 M1000C341 RTWP classes 0 to 21
M1000CC342- M1000C352 Transmitted carrier power classes 0 to 10
In RU20 there are some new counters which can be used to identify
Capacity bottlenecks or Monitor new RU20 capacity features
New traffic class (1002) counters to monitor DCH setup and
Reconfiguration rejections due the codes & power (DL & UL)
New Counters to monitor HSDPA MAC-d Setup failures
New Counters to monitor Average & Max number of HSPA users
Counters to monitor HSDPA power distribution and BTS scheduling
Counter strategy: Useful RU20 counters in Capacity Optimization
Counters to monitor HSDPA power distribution and BTS scheduling
efficiency => Spectral Efficient Link Adaptation RNC
New measurements M802 can be used to monitor RNC capacity
usage
SW license key controlled RNC capacity
New RNC DSP Resource Counters (M609, M615, M612, M617)
Additional HSPDA
RAN1509: RAB Bit Rate Counters
-
Traffic & Capacity
RAN1312: Channel Element Utilization in WBTS
Example of New RU20 counter features
RAB Bit Rate Counters
Possibility to follow HSDPA utilization need in network
HSDPA UE (*)
capability class
QPSK
5 HS-PDSCH Codes
64 QAM
16 QAM
15 HS-PDSCH Codes
4/4 Turbo coding 1/4 Turbo coding
Used modulation
Available codes
Used channel coding
2/4 coding 3/4 coding
HSDPA
performance
Issues in
network
DL Bit Rate ranges implementation based on:
UE Category (*)
HSDPA performance issues
NSN HSDPA features (see HSDPA features in FUDs)
Max 0.9 M 0.9 M-1.8M 1.8M-3.6M 3.6M-7.2M 10M-14.4M 7.2 M-10M 14.4 M < x < 40 M
UE Cat 11 UE Cat 12 UE Cat 1-6
< 384 K
R99
capability class
UE Cat 10 UE Cat 9 UE Cat 7-8
HSDPA Bit
rate ranges for
UE capabilities
UE Cat 13-18
(*) UE classes are here used to help the reader to split out exactly the range of the RAB provided by the Core Network matching with the UE classes.
UE capability provided by PI RRC establishments per UE Capability, M1001XX
384Kb-1.8 M 1.8M-3.6M 3.6M-7.2M 7.2 M-10M 10M-14.4M >14.4M
DL RAB Bit rate
counter ranges
Possibility to follow HSUPA utilization need in network
SF4
UE Category 1 UE Category 2-3 R99
HSUPA UE (*)
capability class
2 x SF4
UE Category 6 UE Category 4
UE Category 5
10 ms 2 ms
Possible SFs
Parallel SFs
TTI interval
SF2
2 x SF2 2 x SF2 + 2 x SF4
HSDPA
performance
Issues in
network
Max 0.72 M 0.72 M-1.45M
1.45 M-2M 2 M-2.91 M 2.91 M < x < 5.8 M < 384 K
HSUPA Bit
rate ranges for
UE capabilities
UL Bit Rate ranges implementation based on:
UE Category (*)
HSUPA performance issues
NSN HSUPA features (see HSUPA features in FUDs)
= < 2 M > 2 M
DL RAB Bit rate counter ranges
(*) UE classes are here used to help the reader to split out exactly the range of the RAB provided by the Core Network matching with the UE classes.
UE capability provided by PI RRC establishments per UE Capability, M1001XX
M1001C659 RAB SETUP ATTEMPTS FOR DL MAX BIT RATE - CLASS 1
DL
M1001C666 RAB SETUP ATTEMPTS FOR UL MAX BIT RATE - CLASS 1
UL
RAN1509
Number of RAB setup attempts for DL for Class ...
Class 1 -> (<= 384 kbps)
Class 2 -> (> 384 kbps <= 1.8 Mbps)
Class 3 -> (> 1.8 Mbps <= 3.6 Mbps)
Class 4 -> (> 3.6 Mbps <= 7.2 Mbps)
Class 5 -> (> 7.2 Mbps <= 10 Mbps)
Class 6 -> (> 10 Mbps <= 14.4 Mbps)
Dlink
Class 6 -> (> 10 Mbps <= 14.4 Mbps)
Class 7 -> (> 14.4 Mbps)
Number of RAB setup attempts for UL for Class ...
Class 1 -> (<= 128 kbps)
Class 2 -> (> 128 kbps <= 384 kbps)
Class 3 -> (> 384 kbps <= 1 Mbps)
Class 4 -> (> 1 Mbps <= 2 Mbps)
Class 5 -> (> 2 Mbps)
Ulink
RAB setup Bitrates uplink -example
60%
80%
100%
RAB_STP_ATT_BR_CLASS_5_UL
(M1001C670)
(M1001C669)
(M1001C668)
More than 50 %
of the RAB
setups are >2
Mits/s
0%
20%
40%
1
3
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
8
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
8
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
(M1001C667)
(M1001C666)
RAB setup Bitrates downlink -example
60%
80%
100%
RAB_STP_ATT_BR_CLASS_1_DL
(M1001C659)
(M1001C665)
(M1001C664)
(M1001C663)
0%
20%
40%
1
3
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
1
8
:
0
0
:
0
0
1
3
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
1
8
:
0
0
:
0
0
1
4
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
0
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
6
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
5
.
0
3
.
2
0
1
0
_
_
1
2
:
0
0
:
0
0
(M1001C662)
(M1001C661)
(M1001C660)
RAN 1312
Channel Element Utilization in WBTS
Total Licensed Capacity
0-50%,
51-70%,
71-90%,
90-99%,
100%
Total
The RAN1312 introduces new counters to
monitor Channel Elements distribution inside the
WBts. It is a completly new concept in
comparison to the existing counters since the new
new ones are showing percentage of utilization.
helping the customer to trigger the investments for CEs expansions.
HSPA UL and HSPA DL distribution of the
total utilized CE capacity
20%,
40%,
60%,
80%,
100%
100%
70-90%
90-99%
50-70%
100%
HSPA UL
HSPA DL
new ones are showing percentage of utilization.
RAN 1312
Channel Element Utilization in WBTS
BTS CE TOTAL UTIL UL - CLASS 1 (0 - <50) %
BTS CE TOTAL UTIL UL - CLASS 5 (90 -<100)%
BTS CE TOTAL UTIL UL - CLASS 6 (100) %
BTS CE HSPA UTIL UL - CLASS 1 (0 - 20) %
BTS CE HSPA UTIL UL - CLASS 2 (>20 - 40) %
HSPA CEs UL
TOTAL Amount of CEs
BTS CE TOTAL UTIL DL - CLASS 1 (0 - <50) %
BTS CE TOTAL UTIL DL - CLASS 5 (90 -<100)%
BTS CE TOTAL UTIL DL - CLASS 6 (100) %
BTS CE HSPA UTIL DL - CLASS 1 (0 - 20) %
BTS CE HSPA UTIL DL - CLASS 2 (>20 - 40) %
In customer documentation: M5001C15 - M5001C36
HSPA CEs DL
Total CE Utilization share in UL example
50%
60%
70%
80%
90%
100%
85.00
90.00
95.00
(100 or more)% M5001C20
(90 - <100)% M5001C19
(80 - <90)% M5001C18
(70 - <80)% M5001C17
(50 - <70)% M5001C16
0%
10%
20%
30%
40%
1
1
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
1
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
3
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
7
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
9
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
2
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
1
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
5
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
7
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
1
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
70.00
75.00
80.00
(0 - <50)% M5001C15
Avg Ratio of Used CE for UL in BTS
RNC_731A
CE HSPA Utilization share in UL +Max HSDPA users-
example
50%
60%
70%
80%
90%
100%
20
25
30
35
40
UL(90 - <100)% M5001C31
UL (80 - <90)% M5001C30
UL (70 - <80)% M5001C29
UL (50 - <70)% M5001C28
UL (0 - <50)% M5001C27
Max HSUPA Users M1031C1
0%
10%
20%
30%
40%
1
1
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
1
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
3
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
7
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
1
9
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
2
1
:
0
0
:
0
0
1
1
.
0
3
.
2
0
1
0
_
_
2
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
1
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
5
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
7
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
0
9
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
1
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
3
:
0
0
:
0
0
1
2
.
0
3
.
2
0
1
0
_
_
1
5
:
0
0
:
0
0
0
5
10
15
Max HSUPA Users M1031C1
Max HSDPA Users M1031C0
Avg ratio of Used CE for UL for HSUPA in
BTS RNC_948A
Avg ratio of Used CE for DL for HSUPA in
BTS RNC_947A
RAN1136
Separate Counters for Relocations
The outgoing relocation is currently visible, M1001C13, but not separated per:
SRNS relocation,
Inter RNC HHO
Inter RAT HHO in counters.
By this feature the operator is able to monitor the frequency and success of SRNS
relocations in all relevant cases, i.e SRNS Relocation, Inter RNC HHO and Inter
RAT HHO.
RAT HHO.
The incoming relocation is also visible, M1001C62, but not separated per:
traffic class
Separate Counters for Relocations
2G-Core
BSC
Abis
A
RNC
Iub
Iu
UMTS
GSM
New counters for Inter
RAT HHO
Relocated UE
Current Relocation
CS:RNC commands the UE the GSM
PS:RNC detects UE has moved
Inter RNC HHO
neededSRNS
3G-Core
Iub
Iu
RNC
Iub
Iu
Iur
New counters for
SRNS and Inter RNC
HHO Relocated UE
Current Relocation
RANAP:Iu Release Complete
Existing counters for L3
layer related
Relocation signal
Existing counters
for air interference
related relocation
RRC signaling
No more WCell in AS for the current RNC
i.e. last RL deleted in current RNC
neededSRNS
relocation needed
RAN1136
Separate Counters for Incoming Relocations
RRC_RELOC_STP_ATT updated a target RNC of HHO or relocation receives a RANAP:
RELOCATION REQUEST message from a core network
RAB_RELOC_STP_ATT updated when a target RNC of HHO or relocation receives a
RANAP: RELOCATION REQUEST message from a core network and the RAB type is
known
RAB_RELOC_ACC_COMP updated when When a target RNC of HHO or relocation
sends a RANAP: RELOCATION COMPLETE message to a core network after a
successful incoming SRNC relocation, Inter-RNC HHO or ISHO procedure
Reloc
M1001C808 ServiceLevel RRC_RELOC_STP_ATT
Reloc
M1001C808 ServiceLevel RRC_RELOC_STP_ATT
M1001C810 ServiceLevel RRC_RELOC_ACC_COMP
M1001C651 ServiceLevel RAB_RELOC_STP_ATT_PS_STREA
M1001C817 ServiceLevel RAB_RELOC_STP_ATT_PS_INT
M1001C826 ServiceLevel RAB_RELOC_STP_ATT_PS_BGR
M1001C653 ServiceLevel RAB_RELOC_STP_ATT_CS_VOICE
M1001C657 ServiceLevel RAB_RELOC_STP_ATT_CS_STREA
M1001C655 ServiceLevel RAB_RELOC_STP_ATT_CS_CONV
M1001C652 ServiceLevel RAB_RELOC_ACC_COMP_PS_STREA
M1001C819 ServiceLevel RAB_RELOC_ACC_COMP_PS_INT
M1001C828 ServiceLevel RAB_RELOC_ACC_COMP_PS_BGR
M1001C654 ServiceLevel RAB_RELOC_ACC_COMP_CS_VOICE
M1001C658 ServiceLevel RAB_RELOC_ACC_COMP_CS_STREA
M1001C656 ServiceLevel RAB_RELOC_ACC_COMP_CS_CONV
RAN1136
Separate Counters for HHO, ISHO and Relocations only
Outgoing relocations
ISHO
IFHO
M1001C647 ServiceLevel RAB_ACT_REL_CS_VOICE_ISHO
M1001C649 ServiceLevel RAB_ACT_REL_CS_STREA_ISHO
M1001C646 ServiceLevel RAB_ACT_REL_CS_STREA_HHO
M1001C644 ServiceLevel RAB_ACT_REL_CS_VOICE_HHO
M1001C801 ServiceLevel RAB_ACT_REL_PS_INTER_HHO
M1001C645 ServiceLevel RAB_ACT_REL_CS_CONV_HHO
M1001C802 ServiceLevel RAB_ACT_REL_PS_BACKG_HHO
M1001C806 ServiceLevel RAB_ACT_REL_PS_STREA_HHO
Inter RNC
HHO
Inter System
HHO
ISHO
Reloc
M1001C649 ServiceLevel RAB_ACT_REL_CS_STREA_ISHO
M1001C648 ServiceLevel RAB_ACT_REL_CS_CONV_ISHO
M1001C805 ServiceLevel RAB_ACT_REL_PS_BGR_ISHO
M1001C807 ServiceLevel RAB_ACT_REL_PS_STREA_ISHO
M1001C804 ServiceLevel RAB_ACT_REL_PS_INTER_ISHO
M1001C153 ServiceLevel RAB_ACT_REL_CS_STREA_SRNC
M1001C151 ServiceLevel RAB_ACT_REL_CS_CONV_SRNC
M1001C169 ServiceLevel RAB_ACT_REL_PS_STREA_SRNC
M1001C171 ServiceLevel RAB_ACT_REL_PS_INTER_SRNC
M1001C167 ServiceLevel RAB_ACT_REL_PS_CONV_SRNC
M1001C172 ServiceLevel RAB_ACT_REL_PS_BACKG_SRNC
M1001C143 ServiceLevel RAB_ACT_REL_CS_VOICE_SRNC
Existing
counters,
but not for
HHO
anymore
Poor CSSR could be a result of
Poor coverage or dominance or interference issues in Radio interface
Capacity issues in Radio or Iub interface
Configuration issues in WBTS (parameters or HW)
CSSR is essentially
RRC Setup Success * RAB Setup Success RRC Setup Success * RAB Setup Success
Call Completion Success Rate - CCSR
KPI construction - call setup (un)success rate
is starting to get transferred.
The CSSR formulas are for different traffic classes like:
CS voice calls (RNC 565 f)
CS video calls (RNC 566e)
PS RT Streaming Calls (RNC 575 d)
PS NRT Calls (Interactive & Background) (RNC 576d)
UE
RRC: Connection Request
RRC Connection Setup phase
RRC: RRC Connection Request Setup
RRC Connection Access phase
RRC: RRC Connection Completed
RRC: Initial Direct Transfer cm service request
BTS
RNC CN
Call Set-up
Definition of Call Set-Up Success Rate (CSSR)
Proceeding)
Request
RRC: Radio Bearer Set-up
RRC: Radio Bearer Setup
Complete
RAB Connection Setup phase
Response
DIRECT TRANSFER (Alerting)
DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect
Acknowledge)
RAB Connection Access phase
Call Set-up
Success
Rate
Call Set-up
Time
CSSR KPI for CS voice from end user perspective (RNC 565f)
)) _ _ _ _ (
) _ _ _ _ ( (
*
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ (
) _ _ _ _
_ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ ( ( * 100
_
CONV MT REL ACC RRC
CSSR AMR

+
+

+
+
=
RRC part
RAB part
RRC request repetitions done by UE after RRC reject are excluded from denominator (not
necessarily seen as failures from the user's perspective)
Emergency calls re-directed to GSM layer are excluded from denominator
The occurred cell re-selections are subtracted both from the numerator and denominator
because they are not considered as call attempts from mobile end-user point of view. The UE
has made a new RRC connection via another cell and Attempts-counter is updated in the new
cell for the new attempt.
RRC part
RAB part
CSSR PS NRT
ents establishm RAB PS for attempts
ents establishm RAB PS successful
setups connection PS RRC for attempts repetetive
setups connection PS RRC for attempts
setup connection PS RRC during ns reselectio cell
setups connection PS RRC of failures
setups connection PS RRC for attempts
CSSR PS
_ _ _ _
_ _ _
*
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_
=
Service level evaluations (PS)
setup connection PS RRC during ns reselectio cell
setups connection PS RRC for attempts repetetive
_ _ _ _ _ _
_ _ _ _ _ _
CSSR KPI for PS NRT
from end user perspective (rnc_576d)
Includes both Interactive and Background PS calls
Counts from RRC request until RAB is established (with 0/0 RB)
Same as CSSR for AMR, except:
Emergency calls not included
Counters for NRT RAB instead of Voice RAB
Service level evaluations (PS/NRT)
RNC_576e Packet Call Setup Success Ratio [%] over the reporting period.
Includes both Interactive and Background PS calls
Counts from RRC request until RAB is established (with 0/0 RB)
)) _ _ _ _
_ _ _ _ (
) _ _ _ _
_ _ _ _ ( (
*
_ _ _ _ _ _
ATTS RIOR_SIGN_ MTC_HIGH_P ATTS RIOR_SIGN_ MOC_HIGH_P
_ _ _ _ _ _ (
) PR_SIGN L_MT_HIGH_ RRC_ACC_RE - PR_SIGN L_MO_HIGH_ RRC_ACC_RE
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_FAILS] PRIOR_SIGN [MTC_HIGH_ - _ATTS PRIOR_SIGN [MTC_HIGH_
FAILS] RIOR_SIGN_ MOC_HIGH_P - _ATTS PRIOR_SIGN [MOC_HIGH_
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _ ( ( * 100
_
BACKG PS ATT STP RAB
INTER PS ATT STP RAB sum
BACKG PS COMP ACC RAB
INTER PS COMP ACC RAB sum
ATTS CALL BACKG MTC ATTS CALL INTER MTC
ATTS CALL BACKG MOC ATTS CALL INTER MOC sum
BACKG MT REL ACC RRC INTER MO REL ACC RRC
BACKG MO REL ACC RRC INTER REL ACC RRC
FAILS CALL BACKG MTC ATTS CALL BACKG MTC
FAILS CALL INTER MTC ATTS CALL INTER MTC
FAILS CALL BACKG MOC ATTS CALL BACKG MOC
FAILS CALL INTER MOC ATTS CALL INTER MOC sum
CSSR PS
+
+
+ +
+ +
+

+
+
+
+
+
=
PS Call Setup Success Rate (CSSR)
Same as CSSR for AMR, except:
Emergency calls not included
In RU10 it was decided that also RRC Connection Establishment requests with 'high priority
signaling' are interpreted as Packet Service requests.
)) PR_SIGN L_MT_HIGH_ RRC_ACC_RE - PR_SIGN L_MO_HIGH_ RRC_ACC_RE
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _
PR_SIGN P_MT_HIGH_ RRC_ATT_RE - PR_SIGN P_MO_HIGH_ RRC_ATT_RE
_ _ _ _ _ _ _
_ _ _ _ _ _
BACKG MT REL ACC RRC INTER MO REL ACC RRC
BACKG MO REL ACC RRC INTER REL ACC RRC
BACKG MT REP ATT RRC BACKG MO REP ATT RRC
INTER MO REP ATT RRC INTER REP ATT RRC
ATTS CALL BACKG MTC ATTS CALL INTER MTC

+ +
RRC part
RAB part
Includes PS NRT traffic
(Interactive & Background) but
not PS RT traffic
_DCH_BGR PS_ATT_DCH M1022C8 + _DCH_INT PS_ATT_DCH M1022C7

D_ALLO_BGR D_D_REQ_D_ M1022C32 + D_ALLO_INT D_D_REQ_D_ M1022C31
100
Interactive RAB
Service level evaluations (PS/Release 99)
Request in DL: DCH
Allocated in DL: DCH
Request in UL: DCH
Allocated in UL: DCH
=
GR SCH_EDCH_B PS_ATT_HSD M1022C4 + NT SCH_EDCH_I PS_ATT_HSD M1022C3
GR S_E_ALLO_B HS_E_REQ_H M1022C21 + NT S_E_ALLO_I HS_E_REQ_H M1022C21
e[%] Perspectiv User from Ratio Success Setup HSUPA RNC_915a
Packet Call: SSSR HSUPA (HSDPA + HSUPA)
Here all possible success combinations without R99 (R5 / R6)
Request Allocation
HSDPA + HSUPA HSDPA + HSUPA
HSDPA + HSUPA HSDPA + DCH
HSDPA + DCH HSDPA + DCH
UE wants to get both HS-DSCH + E-DCH R5 + R6 resource
+
+
+
=
GR S_D_ALLO_B HS_E_REQ_H M1022C24 + NT S_D_ALLO_I HS_E_REQ_H M1022C23 +
GR S_E_ALLO_B HS_E_REQ_H M1022C22 + NT S_E_ALLO_I HS_E_REQ_H M1022C21
[%] Ratio Success Setup Session Packet RNC_916
Packet Call: SSSR - All NRT packet sessions
(HSPA + R99)
+ +
+
+
+ +
+
_DCH_BGR PS_ATT_DCH M1022C8 + _DCH_INT PS_ATT_DCH M1022C7 +

R SCH_DCH_BG PS_ATT_HSD M1022C6 T SCH_DCH_IN PS_ATT_HSD M1022C5 +
GR SCH_EDCH_B PS_ATT_HSD M1022C4 + NT SCH_EDCH_I PS_ATT_HSD M1022C3
D_ALLO_BGR D_D_REQ_D_ M1022C32 + D_ALLO_INT D_D_REQ_D_ M1022C31 +
R _D_ALLO_BG HS_D_REQ_D M1022C30 + T _D_ALLO_IN HS_D_REQ_D M1022C29 +
R _D_ALLO_BG HS_E_REQ_D M1022C28 T _D_ALLO_IN HS_E_REQ_D M1022C27 +
GR S_D_ALLO_B HS_D_REQ_H M1022C26 + NT S_D_ALLO_I HS_D_REQ_H M1022C25 +
100
Formula is a combination of 3 formulas (HSUPA, HSDPA, Rel99)
Only NRT sessions included (both interactive & background)
Here all possible success combinations Here all possible success combinations
Packet Call: SSSR - All NRT packet sessions (at least Cell_DCH)
Here all possible success combinations Here all possible success combinations
Request Request Allocation Allocation
HSDPA + HSUPA HSDPA + HSUPA HSDPA + HSUPA HSDPA + HSUPA
HSDPA + HSUPA HSDPA + HSUPA HSDPA + DCH HSDPA + DCH
HSDPA + HSUPA HSDPA + HSUPA DCH + DCH DCH + DCH
HSDPA + DCH HSDPA + DCH HSDPA + DCH HSDPA + DCH
HSDPA + DCH HSDPA + DCH DCH DCH + DCH + DCH
DCH + DCH DCH + DCH DCH DCH + DCH + DCH
Packet Call Setup Success Ratio [%]
over the reporting period. Includes
both Interactive and Background PS
calls
(in comparison to previous slides
emergency calls included)
For voice KPI = % of successfully
established voice calls
For PS KPI = % of successfully
RRC request repetitions done by UE after RRC
reject are included in the formula
* The occurred cell re-selections are subtracted
both from the numerator and denominator
because they are not considered as call attempts
from mobile end-user point of view. The UE has
made a new RRC connection via another cell
and Attempts-counter is updated in the new cell
for the new attempt.
For PS KPI = % of successfully
established PS calls
RNC_5016a= Maximum number of AMR calls per
RNC=max(M802C1)
RNC_5017a Peak number of HSDPA users in RNC (M609)=
max(DSP_SERVICE_PEAK_RES_ALLOC, service type
ALLHSDPA)
RNC_5018a Peak number of HSUPA users in RNC (M609)=
max(DSP_SERVICE_PEAK_RES_ALLOC, service type
ALLHSUPA)
RNC_5004a Incoming Inter System HHO Success in Target RNC
New KPIs (RU10)
KPI construction - packet call setup
RNC_5004a Incoming Inter System HHO Success in Target RNC
for CS (M1009)=
100* sum(IS_COMPL_TARGET_RNC) / sum(IS_HHO_IN_PREP_REQ)
RNC_5008a Relocation Success in Target RNC for CS (M1009)=
100 * sum(SRNS_RELOC_COMPL_RNC_MSC +
INTER_HHO_COMPL_IN_RNC_MSC) / sum(SRNS_RELOC_IN_REQ_CONTR_MSC
+ INTER_RNC_HHO_IN_REQ_MSC)
RNC_5009a Relocation Success in Target RNC for PS (M1009)=
100* sum(SRNS_RELOC_COMPL_RNC_SGSN +
INTER_HHO_COMPL_IN_RNC_SGSN) /
sum(SRNS_RELOC_IN_REQ_CONTR_SGSN+ INTER_RNC_HHO_REQ_SGSN)
RNC_5019a Iub data volume DL in BTS
(M5003)
sum(CCH_DATA_FROM_IUB +
DCH_DATA_FROM_IUB +
HSDSCH_DATA_FROM_IUB)*8 / 1000 [mbit]
RNC_5020a Iub data volume UL in BTS
(M5003)
sum(CCH_DATA_TO_IUB_INTERFACE +
New KPIs (RU10)
sum(CCH_DATA_TO_IUB_INTERFACE +
DCH_DATA_TO_IUB +
EDCH_DATA_TO_IUB)*8 / 1000 [MBit]
RNC_5021a Iu-PS peak throughput
(M802C9)
sum(IU_PS_THR_PEAK) / 1000 [MBits/s]
RNC_736b - RAB Success Ratio for NRT Services [%] from user
perspective over the reporting period.
Covers RAB Active Phase of a call. Includes both Interactive and
Background PS calls.
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ ( * 100 100
UE BACKG PS FAIL ACT RAB RNC BACKG PS FAIL ACT RAB
IUR BACKG PS FAIL ACT RAB BTS BACKG PS FAIL ACT RAB
RADIO BACKG PS FAIL ACT RAB IU BACKG PS FAIL ACT RAB
UE INTER PS FAIL ACT RAB RNC INTER PS FAIL ACT RAB
IUR INTER PS FAIL ACT RAB BTS INTER PS FAIL ACT RAB
RADIO INTER PS FAIL ACT RAB IU INTER PS FAIL ACT RAB sum
+ +
+ +
+
+ +
+ +
+
Both Interactive
and Background
PS calls
) _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
736 _
UE BACKG PS FAIL ACT RAB UE INTER PS FAIL ACT RAB
RNC BACKG PS FAIL ACT RAB RNC INTER PS FAIL ACT RAB
IUR BACKG PS FAIL ACT RAB IUR INTER PS FAIL ACT RAB
BTS BACKG PS FAIL ACT RAB BTS INTER PS FAIL ACT RAB
RADIO BACKG PS FAIL ACT RAB RADIO INTER PS FAIL ACT RAB
IU BACKG PS FAIL ACT RAB IU INTER PS FAIL ACT RAB
SRNC BACKG PS REL ACT RAB SRNC INTER PS REL ACT RAB
BACKG PS COMP ACT RAB INTER PS COMP ACT RAB sum
PCH INTER PS FAIL ACT RAB PCH BACKG PS FAIL ACT RAB
UE BACKG PS FAIL ACT RAB RNC BACKG PS FAIL ACT RAB
a RNC
+ +
+ +
+ +
+ +
+
+ +
+ + +
+

+ +
=
For NRT RABs pre-emption is not possible
As the formula is based on active fail counters is means in this case that when RAB drops in
CELL_PCH state that two fail counters are updated. This is taken into account in the formula (the
drops in CELL_PCH subtracted from all drops.)
RNC_736b - PS call drop ratio KPI is currently
same than RAB success for NRT services
Includes both Interactive and Background PS
calls
For NRT RABs pre-emption is not possible
As the formula is based on active fail
counters is means in this case that when
RAB drops in CELL_PCH state that two fail
RAB drops in CELL_PCH state that two fail
counters are updated. This is taken into
account in the formula (the drops in
CELL_PCH subtracted from all drops.)
For PS KPI 736a = % of
successfully terminated NRT RABs
Service level evaluations (CS)
) _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_GANHO L_CS_VOICE RAB_ACT_RE _ISHO L_CS_VOICE RAB_ACT_RE
_HHO L_CS_VOICE RAB_ACT_RE _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ ( * 100 100
231 _
UE VOICE CS FAIL ACT RAB RNC VOICE CS FAIL ACT RAB
IUR VOICE CS FAIL ACT RAB BTS VOICE CS FAIL ACT RAB
RADIO VOICE CS FAIL ACT RAB IU VOICE CS FAIL ACT RAB
EMP P VOICE CS REL ACT RAB
SRNC VOICE CS REL ACT RAB VOICE CS COMP ACT RAB sum
UE VOICE CS FAIL ACT RAB RNC VOICE CS FAIL ACT RAB
IUR VOICE CS FAIL ACT RAB BTS VOICE CS FAIL ACT RAB
RADIO VOICE CS FAIL ACT RAB IU VOICE CS FAIL ACT RAB
EMP P VOICE CS REL ACT RAB sum
c RNC
+ +
+ +
+ +
+
+ + +
+
+ +
+ +
+ +
=
For Voice, the
release due to pre-
emption is included
RAB considered Connection UE RAB considered Connection UE -- CN CN
CN
UE
Service level evaluations (CS)
RNC_231c - CDR KPI for CS Voice
(RAB success) from end user perspective
Covers RAB Active Phase of a call. Probability
that call has ended normally after setup has
been successful. This is taking into notice just
calls which has ended this cell, but might have
calls which has ended this cell, but might have
been started in other cells.
For CS KPI 231c = % of
successfully terminated AMR RABs
KPI construction - SHO Failure vs. success rate
SHO success rate KPI (195a) is informing how many successful Active set updates we will
have compared to initial Addition/Replacement/Deletion requests.
This formula is excluding periodical reports, which might occur if for example RNC is busy
and cannot process immediately initial request.
) _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _ _ _ _ ( * 100
_
NRT FOR SHO ON REQ DEL CELL NRT FOR SHO ON REQ REPL CELL
NRT FOR SHO ON REQ ADD CELL RT FOR SHO ON REQ DEL CELL
RT FOR SHO ON REQ REPL CELL RT FOR SHO ON REQ ADD CELL sum
NRT FOR SHO ON UPDATES SUCC RT FOR SHO ON UPDATES SUCC sum
Success SHO
+ +
+ +
+
+
=
RNC BTS
Decision to
set up new RL
Start TX/RX
ALCAP:ERQ
ALCAP:ECF
UE
RNC BTS
Decision to
set up new RL
Start TX/RX
ALCAP:ERQ
ALCAP:ECF
UE
+
+
+
+
ISHO Success Rate (HO from WCDMA to GSM)
Normally ISHO may fail due to missing target cell or the
cell is not good enough coverage, interference or
configuration problem
From the measurement point of view the ISHO is
divided into two phases:
Inter-system measurement
Inter-system handover
Inter-system handover
The Real Time and Non Real Time Inter System HO
differs in nature. Therefore the ISHO KPI can be splitted
in RT and NRT parts. In case of Multi-RAB having at
least one RT RAB only RT counters are updated and
the Handover is performed using RT handover
procedure
ISHO Success Rate
Example NBAP and RRC compressed mode signalling for a CS service ISHO
CN
UE Node B RNC
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
RRC: Physical Channel Reconfiguration
RRC: Physical Channel Reconfiguration Complete
ISHO
triggering
Initial
Compressed
Mode
Configuration
RRC: Handover from UTRAN Command
GSM BSIC
Verification
GSM RSSI
Measurement
RANAP: Relocation Required
RANAP: Relocation Command
RANAP: IU Release Command
RANAP: IU Release Complete
IS_HHO_Att_xx
KPI construction - ISHO Success Rate, RT
ISHO success rate for RT services (RNC_300g)
The Real Time and Non Real Time Inter System HO differs in nature. Therefore the ISHO
KPI is splitted in RT and NRT parts.
The Multi RAB ISHOs are only updated to RT counters. This because the NRT RB follows
the RT parameters when part of RT + NRT Multi RAB.
_ _ _ _ _ _ _UL_RT] HO_LB_CAPA [SUCC_IS_H
_DL_RT] HO_LB_CAPA [SUCC_IS_H _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ ( * 100
+ +
+ +
+ +
+ +
+
RT TOT PRX LB HHO IS SUCC
CALL EMERG HHO IS SUCC
RT IMS IM HHO IS SUCC RT ECNO CPICH HHO IS SUCC
RT RSCP CPICH HHO IS SUCC RT PWR DPCH DL HHO IS SUCC
RT PWR TRX UE HHO IS SUCC RT Q DCH UL HHO IS SUCC sum
ISHO success rate for NRT services (RNC_301e)
) _RT] CELL_BLOCK [ATT_ISHO_
OWN_RT] CELL_SHUTD [ATT_ISHO_ _AMR_RT] [ATT_GANHO PS_RT] T_UL_DCH_W [IS_HHO_AT
T_SB_RT] [IS_HHO_AT SC_RT] T_LB_RSVR_ [IS_HHO_AT IM_RT] T_LB_RES_L [IS_HHO_AT
OT_RT] T_LB_PTX_T [IS_HHO_AT OT_RT] T_LB_PRX_T [IS_HHO_AT UL_RT] T_LB_CAPA_ [IS_HHO_AT
DL_RT] T_LB_CAPA_ [IS_HHO_AT LL] T_EMERG_CA [IS_HHO_AT
T] T_IM_IMS_R [IS_HHO_AT NO_RT] T_CPICH_EC [IS_HHO_AT CP_RT] T_CPICH_RS [IS_HHO_AT
_RT] T_DPCH_PWR [IS_HHO_AT WR_RT] T_UE_TRX_P [IS_HHO_AT RT] _UL_DCH_Q_ IS_HHO_ATT (
) K_RT] _CELL_BLOC [SUCC_ISHO
DOWN_RT] _CELL_SHUT [SUCC_ISHO O_AMR_RT] [SUCC_GANH HO_WPS_RT] [SUCC_IS_H
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _UL_RT] HO_LB_CAPA [SUCC_IS_H
_ _
+
+ + +
+ + +
+ + +
+ +
+ + +
+ +
+
+ + +
+ +
+ +
+ +
=
sum
RT SB HHO IS SUCC RT SC RSVR LB HHO IS SUCC
RT LIM RES LB HHO IS SUCC RT TOT PTX LB HHO IS SUCC
RT TOT PRX LB HHO IS SUCC
RT Success ISHO
KPI construction - ISHO Success Rate, NRT
_ _ _ _ _ _ _ _ _ _ _ _ (
) _NRT CELL_BLOCK SUCC_ISHO_
OWN_NRT CELL_SHUTD SUCC_ISHO_ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ ( * 100
301 _
+
+
+ +
+ +
+ +
+ +
+ +
+ +
+
=
NRT PWR TRX UE ATT HHO IS NRT Q DCH UL ATT HHO IS sum
NRT SB HHO IS SUCC
NRT SC RSVR LB HHO IS SUCC NRT LIM RES LB HHO IS SUCC
NRT TOT PTX LB HHO IS SUCC NRT TOT PRX LB HHO IS SUCC
NRT UL CAPA LB HHO IS SUCC NRT DL CAPA LB HHO IS SUCC
NRT IMS IM HHO IS SUCC NRT ECNO CPICH HHO IS SUCC
NRT RSCP CPICH HHO IS SUCC NRT PWR DPCH DL HHO IS SUCC
NRT PWR TRX UE HHO IS SUCC NRT Q DCH UL HHO IS SUCC sum
e RNC
) NRT ELL_BLOCK_ ATT_ISHO_C N_NRT LL_SHUTDOW TT_ISHO_CE _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
+ + +
+ +
+ +
+ +
+ +
+ +
A NRT SB ATT HHO IS
NRT SC RSVR LB ATT HHO IS NRT LIM RES LB ATT HHO IS
NRT TOT PTX LB ATT HHO IS NRT TOT PRX LB ATT HHO IS
NRT UL CAPA LB ATT HHO IS NRT DL CAPA LB ATT HHO IS
NRT IMS IM ATT HHO IS NRT ECNO CPICH ATT HHO IS
NRT RSCP CPICH ATT HHO IS NRT PWR DPCH DL ATT HHO IS
KPIs for ISHO measurement started for RT and NRT
(RNC_294c, RNC_295c)
KPIs for not good enough cells for RT and NRT,
RNC_296a, and RNC_297a)
ISHO success rate for RT services (RNC_300g)
HHO trigger HHO trigger
UL SIR UL SIR
Target Target
UL UE power UL UE power
DL RL power DL RL power
CPICH RSCP CPICH RSCP
CPICH E CPICH E
cc
/I /I
00
IMSI based IMSI based
Emergency call Emergency call
Load based RTWP Load based RTWP
Load based TCP Load based TCP
Load based HW / logical res. Load based HW / logical res.
Load based code res. Load based code res.
Services based Services based
KPI 195a = % of successful active set updates
KPI 300g = % of successfully terminated ISHOs for RT RABs
Inter System Handover
RNC196
ISHO Success Rates decreased after PCD3.0 installation (correction announced)
ISHO Attempts NRT increased about 50% (under analysis)
RU10
WN6.0 PCD3.0
RU20 PCD2.0
CD0.0
ISHO Attempts NRT
increased
ISHO Success rates
decreased - SOLVED
+
+
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+ +

=
BGR FAIL_HS_E_ PS_REL_RL_ M1022C58 + INT FAIL_HS_E_ PS_REL_RL_ M1022C57
_STRE]) H_FAIL_D_D [PS_REL_OT D_STRE] H_FAIL_HS_ [PS_REL_OT
E_STRE] H_FAIL_HS_ [PS_REL_OT STRE] _FAIL_D_D_ [PS_REL_RL
_STRE] _FAIL_HS_D [PS_REL_RL _STRE] _FAIL_HS_E [PS_REL_RL
_BGR] H_FAIL_D_D [PS_REL_OT _INT] H_FAIL_D_D [PS_REL_OT
D_BGR] H_FAIL_HS_ [PS_REL_OT D_INT] H_FAIL_HS_ [PS_REL_OT
E_BGR] H_FAIL_HS_ [PS_REL_OT E_INT] H_FAIL_HS_ [PS_REL_OT
BGR] _FAIL_D_D_ [PS_REL_RL INT] _FAIL_D_D_ [PS_REL_RL
_BGR] _FAIL_HS_D [PS_REL_RL _INT] _FAIL_HS_D [PS_REL_RL
E_BGR] L_FAIL_HS_ )[PS_REL_R E_INT] L_FAIL_HS_ ([PS_REL_R
% 100 % 100
[%] Ratio Success Session Packet RNC_922b
The Packet Session Success Ratio for Streaming, Interactive and Background Services.
KPI construction packet session success ratio
All NRT sessions, 100 % -drop rate
+ +
+ +
+ +
+ +
+
+
+
+
+
+
+
+
+

E]) RM_D_D_STR [PS_REL_NO RE] RM_HS_D_ST [PS_REL_NO RE] RM_HS_E_ST [PS_REL_NO
_STRE] H_FAIL_D_D [PS_REL_OT D_STRE] H_FAIL_HS_ [PS_REL_OT
E_STRE] H_FAIL_HS_ [PS_REL_OT STRE] _FAIL_D_D_ [PS_REL_RL
_STRE] _FAIL_HS_D [PS_REL_RL _STRE] _FAIL_HS_E [PS_REL_RL
M_D_D_BGR PS_REL_NOR M1022C50 + M_D_D_INT PS_REL_NOR M1022C49 +
M_HS_D_BGR PS_REL_NOR M1022C48 + M_HS_D_INT PS_REL_NOR M1022C47 +
M_HS_E_BGR PS_REL_NOR M1022C46 + M_HS_E_INT PS_REL_NOR M1022C45 +
BGR _FAIL_D_D_ PS_REL_OTH M1022C68 + INT _FAIL_D_D_ PS_REL_OTH M1022C67 +
_BGR _FAIL_HS_D PS_REL_OTH M1022C66 + _INT _FAIL_HS_D PS_REL_OTH M1022C65 +
_BGR _FAIL_HS_E PS_REL_OTH M1022C64 + _INT _FAIL_HS_E PS_REL_OTH M1022C63 +
GR FAIL_D_D_B PS_REL_RL_ M1022C62 + NT FAIL_D_D_I PS_REL_RL_ M1022C61 +
BGR FAIL_HS_D_ PS_REL_RL_ M1022C60 + INT FAIL_HS_D_ PS_REL_RL_ M1022C59 +
BGR FAIL_HS_E_ PS_REL_RL_ M1022C58 + INT FAIL_HS_E_ PS_REL_RL_ M1022C57
% 100 % 100
All combinations
HSDPA + HSUPA, HSDPA + DCH, DCH + DCH
100%
+ M_HS_E_INT PS_REL_NOR M1022C45 E M_HS_E_STR PS_REL_NOR
_BGR _FAIL_HS_E PS_REL_OTH M1022C64 + _INT _FAIL_HS_E PS_REL_OTH M1022C63
_STRE _FAIL_HS_E PS_REL_OTH BGR FAIL_HS_E_ PS_REL_RL_ M1022C58
+ INT FAIL_HS_E_ PS_REL_RL_ M1022C57 STRE FAIL_HS_E_ PS_REL_RL_

_BGR _FAIL_HS_E PS_REL_OTH M1022C64 + _INT _FAIL_HS_E PS_REL_OTH M1022C63
_STRE _FAIL_HS_E PS_REL_OTH BGR FAIL_HS_E_ PS_REL_RL_ M1022C58
+ INT FAIL_HS_E_ PS_REL_RL_ M1022C57 STRE FAIL_HS_E_ PS_REL_RL_
100%
e Perspectiv User From Ratio Success HSUPA RNC_921b
+
+
+ +
+
+ +
+
=
Service level evaluations (HSUPA only)
KPI construction packet session success ratio
The HSUPA Success Ratio for Streaming, Interactive and
Background Services from user perspective.
This KPI is based on Packet Call Measurement (M1022)
Switching from HSPA to R99 is considered as a normal HSPA
release in the formula.
GR E_TO_D_D_B PS_SWI_HS_ NT E_TO_D_D_I PS_SWI_HS_
TRE E_TO_D_D_S PS_SWI_HS_ M_HS_E_BGR PS_REL_NOR M1022C46
+ M_HS_E_INT PS_REL_NOR M1022C45 E M_HS_E_STR PS_REL_NOR
+
+ +
+
Here success ratio expressed as 1 Here success ratio expressed as 1 failure ratio failure ratio
Top (N) drops
Cell and its Neighbour
Cells availability
Alarms/Tickets
Configuration &
Parameter audit
SHO
Success
Conf OK ?
Site OK ?
Iur
performance
Investigation Iur
Audit adjacent sites for
alarms, Availability,
configuration and capacity
Traffic
Neighbours Performance
(use SHO success per adjs
counters to identify badly
performing neighbours) & Map
3G Cell at RNC
border?
NO
YES
YES
YES
YES
SHO
SHO based on DSR,
CPICH EcNo difference,
SHO branch setup fail
BTS/Iub
Max HSPA users in
cell/RNC,RNC licensed
capacity:Max AMR/Iups
throughput
Call set up improvements (RU20)
Success
Rate <
90%?
ISHO
Failures
New site ?
Analyse last detailed
radio measurements
RF and IFHO neighbour
optimisation
No cell
found ratio
>40 %
ISHO
Success
Rate < 90%
RF and ISHO neighbour
optimisation
3G cell covers
over a
coverage hole ?
3G cell at inter-
RNC border ?
Wrong reference clock
(10MHz tuning)
No cell found
ratio > 90 %
and enough
ADJG
2G Cell Doctor
2G Investigation :
TCH blocking or
TCH seizure
failure
(interference)
NO
YES
NO
YES
NO
YES
YES
SHO
ISHO
Top
issu
es
Relocation success in
target RNC
HHO RSSI & BSIC time,
ISHO cancellation
HSDPA IFHO
failures, reject CM
for IFHO
HSUPA Call Establishment
RAB
Establishment
+
+
+
+
+
=
INT _EDCH_BTS_ SETUP_FAIL M1002C525 + BGR _EDCH_BTS_ SETUP_FAIL M1002C526 +
GR L_BTS_HW_B UL_DCH_SE M1002C518 + NT L_BTS_HW_I UL_DCH_SE M1002C517 +
A_USR_INT L_MAX_HSUP UL_DCH_SE M1002C515 + A_USR_BGR L_MAX_HSUP UL_DCH_SE M1002C516 +
_INT CANC_NA_AS EDCH_ALLO_ M1002C519 + _BGR CANC_NA_AS EDCH_ALLO_ M1002C520 +
R SS_EDCH_BG ALLO_SUCCE M1002C532 + T SS_EDCH_IN ALLO_SUCCE M1002C531
R SS_EDCH_BG ALLO_SUCCE M1002C532 + T SS_EDCH_IN ALLO_SUCCE M1002C531

Traffic NRT for ity Accessibil Resource HSUPA RNC_913a
Traffic + packet call measurement
HSUPA failures
E-DCH allocation cancelled due to not acceptable active set Too much E-DCH users in cell /
cell group, No BTS capacity available
+ + = TRE SCH_EDCH_S PS_ATT_HSD BGR DSCH_EDCH_ PS_ATT_HS_ NT SCH_EDCH_I PS_ATT_HSD Attempts HSUPA RNC_928B
+ +
+
T EDCH_UE_IN ETUP_FAIL_ SM1002C523 + GR _EDCH_UE_B SETUP_FAIL M1002C524 +
S_INT _EDCH_TRAN SETUP_FAIL M1002C527 S_BGR _EDCH_TRAN SETUP_FAIL M1002C528 +
R_INT _EDCH_OTHE SETUP_FAIL M1002C529 + R_BGR _EDCH_OTHE SETUP_FAIL M1002C530 +
HSUPA Call Establishment
RAB
Establishment
+ +
+ + +
+ + +
+ +
+ +
+ + +
+ +
+ + +
+ +
=
R_BGR _EDCH_OTHE SETUP_FAIL M1002C530 STR _EDCH_BTS_ SETUP_FAIL
INT _EDCH_BTS_ SETUP_FAIL M1002C525 BGR _EDCH_BTS_ SETUP_FAIL M1002C526
R _BTS_HW_ST UL_DCH_SEL GR L_BTS_HW_B UL_DCH_SE M1002C518
NT L_BTS_HW_I UL_DCH_SE M1002C517 _USR_STR _MAX_HSUPA UL_DCH_SEL
A_USR_INT L_MAX_HSUP UL_DCH_SE M1002C515 A_USR_BGR L_MAX_HSUP UL_DCH_SE M1002C516
_STR CANC_NA_AS EDCH_ALLO_ _INT CANC_NA_AS EDCH_ALLO_ M1002C519
_BGR CANC_NA_AS EDCH_ALLO_ M1002C520 R SS_EDCH_ST ALLO_SUCCE
R SS_EDCH_BG ALLO_SUCCE M1002C532 T SS_EDCH_IN ALLO_SUCCE M1002C531
Selections DCH - E RNC_923c
Traffic + packet call measurement
HSUPA failures
E-DCH allocation cancelled due to not acceptable active set Too much E-DCH users in cell /
cell group, No BTS capacity available
+ +
+ + +
+ + +
+ +
TR _EDCH_UE_S SETUP_FAIL NT _EDCH_UE_I SETUP_FAIL M1002C523
GR _EDCH_UE_B SETUP_FAIL M1002C524 S_STR _EDCH_TRAN SETUP_FAIL
S_INT _EDCH_TRAN SETUP_FAIL M1002C527 S_BGR _EDCH_TRAN SETUP_FAIL M1002C528
R_STR _EDCH_OTHE SETUP_FAIL R_INT _EDCH_OTHE SETUP_FAIL M1002C529
HS-DSCH Serving Cell Change
The HS-DSCH Serving Cell Change success rate can be calculated as below
It should be noted that the KPI above is not very accurate in cell level as denominator is
incremented in the source cell (old serving cell) and numerator is incremented in the
REASON OTHER STARTED SCC UPD SET ACTIVE STARTED SCC
ERROR SIR UL STARTED SCC ECNO CPICH STARTED SCC
SUCCESSFUL BTS INTER SCC SUCCESSFUL BTS INTRA SCC
100% A RNC
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
733 _
+
+ +
+
=
Intra-system hard handover measurement
Data in source
Node B buffer lost
incremented in the source cell (old serving cell) and numerator is incremented in the
target cell (new serving cell)
So this KPI is useful in RNC level
However in case the SCC failure rate is calculated then it is possible to find out under
which HS-DSCH serving cell plenty of SCCs are failing (but this will not tell the cell to
which the SCC is failing)
REASON OTHER STARTED SCC UPD SET ACTIVE STARTED SCC
ERROR SIR UL STARTED SCC ECNO CPICH STARTED SCC
HER _DUE_TO_OT SCC_FAILED _DUE_TO_AC SCC_FAILED
ANSM _DUE_TO_TR SCC_FAILED S _DUE_TO_BT SCC_FAILED _DUE_TO_UE SCC_FAILED
100% Rate Failure SCC
_ _ _ _ _ _ _
_ _ _ _ _ _ _
+
+ +
+
+ + +
=
HSDPA MAC-hs Efficiency
RNC_607c HSDPA MAC-hs efficiency (%)
HSDPA Retransmission ratio between BTS and HSDPA Capable UEs done by
MAC-hs
Actually, this is the successfully sent MAC-hs PDUs divided by all transmitted
MAC-hs PDUs including retransmissions
% 100
+ + +
+ + +
+ + +
+ +
+ + +
+ +
=
CODE_QPSK RETRANS_2_ M5000C60 CODE_QPSK RETRANS_1_ M5000C59 QAM _5_CODE_16 ORIG_TRANS M5000C58
QAM _4_CODE_16 ORIG_TRANS M5000C57 QAM _3_CODE_16 ORIG_TRANS M5000C56 QAM _2_CODE_16 ORIG_TRANS M5000C55
QAM _1_CODE_16 ORIG_TRANS M5000C54 SK _5_CODE_QP ORIG_TRANS M5000C53 SK _4_CODE_QP ORIG_TRANS M5000C52
SK _3_CODE_QP ORIG_TRANS M5000C51 SK _2_CODE_QP ORIG_TRANS M5000C50 SK _1_CODE_QP ORIG_TRANS M5000C49
T_CL_5 U_RETR_DIS MAC_HS_PD M5000C1 T_CL_4 U_RETR_DIS MAC_HS_PD M5000C4 T_CL_3 U_RETR_DIS MAC_HS_PD M5000C3
T_CL_2 U_RETR_DIS MAC_HS_PD M5000C2 T_CL_1 U_RETR_DIS MAC_HS_PD M5000C1 T_CL_0 U_RETR_DIS MAC_HS_PD M5000C0
RNC_607c
HSDPA in WBTS measurement
Number of original PDUs
Number of re-transmitted PDUs
For each modulation and number of
codes individual counter
+
+
+
+
+
+
+
+
+
+
+
+
+ + +
+ + +
+ + +
+ + +
M _CODE_16QA RETRANS_15 M5000C125 + M _CODE_16QA RETRANS_14 M5000C124 + M _CODE_16QA RETRANS_13 M5000C123 +

M _CODE_16QA RETRANS_12 M5000C122 + M _CODE_16QA RETRANS_11 M5000C121 + M _CODE_16QA RETRANS_10 M5000C120 +
CODE_16QAM RETRANS_9_ M5000C119 + CODE_16QAM RETRANS_8_ M5000C118 + CODE_16QAM RETRANS_7_ M5000C117 +
CODE_16QAM RETRANS_6_ M5000C116 + _CODE_QPSK RETRANS_15 M5000C115 + _CODE_QPSK RETRANS_14 M5000C114 +
_CODE_QPSK RETRANS_13 M5000C113 + _CODE_QPSK RETRANS_12 M5000C112 + _CODE_QPSK RETRANS_11 M5000C111 +
_CODE_QPSK RETRANS_10 M5000C110 + CODE_QPSK RETRANS_9_ M5000C109 + CODE_QPSK RETRANS_8_ M5000C108 +
CODE_QPSK RETRANS_7_ M5000C107 + CODE_QPSK RETRANS_6_ M5000C106 + 6QAM _15_CODE_1 ORIG_TRANS M5000C105 +
6QAM _14_CODE_1 ORIG_TRANS M5000C104 + 6QAM _13_CODE_1 ORIG_TRANS M5000C103 + 6QAM _12_CODE_1 ORIG_TRANS M5000C102 +
6QAM _11_CODE_1 ORIG_TRANS M5000C101 + 6QAM _10_CODE_1 ORIG_TRANS M5000C100 + QAM _9_CODE_16 ORIG_TRANS M5000C99 +
QAM _8_CODE_16 ORIG_TRANS M5000C98 + QAM _7_CODE_16 ORIG_TRANS M5000C97 + QAM _6_CODE_16 ORIG_TRANS M5000C96 +
PSK _15_CODE_Q ORIG_TRANS M5000C95 + PSK _14_CODE_Q ORIG_TRANS M5000C94 + PSK _13_CODE_Q ORIG_TRANS M5000C93 +
PSK _12_CODE_Q ORIG_TRANS M5000C92 + PSK _11_CODE_Q ORIG_TRANS M5000C91 + PSK _10_CODE_Q ORIG_TRANS M5000C90 +
SK _9_CODE_QP ORIG_TRANS M5000C89 + SK _8_CODE_QP ORIG_TRANS M5000C88 + SK _7_CODE_QP ORIG_TRANS M5000C87 +
SK _6_CODE_QP ORIG_TRANS M5000C86 + CODE_16QAM RETRANS_5_ M5000C68 CODE_16QAM RETRANS_4_ M5000C67
CODE_16QAM RETRANS_3_ M5000C66 CODE_16QAM RETRANS_2_ M5000C65 CODE_16QAM RETRANS_1_ M5000C64
CODE_QPSK RETRANS_5_ M5000C63 CODE_QPSK RETRANS_4_ M5000C62 CODE_QPSK RETRANS_3_ M5000C61
CODE_QPSK RETRANS_2_ M5000C60 CODE_QPSK RETRANS_1_ M5000C59 QAM _5_CODE_16 ORIG_TRANS M5000C58
The average active HS-DSCH MAC-d throughput from network perspective calculated
as the HSDPA MAC-d throughput at BTS, divided by the active HS-DSCH time from the
network perspective
The active time refers to the scheduled TTIs, i.e. when sending data
The throughput is looked at from MAC-d layer, i.e. how much MAC-d level data the HS-
DSCH is able to successfully transfer to UEs using the scheduled TTIs, so this
considers also the MAC-hs efficiency
Amount of data received in MAC-d PDUs by Node B
amount of data discarded due to buffer overflow
RNC_722b [kbps] =
( )
500
SS_5) R_DIST_CLA HS_SCCH_PW M5000C74 SS_4 R_DIST_CLA HS_SCCH_PW M5000C73 SS_ R_DIST_CLA HS_SCCH_PW M5000C72
SS_2 R_DIST_CLA HS_SCCH_PW M5000C71 SS_1 R_DIST_CLA HS_SCCH_PW M5000C70 SS_0 R_DIST_CLA HS_SCCH_PW M5000C69
1000
TS HS_MACD_BI DISCARDED_ M5000C127 - S S_MACD_BIT RECEIVED_H M5000C126
+ +
+ + +
3
amount of data discarded due to buffer overflow
Number of TTIs with HS-SCCH power
< 0.1 W
0.1-0.2 W
0.2-0.4 W
0.4-0.8 W
0.8-16. W
> 1.6 W
Total number of Total number of
MAC MAC--d PDUs d PDUs
received by Node B received by Node B
1 MAC 1 MAC--d PDU = 336 d PDU = 336
or 656 bit or 656 bit
If 656 bit PDU used, If 656 bit PDU used,
Amount of data Amount of data
received in MAC received in MAC--d d
PDUs by Node B PDUs by Node B
If 656 bit PDU used, KPI If 656 bit PDU used, KPI
606B not applicable 606B not applicable
KPI - statistic examples
KPI construction - Statistic examples
If 656 bit PDU used, If 656 bit PDU used,
KPI 608A not KPI 608A not
applicable applicable
Example: 1000 PDUs with 336 bit + 1000 PDUs with 656 bit Example: 1000 PDUs with 336 bit + 1000 PDUs with 656 bit
M5000C7 = 1000 + 1000 = 2000 PDUs M5000C7 = 1000 + 1000 = 2000 PDUs
M5000C126 = 1000 * 336 bit + 1000 * 656 bit = 992 Kbit M5000C126 = 1000 * 336 bit + 1000 * 656 bit = 992 Kbit
PDUs MACd d transmitte of number
sions retransmis n with correctly delivered PDUs MACd of number n
rate on transmissi
n
_ _ _ _
_ _ _ _ _ _ _ _ ) 1 (
_
+
=
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
KPI - statistic examples
KPI construction - Statistic examples
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
E-DCH Throughput can be measured by RNC_952a
60 ATION PERIOD_DUR 1000
8 TA_VOL SDPA_UL_DA NRT_EDCH_H M1023C10
[kbit/s] RNC at Throughput Average es - MAC HSUPA 952 _

=

a RNC
RU10 Reporting Suite new KPIs
Statistics measurements Statistics measurements
1000
8 10 1023
[kbit] RNC at Volume Data es - MAC HSUPA 931 _

=
ATA_VOL HSDPA_UL_D NRT_EDCH_ C M
a RNC
Amount of data transmitted in
MAC-es PDUs over E-DCH
HS-DSCH Throughput
8 TA_VOL HS_DSCH_DA M1023C8
[kbit/s] RNC at Throughput Average d - MAC HSDPA

=

[kbit] RNC at Volume Data d - MAC SDPA H
1000
8 TA_VOL HS_DSCH_DA M1023C8
[kbit] RNC at Volume Data d - MAC SDPA

=
H
MAC-d PDUs over HS-DSCH
R99 NRT Throughput DL
8 _DATA_VOL NRT_DCH_DL M1023C7
[kbit/s] RNC at Throughput Average d - MAC DL NRT R99

=

[kbit] RNC at Volume Data d - MAC DL RT 99 N R
1000
8 _DATA_VOL NRT_DCH_DL M1023C7
[kbit] RNC at Volume Data d - MAC DL RT 99

=
N R
MAC-d PDUs over DCH
R99 NRT Throughput UL
8 _DATA_VOL NRT_DCH_UL M1023C6
[kbit/s] RNC at Throughput Average d - MAC UL NRT R99

=

[kbit] RNC at Volume Data d - MAC UL RT 99 N R
Statistics measurements
1000
8 _DATA_VOL NRT_DCH_UL M1023C6
[kbit] RNC at Volume Data d - MAC UL RT 99

=
N R
MAC-d PDUs over DCH
Inter System Hard Handover Success Ratio [%]
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ ( * 100
NRT TOT PTX LB HHO IS SUCC RT TOT PTX LB HHO IS SUCC
NRT TOT PRX LB HHO IS SUCC RT TOT PRX LB HHO IS SUCC
NRT UL CAPA LB HHO IS SUCC NRT DL CAPA LB HHO IS SUCC
CALL EMERG HHO IS SUCC
NRT IMS IM HHO IS SUCC RT IMS IM HHO IS SUCC
NRT ECNO CPICH HHO IS SUCC NRT RSCP CPICH HHO IS SUCC
NRT PWR DPCH DL HHO IS SUCC NRT PWR TRX UE HHO IS SUCC
NRT Q DCH UL HHO IS SUCC RT ECNO CPICH HHO IS SUCC
RT RSCP CPICH HHO IS SUCC RT PWR DPCH DL HHO IS SUCC
RT PWR TRX UE HHO IS SUCC RT Q DCH UL HHO IS SUCC sum
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+
+ + +
+ +
+
Load and Service
(RAS51)
This KPI cover both
NRT and RT ISHO
success
Further HHO trigger
Load based capacity rejection
) _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ (
) _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _
_
NRT SB ATT HHO IS RT SB ATT HHO IS
NRT SC RSVR LB ATT HHO IS RT SC RSVR LB ATT HHO IS
NRT LIM RES LB ATT HHO IS RT LIM RES LB ATT HHO IS
NRT TOT PTX LB ATT HHO IS RT TOT PTX LB ATT HHO IS
NRT TOT PRX LB ATT HHO IS RT TOT PRX LB ATT HHO IS
NRT UL CAPA LB ATT HHO IS NRT DL CAPA LB ATT HHO IS
CALL EMERG ATT HHO IS
NRT IMS IM ATT HHO IS RT IMS IM ATT HHO IS
NRT ECNO CPICH ATT HHO IS NRT RSCP CPICH ATT HHO IS
NRT PWR DPCH DL ATT HHO IS NRT PWR TRX UE ATT HHO IS
NRT Q DCH UL ATT HHO IS RT ECNO CPICH ATT HHO IS
RT RSCP CPICH ATT HHO IS RT PWR DPCH DL ATT HHO IS
RT PWR TRX UE ATT HHO IS RT Q DCH UL ATT HHO IS sum
NRT SB HHO IS SUCC RT SB HHO IS SUCC
NRT SC RSVR LB HHO IS SUCC RT SC RSVR LB HHO IS SUCC
NRT LIM RES LB HHO IS SUCC RT LIM RES LB HHO IS SUCC
Success ISHO
+ +
+ +
+ +
+ +
+ +
+ +
+
+ +
+ +
+ +
+ +
+ +
+
+ +
+ +
+ +
=
(RAS51)
Based ISHO Success for
both NRT and RT
Load and Service
(RAS51)
Based ISHO Attempt for
both NRT and RT
RU10 Reporting Suite
RNC level system
program added
Corrections to
Capacity report
Modifications to
Service level report
(Streaming class
added+ some other
Report Topic Name Report Name Report ID
1. System Program System Program RNC Level RSRAN084
1. System Program System Program Cell Level RSRAN000
2. Capacity RNC Capacity RSRAN068
2. Capacity Node B Capacity RSRAN066
2. Capacity Cell Capacity RSRAN067
2. Capacity NRT Radio Bearer Statistics RSRAN013
3. Service Level Service/Session Accessibility Analysis RSRAN073
3. Service Level Service/Session Retainability Analysis RSRAN079
3. Service Level RAB Holding Times RSRAN021
3. Service Level Service Summary RSRAN003
4. Traffic Allocated Traffic Amounts (R99 + HSPA) RSRAN070
4. Traffic Cell Data Volume and Throughput at RNC RSRAN077
4. Traffic Traffic Summary RSRAN026
4. Traffic Used CE Capacity per RB Type in RNC RSRAN022
Classes; KPI
added+ some other
corrections)
4. Traffic Used CE Capacity per RB Type in RNC RSRAN022
4. Traffic Utilization Shares of Total Traffic Allocation Amounts RSRAN071
5. Mobility and Handover Active Set Size for NRT-RT Traffic RSRAN078
5. Mobility and Handover HSPA Serving Cell Change RSRAN033
5. Mobility and Handover IFHO Adjacencies RSRAN044
5. Mobility and Handover Inter-System Handover per Cause RSRAN019
5. Mobility and Handover Inter-System Handover Performance RSRAN023
5. Mobility and Handover Inter-System Handover Reasons RSRAN018
5. Mobility and Handover ISHO Adjacencies RSRAN045
5. Mobility and Handover Load Based HO Related Resources RSRAN047
5. Mobility and Handover Load Based IFHO/ISHO Performance RSRAN048
5. Mobility and Handover Load Based IFHO/ISHO Triggering RSRAN049
5. Mobility and Handover Service Based IFHO/ISHO Performance RSRAN050
5. Mobility and Handover SHO Adjacencies RSRAN046
5. Mobility and Handover Soft Handover Performance RSRAN028
RNC_169e:DR +
GAN HO added,
but load & service
based counters
removed
Module Version control
Version Date Status Contact
RU10_v1.0
RU10_v2.0
06.07.2009
28.08.2009
RU10 level
Ronald Fabian
Dr. Benedikt Aschermann/
Dr. Dirk Rose
Comments
Good exercise is to see look in documentation how the KPIs are
affected with the new features in RU20
Also for each KPI please check the Live Network Target (could be
found in the dictionary)

01 KPI Definition PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 KPI Definition PDF

Uploaded by

Copyright:

Available Formats

Module 1 KPI overview

_DCH_BGR PS_ATT_DCH M1022C8 + _DCH_INT PS_ATT_DCH M1022C7

_DCH_BGR PS_ATT_DCH M1022C8 + _DCH_INT PS_ATT_DCH M1022C7 +

M _CODE_16QA RETRANS_15 M5000C125 + M _CODE_16QA RETRANS_14 M5000C124 + M _CODE_16QA RETRANS_13 M5000C123 +

You might also like