3G KPI Reference PDF

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
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 a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue () Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
1 RAN KPI Reference
1 RAN KPI Reference
About This Chapter
Purpose
This document describes the RAN KPI and the counters used to calculate the KPI. Originally,
the KPI was described based on the commercial network management and radio network
optimization. However, the KPI description is updated from time to time based on the
requirements of customers.
Product Versions
The following table lists the product versions and solution version included in this document.
Product Name Product Version Solution Version
BSC6910 V100R018C00 RAN18.0
BSC6900 V900R018C00
BTS3900 V100R011C00
The mapping single-mode
BTS3900A
base station version is:
BTS3900L NodeB: V200R018C00
BTS3900C
BTS3900AL
DBS3900
BTS3812AE NodeB: V100R018C00
BTS3812A
BTS3812E
DBS3800
Issue () Huawei Proprietary and Confidential 1

1 RAN KPI Reference
Intended Audience
This document is intended for:
l Network planning engineers

l Field engineers
l System engineers
Organization
RAN KPI Reference Summary
1.1 Changes in the RAN KPI Reference

This chapter describes the changes made in the RAN KPI Reference.
1.2 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.
1.3 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
1.4 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an
RNC or a cluster.
1.5 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or
service mode changing in difference scenarios.
1.6 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.
1.7 Service Integrity

Service Integrity KPIs mainly indicate the service capabilities for PS/HSPA throughput during
busy hours in each cell and the service UL Average BLER for evaluating the UL BLER value
of services in each cell.
1.8 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.

1 RAN KPI Reference
1.1 Changes in the RAN KPI Reference

This chapter describes the changes made in the RAN KPI Reference.
Draft A (2015-07-30)
This is the Draft A release of RAN18.0.
Compared with Issue 02 (2015-05-08) of RAN17.1, this issue does not include any changes.
1.2 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.
1.2.1 IU Paging Success Ratio
Table 1-1 IU Paging Success Ratio
Name IU Paging Success Ratio
Formula IU Paging Success Ratio = (Number of SuccessfulPaging Messages to UEs

in Idle Mode/Number of Paging Messages to UEs in Idle Mode) x 100%
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.
Associated IU Paging Success Ratio =

Counters (VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE) x
100%
Object RNC
Unit/Range %
Note In redirection-based CSFB scenarios, the VS.RANAP.Paging.Succ.IdleUE

counter is measured when the following conditions are met: (1) A UE is
redirected to a UMTS network after receiving a paging message on a LTE
network. (2) The UE then sends the RNC an RRC Connection Request
message with the cause value "Terminating Conversational Call." Under
these circumstances, the calculated Iu paging success rate is greater than its
actual value and may even be greater than 100%.

1 RAN KPI Reference
1.2.2 RRC Setup Success Ratio

Table 1-2 RRC Setup Success Ratio
Name RRC Setup Success Ratio
Formula RRC Setup Success Ratio =(Number of RRC Setup Successes/Number of

RRC Connection Attempts)x 100%
Description Description of RRC Setup Success Ratio for service requests:

l The RRC Connection Attempt for service 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 requested by the UE: Conversational Call, Streaming Call,
Background Call, Interactive Call, Originating Subscribed Traffic Call,
Emergency Call, High Priority Signaling, Low Priority Signaling, Cause
Unknown, Call Re-Establishment. For details on the reason types, see
section 10.3.3.11 in 3GPP TS 25.331.
l The RRC Setup Success for Service Procedure is complete when the RNC
receives an RRC CONNECTION SETUP COMPLETE message from the
UE.
Description of RRC Setup Success Ratio for other causes:
l RRC Connection Attempt for Other reasons 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 requested by the UE: Inter-RAT cell re-selection, Inter-RAT cell
change order, Registration and Detach.
l The RRC Setup Success for Other reasons Procedure is complete when
the RNC receives an RRC CONNECTION SETUP COMPLETE message
from the UE.

1 RAN KPI Reference
Associated l RRC Setup Success Ratio (Cell.Service) =

Counters [(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.OrgStrCall+
RRC.SuccConnEstab.OrgInterCall+
RRC.SuccConnEstab.OrgBkgCall+
RRC.SuccConnEstab.OrgSubCall+
RRC.SuccConnEstab.TmConvCall+
RRC.SuccConnEstab.TmStrCall+
RRC.SuccConnEstab.TmItrCall+
RRC.SuccConnEstab.TmBkgCall+
RRC.SuccConnEstab.EmgCall+
RRC.SuccConnEstab.Unkown+
RRC.SuccConnEstab.OrgHhPrSig+
RRC.SuccConnEstab.OrgLwPrSig+
RRC.SuccConnEstab.CallReEst+
RRC.SuccConnEstab.TmHhPrSig+
RRC.SuccConnEstab.TmLwPrSig)/
(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.OrgStrCall+
RRC.AttConnEstab.OrgInterCall +
RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.OrgSubCall+
RRC.AttConnEstab.TmConvCall+
RRC.AttConnEstab.TmStrCall+
RRC.AttConnEstab.TmInterCall+
RRC.AttConnEstab.TmBkgCall+
RRC.AttConnEstab.EmgCall+
RRC.AttConnEstab.Unknown+
RRC.AttConnEstab.OrgHhPrSig+
RRC.AttConnEstab.OrgLwPrSig+
RRC.AttConnEstab.CallReEst+
RRC.AttConnEstab.TmHhPrSig+
RRC.AttConnEstab.TmLwPrSig )] x 100%
l RRC Setup Success Ratio (Cell.Other) =
[(RRC.SuccConnEstab.IRATCelRes+
RRC.SuccConnEstab.IRATCCO+
RRC.SuccConnEstab.Reg+
RRC.SuccConnEstab.Detach)/
(RRC.AttConnEstab.IRATCelRes+

1 RAN KPI Reference
RRC.AttConnEstab.IRATCCO+
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.
The following counters provide the number of RRC connection setup requests
that are resent after the first RRC connection setup request of the UE is
rejected due to resource insufficiency. You can subtract these counters from
the denominator of the formula to increase the value of this KPI:
l RRC.AttConnEstab.Rep.OrgConvCall
l RRC.AttConnEstab.Rep.OrgStrCall
l RRC.AttConnEstab.Rep.OrgInterCall
l RRC.AttConnEstab.Rep.OrgBkgCall
l RRC.AttConnEstab.Rep.TmConvCall
l RRC.AttConnEstab.Rep.TmStrCall
l RRC.AttConnEstab.Rep.TmInterCall
l RRC.AttConnEstab.Rep.TmBkgCall
l RRC.AttConnEstab.Rep.OrgSubCall
l RRC.AttConnEstab.Rep.EmgCall
l RRC.AttConnEstab.Rep.IRATCelRes
l RRC.AttConnEstab.Rep.IRATCCO
l RRC.AttConnEstab.Rep.Reg
l RRC.AttConnEstab.Rep.Detach
l RRC.AttConnEstab.Rep.OrgHhPrSig
l RRC.AttConnEstab.Rep.OrgLwPrSig
l RRC.AttConnEstab.Rep.CallReEst
l RRC.AttConnEstab.Rep.TmHhPrSig
l RRC.AttConnEstab.Rep.TmLwPrSig
l RRC.AttConnEstab.Rep.Unknown
The formula of CS and PS radio access success ratio refer to the 1.2.6 PS
Radio Access Success Ratio and 1.2.8 CS Radio Access Success Ratio
directly.

1 RAN KPI Reference
1.2.3 RRC Setup Success Ratio (PCH)

Table 1-3 RRC Setup Success Ratio (PCH)
Name RRC Setup Success Ratio (PCH)
Formula RRC Setup Success Ratio (PCH) = (Number of RRC Setup Successes/
Number of RRC Connection Attempts) x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "RRC Setup Success Ratio", this
formula includes statistics of connection setups for cell updates initiated by
UEs in the CELL_PCH or URA_PCH state.
If the PCH state switch is turned on, UEs will remain in the always online
state. If a UE has not transmitted data for a certain period of time, it will transit
from the CELL_FACH or CELL_DCH state to the CELL_PCH or
URA_PCH state, instead of the idle mode. In this way, the number of RRC
and RAB setup attempts and successful RRC connection setups decreases
dramatically, affecting the RRC Setup Success Ratio.
UEs do not transmit data in the CELL/URA_PCH state or idle mode. When
they need to transmit data, they will transit to the CELL_FACH or
CELL_DCH state. The state transition procedure from CELL/URA_PCH to
CELL_FACH/CELL_DCH is the same as the RRC and RAB setup
procedures. Therefore, the statistics of connection setups for cell updates
initiated by UEs in the CELL_PCH or URA_PCH state are included in the
formula for calculating the RRC Setup Success Ratio (PCH).
Description of RRC Setup Success Ratio (PCH) for service requests.
l Number of RRC Connection Attempts (PCH)
– After the RNC receives an RRC CONNECTION REQUEST message
from a UE, this counter is measured in the cell that the UE camps on
based on the cause for the RRC connection setup request. The causes
include the following: Conversational Call, Streaming Call,
Background Call, Interactive Call, Originating Subscribed Traffic
Call, Emergency Call, High Priority Signaling, Low Priority
Signaling, Cause Unknown, and Call Re-Establishment.
– After the RNC receives a CELL UPDATE message from a UE in the
CELL/URA_PCH state, this counter is measured in the cell that the
UE camps on when the following conditions are met: The value of the
Cell update cause IE carried in this message is "uplink data
transmission" or "paging response". The value of the Establishment
Cause IE is "Originating Conversational Call", "Originating Streaming
Call", "Originating Interactive Call", "Originating Background Call",
"Originating Subscribed traffic Call", "Terminating Conversational
Call", "Terminating Streaming Call", "Terminating Interactive Call",
"Terminating Background Call", "Emergency Call", "Inter-RAT cell
re-selection", "Inter-RAT cell change order", "Originating High
Priority Signalling", "Originating Low Priority Signalling", "Call re-
establishment", "Terminating High Priority Signalling", "Terminating
Low Priority Signalling", or "Terminating-cause unknown", or the
Establishment Cause IE is not carried in this message.
l Number of RRC Setup Successes (PCH)
– After the RNC receives an RRC CONNECTION SETUP COMPLETE
message from a UE, this counter is measured in the cell that the UE
camps on based on the cause for the RRC connection setup request.
– The RNC receives a CELL UPDATE message from a UE in the CELL/
URA_PCH state and the CELL UPDATE message meets the
following conditions:

1 RAN KPI Reference
– The value of the Cell update cause IE is "uplink data transmission"

or "paging response".
– The value of the Establishment Cause IE is "Originating
Conversational Call", "Originating Streaming Call", "Originating
Interactive Call", "Originating Background Call", "Originating
Subscribed traffic Call", "Terminating Conversational Call",
"Terminating Streaming Call", "Terminating Interactive Call",
"Terminating Background Call", "Emergency Call", "Inter-RAT
cell re-selection", "Inter-RAT cell change order", "Originating
High Priority Signalling", "Originating Low Priority Signalling",
"Call re-establishment", "Terminating High Priority Signalling",
"Terminating Low Priority Signalling", or "Terminating-cause
unknown", or the Establishment Cause IE is not carried in this
message.
When the RNC then receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE or RADIO BEARER
RECONFIGURATION COMPLETE message, this counter is
measured in the cell that the UE camps on based on the cause for the
cell update.
For the classification of establishment causes, see section 10.3.3.11 in
3GPP TS 25.331.
For the classification of cell update causes, see section 10.3.3.3 in
3GPP TS 25.331.
Description of RRC Setup Success Ratio for other causes (PCH)
l Number of RRC Connection Attempts (PCH)
– After the RNC receives an RRC CONNECTION REQUEST message
from a UE, this counter is measured in the cell that the UE camps on
based on the cause for the RRC connection setup request. The causes
include the following: Inter-RAT cell re-selection, Inter-RAT cell
change order, and Registration and Detach.
UE camps on if the CELL UPDATE message meets the following
conditions: The value of the Cell update cause IE carried in this
message is not "uplink data transmission" or "paging response". The
value of the Establishment Cause IE is not "Originating Conversational
Call", "Originating Streaming Call", "Originating Interactive Call",
"Originating Background Call", "Originating Subscribed traffic Call",
"Terminating Conversational Call", "Terminating Streaming Call",
"Terminating Interactive Call", "Terminating Background Call",
"Emergency Call", "Inter-RAT cell re-selection", "Inter-RAT cell
change order", "Originating High Priority Signalling", "Originating
Low Priority Signalling", "Call re-establishment", "Terminating High
Priority Signalling", "Terminating Low Priority Signalling", or
"Terminating-cause unknown".
l Number of RRC Setup Successes (PCH)

1 RAN KPI Reference
– After the RNC receives an RRC CONNECTION SETUP COMPLETE

message from a UE, this counter is measured in the cell that the UE
– The value of the Cell update cause IE is not "uplink data
transmission" or "paging response".
– The value of the Establishment Cause IE is not "Originating
"Terminating Low Priority Signalling", or "Terminating-cause
unknown".
RECONFIGURATION COMPLETE message, this counter is measured
in the cell that the UE camps on based on the cause for the cell update.

1 RAN KPI Reference
Associated l RRC Setup Success Ratio with PCH ( Cell.Service) =

Counters {[(RRC.SuccConnEstab.OrgConvCall +
RRC.SuccConnEstab.OrgStrCall +
RRC.SuccConnEstab.OrgInterCall+
RRC.SuccConnEstab.OrgBkgCall +
RRC.SuccConnEstab.OrgSubCall +
RRC.SuccConnEstab.TmConvCall +
RRC.SuccConnEstab.TmStrCall +
RRC.SuccConnEstab.TmItrCall +
RRC.SuccConnEstab.TmBkgCall +
RRC.SuccConnEstab.EmgCall +
RRC.SuccConnEstab.Unkown +
RRC.SuccConnEstab.OrgHhPrSig +
RRC.SuccConnEstab.OrgLwPrSig +
RRC.SuccConnEstab.CallReEst +
RRC.SuccConnEstab.TmHhPrSig +
RRC.SuccConnEstab.TmLwPrSig)+
(VS.SuccCellUpdt.PageRsp+
VS.SuccCellUpdt.ULDataTrans-
VS.SuccCellUpdt.Reg.PCH-
VS.SuccCellUpdt.Detach.PCH-
VS.SuccCellUpdt.Other.PCH)]/
[(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.OrgStrCall+
RRC.AttConnEstab.OrgInterCall+
RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.OrgSubCall+
RRC.AttConnEstab.TmStrCall+
RRC.AttConnEstab.TmInterCall+
RRC.AttConnEstab.TmBkgCall+
RRC.AttConnEstab.EmgCall+
RRC.AttConnEstab.Unknown+
RRC.AttConnEstab.OrgHhPrSig+
RRC.AttConnEstab.OrgLwPrSig+
RRC.AttConnEstab.CallReEst+
RRC.AttConnEstab.TmHhPrSig+
RRC.AttConnEstab.TmLwPrSig )+
(VS.AttCellUpdt.PageRsp +

1 RAN KPI Reference
VS.AttCellUpdt.ULDataTrans -
VS.AttCellUpdt.Reg.PCH -
VS.AttCellUpdt.Detach.PCH -
VS.AttCellUpdt.Other.PCH )]} x 100%
l RRC Setup Success Ratio with PCH (Cell.Other) =
{[(RRC.SuccConnEstab.IRATCelRes +
RRC.SuccConnEstab.IRATCCO +
RRC.SuccConnEstab.Reg +
RRC.SuccConnEstab.Detach)+
(VS.SuccCellUpdt.Reg.PCH +
VS.SuccCellUpdt.Detach.PCH +
VS.SuccCellUpdt.Other.PCH)]/
[(RRC.AttConnEstab.IRATCelRes +
RRC.AttConnEstab.IRATCCO +
RRC.AttConnEstab.Reg +
RRC.AttConnEstab.Detach)+
(VS.AttCellUpdt.Reg.PCH +
VS.AttCellUpdt.Detach.PCH +
VS.AttCellUpdt.Other.PCH)]} x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
Note The RNC-level KPI is obtained by aggregating values of cell-level counters.

CELLUPDATE_MEASUREMENT_OPT_SWITCH under the
OptimizationSwitch3 parameter in the SET URRCTRLSWITCH
command must be selected when you use this KPI. A UE that has initiated a
cell update request in cell 1 sends another CELL UPDATE message in cell
2 while waiting for a response from the RNC or before the UE sends a
response. The cell update procedure completes in cell 2. In this case, the cell
update attempt is measured twice. After this switch is turned on, only the cell
update attempt in cell 2 is measured.
Counters listed below measure the number of RRC connection requests
retransmitted by a UE due to insufficient resources. The number of RRC
connection requests (PCH) retransmitted in this scenario is subtracted from
the total number of RRC connection attempts (the denominator in the
formula). As a result, the RRC Setup Success Ratio (PCH) increases. For CS
RRC Setup Success Ratio and PS RRC Setup Success Ratio, see "PS Radio
Access Success Ratio" and "CS Radio Access Success Ratio."
RRC.AttConnEstab.Rep.OrgConvCall
RRC.AttConnEstab.Rep.OrgStrCall
RRC.AttConnEstab.Rep.OrgInterCall
RRC.AttConnEstab.Rep.OrgBkgCall
RRC.AttConnEstab.Rep.TmConvCall
RRC.AttConnEstab.Rep.TmStrCall
RRC.AttConnEstab.Rep.TmInterCall
RRC.AttConnEstab.Rep.TmBkgCall
RRC.AttConnEstab.Rep.OrgSubCall
RRC.AttConnEstab.Rep.EmgCall
RRC.AttConnEstab.Rep.IRATCelRes
RRC.AttConnEstab.Rep.IRATCCO
RRC.AttConnEstab.Rep.Reg
RRC.AttConnEstab.Rep.Detach
RRC.AttConnEstab.Rep.OrgHhPrSig
RRC.AttConnEstab.Rep.OrgLwPrSig
RRC.AttConnEstab.Rep.CallReEst
RRC.AttConnEstab.Rep.TmHhPrSig
RRC.AttConnEstab.Rep.TmLwPrSig
RRC.AttConnEstab.Rep.Unknown

1 RAN KPI Reference
1.2.4 Radio Access Success Ratio

Table 1-4 Radio Access Success Ratio
Name Radio Access Success Ratio
Formula Radio Access Success Ratio ={RRC Setup Success Ratio(Service) x [(CS
RAB Success + PS RAB Setup Success)/(CS RAB Setup Attempt + PS RAB
Setup Attempt)]} x 100%
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.

1 RAN KPI Reference
Associated l Radio Access Success Ratio (Cell) =

Counters RRC Setup Success Ratio (Cell.Service) x
{[(VS.RAB.SuccEstabCS.Conv +
VS.RAB.SuccEstabCS.Str) +
(VS.RAB.SuccEstabPS.Conv +
VS.RAB.SuccEstabPS.Str +
VS.RAB.SuccEstabPS.Int +
VS.RAB.SuccEstabPS.Bkg)]/
[(VS.RAB.AttEstabCS.Conv +
VS.RAB.AttEstabCS.Str) +
(VS.RAB.AttEstabPS.Conv +
VS.RAB.AttEstabPS.Str +
VS.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg)]} x 100%
l Radio Access Success Ratio (RNC)=
RRC Setup Success Ratio (Cell.Service) x
{[(VS.RAB.SuccEstabCS.Conv.RNC+
VS.RAB.SuccEstabCS.Str.RNC)+
(VS.RAB.SuccEstabPS.Conv.RNC+
VS.RAB.SuccEstabPS.Str.RNC +
VS.RAB.SuccEstabPS.Int.RNC +
VS.RAB.SuccEstabPS.Bkg.RNC)]/
[(VS.RAB.AttEstabCS.Conv.RNC +
VS.RAB.AttEstabCS.Str.RNC) +
(VS.RAB.AttEstabPS.Conv.RNC +
VS.RAB.AttEstabPS.Str.RNC +
VS.RAB.AttEstabPS.Int.RNC +
VS.RAB.AttEstabPS.Bkg.RNC)]} x 100%
Object CELL, RNC
Unit/Range %
Note None
1.2.5 Radio Access Success Ratio (PCH)

Table 1-5 Radio Access Success Ratio (PCH)
Name Radio Access Success Ratio (PCH)

1 RAN KPI Reference
Formula Radio Access Success Ratio (PCH) = RRC Setup Success Ratio (PCH) x
RAB Setup Success Ratio (PCH) x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.4 Radio Access Success Ratio",
this formula includes statistics of connection setups for cell updates initiated
by UEs in the CELL_PCH or URA_PCH state.
URA_PCH state, instead of the idle mode. As a result, the number of RRC
and RAB setup attempts and successful setups decreases dramatically,
affecting the Radio Access Success Ratio.
formula for calculating the Radio Access Success Ratio (PCH).
For the RRC connection setup procedure involved in this KPI, see "RRC
Setup Success Ratio (PCH)." The following part describes the RAB setup
attempt and RAB setup success procedures.
l Number of RAB Setup Attempts (PCH)
– After the RNC receives from the CN a RAB ASSIGNMENT
REQUEST message, this counter is measured in the best cell that the
UE camps on based on the requested service type. The service types
include the following: CS Conversational RAB Establishments, CS
Streaming RAB Establishments, PS Conversational RAB
Establishment, PS Background RAB Establishments, PS Interactive
RAB Establishments, and PS Streaming RAB Establishments.
conditions:
– The value of the Cell update cause IE carried in this message is
"uplink data transmission" or "paging response".
"Terminating Low Priority Signalling", or "Terminating–cause
message.
l Number of RAB Setup Successes (PCH)

1 RAN KPI Reference
– When the RNC sends the CN a RAB ASSIGNMENT RESPONSE

message after receiving from a UE a RADIO BEARER SETUP
COMPLETE message, this counter is measured based on the type of
services successfully established.
message.

1 RAN KPI Reference
Associated l Radio Access Success Ratio (PCH Cell) =

Counters RRC Setup Success Ratio with PCH (Cell.Service) x
{[(VS.RAB.SuccEstabCS.Conv +
VS.RAB.SuccEstabCS.Str) +
(VS.RAB.SuccEstabPS.Conv +
VS.RAB.SuccEstabPS.Str +
VS.RAB.SuccEstabPS.Int +
VS.RAB.SuccEstabPS.Bkg)+
VS.SuccCellUpdt.PageRsp)+
VS.SuccCellUpdt.ULDataTrans)-
(VS.SuccCellUpdt.Reg.PCH+
VS.SuccCellUpdt.Detach.PCH)+
VS.SuccCellUpdt.other.PCH)]/
[(VS.RAB.AttEstabCS.Conv +
VS.RAB.AttEstabCS.Str) +
(VS.RAB.AttEstabPS.Conv +
VS.RAB.AttEstabPS.Bkg)+
VS.AttCellUpdt.ULDataTrans)-
(VS.AttCellUpdt.Reg.DCH +
VS.AttCellUpdt.Detach.DCH +
VS.AttCellUpdt.other.DCH)]}x 100%
Object CELL
Unit/Range %
Note CELLUPDATE_MEASUREMENT_OPT_SWITCH under the

OptimizationSwitch3 parameter in the SET URRCTRLSWITCH command
must be selected when you use this KPI.
A UE that has initiated a cell update request in cell 1 sends another CELL
UPDATE message in cell 2 while waiting for a response from the RNC or
before the UE sends a response. The cell update procedure completes in cell
2. In this case, the cell update attempt is measured twice. After this switch is
turned on, only the cell update attempt in cell 2 is measured.

1 RAN KPI Reference
1.2.6 PS Radio Access Success Ratio
Table 1-6 PS Radio Access Success Ratio
Name PS Radio Access Success Ratio
Formula PS Radio Access Success Ratio = (RRC Setup Success Ratio x PS RAB Setup
Success Ratio) x 100%
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.
Associated l PS Radio Access Success Ratio (Cell) =

Counters [(RRC.SuccConnEstab.OrgBkgCall +
RRC.SuccConnEstab.OrgInterCall +
RRC.SuccConnEstab.TmItrCall)/
(RRC.AttConnEstab.OrgBkgCall +
RRC.AttConnEstab.TmBkgCall +
RRC.AttConnEstab.TmInterCall )] x
PS RAB Setup Success Ratio (Cell) x 100%
l PS Radio Access Success Ratio (RNC) =
[(RRC.SuccConnEstab.OrgBkgCall +
RRC.SuccConnEstab.TmItrCall)/
RRC.AttConnEstab.TmInterCall)] x
PS RAB Setup Success Ratio (RNC) x 100%
Object CELL, RNC
Unit/Range %
Note None

1 RAN KPI Reference
1.2.7 PS Radio Access Success Ratio(PCH)

Table 1-7 PS Radio Access Success Ratio (PCH)
Name PS Radio Access Success Ratio (PCH)
Formula PS Radio Access Success Ratio (PCH) = PS RRC Setup Success Ratio (PCH)
x PS RAB Setup Success Ratio (PCH) x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.6 PS Radio Access Success
Ratio", this formula includes statistics of connection setups for cell updates
initiated by UEs in the CELL_PCH or URA_PCH state for setting up PS
services.
URA_PCH state, instead of the idle mode. As a result, the number of RRC
affecting the PS Radio Access Success Ratio.
formula for calculating the Radio Access Success Ratio (PCH).
For the PS RAB setup procedure involved in this KPI, see "1.2.16 PS RAB
Setup Success Ratio (PCH)." The following part describes the PS RRC setup
attempt and setup success procedures (PCH).
l Number of PS RRC Connection Attempts (PCH)
– After the RNC receives from a UE an RRC CONNECTION
REQUEST message for setting up a PS service, this counter is
RRC connection setup request. This counter does not include the
number of RRC connection setup requests rejected due to service-
based redirections.
UE camps on when the following conditions are met:
unknown".
– The Establishment Cause IE is not carried in this message.
l Number of PS RRC Setup Successes (PCH)

1 RAN KPI Reference
– After the RNC receives from a UE an RRC CONNECTION SETUP

COMPLETE message, this counter is measured in the cell that the UE
URA_PCH state. When the UE returns a PHYSICAL CHANNEL
cell update. The CELL UPDATE message must meet the following
conditions:
unknown".

1 RAN KPI Reference
Associated l PS Radio Access Success Ratio with PCH ( Cell) =

Counters [(RRC.SuccConnEstab.OrgBkgCall +
RRC.SuccConnEstab.TmItrCall)+(
(VS.SuccCellUpdt.PageRsp+
(VS.SuccCellUpdt.Reg.PCH+
VS.SuccCellUpdt.Detach.PCH+
VS.SuccCellUpdt.other.PCH)/
RRC.AttConnEstab.TmInterCall)+
(VS.AttCellUpdt.PageRsp+
(VS.AttCellUpdt.ULDataTrans)-
(VS.AttCellUpdt.Reg.PCH+
VS.AttCellUpdt.Detach.PCH+
VS.AttCellUpdt.other.PCH))] x
PS RAB Setup Success Ratio with PCH (Cell) x 100%
Object CELL
Unit/Range %

1.2.8 CS Radio Access Success Ratio
Table 1-8 CS Radio Access Success Ratio
Name CS Radio Access Success Ratio
Formula CS Radio Access Success Ratio = (RRC Setup Success Ratio x CS RAB Setup
Success Ratio) x 100%

1 RAN KPI Reference
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.
Associated l CS Radio Access Success Ratio (Cell)=

Counters [(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.EmgCall)/
RRC.AttConnEstab.EmgCall)] x
CS RAB Setup Success Ratio (Cell) x 100%
l CS Radio Access Success Ratio (RNC)=
[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.EmgCall)/
RRC.AttConnEstab.EmgCall)] x
CS RAB Setup Success Ratio (RNC) x 100%
Object CELL,RNC
Unit/Range %
Note None
1.2.9 CS Radio Access Success Ratio (PCH)

Table 1-9 CS Radio Access Success Ratio (PCH)
Name CS Radio Access Success Ratio (PCH)
Formula CS Radio Access Success Ratio (PCH) = CS RRC Setup Success Ratio (PCH)
x CS RAB Setup Success Ratio (PCH) x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.8 CS Radio Access Success
initiated by UEs in the CELL_PCH or URA_PCH state for setting up CS
services.
URA_PCH state, instead of the idle mode. As a result, the number of CS RRC
affecting the CS RRC Setup Success Radio and the CS Access Success Ratio.
they need to transmit CS data, they will transit to the CELL_FACH or
CELL_DCH state to establish CS RABs. The state transition procedure from
CELL/URA_PCH to CELL_FACH/CELL_DCH is the same as the RRC
connection setup procedure. Therefore, the statistics of connection setups for
cell updates initiated by UEs in the CELL_PCH or URA_PCH state for setting
up CS services are included in the formula for calculating the CS Radio
Access Success Ratio (PCH).
For the CS RAB setup procedure involved in this KPI, see "1.2.12 CS RAB
Setup Success Ratio." The following part describes the CS RRC setup
attempt and setup success procedures.
l Number of CS RRC Connection Attempts (PCH)
– After the RNC receives from a UE an RRC CONNECTION
REQUEST message for setting up a CS service, this counter is
RRC connection setup request. This counter does not include the
number of RRC connection setup requests rejected due to service-
based redirections.
conditions:
Conversational Call", "Terminating Conversational Call", or
"Emergency Call".
l Number of CS RRC Setup Successes (PCH)
– After the RNC receives from a UE an RRC CONNECTION SETUP
COMPLETE message, this counter is measured in the cell that the UE

1 RAN KPI Reference

Conversational Call", "Terminating Conversational Call", or
"Emergency Call".
3GPP TS 25.331.
For the classification of cell update causes, see section 10.3.3.3 in 3GPP
TS 25.331.
Associated l CS Radio Access Success Ratio with PCH ( Cell)=

Counters {[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.EmgCall)+
(VS.SuccCellUpdt.OrgConvCall.PCH+
VS.SuccCellUpdt.TmConvCall.PCH+
VS.SuccCellUpdt.EmgCall.PCH)]/
[(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.EmgCall)+
(VS.AttCellUpdt.OrgConvCall.PCH+
VS.AttCellUpdt.TmConvCall.PCH+
VS.AttCellUpdt.EmgCall.PCH)]} x
CS RAB Setup Success Ratio (Cell) x 100%
Object CELL
Unit/Range %
Note None
1.2.10 AMR RAB Setup Success Ratio
Table 1-10 AMR RAB Setup Success Ratio
Name AMR RAB Setup Success Ratio
Formula AMR RAB Setup Success Ratio = (Number of AMR RAB Setup Successes/
Number of AMR RAB Setup Attempts) x 100%

1 RAN KPI Reference
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.
Associated AMR RAB Setup Success Ratio(Cell) =

Counters (VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) x 100%
Object CELL
Unit/Range %
Note RNC-level KPIs are obtained by accumulating values of cell-level counters.

If inter-RAT DRD is enabled during RAB setup, an AMR RAB setup is
measured as an AMR RAB setup failure regardless of whether the DRD
succeeds. As a result, the value of this KPI is smaller than actual value.
Therefore, it is recommended that you add VS.IRATHO.SuccOutCS.DR to
the numerator of the formula for calculating this KPI if inter-RAT DRD is
enabled during RAB setup.
1.2.11 VP RAB Setup Success Ratio
Table 1-11 VP RAB Setup Success Ratio
Name VP RAB Setup Success Ratio
Formula VP RAB Setup Ratio = (Number of VP RAB Setup Successes/ Number of

VP RAB Setup Attempts) x 100%
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.
Associated VP RAB Setup Success Ratio (Cell) =

Counters (VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) x 100%
Object CELL

1 RAN KPI Reference
Unit/Range %
1.2.12 CS RAB Setup Success Ratio
Table 1-12 CS RAB Setup Success Ratio
Name CS RAB Setup Success Ratio
Formula CS RAB Setup Success Ratio = (Number of CS RAB Setup Successes/

Number of CS RAB Setup Attempts) x 100%
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.
Associated l CS RAB Setup Success Ratio (Cell) =

Counters [(VS.RAB.SuccEstabCS.Conv+ VS.RAB.SuccEstabCS.Str)/
(VS.RAB.AttEstabCS.Conv+ VS.RAB.AttEstabCS.Str)] x 100%
l CS RAB Setup Success Ratio (RNC) =
[(VS.RAB.SuccEstabCS.Conv.RNC+
VS.RAB.SuccEstabCS.Str.RNC)/
(VS.RAB.AttEstabCS.Conv.RNC+ VS.RAB.AttEstabCS.Str.RNC)]
x 100%
Object CELL, RNC
Unit/Range %
Note If inter-RAT DRD is enabled during RAB setup, a CS RAB setup is measured
as a CS RAB setup failure regardless of whether the DRD succeeds. As a
result, the value of this KPI is smaller than actual value. Therefore, it is
recommended that you add VS.IRATHO.SuccOutCS.DR to the numerator
of the formula for calculating this KPI if inter-RAT DRD is enabled during
RAB setup.
1.2.13 CS+PS Combined Service RAB Setup Success Rate

1 RAN KPI Reference
Table 1-13 CS+PS Combined Service RAB Setup Success Rate
Name CS+PS Combined Service RAB Setup Success Rate
Formula CS+PS Combined Service RAB Setup Success Rate = [(Number of

successfully set up CS+PS combined service RABs)/(Number of CS+PS
combined service RAB setup attempts)] x 100%
Description This KPI provides the setup success rate of CS+PS combined services.
Number of CS+PS combined service RAB setup attempts: When the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message and one
or more RABs of the UE already exists in the cell, the RNC checks the RAB
type carried in the message and determines the combined service type based
on the existing RAB type of the UE. The number of CS+PS combined service
RAB setup attempts is measured in the best cell that the UE camps on if the
combined service type is CS+PS, CS+2PS, or CS+3PS.
Number of successfully set up CS+PS combined service RABs: When the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after
receiving an RADIO BEARER SETUP COMPLETE message from the UE
and one or more RABs of a UE already exists in the cell, the RNC checks the
RAB type and determines the combined service type based on the existing
RAB type of the UE. The number of successfully set up CS+PS combined
service RABs is measured in the best cell that the UE camps on if the
combined service type is CS+PS, CS+2PS, or CS+3PS.
Associated CS+PS RAB Setup Success ratio=

Counters (VS.MultiRAB.SuccEstab.CSPS/VS.MultiRAB.AttEstab.CSPS) * 100%
Object CELL
Unit/Range %
Note None
1.2.14 PS+PS Combined Service RAB Setup Success Rate
Table 1-14 PS+PS Combined Service RAB Setup Success Rate
Name PS+PS Combined Service RAB Setup Success Rate
Formula PS+PS Combined Service RAB Setup Success Rate = [(Number of

successfully set up PS+PS combined service RABs) /(Number of PS+PS
combined service RAB setup attempts)] x 100%

1 RAN KPI Reference
Description This KPI provides the setup success rate of PS+PS combined services.
Number of PS+PS combined service RAB setup attempts: When the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message and one
or more RABs of the UE already exists in the cell, the RNC checks the RAB
type carried in the message and determines the combined service type based
on the existing RAB type of the UE. The number of PS+PS combined service
RAB setup attempts is measured in the best cell that the UE camps on if the
combined service type is 2PS, 3PS, or 4PS.
Number of successfully set up PS+PS combined service RABs: When the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after
receiving an RADIO BEARER SETUP COMPLETE message from the UE
and one or more RABs of a UE already exists in the cell, the RNC checks the
RAB type and determines the combined service type based on the existing
RAB type of the UE. The number of successfully set up PS+PS combined
service RABs is measured in the best cell that the UE camps on if the
combined service type is 2PS, 3PS, or 4PS.
Associated PS+PS RAB Setup Success ratio=

Counters (VS.MultiRAB.SuccEstab.PSPS/VS.MultiRAB.AttEstab.PSPS) x 100%
Object CELL
Unit/Range %
Note None
1.2.15 PS RAB Setup Success Ratio
Table 1-15 PS RAB Setup Success Ratio
Name PS RAB Setup Success Ratio
Formula PS RAB Setup Success Ratio = (Number of PS RAB Setup Successes/

Number of PS RAB Setup Attempts) x 100%
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.

1 RAN KPI Reference
Associated l PS RAB Setup Success Ratio (Cell) =

Counters [(VS.RAB.SuccEstabPS.Conv+
VS.RAB.SuccEstabPS.Str+
VS.RAB.SuccEstabPS.Int+
VS.RAB.SuccEstabPS.Bkg)/
(VS.RAB.AttEstabPS.Conv+
VS.RAB.AttEstabPS.Str+
VS.RAB.AttEstabPS.Int+
VS.RAB.AttEstabPS.Bkg)] x 100%
l PS RAB Setup Success Ratio (RNC) =
[(VS.RAB.SuccEstabPS.Bkg.RNC+
VS.RAB.SuccEstabPS.Str.RNC+
VS.RAB.SuccEstabPS.Conv.RNC+
VS.RAB.SuccEstabPS.Int.RNC)/
(VS.RAB.AttEstabPS.Conv.RNC+
VS.RAB.AttEstabPS.Bkg.RNC+
VS.RAB.AttEstabPS.Int.RNC+
VS.RAB.AttEstabPS.Str.RNC)] x 100%
Object CELL, RNC
Unit/Range %
Note None
1.2.16 PS RAB Setup Success Ratio (PCH)

Table 1-16 PS RAB Setup Success Ratio (PCH)
Name PS RAB Setup Success Ratio (PCH)
Formula PS RAB Setup Success Ratio (PCH) = Number of PS RAB Setup Successes/
Number of PS RAB Setup Attempts x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.15 PS RAB Setup Success
initiated by UEs in the CELL_PCH or URA_PCH state.
URA_PCH state, instead of the idle mode. In this way, the number of PS RAB
setup attempts and successful setups decreases dramatically, affecting the PS
RAB Setup Success Ratio.
CELL_FACH/CELL_DCH is the same as the PS RAB setup procedure.
Therefore, the statistics of connection setups for cell updates initiated by UEs
in the CELL_PCH or URA_PCH state are included in the formula for
calculating the PS RAB Setup Success Ratio (PCH).
Descriptions of PS RAB Setup Attempts and PS RAB Setup Successes:
l Number of PS RAB Setup Attempts (PCH)
– When the RNC receives from the PS CN a RAB ASSIGNMENT
REQUEST message, this counter is measured based on the requested
service type (including conversational, streaming, background, or
interactive services) carried in this message.
conditions:
message.
l Number of PS RAB Setup Successes (PCH)
message for setting up a PS service after receiving from a UE a RADIO
BEARER SETUP COMPLETE message, this counter is measured
based on the requested PS service type.
URA_PCH state. When the UE returns a PHYSICAL CHANNEL

1 RAN KPI Reference

cell update. The CELL UPDATE message must meet the following
conditions:
unknown".
For the classification of cell update causes, see section 10.3.3.3 in 3GPP
TS 25.331.
3GPP TS 25.331.
Associated l PS RAB Setup Success Ratio with PCH ( Cell)=

Counters {[(VS.RAB.SuccEstabPS.Conv+
VS.RAB.SuccEstabPS.Str+
VS.RAB.SuccEstabPS.Int+
VS.RAB.SuccEstabPS.Bkg)+
(VS.SuccCellUpdt.PageRsp +
(VS.SuccCellUpdt.Reg.PCH +
VS.SuccCellUpdt.Detach.PCH +
VS.SuccCellUpdt.other.PCH)] /
[(VS.RAB.AttEstabPS.Conv +
VS.RAB.AttEstabPS.Bkg +
VS.AttCellUpdt.ULDataTrans)-
(VS.AttCellUpdt.Reg.PCH+
VS.AttCellUpdt.Detach.PCH+
VS.AttCellUpdt.other.PCH)]} x 100%

1 RAN KPI Reference
Object CELL
Unit/Range %

1.2.17 HSDPA RAB Setup Success Ratio
Table 1-17 HSDPA RAB Setup Success Ratio
Name HSDPA RAB Setup Success Ratio
Formula HSDPA RAB Setup Success Ratio = (Number of HSDPA RAB Setup
Successes/Number of HSDPA RAB Setup Attempts) x 100%
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
RESPONSE message to the CN.
Associated HSDPA RAB Setup Success Ratio (Cell) =

Counters (VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%
Object CELL
Unit/Range %
1.2.18 HSDPA RAB Setup Success Ratio (CCH)
Table 1-18 HSDPA RAB Setup Success Ratio (CCH)
Name HSDPA RAB Setup Success Ratio (CCH)

1 RAN KPI Reference
Formula HSDPA RAB Setup Success Ratio (CCH) = Number of HSDPA RAB Setup
Successes/Number of HSDPA RAB Setup Attempts x 100%
Description Compared with the KPI formula for "1.2.17 HSDPA RAB Setup Success
Ratio", this formula includes the statistics of channel switches from
CELL_PCH/URA_PCH/CELL_FACH to HSDPA channels.
If the PCH or FACH state switch is turned on, UEs will remain in the always
online state. If UEs remain in the low traffic state for a certain period of time,
they will transit from the CELL_DCH state to the CELL_FACH state. If UEs
have no data to transmit, they will transit from the CELL_DCH or
CELL_FACH state to the CELL/URA_PCH state, instead of the idle mode.
In this way, the number of HSDPA RAB setup attempts and successful setups
decreases dramatically, affecting the HSDPA RAB Setup Success Ratio.
When UEs have a large amount of data to transmit, they will transit from the
CELL_FACH or CELL/URA_PCH state to the CELL_DCH state, and
establish services on HSDPA channels. This procedure is the same as the
HSDPA RAB setup procedure. Therefore, the number of channel switches
from the CELL/URA_PCH or CELL_FACH state to HSDPA is included in
the formula for calculating the HSDPA RAB Setup Success Ratio (CCH).
l Number of HSDPA RAB Setup Attempts (CCH)
– When the RNC receives from the CN a RAB ASSIGNMENT
REQUEST message for setting up an HSDPA service, this counter is
measured in the serving cell of the UE.
– When a UE has a large amount of data to transmit, the RNC transits
the UE from the CELL/URA_PCH or CELL_FACH state to the
CELL_DCH state. If the UE attempts to set up an HSDPA service, this
counter is measured in the serving cell of the UE.
l Number of HSDPA RAB Setup Successes (CCH)
COMPLETE message for setting up an HSDPA service, this counter
is measured in the serving cell of the UE.
– When the RNC receives from a UE a RADIO BEARER
RECONFIGURATION COMPLETE message for setting up an
HSDPA service after initiating a channel switch from CELL/
URA_PCH or CELL_FACH to HSDPA channels, this counter is
Associated HSDPA RAB Setup Success Ratio with CCH (Cell)=

Counters (VS.HSDPA.RAB.SuccEstab +
VS.SuccRecfg.F2H.DataTransTrig +
VS.SuccRecfg.P2H.DataTransTrig)/
(VS.HSDPA.RAB.AttEstab +
VS.AttRecfg.F2H.DataTransTrig +
VS.AttRecfg.P2H.DataTransTrig) x 100%
Object CELL

1 RAN KPI Reference
Unit/Range %
1.2.19 HSUPA RAB Setup Success Ratio
Table 1-19 HSUPA RAB Setup Success Ratio
Name HSUPA RAB Setup Success Ratio
Formula HSUPA RAB Setup Success Ratio =(Number of HSUPA RAB Setup
Successes/ Number of HSUPA RAB Setup Attempts) x 100%
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
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.
Associated HSUPA RAB Setup Success Ratio (Cell) =

Counters (VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%
Object CELL
Unit/Range %
1.2.20 HSUPA RAB Setup Success Ratio (CCH)

Table 1-20 HSUPA RAB Setup Success Ratio (CCH)
Name HSUPA RAB Setup Success Ratio (CCH)
Formula HSUPA RAB Setup Success Ratio (CCH) = Number of HSUPA RAB Setup
Successes/Number of HSUPA RAB Setup Attempts x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.19 HSUPA RAB Setup Success
Ratio", this formula includes the statistics of channel switches from
CELL_PCH/URA_PCH/CELL_FACH to HSUPA channels.
In this way, the number of HSUPA RAB setup attempts and successful setups
decreases dramatically, affecting the HSUPA RAB Setup Success Ratio.
CELL_FACH or CELL/URA_PCH state to HSUPA channels. This
procedure is the same as the HSUPA RAB setup procedure. Therefore, the
number of channel switches from the CELL/URA_PCH or CELL_FACH
state to HSDPA is included in the formula for calculating the HSUPA RAB
Setup Success Ratio (CCH).
l Number of HSUPA RAB Setup Attempts (CCH)
– When the RNC receives from the CN a RAB ASSIGNMENT
REQUEST message for setting up an HSUPA service, this counter is
the UE from the CELL/URA_PCH or CELL_FACH state to the
CELL_DCH state. If the UE attempts to set up an HSUPA service, this
counter is measured in the serving cell of the UE.
l Number of HSUPA RAB Setup Successes (CCH)
COMPLETE message for setting up an HSUPA service, this counter
is measured in the serving cell of the UE.
RECONFIGURATION COMPLETE message for setting up an
HSUPA service after initiating a channel switch from CELL_PCH/
URA_PCH/CELL_FACH to HSUPA channels, this counter is
Associated HSUPA RAB Setup Success Ratio with CCH (Cell)=

Counters (VS.HSUPA.RAB.SuccEstab +
VS.SuccRecfg.F2E.DataTransTrig +
VS.SuccRecfg.P2E.DataTransTrig)/
(VS.HSUPA.RAB.AttEstab +
VS.AttRecfg.F2E.DataTransTrig +
VS.AttRecfg.P2E.DataTransTrig) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
1.2.21 PS E-FACH RAB Setup Success Ratio

Table 1-21 PS E-FACH RAB Setup Success Ratio
Name PS E-FACH RAB Setup Success Ratio
Formula PS E-FACH RAB Setup Success Ratio = (Number of PSE-FACH RAB Setup
Successes/ Number of PSE-FACH RAB Setup Attempts) x 100%
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.
Associated PS E-FACH RAB Setup Success Ratio (Cell) =

Counters (VS.RAB.SuccEstPS.EFACH/VS.RAB.AttEstPS.EFACH) x 100%
Object CELL
Unit/Range %
1.2.22 CS over HSPA RAB Setup Success Ratio
Table 1-22 CS over HSPA RAB Setup Success Ratio
Name CS over HSPA RAB Setup Success Ratio
Formula CS over HSPA RAB Setup Success Ratio = (CS over HSPA RAB Setup
Successes/ CS over HSPA RAB Setup Attempts) x 100%

1 RAN KPI Reference
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.
Associated CS over HSPA RAB Setup Success Ratio (Cell) =

Counters (VS.HSPA.RAB.SuccEstab.CS.Conv/
VS.HSPA.RAB.AttEstab.CS.Conv) x 100%
Object CELL
Unit/Range %
1.2.23 HSDPA 64QAM RAB Setup Success Ratio

Table 1-23 HSDPA 64QAM RAB Setup Success Ratio
Name HSDPA 64QAM RAB Setup Success Ratio
Formula HSDPA 64QAM RAB Setup Success Ratio = (HSDPA 64QAM RAB Setup
Successes /HSDPA 64QAMRAB Setup Attempts) x 100%
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.
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.
Associated HSDPA 64QAM RAB Setup Success Ratio (Cell) =

Counters (VS.HSDPA.RAB.64QAM.SuccEstab/VS.HSDPA.RAB.
64QAM.AttEstab) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
1.2.24 HSDPA MIMO RAB Setup Success Ratio
Table 1-24 HSDPA MIMO RAB Setup Success Ratio
Name HSDPA MIMO RAB Setup Success Ratio
Formula HSDPA MIMO RAB Setup Success Ratio = (HSDPA MIMO RAB Setup
Successes/HSDPA MIMO RAB Setup Attempts) x 100%
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.
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.
Associated HSDPA MIMO RAB Setup Success Ratio=

Counters (VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEs-
tab) x 100%
Object CELL
Unit/Range %
1.2.25 HSDPA DC RAB Setup Success Ratio
Table 1-25 HSDPA DC RAB Setup Success Ratio
Name HSDPA DC RAB Setup Success Ratio
Formula HSDPA DC RAB Setup Success Ratio = (HSDPA DC RAB Setup Successes/
HSDPA DC RAB Setup Attempts) x 100%
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
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.

1 RAN KPI Reference
Associated HSDPA DC RAB Setup Success Ratio=

Counters (VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x
100%
Object CELL
Unit/Range %
1.2.26 HSDPA MIMO64QAM RAB Setup Success Ratio
Table 1-26 HSDPA MIMO64QAM RAB Setup Success Ratio
Name HSDPA MIMO64QAM RAB Setup Success Ratio
Formula HSDPA MIMO64QAM RAB Setup Success Ratio = (HSDPA

MIMO64QAM RAB Setup Successes/HSDPA MIMO64QAM RAB Setup
Attempts) x 100%
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.
Associated HSDPA MIMO64QAM RAB Setup Success Ratio=

Counters (VS.HSDPA.RAB.MIMO64QAM.SuccEstab/
VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%
Object CELL
Unit/Range %
1.2.27 PTM Channel Setup Success Ratio
Table 1-27 PTM Channel Setup Success Ratio
Name PTM Channel Setup Success Ratio

1 RAN KPI Reference
Formula PTM Channel Setup Success Ratio = (PTM Channel RB Setup Successes/
PTM Channel RB Setup Attempts) x 100%
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.
Associated PTM Channel Setup Success Ratio=

Counters (VS.MBMS.RB.PTM.SuccEstab/ VS.MBMS.RB.PTM.AttEstab) x
100%
Object CELL
Unit/Range %
1.2.28 PTP Channel Setup Success Ratio

Table 1-28 PTP Channel Setup Success Ratio
Name PTP Channel Setup Success Ratio
Formula PTP Channel Setup Success Ratio = (PTP Channel RB Setup Successes/PTP
Channel RB Setup Attempts) x 100%
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.
Associated PTP Channel Setup Success Ratio=

Counters (VS.MBMS.RB.PTP.SuccEstab/ VS.MBMS.RB.PTP.AttEstab) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
1.2.29 RRC Congestion Ratio
Table 1-29 RRC Congestion Ratio
Name RRC Congestion Ratio
Formula RRC Congestion Ratio = (Number of RRC Setup Fails due to Congestion /
Number of RRC Setup Attempts) x 100%
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.
Associated RRC Congestion Ratio=

Counters [(VS.RRC.Rej.ULPower.Cong+
VS.RRC.Rej.DLPower.Cong+
VS.RRC.Rej.ULIUBBand.Cong+
VS.RRC.Rej.DLIUBBand.Cong+
VS.RRC.Rej.ULCE.Cong+
VS.RRC.Rej.DLCE.Cong+
VS.RRC.Rej.Code.Cong)/
VS.RRC.AttConnEstab.Sum] x 100%
Object CELL
Unit/Range %
Note None
1.2.30 CS RAB Congestion Ratio
Table 1-30 CS RAB Congestion Ratio
Name CS RAB Congestion Ratio
Formula CS RAB Congestion Ratio = (Number of CS RAB Setup Fails due to

Congestion/ Number of CS RAB Setup Attempts) x 100%

1 RAN KPI Reference
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.
Associated CS RAB Congestion Ratio=

Counters [(VS.RAB.FailEstabCS.DLIUBBand.Cong+
VS.RAB.FailEstabCS.ULIUBBand.Cong+
VS.RAB.FailEstabCS.ULCE.Cong +
VS.RAB.FailEstabCS.DLCE.Cong +
VS.RAB.FailEstabCS.Code.Cong +
VS.RAB.FailEstabCS.ULPower.Cong+
VS.RAB.FailEstabCS.DLPower.Cong)/
(VS.RAB.AttEstabCS.Conv+
VS.RAB.AttEstabCS.Str)] x100%
Object CELL
Unit/Range %
Note None
1.2.31 PS RAB Congestion Ratio
Table 1-31 PS RAB Congestion Ratio
Name PS RAB Congestion Ratio
Formula PS RAB Congestion Ratio = (Number of PS RAB Setup Fails due to

Congestion/Number of PS RAB Setup Attempts) x 100%

1 RAN KPI Reference
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.
Associated PS RAB Congestion Ratio=

Counters [VS.RAB.FailEstabPS.DLIUBBand.Cong+
VS.RAB.FailEstabPS.ULIUBBand.Cong+
VS.RAB.FailEstabPS.ULCE.Cong+
VS.RAB.FailEstabPS.DLCE.Cong+
VS.RAB.FailEstabPS.Code.Cong+
VS.RAB.FailEstabPS.ULPower.Cong+
VS.RAB.FailEstabPS.DLPower.Cong+
VS.RAB.FailEstabPS.HSDPAUser.Cong+
VS.RAB.FailEstabPS.HSUPAUser.Cong/
VS.RAB.AttEstabPS.Str+
VS.RAB.AttEstabPS.Int+
VS.RAB.AttEstabPS.Bkg] x 100%
Object CELL
Unit/Range %
Note None
1.2.32 PS R99 RAB Setup Success Rate
Table 1-32 PS R99 RAB Setup Success Rate
Name PS R99 RAB Setup Success Rate
Formula PS R99 RAB Setup Success Rate = (Number of successfully set up PS R99
RABs/ Number of PS R99 RAB setup attempts) x 100%

1 RAN KPI Reference
Description This KPI provides the PS R99 RAB setup success rate.
The number of PS R99 RAB setup attempts is measured in the best cell where
the UE camps on when the RNC receives from the PS CN an RAB
ASSIGNMENT REQUEST message. After receiving this message, the RNC
attempts to set up an RAB for the service based on the network configuration.
The number of successfully set up PS R99 RABs is measured in the best cell
where the UE camps on when the RNC sends the CN an RAB ASSIGNMENT
RESPONSE message after receiving a RADIO BEARER SETUP
COMPLETE message from the UE if the RAB is for a PS R99 service.
Associated PS RAB Setup Success Ratio (Cell)=

Counters (VS.RAB.SuccEstab.PSR99/ VS.RAB.AttEstab.PSR99) * 100%
Object CELL
Unit/Range %
1.2.33 PS R99 RAB Setup Success Ratio (CCH)

Table 1-33 PS R99 RAB Setup Success Ratio (CCH)
Name PS R99 RAB Setup Success Ratio (CCH)
Formula PS R99 RAB Setup Success Ratio (CCH) = Number of PS R99 RAB Setup
Successes/Number of PS R99 RAB Setup Attempts x 100%

1 RAN KPI Reference
Description Compared with the KPI formula for "1.2.32 PS R99 RAB Setup Success
Rate", this formula includes the statistics of channel switches from
CELL_PCH/URA_PCH/CELL_FACH to R99 channels.
In this way, the number of PS R99 RAB setup attempts and successful setups
decreases dramatically, affecting the PS R99 RAB Setup Success Ratio.
CELL_FACH or CELL/URA_PCH state to PS R99 channels. This procedure
is the same as the PS R99 RAB setup procedure. Therefore, the number of
channel switches from the CELL/URA_PCH or CELL_FACH state to PS R99
is included in the formula for calculating the PS R99 RAB Setup Success
Ratio (CCH).
l Number of PS R99 RAB Setup Attempts (CCH)
– When the RNC receives from the PS CN a RAB ASSIGNMENT
REQUEST message, the RNC establishes the requested service on a
proper bearer channel based on the network configuration. In this case,
this counter is measured in the best cell that the UE camps on.
the UE from the CELL_PCH/URA_PCH/CELL_FACH state to the
CELL_DCH state. If the UE attempts to set up a PS R99 service, this
counter is measured in the best cell that the UE camps on.
l Number of PS R99 RAB Setup Successes (CCH)
message for setting up a PS R99 service after receiving from a UE a
RADIO BEARER SETUP COMPLETE message, this counter is
measured in the best cell that the UE camps on.
RECONFIGURATION COMPLETE message for setting up a PS R99
service after initiating a channel switch from CELL_PCH/URA_PCH/
CELL_FACH to PS R99 channels, this counter is measured in the
serving cell of the UE.
Associated PS RAB Setup Success Ratio with CCH (Cell)

Counters (VS.RAB.SuccEstab.PSR99 +
VS.SuccRecfg.F2D.DataTransTrig+
VS.SuccRecfg.P2D.DataTransTrig)/
(VS.RAB.AttEstab.PSR99 +
VS.AttRecfg.F2D.DataTransTrig +
VS.AttRecfg.P2D.DataTransTrig) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
1.2.34 WB AMR RAB Setup Success Rate
Table 1-34 WB AMR RAB Setup Success Rate
Name WB AMR RAB Setup Success Rate
Formula WB AMR RAB Setup Success Rate = (Number of successfully set up WB

AMR RABs/Number of WB AMR RAB setup attempts) x 100%
Description This KPI provides the WB AMR RAB setup success rate.
The number of WB AMR RAB setup attempts is measured in the best cell
where the UE camps on when the RNC receives from the CS CN an RAB
ASSIGNMENT REQUEST message for a WB AMR voice service.
The number of successfully set up WB AMR RABs is measured in the best
cell where the UE camps on when the RNC sends the CN an RAB
ASSIGNMENT RESPONSE message after receiving a RADIO BEARER
SETUP COMPLETE message from the UE if the RAB is for a WB AMR
voice service.
Associated AMR WB RAB Setup Success Ratio(Cell)=

Counters (VS.RAB.SuccEstabCS.AMRWB / VS.RAB.AttEstabCS.AMRWB)
*100%
Object CELL
Unit/Range %
1.2.35 Success Ratio of Cell Updates Initiated by CS Service of PCH

UEs
Table 1-35 Success Ratio of Cell Updates Initiated by CS Service of PCH UEs
Name Success Ratio of Cell Updates Initiated by CS Service of PCH UEs
Formula Success Ratio of Cell Updates Initiated by CS Service of PCH UEs =(Number
of Successful Cell Updates Initiated by CS Service of PCH UEs/ Number of
Cell Updates Attempts Initiated by CS Service of PCH UEs) x 100%

1 RAN KPI Reference
Description This KPI monitors the CS access success rate of UEs in the CELL_PCH or
URA_PCH state.
If the switch for state transition to the CELL_PCH or URA_PCH state is
turned on on the network, smartphones will be always online. If there is no
data transmission for a certain period, the UE will transition to the
CELL_PCH or URA_PCH state instead of the idle mode. In this way, the UE
initiates new services in the CELL_PCH or URA_PCH state.
When there are a large number of smartphones, this KPI can better reflect
user experience.
l The procedure for cell update attempts initiated by UEs in the CELL_PCH
or URA_PCH state is as follows: When receiving from the UE a CELL
UPDATE message with the cause value "uplink data transmission" or
"paging response", the RNC calculates the respective number of cell
update attempts based on the values of "establish cause" contained in the
CELL UPDATE message. This counter is not measured for a CELL
UPDATE message retransmitted by the UE.
l The procedure for successful cell updates initiated by UEs in the
CELL_PCH or URA_PCH state is as follows: When receiving from the
UE a CELL UPDATE message with the cause value "uplink data
transmission" or "paging response", the RNC determines that the cell
update procedure is successful if it receives a response from the UE after
sending the CELL UPDATE CONFIRM message to the UE. Then the
RNC calculates the respective number of successful cell updates based on
the values of "establish cause" contained in the CELL UPDATE message.
For details about the cause values of the CELL UPDATE message, see
section 10.3.3.11 in 3GPP TS 25.331.
Associated Success Ratio of Cell Updates Initiated by CS Service of PCH UEs =

Counters (VS.SuccCellUpdt.OrgConvCall.PCH +
VS.SuccCellUpdt.TmConvCall.PCH +
VS.SuccCellUpdt.EmgCall.PCH) /
(VS.AttCellUpdt.OrgConvCall.PCH +
VS.AttCellUpdt.TmConvCall.PCH + VS.AttCellUpdt.EmgCall.PCH ) x
100%
Object CELL
Unit/Range %
1.2.36 Success Ratio of Cell Updates Initiated by New PS Service of

PCH UEs
Table 1-36 Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs
Name Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs

1 RAN KPI Reference
Formula Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs =
(Number of Successful Cell Updates Initiated by New PS Service of PCH
UEs/ Number of Cell Updates Attempts Initiated by New PS Service of PCH
UEs) x 100%
Description This KPI monitors the PS access success rate of UEs in the CELL_PCH or
URA_CELL state.
If the switch for state transition to CELL_PCH or URA_PCH is turned on on
the network, smartphones will be always online. If there is no data
transmission for a certain period, the UE will transition to the CELL_PCH or
URA_PCH state instead of the idle mode. In this way, the UE initiates new
services in the CELL_PCH or URA_PCH state.
user experience.
l The procedure for cell update attempts initiated by UEs in the CEll_PCH
or URA_PCH state is as follows: When receiving from the UE a CELL
UPDATE message with the cause value "uplink data transmission" or
"paging response", the RNC calculates the respective number of cell
update attempts based on the values of "establish cause." This counter is
not measured for a CELL UPDATE message retransmitted by the UE.
l The procedure for successful cell updates initiated by UEs in the
CEll_PCH or URA_PCH state is as follows: When receiving from the UE
a CELL UPDATE message with the cause value "uplink data
transmission" or "paging response", the RNC determines that the cell
update procedure is successful if it receives a response from the UE after
sending the CELL UPDATE CONFIRM message to the UE. Then the
RNC calculates the respective number of successful cell updates based on
the values of "establish cause" contained in the CELL UPDATE message.
For details about the cause values of the CELL UPDATE message, see
section 10.3.3.11 in 3GPPTS 25.331.
Associated Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs =
Counters (VS.SuccCellUpdt.OrgInterCall.PCH +
VS.SuccCellUpdt.OrgBkgCall.PCH +
VS.SuccCellUpdt.TmInterCall.PCH +
VS.SuccCellUpdt.TmBkgCall.PCH) /
(VS.AttCellUpdt.OrgInterCall.PCH +
VS.AttCellUpdt.OrgBkgCall.PCH +
VS.AttCellUpdt.TmInterCall.PCH +
VS.AttCellUpdt.TmBkgCall.PCH ) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
1.2.37 CS RAB Setup Success Ratio of PCH UEs
Table 1-37 CS RAB Setup Success Ratio of PCH UEs
Name CS RAB Setup Success Ratio of PCH UEs
Formula CS RAB Setup Success Ratio of PCH UEs = (Number of Successful CS RAB
Setups of PCH UEs / Number of CS RAB Setup Attempts of PCH UEs)x
100%
Description This KPI monitors the success rate of CS RAB setups initiated by UEs in the
CELL_PCH or URA_PCH state.
If the switch for state transition to the CELL_PCH or URA_PCH state is
turned on on the network, smartphones will be always online. If there is no
data transmission for a certain period, the UE will transition to the
CELL_PCH or URA_PCH state instead of the idle mode. In this way, the UE
initiates new services in the CELL_PCH or URA_PCH state.
user experience.
l The procedure for CS RAB setup attempts initiated by UEs in the
CELL_PCH or URA_PCH state is as follows: A UE in the CELL_PCH
or URA_PCH state initiates CS services and transitions to another state.
After the RNC receives an RAB ASSIGNMENT REQUEST message
from the CS domain of the CN, the RNC calculates the number of CS
RAB setup attempts in the best cell of the UE based on the UE state.
l The procedure for successful CS RAB setups initiated by UEs in the
or URA_PCH state initiates CS services and transitions to another state.
from the CS domain of the CN and responds with an RAB ASSIGNMENT
RESPONSE message, the RNC calculates the number of successful CS
RAB setups in the best cell of the UE based on the UE state.
Associated CS RAB Setup Success Ratio of PCH UEs =

Counters ( VS.SuccEstabCS.AfterP2F + VS.SuccEstabCS.AfterP2D ) /
( VS.AttEstabCS.AfterP2F+ VS.AttEstabCS.AfterP2D ) x 100%
Object CELL
Unit/Range %
1.2.38 New PS RAB Setup Success Ratio of PCH UEs
Table 1-38 New PS RAB Setup Success Ratio of PCH UEs
Name New PS RAB Setup Success Ratio of PCH UEs

1 RAN KPI Reference
Formula New PS RAB Setup Success Ratio of PCH UEs = (Number of Successful
New PS RAB Setups of PCH UEs/ Number of New PS RAB Setup Attempts
of PCH UEs) x 100%
Description This KPI monitors the success rate of the PS RAB setups initiated by UEs in
the CELL_PCH and URA_PCH states.
If the switch for state transition to CELL_PCH or URA_PCH is turned on on
the network, smartphones will be always online. If there is no data
transmission for a certain period, the UE will transition to the CELL_PCH or
URA_PCH state instead of the idle mode. In this way, the UE initiates new
services in the CELL_PCH or CELL_PCH state.
user experience.
l The procedure for the PS RAB setup attempt initiated by UEs in the
or URA_PCH state initiates PS services and transitions to another state.
from the PS domain of the CN, the RNC calculates the number of PS RAB
setup attempts in the best cell of the UE based on the UE state.
l The procedure for the successful PS RAB setup initiated by UEs in the
or URA_PCH state initiates PS services and transitions to another state.
from the PS domain of the CN and responds with an RAB ASSIGNMENT
RESPONSE message, the RNC calculates the number of successful PS
RAB setups in the best cell of the UE based on the UE state.
Associated New PS RAB Setup Success Ratio of PCH UEs =

Counters ( VS.SuccEstabPS.AfterP2F + VS.SuccEstabPS.AfterP2D ) /
( VS.AttEstabPS.AfterP2F+ VS.AttEstabPS.AfterP2D ) x 100%
Object CELL
Unit/Range %
1.3 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
1.3.1 Worst Cell Ratio

1 RAN KPI Reference
Table 1-39 Worst Cell Ratio
Name Worst Cell Ratio
Formula Worst Cell Ratio = {[The number of Cells in which(AMR RAB Setup Success
Ratio(Cell)<95% and VP RAB Setup SuccessRatio(Cell)=<95% ) or (AMR
Call Drop Ratio >3% and VP Call Drop Ratio >3%)]/Total Number of Cells
in RNC} x 100%
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%.
Associated Worst Cell Ratio =

Counters {[The Number Of Cells, In which (AMR RAB Setup Success Ratio (Cell)
< 95% and VP RAB Setup Success Ratio (Cell) =< 95%) or (AMR Call
Drop Ratio > 3% and VP Call Drop Ratio > 3%)]/The Total Number Of
Cells In RNC} x 100%
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.
1.3.2 Paging Congestion Ratio
Table 1-40 Paging Congestion Ratio
Name Paging Congestion Ratio
Formula Iu Paging Congestion Ratio(RNC) =(Failure To Respond To PAGING

Message From CN/PAGING Message From CN) x 100%
Iu Paging Congestion Ratio(Cell) =(Failure To Respond To PAGING
Message From CN/ PAGING Message From CN) x 100%

1 RAN KPI Reference
Description Paging Congestion Ratio (RNC):

This KPI is used to check the consumption of PCCH bandwidth during busy
hours.
l Description of the numerator:
The Failures to Respond to PAGING Message From CN counted if the
RNC does not send a PAGING type 1 or PAGING type 2 message. The
reason is that the RNC does not send a PAGING message due to
congestion causes such as Iu flow control or high CPU usage.
l Description of the denominator:
The Number of PAGING Message from CN is counted when RNC
receives a PAGING message from the CN included CS and PS PAGING.
Paging Congestion Ratio (Cell):
This KPI is used to check the consumption of PCCH bandwidth during the
busy hour.
This counter provides the number of losses of PAGING TYPE 1 message
due to PCH congestion in a cell.
This counter provides the number of paging messages of PAGING TYPE
1 sent by the RNC in a cell.
Associated l IU Paging Congestion Ratio (RNC)=

Counters [(VS.RANAP.CsPaging.Loss+ VS.RANAP.PsPaging.Loss)/
(VS.RANAP.CsPaging.Att+ VS.RANAP.PsPaging.Att)] x 100%
l IU Paging Congestion Ratio (Cell) =
(VS.RRC.Paging1.Loss.PCHCong.Cell/VS.UTRAN.AttPaging1) x
100%
Object RNC, CELL
Unit/Range %
Note None
1.3.3 Call Admission Refused Ratio
Table 1-41 Call Admission Refused Ratio
Name Call Admission Refused Ratio
Formula Call Admission Refused Ratio =(Failed Number of Cell Resource Requests
for New Call Setup/ Number of Cell Resource Requests for New Call Setup)
x 100%

1 RAN KPI Reference
Description This KPI is used to check the admission refused ratio of new calls during busy
hours in an RNC or a cluster.
The failed number of Cell Resource Requests for New Call setup is
counted after RNC requesting cell resources for the UE successfully.
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.
Associated Call admission Refused Ratio=

Counters [1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq] x 100%
Object CELL
Unit/Range %
1.3.4 Congested Cell Ratio
Table 1-42 Congested Cell Ratio
Name Congested Cell Ratio
Formula Congest Cell Ratio =(Congested Cell On Busy Hour/Total number of Cells
in RNC) x 100%
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.
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.
Associated Congested Cell Ratio =

Counters (The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 or
VS.LCC.OLC.DL.Num>0 On Busy Hour/The Total Number Of Cells In
RNC) x 100%
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.

1 RAN KPI Reference
1.3.5 Radio Network Unavailability Ratio
Table 1-43 Radio Network Unavailability Ratio
Name Radio Network Unavailability Ratio
Formula Radio Network Unavailability Ratio = (Cell Unavailable duration/ Total

Number of Cells in RNC) x 100%
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.
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.
Associated Radio Network Unavailability Ratio=

Counters (VS.Cell.UnavailTime.Sys)/(The Total Number Of Cells in RNC x {SP} x
60) x 100%
Object CELL
Unit/Range %
Note The unit of {SP}(Statistic Period): Minute
1.3.6 Average CPU Load
Table 1-44 Average CPU Load
Name Average CPU Load
Formula For BSC6900: Average CPU Load = CPU usage of the XPU subsystem in
the measurement period
For BSC6910: Average CPU Load = CPU usage of the subsystem in the
measurement period
Description This KPI provides the mean CPU usage of a subsystem in the measurement
period. It indicates the load and operating performance of the CPU on the
subsystem in the measurement period.
The CPU usage of the subsystem is sampled every second in the measurement
period. Then, average CPU usage of the subsystem is the accumulated value
divided by the number of sampling times.
Associated For BSC6900: Average CPU Load= VS.XPU.CPULOAD.MEAN

Counters For BSC6910: Average CPU Load= VS.SUBSYS.CPULOAD.MEAN

1 RAN KPI Reference
Object For BSC6900: XPU

For BSC6910: SUBSYS
Unit/Range %
Note Mean CPU Utility is the CPU average load showed in percentage.
1.3.7 Iub Port Available Bandwidth Utilizing Ratio (UL)

Table 1-45 Iub Port Available Bandwidth Utilizing Ratio (UL)
Name Iub Port Available Bandwidth Utilizing Ratio (UL)
Formula Iub Port Available Bandwidth Utilizing Ratio (Uplink) = (Iub Real—Time
Uplink Traffic/ Iub Available Uplink Bandwidth) x 100%
Description This KPI is used to check consumption of NodeB Iub port available
bandwidth utilizing ratio. The Bandwidth could be measured on ATM
Physical Ports or IP physical Ports.

1 RAN KPI Reference
Associated l Iub Port Available Bandwidth Utilizing Ratio (ATM_UL) =

Counters [(VS.ATMUlAvgUsed.1+
VS.ATMUlAvgUsed.2+
VS.ATMUlAvgUsed.3+
VS.ATMUlAvgUsed.4)/
(VS.ATMUlTotal.1+
VS.ATMUlTotal.2+
VS.ATMUlTotal.3+
VS.ATMUlTotal.4)] x 100%
l Iub Port Available Bandwidth Utilizing Ratio (IP_UL)1=
[(VS.IPUlAvgUsed.1+
VS.IPUlAvgUsed.2+
VS.IPUlAvgUsed.3+
VS.IPUlAvgUsed.4)/
(VS.IPUlTotal.1+
VS.IPUlTotal.2+
VS.IPUlTotal.3+
VS.IPUlTotal.4)] x 100%
l Iub Port Available Bandwidth Utilizing Ratio (IP_UL)2 =
[(∑VS.FEGE.TxMeanSpeed+
∑VS.PPP.TxMeanSpeed)/
(∑VS.FEGE.TxTotalBW+
∑VS.PPP.TxTotalBW)x 100%
Object NodeB
Unit/Range %

1 RAN KPI Reference
Note
l The counters in the formula are measured on the NodeB side.The counters
in Iub Port Available Bandwidth Utilizing Ratio (IP_UL) 1 are not used
by co-MPT base stations.
l In Iub over IP mode, the NodeB-level counters VS.IPUlTotal.1,
VS.IPUlTotal.2, VS.IPUlTotal.3, and VS.IPUlTotal.4 provide the
available physical bandwidths of ports rather than the actual available
bandwidths of ports. Therefore, this KPI can not be used to check the Iub
actual bandwidth utilizing ratio.
l The counters in Iub Port Available Bandwidth Utilizing Ratio (IP_UL) 1
will be removed in later versions. It is recommended that Iub Port
Available Bandwidth Utilizing Ratio (IP_UL) 2 be used to calculate the
available bandwidth utilization ratio of separate-MPT multimode base
stations (non-co-transmission scenario), co-MPT base stations (UO), and
UMTS single-mode base stations.
l In the case of rate limitation on Ethernet ports, VS.FEGE.TxTotalBW in
Iub Port Available Bandwidth Utilizing Ratio (IP_UL) 2 measures the
Ethernet port bandwidth after rate limitation. In other rate limitation cases
(for example, rate limitation on the trunk group of FE/GE ports),
VS.FEGE.TxTotalBW in Iub Port Available Bandwidth Utilizing Ratio
(IP_UL) 2 measures the Ethernet port bandwidth. In the latter case, the
calculation result of Iub Port Available Bandwidth Utilizing Ratio
(IP_UL) 2 is smaller than the actual one.
1.3.8 Iub Port Available Bandwidth Utilizing Ratio (DL)

Table 1-46 Iub Port Available Bandwidth Utilizing Ratio (DL)
Name Iub Port Available Bandwidth Utilizing Ratio (DL)
Formula Iub Port Available Bandwidth Utilizing Ratio (Downlink) = (Iub Real—Time
Downlink Traffic /Iub Available Downlink Bandwidth) x 100%
Description This KPI is used to check consumption of NodeB Iub port available
bandwidth utilizing ratio. The Bandwidth could be measured on ATM
Physical Ports or IP physical Ports.

1 RAN KPI Reference
Associated l Iub Port Available Bandwidth Utilizing Ratio (ATM_DL) =

Counters [(VS.ATMDIAvgUsed.1+
VS.ATMDLAvgUsed.2+
VS.ATMDLAvgUsed.3+
VS.ATMDLAvgUsed.4)/
(VS.ATMDLTotal.1+
VS.ATMDLTotal.2+
VS.ATMDLTotal.3+
VS.ATMDLTotal.4)] x 100%
l Iub Port Available Bandwidth Utilizing Ratio (IP_DL)1 =
[(VS.IPDLAvgUsed.1+
VS.IPDLAvgUsed.2+
VS.IPDLAvgUsed.3+
VS.IPDLAvgUsed.4)/
(VS.IPDLTotal.1+
VS.IPDLTotal.2+
VS.IPDLTotal.3+
VS.IPDLTotal.4)] x 100%
l Iub Port Available Bandwidth Utilizing Ratio (IP_DL)2=
[(∑VS.FEGE.RxMeanSpeed+
∑VS.PPP.RxMeanSpeed)/
∑VS.FEGE.RxTotalBW+
(∑VS.PPP.RxTotalBW)] x 100%
Object NodeB
Unit/Range %

1 RAN KPI Reference
Note
l The counters in the formula are measured on the NodeB side.The counters
in Iub Port Available Bandwidth Utilizing Ratio (IP_DL) 1 are not used
by co-MPT base stations.
l In Iub over IP mode, the NodeB-level counters VS.IPDLTotal.1,
VS.IPDLTotal.2, VS.IPDLTotal.3, and VS.IPDLTotal.4 provide the
available physical bandwidths of ports rather than the actual available
bandwidths of ports. Therefore, this KPI can not be used to check the Iub
actual bandwidth utilizing ratio.
l The counters in Iub Port Available Bandwidth Utilizing Ratio (IP_DL) 1
will be removed in later versions. It is recommended that Iub Port
Available Bandwidth Utilizing Ratio (IP_DL) 2 be used to calculate the
available bandwidth utilization ratio of separate-MPT multimode base
stations (non-co-transmission scenario), co-MPT base stations (UO), and
UMTS single-mode base stations.
l In the case of rate limitation on Ethernet ports, VS.FEGE.RxTotalBW in
Iub Port Available Bandwidth Utilizing Ratio (IP_DL) 2 measures the
Ethernet port bandwidth after rate limitation. In other rate limitation cases
(for example, rate limitation on the trunk group of FE/GE ports),
VS.FEGE.RxTotalBW in Iub Port Available Bandwidth Utilizing Ratio
(IP_DL) 2 measures the Ethernet port bandwidth. In the latter case, the
calculation result of Iub Port Available Bandwidth Utilizing Ratio
(IP_DL) 2 is smaller than the actual one.
1.3.9 Cell Unavailability duration
Table 1-47 Cell Unavailability duration
Name Cell Unavailability duration
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
1.3.10 HSDPA Unavailability duration

1 RAN KPI Reference
Table 1-48 HSDPA Unavailability duration
Name HSDPA Unavailability duration
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
1.3.11 HSUPA Unavailability duration
Table 1-49 HSUPA Unavailability duration
Name HSUPA Unavailability duration
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
1.3.12 CE Consumption for a NodeB Cell
Table 1-50 CE Consumption for a NodeB Cell
Name CE Consumption for a NodeB Cell
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.

1 RAN KPI Reference
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
Object NodeB CELL
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.
1.3.13 Hardware Configured CE for a NodeB
Table 1-51 Hardware Configured CE for a NodeB
Name Hardware Configured CE for a NodeB
Description Number of UL/DL CEs configured for a NodeB.
Associated VS.HW.ULCreditAvailable
Counters VS.HW.DLCreditAvailable
Object NodeB
Unit/Range Numbers
Note None
1.3.14 Shared Group Configured License CE for a NodeB
Table 1-52 Shared Group Configured License CE for a NodeB
Name Shared Group Configured License CE for a NodeB
Description The Configured DL/UL CEs for the Shared Group.
Associated VS.LC.ULCreditAvailable.Shared
Counters VS.LC.DLCreditAvailable.Shared

1 RAN KPI Reference
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.
1.3.15 Shared Group License CE Consumption for a NodeB
Table 1-53 Shared Group License CE Consumption for a NodeB
Name Shared Group License CE Consumption for a NodeB
Description The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by an operator, or by HSUPA service.
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.
1.3.16 License Group Configured CE for a NodeB
Table 1-54 License Group Configured CE for a NodeB
Name License Group Configured CE for a NodeB
Description The Number of DL CEs configured for a license Group.

1 RAN KPI Reference
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.
1.3.17 License Group CE Consumption for a NodeB
Table 1-55 License Group CE Consumption for a NodeB
Name License Group CE Consumption for a NodeB
Description The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by a licensed group, or by HSUPA services.
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.
1.3.18 RTWP (Received Total Wideband Power)
Table 1-56 RTWP (Received Total Wideband Power)
Name RTWP (Received Total Wideband Power)

1 RAN KPI Reference
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
1.3.19 TCP (Transmitted Carrier Power)
Table 1-57 TCP (Transmitted Carrier Power)
Name TCP (Transmitted Carrier Power)
Description l The first 3 counters provide the Maximum/Minimum/Mean Transmitted

Power of Carrier for a cell.
l The second 3 counters provide the Maximum/Minimum/Mean Non-
HSDPA Transmitted Carrier Power for a Cell.
l The third 3 counters provide Maximum/Minimum/Mean Power Required
by HS-DSCH for a Cell.
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

1 RAN KPI Reference
Note None
1.3.20 R99 Code Utilization
Table 1-58 R99 Code Utilization
Name R99 Code Utilization
Formula R99 Code Utilization =

[(VS.SingleRAB.SF4+VS.MultRAB.SF4) x 64+
(VS.SingleRAB.SF8+VS.MultRAB.SF8) x 32+
(VS.SingleRAB.SF128+VS.MultRAB.SF128) x 2 +
(VS.SingleRAB.SF256+VS.MultRAB.SF256)]/256 x 100%
Description The occupied codes are the codes occupied by 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.
Associated None
Counters
Object CELL
Unit/Range %
Note The occupied codes are normalized to SF = 256.

Total Code utilization for a cell can be calculated approximately by using the
following formula:
VS.RAB.SFOccupy /256
The value would be greater than the real usage as the code for HSDPA was
reserved initially.
1.3.21 Number of Codes Used by HS-PDSCHs
Table 1-59 Number of Codes Used by HS-PDSCHs
Name Number of Codes Used by HS-PDSCHs

1 RAN KPI Reference
Formula HSDPA Efficiency = Duration when there is HSDPA data transmission/

Duration when there is HSDPA data in the buffer
Description The counters VS.PdschCodeUsed.Mean, VS.PdschCodeUsed.Max, and

VS.PdschCodeUsed.Min provide the mean, maximum, and minimum
number of codes used by HS-PDSCHs in a cell during a measurement period
respectively.
Associated VS.PdschCodeUsed.Mean
Counters VS.PdschCodeUsed.Max
VS.PdschCodeUsed.Min
Object NodeB
Unit/Range None
Note None
1.3.22 HSDPA Efficiency
Table 1-60 HSDPA Efficiency
Name HSDPA Efficiency
Formula HSDPA Efficiency = Duration when there is HSDPA data transmission/

Duration when there is HSDPA data in the buffer
Description This KPI provides the proportion of the duration when there is HSDPA data
transmission to the duration when there is HSDPA data in the buffer.
Associated HSDPA efficiency =

Counters (VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)/
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean +
VS.HSDPA.ScheInactiveDataTtiRatio.Mean)
Object NodeB
Unit/Range %
Note (VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)

indicates the proportion of TTIs with data transmission.
VS.HSDPA.ScheInactiveDataTtiRatio.Mean indicates the proportion of
TTIs when there is no data transmission but the scheduling candidate set
contains data from the buffer.

1 RAN KPI Reference
1.4 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an
RNC or a cluster.
1.4.1 UL Interference Cell Ratio
Table 1-61 UL Interference Cell Ratio
Name UL Interference Cell Ratio
Formula UL Interference Cell Ratio =[(Number of Cells in which Mean

RTWP>-98dBm)/Total Number of Cells] x 100%
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.
Associated UL Interference Cell Ratio =

Counters [(The Number Of Cells In which VS.MeanRTWP >-98dBm)/The Total
Number Of Cells In RNC] x 100%
Object RNC
Unit/Range %
Note -98 dBm is the value obtained based on the references from the commercial
network.
1.4.2 Soft Handover Overhead

Table 1-62 Soft Handover Overhead
KPI Name Soft Handover Overhead (RNC)

1 RAN KPI Reference
Formula Soft Handover Ratio(RNC) =[(A1+B1 x 2+C1 x 3+D1 x 4+E1 x 5+F1 x 6)/
(A1+B1+C1+D1+E1+F1)] x 100%
A1: Number of UEs with 1 RL in the RNC
B1: Number of UEs with 2 RLs in the RNC
C1: Number of UEs with 3 RLs in the RNC
D1: Number of UEs with 4 RLs in the RNC
E1: Number of UEs with 5 RLs in the RNC
F1: Number of UEs with 6 RLs in the RNC.
Soft Handover Ratio(Cell) ={[(A1+B1+C1+D1+E1+F1)/(A1+B1/2+C1/3

+D1/4+E1/5+F1/6)]–1} x 100%
A1: Number of UEs with 1 RL
B1: Number of UEs with 2 RLs
C1: Number of UEs with 3 RLs
D1: Number of UEs with 4 RLs
E1: Number of UEs with 5 RLs
F1: Number of UEs with 6 RLs.
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.

1 RAN KPI Reference
Associated l Soft Handover Overhead (RNC)=

Counters {[VS.SHO.AS.1.RNC +
(VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.2Soft.RNC)x 2 +
(VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Soft.RNC +
VS.SHO.AS.3Softer.RNC )x 3 +
VS.SHO.AS.4.RNC x 4 +
VS.SHO.AS.5.RNCx 5 +
VS.SHO.AS.6.RNCx 6 ]/
(VS.SHO.AS.1.RNC +
VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Softer.RNC +
VS.SHO.AS.4.RNC +
VS.SHO.AS.5.RNC +
VS.SHO.AS.6.RNC)-1}x 100%
l Soft Handover Overhead (Cell)=
[(VS.SHO.AS.1RL +
VS.SHO.AS.2RL +
VS.SHO.AS.3RL +
VS.SHO.AS.4RL +
VS.SHO.AS.5RL +
VS.SHO.AS.6RL )/
(VS.SHO.AS.1RL +
VS.SHO.AS.2RL /2 +
VS.SHO.AS.3RL /3 +
VS.SHO.AS.4RL /4 +
VS.SHO.AS.5RL /5 +
VS.SHO.AS.6RL /6)-1]x 100%
Object RNC, CELL
Unit/Range %
Note None

1 RAN KPI Reference
1.5 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or
service mode changing in difference scenarios.
1.5.1 Soft Handover Success Ratio
Table 1-63 Soft Handover Success Ratio
Name Soft Handover Success Ratio
Formula Soft Handover Success Ratio =(Number of Successful soft handovers/

Number of Attempts of soft handovers) x 100%
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.
Associated Soft Handover Success Ratio (RNC) =

Counters (VS.SHO.Succ.RNC/VS.SHO.Att.RNC) x 100%
Soft Handover Success Ratio (Cell) =
[(VS.SHO.SuccRLAdd+ VS.SHO.SuccRLDel)/(VS.SHO.AttRLAdd
+VS.SHO.AttRLDel)] x 100%
Object RNC, CELL
Unit/Range %
Note None
1.5.2 Softer Handover Success Ratio

Table 1-64 Softer Handover Success Ratio
Name Softer Handover Success Ratio
Formula Softer Handover Success Ratio = (Number of Successful softer handovers/

Number of Attempts of softer handovers) x 100%

1 RAN KPI Reference
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
Associated Softer Handover Success Ratio (RNC) =

Counters (VS.SoHO.Succ.RNC/VS.SoHO.Att.RNC) x 100%
Softer Handover Success Ratio (Cell) =
[(VS.SoHO.SuccRLAdd+VS.SoHO.SuccRLDel)/ (VS.SoHO.AttRLAdd
+VS.SoHO.AttRLDel)] x 100%
Object RNC, CELL
Unit/Range %
Note None
1.5.3 AMR Soft Handover Success Ratio
Table 1-65 AMR Soft Handover Success Ratio
Name AMR Soft Handover Success Ratio
Formula AMR Soft Handover Success Ratio = (Number of AMR Successful Soft
Handovers/ Number of AMR Attempts of Soft Handovers) x 100%
Description This KPI is used to check the AMR Soft Handover Success ratio in a Cluster,
including softer handover.
The Successful AMR Soft Handover procedure is complete when the RNC
during the soft handover procedure.
The attempt procedure is complete when the RNC sends an ACTIVE SET
Associated AMR Soft Handover Success Ratio =

Counters [(VS.SHO.AMR.Succ)/(VS.SHO.AMR.Att)] x 100%
Object CELL
Unit/Range %
Note The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.

1 RAN KPI Reference
1.5.4 CS64 Soft Handover Success Ratio
Table 1-66 CS64 Soft handover Success Ratio
Name CS64 Soft handover Success Ratio
Formula CS64 Soft Handover Success Ratio(Cell) =(Number of CS 64 Successful soft

handovers in a Cell/Number of CS64 Attempts of soft handovers in a Cell) x
100%
Description This KPI is used to check the CS64 Soft Handover Success ratio in a Cluster,
The Successful CS64 Soft Handover procedure is complete when the RNC
Associated CS64 Soft Handover Success Ratio =

Counters [(VS.SHO.CS64.Succ)/(VS.SHO.CS64.Att)] x 100%
Object CELL
Unit/Range %
1.5.5 PS Soft Handover Success Ratio
Table 1-67 PS soft handover Success Ratio
Name PS soft handover Success Ratio
Formula PS soft handover Success Ratio = (Number of PS services Successful soft

handovers/Number of PS services Attempts of soft handovers) x 100%
Description This KPI is used to check the PS Soft Handover Success ratio in a Cluster,
The Successful PS Soft Handover procedure is complete when the RNC
Associated PS services Soft Handover Success Ratio =

Counters [(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)] x 100%

1 RAN KPI Reference
Object CELL
Unit/Range %
1.5.6 Intra-frequency Hard Handover Success Ratio
Table 1-68 Intra-frequency Hard Handover Success Ratio
Name Intra-frequency Hard Handover Success Ratio
Formula Intra-frequency Hard Handover Success Ratio = (IntraFreq HHO Success/

IntraFreq HHO Attempt) x 100%
Description This KPI is used to check the intra-frequency hard handover success ratio in
an RNC or a Cluster.
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.
Associated l Intra-frequency Hard Handover Success Ratio (Cell) =

Counters [(VS.HHO.SuccIntraFreqOut.IntraNodeB+
VS.HHO.SuccIntraFreqOut.InterNodeBIntraRNC+
VS.HHO.SuccIntraFreqOut.InterRNC)/
(VS.HHO.AttIntraFreqOut.InterNodeBIntraRNC+
VS.HHO.AttIntraFreqOut.InterRNC+
VS.HHO.AttIntraFreqOut.IntraNodeB)] x 100%
l Intra-frequency Hard Handover Success Ratio (RNC) =
[(VS.HHO.SuccIntraFreq.RNC)/(VS.HHO.AttIntraFreq.RNC)] x
100%
Object RNC, CELL
Unit/Range %
Note None
1.5.7 Inter-frequency Hard Handover Success Ratio

1 RAN KPI Reference
Table 1-69 Inter-frequency Hard Handover Success Ratio
Name Inter-frequency Hard Handover Success Ratio
Formula Inter-frequency Hard Handover Success Ratio =(Inter-frequency Hard

Handover Success/Inter-frequency Hard Handover Success Attempt) x 100%
Description This KPI is used to check the inter-frequency hard handover success ratio in
an RNC or a Cluster.
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.
Associated Inter-frequency Hard Handover Success Ratio (RNC) =

Counters (VS.HHO.SuccInterFreq.RNC/VS.HHO.AttInterFreq.RNC) x 100%
Inter-frequency Hard Handover Success Ratio (Cell) =
(VS.HHO.SuccInterFreqOut/VS.HHO.AttInterFreqOut) x 100%
Object RNC, CELL
Unit/Range %
Note None
1.5.8 Service Cell Change Success Ratio with SHO (H2H)
Table 1-70 Service Cell Change Success Ratio with SHO (H2H)
Name Service Cell Change Success Ratio with SHO (H2H)
Formula Service Cell Change Success Ratio with SHO (H2H) = (HS-DSCH service
cell change Success with SHO/HS-DSCH service cell change Attempt with
SHO) x 100%

1 RAN KPI Reference
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
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
ACTIVE SET UPDATE COMPLETE
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.
Associated Service Cell Change Success Ratio with SHO (H2H) =

Counters (VS.HSDPA.SHO.ServCellChg.SuccOut/
VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
Object CELL
Unit/Range %
Note None
1.5.9 H2H Intra-Frequency Hard Handover Success Ratio
Table 1-71 H2H Intra-Frequency Hard Handover Success Ratio
Name H2H Intra-Frequency Hard Handover Success Ratio
Formula H2H Intra-Frequency Hard Handover Success Ratio =(H2H Intra - frequency
Hard Handover Success/H2H Intra - frequency Hard Handover Attempt) x
100%

1 RAN KPI Reference
Description This KPI is used to check the intra-frequency hard handover success ratio of
HSDPA service in a Cluster.
l The HS-DSCH service cell change success with SHO is triggered with
the following message:
RADIO BEARER SETUP
RADIO BEARER RELEASE
response.
RADIO BEARER SETUP COMPLETE
RADIO BEARER RELEASE COMPLETE
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.
Associated H2H Intra-Frequency Hard Handover Success Ratio =

Counters (VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.At-
tOutIntraFreq) x 100%
Object CELL
Unit/Range %
1.5.10 H2H Inter-Frequency Hard Handover Success Ratio

Table 1-72 H2H Inter-Frequency Hard Handover Success Ratio
Name H2H Inter-Frequency Hard Handover Success Ratio
Formula H2H Inter-Frequency Hard Handover Success Ratio =(H2H Inter - frequency
Hard Handover Success/H2H Inter - frequency Hard Handover Attempt) x
100%

1 RAN KPI Reference
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:
RADIO BEARER SETUP
response.
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.
Associated H2H Inter-Frequency Hard Handover Success Ratio=

Counters (VS.HSDPA.HHO.H2H.SuccOutInterFreq/VS.HSDPA.HHO.H2H.At-
tOutInterFreq) x 100%
Object CELL
Unit/Range %
Note None
1.5.11 H2D Intra-Frequency Hard Handover Success Ratio

Table 1-73 H2D Intra-Frequency Hard Handover Success Ratio
Name H2D Intra-Frequency Hard Handover Success Ratio
Formula H2D Intra-Frequency Hard Handover Success Ratio = (Number of successful

H2D intra-frequency hard handovers/Number of H2D intra-frequency hard
handover attempts) x 100%

1 RAN KPI Reference
Description This KPI provides the success rate of HSDPA-to-DCH intra-frequency hard
handovers in a cell.
A hard handover is triggered by any of the following messages:
l RADIO BEARER RECONFIGURATION
l RADIO BEARER SETUP
l RADIO BEARER RELEASE
Accordingly, a UE may respond with one of the following messages:
l RADIO BEARER RECONFIGURATION COMPLETE
l RADIO BEARER SETUP COMPLETE
l RADIO BEARER RELEASE COMPLETE
Assume that a hard handover is triggered by the RADIO BEARER
RECONFIGURATION message. The number of successful H2D intra-
frequency hard handovers is measured in the best cell where the UE camps
on before the hard handover when the RNC receives from the UE a RADIO
BEARER RECONFIGURATION COMPLETE message during an intra-
frequency hard handover.
Associated H2D Intra-frequency Hard Handover Success Ratio =

Counters (VS.HSDPA.HHO.H2D.SuccOutIntraFreq/ VS.HSDPA.HHO.H2D.At-
Object CELL
Unit/Range %
1.5.12 H2D Inter-Frequency Hard Handover Success Ratio

Table 1-74 H2D Inter-Frequency Hard Handover Success Ratio
Name H2D Inter-Frequency Hard Handover Success Ratio
Formula H2D Inter-Frequency Hard Handover Success Ratio =(H2D Inter - Frequency
Hardover Success Ratio/H2D Inter - Frequency Hard Handover Attempt) x
100%

1 RAN KPI Reference
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 SETUP
response.
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.
Associated H2D Inter-Frequency Hard Handover Success Ratio =

Counters (VS.HSDPA.HHO.H2D.SuccOutInterFreq/VS.HSDPA.HHO.H2D.At-
Object CELL
Unit/Range %
Note None
1.5.13 E2D Intra-Frequency Hard Handover Success Ratio
Table 1-75 E2D Intra-Frequency Hard Handover Success Ratio
Name E2D Intra-Frequency Hard Handover Success Ratio
Formula E2D Intra-Frequency Hard Handover Success Ratio =(Number of successful

E2D intra-frequency hard handovers /Number of E2D intra-frequency hard

1 RAN KPI Reference
Description This KPI provides the success rate of EDCH-to-DCH intra-frequency hard
handovers in a cell.
The number of E2D intra-frequency hard handover attempts is measured in
the HSUPA serving cell where the UE camps on before the handover when
the RNC sends the UE a RADIO BEARER RECONFIGURATION message
during an EDCH-to-DCH intra-frequency hard handover.
The number of successful E2D intra-frequency hard handovers is measured
in the HSUPA serving cell where the UE camps on before the handover when
the RNC receives from the UE a RADIO BEARER RECONFIGURATION
COMPLETE message during an EDCH-to-DCH intra-frequency hard
handover.
Associated E2D Intra-frequency Hard Handover Success Ratio =

Counters (VS.HSUPA.HHO.E2D.SuccOutIntraFreq/VS.HSUPA.HHO.E2D.At-
Object CELL
Unit/Range %
1.5.14 H2D Channel Switch Success Ratio
Table 1-76 H2D Channel Switch Success Ratio
Name H2D Channel Switch Success Ratio
Formula H2D Channel Switch Success Ratio =(Channel Switch Success/ Channel
Switch Attempt) x 100%
Description This KPI is used to check the channel switch success ratio when UE switches
from HSDPA to DCH in 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.
Associated H2D Channel Switch Success Ratio=

Counters (VS.HSDPA.H2D.Succ/VS.HSDPA.H2D.Att) x 100%

1 RAN KPI Reference
Object CELL
Unit/Range %
1.5.15 D2H Channel Switch Success Ratio
Table 1-77 D2H Channel Switch Success Ratio
Name D2H Channel Switch Success Ratio
Formula D2H Channel Switch Success Ratio = (Channel Switch Success/ Channel
Switch Attempt) x 100%
Description This KPI is used to check the channel switch success ratio when the UE
switches from DCH to HSDPA i 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.
Associated D2H Channel Switch Success Ratio =

Counters (VS.HSDPA.D2H.Succ/VS.HSDPA.D2H.Att) x 100%
Object CELL
Unit/Range %
1.5.16 CS W2G Inter-RAT Handover Out Success Ratio
Table 1-78 CS W2G Inter-RAT Handover Out Success Ratio
Name CS W2G Inter-RAT Handover Out Success Ratio

1 RAN KPI Reference
Formula CS W2G Inter-RAT Handover Out Success Ratio = (CS Inter - RAT
Handover Success/CS Inter - RAT Handover Attempt) x 100%
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 the RNC
receives an IU RELEASE COMMAND message with the cause value of
"Successful Relocation", "Normal Release", or "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.
Number of CS W2G inter-RAT handover attempts = Number of
HANDOVER FROM UTRAN COMMAND messages sent from the RNC
during CS outgoing inter-RAT handovers - Number of CS inter-RAT
handover cancellations caused by UE's failures in receiving the message
Associated CS W2G Inter-RAT Handover Out Success Ratio (RNC) =

Counters (VS.IRATHO.SuccOutCS.RNC/VS.IRATHO.AttOutCS.RNC) x 100%
CS W2G Inter-RAT Handover Out Success Ratio (Cell) =
[(IRATHO.SuccOutCS)/(IRATHO.AttOutCS -
VS.IRATHOCS.Cancel.ReEstab)] x 100%
Object RNC, CELL
Unit/Range %
Note You are advised to accumulate the related numerators and denominators of
the cell level to calculate RNC-level KPIs. For example, if there are n cells
under an RNC, an RNC-level KPI is calculated in the following formula:
{Sum(IRATHO.SuccOutCS)/[Sum(IRATHO.AttOutCS) - Sum
(VS.IRATHOCS.Cancel.ReEstab)]} x 100%
1.5.17 PS W2G Inter-RAT Handover Out Success Ratio
Table 1-79 PS W2G Inter-RAT Handover Out Success Ratio
Name PS W2G Inter-RAT Handover Out Success Ratio
Formula PS W2G Inter-RAT Handover Out Success Ratio = (Number of Successful

PS Inter RAT Outgoing Handover/Number of PS Inter-RAT Outgoing
Handover Attempt) x 100%

1 RAN KPI Reference
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 RANAP IU RELEASE COMPLETE message after
receiving the IU RELEASE COMMAND message with the cause of
"Successful Relocation", "Normal Release" or "Network Optimization." In
this case, the PS outgoing inter-RAT handover succeeds and the counter is
measured.
Number of PS W2G inter-RAT handover attempts = Number of CELL
CHANGE ORDER FROM UTRAN messages sent from the RNC during PS
outgoing inter-RAT handovers - Number of PS inter-RAT handover
cancellations caused by UE's failures in receiving the message
Associated PS W2G Inter-RAT Handover Out Success Ratio(RNC) =

Counters (VS.IRATHO.SuccOutPSUTRAN.RNC/
VS.IRATHO.AttOutPSUTRAN.RNC) x 100%
PS W2G Inter-RAT Handover Out Success Ratio (Cell) =
[IRATHO.SuccOutPSUTRAN/(IRATHO.AttOutPSUTRAN -
VS.IRATHOPS.Cancel.ReEstab)] x 100%
Object RNC, CELL
Unit/Range %
Note You are advised to accumulate the related numerators and denominators of
the cell level to calculate RNC-level KPIs. For example, if there are n cells
under an RNC, an RNC-level KPI is calculated in the following formula:
{Sum(IRATHO.SuccOutPSUTRAN)/[Sum(IRATHO.AttOutPSUTRAN) -
Sum(VS.IRATHOPS.Cancel.ReEstab)]} x 100%
1.5.18 PS G2W Inter-RAT Handover In Success Ratio
Table 1-80 PS G2W Inter-RAT Handover In Success Ratio
Name PS G2W Inter-RAT Handover In Success Ratio
Formula PS G2W Inter-RAT Handover In Success Ratio = (The number of PS IRAT

handover in Success/ The number of PS IRAT Handover in Attempt) x 100%

1 RAN KPI Reference
Description This KPI is used to check the PS inter-RAT handover in success ratio in 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.
Associated PS G2W Inter-RAT Handover In Success Ratio=

Counters [(RRC.SuccConnEstab.IRATCCO+RRC.SuccConnEstab.IRAT-
CelRes)/
(RRC.AttConnEstab.IRATCCO+RRC.AttConnEstab.IRATCelRes)] x
100%
Object CELL
Unit/Range %
Note The KPI includes the IRAT cell reselection of UE in idle status.The RNC
level KPI is calculated by aggregating all the cell counters.
1.5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio
Table 1-81 HSDPA W2G Inter-RAT Handover Out Success Ratio
Name HSDPA W2G Inter-RAT Handover Out Success Ratio
Formula HSDPA W2G Inter-RAT Handover Out Success Ratio =(HSDPA Inter - RAT
HO Success/ HSDPA Inter - RAT HO Attempt) x 100%
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.

1 RAN KPI Reference
Associated HSDPA W2G Inter-RAT Handover Out Success Ratio=

Counters (VS.IRATHO.HSDPA.SuccOutPSUTRAN/VS.IRATHO.HSDPA.At-
tOutPSUTRAN) x 100%
Object CELL
Unit/Range %
Note None
1.5.20 SRNC Relocation Success Ratio
Table 1-82 SRNC Relocation Success Ratio
Name SRNC Relocation Success Ratio
Formula SRNC Relocation Success Ratio = (SRNC Relocation Success / SRNC

Relocation Attempt) x 100%
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).
Associated SRNC Relocation Success Ratio =

Counters [(VS.SRELOC.SuccExecUEInvolCS+
VS.SRELOC.SuccExecUEInvolPS +
VS.SRELOC.SuccExecUENonInvolCS +
VS.SRELOC.SuccExecUENonInvolPS)/
(RELOC.SuccPrepUEInvolCS+
RELOC.SuccPrepUENotInvolCS +
RELOC.SuccPrepUEInvolPS+
RELOC.SuccPrepUENotInvolPS)] x 100%
Object RNC
Unit/Range %
Note None

1 RAN KPI Reference
1.5.21 TRNC Relocation Success Ratio
Table 1-83 TRNC Relocation Success Ratio
Name TRNC Relocation Success Ratio
Formula TRNC Relocation Success Ratio =(TRNC Relocation Success/TRNC

Relocation Preparation Attempt) x 100%
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.
Associated TRNC Relocation Success Ratio =

Counters [(VS.TRELOC.SuccExecUEInvolCS+
VS.TRELOC.SuccExecUEInvolPS+
VS.TRELOC.SuccExecUENotInvolCS+
VS.TRELOC.SuccExecUENotInvolPS)/
(RELOC.SuccResAllocUEInvolCS+
RELOC.SuccResAllocUENotInvolCS+
RELOC.SuccResAllocUEInvolPS+
RELOC.SuccResAllocUENotInvolPS)] x 100%
Object RNC
Unit/Range %
Note None
1.5.22 E-DCH Soft Handover Success Ratio
Table 1-84 E-DCH Soft Handover Success Ratio
Name E-DCH Soft Handover Success Ratio

1 RAN KPI Reference
Formula E-DCH Soft Handover Success Ratio =(Successful Attempts to Add or Delete
EDCH Links/Attempts to Add or Delete EDCH Links due to Soft Handover)
x 100%
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.
Associated E-DCH Soft Handover Success Ratio=

Counters (VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%
Object CELL
Unit/Range %
Note None
1.5.23 E-DCH Cell Change Success Ratio with SHO
Table 1-85 E-DCH Cell Change Success Ratio with SHO
Name E-DCH Cell Change Success Ratio with SHO
Formula E-DCH Cell Change Success Ratio with SHO =(Successful Attempts to
Change EDCH Serving Cells/Attempts to Change EDCH Serving Cells due
to Soft Handover or Multiple Links) x 100%

1 RAN KPI Reference
Description This KPI is used to check the success ratio of HSUPA serving cell changes
in soft handover status for cell.
l The successful HSUPA serving cell changes in soft handover status for
cell, this procedure can be triggered with the following messages:
l Accordingly, the UE sends the following messaged to the RNC as a
response:
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.
Associated E-DCH Service Cell Change Success Ratio with SHO =

Counters (VS.HSUPA.SHO.ServCellChg.SuccOut/
VS.HSUPA.SHO.ServCellChg.AttOut) x 100%
Object CELL
Unit/Range %
Note None
1.5.24 E-DCH Cell Change Success Ratio with Inter-HHO
Table 1-86 E-DCH Cell Change Success Ratio with Inter-HHO
Name E-DCH Cell Change Success Ratio with Inter-HHO

1 RAN KPI Reference
Formula E-DCH Cell Change Success Ratio with Inter-HHO =(Successful Attempts
to Change Serving Cell/Attempts to Change EDCH Serving Cells due to
EDCH-to-EDCH Inter-Frequency Hard Handover Triggered by RNC) x
100%
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 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
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.
Associated E-DCH Service Cell Change Success Ratio with Inter-HHO=

Counters (VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.At-
Object CELL
Unit/Range %
Note None
1.5.25 E2D Channel Switch Success Ratio
Table 1-87 E2D Channel Switch Success Ratio
Name E2D Channel Switch Success Ratio

1 RAN KPI Reference
Formula E2D Channel Switch Success Ratio = (Successful Attempts to Switch

Channel Type from EDCH to DCH/Attempts to Switch Change Type from
EDCH to DCH) x 100%
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.
Associated E2D Channel Switch Success Ratio =

Counters (VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%
Object CELL
Unit/Range %
Note None
1.5.26 D2E Channel Switch Success Ratio
Table 1-88 D2E Channel Switch Success Ratio
Name D2E Channel Switch Success Ratio
Formula D2E Channel Switch Success Ratio =(Successful Attempts to Switch

Channel Type from DCH to EDCH/Attempts to Switch Change Type from
DCH to EDCH) x 100%
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.

1 RAN KPI Reference
Associated D2E Channel Switch Success Ratio (Intra Cell) =

Counters (VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%
Object CELL
Unit/Range %
Note None
1.5.27 E2D Handover Success Ratio with Inter HHO
Table 1-89 E2D Handover Success Ratio with Inter HHO
Name E2D Handover Success Ratio with Inter HHO
Formula E2D Handover Success Ratio with Inter HHO =(Successful Attempts to
Switch Channel Type from EDCH to DCH/Attempts to Switch Change Type
from EDCH to DCH) x 100%
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.
Associated E-DCH to DCH Handover Success Ratio (with Inter HHO) =

Counters (VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.At-
Object CELL
Unit/Range %
Note None
1.5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio

1 RAN KPI Reference
Table 1-90 HSUPA W2G Inter-RAT Handover Out Success Ratio
Name HSUPA W2G Inter-RAT Handover Out Success Ratio
Formula HSUPA W2G Inter-RAT Handover Out Success Ratio = (Successful RNC-
Originated PS Domain Outgoing Inter - RAT Handover for HSUPA/Attempt
RNC-Originated PS Domain Outgoing Inter-RAT Handovers for HSUPA) x
100%
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.
Associated HSUPA W2G Inter-RAT Handover Out Success Ratio =

Counters (VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.At-
tOutPSUTRAN) x 100%
Object CELL
Unit/Range %
Note None
1.5.29 MBMS Service Mode Switch Success Ratio

Table 1-91 MBMS Service Mode Switch Success Ratio
Name MBMS Service Mode Switch Success Ratio
Formula MBMS Service Mode Switch Success Ratio from PTP to PTM =(Number of
channel mode switch Success from PTP to PTM/Number of channel mode
switch Attempt from PTP to PTM) x 100%
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.

1 RAN KPI Reference
Associated MBMS Service Mode Switch Success Ratio from PTP to PTM=
Counters (VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att)*100%
Object CELL
Unit/Range %
Note None
1.5.30 CS Inter-Frequency Hard Handover Success Rate
Table 1-92 CS Inter-Frequency Hard Handover Success Rate
Name CS Inter-Frequency Hard Handover Success Rate
Formula CS Inter-Frequency Hard Handover Success Rate = (Number of successful

CS inter-frequency hard handovers/Number of CS inter-frequency hard
Description This KPI provides the success rate of CS inter-frequency hard handovers of
a Cluster.
The number of CS inter-frequency hard handover attempts is measured when
the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION
message during a CS inter-frequency hard handover.
The number of successful CS inter-frequency hard handovers is measured
when the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message during a CS inter-frequency
hard handover.
Associated CS Inter-frequency Hard Handover Success Ratio =

Counters (VS.HHO.SuccInterFreqOut.CS/ VS.HHO.AttInterFreqOut.CS) x
100%
Object CELL
Unit/Range %
Note RNC-level KPIs are obtained by accumulating values of cell-level counter.
1.5.31 PS Inter-Frequency Hard Handover Success Rate
Table 1-93 PS Inter-Frequency Hard Handover Success Rate
Name PS Inter-Frequency Hard Handover Success Rate

1 RAN KPI Reference
Formula PS Inter-Frequency Hard Handover Success Rate = ( Number of successful

PS inter-frequency hard handovers/Number of PS inter-frequency hard
Description This KPI provides the success rate of PS inter-frequency hard handovers of
a Cluster.
The number of PS inter-frequency hard handover attempts is measured when
the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION
message during a PS inter-frequency hard handover.
The number of successful PS inter-frequency hard handovers is measured
when the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message during a PS inter-frequency
hard handover.
Associated PS Inter-frequency Hard Handover Success Ratio=

Counters (VS.HHO.SuccInterFreqOut.PS/ VS.HHO.AttInterFreqOut.PS) x
100%
Object CELL
Unit/Range %
Note RNC-level KPIs are obtained by accumulating values of cell-level counter.
1.6 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.
1.6.1 CS Service Drop Ratio
Table 1-94 CS Service Drop Ratio
Name CS Service Drop Ratio
Formula CS Service Drop Ratio =(Number of CS RAB Abnormal Releases/Total

number of CS RAB Releases) x 100%

1 RAN KPI Reference
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.
Associated CS Service Drop Ratio (Cell) =

Counters [VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+
VS.RAB.NormRel.CS)] x 100%
CS Service Drop Ratio (RNC) =
[VS.RAB.AbnormRel.CS.RNC/(VS.RAB.AbnormRel.CS.RNC+
VS.RAB.NormRel.CS.RNC)] x 100%
Object CELL, RNC
Unit/Range %
Note This KPI involves CS call drops due to authentication failure during PS
security mode in the cell. You can subtract VS.RAB.AbnormRel.CS.Se-
curity from the numerator of the formula to decrease the value of this KPI.
1.6.2 CS Call Drop Rate in CS+PS Combined Services

Table 1-95 CS Call Drop Rate in CS+PS Combined Services
Name CS Call Drop Rate in CS+PS Combined Services
Formula CS Call Drop Rate in CS+PS Combined Services =( Number of times that a
CS call in a CS+PS combined service drops/ Number of CS+PS combined
service release times) x 100%
Description This KPI provides the drop rate of CS calls in CS+PS combined services.
It reflects the retainability of CS+PS combined services in an RNC or cluster.
When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST
message. After receiving the message, the CN sends an IU RELEASE
COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User
Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization"), then the number of times that a CS call in a CS+PS combined
service drops is measured in the best cell that the UE camps on if the message
is for a CS call in a CS+PS combined service.

1 RAN KPI Reference
Associated CS Call Drop Rate in CS+PS Combined Services (Cell) =

Counters (VS.MultiRAB.CSAbnormRel.CSPS/
(VS.MultiRAB.CSNormRel.CSPS +
VS.MultiRAB.CSAbnormRel.CSPS +
VS.MultiRAB.PSNormRel.CSPS +
VS.MultiRAB.PSAbNormRel.CSPS —
VS.MultiRAB.CSPSNormRel.CSPS —
VS.MultiRAB.CSPSAbNormRel.CSPS)) x 100%
Object CELL
Unit/Range %
Note None
1.6.3 PS Call Drop Rate in CS+PS Combined Services
Table 1-96 PS Call Drop Rate in CS+PS Combined Services
Name PS Call Drop Rate in CS+PS Combined Services
Formula PS Call Drop Rate in CS+PS Combined Services = (Number of times that a
PS connection in a CS+PS combined service fails/Number of CS+PS
combined service release times) x 100%
Description This KPI provides the PS connection failure rate in CS+PS combined
services.
It reflects the retainability of CS+PS combined services in an RNC or cluster.
When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST
message. After receiving the message, the CN sends an IU RELEASE
COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User
Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization"), then the number of times that a PS connection in a CS+PS
combined service fails is measured in the best cell that the UE camps on if
the message is for a PS service in a CS+PS combined service.
Associated PS Call Drop Rate in CS+PS Combined Services (Cell)=

Counters (VS.MultiRAB.PSAbnormRel.CSPS/
(VS.MultiRAB.CSNormRel.CSPS +
VS.MultiRAB.PSAbNormRel.CSPS +
VS.MultiRAB.PSNormRel.CSPS + VS.MultiRAB.PSAbnormRel.CSPS
— VS.MultiRAB.CSPSNormRel.CSPS —
VS.MultiRAB.CSPSAbnormRel.CSPS)) x 100%
Object CELL
Unit/Range %

1 RAN KPI Reference
Note None
1.6.4 AMR Call Drop Ratio
Table 1-97 AMR Call Drop Ratio
Name AMR Call Drop Ratio
Formula AMR Call Drop Ratio =(Number of AMR RAB Abnormal Releases/Total
number of AMR RAB Releases) x 100%
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).
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.
Associated AMR Call Drop Ratio (Cell) =

Counters [VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR+
VS.RAB.NormRel.AMR)] x 100%
AMR Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.AMR}+ Sum
{VS.RAB.AbnormRel.AMR.Iur})/
(Sum{VS.RAB.AbnormRel.AMR}+ Sum{VS.RAB.NormRel.AMR}+
Sum{VS.RAB.AbnormRel.AMR.Iur}+
Sum{VS.RAB.NormRel.AMR.Iur})] x 100%
Object CELL, RNC
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the Cell and Iur
counters in SRNC.
1.6.5 WB AMR Call Drop Rate

1 RAN KPI Reference
Table 1-98 WB AMR Call Drop Rate
Name WB AMR Call Drop Rate
Formula WB AMR Call Drop Rate = (Number of abnormally released WB AMR calls /
Total number of released WB AMR calls) x 100%
Description This KPI provides the proportion of abnormally released WB AMR calls to
the total number of released WB AMR calls. It reflects the retainability of
WB AMR calls in an RNC or a cluster.
When a fault occurs, the RNC sends the CN an IU RELEASE REQUEST or
RAB RELEASE REQUEST message. The number of abnormally released
WB AMR calls is measured in the best cell where the UE camps on when the
RNC receives an IU RELEASE COMMAND or RAB ASSIGNMENT
REQUEST message whose cause value is not "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization".
Associated WB AMR Call Drop Rate (Cell) =

Counters [VS.RAB.AbnormRel.AMRWB/ (VS.RAB.AbnormRel.AMRWB +
VS.RAB.NormRel.AMRWB)] x 100%
AMRWB Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.AMRWB} + Sum
{VS.RAB.AbnormRel.AMRWB.Iur})/(Sum
{VS.RAB.AbnormRel.AMRWB} + Sum{VS.RAB.NormRel.AMRWB}
+ Sum{VS.RAB.AbnormRel.AMRWB.Iur} + Sum
{VS.RAB.NormRel.AMRWB.Iur} )] x 100%
Object CELL, RNC
Unit/Range %
Note None
1.6.6 VP Call Drop Ratio
Table 1-99 VP Call Drop Ratio
Name VP Call Drop Ratio
Formula VP Call Drop Ratio =(Number of VP RAB Abnormal Release/Total number

of VP RAB Release) x 100%

1 RAN KPI Reference
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).
REQUEST message to the CN due to exception. If the RNC receives an IU
any one of the following information: "User Inactivity","Normal Release",
Associated VP Call Drop Ratio (Cell) =

Counters [VS.RAB.AbnormRel.CS64/(VS.RAB.AbnormRel.CS64
+VS.RAB.NormRel.CS64)] x 100%
VP Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.CS64}+Sum
{VS.RAB.AbnormRel.CS64.Iur})/
(Sum{VS.RAB.AbnormRel.CS64}+Sum{VS.RAB.NormRel.CS64}
+Sum{VS.RAB.AbnormRel.CS64.Iur}+Sum
{VS.RAB.NormRel.CS64.Iur})] x 100%
Object CELL, RNC
Unit/Range %
Note None
1.6.7 AMR Traffic Drop Ratio
Table 1-100 AMR Traffic Drop Ratio
Name AMR Traffic Drop Ratio
Formula AMR Traffic Drop Ratio = (AMR Service Erlang/Number of AMR RAB
Abnormal Releases) x 100%

1 RAN KPI Reference
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.
any one of the following information: "User Inactivity", "Normal Release",
Associated l AMR Traffic Drop Ratio (Cell) =

Counters [(VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2+
VS.RB.AMR.DL.7.95+
VS.RB.AMR.DL.7.4+
VS.RB.AMR.DL.6.7+
VS.RB.AMR.DL.5.9+
VS.RB.AMR.DL.5.15+
VS.RB.AMR.DL.4.75) x {SP}/60]/
VS.RAB.AbnormRel.AMR
l AMR Traffic Drop Ratio (RNC) =
[(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.5.15.RNC+
VS.RB.AMR.DL.12.2.RNC) x {SP}/60]/
(VS.RAB.AbnormRel.AMR.RNC)
Object CELL, RNC
Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note None

1 RAN KPI Reference
1.6.8 VP Traffic Drop Ratio
Table 1-101 VP Traffic Drop Ratio
Name VP Traffic Drop Ratio
Formula VP Traffic Drop Ratio = (VP Service Erlang/Number of VP RAB Abnormal

Releases) x 100%
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:
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.
Associated VP Traffic Drop Ratio (Cell) =

Counters (VS.RB.CS.Conv.DL.64 x {SP}/60)/VS.RAB.AbnormRel.CS64
VP Traffic Drop Ratio (RNC) =
(VS.RB.CS.Conv.DL.64.RNC x {SP}/60)/
(VS.RAB.AbnormRel.CS64.RNC)
Object CELL, RNC
Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note None
1.6.9 PS Call Drop Ratio

Table 1-102 PS Call Drop Ratio
Name PS Call Drop Ratio
Formula PS Call Drop Ratio = (Number of PS RAB Abnormal Releases/Total Number

of PS RAB Releases) x 100%

1 RAN KPI Reference
Description This KPI provides the ratio of the PS RAB abnormal Releases to the total
PSRAB Releases (Normal Release + Abnormal Release) and is used to check
the retainabililty of PS Service within the UTRAN (RNC or Cluster).
Associated PS Call Drop Ratio (Cell) =

Counters [VS.RAB.AbnormRel.PS/(VS.RAB.AbnormRel.PS+
VS.RAB.NormRel.PS)] x 100%
PS Call Drop Ratio (RNC) =
[VS.RAB.AbnormRel.PS.RNC/(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNC)] x 100%
Object CELL, RNC
Unit/Range %
Note This KPI involves PS connection failures due to authentication failure during
CS security mode in the cell. You can subtract VS.RAB.AbnormRel.PS.Se-
curity from the numerator of the formula to decrease the value of this KPI.
1.6.10 PS Call Drop Ratio (PCH)

Table 1-103 PS Call Drop Ratio (PCH)
Name PS Call Drop Ratio (PCH)
Formula PS Call Drop Ratio (PCH) =(Number of PS RAB Abnormal Releases/Total

Number of PS RAB Releases) x 100%

1 RAN KPI Reference
Description Compared with 1.6.9 PS Call Drop Ratio, this KPI deducts abnormal RAB
releases caused by UE's state transition to CELL_PCH or URA_PCH.
Smartphones stay in the always-online state in networks when state transition
to PCH is enabled. If state transition to PCH is enabled and there is no data
transmission for a specific period of time, these UEs transit from connected
mode to the PCH state instead of idle mode, resulting in abnormal PS RAB
releases. As a result, the number of normal PS RAB releases decreases and
the value of denominator Total Number of PS RAB Releases is reduced.
The corresponding KPI deteriorates if the original formula for calculating PS
Call Drop Ratio is used.
A RAB release caused by UE's state transition from CELL_DCH to
CELL_PCH or URA_PCH without PS data transmission should be
considered as a normal RAB release because the transition has no impact on
user experience. Therefore, PCH-related abnormal RAB releases caused by
state transition from CELL_DCH to CELL_PCH or URA_PCH are not taken
into account for calculating PS Call Drop Ratio.

1 RAN KPI Reference
Associated l PS Call Drop Ratio with PCH (Cell) =

Counters [(VS.RAB.AbnormRel.PS-
VS.RAB.AbnormRel.PS.PCH-
VS.RAB.AbnormRel.PS.D2P-
VS.RAB.AbnormRel.PS.F2P) /
(VS.RAB.AbnormRel.PS+
VS.RAB.NormRel.PS-
VS.RAB.NormRel.PS.PCH+
VS.DCCC.D2P.Succ+
VS.DCCC.Succ.F2P+
VS.DCCC.Succ.F2U+
VS.DCCC.Succ.D2U)] x 100%
l PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNC-
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.AbnormRel.PS.D2P}-
Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNC-
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.NormRel.PS.PCH} +
Sum{VS.DCCC.D2P.Succ} +
Sum{VS.DCCC.Succ.F2P} +
Sum{VS.DCCC.Succ.F2U}+
Sum{VS.DCCC.Succ.D2U})] x 100%
Object CELL, RNC
Unit/Range %

1 RAN KPI Reference
Note 1. A RAB release caused by UE's state transition to PCH state should be
considered as a normal RAB release for calculating PS Call Drop Ratio.
2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is
subtracted from the denominator?
l If a UE transit to PCH state and then to idle mode, it will be counted
twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P,
VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and
VS.RAB.NormRel.PS.
l The same reason as VS.RAB.AbnormRel.PS.PCH.
3. The measurement object of the counters in Sum{*} is the cell, the RNC
level KPI can be calculated approximately by aggregating all the cell level
counters in the SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS RAB Establishment located in DRNC
via Iur interface, this scenario is not taken into account in the formula.
1.6.11 PS Call Drop Ratio (PCH & Combined Service)

Table 1-104 PS Call Drop Ratio (PCH & Combined Service)
Name PS Call Drop Ratio (PCH & Combined Service)
Formula PS Call Drop Ratio (PCH & Combined Service) =(Number of PS RAB
Abnormal Releases/Total Number of PS RAB Releases) x 100%
Description Compared with 1.6.10 PS Call Drop Ratio (PCH), this KPI deducts
abnormal RAB releases caused by PS service timer expiration after a
successful CS inter-RAT handover in combined CS+PS service.
For CS+PS combined services, after CS inter-RAT handovers are complete,
abnormal RAB releases caused by expiration of the PS service timer are
regarded as problems occurring in GSM networks. Therefore, they are not
taken into account for calculating PS Call Drop Ratio in UMTS networks.

1 RAN KPI Reference
Associated l PS Call Drop Ratio with PCH (Cell) =

Counters [(VS.RAB.AbnormRel.PS-
VS.MultiRAB.PSAbnormRel.ResumeExp -
VS.RAB.AbnormRel.PS.PCH -
VS.RAB.AbnormRel.PS.D2P -
VS.RAB.AbnormRel.PS.F2P)/
(VS.RAB.AbnormRel.PS +
VS.RAB.NormRel.PS -
VS.RAB.AbnormRel.PS.PCH -
VS.RAB.NormRel.PS.PCH +
VS.DCCC.D2P.Succ +
VS.DCCC.Succ.F2P +
VS.DCCC.Succ.F2U +
VS.DCCC.Succ.D2U)] x 100%
l PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNC -
Sum{VS.MultiRAB.PSAbnormRel.ResumeExp} -
Sum{VS.RAB.AbnormRel.PS.PCH} -
Sum{VS.RAB.AbnormRel.PS.D2P} -
Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC +
VS.RAB.NormRel.PS.RNC -
Sum{VS.RAB.AbnormRel.PS.PCH} -
Sum{VS.RAB.NormRel.PS.PCH} +
Sum{VS.DCCC.D2P.Succ} +
Sum{VS.DCCC.Succ.F2P} +
Sum{VS.DCCC.Succ.F2U} +
Sum{VS.DCCC.Succ.D2U})] x 100%
Object Cell, RNC
Unit/Range %

1 RAN KPI Reference
Note 1. A RAB release caused by UE's state transition to PCH state should be
considered as a normal RAB release for calculating PS Call Drop Ratio.
2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is
subtracted from the denominator?
l If a UE transit to PCH state and then to idle mode, it will be counted
twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P,
VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and
VS.RAB.NormRel.PS.
l The same reason as VS.RAB.AbnormRel.PS.PCH.
3. The measurement object of the counters in Sum{*} is the cell, the RNC
level KPI can be calculated approximately by aggregating all the cell level
counters in the SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS RAB Establishment located in DRNC
1.6.12 PS R99 Call Drop Ratio
Table 1-105 PS R99 Call Drop Ratio
Name PS R99 Call Drop Ratio
Formula PS R99 Call Drop Ratio =(Number of PS R99 RAB Abnormal Release/Total
Number of PS R99 RAB Release) x 100%
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).

1 RAN KPI Reference
Associated PS R99 Call Drop Ratio (Cell) =

Counters (VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99
+VS.RAB.NormRel.PSR99) x 100%
PS R99 Call Drop Ratio (RNC)=
[VS.RAB.AbnormRel.PSR99+
(VS.RAB.AbnormRel.PS.Conv.Iur+
VS.RAB.AbnormRel.PS.Str.Iur+
VS.RAB.AbnormRel.PS.BE.Iur-
VS.RAB.AbnormRel.HSDPA.Iur)]/
[VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99+
(VS.RAB.NormRel.PS.Conv.Iur+
VS.RAB.NormRel.PS.Str.Iur+
VS.RAB.NormRel.PS.BE.Iur-
VS.RAB.NormRel.HSDPA.Iur)+
(VS.RAB.AbnormRel.PS.Conv.Iur+
VS.RAB.AbnormRel.PS.Str.Iur+
VS.RAB.AbnormRel.PS.BE.Iur-
VS.RAB.AbnormRel.HSDPA.Iur)]*100%
Object CELL
Unit/Range %
Note This KPI involves the call drops of UEs in CELL_PCH, URA_PCH, or
CELL_FACH state.
1.6.13 PS R99 Call Drop Ratio (PCH)

Table 1-106 PS R99 Call Drop Ratio (PCH)
Name PS R99 Call Drop Ratio (PCH)
Formula PS R99 Call Drop Ratio (PCH) = Number of PS R99 RAB Abnormal Release/
Total Number of PS R99 RAB Release) x 100%
Description Compared with PS R99 Call Drop Ratio, this KPI takes the PCH state into
account.

1 RAN KPI Reference
Associated PS R99 Call Drop Ratio with PCH (Cell) =

Counters [(VS.RAB.AbnormRel.PSR99-
VS.RAB.AbnormRel.PS.R99D2P-
VS.RAB.AbnormRel.PS.F2P)/
(VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99-
VS.RAB.NormRel.PS.PCH+
VS.HSDPA.F2H.Succ+
VS.HSDPA.D2H.Succ+
VS.PSR99.D2P.Succ+
VS.DCCC.Succ.F2P+
VS.DCCC.Succ.F2U)] x 100%
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
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.
1.6.14 PS BE Call Drop Ratio
Table 1-107 PS BE Call Drop Ratio
Name PS BE Call Drop Ratio
Formula PS BE Call Drop Ratio =(Number of PS BE RAB Abnormal Release/Total

Number of PS BE RAB Release) x 100%

1 RAN KPI Reference
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).
Associated PS BE Call Drop Ratio (Cell) =

Counters [VS.RAB.AbnormRel.PS.BE/(VS.RAB.AbnormRel.PS.BE +
VS.RAB.NormRel.PS.BE)] x 100%
PS BE Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.PS.BE} + Sum
{VS.RAB.AbnormRel.PS.BE.Iur})/
(Sum{VS.RAB.AbnormRel.PS.BE} + Sum{VS.RAB.NormRel.PS.BE}
+Sum{VS.RAB.AbnormRel.PS.BE.Iur}+
Sum{VS.RAB.NormRel.PS.BE.Iur})] x 100%
Object CELL, RNC
Unit/Range %
Note RNC level KPI can be calculated approximately by aggregating all the Cell
and Iur level counters in SRNC.
1.6.15 HSDPA Call Drop Ratio
Table 1-108 HSDPA Call Drop Ratio
Name HSDPA Call Drop Ratio
Formula HSDPA Call Drop Ratio = (Number of HSDPA RAB Abnormal Releases/
Total Number of HSDPA RAB Releases) x 100%

1 RAN KPI Reference
Description This KPI provides the ratio of the HSDPA RAB abnormal Releases to the
total HSDPA RAB Releases (Normal Release+ Abnormal Release) and is
used to check the retainabililty of HSDPA Service within the UTRAN (RNC
or Cluster).
Associated l HSDPA Call Drop Ratio (Cell) =

Counters [(VS.HSDPA.RAB.AbnormRel)/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel+
VS.HSDPA.H2D.Succ+
VS.HSDPA.H2F.Succ+
VS.HSDPA.HHO.H2D.SuccOutIntraFreq+
VS.HSDPA.HHO.H2D.SuccOutInterFreq)] x 100%
l HSDPA Call Drop Ratio (RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq})] x 100%
Object CELL, RNC
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 HSDPA RAB
release (Including the transitions due to mobility).
1.6.16 HSDPA Call Drop Ratio (PCH)

1 RAN KPI Reference
Table 1-109 HSDPA Call Drop Ratio (PCH)
Name HSDPA Call Drop Ratio (PCH)
Formula HSDPA Call Drop Ratio (PCH) = (Number of HSDPA RAB Abnormal
Releases/Total Number of HSDPA RAB Releases) x 100%
Description Compared with HSDPA Call Drop Ratio, this KPI takes the PCH state into
account.
Associated l HSDPA Service Drop Ratio with PCH (Cell) =

Counters [(VS.HSDPA.RAB.AbnormRel-
VS.HSDPA.RAB.AbnormRel.H2P)/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel+
VS.HSDPA.HHO.H2D.SuccOutIntraFreq+
VS.HSDPA.HHO.H2D.SuccOutInterFreq+
VS.HSDPA.H2D.Succ+
VS.HSDPA.H2F.Succ+
VS.HSDPA.H2P.Succ)] x 100%
l HSDPA Service Drop Ratio with PCH(RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}-
Sum{VS.HSDPA.RAB.AbnormRel.H2P})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq}+
Sum{VS.HSDPA.H2P.Succ})] x 100%
Object CELL, RNC
Unit/Range %
Note The occasion of a UE transferring out of PS HS-DSCH Channel state (H2D,

H2F, H2P) should be considered as a normal RAB release for calculating the
formula of PS HSDPA Call Drop Ratio.
1.6.17 HSUPA Call Drop Ratio

1 RAN KPI Reference
Table 1-110 HSUPA Call Drop Ratio
Name HSUPA Call Drop Ratio
Formula HSUPA Call Drop Ratio = (Number of HSUPA RAB Abnormal Release/
Total number of HSUPA RAB Release) x 100%
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).
Associated l HSUPA Call Drop Ratio (Cell) =

Counters [VS.HSUPA.RAB.AbnormRel/
(VS.HSUPA.RAB.AbnormRel+
VS.HSUPA.RAB.NormRel+
VS.HSUPA.HHO.E2D.SuccOutIntraFreq+
VS.HSUPA.HHO.E2D.SuccOutInterFreq+
VS.HSUPA.E2F.Succ+
VS.HSUPA.E2D.Succ)] x 100%
l HSUPA Call Drop Ratio (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur})/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}+
Sum{VS.RAB.NormRel.HSUPA.Iur} +
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq} +
Sum{VS.HSUPA.E2F.Succ}+Sum{VS.HSUPA.E2D.Succ})] x 100%
Object CELL, RNC
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).

1 RAN KPI Reference
1.6.18 HSUPA Call Drop Ratio (PCH)
Table 1-111 HSUPA Call Drop Ratio (PCH)
Name HSUPA Call Drop Ratio (PCH)
Formula HSUPA Call Drop Ratio (PCH) =(Number of HSUPA RAB Abnormal
Release/Total Number of HSUPA RAB Release) x 100%
Description Compared with HSUPA Call Drop Ratio, this KPI takes the PCH state into
account.
Associated l HSUPA Call Drop Ratio with PCH (Cell) =

Counters [(VS.HSUPA.RAB.AbnormRel-
VS.HSUPA.RAB.AbnormRel.E2P)/
(VS.HSUPA.RAB.AbnormRel+
VS.HSUPA.RAB.NormRel+
VS.HSUPA.HHO.E2D.SuccOutIntraFreq+
VS.HSUPA.HHO.E2D.SuccOutInterFreq+
VS.HSUPA.E2F.Succ+
VS.HSUPA.E2D.Succ+
VS.HSUPA.E2P.Succ)] x 100%
l HSUPA Call Drop Ratio with PCH (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}-
Sum{VS.HSUPA.RAB.AbnormRel.E2P})/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}+
Sum{VS.RAB.NormRel.HSUPA.Iur}+
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq}+
Sum{VS.HSUPA.E2F.Succ}+
Sum{VS.HSUPA.E2D.Succ}+
Sum{VS.HSUPA.E2P.Succ})] x 100%
Object CELL, RNC
Unit/Range %

1 RAN KPI Reference
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.
1.6.19 MBMS Service PTP drop Ratio

Table 1-112 MBMS Service PTP drop Ratio
Name MBMS Service PTP drop Ratio
Formula MBMS Service PTP Drop Ratio =(Number of MBMS PTP RAB Abnormal
Release/Total Number of MBMS PTP RAB Release) x 100%
Associated MBMS Service PTP Drop Ratio =

Counters [VS.MBMS.RB.PTP.Loss.Abnorm/(VS.MBMS.RB.PTP.Loss.Abnorm
+VS.MBMS.RB.PTP.Loss.norm)]*100%
Object CELL
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the cell counters.
1.6.20 DC-HSDPA Call Drop Ratio

Table 1-113 DC-HSDPA Call Drop Ratio
Name DC-HSDPA Call Drop Ratio
Formula DC-HSDPA Call Drop Ratio =(Number of Abnormal Releases of DC-

HSDPA RABs/Number of Total Releases of DC-HSDPA RABs) x 100%

1 RAN KPI Reference
Description This KPI evaluates the retainability of DC-HSDPA services in an RNC or a

cluster. And this KPI takes the CELL_PCH or URA_PCH state into account.
l Abnormal release:
When an exception occurs, the RNC sends the CN an IU RELEASE
REQUEST or an RAB RELEASE REQUEST message. If the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message with
a cause value other than "User Inactivity", "Normal Release", "Successful
Relocation", "Network Optimization", or "UE Generated Signalling
ConnectionRelease", this counter is incremented in the best cell for the
UE.
l Normal release:
Normal releases includes RAB releases over the Iu interface and the
switchover of the RAB from a technique to another one, involving the
following scenarios:
– RAB releases over the Iu interface
– Fallback to the SC-HSDPA RAB through intra-cell channel
switchovers
– Fallback to the R99 RAB (including R99 RABs of UEs in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state)
through intra-cell channel switchovers
– Fallback to SC-HSDPA RAB through inter-cell hard handovers
(including intra-frequency and inter-frequency hard handovers)
– Fallback to R99 RAB of UEs in the CELL_DCH state through inter-
cell hard handovers (including intra-frequency and inter-frequency
hard handovers)
Associated Call Drop Rate of DC-HSDPA Services =

Counters [( VS.HSDPA.RAB.AbnormRel.DC —
VS.HSDPA.RAB.AbnormRel.DC2P)/
(VS.HSDPA.RAB.AbnormRel.DC +
VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object CELL
Unit/Range %
1.6.21 HSDPA 64QAM Call Drop Ratio

Table 1-114 HSDPA 64QAM Call Drop Ratio
Name HSDPA 64QAM Call Drop Ratio
Formula HSDPA 64QAM Call Drop Ratio =(Number of Abnormal Releases of

HSDPA 64QAM RABs/Number of Total Releases of HSDPA 64QAM
RABs) x 100%

1 RAN KPI Reference
Description This KPI evaluates the retainability of HSDPA 64QAM services in an RNC
or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into
account.
l Abnormal release:
REQUEST or an RAB RELEASE REQUEST message. When the RNC
receives from the CN an IU RELEASE COMMAND message or an RAB
ASSIGNMENT REQUEST message with a cause value other than "User
Optimization", or "UE Generated Signalling Connection Release", this
counter is incremented in the best cell for the UE.
l Normal release:
Normal releases include the RAB releases over the Iu interface and the
– Fallback to the HSDPA RAB through intra-cell channel switchovers
– Fallback to HSDPA RAB through inter-cell hard handovers (including
intra-frequency and inter-frequency hard handovers)
hard handovers)
Associated HSDPA 64QAM Call Drop Ratio (Cell)=

Counters [( VS.HSDPA.RAB.AbnormRel.64QAM — VS.HSDPA.RAB.Abnorm-
Rel.64QAM2P )/(VS.HSDPA.RAB.AbnormRel.64QAM +
VS.HSDPA.RAB.NormRel.64QAM.All )] x 100%
Object CELL
Unit/Range %
1.6.22 HSDPA MIMO Call Drop Ratio

Table 1-115 HSDPA MIMO Call Drop Ratio
Name HSDPA MIMO Call Drop Ratio
Formula HSDPA MIMO Call Drop Ratio =(Number of Abnormal Releases of HSDPA
MIMO RABs/Number of Total Releases of HSDPA MIMO RABs) x 100%

1 RAN KPI Reference
Description This KPI evaluates the retainability of HSDPA services in an RNC or a

l Abnormal release:
l Normal release:
Normal releases includes RAB releases over the Iu interface and the
hard handovers)
Associated HSDPA MIMO Call Drop Rate =

Counters [( VS.HSDPA.RAB.AbnormRel.MIMO —
VS.HSDPA.RAB.AbnormRel.MIMO2P)/
(VS.HSDPA.RAB.AbnormRel.MIMO +
Object CELL
Unit/Range %
1.6.23 HSDPA MIMO+64QAM Call Drop Ratio

Table 1-116 HSDPA MIMO+64QAM Call Drop Ratio
Name HSDPA MIMO+64QAM Call Drop Ratio
Formula HSDPA MIMO+64QAM Call Drop Ratio =[(Number of Abnormal Releases

of HSDPA MIMO+64QAM RABs)/(Number of Total Releases of HSDPA
MIMO+64QAM RABs)] x 100%

1 RAN KPI Reference
Description This KPI evaluates the retainability of HSDPA services in an RNC or a

l Abnormal release:
l Normal release:
Normal releases include the RAB releases over the Iu interface and the
– Fallback to the HSDPA MIMO RAB through intra-cell channel
switchovers
– Fallback to the HSDPA 64QAM RAB through intra-cell channel
switchovers
– Fallback to HSDPA MIMO RAB through inter-cell hard handovers
through inter-cell hard handovers
– Fallback to HSDPA 64QAM RAB through inter-cell hard handovers
hard handovers)
Associated HSDPA MIMO+64QAM Call Drop Rate =

Counters [( VS.HSDPA.RAB.AbnormRel.MIMO64QAM —
VS.HSDPA.RAB.AbnormRel.MIMO64QAM2P)/
(VS.HSDPA.RAB.AbnormRel.MIMO64QAM +
Object CELL
Unit/Range %

1 RAN KPI Reference
1.7 Service Integrity

Service Integrity KPIs mainly indicate the service capabilities for PS/HSPA throughput during
busy hours in each cell and the service UL Average BLER for evaluating the UL BLER value
of services in each cell.
1.7.1 Average UL Throughput for PS R99 Service

Table 1-117 Average UL Throughput for PS R99 Service (Active Set Cell)
Name Average UL Throughput for PS R99 Service (Active Set Cell)
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.

1 RAN KPI Reference
Associated Average UL Throughput for PS R99 Service (Active Set Cell) =

Counters VS.PS.Bkg.Kbps.UL8 +
VS.PS.Bkg.Kbps.UL16 +
VS.PS.Int.Kbps.UL8 +
VS.PS.Str.Kbps.UL8 +
VS.PS.Conv.Kbps.UL
Object CELL
Unit/Range kbit/s
Note None
Table 1-118 Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Name Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Description This KPI provides the average uplink throughput for PS R99 BE services of
a single user in a best cell.
The uplink throughput (excluding the RLC headers and retransmitted data)
for PS BE services of all users on the DCH is accumulated in a measurement
period. At the same time, the number of times when the value of the sampled
uplink throughput is not 0 is accumulated. At the end of the measurement
period, the RNC divides the total uplink throughput by the total sampling
times to obtain the average uplink throughput for PS R99 services of a single
user in a best cell.

1 RAN KPI Reference
Associated Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Counters =
VS.PS.BE.DCH.UL.SumThroughput/
VS.PS.BE.DCH.UL.SamplesThroughput
Object CELL
Unit/Range kbit/s
Note None
1.7.2 Average DL Throughput for PS R99 Service

Table 1-119 Average DL Throughput for PS R99 Service (Active Set Cell)
Name Average DL Throughput for PS R99 Service (Active Set Cell)
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.

1 RAN KPI Reference
Associated Average DL Throughput for PS R99 Service (Active Set Cell) =

Counters VS.PS.Bkg.Kbps.DL8 +
VS.PS.Bkg.Kbps.DL16 +
VS.PS.Int.Kbps.DL8 +
VS.PS.Str.Kbps.DL8 +
VS.PS.Conv.Kbps.DL
Object CELL
Unit/Range kbit/s
Note None
Table 1-120 Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)
Name Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)

1 RAN KPI Reference
Description This KPI provides the average downlink throughput for PS R99 BE services
of a single user in a best cell.
The downlink throughput (excluding the RLC headers and retransmitted data)
of PS BE services for all users on the DCH is accumulated in a measurement
period. At the same time, the number of times when the value of the sampled
downlink throughput is not 0 is accumulated. At the end of the measurement
period, the RNC divides the total downlink throughput by the total sampling
times to obtain the average downlink throughput for PS R99 services of a
single user in a best cell.
Associated Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)
Counters =
VS.PS.BE.DCH.DL.SumThroughput +
VS.PS.BE.DCH.DL.SamplesThroughput
Object CELL
Unit/Range kbit/s
Note None
1.7.3 Average UL BLER for CS Service
Table 1-121 Average UL BLER for CS Service
Name Average UL BLER for CS Service
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
1.7.4 Average UL BLER for PS Service
Table 1-122 Average UL BLER for PS Service
Name Average UL BLER for PS Service

1 RAN KPI Reference
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 Average UL BLER for PS Service =

Counters VS.ULBler.PS.BE.DCH.8 +
VS.ULBler.PS.BE.DCH.16 +
VS.ULBler.PS.BE.RACH +
VS.ULBler.PS.Conv +
VS.ULBler.PS.Str
Object CELL
Unit/Range %
Note None
1.7.5 HSDPA Throughput

Table 1-123 Mean Throughput for One HSDPA User
Name Mean Throughput for One HSDPA User
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 Mean Throughput for One HSDPA User =

Counters VS.HSDPA.MeanChThroughput
Object CELL
Unit/Range kbit/s

1 RAN KPI Reference
Note For 3900 series NodeBs, it is recommended that you use the NodeB counters
in the following formula to calculate the single user throughput. These NodeB
counters measure the valid throughput when data exists in the user buffer
every transmission time interval (TTI). In this case, the value of this KPI is
more accurate for UEs. The throughput of a single user at the NodeB MAC-
hs layer is calculated using the following formula:
VS.HSDPA.DataOutput.Traffic/
(VS.HSDPA.DataTtiNum.User x 2)
NOTE
VS.HSDPA.DataOutput.Traffic measures the total traffic volume of the MAC-hs/
MAC-ehs PDUs with ACKs from all users in a TTI within a measurement period. (Unit :
bit).
VS.HSDPA.DataTtiNum.User measures the total number of user-level TTIs (TTI =
2ms) within which there is data to transmit in HSDPA user queue buffers within a
measurement period. (VS.HSDPA.DataTtiNum.User x 2) and converts the number of
TTIs to the data transmission time.
Table 1-124 Mean Throughput for One HSDPA Cell

Name Mean Throughput for One HSDPA Cell
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 Mean Throughput for One HSDPA Cell =

Counters VS.DataOutput.Mean/(VS.DataTtiRatio.Mean -
VS.HSDPA.InactiveDataTtiRatio.Mean)
Object NodeB
Unit/Range kbit/s
Note 1. 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.
2. For 3900 series NodeBs, the HSDPA throughput at the MAC-hs layer is
calculated using the following formula:
VS.HSDPA.DataOutput.Traffic/
[(VS.DataTtiRatio.Mean -
VS.HSDPA.InactiveDataTtiRatio.Mean) x {SP} x 60]

1 RAN KPI Reference
1.7.6 HSUPA Throughput
Table 1-125 Mean Throughput for One HSUPA User
Name Mean Throughput for One HSUPA User
Description This counter indicates the mean uplink 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 Mean Throughput for One HSUPA User =

Counters VS.HSUPA.MeanChThroughput
Object CELL
Unit/Range kbit/s
Note It is recommended that you use the NodeB counters in the following formula
to calculate the single user throughput. These NodeB counters measure the
actual transmission rate sampled every transmission time interval (TTI) over
the air interface. In this case, the value of this KPI is more accurate for UEs.
The throughput of a single user transmitting the TRB data at the NodeB MAC-
e/i layer is calculated using the following formula:
(VS.HSUPA.2msTTI.Traffic +
VS.HSUPA.10msTTI.Traffic)/
(VS.HSUPA.2msPDU.TTI.Num x 0.002 +
VS.HSUPA.10msPDU.TTI.Num x 0.01)
Table 1-126 Mean Throughput for One HSUPA Cell
Name Mean Throughput for One HSUPA Cell
Description This counter provides the Mean HSUPA Cell Throughput when at least one
HSUPA UE is transmitting data during the entire measurement period.
When the data (including SRB and TRB data) of HSUPA UEs is received in
HSUPA active cells, the NodeB measures the total data that UEs successfully
receive at the MAC-e/i layer in the serving cell. At the same time, the NodeB
measures the number of TTIs when at least one HSUPA UE is transmitting
data to obtain the total transmission duration. (If there are multiple UEs
transmitting data in a TTI, this number is increased by one.) At the end of the
measurement period, the NodeB divides the total successfully received data
by the total transmission duration to obtain the average throughput at the
MAC-e/i layer in one HSUPA cell. When a UE performs a softer handover,
the data of this UE is calculated in both the original and target cells.

1 RAN KPI Reference
Associated Mean Throughput for One HSUPA Cell =

Counters VS.HSUPA.Thruput.ROTAll/
(VS.HSUPA.DataTtiNum x 0.002)
Object NodeB
Unit/Range kbit/s
Note None
1.7.7 PS UL Throughput of RNC
Table 1-127 PS UL Throughput of RNC
Name PS UL Throughput of RNC
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
1.7.8 PS DL Throughput of RNC

1 RAN KPI Reference
Table 1-128 PS DL Throughput of RNC
Name PS DL Throughput of RNC
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
Object RNC
Unit/Range kbit/s
Note None
1.7.9 MBMS Service Throughput
Table 1-129 MBMS Service Throughput
Name MBMS Service Throughput
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

1 RAN KPI Reference
1.8 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.
1.8.1 CS Equivalent Erlang of RNC
Table 1-130 CS Equivalent Erlang of RNC
Name CS Equivalent Erlang of RNC
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

1 RAN KPI Reference
1.8.2 Number of CS Users
Table 1-131 Number of CS Users
Name Number of CS Users
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.
Associated l Cell Counters

Counters (VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2+
VS.RB.AMR.DL.7.95+
VS.RB.AMR.DL.7.4+
VS.RB.AMR.DL.6.7+
VS.RB.AMR.DL.5.9+
VS.RB.AMR.DL.5.15+
VS.RB.AMR.DL.4.75);
VS.RB.CS.Conv.DL.64
l RNC Counters
(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.12.2.RNC);
VS.RB.CS.Conv.DL.64.RNC
Object CELL, RNC
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).
(Only for BSC6900)For a VP service, V1 platform equals to four Erlangs and
V2 platform equals to two Erlangs.

1 RAN KPI Reference
1.8.3 Number of PS R99 Users
Table 1-132 Number of PS R99 Users
Name Number of PS R99 Users
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.

1 RAN KPI Reference
Associated Cell Level

Counters l UL Counters:
VS.RB.PS.Bkg.UL.8
VS.RB.PS.Bkg.UL.16
VS.RB.PS.Bkg.UL.32
VS.RB.PS.Bkg.UL.64
VS.RB.PS.Bkg.UL.128
VS.RB.PS.Bkg.UL.144
VS.RB.PS.Bkg.UL.256
VS.RB.PS.Bkg.UL.384
VS.RB.PS.Int.UL.8
VS.RB.PS.Int.UL.16
VS.RB.PS.Int.UL.32
VS.RB.PS.Int.UL.64
VS.RB.PS.Int.UL.128
VS.RB.PS.Int.UL.144
VS.RB.PS.Int.UL.256
VS.RB.PS.Int.UL.384
VS.RB.PS.Conv.UL.42.8
VS.RB.PS.Conv.UL.40
VS.RB.PS.Str.UL.8
VS.RB.PS.Str.UL.16
VS.RB.PS.Str.UL.32
VS.RB.PS.Str.UL.64
VS.RB.PS.Str.UL.128
VS.RB.PS.Str.UL.144
VS.RB.PS.Str.UL.256.384
VS.RB.PS.Conv.UL.64
l DL Counters:
VS.RB.PS.Bkg.DL.8
VS.RB.PS.Bkg.DL.16
VS.RB.PS.Bkg.DL.32
VS.RB.PS.Bkg.DL.64
VS.RB.PS.Bkg.DL.128
VS.RB.PS.Bkg.DL.144
VS.RB.PS.Bkg.DL.256
VS.RB.PS.Bkg.DL.384

1 RAN KPI Reference
VS.RB.PS.Int.DL.8
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.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.Int.UL.8.RNC
VS.RB.PS.Str.UL.8.RNC

1 RAN KPI Reference
VS.RB.PS.Str.UL.256.384.RNC
VS.RB.PS.Conv.UL.8.RNC
VS.RB.PS.Conv.UL.38.8.RNC
l DL Counters:
VS.RB.PS.Bkg.DL.8.RNC
VS.RB.PS.Int.DL.8.RNC
VS.RB.PS.Str.DL.8.RNC
VS.RB.PS.Str.DL.256.384.RNC
VS.RB.PS.Conv.DL.8.RNC

1 RAN KPI Reference
VS.RB.PS.Conv.DL.42.8.RNC
Object CELL, RNC
Unit/Range None
Note The Unit is average user number, to get Erlang, should be multiplied by {SP}/
60;
The KPI should be collected during busy hour.
1.8.4 Number of HSDPA Users
Table 1-133 Number of HSDPA Users
Name Number of HSDPA Users
Description This KPI provides the mean and maximum 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
1.8.5 Number of HSUPA Users
Table 1-134 Number of HSUPA Users
Name Number of HSUPA Users

1 RAN KPI Reference
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
Note The KPI should be collected during busy hour.
1.8.6 Number of E-FACH Users
Table 1-135 Number of E-FACH Users
Name Mean Number of E-FACH Users
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
1.8.7 Number of E-RACH Users

Table 1-136 Number of E-RACH Users
Name Number of E-RACH Users

1 RAN KPI Reference
Description This KPI provide the average numbers of UEs that are carried on the E-RACH
in the cell.
The RNC takes a sample from the number of UEs carried on the E-RACH in
a cell every 5s. At the end of the measurement period, the average number of
UEs that are carried on the E-RACH is obtained by dividing the accumulated
value of sample data in the period by the number of samples.
Associated Number of E-RACH Users =

Counters VS.ERACHUEs
Object CELL
Unit/Range None
Note You are advised to measure this KPI during busy hours.
1.8.8 Number of CS Over HSPA Users
Table 1-137 Number of CS Over HSPA Users
Name Mean Number of CS Over HSPA Users
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
1.8.9 Number of HSDPA 64QAM Users
Table 1-138 Number of HSDPA 64QAM Users
Name Mean Number of HSDPA 64QAM Users

1 RAN KPI Reference
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
1.8.10 Number of HSDPA MIMO Users
Table 1-139 Number of HSDPA MIMO Users
Name Mean Number of HSDPA MIMO Users
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
obtaining the average number of MIMO UEs in the HSDPA cell.
Associated VS.HSDPA.MIMO.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
1.8.11 Number of HSUPA 16QAM users
Table 1-140 Number of HSUPA 16QAM users
Name Mean Number of HSUPA 16QAM users

1 RAN KPI Reference
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
obtaining the average number of 16QAM UEs in the HSUPA cell.
Associated VS.HSUPA.16QAM.UE.Mean.Cell
Counters
Object CELL
Unit/Range None
1.8.12 Number of HSDPA MIMO64QAM Users
Table 1-141 Number of HSDPA MIMO64QAM Users
Name Mean Number of HSDPA MIMO64QAM Users
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
1.8.13 Number of MBMS Users

Table 1-142 Number of MBMS Users
Name Mean Number of MBMS Users

1 RAN KPI Reference
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
Object CELL
Unit/Range None
1.8.14 HSDPA RLC Traffic Volume
Table 1-143 HSDPA RLC Traffic Volume
Name HSDPA RLC Traffic Volume
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

1 RAN KPI Reference
1.8.15 HSUPA RLC Traffic Volume
Table 1-144 HSUPA RLC Traffic Volume
Name HSUPA RLC Traffic Volume
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
1.8.16 R99 Service UL Traffic Volume
Table 1-145 R99 Service UL Traffic Volume
Name R99 Service UL Traffic Volume
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.

1 RAN KPI Reference
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.Int.UL.8.Traffic
VS.PS.Str.UL.8.Traffic
VS.PS.Conv.UL.Traffic
Object CELL
Unit/Range bit
Note None
1.8.17 R99 Service DL Traffic Volume

1 RAN KPI Reference
Table 1-146 R99 Service DL Traffic Volume
Name R99 Service DL Traffic Volume
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.

1 RAN KPI Reference
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.Int.DL.8.Traffic
VS.PS.Str.DL.8.Traffic
VS.PS.Conv.DL.Traffic
Object CELL
Unit/Range bit

1 RAN KPI Reference
Note None
1.8.18 E-FACH Traffic Volume
Table 1-147 E-FACH Traffic Volume
Name E-FACH Traffic Volume
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.
Associated VS.CRNCIubBytesEFACH.Tx
Counters
Object CELL
Unit/Range byte
Note None
1.8.19 E-RACH Traffic Volume
Table 1-148 E-RACH Traffic Volume
Name E-RACH Traffic Volume
Description This KPI provides the bytes of UL MAC PDUs (including the signaling data
and the service data, not including the FP header) received by the CRNC over
the ERACH FP on the Iub interface.
Associated E-RACH Traffic Volume =

Counters VS.CRNCIubBytesERACH.Rx
Object CELL
Unit/Range byte
Note None
1.8.20 Average Number of DC-HSDPA Users
Table 1-149 Average Number of DC-HSDPA Users
Name Average Number of DC-HSDPA Users

1 RAN KPI Reference
Description This KPI measures the average number of DC-HSDPA users that use this cell
as the primary or secondary carrier cell.
The RNC takes samples of the number of DC-HSDPA users that use a certain
cell as the primary or secondary cell every 5 seconds in a measurement period.
At the end of the measurement period, the RNC obtains the value of this
counter by dividing the accumulated number by the number of sampling
times.
Associated VS.HSDPA.DC.PRIM.UE.Mean.Cell
Counters VS.HSDPA.DC.SEC.UE.Mean.Cell
Object CELL
Unit/Range None


3G KPI Reference PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

3G KPI Reference PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue () Huawei Proprietary and Confidential i

1 RAN KPI Reference

About This Chapter

Product Name Product Version Solution Version

BSC6910 V100R018C00 RAN18.0

BTS3812AE NodeB: V100R018C00

Issue () Huawei Proprietary and Confidential 1

l Network planning engineers

1.1 Changes in the RAN KPI Reference

1.7 Service Integrity

Issue () Huawei Proprietary and Confidential 2

1.1 Changes in the RAN KPI Reference

1.2.1 IU Paging Success Ratio

Table 1-1 IU Paging Success Ratio

Name IU Paging Success Ratio

Formula IU Paging Success Ratio = (Number of SuccessfulPaging Messages to UEs

Associated IU Paging Success Ratio =

Note In redirection-based CSFB scenarios, the VS.RANAP.Paging.Succ.IdleUE

Issue () Huawei Proprietary and Confidential 3

1.2.2 RRC Setup Success Ratio

Name RRC Setup Success Ratio

Formula RRC Setup Success Ratio =(Number of RRC Setup Successes/Number of

Description Description of RRC Setup Success Ratio for service requests:

Issue () Huawei Proprietary and Confidential 4

Associated l RRC Setup Success Ratio (Cell.Service) =

Issue () Huawei Proprietary and Confidential 5

Issue () Huawei Proprietary and Confidential 6

1.2.3 RRC Setup Success Ratio (PCH)

Name RRC Setup Success Ratio (PCH)

Issue () Huawei Proprietary and Confidential 7

Issue () Huawei Proprietary and Confidential 8

– The value of the Cell update cause IE is "uplink data transmission"

Issue () Huawei Proprietary and Confidential 9

– After the RNC receives an RRC CONNECTION SETUP COMPLETE

Issue () Huawei Proprietary and Confidential 10

Associated l RRC Setup Success Ratio with PCH ( Cell.Service) =

Issue () Huawei Proprietary and Confidential 11

Issue () Huawei Proprietary and Confidential 12

Note The RNC-level KPI is obtained by aggregating values of cell-level counters.

Issue () Huawei Proprietary and Confidential 13

1.2.4 Radio Access Success Ratio

Name Radio Access Success Ratio

Issue () Huawei Proprietary and Confidential 14

Associated l Radio Access Success Ratio (Cell) =

Object CELL, RNC

1.2.5 Radio Access Success Ratio (PCH)

Name Radio Access Success Ratio (PCH)

Issue () Huawei Proprietary and Confidential 15

Issue () Huawei Proprietary and Confidential 16

Issue () Huawei Proprietary and Confidential 17

– When the RNC sends the CN a RAB ASSIGNMENT RESPONSE

Issue () Huawei Proprietary and Confidential 18

Associated l Radio Access Success Ratio (PCH Cell) =

Note CELLUPDATE_MEASUREMENT_OPT_SWITCH under the

Issue () Huawei Proprietary and Confidential 19

1.2.6 PS Radio Access Success Ratio

Table 1-6 PS Radio Access Success Ratio

Name PS Radio Access Success Ratio

Associated l PS Radio Access Success Ratio (Cell) =

Object CELL, RNC