O2RD - 09 - XX Definition of RNC KPI Transport & Hardware RU10 Draft A

In Confidence
O2
'Do Once' Radio Design
Definition of RNC KPI - Transport and Hardware
Document Reference : O2RD/09/-Page : 1 of 114
Definition of RNC Key Performance

Indicators: Transport and Hardware
(RU10)
Summary:
This document includes a specification of RNC KPI based upon the RNC Transport and Hardware counter
tables. This report is applicable to NSN software release RU10. Each KPI within this document is specified
in terms of software release, importance, network element scope (per cell, per Node B, per VCC, per VPC),
time resolution, target value, equation and units. Descriptive sections are included to provide justification
for each KPI. Suggestions are made for how the performance of each KPI may be improved. This report has
been generated with the intention of making it applicable to all O2 business operations using the NSN RAN.
The complete set of RNC Transport and Hardware KPI can be categorised as Engineering KPI. This is in
contrast to Business KPI. Engineering KPI are applicable to the operations, radio design and radio network
planning groups.
Authors:
Authors Operating Business:
Date:
Version:
Reference:
Approved by:
Date:
Version : Draft A
In Confidence
Chris Johnson (NSN)

Radio Design, O2 UK
31st March 2009
Draft A
O2RD/09/-Alemu Abate
Date: 31/03/09
In Confidence
O2
DISTRIBUTION LIST
Alemu Abate
Martin Kraus
David Benson
Jacqueline Gray
Rachel Clarkson
Mohamed AbdelAziz
Pinaki Roychowdhury
Patryk Debicki
Michele Garelli
Dave Morris
Ilaria Massa (NSN)
Kenni Rasmussen (NSN)
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
CHANGE HISTORY
Tool used
File location
Create, save & print dates
Version
Draft A
Date
25/03/08
Microsoft Word 97
16/10/2006 09:11:000 01/04/2009 03:25:00 04/11/2005 06:38:00
0
PM
PM
Changed by
Changes
Chris Johnson
First draft generated from issue 1 of the RAS06 RNC
Transport and Hardware KPI document, O2RD/08/50
The following new KPI have been added:
Average RNC Speech Call Count
Maximum RNC Speech Call Count
RNC Speech Call Count > 70% of Licensed Capacity
RNC Speech Call Licensed Capacity
Average RNC PS Throughput
Maximum RNC PS Throughput
RNC PS Throughput > 70% of Licensed Capacity
RNC PS Throughput Licensed Capacity
RNC PS Throughput Limited by Licensed Capacity
Average RRC Connected Mode UE
Maximum RRC Connected Mode UE
Average UE in CELL_DCH
Average UE in CELL_FACH
Average UE in CELL_PCH
Average UE in URA_PCH
Peak DSP Service Allocations
DSP Service Allocation Success Rate
DSP Service Modification Failures
DMPG Automatic Resets
Manual Resets
Service Pool Allocation Success Rate
Average Service Pool Utilisation
Peak Service Pool Utilisation
Service Pool Modification Failures
Service Pool Overflows
Average Application Processes
Average CPU Load
Average Internal Memory Utilisation
Average External Memory Utilisation
Maximum Application Processes
Maximum CPU Load
Maximum Internal Memory Utilisation
Maximum External Memory Utilisation
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
The following KPI have been removed:

RNC Common Channel Load
RNC Signalling Channel Load
RNC CS Speech Load
RNC CS RT Data Load
RNC PS RT Data Load
RNC PS NRT Data Load
RNC HSDPA Common Load
RNC HSDPA NRT Data Load
RNC Common Channel Peak Calls
RNC Signalling Channel Peak Calls
RNC CS Speech Peak Calls
RNC CS RT Data Peak Calls
RNC PS RT Data Peak Calls
RNC PS NRT Data Peak Calls
RNC HSDPA Common Peak Calls
RNC HSDPA NRT Data Peak Calls
RNC Common Channel Failure Rate
RNC Signalling Channel Failure Rate
RNC CS Speech Failure Rate
RNC CS RT Data Failure Rate
RNC PS RT Data Failure Rate
RNC PS NRT Data Failure Rate
RNC HSDPA Common Failure Rate
RNC HSDPA NRT Data Failure Rate
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
TABLE OF CONTENTS
1. Scope................................................................................................................................................8
2. Introduction....................................................................................................................................9
3. RNC Resource Measurements.....................................................................................................10
3.1. RNC Capacity Usage Measurement (802/322H)..................................................................................10
3.1.1. Average RNC Speech Call Count..................................................................................................11
3.1.2. Maximum RNC Speech Call Count...............................................................................................12
3.1.3. RNC Speech Call Count > 70% of Licensed Capacity..................................................................13
3.1.4. RNC Speech Call Licensed Capacity.............................................................................................14
3.1.5. Average RNC PS Throughput.......................................................................................................15
3.1.6. Maximum RNC PS Throughput....................................................................................................16
3.1.7. RNC PS Throughput > 70% of Licensed Capacity........................................................................17
3.1.8. RNC PS Throughput Licensed Capacity........................................................................................18
3.1.9. RNC PS Throughput Limited by Licensed Capacity.....................................................................19
3.1.10. Average RRC Connected Mode UE............................................................................................20
3.1.11. Maximum RRC Connected Mode UE.........................................................................................21
3.1.12. Average UE in CELL_DCH........................................................................................................22
3.1.13. Average UE in CELL_FACH......................................................................................................23
3.1.14. Average UE in CELL_PCH.........................................................................................................24
3.1.15. Average UE in URA_PCH..........................................................................................................25
4. Transport Network Resource Measurements............................................................................26

4.1. AAL2 Path CAC Resource Measurement (550/226H).........................................................................26
4.1.1. DCH Reserved Transport Load.....................................................................................................27
4.1.2. HSDPA Reserved Transport Load.................................................................................................28
4.1.3. Total Reserved Transport Load.....................................................................................................29
4.1.4. Maximum Reserved Transport Load.............................................................................................30
4.1.5. DCH Reserved Transport Bandwidth............................................................................................31
4.1.6. HSDPA Reserved Transport Bandwidth........................................................................................32
4.1.7. Total Reserved Transport Bandwidth............................................................................................33
4.1.8. Maximum Reserved Transport Bandwidth....................................................................................34
4.1.9. Available HSDPA Transport Bandwidth.......................................................................................35
4.1.10. Average AAL2 Transport Connection Load................................................................................36
4.1.11. Maximum AAL2 Transport Connection Load.............................................................................37
4.1.12. Average HSDPA Transport Connection Count............................................................................38
4.1.13. Maximum HSDPA Connection Count.........................................................................................39
4.2. AAL2 Resource Reservation Measurement (800/320H)......................................................................40
4.2.1. AAL2 Reservation Success Rate...................................................................................................41
4.2.2. Transport HSDPA Reservation Success Rate................................................................................42
4.2.3. Transport HSDPA Reservation Utilisation Ratio...........................................................................43
5. Signalling Measurements.............................................................................................................44
5.1. AAL2 Signalling Protocol at UNI Measurement (548/224H)..............................................................44
5.2. AAL2 Signalling at NNI Measurement (552/228H).............................................................................45
5.3. SAAL Signalling Protocol at UNI Measurement (546/222H)..............................................................46
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
5.3.1. Unsolicited SSCOP Errors.............................................................................................................47
6. ATM/IP Transport Measurements.............................................................................................48

6.1. ATM Virtual Channel Connection Measurement (530/212H)..............................................................48
6.1.1. Total User Plane Egress Transport Load........................................................................................49
6.1.2. Total User Plane Ingress Transport Load.......................................................................................50
6.1.3. Egress Cell Drop Ratio..................................................................................................................51
6.1.4. Ingress Cell Drop Ratio.................................................................................................................52
6.2. ATM Layer Performance Measurement (528/210H)............................................................................53
6.2.1. Computer Unit ATM Cell Egress Drop Ratio................................................................................54
6.2.2. Computer Unit ATM Cell Ingress Drop Ratio...............................................................................55
6.3. ATM Route Load Measurement (531/213H).......................................................................................56
6.4. ATM Interface Measurement (532/214H)............................................................................................57
6.4.1. ATM Interface Egress Load...........................................................................................................58
6.4.2. ATM Interface Ingress Load..........................................................................................................59
6.4.3. ATM Interface Egress Cell Drop Ratio.........................................................................................60
6.4.4. ATM Interface Ingress Cell Drop Ratio.........................................................................................61
6.5. ATM Virtual Path Connection Measurement (529/211H)....................................................................62
6.6. AAL5 Protocol Measurement in Chorus (549/225H)...........................................................................62
6.7. AAL5 Protocol Measurement in DMX (547/223H).............................................................................62
6.8. TCP/IP Protocol Measurement (563/233H).........................................................................................62
6.9. AAL2 Scheduling Performance in RNC (553/229H)...........................................................................63
6.9.1. HSDPA Peak AAL2 CPS Rate......................................................................................................64
6.9.2. HSDPA Average AAL2 CPS Rate................................................................................................65
6.9.3. HSDPA Peak AAL2 CPS Delay....................................................................................................66
6.9.4. HSDPA Average AAL2 CPS Delay..............................................................................................67
6.9.5. HSDPA Flow Control Slow Down................................................................................................68
6.9.6. HSDPA Flow Control Speed Up...................................................................................................69
6.9.7. HSDPA Flow Control Stop............................................................................................................70
6.9.8. HSDPA Dropped AAL2 CPS........................................................................................................71
6.10. Iu-PS Throughput Measurement (801/321H).....................................................................................72
6.10.1. Average Uplink Total Iu-PS Throughput.....................................................................................73
6.10.2. Average Uplink RT Iu-PS Throughput........................................................................................74
6.10.3. Average Uplink NRT Iu-PS Throughput.....................................................................................75
6.10.4. Average Downlink Total Iu-PS Throughput................................................................................76
6.10.5. Average Downlink RT Iu-PS Throughput...................................................................................77
6.10.6. Average Downlink NRT Iu-PS Throughput................................................................................78
6.10.7. Iu-PS Error Indications................................................................................................................79
6.10.8. Average Number of GTP Tunnels...............................................................................................80
6.10.9. Maximum Number of GTP Tunnels............................................................................................81
7. Computing Unit Measurements..................................................................................................82

7.1. Availability Performance Measurement (608/260H)............................................................................82
7.2. Unit Load Measurement (592/250H)...................................................................................................82
7.2.1. RNC Computer Unit Average Load...............................................................................................83
7.2.2. RNC Computer Unit Maximum Load............................................................................................84
7.3. WAC Overload Control Measurement (594/252H)..............................................................................85
7.3.1. RNC ICSU WAC Gate Success Rate.............................................................................................86
8. Physical Layer Measurements.....................................................................................................87
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
8.1. IMA Logical Interface Measurement (514/202H)................................................................................87

8.2. STM-1 Interface Measurement (513/201H).........................................................................................89
8.3. SONET/SDH Protection Group Measurement (516/204H)..................................................................90
9. DSP Resource Measurements......................................................................................................91

9.1. DSP Service Statistics Measurement (609/261H)................................................................................91
9.1.1. Peak DSP Service Allocations.......................................................................................................92
9.1.2. DSP Service Allocation Success Rate............................................................................................93
9.1.3. DSP Service Modification Failures................................................................................................94
9.2. DSP State Changes Measurement (612/264H).....................................................................................95
9.2.1. DMPG Automatic Resets...............................................................................................................96
9.2.2. Manual Resets...............................................................................................................................97
9.3. DSP Resource Utilization Measurement (615/267H)...........................................................................98
9.3.1. Service Pool Allocation Success Rate............................................................................................99
9.3.2. Average Service Pool Utilisation.................................................................................................100
9.3.3. Peak Service Pool Utilisation.......................................................................................................101
9.3.4. Service Pool Modification Failures..............................................................................................102
9.3.5. Service Pool Overflows...............................................................................................................103
9.4. DSP Load Measurement (617/269H).................................................................................................104
9.4.1. Average Application Processes....................................................................................................105
9.4.2. Average CPU Load......................................................................................................................106
9.4.3. Average Internal Memory Utilisation..........................................................................................107
9.4.4. Average External Memory Utilisation.........................................................................................108
9.4.5. Maximum Application Processes.................................................................................................109
9.4.6. Maximum CPU Load...................................................................................................................110
9.4.7. Maximum Internal Memory Utilisation.......................................................................................111
9.4.8. Maximum External Memory Utilisation......................................................................................112
10. Conclusion.................................................................................................................................113
11. References.................................................................................................................................114
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
1.
Scope
The scope of this report includes the specification of KPI based upon the RNC Transport and Hardware
counter tables. This report is applicable to NSN software release RU10. Each KPI is specified in terms of
software release, importance, network element scope (per cell, per Node B, per VCC, per VPC), time
resolution, target value, equation and units. Descriptive sections are included to provide justification for each
KPI. Suggestions are made for how the performance of each KPI may be improved.
The report has been generated with the intention of making it applicable to all O2 business operations using
the NSN RAN.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
2.
Introduction
Key Performance Indicators (KPI) are crucial performance metrics which provide a high level indication of
system performance. KPI are typically generated in parallel to a set of Performance Indicators (PI). KPI may
be used for performance benchmarking and for identifying relatively high level issues. Performance
improvement campaigns based upon KPI typically focus upon a specific area of system performance. KPI
may be used to identify the worst performing sites and thus those that are most likely to benefit from
subsequent optimisation or a capacity upgrade. Radio network planning and optimisation processes typically
make use of KPI analysis in either a periodic or event triggered manner. Performance benchmarking tends to
be a periodic process focused upon the continuous improvement of KPI statistics. The capacity upgrade
process is an example of a process that is more likely to use KPI statistics in an event triggered fashion i.e.
the capacity upgrade process is triggered when a specific KPI exceeds a specific threshold.
KPI are typically used by the business, operations, radio design and radio network planning groups within
O2s organisation. Each group has its own priorities and own set of requirements. KPI can be categorised as
either Business KPI or Engineering KPI. Engineering KPI are assumed to be applicable to the operations,
radio design and radio network planning groups. The complete set of RNC Transport and Hardware KPI
have been categorised as Engineering KPI rather than Business KPI.
The specification of any KPI must define the scope over which the KPI is applicable. It may be appropriate
to calculate some KPI on a per cell basis and other KPI on a per RNC basis. Engineering KPI are typically
required on a per cell basis to provide a means to locate specific performance issues. Business KPI are
typically required only on a per RNC or per PLMN basis. The specification of any KPI must also define an
associated measurement period. Both the scope of the KPI and the measurement period have a significant
impact upon the quantity of data created by the generation of KPI statistics. It is generally useful to
maximise the quantity of information available. However, generating large quantities of statistics may result
in the information becoming unmanageable and impractical to archive.
The equation for each KPI specifies the recommended approach for summarising when KPI are calculated
across multiple objects, e.g. a KPI is calculated for all user plane VCC connected to a single RNC. In
general, this involves summing the counters across the set of objects. It can also involve averaging across
objects or taking the maximum across objects.
The high importance KPI have target values associated with them. At this point, these target values are
intended to define a sensible starting point. They are not based upon field experience and should be refined
as the quantity of experience in the field increases.
This document should be used in combination with [1] which specifies the set of RNC Radio Network KPI
and [2] which specifies the set of Node B KPI. In addition, [3] provides a specification of the raw counters.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

3.
RNC Resource Measurements

3.1.
RNC Capacity Usage Measurement (802/322H)
The RNC capacity usage measurement provides information on the number of simultaneous AMR calls, IuPS throughput and the number of UE in different RRC connected mode states. The object of the
measurement is the RNC. Some of the counters are only supported in specific RNC hardware configurations.
The set of counters and the associated dependency upon the RNC hardware configuration are shown below.
Counter
Number
Counter Name
M802C0
M802C1
M802C2
M802C3
M802C4
M802C5
M802C6
M802C7
M802C8
M802C9
M802C10
M802C11
M802C12
M802C13
M802C14
M802C15
M802C16
M802C17
M802C18
M802C19
M802C20
M802C21
M802C2
AMR_AVERAGE
AMR_MAX
AMR_DISTR_CLASS_0
AMR_DISTR_CLASS_1
AMR_DISTR_CLASS_2
AMR_DISTR_CLASS_3
AMR_DISTR_CLASS_4
AMR_LIC_CAPACITY
IU_PS_THR_AVERAGE
IU_PS_THR_PEAK
IUB_PS_THR_DISTR_CLASS_0
IUB_PS_THR_LIC_CAPACITY
IU_PS_THR_LIMIT_DURATION
AVE_RRC_CONN_MODE_USER
MAX_RRC_CONN_MODE_USERS
AVE_USERS_CELL_DCH
AVE_USERS_CELL_FACH
AVE_USERS_CELL_PCH
AVE_USERS_URA_PCH
Version : Draft A
In Confidence
RNC 196 & 450

without IP Upgrade
RNC 196 & 450

with IP Upgrade
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
RNC2600
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Date: 31/03/09
In Confidence
O2
3.1.1.
KPI Name:
KPI Short Name:
NSN KPI Number:
RNC Software Release:
IMPORTANCE:

AV_RNC_SP_CALL
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C0)
AVERAGE(AMR_AVERAGE)
Units: calls
Separate aggregation across objects necessary: No
Notes: None
KPI Description
This KPI quantifies the average number of speech calls within the RNC.
Means to improve
This KPI can be used to trigger a capacity upgrade. The capacity upgrade could be either a hardware upgrade
or a license upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.2.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_RNC_SP_CALL
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C1)
AVERAGE(AMR_MAX)
Units: calls
Notes: None
KPI Description
This KPI quantifies the maximum number of speech calls within the RNC.
Means to improve
This KPI can be used to trigger a capacity upgrade. The capacity upgrade could be either a hardware upgrade
or a license upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.3.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

RNC_SP_CALL_>70%
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
100 % SUM(M802C4 + M802C5 + M802C6) / SUM(M802C2 + M802C3 + M802C4 + M802C5 +
M802C6)
100 % SUM(AMR_DISTR_CLASS_2 + AMR_DISTR_CLASS_3 + AMR_DISTR_CLASS_4) /
SUM(AMR_DISTR_CLASS_0 + AMR_DISTR_CLASS_1 + AMR_DISTR_CLASS_2 +
AMR_DISTR_CLASS_3 + AMR_DISTR_CLASS_4)
Units: %
Notes: This KPI is only applicable to the RNC2600.
KPI Description
This KPI quantifies the percentage of time that the RNC speech call count exceeds 70 % of the licensed
capacity.
Means to improve
This KPI can be used to trigger a capacity upgrade. The capacity upgrade would be a license upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.4.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

RNC_SP_CALL_LIC
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C7)
AVERAGE(AMR_LIC_CAPACITY)
Units: calls
Notes: This KPI is only applicable to the RNC2600.
KPI Description
This KPI quantifies the RNC licensed capacity.
Means to improve
This KPI is provided for information purposes, i.e. to provide a mechanism for monitoring the speech call
capacity licensed at each RNC.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.5.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_RNC_PS_THRU
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C8) / 1000
AVERAGE(IU_PS_THR_AVERAGE) / 1000
Units: Mbps
Notes: This KPI is only applicable to the RNC2600 or the RNC196/RNC450 with the IP upgrade.
KPI Description
This KPI quantifies the average Iu-ps throughput in the downlink direction from the core network to the RNC.
Means to improve
This KPI can be used for traffic monitoring purposes as well as within the capacity upgrade process.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.6.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_RNC_PS_THRU
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C9) / 1000
MAX(IU_PS_THR_PEAK) / 1000
Units: Mbps
KPI Description
This KPI quantifies the maximum Iu-ps throughput in the downlink direction from the core network to the
RNC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.7.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

RNC_PS_THRU_>70%
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
100 % SUM(M802C12 + M802C13 + M802C14) / SUM(M802C10 + M802C11 + M802C12 + M802C13 +
M802C14)
100 % SUM(IUB_PS_THR_DISTR_CLASS_2 + IUB_PS_THR_DISTR_CLASS_3 +
IUB_PS_THR_DISTR_CLASS_4) / SUM(IUB_PS_THR_DISTR_CLASS_0 +
IUB_PS_THR_DISTR_CLASS_1 + IUB_PS_THR_DISTR_CLASS_2 + IUB_PS_THR_DISTR_CLASS_3
+ IUB_PS_THR_DISTR_CLASS_4)
Units: %
KPI Description
This KPI quantifies the percentage of time that the Iu-ps throughput in the downlink direction is greater than
70 % of the licensed capacity.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.8.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

RNC_PS_THRU_LIC
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C15) / 1000
AVERAGE(IUB_PS_THR_LIC_CAPACITY) / 1000
Units: Mbps
KPI Description
This KPI quantifies the RNC licensed capacity.
Means to improve
This KPI is provided for information purposes, i.e. to provide a mechanism for monitoring the packet
switched data throughput capacity licensed at each RNC.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.9.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

RNC_PS_THRU_LIM_LIC
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
100 % SUM(M802C16) / (PERIOD_DURATION 60)
100 % SUM(IU_PS_THR_LIMIT_DURATION) / (PERIOD_DURATION 60)
Units: %
Notes: The PERIOD_DURATION is defined by the measurement period in units of minutes. This KPI is only
applicable to the RNC2600 or the RNC196/RNC450 with the IP upgrade.
KPI Description
This KPI quantifies the percentage of time that the Iu-ps throughput is limited by the licensed capacity.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.10.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_RRC_CON_UE
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M802C17)
AVERAGE(AVE_RRC_CONN_MODE_USERS)
Units: users
Notes: None.
KPI Description
This KPI quantifies the average number of RRC connected mode users in the RNC.
Means to improve
This KPI can be used for traffic monitoring purposes and within the capacity upgrade process. It can also be
used for traffic balancing between RNC.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.11.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_RRC_CON_UE
None
RU10
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C18)
MAX(MAX_RRC_CONN_MODE_USERS)
Units: users
Notes: None.
KPI Description
This KPI quantifies the maximum number of RRC connected mode users in the RNC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.12.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
AV_UE_CELL_DCH
None
RU10
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C19)
MAX(AVE_USERS_CELL_DCH)
Units: users
Notes: None.
KPI Description
This KPI quantifies the average number of CELL_DCH users in the RNC.
Means to improve
This KPI can be used for traffic monitoring purposes and for traffic balancing between RNC.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.13.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
AV_UE_CELL_FACH
None
RU10
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C20)
MAX(AVE_USERS_CELL_FACH)
Units: users
Notes: None.
KPI Description
This KPI quantifies the average number of CELL_FACH users in the RNC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.14.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
AV_UE_CELL_PCH
None
RU10
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C21)
MAX(AVE_USERS_CELL_PCH)
Units: users
Notes: None.
KPI Description
This KPI quantifies the average number of CELL_PCH users in the RNC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
3.1.15.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
AV_UE_URA_PCH
None
RU10
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M802C22)
MAX(AVE_USERS_URA_PCH)
Units: users
Notes: None.
KPI Description
This KPI quantifies the average number of CELL_PCH users in the RNC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.
Transport Network Resource Measurements

4.1.
AAL2 Path CAC Resource Measurement (550/226H)
Counters within the AAL2 Path CAC Resource Measurement table focus upon the resource utilisation for the
user plane VCC AAL2 ATM connections. These counters are applicable to the Iub, Iur and Iu-cs interfaces.
The AAL2 connection resources are allocated and released by the Connection Admission Control (CAC)
based upon requests from the radio layer. The RNC CAC controls resources in the egress direction. Some of
the counters are dedicated to HSDPA, e.g. monitoring the HSDPA resource utilisation.
The object of the measurement is the AAL2 path associated with the user plane VCC. The ATM paths are
selected using their ATM interface/VP/VC identifiers. A maximum of 1600 user plane VCC can be
monitored simultaneously.
The set of counters belonging to the AAL2 Path CAC Resource Measurement counter table are presented
below.
Counter
Number
M550C0
M550C1
M550C2
M550C3
M550C4
M550C5
M550C6
M550C7
M550C8
M550C9
Counter Name
AAL2_PATH_GUAR_CELL_RATE
SUM_RESERVED_CELL_RATE
MIN_RESERVED_CELL_RATE
MAX_RESERVED_CELL_RATE
SUM_AAL2_CONNECTIONS
MIN_AAL2_CONNECTIONS
MAX_AAL2_CONNECTIONS
NBR_SAMPLES
AAL2_RM_SUCCEEDED
AAL2_CAC_REJECTED
Version : Draft A
In Confidence
Counter
Number
M550C10
M550C11
M550C12
M550C13
M550C14
M550C15
M550C16
M550C17
M550C18
M550C19
Counter Name
AAL2_HW_REJECTED
SUM_AAL2_CONNECTIONS_HSDPA
MIN_AAL2_CONNECTION_HSDPA
MAX_AAL2_CONNECTIONS_HSDPA
AAL2_CAC_REJECTED_HSDPA
AAL2_HW_REJECTED_HSDPA
SHARED_HSDPA_AAL2_ALLOCATION
AAL2_RM_SUCCEEDED_HSDPA
MIN_SHARED_HSDPA_AAL2_ALLOC
MAX_SHARED_HSDPA_AAL2_ALLOC
Date: 31/03/09
In Confidence
O2
4.1.1.
DCH Reserved Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

DCH_RESERV_TRANS_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
< 70 %
KPI Expression
100 % SUM(M550C1 M550C16) / SUM(M550C7 (M550C0 M550C19))
100 % SUM(SUM_RESERVED_CELL_RATE - SHARED_HSDPA_AAL2_ALLOCATION) /
SUM(NBR_SAMPLES (AAL2_PATH_GUAR_CELL_RATE
MAX_SHARED_HSDPA_AAL2_ALLOC))
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of the Iub user plane VCC intended for DCH connections which has been
reserved for DCH connections. The M550C1 counter divided by the M550C7 counter represents the total
DCH and HSDPA reservation. The M550C16 counter divided by the M550C7 counter represents only the
HSDPA reservation. The difference between the two provides a measure of the DCH reservation. The result is
divided by the user plane VCC bandwidth intended for DCH connections, i.e. the total user plane VCC
bandwidth minus the size of the HSDPA reservation.
This KPI does not provide an indication of the overall load of the Iub user plane VCC. Instead it provides an
indication of whether or not DCH traffic is loading the Iub to such an extent that it is likely to impact HSDPA
performance.
This KPI can have a result which is greater than 100 %. This can occur if an Iub is heavily loaded with DCH
connections while there are few HSDPA connections. In that case, the DCH connections can use some of the
bandwidth which would be reserved for HSDPA if there were active HSDPA connections. A result of more
than 100 % means that it is unlikely that an HSDPA reservation would be successful. The result should be less
than 70 % to allow HSDPA to make full use of the Iub bandwidth defined by the RNC databuild parameter
SharedHSDPAFlowControlAllocation. This parameter has a recommended value which is 30 % greater than
the reserved HSDPA bandwidth.
Means to improve
Decreasing the Iub DCH reserved load requires either a physical capacity upgrade for the Iub or a reduction in
the HSDPA reservation.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.2.
HSDPA Reserved Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_RESERV_TRANS_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
100 % SUM(M550C16) / SUM(M550C7 M550C19)
100 % SUM(SHARED_HSDPA_AAL2_ALLOCATION) / SUM(NBR_SAMPLES
MAX_SHARED_HSDPA_AAL2_ALLOC)
Units: %
Notes: none
KPI Description
This KPI quantifies the percentage of the maximum HSDPA reservation reserved for HSDPA when averaged
throughout the measurement period. The M550C16 counter divided by the M550C7 counter represents the
actual HSDPA reservation whereas the M550C19 counter represents the maximum HSDPA reservation.
This KPI result should not exceed 100 % although HSDPA connections can use an Iub bandwidth which is
greater than the HSDPA reservation. This KPI focuses upon the size of the reservation rather than actual used
bandwidth. A KPI result of 100 % means that the HSDPA reservation was continuously present throughout
the measurement period.
Means to improve
This KPI provides a way to monitor the percentage of time that an HSDPA reservation is made. If an HSDPA
reservation is not made then either there are no HSDPA connections or the reservation has failed as a result of
high DCH load. If the HSDPA reserved load is low then a check should be made to ensure that the reservation
is not failing as a result of high DCH load. If the HSDPA load is high then an increase in the reservation
bandwidth should be considered which would potentially allow higher HSDPA throughput.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.3.
Total Reserved Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

TOTAL_RESERV_TRANS_LOAD
RNC_601a
RAS05
High
Scope
Time Resolution
Target
User Plane VCC

1 hour
< 70 %
KPI Expression
100 % SUM(M550C1) / SUM(M550C7 M550C0)
100 % SUM(SUM_RESERVED_CELL_RATE) / SUM(NBR_SAMPLES
AAL2_PATH_GUAR_CELL_RATE )
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of the Iub user plane VCC which has been reserved for DCH and HSDPA
connections. This KPI provides an indication of the overall load of the Iub user plane VCC. The actual Iub
throughput can be greater than or less than that indicated by the reserved load, i.e. The DCH throughput
should be less than the DCH reserved bandwidth but the HSPDA throughput may be either greater than or less
than the reserved bandwidth.
The M550C1 counter divided by the M550C7 counter represents the total DCH and HSDPA reservation. The
M550C0 counter represents the size of the Iub user plane VCC.
Means to improve
A high load indicates that a physical capacity upgrade is likely to be necessary. Upgrading the physical
capacity of the Iub would allow an increased user plane VCC capacity and would result in a decreased load.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.4.
Maximum Reserved Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
Maximum Reserved Transport Load

MAX_RESERV_TRANS_LOAD
None
RAS05
High
Scope
Time Resolution
Target
User Plane VCC

1 hour
< 90 %
KPI Expression
100 % SUM(M550C3) / SUM(M550C0)
100 % SUM(MAX_RESERVED_CELL_RATE) / SUM(AAL2_PATH_GUAR_CELL_RATE )
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum percentage of the Iub user plane VCC which has been reserved for DCH
and HSDPA connections. This KPI provides an indication of the maximum overall load of the Iub user plane
VCC. The actual Iub throughput can be greater than or less than that indicated by the reserved load, i.e. The
DCH throughput should be less than the DCH reserved bandwidth but the HSPDA throughput may be either
greater than or less than the reserved bandwidth.
The M550C3 counter represents the maximum DCH and HSDPA reservation. The M550C0 counter
represents the size of the Iub user plane VCC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.5.
DCH Reserved Transport Bandwidth
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

DCH_RESERV_TRANS_BW
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
SUM(M550C1 M550C16) / SUM(M550C7)
SUM(SUM_RESERVED_CELL_RATE - SHARED_HSDPA_AAL2_ALLOCATION) /
SUM(NBR_SAMPLES)
Units: cells per second
Notes: None
KPI Description
This KPI quantifies the bandwidth which has been reserved for DCH connections. The M550C1 counter
divided by the M550C7 counter represents the total DCH and HSDPA reservation. The M550C16 counter
divided by the M550C7 counter represents only the HSDPA reservation. The difference between the two
provides a measure of the DCH reservation.
Means to improve
A high reserved bandwidth indicates that a physical capacity upgrade is likely to be necessary. Upgrading the
physical capacity of the Iub would allow an increased user plane VCC capacity.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.6.
HSDPA Reserved Transport Bandwidth
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_RESERV_TRANS_BW
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
SUM(M550C16) / SUM(M550C7)
SUM(SHARED_HSDPA_AAL2_ALLOCATION) / SUM(NBR_SAMPLES)
Notes: None
KPI Description
This KPI quantifies the average bandwidth reserved for HSDPA throughout the measurement period. The
M550C16 counter divided by the M550C7 counter represents the average HSDPA reservation.
This result from this KPI should not exceed the maximum reserved bandwidth for HSDPA.
Means to improve
If the reserved bandwidth approaches the maximum reserved bandwidth then it may be necessary to increase
the HSPDA bandwidth reservation.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.7.
Total Reserved Transport Bandwidth
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

TOTAL_RESERV_TRANS_BW
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
SUM(M550C1) / SUM(M550C7)
SUM(SUM_RESERVED_CELL_RATE) / SUM(NBR_SAMPLES)
Notes: None
KPI Description
This KPI quantifies the bandwidth which has been reserved for DCH and HSDPA connections. This KPI
provides an indication of the overall load of the Iub user plane VCC. The actual Iub throughput can be greater
than or less than that indicated by the reserved load, i.e. The DCH throughput should be less than the DCH
reserved bandwidth but the HSPDA throughput may be either greater than or less than the reserved
bandwidth.
The M550C1 counter divided by the M550C7 counter represents the total DCH and HSDPA reservation.
Means to improve
A high reserved bandwidth indicates that a physical capacity upgrade is likely to be necessary. Upgrading the
physical capacity of the Iub would allow an increased user plane VCC capacity.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.8.
Maximum Reserved Transport Bandwidth
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
Maximum Reserved Transport Bandwidth

MAX_RESERV_TRANS_BW
None
RAS05
High
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
SUM(M550C3)
SUM(MAX_RESERVED_CELL_RATE)
Notes: None
KPI Description
This KPI quantifies the maximum bandwidth from the Iub user plane VCC which has been reserved for DCH
and HSDPA connections. This KPI provides an indication of the maximum overall load of the Iub user plane
VCC. The actual Iub throughput can be greater than or less than that indicated by the reserved bandwidth, i.e.
The DCH throughput should be less than the DCH reserved bandwidth but the HSPDA throughput may be
either greater than or less than the reserved bandwidth.
The M550C3 counter represents the maximum DCH and HSDPA reservation. The M550C0 counter
represents the size of the Iub user plane VCC.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.9.
Available HSDPA Transport Bandwidth
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AVAIL_HSDPA_TRANS_BW
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
> 1200 kbps
KPI Expression
(53 8 / 1000) (AVG(M550C0) SUM(M550C1 - M550C16) / SUM(M550C7))
(53 8 / 1000) (AVG(AAL2_PATH_GUAR_CELL_RATE) SUM(SUM_RESERVED_CELL_RATE
SHARED_HSDPA_AAL2_ALLOCATION) / SUM(NBR_SAMPLES))
Units: kbps
Notes: None
KPI Description
This KPI quantifies the average Iub bandwidth available for HSDPA. The result is calculated by subtracting
the sum of the DCH reservations from the total Iub user plane VCC bandwidth. The average Iub bandwidth
available for HSDPA provides an indication of the HSDPA throughput which can be expected across the Iub.
The M550C0 counter represents the total bandwidth of the user plane VCC. The M550C0 counter represents
the sum of the DCH and HSDPA reservations whereas the M550C16 counter represents only the HSDPA
reservation. The KPI result is multiplied by (53 * 8 / 1000) to change the units from ATM cells per second to
kbps.
The resulting throughput includes the Iub overheads and should be divided by 1.3 to estimate an equivalent
RLC throughput.
Means to improve
If the average Iub bandwidth available for HSDPA is less than the target HSDPA throughput then a physical
capacity upgrade should be considered.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.10.
Average AAL2 Transport Connection Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_AAL2_TRANS_CONN_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
< 70 %
KPI Expression
100 % SUM(M550C4) / SUM(M550C7 248)
100 % SUM(SUM_AAL2_CONNECTIONS) / SUM(NBR_SAMPLES 248)
Units: %
Notes: None
KPI Description
This KPI quantifies the average percentage of simultaneous AAL2 connection identifiers which were used
throughout the measurement period. The maximum possible number of simultaneous AAL2 connections per
VCC is 248. The M550C4 counter divided by the M550C7 counter indicates the average number of
simultaneous AAL2 connections.
Means to improve
A high average result indicates that it may be necessary to introduce an additional VCC, i.e. a logical capacity
upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.11.
Maximum AAL2 Transport Connection Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_AAL2_TRANS_CONN_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
User Plane VCC

1 hour
< 90 %
KPI Expression
100 % MAX(M550C6) / 248
100 % MAX(MAX_AAL2_CONNECTIONS) / 248
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum percentage of simultaneous AAL2 connection identifiers which were used
throughout the measurement period. The maximum possible number of simultaneous AAL2 connections per
VCC is 248. The M550C6 counter indicates the maximum number of simultaneous AAL2 connections
experienced throughout the measurement period.
Means to improve
A high maximum result indicates that it may be necessary to introduce an additional VCC, i.e. a logical
capacity upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.1.12.
Average HSDPA Transport Connection Count
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_HSDPA_TRANS_CONN_COUNT
None
RAS05
Low
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
SUM(M550C11) / SUM(M550C7)
SUM(SUM_AAL2_CONNECTIONS_HSDPA) / SUM(NBR_SAMPLES)
Units: connections
Notes: None
KPI Description
This KPI quantifies the average number of simultaneous HSDPA connections which were active throughout
the measurement period. This KPI can be used to provide an indication of the quantity of HSDPA traffic.
Means to improve
If the average number of simultaneous HSDPA connections approaches the Node B capability then it may be
necessary to upgrade the capability of the Node B. This KPI quantifies the average rather than peak number of
connections and so blocking is likely to occur while the average result is below the capability of the Node B.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

4.1.13.
Maximum HSDPA Connection Count
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_HSDPA_CONN_COUNT
None
RAS05
Low
Scope
Time Resolution
Target
User Plane VCC

1 hour
None
KPI Expression
MAX(M550C13)
MAX(MAX_AAL2_CONNECTIONS_HSDPA)
Units: connections
Notes: None
KPI Description
This KPI quantifies the maximum number of simultaneous HSDPA connections which were active throughout
the measurement period. This KPI can be used to provide an indication of the quantity of HSDPA traffic.
Means to improve
If the average number of simultaneous HSDPA connections approaches the Node B capability then it may be
necessary to upgrade the capability of the Node B. This KPI quantifies the average rather than peak number of
connections and so blocking is likely to occur while the average result is below the capability of the Node B.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.2.
AAL2 Resource Reservation Measurement (800/320H)
Counters within the AAL2 Resource Reservation Measurement table focus upon the success rate of AAL2
transport resource reservations. AAL2 resource reservations are applicable to the Iub, Iur and Iu-cs
interfaces. These counters capture both the Connection Admission Control (CAC) phase and the AAL2
signalling phase of resource reservation. Individual counters can be used to identify the source of failures
such as a lack of Iub bandwidth, lack of RNC capacity or an AAL2 signalling failure. There are also counters
dedicated to HSDPA, e.g. monitoring the HSDPA resource reservations on the Iub and the duration of those
reservations.
The object of the measurement is the AAL2 path associated with the user plane VCC. The ATM paths are
selected using their ATM interface/VP/VC identifiers. A maximum of 500 user plane VCC can be monitored
simultaneously.
The dummy object interface-0/VPI-0/VCI-0 records statistics for the whole RNC. In addition, the same
dummy object is used when the actual VCI is not known, e.g. digit analysis failures.
The set of counters belonging to the AAL2 Resource Reservation counter table are presented below.
Counter
Number
M800C0
M800C1
M800C2
M800C3
M800C4
M800C5
M800C6
M800C7
M800C8
M800C9
Counter Name
RES_SUCCEEDED
RES_EXT_CAP
RES_INT_CAP
RES_OTHER
AAL2_SUCCEEDED
AAL2_REJECTED
AAL2_SUCCEEDED_HSDPA
TRANSPORT_REJECTED_EXT_HSDPA
TRANSPORT_REJECTED_INT_HSDPA
OTHER_REJECTED_HSDPA
Version : Draft A
In Confidence
Counter
Number
M800C10
M800C11
M800C12
M800C13
M800C14
M800C15
M800C16
M800C17
M800C18
M800C19
Counter Name
ACTIVE_HSDPA_RES_TIME
WAITING_HSDPA_RES_TIME
RELEASE_TIMER_LENGTH
RESERV_REL_DUE_TO_TIMER
RESERV_REL_TIMER_STARTED
RESERV_REL_TIMER_STOPPED
RESERV_REL_DUE_TO_OTHER
ACTIVE_TIME_CUMULATIVE
WAITING_TIME_CUMULATIVE
REJECT_HSDPA_TOO_MANY_USERS
Date: 31/03/09
In Confidence
O2
4.2.1.
AAL2 Reservation Success Rate
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AAL2_RESERV_SUCC_RATE
RNC_602a
RAS05
High
Scope
Time Resolution
Target
User Plane VCC

1 hour
> 99 %
KPI Expression
100 % SUM(M800C4) / SUM(M800C1 + M800C2 + M800C3 + M800C4 + M800C5)
100 % SUM(AAL2_SUCCEEDED) / SUM(RES_EXT_CAP + RES_INT_CAP + RES_OTHER +
AAL2_SUCCEEDED + AAL2_REJECTED)
Units: %
Notes: None
KPI Description
This KPI quantifies the success rate of AAL2 transport reservations. In the case of the Iub, a successful
reservation includes successful admission within both the RNC and the Node B. The RNC admits the resource
request and subsequently sends an AAL2 ERQ message to the Node B. The M800C4 counter is incremented if
the Node B successfully returns an AAL2 ECF message. If the RNC internal reservation fails then one of
M800C1, M800C2 or M800C3 is incremented. M800C1 indicates a lack of external AAL2 resources whereas
M800C2 indicates a lack of AAL2 internal resources. M800C5 is incremented if the ERQ/ECF handshake
with the Node B is rejected.
The object of the measurement is the AAL2 path (user plane VCC). The statistics for the whole RNC can be
calculated using the counter results stored under object interface-0/VPI-0/VCI-0.
Means to improve
A low AAL2 reservation success rate can indicate that there is a lack of user plane VCC resources. This can
be used to trigger a physical capacity upgrade for the transmission link.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.2.2.
Transport HSDPA Reservation Success Rate
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_RESERV_SUCC_RATE
None
RAS05
High
Scope
Time Resolution
Target
User Plane VCC

1 hour
> 95 %
KPI Expression
100 % SUM(M800C6) / SUM(M800C6 + M800C7 + M800C8 + M800C9)
100 % SUM(AAL2_SUCCEEDED_HSDPA)/ SUM(AAL2_SUCCEEDED_HSDPA +
TRANSPORT_REJECTED_EXT_HSDPA + TRANSPORT_REJECTED_INT_HSDPA +
OTHER_REJECTED_HSDPA)
Units: %
Notes: None
KPI Description
This KPI quantifies the success rate of the HSDPA shared AAL2 transport reservation. This KPI is applicable
to the Iub. The reservation for the HSDPA shared bandwidth does not require an AAL2 ERQ/ECF handshake.
The M800C6 counter is incremented if the RNC completes a successful reservation.
If the reservation fails then one of M800C7, M800C8 or M800C9 is incremented. M800C7 indicates a lack of
external resources whereas M800C8 indicates a lack of internal resources. M800C9 is incremented if the
failure is for any other reason.
The object of the measurement is the AAL2 path (user plane VCC). The statistics for the whole RNC can be
calculated using the counter results stored under object interface-0/VPI-0/VCI-0.
Means to improve
A low HSDPA reservation success rate can indicate that there is a lack of user plane VCC resources. This can
be used to trigger a physical capacity upgrade for the transmission link.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
4.2.3.
Transport HSDPA Reservation Utilisation Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_RESERV_UTIL_RATIO
None
RAS05
Low
Scope
Time Resolution
Target
User Plane VCC

1 hour
> 80 %
KPI Expression
100 % SUM(M800C17) / SUM(M800C17 + M800C18)
100 % SUM(ACTIVE_TIME_CUMULATIVE) / SUM(ACTIVE_TIME_CUMULATIVE +
WAITING_TIME_CUMULATIVE)
Units: %
Notes: None
KPI Description
This KPI quantifies the Iub overhead generated by the HSDPA reservation release timer defined by the RNC
databuild parameter ReleaseTimerForSharedHSDPAallocation. If there are relatively few HSDPA data
transfers with a long duration then the overhead will be small. If there are a large number of short HSDPA
data transfers then the overhead will be greater.
The M800C17 counter records the number of seconds during which at least one HSDPA connection has used
the shared HSDPA reservation on the Iub. The M800C18 counter records the number of seconds during which
the shared HSDPA reservation has been made while there are no HSDPA connections.
Means to improve
The Iub HSDPA Allocation Utilisation Ratio is influenced by the traffic profile and also the value assigned to
the RNC databuild parameter ReleaseTimerForSharedHSDPAallocation. The utilisation ratio can be increased
by decreasing the value assigned to the release timer. However, this is only necessary if the total user plane
Iub load is relatively high. Decreasing the release timer also increases the probability of requiring a new
reservation at the start of an HSDPA data transfer. New reservations may be blocked if the DCH load is
relatively high.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
5.
Signalling Measurements
5.1.
AAL2 Signalling Protocol at UNI Measurement (548/224H)
Counters within the AAL2 Signalling Protocol at UNI Measurement table focus upon the control plane
functions used to establish and release AAL2 connections at the User Network Interface (UNI). These
counters are applicable to the Iub interface between the RNC and Node B, i.e. between the RNC and WAM
when AAL2 multiplexing is not used, and between the RNC and AXC when AAL2 multiplexing is used.
The ALCAP ERQ/ECF handshake is used to establish an AAL2 connection after Connection Admission
Control (CAC) has admitted the request. This counter table focuses upon this ALCAP signalling rather than
the CAC admission decision, i.e. this counter table only has visibility of AAL2 reservation requests which
receive a positive response from the CAC.
The object of the measurement is a signalling link identified using its ATM interface/VP/VC identifiers.
There is no limit to the number of signalling links which can be monitored simultaneously.
The set of counters belonging to the Signalling Protocol at UNI Measurement counter table is presented
below.
Counter
Number
M548C1
M548C2
M548C3
M548C4
M548C5
M548C6
M548C7
M548C8
M548C9
M548C10
M548C11
M548C12
Counter Name
NET_OUT
TEMP_FAIL
CONGESTION
REQ_CHAN
RES_UNAVAIL
AAL_PARA
INVALID_MSG
MANDAT_INFO
MSG_NOT_IMPL
INFO_NOT_IMPL
INVALID_INFO
TIMER_EXP_ERQ
Counter
Number
M548C13
M548C14
M548C15
M548C16
M548C17
M548C18
M548C19
M548C20
M548C21
M548C22
M548C23
M548C24
Counter Name
TIMER_EXP_REL
TIMER_EXP_RES
TIMER_EXP_BLO
TIMER_EXP_UBL
MSG_UNRECOG
SAI_ALLOC
CID_VERIF
AAL2PI_VERIF
BINDING_ID_VERIF
LINK_CHAR_VERIF
ADJ_NODE_NOT_AVAIL
COMMON
The counters belonging to rows which are shaded are not available in RAS05. At this stage, no KPI have
been defined from this table of counters. These counters may be used for trouble shooting purposes if there is
a requirement to study the performance of the control plane signalling used to establish and release AAL2
connections.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
5.2.
AAL2 Signalling at NNI Measurement (552/228H)
Counters within the AAL2 Signalling Protocol at NNI Measurement table focus upon the control plane
functions used to establish and release AAL2 connections at the Network Node Interface (NNI) for
signalling points. These counters are applicable to the Iur and Iu-cs interfaces. The ALCAP ERQ/ECF
handshake is used to establish an AAL2 connection after Connection Admission Control (CAC) has admitted
the request. This counter table focuses upon this ALCAP signalling rather than the CAC admission decision,
i.e. this counter table only has visibility of AAL2 reservation requests which receive a positive response from
the CAC.
The object of the measurement is a signalling point identified using its signalling network code and
signalling point code.
The set of counters belonging to the Signalling Protocol at NNI Measurement counter table is presented
below.
Counter
Number
M552C1
M552C2
M552C3
M552C4
M552C5
M552C6
M552C7
M552C8
M552C9
M552C10
M552C11
M552C12
M552C13
M552C14
M552C15
Counter Name
NET_OUT_AT_NNI
TEMP_FAIL_AT_NNI
CONGESTION_AT_NNI
REQ_CHAN_AT_NNI
RES_UNAVAIL_AT_NNI
AAL_PARA_AT_NNI
INVALID_MSG_AT_NNI
MANDAT_INFO_AT_NNI
MSG_NOT_IMPL_AT_NNI
INFO_NOT_IMPL_AT_NNI
INVALID_INFO_AT_NNI
TIMER_EXP_ERQ_AT_NNI
TIMER_EXP_REL_AT_NNI
TIMER_EXP_RES_AT_NNI
TIMER_EXP_BLO_AT_NNI
Counter
Number
M552C16
M552C17
M552C18
M552C19
M552C20
M552C21
M552C22
M552C23
M552C24
M552C25
M552C26
M552C27
M552C28
M552C29
Counter Name
TIMER_EXP_UBL_AT_NNI
MSG_UNRECOG_AT_NNI
SAI_ALLOC_AT_NNI
CID_VERIF_AT_NNI
AAL2PI_VERIF_AT_NNI
BINDING_ID_VERIF_AT_NNI
LINK_CHAR_VERIF_AT_NNI
ADJ_NODE_NOT_AVAIL_AT_NNI
COMMON_AT_NNI
NODAL_FUNCTION_AT_NNI
UNALLOC_NUMB_AT_NNI
NO_ROUTE_AT_NNI
NO_CHANNEL_AT_NNI
RES_MAN_OVERLOAD_AT_NNI
The counters belonging to rows which are shaded are not available in RAS05. At this stage, no KPI have
been defined from this table of counters. These counters may be used for trouble shooting purposes if there is
a requirement to study the performance of the control plane signalling used to establish and release AAL2
connections.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
5.3.
SAAL Signalling Protocol at UNI Measurement (546/222H)
Counters within the SAAL Signalling Protocol at UNI Measurement table focus upon the performance of the
SAAL protocol stack. The measurement table provides information about the Service Specific Coordination
Function (SSCF), the Service Specific Connection Oriented Protocol (SSCOP) errors, the AAL5 Common
Part Convergence Sublayer (CPCS), and the Segmentation and Reassembly sublayer (SAR) for UNI
signalling links. In the case of SSCF, the amount of radio protocol signalling data exchanged between layer 3
and the transport layer, is measured for both the transmitter and receiver. The SSCOP errors provide
performance data regarding the end-to-end secured connection. In the case of the AAL5 CPCS and SAR
sublayers, the quantity of signalling data to and from the ATM Layer, as well as the errors from the radio
transmit and receive side are measured.
The object of the measurement is a signalling link identified using its ATM interface/VP/VC identifiers. The
link type can be AAL2 Signalling Link, CNBAP or DNBAP. There is no limit to the number of signalling
links which can be monitored simultaneously.
The set of counters belonging to the SAAL Signalling Protocol at UNI Measurement counter table is
presented below.
Counter
Number
M546C0
M546C1
M546C2
M546C3
M546C4
M546C5
M546C6
M546C7
M546C8
M546C9
M546C10
M546C11
M546C12
M546C13
M546C14
M546C15
M546C16
M546C17
M546C18
M546C19
M546C20
M546C21
M546C22
M546C23
M546C24
M546C25
Counter Name
MSUS_RECEIVED
OCTETS_RECEIVED
SIG_COMMANDS_RECEIVED
MSUS_TRANSMITTED
OCTETS_TRANSMITTED
SIG_NOTICES_TRANSMITTED
ERROR_CODE_A
ERROR_CODE_B
ERROR_CODE_C
ERROR_CODE_D
ERROR_CODE_E
ERROR_CODE_F
ERROR_CODE_G
ERROR_CODE_H
ERROR_CODE_I
ERROR_CODE_J
ERROR_CODE_K
ERROR_CODE_L
ERROR_CODE_M
ERROR_CODE_O
ERROR_CODE_P
ERROR_CODE_Q
ERROR_CODE_R
ERROR_CODE_S
ERROR_CODE_T
ERROR_CODE_U
Version : Draft A
In Confidence
Counter
Number
M546C26
M546C27
M546C28
M546C29
M546C30
M546C31
M546C32
M546C33
M546C34
M546C35
M546C36
M546C37
M546C38
M546C39
M546C40
M546C41
M546C42
M546C43
M546C44
M546C45
M546C46
M546C47
M546C48
M546C49
M546C50
M546C51
Counter Name
ERROR_CODE_V
ERROR_CODE_W
ERROR_CODE_X
ERROR_CODE_LW
ERROR_CODE_LX
ERROR_CODE_DEL
RX_ERR
NO_ERR
UNEXP_ERR
BA_ERR
CRC_ERR
CPI_ERR
LEN_ERR
PAD_ERR
CRC_PAD_ERR
RSM_TIMEOUT
ABORT_DET
EARLY_DISC
STATUS_QF
VCC_FW
FBQ_UNDERF
STAT_Q_OVERF
VCC_RESE
VCC_RELE
RX_PDU
RX_SIZE
Date: 31/03/09
In Confidence
O2
5.3.1.
Unsolicited SSCOP Errors
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

UNSOL_SSCOP_ERR
None
RAS05
Medium
Scope
Time Resolution
Target
Signalling Link
1 hour
None
KPI Expression
M546C6 + M546C7 + M546C8 + M546C9 + M546C10 + M546C11 + M546C12 + M546C13 + M546C14 +
M546C15 + M546C16 + M546C17 + M546C18 + M546C19 + M546C20 + M546C21 + M546C22 +
M546C23 + M546C24 + M546C25 + M546C26 + M546C27 + M546C28 + M546C29 + M546C30 +
M546C31
ERROR_CODE_A + ERROR_CODE_B + ERROR_CODE_C + ERROR_CODE_D + ERROR_CODE_E +
ERROR_CODE_F + ERROR_CODE_G + ERROR_CODE_H + ERROR_CODE_I + ERROR_CODE_J +
ERROR_CODE_K + ERROR_CODE_L + ERROR_CODE_M + ERROR_CODE_O + ERROR_CODE_P +
ERROR_CODE_Q + ERROR_CODE_R + ERROR_CODE_S + ERROR_CODE_T + ERROR_CODE_U +
ERROR_CODE_V + ERROR_CODE_W + ERROR_CODE_X + ERROR_CODE_LW +
ERROR_CODE_LX + ERROR_CODE_DEL
Units: Errors
Notes: None
KPI Description
The Service Specific Connection Orientated Protocol (SSCOP) layer forms part of the Common NBAP,
Dedicated NBAP, and AAL2 signalling protocol stacks. This KPI quantifies the total number of errors
experienced by the SSCOP layer. The object of the KPI is a VCC belonging to the Iub VP. There can be
separate KPI results for the VCC associated with the Common NBAP, Dedicated NBAP, and AAL2
signalling protocol stacks.
Means to improve
If the number of errors becomes high then it is necessary to identify which counter dominates the result. This
individual counter will provide an indication of the specific cause.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.
ATM/IP Transport Measurements

6.1.
ATM Virtual Channel Connection Measurement (530/212H)
Counters within the ATM Virtual Channel Connection Measurement table focus upon the average data rate
experienced by specific ATM Virtual Channel Connection (VCC). The counters allow the level of ATM
traffic to be monitored, e.g. NBAP signalling, Node B O&M traffic and user plane data.. Traffic can be
monitored on the Iub, Iur or Iu interfaces.
The object of the measurement is an ATM VCC identified using its ATM interface/VP/VC identifiers. All
ATM VCI types can be selected as objects for this measurement.
The set of counters belonging to the ATM Virtual Channel Connection Measurement counter table is
presented below.
Counter
Number
M530C0
M530C1
M530C2
M530C3
M530C4
M530C5
M530C6
M530C7
Version : Draft A
In Confidence
Counter Name
IN_TOT_CELLS_VC
EG_TOT_CELLS_VC
IN_REC_CELLS_VC
IN_QUEUED_CELLS_VC
IN_CAP_VC
EG_REC_CELLS_VC
EG_QUEUED_CELLS_VC
EG_CAP_VC
Date: 31/03/09
In Confidence
O2
6.1.1.
Total User Plane Egress Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

TOT_USR_PL_EGR_LOAD
None
RAS05
High
Scope
Time Resolution
Target
VCC
1 hour
< 70 %
KPI Expression
100 % SUM(M530C1) / SUM(M550C0 PERIOD_DURATION 60)
100 % SUM(EG_TOT_CELLS_VC) / SUM(AAL2_PATH_GUAR_CELL_RATE
PERIOD_DURATION 60)
Units: %
Notes: The PERIOD_DURATION is defined by the measurement period in units of minutes.
KPI Description
This KPI quantifies the total downlink traffic transferred across the Iub user plane VCC as a percentage of the
user plane VCC capacity. The factor of 3600 assumes that the measurement period is 1 hour.
Counter M530C1 quantifies the number of Egress ATM cells which are transferred during the measurement
period. The factor of 3600 is used to convert this result into ATM cells per second. Counter M550C0
quantifies the bandwidth of the Iub user plane VCC.
Means to improve
If the KPI result becomes high, an Iub physical capacity upgrade should be considered. The KPI result
represents an average load during the measurement period. There could be short term peaks in activity which
cause blocking prior to the load approaching 100 %.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.1.2.
Total User Plane Ingress Transport Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

TOT_USR_PL_ING_LOAD
None
RAS05
High
Scope
Time Resolution
Target
VCC
1 hour
< 70 %
KPI Expression
100 % SUM(M530C0) / SUM(M550C0 PERIOD_DURATION 60)
100 % SUM(N_TOT_CELLS_VC) / SUM(AAL2_PATH_GUAR_CELL_RATE PERIOD_DURATION
60)
Units: %
KPI Description
This KPI quantifies the total uplink traffic transferred across the Iub user plane VCC as a percentage of the
user plane VCC capacity. The factor of 3600 assumes that the measurement period is 1 hour.
Counter M530C0 quantifies the number of Ingress ATM cells which are transferred during the measurement
period. The factor of 3600 is used to convert this result into ATM cells per second. Counter M550C0
quantifies the bandwidth of the Iub user plane VCC.
Means to improve
If the KPI result becomes high, an Iub physical capacity upgrade should be considered. The KPI result
represents an average load during the measurement period. There could be short term peaks in activity which
cause blocking prior to the load approaching 100 %.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.1.3.
Egress Cell Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

EGR_DRP_RATIO
None
RAS06
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
100 % SUM(M530C5 - M530C1 - M530C6) / SUM(M530C5)
100 % SUM(EG_REC_CELLS_VC - EG_TOT_CELLS_VC - EG_QUEUED_CELLS_VC) /
SUM(EG_REC_CELLS_VC)
Units: %
Notes: None.
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped by the RNC prior to transmission across
the VCC. Dropping cells corresponds to the RNC output buffer overflowing. The EG_REC_CELLS_VC
counter represents the total number of cells fed into the RNC output buffer. The EG_TOT_CELLS_VC
counter represents the number of cells which are successfully transferred into the VCC whereas the
EG_QUEUED_CELLS_VC counter represents the number of cells within the output buffer.
Means to improve
If the result from this KPI becomes non-zero then the VCC could be experiencing congestion, i.e. the RNC is
not able to empty the output buffer at a sufficient rate. Other KPI should be studied to evaluate the VCC load.
If congestion is confirmed then the transport bearer tuning feature should be evaluated to determine whether
or not connection admission control has been allowed to admit too many connections.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.1.4.
Ingress Cell Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ING_DRP_RATIO
None
RAS06
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
100 % SUM(M530C2 - M530C0 - M530C3) / SUM(M530C2)
100 % SUM(SUM(IN_REC_CELLS_VC IN_TOT_CELLS_VC IN_QUEUED_CELLS_VC) /
SUM(IN_REC_CELLS_VC)
Units: %
Notes: None.
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped by the RNC after receiving them from the
VCC. Dropping cells corresponds to the RNC input buffer overflowing. The IN_REC_CELLS_VC counter
represents the total number of cells fed into the RNC input buffer. The IN_TOT_CELLS_VC counter
represents the number of cells which are successfully transferred into the RNC from the input buffer whereas
the IN_QUEUED_CELLS_VC counter represents the number of cells within the input buffer.
Means to improve
If the result from this KPI becomes non-zero then the RNC could be experiencing congestion, i.e. the RNC is
not able to empty the input buffer at a sufficient rate. Other KPI should be studied to evaluate the RNC
throughput load. It may be necessary to complete an RNC capacity upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.2.
ATM Layer Performance Measurement (528/210H)
Counters within the ATM Layer Performance Measurement table focus upon ATM traffic management
actions. They also provide data regarding the quantity of data passing through the ATM switching units.
The object of the measurement is a computer unit that is identified by its unit type and index.
The set of counters belonging to the ATM Layer Performance Measurement counter table is presented
below.
Counter
Number
M528C2
M528C3
M528C4
M528C5
M528C8
M528C9
M528C10
M528C11
M528C16
M528C17
M528C18
Counter Name
I_CLP1_DROP
I_PPD_DROP
I_EPD_DROP
I_FRAMES_EPD_DROP
E_CLP1_DROP
E_PPD_DROP
E_EPD_DROP
E_FRAMES_EPD_DROP
I_CLP0_DROP
I_TRANSMIT_TO_FABRIC
I_TAGGED
Version : Draft A
In Confidence
Counter
Number
M528C19
M528C20
M528C21
M528C22
M528C23
M528C24
M528C25
M528C26
M528C27
M528C28
M528C29
Counter Name
I_POLICING_DROP
I_ERR_BRAM
I_UTOPIA_ERR
I_ERR_CRC
I_ERR_HEADER
E_CLP0_DROP
E_TRANSMIT_TO_PHY
E_ERR_BRAM
E_RCV_FROM_FI
E_ERR_FI
E_ERR_LOOKUP
Date: 31/03/09
In Confidence
O2
6.2.1.
Computer Unit ATM Cell Egress Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

COMP_ATM_EGR_DROP_RATIO
None
RAS05
Medium
Scope
Time Resolution
Target
Computer Unit
1 hour
< 0.01 %
KPI Expression
100 % SUM(M528C8 + M528C9 + M528C10 + M528C24 + M528C26 + M528C28 + M528C29) /
SUM(M528C25 + M528C8 + M528C9 + M528C10 + M528C24 + M528C26 + M528C28 + M528C29)
100 % SUM(E_CLP1_DROP + E_PPD_DROP + E_EPD_DROP + E_CLP0_DROP + E_ERR_BRAM +
E_ERR_FI + E_ERR_LOOKUP) / SUM(E_TRANSMIT_TO_PHY + E_CLP1_DROP + E_PPD_DROP +
E_EPD_DROP + E_CLP0_DROP + E_ERR_BRAM + E_ERR_FI + E_ERR_LOOKUP)
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped upon leaving the RNC. There is a set of 7
counters which record the number of dropped cells whereas M528C25 records the number of cells which are
successfully forwarded to the physical layer outside the RNC.
Means to improve
If a high drop ratio is recorded then the individual counters should be studied to identify a specific cause for
the ATM cells being dropped.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.2.2.
Computer Unit ATM Cell Ingress Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

COMP_ATM_ING_DROP_RATIO
None
RAS05
Medium
Scope
Time Resolution
Target
Computer Unit
1 hour
< 0.01 %
KPI Expression
100 % SUM(M528C2 + M528C3 + M528C4 + M528C16 + M528C19 + M528C20 + M528C21 +
M528C22 + M528C23) / SUM(M528C17 + M528C2 + M528C3 + M528C4 + M528C16 + M528C19 +
M528C20 + M528C21 + M528C22 + M528C23)
100 % SUM(I_CLP1_DROP + I_PPD_DROP + I_EPD_DROP + I_CLP0_DROP + I_POLICING_DROP +
I_ERR_BRAM + I_UTOPIA_ERR + I_ERR_CRC + I_ERR_HEADER) /
SUM(I_TRANSMIT_TO_FABRIC + I_CLP1_DROP + I_PPD_DROP + I_EPD_DROP + I_CLP0_DROP +
I_POLICING_DROP + I_ERR_BRAM + I_UTOPIA_ERR + I_ERR_CRC + I_ERR_HEADER)
Units: %
Notes: the KPI is not valid for the NIP1 unit because in that case the counter M528C17 records both ingress
and egress cells.
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped upon reaching the RNC. There is a set of
9 counters which record the number of dropped cells whereas M528C17 records the number of cells which are
successfully forwarded to the RNC switching fabric.
Means to improve
If a high drop ratio is recorded then the individual counters should be studied to identify a specific cause for
the ATM cells being dropped.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.3.
ATM Route Load Measurement (531/213H)
The ATM route load measurement reports the AAL2 layer capacity allocations at the ATM route level. The
counters of this measurement are similar to the counters of the AAL2 path CAC resource measurement
(M550/226H). This measurement can be used for trunked interfaces, for which many AAL2 paths use the
same ATM route. The object of the measurement is ATM route and the measured routes are selected with the
ATM route ID. The maximum number of measured routes is 256.
The set of counters belonging to the ATM Route Load Measurement counter table is presented below.
Counter
Number
M531C0
M531C1
M531C2
M531C3
M531C4
M531C5
M531C6
M531C7
M531C8
M531C9
Counter Name
GRT_CELL_RATE
HSDPA_CELL_RATE_MAX
HSDPA_CELL_RATE_MIN
HSDPA_CELL_RATE_AVG
RES_CELL_RATE_MAX
RES_CELL_RATE_MIN
RES_CELL_RATE_AVG
ACTIVE_AAL2_CONN_MAX
ACTIVE_AAL2_CONN_MIN
ACTIVE_AAL2_CONN_AVG
Counter
Number
M531C10
M531C11
M531C12
M531C13
M531C14
M531C15
M531C16
M531C17
M531C18
Counter Name
SUCC_AAL2_CONN
AAL2_REJECT_BY_CAC
AAL2_REJECT_BY_HW
ACTIVE_HSDPA_CONN_MAX
ACTIVE_HSDPA_CONN_MIN
ACTIVE_HSDPA_CONN_AVG
SUCC_HSDPA_CONN
HSDPA_REJECT_BY_CAC
HSDPA_REJECT_BY_HW
No KPI have been defined from this set of counters.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.4.
ATM Interface Measurement (532/214H)
The ATM interface measurement reports traffic statistics for a specific interface inside an ATM interface
unit. The measurement provides an indication of the ATM interface traffic load by reporting the traffic
volumes and the bandwidth available for a specific interface. The measurement can also be used to detect
interfaces that are congested and cause traffic loss.
Congestion can be detected by following the number of ATM cells going in and coming out of the interface.
Note that there is one limitation related to the the ATM cell loss: if ATM OAM CC has been activated, the
cells generated by this functionality are inserted to ATM cell flow inside the interface unit and they are not
counted as input cells, but only as output cells.
The object of the measurement is ATM interface and the measured interfaces are selected with the ATM
interface ID. The set of counters belonging to the ATM Interface Measurement counter table is presented
below.
Counter
Number
M532C0
M532C1
M532C2
M532C3
M532C4
M532C5
M532C6
M532C7
M532C8
M532C9
M532C10
M532C11
M532C12
M532C13
Counter Name
IN_CBR_REC_CELL
IN_CBR_TR_CELL
IN_CBR_QUEUED_CELL
EG_CBR_REC_CELL
EG_CBR_TR_CELL
EG_CBR_QUEUED_CELL
IN_UBR_PLUS_REC_CELL
IN_UBR_PLUS_TR_CELL
IN_UBR_PLUS_QUEUED_CELL
EG_UBR_PLUS_REC_CELL
EG_UBR_PLUS_TR_CELL
EG_UBR_PLUS_QUEUED_CELL
IN_UBR_REC_CELL
IN_UBR_TR_CELL
Version : Draft A
In Confidence
Counter
Number
M532C14
M532C15
M532C16
M532C17
M532C18
M532C19
M532C20
M532C21
M532C22
M532C23
M532C24
M532C25
M532C26
M532C27
Counter Name
IN_UBR_QUEUED_CELL
EG_UBR_REC_CELL
EG_UBR_TR_CELL
EG_UBR_QUEUED_CELL
IN_TOT_REC_CELL
IN_TOT_TR_CELL
IN_TOT_QUEUED_CELL
EG_TOT_REC_CELL
EG_TOT_TR_CELL
EG_TOT_QUEUED_CELL
IN_CAP
EG_CAP
DISC_HEC
ERR_HEC
Date: 31/03/09
In Confidence
O2
6.4.1.
ATM Interface Egress Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ATM_INT_EGR_LOAD
None
RAS06
Low
Scope
Time Resolution
Target
Computer Unit
1 hour
None
KPI Expression
100 % SUM(M532C21) / SUM(M532C25)
100 % SUM(EG_TOT_REC_CELL) / SUM(EG_CAP)
Units: %
Notes: None
KPI Description
This KPI quantifies the load of a specific ATM interface. This ATM interface could be an E1 or STM1. This
KPI can be used in combination with the KPI which monitor the VCC load. When Inverse Multiplexing for
ATM (IMA) is used then the VCC KPI provide an overall reflection of transport network performance
whereas the ATM interface KPI reflect the performance of individual connections, i.e. individual E1 or
STM1.
Means to improve
If the ATM interface load becomes high while the VCC load remains low, checks should be completed for
failed E1 connections belonging to the same IMA group. If both the ATM interface and VCC loads are high
then it may be necessary to complete a capacity upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.4.2.
ATM Interface Ingress Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ATM_INT_ING_LOAD
None
RAS06
Low
Scope
Time Resolution
Target
Computer Unit
1 hour
None
KPI Expression
100 % SUM(M532C18) / SUM(M532C24)
100 % SUM(IN_TOT_REC_CELL) / SUM(IN_CAP)
Units: %
Notes: None
KPI Description
This KPI quantifies the load of a specific ATM interface. This ATM interface could be an E1 or STM1. This
KPI can be used in combination with the KPI which monitor the VCC load. When Inverse Multiplexing for
ATM (IMA) is used then the VCC KPI provide an overall reflection of transport network performance
whereas the ATM interface KPI reflect the performance of individual connections, i.e. individual E1 or
STM1.
Means to improve
If the ATM interface load becomes high while the VCC load remains low, checks should be completed for
failed E1 connections belonging to the same IMA group. If both the ATM interface and VCC loads are high
then it may be necessary to complete a capacity upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.4.3.
ATM Interface Egress Cell Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ATM_INT_EGR_CELL_DRP
None
RAS06
Low
Scope
Time Resolution
Target
Computer Unit
1 hour
None
KPI Expression
100 % SUM(M532C21 - M532C22 - M532C23) / SUM(M532C21)
100 % SUM(EG_TOT_REC_CELL - EG_TOT_TR_CELL - EG_TOT_QUEUED_CELL) /
SUM(EG_TOT_REC_CELL)
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped by the RNC prior to transmission across
the ATM interface. Dropping cells corresponds to the RNC output buffer overflowing. The
EG_TOT_REC_CELL counter represents the total number of cells fed into the RNC output buffer. The
EG_TOT_TR_CELL counter represents the number of cells which are successfully transferred into the ATM
interface whereas the EG_TOT_QUEUED_CELL counter represents the number of cells within the output
buffer.
Means to improve
If the result from this KPI becomes non-zero then the ATM interface could be experiencing congestion, i.e.
the RNC is not able to empty the output buffer at a sufficient rate. Other KPI should be studied to evaluate the
ATM interface load. If congestion is confirmed then the transport bearer tuning feature should be evaluated to
determine whether or not connection admission control has been allowed to admit too many connections.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.4.4.
ATM Interface Ingress Cell Drop Ratio
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ATM_INT_ING_CELL_DRP
None
RAS06
Low
Scope
Time Resolution
Target
Computer Unit
1 hour
None
KPI Expression
100 % SUM(M532C18 - M532C19 - M532C20) / SUM(M532C18)
100 % SUM(IN_TOT_REC_CELL - IN_TOT_TR_CELL - IN_TOT_QUEUED_CELL) /
SUM(IN_TOT_REC_CELL)
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of ATM cells which are dropped by the RNC after receiving them from the
ATM interface. Dropping cells corresponds to the RNC input buffer overflowing. The IN_TOT_REC_CELL
counter represents the total number of cells fed into the RNC input buffer. The IN_TOT_TR_CELL counter
represents the number of cells which are successfully transferred into the RNC from the input buffer whereas
the IN_TOT_QUEUED_CELL counter represents the number of cells within the input buffer.
Means to improve
If the result from this KPI becomes non-zero then the RNC could be experiencing congestion, i.e. the RNC is
not able to empty the input buffer at a sufficient rate. Other KPI should be studied to evaluate the RNC
throughput load. It may be necessary to complete an RNC capacity upgrade.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.5.
ATM Virtual Path Connection Measurement (529/211H)
Counters within the ATM Virtual Path Connection Measurement table report the average rate of traffic
across an ATM Virtual Path Connection. Connections which are terminated at the RNC ATM interface unit
cannot be selected for measurement. Only connections which are switched through the interface can be
selected. This limitation is caused by the ATM hardware.
The object of the measurement is an ATM Virtual Path that is identified by is interface/VP identifiers.
6.6.
AAL5 Protocol Measurement in Chorus (549/225H)
Counters within the AAL5 Protocol Measurement in Chorus table reports information about the quantity of
traffic between the ATM later and the AAL5 layer within the Chorus units. They also provide information
regarding any protocol abnormalities detected during the reassembly of data from ATM cells to CPCS data
units.
The object of the measurement is a computer unit which is identified by its unit type and index.
6.7.
AAL5 Protocol Measurement in DMX (547/223H)
Counters within the AAL5 Protocol Measurement in DMX table reports information about the quantity of
traffic between the ATM later and the AAL5 layer within the DMX units. They also provide information
regarding any protocol abnormalities detected during the reassembly of data from ATM cells to CPCS data
units.
6.8.
TCP/IP Protocol Measurement (563/233H)
Counters within the TCP/IP Protocol Measurement table reports information about the TCP/IP protocol stack
within different units of the network element. TCP, UDP, ICMP, IPv4 and IPv6 transactions are measured.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.9.
AAL2 Scheduling Performance in RNC (553/229H)
Counters within the AAL2 Scheduling Performance in RNC table focus upon the performance of the low
priority AAL2 buffers within the RNC. These low priority buffers are used for HSDPA traffic. If HSDPA is
not enabled the counters within this table are not incremented. The counters are applicable to both the shared
and dedicated VCC configurations. The use of dedicated VCC requires the route selection feature. The object
of the measurement is the VCC associated with the low priority buffer.
The AAL2 scheduling performance depends upon whether or not the dynamic HSDPA scheduling feature is
enabled. The majority of counters are incremented irrespective of whether or not this feature is enabled. A
subset of the counters are only incremented if this feature is enabled, i.e. the number of up, down and stop
commands.
The set of counters belonging to the AAL2 Scheduling Performance in RNC counter table is presented
below.
Counter
Number
M553C0
M553C1
M553C2
M553C3
M553C4
Counter Name
BE_QUE_PEAK
BE_QUE_SUM
BE_QUE_SAMPLES
BE_QUE_DELAY_PEAK
BE_QUE_DELAY_SUM
Version : Draft A
In Confidence
Counter
Number
M553C5
M553C6
M553C7
M553C8
M553C9
Counter Name
BE_QUE_DELAY_SAMPLES
BE_QUE_DOWN_MSGS
BE_QUE_UP_MSGS
BE_QUE_STOP_MSGS
BE_QUE_DRP_EVENTS
Date: 31/03/09
In Confidence
O2
6.9.1.
HSDPA Peak AAL2 CPS Rate
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_PK_AAL2_RATE
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
MAX(M553C0)
MAX(BE_QUE_PEAK)
Units: packets per second
Notes: None
KPI Description
This KPI quantifies the peak rate at which HSDPA AAL2 CPS packets within the low priority buffer are
passed to the ATM layer for transfer across the Iub. The size of an AAL2 CPS packet is not fixed and so it is
not possible to translate the packet rate into an equivalent bit rate. The M553C0 counter records the maximum
number of packets serviced during any individual 1 second interval.
Means to improve
A high peak rate means that HSDPA was able to achieve a high Iub throughput for at least 1 second of the
measurement period. The result from this KPI should be compared with the result from the HSDPA Average
AAL2 CPS Rate KPI. A large difference between the peak and average results could be generated by large
variations in either the non-HSDPA or HSDPA traffic. If the dynamic HSDPA scheduling feature is not used
the peak AAL2 CPS packet rate will be limited by the value assigned to the
SharedHSDPAFlowControlAllocation parameter. If the dynamic HSDPA scheduling feature is used there is
greater potential to achieve higher peak AAL2 CPS packet rates. In general, achieving an increased peak rate
requires an increased Iub capacity. If the dynamic HSDPA scheduling feature is not used then the peak rate
could be increased by increasing the value assigned to the SharedHSDPAFlowControlAllocation parameter.
However, increasing the value assigned to this parameter increases the risk of AAL2 buffer overflow during
periods when non-HSDPA traffic is high.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.2.
HSDPA Average AAL2 CPS Rate
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_AVG_AAL2_RATE
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
SUM(BE_QUE_SUM) / SUM(BE_QUE_SAMPLES)
Units: packets per second
Notes: None
KPI Description
This KPI quantifies the average rate at which HSDPA AAL2 CPS packets within the low priority buffer are
passed to the ATM layer for transfer across the Iub. The size of an AAL2 CPS packet is not fixed and so it is
not possible to translate the packet rate into an equivalent bit rate. The KPI result is averaged across the time
that there is data in the AAL2 buffer. The M553C1 counter records the total number of AAL2 CPS packets
which were passed to the ATM layer during the measurement period. The M553C2 counter records the
number of 1 second intervals during which there was data in the low priority buffer.
Means to improve
A high average rate means that HSDPA was able to maintain a high Iub throughput during the time that there
was HSDPA data to transfer. The result from this KPI should be compared with the result from the HSDPA
Peak AAL2 CPS Rate KPI. The average AAL2 CPS packet rate is likely to be influenced by the value
assigned to the SharedHSDPAallocation parameter. Increasing the value assigned to this parameter should
increase the Iub throughput achieved by HSDPA. However, increasing this parameter by too much will
decrease the probability of a successful Iub reservation. If the HSDPA Iub reservation fails, HSDPA
connections will be admitted as overbooked and HSDPA Iub throughput will be completely best effort. The
average packet rate is also likely to be influenced by the SharedHSDPAFlowControlAllocation parameter
when dynamic HSDPA scheduling is not used.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.3.
HSDPA Peak AAL2 CPS Delay
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
HSDPA Peak AAL2 CPS Packet Delay

HSDPA_PK_AAL2_DELAY
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
MAX(M553C3)
MAX(BE_QUE_DELAY_PEAK)
Units: ms
Notes: None
KPI Description
This KPI quantifies the peak delay experienced by HSDPA AAL2 CPS packets as they pass through the low
priority AAL2 buffer. The delay is sampled once per second and the value assigned to M553C3 is updated if
the sampled delay is greater than the existing value of M553C3.
If dynamic HSDPA flow control is enabled, the result from this KPI should be compared to the value assigned
to either HSDPAFlowControlTargetDelayDedicatedVCC or HSDPAFlowControlTargetDelaySharedVCC.
Means to improve
A high peak delay indicates at least short term Iub congestion. The result from this KPI should be compared
with the result from the average AAL2 CPS packet delay KPI. A peak delay which is significantly greater
than the average delay indicates that the Iub congestion was only short term. The peak and average delays can
be influenced by the SharedHSDPAFlowControlAllocation and SharedHSDPAallocation parameters. The
SharedHSDPAFlowControlAllocation parameter determines the maximum rate at which HSDPA data enters
the low priority buffer. If data enters at a low rate then it is less likely to experience congestion and delays are
less likely to be significant. However this will limit the HSDPA throughput performance. The Iub capacity
should be sufficient to achieve high throughputs with minimum delays. Configuring the
SharedHSDPAallocation parameter with a high value will help to decrease delays by reserving greater
bandwidth for HSDPA but will also increase the probability of the reservation failing.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.4.
HSDPA Average AAL2 CPS Delay
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_AVG_AAL2_DELAY
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
SUM(BE_QUE_DELAY_SUM) / SUM(BE_QUE_DELAY_SAMPLES)
Units: ms
Notes: None
KPI Description
This KPI quantifies the average delay experienced by HSDPA AAL2 CPS packets as they pass through the
low priority AAL2 buffer. The KPI result is averaged across the time that there is data in the AAL2 buffer.
The M553C4 counter records the accumulated delay of AAL2 CPS packets as they pass through the AAL2
buffer. The accumulated delay is based upon a sampling period of 1 second. The M553C5 counter records the
number of 1 second intervals during which there was data in the low priority buffer.
If dynamic HSDPA flow control is enabled, the result from this KPI should be compared to the value assigned
to either HSDPAFlowControlTargetDelayDedicatedVCC or HSDPAFlowControlTargetDelaySharedVCC.
Means to improve
A high average delay indicates longer term Iub congestion. A high average delay could be experienced if the
SharedHSDPAFlowControlAllocation parameter is configured with a high value relative to the
SharedHSDPAallocation parameter, i.e. data enters the AAL2 buffers at a rate which is potentially greater
than the rate at which those buffers can be emptied. Limiting the rate at which data enters the AAL2 buffers is
likely to reduce the AAL2 buffer delay but will have a negative impact upon the HSDPA throughput
performance. Enabling the dynamic HSDPA scheduling feature will remove the requirement to use the
SharedHSDPAFlowControlAllocation parameter to limit the rate at which data enters the low priority buffer.
The Iub capacity should be sufficient to achieve high throughputs with minimum delays. Configuring the
SharedHSDPAallocation parameter with a high value will help to decrease delays by reserving greater
bandwidth for HSDPA but will also increase the probability of the reservation failing
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.5.
HSDPA Flow Control Slow Down
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_FC_DOWN
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
100 % SUM(M553C6) / SUM(M553C6 + M553C7 + M553C8)
100 % SUM(BE_QUE_DOWN_MSGS) / SUM(BE_QUE_DOWN_MSGS + BE_QUE_UP_MSGS +
BE_QUE_STOP_MSGS)
Units: %
Notes: None
KPI Description
This KPI is only applicable if the dynamic HSDPA flow control feature is enabled. This KPI quantifies the
percentage of flow control messages which instruct the MAC layer to decrease the rate at which data is passed
into the AAL2 low priority buffers.
Means to improve
A high percentage of slow down flow control messages indicates that the MAC layer is transferring data too
rapidly into the AAL2 buffers. This increases the probability of high AAL2 buffer occupancy and
consequently flow control may issue a stop message.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.6.
HSDPA Flow Control Speed Up
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_FC_UP
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
100 % SUM(M553C7) / SUM(M553C6 + M553C7 + M553C8)
100 % SUM(BE_QUE_UP_MSGS) / SUM(BE_QUE_DOWN_MSGS + BE_QUE_UP_MSGS +
BE_QUE_STOP_MSGS)
Units: %
Notes: None
KPI Description
percentage of flow control messages which instruct the MAC layer to increase the rate at which data is passed
into the AAL2 low priority buffers.
Means to improve
A high percentage of speed up flow control messages indicates that the MAC layer is transferring data too
slowly into the AAL2 buffers. This could be a result of the MAC layer within the RNC receiving insufficient
HSDPA data from the core network.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.7.
HSDPA Flow Control Stop
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_FC_STOP
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
100 % SUM(M553C8) / SUM(M553C6 + M553C7 + M553C8)
100 % SUM(BE_QUE_STOP_MSGS) / SUM(BE_QUE_DOWN_MSGS + BE_QUE_UP_MSGS +
BE_QUE_STOP_MSGS)
Units: %
Notes: None
KPI Description
percentage of flow control messages which instruct the MAC layer to stop passing data into the AAL2 low
priority buffers.
Means to improve
A high percentage of stop flow control messages indicates that the MAC layer is transferring data too rapidly
into the AAL2 buffers. This increases the probability of high AAL2 buffer occupancy and potential buffer
overflow.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.9.8.
HSDPA Dropped AAL2 CPS
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

HSDPA_DROP_AAL2
None
RAS05.1
Medium
Scope
Time Resolution
Target
VCC
1 hour
None
KPI Expression
SUM(M553C9)
SUM(BE_QUE_DRP_EVENTS)
Units: drop events
Notes: None
KPI Description
This KPI quantifies the number of AAL2 CPS packet drop events. Drop events can be triggered by either high
packet delay or high buffer occupancy. The M553C9 counter records the absolute number of drop events.
Means to improve
The number of drop events should be reduced if the HSDPA dynamic flow control feature is enabled. The
number of drops could be high if dynamic flow control is not enabled and the
SharedHSDPAFlowControlAllocation parameter is configured with a relatively high value.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

6.10.
Iu-PS Throughput Measurement (801/321H)
Counters within the Iu-PS Throughput measurement quantify the Iub-PS interface traffic and events
associated with the GTP protocol between the RNC and PS core network. The measurement results are
recorded on a per GTPU basis. The total RNC or RAN results can be calculated by summing the GTPU
results.
Throughput results are recorded separately for each trafffic class. They are also recorded separately for the
uplink and downlink. The results exclude the overhead generated by the transport headers, i.e. the throughput
generated by the payload is recorded.
The set of counters belonging to the Iu-PS Throughput Measurement counter table is presented below.
Counter
Number
M801C0
M801C1
M801C2
M801C3
M801C4
M801C5
M801C6
M801C7
M801C8
M801C9
Counter Name
INPUT_BYTES_TOTAL_UDP
INPUT_IP_PACKETS_TOTAL
INPUT_TRAF_BYTES_TC_CONV
INPUT_TRAF_BYTES_TC_STREAM
INPUT_TRAF_BYTES_TC_INTERAC
INPUT_TRAF_BYTES_TC_BACKGR
OUTPUT_BYTES_TOTAL_UDP
OUTPUT_IP_PACKETS_TOTAL
OUTPUT_TRAF_BYTES_TC_CONV
OUTPUT_TRAF_BYTES_TC_STREAM
Version : Draft A
In Confidence
Counter
Number
M801C10
M801C11
M801C12
M801C13
M801C14
M801C15
M801C16
M801C17
M801C18
M801C19
Counter Name
OUTPUT_TRAF_BYTES_TC_INTERAC
OUTPUT_TRAF_BYTES_TC_BACKGR
ECHO_REQUEST_RECEIVED
ECHO_RESPONSE_RECEIVED
ECHO_RESPONSE_SENT
ERROR_INDICATIONS_RECEIVED
ERROR_INDICATIONS_SENT
EXTENS_HEAD_NOTIF_RECEIVED
AVERAGE_NBR_OF_GTP_TUNNELS
MAX_NBR_OF_GTP_TUNNELS
Date: 31/03/09
In Confidence
O2
6.10.1.
Average Uplink Total Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_UL_TOT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(M801C6) / [SUM(PERIOD_DURATION) 60000000]
80 SUM(OUTPUT_BYTES_TOTAL_UDP) / [SUM(PERIOD_DURATION) 60000000]
Units: Mbps
KPI Description
This KPI quantifies the average uplink Iu-PS throughput. The M801C6 counter is recorded on a per GTPU
basis. The result must be aggregated across the set of GTPU within each RNC to generate the RNC results.
The multiplying factor of 80 is included because the M801C6 counter has units of 10 bytes. The KPI result
represents the throughput of the Iu-PS payload. It excludes the overheads generated by the GTP and transport
network protocol stack layers. These overheads should be included when comparing the Iu-PS throughput
with the actual physical capacity of the Iu-PS, i.e. when evaluating whether or not the interface is approaching
congestion. The GTP-U/UDP/IP/AAL5/ATM overhead is typically 16 % when assuming a payload of 1420
bytes.
Means to improve
The result from this KPI reflects the quantity of traffic loading the network. A low result indicates that the
quantity of PS traffic is small. If the result from this KPI (with the GTP-U/UDP/IP/AAL5/ATM overhead
added) approaches the capacity of the Iu-PS then it may be necessary to trigger a capacity upgrade. The
comparison between the KPI result and the Iu-PS capacity should account for the KPI result being an average,
i.e. the peak throughput will be greater than the average.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.2.
Average Uplink RT Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_UL_RT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(M801C8 + M801C9) / [SUM(PERIOD_DURATION) 60000000]
80 SUM(OUTPUT_TRAF_BYTES_TC_CONV + OUTPUT_TRAF_BYTES_TC_STREAM) /
[SUM(PERIOD_DURATION) 60000000]
Units: Mbps
KPI Description
This KPI quantifies the average uplink Iu-PS throughput for the conversational and streaming traffic classes.
The M801C8 and M801C9 counters are recorded on a per GTPU basis. The result must be aggregated across
the set of GTPU within each RNC to generate the RNC results. The multiplying factor of 80 is included
because the counters have units of 10 bytes. The KPI result represents the throughput of the Iu-PS payload. It
excludes the overheads generated by the GTP and transport network protocol stack layers. These overheads
should be included when comparing the Iu-PS throughput with the actual physical capacity of the Iu-PS, i.e.
when evaluating whether or not the interface is approaching congestion. The GTP-U/UDP/IP/AAL5/ATM
overhead is typically 16 % when assuming a payload of 1420 bytes.
Means to improve
quantity of PS traffic is small. A low result may also reflect the type of services being offered, i.e. PS
conversational and streaming services may not be offered.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.3.
Average Uplink NRT Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_UL_NRT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(OUTPUT_TRAF_BYTES_TC_INTERAC + OUTPUT_TRAF_BYTES_TC_BACKGR) /
Units: Mbps
KPI Description
This KPI quantifies the average uplink Iu-PS throughput for the interactive and background traffic classes.
The M801C10 and M801C11 counters are recorded on a per GTPU basis. The result must be aggregated
across the set of GTPU within each RNC to generate the RNC results. The multiplying factor of 80 is included
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.4.
Average Downlink Total Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_DL_TOT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(M801C0) / [SUM(PERIOD_DURATION) 60000000]
80 SUM(INPUT_BYTES_TOTAL_UDP) / [SUM(PERIOD_DURATION) 60000000]
Units: Mbps
KPI Description
This KPI quantifies the average downlink Iu-PS throughput. The M801C0 counter is recorded on a per GTPU
basis. The result must be aggregated across the set of GTPU within each RNC to generate the RNC results.
The multiplying factor of 80 is included because the M801C6 counter has units of 10 bytes. The KPI result
represents the throughput of the Iu-PS payload. It excludes the overheads generated by the GTP and transport
network protocol stack layers. These overheads should be included when comparing the Iu-PS throughput
with the actual physical capacity of the Iu-PS, i.e. when evaluating whether or not the interface is approaching
congestion. The GTP-U/UDP/IP/AAL5/ATM overhead is typically 16 % when assuming a payload of 1420
bytes.
Means to improve
quantity of PS traffic is small. If the result from this KPI (with the GTP-U/UDP/IP/AAL5/ATM overhead
added) approaches the capacity of the Iu-PS then it may be necessary to trigger a capacity upgrade. The
comparison between the KPI result and the Iu-PS capacity should account for the KPI result being an average,
i.e. the peak throughput will be greater than the average.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.5.
Average Downlink RT Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_DL_RT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(INPUT_TRAF_BYTES_TC_CONV + INPUT_TRAF_BYTES_TC_STREAM) /
Units: Mbps
KPI Description
This KPI quantifies the average downlink Iu-PS throughput for the conversational and streaming traffic
classes. The M801C2 and M801C3 counters are recorded on a per GTPU basis. The result must be aggregated
across the set of GTPU within each RNC to generate the RNC results. The multiplying factor of 80 is included
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.6.
Average Downlink NRT Iu-PS Throughput
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AV_DL_NRT_IUPS_THRU
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
80 SUM(INPUT_TRAF_BYTES_TC_INTERAC + INPUT_TRAF_BYTES_TC_BACKGR) /
Units: Mbps
KPI Description
This KPI quantifies the average downlink Iu-PS throughput for the interactive and background traffic classes.
The M801C4 and M801C5 counters are recorded on a per GTPU basis. The result must be aggregated across
the set of GTPU within each RNC to generate the RNC results. The multiplying factor of 80 is included
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.7.
Iu-PS Error Indications
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

IUPS_ERR_IND
None
RAS06
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
SUM(M801C15 + M801C16)
SUM(ERROR_INDICATIONS_RECEIVED + ERROR_INDICATIONS_SENT)
Units: Error Indications
Notes: None.
KPI Description
This KPI quantifies the sum of the GTP error indications generated by the RNC and SGSN. These error
indications are signalled as GTP: Error Indication messages.
Means to improve
The result from this KPI should be zero or close to zero. If the result becomes relatively large then the
performance of the Iu-PS interface should be investigated. The individual counters should be studied to
identify whether the RNC or SGSN is generating the majority of the error indications.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.8.
Average Number of GTP Tunnels
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
Average Number of GTP Tunnels

AV_GTP_TNL
None
RAS06
Low
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
AVERAGE(M801C18))
AVERAGE(AVERAGE_NBR_OF_GTP_TUNNELS)
Units: Tunnels
Separate aggregation across objects necessary: Yes, SUM M801C18 across GTPU prior to taking average.
Notes: None.
KPI Description
This KPI quantifies the average number of GTP tunnels between the RNC and SGSN. The M801C18 counter
is summed across all GTPU within the RNC prior to averaging over time. The average number of GTP tunnels
represents the average number of PS RAB. This KPI result could be combined with the average Iu-PS
throughput results to determine the average throughput per connection.
Means to improve
quantity of PS traffic is small.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
6.10.9.
Maximum Number of GTP Tunnels
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_GTP_TNL
None
RAS06
Medium
Scope
Time Resolution
Target
RNC
1 hour
None
KPI Expression
MAX(M801C19)
MAX(MAX_NBR_OF_GTP_TUNNELS)
Units: Tunnels
Separate aggregation across objects necessary: Yes, SUM M801C19 across GTPU prior to taking maximum.
Notes: None.
KPI Description
This KPI quantifies the maximum number of GTP tunnels between the RNC and SGSN. The M801C19
counter is summed across all GTPU within the RNC prior to taking the maximum over time. This generates
a result which is likely to be greater than the actual maximum because it is unlikely that all GTPU peak in
activity simultaneously. The maximum number of GTP tunnels represents the maximum number of PS RAB.
Means to improve
quantity of PS traffic is small.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
7.
Computing Unit Measurements

7.1.
Availability Performance Measurement (608/260H)
Counters within the Availability Performance Measurement table focus upon collecting data regarding
restarts of computer units and process families in IPA2800. They also collect state changes of computer
units. It is possible to calculate the time that a unit has been out of service.
The set of counters belonging to this measurement table is presented below.
Counter
Number
M608C0
M608C1
M608C2
M608C3
M608C4
M608C5
Counter Name
UNIT_RESTARTS
ADMIN_RESTARTS
DUPLEX_RESTARTS
DUPLEX_DISCONNECT_TIME
DISCONNECT_TIME
FAMILY_RESTARTS
7.2.
Unit Load Measurement (592/250H)
Counters within the Unit Load Measurement table focus upon collecting information regarding the processor
load of a computer unit. The average and peak loads of both the DMX and Chorus computer units are
recorded. The time of the peak load is also recorded.
Counter
Number
M592C0
M592C1
M592C2
M592C3
Version : Draft A
In Confidence
Counter Name
AVERAGE_LOAD
PEAK_LOAD
PEAK_LOAD_DATE
PEAK_LOAD_TIME
Date: 31/03/09
In Confidence
O2
7.2.1.
RNC Computer Unit Average Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

COMP_AV_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
Computer Unit
1 hour
< 70 %
KPI Expression
M592C0
AVERAGE_LOAD
Units: %
Notes: None
KPI Description
This KPI quantifies the average load of a specific computer unit within the RNC. The computer unit can be
OMU (2), MXU (268), NIU (301), NIP1 (325), NIS1 (326), NIS1P (271), RSMU (327), RRMU (328), ICSU
(329), GTPU (330), SFU (337), A2SU (1484), DMCU (1488), A2SP (324), DMPG (331). It is suggested that
the load of at least the ICSU, MXU, RSMU, GTPU, DMCU and A2SU are monitored.
Means to improve
A high average load indicates the requirement for a hardware upgrade. Alternatively there may be some scope
to re-distribute the traffic if neighbouring RNC are relatively unloaded. This KPI should be studied in
combination with the RNC Computer Unit Maximum Load.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
7.2.2.
RNC Computer Unit Maximum Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

COMP_MAX_LOAD
None
RAS05
Medium
Scope
Time Resolution
Target
Computer Unit
1 hour
< 90 %
KPI Expression
M592C1
PEAK_LOAD
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum load of a specific computer unit within the RNC. The computer unit can be
OMU (2), MXU (268), NIU (301), NIP1 (325), NIS1 (326), NIS1P (271), RSMU (327), RRMU (328), ICSU
(329), GTPU (330), SFU (337), A2SU (1484), DMCU (1488), A2SP (324), DMPG (331). It is suggested that
the load of at least the ICSU, MXU, RSMU, GTPU, DMCU and A2SU are monitored.
Means to improve
to re-distribute the traffic if neighbouring RNC are relatively unloaded. This KPI should be studied in
combination with the RNC Computer Unit Average Load.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
7.3.
WAC Overload Control Measurement (594/252H)
Counters within the Window Access Control (WAC) Overload Control Measurement table focus upon the
performance of the WAC which is used to limit the number of simultaneous AAL2 or RRC resource
reservations inside the RNC. The counters indicate whether the WAC rejects the establishment of new radio
or transport layer connections. The WAC is used only when the drift RNC receives an AAL2 establishment
request (ERQ) from the serving RNC.
The object of the measurement is a WAC gate type which is identified by its unit type, unit index and WAC
gate type.
Counter
Number
M594C0
M594C1
Version : Draft A
In Confidence
Counter Name
WAC_GATE_REQ_TOTAL
WAC_GATE_REQ_TOTAL_REJ
Date: 31/03/09
In Confidence
O2
7.3.1.
RNC ICSU WAC Gate Success Rate
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

ICSU_WAC_SUCC_RATE
None
RAS05
Medium
Scope
Time Resolution
Target
WAC Gate
1 hour
> 99.9 %
KPI Expression
100 % M594C1 / M594C0
100 % WAC_GATE_REQ_TOTAL_REJ / WAC_GATE_REQ_TOTAL
Units: %
Notes: None
KPI Description
Window Access Control (WAC) is used to limit the number of simultaneous AAL2 and RRC reservations for
an RNC. Limiting the number of reservations helps the RNC to protect existing connections during periods of
overload. This KPI quantifies the success rate of WAC gate requests, i.e. the percentage of reservation
requests which are accepted. The KPI can be generated for both the AAL2 and RRC objects. The AAL2
object is only applicable to the Iur.
Means to improve
to re-distribute the traffic if neighbouring RNC are relatively unloaded..
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

8.
Physical Layer Measurements

8.1.
IMA Logical Interface Measurement (514/202H)
Counters within the Inverse Multiplexing for ATM (IMA) Logical Interface Measurement table focus upon
quantifying the ability of a transmission path to provide the agreed quality between the near and far ends of
an IMA interface. The counters provide both link-specific and group-specific results, i.e. some counters are
generated per physical link whereas others are generated per IMA group. Counters M514C0 and M514C1
are group specific whereas all other counters are link specific.
The object of the measurement is an IMA group that is identified by its IMA group identity.
The set of counters belonging to this measurement table is presented below. With the exception of the groupspecific counters, these counters are grouped according to the link number
Counter
Number
M514C0
M514C1
M514C2
M514C3
M514C4
M514C5
M514C6
M514C7
M514C8
M514C9
M514C10
M514C11
M514C12
M514C13
M514C14
M514C15
M514C16
M514C17
M514C18
M514C19
M514C20
M514C21
M514C22
M514C23
M514C24
M514C25
M514C26
M514C27
M514C28
M514C29
M514C30
M514C31
M514C32
M514C33
M514C34
M514C35
M514C36
Counter Name
GR_UAS_IMA
GR_FC
UNIT_INDEX1
IV_IMA1
SES_IMA1
SES_IMA_FE1
UAS_IMA1
UAS_IMA_FE1
TX_UUS_IMA1
RX_UUS_IMA1
TX_UUS_IMA_FE1
RX_UUS_IMA_FE1
TX_FC1
RX_FC1
UNIT_INDEX2
IV_IMA2
SES_IMA2
SES_IMA_FE2
UAS_IMA2
UAS_IMA_FE2
TX_UUS_IMA2
RX_UUS_IMA2
TX_UUS_IMA_FE2
RX_UUS_IMA_FE2
TX_FC2
RX_FC2
UNIT_INDEX3
IV_IMA3
SES_IMA3
SES_IMA_FE3
UAS_IMA3
UAS_IMA_FE3
TX_UUS_IMA3
RX_UUS_IMA3
TX_UUS_IMA_FE3
RX_UUS_IMA_FE3
TX_FC3
Version : Draft A
In Confidence
Counter
Number
M514C50
M514C51
M514C52
M514C53
M514C54
M514C55
M514C56
M514C57
M514C58
M514C59
M514C60
M514C61
M514C62
M514C63
M514C64
M514C65
M514C66
M514C67
M514C68
M514C69
M514C70
M514C71
M514C72
M514C73
M514C74
M514C75
M514C76
M514C77
M514C78
M514C79
M514C80
M514C81
M514C82
M514C83
M514C84
M514C85
M514C86
Counter Name
UNIT_INDEX5
IV_IMA5
SES_IMA5
SES_IMA_FE5
UAS_IMA5
UAS_IMA_FE5
TX_UUS_IMA5
RX_UUS_IMA5
TX_UUS_IMA_FE5
RX_UUS_IMA_FE5
TX_FC5
RX_FC5
UNIT_INDEX6
IV_IMA6
SES_IMA6
SES_IMA_FE6
UAS_IMA6
UAS_IMA_FE6
TX_UUS_IMA6
RX_UUS_IMA6
TX_UUS_IMA_FE6
RX_UUS_IMA_FE6
TX_FC6
RX_FC6
UNIT_INDEX7
IV_IMA7
SES_IMA7
SES_IMA_FE7
UAS_IMA7
UAS_IMA_FE7
TX_UUS_IMA7
RX_UUS_IMA7
TX_UUS_IMA_FE7
RX_UUS_IMA_FE7
TX_FC7
RX_FC7
UNIT_INDEX8
Date: 31/03/09
In Confidence
O2


M514C37
M514C38
M514C39
M514C40
M514C41
M514C42
M514C43
M514C44
M514C45
M514C46
M514C47
M514C48
M514C49
RX_FC3
UNIT_INDEX4
IV_IMA4
SES_IMA4
SES_IMA_FE4
UAS_IMA4
UAS_IMA_FE4
TX_UUS_IMA4
RX_UUS_IMA4
TX_UUS_IMA_FE4
RX_UUS_IMA_FE4
TX_FC4
RX_FC4
M514C87
M514C88
M514C89
M514C90
M514C91
M514C92
M514C93
M514C94
M514C95
M514C96
M514C97
IV_IMA8
SES_IMA8
SES_IMA_FE8
UAS_IMA8
UAS_IMA_FE8
TX_UUS_IMA8
RX_UUS_IMA8
TX_UUS_IMA_FE8
RX_UUS_IMA_FE8
TX_FC8
RX_FC8
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

8.2.
STM-1 Interface Measurement (513/201H)
Counters within the STM-1 Interface Measurement table focus upon quantifying the ability of different
levels of SDH connection to provide agreed quality at the speed of STM-1 per SDH exchange terminal
(SET). The measurement provides information about the amount of errored background blocks (EBB),
amount of errored seconds (ES), amount of severely errored seconds (SES) and amount of unavailable
seconds (UAS). The measurement counters are collected from the SDH termination equipment on physical
interface (SET).
The object of the measurement is an SDH exchange terminal (SET) that is identified by SET and its index.
There are also counters for SDH paths terminated to a certain SDH exchange terminal. If VC-4 mapping is
used, the STM-1 interface contains one path. The counters of PATH1 are updated and others are left to zero.
If VC-3 mapping is used, the STM-1 interface contains three paths and all path counters are updated.
Some of the measurement counters are for the whole interface and some are defined by path. If VC-4
mapping is used, the STM-1 interface contains one path. The counters of PATH1 are updated and others are
left to zero. If VC-3 mapping is used, the STM-1 interface contains three paths and all path counters are
updated.
Counter
Number
M513C0
M513C1
M513C2
M513C3
M513C4
M513C5
M513C6
M513C7
M513C8
M513C9
M513C10
M513C11
M513C12
M513C13
M513C14
M513C15
M513C16
M513C17
M513C18
M513C19
M513C20
Counter Name
REG_BBE
REG_ES
REG_SES
REG_UAS
MUX_UAS
NE_MUX_BBE
NE_MUX_ES
NE_MUX_SES
NE_PATH1_UAS
NE_PATH1_BBE
NE_PATH1_ES
NE_PATH1_SES
NE_PATH2_UAS
NE_PATH2_BBE
NE_PATH2_ES
Counter
Number
M513C21
M513C22
M513C23
M513C24
M513C25
M513C26
M513C27
M513C28
M513C29
M513C30
M513C31
M513C32
M513C33
M513C34
M513C35
M513C36
M513C37
M513C38
M513C39
M513C40
M513C41
Counter Name
NE_PATH2_SES
NE_PATH3_UAS
NE_PATH3_BBE
NE_PATH3_ES
NE_PATH3_SES
FE_MUX_UAS
FE_MUX_BBE
FE_MUX_ES
FE_MUX_SES
FE_PATH1_UAS
FE_PATH1_BBE
FE_PATH1_ES
FE_PATH1_SES
FE_PATH2_UAS
FE_PATH2_BBE
FE_PATH2_ES
FE_PATH2_SES
FE_PATH3_UAS
FE_PATH3_BBE
FE_PATH3_ES
FE_PATH3_SES
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

8.3.
SONET/SDH Protection Group Measurement (516/204H)
Counters within the SONET/SDH Protection Group Measurement table monitor the use of protection groups
configured for SONET or SDH transmission sections.
The object of the measurement is an SDH exchange terminal (SET) that is identified by SET and its index.
Counter
Number
M516C0
M516C1
Counter Name
PROT_GR_PSC
PROT_GR_PSD
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.
DSP Resource Measurements

9.1.
DSP Service Statistics Measurement (609/261H)
The DSP Service Statistics measurement provides information on the resource allocation for each DSP
service type. This measurement can be used, for example to evaluate the number of simultaneous HSDPA
users on the RNC. The set of counters belonging to this table is shown below.
Counter Number
M609C0
M609C1
M609C2
M609C3
M609C4
Counter Name
DSP_SERVICE_CURR_RES_ALLOC
DSP_SERVICE_PEAK_RES_ALLOC
DSP_SERVICE_SUCC_RES_ALLOC
DSP_SERVICE_FAIL_RES_ALLOC
DSP_SERVICE_FAIL_RES_MODIFY
The object of the measurement is one of the DSP services presented in the table below.
Counter Number
AMR
CCH
HSCCH
ALLHSDPA
HSDPA_NR
HSDPA_RT
HS_16_H
HS_16_L
HS_64_H
HS_64_L
HS_128_H
HS_128_L
HS_384_H
HS_384_L
HSPASWI
ALLHSUPA
HSUPA_NR
HSUPA_RT
IPIUAMR
IPIURTCS
NRTPSR99
RTCSDATA
RTHSDPA
RTHSPASW
RTPSR99
SL
Counter Name
Real time speech service
Common channel service
HSDPA common channel service
Sum of all HSDPA services. Includes both HSDPA NRT and HSDPA RT. HSUPA call does
not update counters for this object even if it uses HSDPA in downlink
HSDPA NRT service. HSUPA call does not update counters for this object even if it uses
HSDPA in downlink
HSDPA RT service. HSUPA call does not update counters for this object even if it uses HSDPA
in downlink
HSDPA 16 kbps uplink return channel, high HS-DSCH peak rate
HSDPA 16 kbps uplink return channel, low HS-DSCH peak rate
HSUPA and HSDPA service used temporarily during channel type switching. Includes both
NRT and RT
Sum of all HSUPA services. Includes both HSUPA NRT and HSUPA RT
HSUPA NRT service
HSUPA RT service
IP based Iu interface real time speech service
IP based Iu interface real time circuit switched data service
Rel99 non real time packet switched data service. Does not include HSDPA uplink return
channel
Real time circuit switched data service
HSDPA real time packet switched data service. HSUPA call does not update counters for this
object even if it uses HSDPA in downlink
Real-time HSUPA and HSDPA service used temporarily during channel type switching
Rel99 real time packed switched data service. Does not include HSDPA uplink return channel
Signalling link service
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.1.1.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

PK_DSP_SERV_ALLOC
None
RU10
Medium
Scope
Time Resolution
Target
Service Type
1 hour
None
KPI Expression
MAX(M609C1)
MAX(DSP_SERVICE_PEAK_RES_ALLOC)
Units: resource allocations
Notes: None
KPI Description
This KPI quantifies the peak number of resources allocated for a specific DSP service type.
Means to improve
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

9.1.2.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

DSP_SERV_ALLOC_SUCC
None
RU10
Medium
Scope
Time Resolution
Target
Service Type
1 hour
None
KPI Expression
100 % SUM(M609C2) / SUM(M609C2 + M609C3)
100 % SUM(DSP_SERVICE_SUCC_RES_ALLOC) / SUM(DSP_SERVICE_SUCC_RES_ALLOC +
DSP_SERVICE_FAIL_RES_ALLOC)
Units: %
Notes: None
KPI Description
This KPI quantifies the percentage of service allocation attempts which are successful.
Means to improve
This KPI can be used for troubleshooting as well as within the capacity upgrade process.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.1.3.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

DSP_SERV_MOD_FAIL
None
RU10
Medium
Scope
Time Resolution
Target
Service Type
1 hour
None
KPI Expression
SUM(M609C4)
SUM(DSP_SERVICE_FAIL_RES_MODIFY)
Units: failures
Notes: None
KPI Description
This KPI quantifies the number of service modification failures.
Means to improve
This KPI can be used for troubleshooting as well as within the capacity upgrade process.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.2.
DSP State Changes Measurement (612/264H)
The DSP State Changes measurement records the number of essential DSP restarts caused by the system or
the operator. The measurement counts DSP internal state changes from WO-RE to TE, or from WO-EX to
TE. Note that the DSP internal states (WO-RE, WO-EX and TE) are not equal to the external states (WO,
BL, TE and SE). The measurement can be used, for example to identify faulty DSP. The object of the
measurement is a DMPG. The counters belonging to the DSP State Changes table are shown below.
Counter Number
M612C0
M612C1
Version : Draft A
In Confidence
Counter Name
RESTART_SYS
RESTART_USER
Date: 31/03/09
In Confidence
O2
9.2.1.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

DMPG_AUTO_RES
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
SUM(M612C0)
SUM(RESTART_SYS)
Units: resets
Notes: None
KPI Description
This counter records the number of times that a DSP is re-started by the system.
Means to improve
This KPI is intended for trouble-shooting purposes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.2.2.
Manual Resets
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
DMPG Manual Resets

DMPG_MAN_RES
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
SUM(M612C1)
SUM(RESTART_USER)
Units: resets
Notes: None
KPI Description
This counter records the number of times that a DSP is re-started manually.
Means to improve
This KPI is intended for trouble-shooting purposes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.3.
DSP Resource Utilization Measurement (615/267H)
The DSP Resource Utilisation measurement provides statistical information on successful and failed
resource allocations. It also provides information regarding the availability of resources. The results can be
used to monitor the service volume trends, to study faults and to plan the hardware configuration. The object
of the measurement is a DSP service pool that is identified by its service pool name. The set of counters
associated with this counter table is presented in the table below.
Counter Number
M615C0
M615C1
M615C2
M615C3
M615C4
M615C5
M615C6
M615C7
M615C8
Version : Draft A
In Confidence
Counter Name
AVAILABLE_CAP_ON_NE
LOWEST_CAP_ON_NE
CURR_RES_ALLOC_ON_NE
PEAK_RES_ALLOC_ON_NE
SUCC_RES_ALLOC_ON_NE
FAIL_ALLOC_DSP_ON_NE
FAIL_ALLOC_PPC_ON_NE
FAIL_MODIFY_ON_NE
SER_POOL_OVERFLOW_ON_NE
Date: 31/03/09
In Confidence
O2

9.3.1.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

SRV_POOL_ALLOC_SUCC
None
RU10
High
Scope
Time Resolution
Target
DSP Service Pool

1 hour
None
KPI Expression
100 % SUM(M615C4) / SUM(M615C4 + M615C5 + M615C6)
100 % SUM(SUCC_RES_ALLOC_ON_NE) / SUM(SUCC_RES_ALLOC_ON_NE +
FAIL_ALLOC_DSP_ON_NE + FAIL_ALLOC_PPC_ON_NE)
Units: %
Notes: None
KPI Description
This KPI quantifies the success rate of DSP service pool allocations within the RNC.
Means to improve
This KPI can be used to monitor the utilisation of RNC resources. It can be used to trigger the adjustment of
the RNC pool sizes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.3.2.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AVE_POOL_UTIL
None
RU10
Medium
Scope
Time Resolution
Target
DSP Service Pool

1 hour
None
KPI Expression
100 % - AVERAGE(M615C0)
100 % - AVERAGE(AVAILABLE_CAP_ON_NE)
Units: %
Notes: None
KPI Description
This KPI quantifies the average utilisation of DSP service pools within the RNC.
Means to improve
the RNC pool sizes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2

9.3.3.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

PK_POOL_UTIL
None
RU10
Medium
Scope
Time Resolution
Target
DSP Service Pool

1 hour
None
KPI Expression
100 % - MIN(M615C1)
100 % - MIN(LOWEST_CAP_ON_NE)
Units: %
Notes: None
KPI Description
This KPI quantifies the peak utilisation of DSP service pools within the RNC.
Means to improve
the RNC pool sizes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.3.4.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

POOL_MOD_FAILS
None
RU10
Medium
Scope
Time Resolution
Target
DSP Service Pool

1 hour
None
KPI Expression
SUM(M615C7)
SUM(FAIL_MODIFY_ON_NE)
Units: failures
Notes: None
KPI Description
This KPI quantifies the failure rate for DSP service pool modifications within the RNC.
Means to improve
the RNC pool sizes. It can also be used for troubleshooting purposes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.3.5.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

POOL_OVERFLOWS
None
RU10
Medium
Scope
Time Resolution
Target
DSP Service Pool

1 hour
None
KPI Expression
SUM(M615C8)
SUM(SER_POOL_OVERFLOW_ON_NE)
Units: overflows
Notes: None
KPI Description
This KPI quantifies the number of times a resource was allocated from a secondary pool instead of the
primary pool. This can mean that either the primary pool was full, or that it was more optimal from the
resource consumption point-of-view to allocate the resource from another pool.
Means to improve
the RNC pool sizes.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.
DSP Load Measurement (617/269H)
The DSP Load measurement provides information on DSP load such as memory utilisation, CPU load and
the number of active processes. This information can be used for example, to check the load balance of each
DMPG. It should be useful during troubleshooting activities. The object of the measurement is the DMPG,
and the set of counters is presented in the table below.
Counter Number
M617C0
M617C1
M617C2
M617C3
M617C4
M617C5
M617C6
M617C7
M617C8
M617C9
M617C10
M617C11
M617C12
M617C13
M617C14
M617C15
M617C16
M617C17
M617C18
M617C19
Version : Draft A
In Confidence
Counter Name
PROC_NUM_AVG
CPU_LOAD_AVG
MEM_USE_INTER_AVG
MEM_USE_EXTER_AVG
PROC_NUM_MAX
CPU_LOAD_MAX_PROC_NUM
MEM_USE_INTER_MAX_PROC_NUM
MEM_USE_EXTER_MAX_PROC_NUM
CPU_LOAD_MAX
PROC_NUM_MAX_CPU_LOAD
MEM_USE_INTER_MAX_CPU_LOAD
MEM_USE_EXTER_MAX_CPU_LOAD
MEM_USE_INTER_MAX
PROC_NUM_MAX_MEM_USE_INTER
CPU_LOAD_MAX_MEM_USE_INTER
MEM_USE_EXTER_MAX_MEM_USE_INT
MEM_USE_EXTER_MAX
PROC_NUM_MAX_MEM_USE_EXTER
CPU_LOAD_MAX_MEM_USE_EXTER
MEM_USE_INTER_MAX_MEM_USE_EXT
Date: 31/03/09
In Confidence
O2
9.4.1.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AVE_APPL_PROC
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
AVERAGE(M617C0)
AVERAGE(PROC_NUM_AVG)
Units: processes
Notes: None
KPI Description
This KPI quantifies the average number of application processes within a specific DMPG.
Means to improve
This KPI can be used for traffic monitoring purposes and for understanding how traffic is distributed across
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.2.
Average CPU Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
Average CPU Load

AVE_CPU_LOAD
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
AVERAGE(M617C1)
AVERAGE(CPU_LOAD_AVG)
Units: %
Notes: None
KPI Description
This KPI quantifies the average CPU load associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.3.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AVE_INT_MEM_UTIL
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
AVERAGE(M617C2)
AVERAGE(MEM_USE_INTER_AVG)
Units: %
Notes: None
KPI Description
This KPI quantifies the average internal memory utilisation associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.4.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

AVE_EXT_MEM_UTIL
None
RU10
Medium
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
AVERAGE(M617C3)
AVERAGE(MEM_USE_EXTER_AVG)
Units: %
Notes: None
KPI Description
This KPI quantifies the average external memory utilisation associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.5.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_APP_PROC
None
RU10
High
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
MAX(M617C4, M617C5, M617C6, M617C7)
AVERAGE(PROC_NUM_MAX, CPU_LOAD_MAX_PROC_NUM, MEM_USE_INTER_MAX_PROC_NUM,
MEM_USE_EXTER_MAX_PROC_NUM)
Units: processes
Notes: None
KPI Description
This KPI quantifies the maximum number of application processes within a specific DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.6.
Maximum CPU Load
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:
Maximum CPU Load

MAX_CPU_LOAD
None
RU10
High
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
MAX(M617C8, M617C9, M617C10, M617C11)
AVERAGE(CPU_LOAD_MAX, PROC_NUM_MAX_CPU_LOAD, MEM_USE_INTER_MAX_CPU_LOAD,
MEM_USE_EXTER_MAX_CPU_LOAD)
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum CPU load associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.7.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_INT_MEM_UTIL
None
RU10
High
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
MAX(M617C12, M617C13, M617C14, M617C15)
AVERAGE(MEM_USE_INTER_MAX, PROC_NUM_MAX_MEM_USE_INTER,
CPU_LOAD_MAX_MEM_USE_INTER, MEM_USE_EXTER_MAX_MEM_USE_INT)
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum internal memory utilisation associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
9.4.8.
KPI Name:
KPI Short Name:
NSN KPI Number:
IMPORTANCE:

MAX_EXT_MEM_UTIL
None
RU10
High
Scope
Time Resolution
Target
DMPG
1 hour
None
KPI Expression
MAX(M617C16, M617C17, M617C18, M617C19)
AVERAGE(MEM_USE_EXTER_MAX, PROC_NUM_MAX_MEM_USE_EXTER,
CPU_LOAD_MAX_MEM_USE_EXTER, MEM_USE_INTER_MAX_MEM_USE_EXT)
Units: %
Notes: None
KPI Description
This KPI quantifies the maximum external memory utilisation associated with a DMPG.
Means to improve
the set of DMPG.
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
10.
Conclusion
The complete set of RNC Transport and Hardware KPI have been categorised as Engineering KPI. This is in
contrast to Business KPI. Engineering KPI are applicable to the operations, radio design and radio network
planning groups. The set of KPI are presented in terms of their importance within Table 1.
Very High Importance
None
HSDPA Peak AAL2 CPS Delay
Average Number of GTP Tunnel
High Importance
Maximum CPU Load
Medium Importance
Manual Resets
Average CPU Load
Low Importance
Table 1 Summary of RNC Transport and Hardware KPI in terms of importance
Version : Draft A
In Confidence
Date: 31/03/09
In Confidence
O2
11.
[1]
[2]
[3]
References
'Definition of RNC Key Performance Indicators - Radio Network (RU10)', Chris Johnson, to
be written
'Definition of Node B Key Performance Indicators (RU10)', Chris Johnson, to be written
'RNC Counters - Transport and HW Part', Nokia Siemens Networks WCDMA RAN, Rel.
RU10 System Library, v.1, dn04143903, Issue 5-1
--- End of Document ---
Version : Draft A
In Confidence
Date: 31/03/09

O2RD - 09 - XX Definition of RNC KPI Transport & Hardware RU10 Draft A

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

O2RD - 09 - XX Definition of RNC KPI Transport & Hardware RU10 Draft A

Diunggah oleh

Hak Cipta:

Format Tersedia

In Confidence

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 1 of 114

Definition of RNC Key Performance

Chris Johnson (NSN)

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 2 of 114

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 3 of 114

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 4 of 114

The following KPI have been removed:

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 5 of 114

4. Transport Network Resource Measurements............................................................................26

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 6 of 114

5.3.1. Unsolicited SSCOP Errors.............................................................................................................47

6. ATM/IP Transport Measurements.............................................................................................48

7. Computing Unit Measurements..................................................................................................82

8. Physical Layer Measurements.....................................................................................................87

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 7 of 114

8.1. IMA Logical Interface Measurement (514/202H)................................................................................87

9. DSP Resource Measurements......................................................................................................91

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 8 of 114

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 9 of 114

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

RNC Resource Measurements

RNC Capacity Usage Measurement (802/322H)

RNC 196 & 450

RNC 196 & 450

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 11 of 114

Average RNC Speech Call Count

Average RNC Speech Call Count

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 12 of 114

Maximum RNC Speech Call Count

Maximum RNC Speech Call Count

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 13 of 114

RNC Speech Call Count > 70% of Licensed Capacity

RNC Speech Call Count > 70% of Licensed Capacity

'Do Once' Radio Design

Definition of RNC KPI - Transport and Hardware

Document Reference : O2RD/09/-Page : 14 of 114

RNC Speech Call Licensed Capacity