Professional Documents
Culture Documents
Singleran Kpi Reference (v900r013c00 - 03) (PDF) - en
Singleran Kpi Reference (v900r013c00 - 03) (PDF) - en
V900R013C00
KPI Reference
Issue 03
Date 2012-02-27
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
The purpose of this document is to specify the SingleRAN KPI definition as well as counters
used to calculate the KPI. The original KPI definition comes from the experiences of commercial
network management and radio network optimization. The KPI definition shall be updated
according to the requirement from customers.
Version
The following table lists the product versions involved in this document.
BSC6900 V900R013C00
NodeB V100R013
NodeB V200R013
BTS3900 BTS3900V100R002C00SPC011
BTS3000 BTS3000V100R009C00SPC011
Intended Audience
This document is intended for:
l Network planners
l Field engineers
l System engineers
Organization
1 Changes in the SingleRAN KPI Reference
This chapter describes the changes made in the SingleRAN KPI Reference.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
This chapter describes the changes made in the SingleRAN KPI Reference.
03 (2012-02-27)
This is the third commercial release of V900R013C00.
Content Description
2.6.2 Call Drop Rate on TCH per Cell Modify another KPI formula that be
(Excluding Handover) used when inter-RAT handovers are
2.6.1 Call Drop Rate on TCH per Cell detected.
(Including Handover)
Compared with issue 02 (2011-08-31), this issue does not exclude any topics.
l UMTS Service KPI
Compared with issue 02 (2011-08-31), this issue does not include any new topics.
Compared with issue 02 (2011-08-31), this issue incorporates the following changes:
Content Description
3.2.8 IUB Bandwidth Utilizing Added the scenario where the value of this KPI
Ratio (DL) is incorrect to Note.
3.2.7 IUB Bandwidth Utilizing
Ratio (UL)
Compared with issue 02 (2011-08-31), this issue does not exclude any topics.
02 (2011-08-31)
This is the second commercial release of V900R013C00.
l GSM Service KPI
Compared with issue 01 (2011-04-25), this issue does not include any new topics.
Compared with issue 01 (2011-04-25), this issue incorporates the following changes:
Content Description
2.6.2 Call Drop Rate on TCH per Add another KPI formula that be used when inter-
Cell (Excluding Handover) RAT handovers are detected.
Compared with issue 01 (2011-04-25), this issue does not exclude any topics.
l UMTS Service KPI
Compared with issue 01 (2011-04-25), this issue does not include any new topics.
Compared with issue 01 (2011-04-25), this issue incorporates the following changes:
Content Description
Compared with issue 01 (2011-04-25), this issue does not exclude any topics.
01 (2011-04-25)
This is the first commercial release of V900R013C00.
Compared with issue Draft A (2011-01-31), this issue does not include any new topics.
Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes.
Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.
Draft A (2011-01-31)
This is the Draft A release of V900R013C00.
l GSM Service KPI
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not include any
new topics.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not incorporate
any changes.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not exclude any
topics.
l UMTS Service KPI
Compared with issue 02 (2010-09-20) of V900R012C01, this issue does not include any
new topics.
Content Description
3.5.7 PS Call Drop Ratio (PCH) Correct the counter name VS.DCCC.Succ.F2P
to VS.DCCC.F2P.Succ
3.5.9 PS R99 Call Drop Ratio Correct the counter name VS.PSR99.F2P.Succ
(PCH) to VS.DCCC.Succ.F2P
Compared with issue 02 (2010-09-20) of V900R012C01, this issue does not exclude any
topics.
Compared with issue 01 (2010-04-10) of V900R012C01, this issue includes the following
new topics:
– 3.1.20 RRC Congestion Ratio
– 3.1.21 CS RAB Congestion Ratio
– 3.1.22 PS RAB Congestion Ratio
– 3.4.6 Intra-frequency Hard Handover Success Ratio
– 3.4.3 AMR Soft Handover Success Ratio
– 3.4.4 CS64 Soft Handover Success Ratio
– 3.4.5 PS Soft Handover Success Ratio
3.7.4 Number of HSDPA Users Modify the KPI name from Mean Number of
HSDPA Users to Number of HSDPA Users
New counter VS.HSDPA.UE.Max.Cell was
added in the section Associated Counters
3.7.5 Number of HSUPA Users Modify the KPI name from Mean Number of
HSUPA Users to Number of HSUPA Users
New counter VS.HSUPA.UE.Max.Cell was
added in the section Associated Counters
Compared with issue 01 (2010-04-10) of V900R012C01, this issue does not exclude any
topics.
This chapter describes the PS Data Throughput Rate KPIs. They involve the performance factors
associated with the terminals, the radio access network, and the core network. Now, the main
performance problem is concerned with the radio access network. Therefore, these KPIs indicate
the end-to-end service data link bearing capability of the GPRS network, which is directly related
to user satisfaction.
2.9 PS delay KPIs
This chapter describes the PS Delay KPIs that indicate the service response speed of the network.
Long delay affects user satisfaction.
2.10 PS Resource Utilization Rate KPIs
This chapter describes the PS Resource Utilization Rate KPIs that indicate the utilization of the
network resource and the busy states of services. Thus, these KPIs can be used to guide network
expansion.
2.11 PS Retainability KPIs
This chapter describes the PS Retainability KPIs that mainly involve the uplink and downlink
TBF call drop rates. These KPIs indicate the capability of providing continuous services by the
network and are directly related to user satisfaction. Thus, an increase in call drop rate directly
leads to a decrease in user satisfaction.
2.12 PS Transmission Performance KPIs
This chapter describes the PS Transmission Performance KPIs that indicate the quality of radio
transmission links in a cell. If the RLC data block retransmission rate in a cell is high, the quality
of the radio transmission links in the cell is poor. Therefore, take corresponding measures, such
as RF optimization.
Measurement CELL
Scope
Formula Congestion Rate on SDCCH per CELL (Due to Busy) = [Failed SDCCH
Seizures due to Busy SDCCH] x{100%}/
[SDCCH Seizure Requests]
RR370 = K3001 x 100%/K3000
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Formula TCH Congestion Rate (Overflow) = {[Failed TCH Seizures due to Busy
TCH (Signaling Channel)]
+ [Failed TCH Seizures due to Busy TCH (Traffic Channel)]
+ [Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic
Channel)]} x {100%}/
{[TCH Seizure Requests (Signaling Channel)]
+ [TCH Seizure Requests (Traffic Channel)]
+[TCH Seizure Requests in TCH Handovers (Traffic Channel)]}
K3041 = (K3021+K3011A+K3011B) x100%/(K3020+K3010A
+K3010B)
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement XPU
Scope
Formula None
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Table 2-15 External Incoming Radio Handover Success Rate per Cell
KPI Name External Incoming Radio Handover Success Rate per Cell
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
Measurement CELL
Scope
Notes Unit: %
2.4.1 Rx_QUALITY(UPLINK)
This counter provides the ratio of uplink half/full rate in the mean receive quality ranks 0 to 4.
Measurement TRX
Scope
Formula Rx_QUALITY(UPLINK)
={[Number of MRs on Uplink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 2)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 3)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 4)]
+ [Number of MRs on Uplink TCHH (Mean Rank of Receive Quality 0)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 2)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 3)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 4)]}x
{100%}/
{[Number of MRs on Uplink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 2)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 3)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 4)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 5)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 6)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 7)]
+ [Number of MRs on Uplink TCHH (Mean Rank of Receive Quality 0)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 2)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 3)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 4)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 5)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 6)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 7)]}
(CS410A + CS411A + CS412A + CS413A + CS414A + CS410C +
CS411C + CS412C + CS413C + CS414C) x{100%}/
(CS410A + CS411A + CS412A + CS413A + CS414A + CS415A +
CS416A + CS417A + CS410C + CS411C + CS412C + CS413C + CS414C
+ CS415C + CS416C + CS417C)
Associated None
Counters
Notes None
2.4.2 Rx_QUALITY(DOWNLINK)
This counter provides the ratio of downlink half/full rate in the mean receive quality ranks 0 to
4.
Measurement TRX
Scope
Formula Rx_QUALITY(DOWNLINK)
= {[Number of MRs on Downlink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 2)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 3)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 4)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 1)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 2)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 3)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 4)]}
x{100%}/
{[Number of MRs on Downlink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 2)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 3)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 4)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 5)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 6)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 7)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 1)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 2)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 3)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 4)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 5)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 6)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 7)]}
(CS410B + CS411B + CS412B + CS413B + CS414B + CS410D +
CS411D + CS412D + CS413D + CS414D) x {100%}/
(CS410B + CS411B + CS412B + CS413B + CS414B + CS415B +
CS416B + CS417B + CS410D + CS411D + CS412D + CS413D + CS414D
+ CS415D + CS416D + CS417D)
Associated None
Counters
Notes None
Measurement CELL
Scope
Associated None
Counters
Measurement CELL
Scope
Associated None
Counters
Measurement CELL
Scope
Associated None
Counters
Notes None
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Formula Actual traffic volume divided by the theoretical capacity (if the theoretical
capacity exceeds 12000 Erl, take 12000 Erl for calculation)
Associated None
Counters
Notes None
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Table 2-29 Call Drop Rate on TCH per Cell (Including Handover)
KPI Name Call Drop Rate on TCH per Cell (Including Handover)
Measurement CELL
Scope
Formula Call Drop Rate on TCH per Cell (Including Handover) = [Call Drops on
Traffic Channel] x {100%}/
{[Successful TCH Seizures (Signaling Channel)]
+ [Successful TCH Seizures (Traffic Channel)]
+ [Successful TCH Seizures in TCH handovers (Traffic Channel)]}
ZTR304 = CM33 x 100%/(K3023+K3013A+K3013B)
Notes 1. Unit: %
2. This KPI is crucial.
Table 2-30 Call Drop Rate on TCH per Cell (Excluding Handover)
KPI Name Call Drop Rate on TCH per Cell (Excluding Handover)
Measurement CELL
Scope
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Formula Traffic Call Drop Ratio per cell = [Traffic Volume on TCHs] x {60} x
100%/
[Call Drops on Traffic Channel]
ZTR308 = 60 x K3014 x 100%/CM33
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Formula Radio Drop Rate of TCH = {[Call Drops on Radio Interface in Stable State
(Traffic Channel)]
+ [Call Drops on Radio Interface in Stable State (Signaling Channel)
(TCH)]} x {100%} /
{[Successful TCH Seizures (Signaling Channel)]
+ [Successful TCH Seizures (Traffic Channel)]
+ [Successful TCH Seizures in TCH handovers (Traffic Channel)]}
RM333 = (CM330 + CM3606) x 100%/(K3023+K3013A+K3013B)
Notes Unit: %
Measurement CELL
Scope
Formula Handover Drop Rate of TCH = {[Call Drops on Signal Channel (TCH)]
+ [Call Drops in TCH Handovers (Traffic Channel)]} x {100%}/
{[Successful TCH Seizures (Signaling Channel)]
+ [Successful TCH Seizures (Traffic Channel)]
+ [Successful TCH Seizures in TCH handovers (Traffic Channel)]}
RH333 = (RH3331+K3012B) x 100%/(K3023+K3013A+K3013B)
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
the end-to-end service data link bearing capability of the GPRS network, which is directly related
to user satisfaction.
Measurement None
Scope
Associated None
Counters
Measurement None
Scope
Associated None
Counters
Measurement None
Scope
Formula The difference between the time when the MS sends an ICMP packet of
the Return Request type and the time when the receiving end responds with
an ICMP packet of the Return Acknowledgment type. Two types of Ping
delay are available: Initial Ping Delay and Consecutive Ping Delay.
Associated None
Counters
Measurement None
Scope
Formula The interval between the time when the MS sends the Activate PDP
Context Request message and the time when the MS receives the Activate
PDP Context Accept message.
Associated None
Counters
Measurement None
Scope
Formula The interval between the time when the MS sends the Attach Request
message and the time when the MS sends the Attach Complete message.
Associated None
Counters
Measurement None
Scope
Formula This counter is appraised in the mode of download test on the application
layer. This counter is defined as follows: the interval between the time
when the original cell receives the last TCP packet and the time when the
target cell receives the first TCP packet.
Associated None
Counters
Notes 1. The upload test is different from the download test. This counter is
appraised in the mode of download test:
2. The Cell Reselection Time is appraised through the Um interface on
some networks. This counter is defined as follows: the interval between
the time when the Cell Reselection message is displayed with the MA test
tool, such as TEMS, and the time when the MS initiates the Channel
Request message in a new cell. The signaling shows the interval which is
measured manually.
3. The Cell Reselection Time is impacted by the following factors:
Whether the NACC and NC2 modes are enabled; whether the 2G/3G inter-
RAT cell reselection is performed; whether the cross-RA reselection is
performed.
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Measurement CELL
Scope
Associated None
Counters
Notes 1. Unit: %
2. This KPI is crucial.
Table 2-63 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4
KPI Name Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Table 2-64 Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4
KPI Name Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Table 2-65 Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
KPI Name Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Table 2-66 Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
KPI Name Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
Measurement CELL
Scope
Associated None
Counters
Notes Unit: %
Table 2-67 Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-68 Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-69 Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-70 Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-71 Average Throughput of Uplink GPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Uplink GPRS RLC per Cell (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-72 Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-73 Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-74 Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-75 Average Throughput of Uplink GPRS LLC per User (kbit/s)
KPI Name Average Throughput of Uplink GPRS LLC per User (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-76 Average Throughput of Downlink GPRS LLC per User (kbit/s)
KPI Name Average Throughput of Downlink GPRS LLC per User (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-77 Average Throughput of Uplink EGPRS LLC per User (kbit/s)
KPI Name Average Throughput of Uplink EGPRS LLC per User (kbit/s)
Measurement CELL
Scope
Associated None
Counters
Table 2-78 Average Throughput of Downlink EGPRS LLC per User (kbit/s)
KPI Name Average Throughput of Downlink EGPRS LLC per User (kbit/s)
Measurement CELL
Scope
Associated None
Counters
3.1 Accessibility
Accessibility is the ability of a user to obtain the requested service from the system. RRC
connection and RAB setup are the main procedures of accessibility.
Formula
Description This KPI is used to check the successful paging responses to the pagings
from the Core Network (CN) in one RNC.
The Attempt Paging Procedure starts when the CN sends a PAGING
message to the RNC, and is complete when the UE in idle mode receives
the PAGING TYPE 1 message from the RNC.
The Successful Paging Procedure is complete when the RNC receives an
RRC CONNECTION REQUEST message from the UE in idle mode.
Object RNC
Unit/Range %
Note None
Formula
RRC.AttConnEstab.Reg +
RRC.AttConnEstab.Detach )] x 100%
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the Radio Access Success Ratio. The details of the
Access Failures caused by the SCCP congestion are not provided in this call
setup procedure.
Description of the RAB Setup Attempt Procedure and the RAB Setup Success
Procedure:
The RAB Setup Attempt Procedure starts when the CN sends an RAB
ASSIGNMENT REQUEST message to the RNC. The message contains
information about one of the following service types: CS Conversational
RAB Establishments, CS Streaming RAB Establishments, PS Conversational
RAB Establishment, PS Background RAB Establishments, PS Interactive
RAB Establishments, PS Streaming RAB Establishments. The RAB Setup
Attempt Procedure is complete When the RNC receives an RAB
ASSIGNMENT REQUEST message from the CN.
The RAB Setup Success Procedure is complete when the RNC sends to the
CN an RAB ASSIGNMENT RESPONSE message.
Unit/Range %
Note None
Formula
Description This KPI is used to check the PS Radio Access Success Ratio. The details of
the Access Failures caused by the SCCP congestion are not provided in this
call setup procedure.
The PS RRC Setup Attempt Procedure is complete when the RNC receives
an RRC CONNECTION REQUEST message from the UE. The message
contains information about one of the following service types: Originating
Interactive Call, Terminating Interactive Call, Originating Background Call,
Terminating Background Call.
The PS RRC Setup Success Procedure is complete when the RNC receives
an RRC CONNECTION SETUP COMPLETE message from the UE.
Unit/Range %
Note None
Formula
Description This KPI is used to check the Radio Access Success Ratio. The details of the
Access Failures caused by the SCCP congestion are not provided in this call
setup procedure.
The CS RRC Setup Attempt Procedure is complete when the RNC receives
an RRC CONNECTION REQUEST message from the UE.The message
contains information about one of the following service types: Originating
Conversational Call, Terminating Conversational Call, Emergency Call.
The CS RRC Setup Success Procedure is complete when the RNC receives
an RRC CONNECTION SETUP COMPLETE message from the UE.
Object CELL,RNC
Unit/Range %
Note None
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the AMR Service.
AMR RAB Setup Attempt Procedure is complete when the RNC receives an
RAB ASSIGNMENT REQUEST message from the CN for the CS narrow
band AMR services.
The AMR RAB Setup Success Procedure starts when the UE sends a RADIO
BEARER SETUP COMPLETE message to the RNC. This procedure is
complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the CN in the CS domain.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB setup success ratio of CS 64 Kbit/s
conversational services in an RNC or a cluster.
VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNC
receives an RAB ASSIGNMENT REQUEST message from the CN (The
RAB type is for the CS 64 Kbit/s conversational service).
VP RAB Setup Success Procedure starts when the UE sends a RADIO
BEARER SETUP COMPLETE message to RNC. This procedure is complete
when the RNC sends an RAB ASSIGNMENT RESPONSE message to the
CN in the CS domain.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of all CS services in
an RNC or a cluster.
The CS RAB Setup Attempt Procedure is complete when the RNC receives
an RAB ASSIGNMENT REQUEST message from the CN in the CS
domain.The message contains information about one of the following service
types: Conversational Services, streaming Services.
The CS RAB Setup Success Procedure starts when the RNC receives a
RADIO BEARER SETUP COMPLETE message from UE. This procedure
is complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the CN in the CS domain.
Unit/Range %
Note None
Formula
Description This KPI is used to check the RAB Setup Success Ratio of all PS services in
an RNC or a cluster.
The PS RAB Setup Attempt Procedure is complete when the RNC receives
an RAB ASSIGNMENT REQUEST message from the SGSN in the PS
domain, the message contains information about one of the following service
types: Conversational services, Streaming services, Interactive Services,
Background Services.
The PS RAB Setup Success Procedure starts when the RNC receives a
RADIO BEARER SETUP COMPLETE message from the UE. This
procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the SGSN in the PS domain.
Unit/Range %
Note None
Formula
Description This KPI is used to check the RAB Setup Success Ratio of PS services that
are carried by HSDPA in a cluster.
The HSDPA RAB Setup Attempt Procedure is complete when the RNC
receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSDPA service.
The HSDPA RAB Setup Success Procedure starts when the RNC receives a
RADIO BEARER SETUP COMPLETE message from the UE. This
procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSUPA service
in an RNC or a cluster.
The HSUPA RAB Setup Success Procedure starts when the RNC receives a
RADIO BEARER SETUP COMPLETE message from the UE. This
procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN.
The HSUPA RAB Setup Attempt Procedure is complete when the RNC
receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSUPA service.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB setup success ratio of the E-FACH service
in an RNC or a cluster.
Successful PS RAB Setup on E-FACH Procedure starts when the RNC
receives a RADIO BEARER SETUP COMPLETE message from the UE.
This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the SGSN in the PS domain.
The procedure of Attempts of PS RAB Setup on E-FACH is complete when
the RNC receives an RAB ASSIGNMENT REQUEST message from the
SGSN, and the PS service is established on the EFACH.
CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB setup success ratio of the CS over HSPA
service.
When the RAB is set for the CS conversational service and is carried on an
HSPA channel, the CS over HSPA RAB Setup Success Procedure starts when
the RNC receives an RADIO BEARER SETUP COMPLETE message from
UE. This procedure is complete when the RNC sends an RAB
ASSIGNMENT RESPONSE message to CN.
The CS over HSPA RAB Setup Attempt Procedure is complete when the
RNC receives an RAB ASSIGNMENT REQUEST message from the CN,
and the RAB is set up on an HSPA channel.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA
64QAM service in an RNC or a cluster.
The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNC
receives an RADIO BEARER SETUP COMPLETE message from the UE.
This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN.
The HSDPA 64QAM RAB Setup Attempt Procedure is complete when the
RNC receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSDPA service using 64QAM.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO
service in an RNC or a cluster.
The HSDPA MIMO RAB Setup Success procedure starts when the RNC
receives a RADIO BEARER SETUP COMPLETE message from the UE.
This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN.
The HSDPA MIMO RAB Setup Attempt procedure is complete when the
RNC receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSDPA service using MIMO.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC
RAB service in an RNC or a cluster.
The HSDPA DC RAB Setup Success procedure starts when the RNC receives
a RADIO BEARER SETUP COMPLETE message from the UE. This
procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the CN.
The HSDPA DC RAB Setup Attempt procedure is complete when the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message for
setting up the HSDPA service using DC-HSDPA.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO
64QAM service in an RNC or a cluster.
The HSDPA MIMO 64QAM RAB Setup Success procedure starts when the
RNC receives a RADIO BEARER SETUP COMPLETE message from the
UE. This procedure is complete when the RNC sends an RAB
ASSIGNMENT RESPONSE message to the CN.
The HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete
when the RNC receives an RAB ASSIGNMENT REQUEST message from
the CN for setting up the HSDPA service using MIMO+64QAM.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the Channel Setup Success Rate of MBMS service
in PTM mode.
When the RB of PTM MBMS service is successfully set up, the PTM Channel
RB is successfully set up.
When the RNC initiates the setup of PTM MBMS service, the PTM Channel
RB Setup Attempt.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the Channel Setup Success Rate of MBMS service
in PTP mode.
The PTP Channel RB Setup Success Procedure is as follows:
When the UE initiates a request to set up an MBMS, the RNC, in response to
the UE's request, initiates PTP RB setup, and the PTP RB is successfully set
up.
The PTP Channel RB Setup Attempt Procedure:
The RNC initiates PTP RB setup after the UE initiates an MBMS setup
request.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the RRC Congestion Ratio in a cluster.
After receiving an RRC CONNECTION REQUEST message from the UE,
the RNC initiates admission procedures for resources of code, power, CE,
and Iub bandwidth. If the resource admission fails, the RRC Setup Failure
due to Congestion procedure is complete when the RNC sends an RRC
CONNECTION REJECT message to the UE.
The RRC Connection Attempt for service Procedure is complete when the
RNC receives an RRC CONNECTION REQUEST message from the UE.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the CS RAB Congestion Ratio in a cluster.
The CS RAB Setup Fails due to Congestion procedure is complete when the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The
message contains one of the following RAB assignment responses: "No
Radio Resources Available in Target cell", "Requested Maximum Bit Rate
not Available", "Requested Maximum Bit Rate for UL not Available",
"Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit
Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not
Available".
The CS RAB Setup Attempt Procedure starts when the RNC receives an RAB
ASSIGNMENT REQUEST message from the CN in the CS domain. The
message contains one of the following RAB assignment requests:
Conversational Services, streaming Services.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the PS RAB Congestion Ratio in a cluster.
The PS RAB Setup Fails due to Congestion procedure is complete when the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The
message contains information about one of the following RAB assignment
responses: "No Radio Resources Available in Target cell", "Requested
Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL
not Available", "Requested Guaranteed Bit Rate not Available", "Requested
Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate
for UL not Available".
The PS RAB Setup Attempt Procedure starts when the RNC receives an RAB
ASSIGNMENT REQUEST message from the SGSN in the PS domain. The
message contains information about one of the following RAB assignment
requests: Conversational services, Streaming services, Interactive Services,
Background Services.
Object CELL
Unit/Range %
Note None
3.2 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
Formula
Description This KPI is used to check the Availability of the cells with poor call drop ratio
or call setup success ratio in an RNC or a cluster.
Description of the numerator:
The number of Cells in which AMR RAB Setup Success Ratio <95% and VP
RAB Setup Ratio <= 95%, or AMR Call Drop Ratio >3% and VP Call Drop
Ratio >3%.
Object CELL
Unit/Range %
Note 95% and 3% are the values obtained based on the references from the
commercial network with the condition of that the traffic of AMR voice and
video call is greater than 0.1 Erlang.
Formula
Unit/Range %
Note None
Formula
Description This KPI is used to check the admission refused ratio of new calls during busy
hours in an RNC or a cluster.
l Description of the numerator:
The failed number of Cell Resource Requests for New Call setup is
counted after RNC requesting cell resources for the UE successfully.
l Description of the denominator:
The number of Cell Resource Requests during RAB establishment for
Cell. After RNC receiving the RAB ASSIGNMENT REQUEST message
from CN, the RNC requests cell resources for the UE and the counter is
pegged in the cell where the UE camps on.
Object CELL
Unit/Range %
Note The RNC level KPI is calculated by aggregating all the cell counters.
Formula
Description This KPI is used to check the utility ratio of radio network resources during
busy hours in an RNC or a cluster. It is the rate of congested cell during the
busy hour to total number of cells in RNC.
Description of the numerator:
The number of congested cells counted after RNC receiving the COMMON
MESUREMENT REPORT message from NodeB. The RNC measures when
overload congestion occurs at UL or DL.
Object CELL
Unit/Range %
Note The number of congested cells is calculated by aggregating the cells that are
congested in DL or UL directions during busy hours.
Formula
Description This KPI describes the ratio of cell unavailable duration to the number of cells
in RNC during busy hours. It is used to check the impact of the degrading of
the network performance caused by the unavailable cells during busy hours
in an RNC.
Description of the numerator:
The cell unavailable time is started to count when the cell is out of service,
or the channel is barred through the LMT in a measurement period, or problem
of CCH such as failed synchronization, or equipment faults.
Object CELL
Unit/Range %
Formula Average CPU Load = XPU usage of the XPU in the measurement period
Description This KPI provides the CPU usage of the XPU in a measurement period. It
also indicates the load and operating performance of CPU on the XPU in the
measurement period.
The CPU usage of the XPU is accumulated every second in the measurement
period.
Object XPU
Unit/Range %
Note Mean CPU Utility is the CPU average load showed in percentage.
Formula
Description This KPI is used to check the ratio of consumption of Iub bandwidth and
configured Iub bandwidth in a NodeB for downlink during busy hours. The
consumption of interactive and background services cannot maintain the full
rate all the time on the configured Iub bandwidth.
The UL Bandwidth could be measured on ATM Physical Ports or IP physical
Ports. The numerator is defined as the average used bandwidth on an ATM
or IP physical ports during a measurement period counted by NodeB. The
NodeB measures the used UL bandwidth on the physical port every five
seconds for 15 minutes and then calculates the average value. The counter
and the physical port have one-to-one relation, and they are all used for traffic
measurement at the physical layer.
Object NodeB
Unit/Range %
Note The counters in the formula are measured on the NodeB side.
In Iub over IP mode, the NodeB-level counters VS.IPUlTotal.1,
VS.IPUlTotal.2, VS.IPUlTotal.3, and VS.IPUlTotal.4 provide the physical
bandwidths of ports rather than the actual available bandwidths of ports.
Therefore, if the actual available bandwidth of a port is different from the
physical bandwidth of the port, the value of this KPI calculated by using this
formula is incorrect, and you are advised to use the actual available
bandwidths as the denominator to calculate this KPI.
Formula
Description This KPI is used to check the ratio of consumption of Iub bandwidth and
configured Iub bandwidth in a NodeB for downlink during busy hours. The
consumption of interactive and background services cannot maintain the full
rate all the time on the configured Iub bandwidth.
The DL Bandwidth could be measured on ATM Physical Ports or IP physical
Ports. The numerator is defined as the average used bandwidth on an ATM
or IP physical ports during a measurement period counted by NodeB. The
NodeB measures the used DL bandwidth on the physical port every five
seconds for 15 minutes and then calculates the average value. The counter
and the physical port have one-to-one relation, and they are all used for traffic
measurement at the physical layer.
Object NodeB
Unit/Range %
Note The counters in the formula are measured on the NodeB side.
In Iub over IP mode, the NodeB-level counters VS.IPDLTotal.1,
VS.IPDLTotal.2, VS.IPDLTotal.3, and VS.IPDLTotal.4 provide the
physical bandwidths of ports rather than the actual available bandwidths of
ports. Therefore, if the actual available bandwidth of a port is different from
the physical bandwidth of the port, the value of this KPI calculated by using
this formula is incorrect, and you are advised to use the actual available
bandwidths as the denominator to calculate this KPI.
Description This KPI is used to check the total duration of the unavailability of a cell
caused by system fault in a measurement period.
Associated VS.Cell.UnavailTime.Sys
Counters
Object CELL
Unit/Range s
Note None
Description This KPI is used to check the total duration of unavailability of the HSDPA
service in a cell,caused by system fault in a measurement period.
Associated VS.Cell.HSDPA.UnavailTime
Counters
Object CELL
Unit/Range s
Note None
Description This KPI is used to check the total duration of unavailability of the HSUPA
service in a cell,caused by system fault in a measurement period.
Associated VS.Cell.HSUPA.UnavailTime
Counters
Object CELL
Unit/Range s
Note None
Description The resources for license groups are measured based on the usage of CEs in
each license group. This measurement indicates the consumption of baseband
resources in the NodeB.
The corresponding counters listed below give the Average/Maximum number
of UL/DL and HSUPA CEs consumption for an operator.
Associated VS.ULCE.Mean.Shared
Counters VS.ULCE.Max.Shared
VS.DLCE.Mean.Shared
VS.DLCE.Max.Shared
VS.ULCE.Mean.Dedicated
VS.ULCE.Max.Dedicated
VS.DLCE.Mean.Dedicated
VS.DLCE.Max.Dedicated
Unit/Range Numbers
Note If only one Operator is available on the NodeB, the Dedicated Counter value
is always Zero and the Shared CE counters should be used to check actual
consumption of the Cell in NodeB.
Associated VS.HW.ULCreditAvailable
Counters VS.HW.DLCreditAvailable
Object NodeB
Unit/Range Numbers
Note None
Associated VS.LC.ULCreditAvailable.Shared
Counters VS.LC.DLCreditAvailable.Shared
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the configured counters given
above should be used to evaluate the total configured License CE in the
NodeB.
Associated VS.LC.ULMean.LicenseGroup.Shared
Counters VS.LC.ULMax.LicenseGroup.Shared
VS.LC.ULMin.LicenseGroup.Shared
VS.HSUPA.LC.ULMean.LicenseGroup.Shared
VS.HSUPA.LC.ULMax.LicenseGroup.Shared
VS.HSUPA.LC.ULMin.LicenseGroup.Shared
VS.LC.DLMean.LicenseGroup.Shared
VS.LC.DLMax.LicenseGroup.Shared
VS.LC.DLMin.LicenseGroup.Shared
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the shared counters given
above should be used to evaluate the total License CE Consumption in the
NodeB.
Associated VS.LC.DLCreditAvailable.LicenseGroup.Dedicated
Counters VS.LC.ULCreditAvailable.LicenseGroup.Dedicated
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the configured counter value
given above is Zero.
Associated l UL Statistics
Counters VS.LC.ULMean.LicenseGroup
VS.LC.ULMax.LicenseGroup
VS.LC.ULMin.LicenseGroup
VS.HSUPA.LC.ULMin.LicenseGroup
VS.HSUPA.LC.ULMean.LicenseGroup
VS.HSUPA.LC.ULMax.LicenseGroup
l DL Statistics
VS.LC.DLMean.LicenseGroup
VS.LC.DLMax.LicenseGroup
VS.LC.DLMin.LicenseGroup
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the counter value given above
is Zero.
Description The first 3 counters given below provide the RTWP measurement values of
a cell in the RNC, Mean/Maximum/Minimum Power of Totally Received
Bandwidth for Cell. The last 3 counters provide average, maximum and
minimum received scheduled E-DCH power shared in the measurement
period for cell.
Associated VS.MaxRTWP
Counters VS.MinRTWP
VS.MeanRTWP
VS.HSUPA.MeanRSEPS
VS.HSUPA.MaxRSEPS
VS.HSUPA.MinRSEPS
Object CELL
Unit/Range dBm; %
Note None
Associated VS.MaxTCP
Counters VS.MinTCP
VS.MeanTCP
VS.MaxTCP.NonHS
VS.MinTCP.NonHS
VS.MeanTCP.NonHS
VS.HSDPA.MaxRequiredPwr
VS.HSDPA.MinRequiredPwr
VS.HSDPA.MeanRequiredPwr
Object CELL
Unit/Range dBm
Note None
Formula
Description The occupied codes are the codes occupied by the common channel and R99
user. The code number is normalized to SF = 256, that is, converted to the
code number when SF = 256.
The counters given below provide the number of single-RAB and Multi-RAB
UEs that occupy the DL R99 codes with Spreading Factor (SF) of
4/8/16/32/64/128/256.
Object CELL
Unit/Range %
3.3 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an
RNC or a cluster.
Formula
Description This KPI is used to check how the UL capacity is limited by the UL
interference of all cells in an RNC.
The mean RTWP's measurement is started when the RNC receives a
COMMON MEASUREMENT REPORT message from the NodeB about the
RTWP of a cell and obtains the RTWP of the cell.
Object RNC
Unit/Range %
Note -98 dBm is the value obtained based on the references from the commercial
network.
Formula
Description This KPI is used to check the consumption of network resources due to soft
handover in an RNC or a Cell. It considered the radio link quantity during the
soft handover.
In the RNC Soft handover ratio, count the mean number of UEs with different
quantity of radio links for RNC from A1 to F1. The RNC periodically samples
of the number of UEs with corresponding radio links in a measurement period.
At the end of the measurement period, the RNC divides the accumulated
number by the sampling times to obtain the soft handover overhead.
The Cell level KPI is only available for cells in a cluster. From A1 to F1 count
the mean number of UEs with different quantity of Radio Links(1~6 radio
links) in the Cell of the active set.
Unit/Range %
Note None
3.4 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or
service mode changing in difference scenarios.
Formula
Description This KPI is used to check the soft handover success ratio in an RNC or in a
Cluster, including softer handover.
l The Successful Soft Handover (including softer handovers) procedure is
complete when the RNC receives an ACTIVE SET UPDATE
COMPLETE message from the UE during the soft handover (including
the softer handover) procedure.
l The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Unit/Range %
Note None
Formula
Description This KPI is used to check the softer handover success ratio in an RNC or a
Cluster, including softer handover.
l The Successful Softer Handover procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE
during the softer handover procedure.
l The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Unit/Range %
Note None
Formula
Description This KPI is used to check the AMR Soft Handover Success ratio in an RNC
or a Cluster, including softer handover.
The Successful AMR Soft Handover procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE
during the soft handover procedure.
The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Object CELL
Unit/Range %
Note The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.
Formula
Description This KPI is used to check the CS64 Soft Handover Success ratio in an RNC
or a Cluster, including softer handover.
The Successful CS64 Soft Handover procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE
during the soft handover procedure.
The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Object CELL
Unit/Range %
Note The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.
Formula
Description This KPI is used to check the PS Soft Handover Success ratio in an RNC or
a Cluster, including softer handover.
The Successful PS Soft Handover procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE
during the soft handover procedure.
The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Object CELL
Unit/Range %
Note The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.
Formula
Description This KPI is used to check the intra-frequency hard handover success ratio in
an RNC.
The Intra-frequency Hard Handover Success procedure is complete when the
RNC receives the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE (for example) message from the UE.
The Intra-frequency Hard Handover Attempt procedure is complete when
RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to
the UE.
Unit/Range %
Note None
Formula
Description This KPI is used to check the inter-frequency hard handover success ratio in
an RNC.
The Inter-frequency Hard Handover Success procedure is complete when
RNC received a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from the UE.
The Inter-frequency Hard Handover attempts procedure starts when RNC
sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE.
In this case the RNC measures the counter.
Unit/Range %
Note None
Table 3-52 Service Cell Change Success Ratio with SHO (H2H)
Name Service Cell Change Success Ratio with SHO (H2H)
Formula
Description l The HS-DSCH service cell change success with SHO is triggered with
the following messages:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
ACTIVE SET UPDATE
l Accordingly, the UE sends the following messages to the RNC as a
response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
ACTIVE SET UPDATE COMPLETE
ACTIVE SET UPDATE FAILURE Message
Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example. When receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE, the RNC measures this item as numerator,
and when sending a PHYSICAL CHANNEL RECONFIGURATION
message to a UE, the RNC measures this item as denominator.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the intra-frequency hard handover success ratio of
HSDPA service in an RNC or a cluster.
l The HS-DSCH service cell change success with SHO is triggered with
the following message:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
l Accordingly, the UE sends the following messages to the RNC as a
response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE , the RNC measures this item in the best
cell from which the UE is handed over if an intra-frequency HSDPA hard
handover without channel change is performed.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to indicate the success ratio of inter-frequency hard
handovers from the HSDPA to the HSDPA in a cell.
l The hard handover procedure can be triggered with the following
message:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
l Accordingly, the UE sends the following messages to the RNC as a
response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE , the RNC measures this item in the best
cell from which the UE is handed over if an inter-frequency HSDPA hard
handover without channel change is performed.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to indicate the success ratio of inter-frequency hard
handovers from the HSDPA to the DCH in a cell.
l The hard handover procedure can be triggered with the following
messages:
RADIO BEARER RECONFIGURATION
RADIO BEARER SETUP
RADIO BEARER RELEASE message
l Accordingly, the UE sends the following messages to the RNC as a
response.
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the RADIO BEARER RECONFIGURATION message as an example,
when receiving a RADIO BEARER RECONFIGURATION COMPLETE
message from a UE , the RNC measures this item in the best cell from which
the UE is handed over if an inter-frequency hard handover from the HSDPA
to the DCH is performed.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the channel switch success ratio when UE switches
from HSDPA to DCH in an RNC or a cluster.
The number of successful HS-DSCH to DCH channel switch measures when
RNC receives a RAIDO BEARER RECONFIGURATION COMPLETE
message from the UE indicating the channel reconfiguration for HSDPA
service in the DCCC or RAB MODIFY procedure. The RNC measures the
item in the HSDPA serving cell.
The attempt number of H2D channel handover counts when RNC decides to
perform a channel handover, which sends a RADIO BEARER
RECONFIGURATION message to a UE during the DCCC or RAB MODIFY
procedure. In this case, the RNC measures the item in the serving cell of the
HSDPA service according to the transport channels of UEs before and after
the reconfiguration.
The RNC performs the transport channel Switch in the same cell.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the channel switch success ratio when the UE
switches from DCH to HSDPA in an RNC or a cluster.
The number of successful DCH to HS-DSCH channel switch measures when
RNC receives from the UE a RAIDO BEARER RECONFIGURATION
COMPLETE message indicating the channel reconfiguration for HSDPA
service in the DCCC or RAB MODIFY procedure. The RNC measures the
item in the HSDPA serving cell.
The attempt number of D2H channel switch counts when RNC decides to
perform a channel switch, which sends a RADIO BEARER
RECONFIGURATION message to a UE during the DCCC or RAB MODIFY
procedure. In this case, the RNC measures the item in the serving cell of the
HSDPA service according to the transport channels of UEs before and after
the reconfiguration.
The RNC performs the transport channel switch in the same cell.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to indicate the success ratio of CS Outgoing inter-RAT
handovers in an RNC or a Cluster.
The CS inter-RAT Handover Success procedure is complete when RNC
receives an IU RELEASE COMMAND message. The message contains one
of the following information: "Successful Relocation", "Normal Release",
"Network Optimization" after sending a HANDOVER FROM UTRAN
COMMAND message during the CS outgoing inter-RAT handover. In this
case, the outgoing handover succeeds and this counter is measured.
The CS inter-RAT Handover attempts procedure starts when the RNC sends
a HANDOVER FROM UTRAN COMMAND message to the UE during the
CS outgoing inter-RAT handover.
Unit/Range %
Note None
Formula
Description This KPI is used to indicate the success ratio of PS outgoing inter-RAT
handover initiated by the RNC or in the best cell.
The PS W2G Inter-RAT Outgoing Handover successes procedure is complete
when the RNC sends the IU RELEASE COMPLETE message after receiving
the IU RELEASE COMMAND message. The message contains one of the
following information: "Successful Relocation", "Normal Release",
"Network Optimization" during the PS outgoing inter-RAT handover. In this
case, the PS outgoing inter-RAT handover succeeds and the counter is
measured.
The PS W2G Inter-RAT Outgoing Handover attempts procedure starts when
the RNC sends the CELL CHANGE ORDER FROM UTRAN message
during the PS outgoing inter-RAT handover.
Unit/Range %
Note None
Formula
Description This KPI is used to check the PS inter-RAT handover in success ratio in an
RNC or a cluster.
The PS G2W Inter-RAT Handover successes procedure is complete when the
RNC receives an RRC CONNECTION SETUP COMPLETE message from
the UE. The reasons for RRC connection request is Inter-RAT Cell Change
Order and Inter-RAT Cell Reselection.
The PS G2W Inter-RAT Handover attempts procedure starts when the RNC
receives an RRC CONNECTION REQUEST message from the UE, the
reasons for RRC connection request are Inter-RAT Cell Change Order and
Inter-RAT Cell Reselection.
Object CELL
Unit/Range %
Note The KPI includes the IRAT cell reselection of UE in idle status.
Formula
Description This KPI is used to check the PS outgoing inter-RAT handover for HSDPA
services initiated by the RNC in the best cell that the UE camps on before the
handover.
The HSDPA Inter-RAT HO successes procedure is complete when the RNC
receives the IU RELEASE COMMAND message. The message contains one
of the following information: "Successful Relocation", "Normal Release",
"Network Optimization" during the PS outgoing inter-RAT handover for
HSDPA services.
The HSDPA Inter-RAT HO attempts procedure starts when the RNC sends
the CELL CHANGE ORDER FROM UTRAN message during the PS
outgoing inter-RAT handover for HSDPA services, the counter is measured
in the best cell that the UE camps on.
Object CELL
Unit/Range %
Note The KPI includes the IRAT cell reselection of UE in idle status.
Formula
Description This KPI is used to check the relocation executions (UE involved and UE not
involved) initiated by SRNC according to different CN domains.
The SRNC Relocation Success procedure is complete when the SRNC
receives an IU RELEASE COMMAND message. The message contains one
of the following information: "Successful Relocation", "Normal Release",
"Network Optimization". In this case, the SRNC measures the related counter
according to the CN domain.
The SRNC Relocation Attempts procedure starts when the SRNC receives a
RELOCATION COMMAND message from the CN in the CS domain. In this
case, the SRNC measures the related counter according to different relocation
types (CS, PS, UE involved, UE not involved).
Object RNC
Unit/Range %
Note None
Formula
Description This KPI is used to check the TRNC relocation executions (UE involved and
UE not involved) initiated by SRNC according to different CN domains.
The TRNC Relocation Success procedure is complete when the TRNC
relocation is complete, and when the TRNC sends a RELOCATION
COMPLETE message to the CN. In this case, the TRNC measures the related
counters according to different relocation types. If the UE connects to both
the CS domain and the PS domain at the same time, the related counters are
increased by one each time the TRNC sends a RELOCATION COMPLETE
message to the CNs in the CS domain and PS domain.
When the resource allocation for TRNC relocation is complete, the TRNC
sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN
in the CS or the PS domain. In this case, the TRNC measures the related
counter according to different relocation types.
Object RNC
Unit/Range %
Note None
Formula
Description This KPI is used to check EDCH RL additions and deletions due to soft
handover in a cell.
The E-DCH soft Handover Success procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE.An
EDCH link is added or deleted during the soft handover.
The E-DCH soft Handover attempts procedure starts when the RNC sends an
ACTIVE SET UPDATE message to the UE and there is EDCH RL to be
deleted or added during the soft handover.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the success ratio of HSUPA serving cell changes
in soft handover status for cell.
Description of the numerator:
l The successful HSUPA serving cell changes in soft handover status for
cell, this procedure can be triggered with the following messages:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
l Accordingly, the UE sends the following messaged to the RNC as a
response:
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
l Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when the RNC receives a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from the UE, the RNC
measures this item in the original HSUPA serving cell if the HSUPA
serving cell is changed. The item is used to indicate the change of HSUPA
serving cells in the soft handover state instead of the hard handover state.
Description of the denominator:
l Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when the RNC sends a PHY CHANNEL
RECONFIGURATION message to the UE. The RNC measures this item
in the original HSUPA serving cell if the HSUPA serving cell is changed.
This item is used to indicate the change of HSUPA serving cells in the
soft handover status instead of the hard handover status.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the E-DCH service cell change success ratio with
the Inter-HHO procedure in an RNC or a cluster.
Description of the numerator:
l When the RNC receives one of the following messages from the UE, the
RNC measures this item in the HSUPA serving cell before the hard
handover if an EDCH-to-EDCH inter-frequency hard handover is
performed.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER SETUP COMPLETE
RADIO BEARER RELEASE COMPLETE
Description of the denominator:
l When the RNC sends the following messages to the UE, the RNC
measures the item in the HSUPA serving cell before the hard handover if
an EDCH-to-EDCH inter-frequency hard handover is performed.
PHYSICAL CHANNEL RECONFIGRATION
TRANSPORT CHANNEL RECONFIGRATION
RADIO BEARER RECONFIGRATION
RADIO BEARER SETUP
RADIO BEARER RELEASE
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the channel switch success ratio when there is UE
handover from E-DCH to DCH in the same cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure
is complete when the RNC receives an RB RECFG CMP message from the
UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the
same cell after reconfigurations, the RNC measures the items in the HSUPA
serving cell by the channel switch type.
The Switch Channel Type from EDCH to DCH attempts procedure starts
when the RNC sends a RADIO BEAR RECONFIGURE message to the UE
during the DCCC or RAB ASSIGN procedure. If the UE camps on the same
cell after reconfigurations, the RNC measures the items in the HSUPA serving
cell by the channel switch type.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the channel switch success ratio when there is UE
handover from E-DCH to DCH in the same cell.
The Switch Channel Type from DCH to EDCH successful attempts procedure
is complete when the RNC receives an RB RECFG CMP message from the
UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the
same cell after reconfigurations, the RNC measures the items in the HSUPA
serving cell by the channel switch type.
The Switch Channel Type from DCH to EDCH attempts procedure starts
when the RNC sends a RADIO BEAR RECONFIGURE message to the UE
during the DCCC or RAB ASSIGN procedure. If the UE camps on the same
cell after reconfigurations, the RNC measures the items in the HSUPA serving
cell by the channel switch type.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the success ratio of HSUPA Inter-Frequency Hard
Handover from EDCH to DCH in a cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure
is complete when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE. The RNC
measures this item in the HSUPA serving cell before the hard handover if an
EDCH-to-DCH inter-frequency hard handover is performed.
The Switch Channel Type from EDCH to DCH attempts procedure starts
when the RNC sends a RADIO BEARER RECONFIGURATION message
to the UE. The RNC measures this item in the HSUPA serving cell before the
hard handover if an EDCH-to-DCH inter-frequency hard handover is
performed.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the HSUPA service Inter-RAT handover success
ratio from WCDMA to GPRS in the best cell that the UE camps on.
The HSUPA W2G Inter-RAT Handover Out success procedure is complete
when the RNC receives an IU RELEASE COMMAND message. The
message contains one of the following information: "Successful Relocation",
"Normal Release", "Network Optimization" and sends an IU RELEASE
COMPLETE message during the PS outgoing inter-RAT handover for
HSUPA services. In this case, the PS outgoing handover succeeds and this
counter is measured in the best cell that the UE camps on before the handover.
The HSUPA W2G Inter-RAT Handover Out attempts procedure starts when
the RNC sends a CELL CHANGE ORDER FROM UTRAN message to the
UE during the PS outgoing inter-RAT handover for HSUPA services. In this
case, this counter is measured in the best cell that the UE camps on.
Object CELL
Unit/Range %
Note None
Formula
Description This KPI is used to check the MBMS service mode switch success ratio from
PTP to PTM.
The MBMS Service Mode Switch Success procedure is complete after a
MBMS service is switched from PTP mode to PTM mode and a PTM MBMS
RB is successfully set up.
The MBMS Service Mode Switch attempts procedure starts after the initiation
of transition from PTP mode to PTM mode.
Associated MBMS Service Mode Switch Success Ratio from PTP to PTM=
Counters (VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att) x 100%
Object CELL
Unit/Range %
Note None
3.5 Retainability
Retainability is defined as the ability of a user to retain its requested service for the required
duration once connected. The RNC level KPIs can be calculated by aggregating all the cell
counters and Iur counters.
Formula
Description This KPI provides the ratio of the CS RAB abnormal Releases to the total CS
RAB Releases (Normal Release + Abnormal Release). This KPI is used to
check the retainabililty of CS Service within the UTRAN (RNC or Cluster).
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exceptions. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with the
causes other than "User Inactivity", "Normal Release", "Successful
Relocation", "Network Optimization", the RNC measures the items
according to the service types in the best cell that the UE camps on if the
released RABs belong to PS domain.
Unit/Range %
Note None
Formula
Description This KPI provides the ratio of AMR RAB abnormal Releases to the total
AMR RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of AMR Service within the UTRAN (RNC or Cluster).
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CNdue to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following messages: "User Inactivity","Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the Cell and Iur
counters in SRNC.
Formula
Description This KPI provides the ratio of the VP (Video Phone) RAB abnormal Releases
to the total VP RAB Releases (Normal Release + Abnormal Release) and is
used to check the retainabililty of VP Service of the UTRAN (RNC or
Cluster).
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity","Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note None
Formula
Description This KPI provides the ratio of the AMR Service Erlang to the AMR RAB
Abnormal Releases, which indicates the AMR average Erlang per AMR call
drop within the UTRAN (RNC or Cluster).
Description of the AMR RB counters in the numerator:
Average number of AMR users with different DL rates during the
measurement period.
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note None
Formula
Description This KPI provides the ratio of the VP (Video Phone) Service Erlang to the
VP RAB Abnormal Releases, which indicates the VP average Erlang per VP
call drop within the UTRAN (RNC or Cluster).
Description of the VS.RB.CS.Conv.DL.64/VS.RB.CS.Conv.DL.64.RNC:
Average number of VP users with different DL rates during the measurement
period.
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT
REQUEST message with any one of the following information: "User
Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", the RNC measures the items according to the service types in
the best cell that the UE camps on if the released RABs belong to PS domain.
Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note None
Formula
Description This KPI provides the ratio of the PS RAB abnormal Releases to the total PS
RAB Releases (Normal Release + Abnormal Release) and is used to check
the retainabililty of PS Service within the UTRAN (RNC or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note None
Formula
Description Compared with PS Call Drop Ratio, these KPIs take the PCH state into
account.
Since more and more smart phones camp on and keep Always Online in the
network, if the PCH transition is switched on while no data transferring for
a period, these UEs usually transfer from connected state into Cell PCH state
instead of Idle state, that is, the occasion of RAB normal release for
transferring into IDLE state will greatly decrease than that in the conditions
without PCH transition.
From user's point of view, the occasion of a UE transferring into PCH state
should be considered as a normal RAB release for calculating the formula of
PS Call Drop Ratio.
Unit/Range %
Formula
Description This KPI provides the ratio of the PS R99 RAB abnormal Releases to the total
PS R99RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of PS R99 Service within the UTRAN (RNC or
Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Object CELL
Unit/Range %
Note RNC level KPI can be calculated approximately by aggregating all the cell
level counters in SRNC, due to the counters are counted in the best cell of
active set. If the best cell for the PS R99 RAB Establishment is located in
DRNC through Iur interface, no counters for the scenario exists in SRNC.
Formula
Description Compared with PS R99 Call Drop Ratio, this KPI takes the PCH state into
account.
Object CELL
Unit/Range %
Note The occasion of a UE transferring out of PS R99 state (F2H, F2P, D2H) should
be considered as a normal RAB release for calculating the formula of PS R99
Call Drop Ratio.
RNC level KPI can be calculated approximately by aggregating all the cell
level counters in SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS R99 RAB Establishment located in DRNC
via Iur interface, this scenario is not taken into account in the formula.
VS.RAB.AbnormRel.PSR99 and VS.RAB.NormRel.PSR99 have already
taken PCH into account, the occasion of the RAB Normal/Abnormal Release
(VS.RAB.AbnormRel.PS.PCH and VS.RAB.NormRel.PS.PCH) should
be excluded off the Denominator.
Formula
Description This KPI provides the ratio of the PS BE RAB abnormal Releases to the total
PS BE RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of PS BE Service of the UTRAN (RNC or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note RNC level KPI can be calculated approximately by aggregating all the Cell
and Iur level counters in SRNC.
Formula
Description This KPI provides the ratio of the HSDPA RAB abnormal Releases to the
total HSDPARAB Releases (Normal Release+ Abnormal Release) and is
used to check the retainabililty of HSDPA Service within the UTRAN (RNC
or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note RNC level KPI is calculated approximately by aggregating all the Cell and
Iur level counters in SRNC.
The successful channel transition is considered as normal HS-DSCH release
(Including the transitions due to mobility).
Formula
Description Compared with HSDPA Call Drop Ratio, this KPI takes the PCH state into
account.
Unit/Range %
Formula
Description This KPI provides the ratio of the HSUPA RAB abnormal Releases to the
total HSUPARAB Releases (Normal Release + Abnormal Release) and is
used to check the retainabililty of HSUPA Service of the UTRAN (RNC or
Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following information: "User Inactivity", "Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Unit/Range %
Note RNC level KPI is calculated approximately by aggregating all the Cell and
Iur level counters in SRNC.
The successful channel transition is considered as normal E-DCH release
(Including the transitions due to mobility).
Formula
Description Compared with HSUPA Call Drop Ratio, this KPI takes the PCH state into
account.
Unit/Range %
Note The occasion of a UE transferring out of PS E-DCH Channel state (E2D, E2F,
E2P) should be considered as a normal RAB release for calculating the
formula of PS HSUPA Call Drop Ratio.
Formula
Object CELL
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the cell counters.
Description These counters provide the average uplink rates of different PS R99 services
in the cells of the active set.
The UL traffic (excluding the RLC header and the retransmitted data, unit:
bit) and the Data transfer duration (unit: ms) of each kind of PS R99 services
are accumulated in the measurement period for the cells that are under the
SRNC. At the end of the measurement period, the RNC divides the total bytes
by the total data transfer time to obtain the Average UL Throughput for each
PS R99 Service.
Associated VS.PS.Bkg.Kbps.UL8
Counters VS.PS.Bkg.Kbps.UL16
VS.PS.Bkg.Kbps.UL32
VS.PS.Bkg.Kbps.UL64
VS.PS.Bkg.Kbps.UL128
VS.PS.Bkg.Kbps.UL144
VS.PS.Bkg.Kbps.UL256
VS.PS.Bkg.Kbps.UL384
VS.PS.Int.Kbps.UL8
VS.PS.Int.Kbps.UL16
VS.PS.Int.Kbps.UL32
VS.PS.Int.Kbps.UL64
VS.PS.Int.Kbps.UL128
VS.PS.Int.Kbps.UL144
VS.PS.Int.Kbps.UL256
VS.PS.Int.Kbps.UL384
VS.PS.Str.Kbps.UL8
VS.PS.Str.Kbps.UL16
VS.PS.Str.Kbps.UL32
VS.PS.Str.Kbps.UL64
VS.PS.Str.Kbps.UL128
VS.PS.Conv.Kbps.UL
Object CELL
Unit/Range Kbit/s
Note None
Description These counters provide the average downlink rates of different PS R99
services in the cells of the active set.
The DL traffic (excluding the RLC header and the retransmitted data, unit:
bit) and the Data transfer duration (unit: ms) of each kind of PS R99 services
are accumulated in the measurement period for the cells that are under the
SRNC. At the end of the measurement period, the RNC divides the total bytes
by the total data transfer time to obtain the Average DL Throughput for each
PS R99 Service.
Associated VS.PS.Bkg.Kbps.DL8
Counters VS.PS.Bkg.Kbps.DL16
VS.PS.Bkg.Kbps.DL32
VS.PS.Bkg.Kbps.DL64
VS.PS.Bkg.Kbps.DL128
VS.PS.Bkg.Kbps.DL144
VS.PS.Bkg.Kbps.DL256
VS.PS.Bkg.Kbps.DL384
VS.PS.Int.Kbps.DL8
VS.PS.Int.Kbps.DL16
VS.PS.Int.Kbps.DL32
VS.PS.Int.Kbps.DL64
VS.PS.Int.Kbps.DL128
VS.PS.Int.Kbps.DL144
VS.PS.Int.Kbps.DL256
VS.PS.Int.Kbps.DL384
VS.PS.Str.Kbps.DL8
VS.PS.Str.Kbps.DL16
VS.PS.Str.Kbps.DL32
VS.PS.Str.Kbps.DL64
VS.PS.Str.Kbps.DL128
VS.PS.Str.Kbps.DL144
VS.PS.Str.Kbps.DL256
VS.PS.Str.Kbps.DL384
VS.PS.Conv.Kbps.DL
Object CELL
Unit/Range Kbit/s
Note None
Description These counters provide the UL BLER of AMR and CS 64K Conv. services
on the DCH in the best cell. The counters are triggered in the best cell when
the number of UL TBs carrying the CS services on the DCH reaches the
defined sampling window (500 TBs).
Associated VS.ULBler.AMR
Counters VS.ULBler.CS64
Object CELL
Unit/Range %
Note None
Description This counter provides the UL BLER of PS services on the DCH in the best
cell.
The counters are triggered in the best cell when the number of UL TBs
carrying the PS services on the DCH reaches the defined sampling window
(500 TBs).
Associated VS.ULBler.PS.BE.DCH.8
Counters VS.ULBler.PS.BE.DCH.16
VS.ULBler.PS.BE.DCH.32
VS.ULBler.PS.BE.DCH.64
VS.ULBler.PS.BE.DCH.128
VS.ULBler.PS.BE.DCH.144
VS.ULBler.PS.BE.DCH.256
VS.ULBler.PS.BE.DCH.384
VS.ULBler.PS.BE.RACH
VS.ULBler.PS.Conv
VS.ULBler.PS.Str
Object CELL
Unit/Range %
Note None
Description This counter indicates the mean downlink throughput for ONE HSDPA UE
in a cell.
When the data is transferred to an HSDPA serving cell, the RNC measures
the data transfer time of all the UEs and the total bytes sent in the cell. At the
end of the measurement period, the RNC divides the total bytes by the total
data transfer time to obtain the mean downlink throughput of MAC-d flow
in the cell. The RLC header and the retransmitted data are excluded.
Associated VS.HSDPA.MeanChThroughput
Counters
Object CELL
Unit/Range Kbit/s
Note None
Description This counter provides the MAC-hs throughput when at least one HSDPA user
is transferring data at the physical layer during the entire measurement period.
Associated VS.DataOutput.Mean/(VS.DataTtiRatio.Mean-
Counters VS.HSDPA.InactiveDataTtiRatio.Mean)
Object NodeB
Unit/Range Kbit/s
Note We can apply the following formula to get the Mean HSDPA Cell Throughput
within RNC approximately:
HSDPA Cell Throughput (RNC Cell) =
VS.HSDPA.MeanChThroughput.TotalBytes x 8/[{SP} x 60]/1000
Where:
l {SP} is the Statistic Period with the unit of Minute.
l The KPI may not be accurate under the following condition: there is no
HSDPA User transferring data for a while during the total measurement
period. Therefore, the KPI should be evaluated during busy hour for
accuracy.
Description This counter indicates the mean downlink throughput for ONE HSUPA UE
in a cell.
When the data is received in HSUPA active cells, the RNC measures the data
transfer time of all the UEs and the total bytes received in the cell. At the end
of the measurement period, the RNC divides the total bytes by the total data
transfer time to obtain the mean uplink throughput of MAC-d flow in the cell.
The RLC header and the retransfer data are excluded.
Associated VS.HSUPA.MeanChThroughput
Counters
Object CELL
Unit/Range Kbit/s
Note None
Description This counter provides the Mean HSUPA Cell Throughput when at least one
HSUPA user is transferring data during the entire measurement period.
Average bit rate of MAC-d data flows that the NodeB receives successfully
from all users over the time when data is transferred during a measurement
period. The time when there is data transfer during a measurement period is
calculated as follows: Sampling times of data transfer x length of the sampling
period If the number of received MAC-d PDU bits is 0 in a certain sampling
period, which is 10 ms in length, the NodeB does not count this period.
Associated VS.HSUPA.MeanBitRate.WithData
Counters
Object NodeB
Unit/Range Kbit/s
Note We can apply the following formula to get the Mean HSUPA Cell Throughput
within the RNC approximately:
HSUPA Cell Throughput (RNC Cell) =
VS.HSUPA.MeanChThroughput.TotalBytes x 8/[{SP} x 60]/1000
Where:
{SP} is the Statistic Period with the unit of Minute.
The KPI may not be accurate under the following condition: there is no
HSUPA User transferring data for a while during the total measurement
period. Therefore, the KPI should be evaluated during busy hour for accuracy.
Description This measurement item provides the Average or Max uplink throughput for
PS services within an RNC.
l Measurement point for Average UL Throughput
The RNC periodically samples the uplink traffic values of the related PS
services in the PS domain. At the end of the measurement period, the RNC
divides the accumulated values by the number of samples to obtain the
mean uplink traffic of all the PS services in the PS domain. The uplink
traffic of all the PS services in the PS domain refers to the traffic obtained
at the RLC layer. The data does not include the RLC head data.
l Measurement point for Max UL Throughput
The RNC periodically samples uplink traffic values of all the related PS
services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum uplink traffic of all the services in the PS domain
within the RNC. The uplink traffic of all the services in the PS domain
refers to the traffic obtained at the RLC layer. The data does not include
the RLC head data.
Associated VS.R99PSLoad.ULThruput.RNC
Counters VS.R99PSLoad.MaxULThruput.RNC
VS.HSUPAPSLoad.ULThruput.RNC
VS.HSUPAPSLoad.MaxULThruput.RNC
Object RNC
Unit/Range kbit/s
Note None
Description These counters provide the Average or Max downlink throughput for PS
services within an RNC.
l Measurement point for Average DL Throughput
The RNC periodically samples the downlink traffic values of the related
PS services in the PS domain. At the end of the measurement period, the
RNC divides the accumulated values by the number of samples to obtain
the mean downlink traffic of all the PS services in the PS domain. The
downlink traffic of all the PS services in the PS domain refers to the traffic
obtained at the RLC layer. The data does not include the RLC head data.
l Measurement point for Max DL Throughput
The RNC periodically samples the downlink traffic values of all the
related PS services in the PS domain. At the end of the measurement
period, the RNC calculates the maximum downlink traffic of all the
services in the PS domain within the RNC. The downlink traffic of all the
services in the PS domain refers to the traffic obtained at the RLC layer.
The data does not include the RLC head data.
Associated VS.R99PSLoad.DLThruput.RNC
Counters VS.HSDPAPSLoad.DLThruput.RNC
VS.R99PSLoad.MaxDLThruput.RNC
VS.HSDPAPSLoad.MaxDLThruput.RNC
VS.MBMSPSLoad.DLThruput.RNC
VS.MBMSPSLoad.MaxDLThruput.RNC
Object RNC
Unit/Range kbit/s
Note None
Description These KPIs are used to check the throughput of MBMS service in a cell.
Associated VS.MBMS.PTM.MeanThroughput
Counters VS.MBMS.PTP.MeanThroughput
Object CELL
Unit/Range kbit/s
Note None
3.7 Traffic
Traffic-related KPIs are used to check the circulated traffic such as CS Equivalent Erlang, PS
Traffic, and Mean UE number for various kinds of services in an RNC or a Cluster.
Description VS.CSLoad.Erlang.Equiv.RNC
This KPI provides the equivalent Erlang values of all the services in the CS
domain in the RNC.
The RNC periodically takes the samples from the equivalent Erlang values
of all the services in the CS domain. At the end of the measurement period,
the RNC divides the accumulated equivalent Erlang values by the number
of samples to obtain the mean equivalent Erlang values of all the services
in the CS domain.
Each time a CS domain service is established, the RNC converts its rate to
the equivalent Erlang, and then increases the equivalent Erlang of the CS
domain in the current RNC.
Each time a CS domain service is released, the RNC converts its rate to the
equivalent Erlang and decreases the equivalent Erlang of the CS domain in
the current RNC.
VS.CSLoad.MaxErlang.Equiv.RNC
This KPI provides the maximum equivalent Erlang values of all the services
in the CS domain within the RNC.
The RNC periodically takes a sample from the equivalent Erlang values of
all the services in the CS domain. At the end of the period, the RNC
calculates the maximum equivalent Erlang of all the services in the CS
domain within the RNC.
Each time a CS domain service is established, the RNC converts its rate to
the equivalent Erlang, and then increases the equivalent Erlang of the CS
domain in the current RNC.
Each time a CS domain service is released, the RNC decreases the
equivalent Erlang of the CS domain in the current RNC.
Associated VS.CSLoad.Erlang.Equiv.RNC
Counters VS.CSLoad.MaxErlang.Equiv.RNC
Object RNC
Unit/Range Erl
Note None
Description These counters provide the number of CS (AMR and VP) users with different
UL and DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At
the end of the measurement period, the value of each counter is obtained as
follows: dividing the accumulated value of each sampling point by the
number of sampling times.
Unit/Range None
Note The Unit is average user number, to get Erlang, the counter value should be
multiplied by {SP}/60, where {SP} is the measurement period (unit: minute).
For a VP service, V1 platform equals to four Erlangs and V2 platform equals
to two Erlangs.
Description These counters provide the number of PS R99 users with different UL and
DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At
the end of the measurement period, the value of each counter is obtained as
follows: dividing the accumulated value of each sampling point by the
number of sampling times.
VS.RB.PS.Int.DL.16
VS.RB.PS.Int.DL.32
VS.RB.PS.Int.DL.64
VS.RB.PS.Int.DL.128
VS.RB.PS.Int.DL.144
VS.RB.PS.Int.DL.256
VS.RB.PS.Int.DL.384
VS.RB.PS.Conv.DL.42.8
VS.RB.PS.Conv.DL.40
VS.RB.PS.Conv.DL.39.2
VS.RB.PS.Conv.DL.38.8
VS.RB.PS.Str.DL.8
VS.RB.PS.Str.DL.16
VS.RB.PS.Str.DL.32
VS.RB.PS.Str.DL.64
VS.RB.PS.Str.DL.128
VS.RB.PS.Str.DL.144
VS.RB.PS.Str.DL.256.384
VS.RB.PS.Conv.DL.64
RNC Counters
l UL Counters:
VS.RB.PS.Bkg.UL.8.RNC
VS.RB.PS.Bkg.UL.16.RNC
VS.RB.PS.Bkg.UL.32.RNC
VS.RB.PS.Bkg.UL.64.RNC
VS.RB.PS.Bkg.UL.128.RNC
VS.RB.PS.Bkg.UL.144.RNC
VS.RB.PS.Bkg.UL.256.RNC
VS.RB.PS.Bkg.UL.384.RNC
VS.RB.PS.Int.UL.8.RNC
VS.RB.PS.Int.UL.16.RNC
VS.RB.PS.Int.UL.32.RNC
VS.RB.PS.Int.UL.64.RNC
VS.RB.PS.Int.UL.128.RNC
VS.RB.PS.Int.UL.144.RNC
VS.RB.PS.Int.UL.256.RNC
VS.RB.PS.Int.UL.384.RNC
VS.RB.PS.Str.UL.8.RNC
VS.RB.PS.Str.UL.16.RNC
VS.RB.PS.Str.UL.32.RNC
VS.RB.PS.Str.UL.64.RNC
VS.RB.PS.Str.UL.128.RNC
VS.RB.PS.Str.UL.144.RNC
VS.RB.PS.Str.UL.256.384.RNC
VS.RB.PS.Conv.UL.8.RNC
VS.RB.PS.Conv.UL.16.RNC
VS.RB.PS.Conv.UL.32.RNC
VS.RB.PS.Conv.UL.64.RNC
VS.RB.PS.Conv.UL.38.8.RNC
VS.RB.PS.Conv.UL.42.8.RNC
VS.RB.PS.Conv.UL.40.RNC
VS.RB.PS.Conv.UL.39.2.RNC
l DL Counters:
VS.RB.PS.Bkg.DL.8.RNC
VS.RB.PS.Bkg.DL.16.RNC
VS.RB.PS.Bkg.DL.32.RNC
VS.RB.PS.Bkg.DL.64.RNC
VS.RB.PS.Bkg.DL.128.RNC
VS.RB.PS.Bkg.DL.144.RNC
VS.RB.PS.Bkg.DL.256.RNC
VS.RB.PS.Bkg.DL.384.RNC
VS.RB.PS.Int.DL.8.RNC
VS.RB.PS.Int.DL.16.RNC
VS.RB.PS.Int.DL.32.RNC
VS.RB.PS.Int.DL.64.RNC
VS.RB.PS.Int.DL.128.RNC
VS.RB.PS.Int.DL.144.RNC
VS.RB.PS.Int.DL.256.RNC
VS.RB.PS.Int.DL.384.RNC
VS.RB.PS.Str.DL.8.RNC
VS.RB.PS.Str.DL.16.RNC
VS.RB.PS.Str.DL.32.RNC
VS.RB.PS.Str.DL.64.RNC
VS.RB.PS.Str.DL.128.RNC
VS.RB.PS.Str.DL.144.RNC
VS.RB.PS.Str.DL.256.384.RNC
VS.RB.PS.Conv.DL.8.RNC
VS.RB.PS.Conv.DL.16.RNC
VS.RB.PS.Conv.DL.32.RNC
VS.RB.PS.Conv.DL.64.RNC
VS.RB.PS.Conv.DL.42.8.RNC
VS.RB.PS.Conv.DL.40.RNC
VS.RB.PS.Conv.DL.39.2.RNC
VS.RB.PS.Conv.DL.38.8.RNC
Unit/Range None
Note The Unit is average user number, to get Erlang, should be multiplied by {SP}/
60;
Description This KPI provides the mean, maximum and minimum number of HSDPA
UEs in an HSDPA serving cell.
The RNC periodically samples the number of HSDPA UEs in the HSDPA
serving cell. At the end of the measurement period, the RNC obtains the mean
and maximum number of HSDPA UEs.
Associated VS.HSDPA.UE.Mean.Cell
Counters VS.HSDPA.UE.Max.Cell
Object CELL
Unit/Range None
Note None
Description These KPIs provide the mean and maximum number of HSUPA UEs in an
HSUPA serving cell.
The RNC periodically samples the number of HSUPA UEs in the HSUPA
serving cell. At the end of the measurement period, the RNC obtains the mean
and maximum number of HSUPA UEs.
Associated VS.HSUPA.UE.Mean.Cell
Counters VS.HSUPA.UE.Max.Cell
Object CELL
Unit/Range None
Description This KPI provides the average number of UEs that are carried on the E-FACH
in the cell
The system periodically samples the UEs that are carried on the EFACH. At
the end of the measurement period, the average number of UEs that are carried
on the E-FACH in the measurement period is obtained by dividing the
accumulated value of sample data in the period by the number of samples.
Associated VS.EFACHUEs
Counters
Object CELL
Unit/Range None
Description This KPI provides the average number of CS over HSPA users in the cell.
The system periodically samples the number of CS Over HSPA. At the end
of a statistical period, the system divides the sampling number by the sum at
each sampling point to obtain the average number of CS Over HSPA during
the period.
Associated VS.HSPA.UE.Mean.CS.Conv.Cell
Counters
Object CELL
Unit/Range None
Description This KPI provides the average number of HSDPA 64QAM UEs in an HSDPA
cell.
The number of HSDPA 64QAM UEs is sampled periodically in the HSDPA
cells. At the end of the measurement period, the RNC divides the accumulated
time weight value of each sampling point by the sampling period, thus
obtaining the average number of 64QAM UEs in the HSDPA cell.
Associated VS.HSDPA.64QAM.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
Description This KPI provides the average number of HSDPA MIMO UEs in an HSDPA
cell.
The number of HSDPA MIMO UEs is sampled periodically in the HSDPA
cells. At the end of the measurement period, the RNC divides the accumulated
time weight value of each sampling point by the sampling period, thus
obtaining the average number of MIMO UEs in the HSDPA cell.
Associated VS.HSDPA.MIMO.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
Description This KPI provides the average number of HSUPA 16QAM UEs in an HSUPA
cell.
The number of HSUPA 16QAM UEs is sampled periodically in the HSUPA
cells. At the end of the measurement period, the RNC divides the accumulated
time weight value of each sampling point by the sampling period, thus
obtaining the average number of 16QAM UEs in the HSUPA cell.
Associated VS.HSUPA.16QAM.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
Description This KPI provides the average number of HSDPA MIMO64QAM UEs in an
HSDPA cell.
The system periodically samples the number of MIMO+64QAM UEs. At the
end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of MIMO
+64QAM UEs in the measurement period is obtained.
Associated VS.HSDPA.MIMO64QAM.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
Description The previous measurement counter provides the mean number of UEs that
subscribes to MBMS channel in PTP mode in a cell.
If the MBMS channel is in PTP mode, the number of cell_MBMS UEs is
reported when a connected UE orders or releases the program in the cell.
When the MBMS channel switches from PTM to PTP, the number of UEs
that have currently ordered the program in the cell is reported. When the
MBMS channel switches from PTP to PTM, the number of UEs that have
ordered the program in PTP mode is reported as 0.
Associated VS.MBMS.PTP.UE.Channel0.Mean.Cell
Counters VS.MBMS.PTM.UE.Channel0.Mean.Cell
VS.MBMS.PTP.UE.Channel1.Mean.Cell
VS.MBMS.PTM.UE.Channel1.Mean.Cell
VS.MBMS.PTP.UE.Channel2.Mean.Cell
VS.MBMS.PTM.UE.Channel2.Mean.Cell
VS.MBMS.PTP.UE.Channel3.Mean.Cell
VS.MBMS.PTM.UE.Channel3.Mean.Cell
VS.MBMS.PTP.UE.Channel4.Mean.Cell
VS.MBMS.PTM.UE.Channel4.Mean.Cell
Object CELL
Unit/Range None
Description This KPI provides the total downlink bytes of all the HSDPA MAC-d flows
in a cell.
When the data is transmitted to an HSDPA serving cell, the RNC measures
the number of total bytes sent in the downlink (including data of all types of
services) at the RLC layer for the MAC-d flow in the cell. The RLC header
and the retransmitted data are excluded.
Associated VS.HSDPA.MeanChThroughput.TotalBytes
Counters
Object CELL
Unit/Range byte
Note None
Description This counter provides the total uplink bytes of all the HSUPA MAC-d flows
in a cell.
When data is received in HSUPA active cells, the RNC measures the number
of total bytes received in the uplink (including data of different services) at
the RLC layer for the MAC-d flow in the cell. The RLC header and the
retransmitted data are excluded.
Associated VS.HSUPA.MeanChThroughput.TotalBytes
Counters
Object CELL
Unit/Range byte
Note None
Description These KPIs provide the uplink traffic volume of different R99 services in all
cells of the active set.
The UL traffic volume (excluding the RLC header and the retransmitted data)
of each kind of R99 services over the RLC layer are accumulated for all cells
of the active set within SRNC.
Associated l CS Domain:
Counters (VS.RB.AMR.UL.12.2 x 12200 +
VS.RB.AMR.UL.10.2 x 10200 +
VS.RB.AMR.UL.7.95 x 7950 +
VS.RB.AMR.UL.7.4 x 7400 +
VS.RB.AMR.UL.5.9 x 5900 +
VS.RB.AMR.UL.5.15 x 5150 +
VS.RB.AMR.UL.4.75 x 4750) x {SP} x 60
l PS Domain:
VS.PS.Bkg.UL.8.Traffic
VS.PS.Bkg.UL.16.Traffic
VS.PS.Bkg.UL.32.Traffic
VS.PS.Bkg.UL.64.Traffic
VS.PS.Bkg.UL.128.Traffic
VS.PS.Bkg.UL.144.Traffic
VS.PS.Bkg.UL.256.Traffic
VS.PS.Bkg.UL.384.Traffic
VS.PS.Int.UL.8.Traffic
VS.PS.Int.UL.16.Traffic
VS.PS.Int.UL.32.Traffic
VS.PS.Int.UL.64.Traffic
VS.PS.Int.UL.128.Traffic
VS.PS.Int.UL.144.Traffic
VS.PS.Int.UL.256.Traffic
VS.PS.Int.UL.384.Traffic
VS.PS.Str.UL.8.Traffic
VS.PS.Str.UL.16.Traffic
VS.PS.Str.UL.32.Traffic
VS.PS.Str.UL.64.Traffic
VS.PS.Str.UL.128.Traffic
VS.PS.Conv.UL.Traffic
Object CELL
Unit/Range bit
Note None
Description These KPIs provide the downlink traffic volume of different R99 services in
all cells of the active set.
The DL traffic volume (excluding the RLC header and the retransmitted data)
of each kind of R99 services over the RLC layer are accumulated for all cells
of the active set within SRNC.
Associated l CS Domain:
Counters (VS.RB.AMR.DL.12.2 x 12200 +
VS.RB.AMR.DL.10.2 x 10200 +
VS.RB.AMR.DL.7.95 x 7950 +
VS.RB.AMR.DL.7.4 x 7400 +
VS.RB.AMR.DL.5.9 x 5900 +
VS.RB.AMR.DL.5.15 x 5150 +
VS.RB.AMR.DL.4.75 x 4750) x {SP} x 60
VS.CS.Conv.DL.64.Traffic
VS.CS.Str.DL.57.6.Traffic
l PS Domain:
VS.PS.Bkg.DL.8.Traffic
VS.PS.Bkg.DL.16.Traffic
VS.PS.Bkg.DL.32.Traffic
VS.PS.Bkg.DL.64.Traffic
VS.PS.Bkg.DL.128.Traffic
VS.PS.Bkg.DL.144.Traffic
VS.PS.Bkg.DL.256.Traffic
VS.PS.Bkg.DL.384.Traffic
VS.PS.Int.DL.8.Traffic
VS.PS.Int.DL.16.Traffic
VS.PS.Int.DL.32.Traffic
VS.PS.Int.DL.64.Traffic
VS.PS.Int.DL.128.Traffic
VS.PS.Int.DL.144.Traffic
VS.PS.Int.DL.256.Traffic
VS.PS.Int.DL.384.Traffic
VS.PS.Str.DL.8.Traffic
VS.PS.Str.DL.16.Traffic
VS.PS.Str.DL.32.Traffic
VS.PS.Str.DL.64.Traffic
VS.PS.Str.DL.128.Traffic
VS.PS.Str.DL.144.Traffic
VS.PS.Str.DL.256.Traffic
VS.PS.Str.DL.384.Traffic
VS.PS.Conv.DL.Traffic
Object CELL
Unit/Range bit
Note None
Description This KPI provides the number of downlink MAC PDU bytes sent by the
CRNC on the E-FACH over the Iub interface in a cell.
The measurement is triggered when the CRNC sends downlink data on the
E-FACH over the Iub interface.
Associated VS.CRNCIubBytesEFACH.Tx
Counters
Object CELL
Unit/Range byte
Note None