Sei sulla pagina 1di 112

WCDMA Performance Management

RBS 6402

DIRECTIONS FOR USE

21/1551-LZA 701 6012 Uen A


Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be


reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

Ericsson Ericsson is the trademark or registered trademark of


Telefonaktiebolaget LM Ericsson. All other product or
service names mentioned in this manual are trademarks
of their respective companies.

21/1551-LZA 701 6012 Uen A | 2016-12-20


Contents

Contents

1 Introduction 1
1.1 Intended Audience 1

2 Performance Management Overview 3


2.1 RBS 6402 Performance Management Overview 3
2.2 Start Performance Measurements Using OSS-RC 5
2.3 Start Performance Measurements Using CLI 23
2.4 Accessing the Result Output Period (ROP) Files 25

3 Counters, PIs, and KPIs 33


3.1 Counters 33
3.2 Performance Indicators (PI) 37
3.3 Key Performance Indicators (KPI) 37
3.4 Performance Management (PM) Categories: 37
3.5 Viewing Counter Details 38

4 RBS 6402 Counter and KPI details 47


4.1 Counters contained in each counter Class 47
4.2 KPI Descriptions and Equations 69

21/1551-LZA 701 6012 Uen A | 2016-12-20


WCDMA Performance Management

21/1551-LZA 701 6012 Uen A | 2016-12-20


Introduction

1 Introduction

This document describes the WCDMA Performance Management (PM) part of


the Operation and Maintenance (O&M) system for the Ericsson RBS 6402.

1.1 Intended Audience


This document is intended for system administrators and other users assigned
to operate and maintain the RBS 6402 WCDMA environment.

Personnel working on Ericsson products or systems must have training and


expertise required to perform their work correctly.

Note: System Operations and Maintenance is only to be performed by


authorized personnel.

1.1.1 Prerequisite Knowledge


The user of this document must have:

• A good understanding of the RBS 6402.

• A good understanding of RBS 6402 WCDMA RAN software. Refer to RBS


6402 WCDMA RAN Software, 1555-HSD 101 02.

• A good understanding of O&M of the Operations Support Systems Radio


and Core (OSS-RC) System. For a high-level overview of OSS-RC, refer
to Introduction to OSS-RC, 1555-AOM 901 110 and OSS-RC System
Administration, 1543-AOM 901 133.

• The necessary access and authorization to the OSS-RC and Network


Elements (NEs). For information on O&M security access, refer to
Security for O&M Node Access, 1551-CXA 110 3235, and Overall Security
Administration in OSS-RC, 3/1543-APR 901 911.

• A verified IP address for remote O&M access to the node. If there is no


remote O&M access, refer to Recovering a Node on Site, 58/1543-LZA
701 6004/1 (WCDMA).

21/1551-LZA 701 6012 Uen A | 2016-12-20 1


WCDMA Performance Management

2 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

2 Performance Management Overview

2.1 RBS 6402 Performance Management Overview


Performance Management (PM) is the evaluation of network behavior based on
performance data generated in the Network Elements (NEs).

PM ensures the most efficient use of the network, and includes the following
activities:

• Monitoring of key performance indicators

• Optimization of the network performance

• Identification of trends

• Troubleshooting the RBS

Monitoring the performance of the RBS 6402 and the WCDMA systems is a
crucial activity for reliable and efficient network operation. The PM functions
can provide detailed information about the network performance, which can be
used to ensure the most efficient network use.

Performance Management allows for:

• Detection of degraded network performance, enabling the operator to take


necessary action to preserve network quality.

• Troubleshooting the network and suggesting actions for network


improvement.

• Monitoring and optimizing the radio and transport network to improve


subscriber-perceived quality, or to use the installed resources better.

• Providing radio and transmission network planners with detailed information


needed for dimensioning of network expansion.

21/1551-LZA 701 6012 Uen A | 2016-12-20 3


WCDMA Performance Management

Figure 1 Performance Statistics

Key
A Performance statistics are captured in PM counters located in the RBS
6402.
There are various PM counter-types referred to as measurement
methods:
• Accumulative Counter
• Peg
• Scan
• Gauge
• Probability Density Function (PDF)
• Condensed PDF
B PM counters increment as the software in the RBS 6402 performs
various tasks and functions.
C A Network Management System (NMS), such as the Operations
Support System for Radio and Core (OSS-RC), is used to manage the
performance data measurements and to analyze the measurement
results.
D The Ericsson Network IQ (ENIQ) can be used for additional
measurements and further processing and analysis of performance
data. ENIQ is proven best-in-class in terms of uploading, storing,
and accessing extensive volumes of data generated within
telecommunication networks.
ENIQ together with OSS-RC is called Next-generation ENIQ and
OSS-RC (NEO). It is an Ericsson solution on Business Intelligence.
ENIQ reports use an ENIQ server as a data warehouse and uses
Business Objects for the data query and presentation.

4 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

Figure 2 Managed Object Model (MOM)

Key
A In the Managed Object Model (MOM), the performance statistics
measurements are defined in Managed Object (MO) Pm.
Each measurement is represented by an instance of MO
MeasurementType.
The measurement types are grouped into PM groups (MO PmGroup).
B The starting and stopping of a performance statistics measurement is
made in the OSS-RC through a PmJob.
It is recommended to manage PM jobs using the Operations Support
System for Radio and Core (OSS-RC), as the OSS-RC can also stop
and delete PM jobs that are not created by the OSS-RC.
C In the MOM, a PM job is represented by an instance of MO PmJob.
D For each performance statistics measurement, the result is presented in
a statistic file at the end of every Result Out Period (ROP).
E The ROP files are stored at the RBS 6402 for 25 hours, or until the file
storage space is full. Before that, the ROP files are collected by the
OSS-RC for analysis and storage. The supported granularity period and
the ROP are 15 minutes.
The performance statistics ROP files are in XML format. By default ROP
files are not compressed. ROP files can be compressed as GZIP files
by setting PmJob.compressionType = 0.

Note: In order for the OSS-RC to retrieve the PM files created on the RBS
6402, both the RBS node and the OSS-RC must have the same
timezone provisioned.

2.2 Start Performance Measurements Using OSS-RC


Use this procedure to create and start a PmJob in the RBS 6402 using the
OSS-RC.

21/1551-LZA 701 6012 Uen A | 2016-12-20 5


WCDMA Performance Management

Figure 3 Starting a PmJob in the RBS 6402

The PmJob starts the data collection process to gather selected counters
and produce the Result Out Period (ROP) files. Data collection is initiated
by creating a Profile using the OSS-RC. The profile identifies the NEs (RBS
6402s) to be configured to collect the selected Objects (counters). The Profile
is then activated to start the data collection process in the RBS 6402s.

To access the OSS-RC and to start a PMJob in the RBS 6402, the user must
have the proper credentials (Username and Password).

1. Access the OSS-RC that is used to manage the RBS 6402.

2. Launch the Performance Management System (PMS) using the options


illustrated in the following graphic:

6 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

The splash screen displays showing the running version of the PMS:

The PMS window displays.

3. To create a profile, from the Profile menu, select Add profile....

21/1551-LZA 701 6012 Uen A | 2016-12-20 7


WCDMA Performance Management

The Add statistical subscription profile wizard. Step 1 of 5 window


displays.

4. Configure the following subscription profile details parameters as required:

Profile name Enter a name for the profile.

Comments Enter any optional comments about the profile.

Subscription types
From the drop-down menu, select a subscription type.
This adds the new profile to a specific tab in the PMS.

8 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

In this example, the new profile is called WCDMA_6402_counters. It is


added to the User defined statistical subscription profile tab in the PMS.

5. Click Next.

The Add statistics subscription profile wizard. Step 2 of 5 window


displays.

6. From the Managed Elements pull-down menu, select MSRBS_V1 and


from the Statistical Type pull-down menu, select Standard.

21/1551-LZA 701 6012 Uen A | 2016-12-20 9


WCDMA Performance Management

7. Click Next.

The Add statistics subscription profile wizard. Step 3 of 5 window


displays.

8. Click the network name to expand and view the RBS 6402s that exist in
the network and select the name of the RBS 6402 to be associated with
the profile.

To select multiple RBS 6402s, use ctrl or shift and click the names.

Note: Disconnected RBS 6402(s) are available in the list but the names
are dimmed. Do not select a disconnected RBS 6402.

In the following example, the RBS 6402 is in the RNC403 network and
is named otprb6301.

10 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

9. Click > (Select one button) to move the RBS 6402(s) from Available
MSRBS_V1(s) to Selected the MSRBS_V1(s).

10. Select one of the following PnP options:

No PnP Create a profile that is only applied to the selected RBS


6402(s).

Network PnP Create a profile that is applied to the selected RBS


6402(s) and is automatically applied to any new RBS
6402(s) added to the network.

SubNetwork PnP
Create a profile that is applied to the selected RBS
6402(s) and is automatically applied to any new RBS
6402(s) added to the subnetwork.

Note: If there are no subnetworks configured on the


network, the SubNetwork PnP option is not
available.

11. Click Next.

The Add statistics subscription profile wizard. Step 4 of 5 window


displays. In this window, the Available counters are grouped in class
folders which correlate to MO class designation of the counters. The class
is used to locate counters in the RBS 6402, Counter List, and the MOM.

21/1551-LZA 701 6012 Uen A | 2016-12-20 11


WCDMA Performance Management

12. Click the class folder name to expand and view the counters that exist
in the class.

12 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

13. Click to select the name of the counter to be collected with the profile.

To select multiple counters, use ctrl or shift and click the names of the
counters.

To select all counters in a class folder, click the class folder name. To
select multiple folders, use ctrl or shift and click the names of the folders.

21/1551-LZA 701 6012 Uen A | 2016-12-20 13


WCDMA Performance Management

14. Move the desired counters or class folders from Available counters to
Selected counter(s) .

Click > (Select one button) to move the counters or class folders from
Available counters to Selected counter(s) or drag and drop the counters
or folders in Selected counter(s).

Note: When >> (Select all button) is clicked, regardless of what is


highlighted, ALL the class folders are moved from the Available
counters to Selected counter(s).

15. Click Next.

The Add statistics subscription profile wizard. Step 5 of 5 window


displays.

16. Select one of the following schedule types:

14 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

Scheduled Produces an ROP file every 15 minutes (Profile


Granularity). The number of ROP files produced is
determined by the Duration. After the specified duration
is completed, the profile is automatically deactivated.

Continuous Produces an ROP file every 15 minutes (Profile


Granularity). This profile runs until it is manually
deactivated by the user.

Periodic Produces an ROP file every 15 minutes (Profile


Granularity). This schedule type provides the user with
full flexibility on when the measurements are taken.

17. In the Periodic dates and time setup, set the Start date for the
measurements. Select the Month and Year, and click the date in the
calendar. A check displays on the selected date.

Example Start date of Monday, September 5, 2016:

21/1551-LZA 701 6012 Uen A | 2016-12-20 15


WCDMA Performance Management

18. If the End date for the measurements is different than the Start date,
set the End date. Select the Month and Year and click the date in the
calendar. A check also displays on the selected date.

Example End date of Friday, September 30, 2016:

19. Select any dates between the Start date and the End date that require
measurements.

To repeat the measurements on specific days, select the days of the week
that require measurements. The choices are: Sun, Mon, Tue, Wed, Thu,
Fri, and Sat.

Example repeat measurements on Mon, Wed, and Fri:

16 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

20. Set the Start time for the measurements. Select the Hour and the Minute
or click Use current time.

Example Start time of 12:30:

21. Set the Duration for ROP file creation. From the drop-down menus, select
the Days, Hours, and Minutes.

ROP files are produced every 15 minutes, and the ROP count is
automatically populated based on the Duration.

If the Duration is set to 0 Days, 0 Hours, and 15 Minutes, only 1 ROP file is
produced for each date selected in the Periodic dates and time setup.

If the Duration is set to 0 Days, 1 Hour, and 0 Minutes, 4 ROP files are
produced for each date selected in the Periodic dates and time setup.

22. Verify the projected times and dates.

The Summary tab displays the projected times of the measurements and
includes the projected Total ROPs (Day count x ROP count):

21/1551-LZA 701 6012 Uen A | 2016-12-20 17


WCDMA Performance Management

The Dates tab displays all the projected dates for the measurements:

18 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

23. Click Finish.

The profile is created.

The User defined statistics profiles tab is updated with the new entry
and is in Inactive state.

21/1551-LZA 701 6012 Uen A | 2016-12-20 19


WCDMA Performance Management

24. Activate the profile. Select the new profile row, right-click, and select
Resume profile... from the drop-down menu.

25. At the confirmation prompt, click Yes.

20 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

The profile is applied to all the RBS 6402s selected in the profile. The
PmJob starts in the selected RBS 6402s and the performance measurement
is activated.

This process automatically:

• Creates an instance of MO Pm.

• Creates an instance of MO PmGroup.

• Creates an instance of MO MeasurementType for each selected


counter.

• Groups the MeasurementType instances into MO PmGroup.

• Creates an instance of MO PmJob.

26. Verify that the profile is now active.

27. To deactivate a profile, select Suspend profile... from the drop-down


menu.

21/1551-LZA 701 6012 Uen A | 2016-12-20 21


WCDMA Performance Management

28. To view the profile details, highlight the profile, right-click, and select Profile
details... Or double-click the profile on the profile display page.

Example of Profile Details:

22 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

2.3 Start Performance Measurements Using CLI

2.3.1 RBS 6402 Access Credentials and Roles

To access the RBS 6402 and to start a PMJob using the CLI, the user must
have the following:

• The proper credentials (Username and Password)

• One of the following roles defined in the RBS 6402:

0 SystemAdministrator

0 SystemSecurityAdministrator

21/1551-LZA 701 6012 Uen A | 2016-12-20 23


WCDMA Performance Management

Note: To verify the roles in the RBS 6402, issue the following commands:

• get . roleName

• get rule ruledata

• lpr role=N (where N = the role number obtained from the


get . roleName command)

2.3.2 Create, Start, and Stop PM Job

To create and start a PmJob:

1. Create an instance of MO PmJob with a unique PmJob Id.

By default, the created PmJob is in the requested job state ACTIVE, and
creates a ROP file in compressed format every 15th minute.

2. Under MO PmJob, create an instance of the MeasurementReader MO for


each MeasureementType or PmGroup MO to include in the PM job.

The NE sets attribute currentJobState on MO PmJob to ACTIVE, and starts


the measurements.

ROP files are created, starting from the first complete ROP.

2.3.3 Stop PM Job

To stop an active PmJob:

1. Set the attribute requestedJobState on MO PmJob to STOPPED. The NE


sets attribute currentJobState on MO PmJob to STOPPED, and stops the
measurements. If the measurement is stopped during a ROP, no ROP
file is created for that ROP.

2. To start a stopped PmJob again, set the attribute requestedJobState to


ACTIVE.

2.3.4 Delete User-Defined PM Job

Before deleting a user-defined PmJob, set attribute requestedJobState to


STOPPED.

To delete a user-defined PmJob, delete the instance of MO PmJob. When the


instance of MO PmJob is deleted, its children MOs are also deleted.

2.3.5 List PM Job


PM jobs can be listed by using the show command in Ericsson CLI and EMCLI.

It is possible to display the PM jobs associated with an MO instance. To do this,


in the Ericsson CLI navigate to the MO instance and issue the show command.

24 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

For more information on the show command, refer to Ericsson CLI.

2.4 Accessing the Result Output Period (ROP) Files


For each performance monitoring that has the Admin state Active, OSS-RC
attempts to collect a Report Output Period (ROP) file.

These ROP files are stored in a corresponding Performance Management


Directory.

The Statistics ROP files are in XML format.

When the file is collected, it is renamed by the PMS (Performance Management


Subsystem) and stored in the predefined OSS-RC subfolder. The PMS initiates
collection of the data files and the FTP Manager collects the files.

Finally, the file availability notifications are sent to any subscribed consumer.
Any consumer can subscribe to these notifications and fetch the collected file
from the OSS-RC node. These notifications contain the URL to the target files.

Note: In order for the OSS-RC to retrieve the PM files created on the RBS
6402, both the RBS node and the OSS-RC must have the same
timezone provisioned.

2.4.1 ROP Directory Description


At the top level that is underneath the /var/opt/ericsson/nms_umts_pms_seg/se
gment1/ folder, there are six separate subfolders named XML, UETR, CTR,
GPEH, CELLTRACE, and UETRACE. Each subfolder contains the applicable
topology substructure as follows:

• Subnetwork/MeContext/ underneath XML/, UETR/, CTR/ and GPEH/ for


RNC, where Subnetwork is the RNS SubNetwork.

• Subnetwork/MeContext/ underneath XML/ and GPEH/ for RBS, where


Subnetwork is the RNS SubNetwork.

• Subnetwork/MeContext/ underneath XML/ for pRBS (WRAN), where


Subnetwork is the RNS SubNetwork.

• Subnetwork=NODE/MeContext/ or Subnetwork=ONRM_ROOT_MO_R/
MeContext/ underneath CELLTRACE/ and XML/ for ERBSs, where
Subnetwork is the RNS SubNetwork if the ERBS exists in an RNS or the
Root MO if the ERBS node exists directly under the Root MO.

• <TRACE REF>>/SubNetwork/MeContext/ underneath UETRACE for


ERBSs, where

0 Subnetwork is the RNS SubNetwork if the ERBS exists in an RNS.


Subnetwork is the Root MO if the ERBS node exists directly under
the Root MO.

21/1551-LZA 701 6012 Uen A | 2016-12-20 25


WCDMA Performance Management

0 The <TRACE REF> is the trace reference which the PMS user
assigned to the UE Trace profile on profile creation.

• Subnetwork=ONRM_ROOT_MO_R/MeContext/ underneath XML/ for RXIs

Each of these subfolders contains only files applicable to that measurement


type and NE instance combination. This reduces the number of files to be
searched for different customer applications.

The following Directory Example shows the possible folders for one RNC, one
RBS, one pRBS (WRAN), and one RXI.

Directory Example:

dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01/
dataroot/UETR/SubNetwork=RNC01/MeContext=RNC01/
dataroot/CTR/SubNetwork=RNC01/MeContext=RNC01/
dataroot/XML/SubNetwork=RNC01/MeContext=RNC01/
dataroot/XML/SubNetwork=RNC01/MeContext=RNC01RBS01/
dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01RBS01/
dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01PICORBS01/
dataroot/XML/MeContext=RNC01RXI01
dataroot/XML/SubNetwork=ONRM_ROOT_MO_R/MeContext=ERBS01/
dataroot/XML/SubNetwork=LTERNS/MeContext=ERBS01/
dataroot/CELLTRACE/SubNetwork=ONRM_ROOT_MO_R/MeContext=ERBS01/
dataroot/CELLTRACE/SubNetwork=LTERNS/MeContext=ERBS01/
dataroot/UETRACE/272F011001000000/SubNetwork=ONRM_ROOT_MO_R/
MeContext=ERBS01/
dataroot/UETRACE/272F011001000000/SubNetwork=LTERNS/
MeContext=ERBS01/

Variable dataroot is the top level (segment1) folder, typically


/var/opt/ericsson/nms_umts_pms_seg/segment1.

2.4.2 ROP File Retention

Result Output Period (ROP) files are stored in the OSS Server based on
their retention period. PMS deletes files that are older than the retention
period every fifteen minutes based on the reporting period of the ROP files.
This retention period is set in the Parameter Editor (PED) by parameters
recordingFileStorageDays, oneMinrecordingFileStorageHours
and recordingFileStorageHours for recording files and by parameter
statisticsFileStorageDays for statistic files.

The parameter recordingFileStorageDays has a default value of zero


days.

The parameter recordingFileStorageHours has a default value of six


hours.

26 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

The parameter oneMinrecordingFileStorageHours has a default value


of four hours.

The parameter statisticsFileStorageDays has a default value of three


days.

PMS can also delete files based on the storage space currently available for the
next ROP file. If PMS determines that there is insufficient space available for
the next ROP file, then the oldest recording files are deleted. This takes place
regardless of the recording files retention period.

This functionality can be turned on and off with a customer-specific parameter


fileDeletionRule in the Parameter Editor (PED).

2.4.3 ROP File Format

The PM data file is in XML format for statistical measurements and binary
format for CTR, UETR, GPEH, CELLTRACE and UETRACE measurements.
CTR and UETR files are binary files with ASN.1 coded content and GPEH files
are bit-packed. CELLTRACE files have internal binary format with the External
Message contents optionally being ASN.1 coded.

XML file names have the suffix .xml and compressed binary file names have
the suffix .bin.gz

2.4.4 ROP File Naming


PM data files are renamed by PMS before the file availability notification is sent
according to the file naming conventions shown in the following table:

Table 1 ROP File Naming Convention


File Type File Naming Convention
Stats: A<Date>.<StartTime>-<EndTime>_<UniqueFDNFromONRM>_statsfile.xml
A<Date>.<StartTime>-<EndTime>_<ShortNodeId>_<ShortScannerId>_<Acc
CTR:
essCell>_ctrfile.bin.gz
A<Date>.<StartTime>-<EndTime>_<ShortNodeId>_<ShortScannerId>_<IMSI
UETR:
>_uetrfile.bin.gz
A<Date>.<StartTime>-<EndTime>_<ShortNodeId>_rnc_gpehfile_Mp<n>.bin.gz
GPEH: for RNCs and A<Date>.<StartTime>-<EndTime>_<ShortNodeId>_rbs_gpehfil
e_Mp<n>.bin.gz

21/1551-LZA 701 6012 Uen A | 2016-12-20 27


WCDMA Performance Management

Table 1 ROP File Naming Convention


A<Date>.<StartTime>-<EndTime>_<UniqueFDNFromSegment>_celltracefile
_<RC>.bin.gz for node before L12B
CELLTRACE:
A<Date>.<StartTime>-<EndTime>_<UniqueFDNFromSegment>_celltracefile_D
UL_<n>_<RC>.bin.gz for L12B nodes and higher.
A<Date>.<StartTime>-<EndTime>_<UniqueFDNFromSegment>_<TraceRef>_<I
UETRACE:
MSI/IMEI/IMEI(SV)>_uetracefile.bin.gz

File naming fields are defined as follows:

A Denotes the single NE and single granularity. It


represents the Type field for statistical files according
to the 3GPP TS 32.401 Rel 4 for statistical files. This
has no specific significance for CTR, UETR, GPEH,
or CELLTRACE files but it is adopted for consistency
reasons.

<Date> Date when the file is generated, in the format


YYYYMMDD.

28 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

<StartTime> Indicates the time when the granularity period starts. If


the PED parameter FileNameIncludesTimeZone
is set to On, the Starttime field is of the form
HHMMshhmm, where:

• HH is the two-digit hour of the day (local time),


based on 24-hour clock (00 - 23).

• MM is the two-digit minute of the hour (local time).


The possible values are 00, 05, 10, 15, 20, 25, 30,
35, 40, 45, 50, and 55.

• s is the sign of the local time differential from UTC


(+ or -). In case the time differential to UTC is 0, the
sign can be arbitrarily set to "+" or "-".

• hh is the two-digit number of hours of the local time


differential from UTC (00-23).

• mm is the two-digit number of minutes of the local


time differential from UTC (00-59).

If the PED parameter FileNameIncludesTimeZone


is set to Off, the Starttime field is of the form HHMM,
where:

• HH is the two-digit hour of the day (local time),


based on 24-hour clock (00 - 23).

• MM is the two-digit minute of the hour (local time).


The possible values are 00, 05, 10, 15, 20, 25, 30,
35, 40, 45, 50, and 55.

<EndTime> Indicates the time when the granularity period ends. The
structure is similar to the Starttime field, however,
the allowed values for the minute of the hour are 05, 10,
15, 20, 25, 30, 35, 40, 45, 50, 55, and 00.

<UniqueFDNFromONRM>
The NE Full Distinguished Name as configured by
the OSS-RC Configuration Management application
in the ONRM CS. This is given in the format
Subnetwork=<ROOT_MO_FROM_ONRM_CS>,
Subnetwork=<PARENTRNS>,MeContext=<NODEN
AME> where the ROOT_MO_FROM_ONRM_CS is
the Root MO stored in the ONRM CS. For example,
ONRM_ROOT_MO.

If the node does not exist under an RNS, the format


is Subnetwork=<ROOT_MO_FROM_ONRM_CS>,Me
Context=<NODENAME>.

21/1551-LZA 701 6012 Uen A | 2016-12-20 29


WCDMA Performance Management

<UniqueFDNFromSegment>
The NE Full Distinguished Name as configured by
the OSS-RC Configuration Management application
in the Segment CS. This is given in the format
Subnetwork=<ROOT_MO_FROM_SEGMENT_CS>,
Subnetwork=<PARENTRNS>,MeContext=<NODENAM
E> where the ROOT_MO_FROM_ SEGMENT _CS is
the Root MO stored in the SEGMENT CS . For example,
ONRM_ROOT_MO_R

If the node does not exist under an RNS, then the


format is Subnetwork=<ROOT_MO_FROM_SEGMENT
_CS>,MeContext=<NODENAME>

<ShortNodeId> The NE Full Distinguished Name as configured by the


OSS-RC Configuration Management application. This is
given in the format Subnetwork=<PARENTRNS>,MeCo
ntext=<NODENAME> for CTR, UETR and GPEH files.

<ShortScannerId>
The integer used to identify the measurement on the
NE. This is unique to each NE and not network-wide.

<IMSI> IMSI number of the User Equipment (UE) that UETR


measurement file refers to.

<IMSI/IMEI/IMEI(SV)>
The IMSI/IMEI/IMEI(SV) number of the User Equipment
(UE) that the UE TRACE measurement file refers to.
If the OSS cannot map an IMSI/IMEI/IMEI(SV) to the
Trace Reference, the IMSI/IMEI/IMEI(SV) is unknown.

<Access_Cell> Full Distinguished Name of the UTRAN cell that the CTR
measurement file refers, as configured by the OSS-RC
Configuration Management application. This is given in
the format Subnetwork=, Subnetwork=,MeContext=,
ManagedElement=, RncFunction=,UTRANCell=.

<n> Number (starting from 0) indicating the file number of a


GPEH file. This is required as GPEH files are split by
Main Processors on an RNC node. Mp0 is the main
file. Mp0 does not contain recordings but provides
the filter information and links to the GPEH subfiles.
Subfiles naming follows the format Mp1, Mp2 ...
Mpn where the index matches the position in the list of
subfile locations given in the link record of the main file.

When this field is used for RBS files, the value is always
n=1.

30 21/1551-LZA 701 6012 Uen A | 2016-12-20


Performance Management Overview

<UniqueId> NE Full Distinguished Name as configured by the


OSS-RC Configuration Management application.

For example:

A20160909.1215+0000-1230+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml
A20160909.1230+0000-1245+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml
A20160909.1245+0000-1300+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml

This example lists three ROP files created for network element “otenb2016”:

• A20160909 – indicates that all three ROP files were created on Sept 9th,
2016.

• The <StartTime> of the first ROP file is “1215+0000”. The file was started
at 12:15 (UTC). The “+0000” indicates that there is no time differential
from UTC.

• The <EndTime> of the first ROP file is 12:30 (UTC). This is the standard 15
minute collection period for ROP files on the RBS 6402 .

• Each of the three ROP files contains 15 minutes of performance data.

2.4.5 ROP File Notifications


All PMS-generated notifications are sent using the CIF Notification Service
which is part of the OSS-RC platform. It is used by PMS to notify consumers
that the measurement data file is available for collection, or that this file has
been missed at a collection attempt. For this purpose, the PMS application
issues the notification NotifyPerformanceDataAvailable.

21/1551-LZA 701 6012 Uen A | 2016-12-20 31


WCDMA Performance Management

32 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

3 Counters, PIs, and KPIs

3.1 Counters

Figure 4 Key Performance Indicators

The RBS 6402 software contains many counters also referred to as


measurement methods.

21/1551-LZA 701 6012 Uen A | 2016-12-20 33


WCDMA Performance Management

Figure 5 Performance Counter Classes

Each of the folders contains one or more classes of counters.

Performance statistics are measured using the following measurement


methods:

Accumulative Counter
An Accumulative Counter (ACC) measurement
increases by the value of a sample. It indicates the total
sum of all sample values taken during a certain time.

Peg A Peg measurement is a special case of an accumulator


measurement. It increases at each occurrence of a
specific activity. It can increase by 1 or other value, for
example, to accumulate the number of bits transferred
because of a specific activity.

34 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

Scan A Scan measurement is a special case of a Peg


measurement. It increases by 1 each time the
corresponding CC increases, and indicates how many
samples of a certain quantity are taken. The average
value of all samples is calculated by dividing the result
of an accumulator measurement by the result of a scan
measurement.

Gauge A Gauge measurement increases or decreases


depending on the activity in the system. It is used when
the measured data varies during the measurement
period.

PDF A Probability Density Function (PDF) measurement is


an array of elements that can be used in different ways.

The PDF measurement format can be used to


represent a histogram where each element of the array
(bin) represents a range measurement. The range
measurement increases every time a sample of a single
variable is measured to lie within the range for that
range measurement. For example, if a variable is used
to measure processor load use, with sampled values
split into four ranges as follows:

• Range1 = [0..25]%

• Range2 = [26..50]%

• Range3 = [51..75]%

• Range4 = [76..100]%

When a sampled value is read every third minute over


a 15-minute period with values [23, 88, 66, 52, 43], the
four range measurements are reported as:

• Range1 = 1

• Range2 = 1

• Range3 = 2

• Range4 = 1

The PDF measurement format can also be used as a


generic array of separate measurement, where each
measurement measures a different variable.

21/1551-LZA 701 6012 Uen A | 2016-12-20 35


WCDMA Performance Management

Compressed PDF
In a compressed PDF measurement, only the non-zero
values are reported. It is used where only a small part
of the range is used.

Example: The Quality of Service Class Indicator


(QCI) PM measurements are arrays of many PM
measurements with no relationship between the
QCI values. A QCI PM measurement measures the
number of establishment attempts per QCI made by
the E-UTRAN Radio Access Bearers (E-RAB). Each
element of the array is an ACC measurement that
counts the number of E-RAB establishment attempts
for a specific QCI value. If the measurement result for
a QCI [256] is as follows:

• [0] = 0

• [1] = 72

• [2] = 0

• [3] = 0

• [4] = 0

• [5] = 0

• [6] = 44

• [7] = 0

• [8] = 0

• [9] = 0

• [255] = 0

The result in compressed PDF format is: 2, 1, 72, 6, 44,


where the first number is the number of reported bins
followed by bin and bin values in pairs. In this example,
two QCI values are reported during the ROP: QCI1 had
72 attempts and QCI6 had 44 attempts.

The used measurement method is presented together with the measurement


result.

In the MOM, the measurement methods are defined by different attributes


under MO MeasurementType.

The ACC, Peg, and Scan measurement methods have the same settings in
attributes aggregation and collectionMethod: CC, and SUM.

36 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

For the Gauge measurement method, attribute collectionMethod is set to


GAUGE. If the measurement method used is PDF, attribute multiplicity is larger
than 1. Measurement type Compressed PDF has the attribute isCompressed
set to true.

3.2 Performance Indicators (PI)


Performance Measurement (PM) counters, also referred to as Performance
Indicators (PIs), are a subset of the counters contained in the RBS 6402. PIs
are a special set of measurements that relate specifically to the performance of
the system, such as throughput or drop-rate.

3.3 Key Performance Indicators (KPI)


The KPI represents the end-user perception of a network on a macro level.
KPI statistics are typically used to benchmark networks against each other
and to detect problem areas. KPIs are calculated using PM counters. The
reliability, granularity, and accuracy of the data are critical, and the data is
collected continuously.

Key Performance Indicators (KPI) Example:

The KPI HSDPA BLER is defined as the High Speed Downlink Packet Access
Block Error Rate.

Figure 6 Example KPI Formula

The KPI is defined as a percentage of the number of Negative


Acknowledgements (NACKs) received divided by the total number of ACKs
plus NACKs received.

Ideally, the number of NACKs is equal to 0, making the HSDPA BLER KPI
equal to 0%.

3.4 Performance Management (PM) Categories:


KPIs, used for Performance Management, provide data on the access network
performance regarding the following categories:

21/1551-LZA 701 6012 Uen A | 2016-12-20 37


WCDMA Performance Management

Accessibility The ability of a service to be obtained, within specified


tolerances and other given conditions, when requested
by the user.

Retainability The ability of a service, once obtained, to continue to


be provided under given conditions for a requested
duration.

Integrity The degree to which a service, once obtained, is


provided without excessive impairments.

Mobility The performance of all types of handover.

System Utilization
Hardware use, licenses, traffic and load, congestion,
transport network, and admission.

Availability The ability of an item to be in a state to perform a


required function at a given instant of time or at any
instant of time within a given time interval. This assumes
that any required external resources are provided.

3.5 Viewing Counter Details

3.5.1 Viewing Counter Details Using the Counter List


For a detailed list of all the WCDA counters used in the RBS 6402, refer to the
WCDMA RAN Counter List, 2/00651-LZN 701 6003 .

3.5.2 Viewing Counter Details Using MOM


Detailed information about each PM counter can also be found in the Managed
Object Model (MOM) RBS in the WCDMA RBS 6402 Radio Node CPI library.

1. Open the most current WCDMA RBS 6402 Radio Node 16 library.

2. Navigate to Operation and Maintenance > MOM Object Management >


Managed Object Model (MOM) RBS > Instances Folder.

38 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

Two types of files display: Instances and Overviews. The RBS 6402
MSRBS_V1 standard instances that contain the counters are displayed.

3. Select a file that contains the counters to be viewed.

The following example is an Overview file. The file shows the PMGroup
and the counters that are contained in that PMGroup.

The PMGroup contain the counters that are identified by the


MeasurementType label.

Each MeasurementType line links to the counter detail. The counter details
are located in the Instance file identified at the top of the Overview file.

21/1551-LZA 701 6012 Uen A | 2016-12-20 39


WCDMA Performance Management

4. Select the MeasurementType to be viewed.

Example of pmNoAllowedEul counter:

40 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

3.5.3 Viewing Counter Details Using the OSS Common Explorer

1. Open the OSS Common Explorer and navigate to the NE to be viewed.

2. Right-click on the NE and select Launch > Advanced MO Scripting.

21/1551-LZA 701 6012 Uen A | 2016-12-20 41


WCDMA Performance Management

The AMOS OSS Framework for MoShell displays.

42 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

3. Enter the following command to log on to the NE:

lt all

4. At the prompt, enter the Username and Node Password.

21/1551-LZA 701 6012 Uen A | 2016-12-20 43


WCDMA Performance Management

5. Use the get command to view the counter details.

To display details for all the counters:

get

Note: This is a large list and takes time to display all the details.

To display details for a specific counter:

get <counter_name>

Example command and system response to display the details of the


pmNoAllowedEul counter:

get pmNoAllowedEul

44 21/1551-LZA 701 6012 Uen A | 2016-12-20


Counters, PIs, and KPIs

In this example:

• PmGroup = EDchResourcesPmGroup

• The measurement instance of MO MeasurementType =


pmNoAllowedEul. This is the name of the counter.

6. Use the pst command to list all the PmJobs configured in the NE.

pst

Example command and system response:

21/1551-LZA 701 6012 Uen A | 2016-12-20 45


WCDMA Performance Management

In this example, there is only one PmJob configured. The PmJob is:

• Currently ACTIVE

• A Statistics Measurement PmJob (MEASJOB)

• Set to run continuously (Continuous_y = ROP file generated every 15


minutes) (900 seconds / 60 = 15 minutes)

• Named: WCDMA_6402_counters

• User defined PmJob = 25000224_USERDEF

7. Use the pgets command to list all performance measurement counters


configured in a specified PmJob.

pgets <PmJob identifier>

Where:

The PmJob identifier parameter is any portion of the PmJob that the
command can uniquely identify. For example: pgets WCDMA_6402,
pgets WCDMA_6402_counters, and pgets MEASJOB all return the
correct information.

46 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

4 RBS 6402 Counter and KPI details

4.1 Counters contained in each counter Class


There are many counters that are defined in MOM and that appear in the RBS
6402. The counters describing in the following sections are only those counters
that are used in the 16A RBS 6402 release.

4.1.1 CommonChannelResources Counter Class


Table 2 CommonChannelResources Counters
Counter Name Counter Description
The number of successfully received transport blocks during a
pmPrachSuccReceivedBlocks
granularity period.
The number of unsuccessfully received transport blocks during a
pmPrachUnsuccReceivedBlocks
granularity period.

4.1.2 EDchResources Counter Class


Table 3 EDchResources Counters
Counter Name Counter Description
The measured uplink Uu load of a cell for users configured with only
Release 99 DCH on the uplink. Load contributions from DPDCH,
DPCCH and HS-DPCCH are included. The sampled value is a load
pmLDch factor and is unitless with range 0..1, where 0 means no load and 1
is maximum possible load. PDF ranges: [0]: Number of samples
in range [0..0.02] [1]: Number of samples in range [0.02..0.04] â ¦
[49]: Number of samples in range [0.98..1]
The measured uplink Uu load of a cell that is caused by users
configured with an E-DCH. Load contributions from E-DPDCH (both
scheduled and not scheduled), E-DPCCH, DPCCH, and DPDCH (if
one is configured) are included.. The sampled value is a load factor
and is unitless with range 0..1, where 0 means no load and 1 is
pmLEDchTot maximum possible load. Also HS-DPCCH is currently included in
load because PHY doesn't support measurement without it. But the
support will be required later. PDF ranges: [0]: Number of samples
in range [0..0.02] [1]: Number of samples in range [0.02..0.04] ....
[48]: Number of samples in range [0.96..0.98] [49]: Number of
samples in range [0.98..1].

21/1551-LZA 701 6012 Uen A | 2016-12-20 47


WCDMA Performance Management

Table 3 EDchResources Counters


The total uplink Uu load headroom for a cell available to users
configured with an E-DCH. The system aims to secure that total
load from E-DCH users for this cell (see pmLEDchTot for a
description) does not exceed the total uplink Uu load headroom.
pmLMaxEDch The sampled value is a load factor and is unitless with range 0..1,
where 0 means no load and 1 is maximum possible load. PDF
ranges: [0]: Number of samples in range [0..0.02] [1]: Number of
samples in range [0.02..0.04]...[48]: Number of samples in range
[0.96..0.98] [49]: Number of samples in range [0.98..1]
Sum of used 10 ms frames (TTI) that receive E-DCH data in a cell
pmNoActive10msFramesEul during an ROP for all E-DCH users, excluding frames that are not
decoded due to lack of hardware.
Counter for the total amount of 10 ms intervals in a cell in which the
pmNoActive10msIntervalsEulTt transmission of one or more E-DCH frames has been detected,
i10 excluding frames that are not decoded due to lack of hardware to
decode the frame.
Sum of used 2 ms frames (TTI) that receive E-DCH data in a cell
pmNoActive2msFramesEul for all E-DCH users, excluding frames that are not decoded due to
lack of hardware.
Counter for the total amount of 2 ms intervals in a cell in which the
transmission of one or more E-DCH frames has been detected,
pmNoActive2msIntervalsEul
excluding frames that are not decoded due to lack of hardware to
decode the frame.
Counter for the total amount of 2 ms intervals in a cell in which the
transmission of one or more E-DCH frames has been detected,
pmNoActive2msIntervalsEulTti2
excluding frames that are not decoded due to lack of hardware to
decode the frame.
Counter used to measure number of times that no E-DCH traffic is
pmNoAllowedEul
allowed owing to uplink interference.
This counter is used to show the used thermal noise level value
in the Rise over Thermal (RoT) measurement. PDF ranges: [0]:
Number of samples less than -114 dBm [1]:Number of samples
pmNoiseFloor
in range [-114..-113]dBm...[54]:Number of samples in range
[-61..-60]dBm [55]:Number of samples greater or equal than -60
dBm.
Counter per cell for the power-controlled noise rise caused by the
intra-cell interference that affects the Uu load. OwnUULoad_dB=
10 * log10 ( 1 / ( 1 - LDCH(t) - LD-EDCH(t) - LHS-DPCCH(t)) )
LDCH is the load for all DCH radio links in a cell and also including
HS-DPCCH load of HSDPA with associated UL DCH users.
pmOwnUuLoad
LD-EDCH is the load for all D-EDCH users in a cell. LHS-DPCCH
is the load for all E-DCH users having HS-DPCCH in a cell. PDF
ranges: [0]:Number of samples in range [0..0.2]dB [1]:Number of
samples in range [0.2..0.4]dB...[49]:Number of samples in range
[9.8..10]dB [50]:Number of samples greater or equal than 10 dB.

48 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 3 EDchResources Counters


Counter for the total amount of acked data received in kbits after
pmSumAckedBitsCellEulTti10 HARQ process on MAC-e level for all 10 ms TTI users in a cell.
Note that k = 1000.
Counter for the total amount of acked data received in kbits after
pmSumAckedBitsCellEulTti2 HARQ process on MAC-e level for 2 ms TTI users. Note that k
= 1000.
Counter for the total amount of nacked data received in kbits after
HARQ process on MAC-e level for all 10 ms TTI users in a cell,
pmSumNackedBitsCellEulTti10
excluding data that is NACKed due to lack of hardware to decode
the frame. Note that k = 1000
Counter for the total amount of nacked data received in kbits after
HARQ process on MAC-e level for 2 ms TTI users, excluding data
pmSumNackedBitsCellEulTti2
that is NACKed due to lack of hardware to decode the frame. Note
that k = 1000.
Counter per cell for the total Rise over Thermal (RoT) (including all
uplink traffic and external interference) that affects the coverage.
pmTotalRotCoverage PDF ranges: [0]:Number of samples less than 0.5 dB [1]:Number
of samples in range [0.5..1.0]dB...[49]:Number of samples in range
[24.5..25]dB [50]:Number of samples greater or equal than 25 dB.
Total granted Uu rate. The counter is the total sum of scheduled
granted rates over all serving D-EDCH users in cell. PDF ranges:
[0]:Number of samples in range [0..100]kbits/s [1]:Number of
pmTotRateGrantedEul
samples in range [100..200] kbits/s...[59]:Number of samples in
range [5900..6000] kbits/s [60]:Number of samples greater or equal
than 6000 kbits/s.

4.1.3 EthernetPort Counter Class

Table 4 EthernetPort Counters


Counter Name Counter Description
The number of broadcast packets delivered to a higher layer
ifHCInBroadcastPkts protocol. Packets counted by ifInDiscards are not included.
Standard reference: RFC 2863, section 6.
The number of multicast packets delivered to a higher layer
ifHCInMulticastPkts protocol. Packets counted by ifInDiscards are not included.
Standard reference: RFC 2863, section 6.
The total number of octets (3GPP, Wi-Fi, OAM) received on the
ifHCInOctets interface including Ethernet header, VLAN tag, payload and Frame
Check Sequence. Standard reference: RFC 2863, section 6.
The number of unicast packets delivered to a higher layer protocol.
ifHCInUcastPkts Packets counted by ifInDiscards are not included. Standard
reference: RFC 2863, section 6.

21/1551-LZA 701 6012 Uen A | 2016-12-20 49


WCDMA Performance Management

Table 4 EthernetPort Counters


The number of broadcast packets that higher level protocols
ifHCOutBroadcastPkts requested be transmitted. Packets counted by ifOutDiscards are
included. Standard reference: RFC 2863, section 6.
The number of multicast packets that higher level protocols
ifHCOutMulticastPkts requested be transmitted. Packets counted by ifOutDiscards are
included. Standard reference: RFC 2863, section 6.
The total number of octets (3GPP, Wi-Fi, OAM) transmitted on the
ifHCOutOctets interface including Ethernet header, VLAN tag, payload and Frame
Check Sequence. Standard reference: RFC 2863, section 6.
The number of unicast packets that higher level protocols requested
ifHCOutUcastPkts be transmitted. Packets counted by ifOutDiscards are included.
Standard reference: RFC 2863, section 6.
The number of input packets which were chosen to be discarded
even though no errors had been detected to prevent their being
ifInDiscards
deliverable to a higher layer protocol. Standard reference: RFC
2863, section 6.
The number of packets received on the interface that contained
ifInErrors errors preventing them from being deliverable to a higher layer
protocol. Standard reference: RFC 2863, section 6.
The number of packets received on the interface that were
ifInUnknownProtos discarded because of an unknown or unsupported protocol.
Standard reference: RFC 2863, section 6.
The number of tagged packets received on the interface that were
ifInUnknownTags
discarded because they belong to an unknown VLAN.
The number of output packets which were chosen to be discarded
ifOutDiscards even though no errors had been detected to prevent their being
transmitted. Standard reference: RFC 2863, section 6.
The number of output packets that could not be transmitted
ifOutErrors
because of errors. Standard reference: RFC 2863, section 6.

4.1.4 HsDschResources Counter Class

Table 5 HsDschResources Counters


Counter Name Counter Description
Number of occasions when ACK is received, not counting
pmAckReceived repetitions of ACK transmissions. The counter reflects the cell
perspective.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi00
Queues (PQs) for Scheduling Priority Indicator (SPI) 00.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi01
Queues (PQs) for Scheduling Priority Indicator (SPI) 01.

50 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi02
Queues (PQs) for Scheduling Priority Indicator (SPI) 02.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi03
Queues (PQs) for Scheduling Priority Indicator (SPI) 03.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi04
Queues (PQs) for Scheduling Priority Indicator (SPI) 04.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi05
Queues (PQs) for Scheduling Priority Indicator (SPI) 05.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi06
Queues (PQs) for Scheduling Priority Indicator (SPI) 06.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi07
Queues (PQs) for Scheduling Priority Indicator (SPI) 07.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi08
Queues (PQs) for Scheduling Priority Indicator (SPI) 08.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi09
Queues (PQs) for Scheduling Priority Indicator (SPI) 09.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi10
Queues (PQs) for Scheduling Priority Indicator (SPI) 10.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi11
Queues (PQs) for Scheduling Priority Indicator (SPI) 11.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi12
Queues (PQs) for Scheduling Priority Indicator (SPI) 12.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi13
Queues (PQs) for Scheduling Priority Indicator (SPI) 13.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi14
Queues (PQs) for Scheduling Priority Indicator (SPI) 14.
Number of discards performed by the AQM feature for all Priority
pmAqmBasedDiscardSpi15
Queues (PQs) for Scheduling Priority Indicator (SPI) 15.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi00
Priority Indicator (SPI) 00.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi01
Priority Indicator (SPI) 01.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi02
Priority Indicator (SPI) 02.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi03
Priority Indicator (SPI) 03.

21/1551-LZA 701 6012 Uen A | 2016-12-20 51


WCDMA Performance Management

Table 5 HsDschResources Counters


Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi04
Priority Indicator (SPI) 04.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi05
Priority Indicator (SPI) 05.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi06
Priority Indicator (SPI) 06.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi07
Priority Indicator (SPI) 07.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi08
Priority Indicator (SPI) 08.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi09
Priority Indicator (SPI) 09.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi10
Priority Indicator (SPI) 10.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi11
Priority Indicator (SPI) 11.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi12
Priority Indicator (SPI) 12.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi13
Priority Indicator (SPI) 13.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi14
Priority Indicator (SPI) 14.
Number of Iub discards on all Priority Queues (PQs), that
pmIubBasedDiscardFrameLoss
experienced the frame loss due to Iub congestion, for Scheduling
UserSpi15
Priority Indicator (SPI) 15.
Number of occasions when NACK is received, not counting
pmNackReceived repetitions of NACK transmissions. The counter reflects the cell
perspective.
Number of active 2 ms intervals. The counter reflects the cell
pmNoActiveSubFrames
perspective.

52 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi00 for scheduling priority class 00. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi01 for scheduling priority class 01. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi02 for scheduling priority class 02. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi03 for scheduling priority class 03. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi04 for scheduling priority class 04. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi05 for scheduling priority class 05. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi06 for scheduling priority class 06. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi07 for scheduling priority class 07. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi08 for scheduling priority class 08. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi09 for scheduling priority class 09. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi10 for scheduling priority class 10. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi11 for scheduling priority class 11. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi12 for scheduling priority class 12. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi13 for scheduling priority class 13. The counter reflects the cell
perspective.

21/1551-LZA 701 6012 Uen A | 2016-12-20 53


WCDMA Performance Management

Table 5 HsDschResources Counters


Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi14 for scheduling priority class 14. The counter reflects the cell
perspective.
Measurement to observe the sum of active 2 ms subframes
pmNoActiveSubFramesSpi15 for scheduling priority class 15. The counter reflects the cell
perspective.
The number of subframes in which no data is transmitted although
there is user data to be sent in the validated PQ. This user data is
either waiting for first transmission, or data waiting for transmission
pmNoInactiveRequiredSubFram
(NACK is received or no ACK/NACK). The counter reflects the cell
es
perspective The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 00 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi00 class 00, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 01 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi01 class 01, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 02 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi02 class 02, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.

54 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


The number of subframes in which no data with scheduling
priority class 03 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi03 class 03, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 04 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi04 class 04, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 05 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi05 class 05, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 06 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi06 class 06, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.

21/1551-LZA 701 6012 Uen A | 2016-12-20 55


WCDMA Performance Management

Table 5 HsDschResources Counters


The number of subframes in which no data with scheduling
priority class 07 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi07 class 07, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 08 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi08 class 08, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 09 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi09 class 09, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 10 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi10 class 10, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.

56 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


The number of subframes in which no data with scheduling
priority class 11 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi11 class 11, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 12 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi12 class 12, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 13 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi13 class 13, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The number of subframes in which no data with scheduling
priority class 14 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi14 class 14, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.

21/1551-LZA 701 6012 Uen A | 2016-12-20 57


WCDMA Performance Management

Table 5 HsDschResources Counters


The number of subframes in which no data with scheduling
priority class 15 is transmitted although there is user data to be
sent in the validated PQ. This user data is either waiting for first
transmission, or data waiting for transmission (NACK is received
pmNoInactiveRequiredSubFram or no ACK/NACK). If a subframe goes without scheduling priority
esSpi15 class 15, i.e. just carrying other scheduling priority classes or going
totally empty, then the counter is stepped. The counter reflects the
cell perspective.The counter is per cell and per subframe, meaning
increments with max 1 per subframe. A "subframe" is a 2 ms TTI
for HS-DSCH.
The UE reported CQI. Note that it is the true (unadjusted) CQI that
is counted. This counter is only relevant for UEs not using 64 QAM.
The counter reflects the cell perspective. PDF ranges: [0]:Number
pmReportedCqi
of reported CQI with value 0 [1]:Number of reported CQI with value
1 ... [30]:Number of reported CQI with value 30 [31]:Number of
reported CQI with invalid value.
The UE reported CQI received for a 64 QAM enabled HS-DSCH.
Note that it is the true (unadjusted) CQI that is counted for 64 QAM
enabled HS-DSCHs. PDF ranges: [0]:Number of reported CQI
pmReportedCqi64Qam
with value 0 [1]:Number of reported CQI with value 1...[30]:Number
of reported CQI with value 30 [31]:Number of reported CQI with
invalid value.
Number of samples in pmSumCapacityUsers (that is,
pmSamplesCapacityUsers pmSamplesCapacityUsers = pmSamplesCapacityUsers + 1,
whenever pmSumCapacityUsers is to be updated).
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi00 MAC-hs/ehs level per scheduling priority class 00. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi01 MAC-hs/ehs level per scheduling priority class 01. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi02 MAC-hs/ehs level per scheduling priority class 02. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi03 MAC-hs/ehs level per scheduling priority class 03. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi04 MAC-hs/ehs level per scheduling priority class 04. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi05 MAC-hs/ehs level per scheduling priority class 05. The counter
reflects the cell perspective.

58 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi06 MAC-hs/ehs level per scheduling priority class 06. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi07 MAC-hs/ehs level per scheduling priority class 07. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi08 MAC-hs/ehs level per scheduling priority class 08. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi09 MAC-hs/ehs level per scheduling priority class 09. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi10 MAC-hs/ehs level per scheduling priority class 10. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi11 MAC-hs/ehs level per scheduling priority class 11. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi12 MAC-hs/ehs level per scheduling priority class 12. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi13 MAC-hs/ehs level per scheduling priority class 13. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi14 MAC-hs/ehs level per scheduling priority class 14. The counter
reflects the cell perspective.
To observe the total amount of acknowledged data sent on
pmSumAckedBitsSpi15 MAC-hs/ehs level per scheduling priority class 15. The counter
reflects the cell perspective.
Aggregate of all sample values (measurement_value) recorded
pmSumCapacityUsers
users.
Number of user buffers with data in the buffer for each 2 ms
pmSumNonEmptyUserBuffers
subframe. The counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 00 with data in the buffer for each 2 ms subframe. The
pi00
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 01 with data in the buffer for each 2 ms subframe. The
pi01
counter reflects the cell perspective.

21/1551-LZA 701 6012 Uen A | 2016-12-20 59


WCDMA Performance Management

Table 5 HsDschResources Counters


Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 02 with data in the buffer for each 2 ms subframe. The
pi02
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 03 with data in the buffer for each 2 ms subframe. The
pi03
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 04 with data in the buffer for each 2 ms subframe. The
pi04
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 05 with data in the buffer for each 2 ms subframe. The
pi05
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 06 with data in the buffer for each 2 ms subframe. The
pi06
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 07 with data in the buffer for each 2 ms subframe. The
pi07
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 08 with data in the buffer for each 2 ms subframe. The
pi08
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 09 with data in the buffer for each 2 ms subframe. The
pi09
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 10 with data in the buffer for each 2 ms subframe. The
pi10
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 11 with data in the buffer for each 2 ms subframe. The
pi11
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 12 with data in the buffer for each 2 ms subframe. The
pi12
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 13 with data in the buffer for each 2 ms subframe. The
pi13
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 14 with data in the buffer for each 2 ms subframe. The
pi14
counter reflects the cell perspective.
Measurement to observe the number of user buffers for scheduling
pmSumNonEmptyUserBuffersS
priority class 15 with data in the buffer for each 2 ms subframe. The
pi15
counter reflects the cell perspective.

60 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi00 priority class 00 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi01 priority class 01 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi02 priority class 02 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi03 priority class 03 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi04 priority class 04 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi05 priority class 05 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi06 priority class 06 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi07 priority class 07 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi08 priority class 08 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi09 priority class 09 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi10 priority class 10 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi11 priority class 11 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi12 priority class 12 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi13 priority class 13 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.

21/1551-LZA 701 6012 Uen A | 2016-12-20 61


WCDMA Performance Management

Table 5 HsDschResources Counters


Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi14 priority class 14 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
Generic counter to observe the total number of users for scheduling
pmSumNoOfUsersSpi15 priority class 15 selected for each 2 ms subframe that is transmitted
in the cell. The counter reflects the PQ perspective.
The distribution of transmitted power for HS (HS traffic on
CELL_DCH). PDF ranges: [0]:Number of samples with values < 0
dBm or 'no transmission' [1]:Number of samples in range [0..0.5]dBm
pmSumOfHsUsedPwr
[2]:Number of samples in range [0.5..1]dBm...[101]:Number of
samples in range [50..50.5]dBm [102]: Number of samples greater
or equal than 50.5dBm.
Aggregate of the squares of the sample values (
measurement_value) in pmSumCapacityUsers, that is,
pmSumSqrCapacityUsers
pmSumSqrCapacityUsers = pmSumSqrCapacityUsers +
sqr(measurement_value).
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi00 MAC-hs/ehs level per scheduling priority class 00. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi01 MAC-hs/ehs level per scheduling priority class 01. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi02 MAC-hs/ehs level per scheduling priority class 02. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi03 MAC-hs/ehs level per scheduling priority class 03. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi04 MAC-hs/ehs level per scheduling priority class 04. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi05 MAC-hs/ehs level per scheduling priority class 05. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi06 MAC-hs/ehs level per scheduling priority class 06. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi07 MAC-hs/ehs level per scheduling priority class 07. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi08 MAC-hs/ehs level per scheduling priority class 08. The counter
reflects the cell perspective.

62 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 5 HsDschResources Counters


Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi09 MAC-hs/ehs level per scheduling priority class 09. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi10 MAC-hs/ehs level per scheduling priority class 10. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi11 MAC-hs/ehs level per scheduling priority class 11. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi12 MAC-hs/ehs level per scheduling priority class 12. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi13 MAC-hs/ehs level per scheduling priority class 13. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi14 MAC-hs/ehs level per scheduling priority class 14. The counter
reflects the cell perspective.
Measurement to observe the total amount of data sent on
pmSumTransmittedBitsSpi15 MAC-hs/ehs level per scheduling priority class 15. The counter
reflects the cell perspective.
Measurement to observe the distribution of transmitted carrier
power for all codes used for transmission of HSDPA channels
including HS-PDSCH, HS-SCCH, E-AGCH, E-RGCH and E-HICH,
pmTransmittedCarrierPowerWH as a percentage of the maximum power (indicated by the counter
s Carrier::pmTransmCarrierPowerWLimit). PDF ranges: [0]:Number
of sampled values in range [0..2]% [1]:Number of sampled
values in range [2..4]% [2]:Number of sampled values in range
[4..6]%...[49]:Number of sampled values in range [98..100]%.
The transmitted carrier power for all non high-speed codes in the
cell, as a percentage of the maximum power (indicated by the
pmTransmittedCarrierPowerWN counter Carrier::pmTransmittedCarrierPowerWLimit. PDF ranges:
onHs [0]:Number of sampled values in range [0..2]% [1]:Number of
sampled values in range [2..4]% [2]:Number of sampled values in
range [4..6]%...[49]:Number of sampled values in range [98..100]%.
The distribution of the HS-PDSCH code utilization, as the number
of HS-PDSCH codes used by the scheduler. PDF ranges[0]: 0
pmUsedHsPdschCodes codes [1]:1 code [2]:2 codes [3]:3 codes [4]:4 codes [5]:5 codes
[6]:6 codes [7]:7 codes [8]:8 codes [9]:9 codes [10]:10 codes [11]:11
codes [12]:12 codes [13]:13 codes [14]:14 codes [15]:15 codes.

21/1551-LZA 701 6012 Uen A | 2016-12-20 63


WCDMA Performance Management

4.1.5 IpsecTunnel Counter Class

Table 6 IpsecTunnel Counters


Counter Name Counter Description
The number of input IKE messages received by this IKE session
ikeTunInMsgs
including those received in error.
The number of input IP octets in IKE messages received by this IKE
ikeTunInOctets
session. IP and UDP headers are not included.
The number of output IKE messages that this IKE session supplied
ikeTunOutMsgs
to the lower layers for transmission including retransmissions.
The number of output octets in IKE messages this IKE session
ikeTunOutOctets supplied to the lower layers for transmission. IP and UDP headers
are not included.

4.1.6 IubDataStreams Counter Class


Table 7 IubDataStreams Counters
Counter Name Counter Description
The number of DCH Iub FP frames discarded owing to header or
pmDchFramesCrcMismatch
payload CRC mismatch.
The number of DCH Iub FP frames arrived after ToAWE but before
pmDchFramesLate
LTOA.
pmDchFramesOutOfSequence The number of Iub DCH Frame Protocol frames received
Dl out-of-sequence in the downlink direction.
pmDchFramesReceived The number of received DCH Iub frames in kframes.
The number of DCH Iub FP frames discarded owing to too late
pmDchFramesTooLate
arrival, that is, after LTOA.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i00 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i01 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i02 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i03 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i04 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i05 in RBS.

64 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 7 IubDataStreams Counters


pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i06 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i07 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i08 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i09 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i10 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i11 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i12 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i13 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i14 in RBS.
pmHsDataFramesReceivedSp The counter counts all correctly received HS-DSCH data frames
i15 in RBS.
Number Iub frame losses for all HS-DSCH data frame flows during
a sampling period. PDF ranges: [0]: Number of values = 0 [1]:
Number of values in range [1..2] [2]: Number of values in range
[3..4] [3]: Number of values in range [5..8] [4]: Number of values in
range [9..16] [5]: Number of values in range [17..32] [6]: Number of
values in range [33..64] [7]: Number of values in range [65..128]
pmIubFrameLossIntensity
[8]: Number of values in range [129..256] [9]: Number of values in
range [257..512] [10]: Number of values in range [513..1024] [11]:
Number of values in range [1025..2048] [12]: Number of values in
range [2049..4096] [13]: Number of values in range [4097..8192]
[14]: Number of values in range [8193..16384] [15]: Number of
values greater or equal than 16385
Iub HS MAC-d PDU received number of bits per one second
interval in the RBS. PDF ranges: [0]: Number of samples in range
pmIubMacdPduRbsReceivedBi
[0..200] kbits/s [1]: Number of samples in range [200..400] kbits/s
ts
... [99]: Number of samples in range [19800..20000] kbits/s [100]:
Number of samples >= 20000 kbits/s.

21/1551-LZA 701 6012 Uen A | 2016-12-20 65


WCDMA Performance Management

4.1.7 NodeBLocalCell Counter Class

Table 8 NodeBLocalCell Counters


Counter Name Counter Description
Received Signal Strength RSSI. PDF ranges: [0]: Number of
sampled values < -110.0 dBm [1]: Number of sampled values
in range [-110.0..-109.5] dBm [2]: Number of sampled values in
range [-109.5..-109.0] dBm [3]: Number of sampled values in
range [-109.0..-108.5] dBm ... [59]: Number of sampled values
pmAverageRssi
in range [-81.0..-80.5] dBm [60]: Number of sampled values in
range [-80.5..-80.0] dBm [61]: Number of sampled values in range
[-80.0..-75.0] dBm [62]: Number of sampled values in range
[-75.0..-70.0] dBm [63]: Number of sampled values in range
[-70.0..-65.0] dBm [64]: Number of sampled values >= -65.0 dBm.
The transmitted carrier power measured at the antenna reference
point, as a percentage of the maximum power (indicated by
the counter pmTransmittedCarrierPowerWLimit). PDF ranges:
pmTransmittedCarrierPowerW
[0]:Number of sampled values in range [0..2]% [1]:Number of
sampled values in range [2..4]% [2]:Number of sampled values in
range [4..6]%...[49]:Number of sampled values in range [98..100]%.
pmTransmittedCarrierPowerWLi Indicates the maximum limit of downlink transmission power. Range
mit [1..1000] where unit is 0.1 W.

4.1.8 Queue Counter Class

Table 9 Queue Counters


Counter Name Counter Description
The number of octets transmitted from the queue including Ethernet
queueHCOutOctets
header, VLAN tag, payload and Frame Check Sequence.
queueHCOutPkts The number of packets transmitted from the queue.
The number of octets discarded by the queue including Ethernet
queueOutDropOctets
header, VLAN tag, payload and Frame Check Sequence.
queueOutDropPkts The number of packets discarded by the queue.

66 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

4.1.9 RadioLinks Counter Class

Table 10 RadioLinks Counters


Counter Name Counter Description
The difference in SIR per receive branch per connection (DPCCH)
per cell. Both DCH and E-DCH branches are considered in counter.
PDF ranges:[0]: Value: SIR sample in range less or equal than
-29.5 dB [1]: Value: SIR sample in range [-29.5 .. -28.5] dB [2]:
Value: SIR sample in range [-28.5 .. -27.5] dB ... [29]: Value: SIR
pmBranchDeltaSir
sample in range [-1.5 .. -0.5] dB [30]: Value: SIR sample in range
[-0.5 .. 0.5] dB [31]: Value: SIR sample in range [0.5 .. 1.5] dB
...[58]: Value: SIR sample in range [27.5 .. 28.5] dB [59]: Value:
SIR sample in range [28.5 .. 29.5] dB [60]: Value: SIR sample in
range equal or greater than 29.5 dB.

4.1.10 SctpProfile Counter Class

Table 11 SctpProfile Counters


Counter Name Counter Description
sctpInControlChunks Number of control chunks received by the system.
Number of incoming from peer SCTP DATA chunks which were
chosen to be discarded by the system even though no errors had
been detected to prevent their delivery to the SCTP Host. Data
chunks are discarded for the following reason: - duplicated chunk -
sctpInDataDroppedChunks wrong association state. - memory allocation problem during chunk
processing. Chunks in the receive buffer that are not delivered to
the application (due to missing chunk with lower sequence number
or closed overload protection window towards the SCTP user) are
also counted before closing of the association.
Number of outgoing data chunks for which no problems were
encountered to prevent their transmission but were discarded by
sctpOutDataChunkDiscards
the system. Data chunks are discarded due to ungraceful closing
of the SCTP association.
sctpRtxChunks Number of data chunk retransmitted by the system.

4.1.11 Transport Counter Class

Table 12 Transport Counters


Counter Name Counter Description
ikeChildSaRekey The number of completed Child SA re-keyings.
The number of IKE_AUTH request messages received by the
ikeInAuthReq
system.

21/1551-LZA 701 6012 Uen A | 2016-12-20 67


WCDMA Performance Management

Table 12 Transport Counters


The number of IKE_AUTH response messages received by the
ikeInAuthRsp
system.
The number of CREATE_CHILD_SA request messages received
ikeInCrChildReq
by the system.
The number of CREATE_CHILD_SA response messages received
ikeInCrChildRsp
by the system.
The number of INFORMATIONAL request messages received by
ikeInInfoReq
the system.
The number of INFORMATIONAL response messages received
ikeInInfoRsp
by the system.
The number of IKE_SA_INIT request messages received by the
ikeInInitReq
system.
The number of IKE_SA_INIT response messages received by the
ikeInInitRsp
system.
The number of IKE_AUTH request messages that this
ikeOutAuthReq system supplied to the lower layers for transmission including
retransmissions.
The number of IKE_AUTH response messages that this
ikeOutAuthRsp system supplied to the lower layers for transmission including
retransmissions.
The number of CREATE_CHILD_SA request messages that this
ikeOutCrChildReq system supplied to the lower layers for transmission including
retransmissions.
The number of CREATE_CHILD_SA response messages that
ikeOutCrChildRsp this system supplied to the lower layers for transmission including
retransmissions.
The number of INFORMATIONAL request messages that this
ikeOutInfoReq system supplied to the lower layers for transmission including
retransmissions.
The number of INFORMATIONAL response messages that this
ikeOutInfoRsp system supplied to the lower layers for transmission including
retransmissions.
The number of IKE_SA_INIT request messages that this
ikeOutInitReq system supplied to the lower layers for transmission including
retransmissions.
The number of IKE_SA_INIT response messages that this
ikeOutInitRsp system supplied to the lower layers for transmission including
retransmissions.

68 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 12 Transport Counters


The number of input datagrams discarded by the system because
the IP address in the destination field of the IP header was not a
valid address to be received at this entity. This count includes invalid
addresses (for example, 0.0.0.0) and addresses of unsupported
ipSystemStatsInAddrErrors
Classes (for example, Class E). For entities that are not IP routers
and therefore do not forward datagrams, this counter includes
datagrams discarded because the destination address was not a
local address.
The number of locally addressed datagrams received successfully
ipSystemStatsInUnknownProtos but discarded by the system because of an unknown or unsupported
protocol.
The number of User Datagram Protocol (UDP) datagrams received
udpInErrors by the system that could not be delivered for reasons other than the
lack of an application at the destination port.

4.2 KPI Descriptions and Equations


For a detailed description of all the WCDA KPIs used in the RBS 6402, refer to
the WCDMA RAN Radio Network KPI, 120/1553-HSD 101 02 .

4.2.1 Accessibility KPIs


Table 13 Accessibility KPIs
KPI Name Description FormulaHi,
CS_A_SigSetup CS signaling setup success rate In an 100 * (RncFunction.pmNoIuSigEs
Shared RAN (MOCN); FAJ 121 974 tablishSuccessCs / RncFunction.
configuration with several CN operators, pmNoIuSigEstablishAttemptCs)
one attempt (RRC: Initial Direct Transfer)
may lead to several successes (SCCP:
Connection Confirmed), since in some
cases several CN operators' nodes may
be tried for the same attempt. Thus, this
KPI shall not be used in this configuration.
PS_A_SigSetup PS signaling setup success rate In an 100 * (RncFunction.pmNoIuSigEs
Shared RAN (MOCN); FAJ 121 974 tablishSuccessPs / RncFunction.
configuration with several CN operators, pmNoIuSigEstablishAttemptPs)
one attempt (RRC: Initial Direct Transfer)
may lead to several successes (SCCP:
Connection Confirmed), since in some
cases several CN operators' nodes may
be tried for the same attempt. Thus, this
KPI shall not be used in this configuration.

21/1551-LZA 701 6012 Uen A | 2016-12-20 69


WCDMA Performance Management

Table 13 Accessibility KPIs


Sp_A Circuit-Switched (CS) Speech 100 * ((UtranCell.pmTotNoRrcCo
Accessibility Accessibility success nnectReqCsSucc + UtranCell.pm
rate per UtranCell. NoCellUpdateSuccMultiCs)/ (Utra
nCell.pmTotNoRrcConnectReqCs
+ UtranCell.pmNoCellUpdateAtt
MultiCs - UtranCell.pmNoLoadS
haringRrcConnCs)) * (UtranCell.
pmNoNormalNasSignReleaseCs
/ (UtranCell.pmNoNormalNasSi
gnReleaseCs + UtranCell.pmN
oSystemNasSignReleaseCs)) *
(UtranCell.pmNoRabEstablishSu
ccessSpeech / UtranCell.pmNoR
abEstablishAttemptSpeech)

70 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 13 Accessibility KPIs


Sp_A_W Circuit-Switched (CS) Speech 100 * (((UtranCell.pmNoRabEsta
Accessibility Weighted Weighted blishAttemptSpeech - UtranCell.p
speech accessibility for call establishment mNoRabEstAttemptMultiSpeech)
from Idle, URA_PCH, CELL_FACH and / UtranCell.pmNoRabEstablish
CELL_DCH. AttemptSpeech) * (UtranCell.p
mTotNoRrcConnectReqCsSucc
/ (UtranCell.pmTotNoRrcCon
nectReqCs - UtranCell.pmN
oLoadSharingRrcConnCs) *
((UtranCell.pmNoNormalNasSi
gnReleaseCs - UtranCell.pmNo
NormalNasSignReleaseMultiCs)
/ (UtranCell.pmNoNormalNasSi
gnReleaseCs - UtranCell.pmNo
NormalNasSignReleaseMultiCs
+ UtranCell.pmNoSystemNasSig
nReleaseCs - UtranCell.pmNoS
ystemNasSignReleaseMultiCs))
* (UtranCell.pmNoRabEstablish
SuccessSpeech - UtranCell.pm
NoRabEstSuccessMultiSpeech)
/ (UtranCell.pmNoRabEstablish
AttemptSpeech - UtranCell.pmN
oRabEstAttemptMultiSpeech)) +
((UtranCell.pmNoRabEstAttempt
MultiSpeechUra / UtranCell.pmN
oRabEstablishAttemptSpeech) *
(UtranCell.pmNoCellUpdateSucc
MultiCs/UtranCell.pmNoCellUpda
teAttemptMultiCs) * (UtranCell.pm
NoNormalNasSignRelMultiCsUra
/ (UtranCell.pmNoNormalNasSign
RelMultiCsUra + UtranCell.pmNo
SystemNasSignRelMultiCsUra)) *
(UtranCell.pmNoRabEstSuccess
MultiSpeechUra / UtranCell.pmNo
RabEstAttemptMultiSpeechUra))
+ ((UtranCell.pmNoRabEstAttem
ptMultiSpeech-UtranCell.pmNoR
abEstAttemptMultiSpeechUra) /
UtranCell.pmNoRabEstablishAtte
mptSpeech) * ((UtranCell.pmNo
NormalNasSignReleaseMultiCs -
UtranCell.pmNoNormalNasSignR
elMultiCsUra) / (UtranCell.pmNo
SystemNasSignReleaseMultiCs -
UtranCell.pmNoSystemNasSign
RelMultiCsUra + UtranCell.pmNo
NormalNasSignReleaseMultiCs -
UtranCell.pmNoNormalNasSign
RelMultiCsUra)) * ((UtranCell.pm
NoRabEstSuccessMultiSpeech -
UtranCell.pmNoRabEstSuccess
MultiSpeechUra) / (UtranCell.pm
21/1551-LZA 701 6012 Uen A | 2016-12-20 71
NoRabEstAttemptMultiSpeech -
UtranCell.pmNoRabEstAttemptM
ultiSpeechUra)))
WCDMA Performance Management

Table 13 Accessibility KPIs


Sp_A_Multi_U CS Speech MultiRAB Accessibility from 100 * (UtranCell.pmNoCellUp
URA_PCH Accessibility success rate dateSuccMultiCs / UtranCell.
per UtranCell for CS Speech (Including pmNoCellUpdateAttMultiCs) *
AMR Single-mode 12.2, AMR-NB (UtranCell.pmNoNormalNasSign
Multi-mode single- and multi-rate, and ReleaseMultiCs / (UtranCell.pmN
AMR-WB) RABs established in MultiRAB oNormalNasSignReleaseMultiCs
connections from URA_PCH. + UtranCell.pmNoSystemNasSig
nReleaseMultiCs)) * (UtranCell.p
mNoRabEstSuccessMultiSpeech
/ UtranCell.pmNoRabEstAttempt
MultiSpeech)
Sp_A_Multi_D CS Speech MultiRAB Accessibility from 100 * (UtranCell.pmNoNor
FACH or DCH Accessibility success rate malNasSignReleaseMultiCs
per UtranCell for CS Speech (Including / (UtranCell.pmNoNormal
AMR Single-mode 12.2, AMR-NB NasSignReleaseMultiCs +
Multi-mode single- and multi-rate, and UtranCell.pmNoSystemNasSignR
AMR-WB) RABs established in MultiRAB eleaseMultiCs)) * (UtranCell.pm
connections from FACH or DCH. NoRabEstSuccessMultiSpeech /
UtranCell.pmNoRabEstAttemptM
ultiSpeech)
CSAmrWb_A_Multi_U CS Speech (AMR-WB) MultiRAB 100 * (UtranCell.pmNoCellUp
Accessibility from URA_PCH Accessibility dateSuccMultiCs / UtranCell.
success rate per UtranCell for CS Speech pmNoCellUpdateAttMultiCs) *
(AMR-WB) RABs established in MultiRAB (UtranCell.pmNoNormalNasSign
connections from URA_PCH. ReleaseMultiCs / (UtranCell.pmN
oNormalNasSignReleaseMultiCs
+ UtranCell.pmNoSystemNasSig
nReleaseMultiCs)) * (UtranCell.p
mNoRabEstSuccessMultiAmrWb
/ UtranCell.pmNoRabEstAttempt
MultiAmrWb)
CSAmrNb_A_Multi_U CS Speech (AMR-NB) MultiRAB 100 * (UtranCell.pmNoCellUp
Accessibility from URA_PCH Accessibility dateSuccMultiCs / UtranCell.
success rate per UtranCell for CS Speech pmNoCellUpdateAttMultiCs) *
(AMR-NB) RABs established in MultiRAB (UtranCell.pmNoNormalNasSign
connections from URA_PCH. ReleaseMultiCs / (UtranCell.pmN
oNormalNasSignReleaseMultiCs
+ UtranCell.pmNoSystemNasSig
nReleaseMultiCs)) * (UtranCell.p
mNoRabEstSuccessMultiAmrNb
/ UtranCell.pmNoRabEstAttempt
MultiAmrNb)

72 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 13 Accessibility KPIs


CSAmrNb_A_Multi_D CS Speech (AMR-WB) MultiRAB 100 * (UtranCell.pmNoNor
Accessibility from FACH or DCH malNasSignReleaseMultiCs
Accessibility success rate per UtranCell / (UtranCell.pmNoNormal
for CS Speech (AMR-WB) RABs NasSignReleaseMultiCs +
established in MultiRAB connections from UtranCell.pmNoSystemNasSign
FACH or DCH. ReleaseMultiCs)) * (UtranCell.p
mNoRabEstSuccessMultiAmrNb
/ UtranCell.pmNoRabEstAttempt
MultiAmrNb)
Sp_A_Csfb Accessibility success rate per UtranCell 100 * (UtranCell.pmTotNoRrcCo
for speech established at CS Voice nnReqCsfbIndSucc / (UtranCell.
Fallback from LTE, excluding RRC pmTotNoRrcConnReqCsfbInd -
accesses subject to inter-frequency load UtranCell.pmNoLoadSharingRr
sharing redirections. This KPI depends cConnCsfbInd)) * (UtranCell.pm
on a UE population in the network utilizing NoNormalNasSignRelCsfbInd /
both types of CSFB determination (UtranCell.pmNoNormalNasSign
methods. If that is not the case, revise the RelCsfbInd + UtranCell.pmNoSy
KPI to only be based on the applicable stemNasSignRelCsfbInd)) * ((Utr
type of CSFB detected or CSFB indicated anCell.pmNoRabEstSuccCsfbInd
counters. For further explanation of + UtranCell.pmNoRabEstSuccCsf
the CSFB counters see Release with bDetect) / (UtranCell.pmNoRabE
Redirect to LTE. stAttCsfbInd + UtranCell.pmNoR
abEstAttCsfbDetect))
CS64_A Circuit-Switched 64 Accessibility 100 * (UtranCell.pmTotNoRrcCon
Accessibility success rate per UtranCell nectReqCsSucc / (UtranCell.pmT
for CS 64. otNoRrcConnectReqCs - UtranCe
ll.pmNoLoadSharingRrcConnCs))
* (UtranCell.pmNoNormalNasSi
gnReleaseCs / (UtranCell.pmN
oNormalNasSignReleaseCs +
UtranCell.pmNoSystemNasSig
nReleaseCs)) * (UtranCell.pm
NoRabEstablishSuccessCs64 /
UtranCell.pmNoRabEstablishAtte
mptCs64)
CS57_A Circuit-Switched Streaming (CS 57) 100 * (UtranCell.pmTotNoRrcCon
Accessibility Accessibility success rate nectReqCsSucc / (UtranCell.pmT
per UtranCell for CS streaming. otNoRrcConnectReqCs - UtranCe
ll.pmNoLoadSharingRrcConnCs))
* (UtranCell.pmNoNormalNasSi
gnReleaseCs / (UtranCell.pmN
oNormalNasSignReleaseCs +
UtranCell.pmNoSystemNasSig
nReleaseCs)) * (UtranCell.pm
NoRabEstablishSuccessCs57 /
UtranCell.pmNoRabEstablishAtte
mptCs57)

21/1551-LZA 701 6012 Uen A | 2016-12-20 73


WCDMA Performance Management

Table 13 Accessibility KPIs


PStr64_A Packet-Switched (PS) Streaming 64 100 * (UtranCell.pmNoRabEst
Accessibility Accessibility success rate ablishSuccessPacketStream /
per UtranCell for PS streaming 64. UtranCell.pmNoRabEstablishAtte
mptPacketStream)
PStr128_A Packet-Switched (PS) Streaming 128 100 * (UtranCell.pmNoRabEsta
Accessibility Accessibility success rate blishSuccessPacketStream128 /
per UtranCell for PS streaming 128. UtranCell.pmNoRabEstablishAtte
mptPacketStream128)
PStrHs_A Packet-Switched (PS) Streaming HS 100 * (UtranCell.pmNoRabE
Accessibility Accessibility success rate stSuccessPacketStreamHs /
per UtranCell for PS streaming HS. UtranCell.pmNoRabEstAttemptP
acketStreamHs)
Pint_A Packet-Switched (PS) Data Interactive 100 * (UtranCell.pmTotNoRrc
Accessibility Accessibility success rate ConnectReqPsSucc / (UtranC
per UtranCell for all PS interactive ell.pmTotNoRrcConnectReqPs
services. - UtranCell.pmNoLoadSharing
RrcConnPs)) * (UtranCell.pm
NoNormalNasSignReleasePs /
(UtranCell.pmNoNormalNasSi
gnReleasePs + UtranCell.pmN
oSystemNasSignReleasePs))
* (UtranCell.pmNoRabEstabli
shSuccessPacketInteractive /
UtranCell.pmNoRabEstablishAtte
mptPacketInteractive)

74 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 13 Accessibility KPIs


Pint_A_Session Packet-Switched (PS) Data Interactive 100 * (((UtranCell.pmNoRabEst
Session Accessibility per Utran cell taking ablishAttemptPacketInteractive -
into consideration all the individual access UtranCell.pmNoRabEstAttemptM
made by the UE. ultiPsInt) / (UtranCell.pmNoRabE
stablishAttemptPacketInteractive
+ UtranCell.pmUpSwitchSessAc
cessAttFach + UtranCell.pmCh
SwitchSuccUraDch - UtranCell.
pmChSwitchSuccUraDchCsInit
+ UtranCell.pmChSwitchSucc
UraHs - UtranCell.pmChSwitc
hSuccUraHsCsInit + UtranCell
.pmChSwitchFailUraFachAdm)
* (UtranCell.pmTotNoRrcCon
nectReqPsSucc / UtranCell.p
mTotNoRrcConnectReqPs)*
(UtranCell.pmNoNormalNasSig
nReleasePs - UtranCell.pmNoN
ormalNasSignReleaseMultiPs) /
(UtranCell.pmNoNormalNasSig
nReleasePs - UtranCell.pmNoN
ormalNasSignReleaseMultiPs +
UtranCell.pmNoSystemNasSig
nReleasePs - UtranCell.pmNoS
ystemNasSignReleaseMultiPs)
* (UtranCell.pmNoRabEstabli
shSuccessPacketInteractive -
UtranCell.pmNoRabEstSuccessM
ultiPsInt) / (UtranCell.pmNoRabE
stablishAttemptPacketInteractive
- UtranCell.pmNoRabEstAttem
ptMultiPsInt))+ ((UtranCell.pm
NoRabEstAttemptMultiPsInt) /
(UtranCell.pmNoRabEstablishAtt
emptPacketInteractive + UtranCel
l.pmUpSwitchSessAccessAttFach
+ UtranCell.pmChSwitchSuccUr
aDch - UtranCell.pmChSwitchSu
ccUraDchCsInit + UtranCell.pm
ChSwitchSuccUraHs - UtranCe
ll.pmChSwitchSuccUraHsCsInit
+ UtranCell.pmChSwitchFailUra
FachAdm) * (UtranCell.pmNoN
ormalNasSignReleaseMultiPs) /
(UtranCell.pmNoNormalNasSign
ReleaseMultiPs + UtranCell.pmN
oSystemNasSignReleaseMultiPs)
* (UtranCell.pmNoRabEstSucc
essMultiPsInt) / (UtranCell.pm
NoRabEstAttemptMultiPsInt)) +
((UtranCell.pmUpSwitchSessAc
cessAttFach + UtranCell.pmCh
SwitchSuccUraDch - UtranCell.
pmChSwitchSuccUraDchCsInit
21/1551-LZA 701 6012 Uen A | 2016-12-20 75
+ UtranCell.pmChSwitchSuccU
raHs - UtranCell.pmChSwitchS
uccUraHsCsInit + UtranCell.p
mChSwitchFailUraFachAdm) /
WCDMA Performance Management

Table 13 Accessibility KPIs


Pint_DCH_A Packet-Switched (PS) Data Interactive 100 * (UtranCell.pmTotNoRrcC
DCH/FACH Accessibility Accessibility onnectReqPsSucc / (UtranCel
success rate per UtranCell for PS l.pmTotNoRrcConnectReqPs -
interactive DCH/FACH. UtranCell.pmNoLoadSharingRrc
ConnPs)) * (UtranCell.pmNoNorm
alNasSignReleasePs / (UtranCell.
pmNoNormalNasSignReleasePs
+ UtranCell.pmNoSystemNasSi
gnReleasePs)) * (UtranCell.pm
NoRabEstSuccessPsIntNonHs /
UtranCell.pmNoRabEstAttemptPs
IntNonHs)
PsInt_A_Multi_D PS Interactive MultiRAB Accessibility 100 * (UtranCell.pmNoNor
from FACH or DCH Accessibility success malNasSignReleaseMultiPs
rate per UtranCell for PS Interactive RABs / (UtranCell.pmNoNormal
established in MultiRAB connections from NasSignReleaseMultiPs +
FACH or DCH UtranCell.pmNoSystemNasSign
ReleaseMultiPs)) * (UtranCell.p
mNoRabEstSuccessMultiPsInt /
UtranCell.pmNoRabEstAttemptM
ultiPsInt)
Pint_HS_A Packet-Switched (PS) Data Interactive 100 * (UtranCell.pmTotNoRrc
HS Accessibility Accessibility success ConnectReqPsSucc / (UtranC
rate per UtranCell for PS interactive HS. ell.pmTotNoRrcConnectReqPs
- UtranCell.pmNoLoadSharing
RrcConnPs)) * (UtranCell.pm
NoNormalNasSignReleasePs /
(UtranCell.pmNoNormalNasSig
nReleasePs + UtranCell.pmNo
SystemNasSignReleasePs)) *
(UtranCell.pmNoRabEstablish
SuccessPacketInteractiveHs /
UtranCell.pmNoRabEstablishAtte
mptPacketInteractiveHs)

76 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 13 Accessibility KPIs


Pint_EUL_A Packet-Switched (PS) Data Interactive 100 * (UtranCell.pmTotNoRrc
EUL Accessibility Accessibility success ConnectReqPsSucc / (UtranC
rate per UtranCell for PS interactive EUL. ell.pmTotNoRrcConnectReqPs
- UtranCell.pmNoLoadSharing
RrcConnPs)) * (UtranCell.pm
NoNormalNasSignReleasePs /
(UtranCell.pmNoNormalNasSig
nReleasePs + UtranCell.pmNo
SystemNasSignReleasePs)) *
(UtranCell.pmNoRabEstablish
SuccessPacketInteractiveEul /
UtranCell.pmNoRabEstablishAtte
mptPacketInteractiveEul)
CBS_TCP_A TCP Connection Accessibility 100 * (IuBcLink.pmN
Accessibility success rate per UtranCell oSuccOutTcpConn /
for TCP connections established from the IuBcLink.pmNoAttOutTcpConn)
RNC to Cell Broadcast Center (CBC).

4.2.2 Retainability KPIs

Table 14 Retainability KPIs


KPI Name Description Formula
Sp_R_D Circuit-Switched (CS) Speech Drop Rate 100 * (UtranCell.pmNoSystemRa
The drop rate per UtranCell for speech. bReleaseSpeech / (UtranCell.pm
NoNormalRabReleaseSpeech +
UtranCell.pmNoSystemRabRele
aseSpeech))
Sp_R_D_Iur Circuit-Switched (CS) Speech Drop Rate 100 * (IurLink.pmNoSystemRab
The drop rate per IurLink for Drifting ReleaseSpeech / (IurLink.pmN
UEs in neighboring RNCs for speech. If oNormalRabReleaseSpeech +
the feature “Drifting RNC Observability”, IurLink.pmNoSystemRabRelease
Performance Management in WCDMA, Speech))
is not in use the total drop rate per RNC
including Drifting UEs for speech is given
by summarizing all cell level counters up
to RNC level together with all Iur level
counters for that particular RNC from
IurLinks in neighboring RNCs.
Sp_Multi_R_D CS Speech Drop Rate in MultiRAB Calls 100 * (UtranCell.pmSystemRel
The Circuit-Switched Speech Drop Rate MultiSpeech / (UtranCell.pmSy
while in MultiRAB calls for UtranCell. stemRelMultiSpeech + UtranC
ell.pmNormalRelMultiSpeech +
UtranCell.pmSystemRelMultiPsIn
tToSpeech + UtranCell.pmNormal
RelMultiPsIntToSpeech))

21/1551-LZA 701 6012 Uen A | 2016-12-20 77


WCDMA Performance Management

Table 14 Retainability KPIs


CsAmrNb_Multi_R_D CS Speech (AMR-NB) Drop Rate in 100 * (UtranCell.pmSystemRelM
MultiRAB Calls The Circuit-Switched ultiAmrNb / (UtranCell.pmSystem
Speech (AMR-NB) Drop Rate while in RelMultiAmrNb + UtranCell.pmN
MultiRAB calls for UtranCell. ormalRelMultiAmrNb + UtranCell.
pmSystemRelMultiPsIntToAmrNb
+ UtranCell.pmNormalRelMultiPsI
ntToAmrNb))
CsAmrWb_Multi_R_D CS Speech (AMR-WB) Drop Rate in 100 * (UtranCell.pmSystemRel
MultiRAB Calls The Circuit-Switched MultiAmrWb / (UtranCell.pmSy
Speech (AMR-WB) Drop Rate while in stemRelMultiAmrWb + UtranC
MultiRAB calls for UtranCell. ell.pmNormalRelMultiAmrWb +
UtranCell.pmSystemRelMultiPsIn
tToAmrWb + UtranCell.pmNormal
RelMultiPsIntToAmrWb))
Sp_R_MD Circuit-Switched (CS) Speech Minutes RESOLUTION_MIN *
per Drop The Speech Minutes per Drop (Sp_U_User / UtranCell.pmN
per UtranCell. RESOLUTION_MIN is the oSystemRabReleaseSpeech)
measurement time in minutes, that is 15
for one ROP.
CS64_R_D Circuit-Switched 64 Drop Rate The drop 100 * (UtranCell.pmNoSystem
rate per UtranCell for CS 64. RabReleaseCs64 / (UtranCell.p
mNoNormalRabReleaseCs64 +
UtranCell.pmNoSystemRabRelea
seCs64))
CS64_R_D_Iur Circuit-Switched 64 Drop Rate The 100 * (IurLink.pmNoSystemRabR
drop rate per IurLink for Drifting UEs eleaseCs64 / (IurLink.pmNoNorm
in neighboring RNCs for CS 64 If the alRabReleaseCs64 + IurLink.pm
feature “Drifting RNC Observability”, NoSystemRabReleaseCs64))
Performance Management in WCDMA,
is not in use the total drop rate per RNC
including Drifting UEs for CS 64 is given
by summarizing all cell level counters up
to RNC level together with all Iur level
counters for that particular RNC from
IurLinks in neighboring RNCs.
CS64_R_MD Circuit-Switched 64 Minutes per Drop The RESOLUTION_MIN *
Circuit-Switched 64 Minutes per Drop (CS64_U_User / UtranCell.p
per UtranCell. RESOLUTION_MIN is the mNoSystemRabReleaseCs64)
measurement time in minutes, that is 15
for one ROP.
CS57_R_D Circuit-Switched Streaming (CS 57) Drop 100 * (UtranCell.pmNoSys
Rate The drop rate per UtranCell for CS temRabReleaseCsStream /
Streaming. (UtranCell.pmNoNormalRabRele
aseCsStream + UtranCell.pmNoS
ystemRabReleaseCsStream))

78 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 14 Retainability KPIs


CS57_R_D_Iur Circuit-Switched Streaming (CS 57) 100 * (IurLink.pmNoSystemRab
Drop Rate The drop rate per IurLink for ReleaseCsStream / (IurLink.pmN
Drifting UEs in neighboring RNCs for CS oNormalRabReleaseCsStream +
Streaming. IurLink.pmNoSystemRabReleas
eCsStream))
CS57_R_MD Circuit-Switched Streaming (CS 57) RESOLUTION_MIN *
Minutes per Drop The Circuit-Switched (CS57_U_User / UtranCell.pmNo
Streaming (CS 57) Minutes per Drop per SystemRabReleaseCsStream)
UtranCell. RESOLUTION_MIN is the
measurement time in minutes, that is 15
for one ROP.
Hs_R_D HS Connection Drop Rate The drop rate 100 *((UtranCell.pmSystemRele
of HS connection (UE connections with at aseHsConn + UtranCell.pmSyst
least one PS RAB mapped on a DCH/HS emRelMultiHsConnToSpeech) /
or EUL/HS Radio Bearer) per UtranCell. (UtranCell.pmNormalReleaseHs
Conn + UtranCell.pmNormalRel
MultiHsConnToSpeech + UtranC
ell.pmSystemReleaseHsConn +
UtranCell.pmSystemRelMultiHsC
onnToSpeech + UtranCell.pmRec
onfSuccOrigHsConn))
PStr64_R_D Packet-Switched (PS) Streaming 64 Drop 100 * (UtranCell.pmNoSyste
Rate The drop rate per UtranCell for PS mRabReleasePacketStream
Streaming 64. / (UtranCell.pmNoNormalR
abReleasePacketStream +
UtranCell.pmNoSystemRabRelea
sePacketStream))
PStr128_R_D Packet-Switched (PS) Streaming 128 100 * (UtranCell.pmNoSystem
Drop Rate The drop rate per UtranCell for RabReleasePacketStream128
PS Streaming 128. / (UtranCell.pmNoNormalRab
ReleasePacketStream128 +
UtranCell.pmNoSystemRabRelea
sePacketStream128))
PStrHS_R_D Packet-Switched (PS) Streaming HS 100 * (UtranCell.pmNoSyst
Drop Rate The drop rate per UtranCell for emRabReleasePsStreamHs
PS Streaming HS. / (UtranCell.pmNoNormalR
abReleasePsStreamHs +
UtranCell.pmNoSystemRabRelea
sePsStreamHs))
PStr_R_D_Iur Packet-Switched (PS) Streaming Drop 100 * (IurLink.pmNoSystem
Rate per IurLink for Drifting Ues The RabReleasePacketStream /
drop rate per IurLink for Drifting UEs in (IurLink.pmNoNormalRabRelease
neighboring RNCs for PS Streaming. PacketStream + IurLink.pmNoSys
temRabReleasePacketStream))

21/1551-LZA 701 6012 Uen A | 2016-12-20 79


WCDMA Performance Management

Table 14 Retainability KPIs


PStr64_R_MD Packet-Switched (PS) Streaming 64 RESOLUTION_MIN
Minutes per Drop The Packet-Switched * (PStr64_U_User /
(PS) Streaming 64 Minutes per Drop per UtranCell.pmNoSystemRabR
UtranCell. RESOLUTION_MIN is the eleasePacketStream128)
measurement time in minutes, that is 15
for one ROP.
PStr128_R_MD Packet-Switched (PS) Streaming 128 RESOLUTION_MIN
Minutes per Drop The Packet-Switched * (PStr128_U_User /
(PS) Streaming 128 Minutes per Drop UtranCell.pmNoSystemRabR
per UtranCell. RESOLUTION_MIN is the eleasePacketStream128)
measurement time in minutes, that is 15
for one ROP.
PStrHS_R_MD Packet-Switched (PS) Streaming HS RESOLUTION_MIN
Minutes per Drop The Packet-Switched * (PStrHS_U_User /
(PS) Streaming Minutes per Drop per UtranCell.pmNoSystemRabR
UtranCell. eleasePsStreamHs)
Pint_R_D Packet-Switched (PS) Interactive Drop 100 * ((UtranCell.pmNoSystemR
Rate The Packet-Switched drop rate per abReleasePacket - UtranCell.pm
UtranCell for all PS interactive services. NoSystemRabReleasePacketUra
- UtranCell.pmChSwitchAttemptF
achUra + UtranCell.pmChSwitch
SuccFachUra - UtranCell.pmChS
witchAttemptDchUra + UtranCell.
pmChSwitchSuccDchUra - Utra
nCell.pmChSwitchAttemptHsUra
+ UtranCell.pmChSwitchSuccHs
Ura) / (UtranCell.pmNoNormalR
abReleasePacket + UtranCell.p
mNoSystemRabReleasePacket -
UtranCell.pmNoNormalRabRele
asePacketUra - UtranCell.pmNo
SystemRabReleasePacketUra +
UtranCell.pmChSwitchSuccFach
Ura + UtranCell.pmChSwitchSuc
cDchUra + UtranCell.pmChSwit
chSuccHsUra))
Pint_R_D_Iur Packet-Switched (PS) Interactive Drop 100 * (IurLink.pmNoSystemRa
Rate per IurLink for Drifting Ues The bReleasePacket / (IurLink.pmN
drop rate per IurLink for Drifting UEs in oNormalRabReleasePacket +
neighboring RNCs for PS Interactive. IurLink.pmNoSystemRabReleas
ePacket))

80 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 14 Retainability KPIs


PsInt_Multi_R_D PS Interactive RAB Drop Rate in 100 * (UtranCell.pmSyste
MultiRAB Calls The Packet-Switched mRelMultiPsInt / (UtranCel
Interactive RAB Drop Rate while in l.pmSystemRelMultiPsInt +
MultiRAB calls for UtranCell. UtranCell.pmNormalRelMultiPsInt
+ UtranCell.pmSystemRelMultiSp
eechToPsInt + UtranCell.pmNorm
alRelMultiSpeechToPsInt))
PintDCH_R_D Packet-Switched (PS) Interactive 100 * ((UtranCell.pmNoSystemR
DCH/FACH Drop Rate Packet-Switched abReleasePacket - UtranCell.pm
(PS) Interactive DCH/FACH drop rate per NoSystemRabReleasePacketUra
UtranCell. - UtranCell.pmNoSystemRbRele
aseHs - UtranCell.pmChSwitchAt
temptFachUra + UtranCell.pmC
hSwitchSuccFachUra - UtranCe
ll.pmChSwitchAttemptDchUra +
UtranCell.pmChSwitchSuccDchU
ra) / (UtranCell.pmNoNormalRab
ReleasePacket - UtranCell.pmNo
NormalRabReleasePacketUra +
UtranCell.pmNoSystemRabRelea
sePacket - UtranCell.pmNoSyste
mRabReleasePacketUra - Utran
Cell.pmNoNormalRbReleaseHs -
UtranCell.pmNoSystemRbReleas
eHs + UtranCell.pmNoSuccRbR
econfOrigPsIntDch + UtranCell.p
mChSwitchSuccFachUra + Utran
Cell.pmUpswitchFachHsSuccess
+ UtranCell.pmChSwitchSuccDch
Ura))
PintHS_R_D Packet-Switched (PS) Interactive HS 100 * (UtranCell.pmNoSystem
Drop Rate Packet-Switched (PS) RbReleaseHs - UtranCell.pmC
Interactive HS drop rate per UtranCell. hSwitchAttemptHsUra + Utran
Cell.pmChSwitchSuccHsUra) /
(UtranCell.pmNoNormalRbRel
easeHs + UtranCell.pmNoSyst
emRbReleaseHs + UtranCell.p
mNoSuccRbReconfPsIntDch +
UtranCell.pmPsIntHsToFachSucc
+ UtranCell.pmChSwitchSuccHs
Ura)
Pint_R_MD Packet-Switched (PS) Interactive RESOLUTION_MIN *
Minutes per Drop The Packet-Switched Pint_U_User / (UtranCell.pm
(PS) Interactive Minutes per Drop per NoSystemRabReleasePacket -
UtranCell. RESOLUTION_MIN is the UtranCell.pmNoSystemRabRele
measurement time in minutes, that is 15 asePacketUra)
for one ROP.

21/1551-LZA 701 6012 Uen A | 2016-12-20 81


WCDMA Performance Management

Table 14 Retainability KPIs


PintDCH_R_MD Packet-Switched (PS) Interactive RESOLUTION_MIN *
DCH/FACH Minutes per Drop (PintDCH_U_User +
Packet-Switched (PS) Interactive PintFach_U_User) / (UtranCell.p
DCH/FACH Minutes per Drop per mNoSystemRabReleasePacket -
UtranCell. RESOLUTION_MIN is the UtranCell.pmNoSystemRabRelea
measurement time in minutes, that is 15 sePacketUra - UtranCell.pmNoSy
for one ROP. stemRbReleaseHs)
PintHS_R_MD Packet-Switched (PS) Interactive HS RESOLUTION_MIN *
Minutes per Drop Packet-Switched (PS) (PintHS_U_User / UtranCell.
Interactive HS Minutes per Drop per pmNoSystemRbReleaseHs)
UtranCell. RESOLUTION_MIN is the
measurement time in minutes, that is 15
for one ROP.
PintEUL_R_MD Packet-Switched (PS) Interactive EUL RESOLUTION_MIN *
Minutes per Drop Packet-Switched (PS) (PintEUL_U_User / UtranCell
Interactive EUL Minutes per Drop per .pmNoSystemRbReleaseEul)
UtranCell. RESOLUTION_MIN is the
measurement time in minutes, that is 15
for one ROP.
SRBonly34_R_D SRB only 3.4 Drop Rate The drop rate 100 * (UtranCell.pmNoSystemRe
per UtranCell for SRB only 3.4. leaseSrbOnly34 / (UtranCell.pm
NoSystemReleaseSrbOnly34 +
UtranCell.pmNoNormalReleaseSr
bOnly34))
SRBonly136_R_D SRB only 13.6 Drop Rate The drop rate 100 * (UtranCell.pmNoSystemRel
per UtranCell for SRB only 13.6. easeSrbOnly136 / (UtranCell.pm
NoSystemReleaseSrbOnly136 +
UtranCell.pmNoNormalReleaseS
rbOnly136))
SRBonlyHS_R_D SRB only HS Drop Rate The drop rate 100 * (UtranCell.pmNoSystemRel
per UtranCell for SRB only HS. easeSrbOnlyHs / (UtranCell.pm
NoSystemReleaseSrbOnlyHs +
UtranCell.pmNoNormalReleaseSr
bOnlyHs))
SRBonlyEUL_R_D SRB only EUL Drop Rate The drop rate 100 * (UtranCell.pmNoSystemRe
per UtranCell for SRB only EUL. leaseSrbOnlyEul / (UtranCell.pm
NoSystemReleaseSrbOnlyEul +
UtranCell.pmNoNormalReleaseSr
bOnlyEul))
Drop_Source Drop Rate on Source UeRc Level The 100 * (UeRc.pmSystemR
drop rate for source UeRc. eleaseSource / (UeRc.p
mSystemReleaseSource +
UeRc.pmNormalReleaseSource))

82 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 14 Retainability KPIs


Reconf_Drop_Source Reconfiguration Drop Rate on Source 100 * (UeRc.pmReconfSysRelSo
UeRc Level The UeRc reconfiguration urce / UeRc.pmReconfAttSource)
drop rate on source UeRc level.
Reconf_Drop_Target Reconfiguration Drop Rate on Source 100 * (UeRc.pmReconfSysRelTar
UeRc Level The UeRc reconfiguration get / UeRc.pmReconfAttTarget)
drop rate on target UeRc level.

4.2.3 Integrity KPIs


Table 15 Integrity KPIs
KPI Name Description Formula
SP_I_UL BLER BLER for both uplink and 100 * (UeRc.pmFaulty
downlink for the different services can TransportBlocksAcUl /
be measured on cell level using RES. UeRc.pmTransportBlocksAcUl)
See Radio Environment Statistics for
more information on RES and the
formulas to use. It is possible to calculate
uplink BLER on RNC level using certain
Transport Block counters. Formula can
be used to calculate the uplink BLER for
different services, using different UeRc
State numbers. UeRc State numbering is
described in General Performance Event
Handling.
PINTHS_I_Bler HSDPA BLER on radio node Level The 100 * (HsDschResources.pmNac
HSDPA BLER on radio node level. kReceived / (HsDschResources.p
mNackReceived + HsDschResou
rces.pmAckReceived))
PINTEUL10ms_I_Bler EUL BLER on RNC level for EUL10ms 100 * (UtranCell.pmEulHarqTra
users The EUL BLER on RNC level nsmTti10Failure / (UtranCell.pm
for EUL10ms users. Values of all EulHarqTransmTti10PsRabs +
pmEulHarqTransmTti10PSRabs ranges UtranCell.pmEulHarqTransmTti1
are added. 0Failure))
PINTEUL2ms_I_Bler EUL BLER on RNC level for EUL2ms 100 * (UtranCell.pmEulHarqTrans
users The EUL BLER on RNC level mTti2Failure / (UtranCell.pmEulH
for EUL2ms users. Values of all arqTransmTti2PsRabs + UtranCe
pmEulHarqTransmTti2PSRabs ranges ll.pmEulHarqTransmTti2Failure))
are added.

21/1551-LZA 701 6012 Uen A | 2016-12-20 83


WCDMA Performance Management

Table 15 Integrity KPIs


PintDCH_I_TP Packet-Switched (PS) DCH/FACH 8 * 1000 * (RncFunction.pmSent
Interactive Average Throughput Equation PacketData2 + RncFunction.pm
measures the Average Throughput for SentPacketData3 + RncFunction
PS interactive DCH/FACH. Counters .pmSentPacketData4) / (RncFun
for small packets, pmSentPacketData1 ction.pmTotalPacketDuration2 +
and pmTotalPacketDurationHs are RncFunction.pmTotalPacketDurat
not included in the formula as there ion3 + RncFunction.pmTotalPack
is a constant one-way delay for each etDuration4)
packet affecting latency for the small
packets, which gives a worse measured
performance than user perceived
performance, if these counters are used.
PintHS_I_TP Packet-Switched (PS) Interactive HS 8 * 1000 * (RncFunction.pmSent
Average Throughput Equation measures PacketDataHs3 + RncFunction.p
the Average Throughput for PS interactive mSentPacketDataHs4) / (RncFun
HS. Counters for small packets, pmSent ction.pmTotalPacketDurationHs3
PacketDataHs1, pmSentPacketDataHs2, + RncFunction.pmTotalPacketD
pmTotalPacketDurationHs1 and urationHs4)
pmTotalPacketDurationHs2 are not
included in the formula as there is
a constant one-way delay for each
packet affecting latency for the small
packets, which gives a worse measured
performance than user perceived
performance, if these counters are used.
PintHSFach_I_Tp_Us Packet-Switched (PS) Interactive Hsdsch.pmSumHsFachRlcUserP
er HS-FACH User Throughput. acketThp / Hsdsch.pmSamplesH
sFachRlcUserPacketThp
PintDCH_I_DlTp_User Packet-Switched (PS) Interactive UtranCell.pmSumDchDlRlcUserP
DCH/FACH User Throughput, Downlink acketThp / UtranCell.pmSamples
The PS Interactive DCH/FACH user DchDlRlcUserPacketThp
downlink throughput per UtranCell in
a measurement period of 15 minutes.
This KPI can be measured for a single
UtranCell and for all UtranCells under the
RNC.
PintDCH_I_UlTp_User Packet-Switched (PS) Interactive UtranCell.pmSumDchUlRlcUserP
DCH/FACH User Throughput, Uplink acketThp / UtranCell.pmSamples
The PS Interactive DCH/FACH user DchUlRlcUserPacketThp
uplink throughput per UtranCell in a
measurement period of 15 minutes.
This KPI can be measured for a single
UtranCell and for all UtranCells under the
RNC.

84 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 15 Integrity KPIs


PintHS_I_DlTp_User Packet-Switched (PS) Interactive HS Hsdsch.pmSumHsDlRlcUserPack
User Throughput, Downlink. The PS etThp / Hsdsch.pmSamplesHsDl
Interactive HS user downlink throughput RlcUserPacketThp
per UtranCell in a measurement period
of 15 minutes.

21/1551-LZA 701 6012 Uen A | 2016-12-20 85


WCDMA Performance Management

Table 15 Integrity KPIs


PINTHS_I_DlTP_User HSDPA User Throughput (HsDschResources.pmSumA
_L1 ckedBitsSpi00 + HsDschReso
urces.pmSumAckedBitsSpi01
+ HsDschResources.pmSumA
ckedBitsSpi02 + HsDschReso
urces.pmSumAckedBitsSpi03
+ HsDschResources.pmSumA
ckedBitsSpi04 + HsDschReso
urces.pmSumAckedBitsSpi05
+ HsDschResources.pmSumA
ckedBitsSpi06 + HsDschReso
urces.pmSumAckedBitsSpi07
+ HsDschResources.pmSumA
ckedBitsSpi08 + HsDschReso
urces.pmSumAckedBitsSpi09
+ HsDschResources.pmSumA
ckedBitsSpi10 + HsDschReso
urces.pmSumAckedBitsSpi11
+ HsDschResources.pmSumA
ckedBitsSpi12 + HsDschReso
urces.pmSumAckedBitsSpi13
+ HsDschResources.pmSum
AckedBitsSpi14) / (0.002 * (
HsDschResources.pmSumN
onEmptyUserBuffersSpi00 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi01 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi02 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi03 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi04 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi05 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi06 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi07 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi08 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi09 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi10 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi11 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi12 +
HsDschResources.pmSumN
onEmptyUserBuffersSpi13 +
HsDschResources.pmSumNonE
mptyUserBuffersSpi14))
86 21/1551-LZA 701 6012 Uen A | 2016-12-20
RBS 6402 Counter and KPI details

Table 15 Integrity KPIs


PINTHS_I_DLTP_L1 HSDPA Cell Throughput Equation for a (HsDschResources.pmSumA
single Utran Cell given, the sum equation ckedBitsSpi00 + HsDschReso
for RNC is not given, only described in urces.pmSumAckedBitsSpi01
the text. + HsDschResources.pmSumA
ckedBitsSpi02 + HsDschReso
urces.pmSumAckedBitsSpi03
+ HsDschResources.pmSumA
ckedBitsSpi04 + HsDschReso
urces.pmSumAckedBitsSpi05
+ HsDschResources.pmSumA
ckedBitsSpi06 + HsDschReso
urces.pmSumAckedBitsSpi07
+ HsDschResources.pmSumA
ckedBitsSpi08 + HsDschReso
urces.pmSumAckedBitsSpi09
+ HsDschResources.pmSumA
ckedBitsSpi10 + HsDschReso
urces.pmSumAckedBitsSpi11
+ HsDschResources.pmSumA
ckedBitsSpi12 + HsDschReso
urces.pmSumAckedBitsSpi13
+ HsDschResources.pmSumA
ckedBitsSpi14 + HsDschReso
urces.pmSumAckedBitsSpi15)
/ (0.002 * (HsDschResource
s.pmNoActiveSubFrames +
HsDschResources.pmNoInactive
RequiredSubFrames))
PintEUL_I_UlTp_User Packet-Switched (PS) Interactive EUL Eul.pmSumEulRlcUserPacketThp
User Throughput, Uplink The PS / Eul.pmSamplesEulRlcUserPac
Interactive EUL user uplink throughput ketThp
per UtranCell in a measurement period
of 15 minutes.
PINTEUL10ms_I_ULT EUL 10 ms TTI User Throughput The EDchResources.pmSumAck
P_User_L1 EUL 10 ms TTI user throughput in kbps. edBitsCellEulTti10 / (0.01 *
EDchResources.pmNoActive10m
sFramesEul)
PINTEUL2ms_I_ULTP EUL 2 ms TTI User Throughput The EUL EDchResources.pmSumAckedBit
_User_L1 2 ms TTI user throughput in kbps. sCellEulTti2 / (0.002 * EDchResou
rces.pmNoActive2msFramesEul)
PINTEUL_I_ULTP_L1 EUL Cell Throughput The EUL cell (EDchResources.pmSumAckedBi
throughput in kbps. tsCellEulTti10 + EDchResource
s.pmSumAckedBitsCellEulTti2) /
(0.002 * EDchResources.pmNoA
ctive2msIntervalsEul)

21/1551-LZA 701 6012 Uen A | 2016-12-20 87


WCDMA Performance Management

Table 15 Integrity KPIs


PINTEUL10ms_I_ULT EUL 10 ms TTI Cell Throughput The EUL EDchResources.pmSumAck
P_L1 10 ms TTI cell throughput in kbps. edBitsCellEulTti10 / (0.01 *
EDchResources.pmNoActive10m
sIntervalsEulTti10)
PINTEUL2ms_I_ULTP EUL 2 ms TTI Cell Throughput The EUL EDchResources.pmSumAck
_L1 2 ms TTI cell throughput in kbps. edBitsCellEulTti2 / (0.002 *
EDchResources.pmNoActive2ms
IntervalsEulTti2)
Pstr64_I_DlTp_User Packet-Switched (PS) Streaming UtranCell.pmSumDlRlcUserThpP
DCH 64 User Throughput, Downlink sStream64 / UtranCell.pmSample
The PS Streaming DCH 64 user sDlRlcUserThpPsStream64
downlink throughput per UtranCell in a
measurement period of 15 minutes.
Pstr128_I_DlTp_User Packet-Switched (PS) Streaming UtranCell.pmSumDlRlcUserThpP
DCH 128 User Throughput, Downlink sStream128 / UtranCell.pmSampl
The PS Streaming DCH 128 user esDlRlcUserThpPsStream128
downlink throughput per UtranCell in a
measurement period of 15 minutes.
PstrHS_I_DlTp_User Packet-Switched (PS) Streaming HS UtranCell.pmSumDlRlcUserThpP
User Throughput, Downlink The PS sStreamHs / UtranCell.pmSample
Streaming HS user downlink throughput sDlRlcUserThpPsStreamHs
per UtranCell in a measurement period
of 15 minutes.
Pstr16_I_UlTp_User Packet-Switched (PS) Streaming DCH UtranCell.pmSumUlRlcUserThpP
16 User Throughput, Uplink The PS sStream16 / UtranCell.pmSample
Streaming DCH 16 user uplink throughput sUlRlcUserThpPsStream16
per UtranCell in a measurement period
of 15 minutes.
Pstr32_I_UlTp_User Packet-Switched (PS) Streaming DCH UtranCell.pmSumUlRlcUserThpP
32 User Throughput, Uplink The PS sStream32 / UtranCell.pmSample
Streaming DCH 32 user uplink throughput sUlRlcUserThpPsStream32
per UtranCell in a measurement period
of 15 minutes.
Pstr128_I_UlTp_User Packet-Switched (PS) Streaming UtranCell.pmSumUlRlcUserThpP
DCH 128 User Throughput, Uplink sStream128 / UtranCell.pmSampl
The PS Streaming DCH 128 user esUlRlcUserThpPsStream128
uplink throughput per UtranCell in a
measurement period of 15 minutes.
PintDCDCH_I_DlLat Packet-Switched (PS) Interactive 1000 * (RncFunction.pmSumDch
DCH/DCH Downlink Latency. The PS DchLatency / RncFunction.pmSa
Interactive DCH/DCH DL Latency per mplesDchDchLatency)
RncFunction in a measurement period of
15 minutes.

88 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 15 Integrity KPIs


PintDCHHS_I_DlLat Packet-Switched (PS) Interactive 1000 * (RncFunction.pmSumHsD
DCH/HS Downlink Latency The PS chLatency / RncFunction.pmSam
Interactive DCH/HS DL Latency per plesHsDchLatency)
RncFunction in a measurement period of
15.
PintEULHS_I_DlLat Packet-Switched (PS) Interactive EUL/HS 1000 * (RncFunction.pmSumHsE
Downlink Latency The PS Interactive ulLatency / RncFunction.pmSamp
EUL/HS DL Latency per RncFunction in a lesHsEulLatency)
measurement period of 15 minutes.
P_I_ChDSw_S Channel Downswitch Success Rate The 100 * (UtranCell.pmDownSwitch
channel downswitch success rate per Success / UtranCell.pmDownSw
UtranCell in a measurement period of 15 itchAttempt)
minutes.
P_I_ChUSw_S Channel Upswitch Success Rate The 100 * ((UtranCell.pmDlUpswitch
channel upswitch success rate per SuccessLow + UtranCell.pmUlU
UtranCell in a measurement period of 15 pswitchSuccessLow + UtranCell.
minutes. pmDlUpswitchSuccessMedium +
UtranCell.pmUlUpswitchSuccess
Medium + UtranCell.pmDlUpswitc
hSuccessHigh + UtranCell.pmUlU
pswitchSuccessHigh + UtranCell.
pmDlUpswitchSuccessHs + Utran
Cell.pmUlUpswitchSuccessEul) /
(UtranCell.pmDlUpswitchAttempt
Low + UtranCell.pmUlUpswitchAtt
emptLow + UtranCell.pmDlUpswit
chAttemptMedium + UtranCell.pm
UlUpswitchAttemptMedium + Utra
nCell.pmDlUpswitchAttemptHigh
+ UtranCell.pmUlUpswitchAttemp
tHigh + UtranCell.pmDlUpswitchA
ttemptHs + UtranCell.pmUlUpswit
chAttemptEul))
CBS_BMC_CTCH_I CBS message Integrity Failure rate to 100 * (UtranCell.pmNoDiscarded
submit CBS messages per cell. BmcCbsMsgs / UtranCell.pmNoA
ttScheduledBmcCbsMsgs)

4.2.4 Mobility KPIs


Table 16 Mobility KPIs

21/1551-LZA 701 6012 Uen A | 2016-12-20 89


WCDMA Performance Management

Table 16 Mobility KPIs


KPI Name Description Formula
AvgNoRlsPerUser Average Number of Radio Link Sets per (UtranCell.pmSumUesWith1Rls
User per UtranCell This metric measures 1RlInActSet / UtranCell.pmSam
the soft handover overhead that results in plesUesWith1Rls1RlInActSet +
multiple Iub and channel element usage UtranCell.pmSumUesWith1Rls
to supports calls within the reference 2RlInActSet / UtranCell.pmSam
UtranCell. plesUesWith1Rls2RlInActSet +
UtranCell.pmSumUesWith1Rls3
RlInActSet / UtranCell.pmSamp
lesUesWith1Rls3RlInActSet + 2
* (UtranCell.pmSumUesWith2R
ls2RlInActSet / UtranCell.pmSa
mplesUesWith2Rls2RlInActSet
+ UtranCell.pmSumUesWith2R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith2Rls3RlInActSet
+ UtranCell.pmSumUesWith2Rls
4RlInActSet / UtranCell.pmSam
plesUesWith2Rls4RlInActSet) +
3 * (UtranCell.pmSumUesWith3
Rls3RlInActSet / UtranCell.pmS
amplesUesWith3Rls3RlInActSet
+ UtranCell.pmSumUesWith3Rls
4RlInActSet / UtranCell.pmSam
plesUesWith3Rls4RlInActSet) +
4 * UtranCell.pmSumUesWith4R
ls4RlInActSet / UtranCell.pmSa
mplesUesWith4Rls4RlInActSet)
/ (UtranCell.pmSumUesWith1R
ls1RlInActSet / UtranCell.pmSa
mplesUesWith1Rls1RlInActSet
+ UtranCell.pmSumUesWith1R
ls2RlInActSet / UtranCell.pmSa
mplesUesWith1Rls2RlInActSet
+ UtranCell.pmSumUesWith1R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith1Rls3RlInActSet
+ UtranCell.pmSumUesWith2R
ls2RlInActSet / UtranCell.pmSa
mplesUesWith2Rls2RlInActSet
+ UtranCell.pmSumUesWith2R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith2Rls3RlInActSet
+ UtranCell.pmSumUesWith2R
ls4RlInActSet / UtranCell.pmSa
mplesUesWith2Rls4RlInActSet
+ UtranCell.pmSumUesWith3R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith3Rls3RlInActSet
+ UtranCell.pmSumUesWith3R
ls4RlInActSet / UtranCell.pmSa
mplesUesWith3Rls4RlInActSet +
UtranCell.pmSumUesWith4Rls4R
90 lInActSet
21/1551-LZA / UtranCell.pmSamples
701 6012 Uen A | 2016-12-20
UesWith4Rls4RlInActSet)
RBS 6402 Counter and KPI details

Table 16 Mobility KPIs


AvgNoRlPerUser Average Number of Radio Links per User 4 * ((UtranCell.pmSumUesWith2
per UtranCell This metric measures the Rls4RlInActSet / UtranCell.pmS
soft/softer handover overhead that results amplesUesWith2Rls4RlInActSet)
in multiple radio link usage to supports + (UtranCell.pmSumUesWith3R
calls within the reference UtranCell. ls4RlInActSet / UtranCell.pmSa
It measures the downlink power and mplesUesWith3Rls4RlInActSet)
channelization code overhead per user + (UtranCell.pmSumUesWith4R
per UtranCell. ls4RlInActSet / UtranCell.pmSa
mplesUesWith4Rls4RlInActSet))
+ (UtranCell.pmSumUesWith1Rl
s1RlInActSet / UtranCell.pmSam
plesUesWith1Rls1RlInActSet) +
2 * ((UtranCell.pmSumUesWith1
Rls2RlInActSet / UtranCell.pmS
amplesUesWith1Rls2RlInActSet)
+ (UtranCell.pmSumUesWith2Rl
s2RlInActSet / UtranCell.pmSam
plesUesWith2Rls2RlInActSet)) +
3 * ((UtranCell.pmSumUesWith1
Rls3RlInActSet / UtranCell.pmS
amplesUesWith1Rls3RlInActSet)
+ (UtranCell.pmSumUesWith2R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith2Rls3RlInActSet)
+ (UtranCell.pmSumUesWith3R
ls3RlInActSet / UtranCell.pmSa
mplesUesWith3Rls3RlInActSet))
/ ((UtranCell.pmSumUesWith1Rl
s1RlInActSet / UtranCell.pmSam
plesUesWith1Rls1RlInActSet) +
(UtranCell.pmSumUesWith1Rls
2RlInActSet / UtranCell.pmSam
plesUesWith1Rls2RlInActSet) +
(UtranCell.pmSumUesWith1Rls
3RlInActSet / UtranCell.pmSam
plesUesWith1Rls3RlInActSet) +
(UtranCell.pmSumUesWith2Rls
2RlInActSet / UtranCell.pmSam
plesUesWith2Rls2RlInActSet) +
(UtranCell.pmSumUesWith2Rls
3RlInActSet / UtranCell.pmSam
plesUesWith2Rls3RlInActSet) +
(UtranCell.pmSumUesWith2Rls
4RlInActSet / UtranCell.pmSam
plesUesWith2Rls4RlInActSet) +
(UtranCell.pmSumUesWith3Rls
3RlInActSet / UtranCell.pmSam
plesUesWith3Rls3RlInActSet) +
(UtranCell.pmSumUesWith3Rls
4RlInActSet / UtranCell.pmSam
plesUesWith3Rls4RlInActSet) +
(UtranCell.pmSumUesWith4Rls4
RlInActSet / UtranCell.pmSample
sUesWith4Rls4RlInActSet))
21/1551-LZA 701 6012 Uen A | 2016-12-20 91
WCDMA Performance Management

Table 16 Mobility KPIs


Sp_M_IFHO_S Inter Frequency Handover Success 100 * (UtranRelation.pmSuccNo
Rate for Speech The following metric nBlindInterFreqHoCsSpeech12 /
measures hard handover success rate UtranRelation.pmAttNonBlindInte
between frequencies in UtranRelation for rFreqHoCsSpeech12)
speech calls.
CS_M_IFHO_S Inter Frequency Handover Success Rate 100 * (UtranRelation.pmSuccNon
for CS Non-speech The following metric BlindInterFreqHoCsConversation
measures hard handover success rate al / UtranRelation.pmAttNonBlindI
between frequencies in UtranRelation for nterFreqHoCsConversational)
CS non-speech calls.
Pint64OrLess_M_IFH Inter Frequency Handover Success 100 * (UtranRelation.pm
O_S_CR Rate for PS Interactive Less than or SuccNonBlindInterFreq
Equal 64 The following metric measures HoPsInteractiveLess64 /
hard handover success rate between UtranRelation.pmAttNonBlind
frequencies in UtranRelation for PS InterFreqHoPsInteractiveLess64)
interactive calls with data rate less than
or equal 64kbps.
Pint64DCHPlus_M_IF Inter Frequency Handover Success Rate 100 * ((UtranRelation.pmSucc
HO_S_CR for PS Interactive Greater than 64 on NonBlindInterFreqHoPsInteract
DCH The following metric measures iveGreater64 - UtranRelation.p
hard handover success rate between mSuccNonBlindIfhoPsIntHs ) /
frequencies in UtranRelation for PS (UtranRelation.pmAttNonBlindIn
interactive calls with data rate on DCH terFreqPsInteractiveGreater64 -
larger than 64kbps. UtranRelation.pmAttNonBlindIfho
PsIntHs))
Pint64Plus_M_IFHO_ Inter Frequency Handover Success Rate 100 * (UtranRelation.pm
S_CR for PS Interactive Greater than 64 The SuccNonBlindInterFreqH
following metric measures hard handover oPsInteractiveGreater64 /
success rate between frequencies in UtranRelation.pmAttNonBlindInte
UtranRelation for PS interactive calls with rFreqHoPsInteractiveGreater64)
data rate larger than 64kbps.
Pint64HS_M_IFHO_S Inter Frequency Handover Success Rate 100 * (UtranRelation.pmSuccNon
_CR for PS Interactive HS The following metric BlindIfhoPsIntHs / UtranRelation.
measures hard handover success rate pmAttNonBlindIfhoPsIntHs)
between frequencies in UtranRelation for
PS interactive HS calls.
Pint64EUL_M_IFHO_ Inter Frequency Handover Success 100 * (UtranRelation.pmSuccNon
S_CR Rate for PS Interactive EUL The BlindIfhoPsIntEul / UtranRelation.
following metric measures hard handover pmAttNonBlindIfhoPsIntEul)
success rate between frequencies in
UtranRelation for PS interactive EUL
calls.

92 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 16 Mobility KPIs


PStrHS_M_IFHO_S_C Inter Frequency Handover Success Rate 100 * (UtranRelation.pmSuccNon
R for PS Streaming HS The following metric BlindIfhoPsStrHs / UtranRelation.
measures hard handover success rate pmAttNonBlindIfhoPsStrHs)
between frequencies in UtranRelation for
PS Streaming HS.
Str_M_IFHO_S_CR Inter Frequency Handover Success 100 * (UtranRelation.pmSuccNon
Rate for Streaming The following metric BlindInterFreqHoStreamingOther
measures hard handover success rate / UtranRelation.pmAttNonBlindInt
between frequencies in UtranRelation for erFreqHoStreamingOther)
Streaming.
Sp_M_IRATHO_GSM Inter Radio Access Technology (GSM) 100 * ((GsmRelation.pmNoSucce
_S_CR Handover Success Rate for Speech The ssOutIratHoSpeech + GsmRelatio
following metric measures hard handover n.pmNoSuccessOutSbHoSpeech
success rate between UtranCell and + GsmRelation.pmSuccLbhoSp
target GSM cell for speech calls. eech) / (GsmRelation.pmNoAtt
OutIratHoSpeech + GsmRelati
on.pmNoAttOutSbHoSpeech +
GsmRelation.pmAttLbhoSpeech))
CS_M_IRATHO_GSM Inter Radio Access Technology 100 * (GsmRelation.pmNoSucces
_S_CR (GSM) Handover Success Rate for sOutIratHoCs57 / GsmRelation.p
Circuit-Switched Streaming (CS 57) The mNoAttOutIratHoCs57)
following metric measures hard handover
success rate between UtranCell and
target GSM cell for CS streaming calls.
Multi_M_IRATHO_GS Inter Radio Access Technology (GSM) 100 * (GsmRelation.pmNoSucces
M_S_CR Handover Success Rate for Multi-RAB sOutIratHoMulti / GsmRelation.p
The following metric measures hard mNoAttOutIratHoMulti)
handover success rate between UtranCell
and target GSM cell for Multi-RAB calls.
Pint_M_IRATCC_GS Inter Radio Access Technology (GSM) 100 * (GsmRelation.pm
M_S_CR Cell Change Success Rate for PS NoOutIratCcSuccess /
Interactive The following metric measures GsmRelation.pmNoOutIratCcAtt)
cell change success rate between
UtranCell and target GSM cell for PS
calls when the UE successfully returns
to UtranCell.
PintDCH_M_IRATCC_ Inter Radio Access Technology (GSM) 100 * ((GsmRelation.pmNoOu
GSM_S_CR Cell Change Success Rate for PS tIratCcSuccess - GsmRelation
Interactive on DCH The following metric .pmNoOutIratCcSuccessHs) /
measures cell change success rate (GsmRelation.pmNoOutIratCcAtt
between UtranCell and target GSM - GsmRelation.pmNoOutIratCcA
cell for PS calls on DCH when the UE ttHs))
successfully returns to UtranCell.

21/1551-LZA 701 6012 Uen A | 2016-12-20 93


WCDMA Performance Management

Table 16 Mobility KPIs


PintHS_M_IRATCC_G Inter Radio Access Technology (GSM) 100 * (GsmRelation.pmNoOutIrat
SM_S_CR Cell Change Success Rate for PS CcSuccessHs / GsmRelation.pm
Interactive on HS The following metric NoOutIratCcAttHs)
measures cell change success rate
between UtranCell and target GSM
cell for PS calls on HS when the UE
successfully returns to UtranCell.
PintEUL_M_IRATCC_ Inter Radio Access Technology (GSM) 100 * (GsmRelation.pmNoOutIrat
GSM_S_CR Cell Change Success Rate for PS CcSuccessEul / GsmRelation.pm
Interactive on EUL The following metric NoOutIratCcAttEul)
measures cell change success rate
between UtranCell and target GSM
cell for PS calls on EUL when the UE
successfully returns to UtranCell.
Str_M_incIRATHO_LT Inter Radio Access Technology (LTE) 100 * (UtranCell.pmN
E_S_CR Handover Success Rate for PS Streaming oInIratHoSuccPsstr /
This metric measures hard handover UtranCell.pmNoInIratHoAttPsstr)
success rate between LTE and target
Utran Cell for PS streaming.
Str128_M_incIRATHO Inter Radio Access Technology (LTE) 100 * (UtranCell.pmNoInIratHoSu
_LTE_S_CR Handover Success Rate for PS Streaming ccPsstr128 / UtranCell.pmNoInIra
128 This metric measures hard handover tHoAttPsstr128)
success rate between LTE and target
UtranCell for PS streaming 128.
StrHS_M_incIRATHO Inter Radio Access Technology (LTE) 100 * (UtranCell.pmNoInIratHoSu
_LTE_S_CR Handover Success Rate for PS Streaming ccPsstrHS / UtranCell.pmNoInIra
HS This metric measures hard handover tHoAttPsstrHS)
success rate between LTE and target
UtranCell for PS streaming HS
Int_M_incIRATHO_LT Inter Radio Access Technology (LTE) 100 * (UtranCell.pmN
E_S_CR Handover Success Rate for PS oInIratHoSuccPsint /
Interactive This metric measures cell UtranCell.pmNoInIratHoAttPsint)
change success rate between LTE and
target UtranCell for PS calls when the UE
successfully returns to UtranCell
IntHS_M_incIRATHO_ Inter Radio Access Technology (LTE) 100 * (UtranCell.pmNoInIratHoSu
LTE_S_CR Handover Success Rate for PS Interactive ccPsintHS / UtranCell.pmNoInIra
HS The following metric measures cell tHoAttPsintHS)
change success rate between LTE and
target Utran Cell for PS calls on HS when
the UE successfully returns to UtranCell

94 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 16 Mobility KPIs


IntEUL_M_incIRATHO Inter Radio Access Technology (LTE) 100 * (UtranCell.pmNoInIratHoSu
_LTE_S_CR Handover Success Rate for PS Interactive ccPsintEUL / UtranCell.pmNoInIr
EUL The following metric measures cell atHoAttPsintEUL)
change success rate between LTE and
target Utran Cell for PS calls on EUL
when the UE successfully returns to
UtranCell.
IntnonHS_M_incIRAT Inter Radio Access Technology (LTE) 100 * (UtranCell.pmNoInIratHoSu
HO_LTE_S_CR Handover Success Rate for PS Interactive ccPsintnonHS / UtranCell.pmNoIn
non-HS The following metric measures IratHoAttPsintnonHS)
cell change success rate between LTE
and target UtranCell for PS calls on
non-HS when the UE successfully returns
to UtranCell
Sp_M_incIRATHO_S_ Inter Radio Access Technology 100 * (UtranCell.pmNoInIratHoSu
CR (GSM/LTE) Handover Success Rate ccSpeech / UtranCell.pmNoInIrat
for speech. This metric measures HoAttSpeech)
hard handover success rate between
GSM/LTE and target UtranCell for
speech.
Sp_M_IRATHO_GAN Inter Radio Access Technology (GAN) 100 * (UtranCell.pmNoOutGanIrat
_S Handover Success Rate for Speech Hard HoSuccSpeech / UtranCell.pmNo
handover success rate per UtranCell for OutGanIratHoAttSpeech)
speech calls.
Multi_M_IRATHO_GA Inter Radio Access Technology (GAN) 100 * (UtranCell.pmNoOutGanIrat
N_S Handover Success Rate for Multi-RAB HoSuccMulti / UtranCell.pmNoOu
Hard handover success rate per UtranCell tGanIratHoAttMulti)
for Multi-RAB calls.
PInt_M_IRATCC_GAN Inter Radio Access Technology (GAN) 100 * (UtranCell.pmN
_S Handover Success Rate for PS Interactive oOutGanIratCcSucc /
Cell change success rate per UtranCell UtranCell.pmNoOutGanIratCcAtt)
for PS calls.
PIntDCH_M_IRATCC Inter Radio Access Technology (GAN) 100 * ((UtranCell.pmNoOut
_GAN_S Cell Change Success Rate for PS GanIratCcSucc - UtranCell.p
Interactive on DCH Cell change success mNoOutGanIratCcSuccHs) /
per UtranCell for PS calls on DCH. (UtranCell.pmNoOutGanIratCcAtt
- UtranCell.pmNoOutGanIratCcA
ttHs))
PIntHS_M_IRATCC_G Inter Radio Access Technology (GAN) 100 * (UtranCell.pmNoOutGanIra
AN_S Cell Change Success Rate for PS tCcSuccHs / UtranCell.pmNoOut
Interactive on HS Cell change success GanIratCcAttHs)
rate per UtranCell for PS calls on HS.

21/1551-LZA 701 6012 Uen A | 2016-12-20 95


WCDMA Performance Management

Table 16 Mobility KPIs


PIntEUL_M_IRATCC_ Inter Radio Access Technology (GAN) 100 * (UtranCell.pmNoOutGanIrat
GAN_S Cell Change Success Rate for PS CcSuccEul / UtranCell.pmNoOut
Interactive on EUL Cell change success GanIratCcAttEul)
rate per UtranCell for PS calls on EUL.
Pint_M_HSCC_S PS Interactive HS Cell Change success 100 * (UtranCell.pmNoHsCcSucc
rate The following metric measures the ess / UtranCell.pmNoHsCcAttem
success rate for HS Cell Change in target pt)
cell.
Pstr_M_HSCC_S PS Streaming HS Cell Change success 100 * (UtranCell.pmNoPsStream
rate The following metric measures the HsCcSuccess / UtranCell.pmNoP
success rate for HS Cell Change in target sStreamHsCcSuccess)
cell.
Pint_M_HStoDCHRC_ PS Interactive reconfiguration HS to 100 * (UtranCell.pmHsToDchSu
S DCH success rate The following metric ccess / UtranCell.pmHsToDchA
measures the success rate for HS to ttempt)
DCH reconfiguration.
Pstr_M_HStoDCHRC_ PS Streaming reconfiguration HS to 100 * (UtranCell.pmPsStreamHsT
S DCH success rate The following metric oDchSuccess / UtranCell.pmPsSt
measures the success rate for HS to reamHsToDchAttempt)
DCH reconfiguration.
PS_M_EULCC_S PS Interactive EUL Cell Change success 100 * (UtranCell.pmNoEulCcSuc
rate The following metric measures the cess / UtranCell.pmNoEulCcAtte
success rate for EUL Cell Change in mpt)
target cell.
PS_M_EULtoDCHRC PS Interactive reconfiguration EUL to 100 * (UtranCell.pm
_S DCH success rate The following metric EulToDchSuccess /
measures the success rate for EUL to UtranCell.pmEulToDchAttempt)
DCH reconfiguration.
Ura_M_Upd_S URA Update success rate The following 100 * (UtranCell.pm
metric measures the URA Update NoUraUpdSuccess /
success rate. UtranCell.pmNoUraUpdAttempt)
Sp_M_CNHHOIn_S Core Network Hard Handover success 100 * (IurLink.pmNoSuccIncCnhh
rate speech, incoming calls The following oSpeech / IurLink.pmNoAttIncCn
metric measures the Core Network hard hhoSpeech)
handover success rate for incoming
speech calls.
Sp_M_CNHHOOut_S Core Network Hard Handover success 100 * (UtranRelation.pmNoSuccO
rate speech, outgoing calls The following utCnhhoSpeech / UtranRelation.p
metric measures the Core Network hard mNoAttOutCnhhoSpeech)
handover success rate for outgoing
speech calls.

96 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 16 Mobility KPIs


CS_M_CNHHOIn_S Core Network Hard Handover success 100 * (UtranRelation.pmNoS
rate CS other than speech, incoming calls uccIncCnhhoCsNonSpeech /
The following metric measures the Core UtranRelation.pmNoAttOutCnhho
Network hard handover success rate for CsNonSpeech)
incoming speech calls.
CS_M_CNHHOOut_S Core Network Hard Handover success 100 * (UtranRelation.pmNoS
rate CS other than speech, outgoing calls uccOutCnhhoCsNonSpeech /
The following metric measures the Core UtranRelation.pmNoAttOutCnhho
Network hard handover success rate for CsNonSpeech)
outgoing speech calls.

4.2.5 Availability KPIs


Table 17 Availability KPIs
KPI Name Description Formula
AV_CELL_HS Cell HS Availability The length of time Hsdsch.pm_count * RESOLUTION
in seconds that a cell is available _SEC
for Packet Interactive HS service
is defined as cell HS availability.
For the definiton of pm_count,
see Section 3.6 in Definitions and
Explanations. RESOLUTION_SEC is
900=15min*60sec.
Av_Man_EUL Cell EUL Unavailability due to Planned 100 * (Eul.pmEulDowntimeMan /
Down Time The length of time in AV_CELL_EUL)
seconds that a cell is unavailable
for EUL service due to maintenance
is called planned EUL downtime.
This period can be measured by
Eul.pmEulDowntimeMan in seconds.

21/1551-LZA 701 6012 Uen A | 2016-12-20 97


WCDMA Performance Management

Table 17 Availability KPIs


Av_Auto_EUL Cell EUL Unavailability due to 100 * (Eul.pmEulDowntimeAuto /
Unplanned Down Time The length AV_CELL_EUL)
of time in seconds that a cell is
unavailable for EUL service due
to malfunction is called unplanned
EUL downtime. This period can be
measured by Eul.pmEulDowntimeAuto
in seconds. This counter actually
measures the time that the cell has
been unavailable for EUL service
because the system considers the cell
as unlocked but down. Since the cell
may take up to 2 seconds to become
fully enabled after being unlocked,
Eul.pmEulDowntimeAuto may also
include this extra time which is not due
to malfunction, but rather a side-effect
of planned downtime.
AV_CELL_EUL Cell EUL Availability The length Eul.pm_count * RESOLUTION_SEC
of time in seconds that a cell
is available for EUL service is
defined as cell EUL availability.For
the definiton of pm_count, see
Section 3.6 in Definitions and
Explanations. RESOLUTION_SEC is
900=15min*60sec.
Av_Man_HS Cell HS Unavailability due to Planned 100 * (Hsdsch.pmHsDowntimeMan
Down Time The length of time in / AV_CELL_HS)
seconds that a cell is unavailable
for HS service due to maintenance
is called planned HS downtime.
This period can be measured by
Hsdsch.pmHsDowntimeMan in
seconds.

98 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 17 Availability KPIs


Av_Auto_HS Cell HS Unavailability due to 100 * (Hsdsch.pmHsDowntimeAuto
Unplanned Down Time The length of / AV_CELL_HS)
time in seconds that a cell is unavailable
for HS service due to malfunction is
called unplanned HS downtime.
This period can be measured by
Hsdsch.pHsDowntimeAuto in seconds.
This counter actually measures
the time that the cell has been
unavailable for HS service because
the system considers the cell as
unlocked but down. Since the cell
may take up to 2 seconds to become
fully enabled after being unlocked,
Hsdsch.pHsDowntimeAuto may also
include this extra time which is not due
to malfunction, but rather a side-effect
of planned downtime.
AV_CELL Accumulated elapsed time UtranCell.pm_count *
for all existing cells, [sec]. RESOLUTION_SEC
RESOLUTION_SEC is
900=15min*60sec. For the definiton
of pm_count, see Section 3.6 in
Definitions and Explanations.
AV_MAN Cell Unavailability due to Planned Down 100 * (UtranCell.pmCellDowntimeM
Time The length of time in seconds that an / AV_CELL)
a cell is unavailable due to maintenance
is called planned downtime. This
period can be measured by
UtranCell.pmCellDowntimeMan in
seconds.

21/1551-LZA 701 6012 Uen A | 2016-12-20 99


WCDMA Performance Management

Table 17 Availability KPIs


AV_AUTO Cell Unavailability due to Unplanned 100 * (UtranCell.pmCellDowntimeA
Down Time The length of time in uto / AV_CELL)
seconds that a cell is unavailable
due to malfunction is called
unplanned downtime. This
period can be measured by
UtranCell.pmCellDowntimeAuto
in seconds. This counter actually
measures the time that the cell
has been unavailable because the
system has considered the cell as
unlocked but down. Since the cell
may take up to 2 seconds to become
fully enabled after being unlocked,
UtranCell.pmCellDowntimeAuto may
also include this extra time which is
not due to malfunction, but rather a
side-effect of planned downtime.
AV_DL_Cong The ratio of Time cells congested due 100 * (1 - UtranCell.pmTotalTimeD
to power DL. lCellCong / AV_CELL)
AV_UL_Cong The ratio of Time cells congested due 100 * (1 - UtranCell.pmTotalTimeU
to power UL. lCellCong / AV_CELL)
AV Cell Availability The length of time in 100 * (1 - (UtranCell.pmCellDo
seconds that a cell is available for wntimeAuto + UtranCell.pmTota
service is defined as cell availability. lTimeDlCellCong) / (AV_CELL -
UtranCell.pmCellDowntimeAuto UtranCell.pmCellDowntimeMan))
measures the length of time in seconds
during which a cell is unavailable for
service due to an unplanned downtime
and UtranCell.pmCellDowntimeMan
measures the length of time in seconds
during which a cell is unavailable for
service due to a planned downtime.
AV_TPS Cell Unavailability due to Traffic Aware 100 * (UtranCell.pmCellDowntimeTp
Power Save-triggered Down Time The s / AV_CELL)
length of time in seconds that a cell
is unavailable due to Traffic Aware
Power Save-triggered power lock
is called Traffic Aware Power Save
downtime or power save downtime.
This period can be measured by
UtranCell.pmCellDowntimeTps in
seconds.

100 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

4.2.6 Call Completion Success Rate (CCSR) KPIs


Table 18 Call Completion Success Rate (CCSR) KPIs
KPI Name Description Formula
Sp_C Circuit-Switched (CS) Speech CCSR Sp_A * (1 - (Sp_R_D / 100))
The call completion success rate per
UtranCell for speech.
CS64_C Circuit-Switched (CS) 64 CCSR The CS64_A * (1 - (CS64_R_D / 100))
call completion success rate per
UtranCell for CS 64.
CS57_C Circuit-Switched (CS) 57 CCSR The CS57_A * (1 - (CS57_R_D / 100))
call completion success rate per
UtranCell for CS 57.
PStr64_C Packet-Switched (PS) Streaming 64 PStr64_A * (1 - (PStr64_R_D / 100))
CCSR The call completion success
rate per UtranCell for PS Streaming 64.
PStr128_C Packet-Switched (PS) Streaming 128 PStr128_A * (1 - (PStr128_R_D /
CCSR The call completion success 100))
rate per UtranCell for PS Streaming
128.
PStrHS_C Packet-Switched (PS) Streaming HS PStrHS_A * (1 - (PStrHS_R_D /
CCSR The call completion success 100))
rate per UtranCell for PS Streaming
HS.
Pint_C Packet-Switched (PS) Interactive Pint_A * (1 - (Pint_R_D / 100))
CCSR Since call completion for packet
data services from user perspective is
completing its service and temporary
interruption may be recovered by
higher layer due to retransmission,
the packet call completion rate per
UtranCell could be approximated from
user perspective with this equation.

21/1551-LZA 701 6012 Uen A | 2016-12-20 101


WCDMA Performance Management

4.2.7 System Utilization KPIs

Table 19 System Utilization KPIs


KPI Name Description Formula
Sp_U_User Average Number of Circuit-Switched (UtranCell.pmSumBestCs12Esta
(CS) Speech Users The average blish / UtranCell.pmSamplesBest
number of speech users per UtranCell Cs12Establish) + (UtranCell.pmS
in a measurement period of 15 minutes. umBestAmr12200RabEstablish /
UtranCell.pmSamplesBestAmr12
200RabEstablish) + (UtranCell.p
mSumBestAmr7950RabEstablish
/ UtranCell.pmSamplesBestAmr7
950RabEstablish) + (UtranCell.p
mSumBestAmr5900RabEstablish
/ UtranCell.pmSamplesBestAmr5
900RabEstablish) + (UtranCell.p
mSumBestAmr4750RabEstablish
/ UtranCell.pmSamplesBestAmr4
750RabEstablish) + (UtranCell.p
mSumBestAmrWbRabEstablish /
UtranCell.pmSamplesBestAmrW
bRabEstablish) + (UtranCell.pmS
umBestAmrNbMmRabEstablish /
UtranCell.pmSamplesBestAmrNbM
mRabEstablish)
Sp_U_Tot Circuit-Switched (CS) Speech (UtranCell.pmSumCs12RabEstabl
Downlink Code Utilization The average ish / UtranCell.pmSamplesCs12Ra
number of downlink code is occupied bEstablish) + (UtranCell.pmSumA
for speech traffic per UtranCell in a mr12200RabEstablish / UtranCell.p
measurement period of 15 minutes. mSamplesAmr12200RabEstablish)
+ (UtranCell.pmSumAmr7950RabE
stablish / UtranCell.pmSamplesAm
r7950RabEstablish) + (UtranCell.p
mSumAmr5900RabEstablish / (2 *
UtranCell.pmSamplesAmr5900Rab
Establish)) + (UtranCell.pmSumAm
r4750RabEstablish / (2 * UtranCell.
pmSamplesAmr4750RabEstablish))
+ (UtranCell.pmSumAmrWbRabE
stablish / UtranCell.pmSamplesA
mrWbRabEstablish) + (UtranCell.
pmSumAmrNbMmRabEstablish /
UtranCell.pmSamplesAmrNbMmR
abEstablish)

102 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 19 System Utilization KPIs


Sp_U_Prim Circuit-Switched (CS) Speech Erlang (UtranCell.pmSumBestCs12Esta
The average speech traffic Erlang blish / UtranCell.pmSamplesBest
carried per UtranCell in one hour. Cs12Establish) + (UtranCell.pmS
umBestAmr12200RabEstablish /
UtranCell.pmSamplesBestAmr12
200RabEstablish) + (UtranCell.p
mSumBestAmr7950RabEstablish
/ UtranCell.pmSamplesBestAmr7
950RabEstablish) + (UtranCell.p
mSumBestAmr5900RabEstablish
/ UtranCell.pmSamplesBestAmr5
900RabEstablish) + (UtranCell.p
mSumBestAmr4750RabEstablish
/ UtranCell.pmSamplesBestAmr4
750RabEstablish) + (UtranCell.p
mSumBestAmrWbRabEstablish /
UtranCell.pmSamplesBestAmrW
bRabEstablish) + (UtranCell.pmS
umBestAmrNbMmRabEstablish /
UtranCell.pmSamplesBestAmrNbM
mRabEstablish)
CS57_U_User Circuit-Switched (CS) 57 Users The UtranCell.pmSumBestCs57RabEst
average number of CS 57 users per ablish / UtranCell.pmSamplesBestC
UtranCell. s57RabEstablish
CS57_U_Tot Circuit-Switched (CS) 57 Downlink UtranCell.pmSumCs57RabEstablis
Code Utilization The average number h / UtranCell.pmSamplesCs57RabE
of downlink code is occupied for CS 57 stablish
traffic per UtranCell in a measurement
period of 15 minutes.
CS57_U_Prim Circuit-Switched (CS) 57 Erlang The UtranCell.pmSumCs57RabEstablis
average Circuit-Switched 57 traffic h / UtranCell.pmSamplesCs57RabE
Erlang carried per UtranCell in one stablish
hour.
CS64_U_User Circuit-Switched (CS) 64 Users The UtranCell.pmSumBestCs64RabEst
average number of CS 64 users per ablish / UtranCell.pmSamplesBestC
UtranCell. s64RabEstablish
CS64_U_Tot Circuit-Switched (CS) 64 Downlink UtranCell.pmSumCs64RabEstablis
Code Utilization The average number h / UtranCell.pmSamplesCs64RabE
of downlink code is occupied for CS 64 stablish
traffic per UtranCell in a measurement
period of 15 minutes.
CS64_U_Prim Circuit-Switched (CS) 64 Erlang The UtranCell.pmSumCs64RabEstablis
average Circuit-Switched 64 traffic h / UtranCell.pmSamplesCs64RabE
Erlang carried per UtranCell in one stablish
hour.

21/1551-LZA 701 6012 Uen A | 2016-12-20 103


WCDMA Performance Management

Table 19 System Utilization KPIs


Pint_U_User PS Interactive Users The average (UtranCell.pmSumBestDchPsIntR
number of PS Interactive users, abEstablish / UtranCell.pmSamp
excluding URA_PCH, per UtranCell. lesBestDchPsIntRabEstablish) +
(UtranCell.pmSumBestPsHsAdch
RabEstablish / UtranCell.pmSamp
lesBestPsHsAdchRabEstablish) +
(UtranCell.pmSumBestPsEulRabE
stablish / UtranCell.pmSamplesBe
stPsEulRabEstablish) + (UtranCel
l.pmSumFachPsIntRabEstablish /
UtranCell.pmSamplesFachPsIntRab
Establish)
Ura_U_User URA_PCH Users The average number Ura.pmSumRabUra /
of URA_PCH Users per URA. Ura.pmSamplesRabUra
PintFach_U_User PS Interactive FACH Users The UtranCell.pmSumFachPsIntRabEst
average number of PS Interactive ablish / UtranCell.pmSamplesFachP
FACH users per UtranCell, excluding sIntRabEstablish
HS-FACH users.
PintHsFach_U_User PS Interactive HS-FACH Users The UtranCell.pmSumHsFachPsIntRab
average number of PS Interactive Est / UtranCell.pmSamplesHsFach
HS-FACH users per UtranCell. PsIntRabEst
PintEulFach_U_User PS Interactive EUL-FACH Users The UtranCell.pmSumEulFachPsIntRab
average number of PS Interactive Est / UtranCell.pmSamplesEulFach
EUL-FACH users per UtranCell. PsIntRabEst
PintDCH_U_User PS Interactive DCH Users The average UtranCell.pmSumBestDchPsIntRab
number of PS Data Interactive DCH Establish / UtranCell.pmSamplesBe
users per UtranCell. stDchPsIntRabEstablish
PintHs_U_User PS Interactive HS Users The average (UtranCell.pmSumBestPsHsAdch
number of PS Interactive HS users per RabEstablish / UtranCell.pmSamp
UtranCell. lesBestPsHsAdchRabEstablish) +
(UtranCell.pmSumBestPsEulRabEs
tablish / UtranCell.pmSamplesBestP
sEulRabEstablish)
PintHs_U_Conn PS Interactive HS Connections The UtranCell.pmSumHsConnServ /
average number of PS Interactive HS UtranCell.pmSamplesHsConnServ
connections per UtranCell.
PintEul_U_User PS Interactive EUL Users The average UtranCell.pmSumBestPsEulRabEst
number of PS Interactive EUL users ablish / UtranCell.pmSamplesBestP
per UtranCell. sEulRabEstablish
PintEul2ms_U_User PS Interactive EUL 2ms TTI Users The UtranCell.pmSumBestPsIntEulTti2R
average number of PS Interactive EUL abEst/UtranCell.pmSamplesBestPsI
2ms TTI users per UtranCell. ntEulTti2RabEst

104 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 19 System Utilization KPIs


Pstr64_U_User PS Streaming 64 Users The average UtranCell.pmSumBestPsStr64Ps8R
number of PS Streaming 64 users per abEstablish / UtranCell.pmSamples
UtranCell. BestPsStr64Ps8RabEstablish
Pstr128_U_User PS Streaming 128 Users The average UtranCell.pmSumBestPsStr128Ps8
number of PS Streaming 128 users per RabEstablish / UtranCell.pmSample
UtranCell. sBestPsStr128Ps8RabEstablish
PstrHS_U_User PS Streaming HS Users The average UtranCell.pmSumBestPsStreamHs
number of PS Streaming HS users per RabEst / UtranCell.pmSamplesBest
UtranCell. PsStreamHsRabEst
SRBOnly34_U_User SRB Only 3.4 Users The average UtranCell.pmSumBestSrbOnly34 /
number of SRB only 3.4 users per UtranCell.pmSamplesBestSrbOnly
UtranCell. 34
SRBOnly34_U_Tot SRB Only 3.4 Downlink Code Utilization UtranCell.pmSumSrbOnly34 /
The average number of downlink code UtranCell.pmSamplesSrbOnly34
is occupied for SRB only 3.4 per
UtranCell in a measurement period of
15 minutes.
SRBOnly34_U_Prim SRB Only 3.4 Erlang The average SRB UtranCell.pmSumBestSrbOnly34 /
only 3.4 Erlang carried per UtranCell UtranCell.pmSamplesBestSrbOnly
in one hour. 34
SRBOnly136_U_User SRB Only 13.6 Users The average UtranCell.pmSumBestRrcOnlyEstab
number of SRB only 13.6 users per lish / UtranCell.pmSamplesBestRrc
UtranCell. OnlyEstablish
SRBOnly136_U_Tot SRB Only 13.6 Downlink Code UtranCell.pmSumRrcOnlyEstablish
Utilization The average number of / UtranCell.pmSamplesRrcOnlyEst
downlink code is occupied for SRB only ablish
13.6 per UtranCell in a measurement
period of 15 minutes.
SRBOnly136_U_Prim SRB Only 13.6 Erlang The average UtranCell.pmSumBestRrcOnlyEstab
SRB only 13.6 Erlang carried per lish / UtranCell.pmSamplesBestRrc
UtranCell in one hour. OnlyEstablish
SRBOnlyHS_U_User SRB Only HS Users The average (UtranCell.pmSumBestSrbOnlyHs /
number of SRB only HS users per UtranCell.pmSamplesBestSrbOnlyH
UtranCell. s) + (UtranCell.pmSumBestSrbOnl
yEul / UtranCell.pmSamplesBestSr
bOnlyEul)
SRBOnlyEUL_U_User SRB Only EUL Users The average UtranCell.pmSumBestSrbOnlyEul /
number of SRB only EUL users per UtranCell.pmSamplesBestSrbOnlyE
UtranCell. ul

21/1551-LZA 701 6012 Uen A | 2016-12-20 105


WCDMA Performance Management

Table 19 System Utilization KPIs


Sp_A_GoS Grade of Service for Circuit-Switched 100 * (1 - (1 - Rrc_Blocking_CS) * (1
(CS) Speech The GoS rate for Speech - Rab_Blocking_Speech))
per UtranCell due to RN admission
blocking, TN congestion or TN failure.
The GoS or blocking probability can
be used together with Erlang metric to
measure the cell capacity for a given
service. Since a cell serves a mixed
traffic, this measure must be used
with respect to the amount of traffic
measured for other services. UniSaal
congestion will be double counted
since it is included in the 2 counters
used to measure the RRC blocking.
Rrc_Blocking_CS Rrc Blocking CS The GoS or blocking (UtranCell.pmNoRrcCsReqDeniedA
probability can be used together with dm + UtranCell.pmNoRrcConnReqB
Erlang metric to measure the cell lockTnCs - UtranCell.pmNoLoadSh
capacity for a given service. Since a aringRrcConnCs) / (UtranCell.pmTo
cell serves a mixed traffic, this measure tNoRrcConnectReqCs - UtranCell.p
must be used with respect to the mNoLoadSharingRrcConnCs)
amount of traffic measured for other
services. UniSaal congestion will be
double counted since it is included in
the 2 counters used to measure the
RRC blocking.
Rrc_Blocking_Speech Rrc Blocking Speech The GoS or (UtranCell.pmNoOfNonHoReqDenie
blocking probability can be used dSpeech + UtranCell.pmNoRabEst
together with Erlang metric to measure BlockTnSpeechBest) / UtranCell.pm
the cell capacity for a given service. NoRabEstablishAttemptSpeech
Since a cell serves a mixed traffic, this
measure must be used with respect
to the amount of traffic measured for
other services. UniSaal congestion will
be double counted since it is included
in the 2 counters used to measure the
RRC blocking.
Rab_Blocking_Speech RAB Blocking Speech (UtranCell.pmNoOfNonHoReqDenie
dSpeech + UtranCell.pmNoRabEst
BlockTnSpeechBest) / UtranCell.pm
NoRabEstablishAttemptSpeech
CS_A_GoS Grade of Service for Circuit-Switched 100 * (1 - (1 - Rrc_Blocking_CS) * (1
(CS) 64 and 57 The GoS rate for both - Rab_Blocking_CS))
CS 64 and 57 calls per UtranCell due to
RN admission blocking, TN congestion
or TN failure.

106 21/1551-LZA 701 6012 Uen A | 2016-12-20


RBS 6402 Counter and KPI details

Table 19 System Utilization KPIs


Rab_Blocking_CS RAB Blocking CS The GoS or blocking UtranCell.pmNoOfNonHoReqDenie
probability can be used together with dCs + ((UtranCell.pmNoRabEstBlo
Erlang metric to measure the cell ckTnCs57Best + UtranCell.pmNoR
capacity for a given service. Since a abEstBlockTnCs64Best) / (UtranC
cell serves a mixed traffic, this measure ell.pmNoRabEstablishAttemptCs64
must be used with respect to the + UtranCell.pmNoRabEstablishAtte
amount of traffic measured for other mptCs57))
services. UniSaal congestion will be
double counted since it is included in
the 2 counters used to measure the
RRC blocking.
Pint_A_GoS Grade of Service for Packet-Switched 100 * (1 - (1 - Rrc_Blocking_PsInt) *
Interactive The blocking rate for PS (1 - Rab_Blocking_PsInt))
interactive calls per UtranCell due to
RN admission blocking, TN congestion
or TN failure. The GoS or blocking
probability can be used together with
Erlang metric to measure the cell
capacity for a given service. Since a
cell serves a mixed traffic, this measure
must be used with respect to the
amount of traffic measured for other
services. UniSaal congestion will be
double counted since it is included in
the 2 counters used to measure the
RRC blocking.
Rrc_Blocking_PsInt Rrc Blocking PsInt The GoS or blocking (UtranCell.pmNoRrcPsReqDeniedA
probability can be used together with dm + UtranCell.pmNoRrcConnReq
Erlang metric to measure the cell BlockTnPs) / UtranCell.pmTotNoRr
capacity for a given service. Since a cConnectReqPs
cell serves a mixed traffic, this measure
must be used with respect to the
amount of traffic measured for other
services. UniSaal congestion will be
double counted since it is included in
the 2 counters used to measure the
RRC blocking.

21/1551-LZA 701 6012 Uen A | 2016-12-20 107


WCDMA Performance Management

Table 19 System Utilization KPIs


Rab_Blocking_PsInt Rab Blocking PsInt The GoS or (UtranCell.pmNoOfNonHoReqDe
blocking probability can be used niedInteractive + UtranCell.pmNo
together with Erlang metric to measure RabEstBlockTnPsIntNonHsBest +
the cell capacity for a given service. UtranCell.pmNoRabEstBlockTnPsIn
Since a cell serves a mixed traffic, this tHsBest) / UtranCell.pmNoRabEsta
measure must be used with respect blishAttemptPacketInteractive
to the amount of traffic measured for
other services. UniSaal congestion will
be double counted since it is included
in the 2 counters used to measure the
RRC blocking.
PStrDCH_A_GoS Grade of Service for Packet-Switched 100 * ((UtranCell.pmNoOfNonHoRe
Streaming DCH The blocking rate for qDeniedPsStreaming + UtranCell.p
PS streaming DCH calls per UtranCell mNoOfNonHoReqDeniedPsStr128
due to RN admission blocking, TN + UtranCell.pmNoRabEstBlockTnP
congestion or TN failure. The GoS sStrNonHsBest) / (UtranCell.pmNo
or blocking probability can be used RabEstablishAttemptPacketStream
together with Erlang metric to measure + UtranCell.pmNoRabEstablishAtte
the cell capacity for a given service. mptPacketStream128))
Since a cell serves a mixed traffic, this
measure must be used with respect
to the amount of traffic measured for
other services.
PStrHS_A_GoS Grade of Service for Packet-Switched 100 * ((UtranCell.pmNorabE
Streaming HS The blocking rate for stBlockRnBestPsStreamHs +
PS streaming HS calls per UtranCell UtranCell.pmNoRabEstBlockTnPsS
due to RN admission blocking, TN treamHsBest) / UtranCell.pmNoRab
congestion or TN failure. The GoS EstAttemptPsStreamHs)
or blocking probability can be used
together with Erlang metric to measure
the cell capacity for a given service.
Since a cell serves a mixed traffic, this
measure must be used with respect
to the amount of traffic measured for
other services.
Hs_U_MHT HS Mean Holding Time The average RESOLUTION_SEC * pm_count
Mean Holding Time for HSDPA *((UtranCell.pmSumHsConnServ /
connections (UE connections with UtranCell.pmSamplesHsConnServ)
at least one PS RAB mapped on a / (UtranCell.pmNormalReleaseHsCo
DCH/HS or EUL/HS Radio Bearer). nn + UtranCell.pmSystemReleaseH
sConn + UtranCell.pmNormalRelM
ultiHsConnToSpeech + UtranCell.p
mSystemRelMultiHsConnToSpeech
+ UtranCell.pmReconfSuccOrigHsC
onn))

108 21/1551-LZA 701 6012 Uen A | 2016-12-20

Potrebbero piacerti anche