HSD Formulas Details

CDMA 1xEV-DO
1xEV-DO Radio Access System

Performance and Capacity Metrics
Release 31.0
401-610-013
Issue 10
September 2008
Alcatel-Lucent - Proprietary
This document contains proprietary information of Alcatel-Lucent
and is not to be disclosed or used except in accordance with applicable agreements.
Copyright 2008 Alcatel-Lucent.

Unpublished and not for publication. All rights reserved.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2008 Alcatel-Lucent. All rights reserved.
Mandatory customer information
This information product does not contain any mandatory customer information.
Interference information: Part 15 of FCC rules
NOTE: This equipment has been tested and found to comply within the limits.
Apache
This product includes software developed by the Apache Software Foundation (http:// www.apache.org/).
Alcatel-Lucent - Proprietary
See notice on first page.
Contents
About this information product

Purpose ..........................................................................................................................................................1
Reason for reissue .........................................................................................................................................1
Information product support ..........................................................................................................................1
Technical support ..........................................................................................................................................1
How to order ..................................................................................................................................................2
How to comment ...........................................................................................................................................2
1 Introduction
Scope ......................................................................................................................................................... 1-1
Performance Metrics ................................................................................................................................. 1-2
Watchmark/IBM Prospect for Alcatel-Lucent ........................................................................................ 1-14
Acronyms ................................................................................................................................................ 1-15
2 Customer Perspective
Overview ................................................................................................................................................... 2-1
1xEV-DO Overview .................................................................................................................................. 2-2
Service Measurements Data Files ............................................................................................................. 2-4
3 Performance Metrics for Release 22

Overview ................................................................................................................................................... 3-1
Session Management Metrics .................................................................................................................... 3-3
Call Setup Metrics ..................................................................................................................................... 3-5
Call Drop Metrics .................................................................................................................................... 3-19
Data Throughput Metrics ........................................................................................................................ 3-21
Handoff Metrics ...................................................................................................................................... 3-30
Capacity Management Performance Metrics .......................................................................................... 3-32
Packet Data Reactivation Metrics ........................................................................................................... 3-33
............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1
Issue 10, May 2008 See notice on first page.
Contents
4 1xEV-DO Metrics in Watchmark Prospect for Release 22

1xEV-DO Performance Metrics ................................................................................................................ 4-1
Session Management Metrics ................................................................................................................... 4-2
Dropped Call Metrics .............................................................................................................................. 4-12
Handoff Metrics ...................................................................................................................................... 4-19
Capacity Management Metrics ............................................................................................................... 4-21

Overview ................................................................................................................................................... 5-1
Handoff Metrics ...................................................................................................................................... 5-39
Capacity Management Metrics ............................................................................................................... 5-42
6 1xEV-DO Metrics in Watchmark Prospect for Release 23
Dropped Call Metrics .............................................................................................................................. 6-14
New Metrics Retrofitted to R23 .............................................................................................................. 6-15

Overview ................................................................................................................................................... 7-1
Handoff Metrics ...................................................................................................................................... 7-37
Capacity Management Performance Metrics .......................................................................................... 7-47
............................................................................................................................................................................................................................................................
2 Alcatel-Lucent - Proprietary 401-610-013
See notice on first page. Issue 10, May 2008
Contents
8 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 24

1xEV-DO Performance Metrics Modified in Prospect R24 ...................................................................... 8-2
New 1xEV-DO Performance Metrics in Prospect R24 ............................................................................. 8-7
Existing xEV_Sector Metrics Replicated as 1xEV_Sector Carrier Metrics ........................................... 8-10
New Metrics Retrofitted to R24 .............................................................................................................. 8-12

Overview ................................................................................................................................................... 9-1
Session Management Metrics .................................................................................................................... 9-4
Connection Setup Metrics ....................................................................................................................... 9-15
Connection Drop Metrics ........................................................................................................................ 9-35
Handoff Metrics ...................................................................................................................................... 9-38
Error Statistics ......................................................................................................................................... 9-61
Power Control .......................................................................................................................................... 9-63
Capacity Management Metrics ................................................................................................................ 9-67

1xEV-DO Performance Metrics .............................................................................................................. 10-1
Modified 1xEV-DO Performance Metrics in Prospect R25 .................................................................... 10-2
Deleted 1xEV-DO Performance Metrics in Prospect R25 ...................................................................... 10-9
New 1xEV-DO Performance Metrics in Prospect R25 ......................................................................... 10-10

Overview ................................................................................................................................................. 11-1
Session Management Metrics .................................................................................................................. 11-4
Packet Data Reactivation Metrics ......................................................................................................... 11-12
Connection Setup Metrics ..................................................................................................................... 11-15
Connection Drop Metrics ...................................................................................................................... 11-38
Handoff Metrics .................................................................................................................................... 11-42
Data Transmission Metrics .................................................................................................................... 11-55
Error Statistics ....................................................................................................................................... 11-71
Power Control ........................................................................................................................................ 11-73
Capacity Management Metrics .............................................................................................................. 11-77
............................................................................................................................................................................................................................................................
Contents

1xEV-DO Performance Metrics Modified in Prospect R26 .................................................................... 12-3
New 1xEV-DO Performance Metrics in Prospect R26 ........................................................................... 12-9

Overview ................................................................................................................................................. 13-1
Session Management Metrics ................................................................................................................. 13-7
Handoff Metrics .................................................................................................................................... 13-45
Data Transmission Metrics ................................................................................................................... 13-58
Error Statistics ....................................................................................................................................... 13-96
Power Control ....................................................................................................................................... 13-98
Capacity Management Metrics ........................................................................................................... 13-108
14 1xEV-DO Metrics in IBM Prospect for Alcatel-lucent Release 27
Modified 1xEV-DO Performance Metrics in Prospect R27 .................................................................... 14-3
1xEV-DO Performance Metrics with Modified PDR/GUI Descriptions in R27 .................................. 14-23

Overview ................................................................................................................................................. 15-1
Handoff Metrics .................................................................................................................................... 15-57
Error Statistics ..................................................................................................................................... 15-121
Power Control ..................................................................................................................................... 15-123
Quality of service(QoS) metrics ......................................................................................................... 15-137
............................................................................................................................................................................................................................................................
Contents
16 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 28

Modified 1xEV-DO Performance Metrics for RNC R28 ........................................................................ 16-3
Obsolete Metrics in R28 ........................................................................................................................ 16-12

Overview ................................................................................................................................................. 17-1
Handoff Metrics .................................................................................................................................... 17-56
Power Control ...................................................................................................................................... 17-111
Capacity Management Metrics ............................................................................................................ 17-120
Quality of service(QoS) metrics .......................................................................................................... 17-123


Overview ................................................................................................................................................. 19-1
Handoff Metrics .................................................................................................................................... 19-44
Power Control ...................................................................................................................................... 19-108
Capacity Management Metrics ............................................................................................................ 19-117
Quality of service(QoS) metrics .......................................................................................................... 19-121
............................................................................................................................................................................................................................................................
Contents

Obsolete 1xEV-DO Performance Metrics in Prospect R30 .................................................................... 20-5
21 Performance Metrics for Alcatel-Lucent Release 31

Call Drop Metrics .................................................................................................................................. 21-44
Handoff Metrics .................................................................................................................................... 21-45
Power Control ..................................................................................................................................... 21-117
Quality of Service (QoS) Metrics ....................................................................................................... 21-134
Metrics Added due to SM Re-Architecture ........................................................................................ 21-144

1xEV-DO Performance Metric ............................................................................................................... 22-1
Modified 1xEV-DO Performance Metrics for Prospect R31 .................................................................. 22-2
Obsolete 1xEV-DO Performance Metrics in Release 31 ........................................................................ 22-4
New 1xEV-DO Performance Metrics in Release 31 ............................................................................... 22-5
............................................................................................................................................................................................................................................................
List of figures
1-1 RLP and MAC protocol layers ................................................................................................... 1-11

2-1 1xEV-DO Network System Block Diagram ................................................................................ 2-2
2-2 1xEV-DO Cell/AP Architecture ................................................................................................... 2-3
............................................................................................................................................................................................................................................................
List of figures
............................................................................................................................................................................................................................................................
Purpose
This document specifies the Alcatel-Lucent recommended performance metrics to
evaluate the voice services offered by the CDMA System. These performance metrics are
based on the Alcatel-Lucent 1xEV-DO system service measurements.
The IBM Prospect for Alcatel-Lucent Primitive Calculations (PCALCS) is also included
in this document.
Reason for reissue

This IP has been updated to include the new R31 chapters:
Performance Metrics for Alcatel-Lucent Release 31 (p. 21-1)
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 31 (p. 22-1)
This IP is continually updated. Check the below section for the most current changes.
After a releases GA publication, updates to this IP for that release will only be published
on the web.
Information product support

For IP usage support, contact:
1 888 727 3615 (for the continental United States)
1 630 713 5000 (for all countries).
Technical support
For technical support, contact your local customer support team. Reach them via the web
at https://support.lucent.com/ or the telephone number listed under the Technical
Assistance Center menu at http://www.lucent.com/contact/.
............................................................................................................................................................................................................................................................
How to order
To order Alcatel-Lucent information products, contact your local sales representative, use
the following websites, or use the email, phone, and fax contacts linked from Contact Us
on those sites:
Documentation: http://www.lucentdocs.com
Training: https://training.lucent.com/
How to comment
To comment on this information product, go to the Online Comment Form or email your
comments to the Comments Hotline (comments@lucent.com).
............................................................................................................................................................................................................................................................
1 Introduction
Scope
............................................................................................................................................................................................................................................................
The scope of this document is limited to defining performance metrics for the 1xEV-DO
system associated with the HDR Cell Site (HCS), Flexent Mobility Server (FMS) (which
includes the HDR Cell Site (HCS) Controller and the Packet Control Function (PCF),
Applications Processor (AP) and the Traffic Processor (TP). No specific performance
metrics associated with the PDSN are included in this document.
The performance metrics are recommended for evaluation of high speed packet data
performance for the 1xEV-DO system. The metrics are defined at the granularity of the
peg counts that comprise the metric and can be rolled up (aggregated) to a higher
granularity. For example, a metric defined on a per-sector-carrier basis can be rolled up to
the cell level by summing the values for all sector-carriers on that cell.
............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1- 1
Introduction Performance Metrics
Performance Metrics
............................................................................................................................................................................................................................................................
Overview
The Alcatel-Lucent recommended metrics for 1xEV-DO fall into the following broad
categories:
for R22 through R24:

1. Air Interface Performance Metrics
a. Session Management
b. Call Setup
c. Call Drop
d. Data Throughput
e. Handoff
2. Capacity Management Metrics
3. Packet Data Reactivation Metrics
for R25 through R28:

1. Session Management
b. Packet Data Reactivation
2. Air Interface
a. Connection Setup
b. Connection Drop
c. Handoff
d. Data Transmission
e. Error Statistics
f. Power Control
g. Capacity Management
for R28 through R30

2. Air Interface
a. Connection Setup
b. Connection Drop
............................................................................................................................................................................................................................................................
1-2 Alcatel-Lucent - Proprietary 401-610-013
c. Handoff
d. Data Throughput
e. Error Statistics
f. Power Control
3. Quality of Service
for R31
2. Air Interface
a. Connection Setup
b. Connection Drop
c. Handoff
d. Data Throughput
e. Error Statistics
f. Power Control
3. Quality Service
4. Metrics Added Due to SM Re-Architecture
............................................................................................................................................................................................................................................................
Session Management Metrics

A 1xEV-DO session begins when the AT is successfully assigned a Unicast Access
Terminal Identifier (UATI) that uniquely identifies it within a part of the network. Often,
the term 1xEV-DO session is used interchangeably with the term UATI session.
There is often some confusion between a 1xEV-DO/UATI session and a PPP session. A
UATI session is 1xEV-DO specific. A UATI session must exist for the AT and AN to
exchange information, such as over the traffic channel. It is different than a PPP session
which acts as a funnel between the AT (or client laptop/PDA) and the PDSN for end-to-
end data transfer of user data. A PPP session may only be established after UATI has been
assigned to the AT; a UATI session on the other hand can exist without a PPP session.
UATI assignment takes place autonomously upon AT power up or as in case of inter-RNC
handoffs; establishing a PPP session requires user initiation (such as dial-up connect).
There are primarily two different stages where the AT may request a UATI:
New session: When AT powers on, it sends a UATI Request message. The AN assigns
it a UATI, which is a number from a pool of unique identifiers that can be assigned to
ATs for association with that part of the network. The AT acknowledges the receipt of
the UATI Assignment message by transmitting a UATI Complete message. The UATI
Request and Complete messages are sent by the AT on the Access channel while the
UATI Assignment message is sent by the AN on the Control Channel.
Inter-RNC Idle Handoff: When the AT crosses into a different color code area while in
idle mode, a similar sequence of messages (UATI Request/Assignment/Complete) is
exchanged to transfer the UATI session. This involves assigning a new UATI. This
process is called inter-RNC Idle handoff. The AN is able to distinguish between a new
session and an inter-RNC handoff request by looking at the contents of the UATI
Request message. The AT includes a Random Access Terminal Identifier (RATI) for
the new session; in case of the inter-RNC idle handoff, it uses the existing UATI
(assigned by the old or the source RNC).
Once a UATI session is established, it may last for hours, days or weeks as long as the AN
and AT can exchange periodic heartbeats (Keep Alive Request/Response messages), and
one of the above events does not take place.
After successfully establishing a new UATI session, a series of messages are exchanged
between the AT and AN via a protocol called Configuration Negotiation (ConfgNeg). This
is a procedure for both sides to agree upon a set of configuration parameters to be
employed for the rest of the session. It is possible that even after a successful UATI
assignment, the session may be closed quickly thereafter if the ConfgNeg fails. This
possibility would lead one to think that any calculation for session setup success rate
should include the outcome of ConfgNeg; however, ConfgNeg may occur any time during
a session, not just at the beginning. For example, if Pilot Add/Drop thresholds are not set
uniformly in various parts of the network, the AN uses the ConfgNeg mechanism to
update the AT when it attempts to reactivate a dormant PPP session on a cell with different
............................................................................................................................................................................................................................................................
parameter settings. Here, no new session is established just prior to the ConfgNeg.
Currently, there is no way to differentiate ConfgNeg associated with session setups versus
the rest. Hence, Alcatel-Lucent recommends that Session Setup Success/Failure rate
should only include the UATI message sequence. Nevertheless, failures associated with
ConfgNeg should be monitored closely for any incompatible network/AT configuration. A
metric was added in R27 to monitor the configuration negotiation success rate.
Part of the configuration negotiation process for Rev A connections is to negotiate the
personality of the connection. A Rev A AT requests a personality as part of the session
setup message which is then negotiated with the AN. The AN may not be able to establish
a Rev A connection due to lack of Rev A resources, or for other reasons. A personality
switch from Rev A to Rel 0 or vice versa may occur during the setup of a subsequent
connection. There are several peg counts measuring how many times these switches occur.
Since none of these events affects the success of a session setup request they are not
included in the metrics.
Packet Data Reactivation Metrics

The Packet Data Reactivation metrics section deals with connection establishment metrics
from the PCF perspective. One is the PCF reactivation performed by the PCF when it
receives data from the PDSN for a dormant connection. The reactivation is considered
successful if the AN is able to set up a traffic channel with the AT. The other metric has to
do with the PCF's ability to activate a R-P link with the PDSN. An R-P or a A10-A11 link
is initiated when the user wishes to establish a fresh PPP connection, or upon inter-RNC
idle handoff transfer.
Call Setup/Connection Setup Metrics

End-to-end data communication between the client and an external server (such as
www.yahoo.com) is carried out over a series of intervening data paths, each involving a
unique protocol to support the transmission. One of the important pieces of this chain is
the air link. To carry out transmission between the AT and the cell site, the two sides have
to engage in an active connection, which simply means a traffic channel needs to be in
place.
A connection is established by exchanging a series of messages over the air. The process is
susceptible to failures from several sources. Connection setup success is one of the key
performance indicators that service providers should monitor in a 1xEV-DO network. The
connection success rate may have a different meaning than in the voice world. For
example, a connection setup failure may just manifest as a delayed connection setup rather
than an outright failure requiring the user to re-establish manually as it may happen in the
voice world (although the latter has been mitigated by the in-built silent re-origination
capability offered by many voice handsets today).
............................................................................................................................................................................................................................................................
Before going into individual metrics that relate to the connection setup process, it is
important to understand various connection types. The connections can be classified in a
few different ways, based on the purpose of establishing one, who initiates it, status of the
PPP session, etc. as detailed below.
For classification based on the purpose of the connection - primarily 3 connection

types:
1. Configuration negotiation - As described earlier, a new session established after a
power up or an inter-subnet handoff transfer is followed with a series of Configuration
Request/Response messages exchanged between the AT and the AN to agree upon a
set of system parameters to be employed for rest of the session. If there is no other user
induced activity by the time the negotiation is over, the connection is released by the
network thereafter. In this case, the connection is entirely devoted to the negotiation
process, and no user application data is exchanged. In some cases, it is possible that
the user has some payload to transmit which then means the connection will continue
after negotiation. Note that such connections are always initiated by the AT.
2. Establish a PPP session - A typical usage pattern of the 1xEV-DO system may be as
follows. The user powers on the AT in the morning. Shortly thereafter (in a matter of
few seconds), the AT autonomously establishes a UATI session and completes the
configuration negotiation and finally goes idle (that is, releases the traffic connection).
Sometime later, when the user wishes to access the internet, the AT must first acquire a
traffic link in order to establish a PPP session with the PDSN before any user
application data can be transmitted. As discussed here, accessing the internet requires
establishing a PPP session with the PDSN (device outside the AN) which in turn needs
a connection to be established with the AN. Note that such connections are always
initiated by the AT. Another point to note is that if the AT didn't go idle (that is, user
attempted to connect to the network immediately after power on or during the
negotiation process), a separate connection would still be needed here because
Standards require that the traffic channel for Configuration Negotiation be released
upon completion of the Configuration Negotiation process.
3. Reactivation from dormancy - In order for the PPP session to stay connected, the
traffic link need not stay active. When there is no user activity for a certain amount of
time (dormancy timer), AN instructs the AT to release the traffic connection. The PPP
session is now said to have gone dormant. When the user is ready to exchange data
again or the AN has some data for the user, the dormant PPP session is revived through
a request to establish a new traffic link or connection - this is referred to as a
reactivation. Such reactivations can be performed by either end - the AT or the AN.
Accordingly, they are commonly referred to as AT or AN initiated connections. In
1xEV-DO (as well as in 3G1x packet data), most connections are reactivations from
dormancy and, of these, primarily AT initiated.
............................................................................................................................................................................................................................................................
For classification based on which end initiates it - three types:

1. AT Initiated Connection - As the name suggests, this type of connection is prompted
by the AT or the end user. Any action that leads to traffic channel establishment
following a Connection Request message from the AT falls into this category. The
actions include configuration negotiation after a fresh power up, network (PPP)
connect, web browsing click while AT is in dormant state (reactivation), etc.
2. AN Initiated Connection - When data shows up from the network (such as internet) for
an AT that has been dormant for more than 5 sec, the AN sends a page to the AT. The
AT responds to the page by sending a Connection Request and Route Update message
to establish a new traffic channel link. Such a transition is labeled AN Initiated
Connection. This could happen, for instance, when a slow internet server responds to a
web download request several seconds later. Note that for this type of connection to
occur, there must be a PPP session in place between the PDSN and the AT.
3. Fast Connect - This is similar to AN Initiated Connection; the only difference is that
AN simply sends a TCA message to the set of sectors used for the last Connection
(a.k.a. last known Active set) instead of sending a Page to the AT. The AN resorts to
Fast Connect only if the AT has been dormant for less than a period called Suspend
Timer (set to 5 seconds in the AT). During this interval, the AT doesn't to go sleep
mode; rather, it continuously monitors the Control Channel for a TCA message. This
is a streamlined mechanism unique to 1xEV-DO that allows quick transition to the
traffic channel by foregoing the paging procedure, which can be very useful in slow
internet server response type scenario described above. Note that the Fast Connect SM
counts are mutually exclusive with the AN Initiated Connection counts.
Call Drop/Connection Drop Metrics

Once a connection setup is complete and the connection comes up stable on the traffic
channel, it can remain active for a while depending on the user activity. When both the AT
and the AN are finished exchanging RLP data and the traffic link stays idle thereafter for a
certain amount of time (Dormancy timer), the AN releases the connection by sending
Connection Close. This is a typical behavior in the 1xEV-DO world. It exemplifies a
normal or an intended release of the connection. Another form of an intended release
occurs when the AT reaches the edge of 1xEV-DO coverage while on an active connection
and decides to release the connection so that it can continue data transfer on the
underlying 3G1x Data system. This is often known as Hybrid mode handoff or 1xEV-DO
to 3G1x Active mode handoff.
On the other hand, there can be a number of reasons when a connection is released
undesirably. This event could be due to insufficient signal strength on the current Active
set, or due to internal errors on the AN/AT, or due to a soft/er handoff add/drop failure.
Such a release is commonly known as Dropped Connection. Any ongoing data transfer is
interrupted and can only be resumed by setting up a fresh connection.
............................................................................................................................................................................................................................................................
Dropped connections often occur because of poor RF link conditions on either or both the
links (forward and/or reverse). A very common scenario occurs when the AT drives out of
the coverage of a cell. Sometimes there is ample signal, but the AT does not have the
proper Pilots in its Active set to sustain the connection. This could be due to incomplete
neighbor lists, inadequate search window size, etc - in general, items indicative of a RF
optimization issue. Soft/er handoff blocking (that is, failure to allocate resources for a
handoff TCA) can also result in situations where the AT does not have the proper Active
set, causing dropped connections. Even if a TCA is assigned, the handoff may not go
through, very likely due to weak RF conditions. If the handoff fails while the AN is
waiting for a TCC after sending a TCA, it releases the connection; this is another example
of a dropped connection.
The AN may forcefully release a connection if it encounters certain internal call
processing errors. There is a special peg to capture such unintended releases and these are
included in the drop connection computation.
Often, the dropped connections are transparent to the end-user inasmuch as the user
typically does not have to reinitiate the connection. Whichever end (AT or AN) has
pending data in its queue will attempt to revive the traffic link on its own soon thereafter.
Of course, this may provide the end-user a perception of added delay or a temporary pause
in the application flow. But this scenario is not nearly as unpalatable as in the voice world,
where a dropped call is considered an annoyance and invariably requires the user to
manually revive the call. For this reason, while dropped connection rate is an important
metric that must be tracked as an indication of the health of the system, it may be
acceptable to operate a 1xEV-DO network, or some parts of it, at a dropped connection
rate several times higher than that in a voice network.
Another reason for the above statement, at least for R25 and earlier, is that most customers
are rolling out ATs configured to operate in Hybrid mode. In this mode, the AT
periodically tunes to the underlying 3G1x system to receive a voice or a SMS page. Each
such periodic visit is commonly known as a "tuneaway". The period is a function of the
Slot Cycle Index used by the AT on the 3G1x system to align each tuneaway with its
designated 3G1x paging slot. The problem is if AT receives a 3G1x voice/SMS page
during one of the tuneaways, it could accept the termination attempt right away. There is
no provision in the 3G1x standard to allow the AT to tune back to the 1xEVDO system and
signal its intent of accepting the 1x termination. As a result, the 1xEVDO system treats it
as a dropped connection much like any other connection lost due to poor RF. The dropped
connection rate is likely to increase as operators begin to roll out handsets which are not
just data only terminals (that is voice capable handsets, not just PCMCIA/PDA terminals).
This can even happen if the user decides not to take the incoming voice termination. This
is because the ringing alert is sent only after the AT has been assigned a 3G1x traffic
channel. The whole process of tuning to 3G1x, receiving a page, receiving the ring alert,
possibly transferring to the voice mail, releasing the 3G1x traffic channel and finally
tuning back to the 1xEVDO system can easily span the RF Fade timer of the 1xEVDO
............................................................................................................................................................................................................................................................
system (currently 5 sec) resulting in a dropped connection. Another scenario is when the
AT stays on 1x much longer during one of the tuneaways to register on the 1x system
(timer/zone based registration, etc.).
In R26, there is an algorithm to estimate dropped connections caused by such tuneaways.
This will help improve the accuracy of the user-perceived DO dropped connection rate.
Handoff Metrics
There are several types of handoffs in 1xEV-DO. Conceptually, they are similar to those
found in other wireless mobility based packet data networks (such as, 3G1x packet data).
Largely, they can be grouped based on whether they occur in active or idle connection
modes as described below. Not all the ones discussed have associated SM based
performance metrics, for reasons provided below.
Active handoffs:
For an active connection, one or more pilots can be added to or removed from the active
set at the same time. If the pilot being added/dropped belonged to the same cell as an
existing active set pilot, it is called softer handoff. If it is the only sector of a cell in the
AT's active set, the event is called soft handoff. The add/drop is based on the pilot Ec/Io
reported by the AT on the Route Update Message. The handoff decisions are made by the
AN as it inspects each RUM for potential handoff triggers. The actual handoff is
performed via a series of messages exchanged between the AN and the AT. The handoff
can fail for several reasons as described in the soft/er handoff failure metrics.
All pilots in the AT's active set are used to provide handoff diversity on the reverse link.
On the forward link, the AT picks only one pilot from the active set, typically the strongest
to receive Control and Traffic channel packets. Such an active set leg is also known as the
DRC-pointed sector. When another active set pilot emerges sufficiently stronger, the AT
switches its forward link reception to this dominant pilot. This process of tuning to the
strongest pilot is called virtual soft/er handoff. It is entirely managed by the AT and
communicated to the AN via DRC Cover messages. Inherently, there is no reason for such
handoffs to fail and hence, although there are SM counts to measure soft and softer virtual
handoffs, there are none to capture any failures. The lack of handoff diversity on the
forward link is offset by the localized ability at the AT to quickly switch among active set
pilots.
Another type of active handoff is a hard handoff (introduced in R26). This occurs when an
inter-frequency handoff is deemed necessary after a Route Update Message (RUM) is
processed by a sector-carrier. A hard handoff in 1xEV-DO is similar in concept to a hard
handoff in other technologies. The handoff decisions are made by the AN as it inspects
each RUM for potential handoff triggers. The actual handoff is performed via a series of
messages exchanged between the AN and the AT. The handoff can fail for several reasons
as described in the hard handoff failure metrics.
............................................................................................................................................................................................................................................................
Idle handoffs:
For an AT in idle mode, there are two handoffs of interest. One is intra-RNC idle handoff,
which occurs, as the name suggests, between cells or sectors of the same RNC. In idle
mode, the AT has at most one pilot in its active set, which it uses to monitor the Control
Channel. Similar to the virtual soft handoff, the AT switches among pilots to maintain
reception on a dominant pilot. There is no communication with the AN needed for the AT
to perform an intra-RNC idle handoff. The AN is oblivious to these handoffs, and hence
there are no SM counts on it.
Another type of handoff is called inter-RNC idle handoff, also commonly known as inter-
subnet, inter-PCF handoff. When the AT crosses an RNC boundary, it first performs an
idle handoff to the cell on the new RNC just as in case of regular intra-RNC handoff.
However, what follows next sets it apart from regular idle handoff. As soon as the AT
decodes the first Control Channel message on the new RNC cell, it realizes the change in
color code (each RNC has a unique identifier called color code that it broadcasts on the
Control Channel). Per the 1xEV-DO standards, the AT is then required to register itself;
that is, request and acquire a new UATI for use on this RNC. A series of messages are
exchanged not only over the air, but also between the old and the new RNCs for proper
transfer of the PPP session (if one exists) and cleaning up the UATI session on the old
RNC. Any break in messaging (such as due to poor RF link, rapid ping-ponging between 2
or more RNCs, etc.) can lead to inter-RNC handoff failures.
Data Throughput Metrics/Data Transmission Metrics

A very basic and an important part of what defines a good user experience in any Data
network - wired or wireless - is the ability to receive data at acceptably high rates. This is
commonly measured in terms of Data rate or throughput.
While Data rate refers to the raw transmission speeds on a given link, throughput is the
effective received data speed after accounting for all errors and re-transmissions. These are
rather general definitions; the precise definition varies based on several factors, such as the
protocol layer measured, measurement tools used, whether protocol layer overheads are
included, effect of any type of compression performed, type of data used (loosely or
tightly packed), measurement interval used (count only while data in the buffer, or entire
length of a traffic connection even if the user is not expecting any data), etc.
As is evident, the measurements will vary based on the selection or assumption of these
underlying factors. Hence, what is more important is to come up with a set of rules or
metrics and then stick to it for a relative consistency in analysis over time. Below we
define such metrics that can be applied to visualize performance of a network in terms of
its ability to offer and serve data speeds to the user.
One way to utilize the information is to simply obtain a snapshot of network quality and
end-user experience. On the other hand, the information has a lot of value in providing
decision points for growing the network. For example, sector throughput/data rate is
............................................................................................................................................................................................................................................................
expected to increase (due to a phenomenon unique to the 1xEV-DO forward link, known
as scheduling gain) up to a certain point as the subscriber usage grows, and then saturate.
Any additional increase in usage will simply reduce the achieved individual user
throughputs/data rate; it will not improve the total throughput delivered by the sector any
further. This behavior can be explored with other metrics, such as average active
connections, scheduler eligible users, and reverse link noise rise for capacity forecasting.
Note that depending on the link and the layer for which a specific metric is computed, it
may not be possible to obtain data rate and throughput both. For example, on the forward
link, one can only compute data rate for the MAC layer; currently there is no provision to
capture MAC layer errors and hence it is difficult to estimate the user perceived
throughput.
For the forward link RLP layer, it is possible to compute only a partial view of throughput
in the sense that the cell site has no way of knowing any loss of RLP data at the AT after
exhausting the RLP retry. Such caveats are noted with each metric listed below. Refer to
Figure 1-1, RLP and MAC protocol layers (p. 1-11) for an illustration on where the RLP
and MAC layers reside in the network protocol stack.
Figure 1-1 RLP and MAC protocol layers
Error Statistics
The Error Statistic metric is comprised of the 1xEV-DO Reverse Frame Error Rate - EVM
metric which represents the total number of active traffic channel links on a given sector.
This metric was moved from the Data Throughput section into the Error Statistic section
in R25.
............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1- 1 1
Power Control
The Power Control section contains metrics to calculate the average reverse link power
control setpoint for each data rate. These metrics are useful to determine whether the
minimum and maximum thresholds are correctly set.
If the average setpoint falls within the middle of the range then it validates the power
control algorithm and verifies the threshold settings.
If, however, the average setpoint is near the maximum threshold, it may be a good
indication that there is either strong external reverse link interference or that the base
station receive diversity is not working (or possibly some other hardware issue). In this
case the service provider should consider raising the maximum threshold.
If the average is near the minimum, then possibly the range can be reduced, i.e., decrease
the maximum setting, which results in higher reverse link capacity.
However, since the calculated values are an average, a higher maximum may still be
needed to counter short term fading and to meet the desired RFER.
In R27, metrics were created for sector-carriers equipped with an SBEVM. The pre-
existing metrics are valid for sector-carriers equipped with an EVM and the counts will be
zero for sector-carriers equipped with an SBEVM.
Capacity Management Metrics

The Capacity Management metrics provide capacity management information.
Quality of Service
Quality of Service (QoS) refers to the capability of providing preferred treatment to
certain applications or users. A Reservation must be opened for an IP flow that has been
negotiated between the AT and theAN. Each reservation is associated with a Profile ID
that defines a set of attributes supporting certain QoS characteristics. A reservation must
be configured before it can be opened. Configured reservationsare represented as
reservation labels.
To open one or more reservations, a ReservationOnRequest (RoR) is needed. An RoR may
include one or more reservation label(s) that have been negotiated between the AT and
AN. An RoR may be combined with a Connection Request if a connection hasnt been
established.
A user can have separate application flows with separate QoS requirements for delay, jitter
or bandwidth.
............................................................................................................................................................................................................................................................
Metrics Added Due to SM Re-Architecture

The re-architecture of Service Measurement collection on the RNC begins in R31. One of
the ramifications of the rearchitecture removes peg counts that are averages that are
distributed between RNCs. In order to be able to distribute the counts across RNCs, the
calculated counts have been separated into 2 counts in R31, representing the numerator
and denominator of the old count.
This section contains formulas to enable users to calculate the quotient of the new counts,
thereby providing a value equal to the
............................................................................................................................................................................................................................................................
Introduction Watchmark/IBM Prospect for Alcatel-Lucent
Watchmark/IBM Prospect for Alcatel-Lucent

............................................................................................................................................................................................................................................................
Overview
The purpose of the Primitive Calculations for Performance Metrics in Watchmark/IBM
Prospect chapters is to provide descriptions of obsolete, new and modified Prospect
Primitive Calculations (PCALCs) that support 1xEV-DO Performance Metrics defined for
each release.
Chapter 4, 1xEV-DO Metrics in Watchmark Prospect for Release 22 contains all
PCALCs defined for R22. Subsequent chapters contain only the PCALCs that have
changed since the previous release. If a PCALC change is ported back to a previous
release, the change is made in the corresponding chapter.
Besides the definition of the Prospect calculation, notes are provided to give a mapping
between the Prospect names and the 1xEV-DO names for each service measurement in the
calculation.
The Prospect names for these calculations with DO. Calculations beginning with
DOp_ are ratios or rates that are reported as percentages.
Note that in R27.0 the name Watchmark Prospect changed to IBM Prospect.
............................................................................................................................................................................................................................................................
Introduction Acronyms
Acronyms
............................................................................................................................................................................................................................................................
1xEV-DO 1X Evolution Data Optimized

A10-PCF PCF to PDSN Traffic Interface
A11-PCF PCF to PDSN Signaling Interface
AN Access Network
AP Applications Processor
AT Access Terminal
BCMCS Broadcast/Multicast Service
BE Best Effort
BSC Base Station Controller
BSN Broadcast Serving Node
BTS Base Transceiver Station
CDMA Code Division Multiple Access
CE Channel Element
CPS Conversational Push-to-Talk Speech
CS Conversational Speech
CV Conversational Video
DRC Data Rate Control
ECPC Executive Cellular Processor Complex
EF Expedited Forwarding
ESN Equipment Serial Number
EVM 1xEV-DO Modem
FRPH Frame Relay Protocol Handler
FTC Forward Traffic Channel
HA Home Agent
HSPD High Speed Packet Data
IP Internet Protocol
............................................................................................................................................................................................................................................................
IUP Inter-User Priority
IWF Inter Working Function
FRBC Frame Relay Bearer Channel
L2TP Layer 2 Tunneling Protocol
LLC Link layer Connection
OHM Overhead Manager
PAF Physical Antenna Face
PCF Packet Control Function

PDSN Packet Data Serving Node
PMDATA Packet Mode DATA
PTT Push to Talk
QoS Quality of Service
RAN Radio Access Network
RATI Random Access Terminal Identifier
Rel 0 Initial issue of IS-856
Rev A Revision A to IS-856
RNC Radio Network Controller
RF Radio Frequency
RoR Reservation On Request
SBEVM Single Board 1xEV-DO Modem
SHLR Stand-alone Home Location Register
SM Service Measurements
SMC Signaling Media Control
SRD System Requirements Document
SVC Switched Virtual Circuit
TCA Traffic Channel Assignment
TCC Traffic Channel Confirmation
TCC Traffic Code Channel
TCCF Traffic Channel Confirmation Failure
TP Traffic Processor
............................................................................................................................................................................................................................................................
UATI Unicast Access Terminal Identifier
UDC User Defined Calculations
VLR Visitor Location Register
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
2 Customer Perspective
Overview
............................................................................................................................................................................................................................................................
Service providers are looking for ways to maximize their revenues and minimize
operational expense. The explosive growth in internet usage fuels service providers'
interest in providing cost effective wireless internet access via packet data infrastructure at
speeds comparable to the landline services. Operators with Alcatel-Lucent wireless
systems use the performance and capacity metrics to evaluate the system performance and
to engineer the services for the Flexent System.
............................................................................................................................................................................................................................................................
Customer Perspective 1xEV-DO Overview
1xEV-DO Overview
............................................................................................................................................................................................................................................................
Figure 2-1, 1xEV-DO Network System Block Diagram (p. 2-2) contains a block
diagram of the 1xEV-DO Network System as showing 1xEV-DO, 3G1x and shared
components. Figure 2-2, 1xEV-DO Cell/AP Architecture (p. 2-3) contains an
architecture diagram of the 1xEV-DO cell/AP configuration. One OMP supports one
Service Node. Note that a service node is a logical entity, not a physical one.
One Service Node supports up to six RNC frames. Each RNC supports up to eight APs,
each of which supports 2 TPs. Each cell is assigned to an Active Controlling AP and a
backup Controlling AP. Each AT is associated with a Controlling AP/TP pair which
handles the AT's connection anywhere in the RNC coverage during the entire session.
Service Measurements are collected at the AP, TP and sector-carrier levels.
Figure 2-1 1xEV-DO Network System Block Diagram
1xEV
Single-mode Radio Network DNS,
1xEV cell Controller DHCP
A12 AAA
R
1xEV o R-P
u 1xEV 1xEV
BTS (A10-A11)
t Controller PCF
(cell)
e OMP-FX
r
1xEV EMS
Flexent EMS
PDSN
1xEV
Dual-mode RCS/AP HLR
cell 3G-1X ECPC
SMS
Center
3G1x 5ESS DCS
BTS R-P
(cell) 3G-1X PCF (A10-A11)
1xEV 3G-1x Shared

Components Components Components
............................................................................................................................................................................................................................................................
Customer Perspective 1xEV-DO Overview
Figure 2-2 1xEV-DO Cell/AP Architecture
............................................................................................................................................................................................................................................................
Customer Perspective Service Measurements Data Files
Service Measurements Data Files

............................................................................................................................................................................................................................................................
The Service Measurements for a 1xEV-DO system consist of two types of files.
The first file consists of service measurement counts that are collected by each individual
cell and is named YYYYMMDDHHmm[timezone].HCSFMSxxx
where xxx = RNC number.
The second file consists of cell/sector service measurement counts that are collected by all
of the APs within the system and is named
YYYYMMDDHHmm[timezone].HDRFMSxxx
where xxx = RNC number.
Since different APs can collect traffic measurements from the same cell, an aggregation of
these counts from all of the APs on all RNCs is contained in one file and sent to the OMP.
The aggregated file is named with "AG_" prepended to the .hdrfms file. The RNC number
used in the file name is the lowest value RNC on the service node. Measurements are
collected hourly.
The files are stored in the /omp-data/logs/HDR/sm_summary_files directory on the OMP.
1xEV-DO service measurements are fully documented in 401-614-326, Flexent Wireless
Networks CDMA2000 1xEV-DO Service Measurements.
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter contains the new, modified, and deleted performance metrics for R22.
Categories and metrics

For an overview of each broad category see Performance Metrics (p. 1-2).
The following performance metrics are provided for R22:
Air Interface Performance Metrics

Session Management
Session Setup Success Rate
Percent Active Sessions Metric
Percent Dormant Sessions Metric
Call Setup
Established Call Rate
Fast Connection Rate
AN-Initiated Connection Blocking Rate (due to resource blocking)
AT-Initiated Connection Blocking Rate (due to resource blocking)
AN-Initiated Ineffective Call Attempt Rate
AT-Initiated Ineffective Call Attempt Rate
Total Ineffective Call Attempt Rate
AN-Initiated RF Failure Rate
AT-Initiated RF Failure Rate
n Connection Attempt Failure Percentage due to Reverse Link not Acquired
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Overview
n Connection Attempt Failure Percentage due to Negotiation Failure

n Connection Attempt Failure Percentage due to No Resources Available
n Connection Attempt Failure Percentage due to No Response to Traffic Channel Assignment
n Connection Attempt Failure Percentage due to Other Failures
Call Drop
Dropped Call Rate
Data Throughput
Forward Link Data Re-transmission Rate
Reverse Link Data Re-transmission Rate
Reverse Link Re-transmission Failure Rate
Total Forward Link Data Transmitted (MB)
Average Forward Link Burst Rate
Percent Forward Link Bandwidth used for Traffic
Average Reverse Link Throughput
Average Reverse Link Burst Rate
Reverse Frame Error Rate
Handoff
Soft/Softer Handoff Success Rate
Inter-Subnet Idle Transfer Success Rate
Soft/Softer Handoff Blocking Rate due to No Resources
Capacity Management Performance Metrics

Traffic Channel Usage (in Erlangs)

PCF Reactivation Rate for AN-Initiations
PCF Reactivation Rate for AT-Initiations
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Session Management Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Session Setup Success Rate

This metric gives the percentage of successful session setups. The peg counts are defined
on a per sector-carrier basis. The session setup occurs before the RF air interface in which
a traffic channel is assigned.
Formula
SESS_SETUP_UATI_COMPLETE_MSG_RCVD
DO Session Setup Success Rate (%) = -----------------------------------------------------X 100
SESSION_SETUP_REQ
Count Definitions
SESSION_SETUP_REQ= 1xEV Session Set Up Request
= Session Set Up - UATI Complete Message Received
1xEV-DO Percent Active Sessions Metric

This metric provides a snapshot of the percentage of active sessions relative to the total
number of sessions at the end of the hour. The peg counts are defined on a per TP basis.
As of Release 23 this metric is no longer applicable.
Formula
ACTIVE_AT_COUNT
DO % Active sessions = ----------------------------------------------------- X 100
TOTAL_ALLOCATED_SESS_TP
Count Definitions
ACTIVE_AT_COUNT = Number of AT active sessions that are being served by

this TP at the end of the hour
TOTAL_ALLOCATED_SESS_TP= Total Number of AT sessions that are being served

by this TP at the end of the hour
............................................................................................................................................................................................................................................................
1xEV-DO Percent Dormant Sessions Metric

This metric provides a snapshot of the percentage of dormant sessions relative to the total
number of sessions at the end of the hour. The peg counts are defined on a per TP basis.
As of Release 23 this metric is no longer applicable.
Formula
TOTAL_ALLOCATED_SESS_TP -
ACTIVE_AT_COUNT
DO % Dormant Sessions = ----------------------------------------------------------- X 100
TOTAL_ALLOCATED_SESS_TP
Count Definitions
ACTIVE_AT_COUNT = Number of AT active sessions that are being served by

this TP at the end of the hour
TOTAL_ALLOCATED_SESS_TP = Total Number of AT sessions that are being served

by this TP at the end of the hour
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Call Setup Metrics
Call Setup Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Established Call Rate

This metric gives the percentage of successful connections relative to connection requests.
It is somewhat equivalent to the established calls = assignments - failures metric for
3G1X. The peg counts are defined on a per sector-carrier basis and can be rolled up to the
cell level. This metric was revised in R24 to remove negotiation failures. The new
formula is applicable to all prior releases.
Formula
(AN_INIT_CONN_REQ + AT_INIT_CONN_REQ -
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ -
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ -
AN_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA -
AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA -
AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES -
AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES -
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL -
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL)
DO Established call rate (%) = ------------------------------------------------------------X 100
(AN_INIT_CONN_REQ + AT_INIT_CONN_REQ)
Count Definitions
AN_INIT_CONN_REQ = AN-Initiated connection requests
AT_INIT_CONN_REQ = AT-Initiated connection requests
AN_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA
= AN-initiated Connection attempt failures - no response to traffic channel
assignment
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
= AN-initiated Connection attempt failures - rev link not acquired
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
= AN-initiated connection attempt failures - no resources available
AN_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES
= AN-initiated Connection attempt failures - other failures
............................................................................................................................................................................................................................................................
AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA
= AT-initiated Connection attempt failures - no response to traffic channel
assignment
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
= AT-initiated Connection attempt failures - rev link not acquired
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
= AT-initiated connection attempt failures - no resources available
AT_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES
= AT-initiated Connection attempt failures - other failures
1xEV-DO Fast Connect Success Rate

This metric gives the percentage of successful fast connections relative to fast connection
requests. The fast connect procedure re-establishes a traffic channel to a dormant AT
when the Suspend Timer is still running, i.e., before the AT goes into the Sleep mode.
This call setup procedure takes less time and uses less system resources than the standard
connect procedure. The peg counts are defined on a per AP basis and can be rolled up to
the RNC or SN level.
Formula
(FAST_CONNECT -
FAST_CONNECT_FAIL_NO_RSP_TO_TCA)
DO Fast connect success rate (%) = ------------------------------------------------------X 100
(FAST_CONNECT)
Count Definitions
FAST_CONNECT = Number of fast connection requests
FAST_CONNECT_FAIL_NO_RSP_TO_TCA = Number of fast connection failures
............................................................................................................................................................................................................................................................
1xEV-DO AN-Initiated Connection Blocking Ratio (due to resource blocking)

This metric gives the percentage blocking for AN-initiated sessions. It is equivalent to the
Seizure to Assignment Deficit Ratio in 3G 1x. The peg counts are defined on a per sector-
carrier basis.
Formula
AN_INIT_CONN_REQ -
TCA_FOR_AN_INIT_CONN_REQ
Connection Blocking Ratio (%) = --------------------------------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
AN_INIT_CONN_REQ = AN-Initiated Connection Requests
TCA_FOR_AN_INIT_CONN_REQ = Traffic Channel Assignments for AN
Initiated Connection Requests
1xEV-DO AT-Initiated Connection Blocking Ratio (due to resource blocking)

This metric gives the percentage blocking for AT-initiated sessions. It is equivalent to the
carrier basis.
Formula
AT_INIT_CONN_REQ -
TCA_FOR_AT_INIT_CONN_REQ
Connection Blocking Ratio (%) = ---------------------------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
AT_INIT_CONN_REQ= AT Initiated Connection Requests
TCA_FOR_AT_INIT_CONN_REQ= Traffic Channel Assignments for AT

............................................................................................................................................................................................................................................................
1xEV-DO AN-Initiated Ineffective Call Attempt Rate

This metric provides the percentage of AN-initiated connection attempts that failed. The
peg counts are defined on a per sector-carrier basis. Note that the AN-Initiated call
success rate is 100 minus this metric. This metric was revised in R24 to remove
negotiation failures. The new formula is applicable to all prior releases.
Formula
(AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL +
AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA +
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ +
AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES)
DO AN-Initiated Ineffective Call Rate (%) = -------------------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
= AN initiated connection attempt failures - maximum connections exceeded
= AN initiated Connection attempt failures - no response to traffic channel
assignment
= AN initiated Connection attempt failures - rev link not acquired
= AN initiated Connection attempt failures - other failures
AN_INIT_CONN_REQ
= 1xEV AN Initiated Connection Requests
1xEV-DO AT-Initiated Ineffective Call Attempt Rate

This metric provides the percentage of AT-initiated connection attempts that failed. The
peg counts are defined on a per sector-carrier basis. Note that the AT-Initiated call success
rate is 100 minus this metric. This metric was revised in R24 to remove negotiation
failures. The new formula is applicable to all prior releases.
............................................................................................................................................................................................................................................................
Formula
(AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL +
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ +
AT_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES)
DO AT-Initiated Ineffective Call Rate (%) = ---------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
= AT initiated connection attempt failures - maximum connections exceeded
= AT initiated Connection attempt failures - no response to traffic channel
assignment
= AT initiated Connection attempt failures - rev link not acquired
= AT initiated Connection attempt failures - other failures
AT_INIT_CONN_REQ
= 1xEV AT Initiated Connection Requests
............................................................................................................................................................................................................................................................
1xEV-DO Total Ineffective Call Attempt Rate

This metric provides the percentage of connection attempts (both AN-initiated and AT-
initiated) that failed. The peg counts are defined on a per sector-carrier basis. Note that
the total call success rate is 100 minus this metric. This metric was revised in R24 to
remove negotiation failures. The new formula is applicable to all prior releases.
Formula
AN_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA +
AN_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES +
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL +
DO Total Ineffective Call Rate (%) = ------------------------------------------------------ X 100
Count Definitions
= AT initiated connection attempt failures - maximum connections exceeded
assignment
AT_INIT_CONN_REQ = 1xEV AT Initiated Connection Requests
= AN initiated connection attempt failures - maximum connections exceeded
assignment
............................................................................................................................................................................................................................................................
AN_INIT_CONN_REQ = 1xEV AN Initiated Connection Requests
1xEV-DO AN-Initiated RF Failure Rate

This metric provides the percentage of AN-initiated connection attempts that failed for RF
air interface reasons relative to the number of traffic channels assigned to AN-initiated
requests. The peg counts are defined on a per sector-carrier basis.
Formula
(AN_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA +
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ)
DO AN-Initiated RF failure rate (%) = ---------------------------------------------------- X 100
Count Definitions
assignment
= AN initiated Connection attempt failures - reverse link not acquired
= 1xEV Traffic Channel Assignments for AN Initiated
1xEV-DO AT-Initiated RF Failure Rate

This metric provides the percentage of AT-initiated connection attempts that failed for RF
air interface reasons relative to the number of traffic channels assigned to AT-initiated
Formula
(AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA +
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ)
DO AT-Initiated RF failure rate (%) = ---------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
assignment
= 1xEV Traffic Channel Assignments for AT Initiated Connection
Requests
1xEV-DO Connection Attempt Failure Percentage due to Reverse Link Not Acquired
This metric gives the percentage of failed connections that are due to the reverse link not
being acquired. The peg counts are defined on a per sector-carrier basis and can be rolled
up to the cell level. This metric was revised in R24 to remove negotiation failures. The
new formula is applicable to all prior releases.
Formula
(AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ +
DO Conn Attempt Fail % - RL Not Acquired = -------------------------------------------X 100
AT_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES +
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL +
Count Definitions
= AT initiated connection attempt failures - maximum connections
exceeded
assignment
............................................................................................................................................................................................................................................................
= AN initiated connection attempt failures - maximum connections
exceeded
assignment
1xEV-DO Connection Attempt Failure Percentage due to Negotiation Failure

This metric gives percentage of failed connections that are due to the failure to negotiate a
traffic channel. The peg counts are defined on a per sector-carrier basis and can be rolled
up to the cell level.
Formula
(AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED +
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED)
DO Conn Attempt Fail % - Negotiation Fail = ------------------------------------------- X 100
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED +
+ AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL)
............................................................................................................................................................................................................................................................
Count Definitions
exceeded
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AT initiated Connection attempt failures - negotiation fail
assignment
exceeded
AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AN initiated Connection attempt failures - negotiation fail
assignment
1xEV-DO Connection Attempt Failure Percentage due to No Resources Available

This metric gives percentage of failed connections that are due to no resources being
available. The peg counts are defined on a per sector-carrier basis and can be rolled up to
the cell level. This metric was revised in R24 to remove negotiation failures. The new
............................................................................................................................................................................................................................................................
Formula
DO Conn Attempt Fail % - No Resources = ---------------------------------------------- X 100
Count Definitions
exceeded
assignment
exceeded
assignment
............................................................................................................................................................................................................................................................
1xEV-DO Connection Attempt Failure Percentage due to No Response to Traffic Channel

Assignment
This metric gives percentage of failed connections that are due to no response to a traffic
channel assignment. The peg counts are defined on a per sector-carrier basis and can be
rolled up to the cell level. This metric was revised in R24 to remove negotiation failures.
The new formula is applicable to all prior releases.
Formula
(AN_INIT_CONN_ATTMPT_NORSP_TO_TCA +
AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA)
Count Definitions
exceeded
assignment
exceeded
assignment
............................................................................................................................................................................................................................................................
1xEV-DO Connection Attempt Failure Percentage due to Other Failures

This metric gives percentage of failed connections that are due to failures not included in
other failure counts. The peg counts are defined on a per sector-carrier basis and can be
Formula
(AN_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES +
DO Conn Attempt Fail % - Other = ---------------------------------------------------- X 100
Count Definitions
exceeded
assignment
............................................................................................................................................................................................................................................................
exceeded
assignment
AN_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES AN initiated Connection

attempt failures - other failures
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Call Drop Metrics
Call Drop Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Dropped Call Rate

This metric provides the percentage of dropped calls relative to established calls. The peg
counts are defined on a per sector-carrier basis. This metric was revised in R24 to remove
negotiation failures (which do not result in a dropped call) and to add soft/softer handoff
failures due to no AT response (which causes the connection to close). The new formula is
applicable to all prior releases.
Formula
CONN_REL_RLL + CONN_REL_OTHER_REASON +
SO_SOR_HOFF_FAIL_NO_AT_RSP)
DO Dropped call rate (%) = --------------------------------------------------------------- X 100
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD -
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD -
Count Definitions
CONN_REL_RLL = Connection Release - RF Link Lost
CONN_REL_OTHER_REASON = Connection Release - Other Reasons
= AN-initiated Connection attempt failures - no response to traffic channel
assignment
= AN-initiated Connection attempt failures - rev link not acquired
= AN-initiated connection attempt failures - no resources available
............................................................................................................................................................................................................................................................
= AT-initiated Connection attempt failures - no response to traffic channel
assignment
= AT-initiated Connection attempt failures - rev link not acquired
= AT-initiated connection attempt failures - no resources available
SO_SOR_HOFF_FAIL_NO_AT_RSP
= Soft-Softer HO Attempt failure due to no response from the AT
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Data Throughput Metrics
Data Throughput Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Data Re-transmission rate

This metric provides a measure of the effectiveness of data transmission on the forward
link. The higher the re-transmission rate, the poorer is the RF performance for the forward
link. This metric is defined on a per sector-carrier basis. This metric can be used for RF
optimization.
Formula
RLP_RETXED_FTC
DO forward retransmission rate (%) = ------------------------------------- X 100
RLP_TXED_FTC
Count Definitions
RLP_RETXED_FTC = RLP Octets re-transmitted on forward link
RLP_TXED_FTC = RLP Octets transmitted on forward link
1xEV-DO Reverse Link Data Re-transmission rate

This metric provides a measure of the effectiveness of data transmission on the reverse
link. the higher the re-transmission rate, the poorer is the RF performance for the reverse
link. This metric is defined on a per sector-carrier basis. This metric can be used for RF
optimization.
Formula
MISSING_RLP_REQ_RTC
DO reverse retransmission rate (%) = ------------------------------------------ X 100
RLP_RXED_RTC
Count definitions
MISSING_RLP_REQ_RTC = missing RLP octets requested for reverse link.
RLP_RXED_RTC = RLP Octets received on reverse link
1xEV-DO Reverse Link Re-transmission Failure Rate

link. The lower the re-transmission failure rate, the better is the RF performance for the
reverse link. This metric is defined on a per sector-carrier basis. This metric can be used
for RF optimization.
............................................................................................................................................................................................................................................................
Formula
MISSING_RLP_NEVER_RXED_RTC
DO reverse retransmission failure rate (%) = ------------------------------------------- X 100
` MISSING_RLP_REQ_RTC
Count definitions
MISSING_RLP_NEVER_RXED_RTC =missing RLP octets never received on the
reverse link.
MISSING_RLP_REQ_RTC RLP = Octets for retransmission on the reverse link
1xEV-DO Total Forward Link MAC Data Transmitted (MB)

This metric gives the average data volume on the forward link in megabytes. The metric is
defined on a per sector-carrier basis. The peg counts are measured in the modem at the
MAC layer. The formula is changed in R24 to account for the peg counts being MAC
layer packets. The new formula is applicable to all previous releases.
Formula
1024 * (EVM_FWD_PACKETS_38_4_TOTAL_COUNT +
EVM_FWD_PACKETS_76_8_TOTAL_COUNT +
EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT +
EVM_FWD_PACKETS_2457_6_TOTAL_COUNT)
DO Forward link MAC data xmitted (MB) =-----------------------------------------------------
8 * 10 ^ 6
Count definitions
EVM_FWD_PACKETS_38_4_TOTAL_COUNT
= Total MAC packets transmitted on forward traffic channels at 38.4 kbps
(1024 bits/packet)
EVM_FWD_PACKETS_76_8_TOTAL_COUNT= Total MAC packets transmitted on

forward traffic channels at 76.8 kbps (1024 bits/packet)
............................................................................................................................................................................................................................................................



EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT= Total MAC packets transmitted

on forward traffic channels at 307.2 kbps - long format (2048 1024
bits/packet)

on forward traffic channels at 614.4 kbps - long format (1024 bits/packet)

EVM_FWD_PACKETS_921_6_TOTAL_COUNT= Total MACpackets transmitted on

forward traffic channels 921.6 kbps (1024 bits/packet)



1xEV-DO Average Forward Link MAC Data Rate (kbps)

This metric gives the average transmission data rate on the forward link in kilobits per
second. The metric is defined on a per sector-carrier basis and is defined only for the one-
hour measurement interval. It cannot be directly summed to obtain results for longer time
periods. The individual counts must be rolled up and then the data rate can be calculated.
The peg counts are measured in the modem at the MAC layer. The metric is calculated as
forward link data volume transmitted divided by the time used to send the traffic data
packets. Note that there are 2,160,000 physical layer slots in one hour (3600 seconds
divided by the length of each slot, which in 1xEV-DO is 1.66 milliseconds). The formula
is changed in R24 to account for the peg counts being MAC layer packets. The new
formula is applicable to all previous releases.
............................................................................................................................................................................................................................................................
Formula
EVM_FWD_PACKETS_2457_6_TOTAL_COUNT) / 1000
DO Forward link MAC data rate (kb/s)= ---------------------------------------------------------
((EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 8) *2,160,000 * 0.001667)
Count definitions






on forward traffic channels at 307.2 kbps - long format (1024bits/packet)



............................................................................................................................................................................................................................................................



EVM_TOTAL_BUSY_PCNT_SLOTS= Percentage of physical layer slots in the

measurement hour used for forward link traffic data transmission (divide
by 10^6 to get percentage)
1xEV-DO Percent Forward Link Bandwidth Used for Traffic

This metric gives the percentage of total physical layer slots used for the forward link
transmission of traffic data. The metric is defined on a per sector-carrier basis. The peg
count is measured in the modem at the physical layer (slots are only defined at the physical
layer). The formula is changed in R24 to use the percent busy slots peg count and is
applicable to previous releases beginning with R22. Note that the peg count measures
only those slots used for actual traffic transmission so the control slot counts do not have
to be subtracted.
Formula
DO % Fwd link BW for Traffic = (EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 6)
Count definitions
EVM_TOTAL_BUSY_PCNT_SLOTS = Percentage of physical layer slots in the

1xEV-DO Average RLP Forward Link Data Rate (kbps)

This metric gives the average throughput on the forward link at the RLP layer in kilobits
per second.
The metric is defined on a per sector-carier basis and is defined only for the one hour
measurement interval. It cannot be directly summed to obtain results for longer time
The peg counts are measured at the RLP layer.
This metric provides a measure of the 'user experience' in terms of average data rate
throughput for the measurement hour. The RLP byte count is closer to the actual user
traffic with less overhead than either MAC layer or physical layer packet counts, which
can be padded with dummy bits to fill the packet.
............................................................................................................................................................................................................................................................
Note that there are 2,160,000 slots in one hour (3600 seconds divided by the length of each
slot, which in 1xEV-DO is 1.66 milliseconds).
There are several caveats regarding the use of this metric. It does not capture a very small
amount of throughput loss due to some of the re-transmitted RLP packets not reaching the
end user (typically ~0.02% for a 1% re-transmission rate). Another small throughput loss
not captured is due to virtual soft handoff on the Forward Link where the RLP packets
already sent to the cell are flushed from the buffer when they are sent to the 'new' cell.
Additionally, the user of this metric should monitor the MODEM_ELAPSED_TIME peg
count, which indicates the time in seconds during the measurement hour since the last
modem reboot. This count will be about 3600 if there has been no modem reboot. If the
count is not about 3600, the metric value will be erroneous for that hour. That is because
the RLP octets will be counted for the entire hour but the denominator indicating the time
used to send data will only reflect the slots since the last modem reboot. If this happens,
the calculated value of RLP data rate for that hour should be ignored.
This metric is new in R24 but can be used for all previous releases.
Formula
(RLP_TXED_FTC * 8) / 1000
DO RLP Forward Link Data Rate (kbps) = -----------------------------------------------------
((EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 8) * 2,160,000 * 0.001667)
Count Definitions
RLP_TXED_FTC= Number of RLP octets transmitted on the forward link
EVM_TOTAL_BUSY_PCNT_SLOTS= Percentage of busy slots used for traffic data

transmission (divide by 10^6 to get percentage)
1xEV-DO Average Forward Link Data Volume per User (MB)

This metric gives the average data volume per user on the forward link at the RLP layer in
megabytes. The metric is defined on a per sector-carrier basis. The peg counts are
measured at the RLP layer. This metric provides a measure of the data volume sent in the
forward direction per active connection. The RLP byte count represents actual user traffic
with less overhead than either MAC layer or physical layer packet counts, which can be
padded with dummy bits to fill the packet. Although the peg count name in the
denominator is "Average Active Connections" it is actually the sum of all the total
connections based on a 10 second scan. Note that if the count is read from IBM Prospect
for Alcatel-Lucent it has already been divided by 360 and should not be divided again.
This metric is new in R24 and is applicable to all previous releases.
............................................................................................................................................................................................................................................................
Formula
(RLP_TXED_FTC) / 10 ^ 6
DO RLP Fwd Link Data Vol per user (MB) = ---------------------------------------------------
AVG_ACTIVE_CONN_PER_SECTOR / 360
Count Definitions
RLP_TXED_FTC= Number of RLP octets transmitted on the forward link
AVG_ACTIVE_CONN_PER_SECTOR= Number of active connections
1xEV-DO Average Reverse Link Throughput (MB)

This metric gives the average throughput on the reverse link in megabytes. The metric is
defined on a per sector-carrier basis.
Formula
(256 * REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
512 * REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS +
4096 * REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS)
DO Reverse link throughput (MB) = ---------------------------------------------------------------
8 * 10^6
Count Definitions
REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS
= Number of 9.6 kbps reverse link frames
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Burst Rate (kbps)

This metric gives the average burst rate on the reverse link in kilobits per second. The
metric is defined on a per sector-carrier basis.
Formula
(9.6 * REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
19.2 * REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS +
153.6 * REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS)
DO Reverse link burst rate (kb/s) = -----------------------------------------------------------------
(REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS +
REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS)
Count Definitions
1xEV-DO Reverse Frame Error Rate

This metric gives the percentage of reverse link frames received in error. The peg counts
are defined on a per sector-carrier basis and can be rolled up to the cell level.
Formula
REVERSE_FRAME_ERROR_COUNT
DO Reverse Frame Error Rate (%) = ------------------------------------------------------ X 100
TOTAL_REVERSE_FRAME_COUNT
............................................................................................................................................................................................................................................................
Count Definitions
REVERSE_FRAME_ERROR_COUNT = 1xEV Frames in Error on RTC
TOTAL_REVERSE_FRAME_COUNT = 1xEV Total Reverse Link Frames
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Handoff Metrics
Handoff Metrics
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Success Rate

This metric gives the success rate for soft/softer handoffs. The peg counts are defined on a
per sector-carrier basis.
Formula
SO_SOR_HOFF_ATTMPT -
(SO_SOR_HOFF_FAIL_NO_RESOURCE +
SO_SOR_HOFF_FAIL_NO_AT_RSP +
SO_SOR_HOFF_FAIL_OTHER_REASON)
DO Handoff success rate (%) = ------ ------------------------------------------------------ X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
SO_SOR_HOFF_ATTMPT = Soft-Softer HO Attempt
SO_SOR_HOFF_FAIL NO_RESOURCE
= Soft-Softer HO Attempt failure due to no resources
SO_SOR_HOFF_FAIL_OTHER_REASON
= Soft-Softer HO Attempt failure due to other reasons
1xEV-DO Inter-Subnet Idle Transfer Success Rate

This metric gives the success rate for Inter-subnet idle transfers. The peg counts are
Formula
INT_SUBNET_IDL_TRFR_ATTMPT -
(INT_SUBNET_IDL_TRFR_FAIL_NO_RSP_FROM_PREV_SUBNET +
INT_SUBNET_IDL_TRFR_FAIL_ORIG_PDSN_CANNOT_CONNECT +
INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON +
INT_SUBNET_IDL_TRFR_FAIL_SOURCE_AN_IP_ADDR_NOT_PROVISIONED +
INT_SUBNET_IDL_TRFR_FAIL_REJECT_MSG_RECEIVED)
DO Int sub idle xfer success rate (%) =-------------------------------------------------- X 100
INT_SUBNET_IDL_TRFR_ATTMPT
............................................................................................................................................................................................................................................................
Count Definitions
INT_SUBNET_IDL_TRFR_ATTMT
= Number of Inter Subnet Idle Transfer Attempts
INT_SUBNET_IDL_TRFR_FAIL_NO_RSP_FROM_PREV_SUBNET
= Number of Inter Subnet Idle transfer failures due to no response from the
previous subnet
INT_SUBNET_IDL_TRFR_FAIL_ORIG_PDSN_CANNOT_CONNECT
= Number of Inter Subnet Idle Transfer failures because an R-P connection
could not be established
INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON
= Number of Inter Subnet Idle transfer failures for reasons not specifically
pegged
INT_SUBNET_IDL_TRFR_FAIL_SOURCE_AN_IP_ADDR_NOT_PROVISIONED
= Number of Inter Subnet Idle transfer failures because the target AN could
not find a valid source AN IP address
INT_SUBNET_IDL_TRFR_FAIL_REJECT_MSG_RECEIVED
= Number of Inter Subnet Idle transfer failures due to an A13 Session
Information Reject message
1xEV-DO Soft/Softer Handoff Blocking Rate (due to no resources)

This metric gives the percentage blocking for soft/softer handoffs due to a lack of
resources. The peg counts are defined on a per sector-carrier basis and are pegged at the
target sector.
Formula
SO_SOR_HOFF_FAIL_NO_RESOURCE
DO HO Blocking Rate (%) = ------------------------------------------------------- X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
= 1xEV Soft-Softer HO Attempt Fail - No Resources
SO_SOR_HOFF_ATTMPT = 1xEV Soft-Softer HO Attempt
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Capacity Management Performance Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Traffic Channel Usage (in Erlangs)

This metric gives the minutes of Traffic Channel use in the measurement hour. The peg
counts are defined on a per sector-carrier basis and can be rolled up to the cell level.
Although the peg count name is "Average Active Connections" it is actually the sum of all
the total connections based on a 10 second scan. Note that if the count is read from IBM
Prospect for Alcatel-Lucent it has already been divided by 360 and should not be divided
again.
Formula
AVG_ACTIVE_CONN_PER_SECTOR
DO Traffic channel usage (erlangs) = ------------------------------------------------
360
Count Definitions
AVG_ACTIVE_CONN_PER_SECTOR = Number of active connections
............................................................................................................................................................................................................................................................
Performance Metrics for Release 22 Packet Data Reactivation Metrics

............................................................................................................................................................................................................................................................
1X-EV DO PCF Reactivation Rate for AN-Initiations

This metric gives the percentage of successful reactivations for dormant ATs. The peg
counts are defined on a per TP basis.
Formula
PCF_INIT_REACT_ATTMPT -
PCF_INIT_REACT_FAIL
DO PCF Reactivation rate AN Init (%) = ------------------------------------------------- X 100
PCF_INIT_REACT_ATTMPT
Count Definitions
PCF_INIT_REACT_ATTMPT = PCF initiated reactivation attempts
PCF_INIT_REACT_FAIL = PCF initiated reactivation failures
1X-EV DO PCF Reactivation Rate for AT-Initiations

This metric gives the percentage of successful reactivations originated by an AT. The peg
counts are defined on a per TP basis.
Formula
RP_CONN_ATTMPTS -
RP_CONN_FAIL
DO PCF reactivation rate AT-Initiations (%) = ------------------------------------------- X100
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS = RP Connection Attempts
RP_CONN_FAIL = RP Connection Failures
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
4 1xEV-DO Metrics in Watchmark
Prospect for Release 22
1xEV-DO Performance Metrics

............................................................................................................................................................................................................................................................
The purpose of this document is to provide definitions for new Prospect Primitive
Calculations (PCALCs) that support the performance metrics defined for FMS R22.
calculation.
A convention has been adopted to begin the Prospect names for these calculations with
DO. Calculations beginning with DOp_ are ratios or rates that are reported as
percentages.
The PCALCs defined herein are targeted to be implemented in Prospect in an R22 post-
GA patch.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Session Management Metrics

............................................................................................................................................................................................................................................................

DOp_SessSUSucc = 100.0 * SessnSUUATICompMsgRcvd / SessionSURq
Notes:
1. Mapping between Prospect names and DO names:
Prospect
Prospect Name DO Name Traffic Entity
SessionSURq SESSION_SETUP_REQ 1xEV_Sector
SessnSUUATICompNsgRcvd SESSION_SETUP_UATI_COMPLETE_MSG_RCVD
Percent Active Sessions Metric

DOp_ActSess = 100.0 * ATActiveSessions / TotAllocSessTP
Notes:
Prospect
ATActiveSessions ACTIVE_AT_COUNT 1xEV_TP
TotAllocSessTP TOTAL_ALLOCATED_SESS_TP

DOp_DormSess = 100.0 * (TotAllocSessTP ATActiveSessions) / TotAllocSessTP
Notes:
Prospect
ATActiveSessions ACTIVE_AT_COUNT 1xEV_TP
TotAllocSessTP TOTAL_ALLOCATED_SESS_TP
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Call Setup Metrics
Call Setup Metrics

............................................................................................................................................................................................................................................................

DOp_EstCall = 100.0 * (ATInitConRq + ANInitConRq - ATInitConAttFlNoResrc -
ATInitConAttFlNoRspTCA - ATInitConAttFlNoRL - ATInitConAttFlOther -
ANInitConAttFlNoResrc - ANInitConAttFlNoRspTCA - ANInitConAttFlNoRL -
ANInitConAttFlOther) / (ATInitConRq + ANInitConRq)
Notes:
Prospect
ATInitConAttFlNoResrc AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL 1xEV_Sector
ATInitConAttFlNoRspTCA AT_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA
ATInitConAttFlNoRL AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
ATInitConAttFlOther AT_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES
ANInitConAttFlNoResrc AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
ANInitConAttFlNoRspTCA AN_INIT_CONN_ATTMPT_FAIL_NORSP_TO_TCA
ANInitConAttFlNoRL AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ
ANInitConAttFlOther AN_INIT_CONN_ATTEMPT_FAILED_OTHER_FAILURES
ATInitConRq AT_INIT_CONN_REQ
ANInitConRq AN_INIT_CONN_REQ
Fast Connect Success Rate

Prospect Traffic Report Entity: AP
DOp_FastCnctSuc = 100.0 * (FastConnect FastConFlNoRspTCA) / FastConnect
Notes:
Prospect
FastConnect FAST_CONNECT AP
FastConFlNoRspTCA FAST_CONNECT_FAIL_NO_RSP_TP_TCA
............................................................................................................................................................................................................................................................
AN-Initiated Connection Blocking Rate

DOp_CnctBlkANInit = 100.0 * (ANInitConRq TCAANInitConRq) / ANInitConRq
Notes:
Prospect
ANInitConRq AN_INIT_CONN_REQ 1xEV_Sector
TCAANInitConRq TCA_FOR_AN_INIT_CONN_REQ
AT-Initiated Connection BlockingRate

DOp_CnctBlkATInit = 100.0 * (ATInitConRq TCAATInitConRq) / ATInitConRq
Notes:
Prospect
ATInitConRq AT_INIT_CONN_REQ 1xEV_Sector
TCAATInitConRq TCA_FOR_AT_INIT_CONN_REQ

DOp_InefCallAttANInit = 100.0 * (ANInitConAttFlNoResrc +
ANInitConAttFlCnfgNegFl + ANInitConAttFlNoRspTCA + ANInitConAttFlNoRL +
ANInitConAttFlOther) / ANInitConRq
Notes:
Prospect
............................................................................................................................................................................................................................................................
ANInitConAttFlCnfgNegFl AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED

DOp_InefCallAttATInit = 100.0 * (ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl
+ ATInitConAttFlNoRspTCA + ATInitConAttFlNoRL + ATInitConAttFlOther) /
ATInitConRq
Notes:
Prospect
Traffic
Prospect Name DO Name Entity
ATInitConAttFlNoResrc AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL
ATInitConAttFlCnfgNegFl AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
............................................................................................................................................................................................................................................................

DOp_InefCallAttTotal = 100.0 * (ANInitConAttFlNoResrc +
ANInitConAttFlNoRspTCA + ANInitConAttFlNoRL + ANInitConAttFlOther +
ATInitConAttFlNoResrc + ATInitConAttFlNoRspTCA + ATInitConAttFlNoRL +
ATInitConAttFlOther) / (ANInitConRq + ATInitConRq)
Notes:
Prospect

DOp_RFailANInit = 100.0 * (ANInitConAttFlNoRspTCA + ANInitConAttFlNoRL) /
TCAANInitConRq
Notes:
Prospect
TCAANInitConRq TCA_FOR_AN_INIT_CONN_REQ 1xEV_Sector
............................................................................................................................................................................................................................................................

DOp_RFFailATInit = 100.0 * (ATInitConAttFlNoRspTCA + ATInitConAttFlNoRL) /
TCAATInitConRq
Notes:
Prospect
TCAATInitConRq TCA_FOR_AT_INIT_CONN_REQ 1xEV_Sector
% Connection Attempt Failures Due to Reverse Link Not Acquired

DOp_CnctFlNoRL = 100.0 * (ATInitConAttFlNoRL + ANInitConAttFlNoRL) /
(ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl + ATInitConAttFlNoRspTCA +
ATInitConAttFlNoRL + ATInitConAttFlOther + ANInitConAttFlNoResrc +
ANInitConAttFlOther)
Notes:
Prospect
ATInitConAttFlNoResrc AT_INIT_CONN_ATTMPT_FAIL_NO_RES_ 1xEV_Sector
AVLBL
............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to Negotiation Failure

DOp_CnctFlCnfgNeg = 100.0 * (ATInitConAttFlCnfgNegFl +
ANInitConAttFlCnfgNegFl) / (ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl +
ATInitConAttFlNoRspTCA + ATInitConAttFlNoRL + ATInitConAttFlOther +
ANInitConAttFlNoResrc + ANInitConAttFlCnfgNegFl + ANInitConAttFlNoRspTCA +
ANInitConAttFlNoRL + ANInitConAttFlOther)
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to No Resources Available

DOp_CnctFlNoResrc = 100.0 * (ATInitConAttFlNoResrc + ANInitConAttFlNoResrc) /
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to No Response to Traffic Channel Assignment

DOp_CnctFlNoRspTCA = 100.0 * (ATInitConAttFlNoRspTCA +
ANInitConAttFlNoRspTCA) / (ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl +
ATInitConAttFlNoRspTCA + ATInitConAttFlNoRL + ATInitConAttFlOther +
ANInitConAttFlNoResrc + ANInitConAttFlCnfgNegFl + ANInitConAttFlNoRspTCA +
ANInitConAttFlNoRL + ANInitConAttFlOther)
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to Other Failures

DOp_CnctFlOther = 100.0 * (ATInitConAttFlOther + ANInitConAttFlOther) /
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Dropped Call Metrics
Dropped Call Metrics

............................................................................................................................................................................................................................................................

Valid Releases: RNC R22
Prospect Traffic Report Entity: 1xEV_Sector
DOp_DropCall = 100.0 * (ConRlsRLL + ConRlsOther + SftSftrHOFlNoATRsp) /
(ATInitConRq + ANInitConRq - ATInitConAttFlNoResrc - ATInitConAttFlNoRspTCA -
ATInitConAttFlNoRL - ATInitConAttFlOther - ANInitConAttFlNoResrc -
ANInitConAttFlNoRspTCA - ANInitConAttFlNoRL - ANInitConAttFlOther)
Notes:
Prospect
Traffic
ConRlsRLL CONN_REL_RLL 1xEV_Sector
ConRlsOther CONN_REL_OTHER_REASON
SftSftrHOFlNoATRsp SO_SOR_HOFF_FAIL_NO_AT_RSP
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Data Throughput Metrics

............................................................................................................................................................................................................................................................

DOp_ReTXFwdLnk = 100.0 * RLPRTXFTC / RLPTXFTC
Notes:
Prospect
RLPRTXFTC RLP_RETXED_FTC 1xEV_Sector
RLPTXFTC RLP_TXED_FTC

DOp_ReTXRevLnk = 100.0 * MissRLPRqRTC / RLPRXRTC
Notes:
Prospect
MissRLPRqRTC MISSING_RLP_REQ_RTC 1xEV_Sector
RLPRXRTC RLP_RXED_RTC
Reverse Link Retransmission Failure Rate

DOp_ReTXFailRevLnk = 100.0 * MissRLPNoRcvRTC / MissRLPRqRTC
Notes:
Prospect
MissRLPRqRTC MISSING_RLP_REQ_RTC 1xEV_Sector
MissRLPNoRcvRTC MISSING_RLP_NEVER_RXED_RTC
............................................................................................................................................................................................................................................................
1xEV-DO Total Data Transmitted on Forward Link

DO_TotDataXmtFwdLnk = (1024.0 * (FwdPkts38kbps + FwdPkts76kbps +
FwdPkts153kbps + FwdPkts307kbps + FwdPkts614kbps) + 2048.0 * (FwdPkts307Lkbps
+ FwdPkts614Lkbps + FwdPkts1228kbps) + 3072.0 * (FwdPkts921kbps +
FwdPkts1843kbps) + 4096.0 * (FwdPkts1228Lkbps + FwdPkts2457kbps)) / 8000000.0
Notes:
Prospect
Traffic
FwdPkts38kbps EVM_FWD_PACKETS_38_4_TOTAL_COUNT 1xEV_Sector
FwdPkts76kbps EVM_FWD_PACKETS_76_8_TOTAL_COUNT
FwdPkts307Lkbps EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT
FwdPkts2457kbps EVM_FWD_PACKETS_2457_6 _TOTAL_COUNT
............................................................................................................................................................................................................................................................
Average Forward Link Burst Rate (kbps)

DOp_AvgBrstFwdLnk = (38.4 * FwdPkts38kbps + 76.8 * FwdPkts76kbps + 153.6 *
FwdPkts153kbps + 307.2 * FwdPkts307kbps + 614.4 * FwdPkts614kbp + 2 * (307.2 *
FwdPkts307Lkbps + 614.4 * FwdPkts614Lkbps + 1228.8 * FwdPkts1228kbps) + 3 *
(921.6 * FwdPkts921kbps + 1843.2 * FwdPkts1843kbps) + 4 * (1228.8 *
FwdPkts1228Lkbps + 2457.6 * FwdPkts2457kbps)) / (FwdPkts38kbps + FwdPkts76kbps
+ FwdPkts153kbps + FwdPkts307kbps + FwdPkts614kbp + 2 * (FwdPkts307Lkbps +
FwdPkts614Lkbps + FwdPkts1228kbps) + 3 * (FwdPkts921kbps + FwdPkts1843kbps) +
4 * (FwdPkts1228Lkbps + FwdPkts2457kbps))
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
Percent Forward Link Bandwidth Used for Traffic

DOp_BndWidthTrfFwdLnk = 100.0 * (16 * FwdPkts38kbps + 8 * FwdPkts76kbps + 4 *
FwdPkts153kbps + 2 * FwdPkts307kbps + FwdPkts614kbp + 4 * FwdPkts307Lkbps + 2
* FwdPkts614Lkbps + FwdPkts1228kbps + 2 * FwdPkts921kbps + FwdPkts1843kbps +
2 * FwdPkts1228Lkbps + FwdPkts2457kbps) / (2160000.0 CntrChAsyncCapXmtSlot -
CntrChSyncCapXmtSlot)
Notes:
Prospect
CntrChAsyncCapXmtSlot EVM_CC_ASYNC_MAC_PACKET_XMIT
CntrChSyncCapXmtSlot EVM_CC_SYNC_MAC_PACKET_XMIT
............................................................................................................................................................................................................................................................
1xEV-DO Total Data Transmitted on Reverse Link

DO_TotDataXmtRevLnk = (256 * RevOutLoopPCFrCt96 + 512 *
RevOutLoopPCFrCt192 + 1024 * RevOutLoopPCFrCt384 + 2048 *
RevOutLoopPCFrCt768 + 4096 * RevOutLoopPCFrCt1536) / 8000000.0
Notes:
Prospect
RevOutLoopPCFrCt96 REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS 1xEV_Sector
RevOutLoopPCFrCt192 REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS
Average Reverse Link Burst Rate (kbps)

DO_AvgBrstRevLnk = (9.6 * RevOutLoopPCFrCt96 + 19.2* RevOutLoopPCFrCt192 +
38.4* RevOutLoopPCFrCt384 + 76.8* RevOutLoopPCFrCt768 + 153.6*
RevOutLoopPCFrCt1536) / (RevOutLoopPCFrCt96 + RevOutLoopPCFrCt192 +
RevOutLoopPCFrCt384 + RevOutLoopPCFrCt768 + RevOutLoopPCFrCt1536)
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_RevFER = 100.0 * IxEVRevFrameError / IxEVTotRevFrame
Notes:
Prospect
IxEVRevFrameError REVERSE_FRAME_ERROR_COUNT 1xEV_Sector
IxEVTotRevFrame TOTAL_REVERSE_FRAME_COUNT
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Handoff Metrics
Handoff Metrics
............................................................................................................................................................................................................................................................
Soft-Softer Handoff Blocking Rate

DOp_SftSftrHOBlk = 100.0 * SftSftrHOFlNoResc / SftSftrHOAtt
Notes:
Prospect
SftSftrHOFlNoResc SO_SOR_FAIL_NO_RESOURCE 1xEV_Sector
SftSftrHOAtt SO_SOR_HOFF_ATTMPT

DOp_SftSftrHOSuc = 100.0 * (SftSftrHOAtt (SftSftrHOFlNoResc +
SftSftrHOFlNoATRsp + SftSftrHOFlOther)) / SftSftrHOAtt
Notes:
Prospect
SftSftrHOFlOther SO_SOR_HOFF_FAIL_OTHER_REASON
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Handoff Metrics

DOp_IntSubIdlTrfSuc = 100.0 * (IntSubIdleTrfrAtt - (IntSubIdlTrfFl_NoRspPrev +
IntSubIdlTrfFl_OrigPDSNcntConn + IntSubIdlTrfFl_RejMsgRcv + IntSubIdlTrfFl_Other
+ IntSbIdlTrfrFl_SrcIpAd) / IntSubIdleTrfrAtt
Notes:
1. IntSbIdlTrfrFl_SrcIpAd is not defined until R22.
Prospect
Traffic
IntSubIdleTrfrAtt INT_SUBNET_IDL_TRFR_ATTMPT 1xEV_Sector
IntSubIdlTrfFl_NoRspPrev INT_SUBNET_IDL_TRFR_FAIL_NO_RSP_FROM_PREV_
SUBNET
IntSubIdlTrfFl_OrigPDSNcnt INT_SUBNET_IDL_TRFR_FAIL_ORIG_PDSN_CANNOT_
Conn CONNECT
IntSubIdlTrfFl_RejMsgRcv INT_SUBNET_IDL_TRFR_FAIL_REJECT_MSG_RECEIV
ED
IntSubIdlTrfFl_Other INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON
IntSbIdlTrfrFl_SrcIpAd INT_SUBNET_IDLE_TRFR_FAIL_SOURCE_IP_ADDR_N
OT_FOUND
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Capacity Management Metrics

............................................................................................................................................................................................................................................................

DO_TrfChnUsg_erl = AvgActCon
Notes:
Prospect Name DO Name Prospect Traffic Entity

AvgActCon AVG_ACTIVE_CONN_PER_SECTOR / 360 1xEV_Sector
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 22 Packet Data Reactivation Metrics

............................................................................................................................................................................................................................................................
1X-EV DO PCF Reactivation Success Rate for AN-Initiations

DOp_SucReactANInit = 100.0 * (PCFInitReactAtt PCFInitReactFl) / PCFInitReactAtt)
Notes:
PCFInitReactAtt PCF_INIT_REACT_ATTMPT 1xEV_TP
PCFInitReactFl PCF_INIT_REACT_FAIL
1X-EV DO PCF Reactivation Success Rate for AT-Initiations

DOp_SucReactOrig = 100.0 * (RPConAtt RPConFail) / RPConAtt
Notes:
Prospect
Name DO Name Prospect Traffic Entity
RPConAtt RP_CONN_ATTMPTS 1xEV_TP
RPConFail RP_CONN_FAIL
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

The following performance metrics are provided for R23:
Air Interface Performance Metrics

Session Management
Average Active Session Rate
Call Setup
n Connection Attempt Failure Percentage due to Negotiation Failure
............................................................................................................................................................................................................................................................

Call Drop
Dropped Call Rate
Data Throughput
Total Forward Link Data Transmitted (MB)
Average Forward Link Burst Rate
Average Reverse Link Physical Data Volume
Average Reverse Link Burst Rate
Handoff
Soft/Softer Handoff Blocking Rate due to No Resources


............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

a traffic channel is assigned.
Formula
DO Session Setup Success Rate (%) = -----------------------------------------------------X 100
SESSION_SETUP_REQ
Count Definitions
SESSION_SETUP_REQ = 1xEV Session Set Up Request
SESS_SETUP_UATI_COMPLETE_MSG_RCVD= Session Set Up - UATI Complete

Message Received
1xEV-DO Average Active Sessions Metric

Beginning with Release 23 this metric provides the average number of active sessions
during the measurement interval. It is defined on a per AP basis.
Formula
AVG_ACTIVE_CONN_PER_AP
DO Avg Active Sessions = ---------------------------------------------------
360
Count Definitions
AVG_ACTIVE_CONN_PER_AP =
Number of active sessions on an AP. This count is pegged every 10
seconds during the measurement interval and added to the previous total.
Therefore, the result is divided by 360 to get the approximate average over
the measurement interval. Note that the measurement interval is not
exactly one hour so the calculation is approximate.
............................................................................................................................................................................................................................................................
Call Setup Metrics

............................................................................................................................................................................................................................................................

3G1X.
Connection Request (CR) simply means an attempt to establish a connection received at
the AN from the AT. The AT may send Connection Request because the user wants to
transmit some data (AT Initiated CR), or in response to a network page (AN Initiated CR).
Note that the metric only captures failures occurring after the AN has received a AT/AN
Initiated CR. If the AN did not receive the CR, this event will likely impact the end-user
experience, but it would not influence the metric.
Note that the metric does not include Fast Connect attempts. In general, these are a small
number when compared to AN Initiated Connections, which in turn are relatively smaller
than the AT Initiated Connections.
There are various reasons that can cause connection failures - such as blocking at the AN,
internal errors allocating TCA, sub-optimal RF conditions between the AT/AN resulting in
missed messages between the AN/AT, etc.
In general, a connection is said to be established when the AN has received a Traffic
Channel Complete message from the AN. This is conceptually very similar to receiving a
Service Connect Complete Message from the mobile in a IS2000 system.
One point to note is that the connection attempt failure counts associated with
configuration negotiation are not included in this metric since this negotiation begins after
a connection has already been established; that is, the AN has already received a Traffic
Channel Complete (TCC) from the AT. However, the connections that are utilized for
Configuration Negotiations are included as there is no distinction made as to the purpose
for a Connection.
The peg counts are defined on a per sector-carrier basis and can be rolled up to the cell
level.
............................................................................................................................................................................................................................................................
Formula
DO Established call rate (%) = -------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
AN Initiated Connection Request is pegged when a connection request
message is received from the AT with the AN_initiated attribute set. Note
that it is possible that both ends (AT and AN) try to reactivate a dormant
connection at the same time (such as, when both sides have data to send
right after a dropped connection). In this case, when AN sends a page and
is awaiting a response, it receives a Connection Request with the
AT_initiated attribute set. In this case, AN will treat it as a AT Initiated
Connection Request.
AT_INIT_CONN_REQ =
AT Initiated Connection Request is pegged at the sector when it receives a
connection request message from the AT with the AT_initiated attribute set.
Note that it is possible that both ends (AT and AN) try to reactivate a
dormant connection at the same time (such as, when both sides have data to
send right after a dropped connection). In this case, when AN sends a page
and is awaiting a response, it receives a Connection Request with the
Connection Request.
All the failure counts below are pegged as AT or AN Initiated depending on whether the
corresponding Connection Request message was received with AT or AN Initiated
attribute set.
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD =
AN acknowledges the acquisition of AT's traffic channel preamble on the
reverse link by sending RTC_Ack message, following which it waits for
the Traffic Channel Complete (TCC) message from the AT. If TCC does
not arrive within a specific period, AN declares a connection attempt
failure and pegs this count on the Connection Request receiving sector. The
failure could be due to AT not receiving the RTC_Ack message or AN not
receiving the TCC.
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ =
After receiving TCA, AT transmits a preamble on the traffic channel to aid
its acquisition at the cell site. AN sends TCA multiple times while waiting
to acquire the preamble on the reverse link, but when it eventually times
out, it declares a connection attempt failure and pegs this count on the
Connection Request receiving sector. The failure could be either because
AT did not receive the TCA or the preamble did not make it to the AN.
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL =
The count is pegged on the Connection Request receiving sector when the
connection could not be setup because none of the cells on the Route
Update Message (RUM) had any resources to set up the traffic channel. By
no resource, it means the sector is already supporting
Max_number_of_connections, a per-sector translation limit. Essentially, it
is an indication of blocking on the sector. Note that if the strongest Pilot on
the RUM does not have resources, but other Pilots have, then it is possible
to allocate traffic channel on the rest and exclude the strongest sector from
the TCA. In this case, this count will not be pegged. Instead,
Num_Times_Max_Conn_Reached count will be pegged on the blocking
sector.
AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES =
AN-initiated Connection attempt failures - other failures
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD =
............................................................................................................................................................................................................................................................
receiving the TCC.
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ =
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL =
sector.
AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES =
AT-initiated Connection attempt failures - other failures
............................................................................................................................................................................................................................................................

when the Suspend Timer is still running, i.e., before the AT goes into the Sleep mode. It
does not involve the traditional Page/Connection Request sequence; rather the AN revives
a dormant connection by directly sending a TCA to the AT. This strategy results in an
expedited connection setup compared to the traditional AN Initiated process.
Note that Fast Connects are treated as mutually exclusive in Service Measurements from
all the AT and AN Initiated connection pegs.
The Fast Connect failures could be due to blocking, internal errors when allocating
resources for TCA, or RF reasons similar to an AT/AN initiated TCA.
The peg counts are defined on a per AP basis and can be rolled up to the RNC or SN level.
Formula
(FAST_CONNECT - FAST_CONNECT_FAIL_NO_TCC_RCVD -
FAST_CONNECT_FAIL_NO_RL_ACQ )
DO Fast connect success rate (%) = ------------------------------------------------------X 100
(FAST_CONNECT)
FAST_CONNECT =
The count is pegged when the AN receives a request from the network to
transmit data to the AT that just went idle and AN decides to revive the
dormant link via Fast Connect method. Note that the count is pegged even
if TCA could not be sent because of resource blocking or TCA allocation
failures.
FAST_CONNECT_FAIL_NO_TCC_RCVD =
Similar to the AT/AN_Init_Fail_No_TCC_Rcvd, these are Fast Connect
failures that occur when AN times out waiting for TCC from the AT after it
has sent RTC_Ack message to the AT indicating it has acquired the
preamble.
FAST_CONNECT_FAIL_NO_RL_ACQ =
Similar to the AT/AN_Init_Fail_No_RL_Acq, these are Fast Connect
failures that occur when AN times out waiting to acquire traffic channel
preamble from the AT after sending TCA.
............................................................................................................................................................................................................................................................

This metric gives the percentage blocking for AN-initiated sessions. It is equivalent to the
carrier basis.
Formula
AN_INIT_CONN_REQ -
Connection Blocking Ratio (%) = --------------------------------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
TCA_FOR_AN_INIT_CONN_REQ = Traffic Channel Assignments for AN Initiated

Connection Requests

carrier basis.
Formula
AT_INIT_CONN_REQ -
Connection Blocking Ratio (%) = ---------------------------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
AT_INIT_CONN_REQ = AT Initiated Connection Requests
TCA_FOR_AT_INIT_CONN_REQ = Traffic Channel Assignments for AT Initiated

Connection Requests
............................................................................................................................................................................................................................................................

Formula
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD +
AN_INIT_CONN_REQ
Count Definitions
= AN initiated connection attempt failures - no resources available
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
= AN initiated Connection attempt failures - no traffic channel
confirmation received
AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES
AN_INIT_CONN_REQ
= AN Initiated Connection Requests
............................................................................................................................................................................................................................................................

Formula
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD +
AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES)
DO AT-Initiated Ineffective Call Rate (%) = -------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
= AT initiated connection attempt failures - no resources available
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
= AT initiated Connection attempt failures - traffic channel confirmation
received
AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES
AT_INIT_CONN_REQ
............................................................................................................................................................................................................................................................

Formula
AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES +
Count Definitions
= AT initiated Connection attempt failures - traffic channel confirmation
received
AT_INIT_CONN_REQ
............................................................................................................................................................................................................................................................
= AN initiated Connection attempt failures - traffic channel confirmation
received
AN_INIT_CONN_REQ

requests. The Established Call rate, or its complementary Ineffective Connection Attempt
rate, encompasses all types of failures that prevent a successful connection setup. Largely,
the failures can be broken down into RF failures or blocking.
The RF Failure rate for Connections includes connection attempt failures due to reverse
link not acquired and No TCC received from the AT. Both these failures occur after the
AN has sent the TCA. In addition, another peg count, other failures - post-TCA is included
in the formula to account for post-TCA failure not specifically pegged. Basically, the rf
failure rate means either the AT or the AN did not have sufficient signal strength to receive
signaling and/or actual traffic channel assignment packets leading up to the connection
setup failure.
Note that the RF conditions can be poor to begin with, even as early as the AT is about to
send the Connection Request. However, any performance hit is not captured in SM until
the initial stages of the traffic channel setup (that is, if AN times out waiting for traffic
channel preamble or TCC message).
The peg counts are defined on a per sector-carrier basis.
Formula
(AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD +
............................................................................................................................................................................................................................................................
Count Definitions
= 1xEV Traffic Channel Assignments for AN Initiated Connection
Requests

Formula
(AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD +
DO AT-Initiated RF failure rate (%) = --------------------------------------------------- X 100
Count Definitions
= AT initiated Connection attempt failures - no traffic channel confirmation
received
= 1xEV Traffic Channel Assignments for AT Initiated Connection
Requests
............................................................................................................................................................................................................................................................
Formula
AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES +
Count Definitions
received
............................................................................................................................................................................................................................................................
1xEV-DO Connection Attempt Failure Percentage due to Negotiation Failure

This metric gives percentage of failed connections that are due to the failure to negotiate a
traffic channel. The peg counts are defined on a per sector-carrier basis and can be rolled
Formula
DO Conn Attempt Fail % - Negotiation Fail = ----------------------------------------- X 100
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED +
Count Definitions
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AT initiated Connection attempt failures - negotiation fail
received
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED
= AN initiated Connection attempt failures - negotiation fail

Formula
AT_INIT_CONN_ATTMPT_FAIL_NO_ TCC_RCVD +
............................................................................................................................................................................................................................................................
Count Definitions
received
............................................................................................................................................................................................................................................................

Assignment
Formula
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD)
Count Definitions
received
............................................................................................................................................................................................................................................................

Formula
(AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES +
DO Conn Attempt Fail % - Other = ------------------------------------------------------- X 100
Count Definitions
received
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Call Drop Metrics

............................................................................................................................................................................................................................................................

Formula
Count Definitions
CONN_REL_RLL = Connection Release due to RF Link Lost. These are connection

releases declared by the AN when it stops receiving valid data from the AT
on the reverse link. More precisely, when the AN sees no more than 3 good
DRCs in the trailing 5 sec interval, it drops the connection. The dropped
connection may be caused by poor RF link conditions on the reverse link,
or if AT disables reverse link transmission (because it lost the forward link
or due to any internal errors). This peg count is conceptually similar to the
Lost call count in the Alcatel-Lucent 2G/3G1x product, of course, the logic
for declaring dropped connection is quite different.
CONN_REL_OTHER_REASON = This is a catch all for releases not accounted for by

any of the Connection Release related peg counts. One of the main causes
is internal call processing errors at the AN.
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD = AT initiated Connection attempt

failures - no traffic channel confirmation received
AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = AN-initiated Connection attempt

failures - rev link not acquired
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = AN-initiated connection

attempt failures - no resources available
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD = AN initiated Connection attempt

AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = AT-initiated Connection attempt

AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = AT-initiated connection attempt

failures - no resources available
SO_SOR_HOFF_FAIL_NO_AT_RSP = This count reflects soft/softer handoff failures

primarily due to RF link conditions. When an attempt to add or drop a
handoff leg fails because the AN has timed out waiting for a Traffic
Channel Complete message from the AT in response to a TCA, the
connection resources are released and this count is pegged. The peg is
similar to the Call shutdown due to Handoff Timeout peg in 3G1x. Note
that the handoff here refers to the process of adding or dropping a leg to the
Active set. In 1xEV-DO, all legs in the Active set (up to a max of 6) are
used for reverse link operation. Of these, AT selects only one leg for
forward link reception. The process of switching between legs on the
forward link (when a different active set leg becomes stronger) is called
virtual soft/er handoff and is entirely controlled by the AT. The handoff
failure peg discussed here has no relation to the virtual soft/er handoffs.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Data Re-transmission rate

link. It is simply the rate at which some of the original RLP bytes have to be re-
transmitted. The AT requests the re-transmission when it encounters a gap in sequence
number in its receive queue. In essence, if a RLP packet with sequence N is missed, it is
not until the receipt of packet N+1 before the AT senses the loss. At this point, the AT
sends a NAK (negative acknowledgement) and requests the AN to resend the lost data.
Re-transmission impacts the end-user experience in that it delays the eventual reception of
the original data. A re-transmission rate of ~1% is usually tolerable. Higher rates may be
more indicative of congestion points within the AN or AT, rather than physical layer
errors. For example, a "dirty" T1 could result in data loss between the cell and the RNC. It
would have nothing to do with the underlying RF channel. The AT itself may also drop
RLP packets or mis-segment them if it is unable to keep up with the processing, resulting
in RLP NAKs.
ATs usually do a good job of maintaining close to 1% packet error by adjusting requested
DRC rates based on the prevailing RF conditions and achieved error rates. Unless the user
is in bad coverage for extended periods or there is a hardware issue with the AT or the
cellsite (in the RF or digital chain, timing circuitry etc), the physical layer error rate is
typically not an issue. Issues in the AN beyond the cellsite (such as T1, router, RNC, etc)
do not have much influence on the packet error rate; they only impact the RLP NAK rate.
This metric is defined on a per sector-carrier basis.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions
RLP_RETXED_FTC = The total number of RLP octets requested for re-transmission by

the AT via RLP NAKs. In 1xEV-DO, there is only one retry allowed. If the
AT is unable to receive the original RLP data on the forward link which it
is able to identify by seeing a gap in sequence number on successive RLP
packets, it requests the AN to resend the missing data by send a NAK
message. The NAK message contains the starting sequencing number as
well as the length of the missing block of data. When the AT receives the
............................................................................................................................................................................................................................................................
re-transmitted data, it plugs the gap and goes on with further processing. If
it still does not receive data within a certain period of sending the NAK,
then it is up to the higher layers to recover. The purpose of implementing
RLP layer in a wireless data network is to present the upper layers with an
extremely low error probability channel. The upper layers were designed a
while back for wired connections, and do not operate well on a lossy
channel.
RLP_TXED_FTC = Total number of original RLP octets transmitted on the forward link
traffic channel of a given sector. It is raw user payload plus any overhead
bytes from protocol layers above RLP (Application/TCP/IP/PPP),
including any data that could not be delivered to the end user even after the
single RLP retry. It does not include RLP layer overhead bytes or RLP
layer re-transmissions.
1xEV-DO Reverse Link Data Re-transmission rate

link. Similar to the forward link, any RLP NAKs could be due to errors on the physical
layer or packet drops within the AN/AT.
For example, problems in the cell aggregation router or backhaul link can drop some RLP
packets before they reach the RNC. The TP in the RNC is responsible for processing RLP
packets. When the TP encounters a gap in the sequence number on the incoming RLP
stream, it declares a RLP NAK; the underlying physical layer delivery might have been
perfectly fine.
Formula
MISSING_RLP_REQ_RTC
RLP_RXED_RTC
Count definitions
MISSING_RLP_REQ_RTC = The total number of bytes the AN requests the AT to re-

transmit on the reverse link. The request is made via an RLP NAK
message. As on the forward link, any such missing data can be NAK'ed
only once. If after the retry, the AN still is still unable to receive the data, it
declares a NAK Abort and lets upper layer(s) handle the recovery.
............................................................................................................................................................................................................................................................
RLP_RXED_RTC = The total number of original RLP octets received on the reverse link
bytes from protocol layers above RLP (Application/TCP/IP/PPP). It does
not include RLP layer overhead bytes, RLP layer re-transmissions or any
data lost in transit even after the single RLP retry by the AT.

link. There is additional information available at the cell regarding reverse link
retransmissions. Basically, if the AN times out waiting for a re-transmission from the AT,
it pegs the amount of missing RLP data as a separate count. This allows defining a metric
called re-transmission failure rate, which is the rate at which the requested retransmission
bytes fail to arrive at the AN.
Normally, the re-transmission failure rate should not be much worse than a few percentage
points (considering 1% chance that either the downlink RLP NAK got lost or the re-
transmission from the AT got corrupted). However, the issues that led to the re-
transmissions in the first place may also contribute to a higher re-transmission failure rate
(RF link degradation, AT taking longer than usual on a hybrid mode periodic search of
3G1x system or configuration/processing issues in the AT/AN). Packet losses on the T1 or
mis-configuration of the cell aggregation router can lead to loss of RLP packets within the
AN resulting in high re-transmission failure rate. Similarly, any issues within the AT can
also be a contributor.
The impact to the end-user of RLP re-transmission failures may be much higher than the
RLP re-transmissions itself; the upper layers now have to handle the recovery of the
missing data. The TCP layer is known to overcompensate for such losses by throttling the
transmission until a stable channel is reestablished; in the short-term it ends up slowing
down the user experience.
Formula
MISSING_RLP_REQ_RTC
Count definitions
MISSING_RLP_NEVER_RXED_RTC = The total number of RLP bytes that the AN did

not receive within a certain timeout interval after it has requested the AT to
retransmit it.
MISSING_RLP_REQ_RTC = RLP Octets for retransmission on the reverse link

............................................................................................................................................................................................................................................................

MAC layer.
The formula is changed in R24 to account for the peg counts being MAC layer packets.
The new formula is applicable to all previous releases.
Formula
8 * 10 ^ 6
Count definitions
(1024 bits/packet)
(1024 bits/packet)
= Total MAC packets transmitted on forward traffic channels at 153.6
kbps (1024 bits/packet)
............................................................................................................................................................................................................................................................
EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT
kbps - long format (2048 1024 bits/packet)
kbps - long format (1024 bits/packet)
= Total MACpackets transmitted on forward traffic channels 921.6 kbps
(1024 bits/packet)
= Total MAC packets transmitted on forward traffic channels 1843.2 kbps
(1024 bits/packet)

second. The metric is defined on a per sector-carrier basis and is defined only for the one
The peg counts are measured in the modem at the MAC layer. In the 1xEV-DO protocol
stack, the MAC layer resides between the physical and RLP layers.
............................................................................................................................................................................................................................................................
The metric is computed using the counts of MAC layer packets transmitted at various
rates. The MAC layer packet counts include both the traffic and the signaling packets
transmitted by a sector to serve all active users during the hour.
The MAC layer Data rate is effectively a measure of sector data rate. There can be several
users on a sector requesting data concurrently, but the scheduler serves only one user in a
given slot by the very nature of time-shared 1xEV-DO scheduler on the forward link.
Furthermore, the metric in the denominator counts up the active transmission slots only
once, not multiple times if there are multiple users in the queue. These considerations
point out that the metric does not represent individual user data rate (data served / total
wait time), but is a very good indication of the sum of individual user data rates. For
example, if there are 10 users each getting 100 kbps continuously over the hour or 1 user
getting 1Mbps throughout the hour, the metric will report 1Mbps in both the cases.
The metric can be used in multiple ways. It is expected to register an increase initially as
the traffic grows and then saturate at a certain level, which may be a function of the
number of T1/E1s equipped on the cell, user mobility/usage location, mix of end-user
applications, etc. As the number of users increases initially, a phenomenon called
"scheduler gain" kicks in. The scheduler exploits short-term temporal variations in RF
conditions and attempts to serve a user when it is at the best possible RF conditions. When
the AT experiences constructive fading, it is likely to request a much higher DRC
compared to other times, when it is in a destructive fade. This allows the scheduler to
boost the overall sector data rate. Beyond a certain number of users, the gains diminish
and saturate eventually as collectively the users do not present any better rates for the
scheduler to exploit further. The trending along with other metrics/counts can be used for
capacity forecast and provisioning, as mentioned throughout the document.
The metric may also find its use for performance troubleshooting purposes - sudden drop
in data rate served is an indicator of a problem in the backhaul (one of the T1s goes out of
service), cell (CBR issue lowering the SNR received at the AT), etc.
Alternatively, the MAC layer transmitted packets can be utilized to provide a general view
of the RF optimization state of a sector and/or RF signal quality experienced by the user.
The MAC layer packet counts are available separately for each forward link rate (38.4 to
2457.6 kbps). Their relative distribution can reveal interesting performance insights. For
example, if a substantial number of packets are transmitted at higher rates, then this means
the users are in a benign RF coverage area. Of course, this inference lies on the assumption
there are relatively few users on the sector. As the number of users concurrently
downloading data increases on a sector, the scheduler gain kicks in. The proportional fair
scheduler attempts to serve users when they are experiencing local SNR peaks (short term
constructive fades). This will naturally skew the MAC layer packet distribution towards
higher rates.
............................................................................................................................................................................................................................................................
The MAC layer packet distribution may also be used for performance troubleshooting. A
deterioration over time (that is, shift towards lower rates) may be an indication of
degradation of signal quality (such as, due to external interference, faulty cellsite
hardware, etc.).
The metric is calculated as forward link data volume transmitted divided by the time used
to send the traffic data packets. Note that there are 2,160,000 physical layer slots in one
hour (3600 seconds divided by the length of each slot, which in 1xEV-DO is 1.66
milliseconds).
Formula
Count definitions
(1024 bits/packet)
(1024 bits/packet)
............................................................................................................................................................................................................................................................
kbps - long format (1024bits/packet)
(1024 bits/packet)
(1024 bits/packet)
............................................................................................................................................................................................................................................................
EVM_TOTAL_BUSY_PCNT_SLOTS
= Percentage of physical layer slots in the measurement hour used for
forward link traffic data transmission (divide by 10^6 to get percentage)

transmission of traffic data. At any given time, only one user can be served traffic on the
1xEV-DO forward link. This is inherent to the time-shared mechanism adopted by the IS-
856 standards for the forward link. Therefore, a metric such as active connections is only
of secondary value to quantify the forward link usage (secondary in the sense that the
operator may still want to make sure that a given sector does not outrun any other forward
link constraints, such as max of 64 MAC indices allowed by the standards). But the
primary way to characterize forward link loading requires one to look at the percentage of
slots being used in an hour to serve traffic users. A higher utilization increases the
likelihood for user starvation as the available bandwidth is getting time shared by the
users.
A large value indicated by this metric does not necessarily mean congestion on the air link.
A single user doing FTP downloads throughout the hour is expected to drive the utilization
very high (say in 90s, won't reach 100% because the % busy slots exclude the synchronous
and asynchronous Control Channel slots); this is not a surprising result. This underscores
the fact that the metric should be interpreted collectively with Average active connections
or another peg count called Evm_Avg_Elig_User (Average number of Scheduler Eligible
Users to determine if indeed there are a large number of users responsible for driving up
the loading.
The metric is defined on a per sector-carrier basis. The peg count is measured in the
modem at the physical layer (slots are only defined at the physical layer).
The formula is changed in R24 to use the percent busy slots peg count and is applicable to
previous releases beginning with R22.
Note that the peg count measures only those slots used for actual traffic transmission so
the control slot counts do not have to be subtracted.
Formula
Count definitions
EVM_TOTAL_BUSY_PCNT_SLOTS =
Percentage of physical layer slots in the measurement hour that were
actually used for forward link traffic data transmission (divide by 10^6 to
get percentage)
............................................................................................................................................................................................................................................................

per second.
Formula
............................................................................................................................................................................................................................................................
Count Definitions
EVM_TOTAL_BUSY_PCNT_SLOTS = Percentage of busy slots used for traffic data


megabytes.
The metric is defined on a per sector-carrier basis.
The peg counts are measured at the RLP layer. This metric provides a measure of the data
volume sent in the forward direction per active connection. The RLP byte count
represents actual user traffic with less overhead than either MAC layer or physical layer
packet counts, which can be padded with dummy bits to fill the packet. Although the peg
count name in the denominator is "Average Active Connections" it is actually the sum of
all the total connections based on a 10 second scan.
Note that if the count is read from IBM Prospect for Alcatel-Lucent, it has already been
divided by 360 and should not be divided again.
Formula
Count Definitions
RLP_TXED_FTC = Number of RLP octets transmitted on the forward link
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Physical Data Volume (MB)

This metric gives the average data volume on the reverse link in megabytes.
The metric is defined on a per sector-carrier basis. The peg counts are pegged only on the
DRC pointed sector (the sector that AT is tuned to for forward ink data reception) even if
there are multiple pilots in the active set.
Formula
DO Reverse link physical data volume (MB) =
----------------------------------------------------------------------------------
8 * 10^6
Count Definitions
............................................................................................................................................................................................................................................................

This metric gives the average data rate on the reverse link in kilobits per second.
The metric is defined on a per sector-carrier basis.The metric provides a measure of
individual user data rate, a good indicator of average user experience in the network on the
reverse link. Beyond a certain number of users on the sector, the individual user rate
begins to suffer because of the limited bandwidth on the air link. This behavior points to
its possible use in capacity planning for the reverse link.
Note that only rates of 9.6, 19.2, 38.4, 76.8 and 153.6 kbps are included in the
computation. The frame count for 0 kbps (which means frames with no data content, just
control information such as Pilot, DRC, RRI and ACK streams) is not included. This is a
closer representation to end user experience since idle times are ignored.
There is no count to directly capture the total sector level rate. It can be computed by
converting the number of frames at each rate into total data transmitted (each frame is
26.66 ms, so a 9.6 kbps frame carries 256 bits at the physical layer), adding the total bits
transmitted over the hour and dividing it by 3600 seconds. (The previous metric calculates
the total data volume). This calculation provides an indication of the amount of data
transmitted per second as an average over the hour; however, the problem with this
approach is that there may be several seconds or minutes during the hour when there are
no or a small number of user connections, which will underreport the true sector level data
rates.
Formula
DO Reverse link burst rate (kb/s) = -----------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

As opposed to the RLP layer errors which may be induced by several sources, this metric
is a direct indication of errors on the RF link. It is the rate at which the frames on the
reverse traffic channel could not be successfully decoded due to insufficient signal
strength. A frame error means a checksum failure was encountered by the cellsite when
processing a frame whose RRI bits indicated a rate of 9.6kbps or higher.
The metric is a useful indication of prevailing RF conditions experienced by the user on
the reverse link. If the RLP layer re-transmissions are significantly higher than the
physical layer error rate (which usually ranges from 0.5 to 1.5%), it is indicative of
problems outside of the RF link (typically, the backhaul, the cell aggregation router, or
some processing burden constraints at the AT).
level.
Formula
DO Reverse Frame Error Rate (%) = ------------------------------------------------------ X 100
Count Definitions
REVERSE_FRAME_ERROR_COUNT = Total number of frames received at the cellsite

that could not be decoded properly and hence were discarded. These are the
frames for which the corresponding Reverse Rate Indicator (RRI) was
successfully decoded and indicated as 9.6kbps or higher, but its traffic
channel content did not pass the CRC check. In other words, only the
frames which had traffic content are evaluated for CRC. There is no traffic
content on the 0kbps frame, hence no question of computing a CRC check.
............................................................................................................................................................................................................................................................
Given that a erased frame, by definition, has a traffic content, this also
implies that it will result in RLP error as well, forcing a re-transmission
(assuming the errors occurred on the first RLP attempt). If there are
multiple pilots in the active set, the status of only the selected frame is
pegged. The count is pegged only on the DRC pointed sector.
TOTAL_REVERSE_FRAME_COUNT = Total number of frames received at the cellsite

on the reverse traffic channel (both good and erased). It only includes the
frames received with rates of 9.6kbps or higher. If there are multiple pilots
in the active set, status of only the selected frame is pegged. The count is
pegged only on the DRC pointed sector.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Success Rate

This metric gives the success rate for soft/softer handoffs. The peg counts are defined on a
per sector-carrier basis.
Formula
DO Handoff success rate (%) = ------ ------------------------------------------------------ X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
SO_SOR_HOFF_ATTMPT
= Soft-Softer HO Attempt
= Soft-Softer HO Attempt failure due to no resources
SO_SOR_HOFF_FAIL_OTHER_REASON
= Soft-Softer HO Attempt failure due to other reasons
............................................................................................................................................................................................................................................................

This metric gives the success rate for Inter-subnet idle transfers. The peg counts are
Formula
INT_SUBNET_IDL_TRFR_ATTMPT -
(ISBNT_IDL_TRFR_FAIL_NO_RSP_ PRV_SBNET +
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN +
ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_NT_FOUND +
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD)
DO Int sub idle xfer success rate (%) = ---------------------------------------------------- X 100
INT_SUBNET_IDL_TRFR_ATTMPT
Count Definitions
INT_SUBNET_IDL_TRFR_ATTMT
= Number of Inter Subnet Idle Transfer Attempts
INT_SUBNET_IDL_TRFR_FAIL_NO_RSP_FROM_PREV_SUBNET
previous subnet
IBNT_IDL_TRFR_FAIL_NO_RSP_PRV_SBNET
previous subnet
INT_SUBNET_IDL_TRFR_FAIL_ORIG_PDSN_CANNOT_CONNECT
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN
INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON
= Number of Inter Subnet Idle transfer failures for reasons not specifically
pegged
............................................................................................................................................................................................................................................................
INT_SUBNET_IDL_TRFR_FAIL_SOURCE_ IP_ADDR_NOT_FOUND
ISBNT_IDL_TRFR_FAIL_SRC_ IP_ADR_NT_FOUND
INT_SUBNET_IDL_TRFR_FAIL_REJECT_MSG_RECEIVED
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD
1xEV-DO Soft/Softer Handoff Blocking Rate (due to no resources)

This metric gives the percentage blocking for soft/softer handoffs due to a lack of
resources. The peg counts are defined on a per sector-carrier basis and are pegged at the
target sector.
Formula
SO_SOR_HOFF_FAIL_NO_RESOURCE
DO HO Blocking Rate (%) = ------------------------------------------------------- X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
SO_SOR_HOFF_FAIL NO_RESOURCE= 1xEV Soft-Softer HO Attempt Fail - No

Resources
SO_SOR_HOFF_ATTMPT = 1xEV Soft-Softer HO Attempt
............................................................................................................................................................................................................................................................
Performance Metrics for Release 23 Capacity Management Metrics

............................................................................................................................................................................................................................................................

This metric represents the total number of active traffic channel links on a given sector. It
is more relevant on the reverse link where each active user including its soft as well as
softer link is actively demodulated at the cell site at all times. It does not have much
meaning on the forward link due to the time shared and virtual soft handoff concepts of
1xEV-DO.
For example, if there are 10 connections on the sector at a given time and only 2 of them
are really using their connections to upload some data, the remaining 8 are still utilizing
some of the reverse link bandwidth (typically, only pilot, MAC and Ack channels - no
traffic). This will get considered as 10 active connections. On the forward link, let's say
the same two users are also downloading. Each user will contend and get served on some
of the time slots, but the point is that the presence of 10 connections on the reverse link
have no bearing on the forward link utilization.
Note that the Average Active connections include soft and softer links. If one were to
compare with 2G/3G1x, this would be similar to Total Walsh Code or Total RF link usage
metric with the only difference that in 1xEV-DO it has meaning on the reverse link only.
For capacity forecasting purpose, it makes more sense to evaluate the metric on a daily
busy hour basis per sector or as an average computed over a few busy hours in a day, rather
than a large grouping of cells or combined over all hours of the day.
level. Although the peg count name is "Average Active Connections" it is actually the
sum of all the total connections based on a 10 second scan.
Formula
360
Count Definitions
AVG_ACTIVE_CONN_PER_SECTOR = Each sector maintains and increments this

counter every 10 seconds by an amount equal to the number of active
connections (including soft and softer handoff links) present at the time on
the given sector. Essentially it is a single snapshot within the 10 sec period.
Since, there are 360 such intervals in an hour, it is divided by 360 to
provide DO Traffic channel usage in a given hour.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

A PCF reactivation is defined as a transition from a dormant to an active connection
triggered by a fresh data request from the PDSN.
When the PCF receives data to be transmitted to a dormant user, it attempts to send a page
or use the Fast Connect method to revive the link depending on the time elapsed since the
last connection went dormant. Once a traffic channel is established and the path from the
PDSN all the way down to the AT is ready for data transmission, it is considered a
successful PCF reactivation.
Note that a fresh PPP link can only be initiated by the AT. Hence, there is no concept of
network activation. Data from the PDSN may only start flowing once a PPP link is
established. If the data from the PDSN arrives when the PPP link is dormant, then it
results in what is known as PCF or network reactivation, as discussed above.
The PCF reactivation failures can be contributed by RF failures (resulting in Page timeout
or AN initiated Connection Failure or Fast Connect Failure), any system bottlenecks (such
as inability to allocate traffic channel resources), AT not reachable (such as AT powered
off or moved to a different RNC without a clean inter-RNC idle handoff), etc.
The peg counts are defined on a per TP basis.
Formula
PCF_INIT_REACT_FAIL
DO PCF Reactivation rate AN Init (%) = ------------------------------------------------- X 100
Count Definitions
PCF_INIT_REACT_ATTMPT =
Total number of attempts made by the PCF to revive a dormant traffic
connection when it receives data from the PDSN for transmission to the
end user.
PCF_INIT_REACT_FAIL =
This count is incremented when the AN is unable to establish a data path to
a dormant end user in response to data transmission request from the
PDSN.
............................................................................................................................................................................................................................................................

Most of the metrics discussed so far relate to measuring performance on the air interface.
This metric deals with the success rate associated with setting up connections on the R-P
link.
The R-P link is also known as A10-A11 connection. It is responsible for transporting GRE
packets between the PCF and the PDSN. When the AN receives a request from the user to
set up a PPP connection with the PDSN, it instructs the PCF to initiate an A11 link with
the PDSN. The A11 link is really a protocol consisting of a series of signaling messages
between the PCF and the PDSN to set the path for follow-on A10 bearer (user data)
packets. Similarly, when the user releases a PPP connection, the PCF tears the down the
A11 link by sending appropriate messages to the PDSN. A fresh R-P connection is also
established by the PCF on the target RNC with the old PDSN after an inter-RNC idle
handoff.
The R-P connection success rate is a useful measure of proper connectivity between the
AN and the PDSN as well as any provisioning needs. For example, increased number of
PDSN rejects in the busy hour may be a sign of bottlenecks at the PDSN. Increased
number of failures during low usage hours may simply be a reflection of PDSN outages
for maintenance. If the R-P connection failure rate is unacceptable, it may be worthwhile
to also evaluate error codes obtained directly from the PDSN to facilitate further
investigation. Starting with R23, the ROP file also stores reason codes for R-P connection
failures.
Formula
RP_CONN_ATTMPTS -
RP_CONN_FAIL
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS =
Total number of attempts made by the AN to setup an A11 connection with
the PDSN based on requests from the AT. Basically, any PPP packet from
the AT that requires transmission to the PDSN for which an A10 link does
not exist results in a R-P connection attempt. Furthermore, an attempt to
transfer an existing R-P session between PCFs on the source and target
RNCs as part of an inter-RNC Idle handoff will also increment this peg.
Any reactivations from dormancy, whether AT or AN initiated, are not
included in the count.
............................................................................................................................................................................................................................................................
RP_CONN_FAIL =
Total number of attempts to establish a R-P connection that fail. The failure
could either be due to a reject message from the PDSN, or a response
timeout (PDSN not reachable due to addressing error, PDSN not in
service).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Prospect for Release 23

............................................................................................................................................................................................................................................................
The purpose of this chapter is to provide definitions for new Prospect Primitive
Calculations (PCALCs) that support the performance metrics defined for FMS R23.
Existing PCALCs supporting 1xEV-DO performance metrics that did not change in ECP
R23 are not included in this chapter. Please refer to Chapter 4, 1xEV-DO Metrics in
Watchmark Prospect for Release 22.
calculation.
percentages.
The PCALCs defined in the chapter are targeted to be implemented in Prospect R23.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 23 Session Management Metrics

............................................................................................................................................................................................................................................................
Percent Active Session Metric

DOp_ActSess is not defined for FMS R23 and later.
Average Active Sessions

Prospect Traffic Report Entity: 1xEV_AP
Valid Releases: FMS R23 and later
DOp_AvgActSess = AvgActiveConnAP / 3600.0
Notes:

AvgActiveConnAP AVG_ACTIVE_CONN_PER_AP 1xEV_AP

DOp_DormSess is not defined for FMS R23 and later.
............................................................................................................................................................................................................................................................
Call Setup Metrics

............................................................................................................................................................................................................................................................

Valid Releases: RNC R23, R24, and R25
DOp_EstCall = 100.0 * (ATInitConRq + ANInitConRq - ATInitConAttFlNoResrc -
ATInitConAttFlNoTCCmpRcv - ATInitConAttFlNoRL - ATInitConAttFlOther -
ANInitConAttFlNoResrc - ANInitConAttFlNoTCCmpRcv - ANInitConAttFlNoRL -
ANInitConAttFlOther) / (ATInitConRq + ANInitConRq)
Mapping between Prospect names and 1xEV-DO Names:
Prospect
ATInitConAttFlNoResrc AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL 1xEV_SectorCa
rrier
ATInitConAttFlNoTCCmpRcv AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
ATInitConAttFlOther AT_INIT_CONN_ATMPT_FAILED_OTH_FAILURES
ANInitConAttFlNoTCCmpRcv AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD
ANInitConAttFlOther AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES
............................................................................................................................................................................................................................................................

Valid Releases: FMS R23 and R24
DOp_FastCnctSuc = 100.0 * (FastConnect - FastConFlNoTCCmpRcv -
FastConFlRevLnkNotAcq) / FastConnect
Notes:
Prospect
Traffic
FastConnect FAST_CONNECT 1xEV_AP
FastConFlNoTCCmpRcv FAST_CONNECT_FAIL_NO_TCC_RCVD
FastConFlRevLnkNotAcq FAST_CONNECT_FAIL_NO_RL_ACQ
............................................................................................................................................................................................................................................................

Valid Releases: RNC R23 and later
ANInitConAttFlNoTCCmpRcv + ANInitConAttFlNoRL + ANInitConAttFlOther) /
ANInitConRq
Notes:
1. The current calculation is modified by removing ANInitConAttFlCnfgNegFl from the
numerator
2. Mapping between Prospect names and 1xEV-DO Names
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_InefCallAttATInit = 100.0 * (ATInitConAttFlNoResrc +
ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL + ATInitConAttFlOther) /
ATInitConRq
Notes:
1. The current calculation is modified by removing ATInitConAttFlCnfgNegFl from the
numerator.
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_InefCallAttTotal = 100.0 * (ANInitConAttFlNoResrc +
ANInitConAttFlNoTCCmpRcv + ANInitConAttFlNoRL + ANInitConAttFlOther +
ATInitConAttFlNoResrc + ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL +
ATInitConAttFlOther) / (ANInitConRq + ATInitConRq)
Notes:
Mapping between Prospect names and 1xEV-DO Names
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................

DOp_RFFailANInit = 100.0 * (ANInitConAttFlNoTCCmpRcv +
ANInitConAttFlNoRL) / TCAANInitConRq
Notes:
Prospect
Traffic

DOp_RFFailATInit = 100.0 * (ATInitConAttFlNoTCCmpRcv +
ATInitConAttFlNoRL) / TCAATInitConRq
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to Reverse Link Not Acquired

DOp_CnctFlNoRL = 100.0 * (ATInitConAttFlNoRL + ANInitConAttFlNoRL) /
(ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl +
ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL + ATInitConAttFlOther +
ANInitConAttFlNoResrc + ANInitConAttFlCnfgNegFl +
ANInitConAttFlNoTCCmpRcv + ANInitConAttFlNoRL + ANInitConAttFlOther)
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_CnctFlCnfgNeg = 100.0 * (ATInitConAttFlCnfgNegFl +
ANInitConAttFlCnfgNegFl) / (ATInitConAttFlNoResrc + ATInitConAttFlCnfgNegFl +
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_CnctFlNoResrc = 100.0 * (ATInitConAttFlNoResrc + ANInitConAttFlNoResrc) /
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
Connection Attempt Failures Due to No Response to Traffic Channel Assignment

DOp_CnctFlNoTCCmpRcv = 100.0 * (ATInitConAttFlNoTCCmpRcv +
ANInitConAttFlNoTCCmpRcv) / (ATInitConAttFlNoResrc +
ATInitConAttFlCnfgNegFl + ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL +
ATInitConAttFlOther + ANInitConAttFlNoResrc + ANInitConAttFlCnfgNegFl +
Notes:
Prospect
Traffic
ANInitConAttFlNoTCCmpRcv AN_INIT_CONN_ATTMPT_FAIL_No_TCC_RCVD
............................................................................................................................................................................................................................................................

DOp_CnctFlOther = 100.0 * (ATInitConAttFlOther + ANInitConAttFlOther) /
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 23 Dropped Call Metrics
Dropped Call Metrics

............................................................................................................................................................................................................................................................

DOp_DropCall = 100.0 * (ConRlsRLL + ConRlsOther + SftSftrHOFlNoATRsp) /
(ATInitConRq + ANInitConRq - ATInitConAttFlNoResrc -
ATInitConAttFlNoTCCmpRcv - ATInitConAttFlNoRL - ATInitConAttFlOther -
ANInitConAttFlNoResrc - ANInitConAttFlNoTCCmpRcv - ANInitConAttFlNoRL -
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Release 23 New Metrics Retrofitted to R23
New Metrics Retrofitted to R23

............................................................................................................................................................................................................................................................
1xEV-DO Reverse Link RLP Data Throughput

Prospect Traffic Report Entity: 1xEV_Sector, 1xEV_SectorCarrier (RNC R24 and later)
Valid Releases: All RNC releases
DO_RLPThruput_RevL = (8 * RLPRXRTC /1000.0) /
(0.0266 * (RevOutLoopPCFrCt96 + RevOutLoopPCFrCt192 +
RevOutLoopPCFrCt384 + RevOutLoopPCFrCt768 + RevOutLoopPCFrCt1536))
Notes:
Prospect Traffic
RLPRXRTC RLP_RXED_RTC 1xEV_SectorCarrier

RP Connection Success Rate

Prospect Traffic Report Entity: 1xEV_TP
Valid Releases: RNC R21and later
DOp_RPCnctSuccess = 100.0 * (RPConAtt - RPConFail) / RPConAtt
Notes:
1. The name of the metric DOp_SucReactATInit changes from "1X-EV DO PCF
Reactivation Success Rate for AT-Initiations" to "RP Connection Success Rate" in R25.
This name change is reflected in the Prospect Name, Column Headings and the GUI
Description. The old name will automatically point to the new name in template
definitions, UDCs, etc.
............................................................................................................................................................................................................................................................
Prospect Traffic
Average Reverse Link Data Rate (kbps)

DO_AvgRevL_kbps = (9.6 * RevOutLoopPCFrCt96 + 19.2* RevOutLoopPCFrCt192 +
Notes:
1. The name of the metric DO_AvgBrstRevLnk changes from "Average Reverse Link
Burst Rate (kbps)" to "Average Reverse Link Data Rate (kbps)" in R25. This name change
is reflected in the Prospect Name, Column Headings and the GUI Description. The old
name will automatically point to the new name in template definitions, UDCs, etc.
Prospect Traffic
RevOutLoopPCFrCt96 REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS 1xEV_SectorCarrier

1xEV-DO Soft/Softer Handoff RF Failure Rate-Requesting Sector

DOp_SftSftrHOFlRF_Req = 100.0 * SftSftrHOFlNoATRsp / SftSftrHOAttTCA
............................................................................................................................................................................................................................................................
Notes:
Prospect Traffic
SftSftrHOFlNoATRsp SO_SOR_HOFF_FAIL_NO_AT_RSP 1xEV_SectorCarrier
SftSftrHOAttTCA SO_SOR_ATTMPT_TCA_SENT 1xEV_Sector
1xEV-DO Average Reverse Link Power Control Setpoint - 0 kbps

DO_AvgRevLnkPCSetpoint_0 = 8.0 * RevOutLoopPCOut0 / RevOutLoopPCFrCt0
Notes:
Prospect Traffic
RevOutLoopPCOut0 REV_OUTER_LOOP_PC_TOTAL_OUTPUT_0KBPS 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Power Control Setpoint - 9.6 kbps

Notes:
Prospect Traffic

DO_AvgRevLnkPCSetpoint_192 = 8.0 * RevOutLoopPCOut192 /
RevOutLoopPCFrCt192
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

RevOutLoopPCFrCt384
Notes:
Prospect Traffic

RevOutLoopPCFrCt768
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

RevOutLoopPCFrCt1536
Notes:
Prospect Traffic
1xEV-DO AN-Initiated Blocking Ratio Due to No Resources

DOp_CnctBlkANInit_NoRsrc = 100.0 * ANInitConAttFlNoResrc / ANInitConRq
Notes:
Prospect Traffic
ANInitConRq AN_INIT_CONN_REQ 1xEV_SectorCarrier
ANInitConAttFlNoResrc AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL 1xEV_Sector
............................................................................................................................................................................................................................................................
1xEV-DO AT-Initiated Blocking Ratio Due to No Resources

DOp_CnctBlkATInit_NoRsrc = 100.0 * ATInitConAttFlNoResrc / ATInitConRq
Notes:
Prospect Traffic
ATInitConRq AT_INIT_CONN_REQ 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

The following performance metrics are provided:

1a. Session Management
Average Active Session Rate
1b. Call Setup
............................................................................................................................................................................................................................................................
1c. Call Drop

Dropped Call Rate
1d. Data Throughput
Total Forward Link MAC Data Transmitted (MB)
Average Forward Link MAC Datat Rate (kbps)
Average RLP Forward Link Data Rate (kbps)
Average User Forward Link Data Volume (MB)
Average Reverse Link Data Volume (MB)
1e. Handoff
Soft/Softer Handoff Success Rate - Requesting Sector
Soft/Softer Handoff Success Rate - Target Sector
Soft/Softer Handoff Blocking Rate due to No Resources - Requesting Sector
Soft/Softer Handoff Blocking Rate due to No Resources - Target Sector
Soft/Softer Handoff RF Failuer Rate - Requesting Sector
Soft/Softer Handoff RF Failuer Rate - Target Sector
2. Capacity Management Performance Metrics

3. Packet Data Reactivation Metrics

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

a traffic channel is assigned. A session setup may not succeed for various reasons. These
include blocking at the AN (already at max number of sessions); poor RF link (loss of
UATI Assignment or Complete messages on the air link even after exhausting all the
retries); AN unable to obtain old session information from the source RNC (applies only
to the color code method of inter-RNC idle handoff method where the target RNC must
find the old session info prior to assigning a UATI); potential misalignment between the
AT and AN (applies mainly to the Assign First method of inter-RNC idle handoff where
AN does not have knowledge of layer 2 messaging sequence number being used on the
source RNC), etc.
Due to changes in the way counts are pegged, as of R24 the session setup counts only
include new sessions and inter-subnet idle transfers using the prior session method. In
previous releases they also included sessions set up due to inter-subnet idle transfers. In
order to make this metric comparable to earlier releases, the session setup inter-subnet idle
transfer UATI complete count was added to the numerator and the inter-subnet idle
transfer attempts were added to the denominator.
This new formula is effective beginning with R24. As before, some failures included in
this metric result from inter-subnet idle transfers (color code method), so the metric is not
strictly indicative of RF quality.
Formula
DO Session Setup Success Rate (%) =
SESS_SETUP_UATI_COMPLETE_MSG_RCVD +
SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD
-----------------------------------------------------------------------------------------------X 100
SESSION_SETUP_REQ + INT_SUBNET_IDL_TRFR_ATTMPT
Count Definitions
SESSION_SETUP_REQ = Session Set Up Request (new and prior)
INT_SUBNET_IDL_TRFR_ATTMPT =
Inter-subnet idle transfer attempts (assign first and color code)
............................................................................................................................................................................................................................................................
SESS_SETUP_UATI_COMPLETE_MSG_RCVD =
Session Set Up - UATI Complete Message Received (new & prior). Pegged
when the AT acknowledges a UATI assignment message sent by the AN in
response to a UATI request.
SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD =
Session Set Up - UATI Complete Message Received (assign first & color
code)

Formula
360
Count Definitions
Number of active sessions on an AP. This count is pegged every 10
seconds during the measurement interval and added to the previous total.
Therefore, the result is divided by 360 to get the approximate average over
the measurement interval. Note that the measurement interval is not
exactly one hour so the calculation is approximate.
............................................................................................................................................................................................................................................................
Call Setup Metrics

............................................................................................................................................................................................................................................................

3G1X.
for a Connection.
level.
Formula
............................................................................................................................................................................................................................................................
DO Established call rate (%) = -------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
AT_INIT_CONN_REQ =
Connection Request.
attribute set.
receiving the TCC.
............................................................................................................................................................................................................................................................
sector.
AN-initiated Connection attempt failures-other failures
receiving the TCC.
............................................................................................................................................................................................................................................................
sector.
AT-initiated Connection attempt failures - other failures

Formula
DO Fast connect success rate = ------------------------------------------------------X 100
(FAST_CONNECT)
............................................................................................................................................................................................................................................................
Count Definitions
FAST_CONNECT =
failures.
preamble.

This metric gives the percentage blocking for AN-initiated connections. It is equivalent to
the Seizure to Assignment Deficit Ratio for terminations in 3G 1x. The peg counts are
Formula
AN_INIT_CONN_REQ -
DO AN-Initiated Connection Blocking Ratio (%) = ----------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
TCA_FOR_AN_INIT_CONN_REQ = Traffic Channel Assignments for AN Initiated

Connection Requests
............................................................................................................................................................................................................................................................

Seizure to Assignment Deficit Ratio for originations in 3G 1x. Any connection attempt
failures occurring after receiving a Connection Request and prior to sending the TCA are
termed as connection blocks or connection attempt deficits. These are failures entirely
happening within the AN, such as TCA allocation failure, some type of resource overload
or overflow, internal errors or messaging failure.
The blocks do not include any RF failures (there is no over-the-air interaction with the AT
once a Connection Request is received until after the TCA is sent). The blocks also do not
involve any failures associated with the external network beyond the AN (such as, AAA
and PDSN). Finally, the blocks do not include any PPP authentication failures since the
PPP negotiation between the PDSN and the AT occurs on the traffic channel after a
connection is already established. The blocks may include 1xEV-DO Access
Authentication failures, but the current recommendation is to turn the feature off; even if
enabled, such failures are likely to be rare.
Formula
AT_INIT_CONN_REQ -
DO AT-Initiated Connection Blocking Ratio (%) = ------------------------------------ X 100
AT_INIT_CONN_REQ
Count Definitions

Connection Requests

Formula
............................................................................................................................................................................................................................................................
AN_INIT_CONN_REQ
Count Definitions
AN_INIT_CONN_REQ

Formula
DO AT-Initiated Ineffective Call Rate (%) = -------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
............................................................................................................................................................................................................................................................
= AT initiated Connection attempt failures - no response to traffic
channel assignment
= AT initiated Connection attempt failures - no traffic channel
AT_INIT_CONN_REQ

Formula
Count Definitions
............................................................................................................................................................................................................................................................

AT_INIT_CONN_REQ= 1xEV AT Initiated Connection Requests
AN_INIT_CONN_REQ= 1xEV AN Initiated Connection Requests

setup failure.
............................................................................................................................................................................................................................................................
Formula
Count Definitions
= 1xEV Traffic Channel Assignments for AN Initiated Connection Requests

Formula
DO AT-Initiated RF failure rate (%) = --------------------------------------------------- X 100
Count Definitions
............................................................................................................................................................................................................................................................
= 1xEV Traffic Channel Assignments for AT Initiated Connection Requests
Formula
Count Definitions
AT initiated connection attempt failures - no resources available
AT initiated Connection attempt failures - no traffic channel confirmation
received
AT initiated Connection attempt failures - rev link not acquired
AT initiated Connection attempt failures - other failures
............................................................................................................................................................................................................................................................
AN initiated connection attempt failures - no resources available
AN initiated Connection attempt failures - no traffic channel confirmation
received
AN initiated Connection attempt failures - rev link not acquired
AN initiated Connection attempt failures - other failures

Formula
AT_INIT_CONN_ATTMPT_FAIL_NO_ TCC_RCVD +
Count Definitions
............................................................................................................................................................................................................................................................

Assignment
Formula
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD)
............................................................................................................................................................................................................................................................
Count Definitions
AAN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES

............................................................................................................................................................................................................................................................
Formula
(AN_INIT_CONN_ATMPT_FAILED_OTH_FAILURES +
DO Conn Attempt Fail % - Other = ------------------------------------------------------- X 100
Count Definitions
............................................................................................................................................................................................................................................................
Call Drop Metrics

............................................................................................................................................................................................................................................................

Formula
Count Definitions


............................................................................................................................................................................................................................................................







............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Data Re-Transmission rate

in RLP NAKs.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
channel.
1xEV-DO Reverse Link Data Re-Transmission Rate

perfectly fine.
Formula
MISSING_RLP_REQ_RTC
RLP_RXED_RTC
Count definitions

............................................................................................................................................................................................................................................................
1xEV-DO Reverse Link Re-Transmission Failure Rate

Formula
MISSING_RLP_REQ_RTC
Count definitions

retransmit it.
MISSING_RLP_REQ_RTC = RLP Octets for retransmission on the reverse link.

............................................................................................................................................................................................................................................................

MAC layer.
Formula
8 * 10 ^ 6
Count definitions
(1024 bits/packet)
............................................................................................................................................................................................................................................................
kbps - long format (2048 1024 bits/packet)
= Total MACpackets transmitted on forward traffic channels 921.6
= Total MAC packets transmitted on forward traffic channels 1843.2

............................................................................................................................................................................................................................................................
higher rates.
............................................................................................................................................................................................................................................................
hardware, etc.).
milliseconds).
Formula
Count definitions
............................................................................................................................................................................................................................................................
kbps - long format (1024bits/packet)
EVM_TOTAL_BUSY_PCNT_SLOTS
= Percentage of physical layer slots in the measurement hour used for
............................................................................................................................................................................................................................................................

users.
the loading.
Formula
Count definitions
get percentage)
............................................................................................................................................................................................................................................................

per second.
Formula
Count Definitions
............................................................................................................................................................................................................................................................


megabytes.
Formula
Count Definitions
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Data Volume (MB)

Formula
(256 *REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
DO Reverse link data volume (MB) = --------------------------------------------------- X 100
8 * 10^6
Count Definitions
= Number of 9.6 kbps reverse link frames (256 bits/frame)
............................................................................................................................................................................................................................................................

rates.
Formula
DO Reverse link burst rate (kbps) = --------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions

level.
Formula
DO Reverse Frame Error Rate (%) = --------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions


............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Success Rate - Requesting Sector

This metric gives the success rate for soft/softer handoffs from the requesting sector
("hand-outs"). The peg counts are defined on a per sector-carrier basis.
Formula
DO SSO Handoff Success Rate Requesting Sector (%) = ------------------------------ X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
SO_SOR_HOFF_ATTMPT =
This count is the number of soft/er handoff attempts being processed. If
there are multiple triggers in a RUM that are being acted upon in a single
TCA, then the count is pegged only once. Note that the count is pegged
even if the RUM with an add trigger is discarded because the connection is
already at the maximum number of active set legs allowed and there are no
suitable pilots in the active set that can be dropped as part of the same
TCA.
All of these handoff counts are pegged on the sector that received Route Update message,
i.e., the DRC-pointed sector (also known as requesting or source sector).
SO_SOR_HOFF_FAIL NO_RESOURCE =
Soft-Softer HO Attempt failure due to the AN's inability to send a TCA
because the candidate sector being added is already supporting the
maximum number of connections allowed.
SO_SOR_HOFF_FAIL_NO_AT_RSP =
Soft-Softer HO Attempt failure due to no response from the AT
SO_SOR_HOFF_FAIL_OTHER_REASON =
Soft-Softer HO Attempt failure due to other reasons
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Success Rate - Target Sector

This metric gives the success rate for soft/softer handoffs to the target sector ("hand-ins").
This metric is new in R24 and the peg counts are defined beginning in R24. Note that the
number of handoff attempts from the requesting sector will, in general, not equal the
number of handoff attempts at the target sector.
Formula
SO_SOR_HOFF_ATTMPT_TARGET -
(SO_SOR_HOFF_FAIL_NO_RESOURCE_TARGET +
SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET +
SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET +
SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET)
DO SSO Handoff Success Rate Target Sector (%) = ----------------------------------- X 100
SO_SOR_HOFF_ATTMPT
Count Definitions
SO_SOR_HOFF_ATTMPT_TARGET =
Soft-Softer HO Attempt at the target sector-carrier
SO_SOR_HOFF_FAIL NO_RESOURCE_TARGET =
Soft-Softer HO Attempt failure at the target sector-carrier due to no
resources
SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET =
response from the AT
SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET =
Soft-Softer HO Attempt failure at the target sector-carrier due to other
reasons prior to traffic channel assignment
SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET =
reasons after traffic channel assignment
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Blocking Rate - Requesting Sector (due to no resources)

This metric gives the percentage blocking for soft/softer handoffs measured at the
requesting sector. Handoff blocking is a category of soft/er handoff failures that results in
AN not issuing a TCA even though the RUM presented a valid handoff trigger that
normally would have resulted in an active set change.
The soft/er handoff blocks, in general, are errors that occur entirely within the AN. Since
there is no messaging involved with the AT or an element outside the AN between the time
a RUM is received and a TCA is sent, there is little vulnerability from these outside
sources.
The handoff blocks may occur because the candidate sector is already at its maximum
allowed connections (controlled via translations) or there is some trouble allocating
resources at the candidate cell (message exchange issues between the RNC and the cell).
If a handoff is prevented because of a full active set (applies in case of handoff adds), this
is not even counted as a handoff attempt, so it is not taken into the metric computation.
Instead, it is captured as a separate peg count to reflect optimization needs.
One point to note is that the handoff blocks for most part apply to adds. There is no
allocation to be made for drops - any issues with the allocation process might have already
prevented the add itself.
The peg counts are defined on a per sector-carrier basis and are pegged at the requesting
sector. The formula is revised in R25 to more closely match other blocking formulae and
is applicable to all prior releases.
The relative distribution of individual peg counts that contribute to the blocking can be
seen from SO_SOR_HOFF_FAIL_NO_RESOURCE,
SO_SOR_HOFF_FAIL_OTHER_PRETCA and
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED.
Formula
DO HO Blocking Rate (%) =
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED -
SO_SOR_HOFF_ATTMPT_TCA_SENT
----------------------------------------------------------------------------------------------- X 100
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED
Count Definitions
Soft-Softer HO Attempt
............................................................................................................................................................................................................................................................
SO_SOR_HOFF_ATTMPT_TCA_SENT =
This count is pegged if upon inspecting a RUM from the AT, the AN
decides to perform soft/er handoff. If the TCA allocation process succeeds
(only needed for an add at the candidate cell, for drop traffic channel
resource de-allocation is performed after receiving TCC), the AN sends
TCA to apprise the AT of the new active set. When the TCA is sent, AN
pegs the SO_SOR_HOFF_ATTMPT_TCA_SENT count. By definition, it
signifies a successful traffic channel resource allocation, but pending TCC
from the AT.
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED =
Number of times a soft/softer handoff request cannot be processed because
the total number of legs already has reached the maximum specified by the
translation. Beginning in R25, handoff attempts will also be pegged when
the maximum number of legs is reached
1xEV-DO Soft/Softer Handoff Blocking Rate - Target Sector (due to no resources)

This metric gives the percentage blocking for soft/softer handoffs measured at the target
sector. The peg counts are defined on a per sector-carrier basis and are pegged at the target
sector.
The formula is revised in R25 to more closely match other blocking formulae and is
applicable to R24.
seen from SO_SOR_HOFF_FAIL_NO_RESOURCE_TARGET,
SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET and
Formula
DO HO Blocking Rate - Target Sector(%) =
SO_SOR_HOFF_ATTMPT_TCA_SENT_TARGET
--------------------------------------------------------------------------------------------- X 100
SO_SOR_HOFF_ATTMPT_TARGET
Count Definitions
SO_SOR_HOFF_ATTMPT_TARGET = Soft-Softer HO Attempts
SO_SOR_HOFF_ATTMPT_TCA_SENT_TARGET =
TCA sent in response to a soft/softer handoff attempt
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff RF Failure Rate - Requesting Sector

This metric provides the rate at which handoffs attempts fail from the requesting sector
perspective after the AN has sent a handoff TCA to the AT and the AN has timed out
waiting for a TCC in response. Such failures are caused by RF impairments, either
because the AT could receive the TCA or the AN could not decode the TCC, despite
multiple retries by each side.
The metric includes all soft and softer handoff attempts. It includes handoff adds and
drops. When multiple adds and/or drops are performed as part of a single TCA event, it is
counted as one handoff attempt.
sector.
This metric is new in R25 and is applicable to releases R24 and later.
Formula
DO HO RF Failure Rate Requesting Sector (%) =
------------------------------------------------------------------------------ X 100
Count Definitions
Soft-Softer HO failures due to no response from the AT in response to a
TCA sent by the AN.
TCA sent in response to a soft/softer handoff request.
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff RF Failure Rate - Target Sector

This metric provides the rate at which handoffs attempts fail from the target sector
The peg counts are defined on a per sector-carrier basis and are pegged at the target sector.
Formula
DO HO RF Failure Rate Target Sector (%) =
SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET
--------------------------------------------------------------------------------- X 100
Count Definitions
TCA sent by the AN.

This metric gives the success rate for all Inter-subnet idle transfers (Prior Session, Assign
First and Color Code methods). As discussed previously, Inter-RNC Idle handoffs differ
from intra-RNC handoffs in that the former entail a series of messages exchanged between
the AT and the cell on the new RNC as well as between the old and the new RNCs. The
messaging is required to assign a new UATI for use on the new RNC, to transfer any
existing PPP session over from the PCF on the old RNC, and to clean up the old UATI
session on the old RNC. The process is subject to failures from a variety of sources
including RF conditions (poor RF, rapid ping-ponging), provisioning errors on the AN,
misalignment of AT information in the two RNCs, or issues within the AT itself.
............................................................................................................................................................................................................................................................
This type of failure often means an extra delay in completing the handoff - either in
obtaining the new UATI or getting the PPP session plumbed through the new PCF. Unless
the user is in a terminally bad environment (RF wise or an unreachable RNC), the idle
handoff usually completes on its own after a few retries without requiring manual
intervention.
The other thing that mitigates the impact is that in many cases these failures are
completely transparent to the end user. The user would feel the impact only if it wishes to
access the network while in a dormant state right after the inter-RNC idle handoff trigger.
Hence, a relatively high rate of inter-RNC idle handoff failures may not be that egregious.
Note that there is a common misconception on inter-RNC active transfers. When a user
crosses an RNC border during an active connection, legs are added and/or dropped similar
to any other soft/er handoff. The TP that was in control of the connection on the old RNC
continues to be in charge even if the user drives in further and the AT is entirely served by
cells on the new RNC. This is conceptually very similar to the inter-MSC packet data soft
handoffs in the Alcatel-Lucent 2G/3G1x product. The inter-RNC idle handoff does not
occur until after the connection is released and the AT has gone dormant. Hence, it is fair
to say that inter-RNC handoff idle failures that are of short-term nature (such as due to
poor RF conditions or mismatch in the RNCs about the AT state, as opposed to a broken
backbone connectivity between the two RNCs) have little or no impact on the performance
of an active connection.
An inter-RNC idle handoff may fail for a variety of reasons - there are several peg counts
to capture the individual causes. The underlying cause may be inadequate RF signal
(break down in messaging between AN and AT), frequent ping-ponging between a pair of
RNCs at the border, incorrect entries in the database that maps A11 IP address with RNC
Color Code (applies only to color code method), incorrect A11 IP address of a RNC in
translations (can apply to either color code or assign first method), connectivity issues
between a pair of RNCs or between the target RNC and the old PDSN, or in rare instances
a blocking (the target RNC is already serving the maximum allowed UATI sessions).
This metric was revised in R24 to account for the Prior Session method. The peg counts
are defined on a per sector-carrier basis.
............................................................................................................................................................................................................................................................
Formula
DO Int sub idle xfer success rate (%) =
(INT_SUBNET_IDL_TRFR_ATTMPT +
INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS -
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD +
ISBNT_IDL_TRFR_FAIL_PRIOR_SES_NO_RSP +
INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ)
-------------------------------------------------------------------------------------------------- X100
INT_SUBNET_IDL_TRFR_PRIOR SES_ATTEMPTS)
Count Definitions
INT_SUBNET_IDL_TRFR_ATTMT =
This is the total number of inter-subnet or inter-RNC idle transfer attempts
pegged on the new RNC (target RNC) for the assign first and color code
methods. The count is pegged when the target RNC receives a UATI
Request message that contains a UATI assigned by a different RNC. The
count is not pegged for UATI Request messages received with a RATI
instead.
INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS =
pegged on the new RNC (target RNC) for the prior session method. The
count is pegged when the target RNC receives a UATI Request message
that contains a RATI assigned by a different RNC.
IBNT_IDL_TRFR_FAIL_NO_RSP_PRV_SBNET =
This is the number of inter-RNC idle handoffs that fail because the new
RNC did not receive response from the old RNC in order to carry out the
transfer. This could happen either because the old RNC is not reachable
(such as, due to temporary inter-RNC link outages), or the new RNC does
not have proper reachable PCF A11 IP address of the old RNC.
............................................................................................................................................................................................................................................................
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN =
This is the number of inter-RNC idle handoff failures that occur because
the PCF on the new RNC could not establish an A11 (also known as R-P)
connection with the original PDSN. In essence, a new UATI is assigned
successfully but the connection to the PDSN failed subsequently.
INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON =
As with other failures for connection and soft/er handoff failures, this
accounts for all inter-RNC idle handoff attempts that failed for reasons not
accounted for by the other specific failure counts. One scenario where this
is seen quite often is the ping pong scenario. When RNC2 times out
waiting for the UATI Complete message in response to the UATI
Assignment message because the AT has moved to a different RNC (RNC1
or RNC3), it declares it as an Other failure. Of course, the timeout may also
happen due to poor RF conditions or if RNC2 did not send the UATI
Assignment message with proper message sequence number (often is the
case with the Assign First method where RNC has to "guess" a sequence
number since it has not yet communicated with the old RNC and has no
way of knowing the last sequence number used to communicate with the
AT). This count may also reflect blocking where the target RNC has no
more spare UATIs to assign to the requesting AT.
ISBNT_IDL_TRFR_FAIL_SRC_ IP_ADR_NT_FOUND =
This count is pegged when, as the name suggests, the PCF A11 IP address
of the old RNC is not provisioned on the new RNC. The problem is
applicable only for the Color Code method of the inter-RNC Idle handoff,
which requires the new RNC to perform a look up of old RNC's IP address
in a locally stored mapping table. The lookup is performed using the color
code retrieved from the old UATI sent by the AT as part of the UATI
Request message. If the Assign First method is used instead, the AN first
assigns the UATI to the AT and as part of the UATI Assignment message,
instructs the AT to directly report back the old RNC's PCF A11 address.
Using this information, the new RNC then attempts to initiate the session
transfer from the old RNC. In this case, no lookup table is needed at the
new RNC, and hence this type of failure does not apply in case of the
Assign First method.
............................................................................................................................................................................................................................................................
Another scenario where this count may get pegged for either Assign First
or Color Code method is when the PDSN's IP address reported in the A13
Session Information Response message by the source RNC is invalid (that
is, 255.255.255.255 or NULL).
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD =
This failure is pegged when the new RNC receives a A13 Reject message
from the old RNC in response to a session transfer request. One scenario
where this may occur is when the AT has gone back to the old RNC (call it
RNC 1) or a third RNC (call it RNC 3) before it could send a UATI
Complete to the new RNC (call it RNC 2). In this case, the new RNC
(RNC 2) does not yet consider itself to be in control of AT's session and
hence, would reject the subsequent session transfer request (from RNC1 or
RNC3 in this rapid handoff scenario).
ISBNT_IDL_TRFR_FAIL_PRIOR_SES_NO_RSP =
Number of Inter Subnet Idle Transfer failures due to no response from the
previous subnet using the Prior Sessions method.
INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ =
Number of Inter Subnet Idle Transfer failures due to a failure to find the
target AN because of insufficient information in the Configuration Request
message using the Prior Sessions method.
............................................................................................................................................................................................................................................................
Performance Metrics for Release 24 Capacity Management Performance Metrics

............................................................................................................................................................................................................................................................

1xEV-DO.
level. Although the peg count name is "Average Active Connections" it is actually the sum
of all the total connections based on a 10 second scan.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

Formula
PCF_INIT_REACT_FAIL
DO PCF Reactivation rate AN Init (%) = ------------------------------------------------ X 100
Count Definitions
end user.
PDSN.
............................................................................................................................................................................................................................................................

link.
handoff.
failures.
Formula
RP_CONN_ATTMPTS -
RP_CONN_FAIL
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS =
............................................................................................................................................................................................................................................................
RP_CONN_FAIL =
service).
............................................................................................................................................................................................................................................................
Prospect for Alcatel-Lucent
Release 24

............................................................................................................................................................................................................................................................
The purpose of this chapter is to provide definitions for new Prospect Primitive
Calculations (PCALCs) that support performance metrics for 1xEV-DO for FMS R24.
Existing PCALCs supporting 1xEV-DO performance metrics that did not change in ECP
R24 are not included in this chapter. For PCALC information supporting previous
releases, refer to:
Chapter 4, 1xEV-DO Metrics in Watchmark Prospect for Release 22
Chapter 6, 1xEV-DO Metrics in Watchmark Prospect for Release 23.
calculation.
percentages.
The PCALCs defined in the chapter are targeted to be implemented in Prospect R24.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- 1xEV-DO Performance Metrics Modified in
Lucent Release 24 Prospect R24
1xEV-DO Performance Metrics Modified in Prospect R24

............................................................................................................................................................................................................................................................
1xEV-DO MAC Data Transmitted on Forward Link (MBytes)
Prospect Traffic Report Entity: 1xEV_SectorCarrier, 1xEV_Sector

Valid Releases: 1xEV-DO R21 and later
DO_TotDataXmtFwdLnk = 0.000128 * (FwdPkts38kbps + FwdPkts76kbps +
FwdPkts153kbps + FwdPkts307kbps + FwdPkts614kbps + FwdPkts307Lkbps +
FwdPkts614Lkbps + FwdPkts1228kbps + FwdPkts921kbps + FwdPkts1843kbps +
FwdPkts1228Lkbps + FwdPkts2457kbps)
Notes:
1. Beginning in 1xEV-DO R24, the counts in this equation are at the sector carrier level. In
prior releases, they are at the sector level.
2. 0.000128 = 1024 / (8 * 1000000). 1024 represents the number of bits in a packet, 8 is
the number of bits per byte and 1000000.0 converts from bytes to MBytes.
3. Mapping between Prospect names and 1xEV-DO Names:
Prospect Traffic
FwdPkts38kbps EVM_FWD_PACKETS_38_4_TOTAL_COUNT 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................
Average Forward Link Burst Rate (kbps)

This metric was improperly defined in R23 and is marked invalid in Prospect R24.
DOp_AvgBrstFwdLnk is marked Invalid
Percent Forward Link Bandwidth Used for Traffic

Valid Releases: Cell/RNC R22 and later
DOp_BndWidthTrfFwdLnk = 0.000001 * PcntSltsUsrTrf
Notes:
1. Beginning in 1xEV-DO R24, the count in this equation is at the sector carrier level. In
prior releases, it was at the sector level.
2. In this equation, the raw peg counts needs to be divided by 1000000.0 to get a
percentage value. To avoid a bug in the report generator when there is a constant term in an
aggregated calculation, the count is multiplied by .000001 instead.
Prospect Traffic
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................
1xEV-DO Total Data Transmitted on Reverse Link (MBytes)

The only change required for this metric is to define the metric at the 1xEV_SectorCarrier
level
DO_TotDataXmtRevLnk = (256 * RevOutLoopPCFrCt96 + 512 *
RevOutLoopPCFrCt192 + 1024 * RevOutLoopPCFrCt384 + 2048 *
RevOutLoopPCFrCt768 + 4096 * RevOutLoopPCFrCt1536) / 8000000.0
Notes:
1. Beginning in 1xEV-DO R24, the counts in this equation are at the sector carrier level. In
prior releases, they are at the sector level.
Prospect

Valid Releases: FMS R23
DOp_AvgActSess = AvgActiveConnAP / 360.0
Notes:
Prospect
Traffic
AvgActiveConnAP AVG_ACTIVE_CONN_PER_AP 1xEV_AP
............................................................................................................................................................................................................................................................

Prospect Traffic Report Entity: 1xEV_Sector and 1xEV_SectorCarrier
DOp_IntSubIdlTrfSuc = 100.0 * (IntSubIdleTrfrAtt + IntSubIdlTrnsfPriorSesAtt -
(IntSubIdlTrfFl_NoRspPrev + IntSubIdlTrfFl_OrigPDSNcntConn +
IntSubIdlTrfFl_RejMsgRcv + IntSubIdlTrfFl_Other + IntSbIdlTrfrFl_SrcIpAd +
IntSubIdlTrnsfPriorSesBadRq + IntSubIdlTrnsfPriorSesNoRsp)) / (IntSubIdleTrfrAtt +
IntSubIdlTrnsfPriorSesAtt)
Notes:
Prospect
Traffic
Carrier
IntSubIdlTrfFl_NoRspPrev ISBNT_IDL_TRFR_FAIL_NO_RSP_PRV_SBNET
IntSubIdlTrfFl_OrigPDSNcntConn ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN
IntSubIdlTrfFl_RejMsgRcv ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD
IntSbIdlTrfrFl_SrcIpAd ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_NT_FOUND
IntSubIdlTrnsfPriorSesAtt INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS
IntSubIdlTrnsfPriorSesBadRq INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ
IntSubIdlTrnsfPriorSesBadRq INT_SUBNET_IDL_TRFR_PRIOR_SES_NO_RSP
............................................................................................................................................................................................................................................................

Prospect Traffic Report Entity: 1xEV_SectorCarrier and 1xEV_Sector
DOp_SessSUSucc = 100.0 * (SessnSUUATICompMsgRcvd +
SesSUIntSubUATICmpMsgRcvd) / (SessnSURq + IntSubIdleTrfrAtt)
Notes:
Prospect
Traffic
SessnSUUATICompNsgRcvd SESSION_SETUP_UATI_COMPLETE_MSG_RCVD 1xEV_Sector
Carrier
SesSUIntSubUATICmpMsgRcvd SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD
IntSubIdleTrfrAtt INT_SUBNET_IDL_TRFR_ATTMPT
SessnSURq SESSION_SETUP_REQ
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- New 1xEV-DO Performance Metrics in Prospect
Lucent Release 24 R24
New 1xEV-DO Performance Metrics in Prospect R24

............................................................................................................................................................................................................................................................
Average Forward Link Data Rate (kbps)

Prospect Traffic Report Entity: 1xEV_SectorCarrier
DO_AvgFwdL_kbps = (8000.0 * DO_TotDataXmtFwdLnk) / (0.0216 * 0.001667 *
PcntSltsUsrTrf)
Notes:
1. 8000.0 converts the numerator from MBytes to kb. In the denominator, 0.001667 is the
length of a slot in seconds and 0.0216 is the total slots in an hour divided by 10E8 (10E8 is
required to convert PcntSltsUsrTrf to a fraction of slots used for traffic).
Prospect Traffic
DO_TotDataXmtFwdLnk Prospect PCALC 1xEV_SectorCarrier
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS

DO_RLPFwdL_kbps = (222.17778 * RLPTXFTC) / (PcntSltsUsrTrf)
Notes:
1. RLPTXFTC has units of octets. Multiply by 8 to convert to bits and divide by 1000 to
get kilobits. In denominator , there are 2160000 slots per hour, each of length .001667 secs
and PcntSltsUsrTrf is divided by 10E8 to get the fraction of slots used for traffic.
Prospect Traffic
RLPTXFTC RLP_TX_FTC 1xEV_SectorCarrier
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS
............................................................................................................................................................................................................................................................
1xEV-DO Average User Forward Link Data Volume (MBytes)

DO_RLPFwdLUsr_MB = RLPTXFTC / (1000000.0 * AvgActCon)
Notes:
1. RLPTXFTC has units of octets. Dividing by 1000000.0 converts it to MBytes
Prospect Traffic
RLPTXFTC RLP_TX_FTC 1xEV_SectorCarrier
AvgActCon AVG_ACTIVE_CONN_PER_SECTOR / 360.0
Soft-Softer Handoff Blocking Rate- Target Sector

DOp_SftSftrHOBlk_Tgt = 100.0 * (SftSftrHOAtt_Tgt - SftSftrHOAttTCASent_Tgt) /
SftSftrHOAtt_Tgt
Notes:
1. New terms in bold.
Prospect
Traffic
SftSftrHOAttTCASent_Tgt SO_SOR_ATTMPT_TCA_SENT_TARGET 1xEV_Sector
Carrier
SftSftrHOAtt_Tgt SO_SOR_HOFF_ATTMPT_TARGET
............................................................................................................................................................................................................................................................

DOp_SftSftrHOSuc_Tgt = 100.0 * (SftSftrHOAtt_Tgt - (SftSftrHOFlNoResc_Tgt +
SftSftrHOFlNoATRsp_Tgt + SftSftrHOFlOther_PreTCA_Tgt +
SftSftrHOFlOther_PostTCA_Tgt)) / SftSftrHOAtt_Tgt
Notes:
Prospect Traffic
SftSftrHOFlNoResc_Tgt SO_SOR_FAIL_NO_RESOURCE_TARGET 1xEV_SectorCarrier
SftSftrHOFlNoATRsp_Tgt SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET
SftSftrHOFlOther_PreTCA_Tgt SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET
SftSftrHOFlOther_PostTCA_Tgt SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- Existing xEV_Sector Metrics Replicated as
Lucent Release 24 1xEV_Sector Carrier Metrics
Existing xEV_Sector Metrics Replicated as 1xEV_Sector Carrier

Metrics
............................................................................................................................................................................................................................................................
Beginning in 1xEV-DO R24, there will be support for up to three carriers and Prospect
will begin loading sector-carrier counts instead of sector counts. Every sector count in
Prospect R23 will be a sector-carrier count in R24.
Several metrics were defined at the 1xEV_Sector level in Prospect R23. These metrics
need to be replicated at the 1xEV_SectorCarrier level in Prospect R24. For each metric,
the names of the counts, the metric equation, the column headings, the GUI description
and the PDR description are all unchanged; they are merely replicated at the
1xEV_SectorCarrier level. The descriptions of those calculations will not be duplicated in
this R24 chapter
Note that three of the R23 metrics were modified and these metrics are described in
Section 1 above for both the 1xEV_Sector and the 1xEV_SectorCarrier level. These
PCALCs are named
1. DO_TotDataXmtFwdLnk
2. DOp_AvgBrstFwdLnk
3. DOp_BndWidthTrfFwdLnk
The following 1xEV_Sector PCALCs introduced in Prospect R23 will be replicated at the
1xEV_SectorCarrier level in Prospect R24. All attributes of each PCALC (name, column
heading, GUI description, PDR description, aggregator type, etc) will be the same as will
the calculation and the names of the counts in the calculation. The only change will be the
traffic level where the PCALC is defined.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- Existing xEV_Sector Metrics Replicated as
Lucent Release 24 1xEV_Sector Carrier Metrics
1. DOp_SessSUSucc
2. DOp_CnctBlkANInit
3. DOp_CnctBlkATInit
4. DOp_DropCall
5. DOp_InefCallAttANInit
6. DOp_InefCallAttATInit
7. DOp_InefCallAttTotal
8. DOp_RFFailANInit
9. DOp_RFFailATInit
10. DOp_EstCall
11. DOp_CnctFlNoRL
12. DOp_CnctFlCnfgNeg
13. DOp_CnctFlNoResrc
14. DOp_CnctFlNoRspTCA
15. DOp_CnctFlNoTCCmpRcv
16. DOp_CnctFlOther
17. DOp_ReTXFwdLnk
18. DOp_ReTXRevLnk
19. DOp_ReTXFailRevLnk
20. DO_TotDataXmtRevLnk
21. DO_AvgBrstRevLnk
22. DOp_SftSftrHOBlk
23. DOp_SftSftrHOSuc
24. DOp_IntSubIdlTrfSuc
25. DO_TrfChnUsg_erl
26. DOp_RevFER
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- New Metrics Retrofitted to R24
Lucent Release 24
New Metrics Retrofitted to R24

............................................................................................................................................................................................................................................................

Notes:
Prospect Traffic


Notes:
............................................................................................................................................................................................................................................................
Lucent Release 24
Prospect Traffic

Notes:
Prospect Traffic


............................................................................................................................................................................................................................................................
Lucent Release 24
Notes:
Prospect Traffic
1xEV-DO Soft/Softer Handoff RF Failure Rate-Target Sector

Prospect Traffic Report Entity: 1xEV_Sector, 1xEV_SectorCarrier
DOp_SftSftrHOFlRF_Tgt = 100.0 * SftSftrHOFlNoATRsp_Tgt /
SftSftrHOAttTCASent_Tgt
Notes:
Prospect Traffic
SftSftrHOFlNoATRsp_Tgt SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET 1xEV_SectorCarrier

Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................
Lucent Release 24

Notes:
Prospect Traffic

RevOutLoopPCFrCt192
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................
Lucent Release 24

RevOutLoopPCFrCt384
Notes:
Prospect Traffic

RevOutLoopPCFrCt768
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................
Lucent Release 24

Notes:
Prospect Traffic

Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................
Lucent Release 24

Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose
Changes in this Release
Metrics added:
Session Assignment to Request Rate
Established Connection Rate - Peg
Fast Connect Success Rate - Peg
AN-Initiated Connection Blocking Ratio due to No Resources
AT-Initiated Connection Blocking Ratio due to No Resources
AN-Initiated Ineffective Connection Attempt Rate - Peg
AT-Initiated Ineffective Connection Attempt Rate - Peg
Total Ineffective Connection Attempt Rate - Peg
Paging Success Rate
Paging Failure Rate due to RF Failures
RAN Authentication Success Rate
Dropped Connection Rate - Peg
Soft/Softer Handoff RF Failure Rate - Requesting Sector
Soft/Softer Handoff RF Failure Rate - Target Sector
Average Reverse Link Power Control Setpoint (separate metrics for each rate)
Metrics revised:
AN-Initiated Connection Blocking (title change only)
AT-Initiated Connection Blocking (title change only)
AN-Initiated Ineffective Connection Attempt Rate
AT-Initiated Ineffective Connection Attempt Rate
Total Ineffective Connection Attempt Rate
............................................................................................................................................................................................................................................................

Soft/Softer Handoff Blocking Rate - Requesting Sector
Soft/Softer Handoff Blocking Rate - Target Sector
Added section describing new Active Connection Histogram peg counts.
Replaced connection failure percentage metrics with section describing detailed peg
counts to be used for monitoring individual failure reasons
Categories and Metrics
The following performance metrics are provided:
a. Session Management Metrics
Average Active Sessions Metric
b. Packet Data Reactivation Metrics
R-P Connection Success Rate
a. Connection Setup
Established Connection Rate
Fast Connection Rate - Peg
AN-Initiated Connection Blocking Rate due to no resources
AT-Initiated Connection Blocking Rate
AT-Initiated Connection Blocking Rate due to no resources
AN-Initiated Ineffective Connection Attempt Rate - Peg
AT-Initiated Ineffective Connection Attempt Rate - Peg
Paging Success Rate
............................................................................................................................................................................................................................................................
b. Connection Drop
Dropped Connection Rate
c. Handoff
d. Data Throughput
Average Forward Link MAC Data Rate (kpbs)
Reverse Link RLP Data Throughput (kbps)
e. Error Statistics
f. Power Control
Average Reverse Link Power Control Setpoint - 0 kbps
Average Reverse Link Power Control Setpoint - 9.6 kbps
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
Formula
-------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ = Session Set Up Request (new & prior)
Inter-subnet idle transfer attempts (assign first & color code)
............................................................................................................................................................................................................................................................
Session Set Up - UATI Complete Message Received (new & prior). Pegged
when the AT acknowledges a UATI assignment message sent by the AN in
response to a UATI request.
code)
1xEV-DO Session Assignment to Request Rate

The metric is a measure of successful UATI allocation, that is, ability to obtain necessary
resources within the AN and send out a UATI Assignment message. A complementary
metric (1 minus this ratio) essentially represents session blocking.
Note that a successfully allocated session may still fail subsequently due to RF conditions,
AT issues, inability to negotiate to mutually agreeable settings, etc.
Normally, the AN should have no problem allocating a UATI to the AT as long as the
operator engineers the network to keep the requested number of sessions from frequently
exceeding the maximum number of sessions limit, and, the source and old RNCs can
communicate & exchange proper information in case of Color Code method of inter-RNC
idle handoff. A ratio less than 1 is reflective purely of a AN issue; no over the air
messaging is involved.
This metric is new in R25 and is applicable to prior releases.
Formula
DO Session Assignment to Request Rate (%) =
SESS_SETUP_UATI_ASSGNMT_MSG_SENT +
SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT
----------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ =
Session Set Up Request (pegged when the AN receives a UATI request
message for new & prior session setups)
............................................................................................................................................................................................................................................................
SESS_SETUP_UATI_ASSGNMT_MSG_SENT =
Session Set Up - UATI Assignment Message Sent to AT upon receipt of a
UATI request message (new & prior sessions)
SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT =
Session Set Up - UATI Assignment Message Sent (assign first & color
code)
1xEV-DO Average Active Sessions

Beginning with Release 23, this metric provides the average number of active sessions
Formula
360
Count Definitions
Number of active sessions on an AP (sessions with an active PPP session).
This count is pegged every 10 seconds during the measurement interval
and added to the previous total. Therefore, the result is divided by 360 to
get the approximate average over the measurement interval. Note that the
measurement interval is not exactly one hour, so the calculation is
approximate.
............................................................................................................................................................................................................................................................

intervention.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------------------------- X100
Count Definitions
instead.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
is, 255.255.255.255 or NULL).
1xEV-DO RAN Authentication Success Rate

This metric gives the percentage of successful RAN Authentication attempts. RAN
authentication takes place when a user first establishes a session on the network. The peg
counts are defined on a per-TP basis and can be rolled up to the RNC or Service Node.
The metric is new in R25 and is effective beginning with R25.
There are several individual peg counts that give visibility into the different causes of
RAN authentication failures. These counts are defined in the 1xEV-DO service
measurements manual (401-614-326). These counts should be monitored by service
providers, especially if the failure rate is high.
Formula
DO RAN Authentication Success Rate (%) =
RAN_AUTH_SUCCESSFUL_ATTMPT
--------------------------------------------------- x 100
RAN_AUTH_TOTAL_ATTMPT
............................................................................................................................................................................................................................................................
Count Definitions
RAN_AUTH_SUCCESSFUL_ATTMPT =
Number of successful RAN authentication attempts
RAN_AUTH_TOTAL_ATTMPT =
Total number of RAN authentication attempts
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
1xEV-DO PCF Reactivation Rate Success Rate for AN-Initiations

Formula
DO PCF Reactivation Success rate AN Init (%) =
PCF_INIT_REACT_ATTMPT - PCF_INIT_REACT_FAIL
------------------------------------------------------------------------------ X 100
Count Definitions
end user.
PDSN.
............................................................................................................................................................................................................................................................
1xEV-DO R-P Connection Success Rate

link.
handoff.
failures.
The peg counts are defined on a per TP basis. The name of this metric was changed in
R25.
Formula
DO RP conn success rate (%) =
RP_CONN_ATTMPTS - RP_CONN_FAIL
------------------------------------------------------------------------------ X 100
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS =
............................................................................................................................................................................................................................................................
RP_CONN_FAIL =
service).
............................................................................................................................................................................................................................................................
Performance Metrics for Release 25 Connection Setup Metrics
Connection Setup Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Established Connection Rate

3G1X.
for a Connection.
level. The formula is revised in R25 to account for the separation of the 'other failures' peg
count into pre-TCA and post-TCA counts. The new formula is effective beginning with
R25.
............................................................................................................................................................................................................................................................
Formula
DO Established connection rate (%) =
AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA -
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA -
AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA -
AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA -
----------------------------------------------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
AT_INIT_CONN_REQ =
Connection Request.
attribute set.
............................................................................................................................................................................................................................................................
receiving the TCC.
sector.
AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA =
This is a catch-all for remaining failure reasons that prevent a successful
onnection setup that occur before sending TCA. The reasons may include
internal call processing errors, time outs, message build or send errors,
blocking due to system bottlenecks, etc.
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA =
onnection setup that occur after sending TCA. The reasons may include
receiving the TCC.
sector.
AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA =
onnection setup that occur before sending TCA. The reasons may include
............................................................................................................................................................................................................................................................
blocking due to system bottlenecks,
etc.AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = This is a
catch-all for remaining failure reasons that prevent a successful onnection
setup that occur before sending TCA. The reasons may include internal call
processing errors, time outs, message build or send errors, blocking due to
system bottlenecks, etc.
1xEV-DO Established Connection Rate - Peg

cell level.
The formula is revised for R25 to use the new Established Calls peg counts and is expected
to be more accurate than the old formula. However, it is recommended that customers use
both formulas for a couple of Releases to compare the values obtained by both.
Formula
DO Established call rate - peg (%) =
(AN_INIT_ESTABLISHED_CONN + AT_INIT_ESTABLISHED_CONN
---------------------------------------------------------------------------------------------------X 100
Count Definitions
AN_INIT_ESTABLISHED_CONN = Number of AN-Initiated successful connections
AT_INIT_ESTABLISHED_CONN = Number of AT-Initiated successful connections
............................................................................................................................................................................................................................................................

Formula
DO Fast connect success rate =
------------------------------------------------------------------------------------------------X 100
(FAST_CONNECT)
Count Definitions
FAST_CONNECT =
failures.
preamble.
............................................................................................................................................................................................................................................................
1xEV-DO Fast Connect Success Rate - Peg

connect procedure. The peg counts are defined on a per AP basis and can be rolled up to
the RNC or SN level.
The formula is revised for R25 to use the new Fast Connect Established Calls peg count
and is expected to be more accurate than the old formula. However, it is recommended
that customers use both formulas for a couple of Releases to compare the values obtained
by both.
Formula
DO Fast connect success rate - peg =
FAST_CONNECT_ESTABLISHED_CALLS
--------------------------------------------------------------------------X 100
FAST_CONNECT
Count Definitions
FAST_CONNECT_ESTABLISHED_CALLS =
The number of fast connect procedures that result in an active connection.
1xEV-DO AN-Initiated Connection Blocking Ratio

This metric gives the percentage blocking for AN-initiated connections. It is equivalent to
the Seizure to Assignment Deficit Ratio for terminations in 3G 1x. The peg counts are
The title of this metric was changed in R25 to clarify that it includes all blocking, not only
blocking due to no resources. A new metric was added to calculate blocking due to no
resources.
Formula
DO AN-Initiated Connection Blocking Ratio (%) =
AN_INIT_CONN_REQ - TCA_FOR_AN_INIT_CONN_REQ
-------------------------------------------------------------------------------------------------- X 100
AN_INIT_CONN_REQ
............................................................................................................................................................................................................................................................
Count Definitions
TCA_FOR_AN_INIT_CONN_REQ = Traffic Channel Assignments in response to AN

1xEV-DO AN-Initiated Connection Blocking Ratio Due to No Resources

This metric gives the percentage blocking due to no resources for AN-Initiated
connections. The peg counts are defined on a sector-carrier basis.
This metric is new in R25 to provide the percentage blocking due only to no resources
being available. It is applicable to all prior releases.
Formula
DO AN-Initiated Connection Blocking Ratio - No Resources (%) =
---------------------------------------------------------------------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
AN-initiated connection attempt failures - no resources available
1xEV-DO AT-Initiated Connection Blocking Ratio

Seizure to Assignment Deficit Ratio for originations in 3G 1x. Any connection attempt
............................................................................................................................................................................................................................................................

The peg counts are defined on a per sector-carrier basis. The title of this metric was
changed in R25 to clarify that it includes all blocking, not only blocking due to no
resources. A new metric was added to calculate blocking due to no resources.
Formula
DO AT-Initiated Connection Blocking Ratio (%) =
AT_INIT_CONN_REQ - TCA_FOR_AT_INIT_CONN_REQ
----------------------------------------------------------------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions

Connection Requests
1xEV-DO AT-Initiated Connection Blocking Ratio Due to No Resources

This metric gives the percentage blocking due to no resources for AT-Initiated
connections. The peg counts are defined on a sector-carrier basis.
This metric is new in R25 to provide the percentage blocking due only to no resources
being available. It is applicable to all prior releases.
Formula
DO AT-Initiated Connection Blocking Ratio - No Resources (%) =
---------------------------------------------------------------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions

AT_INIT_CONN_REQ = AT-Initiated Connection Requests
............................................................................................................................................................................................................................................................
1xEV-DO AN-Initiated Ineffective Connection Attempt Rate

peg counts are defined on a per sector-carrier basis. Note that the AN-Initiated established
connection rate is 100 minus this metric. The peg counts are defined on a per sector-
carrier basis and can be rolled up to the cell level.
The formula is revised in R25 to account for the separation of the 'other failures' peg count
into pre-TCA and post-TCA counts. The new formula is effective beginning with R25.
Formula
DO AN-Initiated Ineffective Connection Rate (%) =
AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA
+AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA)
------------------------------------------------------------------------------------------------ X 100
AN_INIT_CONN_REQ
Count Definitions
AN-initiated Connection attempt failures - no traffic channel confirmation
received
AN-initiated Connection attempt failures - rev link not acquired
AN-initiated Connection attempt failures - other failures pre-TCA
AN-initiated Connection attempt failures - other failures post-TCA
............................................................................................................................................................................................................................................................
1xEV-DO AN-Initiated Ineffective Connection Attempt Rate - Peg

peg counts are defined on a per sector-carrier basis. Note that the AN-Initiated established
connection rate is 100 minus this metric.
Formula
DO AN-Initiated Ineffective Connection Rate - Peg (%) =
AN_INIT_CONN_REQ - AN_INIT_ESTABLISHED_CONN
------------------------------------------------------------------------------------------------- X 100
AN_INIT_CONN_REQ
Count Definitions
AN_INIT_ESTABLISHED_CONN = Number of AN initiated successful connections
AN_INIT_CONN_REQ = AN Initiated Connection Requests
1xEV-DO AT-Initiated Ineffective Connection Attempt Rate

peg counts are defined on a per sector-carrier basis. Note that the AT-Initiated established
connection rate is 100 minus this metric. The peg counts are defined on a per sector-
carrier basis and can be rolled up to the cell level.
Formula
DO AT-Initiated Ineffective Connection Rate (%) =
AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA +
AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA)
------------------------------------------------------------------------------------------------ X 100
AT_INIT_CONN_REQ
............................................................................................................................................................................................................................................................
Count Definitions
received
AT-initiated Connection attempt failures - other failures pre-TCA
AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA =
AT-initiated Connection attempt failures - other failures post-TCA
1xEV-DO AT-Initiated Ineffective Connection Attempt Rate - Peg

peg counts are defined on a per sector-carrier basis. Note that the AT-Initiated established
connection rate is 100 minus this metric.
Formula
DO AT-Initiated Ineffective Connection Rate - Peg (%) =
AT_INIT_CONN_REQ - AT_INIT_ESTABLISHED_CONN
------------------------------------------------------------------------------------------- X 100
AT_INIT_CONN_REQ
Count Definitions
AT_INIT_ESTABLISHED CONNECTIONS = Number of AT initiated successful

connections
............................................................................................................................................................................................................................................................
1xEV-DO Total Ineffective Connection Attempt Rate

initiated) that failed. The peg counts are defined on a per sector-carrier basis. The peg
counts are defined on a per sector-carrier basis and can be rolled up to the cell level.
Formula
DO Total Ineffective Connection Rate (%) =
AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA +
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA +
AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA +
----------------------------------------------------------------------------------------------- X 100
Count Definitions
received
............................................................................................................................................................................................................................................................
received
1xEV-DO Total Ineffective Connection Attempt Rate - Peg

the total call success rate is 100 minus this metric.
Formula
DO Total Ineffective Call Rate - Peg (%) =
AN_INIT_ESTABLISHED CONN - AT_INIT_ESTABLISHED_CONN)
------------------------------------------------------------------------------------------------ X 100
Count Definitions
............................................................................................................................................................................................................................................................
AT_INIT_ESTABLISHED_CONN = Number of AT initiated successful connections
AN_INIT_CONN_REQ = AN Initiated Connection Requests

setup failure.
The formula is revised is R25. The new formula is applicable for releases R25 and later.
The prior formula is still applicable for releases R24 and earlier.
Formula
DO AN-Initiated RF failure rate (%) =
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA)
-------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
received
AN initiated Connection attempt failures - reverse link not acquired
AN Initiated connection attempt failures - other reasons post-TCA
TCA_FOR_AN_INIT_CONN_REQ =
Traffic Channel Assignments for AN Initiated Connection Requests

The prior formula is still applicable for Releases R24 and earlier.
Formula
DO AT-Initiated RF failure rate (%) =
-------------------------------------------------------------------------------------------- X 100
Count Definitions
received
............................................................................................................................................................................................................................................................
AT initiated connection attempt failures - other reasons post-TCA
TCA_FOR_AT_INIT_CONN_REQ =
Traffic Channel Assignments for AT Initiated Connection Requests
1xEV-DO Connection Failure Percentage Metrics

The metrics giving the percentage of connection failures for each failure reason have been
deleted as Alcatel-Lucent supported metrics as of R25. The individual failures can be
seen from the following raw peg counts:
Count definitions
received
received
............................................................................................................................................................................................................................................................
1xEV-DO Paging Success Rate

This metric gives the percentage of successful page attempts. The peg counts are defined
on a per AP basis. This metric is effective beginning with R25.
Formula
DO Paging Success Rate (%) =
(PAGE_TRANSMISSION_FAILURE +
PAGE_ATTEMPT_NOT_RESPONDED)
[ 1 - ------------------------------------------------------------------------------------------ ] x 100
(PAGE_ATTEMPTS -
PAGE_ATTEMPT_AT_INIT_CONN_REQ)
Count definitions
PAGE_ATTEMPTS = Number of page attempts sent
PAGE_ATTEMPT_AT_INIT_CONN_REQ =
Number of times the AN sends a page to an AT and receives an AT-initiated
connection request before receiving a page response.
PAGE_TRANSMISSION_FAILURE =
Number of page transmission failures because no UATI session exists,
internal RNC errors, etc.
PAGE_ATTEMPT_NOT_RESPONDED =
Number of paging failures when no response is received from the AT. This
count is pegged only after all paging retries have failed.
............................................................................................................................................................................................................................................................
1xEV-DO Paging Failure Rate due to RF Failures

This metric provides the paging failure rate due to RF failures, i.e., no response from the
AT being paged. The peg counts are defined on a per AP basis.
This metric is effective beginning with R25.
Formula
DO Paging RF Failure Rate (%) =
PAGE_ATTEMPT_NOT_RESPONDED
------------------------------------------------------------------------------------------------- X 100
(PAGE_ATTEMPTS - PAGE_TRANSMISSION_FAILURE -
Count definitions
Number of page times the AN sends a page to an AT and receives an AT-
initiated connection request before receiving a page response.

The metric is new in R25 and is effective beginning with R25.
There are several individual peg counts that give visibility into the different causes of
RAN authentication failures. These counts are defined in the 1xEV-DO Service
Measurements manual (401-614-326). These counts should be monitored by service
providers, especially if the failure rate is high.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------- X 100
Count definitions
RAN_AUTH_TOTAL_ATTMPT = Total number of RAN authentication attempts
1xEV-DO Active Connections Histograms

Beginning in R25, active connection histogram counts have been added at the per sector-
carrier level. These counts measure the number of active connections during the
measurement hour in the following bins: 0 to 5, 6 to 10, 11 to 15, 16 to 20, 21 to 25, 26 to
30, greater than 30.
It is recommended that service providers monitor these counts from a capacity planning
perspective. Alcatel-Lucent performance engineers will monitor actual customer data in
order to determine what the appropriate critical triggers are and whether additional
performance metrics utilizing these counts are warranted. Details of the counts can be
found in the 1xEV-DO Service Measurements manual, 401-614-326.
............................................................................................................................................................................................................................................................
Performance Metrics for Release 25 Connection Drop Metrics
Connection Drop Metrics

............................................................................................................................................................................................................................................................
1xEV-DO Dropped Connection Rate

This metric provides the percentage of dropped connections relative to established
connections. The peg counts are defined on a per sector-carrier basis.
Formula
DO Dropped connection rate (%) =
-------------------------------------------------------------------------------------- X 100
Count Definitions

............................................................................................................................................................................................................................................................





AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA = AT initiated Connection attempt

failures - other failures pre-TCA
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = AT initiated Connection

attempt failures - other failures post-TCA


............................................................................................................................................................................................................................................................

AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA = AN initiated Connection attempt

AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = AN initiated Connection

1xEV-DO Dropped Connection Rate - Peg

The formula is revised for R25 to use the new Established Connections peg counts and is
expected to be more accurate than the old formula. However, it is recommended that
customers use both formulas for a couple of Releases to compare the values obtained by
both.
Formula
DO Dropped connection rate - peg (%) =
(CONN_REL_RLL + CONN_REL_OTHER_REASON +
----------------------------------------------------------------------------------------------- X 100
(AN_INIT_ESTABLISHED_CONN + AT_INIT_ESTABLISHED_CONN)
Count Definitions
SO_SOR_HOFF_FAIL_NO_AT_RSP = Soft-Softer HO attempt failure due to no

............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

("hand-outs") perspective. The peg counts are defined on a per sector-carrier basis.
Note that the pre-TCA failures peg count may include some normal releases that occur
prior to TCA. Therefore, the peg count may be inflated and the success rate calculation
may be artificially low.
Formula
DO SSO Handoff Success Rate Requesting Sector (%) =
SO_SOR_HOFF_FAIL_OTHER_PRETCA +
SO_SOR_HOFF_FAIL_OTHER_POSTTCA)
------------------------------------------------------------------------------------------------- X 100
Count Definitions
TCA.
In addition, another count, So_Sor_Hoff_Fail_Max_No_Legs_Reached, is
pegged.
All of these handoff counts are pegged on the sector that received Route
Update message, i.e., the DRC-pointed sector (also known as requesting or
source sector).
............................................................................................................................................................................................................................................................
the maximum number of legs is reached.
SO_SOR_HOFF_FAIL_OTHER_PRETCA =
These are TCA allocation failures stemming from issues such as no
response from the sector being added (link failures or misconfigured link
between cell/RNC), inability to build/send internal messages, neighbor list
provisioning issues, etc. Basically, it is a catch-all for handoff failures not
specifically pegged.
SO_SOR_HOFF_FAIL_OTHER_POSTTCA =
Soft-Softer HO Attempt failure due to other reasons after TCA is sent.
............................................................................................................................................................................................................................................................

The peg counts are defined on a per sector-carrier basis. Note that the number of handoff
attempts from the requesting sector will, in general, not equal the number of handoff
attempts at the target sector.
Formula
DO SSO Handoff Success Rate Target Sector (%) =
---------------------------------------------------------------------------------------------- X 100
Count Definitions
resources
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Blocking Rate - Requesting Sector

sources.
is applicable to all prior releases.
Formula
----------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
from the AT.
............................................................................................................................................................................................................................................................
1xEV-DO Soft/Softer Handoff Blocking Rate - Target Sector

sector.
applicable to R24.
Formula
--------------------------------------------------------------------------------------------- X 100
Count Definitions
............................................................................................................................................................................................................................................................

sector.
Formula
------------------------------------------------------------------------------ X 100
Count Definitions
TCA sent by the AN.
............................................................................................................................................................................................................................................................

Formula
--------------------------------------------------------------------------------- X 100
Count Definitions
TCA sent by the AN.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Data Re-Transmission Rate

in RLP NAKs.
Formula
RLP_RETXED_FTC
DO forward retransmission rate (%) = ------------------------------------------ X 100
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
channel.

perfectly fine.
Formula
MISSING_RLP_REQ_RTC
DO reverse retransmission rate (%) = ----------------------------------------------- X 100
RLP_RXED_RTC
Count Definitions

............................................................................................................................................................................................................................................................

Formula
DO reverse retransmission failure rate =
-------------------------------------------------------------- X 100
MISSING_RLP_REQ_RTC
............................................................................................................................................................................................................................................................
Count Definitions

retransmit it.

MAC layer.
Formula
DO Forward link MAC data xmitted (MB) =
------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
EVM_FWD_PACKETS_38_4_TOTAL_COUNT =
Total MAC packets transmitted on forward traffic channels at 38.4 kbps
(1024 bits/packet)
............................................................................................................................................................................................................................................................
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT =
Total MAC packets transmitted on forward traffic channels at 307.2 kbps -
long format (2048 1024 bits/packet)
long format (1024 bits/packet)
(1024 bits/packet)
Total MACpackets transmitted on forward traffic channels 921.6 kbps
(1024 bits/packet)
Total MAC packets transmitted on forward traffic channels 1843.2 kbps
(1024 bits/packet)
- long format (1024 bits/packet)
............................................................................................................................................................................................................................................................
(1024 bits/packet)

............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
milliseconds).
Formula
DO Forward link MAC data rate (kbps)=
------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
long format (1024bits/packet)
(1024 bits/packet)
(1024 bits/packet)
............................................................................................................................................................................................................................................................
(1024 bits/packet)
(1024 bits/packet)
Percentage of physical layer slots in the measurement hour used for

users.
the loading.
............................................................................................................................................................................................................................................................
Formula
Count Definitions
get percentage)

per second.
............................................................................................................................................................................................................................................................
Formula
DO RLP Forward Link Data Rate (kbps) =
--------------------------------------------------------------------------------------------------
Count Definitions


megabytes.
Formula
DO RLP Fwd Link Data Vol per user (MB) =
-----------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
1xEV-DO Average Reverse Link Physical Layer Data Volume (MB)

Formula
DO Reverse link physical layer data volume (MB) =
---------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions
REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS =
Number of 9.6 kbps reverse link frames (256 bits/frame)
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Physical Layer Data Rate (kbps)

rates.
Formula
DO Reverse link physical layer data rate (kbps) =
----------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

This metric, similar to the forward link RLP Data throughput, provides an RLP throughput
on the reverse link. Only the truly received bytes are included in the numerator, i.e., the
raw user payload plus overhead bytes from protocol layers above the RLP layer
(application, TCP, IP, PPP). Since the base station is the receiver in this case, it has the
knowledge of bytes lost even after it requested the RLP retry, so there is no ambiguity.
The metric is reflective of the individual user throughput (total data sent/total usage time
over all users). The multiplier .0266 in the denominator is to translate physical layer
frames to the total traffic usage in seconds. It is closer to the true end-user experienced
throughput on the reverse link given that it reduces the effect of padding on the physical
layer, and properly accounts for re-transmissions and data lost
Formula
DO Reverse link RLP data throughput (kbps) =
(RLP_RXED_RTC * 8) / 1000
--------------------------------------------------------------------------------
0.0266 * (REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
............................................................................................................................................................................................................................................................
Count Definitions
............................................................................................................................................................................................................................................................
Performance Metrics for Release 25 Error Statistics
Error Statistics
............................................................................................................................................................................................................................................................

level.
Formula
DO Reverse Frame Error Rate (%) = ---------------------------------------------------- X 100
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Performance Metrics for Release 25 Power Control
Power Control
............................................................................................................................................................................................................................................................

This metric gives the average reverse link power control setpoint per frame for those
frames when no data is received, i.e., 0 kbps frames.
This metric is new for R25 and is applicable to all prior releases.
Formula
DO Avg RL PC Setpoint 0 kbps (dB) =
REV_OUTER_LOOP_PC_TOTAL_OUTPUT_0KBPS
--------------------------------------------------------------------------------
REV_OUTER_LOOP_PC_FRAME_COUNT_0KBPS * 8
Count Definitions
REV_OUTER_LOOP_PC_TOTAL_OUTPUT_0KBPS = Total count for the reverse link

outer loop set point used when no reverse link traffic frame is received, i.e.,
the frame rate is 0kbps. This is only counted on the DRC pointed sector.
The units of the count are dB/8.
REV_OUTER_LOOP_PC_FRAME_COUNT_0KBPS = Total number of reverse link

frames received with no data.

frames in which the data rate is 9.6 kbps.
Formula
DO Avg RL PC Setpoint 9.6 kbps (dB) =
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
REV_OUTER_LOOP_PC_TOTAL_OUTPUT_96KBPS = Total count for the reverse

link outer loop set point used for frames in which the data rate is 9.6 kbps.
This is only counted on the DRC pointed sector. The units of the count are
dB/8.

frames received in which the data rate is 9.6 kbps

Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................

Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.


Formula
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

dB/8.


Formula
---------------------------------------------------------------------------------
Count Definitions
REV_OUTER_LOOP_PC_TOTAL_OUTPUT_1536BPS = Total count for the reverse

link outer loop set point used for frames in which the data rate is 153.6
kbps. This is only counted on the DRC pointed sector. The units of the
count are dB/8.

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO.
level. Although the peg count name is "Average Active Connections" it is actually the sum
of all the total connections based on a 10 second scan.
Formula
DO Traffic channel usage (erlangs) = --------------------------------------------------
360
Count Definitions

Since, there are 360 such intervals in an hour, it is divided by 360 to provide
DO Traffic channel usage in a given hour.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Release 25

............................................................................................................................................................................................................................................................
Overview
The purpose of this section is to provide descriptions of new, modified, and obsolete
(OBS) Prospect Primitive Calculations (PCALCs) that support 1xEV-DO Performance
Metrics defined for RNC R25 and earlier and are implemented in RNC R25 of Prospect.
Existing PCALCs supporting 1xEV-DO performance metrics that did not change in RNC
releases, refer to:
Chapter 8, 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 24.
............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1 0- 1
1xEV-DO Metrics in Watchmark Prospect for Alcatel- Modified 1xEV-DO Performance Metrics in
Modified 1xEV-DO Performance Metrics in Prospect R25

............................................................................................................................................................................................................................................................

ANInitConAttFlNoTCCmpRcv + ANInitConAttFlNoRL + ANInitConAttFlOther) /
ANInitConRq
Notes:
1. The current calculation is modified by removing ANInitConAttFlCnfgNegFl from the
numerator
Prospect
Traffic
............................................................................................................................................................................................................................................................

DOp_InefCallAttATInit = 100.0 * (ATInitConAttFlNoResrc +
ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL + ATInitConAttFlOther) /
ATInitConRq
Notes:
1. The current calculation is modified by removing ATInitConAttFlCnfgNegFl from the
numerator.
Prospect
Traffic
Carrier

DOp_RFFailANInit = 100.0 * (ANInitConAttFlNoTCCmpRcv +
ANInitConAttFlNoRL + ANInitConAttFlOther_PostTCA) / TCAANInitConRq
............................................................................................................................................................................................................................................................
Notes:
1. Existing PCALCs still valid for releases prior to RNC R25.
2. Change for R25 is indicated in bold.
Prospect
TCAANInitConRq TCA_FOR_AN_INIT_CONN_REQ 1xEV_SectorCarri
er
ANInitConAttFlOther-PreTCA AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA

DOp_RFFailATInit = 100.0 * (ATInitConAttFlNoTCCmpRcv + ATInitConAttFlNoRL +
ATInitConAttFlOther_PostTCA) / TCAATInitConRq
Notes:
1. Existing PCALCs still valid for releases prior to RNC R25.
2. Change for R25 is indicated in bold.
Prospect
Traffic
Carrier
ATInitConAttFlOther_PreTCA AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA
............................................................................................................................................................................................................................................................
Soft-Softer Handoff Blocking Rate- Requesting Sector

DOp_SftSftrHOBlk = 100.0 * (SftSftrHOAtt - SftSftrHOAttTCA) / SftSftrHOAtt
Notes:
Prospect
Traffic

DOp_SftSftrHOBlk_Tgt = 100.0 * (SftSftrHOAtt_Tgt - SftSftrHOAttTCASent_Tgt) /
SftSftrHOAtt_Tgt
Notes:
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................
1X-EV DO PCF Reactivation Success Rate for AT-Initiations

The name of the metric DOp_SucReactATInit changes from "1X-EV DO PCF
DOp_SucReactATInit is assigned a Field Type of OBS (obsolete) beginning in Prospect
R25 (The new name for this metric will be DOp_RPCnctSuccess.)
The old name will automatically point to the new name in template definitions, UDCs, etc.

The name of the metric DO_AvgBrstRevLnk changes from "Average Reverse Link Burst
Rate (kbps)" to "Average Reverse Link Data Rate (kbps)" in R25.
DO_AvgBrstRevLnk is assigned a Field Type of OBS (obsolete) beginning in Prospect
R25 (The new name for this metric will be DOp_AvgRevL_kbps.)
The old name will automatically point to the new name in template definitions, UDCs, etc.
Soft-Softer Handoff Success Rate- Requesting Sector

DOp_SftSftrHOSuc = 100.0 * (SftSftrHOAtt - SftSftrHOFlMaxLegs -
(SftSftrHOFlNoResc + SftSftrHOFlNoATRsp + SftSftrHOFlOther)) / SftSftrHOAtt
Notes:
Prospect
Traffic
Carrier
SftSftrHOFlOther SO_SOR_HOFF_FAIL_OTHER_REASON
SftSftrHOFlMaxLegs SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED
............................................................................................................................................................................................................................................................

Prospect Traffic Report Entity: 1xEV_Sector and 1xEV_SectorCarrier
DOp_IntSubIdlTrfSuc = 100.0 * (IntSubIdleTrfrAtt + IntSubIdlTrnsfPriorSesAtt -
(IntSubIdlTrfFl_NoRspPrev + IntSubIdlTrfFl_OrigPDSNcntConn +
IntSubIdlTrfFl_RejMsgRcv + IntSubIdlTrfFl_Other + IntSbIdlTrfrFl_SrcIpAd +
IntSubIdlTrnsfPriorSesBadRq + IntSubIdlTrnsfPriorSesNoRsp)) / (IntSubIdleTrfrAtt +
IntSubIdlTrnsfPriorSesAtt)
Notes:
Prospect
Traffic
Carrier
IntSubIdlTrfFl_NoRspPrev ISBNT_IDL_TRFR_FAIL_NO_RSP_PRV_SBNET
IntSubIdlTrfFl_OrigPDSNcntConn ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN
IntSubIdlTrfFl_RejMsgRcv ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD
IntSbIdlTrfrFl_SrcIpAd ISBNT_IDL_TRFR_FAIL_SRC_IP_ADR_NT_FOUND
IntSubIdlTrnsfPriorSesAtt INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS
IntSubIdlTrnsfPriorSesBadRq INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ
IntSubIdlTrnsfPriorSesBadRq INT_SUBNET_IDL_TRFR_PRIOR_SES_NO_RSP
............................................................................................................................................................................................................................................................

Prospect Traffic Report Entity: 1xEV_SectorCarrier and 1xEV_Sector
SesSUIntSubUATICmpMsgRcvd) / (SessnSURq + IntSubIdleTrfrAtt)
Notes:
Prospect
Traffic
Carrier
SesSUIntSubUATICmpMsgRcvd SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- Deleted 1xEV-DO Performance Metrics in
Deleted 1xEV-DO Performance Metrics in Prospect R25

............................................................................................................................................................................................................................................................
% Connection Attempt Failures Due to Reverse Link Not AcquiredProspect Traffic Report Entity:
1xEV_Sector, 1xEV_SectorCarrier (RNC R24 and later)
Beginning in Prospect R25, the primitive calculation DOp_CnctFlNoRL is assigned a
field type of OBS.

Beginning in Prospect R25, the primitive calculation DOp_CnctFlNoResrc is assigned a
field type of OBS.
% Connection Attempt Failures Due to No Response to Traffic Channel Assignment

Beginning in Prospect R25, the primitive calculation DOp_CnctFlNoTCCmpRcv is
assigned a field type of OBS.

Beginning in Prospect R25, the primitive calculation DOp_CnctFlOther is assigned a field
type of OBS.

Prospect Traffic Report Entity: 1xEV_Sector, 1xEV_SectorCarrier (R24 and later)
Beginning in Prospect R25, the primitive calculation DOp_CnctFlCnfgNeg is assigned a
field type of INV (Configuration negotiation failures are no longer considered connection
failures).
1xEV-DO Inter-Subnet Idle Transfer Success Rate - Prior Session Method

Prospect Name: DOp_IntSubIdlTrnsfSuc_PriorSes
Note:
THIS METRIC IS INVALID AND IS REMOVED FROM PROSPECT
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

DOp_EstCnct = 100.0 * (ATInitEstabConnection + ANInitEstabConnection) /
(ATInitConRq + ANInitConRq)
Notes:
Prospect Traffic
ATInitEstabConnection AT_INIT_ESTABLISHED_CONN_ 1xEV_SectorCarrier
ATInitEstabConnection AT_INIT_ESTABLISHED_CONN
............................................................................................................................................................................................................................................................

Valid Releases: RNC 25 and later
DOp_FastCnctSuc =
100.0 * (FastConnect - FastConFlNoTCCmpRcv - FastConFlRevLnkNotAcq -
FastConnectFlNoResource) / FastConnect
Notes:
Prospect
Traffic
FastConnectFlNoResource FAST_CONNECT_FAIL_NO_RSC
1xEV-DO AN-Initiated Ineffective Connection Attempt Rate

DOp_InefCnctAttANInit = 100.0 * (ANInitConRq - ANInitEstabConnection) /
ANInitConRq
Notes:
Prospect Traffic
ANInitEstabConnection AN_INIT_ESTABLISHED_CONN
............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1 0- 1 1
1xEV-DO AT-Initiated Ineffective Connection Attempt Rate

DOp_InefCnctAttATInit = 100.0 * (ATInitConRq - ATInitEstabConnection) /
ATInitConRq
Notes:
Prospect Traffic

DOp_InefCnctAttTotal = 100.0 * (ANInitConRq + ATInitConRq -
ANInitEstabConnection - ATInitEstabConnection) / (ANInitConRq + ATInitConRq)
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

DOp_InefCnctAttTotal = 100.0 * (ANInitConRq + ATInitConRq -
ANInitEstabConnection - ATInitEstabConnection) / (ANInitConRq + ATInitConRq)
Notes:
Prospect Traffic

DOp_DropCnct = 100.0 * (ConRlsRLL + ConRlsOther + SftSftrHOFlNoATRsp) /
(ANInitEstabConnection + ATInitEstabConnection)
Notes:
Prospect Traffic
ConRlsRLL CONN_REL_RLL 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................

DOp_SessAsgnReq = 100.0 * (SessnSUUATIAsgnMsgSent +
SesSUIntSubUATIAsgnMsgSent) / (SessnSURq + IntSubIdleTrfrAtt)
Notes:
Prospect
SessnSUUATIAsgnMsgSent SESS_SETUP_UATI_ASSGNMT_MSG_SENT 1xEV_SectorCarri
er
SesSUIntSubUATIAsgnMsgSent SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT

DOp_PageSucc = 100.0 *(1.0 - ((PageTransmFail + 1xEVPageAttNotRsp) /
(1xEVPageAttempts - PageAtmptATInitCnctReq)))
Notes:
Prospect Traffic
PageTransmFail PAGE_TRANSMISSION_FAILURE 1xEV_AP
1xEVPageAttNotRsp PAGE_ATTEMPT_NOT_RESPONDED
1xEVPageAttempts PAGE_ATTEMPTS
PageAtmptATInitCnctReq PAGE_ATTEMPT_AT_INIT_CONN_REQ
............................................................................................................................................................................................................................................................
1xEV-DO Paging Failure Rate Due to RF Failures

DOp_RFPageFail = 100.0 * 1xEVPageAttNotRsp / (1xEVPageAttempts -
PageTransmFail - PageAtmptATInitCnctReq - 1xEVPageAttNotRsp)
Notes:
Prospect Traffic
PageTransmFail PAGE_TRANSMISSION_FAILURE 1xEV_AP
1xEVPageAttNotRsp PAGE_ATTEMPT_NOT_RESPONDED
1xEVPageAttempts PAGE_ATTEMPTS
PageAtmptATInitCnctReq PAGE_ATTEMPT_AT_INIT_CONN_REQ

Notes:
Prospect Traffic

............................................................................................................................................................................................................................................................

Notes:
Prospect Traffic

Notes:
............................................................................................................................................................................................................................................................
Prospect Traffic


Notes:
Prospect Traffic
1xEV-DO Soft/Softer Handoff RF Failure Rate-Target Sector

SftSftrHOAttTCASent_Tgt
............................................................................................................................................................................................................................................................
Notes:
Prospect Traffic
SftSftrHOFlNoATRsp_Tgt SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET 1xEV_SectorCarrier

Notes:
Prospect Traffic

Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

RevOutLoopPCFrCt192
Notes:
Prospect Traffic

RevOutLoopPCFrCt384
Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

RevOutLoopPCFrCt768
Notes:
Prospect Traffic

Notes:
Prospect Traffic
............................................................................................................................................................................................................................................................

Notes:
Prospect Traffic

Notes:
Prospect Traffic
1xEV-DO RAN Authentication Success Rate (%)

DOp_RANAuthSucc = 100.0 * RANAuth_SucAttmpt / RANAuth_TotAttmpt
............................................................................................................................................................................................................................................................
Notes:
Prospect Traffic
RANAuth_SucAttmpt RAN_AUTH_SUCCESSFUL_ATTMPT 1xEV_TP
RANAuth_TotAttmpt RAN_AUTH_TOTAL_ATTMPT
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose
Changes This Release

New metrics were added for hard handoffs, paralleling the soft/softer handoff metrics.
Also added is a metric for AT-initiated connection blocking ratio during session setup. All
connection-related metrics were changed due to the multiple carrier feature. The separate
AT-initiated and AN-initiated connection metrics were deleted and replaced with
combined metrics for both connections.
New metrics:
Connection Blocking Rate
AT-Initiated Connection Blocking Ratio - Session Setup
RF Failure Rate - Peg
Hard Handoff Success Rate - Requesting Sector
Hard Handoff Success Rate - Target Sector
Hard Handoff Blocking Rate - Requesting Sector
Hard Handoff Blocking Rate - Target Sector
Hard Handoff RF Failure Rate - Requesting Sector
Hard Handoff RF Failure Rate - Target Sector
Metrics revised:
............................................................................................................................................................................................................................................................
RF Failure Rate
Metrics deleted:
AN-Initiated Connection Blocking Ratio
AT-Initiated Connection Blocking Ratio
AN-Initiated Connection Blocking Ratio due to No Resources
AT-Initiated Connection Blocking Ratio due to No Resources
AN-Initiated Ineffective Connection Rate
AT-Initiated Ineffective Connection Rate
AN-Initiated Ineffective Connection Rate - Peg
AT-Initiated Ineffective Connection Rate - Peg
The following performance metrics are provided in R26:
a. Connection Setup
AT-Initiated Connection Blocking Rate - Session Setup
RF Failure Rate
............................................................................................................................................................................................................................................................
Paging Success Rate

b. Connection Drop
c. Handoff
Average Forward Link MAC Data Rate (kpbs)
Reverse Link RLP Data Throughput (kbps)
e. Error Statistics
f. Power Control
Average Reverse Link Power Control Setpoint - 0 kbps
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
Formula
-------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ = Session Set Up Request (pegged when the AN receives a

UATI request message for new and prior session setups)
............................................................................................................................................................................................................................................................
Session Set Up - UATI Complete Message Received (new and prior).
Pegged when the AT acknowledges a UATI assignment message sent by
the AN in response to a UATI request.
Session Set Up - UATI Complete Message Received (assign first and color
code)

communicate and exchange proper information in case of Color Code method of inter-
RNC idle handoff. A ratio less than 1 is reflective purely of a AN issue; no over the air
This metric is new in R25 and is applicable to prior releases.
Formula
----------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ =
message for new and prior session setups)
............................................................................................................................................................................................................................................................
UATI request message (new and prior sessions)
Session Set Up - UATI Assignment Message Sent (assign first and color
code)

during the measurement interval. It is defined on a per AP basis. Note that the
measurement interval may not be exactly one hour so the calculation is approximate.
Formula
360
Count Definitions
approximate.
............................................................................................................................................................................................................................................................

intervention.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------------------------- X100
Count Definitions
instead.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
is, 255.255.255.255 or NULL).

The metric is new in R25 and is effective beginning with R25. There are several individual
peg counts that give visibility into the different causes of RAN authentication failures.
These counts are defined in 401-614-326, 1xEV-DO Service Measurements. These counts
should be monitored by service providers, especially if the failure rate is high.
Formula
--------------------------------------------------- x 100
............................................................................................................................................................................................................................................................
Count Definitions
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

results in what is known as PCF or network reactivation, as discussed above.The PCF
reactivation failures can be contributed by RF failures (resulting in Page timeout or AN
initiated Connection Failure or Fast Connect Failure), any system bottlenecks (such as
inability to allocate traffic channel resources), AT not reachable (such as AT powered off
or moved to a different RNC without a clean inter-RNC idle handoff), etc.
Formula
------------------------------------------------------------------------------ X 100
Count Definitions
end user.
PDSN.
............................................................................................................................................................................................................................................................

The one in this section deals with the success rate associated with setting up connections
on the R-P link.
handoff.
failures.The peg counts are defined on a per TP basis.
The name of this metric was changed in R25.
Formula
------------------------------------------------------------------------------ X 100
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS =
............................................................................................................................................................................................................................................................
RP_CONN_FAIL =
service).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

3G1X.
than the AT Initiated Connections.There are various reasons that can cause connection
failures - such as blocking at the AN, internal errors allocating TCA, sub-optimal RF
conditions between the AT/AN resulting in missed messages between the AN/AT, etc.In
general, a connection is said to be established when the AN has received a Traffic Channel
Complete message from the AN. This is conceptually very similar to receiving a Service
Connect Complete Message from the mobile in a IS2000 system.
for a Connection.The peg counts are defined on a per sector-carrier basis and can be rolled
The formula is revised in R26 to account for cross carrier connections. The new formula
is effective beginning with R26.
Beginning with R26 SU1, SESS_CLOSE_SESS_TRFR_ABORTED will also peg
AT/AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA. Users should change the
formula to remove SESS_CLOSE_SESS_TRFR_ABORTED from the metric when they
install R26 SU1.
............................................................................................................................................................................................................................................................
Formula
SESS_CLOSE_SESS_TRFR_ABORTED -
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD -
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD)
--------------------------------------------------------------------------------------------------X 100
(AN_INIT_CONN_REQ - AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT +
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD + AT_INIT_CONN_REQ -
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT +
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD -
SESS_CLOSE_SESS_TRFR_ABORTED)
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT =
This count is pegged when an AN initiated connection request is received
on this sector-carrier but Load Balancing did not select this sector-carrier
for assignment (TCA is sent by another sector-carrier).
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD =
on another sector-carrier but Load Balancing selected this sector-carrier for
assignment (TCA is sent by this sector-carrier).
AT_INIT_CONN_REQ =
Connection Request.
SESS_CLOSE_SESS_TRFR_ABORTED =
This count is pegged for each connection request received when the UATI
associated with the request does not have a valid session due to a Session
transfer failure. The count is used to measure connection attempt rejects
due to session transfer failures.
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD =
This count is pegged when an AT initiated connection request is received
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT =
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD =
This count is pegged for each established connection (TCC is sent to from
the AT) where the TCA does not include the sector-carrier that received the
connection request. It is pegged against the strongest sector-carrier
selected for traffic channel allocation by the load balancing algorithm.
............................................................................................................................................................................................................................................................
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD =
connection request. It is pegged against the sector-carrier that received the
connection request.
Note: All the failure counts below are pegged as AT or AN Initiated depending on whether
the corresponding Connection Request message was received with AT or AN Initiated
attribute set.
receiving the TCC.
Ma x _n u mb er _ of _c o nn e ct io n s , a per-sector translation limit.
Essentially, it is an indication of blocking on the sector. Note that if the
strongest Pilot on the RUM does not have resources, but other Pilots have,
then it is possible to allocate traffic channel on the rest and exclude the
strongest sector from the TCA. In this case, this count will not be pegged.
Instead, N um _ Ti me s _M ax _ Co n n_ Re a ch ed count will be pegged on the
blocking sector.
............................................................................................................................................................................................................................................................
This is a catch-all for remaining connection setup failure scenarios that
occur before sending TCA.The reasons may include internal call
occur after sending TCA. The reasons may include internal call processing
errors, time outs, message build or send errors, blocking due to system
bottlenecks, etc.
receiving the TCC.
M ax _ nu mb e r_ o f_ co n ne ct i on s , a per-sector translation limit.
............................................................................................................................................................................................................................................................
blocking sector.
occur after sending TCA.The reasons may include internal call processing
bottlenecks, etc.

cell level.
This metric is new for R25 to use the new Established Calls peg counts and is expected to
be more accurate than the old formula. However, it is recommended that customers use
The formula is revised in R26 to subtract session related connection attempts and to
account for cross carrier connections. The new formula is effective beginning with R26.
Beginning with R26 SU1, SESS_CLOSE_SESS_TRFR_ABORTED will also peg
AT/AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA. Users should change the
formula to remove SESS_CLOSE_SESS_TRFR_ABORTED from the metric when they
install R26 SU1.
............................................................................................................................................................................................................................................................
Formula
(AN_INIT_ESTABLISHED_CONN + AT_INIT_ESTABLISHED_CONN +
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD)-
---------------------------------------------------------------------------------------------------X 100
SESS_CLOSE_SESS_TRFR_ABORTED)
Count Definitions
AN_INIT_ESTABLISHED_CONN =
Number of AN-Initiated successful connections (pegged when a TCC is
received or an RLP packet is received from the AT on the reverse traffic
channel.)
AT_INIT_ESTABLISHED_CONN =
Number of AT-Initiated successful connections (pegged when a TCC is
channel.)
............................................................................................................................................................................................................................................................
connection request.
Number of AN-Initiated connection requests on this sector-carrier served
by another sector-carrier.
Number of AN-Initiated connection requests on another sector-carrier
served by this sector-carrier
by another sector-carrier
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD = Number of AT-Initiated

connection requests on another sector-carrier served by this sector-carrier

all the AT and AN Initiated connection pegs. Note also that the Fast Connect procedure is
not affected by load balancing or cross-carrier assignments.The Fast Connect failures
could be due to blocking, internal errors when allocating resources for TCA, or RF
reasons similar to an AT/AN initiated TCA.
............................................................................................................................................................................................................................................................
The formula is changed in R26 to add the new no resources peg count and is effective with
R26.
Formula
FAST_CONNECT_FAIL_RL_NOT_ACQ - FAST_CONNECT_FAIL_NO_RSC )
---------------------------------------------------------------------------------------------------X 100
(FAST_CONNECT)
Count Definitions
FAST_CONNECT =
failures.
preamble.
FAST_CONNECT_FAIL_NO_RSC =
This count is pegged when the AN is no able to send an Allocate Traffic
Channel Request to all sectors or if all sectors fail to send a successful
Allocate Traffic Channel Response to the AN. This occurs when there are
on resources available to establish a traffic channel.
............................................................................................................................................................................................................................................................

connect procedure.
by both.
Formula
--------------------------------------------------------------------------X 100
FAST_CONNECT
Count Definitions
1xEV-DO Connection Blocking Rate

This metric gives the percentage blocking for AT-initiated and AN-initiated connections.
It is equivalent to the Seizure to Assignment Deficit Ratio for originations and
terminations in 3G 1x. Any connection attempt failures occurring after receiving a
Connection Request and prior to sending the TCA are termed as connection blocks or
connection attempt deficits. These are failures entirely happening within the AN, such as
TCA allocation failure, some type of resource overload or overflow, internal errors or
messaging failure.
............................................................................................................................................................................................................................................................

This metric is new in R26 and replaces the separate AT-Initiated and AN-Initiated
blocking ratio metrics. The separate metrics have been deleted in R26 because the cross-
carrier counts are not provided as separate AT-initiated and AN-initiated counts. Note that
the old separate formulas continue to be provided for R25 and earlier.
Formula
DO Connection Blocking Rate (%) =
SESS_CLOSED_SESS_TRFR_ABORTED -
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT +
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD -
(TCA_FOR_AN_INIT_CONN_REQ + TCA_FOR_AT_INIT_CONN_REQ +
CROSS_CARR_ATTMPT_RCVD_TCA_SENT -
CROSS_CARR_ATTMPT_SENT_TCA_SENT))
---------------------------------------------------------------------------------------------------- X 100
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD)
Count Definitions
Traffic Channel Assignments sent by the AN on this sector-carrier in
response to AN-Initiated Connection Requests either received and served
on this sector-carrier (same sector-carrier assignment) or received on
another sector-carrier and served on this sector-carrier (cross sector-carrier
assignment).
response to AT-Initiated Connection Requests either received and served
............................................................................................................................................................................................................................................................

assignment).
CROSS_CARR_ATTMPT_RCVD_TCA_SENT =
response to a connection request received on another sector-carrier. It is
pegged against the strongest sector-carrier selected for traffic channel
allocation by the load balancing algorithm.
CROSS_CARR_ATTMPT_SENT_TCA_SENT =
Traffic Channel Assignments sent by the AN on another sector-carrier in
response to a connection request received on this sector-carrier. It is
pegged against the sector-carrier that received the connection request.
AN_INIT_CONN_REQ =
AN-Initiated Connection Requests received on this sector-carrier
AT_INIT_CONN_REQ =
Number of AN-Initiated connection requests received on this sector-carrier
served by a different sector-carrier
Number of AN-Initiated connection requests received on a different sector-
carrier but served by this sector-carrier
served by a different sector-carrier.
............................................................................................................................................................................................................................................................
response to AN-Initiated Connection Requests received on this sector-
carrier
response to AT-Initiated Connection Requests received on this sector-
carrier
allocation by the load balancing algorithm
1xEV-DO AT-Initiated Connection Blocking Rate - Session Setup

This metric gives the percentage blocking for AT-initiated connections while the UATI
session is in a state of waiting for Configuration Negotiation. Any connection attempt
............................................................................................................................................................................................................................................................

This metric is new in R26 and is effective with R26.
Formula
DO AT-Initiated Connection Blocking Rate - Session Setup (%) =
(AT_INIT_CONN_REQ_SESS - TCA_FOR_AT_INIT_CONN_REQ_SESS)
---------------------------------------------------------------------------------------------------- X 100
AT_INIT_CONN_REQ_SESS
Count Definitions
AT_INIT_CONN_REQ_SESS = AT Initiated Connection Requests, Session Setup
TCA_FOR_AT_INIT_CONN_REQ_SESS = Traffic Channel Assignments for AT

Initiated Connection Requests for session setup

initiated) that failed. It is defined as 100 - established connection rate (see 1xEV-DO
Established Connection Rate (p. 11-15).
The formula is revised in R26 for simplification. The old formula could not be used with
the new load balancing (cross-connect) feature because there are no cross-connect failure
counts defined. The new formula is effective beginning with R26, but can be used in prior
releases.
Formula
DO Total Ineffective Connection Rate (%) = 100 - DO Established Connection Rate (%)
Count Definitions
There are no peg counts explicitly used in this metric. See 1xEV-DO Established
Connection Rate (p. 11-15) for the counts included in the established connection rate
metric.

initiated) that failed. It is defined as 100 - established connection rate - peg (see 1xEV-
DO Established Connection Rate - Peg (p. 11-20).
............................................................................................................................................................................................................................................................
The formula is revised is R26 for simplification. The old formula could not be used with
the new load balancing (cross-connect feature because the established connection counts
are not defined for cross-connects.
The new formula is effective beginning with R26, but can be used in prior releases.
Formula
DO Total Ineffective Call Rate - Peg (%) = 100 - DO established connection rate - peg (%)
Count Definitions
Connection Rate - Peg (p. 11-20) for the counts included in the established connection
rate - peg metric.
1xEV-DO RF Failure Rate

This metric provides the percentage of AN-initiated and AT-initiated connection attempts
that failed for RF air interface reasons relative to the number of traffic channels assigned
to the requests. The Established Call rate, or its complementary Ineffective Connection
Attempt rate, encompasses all types of failures that prevent a successful connection setup.
Largely, the failures can be broken down into RF failures or blocking.
signalling and/or actual traffic channel assignment packets leading up to the connection
setup failure.
This metric for combined AT-initiated and AN-initiated RF failure rate is new in R26 and
replaces the separate metrics used in prior releases. The formula is revised in R26 to
include load balancing effects. RF failure rate is now defined as TCA sent minus
established connections. The old formula could not be used with the new load balancing
(cross-connect) feature because the established connection counts are not defined for
cross-connects. The new formula is effective beginning with R26.
............................................................................................................................................................................................................................................................
Formula
DO RF failure rate (%) =
AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA +
(CROSS_CARR_ATTMPT_RCVD_TCA_SENT -
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD) -
(CROSS_CARR_ATTMPT_SENT_TCA_SENT -
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD))
-------------------------------------------------------------------------------------------------- X 100
CROSS_CARR_ATTMPT_SENT_TCA_SENT)
Count Definitions
carrier
carrier
............................................................................................................................................................................................................................................................
connection request.All the failure counts below are pegged as AT or AN
Initiated depending on whether the corresponding Connection Request
message was received with AT or AN Initiated attribute set.
receiving the TCC.
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = This is a catch-all for

remaining failure reasons that prevent a successful connection setup that
bottlenecks, etc.
............................................................................................................................................................................................................................................................
receiving the TCC.
connection setup that occur before sending TCA.The reasons may include
1xEV-DO RF Failure Rate - Peg

This metric is new for R26 to use the established connection peg counts based on the
revised rf failure rate definition of TCA sent minus established calls. It is expected to be
more accurate than the detailed formula in 1xEV-DO RF Failure Rate (p. 11-29) but it is
recommended that customers use both formulas for a couple of releases to compare the
values obtained by both.
The new formula is effective beginning with R26.
............................................................................................................................................................................................................................................................
Formula
DO RF failure rate - peg (%) =
((TCA_FOR_AN_INIT_CONN_REQ + TCA_FOR_AT_INIT_CONN_REQ +
CROSS_CARR_ATTMPT_SENT_TCA_SENT) -
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD))
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
carrier
carrier
Number of AN-Initiated successful connections for connection requests
received on this sector-carrier.
............................................................................................................................................................................................................................................................
Number of AT-Initiated successful connections for connection requests
connection request.

deleted as Alcatel-Lucent supported metrics as of R25. The individual failures can be
seen from the following raw peg counts:
Count definitions
received
............................................................................................................................................................................................................................................................
received

Formula
(1 - ---------------------------------------------------------------------------------------------) X 100
(PAGE_ATTEMPTS - PAGE_ATTEMPT_AT_INIT_CONN_REQ)
Count definitions
PAGE_ATTEMPTS =
Number of page attempts; a single attempt can consist of multiple retries,
but is pegged only once.
connection request before receiving a page response. Such an attempt is
treated as AT initiated connection for pegging purposes and hence should
............................................................................................................................................................................................................................................................
not be considered as a page attempt. This could happen when both AN and
AT have some data in their transmit queues and hence end up attempting to
reactivate a dormant connection at the same time.
internal RNC errors, etc. Essentially, no page could be sent out due to these
errors.
count is pegged only after all paging retries have failed. Such paging
failures may mean the AT is in poor RF conditions, the AT is turned off, the
AT has moved to a different subnet area and has not yet registered there
successfully, AT has tuned to 1x system, etc.

This metric provides the paging failure rate due to RF failures, that is, no response from
the AT being paged. The peg counts are defined on a per AP basis.
Formula
------------------------------------------------------------------------------------------------- X 100
Count definitions
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

The formula is revised in R26 to account for the cross-connect (load balancing) feature.
Beginning with R26 there is a translation in RC/V to not peg the CONN_REL_RLL peg
count for dropped connections estimated to be caused by "long" AT tuneaways to a 3G1x
carrier. If the translation is set to continue pegging, then the CONN_REL_RLL count
will include the tuneaways and the dropped call rate will be inflated.
The SO_SOR_HOFF_FAIL_NO_AT_RSP peg was deleted from the formula because
beginning in R26, these failures are included as part of the connection release other
reasons count.
Formula
CONN_REL_RLL + CONN_REL_OTHER_REASON
---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
Connection Release due to RF Link Lost. These are connection releases
declared by the AN when it stops receiving valid data from the AT on the
............................................................................................................................................................................................................................................................
reverse link. More precisely, when the AN sees no more than 3 good DRCs
in the trailing 5 sec interval, it drops the connection. The dropped
for declaring dropped connection is quite different. As of R26, dropped
connections estimated to be caused by "long" AT tuneaways to a 3G1x
carrier are excluded from this count.
CONN_REL_OTHER_REASON =
This is a catch all for releases not accounted for by any of the Connection
Release related peg counts. One of the main causes is internal call
processing errors at the AN.
received
AT initiated Connection attempt failures - other failures pre-TCA
AT initiated Connection attempt failures - other failures post-TCA
received
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = A
T-initiated Connection attempt failures - rev link not acquired
............................................................................................................................................................................................................................................................
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = A
T-initiated connection attempt failures - no resources available
AN initiated Connection attempt failures - other failures pre-TCA
AN initiated Connection attempt failures - other failures post-TCA
connection request.

carrier. If the translation is set to continue pegging, then the CONN_REL_RLL count
will include the tuneaways and the dropped call rate will be inflated.
beginning in R26 these failures are included as part of the connection release other reasons
count.
............................................................................................................................................................................................................................................................
Formula
(CONN_REL_RLL + CONN_REL_OTHER_REASON )
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
connection request.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

("hand-outs") perspective. The peg counts are defined on a per sector-carrier basis. The
formula is revised is R25.
The new formula is applicable for releases R25 and later. Note that the pre-TCA other
failures peg count may include some normal connection releases that occur prior to
sending handoff TCA. Therefore the peg count may be inflated and the success rate
calculation may be artificially low.
Formula
------------------------------------------------------------------------------------------------- X 100
Count Definitions
TCA. In addition, another count,
So_Sor_Hoff_Fail_Max_No_Legs_Reached, is pegged.All of these
handoff counts are pegged on the sector that received Route Update
message.
............................................................................................................................................................................................................................................................
translation and there is no strong candidate pilot on the RUM that can
replace a weaker active set pilot. Beginning in R25, handoff attempts will
also be pegged when the maximum number of legs is reached.
............................................................................................................................................................................................................................................................
1xEV-DO Hard Handoff Success Rate - Requesting Sector

This metric gives the success rate for hard handoffs from the requesting sector ("hand-
outs") perspective. The peg counts are defined on a per sector-carrier basis.
This metric is new in R26 and is effective with R26. Note that the pre-TCA failures peg
count may include some normal releases that occur prior to TCA. Therefore the peg count
may be inflated and the success rate calculation may be artificially low.
Formula
DO Hard Handoff Success Rate Requesting Sector (%) =
HHOFF_ATTMPT_REQ - (HHOFF_FAIL_NO_RESOURCE_REQ +
HHOFF_FAIL_NO_AT_RSP_REQ + HHOFF_FAIL_OTHER_PRETCA_REQ +
HHOFF_FAIL_OTHER_POSTTCA_REQ)
-------------------------------------------------------------------------------------------------- X 100
HOFF_ATTMPT_REQ
Count Definitions
HHOFF_ATTMPT_REQ =
This count is the number of Hard handoff attempts being processed. A hard
handoff is attempted if, after processing a RUM, the AN determines that an
inter-frequency handoff is necessary.All of these handoff counts are pegged
on the sector-carrier that received Route Update message.
HHOFF_FAIL NO_RESOURCE_REQ =
Hard HO Attempt failure due to the AN's inability to send a TCA because
the candidate sector-carrier being added is already supporting the
HHOFF_FAIL_NO_AT_RSP_REQ =
Hard HO Attempt failure due to no response from the AT, i.e., a Traffic
Channel Complete (TCC) message was not received from the AT in
response to a Traffic Channel Assignment (TCA) for a handoff.
HHOFF_FAIL_OTHER_PRETCA_REQ =
response from the sector-carrier being added (link failures or
misconfigured link between cell/RNC), inability to build/send internal
messages, neighbor list provisioning issues, etc. Basically, it is a catch-all
for handoff failures not specifically pegged.
............................................................................................................................................................................................................................................................
HHOFF_FAIL_OTHER_POSTTCA_REQ =
Hard HO Attempt failure due to other reasons after TCA is sent.

Formula
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET -
--------------------------------------------------------------------------------------------------- X 100
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET
Count Definitions
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET =
the total number of legs has reached the maximum specified by the
translation. Handoff attempts will also be pegged when the maximum
number of legs is reached.
resources
............................................................................................................................................................................................................................................................
1xEV-DO Hard Handoff Success Rate - Target Sector

This metric gives the success rate for hard handoffs to the target sector ("hand-ins"). The
peg counts are defined on a per sector-carrier basis. Note that the number of handoff
attempts at the target sector. This metric is new in R26 and is effective with R26.
Formula
DO Hard Handoff Success Rate Target Sector (%) =
HHOFF_ATTMPT_TARGET - (HHOFF_FAIL_NO_RESOURCE_TARGET +
HHOFF_FAIL_NO_AT_RSP_TARGET + HHOFF_FAIL_OTHER_PRETCA_TARGET
+ HHOFF_FAIL_OTHER_POSTTCA_TARGET)
--------------------------------------------------------------------------------------------------- X 100
HHOFF_ATTMPT_TARGET
Count Definitions
HHOFF_ATTMPT_TARGET = Hard HO Attempt at the target sector-carrier
HHOFF_FAIL NO_RESOURCE_TARGET = Hard HO Attempt failure at the target

sector-carrier due to no resources
HHOFF_FAIL_NO_AT_RSP_TARGET = Hard HO Attempt failure at the target sector-

carrier due to no response from the AT
HHOFF_FAIL_OTHER_PRETCA_TARGET = Hard HO Attempt failure at the target

sector-carrier due to other reasons prior to traffic channel assignment
HHOFF_FAIL_OTHER_POSTTCA_TARGET = Hard HO Attempt failure at the target

sector-carrier due to other reasons after traffic channel assignment
............................................................................................................................................................................................................................................................

sources.
prevented the add itself.The peg counts are defined on a per sector-carrier basis and are
pegged at the requesting sector.
Formula
----------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
from the AT.
1xEV-DO Hard Handoff Blocking Rate - Requesting Sector

This metric gives the percentage blocking for hard handoffs measured at the requesting
sector. Handoff blocking is a category of hard handoff failures that results in AN not
issuing a TCA even though the RUM presented a valid handoff trigger that normally
would have resulted in an active set change.
The hard handoff blocks, in general, are errors that occur entirely within the AN. Since
sources.
The handoff blocks may occur because the candidate sector-carrier is already at its
maximum allowed connections (controlled via translations) or there is some trouble
allocating resources at the candidate cell (message exchange issues between the RNC and
the cell).
sector.
The metric is new in R26 and is effective with R26.
............................................................................................................................................................................................................................................................
seen from HHOFF_FAIL_NO_RESOURCE_REQ and
HHOFF_FAIL_OTHER_PRETCA_REQ.
Formula
DO HHO Blocking Rate (%) =
HHOFF_ATTMPT_REQ - HHOFF_TCA_SENT_REQ
------------------------------------------------------------------------------------------ X 100
HHOFF_ATTMPT_REQ
Count Definitions
HHOFF_ATTMPT_REQ =
inter-frequency handoff is necessary.
HHOFF_TCA_SENT_REQ =
This count is pegged when a Traffic Channel Assignment message is sent
to perform an inter-frequency hard handoff.
Important! Both of these handoff counts are pegged on the sector-carrier that
received Route Update message, i.e., the DRC-pointed sector (also known as
requesting or source sector).
............................................................................................................................................................................................................................................................

sector.
applicable to R24.
Formula
(SO_SOR_HOFF_ATTMPT_TARGET -
SO_SOR_HOFF_ATTMPT_TCA_SENT_TARGET)
--------------------------------------------------------------------------------------------------- X 100
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET)
Count Definitions
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET =
the total number of legs has reached the maximum specified by the
translation. Handoff attempts will also be pegged when the maximum
............................................................................................................................................................................................................................................................
1xEV-DO Hard Handoff Blocking Rate - Target Sector

This metric gives the percentage blocking for hard handoffs measured at the target sector.
seen from HHOFF_FAIL_NO_RESOURCE_TARGET and
HHOFF_FAIL_OTHER_PRETCA_TARGET.
Formula
DO Hard HO Blocking Rate - Target Sector(%) =
HHOFF_ATTMPT_TARGET - HHOFF_TCA_SENT_TARGET
-------------------------------------------------------------------------------------- X 100
HHOFF_ATTMPT_TARGET
Count Definitions
HHOFF_ATTMPT_TARGET= Hard HO Attempts
HHOFF_TCA_SENT_TARGET = TCA sent in response to a hard handoff attempt

sector.
Formula
------------------------------------------------------------------------------ X 100
............................................................................................................................................................................................................................................................
Count Definitions
TCA sent by the AN.
1xEV-DO Hard Handoff RF Failure Rate - Requesting Sector

This metric provides the rate at which hard handoff attempts fail from the requesting
sector perspective after the AN has sent a handoff TCA to the AT and the AN has timed
out waiting for a TCC in response. Such failures are caused by RF impairments, either
because the AT could not receive the TCA or the AN could not decode the TCC, despite
sector.
Formula
DO Hard HO RF Failure Rate Requesting Sector (%) =
HHOFF_FAIL_NO_AT_RSP_REQ
----------------------------------------------------------- X 100
HHOFF_TCA_SENT_REQ
Count Definitions
Hard HO failures due to no response from the AT in response to a TCA
sent by the AN.
TCA sent in response to a hard handoff request.
............................................................................................................................................................................................................................................................

Formula
--------------------------------------------------------------------------------- X 100
Count Definitions
TCA sent by the AN.
1xEV-DO Hard Handoff RF Failure Rate - Target Sector

This metric provides the rate at which hard handoff attempts fail from the target sector
............................................................................................................................................................................................................................................................
Formula
DO Hard HO RF Failure Rate Target Sector (%) =
HHOFF_FAIL_NO_AT_RSP_TARGET
--------------------------------------------------------------------------------- X 100
HHOFF_TCA_SENT_TARGET
Count Definitions
HHOFF_FAIL_NO_AT_RSP_TARGET =
sent by the AN.
HHOFF_TCA_SENT_TARGET =
............................................................................................................................................................................................................................................................
Performance Metrics for Release 26 Data Transmission Metrics
Data Transmission Metrics

............................................................................................................................................................................................................................................................

in RLP NAKs.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
extremely low error probability channel. The upper layers were designed
for wired connections, and do not operate well on a lossy channel.

layer or packet drops within the AN/AT. For example, problems in the cell aggregation
router or backhaul link can drop some RLP packets before they reach the RNC. The TP in
the RNC is responsible for processing RLP packets. When the TP encounters a gap in the
sequence number on the incoming RLP stream, it declares a RLP NAK; the underlying
physical layer delivery might have been perfectly fine.
Formula
MISSING_RLP_REQ_RTC
RLP_RXED_RTC
Count Definitions

............................................................................................................................................................................................................................................................

Formula
-------------------------------------------------------------- X 100
MISSING_RLP_REQ_RTC
............................................................................................................................................................................................................................................................
Count Definitions

retransmit it.

MAC layer.
Formula
------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
(1024 bits/packet)
............................................................................................................................................................................................................................................................
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
long format (2048 1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
............................................................................................................................................................................................................................................................
(1024 bits/packet)

rates. The MAC layer packet counts include both the traffic and the signalling packets
transmitted by a sector to serve all active users during the hour.The MAC layer Data rate is
effectively a measure of sector data rate. There can be several users on a sector requesting
data concurrently, but the scheduler serves only one user in a given slot by the very nature
of time-shared 1xEV-DO scheduler on the forward link.
In 1xEV-DO, active users continuously request the rate (commonly known as DRC rate) at
which they could be served forward link data. If the cell decides to serve a particular user,
it must do so at the mobile requested rate. Although the user is chosen by the cell, the rate
is governed by the corresponding user. The rate itself is a function of RF conditions at the
mobile. This data rate metric can be interpreted as a measure of RF efficiency of the
sector.Furthermore, the metric in the denominator counts up the active transmission slots
only once, not multiple times if there are multiple users in the queue. These considerations
Only the actual traffic serving slots are used to compute the data rate. This means any gaps
in data transfer caused by user think time, Internet delays, backhaul congestions, TCP
backoffs, etc. will not impact the measured data rate. Rather it is simply an indication of
the rate at which users were served in the traffic channel slots. The metric is a reflection of
RF conditions at the time the user was served.
............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
milliseconds). The user of this metric should monitor the MODEM_ELAPSED_TIME
peg count, which indicates the time in seconds during the measurement hour since the last
the denominator indicating the time used to send data will not accurately reflect the slots
since the last modem reboot. If this happens, the calculated value of forward MAC layer
data rate for that hour should be ignored.
............................................................................................................................................................................................................................................................
Formula
DO Forward link MAC data rate (kbps) =
--------------------------------------------------------------------------------------------------------
Count Definitions
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
............................................................................................................................................................................................................................................................
long format (1024bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
(1024 bits/packet)
EVM_TOTAL_BUSY_PCNT_SLOTS=
Percentage of physical layer slots in the measurement hour used for

............................................................................................................................................................................................................................................................
users.
or another peg count called E vm _A v g_ El i g_ U se r (Average number of Scheduler
Eligible Users to determine if indeed there are a large number of users responsible for
driving up the loading.
The peg count is measured in the modem at the physical layer (slots are only defined at the
physical layer).
previous releases beginning with R22. Note that the peg count measures only those slots
used for actual traffic transmission so the control slot counts do not have to be subtracted.
Formula
Count Definitions
get percentage)

per second.
The metric is defined on a per sector-carrier basis and is defined only for the one hour
............................................................................................................................................................................................................................................................
The metric carries a "sector level" connotation rather than a "per user" view given the
denominator includes the total traffic channel slots used in an hour. So it reflects the
average RF conditions the sector serves. The RLP byte count is closer to the actual user
There are several caveats regarding the use of this metric.
It does not capture a very small amount of throughput loss due to some of the re-
transmitted RLP packets not reaching the end user (typically ~0.02% for a 1% re-
transmission rate).
It may slightly inflate the data rate at virtual soft handoff events. The RLP bytes are
pegged at the TP before getting transmitted to the cell. In case of virtual soft handoff,
some small amount of data gets transmitted to both the old and the new cells, resulting
in double pegging at the TP.
The above issue does not impact virtual softer handoffs. However, there could be small
amount of error stemming from pegging bytes on the older sector a little while longer
than actual virtual softer handoff transfer. There is no impact if RLP bytes are viewed
on a per-cell basis or RNC/SN wide.
The impact of the second and third issues is most noticeable at very low loading points
where RLP bytes appear larger than the MAC data volume on a given sector. Given the
above issues, RLP data rate should only be viewed as an estimate of actual rate, although it
is not far off the mark especially at moderate to high low loading points.
............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------------------------
Count Definitions


megabytes.
The metric is defined on a per sector-carrier basis. The peg counts are measured at the
RLP layer.
This metric provides a measure of the data volume sent in the forward direction per active
connection. The RLP byte count represents actual user traffic with less overhead than
either MAC layer or physical layer packet counts, which can be padded with dummy bits
to fill the packet. Although the peg count name in the denominator is "Average Active
Connections" it is actually the sum of all the total connections based on a 10 second scan.
Note that if the count is read from IBM Prospect for Alcatel-Lucent it has already been
Formula
-----------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
1xEV-DO Average Reverse Link Physical Layer Data Volume (MB)

Formula
---------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions
............................................................................................................................................................................................................................................................
1xEV-DO Average Reverse Link Physical Layer Data Rate (kbps)

This metric gives the average data rate on the reverse link in kilobits per second. The
The metric provides a measure of individual user data rate, a good indicator of average
user experience in the network on the reverse link. Beyond a certain number of users on
the sector, the individual user rate begins to suffer because of the limited bandwidth on the
air link. This behavior points to its possible use in capacity planning for the reverse link.
no or small number of user connections, which will underreport the true sector level data
rates.
Formula
----------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

layer, and properly accounts for re-transmissions and data lost.
Formula
----------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
............................................................................................................................................................................................................................................................
Error Statistics
............................................................................................................................................................................................................................................................

level.
Formula
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Power Control
............................................................................................................................................................................................................................................................

Formula
--------------------------------------------------------------------------------
Count Definitions



Formula
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

dB/8.


Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.


............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.


Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................

Formula
---------------------------------------------------------------------------------
Count Definitions

count are dB/8.

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO. For example, if there are 10 connections on the sector at a given time and only
2 of them are really using their connections to upload some data, the remaining 8 are still
utilizing some of the reverse link bandwidth (typically, only pilot, MAC and Ack channels
- no traffic). This will get considered as 10 active connections. On the forward link, let's
say the same two users are also downloading. Each user will contend and get served on
some of the time slots, but the point is that the presence of 10 connections on the reverse
link have no bearing on the forward link utilization.
level.
again.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Release 26

............................................................................................................................................................................................................................................................
Overview
The purpose of this section is to provide descriptions of obsolete, new and modified
Prospect Primitive Calculations (PCALCs) that support 1xEV-DO Performance Metrics
defined for RNC R26.
The new and modified PCALCs defined in this section are implemented in RNC R26 of
Prospect. Prospect R26 also supports earlier RNC releases.
Existing PCALCs supporting 1xEV-DO performance metrics that did not change in RNC
releases, refer to:
Chapter 8, 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 24
Chapter 10, 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release
25.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in Watchmark Prospect for Alcatel- 1xEV-DO Performance Metrics
Lucent Release 26
Changes this release
Modified Metric
_________________________________________________ Prospect Name
_________________________
_________________________________________________ DOp_FastCnctSuc
_________________________
_________________________________________________ DOp_EstCall
_________________________
_________________________________________________ DOp_InefCallAttTotal
_________________________
_________________________________________________ DOp_EstCnct
_________________________
_________________________________________________ DOp_InefCnctAttTotal
_________________________
_________________________________________________ DOp_DropCall
_________________________
1xEV-DO Droped Connection Rate
_________________________________________________ DOp_DropCnct
_________________________
New Metric
_________________________________________________ Prospect Name
_________________________
_________________________________________________ DOp_RFFail
_________________________
1xEV-DO RF Failure Rate - Pegged
_________________________________________________ DOp_RFFail_Peg
_________________________
1xEV-DO AT-Initiated Connection Blocking Rate - Session Setup _________________________
_________________________________________________ DOp_ATInitConnBlk_SessSU
_________________________________________________ DOp_CnctBlk
_________________________
_________________________________________________ DOp_HHSucc_ReqSect
_________________________
_________________________________________________ DOp_HHSucc_TgtSect
_________________________
_________________________________________________ DOp_HHBlk_ReqSect
_________________________
_________________________________________________ DOp_HHBlk_TgtSect
_________________________
1xEV-DO Hard Handoff RF Failure Rate - Requesting Sector _________________________
_________________________________________________ DOp_HHRFFail_ReqSect
_________________________________________________ DOp_HHRFFail_TgtSect
_________________________
Deleted Metric
_________________________________________________ Prospect Name
_________________________
_________________________________________________ DOp_InefCallAttANInit
_________________________
_________________________________________________ DOp_InefCallAttATInit
_________________________
_________________________________________________ DOp_RFFailANInit
_________________________
_________________________________________________ DOp_RFFailATInit
_________________________
_________________________________________________ DOp_InefCnctAttANInit
_________________________
_________________________________________________ DOp_InefCnctAttATInit
_________________________
_________________________________________________ DOp_CnctBlkANInit
_________________________
AT-Initiated Connection Blocking Rate
_________________________________________________ DOp_CnctBlkATInit
_________________________
AN-Initiated Blocking Ratio Due to No Resources
_________________________________________________ DOp_CnctBlkANInit_NoRsrc
_________________________
AT-Initiated Blocking Ratio Due to No Resources
_________________________________________________ DOp_CnctBlkATInit_NoRsrc
_________________________
% Connection Attempt Failures Due to No Response to Traffic _________________________
DOp_CnctFlNoRspTCA
Channel Assignment
_________________________________________________
............................................................................................................................................................................................................................................................
1xEV-DO Performance Metrics Modified in Prospect R26

............................................................................................................................................................................................................................................................

Valid Releases: RNC 26 and later
D Op _ Fa st C nc tS u c = 10 0. 0 * (F a st C on ne c t - F a st C on Fl N oT CC m pR c v -
F as t Co nF l Re vL n kN o tA cq - Fa st C on n ec tF l No Re s ou r ce ) / F as tC o nn ec t
Notes:
Prospect
Traffic
FastConnectFlNoResource FAST_CONNECT_FAIL_NO_RSC
2. For the previous version of this metric, see:

R25: Fast Connect Success Rate (p. 10-11)

D Op _ Es tC a ll = 10 0 .0 * (A TI n it C on Rq + AN I ni t Co nR q -
S es s Cl os e _S es s Tr n fA bo r t - A TI n it Co n At tF l No R es rc -
A TI n it Co n At tF l No T CC mp R cv - AT I ni tC o nA tt F lN o RL -
A TI n it Co n At tF l Ot h er - AN In i tC o nA tt F lN oR e sr c -
A NI n it Co n At tF l No T CC mp R cv - AN I ni tC o nA tt F lN o RL -
A NI n it Co n At tF l Ot h er + C ro s sC a rr At t mp tR c vd T CC Rc v d -
C ro s sC ar r At tm p tS e nt TC C Rc vd ) / (A TI n it Co n Rq -
A TI n it Co n nA tt m pt D if fS e cC ar r Se n t +
A TI n it Co n nA tt m pt D if fS e cC ar r Rc v d + A NI ni t Co n Rq -
A NI n it Co n nA tt m pt D if fS e cC ar r Se n t +
A NI n it Co n nA tt m pt D if fS e cC ar r Rc v d - S es sC l os e _S es s Tr nf A bo r t)
............................................................................................................................................................................................................................................................
Notes:
Prospect
Traffic
ATInitConAttFlOther N/A 1xEV_Sector
Prospect PCALC Carrier
ANInitConAttFlOther
CrossCarrAttmptRcvdTCCRcvd CROSS_CARR_ATTMPT_RCVD_TCC_RCVD
CrossCarrAttmptSentTCCRcvd CROSS_CARR_ATTMPT_SENT_TCC_RCVD
ANInitConnAttmptDiffSecCarrRcvd AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD
ANInitConnAttmptDiffSecCarrSent AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT
ATInitConnAttmptDiffSecCarrRcvd AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD
ATInitConnAttmptDiffSecCarrSent AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT
SessClose_SessTrnfAbort SESS_CLOSE_SESS_TRFR_ABORTED

R23, R24, and R25: 1xEV-DO Established Call Rate (p. 6-3)
............................................................................................................................................................................................................................................................

D Op _ In ef C al lA t tT o ta l = 1 00 . 0 - D Op _ Es tC a ll
Notes:
Prospect
DOp_EstCall NA 1xEV_SectorCarri
er
PCALC

R23, R24 and R25: Total Ineffective Call Attempt Rate (p. 6-7)

D Op _ Es tC n ct = 10 0 .0 * (A TI n it E st ab C on ne c ti o n +
A NI n it Es t ab Co n ne c ti on + C r os s Ca rr A tt mp t Rc v dT CC R cv d -
C ro s sC ar r At tm p tS e nt TC C Rc vd ) / (A TI n it Co n Rq -
A NI n it Co n nA tt m pt D if fS e cC ar r Rc v d - S es sC l os e _S es s Tr nf A bo r t)
............................................................................................................................................................................................................................................................
Notes:
Prospect
Traffic
ANInitEstabConnection AN_INIT_ESTABLISHED_CONN 1xEV_Sector
Carrier

R25: 1xEV-DO Established Connection Rate (p. 10-10)

DO p _I n ef Cn c tA tt T ot a l = 1 00 .0 - D Op _E s tC nc t
Notes:
Prospect Traffic
DOp_EstCnct NA 1xEV_SectorCarrier
PCALC

R25: 1xEV-DO Total Ineffective Connection Attempt Rate (p. 10-12)
............................................................................................................................................................................................................................................................

Prospect Traffic Report Entity: : 1xEV_Sector, 1xEV_SectorCarrier
D Op _ Dr op C al l = 1 0 0. 0 * ( Co n Rl s RL L + C on R ls O th er ) /
( AT I ni tC o nR q + A N In it C on Rq - A TI ni t Co nA t tF l No Re s rc -
A TI n it Co n At tF l No T CC mp R cv - AT I ni tC o nA tt F lN o RL -
A TI n it Co n At tF l Ot h er - AN In i tC o nA tt F lN oR e sr c -
A NI n it Co n At tF l No T CC mp R cv - AN I ni tC o nA tt F lN o RL -
A NI n it Co n At tF l Ot h er + Cr os s Ca r rA tt m pt Rc v dT C CR cv d -
C ro s sC ar r At tm p tS e nt TC C Rc vd )
Notes:
Prospect
Traffic
Carrier

R23, R24, and R25: 1xEV-DO Dropped Call Rate (p. 6-14)
............................................................................................................................................................................................................................................................

DO p _D r op Cn c t = 1 00 . 0 * ( Co nR l sR L L + C on Rl s Ot h er ) /
(A T In i tE st a bC on n ec t io n + A NI n it E st ab C on ne c ti o n +
Cr o ss C ar rA t tm pt R cv d TC CR c vd - Cr o ss Ca r rA tt m pt S en tT C CR cv d )
Notes:
Prospect Traffic
ConRlsRLL CONN_REL_RLL 1xEV_SectorCarrier

R25: 1xEV-DO Dropped Connection Rate (p. 10-13)
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

D Op _ RF Fa i l = 1 00 . 0 * ( ( AT In i tC on A tt F lN oR L + AN In i tC o nA tt F lN oR L
+ A T In it C on At t Fl N oT CC m pR cv + A NI ni t Co nA t tF l No TC C mp Rc v +
A TI n it Co n At tF l Ot h er _P o st TC A + AN In i tC on A tt F lO th e r_ Po s tT C A+
C ro s sC ar r At tm p tR c vd TC A Se nt - C ro ss C ar rA t tm p tS en t TC AS e nt ) -
( Cr o ss Ca r rA tt m pt R cv dT C CR cv d - Cr os s Ca rr A tt m pt Se n tT CC R cv d )) /
( TC A AT In i tC on R q + T CA A NI n it Co n Rq + Cr o ss Ca r rA t tm pt R cv dT C AS e nt
- C r os sC a rr At t mp t Se nt T CA Se n t)
Prospect
Traffic
ATInitConAttFlNoRL AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ 1xEV_Sector
Carrier
ATInitConAttFlOther_PostTCA AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA
ANInitConAttFlOther_PostTCA AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA
CrossCarrAttmptRcvdTCASent CROSS_CARR_ATTMPT_RCVD_TCA_SENT
CrossCarrAttmptSentTCASent CROSS_CARR_ATTMPT_SENT_TCA_SENT
............................................................................................................................................................................................................................................................
1xEV-DO RF Failure Rate - Pegged

DO p _R F Fa il _ Pe g = 1 0 0. 0 * ( (T C AA T In it C on Rq + T CA AN I ni tC o nR q +
Cr o ss C ar rA t tm pt R cv d TC AS e nt - Cr o ss Ca r rA tt m pt S en tT C AS en t ) -
(A N In i tE st a bC on n ec t io n + A TI n it E st ab C on ne c ti o n +
Cr o ss C ar rA t tm pt R cv d TC CR c vd - Cr o ss Ca r rA tt m pt S en tT C CR cv d )) /
(T C AA T In it C on Rq + T CA AN I ni tC o nR q + C r os s Ca rr A tt mp t Rc v dT CA S en t
- C ro s sC ar r At tm p tS e nt TC A Se nt )

Prospect Traffic
TCAATInitConRq TCA_FOR_AT_INIT_CONN_REQ 1xEV_SectorCarrier

DO p _A T In it C on nB l k_ S es sS U = 1 0 0. 0 * ( A TI ni t Co n nR eq S es s -
TC A fo r AT In i tC on n Re q Se ss ) / A T In i tC on n Re qS e ss
Prospect Traffic
ATInitConnReqSess AT_INIT_CONN_REQ_SESS 1xEV_SectorCarrier
TCAforATInitConnReq TCA_FOR_AT_INIT_CONN_REQ_SESS
Sess
............................................................................................................................................................................................................................................................

D Op _ Cn ct B lk = 10 0 .0 * (A NI n it C on Rq -
A NI n it Co n nA tt m pt D if fS e cC ar r Rc v d + A TI ni t Co n Rq -
A TI n it Co n nA tt m pt D if fS e cC ar r Rc v d - S es sC l os e _S es s Tr nf A bo r t -
( TC A AN In i tC on R q + T CA A TI ni t Co n Rq +
C ro s sC ar r At tm p tR c vd TC A Se nt - C ro ss C ar rA t tm p tS en t TC AS e nt ) ) /
( AN I ni tC o nR q - A N In it C on nA t tm p tD if f Se cC a rr S en t +
A NI n it Co n nA tt m pt D if fS e cC ar r Rc v d + A TI ni t Co n Rq -
A TI n it Co n nA tt m pt D if fS e cC ar r Rc v d - S es sC l os e _S es s Tr nf A bo r t)
Prospect
Traffic
Carrier
TCAATInitConRq TCA_FOR_AT_INIT_CONN_REQ
............................................................................................................................................................................................................................................................

DO p _H H Su cc _ Re qS e ct = 10 0 .0 * (H a rd HO A tt - (H a rd HO F lN oR e sc +
Ha r dH O Fl No A TR sp + H ar dH O Fl Ot h er _ Pr eT C A +
Ha r dH O Fl Ot h er _P o st T CA )) / Ha r dH O At t
Prospect Traffic
HardHOAtt HHOFF_ATTMPT_REQ 1xEV_SectorCarrier
HardHOFlNoResc HHOFF_FAIL_NO_RESOURCE_REQ
HardHOFlNoATRsp HHOFF_FAIL_NO_AT_RESP_REQ
HardHOFlOther_PreTCA HHOFF_FAIL_OTHER_PRETCA_REQ
HardHOFlOther_PostTCA HHOFF_FAIL_OTHER_POSTTCA_REQ

DO p _H H Su cc _ Tg tS e ct = 10 0 .0 * (H a rd HO A tt _T g t -
(H a rd H OF lN o Re sc _ Tg t + H a rd HO F lN o AT Rs p _T gt +
Ha r dH O Fl Ot h er _P r eT C A_ Tg t + H a rd H OF lO t he r_ P os t TC A_ T gt )) /
Ha r dH O At t_ T gt
Prospect Traffic
HardHOAtt_Tgt HHOFF_ATTMPT_TARGET 1xEV_SectorCarrier
HardHOFlNoResc_Tgt HHOFF_FAIL_NO_RESOURCE_TARGET
HardHOFlNoATRsp_Tgt HHOFF_FAIL_NO_AT_RESP_TARGET
HardHOFlOther_PreTCA_Tgt HHOFF_FAIL_OTHER_PRETCA_TARGET
HardHOFlOther_PostTCA_Tgt HHOFF_FAIL_OTHER_POSTTCA_TARGET
............................................................................................................................................................................................................................................................

D Op _ HH Bl k _R eq S ec t = 1 0 0. 0 * ( H ar dH O At t - H a rd HO A tt TC A Se n t) /
H ar d HO At t
Prospect Traffic
HardHOAttTCASent HHOFF_TCA_SENT_REQ

D Op _ HH Bl k _T gt S ec t = 1 0 0. 0 * ( H ar dH O At t_ T gt -
H ar d HO At t TC AS e nt _ Tg t) / Ha r dH O At t_ T gt
Prospect Traffic
HardHOAtt_Tgt HHOFF_ATTMPT_TARGET 1xEV_SectorCarrier
HardHOAttTCASent_Tgt HHOFF_TCA_SENT_TARGET
............................................................................................................................................................................................................................................................

DO p _H H RF Fa i l_ Re q Se c t = 1 00 .0 * H ar dH O Fl No A TR s p /
Ha r dH O At tT C AS en t
Prospect Traffic
HardHOFlNoATRsp HHOFF_FAIL_NO_AT_RSP_REQ 1xEV_SectorCarrier
HardHOAttTCASent HHOFF_TCA_SENT_REQ

DO p _H H RF Fa i l_ Tg t Se c t = 1 00 .0 * H ar dH O Fl No A TR s p_ Tg t /
Ha r dH O At tT C AS en t _T g t
Prospect Traffic
HardHOFlNoATRsp_Tgt HHOFF_FAIL_NO_AT_TARGET 1xEV_SectorCarrier
HardHOAttTCASent_Tgt HHOFF_TCA_SENT_TARGET
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

New metrics were added for
Forward and Reverse Link data volume and data rates at the physical and RLP layers
based on the new counts provided by the single board EVM (SBEVM),
per user data rate metrics for the forward link physical and RLP layers, and
new average reverse link power control setpoint metrics using the new SBEVM
counts.
Revisions were made to
The soft/softer handoff success rate and blocking rate metrics to account for the
connection/session close during handoff counts.
In R26 a new single board EVM (SBEVM) was introduced and can be used to replace the
older EVM which occupied two card slots. In R27 the new SBEVM is capable of
supporting Rev A connections. Some service measurements and hence, some metrics, are
only applicable to the new SBEVM, while others are applicable only to the older EVM
(referred to as EVM), and still others are applicable to both. Those metrics that are only
applicable to either the EVM or the SBEVM are clearly indicated as such.
The new metrics and changes to existing metrics are applicable beginning with R27 since
they are involved with new peg counts.
............................................................................................................................................................................................................................................................
New metrics:
1xEV-DO Configuration Negotiation Success Rate (p. 13-14)
1xEV-DO Total Forward Link Physical Layer Data Transmitted - SBEVM (MB) (p.
13-62)
1xEV-DO Average Forward Link Physical Layer Date Rate - SBEVM (kbps) (p.
13-68)
1xEV-DO Composite Average Forward Link Physical Layer Data Rate (p. 13-74)
1xEV-DO Forward Link Physical Layer Data Rate per User - SBEVM (p. 13-75)
1xEV-DO Average RLP Forward Link Data Rate with SBEVM (kbps) (p. 13-80)
1xEV-DO Average Forward Link RLP Data Rate per User - SBEVM (kbps) (p.
13-83)
1xEV-DO Average Reverse Link Physical Layer Data Volume with SBEVM (MB)
(p. 13-85)
1xEV-DO Average Reverse Link Physical Layer Data Rate with SBEVM (kbps) (p.
13-88)
1xEV-DO Composite Average Reverse Link Physical Layer Data Rate (p. 13-91)
1xEV-DO Reverse Link RLP Data Throughput with SBEVM (p. 13-93)
1xEV-DO Composite Reverse Link RLP Data Throughput (p. 13-95)
1xEV-DO Average Reverse Link Power Control Setpoint - 128 bits - SBEVM (p.
13-102)
13-102)
13-103)
13-103)
13-104)
13-104)
13-105)
13-105)
13-106)
13-106)
............................................................................................................................................................................................................................................................
13-107)
13-107)
1xEV-DO "Primary" Traffic Channel Usage (in Erlangs) - SBEVM (p. 13-109)
1xEV-DO Soft/Softer Handoff Overhead with SBEVM (p. 13-110)
Revised metrics:
1xEV-DO Soft/Softer Handoff Success Rate - Requesting Sector (p. 13-45)
1xEV-DO Soft/Softer Handoff Success Rate - Target Sector (p. 13-48)
1xEV-DO Soft/Softer Handoff Blocking Rate - Requesting Sector (p. 13-50)
1xEV-DO Soft/Softer Handoff Blocking Rate - Target Sector (p. 13-53)
1xEV-DO Soft/Softer Handoff RF Failure Rate - Requesting Sector (p. 13-54)
1xEV-DO Soft/Softer Handoff RF Failure Rate - Target Sector (p. 13-56)
Descriptions revised to indicate that they are only applicable to sectors equipped
with a dual board EVM:
1xEV-DO Total Forward Link MAC Data Transmitted - EVM (MB) (p. 13-61)
1xEV-DO Average Forward Link MAC Data Rate - EVM (kbps) (p. 13-64)
1xEV-DO Average RLP Forward Link Data Rate (kbps) (p. 13-78)
1xEV-DO Average Reverse Link Physical Layer Data Volume - EVM (MB) (p.
13-84)
1xEV-DO Average Reverse Link Physical Layer Data Rate - EVM (kbps) (p. 13-87)
1xEV-DO Reverse Link RLP Data Throughput - EVM (p. 13-92)
1xEV-DO Reverse Frame Error Rate - EVM (p. 13-96)
Power Control (p. 13-98)
The following performance metrics are provided in R27 (new metrics are in italics):
1xEV-DO Configuration Negotiation Success Rate
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

a. Connection Setup
b. Connection Drop
c. Handoff
1xEV-DO Forward Link Data Re-transmission Rate
1xEV-DO Total Forward Link MAC Data Transmitted - EVM (MB)
1xEV-DO Total Forward Link Physical Layer Data Transmitted - SBEVM (MB)
1xEV-DO Average Forward Link MAC Data Rate - EVM (kpbs)
1xEV-DO Average Forward Link Physical Layer Date Rate - SBEVM (kbps)
1xEV-DO Composite Average Forward Link Physical Layer Data Rate
1xEV-DO Average Forward Link Physical Layer Data Rate per User - SBEVM
(kbps)
1xEV-DO Percent Forward Link Bandwidth used for Traffic
1xEV-DO Average RLP Forward Link Data Rate with SBEVM (kbps)
............................................................................................................................................................................................................................................................
1xEV-DO Average RLP Forward Link Data Rate per User (kbps) - SBEVM
1xEV-DO Average Forward Link RLP Data Volume per User (MB)
1xEV-DO Average Forward Link RLP Data Rate per User - SBEVM (kbps)
1xEV-DO Average Reverse Link Physical Layer Data Volume - EVM (MB)
1xEV-DO Average Reverse Link Physical Layer Data Volume with SBEVM
1xEV-DO Average Reverse Link Physical Layer Data Rate - EVM (kbps)
1xEV-DO Average Reverse Link Physical Layer Data Rate with SBEVM (kbps)
1xEV-DO Composite Average Reverse Link Physical Layer Data Rate
1xEV-DO Reverse Link RLP Data Throughput - EVM (kbps)
1xEV-DO Reverse Link RLP Data Throughput with SBEVM (kbps)
1xEV-DO Composite Reverse Link RLP Data Throughput
e. Error Statistics
1xEV-DO Reverse Frame Error Rate - EVM
f. Power Control
1xEV-DO Average Reverse Link Power Control Setpoint - 0 kbps - EVM
1xEV-DO Average Reverse Link Power Control Setpoint - 9.6 kbps - EVM
1xEV-DO Average Reverse Link Power Control Setpoint - 128 bits - SBEVM
1xEV-DO Average Reverse Link Power Control Setpoint - 8192bits - SBEVM
1xEV-DO "Primary" Traffic Channel Usage (in Erlangs) - SBEVM
1xEV-DO Soft/Softer Handoff Overhead with SBEVM
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
Formula
-------------------------------------------------------------------------------------------------X 100
Count Definitions

UATI request message for new and prior session setups)
............................................................................................................................................................................................................................................................
Session Set Up - UATI Complete Message Received (new and prior).
Pegged when the AT acknowledges a UATI assignment message sent by
the AN in response to a UATI request.
Session Set Up - UATI Complete Message Received (assign first and color
code)

communicate and exchange proper information in case of Color Code method of inter-
RNC idle handoff. A ratio less than 1 is reflective purely of a AN issue; no over the air
Formula
----------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ =
message for new and prior session setups)
............................................................................................................................................................................................................................................................
code)

during the measurement interval. It is defined on a per AP basis. Note that the
measurement interval may not be exactly one hour so the calculation is approximate.
Formula
360
Count Definitions
approximate.
............................................................................................................................................................................................................................................................

intervention.
............................................................................................................................................................................................................................................................
Formula
INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ))
-------------------------------------------------------------------------------------------------- X100
Count Definitions
instead.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
is, 255.255.255.255 or NULL).

The metric is new in R25 and is effective beginning with R25.There are several individual
These counts are defined in 401-614-326, 1xEV-DO Service Measurements. These counts
should be monitored by service providers, especially if the failure rate is high.
Formula
--------------------------------------------------- x 100
............................................................................................................................................................................................................................................................
Count Definitions

This metric gives the success rate of the configuration negotiation procedure during
session setup. Configuration negotiation takes place during session setup after an active
connection has successfully been established. The peg counts are defined on a sector-
carrier basis and are pegged against the DRC-pointed sector-carrier at the time of
configuration negotiation.
This metric is new in R27 and is effective beginning with R27 since in prior releases not
all counts were pegged on the same sector-carrier.
Formula
DO Config Nego Success Rate (%) =
(CONFIG_NEGO - AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED -
---------------------------------------------------------------------------------------------------- X 100
CONFIG_NEGO
Count Definitions
CONFIG_NEGO = This count is incremented for each established connection where the
configuration negotiation procedure takes place. It is pegged against the
sector-carrier on which the configuration negotiation procedure takes
place.
AN_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED = The number of times a

configuration negotiation initiated by the AN failed because the
Configuration Response message was not received from the AT. It is
pegged against the last known DRC-pointed sector-carrier at the time the
configuration negotiation process is declared a failure.
............................................................................................................................................................................................................................................................
AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED = The number of times a

configuration negotiation initiated by the AT failed because the
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

results in what is known as PCF or network reactivation, as discussed above.The PCF
reactivation failures can be contributed by RF failures (resulting in Page timeout or AN
initiated Connection Failure or Fast Connect Failure), any system bottlenecks (such as
inability to allocate traffic channel resources), AT not reachable (such as AT powered off
or moved to a different RNC without a clean inter-RNC idle handoff), etc.
Formula
------------------------------------------------------------------------------ X 100
Count Definitions
end user.
PDSN.
............................................................................................................................................................................................................................................................

on the R-P link.
handoff.
failures.The peg counts are defined on a per TP basis.
The name of this metric was changed in R25.
Formula
------------------------------------------------------------------------------ X 100
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS =
............................................................................................................................................................................................................................................................
RP_CONN_FAIL =
service).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

3G1X.
than the AT Initiated Connections.There are various reasons that can cause connection
failures - such as blocking at the AN, internal errors allocating TCA, sub-optimal RF
conditions between the AT/AN resulting in missed messages between the AN/AT, etc.In
general, a connection is said to be established when the AN has received a Traffic Channel
Complete message from the AN. This is conceptually very similar to receiving a Service
Connect Complete Message from the mobile in a IS2000 system.
for a Connection.The peg counts are defined on a per sector-carrier basis and can be rolled
level. The formula is revised in R27 to remove the
SESS_CLOSE_SESS_TRFR_ABORTED count since these instances are pegged as part
of the pre-tca failures count beginning with R26 SU1. The new formula is effective
beginning with R27.
............................................................................................................................................................................................................................................................
Formula
CROSS_CARR_ATTMPT_RCVD_TCC_RCVD -
CROSS_CARR_ATTMPT_SENT_TCC_RCVD)
--------------------------------------------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
............................................................................................................................................................................................................................................................
AT_INIT_CONN_REQ =
Connection Request.
CROSS_CARR_ATTMPT_RCVD_TCC_RCVD =
CROSS_CARR_ATTMPT_SENT_TCC_RCVD =
connection request.
attribute set.
............................................................................................................................................................................................................................................................
receiving the TCC.
Ma x _n u mb er _ of _c o nn e ct io n s , a per-sector translation limit.
blocking sector.
............................................................................................................................................................................................................................................................
bottlenecks, etc.
receiving the TCC.
M ax _ nu mb e r_ o f_ co n ne ct i on s , a per-sector translation limit.
Instead, N u m_ Ti m es _ Ma x_ C on n_ R ea c he d count will be pegged on the
blocking sector.
............................................................................................................................................................................................................................................................
bottlenecks, etc.

cell level.
This metric is new for R25 to use the new Established Calls peg counts and is expected to
be more accurate than the old formula. However, it is recommended that customers use
The formula was revised in R27 to remove the SESS_CLOSE_SESS_TRFR_ABORTED
count since these instances are pegged as part of the pre-tca failures count beginning with
R26 SU1. The new formula is effective beginning with R27.
Formula
CROSS_CARR_ATTMPT_SENT_TCC_RCVD)-
---------------------------------------------------------------------------------------------------X 100
............................................................................................................................................................................................................................................................
Count Definitions
channel.)
Number of AT-Initiated successful connections (pegged when a TCC is
channel.)
connection request.
served by this sector-carrier
............................................................................................................................................................................................................................................................


not affected by load balancing or cross-carrier assignments.The Fast Connect failures
could be due to blocking, internal errors when allocating resources for TCA, or RF
reasons similar to an AT/AN initiated TCA.
R26.
Formula
FAST_CONNECT_FAIL_RL_NOT_ACQ - FAST_CONNECT_FAIL_NO_RSC )
---------------------------------------------------------------------------------------------------X 100
(FAST_CONNECT)
Count Definitions
FAST_CONNECT =
failures.
............................................................................................................................................................................................................................................................
preamble.
This count is pegged when the AN is no able to send an Allocate Traffic
on resources available to establish a traffic channel.

connect procedure.
by both.
Formula
--------------------------------------------------------------------------X 100
FAST_CONNECT
Count Definitions

............................................................................................................................................................................................................................................................

messaging failure.
Formula
---------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
assignment).
assignment).
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
............................................................................................................................................................................................................................................................
served by a different sector-carrier.
carrier
carrier
............................................................................................................................................................................................................................................................

Formula
DO AT-Initiated Connection Blocking Rate - Session Setup (%) =
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
AT_INIT_CONN_REQ_SESS = AT Initiated Connection Requests, Session Setup


initiated) that failed. It is defined as 100 - established connection rate (see 1xEV-DO
Established Connection Rate (p. 13-19).
counts defined. The new formula is effective beginning with R26, but can be used in prior
releases.
............................................................................................................................................................................................................................................................
Formula
DO Total Ineffective Connection Rate (%) = 100 - DO Established Connection Rate (%)
Count Definitions
Connection Rate (p. 13-19) for the counts included in the established connection rate
metric.

initiated) that failed. It is defined as 100 - established connection rate - peg (see 1xEV-
DO Established Connection Rate - Peg (p. 13-24).
The formula is revised is R26 for simplification. The old formula could not be used with
the new load balancing (cross-connect feature because the established connection counts
are not defined for cross-connects.
The new formula is effective beginning with R26, but can be used in prior releases.
Formula
Count Definitions
Connection Rate - Peg (p. 13-24) for the counts included in the established connection
rate - peg metric.

signalling and/or actual traffic channel assignment packets leading up to the connection
setup failure.
............................................................................................................................................................................................................................................................
replaces the separate metrics used in prior releases. The formula is revised in R26 to
cross-connects. The new formula is effective beginning with R26.
Formula
CROSS_CARR_ATTMPT_RCVD_TCC_RCVD) -
(CROSS_CARR_ATTMPT_SENT_TCA_SENT -
CROSS_CARR_ATTMPT_SENT_TCC_RCVD))
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
carrier
carrier
............................................................................................................................................................................................................................................................
response to a connection request received on this sector-carrier. It is pegged
against the sector-carrier that received the connection request.
connection request. It is pegged against the strongest sector-carrier selected
for traffic channel allocation by the load balancing algorithm.
connection request.All the failure counts below are pegged as AT or AN
Initiated depending on whether the corresponding Connection Request
message was received with AT or AN Initiated attribute set.
receiving the TCC.
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = This is a catch-all for

remaining failure reasons that prevent a successful connection setup that
bottlenecks, etc.
receiving the TCC.

............................................................................................................................................................................................................................................................
This metric is new for R26 to use the established connection peg counts based on the
revised rf failure rate definition of TCA sent minus established calls. It is expected to be
more accurate than the detailed formula in 1xEV-DO RF Failure Rate (p. 13-32) but it is
recommended that customers use both formulas for a couple of releases to compare the
values obtained by both.
Formula
CROSS_CARR_ATTMPT_SENT_TCA_SENT) -
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
carrier
carrier
............................................................................................................................................................................................................................................................
connection request.

deleted as Alcatel-Lucent supported metrics as of R25. The individual failures can be seen
from the following raw peg counts:
Count definitions
received
............................................................................................................................................................................................................................................................
received

Formula
(1 - ---------------------------------------------------------------------------------------------) X 100
............................................................................................................................................................................................................................................................
Count definitions
PAGE_ATTEMPTS =
errors.

This metric provides the paging failure rate due to RF failures, that is, no response from
the AT being paged. The peg counts are defined on a per AP basis.
Formula
------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

carrier. If the translation is set to continue pegging, then the CONN_REL_RLL count will
include the tuneaways and the dropped call rate will be inflated.
beginning in R26, these failures are included as part of the connection release other
reasons count.
Formula
---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
............................................................................................................................................................................................................................................................
received
received
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = A
T-initiated Connection attempt failures - rev link not acquired
............................................................................................................................................................................................................................................................
AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = A
T-initiated connection attempt failures - no resources available
AN initiated Connection attempt failures - other failures post-TCA
connection request.

carrier. If the translation is set to continue pegging, then the CONN_REL_RLL count will
include the tuneaways and the dropped call rate will be inflated.
beginning in R26 these failures are included as part of the connection release other reasons
count.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
connection request.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

Note that the pre-TCA other failures peg count may include some normal connection
releases that occur prior to sending handoff TCA. Therefore the peg count may be inflated
and the success rate calculation may be artificially low.
The formula is revised in R27 to subtract the new counts that measure the number of times
a connection close or session close is received prior to completion of the handoff
procedure. The new formula is applicable for release R27 and later.
Formula
SO_SOR_HOFF_ATTMPT - SO_SOR_HOFF_CONN_CLOSE_PRETCA -
SO_SOR_HOFF_CONN_CLOSE_POSTTCA -
(SO_SOR_HOFF_FAIL_NO_RESOURCE + SO_SOR_HOFF_FAIL_NO_AT_RSP +
---------------------------------------------------------------------------------------------------- X 100
(SO_SOR_HOFF_ATTMPT - SO_SOR_HOFF_CONN_CLOSE_PRETCA -
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED)
Count Definitions
SO_SOR_HOFF_ATTMPT = This count is the number of soft/er handoff attempts being

processed. If there are multiple triggers in a RUM that are being acted upon
in a single TCA, then the count is pegged only once. Note that the count is
pegged even if the RUM with an add trigger is discarded because the
connection is already at the maximum number of active set legs allowed
and there are no suitable pilots in the active set that can be dropped as part
of the same TCA.
In addition, another count, So_Sor_Hoff_Fail_Max_No_Legs_Reached, is
pegged.
All of these handoff counts are pegged on the sector that received Route Update message,
i.e., the DRC-pointed sector (also known as requesting or source sector).
............................................................................................................................................................................................................................................................
SO_SOR_HOFF_CONN_CLOSE_PRETCA = The number of soft/softer handoffs when

a connection close or session close is received before TCA and prior to
completion of the handoff procedure.
SO_SOR_HOFF_CONN_CLOSE_POSTTCA = The number of soft/softer handoffs when

a connection close or session close is received after TCA but prior to
SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED = Number of times a soft/softer

handoff request cannot be processed because the total number of legs
already has reached the maximum specified by the translation and there is
no strong candidate pilot on the RUM that can replace a weaker active set
pilot. Beginning in R25, handoff attempts will also be pegged when the
maximum number of legs is reached.
SO_SOR_HOFF_FAIL NO_RESOURCE = Soft-Softer HO Attempt failure due to the

AN's inability to send a TCA because the candidate sector being added is
already supporting the maximum number of connections allowed.
SO_SOR_HOFF_FAIL_NO_AT_RSP = Soft-Softer HO Attempt failure due to no

SO_SOR_HOFF_FAIL_OTHER_PRETCA = These are TCA allocation failures

stemming from issues such as no response from the sector being added
(link failures or misconfigured link between cell/RNC), inability to
build/send internal messages, neighbor list provisioning issues, etc.
Basically, it is a catch-all for handoff failures not specifically pegged.
SO_SOR_HOFF_FAIL_OTHER_POSTTCA = Soft-Softer HO Attempt failure due to

other reasons after TCA is sent.
............................................................................................................................................................................................................................................................

Note that the pre-TCA failures peg count may include some normal releases that occur
prior to TCA. Therefore the peg count may be inflated and the success rate calculation
may be artificially low.
Formula
HHOFF_ATTMPT_REQ - (HHOFF_FAIL_NO_RESOURCE_REQ +
-------------------------------------------------------------------------------------------------- X 100
HOFF_ATTMPT_REQ
Count Definitions
HHOFF_ATTMPT_REQ =
inter-frequency handoff is necessary.All of these handoff counts are pegged
on the sector-carrier that received Route Update message.
............................................................................................................................................................................................................................................................

This metric gives the success rate for soft/softer handoffs to the target sector (hand-ins).
Formula
SO_SOR_HOFF_CONN_CLOSE_PRETCA_TARGET -
SO_SOR_HOFF_CONN_CLOSE_POSTTCA_TARGET -
------------------------------------------------------------------------------------------------ X 100
Count Definitions
SO_SOR_HOFF_ATTMPT_TARGET = Soft-Softer HO Attempt at the target sector-

carrier
SO_SOR_HOFF_CONN_CLOSE_PRETCA_TARGET = The number of soft/softer

handoffs when a connection close or session close is received before TCA
and prior to completion of the handoff procedure.
SO_SOR_HOFF_CONN_CLOSE_POSTTCA_TARGET = The number of soft/softer

handoffs when a connection close or session close is received after TCA
but prior to completion of the handoff procedure.
............................................................................................................................................................................................................................................................
SO_SOR_HOFF_NOP_MAX_LEGS_TARGET = Number of times a soft/softer handoff

request cannot be processed because the total number of legs has reached
the maximum specified by the translation. Handoff attempts will also be
pegged when the maximum number of legs is reached.
SO_SOR_HOFF_FAIL NO_RESOURCE_TARGET = Soft-Softer HO Attempt failure at

the target sector-carrier due to no resources
SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET = Soft-Softer HO Attempt failure at the

target sector-carrier due to no response from the AT
SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET = Soft-Softer HO Attempt failure

at the target sector-carrier due to other reasons prior to traffic channel
assignment
SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET = Soft-Softer HO Attempt

failure at the target sector-carrier due to other reasons after traffic channel
assignment

This metric gives the success rate for hard handoffs to the target sector ("hand-ins"). The
Formula
HHOFF_ATTMPT_TARGET - (HHOFF_FAIL_NO_RESOURCE_TARGET +
HHOFF_FAIL_NO_AT_RSP_TARGET + HHOFF_FAIL_OTHER_PRETCA_TARGET
+ HHOFF_FAIL_OTHER_POSTTCA_TARGET)
--------------------------------------------------------------------------------------------------- X 100
HHOFF_ATTMPT_TARGET
Count Definitions

............................................................................................................................................................................................................................................................

carrier due to no response from the AT



sources.
sector.
............................................................................................................................................................................................................................................................
Formula
SO_SOR_HOFF_ATTMPT_TCA_SENT)
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
SO_SOR_HOFF_ATTMPT = Soft-Softer HO Attempt

SO_SOR_HOFF_ATTMPT_TCA_SENT = This count is pegged if upon inspecting a

RUM from the AT, the AN decides to perform soft/er handoff. If the TCA
allocation process succeeds (only needed for an add at the candidate cell,
for drop traffic channel resource de-allocation is performed after receiving
TCC), the AN sends TCA to apprise the AT of the new active set. When the
TCA is sent, AN pegs the SO_SOR_HOFF_ATTMPT_TCA_SENT count.
By definition, it signifies a successful traffic channel resource allocation,
but pending TCC from the AT.

already has reached the maximum specified by the translation. Beginning
in R25, handoff attempts will also be pegged when the maximum number
of legs is reached.

............................................................................................................................................................................................................................................................
sources.
the cell).
sector.
The metric is new in R26 and is effective with R26.
Formula
HHOFF_ATTMPT_REQ - HHOFF_TCA_SENT_REQ
------------------------------------------------------------------------------------------ X 100
HHOFF_ATTMPT_REQ
Count Definitions
HHOFF_ATTMPT_REQ =
to perform an inter-frequency hard handoff.
Important! Both of these handoff counts are pegged on the sector-carrier that
received Route Update message, i.e., the DRC-pointed sector (also known as
requesting or source sector).
............................................................................................................................................................................................................................................................

sector.
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions

SO_SOR_HOFF_ATTMPT_TCA_SENT_TARGET = TCA sent in response to a

soft/softer handoff attempt

............................................................................................................................................................................................................................................................

Formula
HHOFF_ATTMPT_TARGET - HHOFF_TCA_SENT_TARGET
-------------------------------------------------------------------------------------- X 100
HHOFF_ATTMPT_TARGET
Count Definitions
HHOFF_TCA_SENT_TARGET = TCA sent in response to a hard handoff attempt

sector.
The formula is revised in R27 to subtract the new count that measures the number of times
a connection close or session close is received after TCA is sent but prior to completion of
the handoff procedure. The new formula is applicable for release R27 and later.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------ X 100
(SO_SOR_HOFF_ATTMPT_TCA_SENT -
SO_SOR_HOFF_CONN_CLOSE_POSTTCA)
Count Definitions
TCA sent by the AN.

a connection close or session close is received after TCA but prior to

sector.
Formula
----------------------------------------------------------- X 100
HHOFF_TCA_SENT_REQ
............................................................................................................................................................................................................................................................
Count Definitions
sent by the AN.

Formula
--------------------------------------------------------------------------------- X 100
(SO_SOR_HOFF_ATTMPT_TCA_SENT_TARGET -
SO_SOR_HOFF_CONN_CLOSE_POSTTCA_TARGET)
Count Definitions
TCA sent by the AN.
............................................................................................................................................................................................................................................................


Formula
--------------------------------------------------------------------------------- X 100
HHOFF_TCA_SENT_TARGET
Count Definitions
sent by the AN.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

in RLP NAKs.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
extremely low error probability channel. The upper layers were designed
for wired connections, and do not operate well on a lossy channel.

Formula
MISSING_RLP_REQ_RTC
RLP_RXED_RTC
Count Definitions

............................................................................................................................................................................................................................................................

Formula
-------------------------------------------------------------- X 100
MISSING_RLP_REQ_RTC
............................................................................................................................................................................................................................................................
Count Definitions

retransmit it.

MAC layer.
These counts are only measured in the EVM. Beginning with R27, this metric will report
'zero' for sector-carriers equipped with a single board EVM (SBEVM). New metrics are
provided for the physical layer for sector-carriers equipped with an SBEVM.
Formula
------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
EVM_FWD_PACKETS_38_4_TOTAL_COUNT = Total MAC packets transmitted on


............................................................................................................................................................................................................................................................



EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT = Total MAC packets transmitted







This metric gives the average data volume in the physical layer on the forward link in
megabytes. The peg counts are measured in the SBEVM at the physical layer.
The metric is defined on a per sector-carrier basis and is applicable to sector-carriers
equipped with a SBEVM, replacing the MAC layer data transmitted metric in 1xEV-DO
Total Forward Link MAC Data Transmitted - EVM (MB) (p. 13-61). The counts are the
total of all Rel 0 and Rev A connections. The MAC layer data transmitted metric is still
applicable to sector-carriers equipped with an EVM. This metric is new in R27 and is not
applicable to prior releases.
............................................................................................................................................................................................................................................................
Formula
DO Forward Link Physical Layer Data Xmitted - SBEVM (MB) =
(EVM_FTC_TOT_BYTES_4_8 + EVM_FTC_TOT_BYTES_9_6 +
EVM_FTC_TOT_BYTES_19_2 + EVM_FTC_TOT_BYTES_38_4 +
EVM_FTC_TOT_BYTES_1536 + EVM_FTC_TOT_BYTES_1843_2 +
EVM_FTC_TOT_BYTES_2457_6 + EVM_FTC_TOT_BYTES_3072)
-----------------------------------------------------------------------------------------------------------
10 ^ 6
Count Definitions
EVM_FTC_TOT_BYTES_4_8 = The number of Physical Layer bytes transmitted on the

FTC by the SBEVM to the AT at a nominal rate of 4.8 kbps for both Rel 0
and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.
EVM_FTC_TOT_BYTES_153_6 = The number of Physical Layer bytes transmitted on

the FTC by the SBEVM to the AT at a nominal rate of 153.6 kbps for both
Rel 0 and Rev A traffic.
............................................................................................................................................................................................................................................................




EVM_FTC_TOT_BYTES_1536 = The number of Physical Layer bytes transmitted on the

FTC by the SBEVM to the AT at a nominal rate of 1536 kbps for both Rel
0 and Rev A traffic.



1xEV-DO Average Forward Link MAC Data Rate - EVM (kbps)

............................................................................................................................................................................................................................................................
In 1xEV-DO, active users continuously request the rate (commonly known as DRC rate) at
it must do so at the AT requested rate. Although the user is chosen by the cell, the rate is
governed by the corresponding user. The rate itself is a function of RF conditions at the
sector.
once, not multiple times if there rate (data served / total wait time), but is a very good
indication of the sum of individual user perceived data rates. For example, if there are 10
users each getting 100 kbps continuously over the hour or 1 user getting 1Mbps
throughout the hour, the metric will report 1Mbps in both the cases.
scheduler gain kicks in. The scheduler exploits short-term temporal variations in RF
............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
The packet counts are only measured in the EVM. Beginning with R27, this metric will
report 'zero' for sector-carriers equipped with a single board EVM (SBEVM). New metrics
are provided for the physical layer for sector-carriers equipped with an SBEVM. However,
there are difficulties in aggregating this metric to higher level network elements since the
EVM_TOTAL_BUSY_PCNT_SLOTS count is pegged for both modems and does not
differentiate between them. In order to aggregate the forward link MAC layer data rate to a
higher network element the denominator can be calculated as follows:
( ((EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 8) * 2,160,000) -
(EVM_FTC_NUM_SLOT_rate)) * 0.001667
where the summations are over all sector-carriers being aggregated.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------
Count Definitions







............................................................................................................................................................................................................................................................





EVM_TOTAL_BUSY_PCNT_SLOTS = Percentage of physical layer slots in the

second for sector-carriers equipped with an SBEVM, replacing the MAC layer data rate
metric in 1xEV-DO Average Forward Link MAC Data Rate - EVM (kbps) (p. 13-64).
The counts are the total of all Rel 0 and Rev A connections. The MAC layer data rate
metric is still applicable to sector-carriers equipped with an EVM. The metric is defined
on a per sector-carrier basis and is defined only for the one hour measurement interval. It
cannot be directly summed to obtain results for longer time periods. The individual counts
must be rolled up and then the data rate can be calculated. The peg counts are measured in
the SBEVM at the physical layer. In the 1xEV-DO protocol stack, the physical layer
resides below the MAC layer.
The metric is computed using the counts of physical layer bytes transmitted at various
rates and the number of slots used to transmit those bytes. The byte counts include the
traffic packets transmitted by a sector to serve all active users during the hour.
In 1xEV-DO Rel 0, active ATs continuously request the rate (commonly known as DRC
rate) at which they could be served forward link data. If the cell decides to serve a
particular AT, it must do so at the AT requested rate. Although the AT is chosen by the cell,
the rate is governed by the corresponding AT. In Rev A the situation is more complex. The
requested DRC index can contain several transmission format options with different rates.
The cell (scheduler) selects the format based on other considerations including the amount
............................................................................................................................................................................................................................................................
of data to be transmitted to the user, the number of users waiting to send data, QoS,
multiuser packet options, etc. The rate itself is a function of RF conditions at the mobile.
This data rate metric can be interpreted as a measure of RF efficiency of the sector.
This metric utilizes the actual number of slots used to send the data rather than the percent
busy slots count used by the EVM. Note that since the metric in the denominator counts up
the actual active transmission slots it's not counting multiple times if there are multiple
ATs in the queue. These considerations point out that the metric does not represent
individual user data rate (data served / total wait time), but is a very good indication of the
sum of individual user data rates. For example, if there are 10 ATs each getting 100 kbps
continuously over the hour or 1 AT getting 1Mbps throughout the hour, the metric will
report 1Mbps in both the cases.
Only the actual serving slots are used to compute the data rate. This means any gaps in
data transfer caused by user think time, Internet delays, backhaul congestions, TCP
Alternatively, the physical layer transmitted bytes can be utilized to provide a general view
The physical layer byte counts are available separately for each forward link rate (4.8 to
3072 kbps). Their relative distribution can reveal interesting performance insights. For
constructive fades). This will naturally skew the physical layer byte distribution towards
higher rates.
............................................................................................................................................................................................................................................................
The physical layer byte distribution may also be used for performance troubleshooting. A
hardware, etc.).
milliseconds). Since this metric is using the actual number of slots used at each rate the
problem with erroneous values due to modem reboots will not be an issue as it was for the
EVM.
equipped with a SBEVM, replacing the MAC layer data rate metric in 1xEV-DO Average
Forward Link MAC Data Rate - EVM (kbps) (p. 13-64). The counts are the total of all
Rel 0 and Rev A connections. The MAC layer data transmitted metric is still applicable to
sector-carriers equipped with an EVM. This metric is new in R27 and is not applicable to
prior releases.
Formula
DO Forward Link Physical Layer Data Rate - SBEVM (kbps) =
(8 * (EVM_FTC_TOT_BYTES_4_8 + EVM_FTC_TOT_BYTES_9_6 +
EVM_FTC_TOT_BYTES_2457_6 + EVM_FTC_TOT_BYTES_3072)) / 10 ^ 3
-----------------------------------------------------------------------------------------------------------
(EVM_FTC_NUM_SLOT_4_8 + EVM_FTC_NUM_SLOT_9_6 +
EVM_FTC_NUM_SLOT_19_2 + EVM_FTC_NUM_SLOT_38_4 +
EVM_FTC_NUM_SLOT_1536 + EVM_FTC_NUM_SLOT_1843_2 +
EVM_FTC_NUM_SLOT_2457_6 + EVM_FTC_NUM_SLOT_3072) * 0.001667
Count Definitions

and Rev A traffic.
............................................................................................................................................................................................................................................................

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.






............................................................................................................................................................................................................................................................



EVM_FTC_NUM_SLOT_4_8 = The number of slots used to transmit Physical Layer data

on the FTC by the SBEVM to the AT at a nominal rate of 4.8 kbps for both

EVM_FTC_NUM_SLOT_19_2 = The number of slots used to transmit Physical Layer

data on the FTC by the SBEVM to the AT at a nominal rate of 19.2 kbps
for both Rel 0 and Rev A traffic.




............................................................................................................................................................................................................................................................



EVM_FTC_NUM_SLOT_1536 = The number of slots used to transmit Physical Layer

data on the FTC by the SBEVM to the AT at a nominal rate of 1536 kbps



............................................................................................................................................................................................................................................................

A composite data rate for the Forward Link physical layer can be defined that is
independent of modem type by combining the formulae in the previous two sections. This
formula is defined at the sector-carrier level and can be aggregated to higher level network
elements. The composite formula is:
DO Forward Link Composite Physical Layer Data Rate (kbs) =
(1024 * EVM_FWD_PACKETS_RATE_TOTAL_COUNT +
8* EVM_FTC_TOT_BYTES_RATE) / 1000
(1024 * (EVM_FWD_PACKETS_38_4_TOTAL_COUNT +
+
8 * (EVM_FTC_TOT_BYTES_4_8 + EVM_FTC_TOT_BYTES_9_6 +
EVM_FTC_TOT_BYTES_2457_6 + EVM_FTC_TOT_BYTES_3072)) / 1000
------------------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Physical Layer Data Rate per User - SBEVM
This metric provides a measure of the average per user perceived data rate on a sector-
carrier. It uses the active usage peg count which measures the number of users either
waiting to be served or in the process of transmission on the forward link. Note that each
user in a multi-user packet is counted separately. It captures the effects of any event that is
making a user wait for the data available at the cell, e.g., multi-user contention, delays
associated with hybrid tuneaway or virtual soft/softer handoff, erased DRCs on the reverse
link, time waiting to transmit a packet (waiting for continuation slots). A Rev A user with
multiple flows will be counted only once per slot.
The metric is defined on a per sector-carrier basis on the DRC pointed sector. It is
applicable only to sector-carriers equipped with the SBEVM and is new for R27.
Formula
DO Forward Link Physical Layer Data Rate per User - SBEVM (kbps) =
------------------------------------------------------------------------------------------------------------
EVM_ACTIVE_USAGE * 0.001667
Count Definitions

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.
............................................................................................................................................................................................................................................................

and Rev A traffic.

and Rev A traffic.








............................................................................................................................................................................................................................................................

EVM_ACTIVE_USAGE = For each slot (traffic channel or control channel), this count
shall be incremented by the number of users who have data to send for any
flow (BE, or EF), either waiting to be scheduled or in the process of
transmission. This count shall be incremented based on the users (not
flows) as long as they have data to be served regardless of whether the
DRC is 0, or there is a DRC erasure, or the cover is not pointing to sector.
Only one sector shall peg each user towards this count.
If a multi-slot packet terminates early and there are no more packets
(scheduled or not), the user shall no longer be counted in the measurement
as soon as the ACK is received on the reverse link. If the transmission goes
on till the maximum allowed continuations, the pegging shall be stopped at
the last continuation (no need to wait for the last ACK/NACK).
This count shall be pegged on a Rev A capable carrier (a carrier equipped
with a SBEVM) for both Rev A and Rel 0 traffic.

users.
or another peg count called E vm _ Av g_ E li g _U se r (Average number of Scheduler
Eligible Users to determine if indeed there are a large number of users responsible for
driving up the loading.
............................................................................................................................................................................................................................................................
The peg count is measured in the modem at the physical layer (slots are only defined at the
physical layer).
The formula was changed in R24 to use the percent busy slots peg count and is applicable
to previous releases beginning with R22. Note that the peg count measures only those slots
used for actual traffic transmission so the control slot counts do not have to be subtracted.
Formula
Count Definitions
get percentage)

per second.
The metric carries a sector level connotation rather than a per user view given the
RF conditions at the time the user was served
transmission rate).
............................................................................................................................................................................................................................................................
some small amount of data gets transmitted to both the old & the new cells, resulting
is not far off the mark especially at moderate to high low loading points.
This metric remains usable with the SBEVM, however, it is more accurate to use the
actual slot counts in the denominator. The use of the actual slots counts also avoids the
problem mentioned above if the modem elapsed time is not about 3600 due to a reboot.
Beginning with R27 the metric in 1xEV-DO Average RLP Forward Link Data Rate with
SBEVM (kbps) (p. 13-80) should be used for sector-carriers equipped with an SBEVM.
Formula
--------------------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

per second.
The metric is defined on a per sector-carrier basis for sectors equipped with an SBEVM
and is defined only for the one hour measurement interval. It cannot be directly summed to
obtain results for longer time periods. The individual counts must be rolled up and then the
data rate can be calculated. The peg counts are measured at the RLP layer.
Only the actual traffic channel serving slots are used to compute the data rate. This means
any gaps in data transfer caused by user think time, Internet delays, backhaul congestions,
TCP backoffs, etc. will not impact the measured data rate. Rather it is simply an indication
of the rate at which users were served in the traffic channel slots. The metric is a reflection
of RF conditions at the time the user was served
transmission rate).
............................................................................................................................................................................................................................................................
where RLP bytes appear larger than the MAC or physical layer data volume on a given
sector. Given the above issues, RLP data rate should only be viewed as an estimate of
actual rate, although it is not far off the mark especially at moderate to high low loading
points.
This metric is new and effective in R27 for sectors equipped with an SBEVM and is the
aggregate of all Rel 0 and Rev A connections.
Formula
DO RLP Forward Link Data Rate SBEVM (kbps) =
-----------------------------------------------------------------------------------------------------------
EVM_FTC_NUM_SLOT_1536 + EVM_FTC_NUM_SLOT_1843_2 +
Count Definitions
RLP_TXED_FTC= Total number of original RLP octets transmitted on the forward link



............................................................................................................................................................................................................................................................










............................................................................................................................................................................................................................................................


megabytes.
The metric is defined on a per sector-carrier basis. The peg counts are measured at the
RLP layer.
This metric provides a measure of the data volume sent in the forward direction per active
connection. The RLP byte count represents actual user traffic with less overhead than
either MAC layer or physical layer packet counts, which can be padded with dummy bits
to fill the packet. Although the peg count name in the denominator is "Average Active
Connections" it is actually the sum of all the total connections based on a 10 second scan.
Note that if the count is read from IBM Prospect for Alcatel-Lucent it has already been
Formula
-----------------------------------------------------------------------
Count Definitions
This metric provides a measure of the average per user data rate on a sector-carrier on the
RLP layer. It uses the average active user peg count which measures the number slots that
have a user either waiting to be served or in the process of transmission on the forward
link. It captures the effects of any event that is making a user wait for the data available at
the cell, e.g., multi-user contention, delays associated with hybrid tuneaway or virtual
soft/softer handoff, erased DRCs on the reverse link, time waiting to transmit a packet
(waiting for continuation slots). A Rev A user with multiple flows will be counted only
once per slot.
............................................................................................................................................................................................................................................................
Formula
DO RLP Forward Link Data Rate per User SBEVM (kbps) =
--------------------------------------------------------------------
Count Definitions
transmission.
This count shall be incremented based on the users (not flows) as long as
they have data to be served regardless of whether the DRC is 0, or there is a
DRC erasure, or the cover is not pointing to sector. Only one sector shall
peg each user towards this count.
This metric gives the average data volume on the reverse link in megabytes. The metric is
defined on a per sector-carrier basis. The peg counts are pegged only on the DRC pointed
sector (the sector that AT is tuned to for forward ink data reception) even if there are
multiple pilots in the active set.
These counts are only measured in the dual board EVM. Beginning with R27, this metric
will report 'zero' for sector-carriers equipped with a single board EVM (SBEVM). New
metrics are provided for sector-carriers equipped with an SBEVM.
............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions
sector (the sector that AT is tuned to for forward link data reception) even if there are
............................................................................................................................................................................................................................................................
Formula
DO Reverse link physical layer data volume SBEVM (MB) =
(128 * REV_PACKETS_128_TOTAL_COUNT + 256 * REV_PACKETS_256_TOTAL_COUNT +
512 * REV_PACKETS_512_TOTAL_COUNT + 768 * REV_PACKETS_768_TOTAL_COUNT +
8192 * REV_PACKETS_8192_TOTAL_COUNT + 12288 *REV_PACKETS_12288_TOTAL_COUNT)
------------------------------------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
REV_PACKETS_128_TOTAL_COUNT = The number of actual physical layer packets

of 128 bits received on the reverse traffic channel.








............................................................................................................................................................................................................................................................



rates.
'zero' for sector-carriers equipped with a single board EVM (SBEVM). A new metric is
provided for sector-carriers equipped with an SBEVM.
............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------------------------------------------------
Count Definitions
This metric gives the average data rate on the reverse link in kilobits per second for sector-
carriers equipped with an SBEVM. The metric is defined on a per sector-carrier basis.
............................................................................................................................................................................................................................................................
The metric uses the new SBEVM counts for the actual number of subpackets used for
physical layer reverse link traffic at each rate. The numerator is the data volume computed
in 1xEV-DO Average Reverse Link Physical Layer Data Volume with SBEVM (MB) (p.
13-85). The denominator uses the sum of the subpackets times the subpacket duration of
6.6 ms.
Formula
DO Reverse link physical layer data rate SBEVM (kbps) =
8192 * REV_PACKETS_8192_TOTAL_COUNT + 12288 * REV_PACKETS_12288_TOTAL_COUNT) /
10 ^ 3
------------------------------------------------------------------------------------------------------------------------------
(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_512 + NUM_SUBPKTS_RL_768 +
NUM_SUBPKTS_RL_2048 +NUM_SUBPKTS_RL_3072 +
NUM_SUBPKTS_RL_8192 + NUM_SUBPKTS_RL_12288) * 0.00667
Count Definitions





............................................................................................................................................................................................................................................................







NUM_SUBPKTS_RL_256 = The number of actual physical layer subpackets received on

the reverse traffic channel for a user packet of 256 bits.


NUM_SUBPKTS_RL_1024 = The number of actual physical layer subpackets received

on the reverse traffic channel for a user packet of 1024 bits.


............................................................................................................................................................................................................................................................
NUM_SUBPKTS_RL_3072 = The number of actual physical layer subpackets received on the

reverse traffic channel for a user packet of 3072 bits.





A composite data rate for the Reverse Link physical Layer can be defined that is
independent of modem type in a similar fashion to the composite forward link data rate.
This formula is defined at the sector-carrier level and can be aggregated to higher level
network elements. The composite formula is:
DO Reverse Link Composite Physical Layer Data Rate (kbs) =
[(256* REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
2048* REV_OUTER_LOOP_PC_FRAME_COUNT_768KBPS +
+
1024 * REV_PACKETS_1024_TOTAL_COUNT + 1536 * REV_PACKETS_1536_TOTAL_COUNT+
2048 * REV_PACKETS_2048_TOTAL_COUNT + 3072 * REV_PACKETS_3072_TOTAL_COUNT+
8192 * REV_PACKETS_8192_TOTAL_COUNT + 12288 * REV_PACKETS_12288_TOTAL_COUNT)]
/1000
---------------------------------------------------------------------------------------------------------------------------------
[(REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS) * 0.0266]
+
[(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_8192 + NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
1xEV-DO Reverse Link RLP Data Throughput - EVM

The frame counts are only measured in the EVM. Beginning with R27, this metric will
report 'zero' for sector-carriers equipped with a single board EVM (SBEVM). A new
metric is provided for sector-carriers equipped with an SBEVM.
Formula
----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
1xEV-DO Reverse Link RLP Data Throughput with SBEVM

over all users). The denominator is the same as for the reverse link physical layer data rate
with an SBEVM (1xEV-DO Average Reverse Link Physical Layer Data Rate with
SBEVM (kbps) (p. 13-88)). this metric is closer to the true end-user experienced
The frame counts are only measured in the dual board EVM. Beginning with R27, this
metric will report 'zero' for sector-carriers equipped with a single board EVM (SBEVM).
A new metric is provided for sector-carriers equipped with an SBEVM.
Formula
DO Reverse link RLP throughput SBEVM (kbps) =
-----------------------------------------------------------------------------------------------------------
(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_8192 + NUM_SUBPKTS_RL_12288) * 0.00667
............................................................................................................................................................................................................................................................
Count Definitions
NUM_SUBPKTS_RL_128 = The number of actual physical layer subpackets of 128 bits

received on the reverse traffic channel.



NUM_SUBPKTS_RL_1024 = The number of actual physical layer subpackets of 1024

bits received on the reverse traffic channel.






............................................................................................................................................................................................................................................................


A composite data throughput for the Reverse Link RLP Layer can be defined that is
independent of modem type in a similar fashion to the composite forward and reverse link
physical layer data rates. This formula is defined at the sector-carrier level and can be
aggregated to higher level network elements. The composite formula is:
DO Reverse Link Composite RLP Throughput (kbps) =
----------------------------------------------------------------------------------------------------
[(REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +
REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS) * 0.0266]
+
[(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_8192 + NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
Error Statistics
............................................................................................................................................................................................................................................................

level.
The peg counts are only applicable to the EVM. The counts used in this metric will be
reported as 0 for sector-carriers equipped with an SBEVM.
Formula
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Power Control
............................................................................................................................................................................................................................................................
The following metrics are valid for sector-carriers equipped with an EVM. The counts will
be zero for sector-carriers equipped with an SBEVM:
The following metrics are new in R27 and are valid for sector-carriers equipped with an
SBEVM:
13-102)
13-102)
13-103)
13-103)
13-104)
13-104)
13-105)
13-105)
13-106)
13-106)
13-107)
13-107)
............................................................................................................................................................................................................................................................

Formula
--------------------------------------------------------------------------------
Count Definitions


Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

Formula
---------------------------------------------------------------------------------
Count Definitions

count are dB/8.

............................................................................................................................................................................................................................................................
401-610-013 Alcatel-Lucent - Proprietary 1 3- 1 0 1
packets containing 128 bits. The peg counts are defined on a per sector-carrier basis. This
metric is new and effective for R27 for sector-carriers equipped with an SBEVM.
Formula
DO Avg RL PC Setpoint 128 bits SBEVM (dB) =
REV_OL_PC_TOTAL_SETPOINT_128
---------------------------------------------------------------------------
REV_PACKETS_128_TOTAL_COUNT * 8
Count Definitions
REV_OL_PC_TOTAL_SETPOINT_128 = Total count for the reverse link outer loop set
point used for 128 bit frames. This is only counted on the DRC pointed
sector. The units of the count are dB/8.
REV_PACKETS_128_TOTAL_COUNT = The actual number of physical layer packets

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

packets containing 12288 bits. The peg counts are defined on a per sector-carrier basis.
This metric is new and effective for R27 for sector-carriers equipped with an SBEVM.
Formula
---------------------------------------------------------------------------
Count Definitions
REV_OL_PC_TOTAL_SETPOINT_12288 = Total count for the reverse link outer loop

set point used for 12288 bit frames. This is only counted on the DRC
pointed sector. The units of the count are dB/8.

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO. For example, if there are 10 connections on the sector at a given time and only
2 of them are really using their connections to upload some data, the remaining 8 are still
utilizing some of the reverse link bandwidth (typically, only pilot, MAC and Ack channels
- no traffic). This will get considered as 10 active connections. On the forward link, let's
say the same two users are also downloading. Each user will contend and get served on
some of the time slots, but the point is that the presence of 10 connections on the reverse
link have no bearing on the forward link utilization.
level.
again.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................

This metric represents the total number of active users on a given sector-carrier. It only
represents users (ATs) with their DRC pointing to the sector-carrier. Therefore, the
soft/softer handoff overhead is excluded. It is more relevant on the reverse link and does
not have much meaning on the forward link due to the time shared and virtual soft handoff
concepts of 1xEV-DO.
traffic). This will get considered as 10 active connections. On the forward link, lets say
Note that this metric does not include soft and softer links, unlike the previous one. Hence,
it is more representative of the reverse link traffic on a given sector-carrier.
The peg counts are defined on a per sector-carrier basis for sector-carriers equipped with
an SBEVM and count both Rel 0 and Rev A connections. They can be rolled up to the cell
level only if all sector-carriers on that cell are equipped with an SBEBM.
Formula
DO "Primary" traffic channel usage - SBEVM (erlangs) =
EVM_AVG_DRC_POINTED_USERS * 0.001
Count Definitions
EVM_AVG_DRC_POINTED_USERS = This count is the average number of DRC

pointed active users for the sector-carrier. The unit of measure is average
value multiplied by 100.
The system measures and sums the total number of DRC pointed active
users for the sector-carrier at the end of each 10-second interval. If there is
no DRC pointed sector for a given connection at the time of pegging, then
the last known DRC pointed sector shall be used. At the end of the SM
collection period, the system divides the value by the number of 10 second
periods in the collection interval to get the average and the value is rounded
up to the next hundredth. The system then reports the measurement as
............................................................................................................................................................................................................................................................
(average * 100).
This count shall be pegged only on a carrier equipped with an SBEVM for
both Rev A and Rel 0 traffic.

This metric is a ratio of the total number of air links on a sector-carrier to the number of
DRC pointed links on it. For example, a ratio of 2.5 indicates that for every user that this
sector-carrier is serving on the forward link, it has 1.5 other users who are pointing their
DRCs to some other sector-carriers.
The metric represents the soft/softer handoff usage in the area. The soft/softer handoff
overlap can be used to potentially look for the presence of pilot pollution in the region.
From the reverse link perspective, the metric may also be useful in cell capacity forecast.
Note that in 1xEVDO, additional soft/softer legs do not consume any resources on the
forward link; they merely act as interferers.
The peg counts are defined on a sector-carrier basis. This metric is new in R27 and is
applicable to sector-carriers equipped with an SBEVM for both Rel 0 and Rev A
connections.
Formula
DO Soft/Softer Handoff Overhead - SBEVM =
-----------------------------------------------------------------------
Count Definitions


............................................................................................................................................................................................................................................................
(average * 100).
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
14 1xEV-DO Metrics in IBM Prospect
for Alcatel-lucent Release 27

............................................................................................................................................................................................................................................................
Overview
The purpose of this chapter is to describe new and modified Primitive Calculations in IBM
Prospect for Alcatel-lucent R27 that support 1XEV-DO Performance Metrics. In addition,
descriptions of several existing and unchanged calculations have been updated.
Note that as of R27 the name Watchmark Prospect changes to IBM Prospect.
This chapter includes
8 modified PCALCs for previously supported 1xEV-DO performance metrics
(see Modified 1xEV-DO Performance Metrics in Prospect R27 (p. 14-3)),
23 new 1xEV-DO performance metrics for R27
(see New 1xEV-DO Performance Metrics in Prospect R27 (p. 14-9)), and
12 existing metrics have descriptions in the Performance Data Reference (PDR) and in
the GUI of the template editor modified in R27. These changes are made to explicitly
identify whether they apply to EVM or SBEVM boards
(see 1xEV-DO Performance Metrics with Modified PDR/GUI Descriptions in R27
(p. 14-23)).
The new and modified PCALCs defined in this chapter are implemented in R27 of
Prospect. Prospect R27 also supports earlier RNC releases and the descriptions of existing
calculations that did not change in R27 are contained in the documentation for those
earlier releases:
25
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-lucent 1xEV-DO Performance Metrics
Release 27

26
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-lucent Modified 1xEV-DO Performance Metrics in
Release 27 Prospect R27
Modified 1xEV-DO Performance Metrics in Prospect R27

............................................................................................................................................................................................................................................................

D Op _ Es tC a ll = 10 0 .0 * (A TI n it C on Rq + AN I ni t Co nR q -
A TI n it Co n At tF l No R es rc - AT I ni t Co nA t tF lN o TC C mp Rc v -
A TI n it Co n At tF l No R L - A TI ni t Co n At tF l Ot he r -
A NI n it Co n At tF l No R es rc - AN I ni t Co nA t tF lN o TC C mp Rc v -
A NI n it Co n At tF l No R L - A NI ni t Co n At tF l Ot he r +
C ro s sC ar r At tm p tR c vd TC C Rc vd - C ro ss C ar rA t tm p tS en t TC CR c vd ) /
( AT I ni tC o nR q - A T In it C on nA t tm p tD if f Se cC a rr S en t +
A NI n it Co n nA tt m pt D if fS e cC ar r Rc v d)
Notes:
Prospect
Traffic
ATInitConAttFlOther N/A 1xEV_Sector
Prospect PCALC Carrier
ANInitConAttFlOther
............................................................................................................................................................................................................................................................
ANInitConnAttmptDiffSecCarrSent AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT 1xEV_Sector

Carrier

R26: 1xEV-DO Established Call Rate (p. 12-3)

DO p _E s tC nc t = 1 0 0. 0 * ( A TI ni t Es t ab Co n ne ct i on +
AN I ni t Es ta b Co nn e ct i on + Cr os s Ca r rA tt m pt Rc v dT C CR cv d -
Cr o ss C ar rA t tm pt S en t TC CR c vd ) / ( A TI ni t Co nR q -
AT I ni t Co nn A tt mp t Di f fS ec C ar rS e nt +
AT I ni t Co nn A tt mp t Di f fS ec C ar rR c vd + AN I ni tC o nR q -
AN I ni t Co nn A tt mp t Di f fS ec C ar rS e nt +
AN I ni t Co nn A tt mp t Di f fS ec C ar rR c vd )
Notes:
Prospect
Traffic
Carrier

R26: 1xEV-DO Established Connection Rate (p. 12-5)
............................................................................................................................................................................................................................................................

D Op _ Sf tS f tr HO S uc = 10 0 .0 * (S f tS ft r HO At t -
S ft S ft rH O Co nC l os e _P re T CA - Sf t Sf tr H OC on C lo s e_ Po s tT CA -
S ft S rH OF l Ma xL e gs - (S f tS ft r HO F lN oR e sc + Sf t Sf tr H OF lN o AT R sp +
S ft S ft rH O Fl Ot h er ) ) / ( Sf tS f tr H OA tt -
S ft S ft rH O Co nC l os e _P re T CA - Sf t Sf tr H OC on C lo s e_ Po s tT CA -
S ft S rH OF l Ma xL e gs )
Notes:
Prospect Traffic
SftSftrHOFlOther Prospect PCALC summing pre- and post-TCA counts
SftSftrHOFlNoResc SO_SOR_FAIL_NO_RESOURCE 1xEV_SectorCarrier
SftSrHOFlMaxLegs SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED
SftSftrHOConClose_PreTCA SO_SOR_HOFF_CON_CLOSE_PRETCA
SftSftrHOConClose_PostTCA SO_SOR_HOFF_CON_CLOSE_POSTTCA

R25: Soft-Softer Handoff Success Rate- Requesting Sector (p. 10-6)

D Op _ Sf tS f tr HO S uc _ Tg t = 1 00 . 0 * ( Sf t Sf tr H OA t t_ Tg t -
S ft S ft rH O Co nC l os e _P re T CA _T g t - S ft Sf t rH OC o nC l os e_ P os tT C A_ T gt -
S ft S ft rH O No tP r oc M ax Le g s_ Tg t - (S ft S ft rH O Fl N oR es c _T gt +
S ft S ft rH O Fl No A TR s p_ Tg t + S f tS f tr HO F lO th e r_ P re TC A _T gt +
S ft S ft rH O Fl Ot h er _ Po st T CA _T g t) ) / ( S ft Sf t rH O At t_ T gt -
S ft S ft rH O Co nC l os e _P re T CA _T g t - Sf tS f tr HO C on C lo se _ Po st T CA _ Tg t -
S ft S ft rH O No tP r oc M ax Le g s_ Tg t )
............................................................................................................................................................................................................................................................
Notes:
Prospect
Traffic
SftSftrHOFlNoResc_Tgt SO_SOR_FAIL_NO_RESOURCE_TARGET 1xEV_Secto
rCarrier
SftSftrHOFlNoATRsp_Tgt SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET
SftSftrHOFlOther_PreTCA_Tgt SO_SOR_HOFF_FAIL_OTHER_PRETCA_TARGET
SftSftrHOFlOther_PostTCA_Tgt SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET
SftSftrHOConClose_PreTCA_Tgt SO_SOR_HOFF_CON_CLOSE_PRETCA_TARGET
SftSftrHOConClose_PostTCA_Tgt SO_SOR_HOFF_CON_CLOSE_POSTTCA_TARGET
SftSftrHONotProcMaxLegs_Tgt SO_SOR_HOFF_NOP_MAX_LEGS_TARGET

R24: Soft/Softer Handoff Success Rate - Target Sector (p. 8-9)

DO p _S f tS ft r HO Bl k = 10 0. 0 * ( S ft S ft rH O At t -
Sf t Sf t rH OC o nC lo s e_ P re TC A - S f tS r HO Fl M ax Le g s -
Sf t Sf t rH OA t tT CA ) / (S ft S ft rH O At t - S f tS ft r HO C on Cl o se _P r eT CA -
Sf t Sr H OF lM a xL eg s )
Notes:
Prospect Traffic
SftSrHOFlMaxLegs SO_SOR_HOFF_FAIL_MAX_NO_LEGS_REACHED
SftSftrHOConClose_PreTCA SO_SOR_HOFF_CON_CLOSE_PRETCA

R25: Soft-Softer Handoff Blocking Rate- Requesting Sector (p. 10-5)
............................................................................................................................................................................................................................................................

DOp_SftSftrHOBlk_Tgt = 100.0 * (SftSftrHOAtt_Tgt -
SftSftrHOConClose_PreTCA_Tgt - SftSftrHONotProcMaxLegs_Tgt -
SftSftrHOAttTCASent_Tgt) / (SftSftrHOAtt_Tgt -
SftSftrHOConClose_PreTCA_Tgt - SftSftrHONotProcMaxLegs_Tgt)
Notes:
Prospect
Traffic
Carrier
SftSftrHOConClose_PreTCA_Tgt SO_SOR_HOFF_CON_CLOSE_PRETCA_TARGET
SftSftrHONotProcMaxLegs_Tgt SO_SOR_HOFF_NOP_MAX_LEGS_TARGET

R25: Soft-Softer Handoff Blocking Rate- Target Sector (p. 10-5)
Soft-Softer Handoff RF Failure Rate - Requesting Sector

DOp_SftSftrHOFlRF_Req = 100.0 * SftSftrHOFlNoATRsp / (SftSftrHOAttTCA -
SftSftrHOConClose_PostTCA)
Notes:
Prospect
Traffic
SftSftrHOFlNoATRsp SO_SOR_HOFF_FAIL_NO_AT_RSP 1xEV_Sector
Carrier
SftSftrHOAttTCA SO_SOR_ATTMPT_TCA_SENT
1xEV_Sector
SftSftrHOConClose_PostTCA SO_SOR_HOFF_CON_CLOSE_POSTTCA
............................................................................................................................................................................................................................................................

R25: 1xEV-DO Soft/Softer Handoff RF Failure Rate-Requesting Sector (p.
10-17)
Soft-Softer Handoff RF Failure Rate - Target Sector

(SftSftrHOAttTCASent_Tgt - SftSftrHOConClose_PostTCA_Tgt)
Notes:
Prospect
Traffic
SftSftrHOFlNoATRsp_Tgt SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET 1xEV_Sector
Carrier
SftSftrHOAttTCASent_Tgt SO_SOR_ATTMPT_TCA_SENT_TARGET
1xEV_Sector
SftSftrHOConClose_PostTCA_Tgt SO_SOR_HOFF_CON_CLOSE_POSTTCA_TARGET

R25: 1xEV-DO Soft/Softer Handoff RF Failure Rate-Target Sector (p. 10-17)
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-lucent New 1xEV-DO Performance Metrics in Prospect
Release 27 R27

............................................................................................................................................................................................................................................................
Total Forward Link Physical Layer Data Transmitted - SBEVM

D O_ F LP hy s La yT o tX m t_ SB E VM = (F T CT ot B yt es _ 4_ 8 +
F TC T ot By t es _9 _ 6 + F TC T ot By t es _ 19 _2 + FT C To t By te s _3 8_ 4 +
F TC T ot By t es _7 6 _8 + FT C To tB y te s _1 53 _ 6 + F TC T ot By t es _3 0 7_ 2 +
F TC T ot By t es _6 1 4_ 4 + FT C To tB y te s _9 21 _ 6 + F TC T ot By t es _1 2 28 _ 8 +
F TC T ot By t es _1 5 36 + FT C To tB y te s _1 84 3 _2 + FT C To tB y te s_ 2 45 7 _6 +
F TC T ot By t es _3 0 72 ) / 1 0 00 00 0 .0
Prospect
Traffic
FTCTotBytes_1228_8 EVM_FTC_TOT_BYTES_1228_8 1xEV_Sector
Carrier
FTCTotBytes_1536 EVM_FTC_TOT_BYTES_1536
FTCTotBytes_153_6 EVM_FTC_TOT_BYTES_153_6
............................................................................................................................................................................................................................................................
Release 27 R27
Average Forward Link Physical Layer Data Rate - SBEVM

DO p _F L Ph ys L ay Av g Ra t e_ S B EV M = (8 .0 /1 0 00 .0 ) * (F TC T ot B yt es _ 4_ 8
+ F TC T ot By t es _9 _ 6 + F TC T ot By t es _ 19 _2 + FT C To t By te s _3 8_ 4 +
FT C To t By te s _7 6_ 8 + FT CT o tB yt e s_ 1 53 _6 + FT C To t By te s _3 07 _ 2 +
FT C To t By te s _6 14 _ 4+ FT CT o tB yt e s_ 9 21 _6 + FT C To t By te s _1 22 8 _8 +
FT C To t By te s _1 53 6 + FT CT o tB yt e s_ 1 84 3_ 2 + F T CT o tB yt e s_ 24 5 7_ 6 +
FT C To t By te s _3 07 2 ) / ( (F T CN um S lo t _4 _8 + FT C Nu m Sl ot _ 9_ 6 +
FT C Nu m Sl ot _ 19 _2 + F TC Nu m Sl ot _ 38 _ 4 + F TC Nu m Sl o t_ 76 _ 8 +
FT C Nu m Sl ot _ 15 3_ 6 + FT CN u mS lo t _3 0 7_ 2 + F TC N um S lo t_ 6 14 _4 +
FT C Nu m Sl ot _ 92 1_ 6 + FT CN u mS lo t _1 2 28 _8 + FT C Nu m Sl ot _ 15 36 +
FT C Nu m Sl ot _ 18 43 _ 2 + F TC N um Sl o t_ 2 45 7_ 6 + F T CN u mS lo t _3 07 2 ) *
0. 0 01 6 67 )

Prospect Traffic
FTCTotBytes_1228_8 EVM_FTC_TOT_BYTES_1228_8 1xEV_SectorCarrier
FTCNumSlot_1228_8 EVM_FTC_NUM_SLOT_1228_8
FTCNumSlot_1536 EVM_FTC_NUM_SLOT_1536
............................................................................................................................................................................................................................................................
Release 27 R27
FTCNumSlot_19_2 EVM_FTC_NUM_SLOT_19_2 1xEV_SectorCarrier

Average Forward Link Physical Layer Data Rate per User - SBEVM
D Op _ FL Ph y sL ay A vg R at eU s r_ S B EV M = ( 8 .0 / 1 00 0 .0 ) *
( FT C To tB y te s_ 4 _8 + FT C To tB y te s _9 _6 + FT C To t By te s _1 9_ 2 +
F TC T ot By t es _3 8 _4 + FT C To tB y te s _7 6_ 8 + F T CT o tB yt e s_ 15 3 _6 +
F TC T ot By t es _3 0 7_ 2 + F T CT ot B yt e s_ 61 4 _4 + F TC T ot By t es _9 2 1_ 6 +
F TC T ot By t es _1 2 28 _ 8 + F TC To t By t es _1 5 36 + FT C To tB y te s_ 1 84 3 _2 +
F TC T ot By t es _2 4 57 _ 6 + F TC To t By t es _3 0 72 ) / ( A ct iv e Us ag e *
0 .0 0 16 67 )
Prospect Traffic
............................................................................................................................................................................................................................................................
Release 27 R27

ActiveUsage EVM_ACTIVE_USAGE
Average Forward Link RLP Data Rate - SBEVM

DO p _F L RL PA v gR at e _S B EV M = ( 8. 0 / 1 00 0. 0 ) * R LP T XF TC /
(( F TC N um Sl o t_ 4_ 8 + FT CN u mS lo t _9 _ 6 + F TC Nu m Sl o t_ 19 _ 2 +
FT C Nu m Sl ot _ 38 _4 + F TC Nu m Sl ot _ 76 _ 8 + F TC Nu m Sl o t_ 15 3 _6 +
FT C Nu m Sl ot _ 30 7_ 2 + FT CN u mS lo t _6 1 4_ 4 + F TC N um S lo t_ 9 21 _6 +
FT C Nu m Sl ot _ 12 28 _ 8 + F TC N um Sl o t_ 1 53 6 + F TC N um S lo t_ 1 84 3_ 2 +
FT C Nu m Sl ot _ 24 57 _ 6 + F TC N um Sl o t_ 3 07 2) * 0. 0 01 6 67 )
Prospect
Traffic
RLPTXFTC RLP_TXED_FTC 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 27 R27
FTCNumSlot_76_8 EVM_FTC_NUM_SLOT_76_8 1xEV_Sector

Carrier
Average Forward Link RLP Data Rate per User - SBEVM

D Op _ FL RL P Av gR a te U se r_ S BE VM = ( 8. 0 / 10 00 . 0) * RL P TX FT C /
( Ac t iv eU s ag e * 0 . 00 16 6 7)
Prospect
Traffic
Carrier
ActiveUsage EVM_ACTIVE_USAGE
Total Reverse Link Physical Layer Data Volume - SBEVM

D O_ R LP hy s La yT o tX m t_ SB E VM =
( 12 8 .0 * Re vP a ck e ts _1 2 8_ To t al C ou nt +
2 56 . 0 * R ev Pa c ke t s_ 25 6 _T ot a lC o un t +
1 02 4 .0 * Re vP a ck e ts _1 0 24 _T o ta l Co un t +
1 22 8 8. 0 * R ev P ac k et s_ 1 22 88 _ To t al Co u nt ) / ( 8 .0 * 1 00 00 0 0. 0 )
............................................................................................................................................................................................................................................................
Release 27 R27
Prospect
Traffic
RevPackets_1024_TotalCount REV_PACKETS_1024_TOTAL_COUNT 1xEV_Sector
Carrier
RevPackets_12288_TotalCount REV_PACKETS_12288_TOTAL_COUNT
Average Reverse Link Physical Layer Data Rate - SBEVM

DO p _R L Ph ys L ay Av g Ra t e =
(1 2 8. 0 * R e vP ac k et s _1 28 _ To ta l Co u nt +
25 6 .0 * Re v Pa ck e ts _ 25 6_ T ot al C ou n t +
10 2 4. 0 * R e vP ac k et s _1 02 4 _T ot a lC o un t +
12 2 88 . 0 * R ev Pa c ke t s_ 12 2 88 _T o ta l Co un t ) /
(0 . 00 6 6 * 1 00 0. 0 * (N um S ub pk t sR L _1 28 + Nu m Su b pk ts R L_ 25 6 +
Nu m Su b pk ts R L_ 51 2 + Nu mS u bp kt s RL _ 76 8 + N um S ub p kt sR L _1 02 4 +
Nu m Su b pk ts R L_ 15 3 6 + N um S ub pk t sR L _2 04 8 + N u mS u bp kt s RL _3 0 72 +
Nu m Su b pk ts R L_ 12 2 88 ) )
............................................................................................................................................................................................................................................................
Release 27 R27
Prospect
Traffic
NumSubpktsRL_1024 NUM_SUBPKTS_RL_1024 1xEV_Sector
Carrier
NumSubpktsRL_12288 NUM_SUBPKTS_RL_12288
............................................................................................................................................................................................................................................................
Release 27 R27
Average Reverse Link RLP Data Throughput - SBEVM

DO p _R L RL PA v gT hr u _S B EV M = ( 8. 0 * R LP RX R TC ) / ( 0. 00 6 6 * 10 0 0. 0 *
(N u mS u bp kt s RL _1 2 8 + N um S ub pk t sR L _2 56 + Nu m Su b pk ts R L_ 51 2 +
Nu m Su b pk ts R L_ 76 8 + Nu mS u bp kt s RL _ 10 24 + Nu m Su b pk ts R L_ 15 3 6 +
Nu m Su b pk ts R L_ 61 4 4) )
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................
Release 27 R27
D O_ A vg Re v Ln kP C Se t Po in t _1 28 _ SB E VM = Re v OL PC T ot al S et p oi nt _ 12 8 /
( 8. 0 * R e vP ac k et s _1 28 _ To ta l Co u nt )
Prospect
Traffic
RevOLPCTotalSetpoint_128 REV_OL_PC_TOTAL_SETPOINT_128 1xEV_Sector
Carrier
D O_ A vg Re v Ln kP C Se t Po in t _2 56 _ SB E VM = Re v OL PC T ot al S et p oi nt _ 25 6 /
Prospect
Traffic
Carrier
O _A v gR ev L nk PC S et P oi nt _ 51 2_ S BE V M = R ev OL P CT o ta lS e tp oi n t_ 5 12 /
Prospect
Traffic
............................................................................................................................................................................................................................................................
Release 27 R27

Carrier
DO _ Av g Re vL n kP CS e tP o in t_ 7 68 _S B EV M = R e vO L PC To t al Se t po i nt _7 6 8 /
(8 . 0 * R ev P ac ke t s_ 7 68 _T o ta lC o un t )
Prospect
Traffic
Carrier
DO _ Av g Re vL n kP CS e tP o in t_ 1 02 4_ S BE V M =
Re v OL P CT ot a lS et p oi n t_ 10 2 4 / (8 . 0 * Re v Pa c ke ts _ 10 24 _ To t al Co u nt )
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................
Release 27 R27
Prospect
Traffic
Carrier
D O_ A vg Re v Ln kP C Se t Po in t _2 04 8 _S B EV M =
R ev O LP CT o ta lS e tp o in t_ 2 04 8 / ( 8. 0 * R ev P ac ke t s_ 2 04 8_ T ot al C ou nt )
Prospect
Traffic
Carrier
D O_ A vg Re v Ln kP C Se t Po in t _3 07 2 _S B EV M =
R ev O LP CT o ta lS e tp o in t_ 3 07 2 / ( 8. 0 * R ev P ac ke t s_ 3 07 2_ T ot al C ou nt )
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................
Release 27 R27
Prospect
Traffic
Carrier
Prospect
Traffic
Carrier
Prospect
Traffic
............................................................................................................................................................................................................................................................
Release 27 R27

Carrier
D O_ A vg Re v Ln kP C Se t Po in t _1 22 8 8_ S BE VM =
R ev O LP CT o ta lS e tp o in t_ 1 22 88 /
( 8. 0 * R e vP ac k et s _1 22 8 8_ To t al C ou nt )
Prospect
Traffic
Carrier

D Op _ Co nf i gN eg o tS u c =
1 00 . 0 * ( Co nf i gN e go - AT In i tC o nA tt F lC nf g Ne g Fl -
A NI n it Co n At tF l Cn f gN eg F l) / Co n fi gN e go
Prospect
Traffic
ATInitConAttFlCnfgNegFl AT_INIT_CONN_ATT_FAIL_CONFIG_NEGO_FAILED 1xEV_Sector
Carrier
ConfigNego CONFIG_NEGO
1xEV-DO CPrimary Traffic Channel Usage (Erlangs)- SBEVM

D O_ P ri mT r fC hU s g_ S BE VM = 0. 0 1 * A vg D RC Po i nt e dU se r s
............................................................................................................................................................................................................................................................
Release 27 R27
Prospect
Traffic
AvgDRCPointedUsers EVM_AVG_DRC_POINTED_USERS 1xEV_Sector
Carrier
1xEV-DO Soft/Softer Handoff Overhead - SBEVM

DO p _S f tS ft r HO Ov e rh e ad _S B EV M= Av g Ac tC o n_ Pe g / (3 .6 *
Av g DR C Po in t ed Us e rs )
Prospect
Traffic
AvgActCon_Peg AVG_ACTIVE_CONN_PER_SECTOR 1xEV_Sector
Carrier
AvgDRCPointedUsers EVM_AVG_DRC_POINTED_USERS
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-lucent 1xEV-DO Performance Metrics with Modified
Release 27 PDR/GUI Descriptions in R27
1xEV-DO Performance Metrics with Modified PDR/GUI

Descriptions in R27
............................................................................................................................................................................................................................................................
Overview1x
The following table lists existing 1xEV-DO performance metrics that have modified
descriptions in the PDR and modified template editor GUI descriptions in Prospect R27.
Old Template Editor GUI New Template Editor GUI

Metric Name
Description Description
1xEV-DO total data trans on fwd 1xEV-DP total data trans on fwd
DO_TotDataXmtFwdLink
link (Mbytes) link (Mbytes) for EVM
1xEV-DO avg fwrd link data rate 1xEV-DO avg fwrd link data rate
DO_AvgFwdL_kbps
(kbps) (kbps) for EVM
1xEV-DO avg RLP data rate fwd 1xEV-DO avg RLP data rate fwd
DO_RLPFwdL_kbps
link (kbps) link (kbps) for EVM
1xEV-DP total data trans on rev 1xEV-DP total data trans on rev
DO_TotDataXmtRevLnk
link (Mbytes) link (Mbytes) for EVM
1xEV-DO avg fwrd link data rate 1xEV-DO avg fwrd link data rate
DO_AvgRevL_kbps
(kbps) (kbps) for EVM
1xEV-DO reverse link RLP data 1xEV-DO reverse link RLP data
DO_RLPThruput_RevL
throughput - kbps throughput - kbps for EVM
1xEV-DO average reverse link

DO_AvgRevLnkPCSetpoint_0 power control setpoint - 0 kbps for
power control setpoint - 0 kbps
EVM

DO_AvgRevLnkPCSetpoint_96 power control setpoint - 9.6 kbps
power control setpoint - 9.6 kbps
for EVM

for EVM

for EVM
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-lucent 1xEV-DO Performance Metrics with Modified
Release 27 PDR/GUI Descriptions in R27
Old Template Editor GUI New Template Editor GUI

Metric Name
Description Description

for EVM
1xEV-DO average reverse link 1xEV-DO average reverse link

DO_AvgRevLnkPCSetpoint_1536 power control setpoint - 153.6 power control setpoint - 153.6
kbps kbps for EVM
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

system associated with the HDR Cell Site (HCS), Radio Network Controller (RNC)
(which includes the HDR Cell Site (HCS) Controller and the Packet Control Function
(PCF), Applications Processor (AP) and the Traffic Processor (TP). No specific
performance metrics associated with the PDSN are included in this document.
This SRD is issued for 1xEV-DO Release 28. The metrics that were changed, added or
deleted are listed in Section 1.3, Reason for Re-Issue.
The new composite metrics are applicable back to R27. The other new metrics and
changes to existing metrics are applicable beginning with R28 since they are involved with
new peg counts.
New metrics:
1xEV-DO Intra-RNC Group Session Transfer Success Rate (p. 15-15)
1xEV-DO Established Connection Rate - Peg (p. 15-26)
1xEV-DO Established Connection Rate - User - Peg (%) (p. 15-29)
1xEV-DO Connection Blocking Rate - User (%) (p. 15-37)
1xEV-DO RF Failure Rate - Session Setup (%) (p. 15-45)
1xEV-DO RF Failure Rate - User (%) (p. 15-46)
1xEV-DO Paging Effectiveness (p. 15-50)
1xEV-DO Forward Link Data Re-Transmission Rate (NAK) - SBEVM (p. 15-74)
............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Retransmission Rate (DARQ) - SBEVM (p. 15-75)

1xEV-DO Composite Forward Link Physical Layer Data Transmitted (MB) (p.
15-85)
1xEV-DO Composite Average Forward Link Physical Layer Data Rate (p. 15-94)
1xEV-DO Composite RLP Forward Link Data Rate (kbps) (p. 15-104)
1xEV-DO Reverse Link Physical Layer Composite Data Volume (MB) (p. 15-111)
1xEV-DO Composite Average Reverse Link Physical Layer Data Rate (p. 15-116)
1xEV-DO Composite Reverse Link RLP Data Throughput (p. 15-120)
1xEV-DO ReservationOnRequest Success Rate (p. 15-137)
1xEV-DO FL Conversational Speech Reservation Success Rate (p. 15-137)
1xEV-DO FL Conversational Speech Dropped Reservation Rate (p. 15-138)
1xEV-DO FL Conversational Video Reservation Success Rate (p. 15-138)
1xEV-DO FL Conversational Video Dropped Reservation Rate (p. 15-139)
1xEV-DO FL Conversational PTT Speech Reservation Success Rate (p. 15-140)
1xEV-DO FL Conversational PTT Speech Dropped Reservation Rate (p. 15-140)
1xEV-DO RL Conversational Speech Dropped Reservation Rate (p. 15-141)
1xEV-DO RL Conversational Video Dropped Reservation Rate (p. 15-141)
1xEV-DO RL Conversational PTT Speech Dropped Reservation Rate (p. 15-142)
Revised metrics:
1xEV-DO Average Active Sessions Metric (p. 15-9)
1xEV-DO Fast Connect Success Rate (p. 15-31)
1xEV-DO Hard Handoff Success Rate - Requesting Sector (p. 15-59)
1xEV-DO Hard Handoff Success Rate - Target Sector (p. 15-62)
1xEV-DO Hard Handoff Blocking Rate - Requesting Sector (p. 15-65)
1xEV-DO Hard Handoff Blocking Rate - Target Sector (p. 15-68)
1xEV-DO Hard Handoff RF Failure Rate - Requesting Sector (p. 15-69)
1xEV-DO Hard Handoff RF Failure Rate - Target Sector (p. 15-71)
1xEV-DO Forward Link Data Re-Transmission Rate - EVM (p. 15-73)
1xEV-DO Average RLP Forward Link Data Rate (kbps) (p. 15-99)
1xEV-DO Average Forward Link RLP Data Volume per User (MB) (p. 15-105)
1xEV-DO Average Forward Link RLP Data Rate per User - SBEVM (kbps) (p.
15-107)
............................................................................................................................................................................................................................................................
Obsoleted metrics:
1xEV-DO Established Connection Rate (p. 15-21)
1xEV-DO Fast Connect Success Rate (p. 15-31)
1xEV-DO Total Ineffective Connection Attempt Rate (p. 15-38)
1xEV-DO RF Failure Rate (p. 15-39)
1xEV-DO Paging Success Rate (p. 15-48)
1xEV-DO Paging Failure Rate due to RF Failures (p. 15-49)
1xEV-DO Dropped Connection Rate (p. 15-53)
Intra-RNC Group Session Transfer Success Rate
............................................................................................................................................................................................................................................................

a. Connection Setup
1xEV-DO Established Connection Rate - Session Setup - Peg
1xEV-DO Established Connection Rate - User -Peg
1xEV-DO Connection Blocking Rate - User
1xEV-DO RF Failure Rate - Session Setup
1xEV-DO RF Failure Rate - User
1xEV-DO Paging Effectiveness
b. Connection Drop
c. Handoff
1xEV-DO Forward Link Data Re-transmission Rate - EVM
1xEV-DO Forward Link Data Re-transmission Rate (NAK) - SBEVM
1xEV-DO Forward Link Data Re-transmission Rate (DARQ) - SBEVM
1xEV-DO Reverse Link Data Re-transmission Rate
1xEV-DO Total Forward Link MAC Data Transmitted - EVM (MB))
1xEV-DO Composite Forward Link Physical Layer Data Transmitted (MB)
1xEV-DO Average Forward Link MAC Data Rate - EVM (kpbs)
............................................................................................................................................................................................................................................................
1xEV-DO Average Forward Link Physical Layer Data Rate per User - SBEVM
(kbps)
1xEV-DO Percent Forward Link Bandwidth used for Traffic
1xEV-DO Average RLP Forward Link Data Rate - EVM (kbps))
1xEV-DO Average RLP Forward Link Data Rate with SBEVM (kbps))
1xEV-DO Composite RLP Forward Link Data Rate (kbps)
1xEV-DO Average RLP Forward Link Data Rate per User - SBEVM (kbps)
1xEV-DO Average Reverse Link Pysical Layer Data Volume - EVM (MB)
1xEV-DO Average Reverse Link Data Volume with SBEVM (MB)
1xEV-DO Reverse Link Physical Layer Composite Data Volume (MB)
Composite Reverse Link RLP Data Throughput
e. Error Statistics
f. Power Control
1xEV-DO Average Reverse Link Power Control Setpoint - 8192bits - SBEVM
............................................................................................................................................................................................................................................................
3. Quality of Service Metrics

1xEV-DO ReservationOnRequest Success Rate
1xEV-DO Forward Link Conversational Speech Reservation Success Rate
1xEV-DO Forward Link Conversational Speech Dropped Reservation Rate
1xEV-DO Forward Link Conversational Video Reservation Success Rate
1xEV-DO Forward Link Conversational Video Dropped Reservation Rate
1xEV-DO Forward Link Conversational Push to Talk Reservation Success Rate
1xEV-DO Forward Link Conversational Push to Talk Dropped Reservation Rate
1xEV-DO Reverse Link Conversational Speech Dropped Reservation Rate
1xEV-DO Reverse Link Conversational Video Dropped Reservation Rate
1xEV-DO Reverse Link Conversational Push to Talk Speech Dropped Reservation
Rate
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
transfer attempts were added to the denominator. This new formula is effective beginning
with R24. As before, some failures included in this metric result from inter-subnet idle
transfers (color code method), so the metric is not strictly indicative of RF quality.
The formula was changed in R28 to include the new UATI complete count for intra-RNC
group transfers.
Formula
(SESS_SETUP_UATI_COMPLETE_MSG_RCVD +
SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD +
INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD)
-----------------------------------------------------------------------------------------------------X100
(SESSION_SETUP_REQ + INT_SUBNET_IDL_TRFR_ATTMPT +
INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT)
Count Definitions
SESSION_SETUP_REQ =
............................................................................................................................................................................................................................................................

Session Set Up - UATI Complete Message Received (new & prior
sessions). Pegged when the AT acknowledges a UATI assignment message
sent by the AN in response to a UATI request.
code).
INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD =
This count is incremented each time a UATI Complete is received or any
access channel packet received with just assigned UATI for a session
transfer within an RNC Group.
INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT =
This count is incremented for each Route Update message received with
UATI on the access channel from an AT with its serving AP in a different
RNC from the last seen RNC within the same RNC Group.

This metric is revised in R28 to include the new Intra-RNC Group transfer counts.
............................................................................................................................................................................................................................................................
Formula
(SESS_SETUP_UATI_ASSGNMT_MSG_SENT +
SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT +
INTRA_RNC_GROUP_SESS_TRFR_UATI_ASSGN_SENT)
----------------------------------------------------------------------------------------------------X 100
Count Definitions
SESSION_SETUP_REQ =
code)
INTRA_RNC_GROUP_SESS_TRFR_UATI_ASSGN_SENT =
This count is incremented each time a UATI assignment is sent for a
session transfer within an RNC Group.
This count is incremented for each Route Update message received with
UATI on the access channel from an AT with its serving AP in a different
RNC from the last seen RNC within the same RNC Group.

during the measurement interval. Active sessions are also sometimes referred to as active
connections.
............................................................................................................................................................................................................................................................
They are UATI sessions with an active PPP session.

The metric is changed beginning in R28 to change from an AP to an OHM based peg
count, so the metric is defined on a per OHM basis.
Formula
AVG_ACTIVE_CONN_PER_OHM
360
Count Definitions
AVG_ACTIVE_CONN_PER_OHM =
Number of active connections on an OHM (sessions with an active PPP
session). This count is pegged every 10 seconds during the measurement
interval and added to the previous total. Therefore, the result is divided by
360 to get the approximate average over the measurement interval. Note
that the measurement interval is not exactly one hour so the calculation is
approximate.
............................................................................................................................................................................................................................................................

First and Color Code methods). As discussed previously, Inter-subnet Idle handoffs differ
from intra-subnet handoffs in that the former entail a series of messages exchanged
between the AT and the AN on the new subnet as well as between the old and the new
subnets. The messaging is required to assign a new UATI for use on the new subnet, to
transfer any existing PPP session over from the PCF on the old subnet, and to clean up the
old UATI session on the old subnet. The process is subject to failures from a variety of
sources including RF conditions (poor RF, rapid ping-ponging), provisioning errors on the
AN, misalignment of AT information in the two subnets, or issues within the AT itself.
intervention.
completely transparent to the end user. The subscriber unit would observe the impact only
if it was used to access the network while in a dormant state right after the inter-subnet idle
handoff trigger. Hence, a relatively high rate of inter-RNC idle handoff failures may not be
that egregious.
Note that there is a common misconception on inter-subnet active transfers. When a user
crosses an subnet border during an active connection, legs are added and/or dropped
similar to any other soft/er handoff. The TP that was in control of the connection on the
old subnet continues to be in charge even if the user drives in further and the AT is entirely
served by cells on the new subnet. This is conceptually very similar to the inter-MSC
packet data soft handoffs in the Alcatel-lucent 2G/3G1x product. The inter-subnet idle
handoff does not occur until after the connection is released and the AT has gone dormant.
Hence, it is fair to say that inter-subnet handoff idle failures that are of short-term nature
(such as due to poor RF conditions or mismatch in the subnets about the AT state, as
opposed to a broken backbone connectivity between the two subnets) have little or no
impact on the performance of an active connection.
An inter-subnet idle handoff may fail for a variety of reasons - there are several peg counts
............................................................................................................................................................................................................................................................
are defined on a per sector-carrier basis. Beginning in R28 a subnet may be defined to
include more than one RNC. The description in this section and in some of the peg counts
was changed to reflect this enhancement. The formula is not changed.
Formula
INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ) )
-------------------------------------------------------------------------------------------------- X100
INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS)
Count Definitions
This count is incremented for each attempt to transfer a dormant data
session between subnets using a method other than the Prior Session
method and is the total of all such idle transfer attempts for the HDR Cell
sector-carrier that received the UATIRequest.
This count is used to measure idle transfer activity. This count should be
pegged when an A13-Session Information Request is generated in the
target AN, omitting the number of such requests that are associated with
the Prior Session method.Note that if the A13 message is repeated, the
count is only pegged once.
Beginning in R28 this count will exclude the session transfer for load
balancing between RNC members within a RNC Group.
............................................................................................................................................................................................................................................................
This count is incremented for each idle transfer attempt using the Color
Code Method or the Assign First Method that failed because the previous
subnet did not respond and is the total of all such idle transfer failures for
the HDR Cell sector-carrier. This count is used to measure idle transfer
failures because the old subnet did not respond to the transfer request. The
count should be pegged after both request attempts have failed.
case with the Assign First method where RNC has to guess a sequence
............................................................................................................................................................................................................................................................
Beginning in R28, this count shall exclude the session transfer for load
which requires the new RNC to perform a look up of old RNCs IP address
instructs the AT to directly report back the old RNCs PCF A11 address.
Another scenario where this count may get pegged for either the Assign
First or Color Code method is when the PDSN's IP address reported in the
A13 Session Information Response message by the source RNC is invalid
(i.e., 255.255.255.255 or NULL).
Beginning in R28, this count shall exclude the session transfer for load
(RNC 2) does not yet consider itself to be in control of ATs session and
............................................................................................................................................................................................................................................................
source AN because of insufficient information in the Configuration
Request message using the Prior Sessions method.
1xEV-DO Intra-RNC Group Session Transfer Success Rate

This metric gives the success rate of session transfers between RNCs in the same RNC
group (subnet). This may occur when the serving OHM and session controlling OHM are
in different RNCs within the same RNC group.The peg counts are defined on a sector-
carrier basis.
Formula
DO Intra RNC Session Xfer Success Rate (%) =
INTRA_RNC_GROUP_SESS_TRFR_SUCCESS
---------------------------------------------------------------------------
INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT
Count Definitions
INTRA_RNC_GROUP_SESS_TRFR_SUCCESS =
This count is incremented each time a session transfer is successful for a
Route Update message received with an UATI Request with UATI on the
access channel from an AT with its cell serving OHM in different RNC
from the last seen RNC within the same RNC Group. The session transfer
is considered successful after the serving RNC has finished the negotiation
with PDSN if there is a session setup between AT and PDSN or after the
serving RNC has received the UATI Complete message from AT or any
access channel packet with just assigned UATI if there is no session setup
with PDSN.
............................................................................................................................................................................................................................................................
This count is incremented each time a session transfer is attempted for a
Route Update received with an UATI Request with UATI on the access
channel from an AT with its cell serving OHM in different RNC from the
last seen RNC within the same RNC group.

These counts are defined in the 1xEV-DO service measurements manual (401-614-326).
These counts should be monitored by service providers, especially if the failure rate is
high.
Formula
--------------------------------------------------------------------- X 100
Count Definitions
RAN_AUTH_SUCCESSFUL_ATTMPT = Number of successful RAN authentication

attempts.

session setup.
Configuration negotiation takes place during session setup after an active connection has
successfully been established. The peg counts are defined on a sector-carrier basis and are
pegged against the DRC-pointed sector-carrier at the time of configuration negotiation.
............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------------------------- X 100
CONFIG_NEGO
Count Definitions
place.


............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
This section deals with connection establishment metrics from the PCF perspective. One is
the PCF reactivation performed by the PCF when it receives data from the PDSN for a
dormant connection. The reactivation is considered successful if the AN is able to set up a
traffic channel with the AT. The other metric has to do with the PCFs ability to activate a
R-P link with the PDSN. An R-P or a A10-A11 link is initiated when the user wishes to
establish a fresh PPP connection, or upon inter-RNC idle handoff transfer.
1xEV-DO PCF Reactivation Success Rate for AN-Initiations

last connection went dormant.Once a traffic channel is established and the path from the
network activation.Data from the PDSN may only start flowing once a PPP link is
established. If the data from the PDSN arrives when the PPP link is dormant, then it results
in what is known as PCF or network reactivation, as discussed above.
Formula
------------------------------------------------------------------------------ X 100
............................................................................................................................................................................................................................................................
Count Definitions
end user.
PDSN.

on the R-P link.
established by the PCF on the target RNC with the old PDSN after an inter-RNC idle The
R-P connection success rate is a useful measure of proper connectivity between the AN
and the PDSN as well as any provisioning needs. For example, increased number of PDSN
rejects in the busy hour may be a sign of bottlenecks at the PDSN. Increased number of
failures during low usage hours may simply be a reflection of PDSN outages for
maintenance.
If the R-P connection failure rate is unacceptable, it may be worthwhile to also evaluate
error codes obtained directly from the PDSN to facilitate further investigation. Starting
with R23, the ROP file also stores reason codes for R-P connection failures.
Formula
------------------------------------------------------------------------------ X 100
RP_CONN_ATTMPTS
............................................................................................................................................................................................................................................................
Count Definitions
RP_CONN_ATTMPTS =
RP_CONN_FAIL =
service).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

3G1X.
missed messages between the AN/AT, etc. In general, a connection is said to be
established when the AN has received a Traffic Channel Complete message from the AN.
This is conceptually very similar to receiving a Service Connect Complete Message from
the mobile in a IS2000 system.
for a Connection.
beginning with R27.
This metric is made obsolete and should not be used beginning in R28. The following
metric, DO Established Connection Rate - Peg should now be used.
............................................................................................................................................................................................................................................................
Formula
(AN_INIT_CONN_REQ + AT_INIT_CONN_REQ
--------------------------------------------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
............................................................................................................................................................................................................................................................
AT_INIT_CONN_REQ =
Connection Request.
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD=
connection request.
attribute set.
............................................................................................................................................................................................................................................................
AT_INIT_BUNDLED_CONN_ATTEMPT_FAILURE =
This count is incremented when a Connection Request bundled with a
ReservationOnRequest (RoR) is rejected due to the RoR rejection. The
specific reason the RoR rejection is kept with the RoR failure counts. All
the failure counts below are pegged as AT or AN Initiated depending on
whether the corresponding Connection Request message was received with
AT or AN Initiated attribute set.
AN acknowledges the acquisition of ATs traffic channel preamble on the
receiving the TCC.
sector.
............................................................................................................................................................................................................................................................
This is a catch-all for remainingconnection setup failure scenarios that
processing errors, time outs, message build or senderrors, blocking due to
This is a catch-all forremaining connection setup failure scenarios that
occur after sending TCA. The reasonsmay include internal call processing
errors, time outs, messagebuild or send errors, blocking due to system
bottlenecks, etc.AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD =
receiving the TCC.
sector.
............................................................................................................................................................................................................................................................
errors, time outs, message build or senderrors, blocking due to system
bottlenecks, etc.

3G1X.
This metric includes all connections, those established as part of session setup as well as
'user' connections established for data transmission. Beginning with R28, separate metrics
are provided for session setup established connection rate and user established connection
rate.
............................................................................................................................................................................................................................................................
level.
The formula is revised in R27 to remove the SESS_CLOSE_SESS_TRFR_ABORTED
Beginning with R28 this is the recommended metric for Established Connection Rate.
Formula
---------------------------------------------------------------------------------------------------X 100
Count Definitions
channel.)
Number of AT-Initiated successful connections(pegged when a TCC is
channel.)
for traffic channel allocation by the load balancing alogorithm.
............................................................................................................................................................................................................................................................
connection request.
AN_INIT_CONN_REQ =
AN-Initiated connection requests = This count is pegged for each
connection request received when the UATI associated with the request
does not have a valid session due to a Session transfer failure. The count is
used to measure connection attempt rejects due to session transfer failures.
served by this sector-carrier.

1xEV-DO Established Connection Rate - Session Setup - Peg (%)

This metric gives percentage of successful connections relative to connection requeests for
those connection requests that are part of session setup and excludes those connection
requests initiated for the transmission of user data.The peg counts are defined on a sector-
carrier basis and are pegged at the sector-carrier that received the connection request.
The metric is new in R28.
............................................................................................................................................................................................................................................................
Formula
DO Established Connection rate - Session Setup - Peg (%) =
AT_INIT_ESTABLISHED_CONN_SESS
---------------------------------------------------------------------------------------------------X 100
Count Definitions
AT_INIT_ESTABLISHED_CONN_SESS =
This count is incremented each time a connection is established for a
sector-carrier for a connection request while the UATI Session is in a state
of waiting for a Configuration Negotiation or the UATI Session is
associated with a Color Code that is not supported by this AN. This count
is pegged against the sector-carrier that received the Connection Request.
This count is used to measure the success of AT-initiated initial
(configuration negotiation) connection requests associated with session
setup attempts or for UATIs associated with a Color Code that is not
supported by this AN, at least up to the point where an initial connection is
established
AT_INIT_CONN_REQ_SESS =
This count is incremented each time a connection request is received by a
sector-carrier while the UATI Session is in a state of waiting for a
Configuration Negotiation or the UATI Session is associated with a Color
Code that is not supported by this AN. This count is pegged against the
sector-carrier that received the Connection Request. This count is used to
measure the number of AT-initiated initial (configuration negotiation)
connection requests associated with session setup attempts or for UATIs
associated with a Color Code that is not supported by this AN.
1xEV-DO Established Connection Rate - User - Peg (%)

This metric gives percentage of successful connections relative to connection requests for
those connection requests initiated for the transmission of user data and excludes those
initiated as part of session setup.
The peg counts are defined on a sector-carrier basis. However, the metric is defined
aggregated to the sector level. It cannot be used at the sector-carrier level because the cross
connect counts for load balancing do not make a distinction between user and session
............................................................................................................................................................................................................................................................
setup established connections. Since the overall established connections count is pegged
on the sector-carrier receiving the TCC, the metric cannot be adjusted for load balancing.
Hence it is only valid at the sector level or above.
Formula
DO Established Connection Rate - User - Peg (%) =
(AN_INIT_ESTABLISHED_CONN + AT_INIT_ESTABLISHED_CONN -
AT_INIT_ESTABLISHED_CONN_SESS)
----------------------------------------------------------------------------------------------------X 100
(AN_INIT_CONN_REQ + AT_INIT_CONN_REQ - AT_INIT_CONN_REQ_SESS)
Count Definitions
channel.)
AT_INIT_ESTABLISHED_CONN = Number of AT-Initiated successful

connections(pegged when a TCC is received or an RLP packet is received
from the AT on the reverse traffic channel.)
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
AT-Initiated connection requests
............................................................................................................................................................................................................................................................
established

requests. The fast connect procedure re-establishes a traffic channel to a dormant AT when
the Suspend Timer is still running, i.e., before the AT goes into the Sleep mode. It does not
involve the traditional Page/Connection Request sequence; rather the AN revives a
dormant connection by directly sending a TCA to the AT. This strategy results in an
not affected by load balancing or cross-carrier assignments.
R26. The peg counts are defined on a per OHM basis (changed from per AP in R28) and
can be rolled up to the RNC or SN level.
metric, DO Fast Connect Success Rate - Peg should now be used.
Formula
FAST_CONNECT_FAIL_RL_NOT_ACQ - FAST_CONNECT_FAIL_NO_RSC)
---------------------------------------------------------------------------------------------------- X 100
(FAST_CONNECT)
............................................................................................................................................................................................................................................................
Count Definitions
FAST_CONNECT =
failures.
preamble..
FAST_CONNECT_FAIL_RL_NOT_ACQ =
This count is pegged when the AN is not able to send an Allocate Traffic
no resources available to establish a traffic channel.

the Suspend Timer is still running, i.e., before the AT goes into the Sleep mode. This call
setup procedure takes less time and uses less system resources than the standard connect
procedure. The formula is revised for R25 to use the new Fast Connect Established Calls
peg count and is expected to be more accurate than the old formula. Beginning with R28
this is the recommended metric for Fast connect Success Rate. The peg counts are defined
on a per OHM basis (changed from per AP in R28) and can be rolled up to the RNC or SN
level.
............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------------------------- X 100
FAST_CONNECT
Count Definitions
The number of fast connect procedures thatresult in an active connection
(defined as receipt of TCC or an RLP packet on the reverse traffic
channel).
FAST_CONNECT =
Number of fast connection requests.

messaging failure.
The peg counts are defined on a per sector-carrier basis. This metric is new in R26 and
replaces the separate AT-Initiated and AN-Initiated blocking ratio metrics. The separate
metrics have been deleted in R26 because the cross-carrier counts are not provided as
separate AT-initiated and AN-initiated counts. Note that the old separate formulas
continue to be provided for R25 and earlier.
............................................................................................................................................................................................................................................................
Formula
-----------------------------------------------------------------------------------------------------X100
Count Definitions
assignment).
assignment).
............................................................................................................................................................................................................................................................
due to session transfer failures
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
............................................................................................................................................................................................................................................................
carrier
raffic Channel Assignments sent by the AN on this sector-carrier in
carrier

The peg counts are defined on a per sector-carrier basis. This metric is new in R26 and is
effective with R26.
............................................................................................................................................................................................................................................................
Formula
DO AT-Initiated Connection Blocking Rate - Session Setup (%)=
-----------------------------------------------------------------------------------------------------X100
Count Definitions
T Initiated Connection Requests, Session Setup.
TCA_FOR_AT_INIT_CONN_REQ_SESS =
Traffic Channel Assignments for AT Initiated Connection Requests for session setup.
1xEV-DO Connection Blocking Rate - User (%)

This metric gives the percentage blocking for connection requests initiated for
transmission of user data. Any connection attempt failures occurring after receiving a
messaging failure.
This metric is new in R28.
Formula
DO Connection Blocking Rate - User (%) =
............................................................................................................................................................................................................................................................
AN_INIT_CONN_REQ + AT_INIT_CONN_REQ - AT_INIT_CONN_REQ_SESS -

(TCA_FOR_AN_INIT_CONN_REQ + TCA_FOR_AT_INIT_CONN_REQ -
TCA_FOR_AT_INIT_CONN_REQ_SESS))
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
assignment).
assignment).
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
AT Initiated Connection Requests, Session Setup.
Traffic Channel Assignments for AT Initiated Connection Requests for
session setup

initiated) that failed. It is defined as 100 - established connection rate (see section 4.2.1.1).
............................................................................................................................................................................................................................................................
counts defined. The new formula is effective beginning with R26 but can be used in prior
releases.
metric, DO Total Ineffective Connection Attempt Rate - Peg should now be used.
Formula
DO Total Ineffective Connection Rate (%) = 100 - DO Established Connection Rate (%))
Count Definitions
There are no peg counts explicitly used in this metric. See section 4.2.1.1 for the counts
included in the established connection rate metric.

initiated) that failed. It is defined as 100 - established connection rate - peg (see section
4.2.1.2). The formula is revised is R26 for simplification. The old formula could not be
used with the new load balancing (cross-connect feature because the established
connection counts are not defined for cross-connects. The new formula is effective
beginning with R26, but can be used in prior releases.
Formula
Count definitions
There are no peg counts explicitly used in this metric. See section 1xEV-DO Established
Connection Rate - User - Peg (%) for the counts included in the established connection
rate - peg metric.

Largely, the failures can be broken down into RF failures or blocking. The RF Failure rate
for Connections includes connection attempt failures due to reverse link not acquired and
No TCC received from the AT. Both these failures occur after the AN has sent the TCA. In
addition, another peg count, other failures - post-TCA is included in the formula to
............................................................................................................................................................................................................................................................
account for post-TCA failure not specifically pegged. Basically, the rf failure rate means
either the AT or the AN did not have sufficient signal strength to receive signalling and/or
actual traffic channel assignment packets leading up to the connection setup failure.
replaces the separate metrics used in prior releases. The formula is revised is R26 to
cross-connects.
metric, DO RF Failure Rate - Peg should now be used.
Formula
(CROSS_CARR_ATTMPT_SENT_TCA_SENT) -
------------------------------------------------------------------------------------------) X 100
............................................................................................................................................................................................................................................................
Count definitions
carrier
carrier
CROSS_CARR_ATTMPT_SENT_TCA_SENT=
connection request.
attribute set.
............................................................................................................................................................................................................................................................
receiving the TCC.
This is a catch-all forremaining failure reasons that prevent a successful
connection setup that occur aftersending TCA. The reasons may include
internal call processing errors, time outs, messagebuild or send errors,
reverse link by sending RTC_Ack message, following which it waits for the
Traffic Channel Complete (TCC) message from the AT. If TCC does not
arrive within a specific period, AN declares a connection attempt failure
and pegs this count on the Connection Request receiving sector. The failure
could be due to AT not receiving the RTC_Ack message or AN not
receiving the TCC.
............................................................................................................................................................................................................................................................
This is a catch-all for remainingfailure reasons that prevent a successful
internal call processing errors, time outs, message build or senderrors,

Largely, the failures can be broken down into RF failures or blocking. This metric is new
for R26 to use the established connection peg counts based on the revised rf failure rate
definition of TCA sent minus established calls. It is expected to be more accurate than the
detailed formula in the above metric 1xEV-DO RF Failure Rate but it is recommended
that customers use both forumula for a couple of releases to compare the values obtained
by both. The new formula is effective beginning with R26. Beginning with R28 this is the
recommended metric for RF Failure Rate.
Formula
CROSS_CARR_ATTMPT_SENT_TCA_SENT) -(AN_INIT_ESTABLISHED_CONN +
AT_INIT_ESTABLISHED_CONN + CROSS_CARR_ATTMPT_RCVD_TCC_RCVD -
------------------------------------------------------------------------------------------------- X 100
Count definitions
carrier
............................................................................................................................................................................................................................................................
carrier
connection request.
............................................................................................................................................................................................................................................................
1xEV-DO RF Failure Rate - Session Setup (%)

to the requests while the UATI session is in a state of waiting for Configuration
Negotiation. The Established Call rate, or its complementary Ineffective Connection
The peg counts are defined on a per sector-carrier basis. This metric is new in R28.
Formula
DO RF Failure Rate - Session Setup (%) =
(TCA_FOR_AT_INIT_CONN_REQ_SESS - AT_INIT_ESTABLISHED_CONN_SESS)
------------------------------------------------------------------------------------------------- X 100
TCA_FOR_AT_INIT_CONN_REQ_SESS
Count definitions
This count is incremented for a sector-carrier each time a TCA is sent for a
connection request while the UATI Session is in a state of waiting for a
Code that is not supported by this AN. This count is pegged only once for
each Connection Request procedure when multiple TCAs are sent. It is the
total of all such Connection Requests for which at least one TCA is sent.
This count pegged against the sector-carrier that received the Connection
Request. This count is used to measure the success of AT-initiated initial
supported by this AN to the point that a TCA is sent.
............................................................................................................................................................................................................................................................
established.
1xEV-DO RF Failure Rate - User (%)

initiated for transmission of user data that failed for RF air interface reasons relative to the
number of traffic channels assigned to the requests. The Established Call rate, or its
complementary Ineffective Connection Attempt rate, encompasses all types of failures
that prevent a successful connection setup. Largely, the failures can be broken down into
RF failures or blocking.
Formula
DO RF Failure Rate - User (%) =
((TCA_FOR_AN_INIT_CONN_REQ + TCA_FOR_AT_INIT_CONN_REQ -
TCA_FOR_AT_INIT_CONN_REQ_SESS) - (AN_INIT_ESTABLISHED_CONN +
AT_INIT_ESTABLISHED_CONN - AT_INIT_ESTABLISHED_CONN_SESS))
---------------------------------------------------------------------------------------------X 100
TCA_FOR_AT_INIT_CONN_REQ_SESS)
Count Definitions
carrier
carrier
............................................................................................................................................................................................................................................................
established

deleted as Alcatel-lucent supported metrics as of R25. The individual failures can be seen
............................................................................................................................................................................................................................................................
received
received
AN initiated Connection attempt failures - rev link not acquired.

This metric becomes obsolete in R28 and is replaced with a new 1xEV-DO Paging
Effectiveness.
............................................................................................................................................................................................................................................................
Formula
(1 - ---------------------------------------------------------------------------------------------) X 100
Count Definitions
PAGE_ATTEMPTS =
errors.

AT being paged. The peg counts are defined on a per AP basis. This metric is effective
beginning with R25.
This metric becomes obsolete in R28.
............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------------------X 100
Count Definitions
PAGE_ATTEMPTS =
Number of page attempts sent
Number of page times the AN sends a page to an AT and receives an AT-
initiated connection rrequest before receiving a page response.

Beginning in R28 an enhanced paging strategy is incorporated into 1xEV-DO for Quality
of Service (QoS). In addition to the simple paging process used before, there are now up to
8 configurable page attempts per pageable profile ID for QoS. The paging process
includes Last Seen Active Set paging, Last Seen RNC paging, Neighbor RNC paging (last
seen RNC and previously seen RNC), RNC Group paging, priority paging, paging area
de-escalation and paging area escalation. This provides the capability for the service
provider to specify different paging strategies for different QoS Profile IDs. It allows for
tradeoff of paging effectiveness, efficiency and latency for different applications. For
example, when paging for PTT the paging strategy might aggressively try to find the AT
on the first attempt while paging for BE the paging strategy could be optimized for
capacity. The paging area can be selected to identify the set of BTSs for which a page will
be attempted. QoS paging supports four paging area types: Last Seen Active Set, Color
Code (Last Seen RNC), RNC Group, and Neighbor RNC. The paging area type can be
............................................................................................................................................................................................................................................................
selected for each page attempt (1 through 8) for each pageable profile ID. The default
paging for Profile Ids for which QoS paging is not used is counted under the BE Profile
ID.
The peg counts are defined on an OHM-pageable profile ID-paging attempt number basis.
The effectiveness metric could be calculated per RNC-profile ID basis, but is more
meaningful per RNC Group-Profile ID since that's how the paging strategy should be
defined. This metric is effective beginning with R28.
Formula
DO Paging Effectiveness (%) =
(SUM over OHMS in RNC Group (SUM over page attempts 1 through 8)
PAGE_CR_RCVD)
---------------------------------------------------------------------------------------------X 100
(SUM over OHMS in RNC Group (PAGES for page attempt 1))
Count Definitions
PAGE_CR_RCVD =
This count is incremented when a connection request is received while
waiting for a response to the Kth Paging attempt. K varies from 1 to 8.
Therefore, there are 8 counts, one for each value of K. Note that if the
default paging of the service node is used, then the BEpID will be used for
pegging.
This count is reported per OHM-Profile ID.This count, in conjunction with

the number of pages or connection requests received, is used to monitor the
effectiveness and efficiency of each page attempt in the Paging sequence.
This information can be used to optimize the paging strategy setting.
PAGES =
This count is incremented when a page is attempted for a given attempt K
within the Paging Sequence. K varies from 1 to 8. Therefore, there are 8
counts, one for each value of K. Note that if the default paging of the
service node is used, then the BEpID will be used for pegging. This count
is reported per OHM-Profile ID.
This count, in conjunction with the count of connection requests received,

is used to monitor the effectiveness of each page attempt in the Paging
sequence. This information can be used to optimize the paging strategy
............................................................................................................................................................................................................................................................
setting. The effectiveness of page attempt K may be defined as the ratio of

number of connection requests received over the number of attempts for
attempt K. Higher value of the ratio indicates higher effectiveness.

Beginning in R25 active connection histogram counts have been added at the per sector-
30, greater than 30. It is recommended that service providers monitor these counts from a
capacity planning perspective. Alcatel-lucent performance engineers will monitor actual
customer data in order to determine what the appropriate critical triggers are and whether
additional performance metrics utilizing these counts are warranted. Details of the counts
can be found in the 1xEV-DO Service Measurements manual, 401-614-326.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

connections. The peg counts are defined on a per sector-carrier basis. The formula is
revised in R26 to account for the cross-connect (load balancing) feature. The new formula
is effective beginning with R26. Beginning with R26 there is a translation in RC/V to not
peg the CONN_REL_RLL peg count for dropped connections estimated to be caused by
"long" AT tuneaways to a 3G1x carrier. If the translation is set to to continue pegging, then
the CONN_REL_RLL count will include the tuneaways and the dropped call rate will be
inflated.
metric, DO Dropped Connection Rate - Peg should now be used.
Formula
---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
............................................................................................................................................................................................................................................................

Lost call count in the Alcatel-lucent 2G/3G1x product, of course, the logic
received
received.
AT-initiated Connection attempt failures - rev link not acquired
AT-initiated connection attempt failures - no resources available
............................................................................................................................................................................................................................................................
AN initiated Connection attempt failures - other
failures post-TCA
connection request.

connections. The peg counts are defined on a per sector-carrier basis. Beginning with R26
there is a translation in RC/V to not peg the CONN_REL_RLL peg count for dropped
connections estimated to be caused by "long" AT tuneaways to a 3G1x carrier. If the
translation is set to to continue pegging, then the CONN_REL_RLL count will include the
tuneaways and the dropped call rate will be inflated. The formula is revised in R26 to
account for the cross-connect (load balancing) feature. The new formula is effective
beginning with R26. The SO_SOR_HOFF_FAIL_NO_AT_RSP peg was deleted from the
formula because beginning in R26 these failures are included as part of the connection
release - other reasons count (CONN_REL_OTHER_REASON).
Formula
---------------------------------------------------------------------------------------------X 100
............................................................................................................................................................................................................................................................
Count Definitions
CONN_REL_RLL =
Connection Release - RF Link LostCONN_REL_OTHER_REASON =
Connection Release - Other Reasons
Number of AT initiated successful connections
Number of AN initiated successful connections.
connection request.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

The formula is revised in R25. The new formula is applicable for releases R25 and later.
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
............................................................................................................................................................................................................................................................
message, i.e., the DRC-pointed sector (also known as requesting or source
sector).
SO_SOR_HOFF_CONN_CLOSE_PRETCA =
The number of soft/softer handoffs when a connection close or session
close is received before TCA and prior to completion of the handoff
procedure.
SO_SOR_HOFF_CONN_CLOSE_POSTTCA=
close is received after TCA but prior to completion of the handoff
procedure.
............................................................................................................................................................................................................................................................

The formula is changed in R28 to subtract the new peg counts measuring hard handoff
terminations due to receipt of a session close or connection close message. The new
formula is applicable to releases R28 and later.
Formula
(HHOFF_ATTMPT_REQ - HHOFF_CONN_CLOSE_POSTTCA_REQ -
HHOFF_CONN_CLOSE_PRETCA_REQ - (HHOFF_FAIL_NO_RESOURCE_REQ +
-------------------------------------------------------------------------------------------------- X 100
HHOFF_CONN_CLOSE_PRETCA_REQ)
Count Definitions
HHOFF_ATTMPT_REQ =
All of these handoff counts are pegged on the sector-carrier that received
Route Update message.
HHOFF_CONN_CLOSE_POSTTCA_REQ =
This count is the number of inter-frequency hard handoff attempts that are
terminated when a connection close or session close is received after TCA.
It is pegged on the sector-carrier that received the Route Update message
that prompted the handoff.
............................................................................................................................................................................................................................................................
HHOFF_CONN_CLOSE_PRETCA_REQ =
terminated when a connection close or session close is received before
TCA. It is pegged on the sector-carrier that received the Route Update
message that prompted the handoff.

............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------ X 100
Count Definitions
SO_SOR_HOFF_ATTMPT_TARGET = Soft-Softer HO Attempt at the target sector-

carrier




............................................................................................................................................................................................................................................................


assignment

assignment

This metric gives the success rate for hard handoffs to the target sector (hand-ins). The
Formula
(HHOFF_ATTMPT_TARGET - HHOFF_CONN_CLOSE_POSTTCA_TARGET -
HHOFF_CONN_CLOSE_PRETCA_TARGET -
(HHOFF_FAIL_NO_RESOURCE_TARGET + HHOFF_FAIL_NO_AT_RSP_TARGET
+ HHOFF_FAIL_OTHER_PRETCA_TARGET +
HHOFF_FAIL_OTHER_POSTTCA_TARGET))
--------------------------------------------------------------------------------------------------- X 100
HHOFF_CONN_CLOSE_PRETCA_TARGET)
Count Definitions
HHOFF_CONN_CLOSE_POSTTCA_TARGET = This count is the number of inter-

frequency hard handoff attempts that are terminated when a connection
close or session close is received after TCA. It is pegged on the target
sector-carrier.
............................................................................................................................................................................................................................................................
HHOFF_CONN_CLOSE_PRETCA_TARGET= This count is the number of inter-

close or session close is received before TCA. It is pegged on the target
sector-carrier.


carrier due to no response from the AT.



normally would have resulted in an active set change. The soft/er handoff blocks, in
general, are errors that occur entirely within the AN. Since there is no messaging involved
with the AT or an element outside the AN between the time a RUM is received and a TCA
is sent, there is little vulnerability from these outside sources.
pegged at the requesting sector. The formula is revised in R25 to more closely match other
blocking formulae and is applicable to all prior releases.
............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
SO_SOR_HOFF_ATTMPT= Soft-Softer HO Attempt



of legs is reached.
............................................................................................................................................................................................................................................................

sources.
the cell).
sector. The metric is new in R26 and is effective with R26.
Formula
(HHOFF_ATTMPT_REQ - HHOFF_CONN_CLOSE_PRETCA_REQ -
HHOFF_TCA_SENT_REQ)
------------------------------------------------------------------------------------------ X 100
HHOFF_ATTMPT_REQ - HHOFF_CONN_CLOSE_PRETCA_REQ
Count Definitions
HHOFF_ATTMPT_REQ =
............................................................................................................................................................................................................................................................
to perform an inter-frequency hard handoff. Both of these handoff counts
are pegged on the sector-carrier that received Route Update message, i.e.,
the DRC-pointed sector (also known as requesting or source sector).
............................................................................................................................................................................................................................................................

is applicable to R24.
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions



............................................................................................................................................................................................................................................................

Formula
(HHOFF_ATTMPT_TARGET - HHOFF_CONN_CLOSE_PRETCA_TARGET -
HHOFF_TCA_SENT_TARGET)
-------------------------------------------------------------------------------------- X 100
(HHOFF_ATTMPT_TARGET - HHOFF_CONN_CLOSE_PRETCA_TARGET)
Count Definitions
HHOFF_CONN_CLOSE_PRETCA_TARGET = This count is the number of inter-

close or session close is received prior to TCA.
HHOFF_TCA_SENT_TARGET = TCA sent in response to a hard handoff attempt.

counted as one handoff attempt.The peg counts are defined on a per sector-carrier basis
and are pegged at the requesting sector. This metric is new in R25 and is applicable to
releases R24 and later.
............................................................................................................................................................................................................................................................
The formula is revised in R27 to subtract the new count that measurse the number of times
Formula
DO SSO RF Failure Rate Requesting Sector (%) =
------------------------------------------------------------------------------ X 100
Count Definitions
TCA sent by the AN
SO_SOR_HOFF_CONN_CLOSE_POSTTCA =
procedure.

sector. This metric is new in R26 and is applicable to releases R26 and later.
Formula
............................................................................................................................................................................................................................................................
----------------------------------------------------------- X 100
(HHOFF_TCA_SENT_REQ - HHOFF_CONN_CLOSE_POSTTCA_REQ)
Count Definitions
sent by the AN.

and are pegged at the target sector. This metric is new in R25 and is applicable to releases
R24 and later.
Formula
--------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
TCA sent by the AN.


Formula
--------------------------------------------------------------------------------- X 100
HHOFF_TCA_SENT_TARGET - HHOFF_CONN_CLOSE_POSTTCA_TARGET
Count Definitions
sent by the AN.
............................................................................................................................................................................................................................................................
HHOFF_CONN_CLOSE_POSTTCA_TARGET =
terminated when a connection close or session close is received after TCA
but prior to completion of the handoff process.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
1xEV-DO Forward Link Data Re-Transmission Rate - EVM

in RLP NAKs.
This metric is defined on a per sector-carrier basis. Beginning with R28, this metric will
are provided for sector-carriers equipped with an SBEVM.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions
RLP_RETXED_FTC= The total number of RLP octets requested for re-transmission by

............................................................................................................................................................................................................................................................
channel.
1xEV-DO Forward Link Data Re-Transmission Rate (NAK) - SBEVM

errors. For example, a dirty T1 could result in data loss between the cell and the RNC. It
in RLP NAKs.
This metric is defined on a per sector-carrier basis and is applicable to sector-carriers
equipped with an SBEVM. Peg counts are provided for each flow type but are separated
by NAK retransmissions and DARQ retransmissions. Separate metrics are provided for
............................................................................................................................................................................................................................................................
each case, but combine all applicable flows. into a single metric. Separate calculations can
be made for individual flows. The metric is new in R28 and is not applicable to prior
releases.
Formula
DO forward retransmission rate (NAK) - SBEVM (%) =
(EVM_RLP_RETXED_FTC_BE + EVM_RLP_RETXED_FTC_SMC)
----------------------------------------------------------------------------X 100
(EVM_RLP_TXED_FTC_BE + EVM_RLP_TXED_FTC_SMC)
Count Definitions
EVM_RLP_RETXED_FTC_BE = This count shall be incremented for each Best Effort

RLP octet that is re-transmitted to an AT in response to a NAK recevied
from the previous tranmission. It is the total of all octets retransmitted on
the forward traffic channels for a sector-carrier.
EVM_RLP_RETXED_FTC_SMC = his count shall be incremented for each SMC RLP

octet that is re-transmitted to an AT in response to a NAK recevied from
the previous tranmission. It is the total of all octets retransmitted on the
forward traffic channels for a sector-carrier.This count shall not include the
RLP octets retransmitted on FTC when DARQ is turned on.
TEVM_RLP_TXED_FTC_BE = This count shall be incremented for each Best Effort

RLP octet transmitted to an AT and it shall not include any octets that may
be used for padding at the MAC layer. It is the total of all octets transmitted
on the forward traffic channels for a sector-carrier.
EVM_RLP_TXED_FTC_SMC = This count shall be incremented for each SMC RLP

octet transmitted to an AT and it shall not include any octets that may be
used for padding at the MAC layer. It is the total of all octets transmitted on
the forward traffic channels for a sector-carrier. This count shall not include
any of the re-transmitted RLP octets.
1xEV-DO Forward Link Retransmission Rate (DARQ) - SBEVM

............................................................................................................................................................................................................................................................
errors. For example, a dirty T1 could result in data loss between the cell and the RNC
with nothing to do with the underlying RF channel. The AT itself may also drop RLP
packets or mis-segment them if it is unable to keep up with the processing, resulting in
RLP NAKs.
releases.
Formula
DO forward retransmission rate (DARQ - SBEVM (%) =
(EVM_RLP_RETXED_FTC_DARQ_BE + EVM_RLP_RETXED_FTC_DARQ_CPS +
EVM_RLP_RETXED_FTC_DARQ_CS + EVM_RLP_RETXED_FTC_DARQ_CV +
EVM_RLP_RETXED_FTC_DARQ_SMC)
---------------------------------------------------------------------------------------------------- X 100
(EVM_RLP_TXED_FTC_BE + EVM_RLP_TXED_FTC_CPS +
EVM_RLP_TXED_FTC_CS + EVM_RLP_TXED_FTC_CV +
EVM_RLP_TXED_FTC_SMC)
Count Definitions
EVM_RLP_RETXED_FTC_DARQ_BE = This count shall be incremented for each Best

Effort RLP octet that is re-transmitted to an AT when DARQ is turned on.
It is the total of all octets retransmitted on the forward traffic channels for a
sector-carrier.
............................................................................................................................................................................................................................................................
EVM_RLP_RETXED_FTC_DARQ_CPS = This count shall be incremented for each

Push-to-Talk RLP octet that is re-transmitted to an AT when DARQ is
turned on. It is the total of all octets retransmitted on the forward traffic
channels for a sector-carrier.
EVM_RLP_RETXED_FTC_DARQ_CS = This count shall be incremented for each

Conversational Speech (with or without ROHC) RLP octet that is re-
transmitted to an AT when DARQ is turned on. It is the total of all octets
retransmitted on the forward traffic channels for a sector-carrier.
EVM_RLP_RETXED_FTC_DARQ_CV = This count shall be incremented for each

Conversational Video (with or without ROHC) RLP octet that is re-
transmitted to an AT when DARQ is turned on. It is the total of all octets
EVM_RLP_RETXED_FTC_DARQ_SMC = This count shall be incremented for each

SMC RLP octet that is re-transmitted to an AT due to DARQ is turned on.
sector-carrier.
EVM_RLP_TXED_FTC_BE = This count shall be incremented for each Best Effort RLP
EVM_RLP_TXED_FTC_CPS = This count shall be incremented for each Push-to-Talk

on the forward traffic channels for a sector-carrier. This count shall not
include any of the re-transmitted RLP octets.
EVM_RLP_TXED_FTC_CS = This count shall be incremented for each Conversational

Speach (with or without ROHC) RLP octet transmitted to an AT and it
shall not include any octets that may be used for padding at the MAC layer.
It is the total of all octets transmitted on the forward traffic channels for a
sector-carrier. This count shall not include any of the re-transmitted RLP
octets.
............................................................................................................................................................................................................................................................
EVM_RLP_TXED_FTC_CV = This count shall be incremented for each Conversational

Video (with or without ROHC) RLP octet transmitted to an AT and it shall
not include any octets that may be used for padding at the MAC layer. It is
the total of all octets transmitted on the forward traffic channels for a
octets.


Formula
DO reverse retransmission rate (%) =
MISSING_RLP_REQ_RTC
-------------------------------------------X100
RLP_RXED_RTC
Count Definitions

message. As on the forward link, any such missing data can be NAKed
............................................................................................................................................................................................................................................................

Formula
-------------------------------------------------------------------------------------------X100
MISSING_RLP_REQ_RTC
............................................................................................................................................................................................................................................................
Count Definitions

retransmit it.

MAC layer. The formula is changed in R24 to account for the peg counts being MAC layer
packets. The new formula is applicable to all previous releases.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions







............................................................................................................................................................................................................................................................





1xEV-DO Total Forward Link Physical Layer Data Transmitted - SBEVM(MB)

Reverse Link Data Re-Transmission Rate. The counts are the total of all Rel 0 and Rev A
connections. The MAC layer data transmitted metric is still applicable to sector-carriers
equipped with an EVM. This metric is new in R27 and is not applicable to prior releases.
Formula
EVM_FTC_TOT_BYTES_307_2 + EVM_FTC_TOT_BYTES_614_4
+EVM_FTC_TOT_BYTES_921_6 + EVM_FTC_TOT_BYTES_1228_8
+EVM_FTC_TOT_BYTES_1536 + EVM_FTC_TOT_BYTES_1843_2 +
-----------------------------------------------------------------------------------------------------------
10 ^ 6
............................................................................................................................................................................................................................................................
Count Definitions

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.




............................................................................................................................................................................................................................................................





............................................................................................................................................................................................................................................................

A composite data volume for the Forward Link physical layer can be defined that is
independent of modem type by combining the formulae in the previous two sections. The
=
(1024/8 * (EVM_FWD_PACKETS_38_4_TOTAL_COUNT +
EVM_FWD_PACKETS_2457_6_TOTAL_COUNT) + (EVM_FTC_TOT_BYTES_4_8 +
EVM_FTC_TOT_BYTES_614_4 +EVM_FTC_TOT_BYTES_921_6 +
EVM_FTC_TOT_BYTES_1228_8 +EVM_FTC_TOT_BYTES_1536 +
EVM_FTC_TOT_BYTES_3072))
--------------------------------------------------------------------------------------- =
10 ^ 6
............................................................................................................................................................................................................................................................

In 1xEVDO, active users continuously request the rate (commonly known as DRC rate) at
sector.
wait time), but is a very good indication of the sum of individual user perceived data rates.
For example, if there are 10 users each getting 100 kbps continuously over the hour or 1
user getting 1Mbps throughout the hour, the metric will report 1Mbps in both the cases.
............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
differentiate between them. The metric can only be aggregated to higher level network
elements if all modems in the aggregation are the same type. Alternatively, in order to
aggregate the forward link MAC layer data rate to a higher network element the
denominator can be calculated as follows:
( ((EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 8) * 2,160,000) - S
(EVM_FTC_NUM_SLOT_rate)) * 0.001667,
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------
Count Definitions






............................................................................................................................................................................................................................................................







metric in 4.2.4.6. The counts are the total of all Rel 0 and Rev A connections. The MAC
layer data rate metric is still applicable to sector-carriers equipped with an EVM. The
metric is defined on a per sector-carrier basis and is defined only for the one hour
The peg counts are measured in the SBEVM at the physical layer. In the 1xEV-DO
protocol stack, the physical layer resides below the MAC layer.
In 1xEVDO Rel 0, active ATs continuously request the rate (commonly known as DRC
............................................................................................................................................................................................................................................................
higher rates.
............................................................................................................................................................................................................................................................
hardware, etc.).
EVM.
equipped with a SBEVM, replacing the MAC layer data rate metric in 4.2.4.6. The counts
are the total of all Rel 0 and Rev A connections. The MAC layer data transmitted metric is
still applicable to sector-carriers equipped with an EVM. This metric is new in R27 and is
not applicable to prior releases.
Formula
DO Forward Link Physical Layer Data Rate - SBEVM (kbps)=
------------------------------------------------------------------------------------------------------------
EVM_FTC_NUM_SLOT_307_2 + EVM_FTC_NUM_SLOT_614_4
+EVM_FTC_NUM_SLOT_921_6 + EVM_FTC_NUM_SLOT_1228_8
+EVM_FTC_NUM_SLOT_1536 + EVM_FTC_NUM_SLOT_1843_2 +
Count Definitions

and Rev A traffic.
............................................................................................................................................................................................................................................................

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.






............................................................................................................................................................................................................................................................










............................................................................................................................................................................................................................................................








............................................................................................................................................................................................................................................................
=
+
EVM_FTC_TOT_BYTES_2457_6 + EVM_FTC_TOT_BYTES_3072))
--------------------------------------------------------------------------------------------------
This metric provides a measure of the average per user perceived data rate on a sector-
carrier. It uses the active usage peg count which measures the number of users either
............................................................................................................................................................................................................................................................
Formula
-----------------------------------------------------------------------------------------------------------
Count Definitions

and Rev A traffic.E
VM_FTC_TOT_BYTES_9_6 = The number of Physical Layer bytes transmitted on the

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

and Rev A traffic.

............................................................................................................................................................................................................................................................








transmission.
............................................................................................................................................................................................................................................................



users.
very high (say in 90s, wont reach 100% because the % busy slots exclude the
synchronous and asynchronous Control Channel slots); this is not a surprising result. This
underscores the fact that the metric should be interpreted collectively with Average active
connections or another peg count called Evm_Avg_Elig_User (Average number of
Scheduler Eligible Users to determine if indeed there are a large number of users
responsible for driving up the loading.
modem at the physical layer (slots are only defined at the physical layer). The formula is
changed in R24 to use the percent busy slots peg count and is applicable to previous
releases beginning with R22. Note that the peg count measures only those slots used for
actual traffic transmission so the control slot counts do not have to be subtracted.
............................................................................................................................................................................................................................................................
Formula
Count Definitions

measurement hour that were actually used for forward link traffic data

per second.
transmission rate).
It may slightly inlfate the data rate at virtual soft handoff events. The RLP bytes are
............................................................................................................................................................................................................................................................
The above issue does not impact virtual softer handoffs. However, there could be
small amount of error stemming from pegging bytes on the older sector a little while
longer than actual virtual softer handoff transfer. There is no impact if RLP bytes are
viewed on a per-cell basis or RNC/SN wide
is not far off the mark especially at moderate to high loading points.
Beginning with R28 this metric will report 'zero' for sector-carriers equipped with a single
board EVM (SBEVM). New metrics are provided for sector-carriers equipeed with an
SBEVM. However, there are difficulties in aggregating this metric to higher level network
elements since the EVM_TOTAL_BUSY_PCNT_SLOTS count is pegged for both
modems and does not differentiate between them. The metric can only be aggregated to
higher level network elements if all modems in the aggregation are the same type.
Formula
--------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

transmission (divide by 10^6 to get percentage).
per second.
of RF conditions at the time the user was served.
Since the RLP byte counts are pegged in the modem for the SBEVM, most of the caveats
regarding the use of the metric discussed in the previous metric (for the EVM) do not
apply to secotr-carriers equipped with an SBEVM. The only remaining potential source of
inaccuracy is that the metric does not capture a very small amount of throughput loss due
to some of the re-transmitted RLP packets not reaching the end user (typically ~0.02% for
a 1% re-transmission rate).
This metric is revised in R28. The changes are not applicable to prior releases.
............................................................................................................................................................................................................................................................
Formula
((EVM_RLP_TXED_FTC_BE + EVM_RLP_TXED_FTC_CPS +
EVM_RLP_TXED_FTC_SMC) * 8) / 1000
---------------------------------------------------------------------------------------------------------
Count Definitions


octets.

............................................................................................................................................................................................................................................................
octets.








............................................................................................................................................................................................................................................................








A composite data rate for the Forward Link RLP layer can be defined that is independent
of modem type by combining the formulae in the previous two sections. The formula is
defined at the sector-carrier level and can be aggregated to higher level network elements.
The formula is effective with R28. The composite formula is:
............................................................................................................................................................................................................................................................
Formula
DO RLP Forward Link Composite Data Rate (kbps) =
((RLP_TXED_FTC + EVM_RLP_TXED_FTC_BE + EVM_RLP_TXED_FTC_CPS +
------------------------------------------------------------------------------------------------------------
denominator is Average Active Connections it is actually the sum of all the total
connections based on a 10 second scan. Note that if the count is read from WatchMark
Prospect for Alcatel-lucent it has already been divided by 360 and should not be divided
again. This metric is new in R24 and is applicable to all previous releases.
This metric is defined at the sector-carrier level, is independent of modem type and can be
aggregated to higher level network elements. The formula is revised in R28 and is not
............................................................................................................................................................................................................................................................
Formula
(RLP_TXED_FTC + EVM_RLP_TXED_FTC_BE + EVM_RLP_TXED_FTC_CPS +
EVM_RLP_TXED_FTC_SMC) / 10 ^ 6
----------------------------------------------------------------------------------------------------
Count Definitions


octets.

octets.
............................................................................................................................................................................................................................................................

once per slot.
applicable only to sector-carriers equipped with the SBEVM and is new for R27. The
formula is revised in R28 and is not applicable to prior releases.
Formula
------------------------------------------------------------------------------------------------------------
(EVM_ACTIVE_USAGE * 0.001667)
Count Definitions
............................................................................................................................................................................................................................................................


octets.

octets.

transmission.
............................................................................................................................................................................................................................................................


Formula
(256 * REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS + 512 *
REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS + 1024 *
------------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions
REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS= Number of 9.6 kbps reverse
link frames (256 bits/frame)
............................................................................................................................................................................................................................................................
REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS= Number of 153.6 kbps

reverse link frames (4096 bits/frame)
Formula
(128 * REV_PACKETS_128_TOTAL_COUNT + 256 *
REV_PACKETS_256_TOTAL_COUNT +512 * REV_PACKETS_512_TOTAL_COUNT
+ 768 * REV_PACKETS_768_TOTAL_COUNT +1024 *
REV_PACKETS_1024_TOTAL_COUNT + 1536 *
REV_PACKETS_1536_TOTAL_COUNT +2048 *
REV_PACKETS_8192_TOTAL_COUNT + 12288
*REV_PACKETS_12288_TOTAL_COUNT)
----------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions




............................................................................................................................................................................................................................................................








of 12288 bits received on the reverse traffic

A composite data volume for the Reverse Link physical layer can be defined that is
DO Reverse Link Physical Layer Composite Data Volume (MB) =
............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------------------------------------
8 * 10^6
rates.
Formula:
............................................................................................................................................................................................................................................................
(9.6 * REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS + 19.2 *

REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS + 38.4 *
REV_OUTER_LOOP_PC_FRAME_COUNT_768KBPS + 153.6
*REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS)
---------------------------------------------------------------------------------------------------
Count Definitions





This metric gives the average data rate on the reverse link in kilobits per second for sector-
carriers equipped with an SBEVM. The metric is defined on a per sector-carrier basis.
in 4.2.4.15. The denominator uses the sum of the subpackets times the subpacket duration
of 6.6 ms.
............................................................................................................................................................................................................................................................
Formula
REV_PACKETS_12288_TOTAL_COUNT) / 10 ^ 3
----------------------------------------------------------------------------------------
(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +NUM_SUBPKTS_RL_512 +
NUM_SUBPKTS_RL_768 +NUM_SUBPKTS_RL_1024 + NUM_SUBPKTS_RL_1536
+NUM_SUBPKTS_RL_2048 +NUM_SUBPKTS_RL_3072
+NUM_SUBPKTS_RL_4096 + NUM_SUBPKTS_RL_6144
+NUM_SUBPKTS_RL_8192 + NUM_SUBPKTS_RL_12288) * 0.00667
Count Definitions





............................................................................................................................................................................................................................................................













............................................................................................................................................................................................................................................................






[(256* REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS +512 *
REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS +1024 *
REV_OUTER_LOOP_PC_FRAME_COUNT_384KBPS +2048*
REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS) + (128 *
REV_PACKETS_1536_TOTAL_COUNT+2048 *
REV_PACKETS_12288_TOTAL_COUNT)] /1000
----------------------------------------------------------------------------------------
[(REV_OUTER_LOOP_PC_FRAME_COUNT_96KBPS
+REV_OUTER_LOOP_PC_FRAME_COUNT_192KBPS
............................................................................................................................................................................................................................................................
+REV_OUTER_LOOP_PC_FRAME_COUNT_1536KBPS) * 0.0266]
+[(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_512 + NUM_SUBPKTS_RL_768 + NUM_SUBPKTS_RL_1024
+ NUM_SUBPKTS_RL_1536 + NUM_SUBPKTS_RL_2048
+NUM_SUBPKTS_RL_3072 + NUM_SUBPKTS_RL_4096 +
NUM_SUBPKTS_RL_12288) * 0.00667]

metric is provided for sector-carriers equipped with an SBEVM. This metric can only be
aggregated to higher level network elements if all modems are EVMs.
Formula
----------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
RLP_RXED_RTC= The total number of original RLP octets received on the reverse link






with an SBEVM (4.2.4.23). This metric is closer to the true end-user experienced
............................................................................................................................................................................................................................................................
aggregate of all Rel 0 and Rev A connections. It can only be aggregated to higher level
network elements if all modems are SBEVMs.
Formula
----------------------------------------------------------------------------------------
Count Definitions


recieved on the reverse traffic channel.



bits recieved on the reverse traffic channel.

............................................................................................................................................................................................................................................................







aggregated to higher level network elements. The composite formula is
----------------------------------------------------------------------------------------
+
[(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 + NUM_SUBPKTS_RL_512
+ NUM_SUBPKTS_RL_768 + NUM_SUBPKTS_RL_1024 +
NUM_SUBPKTS_RL_1536 + NUM_SUBPKTS_RL_2048
NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
Error Statistics
............................................................................................................................................................................................................................................................

processing a frame whose RRI bits indicated a rate of 9.6kbps or higher.The metric is a
useful indication of prevailing RF conditions experienced by the user on the reverse link.
If the RLP layer re-transmissions are significantly higher than the physical layer error rate
(which usually ranges from 0.5 to 1.5%), it is indicative of problems outside of the RF link
(typically, the backhaul, the cell aggregation router, or some processing burden constraints
at the AT).
level.
Formula
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Power Control
............................................................................................................................................................................................................................................................

frames when no data is received, i.e., 0 kbps frames. The peg counts are defined on a per
sector-carrier basis.
Formula
DO Avg RL PC Setpoint 0 kbps (dB)=
--------------------------------------------------------------------------------
Count Definitions

the frame rateis 0kbps. This is only counted on the DRC pointed sector.

frames in which the data rate is 9.6 kbps. The peg counts are defined on a per sector-
carrier basis.
Formula
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

dB/8.

frames in which the data rate is 19.2 kbps. The peg counts are defined on a per sector-
carrier basis.
Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

Formula
---------------------------------------------------------------------------------
Count Definitions

dB/8.

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------
Count Definitions

count are dB/8.

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions

Formula
---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------
Count Definitions


............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO.
compare with 2G/3G1x, this would be similar to Total Walsh Code metric with the only
difference that in 1xEV-DO it has meaning on the reverse link only.
level. Although the peg count name is Average Active Connections it is actually the sum
of all the total connections based on a 10 second scan. Note that if the count is read from
IBM Prospect for Alcatel-lucent it has already been divided by 360 and should not be
divided again.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................

an SBEVM and count both Rel 0 and Rev A connections. They can be aggregated to the
cell level only if all sector-carriers on that cell are equipped with an SBEVM.
Formula
Count Definitions

............................................................................................................................................................................................................................................................
(average * 100).

connections.
Formula
-----------------------------------------------------------------------
Count Definitions


............................................................................................................................................................................................................................................................
(average * 100).
............................................................................................................................................................................................................................................................
Performance Metrics for Release 28 Quality of service(QoS) metrics
Quality of service(QoS) metrics

............................................................................................................................................................................................................................................................

This metric provides the success rate of ReservationOnRequests (RoR) received by the
AN. An RoR is accepted only when all of the reservations included in the request can be
successfully admitted using the admission evaluation algorithms defined by call
processing. There are peg counts for the specific reasons for rejection that should be
monitored by the user, especially if the success rate falls to an unacceptably low level.
The peg counts are defined on a sector-carrier basis. If the RoR is bundled with a
connection request, then the counts are pegged against the sector-carrier that received the
request. If the RoR comes alone, then since the connection is already established, the
counts are pegged against the current serving sector-carrier. This metric is effective
beginning in R28.
Formula
DO RoR Success Rate (%)=
ROR_ACCEPTED
-------------------------------------X100
ROR_RECEIVED
Count Definitions
ROR_ACCEPTED = The number of ReservationOnRequests accepted by the AN. An

RoR is accepted only when all of the reservations included in the request
can be successfully admitted using the admission evaluation algorithms
defined in call processing (i.e., when sufficient resources are available to
support all of the reservations.)
ROR_RECEIVED = The number of RoRs received from an AT, regardless of whether it is

bundled with a connection request.
1xEV-DO FL Conversational Speech Reservation Success Rate

This metric provides the success rate of forward link conversational speech reservation
requests. It provides a measure of the loading on the system. The peg counts are defined
on a sector-carrier basis. This metric is new in R28.
Formula
DO FL CS Res Success Rate (%) =
............................................................................................................................................................................................................................................................
FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT
-----------------------------------------------------------------------X100
FL_REQ_CONV_RATE_SET_1_SPEECH
Count Definitions
FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT = This count is incremented when

a FL reservation of Conversational Speech is included in a
ReservationOnRequest that has been accepted.
FL_REQ_CONV_RATE_SET_1_SPEECH = This count is incremented when a FL

reservation of Conversational Speech is included in a
ReservationOnRequest.
1xEV-DO FL Conversational Speech Dropped Reservation Rate

This metric provides a measure of the dropped reservation rate for Forward Link
conversational speech reservations relative to the number of accepted reservations. The
peg counts are defined on a sector-carrier basis. This metric is effective beginning in R28.
Formula
DO FL CS Dropped Res Success Rate (%) =
FL_CONV_RATE_SPEECH_DROPPED_BH_OVERLOAD
----------------------------------------------------------------------------X100
FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT
Count Definitions
FL_CONV_RATE_SPEECH_DROPPED_BH_OVERLOAD = This count is incremented

when a FL reservation of Conversational Speech is terminated due to
backhaul overload.
FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT = This count is incremented when

a FL reservation of Conversational Speech is included in a
1xEV-DO FL Conversational Video Reservation Success Rate

This metric provides the success rate of forward link conversational video reservation
............................................................................................................................................................................................................................................................
Formula
DO FL CV Res Success Rate (%) =
FL_REQ_CONV_VIDEO_ACCEPT
--------------------------------------------------------------X100
FL_REQ_CONV_VIDEO
Count Definitions
FL_REQ_CONV_VIDEO_ACCEPT = This count is incremented when a FL reservation

of Conversational Video is included in a ReservationOnRequest that has
been accepted.
FL_REQ_CONV_VIDEO = This count is incremented when a FL reservation of

Conversational Video is included in a ReservationOnRequest.
1xEV-DO FL Conversational Video Dropped Reservation Rate

Formula
DO FL CV Dropped Res Rate (%) =
FL_CONV_VIDEO_BH_OVERLOAD
----------------------------------------------------------X100
FL_REQ_CONV_VIDEO_ACCEPT
Count Definitions
FL_CONV_VIDEO_BH_OVERLOAD = This count is incremented when a FL

reservation of Conversational Video is terminated due to backhaul
overload.
FL_REQ_CONV_VIDEO_ACCEPT = This count is incremented when a FL reservation

been accepted.
............................................................................................................................................................................................................................................................
1xEV-DO FL Conversational PTT Speech Reservation Success Rate

This metric provides the success rate of forward link conversational PTT reservation
Formula
DO FL PTT Res Success Rate (%) =
FL_RESV_ADMT_CONV_PTT_SPEECH
-----------------------------------------------------------------------X100
FL_RESV_REQ_CONV_PTT_SPEECH
Count Definitions
FL_RESV_ADMT_CONV_PTT_SPEECH = This count is incremented when a FL

reservation of Conversational PTT Speech is included in a
FL_RESV_REQ_CONV_PTT_SPEECH = This count is incremented when a FL

reservation of Conversational PTT Speech is included in a
ReservationOnRequest.
1xEV-DO FL Conversational PTT Speech Dropped Reservation Rate

conversational push-to-talk speech reservations relative to the number of accepted
reservations. The peg counts are defined on a sector-carrier basis. This metric is effective
beginning in R28.
Formula
DO FL PTT Dropped Res Rate (%) =
FL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_OVL
-----------------------------------------------------------------------X100
FL_RESV_ADMT_CONV_PTT_SPEECH
Count Definitions
FL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_OVL = This count is incremented

when a FL reservation of conversational push-to-talk Speech is terminated
due to backhaul overload.
............................................................................................................................................................................................................................................................
FL_RESV_ADMT_CONV_PTT_SPEECH = This count is incremented when a FL

reservation of Conversational PTT Speech has been accepted.
1xEV-DO RL Conversational Speech Dropped Reservation Rate

This metric provides a measure of the dropped reservation rate for Reverse Link
Formula
DO RL CS Dropped Res Rate (%) =
(RL_CONV_RATE_SPEECH_DROPPED_BH_OVERLOAD +
RL_CONV_RATE_SPEECH_DROPPED_RLRF_OLOAD)
---------------------------------------------------------------------------------X100
RL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT
Count Definitions
RL_CONV_RATE_SPEECH_DROPPED_BH_OVERLOAD = This count is

incremented when a RL reservation of Conversational Speech is
terminated due to backhaul overload.
RL_CONV_RATE_SPEECH_DROPPED_RLRF_OLOAD = This count is incremented

when a RL reservation of Conversational Speech is terminated due to
reverse link RF overload.
RL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT = This count is incremented when

a RL reservation of Conversational Speech is included in a
1xEV-DO RL Conversational Video Dropped Reservation Rate

conversational video reservations relative to the number of accepted reservations. The peg
counts are defined on a sector-carrier basis. This metric is effective beginning in R28.
Formula
DO RL CV Dropped Res Rate (%) =
(RL_CONV_VIDEO_BH_OVERLOAD +RL_CONV_VIDEO_RLRF_OVERLOAD)
-----------------------------------------------------------------------X100
RL_REQ_CONV_VIDEO_ACCEPT
............................................................................................................................................................................................................................................................
Count Definitions
RL_CONV_VIDEO_BH_OVERLOAD = This count is incremented when a RL

reservation of Conversational Speech is terminated due to backhaul
overload.
RL_CONV_VIDEO_RLRF_OVERLOAD = This count is incremented when a RL

reservation of Conversational Speech is terminated due to reverse link RF
overload.
RL_REQ_CONV_VIDEO_ACCEPT = This count is incremented when a RL reservation

been accepted.
1xEV-DO RL Conversational PTT Speech Dropped Reservation Rate

beginning in R28.
Formula
DO RL PTT Dropped Res Rate (%) =
(RL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_OVL
+RL_RESV_DRPD_CONV_PTT_SPCH_RL_RF_OVL)
--------------------------------------------------------------------------X100
RL_RESV_ADMT_CONV_PTT_SPEECH
Count Definitions
RL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_OVL = This count is incremented

when a RL reservation of conversational push-to-talk Speech is terminated
due to backhaul overload.
RL_RESV_DRPD_CONV_PTT_SPCH_RL_RF_OVL = This count is incremented when

a RL reservation of Conversational push-to-talk Speech is terminated due
to reverse link RF overload.
RL_RESV_ADMT_CONV_PTT_SPEECH = This count is incremented when a RL

reservation of Conversational PTT Speech has been accepted.
............................................................................................................................................................................................................................................................
for Alcatel-Lucent Release 28

............................................................................................................................................................................................................................................................
Overview
The purpose of this chapter is to describe new and modified Primitive Calculations in IBM
Prospect for Alcatel-lucent R28 that support 1XEV-DO Performance Metrics.
Note that as of R28 the name Watchmark Prospect changes to IBM Prospect.
12 modified PCALCs for previously supported 1xEV-DO performance metrics (see
Modified 1xEV-DO Performance Metrics for RNC R28 (p. 16-3),
33 new 1xEV-DO performance metrics for R28 (see New 1xEV-DO Performance
Metrics in Prospect R28 (p. 16-14) ),
Note that nine existing metrics have modified descriptions in the Performance Data
Reference (PDR) and in the GUI of the template in R28 to explicitly identify whether they
apply to EVM or SBEVM boards.
These changes are made to explicitly identify whether they apply to EVM or SBEVM
boards (see (p. 16-40)).
The new and modified PCALCs defined in this section are implemented in R28 of
calculations that did not change in R28 are contained in the document for those earlier
releases:
25
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent 1xEV-DO Performance Metrics
Release 28

26
Chapter 14, 1xEV-DO Metrics in IBM Prospect for Alcatel-lucent Release 27
Chapter 16, 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 28
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Modified 1xEV-DO Performance Metrics for
Release 28 RNC R28
Modified 1xEV-DO Performance Metrics for RNC R28

............................................................................................................................................................................................................................................................
D Op _ FL RL P Av gR a te _ SB EV M = ( 8 .0 /1 00 0 .0 ) * ( R LP Tx e dF TC _ BE +
R LP T xe dF T C_ CP S + RL PT x ed FT C _C S + R L PT xe d FT C _C V +
R LP T xe dF T C_ SM C )/ (( FT C Nu mS l ot _ 4_ 8 + F TC N um S lo t_ 9 _6 +
F TC N um Sl o t_ 19 _ 2 + F TC N um Sl o t_ 3 8_ 4 + F TC N um S lo t_ 7 6_ 8 +
F TC N um Sl o t_ 15 3 _6 + FT C Nu mS l ot _ 30 7_ 2 + F T CN u mS lo t _6 14 _ 4 +
F TC N um Sl o t_ 92 1 _6 + FT C Nu mS l ot _ 12 28 _ 8 + F TC N um Sl o t_ 15 3 6 +
F TC N um Sl o t_ 18 4 3_ 2 + F T CN um S lo t _2 45 7 _6 + FT C Nu mS l ot _3 0 72 ) *
0 .0 0 16 67 )
Notes:
Prospect
Traffic
RLPTxedFTC_BE EVM_RLP_TXED_FTC_BE 1xEV_Sector
Carrier
RLPTxedFTC_CPS EVM_RLP_TXED_FTC_CPS 1xEV_Sector
Carrier
RLPTxedFTC_CS EVM_RLP_TXED_FTC_CS 1xEV_Sector
Carrier
RLPTxedFTC_CV EVM_RLP_TXED_FTC_CV 1xEV_Sector
Carrier
RLPTxedFTC_SMC EVM_RLP_TXED_FTC_SMC 1xEV_Sector
Carrier
Carrier
FTCNumSlot_1536 EVM_FTC_NUM_SLOT_1536 1xEV_Sector
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 RNC R28

Carrier
Carrier
FTCNumSlot_3072 EVM_FTC_NUM_SLOT_3072 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
1xEV-DO Hard Handoff Success Rate Requesting Sector

DO p _H H Su cc _ Re qS e ct = 10 0 .0 * (H a rd HO A tt
HH O ff C on nC l os eP o st T CA Re q H H Of f Co nn C lo se P re T CA Re q -
(H a rd H OF lN o Re sc + H ar dH O Fl No A TR s p + H ar dH O Fl O th er _ Pr eT C A +
Ha r dH O Fl Ot h er _P o st T CA )) / (H a rd H OA tt
HH O ff C on nC l os eP o st T CA Re q H H Of f Co nn C lo se P re T CA Re q )
Notes:
Prospect
Traffic
HardHOAtt HHOFF_ATTMPT_REQ 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 RNC R28
HardHOFlNoResc HHOFF_FAIL_NO_RESOURCE_REQ 1xEV_Sector

Carrier
HardHOFlNoATRsp HHOFF_FAIL_NO_AT_RESP_REQ 1xEV_Sector
Carrier
HardHOFlOther_PreTCA HHOFF_FAIL_OTHER_PRETCA_REQ 1xEV_Sector
Carrier
HardHOFlOther_PostTCA HHOFF_FAIL_OTHER_POSTTCA_REQ 1xEV_Sector
Carrier
HHOffConnClosePostTCAReq HHOFF_CONN_CLOSE_POSTTCA_REQ 1xEV_Sector
Carrier
HHOffConnClosePreTCAReq HHOFF_CONN_CLOSE_PRETCA_REQ 1xEV_Sector
Carrier
1xEV-DO Hard Handoff Success Rate Target Sector

D Op _ HH Su c c_ Tg t Se c t = 1 00 .0 * ( Ha rd H OA tt _ Tg t
H HO f fC on n Cl os e Po s tT CA T ar ge t - HH Of f Co nn C lo s eP re T CA Ta r ge t
( Ha r dH OF l No Re s c_ T gt + Ha rd H OF l No AT R sp _T g t +
H ar d HO Fl O th er _ Pr e TC A_ T gt + Ha r dH OF l Ot he r _P o st TC A _T gt ) ) /
( Ha r dH OA t t_ Tg t HH Of f Co nn C lo s eP os t TC AT a rg e t
H HO f fC on n Cl os e Pr e TC AT a rg et )
Notes:
Prospect Traffic
HardHOAtt_Tgt HHOFF_ATTMPT_TARGET 1xEV_SectorCarrie
r
HardHOFlNoResc_Tgt HHOFF_FAIL_NO_RESOURCE_TARGET 1xEV_SectorCarrie
r
HardHOFlNoATRsp_Tgt HHOFF_FAIL_NO_AT_RESP_TARGET 1xEV_SectorCarrie
r
HardHOFlOther_PreTCA_Tgt HHOFF_FAIL_OTHER_PRETCA_TARGET 1xEV_SectorCarrie
r
HardHOFlOther_PostTCA_T HHOFF_FAIL_OTHER_POSTTCA_TARGET 1xEV_SectorCarrie
gt r
............................................................................................................................................................................................................................................................
Release 28 RNC R28
HHOffConnClosePostTCATar HHOFF_CONN_CLOSE_POSTTCA_TARGET 1xEV_SectorCarrie

get r
HHOffConnClosePreTCATarg HHOFF_CONN_CLOSE_PRETCA_TARGET 1xEV_SectorCarrie
et r
1xEV-DO Hard Handoff Blocking Rate Requesting Sector

DO p _H H Bl k_ R eq Se c t = 1 00 . 0 * ( Ha r dH OA t t
HH O ff C on nC l os eP r eT C AR eq - Ha r dH O At tT C AS en t ) / ( Ha r dH OA t t
HH O ff C on nC l os eP r eT C AR eq )
Notes:
Prospect Traffic
HardHOAttTCASent HHOFF_TCA_SENT_REQ 1xEV_SectorCarrier
HHOffConnClosePreTCAReq HHOFF_CONN_CLOSE_PRETCA_REQ 1xEV_SectorCarrier
1xEV-DO Hard Handoff Blocking Rate Target Sector

DO p _H H Bl k_ T gt Se c t = 1 00 . 0 * ( Ha r dH OA t t_ Tg t -
HH O ff C on nC l os eP r eT C AT ar g et Ha r dH OA t tT CA S en t _T gt ) /
(H a rd H OA tt _ Tg t H HO f fC on n Cl os e Pr e TC AT a rg et )
Notes:
Prospect Traffic
HardHOAtt_Tgt HHOFF_ATTMPT_TARGET 1xEV_SectorCarrie
r
HardHOAttTCASent_Tgt HHOFF_TCA_SENT_TARGET 1xEV_SectorCarrie
r
HHOffConnClosePreTCATarg HHOFF_CONN_CLOSE_PRETCA_TARGET 1xEV_SectorCarrie
et r
............................................................................................................................................................................................................................................................
Release 28 RNC R28
1xEV-DO Hard Handoff RF Failure Rate Requesting Sector

DDOp_HHRFFail_ReqSect = 100.0 * HardHOFlNoATRsp / (HardHOAttTCASent
HHOffConnClosePostTCAReq)
Notes:
Prospect
Traffic
HardHOFlNoATRsp HHOFF_FAIL_NO_AT_RSP_REQ 1xEV_Sector
Carrier
HardHOAttTCASent HHOFF_TCA_SENT_REQ 1xEV_Sector
Carrier
HHOffConnClosePostTCAReq HHOFF_CONN_CLOSE_POSTTCA_REQ 1xEV_Sector
Carrier
1xEV-DO Hard Handoff RF Failure Rate Target Sector

DOp_HHRFFail_TgtSect =100.0 * HardHOFlNoATRsp_Tgt /(HardHOAttTCASent_Tgt
HHOffConnClosePostTCATarget)
Notes:
Prospect
Traffic
HardHOFlNoATRsp_Tgt HHOFF_FAIL_NO_AT_TARGET 1xEV_Sector
Carrier
HardHOAttTCASent_Tgt HHOFF_TCA_SENT_TARGET 1xEV_Sector
Carrier
HHOffConnClosePostTCATarget HHOFF_CONN_CLOSE_POSTTCA_TARGET 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 RNC R28
DO_RLPFwdLUsr_MB = (RLPTXFTC + RLPTxedFTC_BE + RLPTxedFTC_CPS +
RLPTxedFTC_CS + RLPTxedFTC_CV + RLPTxedFTC_SMC) / (1000000.0 *
AvgActCon)
Notes:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
Carrier
Carrierr
AvgActCon AVG_ACTIVE_CONN_PER_SECTOR / 360.0 1xEV_Sector

Carrier
1xEV-DO Soft/Softer Handoff Overhead SBEVM)

DOp_SftSftrHOOverhead_SBEVM = AvgActCon_Peg / (0.36 *
AvgDRCPointedUsers)
Notes:
1. The factor 0.36 in the denominator was incorrectly implemented as 3.6 in R27. Nothing
else needs to be changed for this metric in R28.
............................................................................................................................................................................................................................................................
Release 28 RNC R28
2. Mapping between Prospect names and EVDO Names
Prospect
Traffic
AvgActCon_Peg AVG_ACTIVE_CONN_PER_SECTOR 1xEV_Sector
Carrier
AvgDRCPointedUsers EVM_AVG_DRC_POINTED_USERS 1xEV_Sector
Carrier
1xEV-DO Average Forward Link RLP Data Rate per User SBEVM (kbps)
DOp_FLRLPAvgRateUser_SBEVM = (8.0 /1000.0) * (RLPTxedFTC_BE +
RLPTxedFTC_CPS + RLPTxedFTC_CS + RLPTxedFTC_CV + RLPTxedFTC_SMC) /
(ActiveUsage * 0.001667)
Notes:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
Carrier
ActiveUsage EVM_ACTIVE_USAGE 1xEV_Sector
Carrier

Prospect Traffic Report Entity: IxEV_SectorCarrier and IxEV_Sector
Valid Releases: Cell/FMS R28 and later
............................................................................................................................................................................................................................................................
Release 28 RNC R28

SesSUIntSubUATICmpMsgRcvd + IntraRNCGroupSessTrfrUATICompleteRcvd) /
(SessnSURq + IntSubIdleTrfrAtt + IntraRNCGroupSessTrfrAttempt)
Notes:
1. Mapping between Prospect names and 1xEV-DO Names new in R28
Prospect
Traffic
Carrier
SesSUIntSubUATICmpMsgRcvd SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_R 1xEV_Sector
CVD Carrier
Carrier
SessnSURq SESSION_SETUP_REQ 1xEV_Sector
Carrier
IntraRNCGroupSessTrfrUATIComple INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPL 1xEV_Sector
teRcvd ETE_RCVD Carrier
IntraRNCGroupSessTrfrAttempt INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT 1xEV_Sector
Carrier

DOp_SessAsgnReq = 100.0 * (SessnSUUATIAsgnMsgSent +
SesSUIntSubUATIAsgnMsgSent + IntraRNCGroupSessTrfrUATIAssgnSent) /
(SessnSURq + IntSubIdleTrfrAtt + IntraRNCGroupSessTrfrAttempt)
Notes:
Prospect
Traffic
SessnSUUATIAsgnMsgSent SESS_SETUP_UATI_ASSGNMT_MSG_SENT 1xEV_Sector
Carrier
SesSUIntSubUATIAsgnMsgSent SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 RNC R28
SessnSURq SESSION_SETUP_REQ 1xEV_Sector

Carrier
Carrier
IntraRNCGroupSessTrfrUATIAssgnS INTRA_RNC_GROUP_SESS_TRFR_UATI_ASSGN 1xEV_Sector
ent _SENT Carrier
Carrier
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Obsolete Metrics in R28
Release 28
Obsolete Metrics in R28

............................................................................................................................................................................................................................................................
The following metrics are assigned a field type of OBS (Obsolete) in R28.

PCALC Name: DOp_PageSucc
Traffic Entity: IxEV_AP
1xEV-DO Paging Failure Rate Due to RF Failures

PCALC Name: DOp_RFPageFail

PCALC Name: DOp_EstCall
Traffic Entity: IxEV_Sector, IxEV_SectorCarrier

PCALC Name: DOp_DropCall
Traffic Entity: IxEV_Sector, IxEV_SectorCarrier

PCALC Name: DOp_FastCnctSuc
Fast Connect Success Rate Peg

PCALC Name: DOp_FastCnctSuc_Peg

PCALC Name: DOp_AvgActSess

PCALC Name: DOp_InefCallAttTotal
Traffic Entity: IxEV_SectorCarrier, IxEV_Sector
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Obsolete Metrics in R28
Release 28

PCALC Name: DOp_RFFail
Traffic Entity: IxEV_SectorCarrier
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent New 1xEV-DO Performance Metrics in Prospect
Release 28 R28

............................................................................................................................................................................................................................................................

DO p _I n tr aR N CG rp S es s Tr fr S uc = 10 0 .0 *
In t ra R NC Gr o up Se s sT r fr Su c ce ss / I nt ra R NC Gr o up S es sT r fr At t em pt
Note:
Prospect
Traffic
Carrier
IntraRNCGroupSessTrfrSuccess INTRA_RNC_GROUP_SESS_TRFR_SUCCESS 1xEV_Sector
Carrier
Paging Profile ID BE
Prospect Traffic Report Entity: FMS
DO p _P a ge Ef f _B E = 1 0 0. 0 * ( Pa g eC R Rc vd _ BE / (p a ge s1 b e -
Pa g eA b or tH i gh er P ID _ BE )
Notes:
1. Note that this metric is calculated at the FMS level, but the counts in the equation are
at the IxEV_PageAttempt level. This means that the counts in the numerator are
rolled-up over paging attempts (1 - 8) and OHM. However, the page attempt counts in
the denominator are for Page Attempt 1 only. I.e., these terms are not rolled up over
paging attempts but are rolled up over OHMs
Prospect Traffic
pages1be PAGES (BE; Page attempt 1) IxEV_PageAttempts
PageCRRcvd_BE PAGE_CR_RCVD (BE) IxEV_PageAttempts
............................................................................................................................................................................................................................................................
Release 28 R28
Paging Profile ID CMCS

D Op _ Pa ge E ff _C M CS = 10 0 .0 * Pa g eC RR c vd _C M CS / Pa ge s _C MC S ( P ag e
A tt e mp t 1 )
Notes:
at the IxEV_PageAttempt level. This means that the count in the numerator is rolled-
up over paging attempts (1 8) and OHM. However, the denominator (Pages_BE) is
for Page Attempt 1 only. I.e., the denominator is not rolled up over paging attempts but
is rolled up over OHMs
Prospect Traffic
Pages_CMCS PAGES (CMCS) IxEV_PageAttempts
PageCRRcvd_CMCS PAGE_CR_RCVD (CMCS) IxEV_PageAttempts
Paging Profile ID PTT_CALL_SETUP_SIG

D Op _ Pa ge E ff _P T TC S S = 1 00 .0 * P ag eC R Rc vd _ PT T CS S/ P ag es _ PT T CS S
( Pa g e At t em pt 1)
Notes:
Prospect
Traffic
Pages_PTTCSS PAGES (PTT_CALL_SETUP_SIG) IxEV_PageA
ttempts
PageCRRcvd_PTTCSS PAGE_CR_RCVD (PTT_CALL_SETUP_SIG) IxEV_PageA
ttempts
............................................................................................................................................................................................................................................................
Release 28 R28
Paging Profile ID PTT_INCALL_SIG

DO p _P a ge Ef f _P TT I CS = 10 0 .0 * Pa g eC RR c vd _P T TI C S/ Pa g es _P T TI CS
(P a ge At te m pt 1 )
Notes:
Prospect
Traffic
Pages_PTTICS PAGES (PTT_INCALL_SIG) IxEV_PageA
ttempts
PageCRRcvd_PTTICS PAGE_CR_RCVD (PTT_INCALL_SIG) IxEV_PageA
ttempts
Paging Profile ID PTT_SPEECH_BEARER1

DO p _P a ge Ef f _P TT S B1 = 10 0 .0 * Pa g eC RR c vd _P T TS B 1/ Pa g es _P T TS B1
(P a ge At te m pt 1 )
Notes:
Prospect
Traffic
Pages_PTTSB1 PAGES (PTT_SPEECH_BEARER1) IxEV_PageA
ttempts
............................................................................................................................................................................................................................................................
Release 28 R28
PageCRRcvd_PTTSB1 PAGE_CR_RCVD (PTT_SPEECH_BEARER1) IxEV_PageA

ttempts

D Op _ Pa ge E ff _P T TS B 2 = 1 00 .0 * P ag eC R Rc vd _ PT T SB 2/ P ag es _ PT T SB 2
( Pa g e At t em pt 1)
Notes:
Prospect
Traffic
Pages_PTTSB2 PAGES (PTT_SPEECH_BEARER2) IxEV_PageA
ttempts
ttempts
1xEV-DOReservationOnRequest Success Rate
1xEV-DOReservationOnRequest Success Rate

Prospect Traffic Report Entity: IxEV_SectorCarrier
D Op _ RO RS u cc = 10 0 .0 * RO RA c ce p te d / R OR R ec e iv ed
Notes:
Prospect
Traffic
RORAccepted ROR_ACCEPTED 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
RORReceived ROR_RECEIVED 1xEV_Sector

Carrier

DO p _F L CS Rs r vS uc c = 10 0. 0 * F L Re q Co nv R at eS e t1 S pe ec h Ac ce p t /
FL R eq C on vR a te Se t 1S p ee ch
Prospect
Traffic
FLReqConvRateSet1SpeechAccept FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT 1xEV_Sector
Carrier
FLReqConvRateSet1Speech FL_REQ_CONV_RATE_SET_1_SPEECH 1xEV_Sector
Carrier

DO p _F L CV Rs r vS uc c = 10 0. 0 * F L Re q Co nv V id eo A cc e pt /
FL R eq C on vV i de o
Notes:
Prospect
Traffic
FLReqConvVideoAccept FL_REQ_CONV_VIDEO_ACCEPT 1xEV_Sector
Carrier
FLReqConvVideot FL_REQ_CONV_VIDEO 1xEV_Sector
Carrier
1xEV-DO Forward Link Conversational PTT Speech Reservation Success Rate

............................................................................................................................................................................................................................................................
Release 28 R28
D Op _ FL CP S Rs rv S uc c = 1 0 0. 0 * F L Re sv A dm tC o nv P TT Sp e ec h /
F LR e sv Re q Co nv P TT S pe ec h
Notes:
Prospect
Traffic
FLResvAdmtConvPTTSpeech FL_RESV_ADMT_CONV_PTT_SPEECH 1xEV_Sector
Carrier
FLResvReqConvPTTSpeech FL_RESV_REQ_CONV_PTT_SPEECH 1xEV_Sector
Carrier
1xEV-DO Established Connection Rate Session Setup - Peg

DOp_EstConn_SessSU = 100.0 * ATInitEstablishedConnSess / ATInitConnReqSess
Note:
Prospect
Traffic
ATInitEstablishedConnSess AT_INIT_ESTABLISHED_CONN_SESS 1xEV_Sector
Carrier
ATInitConnReqSess AT_INIT_CONN_REQ_SESS 1xEV_Sector
Carrier
1xEV-DO Established Connection Rate User

D Op _ Es tC o nn _U s er = 10 0 .0 * (A N In it E st ab C on n ec ti o n +
A TI n it Es t ab Co n ne c ti on AT I ni t Es ta b li sh e dC o nn Se s s) /
( AN I ni tC o nR q + A T In it C on Rq - A TI ni t Co nn R eq S es s)
............................................................................................................................................................................................................................................................
Release 28 R28
Note:
Prospect
Traffic
Carrier
Carrier
ATInitEstabConnection AT_INIT_ESTABLISHED_CONN 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
1xEV-DO Connection Blocking Rate User

Prospect Traffic Report Entity: IxEV_Sector
DOp_ConnBlk_User = 100.0 * (ANInitConRq + ATInitConRq ATInitConnReqSess

(TCAANInitConRq + TCAATInitConRq - TCAforATInitConnReqSess)) / (ANInitConRq
+ ATInitConRq ATInitConnReqSess)
Note:
Prospect
Traffic
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
TCAforATInitConnReqSess TCA_FOR_AT_INIT_CONN_REQ_SESS 1xEV_Sector
Carrier
11xEV-DO RF Failure Rate Session Setup

D Op _ RF Fa i l_ Se s sS U = 1 0 0. 0 * ( T CA fo r AT In i tC o nn Re q Se ss
A TI n it Es t ab li s he d Co nn S es s) / T CA fo r AT In i tC o nn Re q Se ss
Note:
Prospect
Traffic
Carrier
ATInitEstablishedConnSesst AT_INIT_ESTABLISHED_CONN_SESS 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
1xEV-DO RF Failure Rate User

DO p _R F Fa il _ Us er = 1 00 .0 * (T C AA N In it C on Rq + T CA AT I ni tC o nR q
TC A fo r AT In i tC on n Re q Se ss (A N In i tE st a bC on n ec t io n +
AT I ni t Es ta b Co nn e ct i on - AT In i tE s ta bl i sh ed C on n Se ss ) ) /
(T C AA N In it C on Rq + T CA AT I ni tC o nR q T C Af or A TI n it Co n nR eq S es s)
Note:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
ATInitEstabConnection AT_INIT_ESTABLISHED_CONN 1xEV_Sector
Carrier
Carrier
1xEV-DO Dropped Reservation Rates

DOp_FLConvSpeechDropReserv = 100.0 * FLConvRateSpeechDroppedBHOverload /

FLReqConvRateSet1SpeechAccept
............................................................................................................................................................................................................................................................
Release 28 R28
Note:
Prospect
Traffic
FLConvRateSpeechDroppedBHOve FL_CONV_RATE_SPEECH_DROPPED_BH_OVERL 1xEV_Sector
rload OAD Carrier
FLReqConvRateSet1SpeechAccept FL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT 1xEV_Sector
Carrier

D Op _ FL Co n vV id e oD r op Re s er v = 1 0 0. 0 *
F LC o nv Vi d eo Dr o pp e dB HO v er lo a d / F LR e qC on v Vi d eo Ac c ep t
Note:
Prospect
Traffic
FLConvVideoDroppedBHOverload FL_CONV_VIDEO_DROPPED_BH_OVERLOAD 1xEV_Sector
Carrier
FLReqConvVideoAccept FL_REQ_CONV_VIDEO_ACCEPT 1xEV_Sector
Carrier
1xEV-DO Forward Link Conversational PTT Speech Dropped Reservation Rate

D Op _ FL Co n vP TT S pc h Dr op R es er v = 10 0. 0 *
F LR e sv Dr p dC on v PT T Sp ch B kh au l Ov l / F L Re sv A dm t Co nv P TT Sp e ec h
Note:
Prospect
Traffic
............................................................................................................................................................................................................................................................
Release 28 R28
FLResvDrpdConvPTTSpchBkhaul FL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_O 1xEV_Sector

Ovl VL Carrier
FLResvAdmtConvPTTSpeech FL_RESV_ADMT_CONV_PTT_SPEECH 1xEV_Sector
Carrier
1xEV-DO Reverse Link Conversational Speech Dropped Reservation Rate

DO p _R L Co nv S pe ec h Dr o pR es e rv = 10 0 .0 *
(R L Co n vR at e Sp ee c hD r op pe d BH Ov e rl o ad +
RL C on v Ra te S pe ec h Dr o pp ed R LR FO l oa d +
RL C on v Ra te S pe ec h Dr o pp ed T PE FQ O lo a d) /
RL R eq C on vR a te Se t 1S p ee ch A cc ep t
Note:
Prospect
Traffic
RLConvRateSpeechDroppedBH RL_CONV_RATE_SPEECH_DROPPED_BH_OVERLO 1xEV_Sector
Overload AD Carrier
RLConvRateSpeechDroppedRL RL_CONV_RATE_SPEECH_DROPPED_RLRF_OLOA 1xEV_Sector
RFOload D Carrier
RLConvRateSpeechDroppedTP RL_CONV_RATE_SPEECH_DROPPED_TPEF_Q_OLO 1xEV_Sector
EFQOload AD Carrier
RLReqConvRateSet1SpeechAcc RL_REQ_CONV_RATE_SET_1_SPEECH_ACCEPT 1xEV_Sector
ept Carrier

DO p _R L Co nv V id eo D ro p Re se r v = 1 00 . 0 *
(R L Co n vV id e oD ro p pe d BH Ov e rl oa d +
RL C on v Vi de o Dr op p ed R LR FO v er lo a d + R LC o nv Vi d eo T PE FQ O ve rl o ad ) /
RL R eq C on vV i de oA c ce p t
............................................................................................................................................................................................................................................................
Release 28 R28
Notes:
Prospect
Traffic
RLConvVideoDroppedBHOverl RL_CONV_VIDEO_DROPPED_BH_OVERLOAD 1xEV_Sector
oad Carrier
RLConvVideoDroppedRLRFOv RL_CONV_VIDEO_DROPPED_RLRF_OVERLOAD 1xEV_Sector
erload Carrier
RLConvVideoTPEFQOverload RL_CONV_VIDEO_TPEF_Q_OVERLOAD 1xEV_Sector
Carrier
RLReqConvVideoAccept RL_REQ_CONV_VIDEO_ACCEPT 1xEV_Sector
Carrier
1xEV-DO Reverse Link Conversational PTT Speech Dropped Reservation Rate

D Op _ RL Co n vP TT S pc h Dr op R es er v = 10 0. 0 *
( RL R es vD r pd Co n vP T TS pc h Bk ha u lO v l +
R LR e sv Dr p dC on v PT T Sp ch R LR FO v l + R L Re sv D rp dC o nv P TT Sp c hT PE F QO vl )
/ R L Re sv A dm tC o nv P TT Sp e ec h
Note:
Prospect
Traffic
RLResvDrpdConvPTTSpchBkhaul RL_RESV_DRPD_CONV_PTT_SPCH_BKHAUL_O 1xEV_Sector
Ovl VL Carrier
RLResvDrpdConvPTTSpchRLRFO RL_RESV_DRPD_CONV_PTT_SPCH_RL_RF_OVL 1xEV_Sector
vl Carrier
RLResvDrpdConvPTTSpchTPEFQ RL_RESV_DRPD_CONV_PTT_SPCH_TP_EF_Q_O 1xEV_Sector
Ovl VL Carrier
RLResvAdmtConvPTTSpeech RL_RESV_ADMT_CONV_PTT_SPEECH 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

DO p _F L Da ta R eT x_ N AK _ SB EV M = 1 0 0. 0 * ( R LP Re t xe d FT C_ B E +
RL P Re t xe dF T C_ SM C ) / ( RL P Tx ed F TC _ BE + RL PT x ed F TC _S M C)
Note:
Prospect
Traffic
RLPRetxedFTC_BE EVM_RLP_RETXED_FTC_BE 1xEV_Sector
Carrier
RLPRetxedFTC_SMC EVM_RLP_RETXED_FTC_SMC 1xEV_Sector
Carrier
Carrier
Carrier
1xEV-DO Forward Link Data Re-Transmission Rate (DARQ) - SBEVM

DO p _F L Da ta R eT x_ D AR Q _S BE V M = 1 00 . 0 * ( RL PR e tx e dF TC D AR Q_ B E +
RL P Re t xe dF T CD AR Q _C P S + R LP Re t xe d FT CD A RQ _C S +
RL P Re t xe dF T CD AR Q _C V + RL PR e tx ed F TC D AR Q_ S MC ) / ( R LP T xe dF T C_ BE +
RL P Tx e dF TC _ CP S + R L PT xe d FT C_ C S + R LP T xe dF T C_ C V +
RL P Tx e dF TC _ SM C)
Note:
Prospect
Traffic
RLPRetxedFTCDARQ_BE EVM_RLP_RETXED_FTC_DARQ_BE 1xEV_Sector
Carrier
RLPRetxedFTCDARQ_CPS EVM_RLP_RETXED_FTC_DARQ_CPS 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
RLPRetxedFTCDARQ_CS EVM_RLP_RETXED_FTC_DARQ_CS 1xEV_Sector

Carrier
RLPRetxedFTCDARQ_CV EVM_RLP_RETXED_FTC_DARQ_CV 1xEV_Sector
Carrier
RLPRetxedFTCDARQ_SMC EVM_RLP_RETXED_FTC_DARQ_SMC 1xEV_Sector
Carrier
Carrier
RLPTxedFTC_CPS EVM_RLP_TXED_FTC_CDPS 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
1xEV-DO Forward Link Physical Layer Composite Data Transmitted (MB)

D O_ C om pF L Ph ys L ay e rD at a Xm it = ( (1 02 4 .0 / 8. 0) * (F w dP k ts 38 k bp s +
F wd P kt s7 6 kb ps + F wd Pk t s1 53 k bp s + F w dP kt s 30 7 kb ps +
F wd P kt s6 1 4k bp s + Fw dP k ts 30 7 Lk b ps + Fw dP k ts 6 14 Lk b ps +
F wd P kt s1 2 28 kb p s + F wd P kt s9 2 1k b ps + Fw dP k ts 1 84 3k b ps +
F wd P kt s1 2 28 Lk b ps + Fw d Pk ts 2 45 7 kb ps ) + F T CT o tB yt e s_ 4_ 8 +
F TC T ot By t es _3 0 72 ) / 1 0 00 00 0 .0
Note:
Prospect
Traffic
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
FwdPkts307Lkbps EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
FwdPkts2457kbps EVM_FWD_PACKETS_2457_6 _TOTAL_COUNT 1xEV_Sector
Carrier
Carrier
FTCTotBytes_1536 EVM_FTC_TOT_BYTES_1536 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
1xEV-DO Composite Average Forward Link Physical Layer Data Rate (kbps)
D O_ C om pF L Ph ys L ay e rD at a Ra te = ( (1 02 4 .0 * (F w dP kt s 38 kb p s +
F wd P kt s7 6 kb ps + F wd Pk t s1 53 k bp s + F w dP kt s 30 7 kb ps +
F wd P kt s6 1 4k bp s + Fw dP k ts 30 7 Lk b ps + Fw dP k ts 6 14 Lk b ps +
F wd P kt s1 2 28 kb p s + F wd P kt s9 2 1k b ps + Fw dP k ts 1 84 3k b ps +
F wd P kt s1 2 28 Lk b ps + F wd P kt s2 4 57 k bp s) + 8 .0 * ( F TC To t By te s _4 _ 8 +
F TC T ot By t es _3 0 72 ) ) / ( Pc nt S lt s Us rT r f * 0 .2 1 6 * 0 .1 66 7 )
Note:
Prospect
Traffic
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
FwdPkts2457kbps EVM_FWD_PACKETS_2457_6 _TOTAL_COUNT 1xEV_Sector
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
1xEV-DO Composite Average Reverse Link Physical Layer Data Rate (kbps)
DO _ Co m pR LP h ys La y Av g Ra te = 0 .0 01 * ( 2 56 .0 * R ev O ut Lo o pP CF r Ct 9 6 +
51 2 .0 * Re v Ou tL o op P CF rC t 19 2 + 1 0 24 .0 * Re v Ou t Lo op P CF rC t 38 4 +
20 4 8. 0 * Re v Ou tL o op P CF rC t 76 8 + 40 9 6. 0 * Re vO u tL o op PC F rC t1 5 36 +
2 5 6. 0 * R e vP ac k et s _2 56 _ To ta l Co u nt + 51 2. 0 *
Re v Pa c ke ts _ 51 2_ T ot a lC ou n t + 7 68 . 0 * R ev P ac ke t s_ 76 8 _T o ta lC o un t
+ 1 02 4 .0 * Re vP a ck e ts _1 0 24 _T o ta l Co un t + 1 5 36 . 0 *
Re v Pa c ke ts _ 15 36 _ To t al Co u nt + 20 4 8. 0 *
Re v Pa c ke ts _ 81 92 _ To t al Co u nt + 12 2 88 .0 *
Re v Pa c ke ts _ 12 28 8 _T o ta lC o un t) / ( 0. 0 26 6 * ( R ev Ou t Lo o pP CF r Ct 96 +
Re v Ou t Lo op P CF rC t 19 2 + R e vO ut L oo p PC Fr C t3 84 +
Re v Ou t Lo op P CF rC t 76 8 + R e vO ut L oo p PC Fr C t1 53 6 ) + 0 .0 0 66 7 *
(N u mS u bp kt s RL _1 2 8 + Nu mS u bp kt s RL _ 25 6 + N um S ub p kt sR L _5 12 +
Nu m Su b pk ts R L_ 76 8 + Nu mS u bp kt s RL _ 10 24 + Nu m Su b pk ts R L_ 15 3 6 +
Nu m Su b pk ts R L_ 61 4 4 + N um S ub pk t sR L _8 19 2 + N u mS u bp kt s RL _1 2 28 8) )
Note:
Prospect
Traffic
RevOutLoopPCFrCt96 REV_OUTER_LOOP_PC_FRAME_COUNT_96KBP 1xEV_Sector
S Carrier
RevOutLoopPCFrCt192 REV_OUTER_LOOP_PC_FRAME_COUNT_192KB 1xEV_Sector
PS Carrier
PS Carrier
PS Carrier
PS Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
Carrier
Carrier
1xEV-DO RLP Reverse Link Composite Data Volume (MB)

DO _ RL P RL Co m pD at a Vo l = ( 2 56 .0 * R ev Ou t Lo op P CF r Ct 96 + 51 2 .0 *
Re v Ou t Lo op P CF rC t 19 2 + 1 02 4. 0 * R ev Ou t Lo o pP CF r Ct 38 4 + 2 04 8 .0 *
Re v Ou t Lo op P CF rC t 76 8 + 4 09 6. 0 * R ev Ou t Lo o pP CF r Ct 15 3 6 + 12 8 .0 *
Re v Pa c ke ts _ 12 8_ T ot a lC ou n t + 2 56 . 0 * R ev P ac ke t s_ 25 6 _T o ta lC o un t
+ 5 12 . 0 * R ev Pa c ke t s_ 51 2 _T ot a lC o un t + 7 68 . 0 *
Re v Pa c ke ts _ 76 8_ T ot a lC ou n t + 1 02 4 .0 *
Re v Pa c ke ts _ 81 92 _ To t al Co u nt + 12 2 88 .0 *
Re v Pa c ke ts _ 12 28 8 _T o ta lC o un t) / ( 80 00 0 00 .0 )
Note:
Prospect
Traffic
S Carrier
PS Carrier
PS Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

PS Carrier
PS Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
1xEV-DO RLP Forward Link Composite Data Volume (MB)

D O_ R LP FL C om pD a ta V ol = (R LP T XF T C + R LP Tx e dF T C_ BE +
R LP T xe dF T C_ CP S + RL PT x ed FT C _C S + R L PT xe d FT C _C V +
R LP T xe dF T C_ SM C ) / 1 00 0 00 0
............................................................................................................................................................................................................................................................
Release 28 R28
Note:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
1xEV-DO RLP Forward Data Link Composite Data Rate (kbps)

D O_ R LP FL C om pD a ta R at e = ( 8 .0 /1 0 00 . ) * ( RL P TX FT C + RL P Tx ed F TC _B E
+ R L PT xe d FT C_ C PS + RL P Tx ed F TC _ CS + RL PT x ed F TC _C V +
R LP T xe dF T C_ SM C ) / ( Pc n tS lt s Us r Tr f * 0 .0 2 16 * 0. 0 01 66 7 )
Note:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS 1xEV_Sector
Carrier
1xEV-DO Composite Reverse Link RLP Data Throughput (kbps)

D O_ C om pR L RL PT h ru p ut = (8 .0 / 1 00 0. 0 ) * R LP R XR TC / (0 . 02 6 6 *
( Re v Ou tL o op PC F rC t 96 + Re vO u tL o op PC F rC t1 9 2 +
R ev O ut Lo o pP CF r Ct 3 84 + Re vO u tL o op PC F rC t7 6 8 +
R ev O ut Lo o pP CF r Ct 1 53 6) + 0. 0 06 6 7 * ( Nu mS u bp k ts RL _ 12 8 +
N um S ub pk t sR L_ 2 56 + Nu m Su bp k ts R L_ 51 2 + N u mS u bp kt s RL _7 6 8 +
N um S ub pk t sR L_ 1 02 4 + N u mS ub p kt s RL _1 5 36 + Nu m Su bp k ts RL _ 20 4 8 +
N um S ub pk t sR L_ 3 07 2 + N u mS ub p kt s RL _4 0 96 + Nu m Su bp k ts RL _ 61 4 4 +
N um S ub pk t sR L_ 8 19 2 + N u mS ub p kt s RL _1 2 28 8) )
............................................................................................................................................................................................................................................................
Release 28 R28
Note:
Prospect
Traffic
RLPRXRTC RLP_RXED_RTC 1xEV_Sector
Carrier
S Carrier
PS Carrier
PS Carrier
PS Carrier
PS Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28

Carrier
Carrier
Carrier
............................................................................................................................................................................................................................................................
Release 28 R28
1xEV-DO Average Active Sessions Per OHM

Prospect Traffic Report Entity: IxEV_OHM
DO _ Av g Ac tS e ss _O H M = A vg A ct iv e Co n nP er O HM / 36 0 .0
Note:
Prospect
Traffic
AvgActiveConnPerOHM AVG_ACTIVE_CONN_PER_OHM IxEV_OHM
1xEV-DO Fast Connect Success Rate- Peg

DOp_FastCnctSuc_Peg = 100.0 * FastConnectEstablishedCalls / FastConnect
Note:
Prospect
Traffic
FastConnect FAST_CONNECT IxEV_OHM
FastConnectEstablishedCalls FAST_CONNECT_ESTABLISHED_CALLS IxEV_OHM
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

system associated with the HDR Cell Site (HCS) and Radio Network Controller (RNC).
No specific performance metrics associated with the PDSN are included in this document.
New metrics:
1xEV-DO Intra-RNC Session Balance Success Rate (p. 17-15)
1xEV-DO Paging Escalation Success Rate (p. 17-47)
1xEV-DO Paging De-Escalation Success Rate (p. 17-48)
1xEV-DO Paging Efficiency by Sectors per Page Attempt (p. 17-48)
1xEV-DO Data Over Signalling Effectiveness (p. 17-49)
1xEV-DO Data Over Signalling Success Rate by Page Attempt (p. 17-50)
1xEV-DO Missed Termination Target of LoLat Packets (p. 17-110)
1xEV-DO Broadcast Registration Success Rate (p. 17-130)
1xEV-DO Service Request Success Rate (p. 17-130)
Revised metrics:
1xEV-DO Connection Blocking Rate (p. 17-30)

1xEV-DO Paging Effectiveness (p. 17-44)
1xEV-DO FL Conversational Speech Reservation Success Rate (p. 17-123)
1xEV-DO FL Conversational Speech Dropped Reservation Rate (p. 17-124)
1xEV-DO FL Conversational Video Reservation Success Rate (p. 17-125)
1xEV-DO FL Conversational Video Dropped Reservation Rate (p. 17-125)
1xEV-DO FL Conversational PTT Speech Reservation Success Rate (p. 17-126)
............................................................................................................................................................................................................................................................
1xEV-DO FL Conversational PTT Speech Dropped Reservation Rate (p. 17-127)

1xEV-DO RL Conversational Speech Dropped Reservation Rate (p. 17-127)
1xEV-DO RL Conversational Video Dropped Reservation Rate (p. 17-128)
1xEV-DO RL Conversational PTT Speech Dropped Reservation Rate (p. 17-129)
Revised Peg Counts Descriptions:
1xEV-DO Session Setup Success Rate (p. 17-6)

1xEV-DO Session Assignment to Request Rate (p. 17-7)
1xEV-DO Inter-Subnet Idle Transfer Success Rate (p. 17-9)
1xEV-DO R-P Connection Success Rate (p. 17-18)

1xEV-DO Intra-RNC Session Balance Success Rate
2. Air Interface
a. Connection Setup Metrics
............................................................................................................................................................................................................................................................

1xEV-DO Paging Success Rate by Page Attempt
1xEV-DO Paging Escalation Success Rate
1xEV-DO Paging De-Escalation Success Rate
1xEV-DO Paging Efficiency by Sectors per Page Attempt
1xEV-DO Data Over Signalling Effectiveness
1xEV-DO Data Over Signalling Success Rate by Page Attempt
b. Connection Drop Metrics
c. Handoff Metrics
d. Data Transmission Metrics
1xEV-DO Total Forward Link Physical Layer Data Transmitted -
SBEVM(MB)
1xEV-DO Composite Forward Link Physical Layer Data Transmitted
............................................................................................................................................................................................................................................................
(MB)
1xEV-DO Average Forward Link Physical Layer Date Rate - SBEVM
(kbps)
1xEV-DO Average Forward Link RLP Data Rate per User - SBEVM
(kbps)
1xEV-DO Average Reverse Link Physical Layer Data Volume - EVM
(MB)
1xEV-DO Average Reverse Link Physical Layer Data Volume with
SBEVM (MB)
1xEV-DO Average Reverse Link Physical Layer Data Rate with SBEVM
(kbps)
e. Error Statistics
1xEV-DO Missed Termination Target of LoLat Packets
f. Power Control
1xEV-DO Average Reverse Link Power Control Setpoint - 9.6 kbps -
EVM
EVM
EVM
EVM
EVM
1xEV-DO Average Reverse Link Power Control Setpoint - 128 bits -
............................................................................................................................................................................................................................................................
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
g. Capacity Management Metrics
3. Quality of Service (QoS) Metrics
1xEV-DO Broadcast Registration Success Rate
1xEV-DO Service Request Success Rate
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
group transfers.
Formula

INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD
------------------------------------------------------------------------------------------------X 100
SESSION_SETUP_REQ + INT_SUBNET_IDL_TRFR_ATTMPT +
Count Definitions

UATI request message for new & prior session setups)
SESS_SETUP_UATI_COMPLETE_MSG_RCVD = Session Set Up - UATI Complete
Message Received (new & prior sessions). Pegged when the AT
acknowledges a UATI assignment message sent by the AN in response to a
............................................................................................................................................................................................................................................................
UATI request.
When FID-12458.0 is enabled (Intra-RNC UATI Session Resource Balancing Enable
parameter is set to yes) and Control OHM is transferred, this count is
pegged by the new control OHM against the sector-carrier where the UATI
Request message is received.
SESS_SETUP_ISBNT_UATI_COMPLETE_MSG_RCVD = Session Set Up - UATI
Complete Message Received (assign first & color code).
INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD = This count is
incremented each time a UATI Complete is received or any access channel
packet received with just assigned UATI for a session transfer within an
RNC Group.
INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT = This count is incremented for each
Route Update message received with UATI on the access channel from an
AT with its serving AP in a different RNC from the last seen RNC within
the same RNC Group.
INT_SUBNET_IDL_TRFR_ATTMPT = This count is incremented for each attempt to
transfer a dormant data session between subnets using a method other than
the Prior Session method and is the total of all such idle transfer attempts
for the HDR Cell sector-carrier that received the UATIRequest. This count
is used to measure idle transfer activity. This count should be pegged when
an A13-Session Information Request is generated in the target AN,
omitting the number of such requests that are associated with the Prior
Session method. Note that if the A13 message is repeated, the count is only
pegged once.
With implementation of 12456.0, this count shall exclude the session transfer for load

............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------------X 100
Count Definitions

INT_SUBNET_IDL_TRFR_ATTMPT = Inter-subnet idle transfer attempts (assign first &
color code)
SESS_SETUP_UATI_ASSGNMT_MSG_SENT = Session Set Up - UATI Assignment
Message Sent to AT upon receipt of a UATI request message (new & prior
sessions)
SESS_SETUP_ISBNT_UATI_ASSGN_MSG_SENT = Session Set Up - UATI
Assignment Message Sent (assign first & color code)
INTRA_RNC_GROUP_SESS_TRFR_UATI_ASSGN_SENT = This count is
incremented each time a UATI assignment is sent for a session transfer
within an RNC Group.
............................................................................................................................................................................................................................................................
the same RNC Group.

connections.
Formula
DO Avg Active Sessions = ---------------------------------------------------360
Count Definitions
approximate.

the user is in a terminally bad environment (RF wise or an unreachable subnet), the idle
intervention.
if it was used to access the network while in a dormant state right after the inter-subnet
............................................................................................................................................................................................................................................................
idle
handoff trigger. Hence, a relatively high rate of inter-RNC idle handoff failures may not
be that egregious.
packet data soft handoffs in the Alcatel-Lucent 2G/3G1x product. The inter-subnet idle
Formula

------------------------------------------------------------------------------------------------- X100
............................................................................................................................................................................................................................................................
Count Definitions
INT_SUBNET_IDL_TRFR_ATTMT = This count is incremented for each attempt to

for the HDR Cell sector-carrier that received the UATIRequest.
This count is used to measure idle transfer activity. This count should be pegged when an
A13-Session Information Request is generated in the target AN, omitting
the number of such requests that are associated with the Prior Session
method. Note that if the A13 message is repeated, the count is only pegged
once.
Beginning in R28 this count will exclude the session transfer for load balancing between
RNC members within a RNC Group.
INT_SUBNET_IDL_TRFR_PRIOR_SES_ATTEMPTS = This is the total number of
inter-subnet or inter-RNC idle transfer attempts pegged on the new RNC
(target RNC) for the prior session method. The count is pegged when the
target RNC receives a UATI Request message that contains a RATI
assigned by a different RNC.
IBNT_IDL_TRFR_FAIL_NO_RSP_PRV_SBNET = This count is incremented for each
idle transfer attempt using the Color Code Method or the Assign First
Method that failed because the previous subnet did not respond and is the
total of all such idle transfer failures for the HDR Cell sector-carrier. This
count is used to measure idle transfer failures because the old subnet did
not respond to the transfer request. The count should be pegged after both
request attempts have failed.
ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN = This is the number of inter-
RNC idle handoff failures that occur because the PCF on the new RNC
could not establish an A11 (also known as R-P) connection with the
original PDSN. In essence, a new UATI is assigned successfully but the
connection to the PDSN failed subsequently.
............................................................................................................................................................................................................................................................

INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON = As with other failures for
connection and soft/er handoff failures, this accounts for all inter-RNC idle
handoff attempts that failed for reasons not accounted for by the other
specific failure counts. One scenario where this is seen quite often is the
ping pong scenario. When RNC2 times out waiting for the UATI Complete
message in response to the UATI Assignment message because the AT has
moved to a different RNC (RNC1 or RNC3), it declares it as an Other
failure. Of course, the timeout may also happen due to poor RF conditions
or if RNC2 did not send the UATI Assignment message with proper
message sequence number (often is the case with the Assign First method
where RNC has to guess a sequence number since it has not yet
communicated with the old RNC and has no way of knowing the last
sequence number used to communicate with the AT). This count may also
reflect blocking where the target RNC has no more spare UATIs to assign
to the requesting AT.
Beginning in R28, this count shall exclude the session transfer for load balancing between
ISBNT_IDL_TRFR_FAIL_SRC_ IP_ADR_NT_FOUND = This count is pegged when,
as the name suggests, the PCF A11 IP address of the old RNC is not
provisioned on the new RNC. The problem is applicable only for the Color
Code method of the inter-RNC Idle handoff, which requires the new RNC
to perform a look up of old RNCs IP address in a locally stored mapping
table. The lookup is performed using the color code retrieved from the old
UATI sent by the AT as part of the UATI Request message. If the Assign
First method is used instead, the AN first assigns the UATI to the AT and as
part of the UATI Assignment message, instructs the AT to directly report
back the old RNCs PCF A11 address. Using this information, the new
RNC then attempts to initiate the session transfer from the old RNC. In
this case, no lookup table is needed at the new RNC, and hence this type of
failure does not apply in case of the Assign First method.
Another scenario where this count may get pegged for either the Assign First or Color
Code method is when the PDSN's IP address reported in the A13 Session
Information Response message by the source RNC is invalid (i.e.,
............................................................................................................................................................................................................................................................
255.255.255.255 or NULL).
ISBNT_IDL_TRFR_FAIL_RJCT_MSG_RCVD = This failure is pegged when the new
RNC receives a A13 Reject message from the old RNC in response to a
session transfer request. One scenario where this may occur is when the AT
has gone back to the old RNC (call it RNC 1) or a third RNC (call it RNC
3) before it could send a UATI Complete to the new RNC (call it RNC 2).
In this case, the new RNC (RNC 2) does not yet consider itself to be in
control of ATs session and hence, would reject the subsequent session
transfer request (from RNC1 or RNC3 in this rapid handoff scenario).
ISBNT_IDL_TRFR_FAIL_PRIOR_SES_NO_RSP = Number of Inter Subnet Idle
Transfer failures due to no response from the previous subnet using the
Prior Sessions method.
INT_SUBNET_IDL_TRFR_PRIOR_SES_BAD_REQ = Number of Inter Subnet Idle
Transfer failures due to a failure to find the source AN because of
insufficient information in the Configuration Request message using the

in different RNCs within the same RNC group.The peg counts are defined on a
sectorcarrier
basis.
Formula

---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
with PDSN.

high.
Formula

--------------------------------------------------------------------- X 100
Count Definitions

attempts.

session setup.
............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------------------------------------- X 100
CONFIG_NEGO
Count Definitions
place.

This metric provides the success rate of intra-RNC session setups where the originating
OHM and the target OHM are different. If a UATI session setup request comes into an
OHM and the session balance threshold was exceeded, then the OHM will attempt to
transfer the session setup request to another OHM within the same RNC. This may occur
for both new session requests and idle transfer scenarios.
The peg counts are defined on a per OHM basis. This metric is new in R29.
Formula
DO Intra-RNC Session Balance Success Rate (%) =

SESS_BAL_SUCCESS_INTRA_RNC_ORIG_OHM
---------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
SESS_BAL_REQ_INTRA_RNC_ORIG_OHM
Count Definitions
SESS_BAL_SUCCESS_INTRA_RNC_ORIG_OHM = This count measures the total

number of successful session balances during the SM collection interval at
the originating OHM because the Intra-RNC UATI Session Balance
Threshold was exceeded. This count includes new session request and idle
transfer scenarios.The session balance is considered successful when the
originating OHM receives confirmation message from the target OHM
indicating the session balance request has been accepted by the target
OHM.
SESS_BAL_REQ_INTRA_RNC_ORIG_OHM = This count measures the total number
of UATI session balance requests sent to another OHM within the same
RNC during the SM collection interval at the originating OHM because the
Intra-RNC UATI Session Balance Threshold was exceeded. This count
includes new session request and idle transfer scenarios. If a session OHM
balance request is rejected by a target OHM, the requesting OHM may
retry to transfer the session to another target OHM. In this scenario the
count is incremented only once.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
This section deals with connection establishment metrics from the PCF perspective. One
is the PCF reactivation performed by the PCF when it receives data from the PDSN for a

Formula

------------------------------------------------------------------------------ X 100
Count Definitions
end user.
............................................................................................................................................................................................................................................................

PDSN.

on the R-P link.
the PDSN. The A11 link is really a protocol consisting of a series of signalling messages
handoff.
failures.
Formula

-------------------------------------------------------- X100
RP_CONN_ATTMPTS
Count Definitions
RP_CONN_ATTMPTS= Total number of attempts made by the AN to setup an A11

connection with the PDSN based on requests from the AT. Basically, any
PPP packet from the AT that requires transmission to the PDSN for which
an A10 link does not exist results in a R-P connection attempt.
Furthermore, an attempt to transfer an existing R-P session between PCFs
on the source and target RNCs as part of an inter-RNC Idle handoff will
also increment this peg. Any reactivations from dormancy, whether AT or
AN initiated, are not included in the count.
............................................................................................................................................................................................................................................................
The count does not include R-P connection attempts for Broadcast/Multicast Service
(BCMCS).
RP_CONN_FAIL= Total number of attempts to establish a R-P connection that fail. The
failure could either be due to a reject message from the PDSN, or a
response timeout (PDSN not reachable due to addressing error, PDSN not
in service).
(BCMCS).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

3G1X.
for a Connection.
beginning with R27.
metric, DO Established Connection Rate - Peg should now be used.
Formula
............................................................................................................................................................................................................................................................
--------------------------------------------------------------------------------------------------X 100
Count Definitions
AN_INIT_CONN_REQ =
Connection Request.
AT_INIT_CONN_REQ =
............................................................................................................................................................................................................................................................
Connection Request.
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD=
connection request.
attribute set.
AT_INIT_BUNDLED_CONN_ATTEMPT_FAILURE =
This count is incremented when a Connection Request bundled with a
ReservationOnRequest (RoR) is rejected due to the RoR rejection. The
specific reason the RoR rejection is kept with the RoR failure counts. All the failure
counts below are pegged as AT or AN Initiated depending on
whether the corresponding Connection Request message was received with
AT or AN Initiated attribute set.
receiving the TCC.
............................................................................................................................................................................................................................................................
sector.
This is a catch-all forremaining connection setup failure scenarios that
occur after sending TCA. The reasonsmay include internal call processing
errors, time outs, messagebuild or send errors, blocking due to system
bottlenecks, etc.AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD =
receiving the TCC.
............................................................................................................................................................................................................................................................

sector.
errors, time outs, message build or senderrors, blocking due to system
bottlenecks, etc.

3G1X.
............................................................................................................................................................................................................................................................

rate.
level.
Formula

---------------------------------------------------------------------------------------------------X 100
Count Definitions
channel.)
channel.)
............................................................................................................................................................................................................................................................

connection request.
AN_INIT_CONN_REQ =

This metric gives percentage of successful connections relative to connection requeests
for
requests initiated for the transmission of user data.The peg counts are defined on a
sectorcarrier
basis and are pegged at the sector-carrier that received the connection request.
Formula

---------------------------------------------------------------------------------------------------X 100
............................................................................................................................................................................................................................................................
Count Definitions
established

aggregated to the sector level. It cannot be used at the sector-carrier level because the
cross
Formula

----------------------------------------------------------------------------------------------------X 100
............................................................................................................................................................................................................................................................
Count Definitions
channel.)
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
established

the Suspend Timer is still running, i.e., before the AT goes into the Sleep mode. It does not
involve the traditional Page/Connection Request sequence; rather the AN revives a
............................................................................................................................................................................................................................................................
dormant connection by directly sending a TCA to the AT. This strategy results in an
not affected by load balancing or cross-carrier assignments.
R26. The peg counts are defined on a per OHM basis (changed from per AP in R28) and
can be rolled up to the RNC or SN level.
metric, DO Fast Connect Success Rate - Peg should now be used.
Formula

FAST_CONNECT_FAIL_RL_NOT_ACQ - FAST_CONNECT_FAIL_NO_RSC)
---------------------------------------------------------------------------------------------------- X 100
(FAST_CONNECT)
Count Definitions
FAST_CONNECT =
failures.
preamble..
FAST_CONNECT_FAIL_RL_NOT_ACQ =
This count is pegged when the AN is not able to send an Allocate Traffic
............................................................................................................................................................................................................................................................
no resources available to establish a traffic channel.

level.
Formula

---------------------------------------------------------------------------------------------------- X 100
FAST_CONNECT
Count Definitions
channel).
FAST_CONNECT =

messaging failure.
............................................................................................................................................................................................................................................................
The formula is revised in R29 to remove the session close sessions transfer aborted count.
This change is applicable to R28.
Formula
--------------------------------------------------------------------------------------------------- X 100
Count Definitions
TCA_FOR_AN_INIT_CONN_REQ = Traffic Channel Assignments sent by the AN on

this sector-carrier in response to AN-Initiated Connection Requests either
received and served on this sector-carrier (same sector-carrier assignment)
or received on another sector-carrier and served on this sector-carrier (cross
sector-carrier assignment).
TCA_FOR_AT_INIT_CONN_REQ = Traffic Channel Assignments sent by the AN on
this sector-carrier in response to AT-Initiated Connection Requests either
CROSS_CARR_ATTMPT_RCVD_TCA_SENT = Traffic Channel Assignments sent by
the AN on this sector-carrier in response to a connection request received
............................................................................................................................................................................................................................................................
on another sector-carrier. It is pegged against the strongest sector-carrier

selected for traffic channel allocation by the load balancing algorithm
CROSS_CARR_ATTMPT_SENT_TCA_SENT = Traffic Channel Assignments sent by
the AN on another sector-carrier in response to a connection request
received on this sector-carrier. It is pegged against the sector-carrier that
received the connection request.
AN_INIT_CONN_REQ = AN-Initiated Connection Requests received on this
sectorcarrier
AT_INIT_CONN_REQ = AN-Initiated Connection Requests received on this
sectorcarrier
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT = Number of AN-Initiated
connection requests received on this sector-carrier served by a different
sector-carrier
AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD = Number of AN-Initiated
connection requests received on a different sector-carrier but served by this
sector-carrier
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SENT = Number of AN-Initiated
sector-carrier
AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RCVD = Number of AN-Initiated
sector-carrier
this sector-carrier in response to AN-Initiated Connection Requests
received on this sector-carrier
this sector-carrier in response to AT-Initiated Connection Requests received
on this sector-carrier

............................................................................................................................................................................................................................................................
effective with R26.
Formula

-----------------------------------------------------------------------------------------------------X100
Count Definitions

messaging failure.
............................................................................................................................................................................................................................................................

cross
Formula

-------------------------------------------------------------------------------------------------- X 100
Count Definitions
assignment).
assignment).
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
session setup
............................................................................................................................................................................................................................................................

This metric provides the percentage of connection attempts (both AN-initiated and
ATinitiated)
that failed. It is defined as 100 - established connection rate (see section 4.2.1.1).
releases.
Formula
Count Definitions

ATinitiated)
that failed. It is defined as 100 - established connection rate - peg (see section
Formula
Count definitions
There are no peg counts explicitly used in this metric. See section 1xEV-DO
Established Connection Rate - User - Peg (%) (p. 17-27) for the counts included in the
established connection rate - peg metric.

Largely, the failures can be broken down into RF failures or blocking. The RF Failure rate
............................................................................................................................................................................................................................................................
for Connections includes connection attempt failures due to reverse link not acquired and
No TCC received from the AT. Both these failures occur after the AN has sent the TCA. In
addition, another peg count, other failures - post-TCA is included in the formula to
account for post-TCA failure not specifically pegged. Basically, the rf failure rate means
either the AT or the AN did not have sufficient signal strength to receive signalling and/or
actual traffic channel assignment packets leading up to the connection setup failure.
replaces the separate metrics used in prior releases. The formula is revised is R26 to
cross-connects.
metric, DO RF Failure Rate - Peg should now be used.
Formula
(CROSS_CARR_ATTMPT_SENT_TCA_SENT) -
------------------------------------------------------------------------------------------) X 100
Count definitions
............................................................................................................................................................................................................................................................

response to AN-Initiated Connection Requests received on this sectorcarrier
response to AT-Initiated Connection Requests received on this sectorcarrier
CROSS_CARR_ATTMPT_SENT_TCA_SENT=
connection request.
attribute set.
receiving the TCC.
............................................................................................................................................................................................................................................................
This is a catch-all forremaining failure reasons that prevent a successful
connection setup that occur aftersending TCA. The reasons may include
internal call processing errors, time outs, messagebuild or send errors,
reverse link by sending RTC_Ack message, following which it waits for the
Traffic Channel Complete (TCC) message from the AT. If TCC does not
arrive within a specific period, AN declares a connection attempt failure
and pegs this count on the Connection Request receiving sector. The failure
could be due to AT not receiving the RTC_Ack message or AN not
receiving the TCC.
This is a catch-all for remainingfailure reasons that prevent a successful
internal call processing errors, time outs, message build or senderrors,

detailed formula in the above metric 1xEV-DO RF Failure Rate (p. 17-35) but it is
recommended
............................................................................................................................................................................................................................................................
Formula

------------------------------------------------------------------------------------------------- X 100
Count definitions
............................................................................................................................................................................................................................................................

connection request.

Formula

------------------------------------------------------------------------------------------------- X 100
Count definitions
............................................................................................................................................................................................................................................................

established.

cross
Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
............................................................................................................................................................................................................................................................

established

received
............................................................................................................................................................................................................................................................
received

This metric becomes obsolete in R28 and is replaced with a new 1xEV-DO Paging
Effectiveness (p. 17-44)
Formula

(1 - ---------------------------------------------------------------------------------------------) X 100
Count Definitions
PAGE_ATTEMPTS =
............................................................................................................................................................................................................................................................
errors.

AT being paged. The peg counts are defined on a per AP basis. This metric is effective
beginning with R25.
This metric becomes obsolete in R28.
Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
PAGE_ATTEMPTS =
Number of page attempts sent
Number of page times the AN sends a page to an AT and receives an ATinitiated
connection rrequest before receiving a page response.

of Service (QoS). In addition to the simple paging process used before, there are now up
to 8 configurable page attempts per pageable profile ID for QoS. The paging process
............................................................................................................................................................................................................................................................
ID.
For the purposes of the metric, effectiveness is 'defined' as the number of successful pages
divided by the number of unique page attempts. Unique page attempts is measured by the
number of page attempt number 1, since subsequent page attempts (2 though 8) are simply
repeating the initial page.
The effectiveness metric could be viewed on a per OHM basis since the peg counts are
collected on the same OHM. However, we need to sum over the RNC Group since that is
where the paging strategy is defined. With the introduction of Data over Signalling in R29
the formula is changed to represent an overall paging and DoS effectiveness (overall
delivery effectiveness). If DoS fails, the system may then revert to regular paging to locate
the AT, set up a traffic channel and deliver the packets. In that case page attempt #2 would
be the first page attempt count to be pegged. So, the DoS counts must be included in order
to provide an overall effectiveness of packet delivery based on uniques page attempts.
This revision to the formula is effective with R29.
Formula

{SUM over OHMS in RNC Group [SUM over page attempts 1 through 8]
(PAGE_CR_RCVD + MT_DOS_SUCCESS)}
--------------------------------------------------------------------------------------------------- X 100
(SUM over OHMS in RNC Group (PAGES for page attempt 1 + MT_DOS_ATTEMPTS
for page attempt 1 - PAGE_ABORT_HIGHER_PID))
Count Definitions
PAGE_CR_RCVD = This count is incremented when a connection request is received

while waiting for a response to the Kth Paging attempt. K varies from 1 to
8. Therefore, there are 8 counts, one for each value of K. Note that if the
pegging. This count is reported per OHM-Profile ID-page attempt. This
............................................................................................................................................................................................................................................................
count, in conjunction with the number of pages or connection requests

received, is used to monitor the effectiveness and efficiency of each page
attempt in the Paging sequence. This information can be used to optimize
the paging strategy setting.
PAGES = This count is incremented when a page is attempted for a given attempt K
is reported per OHM-Profile ID-page attempt.
MT_DOS_SUCCESS = This count is incremented each time DOS was successfully used
to deliver the message to the AT for the Kth Paging attempt within the QoS
paging sequence. K varies from 1 to 8. Therefore, there are 8 counts, one
for each value of K. Pegging of this count is equivalent to pegging the CR
count associated with the Kth attempt within the QoS paging sequence. In
either case, the Kth attempt of the paging sequence was successful and
paging is terminated. This count is reported per OHM-Profile ID-Page
Attempt.
MT_DOS_ATTEMPTS = This count is incremented when the AN attempts to deliver a
Mobile Terminated DOS message to an AT in lieu of QoS paging. A page
is attempted for a given attempt K within the Paging Sequence. K varies
from 1 to 8. Therefore, there are 8 counts, one for each value of K. This
count is reported per OHM-Profile ID-Page Attempt.
PAGE_ABORT_HIGHER_PID = This count is incremented when the current QoS page
attempt sequence is aborted due to override from page of higher priority
ProfileID. This count is pegged only when the QoS Paging is active for a
ProfileID. This count is reported per OHM-Profile ID.

This metric gives the success rate of each page attempt (1 to 8) per pageable Profile ID.
The formula will be repeated 8 times, once for each page attempt. The metrics can be
used to monitor the success rate of individual page attempts to optimize the paging
strategy for each Profile ID.
The metric could be calculated per OHM-profile ID basis, but is more meaningful per
RNC Group-Profile ID since that's how the paging strategy can only be defined.
This metric is new in R29 but can be used in R28.
Formula
DO Paging Success Rate by Page Attempt (%) =

(SUM over OHMS in RNC Group (PAGE_CR_RCVD))
............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------X 100
(SUM over OHMS in RNC Group (PAGES))
Count Descriptions

pegging. This count is reported per OHM-Profile ID. This count, in
conjunction with the number of pages or connection requests received, is
used to monitor the effectiveness and efficiency of each page attempt in the
Paging sequence. This information can be used to optimize the paging
strategy setting.

This metric provides the success rate of the paging area escalation procedure. Paging area
escalation is an increase in the paging area, e.g., from Last Active Set to any larger paging
area.
The peg counts are defined on an OHM-pageable profile ID basis. The metric could be
calculated per OHM-profile ID basis, but is more meaningful per RNC Group-Profile ID
since that's how the paging strategy can only be defined. This metric is new in R29.
Formula
DO Paging Escalation Success Rate (%) =

(SUM over OHMS in RNC Group (PAGE_ESC_RESP))
-----------------------------------------------------------------------------X 100
(SUM over OHMS in RNC Group (PAGE_ESC))
Count Descriptions
PAGE_ESC_RESP = This count is incremented when a Connection Request is received

while waiting for a response to a page that was escalated.
PAGE_ESC = This count is incremented when the paging method was switched from Last
Active Set Paging to another paging area. Last Seen RNC Paging area is
used for default paging or when QoS Paging is active for a profileID but
Paging Enhancements Enable is set to No. The paging area configured for
the subsequent attempt, if non-blank and not Last Active Set, is used when
............................................................................................................................................................................................................................................................
Paging Enhancements Enable is set to Yes. The method switch occurs

when the T_Page1 timer expires before the AT's next wakeup cycle. Note
that BEpID will be used for pegging when default paging is used.
This count is used to monitor if the T_Page1 timer is set properly.

This metric provides the success rate of the paging area de-escalation procedure. Paging
area de-escalation is a decrease in the paging area to Last Active Set. This can only occur
on the first paging attempt.
The peg counts are defined on an OHM-pageable profile ID. The metric could be
Formula

(SUM over OHMS in RNC Group (PAGE_DE_ESC_RESP))
-----------------------------------------------------------------------------X 100
(SUM over OHMS in RNC Group (PAGE_DE_ESC))
Count Descriptions
PAGE_DE_ESC_RESP = This count is incremented when a Connection Request is

received while waiting for a response to a page that was de-escalated.
PAGE_DE_ESC = This count is incremented when the paging method was switched to
Last Active Set. Paging de-escalation can only occur on the first page
attempt.

This metric gives a measure of the efficiency of each page attempt (1 to 8) per pageable
Profile ID as a ratio of the number of sectors included in each page attempt divided by the
number of page attempts. The formula will be repeated 8 times, once for each page
attempt.. The metrics can be used to optimize the paging strategy settings.
The metric can only be calculated per RNC Group-profile ID basis since the SM counts
are pegged in different OHMs across the RNC Group.
Formula
DO Paging Efficiency by Sectors per Page Attempt =

(SUM over OHMS in RNC Group (PAGE_SECTORS))
-----------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Descriptions
PAGE_SECTORS = This count is incremented for each page message sent to a sector for
a given attempt K within the Paging Sequence. For example, if a page
attempt for attempt K triggers a page sent to 10 different sectors, then this
count is incremented by 10 for attempt K. K varies from 1 to 8. Therefore,
there are 8 counts, one for each value of K. Note that if the default paging
of the service node is used, then the BEpID will be used for pegging.

Beginning in R29 Data over Signalling is incorporated into 1xEV-DO for improved
paging latency, especially for Push to Talk applications. DOS is sent over the control
channel so that a traffic channel does not have to be set up in order to send a small payload
to an AT.
For the purposes of the metric, effectiveness is 'defined' as the number of successful DOS
deliveries divided by the number of unique attempts. Unique attempts is measured by the
number of attempt number 1, since subsequent attempts (2 though 8) are simply repeating
the initial page.
RNC Group-Profile ID since that's how the paging strategy can only be defined. This
metric is effective beginning with R29.
Formula
DO Data Over Signalling Effectiveness (%) =

MT_DOS_SUCCESS)
-------------------------------------------------------------------------------------------------- X 100
(SUM over OHMS in RNC Group (MT_DOS_ATTEMPTS for page attempt 1))
Count Descriptions
............................................................................................................................................................................................................................................................
Attempt.


This metric gives the success rate of each DOS page attempt (1 to 8) per pageable Profile
ID. The formula will be repeated 8 times, once for each page attempt.. The metrics can
me used to monitor the success rate of individual DOS page attempts to determine how
many attempts on average are needed for each Profile ID.
Formula
DO Data Over Signalling Success Rate by Page Attempt (%) =

(SUM over OHMS in RNC Group (MT_DOS_SUCCESS))
-----------------------------------------------------------------------------------X 100
(SUM over OHMS in RNC Group (MT_DOS_ATTEMPT))
Count Descriptions
Attempt.
............................................................................................................................................................................................................................................................

Beginning in R25 active connection histogram counts have been added at the per
sectorcarrier
level. These counts measure the number of active connections during the
capacity planning perspective. Alcatel-Lucent performance engineers will monitor actual
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

connections. The peg counts are defined on a per sector-carrier basis. The formula is
revised in R26 to account for the cross-connect (load balancing) feature. The new formula
is effective beginning with R26. Beginning with R26 there is a translation in RC/V to not
peg the CONN_REL_RLL peg count for dropped connections estimated to be caused by
"long" AT tuneaways to a 3G1x carrier. If the translation is set to to continue pegging, then
the CONN_REL_RLL count will include the tuneaways and the dropped call rate will be
inflated.
metric, DO Dropped Connection Rate - Peg should now be used.
Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
............................................................................................................................................................................................................................................................
received
received.
AT-initiated Connection attempt failures - rev link not acquired
AT-initiated connection attempt failures - no resources available
AN initiated Connection attempt failures - other
failures post-TCA
............................................................................................................................................................................................................................................................
connection request.

Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
............................................................................................................................................................................................................................................................
connection request.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions
sector).
............................................................................................................................................................................................................................................................

procedure.
procedure.

This metric gives the success rate for hard handoffs from the requesting sector
("handouts")
perspective. The peg counts are defined on a per sector-carrier basis.
Formula
............................................................................................................................................................................................................................................................
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
HHOFF_ATTMPT_REQ =
............................................................................................................................................................................................................................................................

Formula

------------------------------------------------------------------------------------------------ X 100
Count Definitions
SO_SOR_HOFF_ATTMPT_TARGET = Soft-Softer HO Attempt at the target

sectorcarrier
............................................................................................................................................................................................................................................................

assignment
assignment

Formula

--------------------------------------------------------------------------------------------------- X 100
Count Definitions

HHOFF_CONN_CLOSE_POSTTCA_TARGET = This count is the number of
interfrequency
hard handoff attempts that are terminated when a connection
sector-carrier.
HHOFF_CONN_CLOSE_PRETCA_TARGET= This count is the number of

interfrequency
sector-carrier.
............................................................................................................................................................................................................................................................

HHOFF_FAIL_NO_AT_RSP_TARGET = Hard HO Attempt failure at the target
sectorcarrier
due to no response from the AT.

Formula

............................................................................................................................................................................................................................................................
---------------------------------------------------------------------------------------------------- X 100
Count Definitions

of legs is reached.

there is no messaging involved with the AT or an element outside the AN between the
time
sources.
the cell).
............................................................................................................................................................................................................................................................

Formula

HHOFF_TCA_SENT_REQ)
------------------------------------------------------------------------------------------ X 100
Count Definitions
HHOFF_ATTMPT_REQ =

............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions


Formula

-------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions

HHOFF_CONN_CLOSE_PRETCA_TARGET = This count is the number of
interfrequency

Formula

------------------------------------------------------------------------------ X 100
Count Definitions
TCA sent by the AN
procedure.
............................................................................................................................................................................................................................................................

Formula

----------------------------------------------------------- X 100
Count Definitions
sent by the AN.

R24 and later.
............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------------------- X 100
Count Definitions
TCA sent by the AN.

Formula

--------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
sent by the AN.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

link. It is simply the rate at which some of the original RLP bytes have to be retransmitted.
The AT requests the re-transmission when it encounters a gap in sequence
in RLP NAKs.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
channel.

in RLP NAKs.
releases.
............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------X 100
Count Definitions


RLP NAKs.
............................................................................................................................................................................................................................................................
releases.
Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions

sector-carrier.
Conversational Speech (with or without ROHC) RLP octet that is retransmitted
to an AT when DARQ is turned on. It is the total of all octets
Conversational Video (with or without ROHC) RLP octet that is retransmitted
............................................................................................................................................................................................................................................................
sector-carrier.
octets.

octets.

............................................................................................................................................................................................................................................................
Formula

MISSING_RLP_REQ_RTC
-------------------------------------------X100
RLP_RXED_RTC
Count Definitions
MISSING_RLP_REQ_RTC = The total number of bytes the AN requests the AT to

retransmit
on the reverse link. The request is made via an RLP NAK
message. As on the forward link, any such missing data can be NAKed

points (considering 1% chance that either the downlink RLP NAK got lost or the
retransmission
from the AT got corrupted). However, the issues that led to the retransmissions
in the first place may also contribute to a higher re-transmission failure rate
............................................................................................................................................................................................................................................................
Formula

-------------------------------------------------------------------------------------------X100
MISSING_RLP_REQ_RTC
Count Definitions

retransmit it.

layer
Formula

------------------------------------------------------------------------------------------------------------
8 * 10 ^ 6
............................................................................................................................................................................................................................................................
Count Definitions



Formula

............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------------------------------------
10 ^ 6
Count Definitions

and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................


=
EVM_FWD_PACKETS_2457_6_TOTAL_COUNT) + (EVM_FTC_TOT_BYTES_4_8
+
--------------------------------------------------------------------------------------- =
10 ^ 6

............................................................................................................................................................................................................................................................
sector.
............................................................................................................................................................................................................................................................
the users are in a benign RF coverage area. Of course, this inference lies on the
assumption
higher rates.
hardware, etc.).
Formula

............................................................................................................................................................................................................................................................
------------------------------------------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Alternatively, the physical layer transmitted bytes can be utilized to provide a general
view
assumption
higher rates.
hardware, etc.).
EVM.
Formula

............................................................................................................................................................................................................................................................
------------------------------------------------------------------------------------------------------------
Count Definitions

and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................


=
+
............................................................................................................................................................................................................................................................
--------------------------------------------------------------------------------------------------
This metric provides a measure of the average per user perceived data rate on a
sectorcarrier.
It uses the active usage peg count which measures the number of users either
Formula
-----------------------------------------------------------------------------------------------------------
Count Definitions

and Rev A traffic.E
and Rev A traffic.
............................................................................................................................................................................................................................................................
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.

transmission.
............................................................................................................................................................................................................................................................


users.
A large value indicated by this metric does not necessarily mean congestion on the air
link.
A single user doing FTP downloads throughout the hour is expected to drive the
utilization
Formula
............................................................................................................................................................................................................................................................
Count Definitions


per second.
The metric carries a sector level? connotation rather than a per user?
view given the denominator includes the total traffic channel slots used in an hour. So
it reflects the average RF conditions the sector serves. The RLP byte count is closer to the
actual user traffic with less overhead than either MAC layer or physical layer packet
counts, which can be padded with dummy bits to fill the packet.
Note that there are 2,160,000 slots in one hour (3600 seconds divided by the length of
each slot, which in 1xEV-DO is 1.66 milliseconds).
It does not capture a very small amount of throughput loss due to some of the
retransmitted
RLP packets not reaching the end user (typically ~0.02% for a 1% retransmission
rate).
above issues, RLP data rate should only be viewed as an estimate of actual rate, although
it is not far off the mark especially at moderate to high loading points.
............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------
Count Definitions
per second.
The metric carries a ector level ? connotation rather than a er
user ? view given the
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
octets.
octets.
............................................................................................................................................................................................................................................................

Formula

------------------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------------------
Count Definitions
octets.
octets.
............................................................................................................................................................................................................................................................

once per slot.
Formula

------------------------------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
octets.
octets.
transmission.
............................................................................................................................................................................................................................................................
Formula

------------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions

Formula

REV_PACKETS_512_TOTAL_COUNT
............................................................................................................................................................................................................................................................
----------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions


............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------------------------------------
8 * 10^6
rates.
............................................................................................................................................................................................................................................................
Formula:

---------------------------------------------------------------------------------------------------
Count Definitions

This metric gives the average data rate on the reverse link in kilobits per second for
sectorcarriers
equipped with an SBEVM. The metric is defined on a per sector-carrier basis.
of 6.6 ms.
............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................


............................................................................................................................................................................................................................................................
----------------------------------------------------------------------------------------
NUM_SUBPKTS_RL_12288) * 0.00667]

Formula
............................................................................................................................................................................................................................................................
----------------------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

----------------------------------------------------------------------------------------
+
NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Error Statistics
............................................................................................................................................................................................................................................................

at the AT).
level.
Formula
Count Definitions

............................................................................................................................................................................................................................................................

Since the reverse frame error rate peg counts are not pegged for the SBEVM there is no
direct indication of errors on the reverse rf link. This metric provides some measure of the
rf quality of the reverse link by calculating the percentage of LoLat packets that missed
their termination target. The lower the value of the calculation, the better the quality of the
link.
The peg counts are defined on a sector-carrier basis. The metric is new R29.
Formula
RL_LOLAT_PKTS_MISSED_TARGET
------------------------------------------------------- X 100
RL_LOLAT_PKTS_RCVD
Count Definitions
RL_LOLAT_PKTS_MISSED_TARGET = This count is pegged when a TP receives a

LoLat packet that has missed termination target.
RL_LOLAT_PKTS_RCVD = This count is pegged when a TP receives a LoLat packet.
............................................................................................................................................................................................................................................................
Power Control
............................................................................................................................................................................................................................................................

Formula

--------------------------------------------------------------------------------
Count Definitions

frames in which the data rate is 9.6 kbps. The peg counts are defined on a per sectorcarrier
basis.
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
............................................................................................................................................................................................................................................................
frames in which the data rate is 19.2 kbps. The peg counts are defined on a per
sectorcarrier basis.
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
Formula

---------------------------------------------------------------------------------
Count Definitions

count are dB/8.
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO.
busy hour basis per sector or as an average computed over a few busy hours in a day,
rather than a large grouping of cells or combined over all hours of the day.
IBM Prospect for Alcatel-Lucent it has already been divided by 360 and should not be
divided again.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................

Formula

Count Definitions

(average * 100).
............................................................................................................................................................................................................................................................

connections.
Formula

-----------------------------------------------------------------------
Count Definitions

(average * 100).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

beginning in R28.
Formula

ROR_ACCEPTED
-------------------------------------X100
ROR_RECEIVED
Count Definitions


on a sector-carrier basis. This metric is new in R28. The formula is changed beginning in
R29 due to peg count name changes.
Formula

RESV_ADMITTED_FL_CS
------------------------------------------------------------------------ X 100
............................................................................................................................................................................................................................................................
RESV_REQ_FL_CS
Count Definitions
RESV_ADMITTED_FL_CS = This count is incremented when a FL reservation of

Conversational Speech is included in a ReservationOnRequest that has
been accepted.
RESV_REQ_FL_CS = This count is incremented when a FL reservation of
Conversational Speech is included in a ReservationOnRequest.

The formula is changed beginning in R29.
Formula
DO FL CS Dropped Res Rate (%) =

(RESV_DROP_BH_OVLD_FL_CS +
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CS +
FL_RESV_TERM_OPPOSITE_RESV_DROP_CS +
FL_RESV_TERM_INV_BH_CS)
----------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CS
Count Definitions
RESV_DROP_BH_OVLD_FL_CS = This count is incremented when a FL reservation of

Conversational Speech is terminated due to backhaul overload.
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CS = This count is incremented
when a FL reservation of Conversational Speech is terminated because
number of packets dropped by the scheduler has exceeded the threshold set
in translations.
CAUTION: In areas where BCMCS is enabled, some percentage of dropped reservations
may be due to resource contention between unicast and BCMCS services
and are not indicative of a system or network problem. BCMCS
measurement data must be included in the analysis to determine whether a
system or network problem exists or not. Slots reserved for BCMCS traffic
can not be allocated to unicast traffic.
FL_RESV_TERM_OPPOSITE_RESV_DROP_CS = This count is incremented when a
FL reservation of Conversational Speech is terminated because its
counterpart in the RL has been terminated.
FL_RESV_TERM_INV_BH_CS = This count is incremented when a FL reservation of
............................................................................................................................................................................................................................................................
Conversational Speech is terminated when a sector that is not supported by

either MLPPP or ethernet has been added to the active set of the AT.
been accepted.

Formula

RESV_ADMITTED_FL_CV
-----------------------------------------------------X 100
RESV_REQ_FL_CV
Count Definitions
RESV_ADMITTED_FL_CV= This count is incremented when a FL reservation of

Conversational Video is included in a ReservationOnRequest that has been
accepted.
RESV_REQ_FL_CV = This count is incremented when a FL reservation of

Formula

(RESV_DROP_BH_OVLD_FL_CV +
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CV +
FL_RESV_TERM_OPPOSITE_RESV_DROP_CV +
FL_RESV_TERM_INV_BH_CV)
--------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CV
............................................................................................................................................................................................................................................................
Count Descriptions
RESV_DROP_BH_OVLD_FL_CV = This count is incremented when a FL reservation of

Conversational Video is terminated due to backhaul overload.
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CV = This count is incremented
when a FL reservation of Conversational Video is terminated because
in translations.
may be due to resource contention between unicast and BCMCS services and are not
indicative of a system or network problem. BCMCS measurement data must be included
in the analysis to determine whether a system or network problem exists or not. Slots
reserved for BCMCS traffic can not be allocated to unicast traffic.
FL_RESV_TERM_OPPOSITE_RESV_DROP_CV = This count is incremented when a
FL reservation of Conversational Video is terminated because its
FL_RESV_TERM_INV_BH_CV = This count is incremented when a FL reservation of
Conversational Video is terminated when a sector that is not supported by
RESV_ADMITTED_FL_CV = This count is incremented when a FL reservation of
accepted.

on a sector-carrier bases. This metric is new in R28. The formula is changed beginning in
Formula

RESV_ADMITTED_FL_CPS
-----------------------------------------------------------X 100
RESV_REQ_FL_CPS
Count Definitions
RESV_ADMITTED_FL_CPS = This count is incremented when a FL reservation of

Conversational PTT Speech is included in a ReservationOnRequest that
has been accepted.
RES_REQ_FL_CPS = This count is incremented when a FL reservation of
Conversational PTT Speech is included in a ReservationOnRequest.
............................................................................................................................................................................................................................................................

beginning in R28. The formula is revised beginning in R29.
Formula

(RESV_DROP_BH_OVLD_FL_CPS +
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CPS +
FL_RESV_TERM_OPPOSITE_RESV_DROP_CPS +
FL_RESV_TERM_INV_BH_CPS)
----------------------------------------------------------------------------------X 100
Count Descriptions
RESV_DROP_BH_OVLD_FL_CPS = This count is incremented when a FL reservation

of conversational push-to-talk Speech is terminated due to backhaul
overload.
FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_CPS = This count is incremented
when a FL reservation of Conversational PTT Speech is terminated
because number of packets dropped by the scheduler has exceeded the
threshold set in translations.
FL_RESV_TERM_OPPOSITE_RESV_DROP_CPS = This count is incremented when a
FL reservation of Conversational PTT Speech is terminated becauseits
FL_RESV_TERM_INV_BH_CPS = This count is incremented when a FL reservation of
Conversational PTT Speech is terminated when a sector that is not
supported by either MLPPP or ethernet has been added to the active set of
the AT.
Conversational PTT Speech has been accepted.

............................................................................................................................................................................................................................................................
The formula is revised beginning in R29.
Formula

(RESV_DROP_BH_OVLD_RL_CS +
RESV_DROP_RF_OVLD_RL_CS +
RL_RESV_TERM_OPPOSITE_RESV_DROP_CS +
RL_RESV_TERM_INV_BH_CS)
--------------------------------------------------------------------------------------------- X 100
RESV_ADMITTED_RL_CS
Count Descriptions
RESV_DROP_BH_OVLD_RL_CS = This count is incremented when a RL reservation of

RESV_DROP_RF_OVLD_RL_CS = This count is incremented when a RL reservation of
Conversational Speech is terminated due to reverse link RF overload.
RL_RESV_TERM_OPPOSITE_RESV_DROP_CS = This count is incremented when a
RL reservation of Conversational Speech is terminated due to the
termination of it's FL counterpart.
RL_RESV_TERM_INV_BH_CS = This count is incremented when a RL reservation of
RESV_ADMITTED_RL_CS = This count is incremented when a RL reservation of
been accepted.

Formula

(RESV_DROP_BH_OVLD_RL_CV +
RESV_DROP_RF_OVLD_RL_CV +
RL_RESV_TERM_OPPOSITE_RESV_DROP_CV +
RL_RESV_TERM_INV_BH_CV)
------------------------------------------------------------------------X 100
RESV_ADMITTED_RL_CV
............................................................................................................................................................................................................................................................
Count Descriptions
RESV_DROP_BH_OVLD_RL_CV = This count is incremented when a RL reservation

of Conversational Video is terminated due to backhaul overload.
RESV_DROP_RF_OVLD_RL_CV = This count is incremented when a RL reservation of
Conversational Video is terminated due to reverse link RF overload.
RL_RESV_TERM_OPPOSITE_RESV_DROP_CV = This count is incremented when a
RL reservation of Conversational Video is terminated due to the
termination of its FL counterpart.
RL_RESV_TERM_INV_BH_CV = This count is incremented when a RL reservation of
RESV_ADMITTED_RL_CV = This count is incremented when a RL reservation of
accepted.

beginning in R28. The formula is revised beginning with R29.
Formula

(RESV_DROP_BH_OVLD_RL_CPS +
RESV_DROP_RF_OVLD_RL_CPS +
RL_RESV_TERM_OPPOSITE_RESV_DROP_CPS +
RL_RESV_TERM_INV_BH_CPS)
----------------------------------------------------------------------------------X 100
RESV_ADMITTED_RL_CPS
Count Descriptions
RESV_DROP_BH_OVLD_RL_CPS = This count is incremented when a RL reservation

overload.
RESV_DROP_RF_OVLD_RL_CPS = This count is incremented when a RL reservation
of Conversational push-to-talk Speech is terminated due to reverse link RF
overload.
RL_RESV_TERM_OPPOSITE_RESV_DROP_CPS = This count is incremented when a
RL reservation of Conversational PTT Speech is terminated due to the
RL_RESV_TERM_INV_BH_CPS = This count is incremented when a RL reservation of
............................................................................................................................................................................................................................................................

the AT.
RESV_ADMITTED_RL_CPS = This count is incremented when a RL reservation of

This metric provides the success rate of the Broadcast/Multicast Service (BCMCS )
registration on the Broadcast Serving Node (BSN). BCMCS is a service wherein a single
stream of data is sent to multiple ATs from all of the sectors on the BCMCS carrier.The
peg counts are defined on a per TP basis. The metric is effective beginning in R29.
Formula
DO BCMCS Reg Success Rate (%) =

A11_BC_REG_REPLY_SUCC_RCVD
-------------------------------------------------------- X 100
A11_BC_REG_REQ_ SENT
Count Descriptions
A11_BC_REG_REPLY_SUCC_RCVD = This count is pegged every time a successful

A11 Broadcast registration reply message is received at the AP from the
Broadcast Serving Node (BSN) in response to the A11 BC registration
request previously sent.
A11_BC_REG_REQ_ SENT = This count is pegged each time an A11 Broadcast
registration request message is sent from the AP to the BSN. This count
does not include the A11 Broadcast registration request retries.

This metric provides the success rate of the BCMCS service request to the BSN.
The peg counts are defined on a per TP basis. This metric is effective beginning in R29.
Formula
DO BCMCS Service Req Success Rate (%) =

A11_BC_SERVICE_RESPONSE_SUCC_RCVD
------------------------------------------------------------------- X 100
A11_BC_SERVICE_REQ_ SENT
Count Descriptions
A11_BC_SERVICE_RESPONSE_SUCC_RCVD = This count is pegged every time a

successful A11 Broadcast service response message is received at the AP
from the Broadcast Serving Node (BSN) in response to the A11 BC serivce
............................................................................................................................................................................................................................................................

A11_BC_SERVICE_REQ_ SENT = This count is pegged each time an A11 Broadcast
service request message is sent from the AP to the BSN. This count does
not include the A11 Broadcast service request retries.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Overview
The purpose of this chapter is to describe new and modified Primitive Calculations
(PCALCS) that support 1XEV-DO Performance Metrics in IBM Prospect for Alcatel-
Lucent R29.
earlier releases.
166 new 1xEV-DO performance metrics for R29 (see New 1xEV-DO Performance
Metrics in Prospect R29 (p. 18-15) ). Three metrics are defined on a page attempt
(k=1-8) and 6 are defined on a paging personality ID basis. For each of these three
metrics, there are 48 PCALCs in Prospect.
releases:
25
............................................................................................................................................................................................................................................................
Release 29

26
............................................................................................................................................................................................................................................................
Release 29 RNC R29

............................................................................................................................................................................................................................................................

D Op _ FL CS R sr vS u cc = 10 0 .0 * Re s vA dm i tt ed F L_ C S / R es vR e qF L _C S
Notes:
1. The formula changed in R29 due to peg count name changes
Prospect
Traffic
ResvAdmittedFL_CS RESV_ADMITTED_FL_CS IxEV_Sector
Carrier
ResvReqFL_CS RESV_REQ_FL_CS 1xEV_Sector
Carrier

D Op _ FL CV R sr vS u cc = 10 0 .0 * Re s vA dm i tt ed F L_ C V/ R e sv Re q FL _ CV
Notes:
Prospect
Traffic
ResvAdmittedFL_CV RESV_ADMITTED_FL_CV 1xEV_Sector
Carrier
ResvReqFL_CV RESV_REQ_FL_CV 1xEV_Sector
Carrier
1xEV-DO Forward Link Conversational PTT Speech Reservation Success Rate

............................................................................................................................................................................................................................................................
Release 29 RNC R29
DO p _F L CP SR s rv Su c c = 10 0. 0 * R es v Ad mi t te dF L _C PS / R e sv R eq FL _ CP S
Notes:
Prospect
Traffic
ResvAdmittedFL_CPS RESV_ADMITTED_FL_CPS 1xEV_Sector
Carrier
ResvReqFL_CPS RESV_REQ_FL_CPS 1xEV_Sector
Carrier

DO p _F L Co nv S pe ec h Dr o pR es e rv = 10 0 .0 * (R es v Dr o pB HO v ld FL _ CS +
FL R es v Te rm D ro pp e dP k ts Ex T hr es h _C S +
FL R es v Te rm O pp os i te R es vD r op _C S + FL Re s vT er m In v BH _C S ) /
Re s vA d mi tt e dF L_ C S
Notes:
Prospect Traffic
ResvDropBHOvldFL_CS RESV_DROP_BH_OVLD_FL_CS 1xEV_SectorCarrier
FLResvTermDroppedPktsExThr FL_RESV_TERM_DROPPED_PKTS_EX_THRE 1xEV_SectorCarrier
esh_CS SH_CS
FLResvTermOppositeResvDrop FL_RESV_TERM_OPPOSITE_RESV_DROP_CS 1xEV_SectorCarrier
_CS
FLResvTermInvBH_CS FL_RESV_TERM_INV_BH_CS 1xEV_SectorCarrier
ResvAdmittedFL_CS RESV_ADMITTED_FL_CS 1xEV_SectorCarrier
............................................................................................................................................................................................................................................................
Release 29 RNC R29

D Op _ FL Co n vV id e oD r op Re s er v = 1 0 0. 0 * ( Re s vD r op BH O vl dF L _C V +
F LR e sv Te r mD ro p pe d Pk ts E xT hr e sh _ CV +
F LR e sv Te r mO pp o si t eR es v Dr op _ CV + FL R es vT e rm I nv BH _ CV ) /
R es v Ad mi t te dF L _C V
Notes:
Prospect Traffic
ResvDropBHOvldFL_CV RESV_DROP_BH_OVLD_FL_CV 1xEV_SectorCarrie
r
FLResvTermDroppedPktsExT FL_RESV_TERM_DROPPED_PKTS_EX_THRESH_ 1xEV_SectorCarrie
hresh_CV CV r
FLResvTermOppositeResvDr FL_RESV_TERM_OPPOSITE_RESV_DROP_CV 1xEV_SectorCarrie
op_CV r
FLResvTermInvBH_CV FL_RESV_TERM_INV_BH_CV 1xEV_SectorCarrie
r
ResvAdmittedFL_CV RESV_ADMITTED_FL_CV 1xEV_SectorCarrie
r
1xEV-DO Forward Link Conversational PTT Speech Dropped Reservation Rate

DOp_FLConvPTTSpchDropReserv = 100.0 * (ResvDropBHOvldFL_CPS +
FLResvTermDroppedPktsExThresh_CPS + FLResvTermOppositeResvDrop_CPS +
FLResvTermInvBH_CPS) / ResvAdmittedFL_CPS
Notes:
Prospect
Traffic
ResvDropBHOvldFL_CPS RESV_DROP_BH_OVLD_FL_CPS 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 29 RNC R29
FLResvTermDroppedPktsExThres FL_RESV_TERM_DROPPED_PKTS_EX_THRESH 1xEV_Sector

h_CPS _CPS Carrier
FLResvTermOppositeResvDrop_ FL_RESV_TERM_OPPOSITE_RESV_DROP_CPS 1xEV_Sector

CPS Carrier
FLResvTermInvBH_CPS FL_RESV_TERM_INV_BH_CPS 1xEV_Sector

Carrier
ResvAdmittedFL_CPS RESV_ADMITTED_FL_CPS 1xEV_Sector
Carrier
2.2.41xEV-DO Reverse Link Conversational Speech Dropped Reservation Rate

DOp_RLConvSpeechDropReserv = 100.0 * (ResvDropBHOvldRL_CS +
ResvDropRFOvldRL_CS + RLResvTermOppositeResvDrop_CS +
RLResvTermInvBH_CS) / ResvAdmittedRL_CS
Notes:
Prospect
Traffic
ResvDropBHOvldRL_CS RESV_DROP_BH_OVLD_RL_CS 1xEV_Sector
Carrier
ResvDropRFOvldRL_CS RESV_DROP_RF_OVLD_RL_CS 1xEV_Sector
Carrier
RLResvTermOppositeResvDrop_ RL_RESV_TERM_OPPOSITE_RESV_DROP_CS 1xEV_Sector
CS Carrier
RLResvTermInvBH_CS RL_RESV_TERM_INV_BH_CS 1xEV_Sector

Carrier
ResvAdmittedRL_CS RESV_ADMITTED_RL_CS 1xEV_Sector
Carrier

............................................................................................................................................................................................................................................................
Release 29 RNC R29
DOp_RLConvVideoDropReserv = 100.0 * (ResvDropBHOvldRL_CV +

ResvDropRFOvldRL_CV + RLResvTermOppositeResvDrop_CV +
RLResvTermInvBH_CV) / ResvAdmittedRL_CV
Notes:
Prospect
Traffic
ResvDropBHOvldRL_CV RESV_DROP_BH_OVLD_RL_CV 1xEV_Sector
Carrier
ResvDropRFOvldRL_CV RESV_DROP_RF_OVLD_RL_CV 1xEV_Sector
Carrier
RLResvTermOppositeResvDrop_CV RL_RESV_TERM_OPPOSITE_RESV_DROP_CV 1xEV_Sector
Carrier
RLResvTermInvBH_CV RL_RESV_TERM_INV_BH_CV 1xEV_Sector
Carrier
ResvAdmittedRL_CV RESV_ADMITTED_RL_CV 1xEV_Sector
Carrier
2.2.61xEV-DO Reverse Link Conversational PTT Speech Dropped Reservation Rate

DOp_RLConvPTTSpchDropReserv = 100.0 * (ResvDropBHOvldRL_CPS +
ResvDropRFOvldRL_CPS + RLResvTermOppositeResvDrop_CPS +
RLResvTermInvBH_CPS) / ResvAdmittedRL_CPS
Notes:
1. Mapping between Prospect names and EVDO Names
Prospect
Traffic
ResvDropBHOvldRL_CPS RESV_DROP_BH_OVLD_RL_CPS 1xEV_Sector
Carrier
ResvDropRFOvldRL_CPS RESV_DROP_RF_OVLD_RL_CPS 1xEV_Sector
Carrier
RLResvTermOppositeResvDrop_CP RL_RESV_TERM_OPPOSITE_RESV_DROP_CPS 1xEV_Sector
S Carrier
............................................................................................................................................................................................................................................................
Release 29 RNC R29
RLResvTermInvBH_CPS RL_RESV_TERM_INV_BH_CPS 1xEV_Sector

Carrier
ResvAdmittedRL_CPS RESV_ADMITTED_RL_CPS 1xEV_Sector
Carrier
1xEV-DO Average Forward Link RLP Data Rate per User SBEVM (kbps)
DOp_FLRLPAvgRateUser_SBEVM = (8.0 /1000.0) * (RLPTxedFTC_BE +
RLPTxedFTC_CPS + RLPTxedFTC_CS + RLPTxedFTC_CV + RLPTxedFTC_SMC) /
(ActiveUsage * 0.001667)
Notes:
Prospect
Traffic
Carrier
Carrier
Carrier
Carrier
Carrier
ActiveUsage EVM_ACTIVE_USAGE 1xEV_Sector
Carrier

DOp_CnctBlk = 100.0 * (ANInitConRq - ANInitConnAttmptDiffSecCarrSent +
ANInitConnAttmptDiffSecCarrRcvd + ATInitConRq -
ATInitConnAttmptDiffSecCarrSent + ATInitConnAttmptDiffSecCarrRcvd -
(TCAANInitConRq + TCAATInitConRq +CrossCarrAttmptRcvdTCASent -
CrossCarrAttmptSentTCASent)) / (ANInitConRq -
............................................................................................................................................................................................................................................................
Release 29 RNC R29
ANInitConnAttmptDiffSecCarrSent + ANInitConnAttmptDiffSecCarrRcvd +
ATInitConRq - ATInitConnAttmptDiffSecCarrSent +
ATInitConnAttmptDiffSecCarrRcvd)
Notes:
1. Remove SessClose_SessTrnfAbort from numerator and denominator
Prospect
Traffic
ANInitConnAttmptDiffSecCarrRcvd AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RC 1xEV_Sector
VD
ANInitConnAttmptDiffSecCarrSent AN_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SE 1xEV_Sector
NT
ATInitConnAttmptDiffSecCarrRcvd AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_RC 1xEV_Sector
VD
ATInitConnAttmptDiffSecCarrSent AT_INIT_CONN_ATTMPT_DIFF_SEC_CARR_SEN 1xEV_Sector
T
CrossCarrAttmptRcvdTCASent CROSS_CARR_ATTMPT_RCVD_TCA_SENT 1xEV_Sector
CrossCarrAttmptSentTCASent CROSS_CARR_ATTMPT_SENT_TCA_SENT 1xEV_Sector
SessClose_SessTrnfAbort SESS_CLOSE_SESS_TRFR_ABORTED 1xEV_Sector

DOp_PageEff_BE = 100.0 * (PageCRRcvd_BE + MTDOSSuccess_BE) / (pages1be +
mtdosAttempts1be - PageAbortHigherPID_BE)
............................................................................................................................................................................................................................................................
Release 29 RNC R29
Notes:
1. Note that this metric is calculated at the FMS level, but the counts in the equation are at
the IxEV_PageAttempt level. This means that the counts in the numerator are rolled-up
over paging attempts (1 - 8) and OHM. However, the page attempt counts in the
denominator are for Page Attempt 1 only. I.e., these terms are not rolled up over paging
attempts but are rolled up over OHMs
Prospect
Traffic
pages1be PAGES (BE; Page attempt 1) IxEV_PageA
ttempts
PageCRRcvd_BE PAGE_CR_RCVD (BE) IxEV_PageA
ttempts
MTDOSSuccess_BE MT_DOS_SUCCESS (BE) IxEV_PageA
ttempts
mtdosAttempts1be MT_DOS_ATTEMPTS (BE; Page attempt 1) IxEV_PageA
ttempts
PageAbortHigherPID_BE PAGE_ABORT_HIGHER_PID (BE) IxEV_OHM
Paging Profile ID CMCS

DOp_PageEff_CMCS = 100.0 * (PageCRRcvd_CMCS + MTDOSSuccess_CMCS) /
(pages1cmcs + mtdosAttempts1cmcs - PageAbortHigherPID_CMCS)
Notes:
Prospect
Traffic
............................................................................................................................................................................................................................................................
Release 29 RNC R29
pages1cmcs PAGES (CMCS; Page attempt 1) IxEV_PageA

ttempts
PageCRRcvd_CMCS PAGE_CR_RCVD (CMCS) IxEV_PageA
ttempts
MTDOSSuccess_CMCS MT_DOS_SUCCESS (CMCS) IxEV_PageA
ttempts
mtdosAttempts1cmcs MT_DOS_ATTEMPTS (CMCS; Page attempt 1) IxEV_PageA
ttempts
PageAbortHigherPID_CMCS PAGE_ABORT_HIGHER_PID (CMCS) IxEV_OHM

DOp_PageEff_PTTCSS = 100.0 * (PageCRRcvd_PTTCSS + MTDOSSuccess_PTTCSS) /
(pages1pttcss + mtdosAttempts1pttcss - PageAbortHigherPID_PTTCSS)
Notes:
Prospect
Traffic
pages1pttcss PAGES (PTT_CALL_SETUP_SIG; Page attempt 1) IxEV_PageA
ttempts
PageCRRcvd_PTTCSS PAGE_CR_RCVD (PTT_CALL_SETUP_SIG) IxEV_PageA
ttempts
MTDOSSuccess_PTTCSS MT_DOS_SUCCESS (PTT_CALL_SETUP_SIG) IxEV_PageA
ttempts
mtdosAttempts1pttcss MT_DOS_ATTEMPTS (PTT_CALL_SETUP_SIG; IxEV_PageA
Page attempt 1) ttempts
PageAbortHigherPID_PTTCSS PAGE_ABORT_HIGHER_PID IxEV_OHM
(PTT_CALL_SETUP_SIG)

............................................................................................................................................................................................................................................................
Release 29 RNC R29

DOp_PageEff_PTTICS = 100.0 * (PageCRRcvd_PTTICS + MTDOSSuccess_PTTICS) /
(pages1pttics + mtdosAttempts1pttics - PageAbortHigherPID_PTTICS)
Notes:
Prospect
Traffic
pages1pttics PAGES (PTT_INCALL_SIG; Page attempt 1) IxEV_PageA
ttempts
PageCRRcvd_PTTICS PAGE_CR_RCVD (PTT_INCALL_SIG) IxEV_PageA
ttempts
MTDOSSuccess_PTTICS MT_DOS_SUCCESS (PTT_INCALL_SIG) IxEV_PageA
ttempts
mtdosAttempts1pttics MT_DOS_ATTEMPTS (PTT_INCALL_SIG; Page IxEV_PageA
attempt 1) ttempts
PageAbortHigherPID_PTTICS PAGE_ABORT_HIGHER_PID (PTT_INCALL_SIG) IxEV_OHM

DOp_PageEff_PTTSB1 = 100.0 * (PageCRRcvd_PTTSB1 + MTDOSSuccess_PTTSB1) /
(pages1pttsb1 + mtdosAttempts1pttsb1 - PageAbortHigherPID_PTTSB1)
Notes:
............................................................................................................................................................................................................................................................
Release 29 RNC R29
Prospect
Traffic
pages1pttsb1 PAGES (PTT_SPEECH_BEARER1; Page attempt 1) IxEV_PageA
ttempts
ttempts
MTDOSSuccess_PTTSB1 MT_DOS_SUCCESS (PTT_SPEECH_BEARER1) IxEV_PageA
ttempts
mtdosAttempts1pttb1 MT_DOS_ATTEMPTS (PTT_SPEECH_BEARER1; IxEV_PageA
PageAbortHigherPID_PTTSB1 PAGE_ABORT_HIGHER_PID IxEV_OHM
(PTT_SPEECH_BEARER1)

DOp_PageEff_PTTSB2 = 100.0 * (PageCRRcvd_PTTSB2 + MTDOSSuccess_PTTSB2) /
(pages1pttsb2 + mtdosAttempts1pttsb2 - PageAbortHigherPID_PTTSB2)
Notes:
Prospect
Traffic
pages1pttsb2 PAGES (PTT_SPEECH_BEARER2; Page attempt 1) IxEV_PageA
ttempts
ttempts
ttempts
............................................................................................................................................................................................................................................................
Release 29 RNC R29
mtdosAttempts1pttsb2 MT_DOS_ATTEMPTS (PTT_SPEECH_BEARER2; IxEV_PageA

PageAbortHigherPID_PTTSB2 PAGE_ABORT_HIGHER_PID IxEV_OHM
(PTT_SPEECH_BEARER2)
............................................................................................................................................................................................................................................................
Release 29 R29

............................................................................................................................................................................................................................................................
1xEV-DO Intra_RNC Session Balance Success Rate

D Op _ In tr a RN CS e ss B al Su c c = 1 00 . 0 *
S es s Ba lS u cc es s In t ra RN C Or ig O HM / S es s Ba lR e qI n tr aR n cO ri g OH M
Note:
Prospect
Traffic
SessBalSuccessIntraRNCOrigOHM SESS_BAL_SUCCESS_INTRA_RNC_ORIG_OHM IxEV_OHM
SessBalReqIntraRncOrigOHM SESS_BAL_REQ_INTRA_RNC_ORIG_OHM IxEV_OHM
Paging Success Rate by Page Attempt and Paging Profile ID

Paging Success Rate by Page Attempt and Paging Profile ID = BE

D Op _ Pa ge S uc c_ B E_ k = 1 0 0. 0 * p a ge cr r cv dk b e / p ag e sk be ( Pa ge
A tt e mp t = k = 1- 8)
Paging Success Rate by Page Attempt and Paging Profile ID = CMCS

D Op _ Pa ge S uc c_ C MC S _k = 10 0. 0 * pa ge c rr cv d kc m cs / pa ge s kc m cs
( Pa g e At t em pt = k = 1 - 8 )
Paging Success Rate by Page Attempt and Paging Profile ID = PTTCSS

D Op _ Pa ge S uc c_ P TT C SS _k = 10 0 .0 * pa g ec rr c vd k pt tc s s /
p ag e sk pt t cs s ( P ag e A tt em p t = k = 1- 8 )
Paging Success Rate by Page Attempt and Paging Profile ID = PTTICS

D Op _ Pa ge S uc c_ P TT I CS _k = 10 0 .0 * pa g ec rr c vd k pt ti c s /
p ag e sk pt t ic s ( P ag e A tt em p t = k = 1- 8 )
............................................................................................................................................................................................................................................................
Release 29 R29
Paging Success Rate by Page Attempt and Paging Profile ID = PTTSB1

DO p _P a ge Su c c_ PT T SB 1 _k = 10 0. 0 * pa ge c rr cv d kp t ts b1 /
pa g es k pt ts b 1 ( Pa g e At t em pt = k = 1 - 8 )
Paging Success Rate by Page Attempt and Paging Profile ID = PTTSB2

DO p _P a ge Su c c_ PT T SB 2 _k = 10 0. 0 * pa ge c rr cv d kp t ts b2 /
pa g es k pt ts b 2 ( Pa g e At t em pt = k = 1 - 8 )
Notes:
at the IxEV_PageAttempt level. This means that the counts in the numerator are
rolled-up over paging attempts (1 - 8) and OHM. However, the page attempt counts in
the denominator are for Page Attempt 1 only. I.e., these terms are not rolled up over
paging attempts but are rolled up over OHMs. Each row represents 8 metrics
Prospect Traffic
pageskbe PAGES (BE; Page attempt k, k = 1 - 8) IxEV_PageAttempts
pageskcmcs PAGES (CMCS; Page attempt k, k = 1 - 8) IxEV_PageAttempts
pageskpttcss PAGES (PTT_CALL_SETUP_SIG; Page attempt IxEV_PageAttempts
k, k = 1 - 8)
pageskpttics PAGES (PTT_INCALL_SIG; Page attempt k, k = 1 IxEV_PageAttempts
- 8)
pageskpttsb1 PAGES (PTT_SPEECH_BEARER1; Page attempt IxEV_PageAttempts
k, k = 1 - 8)
pageskpttsb2 PAGES (PTT_SPEECH_BEARER2; Page attempt IxEV_PageAttempts
k, k = 1 - 8)
pagecrrcvdkbe PAGE_CR_RCVD (BE; Page attempt k, k = 1 - 8) IxEV_PageAttempts
pagecrrcvdkcmcs PAGE_CR_RCVD (CMCS; Page attempt k, k = 1 - IxEV_PageAttempts
8)
pagecrrcvdkpttcss PAGE_CR_RCVD (PTT_CALL_SETUP_SIG; IxEV_PageAttempts
Page attempt k, k = 1 - 8)
pagecrrcvdkpttics PAGE_CR_RCVD (PTT_INCALL_SIG; Page IxEV_PageAttempts
attempt k, k = 1 - 8)
pagecrrcvdkpttsb1 PAGE_CR_RCVD (PTT_SPEECH_BEARER1; IxEV_PageAttempts
............................................................................................................................................................................................................................................................
Release 29 R29
pagecrrcvdkpttsb2 PAGE_CR_RCVD (PTT_SPEECH_BEARER2; IxEV_PageAttempts

Paging Escalation Success Rate

Paging Escalation Success Rate for BE

D Op _ Pa ge E sc Su c c_ B E = 1 00 .0 * P ag eE s cR es p _B E /P ag e Es c_ B E
Paging Escalation Success Rate for CMCS

D Op _ Pa ge E sc Su c c_ C MC S = 10 0 .0 * P ag e Es cR e sp _ CM CS / P a ge E sc _C M CS
Paging Escalation Success Rate for PTTCSS

D Op _ Pa ge E sc Su c c_ P TT CS S = 1 0 0. 0 * P a ge Es c Re s p_ PT T CS S/
P ag e Es c_ P TT CS S
Paging Escalation Success Rate for PTTICS

D Op _ Pa ge E sc Su c c_ P TT IC S = 1 0 0. 0 * P a ge Es c Re s p_ PT T IC S/
P ag e Es c_ P TT IC S
Paging Escalation Success Rate for PTTSB1

D Op _ Pa ge E sc Su c c_ P TT SB 1 = 1 0 0. 0 * P a ge Es c Re s p_ PT T SB 1/
P ag e Es c_ P TT SB 1
Paging Escalation Success Rate for PTTSB2

D Op _ Pa ge E sc Su c c_ P TT SB 2 = 1 0 0. 0 * P a ge Es c Re s p_ PT T SB 2/
P ag e Es c_ P TT SB 2
Notes:
Prospect Traffic
PageEsc_BE PAGE_ESC (BE) IxEV_OHM
............................................................................................................................................................................................................................................................
Release 29 R29
PageEsc_CMCS PAGE_ESC (CMCS) IxEV_OHM

PageEsc_PTTCSS PAGE_ESC (PTT_CALL_SETUP_SIG) IxEV_OHM
PageEsc_PTTICS PAGE_ESC (PTT_INCALL_SIG) IxEV_OHM
PageEsc_PTTSB1 PAGE_ESC (PTT_SPEECH_BEARER1) IxEV_OHM
PageEsc_PTTSB2 PAGE_ESC (PTT_SPEECH_BEARER2) IxEV_OHM
PageEscResp_BE PAGE_ESC_RESP (BE) IxEV_OHM
PageEscResp_CMCS PAGE_ESC_RESP (CMCS) IxEV_OHM
PageEscResp_PTTCSS PAGE_ESC_RESP (PTT_CALL_SETUP_SIG) IxEV_OHM
PageEscResp_PTTICS PAGE_ESC_RESP (PTT_INCALL_SIG) IxEV_OHM
PageEscResp_PTTSB1 PAGE_ESC_RESP (PTT_SPEECH_BEARER1) IxEV_OHM
PageEscResp_PTTSB2 PAGE_ESC_RESP (PTT_SPEECH_BEARER2) IxEV_OHM
Paging De-Escalation Success Rate

Paging De-Escalation Success Rate for BE

DO p _P a ge De E sc Su c c_ B E = 1 00 .0 * P ag eD e Es cR e sp _ BE /P a ge De E sc _B E
Paging De-Escalation Success Rate for CMCS

DO p _P a ge De E sc Su c c_ C MC S = 1 00 . 0 * P ag e De Es c Re s p_ CM C S/
Pa g eD e Es c_ C MC S
Paging De-Escalation Success Rate for PTTCSS

DO p _P a ge De E sc Su c c_ P TT CS S = 1 0 0. 0 * P a ge De E sc R es p_ P TT CS S /
Pa g eD e Es c_ P TT CS S
Paging De-Escalation Success Rate for PTTICS

DO p _P a ge De E sc Su c c_ P TT IC S = 1 0 0. 0 * P a ge De E sc R es p_ P TT IC S /
Pa g eD e Es c_ P TT IC S
Paging De-Escalation Success Rate for PTTSB1

DO p _P a ge De E sc Su c c_ P TT SB 1 = 1 0 0. 0 * P a ge De E sc R es p_ P TT SB 1 /
Pa g eD e Es c_ P TT SB 1
............................................................................................................................................................................................................................................................
Release 29 R29
Paging De-Escalation Success Rate for PTTSB2

D Op _ Pa ge D eE sc S uc c _P TT S B2 = 10 0 .0 * Pa ge D eE s cR es p _P TT S B2 /
P ag e De Es c _P TT S B2
Notes:
Prospect Traffic
PageDeEsc_BE PAGE_DE_ESC (BE) IxEV_OHM
PageDeEsc_CMCS PAGE_DE_ESC (CMCS) IxEV_OHM
PageDeEsc_PTTCSS PAGE_DE_ESC (PTT_CALL_SETUP_SIG) IxEV_OHM
PageDeEsc_PTTICS PAGE_DE_ESC (PTT_INCALL_SIG) IxEV_OHM
PageDeEsc_PTTSB1 PAGE_DE_ESC (PTT_SPEECH_BEARER1) IxEV_OHM
PageDeEsc_PTTSB2 PAGE_DE_ESC (PTT_SPEECH_BEARER2) IxEV_OHM
PageDeEscResp_BE PAGE_DE_ESC_RESP (BE) IxEV_OHM
PageDeEscResp_CMCS PAGE_DE_ESC_RESP (CMCS) IxEV_OHM
PageDeEscResp_PTTCS PAGE_DE_ESC_RESP (PTT_CALL_SETUP_SIG) IxEV_OHM
S
PageDeEscResp_PTTIC PAGE_DE_ESC_RESP (PTT_INCALL_SIG) IxEV_OHM
S
PageDeEscResp_PTTSB PAGE_DE_ESC_RESP (PTT_SPEECH_BEARER1) IxEV_OHM
1
PageDeEscResp_PTTSB PAGE_DE_ESC_RESP (PTT_SPEECH_BEARER2) IxEV_OHM
2
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID

............................................................................................................................................................................................................................................................
Release 29 R29
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = BE

DO _ Pa g eE ff S ec t_ B E_ k = p a ge se c to r sk be / pa g es k be (P ag e
At t em p t = k = 1 - 8 )
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = CMCS

DO _ P ag eE f fS e ct _C M CS _k = p a ge se c to r sk cm c s / pa ge s kc mc s (P a ge
At t em p t = k = 1 - 8 )
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = PTTCSS

DO _ P ag e Ef fS e ct _P T TC S S_ k = pa g es ec t or s kp tt c ss / p ag e sk p tt cs s
(P a ge At te m pt = k = 1 - 8 )
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = PTTICS

DO _ P ag eE f fS e ct _P T TI CS _ k = pa ge s ec to r sk p tt ic s / pa g es k pt ti c s
(P a ge At te m pt = k = 1 - 8 )
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = PTTSB1

DO _ P ag e Ef fS e ct _P T TS B 1_ k = p ag e se ct o rs k pt ts b 1 / pa ge s kp tt s b1
(P a ge At te m pt = k = 1 - 8 )
Paging Efficiency by Sectors by Page Attempt and Paging Profile ID = PTTSB2

DO _ P ag eE f fS e ct _P T TS B2 _ k = pa ge s ec to r sk p tt sb 2 / pa g es k pt ts b 2
(P a ge At te m pt = k = 1 - 8 )
Notes:
1. Note that these metrics are calculated at the FMS level, but the counts in the equations
are at the IxEV_PageAttempt level. The counts in each calculation are for a given Page
Attempt k only ( k = 1-8). In each case, the counts are not rolled up over paging
attempts but are rolled up over OHMs. Each row above represents 8 metrics.
Prospect
Traffic
pageskbe PAGES (BE; Page attempt k, k = 1 - 8) IxEV_PageA
ttempts
pageskcmcs PAGES (CMCS; Page attempt k, k = 1 - 8) IxEV_PageA
ttempts
pageskpttcss PAGES (PTT_CALL_SETUP_SIG; Page attempt k, k = IxEV_PageA
1 - 8) ttempts
pageskpttics PAGES (PTT_INCALL_SIG; Page attempt k, k = 1 - 8) IxEV_PageA
ttempts
............................................................................................................................................................................................................................................................
Release 29 R29
pageskpttsb1 PAGES (PTT_SPEECH_BEARER1; Page attempt k, k IxEV_PageA

= 1 - 8) ttempts
pageskpttsb2 PAGES (PTT_SPEECH_BEARER2; Page attempt k, k IxEV_PageA
= 1 - 8) ttempts
pagesectorskbe PAGE_SECTORS (BE; Page attempt k, k = 1 - 8) IxEV_PageA
ttempts
pagesectorskcmcs PAGE_SECTORS (CMCS; Page attempt k, k = 1 - 8) IxEV_PageA
ttempts
pagesectorskpttcss PAGE_SECTORS (PTT_CALL_SETUP_SIG; Page IxEV_PageA
attempt k, k = 1 - 8) ttempts
pagesectorskpttics PAGE_SECTORS (PTT_INCALL_SIG; Page attempt IxEV_PageA
k, k = 1 - 8) ttempts
pagesectorskpttsb1 PAGE_SECTORS (PTT_SPEECH_BEARER1; Page IxEV_PageA
pagesectorskpttsb2 PAGE_SECTORS (PTT_SPEECH_BEARER2; Page IxEV_PageA
Data Over Signaling Effectiveness
D Op _ DO SE f f_ BE = 1 00 .0 * MT D OS S uc ce s s_ BE / m td os A tt em p ts 1 be
Notes:
up over paging attempts (1 - 8) and OHM. However, the denominator is for Page
Attempt 1 only. I.e., the denominator is not rolled up over paging attempts but is rolled
up over OHMs
Prospect
Traffic
MTDOSSuccess_BE MT_DOS_SUCCESS (BE) IxEV_PageA
ttempts
............................................................................................................................................................................................................................................................
Release 29 R29
mtdosAttempts1be MT_DOS_ATTEMPTS (BE; Page attempt = 1) IxEV_PageA

ttempts
DO p _D O SE ff _ CM CS = 10 0. 0 * M T DO S Su cc e ss _C M CS /
mt d os A tt em p ts 1c m cs
Notes:
up over OHMs
Prospect
Traffic
MTDOSSuccess_CMCS MT_DOS_SUCCESS (CMCS) IxEV_PageA
ttempts
mtdosAttempts1cmcs MT_DOS_ATTEMPTS (CMCS; Page attempt = 1) IxEV_PageA
ttempts

DO p _D O SE ff _ PT TC S S = 1 00 . 0 * M TD O SS uc c es s_ P TT C SS /
mt d os A tt em p ts 1p t tc s s
............................................................................................................................................................................................................................................................
Release 29 R29
Notes:
up over OHMs
Prospect
Traffic
MTDOSSuccess_PTTCSS MT_DOS_SUCCESS (PTTCSS) IxEV_PageA
ttempts
mtdosAttempts1pttcss MT_DOS_ATTEMPTS (PTTCSS; Page attempt = 1) IxEV_PageA
ttempts

D Op _ DO SE f f_ PT T IC S = 1 0 0. 0 * M T DO SS u cc es s _P T TI CS /
m td o sA tt e mp ts 1 pt t ic s
Notes:
up over OHMs
Prospect
Traffic
MTDOSSuccess_PTTICS MT_DOS_SUCCESS (PTTICS) IxEV_PageA
ttempts
mtdosAttempts1pttics MT_DOS_ATTEMPTS (PTTICS; Page attempt = 1) IxEV_PageA
ttempts
............................................................................................................................................................................................................................................................
Release 29 R29

DO p _D O SE ff _ PT TS B 1 = 1 00 . 0 * M TD O SS uc c es s_ P TT S B1 /
mt d os A tt em p ts 1p t ts b 1
Notes:
up over OHMs
Prospect
Traffic
ttempts
Page attempt = 1) ttempts

DO p _D O SE ff _ PT TS B 2 = 1 00 . 0 * M TD O SS uc c es s_ P TT S B2 /
mt d os A tt em p ts 1p t ts b 2
Notes:
up over OHMs
Prospect
Traffic
............................................................................................................................................................................................................................................................
Release 29 R29

ttempts
Page attempt = 1) ttempts
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID = BE
D Op _ DO SS u cc _B E _k = 1 0 0. 0 * mt d os Su c ce s sk be / m t do sA t te m pt sk b e
( Pa g e At t em pt = k = 1 - 8 )
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID - CMCS
D Op _ DO SS u cc _C M CS _ k = 1 00 .0 * m td os S uc ce s sk c mc s /
m td o sA tt e mp ts k cm c s ( Pa g e A tt em p t = k = 1- 8 )
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID =
PTTCSS
D Op _ DO SS u cc _P T TC S S_ k = 1 00 . 0 * m td o sS uc c es s kp tt c ss s /
m td o sA tt e mp ts k pt t cs s (P a ge A t te mp t = k = 1 - 8)
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID = PTTICS
D Op _ DO SS u cc _P T TI C S_ k = 1 00 . 0 * m td o sS uc c es s kp tt i cs /
m td o sA tt e mp ts k pt t ic s ( Pa g e At t em pt = k = 1 - 8 )
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID = PTTSB1
D Op _ DO SS u cc _P T TS B 1_ k = 1 00 . 0 * m td o sS uc c es s kp tt s b1 /
m td o sA tt e mp ts k pt t sb 1 ( P ag e A tt e mp t = k = 1- 8)
Data Over Signaling Success Rate by Page Attempt and Paging Profile ID = PTTSB2
D Op _ DO SS u cc _P T TS B 2_ k = 10 0 .0 * mt d os Su c ce s sk pt t sb 2 /
m td o sA tt e mp ts k pt t sb 2 (P a ge At te m pt = k = 1 - 8 )
............................................................................................................................................................................................................................................................
Release 29 R29
Notes:
1. Note that these metrics are calculated at the FMS level, but the counts in the equations
are at the IxEV_PageAttempt level. The counts in each calculation are for a given Page
Attempt k only ( k = 1-8). In each case, the counts are not rolled up over paging
attempts but are rolled up over OHMs. Each row in the above table represents 8
metrics.
Prospect
Traffic
mtdosAttemptskbe MT_DOS_ATTEMPTS (BE; Page attempt k, k = 1- 8) IxEV_PageA
ttempts
mtdosAttemptskcmcs MT_DOS_ATTEMPTS (CMCS; Page attempt k, k = 1- IxEV_PageA
8) ttempts
mtdosAttemptskpttcss MT_DOS_ATTEMPTS (PTT_CALL_SETUP_SIG; IxEV_PageA
Page attempt k, k = 1- 8) ttempts
mtdosAttemptskpttics MT_DOS_ATTEMPTS (PTT_INCALL_SIG; Page IxEV_PageA

attempt k, k = 1- 8) ttempts
mtdosAttemptskpttsb1 MT_DOS_ATTEMPTS (PTT_SPEECH_BEARER1; IxEV_PageA

mtdosAttemptskpttsb2 MT_DOS_ATTEMPTS (PTT_SPEECH_BEARER2; IxEV_PageA

mtdosSuccesskbe MT_DOS_SUCCESS (BE; Page attempt k, k = 1- 8) IxEV_PageA

ttempts
mtdosSuccesskcmcs MT_DOS_SUCCESS (CMCS; Page attempt k, k = 1- 8) IxEV_PageA

ttempts
mtdosSuccesskpttcss MT_DOS_SUCCESS (PTT_CALL_SETUP_SIG; Page IxEV_PageA

............................................................................................................................................................................................................................................................
Release 29 R29
mtdosSuccesskpttics MT_DOS_SUCCESS (PTT_INCALL_SIG; Page IxEV_PageA

mtdosSuccesskpttsb1 MT_DOS_SUCCESS (PTT_SPEECH_BEARER1; IxEV_PageA

mtdosSuccesskpttsb2 MT_DOS_SUCCESS (PTT_SPEECH_BEARER2; IxEV_PageA

Missed Termination Target of LoLat Packets

D Op _ Mi ss T rm Tr g tL o La tP k ts = 10 0 .0 * RL Lo L at P kt sM i ss ed T ar g et /
R LL o La tP k ts Rc v d
Notes:
Prospect
Traffic
RLLoLatPktsMissedTarget RL_LOLAT_PKTS_MISSED_TARGET IxEV_Sector
Carrier
RLLoLatPktsRcvd RL_LOLAT_PKTS_RCVD 1xEV_Sector
Carrier
Broadcast Registration Success Rate

Prospect Traffic Report Entity: IxEV_TP
D Op _ BC Re g Su cc = 1 00 .0 * A1 1 BC R eg Re p ly Su c cR c vd /
A 11 B CR eg R eq Se n t
............................................................................................................................................................................................................................................................
Release 29 R29
Notes:
Prospect
Traffic
A11BCRegReplySuccRcvd A11_BC_REG_REPLY_SUCC_RCVD IxEV_TP
A11BCRegReqSent A11_BC_REG_REQ_ SENT IxEV_TP
1.1Service Request Success Rate

Prospect Traffic Report Entity: IxEV_TP
DO p _S r vc Rq s tS uc c = 10 0. 0 * A 1 1B C Se rv i ce Re s po n se Su c cR cv d /
A1 1 BC S er vi c eR eq S en t
Note:
Prospect
Traffic
A11BCServiceResponseSuccRcvd A11_BC_SERVICE_RESPONSE_SUCC_RCVD 1xEV_Sector
Carrier
A11BCServiceReqSent A11_BC_SERVICE_REQ_SENT 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Overview
............................................................................................................................................................................................................................................................
Purpose

New metrics:
1xEV-DO Reverse Link Transmission Error Rate for CS and CV (p. 19-64)
1xEV-DO Average RLP Forward Link Data Rate - BE Traffic (kbps) (p. 19-84)
1xEV-DO Average RLP Forward Link User Data Rate - BE (kbps) (p. 19-88)
1xEV-DO Percentage of Band Width Used for Signaling (%) (p. 19-89)
1xEV-DO Average Number of Contending Users - BE (p. 19-90)
1xEV-DO Average Number of Contending Flows - EF (p. 19-91)
1xEV-DO Average Number of Contending Users (p. 19-92)
1x EV-DO Soft/Softer Handoff Overhead (Measured at TP) (p. 19-93)
Revised metrics:
1xEV-DO Reverse Link Data Re-Transmission Rate (p. 19-61)
1xEV-DO Reverse Link Re-Transmission Failure Rate (p. 19-62)
Obsolete metrics
1xEV-DO Soft/Softer Handoff Overhead with SBEVM (p. 19-119)

............................................................................................................................................................................................................................................................
2. Air Interface
1xEV-DO Paging Effectiveness by Sectors per Page Attempt
b. Connection Drop Metrics
............................................................................................................................................................................................................................................................
c. Handoff Metrics
d. Data Transmission Metrics
Reverse Link Transmission Error Rate for CS and CV
1xEV-DO Total Forward Link Physical Layer Data Transmitted -
SBEVM(MB)
1xEV-DO Composite Forward Link Physical Layer Data Transmitted
(MB)
1xEV-DO Average Forward Link Physical Layer Date Rate - SBEVM
(kbps)
1xEV-DO Average Forward Link Physical Layer Data Rate per User -
SBEVM (kbps)
1xEV-DO Average RLP Forward Link Data Rate - EVM (kbps)
1xEV-DO Average RLP Forward Link Data Rate - BE Traffic
(kbps)
1xEV-DO Average Forward Link RLP Data Rate per User - SBEVM
(kbps)
1xEV-DO Average RLP Forward Link User Data Rate - BE (kbps)
............................................................................................................................................................................................................................................................
1xEV-DO Percentage of Band Width Used for Signaling (%)

1xEV-DO Average Reverse Link Physical Layer Data Volume - EVM
(MB)
1xEV-DO Average Reverse Link Physical Layer Data Volume with
SBEVM (MB)
1xEV-DO Average Reverse Link Physical Layer Data Rate with SBEVM
(kbps)
e. Error Statistics
f. Power Control
EVM
EVM
EVM
EVM
EVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
............................................................................................................................................................................................................................................................
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
SBEVM
g. Capacity Management Metrics
1xEV-DO Average Number of Contending Users - BE
1xEV-DO Average Number of Contending Flows - EF
1xEV-DO Average Number of Contending Users
1xEV-DO Soft/Softer Handoff Overhead (Measured at TP)
3. Quality of Service (QoS) Metrics
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

source RNC), etc.
group transfers.
Formula

INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD
------------------------------------------------------------------------------------------------X 100
SESSION_SETUP_REQ + INT_SUBNET_IDL_TRFR_ATTMPT +
Count Definitions

Message Received (new & prior sessions). Pegged when the AT
acknowledges a UATI assignment message sent by the AN in response to a
............................................................................................................................................................................................................................................................
UATI request.
incremented each time a UATI Complete is received or any access channel
packet received with just assigned UATI for a session transfer within an
RNC Group.
the same RNC Group.
INT_SUBNET_IDL_TRFR_ATTMPT = This count is incremented for each attempt to
for the HDR Cell sector-carrier that received the UATIRequest. This count
is used to measure idle transfer activity. This count should be pegged when
an A13-Session Information Request is generated in the target AN,
omitting the number of such requests that are associated with the Prior
Session method. Note that if the A13 message is repeated, the count is only
pegged once.
With implementation of 12456.0, this count shall exclude the session transfer for load

............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------------X 100
Count Definitions

color code)
sessions)
incremented each time a UATI assignment is sent for a session transfer
within an RNC Group.
............................................................................................................................................................................................................................................................
the same RNC Group.

connections.
Formula
360
Count Definitions
approximate.

intervention.
............................................................................................................................................................................................................................................................
if it was used to access the network while in a dormant state right after the inter-subnet
idle
handoff trigger. Hence, a relatively high rate of inter-RNC idle handoff failures may not
be that egregious.
Formula

------------------------------------------------------------------------------------------------- X100
............................................................................................................................................................................................................................................................
Count Definitions

for the HDR Cell sector-carrier that received the UATIRequest.
A13-Session Information Request is generated in the target AN, omitting
the number of such requests that are associated with the Prior Session
method. Note that if the A13 message is repeated, the count is only pegged
once.
inter-subnet or inter-RNC idle transfer attempts pegged on the new RNC
(target RNC) for the prior session method. The count is pegged when the
target RNC receives a UATI Request message that contains a RATI
assigned by a different RNC.
idle transfer attempt using the Color Code Method or the Assign First
Method that failed because the previous subnet did not respond and is the
total of all such idle transfer failures for the HDR Cell sector-carrier. This
count is used to measure idle transfer failures because the old subnet did
not respond to the transfer request. The count should be pegged after both
request attempts have failed.
RNC idle handoff failures that occur because the PCF on the new RNC
could not establish an A11 (also known as R-P) connection with the
original PDSN. In essence, a new UATI is assigned successfully but the
connection to the PDSN failed subsequently.
............................................................................................................................................................................................................................................................
connection and soft/er handoff failures, this accounts for all inter-RNC idle
handoff attempts that failed for reasons not accounted for by the other
specific failure counts. One scenario where this is seen quite often is the
ping pong scenario. When RNC2 times out waiting for the UATI Complete
message in response to the UATI Assignment message because the AT has
moved to a different RNC (RNC1 or RNC3), it declares it as an Other
failure. Of course, the timeout may also happen due to poor RF conditions
or if RNC2 did not send the UATI Assignment message with proper
message sequence number (often is the case with the Assign First method
where RNC has to guess a sequence number since it has not yet
communicated with the old RNC and has no way of knowing the last
sequence number used to communicate with the AT). This count may also
reflect blocking where the target RNC has no more spare UATIs to assign
to the requesting AT.
as the name suggests, the PCF A11 IP address of the old RNC is not
provisioned on the new RNC. The problem is applicable only for the Color
Code method of the inter-RNC Idle handoff, which requires the new RNC
to perform a look up of old RNCs IP address in a locally stored mapping
table. The lookup is performed using the color code retrieved from the old
UATI sent by the AT as part of the UATI Request message. If the Assign
First method is used instead, the AN first assigns the UATI to the AT and as
part of the UATI Assignment message, instructs the AT to directly report
back the old RNCs PCF A11 address. Using this information, the new
RNC then attempts to initiate the session transfer from the old RNC. In
this case, no lookup table is needed at the new RNC, and hence this type of
failure does not apply in case of the Assign First method.
............................................................................................................................................................................................................................................................
Code method is when the PDSN's IP address reported in the A13 Session
Information Response message by the source RNC is invalid (i.e.,
255.255.255.255 or NULL).
RNC receives a A13 Reject message from the old RNC in response to a
session transfer request. One scenario where this may occur is when the AT
has gone back to the old RNC (call it RNC 1) or a third RNC (call it RNC
3) before it could send a UATI Complete to the new RNC (call it RNC 2).
In this case, the new RNC (RNC 2) does not yet consider itself to be in
control of ATs session and hence, would reject the subsequent session
transfer request (from RNC1 or RNC3 in this rapid handoff scenario).
Transfer failures due to no response from the previous subnet using the
Transfer failures due to a failure to find the source AN because of
insufficient information in the Configuration Request message using the

sectorcarrier
basis.
Formula

---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
with PDSN.

high.
Formula

--------------------------------------------------------------------- X 100
Count Definitions

attempts.
............................................................................................................................................................................................................................................................

session setup.
Formula

--------------------------------------------------------------------------------------------------- X 100
CONFIG_NEGO
Count Definitions
place.

............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------- X 100
Count Definitions

number of successful session balances during the SM collection interval at
the originating OHM because the Intra-RNC UATI Session Balance
Threshold was exceeded. This count includes new session request and idle
transfer scenarios.The session balance is considered successful when the
originating OHM receives confirmation message from the target OHM
indicating the session balance request has been accepted by the target
OHM.
of UATI session balance requests sent to another OHM within the same
RNC during the SM collection interval at the originating OHM because the
Intra-RNC UATI Session Balance Threshold was exceeded. This count
includes new session request and idle transfer scenarios. If a session OHM
balance request is rejected by a target OHM, the requesting OHM may
retry to transfer the session to another target OHM. In this scenario the
count is incremented only once.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

Formula

------------------------------------------------------------------------------ X 100
Count Definitions
end user.
............................................................................................................................................................................................................................................................

PDSN.

on the R-P link.
handoff.
failures.
Formula

-------------------------------------------------------- X100
RP_CONN_ATTMPTS
Count Definitions

connection with the PDSN based on requests from the AT. Basically, any
PPP packet from the AT that requires transmission to the PDSN for which
an A10 link does not exist results in a R-P connection attempt.
Furthermore, an attempt to transfer an existing R-P session between PCFs
on the source and target RNCs as part of an inter-RNC Idle handoff will
also increment this peg. Any reactivations from dormancy, whether AT or
AN initiated, are not included in the count.
............................................................................................................................................................................................................................................................
(BCMCS).
failure could either be due to a reject message from the PDSN, or a
response timeout (PDSN not reachable due to addressing error, PDSN not
in service).
(BCMCS).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

3G1X.
rate.
level.
Formula

............................................................................................................................................................................................................................................................
---------------------------------------------------------------------------------------------------X 100
Count Definitions
channel.)
channel.)
connection request.
AN_INIT_CONN_REQ =
............................................................................................................................................................................................................................................................


for
sectorcarrier
basis and are pegged at the sector-carrier that received the connection request.
Formula

---------------------------------------------------------------------------------------------------X 100
Count Definitions
established
............................................................................................................................................................................................................................................................

cross
Formula

----------------------------------------------------------------------------------------------------X 100
Count Definitions
channel.)
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
............................................................................................................................................................................................................................................................

established

level.
Formula

---------------------------------------------------------------------------------------------------- X 100
FAST_CONNECT
Count Definitions
channel).
FAST_CONNECT =
............................................................................................................................................................................................................................................................

messaging failure.
Formula
--------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions

this sector-carrier in response to AN-Initiated Connection Requests either
this sector-carrier in response to AT-Initiated Connection Requests either
sectorcarrier
sectorcarrier
sector-carrier
sector-carrier
sector-carrier
sector-carrier
this sector-carrier in response to AN-Initiated Connection Requests
received on this sector-carrier
this sector-carrier in response to AT-Initiated Connection Requests received
on this sector-carrier
............................................................................................................................................................................................................................................................


effective with R26.
Formula

-----------------------------------------------------------------------------------------------------X100
Count Definitions
............................................................................................................................................................................................................................................................

messaging failure.
cross
Formula

-------------------------------------------------------------------------------------------------- X 100
Count Definitions
assignment).
............................................................................................................................................................................................................................................................

assignment).
AN_INIT_CONN_REQ =
AT_INIT_CONN_REQ =
session setup

ATinitiated)
that failed. It is defined as 100 - established connection rate (see section 4.2.1.1).
releases.
Formula
Count Definitions

ATinitiated)
that failed. It is defined as 100 - established connection rate - peg (see section
............................................................................................................................................................................................................................................................
Formula
Count definitions

detailed formula in the above metric There are no peg counts explicitly used in this
metric. See section 1xEV-DO Established Connection Rate - User - Peg (%) (p.
19-23) for the counts included in the established connection rate - peg metric. (p.
19-30) but it is recommended
Formula

------------------------------------------------------------------------------------------------- X 100
Count definitions
............................................................................................................................................................................................................................................................

connection request.

............................................................................................................................................................................................................................................................
Formula

------------------------------------------------------------------------------------------------- X 100
Count definitions
established.

cross
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
............................................................................................................................................................................................................................................................
established

received
received

............................................................................................................................................................................................................................................................
of Service (QoS). In addition to the simple paging process used before, there are now up
to 8 configurable page attempts per pageable profile ID for QoS. The paging process
ID.
to provide an overall effectiveness of packet delivery based on uniques page attempts.
This revision to the formula is effective with R29.
Formula

--------------------------------------------------------------------------------------------------- X 100
Count Definitions

............................................................................................................................................................................................................................................................
pegging. This count is reported per OHM-Profile ID-page attempt. This
count, in conjunction with the number of pages or connection requests
received, is used to monitor the effectiveness and efficiency of each page
attempt in the Paging sequence. This information can be used to optimize
the paging strategy setting.
is reported per OHM-Profile ID-page attempt.
Attempt.
attempt sequence is aborted due to override from page of higher priority
ProfileID. This count is pegged only when the QoS Paging is active for a
ProfileID. This count is reported per OHM-Profile ID.

The formula will be repeated 8 times, once for each page attempt. The metrics can be
used to monitor the success rate of individual page attempts to optimize the paging
strategy for each Profile ID.
This metric is new in R29 but can be used in R28.
............................................................................................................................................................................................................................................................
Formula

-----------------------------------------------------------------------------X 100
Count Descriptions

pegging. This count is reported per OHM-Profile ID. This count, in
conjunction with the number of pages or connection requests received, is
used to monitor the effectiveness and efficiency of each page attempt in the
Paging sequence. This information can be used to optimize the paging
strategy setting.

area.
Formula

-----------------------------------------------------------------------------X 100
Count Descriptions

............................................................................................................................................................................................................................................................
Active Set Paging to another paging area. Last Seen RNC Paging area is
used for default paging or when QoS Paging is active for a profileID but
Paging Enhancements Enable is set to No. The paging area configured for
the subsequent attempt, if non-blank and not Last Active Set, is used when
Paging Enhancements Enable is set to Yes. The method switch occurs
when the T_Page1 timer expires before the AT's next wakeup cycle. Note
that BEpID will be used for pegging when default paging is used.
This count is used to monitor if the T_Page1 timer is set properly.

Formula

-----------------------------------------------------------------------------X 100
Count Descriptions

Last Active Set. Paging de-escalation can only occur on the first page
attempt.

attempt.. The metrics can be used to optimize the paging strategy settings.
The metric can only be calculated per RNC Group-profile ID basis since the SM counts
are pegged in different OHMs across the RNC Group.
............................................................................................................................................................................................................................................................
Formula

-----------------------------------------------------------------------------
Count Descriptions
a given attempt K within the Paging Sequence. For example, if a page
attempt for attempt K triggers a page sent to 10 different sectors, then this
count is incremented by 10 for attempt K. K varies from 1 to 8. Therefore,
there are 8 counts, one for each value of K. Note that if the default paging
of the service node is used, then the BEpID will be used for pegging.

to an AT.
the initial page.
metric is effective beginning with R29.
Formula

MT_DOS_SUCCESS)
-------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Descriptions
Attempt.


ID. The formula will be repeated 8 times, once for each page attempt.. The metrics can
me used to monitor the success rate of individual DOS page attempts to determine how
many attempts on average are needed for each Profile ID.
Formula

-----------------------------------------------------------------------------------X 100
Count Descriptions
Attempt.
............................................................................................................................................................................................................................................................


sectorcarrier
level. These counts measure the number of active connections during the
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

Formula

---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL =
............................................................................................................................................................................................................................................................

connection request.
............................................................................................................................................................................................................................................................
Handoff Metrics
............................................................................................................................................................................................................................................................

Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions
sector).
............................................................................................................................................................................................................................................................

procedure.
procedure.

("handouts")
perspective. The peg counts are defined on a per sector-carrier basis.
............................................................................................................................................................................................................................................................
Formula

-------------------------------------------------------------------------------------------------- X 100
Count Definitions
HHOFF_ATTMPT_REQ =
............................................................................................................................................................................................................................................................

Formula

------------------------------------------------------------------------------------------------ X 100
Count Definitions

sectorcarrier
............................................................................................................................................................................................................................................................

assignment
assignment

Formula

--------------------------------------------------------------------------------------------------- X 100
Count Definitions

interfrequency
sector-carrier.

interfrequency
............................................................................................................................................................................................................................................................

sector-carrier.
sectorcarrier
due to no response from the AT.

............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions

of legs is reached.

there is no messaging involved with the AT or an element outside the AN between the
time
sources.
............................................................................................................................................................................................................................................................
the cell).
Formula

HHOFF_TCA_SENT_REQ)
------------------------------------------------------------------------------------------ X 100
Count Definitions
HHOFF_ATTMPT_REQ =

............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions


Formula

............................................................................................................................................................................................................................................................
-------------------------------------------------------------------------------------- X 100
Count Definitions

interfrequency

Formula

------------------------------------------------------------------------------ X 100
Count Definitions
TCA sent by the AN
............................................................................................................................................................................................................................................................
procedure.

Formula

----------------------------------------------------------- X 100
Count Definitions
sent by the AN.

............................................................................................................................................................................................................................................................

R24 and later.
Formula

--------------------------------------------------------------------------------- X 100
Count Definitions
TCA sent by the AN.

............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------------------- X 100
Count Definitions
sent by the AN.
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

in RLP NAKs.
Formula
RLP_RETXED_FTC
RLP_TXED_FTC
Count Definitions

............................................................................................................................................................................................................................................................
channel.

in RLP NAKs.
releases.
............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------X 100
Count Definitions


RLP NAKs.
............................................................................................................................................................................................................................................................
releases.
Formula

---------------------------------------------------------------------------------------------------- X 100
Count Definitions

sector-carrier.
Conversational Speech (with or without ROHC) RLP octet that is retransmitted
Conversational Video (with or without ROHC) RLP octet that is retransmitted
............................................................................................................................................................................................................................................................
sector-carrier.
octets.

octets.

perfectly fine.
The formula is changed in R30 to reflect the new peg counts and is not applicable to prior
............................................................................................................................................................................................................................................................
releases. The new formula only includes BE and SMC flows since CS and CV do not
have re-transmission on the reverse link.
Formula

(MISSING_RLP_REQ_RTC_BE + MISSING_RLP_REQ_RTC_SMC)
-----------------------------------------------------------------------------------------X100
(RLP_RXED_RTC- RLP_RCVD_RTC_CPS - RLP_RCVD_RTC_CS -
RLP_RCVD_RTC_CV)
Count Definitions
MISSING_RLP_REQ_RTC_BE = This count is incremented for each Best

Effort RLP octet whose transmission is requested via Nak. It is the total
of all BE octets requested in Naks for the reverse traffic channels for a
sector-carrier.
MISSING_RLP_REQ_RTC_SMC = This count is incremented for each SMC RLP octet
whose transmission is requested via Nak. It is the total of all SMC octets requested in
Naks for the reverse traffic channels for a sector-carrier. This count is pegged against the
DRC pointed sector.
RLP_RXED_RTC = The total number of original RLP octets received on the
reverse link traffic channel of a given sector. It is raw user payload
plus any overhead bytes from protocol layers above RLP
(Application/TCP/IP/PPP). It does not include RLP layer overhead bytes,
RLP layer re-transmissions or any data lost in transit even after the
single RLP retry by the AT.
RLP_RCVD_RTC_CPS = This count shall be incremented for each CPS RLP octet
received at the TP. It is the total of all octets received on the reverse
traffic channels for a sector-carrier.
RLP_RCVD_RTC_CS = This count shall be incremented for each CS RLP octet
RLP_RCVD_RTC_CV = This count shall be incremented for each CV RLP octet

............................................................................................................................................................................................................................................................

retransmission
from the AT got corrupted). However, the issues that led to the retransmissions
in the first place may also contribute to a higher re-transmission failure rate
releases. Note that this metric is only for retransmission failures of BE and SMC octets
since CS and CV octets are not retransmitted. Separate peg counts are available to
measure missing octets never received for CS and CV flows.
Formula

(MISSING_RLP_NEVER_RXED_RTC_BE +
MISSING_RLP_NEVER_RXED_RTC_SMC)
-------------------------------------------------------------------------------------------X100
Count Definitions
MISSING_RLP_NEVER_RXED_RTC_BE = This count is incremented for each BE RLP

octet that was missing from the RLP receive buffer when the buffer's contents were passed
to the higher layer protocol. It is the total of all BE octets not received for the reverse
traffic channels on a sector-carrier.
MISSING_RLP_NEVER_RXED_RTC_SMC = This count is incremented for each SMC
RLP octet that was missing from the RLP receive buffer when the buffer's contents were
passed to the higher layer protocol. It is the total of all SMC octets not received for the
reverse traffic channels on a sector-carrier. This count is pegged against the DRC pointed
sector.
MISSING_RLP_REQ_RTC_BE = This count is incremented for each Best Effort RLP
octet whose transmission is requested via Nak. It is the total of all BE octets requested in
Naks for the reverse traffic channels for a sector-carrier.
............................................................................................................................................................................................................................................................

DRC pointed sector.
1xEV-DO Reverse Link Transmission Error Rate for CS and CV

This metric provides a measure of the error rate for CS and CV packets on the reverse link.
CS and CV packets are not retransmitted if the packet does not reach the AN. However,
the missing packets are noted and the appropriate counts are pegged.
The metric is new and effective in R30 and is not applicable to prior releases. Note that
this metric is only for transmission failures of CS and CV octets. There are separate
metrics for the retransmission rate and retransmission failure rates of BE and SMC octets.
Formula
DO reverse transmission error rate for CS and CV (%) =

(MISSING_RLP_NEVER_RXED_RTC_CV +
MISSING_RLP_PACKET_NEVER_RXED_RTC_CS)
-------------------------------------------------------------------------------------------X100
(RLP_RCVD_RTC_CV+ RLP_RCVD_RTC_CS)
Count Definitions
MISSING_RLP_NEVER_RXED_RTC_CV = This count is incremented for each CV

passed to the higher layer protocol. It is the total of all CV octets not received for the
reverse traffic channels on a sector-carrier.
MISSING_RLP_PACKET_NEVER_RXED_RTC_CS = This count is incremented for

each CS RLP octet that was missing from the RLP receive buffer when the buffer's
contents were passed to the higher layer protocol. It is the total of all CS octets not
received for the reverse traffic channels on a sector-carrier. This count is pegged against
the DRC pointed sector.
RLP_RCVD_RTC_CV = This count is incremented for each CV RLP octet received on
the RL. It is the total of all CV octets for the reverse traffic channels for a sector-carrier.
This count is pegged against the DRC pointed sector.
RLP_RCVD_RTC_CS = This count is incremented for each CS RLP octet received on the
RL . It is the total of all CS octets for the reverse traffic channels for a sector-carrier. This
count is pegged against the DRC pointed sector.
............................................................................................................................................................................................................................................................

layer
Formula

------------------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions

............................................................................................................................................................................................................................................................



Formula

-----------------------------------------------------------------------------------------------------------
10 ^ 6
Count Definitions

and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................

and Rev A traffic.
and Rev A traffic.
and Rev A traffic.

............................................................................................................................................................................................................................................................

=
+
--------------------------------------------------------------------------------------- =
10 ^ 6

............................................................................................................................................................................................................................................................
sector.
assumption
higher rates.
............................................................................................................................................................................................................................................................
hardware, etc.).
Formula

------------------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

............................................................................................................................................................................................................................................................
Alternatively, the physical layer transmitted bytes can be utilized to provide a general
view
............................................................................................................................................................................................................................................................
assumption
higher rates.
hardware, etc.).
EVM.
Formula

------------------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................


=
+
--------------------------------------------------------------------------------------------------
sectorcarrier.
It uses the active usage peg count which measures the number of users either
............................................................................................................................................................................................................................................................
Formula
-----------------------------------------------------------------------------------------------------------
Count Definitions

and Rev A traffic.E
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................

transmission.

............................................................................................................................................................................................................................................................
users.
A large value indicated by this metric does not necessarily mean congestion on the air
link.
A single user doing FTP downloads throughout the hour is expected to drive the
utilization
Formula
Count Definitions


per second.
The metric carries a sector level? connotation rather than a per user?
view given the denominator includes the total traffic channel slots used in an hour. So
it reflects the average RF conditions the sector serves. The RLP byte count is closer to the
............................................................................................................................................................................................................................................................
actual user traffic with less overhead than either MAC layer or physical layer packet
retransmitted
RLP packets not reaching the end user (typically ~0.02% for a 1% retransmission
rate).
above issues, RLP data rate should only be viewed as an estimate of actual rate, although
it is not far off the mark especially at moderate to high loading points.
............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------
Count Definitions
per second.
The metric carries a ector level ? connotation rather than a er
user ? view given the
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------------------------------
Count Definitions
octets.
octets.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................

Formula

------------------------------------------------------------------------------------------------------------
1xEV-DO Average RLP Forward Link Data Rate - BE Traffic (kbps)

This metric gives the average data rate for Best Effort (BE) traffic on the forward link at
the RLP layer in kilobits per second
and is defined only for the one hour measurement interval. It cannot be directly summed
to obtain results for longer time periods. The individual counts must be rolled up and then
the data rate can be calculated. The peg counts are measured at the RLP layer.
The metric carries a sector-carrier level connotation rather than a per user view given
the denominator includes the total traffic channel slots used for BE data in an hour. So it
reflects the average RF conditions the sector-carrier serves. The RLP byte count is closer
to the actual user traffic with less overhead than either MAC layer or physical layer packet
of RF conditions at the time the user was served. Note that there are 2,160,000 slots in one
milliseconds).
............................................................................................................................................................................................................................................................
regarding the use of the metric discussed in the prior metrics for the EVM do not apply to
sector-carriers equipped with an SBEVM. The only remaining potential source of
This metric is new in R30 and is not applicable to prior releases. Note that the same
packet can carry BE and EF traffic and both busy slots counts would be pegged. So the
sum of the total busy slots for BE plus total busy slots for EF won't necessarily equal the
total busy slots count.
Formula
DO RLP Fwd Link Data Rate BE Traffic (kbps) =

(EVM_RLP_TXED_FTC_BE * 8) / 1000
------------------------------------------------------------------------------------------------------------
(EVM_TOTAL_BUSY_SLOTS_BE * 0.001667)
Count Definitions
octet transmitted to an AT and it shall not include any octets that may be used for padding
at the MAC layer. It is the total of all octets transmitted on the forward traffic channels for
a sector-carrier.
This count shall not include any of the re-transmitted RLP octets.
EVM_TOTAL_BUSY_SLOTS_BE = This count shall measure the total number of
busy slots on the forward link used for BE (Best Effort) traffic data
transmission for the sector-carrier.
............................................................................................................................................................................................................................................................
Formula

----------------------------------------------------------------------------------------------------
Count Definitions
octets.
octets.
............................................................................................................................................................................................................................................................
once per slot.
Formula

------------------------------------------------------------------------------------------------------------
Count Definitions
octets.
............................................................................................................................................................................................................................................................

octets.
transmission.

This metric provides the average user data rate for BE traffic at the RLP layer in kilobits
per second.
The counts are measured at the TP at a sector-carrier level. Measurements are taken every
267 milliseconds and summed at the end of the measurement interval to represent the total
number of RLP bytes sent to the BTS for that sector-carrier and the total number of BE
users with data being sent or waiting to be sent to the BTS for that sector-carrier. The
measurements are made on a sampling of approximately 10% of the active connections
and only data rates above 20 kps are included.
The peg counts are on a sector-carrier basis. This metric is new and effective in R30.0.
............................................................................................................................................................................................................................................................
Formula
DO Average RLP Forward Link User Data Rate - BE (kbps) =

(RLP_SENT_TO_BTS_AT_TP_BE * 8) / 1000
------------------------------------------------------------------------------------------------------------
(USER_PRESENT_AT_TP_BE * 0.267)
Count Definitions
RLP_SENT_TO_BTS_AT_TP_BE = This count measures the total number of Best Effort

(BE) RLP octets sent to the BTS by the TP for all the sampled connections.
For each sampled connection, RNC/TP shall keep track of the RLP octets being sent to the
BTS for BE user data for each sampling interval if the BE user data sent is greater than the
defined threshold for each sampling interval.
The measurements collected shall not include the re-transmitted data.
The threshold used for each sampling interval is equivalent to 20kbps.
USER_PRESENT_AT_TP_BE = This count measures the total number of Best Effort
(BE) users present at the TP for the sampled connections if the user's BE data is greater
than the defined threshold or the user has data arrived but waiting to be sent to the BTS
during the sampling interval.
For each sampling measureing interval, this count shall be incremented by the number of
BE users that either have data arrived waiting to be sent, or sent during the interval for all
the sampled connections.
The threshold used for each sampling interval is equivalent to 20kbps.

This metric provides the percentage of band width not used for traffic packets, i.e., for
control channel signalling messages. The computation includes asynchronous,
synchronous and sub-synchronous signalling messages.
The peg counts are defined on a sector-carrier basis. This metric is new and effective in
R30.
Formula
DO Percent BW Used for Signaling (%) =
(EVM_CC_SLOTS_SYNC_MSG_XMIT +
EVM_CC_SLOTS_SUBSYNC_MSG_XMIT +
EVM_CC_SLOTS_ASYNC_MSG_XMIT)
----------------------------------------------- ------------------------------X 100
2,160,000
............................................................................................................................................................................................................................................................
Count Definitions
EVM_CC_SLOTS_SYNC_MSG_XMIT = This count measures the total number of slots

used for sending the synchronous signaling messages on the Control Channel for a sector-
carrier.
This count shall not include the slots used for sending the sub-synchronous signaling
messages.
EVM_CC_SLOTS_SUBSYNC_MSG_XMIT = This count measures the total number of

slots used for sending the sub-synchronous signaling messages on the Control Channel for
a sector-carrier.
EVM_CC_SLOTS_ASYNC_MSG_XMIT = This count measures the total number of

slots used for sending the asynchronous signaling messages on the Control Channel for a
sector-carrier.

This metric represents the average number of BE users contending for slot usage. It is
calculated from the average number of active users with BE data to send that are eligible
to be selected by the scheduler and the number of busy slots when BE users are present.
The peg counts are defined on a per sector-carrier basis. This metric is new and effective
in R30.
Formula
DO Average Number of Contending Users - BE =
EVM_AVG_ELIG_USER_BE / 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_SLOTS_BE_USER_PRESENT / 2,160,000
Count Definitions
EVM_AVG_ELIG_USER_BE = This count records the average number of active users

per slot that are eligible to be selected by the scheduler for the sector/carrier.
For each slot, modem/DSP increments the counter by the number of BE flows which have
data waiting to be scheduled and it shall not include the BE flows that are already in the
process of transmission and without data waiting. At the end of SM collection interval, the
system shall calculate the average value by using the summation of all such flows divided
by the total number of slots.
............................................................................................................................................................................................................................................................
This count must be divided by 10^6 to obtain the average number of scheduler eligible
users per slot.
EVM_TOTAL_BUSY_SLOTS_BE_USER_PRESENT = This count shall measure the
total number of busy slots on the forward link when BE (Best Effort) users are present for
the sector-carrier.
For each slot that's used for user data traffic, this count shall be incremented by 1 if the slot
is used for transmitting BE user data or if there is BE user waiting in the queue.

This metric represents the average number of EF flows contending for slot usage. It is
calculated from the average number of active EF flows that are eligible to be selected by
the scheduler and the number of busy slots when EF flows are present.
in R30.
Formula
DO Average Number of Contending Flows - EF =
EVM_AVG_ELIG_FLOW_EF / 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_SLOTS_EF_USER_PRESENT / 2,160,000
Count Definitions
EVM_AVG_ELIG_FLOW_EF = This count measures the average number of active EF

(Expedited Forwarding) flows that are eligible to be selected by the scheduler for the
sector-carrier.
For each slot, modem/DSP increments the counter by the number of EF flows which have
data waiting to be scheduled and it shall not include the EF flows that are already in the
When DRC erasure mapping algorithm is implemented and an erasure-mapped user is

served by OTA softer-multicasting, this count shall be pegged on all the eligible multicast
legs where the user has EF flow data waiting.
............................................................................................................................................................................................................................................................
This count is reported as average * 10^6.

EVM_TOTAL_BUSY_SLOTS_EF_USER_PRESENT =
This count shall measure the total number of busy slots on the forward link when EF
(Expedited Forwarding) users are present for the sector-carrier.
is used for transmitting EF user data (CS, CV, or Conversational PTT Speech) or if there is
EF user waiting in the queue.

served by OTA softer-multicasting, this count shall be pegged on all the multicast legs for
each slot that's qualified for the same condition above.

This metric represents the average number of users contending for slot usage, regardless
of the type of data being sent. It is calculated from the average number of active users that
are eligible to be selected by the scheduler and the number of busy slots.
in R30.
Formula
DO Average Number of Contending Users =
EVM_AVG_ELIG_USER_ALL/ 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^8
Count Definitions
EVM_AVG_ELIG_USER_ALL = This count measures the average number of active

users that are eligible to be selected by the scheduler for the sector-carrier regardless of the
traffic type.
For each slot, modem/DSP increments the count by the number of users who have data
waiting to be scheduled and it shall not include the users that are already in the process of
transmission and without data waiting. If a user has multiple flows, e.g. BE and EF in the
backlog, the count shall be incremented only by 1. At the end of SM collection interval,
the system shall calculate the average value by using the summation of all such users
............................................................................................................................................................................................................................................................
divided by the total number of slots.

legs where the user has EF data waiting, regardless of the state of this user's BE data. If the
erasure-mapped user only has BE data waiting, this count shall be pegged against last
known DRC pointed sector.
This count is reported as average * 10^6.
EVM_TOTAL_BUSY_PCNT_SLOTS = This count shall measure the percentage of

physical layer slots actually used for forward link traffic data transmission. The count
must be divided by 10^6 to obtain percentage.
1x EV-DO Soft/Softer Handoff Overhead (Measured at TP)

This metric is a ratio of the total number of air links on a sector-carrier to
the number of DRC pointed links on it, as measured at the TP. For example, a ratio of 2.5
indicates that for every user that this sector-carrier is serving on the forward link, it
has 1.5 other users who are pointing their DRCs to some other sector-carriers.
overlap can be used to potentially look for the presence of pilot pollution in
the region.
From the reverse link perspective, the metric may also be useful in cell
capacity forecast. Note that in 1xEVDO, additional soft/softer legs do not consume
any resources on the forward link; they merely act as interferers.
The peg counts are defined on a sector-carrier basis and measured at the TP. This metric is
new and effective in R30 and is applicable to all connections, both Rel 0 and Rev A for
any type of EVM. This metric replaces the previous metric which is obsolete as of R30.
Formula
DO Soft/Softer Handoff Overhead - Measured at TP =
TOT_ACTIVE_CONN_PER_SECTOR_TP
------------------------------------------------------------------------------------------------------------
TOT_DRC_POINTED_ACTIVE_CONN_PER_SECTOR_TP
............................................................................................................................................................................................................................................................
Count Definitions
TOT_ACTIVE_CONN_PER_SECTOR_TP = This count measures the total number of

active connections for a sector-carrier that the sector is in the active set for the connection.
Every 10 seconds, RNC/TP shall increment the count by one for each active connection
against all the legs in the active set and at the end of SM collection interval the
accumulated value for the total active connections shall be reported.
TOT_DRC_POINTED_ACTIVE_CONN_PER_SECTOR_TP = This count measures the
total number of active connections for a sector-carrier that the sector is the DRC-Pointed
sector for the connection.
against the DRC-pointed sector and at the end of SM collection interval the accumulated
value for the total DRC-Pointed active connections shall be reported.
Formula

------------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions

............................................................................................................................................................................................................................................................

Formula

----------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions

............................................................................................................................................................................................................................................................


............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------------------------------------
8 * 10^6
rates.
Formula:

---------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

sectorcarriers
equipped with an SBEVM. The metric is defined on a per sector-carrier basis.
of 6.6 ms.
Formula

............................................................................................................................................................................................................................................................
----------------------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................


----------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
NUM_SUBPKTS_RL_12288) * 0.00667]

Formula

----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

Formula

----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

----------------------------------------------------------------------------------------
+
............................................................................................................................................................................................................................................................

NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................
Error Statistics
............................................................................................................................................................................................................................................................

at the AT).
level.
Formula
Count Definitions

............................................................................................................................................................................................................................................................

link.
Formula
------------------------------------------------------- X 100
RL_LOLAT_PKTS_RCVD
Count Definitions

............................................................................................................................................................................................................................................................
Power Control
............................................................................................................................................................................................................................................................

Formula

--------------------------------------------------------------------------------
Count Definitions

basis.
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------------
Count Definitions

dB/8.
Formula

---------------------------------------------------------------------------------
Count Definitions

count are dB/8.
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions
Formula

---------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................
Formula

---------------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

1xEV-DO.
divided again.
Formula
360
Count Definitions

............................................................................................................................................................................................................................................................

Formula

Count Definitions

(average * 100).
............................................................................................................................................................................................................................................................

connections.
metric, DO Soft/Softer Handoff Overhead - Measured at TP should now be used. The new
metric is valid for both EVM and SBEVM and is expected to be more accurate since the
counts are all measured at the TP.
Formula

-----------------------------------------------------------------------
Count Definitions

............................................................................................................................................................................................................................................................
(average * 100).
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

beginning in R28.
Formula

ROR_ACCEPTED
-------------------------------------X100
ROR_RECEIVED
Count Definitions


Formula

RESV_ADMITTED_FL_CS
------------------------------------------------------------------------ X 100
............................................................................................................................................................................................................................................................
RESV_REQ_FL_CS
Count Definitions

been accepted.

Formula

----------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CS
Count Definitions

when a FL reservation of Conversational Speech is terminated because
in translations.
may be due to resource contention between unicast and BCMCS services
and are not indicative of a system or network problem. BCMCS
measurement data must be included in the analysis to determine whether a
system or network problem exists or not. Slots reserved for BCMCS traffic
can not be allocated to unicast traffic.
FL reservation of Conversational Speech is terminated because its
............................................................................................................................................................................................................................................................

been accepted.

Formula

RESV_ADMITTED_FL_CV
-----------------------------------------------------X 100
RESV_REQ_FL_CV
Count Definitions

accepted.

Formula

--------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CV
............................................................................................................................................................................................................................................................
Count Descriptions

when a FL reservation of Conversational Video is terminated because
in translations.
FL reservation of Conversational Video is terminated because its
accepted.

Formula

-----------------------------------------------------------X 100
RESV_REQ_FL_CPS
Count Definitions

Conversational PTT Speech is included in a ReservationOnRequest that
has been accepted.
RES_REQ_FL_CPS = This count is incremented when a FL reservation of
Conversational PTT Speech is included in a ReservationOnRequest.
............................................................................................................................................................................................................................................................

Formula

----------------------------------------------------------------------------------X 100
Count Descriptions

overload.
when a FL reservation of Conversational PTT Speech is terminated
because number of packets dropped by the scheduler has exceeded the
threshold set in translations.
FL reservation of Conversational PTT Speech is terminated becauseits
the AT.

............................................................................................................................................................................................................................................................
Formula

--------------------------------------------------------------------------------------------- X 100
RESV_ADMITTED_RL_CS
Count Descriptions

RL reservation of Conversational Speech is terminated due to the
been accepted.

Formula

------------------------------------------------------------------------X 100
RESV_ADMITTED_RL_CV
............................................................................................................................................................................................................................................................
Count Descriptions

RL reservation of Conversational Video is terminated due to the
termination of its FL counterpart.
accepted.

Formula

----------------------------------------------------------------------------------X 100
Count Descriptions

overload.
of Conversational push-to-talk Speech is terminated due to reverse link RF
overload.
RL reservation of Conversational PTT Speech is terminated due to the
............................................................................................................................................................................................................................................................

the AT.

Formula

-------------------------------------------------------- X 100
Count Descriptions

A11 Broadcast registration reply message is received at the AP from the
Broadcast Serving Node (BSN) in response to the A11 BC registration
registration request message is sent from the AP to the BSN. This count
does not include the A11 Broadcast registration request retries.

This metric provides the success rate of the BCMCS service request to the BSN.
The peg counts are defined on a per TP basis. This metric is effective beginning in R29.
Formula

------------------------------------------------------------------- X 100
Count Descriptions

successful A11 Broadcast service response message is received at the AP
from the Broadcast Serving Node (BSN) in response to the A11 BC serivce
............................................................................................................................................................................................................................................................

service request message is sent from the AP to the BSN. This count does
not include the A11 Broadcast service request retries.
............................................................................................................................................................................................................................................................
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Overview
The purpose of this chapter is to describe new and modified Primitive Calculations
(PCALCS) that support 1XEV-DO Performance Metrics in IBM Prospect for Alcatel-
Lucent R30.
earlier releases.
8 new PCALCs 1xEV-DO performance metrics for R30 New 1xEV-DO Performance
Metrics in Prospect R30 (p. 20-6).
1 existing metric is obsolete in R30.
releases:
25
26
............................................................................................................................................................................................................................................................
Release 30

............................................................................................................................................................................................................................................................
Release 30 RNC R30

............................................................................................................................................................................................................................................................

D Op _ Re TX R ev Ln k = 10 0. 0 * ( M is s in gR L PR eq R TC _ BE +
M is s in gR L PR eq R TC _ SM C) / (R L PR X RT C + R LP R cv d RT CS M C)
Notes:
Prospect
Traffic
MissingRLPReqRTC_BE MISSING_RLP_REQ_RTC_BE IxEV_Sector
Carrier
MissingRLPReqRTC_SMC MISSING_RLP_REQ_RTC_SMC 1xEV_Sector
Carrier
RLPRXRTC RLP_RXED_RTC 1xEV_Sector
Carrier
RLPRcvdRTCSMC RLP_RCVD_RTC_SMC 1xEV_Sector
Carrier
1xEV-DO Reverse Link Retransmission Failure Rate

D Op _ Re TX F ai lR e vL n k = 1 00 .0 * ( Mi ss i ng RL P Ne v er Rx e dR TC _ BE +
M is s in gR L PN ev e rR x ed RT C _S MC ) / (M is s in gR L PR e qR TC _ BE +
M is s in gR L PR eq R TC _ SM C)
Notes:
Prospect
Traffic
MissingRLPReqRTC_BE MISSING_RLP_REQ_RTC_BE 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
Release 30 RNC R30
MissingRLPReqRTC_SMC MISSING_RLP_REQ_RTC_SMC 1xEV_Sector

Carrier
MissingRLPNeverRxedRTC_BE MISSING_RLP_NEVER_RXED_RTC_BE 1xEV_Sector
Carrier
MissingRLPNeverRxedRTC_SMC MISSING_RLP_NEVER_RXED_RTC_SMC 1xEV_Sector
Carrier
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Obsolete 1xEV-DO Performance Metrics in
Obsolete 1xEV-DO Performance Metrics in Prospect R30

............................................................................................................................................................................................................................................................
DOp_SftSftrHOOverhead_SBEVM (1xEV-DO Soft/Softer Handoff Overhead SBEVM)

The EVDO metric DOp_SftSftrHOOverhead_SBEVM (1xEV-DO Soft/Softer Handoff
Overhead SBEVM) will be obsolete for RNC R30 data.
For backward compatibility, the current metric DOp_SftSftrHOOverhead_SBEVM will
continue to be valid for data for RNC R27 R29.
Note:
1. DOp_SftSftrHOOverhead_SBEVM is replaced with the new metric
DO_SftSftrHOOverhead
2. DOp_SftSftrHOOverhead will be valid for both SBEVM and DBEVM
3. DOp_SftSftrHOOverhead is a more accurate calculation than
DOp_SftSftrHOOverhead_SBEVM
............................................................................................................................................................................................................................................................
Release 30 R30

............................................................................................................................................................................................................................................................

Valid Releases: RNC/Cell R30 and later
DO _ Av g RL PF L Da ta R at e _B E = ( 8. 0 * RL PT x ed FT C _B E ) / ( 1. 66 7 *
To t al B us yS l ot s_ B E)
Notes:
Prospect
Traffic
RLPTxedFTC_BE EVM_RLP_TXED_FTC_BE IxEV_Sector
Carrier
TotalBusySlots_BE EVM_TOTAL_BUSY_SLOTS_BE IxEV_Sector
Carrier

DO p _R L Xm it E rr or _ CS C V = 1 00 .0 *
(M i ss i ng RL P Pa ck e tN e ve rR x ed RT C _C S + M i ss i ng RL P Ne ve r Rx e dR TC _ CV )
/ ( RL P Rc vd R TC _C S + RL PR c vd RT C _C V )
Notes:
Prospect Traffic
MissingRLPPacketNeverRxedR MISSING_RLP_PACKET_NEVER_RXED_RTC IxEV_SectorCarrier
TC_CS _CS
MissingRLPNeverRxedRTC_C MISSING_RLP_NEVER_RXED_RTC_CV IxEV_SectorCarrier
V
RLPRcvdRTC_CS RLP_RCVD_RTC_CS IxEV_SectorCarrier
............................................................................................................................................................................................................................................................
Release 30 R30
RLPRcvdRTC_CV RLP_RCVD_RTC_CV IxEV_SectorCarrier

D O_ A vg RL P FL Us r Da t aR at e _B E = 8 . 0 * R L PS en t To BT S At T P_ BE / ( 26 7. 0
* U s er Pr e se nt A tT P _B E)
Notes
Prospect Traffic
RLPSentToBTSAtTP_B RLP_SENT_TO_BTS_AT_TP_BE IxEV_SectorCarrier
E
UserPresentAtTP_BE USER_PRESENT_AT_TP_BE IxEV_SectorCarrier
1xEV-DO Percentage of Bandwidth Used for Signaling (%)

D Op _ BW Us e dS ig n al = 10 0 .0 * (C C Sl ot s Sy nc M sg X mi t +
C CS l ot sA s yn cM s gX m it + CC Sl o ts S ub sy n cM sg X mi t ) / 2 16 00 0 0. 0
Notes:
Prospect Traffic
CCSlotsSyncMsgXmit EVM_CC_SLOTS_SYNC_MSG_XMIT IxEV_SectorCarrier
CCSlotsAsyncMsgXmit EVM_CC_SLOTS_ASYNC_MSG_XMIT IxEV_SectorCarrier
CCSlotsSubsyncMsgXm EVM_CC_SLOTS_SUBSYNC_MSG_XMIT IxEV_SectorCarrier
it
1xEV-DO Average Number of Contending Users BE

............................................................................................................................................................................................................................................................
Release 30 R30
DO _ Av g Nu mC o nt en d Us e rs _B E = 2 . 16 * Av g El ig U se r _B E /
To t al B us yS l ot sU s er P re se n t_ BE
Notes:
Prospect
Traffic
AvgEligUser_BE EVM_AVG_ELIG_USER_BE IxEV_Sector
Carrier
TotalBusySlotsUserPresent_BE EVM_TOTAL_BUSY_SLOTS_BE_USER_PRESENT IxEV_Sector
Carrier
1xEV-DO Average Number of Contending Flows EF

DO _ Av g Nu mC o nt en d Fl o ws _E F = 2 . 16 * Av g El ig F lo w _E F /
To t al B us yS l ot sU s er P re se n t_ EF
Notes:
Prospect
Traffic
AvgEligFlow_EF EVM_AVG_ELIG_FLOW_EF IxEV_Sector
Carrier
TotalBusySlotsUserPresent_EF EVM_TOTAL_BUSY_SLOTS_EF_USER_PRESENT IxEV_Sector
Carrier

DO _ Av g Nu mC o nt en d Us e rs = 10 0. 0 * Av gE l ig Us e r_ A ll /
Pc n tS l ts Us r Tr f
............................................................................................................................................................................................................................................................
Release 30 R30
Notes:
Prospect
Traffic
AvgEligUser_All EVM_AVG_ELIG_USER_ALL IxEV_Sector
Carrier
PcntSltsUsrTrf EVM_TOTAL_BUSY_PCNT_SLOTS IxEV_Sector
Carrier
1xEV-DO Soft/Softer Handoff Overhead (Measured at TP)

D O_ S ft Sf t rH OO v er h ea d = T ot A ct i ve Co n nP er S ec t or TP /
T ot D RC Po i nt ed A ct i ve Co n nP er S ec t or TP
Notes:
1. DO_SftSftrHOOverhead is valid for both SBEVM and DBEVM and replaces the
obsolete (in R30) metric DO_SftSftrHOOverhead_SBEVM
Prospect
Traffic
TotActiveConnPerSectorTP TOT_ACTIVE_CONN_PER_SECTOR_TP IxEV_Sector
Carrier
TotDRCPointedActiveConnPerSect TOT_DRC_POINTED_ACTIVE_CONN_PER_SECT IxEV_Sector
orTP OR_TP Carrier
............................................................................................................................................................................................................................................................
Release 30 R30
............................................................................................................................................................................................................................................................
21 Performance Metrics for Alcatel-
Lucent Release 31
Overview
............................................................................................................................................................................................................................................................
Purpose
This chapter contains new,modified and deleted performance for R31.

This SRD is issued for 1xEV-DO Release 31. The metrics that were changed, or added are
listed in Section 1.3, Reason for Re-Issue.
New Metrics
1xEV-DO Percentage of AT-Assisted Interfrequency Handoffs - Requesting Sector

(p. 21-56)
1xEV-DO Directed IFHO Triggered by Pilot Strength Success Rate - Requesting
Sector (%) (p. 21-57)
1xEV-DO Directed IFHO Triggered by Upper Distance Threshold Success Rate -

Requesting Sector (%) (p. 21-58)
1xEV-DO Round Trip Delay Measurement Validity Rate (p. 21-59)
1xEV-DO Average Distance Between AT and BTS for Pilot Strength Triggered
Directed IFHO (p. 21-60)
1xEV-DO Average Ratio of Pilot Strength and Threshold for IFHO (p. 21-61)
1xEV-DO Average RLP Forward Link User Data Rate - BE - BTS (kbps) (p.
21-100)
1xEV-DO Average Degree Out of Sequence Packets, FL CS (p. 21-144)
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Overview
1xEV-DO Average Degree Out of Sequence Packets, FL CV (p. 21-145)

1xEV-DO Average Degree Out of Sequence Packets, RL CS (p. 21-146)
1xEV-DO Average Degree Out of Sequence Packets, RL CV (p. 21-147)
1xEV-DO Percentage of Out of Sequence Packets, FL CS (p. 21-148)
1xEV-DO Percentage of Out of Sequence Packets, FL CV (p. 21-149)
1xEV-DO Percentage of Out of Sequence Packets, RL CS (p. 21-150)
1xEV-DO Percentage of Out of Sequence Packets, RL CV (p. 21-151)
Revised Metrics:
1xEV-DO Reverse Link Data Re-Transmission Rate (p. 21-69)

For a broad overview of each broad category see Performance Metrics (p. 1-2)
The following performance metrics are provided (new metrics in R31 are in italics):

Intra-RNC Group Session Transfer Success Rate
Configuration Negotiation Success Rate
Intra-RNC Session Balance Success Rate

Established Connection Reg - Peg

Established Connection Rate - Session Setup - Peg
Established Connection Rate - User -Peg
............................................................................................................................................................................................................................................................
AT-Initiated Connection Blocking Rate - Session Setup

Connection Blocking Rate - User
RF Failure Rate - Session Setup
RF Failure Rate - User
Paging Effectiveness
Paging Success Rate by Page Attempt
Paging Escalation Success Rate
Paging De-Escalation Success Rate
Paging Effectiveness by Sectors per Page Attempt
Data Over Signalling Effectiveness
Data Over Signalling Success Rate by Page Attempt
b. Call Drop Metrics
Dropped Connection Rate - peg
c. Handoff Metrics

Percentage of AT-Assisted Interfrequency Handoffs - Requesting Sector
Directed IFHO Triggered by Pilot Strength Success Rate - Requesting Sector

Directed IFHO Triggered by Upper Distance Threshold Success Rate - Requesting
Sector
Round Trip Delay Measurement Success Rate
Average Distance Between AT and BTS for Pilot Strength Triggered Directed
IFHO
Average Ratio of Pilot Strength and Threshold for IFHO
............................................................................................................................................................................................................................................................

Forward Link Data Re-transmission Rate - EVM
Forward Link Data Re-transmission Rate (NAK) - SBEVM
Forward Link Data Re-transmission Rate (DARQ) - SBEVM
Reverse Link Transmission Error Rate for CS and CV
Total Forward Link MAC Data Transmitted - EVM (MB)
Total Forward Link Physical Layer Data Transmitted - SBEVM (MB)
Composite Forward Link Physical Layer Data Transmitted (MB)
Average Forward Link MAC Data Rate - EVM (kpbs)
Average Forward Link Physical Layer Date Rate - SBEVM (kbps)
Composite Average Forward Link Physical Layer Data Rate
Average Forward Link Physical Layer Data Rate per User - SBEVM (kbps)
Average RLP Forward Link Data Rate - EVM (kbps)
Average RLP Forward Link Data Rate with SBEVM (kbps)
Composite RLP Forward Link Data Rate (kbps)
Average RLP Forward Link Data Rate - BE Traffic (kbps)
Average Forward Link RLP Data Volume per User (MB)
Average RLP Forward Link Data Rate per User - SBEVM (kbps)
Average RLP Forward Link User Data Rate - BE (kbps)
Average RLP Forward Link User Data Rate - BE- BTS (kbps)
Percentage of Band Width Used for Signaling (%)
Average Reverse Link Pysical Layer Data Volume - EVM (MB)
Average Reverse Link Data Volume with SBEVM (MB)
Reverse Link Physical Layer Composite Data Volume (MB)
Average Reverse Link Physical Layer Data Rate - EVM (kbps)
Average Reverse Link Physical Layer Data Rate with SBEVM (kbps)
Composite Average Reverse Link Physical Layer Data Rate
Reverse Link RLP Data Throughput - EVM
Reverse Link RLP Data Throughput with SBEVM
Composite Reverse Link RLP Data Throughput
e. Error Statistics
............................................................................................................................................................................................................................................................
Reverse Frame Error Rate - EVM

Missed Termination Target of LoLat Packets
f. Power Control
Average Reverse Link Power Control Setpoint - 0 kbps -EVM

Average Reverse Link Power Control Setpoint - 9.6 kbps - EVM
Average Reverse Link Power Control Setpoint - 76.8 kbps -EVM
Average Reverse Link Power Control Setpoint - 128 bits - SBEVM
Average Reverse Link Power Control Setpoint - 8192 bits -SBEVM

"Primary" Traffic Channel Usage (in Erlangs) - SBEVM
Average Number of Contending Users - BE
Average Number of Contending Flows - EF
Average Number of Contending Users
Soft/Softer Handoff Overhead (Measured at TP)
3. Quality of Service Metrics
ReservationOnRequest Success Rate

Forward Link Conversational Speech Reservation Success Rate
Forward Link Conversational Speech Dropped Reservation Rate
Forward Link Conversational Video Reservation Success Rate
Forward Link Conversational Video Dropped Reservation Rate
............................................................................................................................................................................................................................................................
Forward Link Conversational Push to Talk Reservation Success Rate

Forward Link Conversational Push to Talk Dropped Reservation Rate
Reverse Link Conversational Speech Dropped Reservation Rate
Reverse Link Conversational Video Dropped Reservation Rate
Reverse Link Conversational Push to Talk Speech Dropped Reservation Rate
Broadcast Registration Success Rate
Service Request Success Rate
4. Metrics Added Due to SM Re-Architecture
Average Degree Out of Sequence Packets FL CS

Average Degree Out of Sequence Packets FL CV
Average Degree Out of Sequence Packets RL CS
Average Degree Out of Sequence Packets RL CV
Percentage of Out of Sequence Packets FL CS
Percentage of Out of Sequence Packets FL CV
Percentage of Out of Sequence Packets RL CS
Percentage of Out of Sequence Packets RL CV
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Session Management Metrics

............................................................................................................................................................................................................................................................

source RNC), etc.
group transfers.
............................................................................................................................................................................................................................................................
Formula
(SESS_SETUP_UATI_COMPLETE_MSG_RCVD +
INTRA_RNC_GROUP_SESS_TRFR_UATI_COMPLETE_RCVD)
-----------------------------------------------------------------------------------------------------X100
Count Definitions
color code)
Message Received (new & prior sessions). Pegged when the AT acknowledges a UATI
assignment message sent by the AN in response to a UATI request.
incremented each time a UATI Complete is received or any access channel packet received
with just assigned UATI for a session transfer within an RNC Group.
Route Update message received with UATI on the access channel from an AT with its
serving AP in a different RNC from the last seen RNC within the same RNC Group.

AT issues, inability to negotiate to mutually agreeable settings, etc. Normally, the AN
should have no problem allocating a UATI to the AT as long as the operator engineers the
network to keep the requested number of sessions from frequently exceeding the
............................................................................................................................................................................................................................................................
maximum number of sessions limit, and, the source and old RNCs can communicate &
exchange proper information in case of Color Code method of inter-RNC idle handoff. A
ratio less than 1 is reflective purely of a AN issue; no over the air messaging is involved.
Formula
+INTRA_RNC_GROUP_SESS_TRFR_UATI_ASSGN_SENT)
----------------------------------------------------------------------------------------------X 100
Count Definitions
color code)
sessions)
pegged by the new control OHM against the sector-carrier where the UATI Request
message is received.
parameter is set to yes) and Control OHM is transferred, this count is pegged by the new
control OHM against the sector-carrier where the UATI Request message is received.
incremented each time a UATI assignment is sent for a session transfer within an RNC
Group.
............................................................................................................................................................................................................................................................

Route Update message received with UATI on the access channel from an AT with its
serving AP in a different RNC from the last seen RNC within the same RNC Group.

connections.
Formula
DO Avg Active Sessions =
---------------------------------------------------------
360
Count Definitions
AVG_ACTIVE_CONN_PER_OHM = Number of active connections on an OHM
(sessions with an active PPP session). This count is pegged every 10 seconds during the
measurement interval and added to the previous total. Therefore, the result is divided by
360 to get the approximate average over the measurement interval. Note that the
measurement interval is not exactly one hour so the calculation is approximate.

............................................................................................................................................................................................................................................................
intervention.
if it was used to access the network while in a dormant state right after the inter-subnet idle
handoff trigger. Hence, a relatively high rate of inter-RNC idle handoff failures may not be
that egregious.
a blocking (the target RNC is already serving the maximum allowed UATI sessions). This
metric was revised in R24 to account for the Prior Session method. The peg counts are
defined on a per sector-carrier basis. Beginning in R28 a subnet may be defined to include
more than one RNC. The description in this section and in some of the peg counts was
changed to reflect this enhancement. The formula is not changed.
Formula
DO Int sub idle xfer success rate (%) = (INT_SUBNET_IDL_TRFR_ATTMPT +
(ISBNT_IDL_TRFR_FAIL_NO_RSP_ PRV_SBNET
+ISBNT_IDL_TRFR_FAIL_ORG_PDSN_CANT_CONN
+INT_SUBNET_IDL_TRFR_FAIL_OTHER_REASON +
............................................................................................................................................................................................................................................................
------------------------------------------------------------------------------------------------- X100
Count Definitions
transfer a dormant data session between subnets using a method other than the Prior
Session method and is the total of all such idle transfer attempts for the HDR Cell sector-
carrier that received the UATIRequest.
A13-Session Information Request is generated in the target AN, omitting the number of
such requests that are associated with the Prior Session method. Note that if the A13
message is repeated, the count is only pegged once.
inter-subnet or inter-RNC idle transfer attempts pegged on the new RNC (target RNC) for
the prior session method. The count is pegged when the target RNC receives a UATI
Request message that contains a RATI assigned by a different RNC.
idle transfer attempt using the Color Code Method or the Assign First Method that failed
because the previous subnet did not respond and is the total of all such idle transfer
failures for the HDR Cell sector-carrier. This count is used to measure idle transfer failures
because the old subnet did not respond to the transfer request. The count should be pegged
after both request attempts have failed.
............................................................................................................................................................................................................................................................

RNC idle handoff failures that occur because the PCF on the new RNC could not establish
an A11 (also known as R-P) connection with the original PDSN. In essence, a new UATI
is assigned successfully but the connection to the PDSN failed subsequently
connection and soft/er handoff failures, this accounts for all inter-RNC idle handoff
attempts that failed for reasons not accounted for by the other specific failure counts. One
scenario where this is seen quite often is the ping pong scenario. When RNC2 times out
waiting for the UATI Complete message in response to the UATI Assignment message
because the AT has moved to a different RNC (RNC1 or RNC3), it declares it as an Other
failure. Of course, the timeout may also happen due to poor RF conditions or if RNC2 did
not send the UATI Assignment message with proper message sequence number (often is
the case with the Assign First method where RNC has to guess a sequence number since
it has not yet communicated with the old RNC and has no way of knowing the last
sequence number used to communicate with the AT). This count may also reflect blocking
where the target RNC has no more spare UATIs to assign to the requesting AT.
as the name suggests, the PCF A11 IP address of the old RNC is not provisioned on the
new RNC. The problem is applicable only for the Color Code method of the inter-RNC
Idle handoff, which requires the new RNC to perform a look up of old RNCs IP address
in a locally stored mapping table. The lookup is performed using the color code retrieved
from the old UATI sent by the AT as part of the UATI Request message. If the Assign First
method is used instead, the AN first assigns the UATI to the AT and as part of the UATI
Assignment message, instructs the AT to directly report back the old RNCs PCF A11
address. Using this information, the new RNC then attempts to initiate the session transfer
from the old RNC. In this case, no lookup table is needed at the new RNC, and hence this
type of failure does not apply in case of the Assign First method.
............................................................................................................................................................................................................................................................
Code method is when the PDSN's IP address reported in the A13 Session Code method is
when the PDSN's IP address reported in the A13 Session Information Response message
by the source RNC is invalid (i.e., 255.255.255.255 or NULL).
RNC receives a A13 Reject message from the old RNC in response to a session transfer
request. One scenario where this may occur is when the AT has gone back to the old RNC
(call it RNC 1) or a third RNC (call it RNC 3) before it could send a UATI Complete to the
new RNC (call it RNC 2). In this case, the new RNC (RNC 2) does not yet consider itself
to be in control of ATs session and hence, would reject the subsequent session transfer
request (from RNC1 or RNC3 in this rapid handoff scenario).
Transfer failures due to no response from the previous subnet using the Prior Sessions
method.
Transfer failures due to a failure to find the source AN because of insufficient information
in the Configuration Request message using the Prior Sessions method.

Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
INTRA_RNC_GROUP_SESS_TRFR_SUCCESS = This count is incremented each time
a session transfer is successful for a Route Update message received with an UATI
Request with UATI on the access channel from an AT with its cell serving OHM in
different RNC from the last seen RNC within the same RNC Group. The session transfer
is considered successful after the serving RNC has finished the negotiation with PDSN if
there is a session setup between AT and PDSN or after the serving RNC has received the
UATI Complete message from AT or any access channel packet with just assigned UATI if
there is no session setup with PDSN.
INTRA_RNC_GROUP_SESS_TRFR_ATTEMPT = This count is incremented each time
a session transfer is attempted for a Route Update received with an UATI Request with
UATI on the access channel from an AT with its cell serving OHM in different RNC from
the last seen RNC within the same RNC group.

high.
Formula
--------------------------------------------------------------------- X 100
Count Definitions
attempts.
RAN_AUTH_TOTAL_ATTMPT = Total number of RAN authentication attempts.

............................................................................................................................................................................................................................................................
session setup.
Formula
--------------------------------------------------------------------------------------------------- X 100
CONFIG_NEGO
Count Definitions
configuration negotiation procedure takes place. It is pegged against the sector-carrier on
which the configuration negotiation procedure takes place.
configuration negotiation initiated by the AN failed because the Configuration Response
message was not received from the AT. It is pegged against the last known DRC-pointed
sector-carrier at the time the configuration negotiation process is declared a failure.
configuration negotiation initiated by the AT failed because the Configuration Response
message was not received from the AT. It is pegged against the last known DRC-pointed
sector-carrier at the time the configuration negotiation process is declared a failure.

Formula
............................................................................................................................................................................................................................................................
---------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
number of successful session balances during the SM collection interval at the originating
OHM because the Intra-RNC UATI Session Balance Threshold was exceeded. This count
includes new session request and idle transfer scenarios.The session balance is considered
successful when the originating OHM receives confirmation message from the target
OHM indicating the session balance request has been accepted by the target OHM.
of UATI session balance requests sent to another OHM within the same RNC during the
SM collection interval at the originating OHM because the Intra-RNC UATI Session
Balance Threshold was exceeded. This count includes new session request and idle
transfer scenarios. If a session OHM balance request is rejected by a target OHM, the
requesting OHM may retry to transfer the session to another target OHM. In this scenario
the count is incremented only once.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Packet Data Reactivation Metrics

............................................................................................................................................................................................................................................................

established. If the data from the PDSN arrives when the PPP link is dormant, then it results
in what is known as PCF or network reactivation, as discussed above.
Formula
------------------------------------------------------------------------------ X 100
............................................................................................................................................................................................................................................................
Count Definitions
PCF_INIT_REACT_ATTMPT = Total number of attempts made by the PCF to revive a
dormant traffic connection when it receives data from the PDSN for transmission to the
end user.
PCF_INIT_REACT_FAIL = This count is incremented when the AN is unable to establish
a data path to a dormant end user in response to data transmission request from the PDSN.

on the R-P link.
handoff.
failures.
Formula
-------------------------------------------------------- X100
RP_CONN_ATTMPTS
............................................................................................................................................................................................................................................................
Count Definitions
connection with the PDSN based on requests from the AT. Basically, any PPP packet from
the AT that requires transmission to the PDSN for which an A10 link does not exist results
in a R-P connection attempt.
Furthermore, an attempt to transfer an existing R-P session between PCFs on the source
and target RNCs as part of an inter-RNC Idle handoff will also increment this peg. Any
reactivations from dormancy, whether AT or AN initiated, are not included in the count.
(BCMCS).
failure could either be due to a reject message from the PDSN, or a response timeout
(PDSN not reachable due to addressing error, PDSN not in service).
(BCMCS).
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Connection Setup Metrics

............................................................................................................................................................................................................................................................

3G1X.
number when compared to AN Initiated connections, which in turn are relatively smaller

rate.
The peg counts are defined on a per sector-carrier basis. For roll ups to the sector, cell and
higher levels, the cross-carrier counts can be omitted since they will cancel out. However,
leaving the cross carrier count in the formula will still provide correct roll ups.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------- X 100
Count Definitions
(pegged when a TCC is received or an RLP packet is received from the AT on the reverse
traffic channel.)
connections(pegged when a TCC is received or an RLP packet is received from the AT on
the reverse traffic channel.)
CROSS_CARRIER_ATTMPT_RCVD_TCC_RCVD = This count is pegged for each
established connection (TCC is sent to from the AT) where the TCA does not include the
sector-carrier that received the connection request. It is pegged against the strongest
sector-carrier selected for traffic channel allocation by the load balancing alogorithm.
CROSS_CARRIER_ATTMPT_SENT_TCC_RCVD = This count is pegged for each
sector-carrier that received the connection request. It is pegged against the sector-carrier
that received the connection request.
AN_INIT_CONN_REQ = AN-Initiated connection requests = This count is pegged for
each connection request received when the UATI associated with the request does not have
a valid session due to a Session transfer failure. The count is used to measure connection
attempt rejects due to session transfer failures.
connection requests on this sector-carrier served by another sector-carrier.
connection requests on another sector-carrier served by this sector-carrier.
connection requests on this sector-carrier served by another sector-carrier.
............................................................................................................................................................................................................................................................

connection requests on another sector-carrier served by this sector-carrier.

for those connection requests that are part of session setup and excludes those connection
sectorcarrier basis and are pegged at the sector-carrier that received the connection
request.
Formula
---------------------------------------------------------------------------------------------------X 100
Count Definitions
AT_INIT_ESTABLISHED_CONN_SESS = This count is incremented each time a
connection is established for a sector-carrier for a connection request while the UATI
Session is in a state of waiting for a Configuration Negotiation or the UATI Session is
associated with a Color Code that is not supported by this AN. This count is pegged
against the sector-carrier that received the Connection Request. This count is used to
measure the success of AT-initiated initial (configuration negotiation) connection requests
associated with session setup attempts or for UATIs associated with a Color Code that is
not supported by this AN, at least up to the point where an initial connection is established
AT_INIT_CONN_REQ_SESS = This count is incremented each time a connection
request is received by a sector-carrier while the UATI Session is in a state of waiting for a
Configuration Negotiation or the UATI Session is associated with a Color Code that is not
supported by this AN. This count is pegged against the sector-carrier that received the
Connection Request. This count is used to measure the number of AT-initiated initial
(configuration negotiation) connection requests associated with session setup attempts or
for UATIs associated with a Color Code that is not supported by this AN.
............................................................................................................................................................................................................................................................

Formula
----------------------------------------------------------------------------------------------------X 100
Count Definitions
(pegged when a TCC is received or an RLP packet is received from the AT on the reverse
traffic channel.)
connections(pegged when a TCC is received or an RLP packet is received from the AT on
the reverse traffic channel.)
AN_INIT_CONN_REQ = AN-Initiated connection requests = This count is pegged for
each connection request received when the UATI associated with the request does not have
a valid session due to a Session transfer failure. The count is used to measure connection
attempt rejects due to session transfer failures.
AT_INIT_CONN_REQ = AT-Initiated connection requests.
against the sector-carrier that received the Connection Request.
............................................................................................................................................................................................................................................................
This count is used to measure the success of AT-initiated initial (configuration negotiation)
connection requests associated with session setup attempts or for UATIs associated with a
Color Code that is not supported by this AN, at least up to the point where an initial
connection is established
AT_INIT_CONN_REQ_SESS = This count is incremented each time a connection
request is received by a sector-carrier while the UATI Session is in a state of waiting for a
Configuration Negotiation or the UATI Session is associated with a Color Code that is not
supported by this AN. This count is pegged against the sector-carrier that received the
Connection Request. This count is used to measure the number of AT-initiated initial
(configuration negotiation) connection requests associated with session setup attempts or
for UATIs associated with a Color Code that is not supported by this AN.

level.
Formula
---------------------------------------------------------------------------------------------------- X 100
FAST_CONNECT
Count Definitions
FAST_CONNECT_ESTABLISHED_CALLS = The number of fast connect procedures
thatresult in an active connection (defined as receipt of TCC or an RLP packet on the
reverse traffic channel).
FAST_CONNECT = Number of fast connection requests.
............................................................................................................................................................................................................................................................

This metric gives the percentage blocking for AT-initiated and AN-initiated connections. It
is equivalent to the Seizure to Assignment Deficit Ratio for originations and terminations
in 3G 1x. Any connection attempt failures occurring after receiving a Connection Request
and prior to sending the TCA are termed as connection blocks or connection attempt
deficits. These are failures entirely happening within the AN, such as TCA allocation
failure, some type of resource overload or overflow, internal errors or messaging failure.
The peg counts are defined on a per sector-carrier basis. For roll ups to the sector, cell and
higher levels, the cross-carrier counts can be omitted since they will cancel out. However,
leaving the cross carrier count in the formula will still provide correct roll ups.
............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------------------------- X 100
Count Definitions
this sector-carrier in response to AN-Initiated Connection Requests either received and
served on this sector-carrier (same sector-carrier assignment) or received on another
sector-carrier and served on this sector-carrier (cross sector-carrier assignment).
this sector-carrier in response to AT-Initiated Connection Requests either received and
the AN on this sector-carrier in response to a connection request received on another
sector-carrier. It is pegged against the strongest sector-carrier selected for traffic channel
the AN on another sector-carrier in response to a connection request received on this
sector-carrier. It is pegged against the sector-carrier that received the connection request.
sectorcarrier.
sectorcarrier.
............................................................................................................................................................................................................................................................

connection requests received on this sector-carrier served by a different sector-carrier
connection requests received on a different sector-carrier but served by this sector-carrier
connection requests received on this sector-carrier served by a different sector-carrier
connection requests received on a different sector-carrier but served by this sector-carrier
this sector-carrier in response to AN-Initiated Connection Requests received on this
sector-carrier
this sector-carrier in response to AT-Initiated Connection Requests received on this sector-
carrier

............................................................................................................................................................................................................................................................
effective with R26.
Formula
-----------------------------------------------------------------------------------------------------X100
Count Definitions
AT_INIT_CONN_REQ_SESS = T Initiated Connection Requests, Session Setup.
Initiated Connection Requests for session setup.

messaging failure.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
Traffic Channel Assignments sent by the AN on this sector-carrier in response to AN-
Initiated Connection Requests either received and served on this sector-carrier (same
sector-carrier assignment) or received on another sector-carrier and served on this sector-
carrier (cross sector-carrier assignment).
this sector-carrier in response to AT-Initiated Connection Requests either received and
AN_INIT_CONN_REQ = AN-Initiated Connection Requests received on this sector-
carrier
AT_INIT_CONN_REQ = AN-Initiated Connection Requests received on this sector-
carrier
AT_INIT_CONN_REQ_SESS = AT Initiated Connection Requests, Session Setup.

ATinitiated) that failed. It is defined as 100 - established connection rate (see section
4.2.1.1). The formula is revised in R26 for simplification. The old formula could not be
used with the new load balancing (cross-connect) feature because there are no cross-
connect failure counts defined. The new formula is effective beginning with R26 but can
be used in prior releases.
............................................................................................................................................................................................................................................................
Formula
Count Definitions

ATinitiated) that failed. It is defined as 100 - established connection rate - peg (see section
Formula
Count definitions

detailed formula in the above metric There are no peg counts explicitly used in this
metric. See section 1xEV-DO Established Connection Rate - User - Peg (%) (p. 19-23)
for the counts included in the established connection rate - peg metric. (p. 19-30) but it is
recommended that customers use both forumula for a couple of releases to compare the
values obtained by both. The new formula is effective beginning with R26. Beginning with
R28 this is the recommended metric for RF Failure Rate.
............................................................................................................................................................................................................................................................
Formula
Formula
------------------------------------------------------------------------------------------------- X 100
Count definitions
sectorcarrier
this sector-carrier in response to AT-Initiated Connection Requests received on this
sectorcarrier
AN_INIT_ESTABLISHED_CONN = Number of AN-Initiated successful connections for
connection requests received on this sector-carrier.
AT_INIT_ESTABLISHED_CONN = Number of AT-Initiated successful connections for
CROSS_CARR_ATTMPT_RCVD_TCC_RCVD = This count is pegged for each
sector-carrier selected for traffic channel allocation by the load balancing algorithm.
............................................................................................................................................................................................................................................................
CROSS_CARR_ATTMPT_SENT_TCC_RCVD = This count is pegged for each

sector-carrier that received the connection request. It is pegged against the sector-carrier

Largely, the failures can be broken down into RF failures or blocking. The peg counts are
defined on a per sector-carrier basis. This metric is new in R28.
Formula
------------------------------------------------------------------------------------------------- X 100
Count definitions
TCA_FOR_AT_INIT_CONN_REQ_SESS = This count is incremented for a sector-
carrier each time a TCA is sent for a connection request while the UATI Session is in a
state of waiting for a Configuration Negotiation or the UATI Session is associated with a
Color Code that is not supported by this AN. This count is pegged only once for each
Connection Request procedure when multiple TCAs are sent. It is the total of all such
Connection Requests for which at least one TCA is sent.
This count pegged against the sector-carrier that received the Connection Request. This
count is used to measure the success of AT-initiated initial (configuration negotiation)
Color Code that is not supported by this AN to the point that a TCA is sent.
against the sector-carrier that received the Connection Request.
............................................................................................................................................................................................................................................................
This count is used to measure the success of AT-initiated initial (configuration negotiation)
Color Code that is not supported by this AN, at least up to the point where an initial
connection is established.

Hence it is only valid at the sector level or above. This metric is new in R28.
Formula
---------------------------------------------------------------------------------------------X 100
Count Definitions
sectorcarrier
this sector-carrier in response to AT-Initiated Connection Requests received on this
sectorcarrier
AN_INIT_ESTABLISHED_CONN = Number of AN-Initiated successful connections for
connection requests
............................................................................................................................................................................................................................................................

AT_INIT_ESTABLISHED_CONN = Number of AT-Initiated successful connections for
TCA_FOR_AT_INIT_CONN_REQ_SESS = This count is incremented for a sector-
carrier each time a TCA is sent for a connection request while the UATI Session is in a
state of waiting for a Configuration Negotiation or the UATI Session is associated with a
Color Code that is not supported by this AN. This count is pegged only once for each
Connection Request procedure when multiple TCAs are sent. It is the total of all such
Connection Requests for which at least one TCA is sent. This count pegged against the
sector-carrier that received the Connection Request. This count is used to measure the
success of AT-initiated initial (configuration negotiation) connection requests associated
with session setup attempts or for UATIs associated with a Color Code that is not
against the sector-carrier that received the Connection Request. This count is used to
measure the success of AT-initiated initial (configuration negotiation) connection requests
associated with session setup attempts or for UATIs associated with a Color Code that is
not supported by this AN, at least up to the point where an initial connection is established

AT_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = AT initiated connection attempt
AT_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD = AT initiated Connection attempt
AT_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = AT initiated Connection attempt
AT_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA = AT-initiated Connection attempt
AT_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = AT-initiated Connection
AN_INIT_CONN_ATTMPT_FAIL_NO_RES_AVLBL = AN initiated connection
............................................................................................................................................................................................................................................................
AN_INIT_CONN_ATTMPT_FAIL_NO_TCC_RCVD = AN initiated Connection attempt

AN_INIT_CONN_ATTMPT_FAIL_RL_NOT_ACQ = AN initiated Connection attempt
failures - rev link not acquired.
AN_INIT_CONN_ATMPT_FAIL_OTHER_PRETCA = AN-initiated Connection attempt
AN_INIT_CONN_ATMPT_FAIL_OTHER_POSTTCA = AN-initiated Connection

of Service (QoS). In addition to the simple paging process used before, there are now up to
8 configurable page attempts per pageable profile ID for QoS. The paging process
ID.
to provide an overall effectiveness of packet delivery based on uniques page attempts. This
revision to the formula is effective with R29.
............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------------------------- X 100
Count Definitions
while waiting for a response to the Kth Paging attempt. K varies from 1 to 8. Therefore,
there are 8 counts, one for each value of K. Note that if the default paging of the service
node is used, then the BEpID will be used for pegging. This count is reported per OHM-
Profile ID-page attempt. This count, in conjunction with the number of pages or
connection requests received, is used to monitor the effectiveness and efficiency of each
page attempt in the Paging sequence. This information can be used to optimize the paging
strategy setting.
PAGES = This count is incremented when a page is attempted for a given attempt K within
the Paging Sequence. K varies from 1 to 8. Therefore, there are 8 counts, one for each
value of K. Note that if the default paging of the service node is used, then the BEpID will
be used for pegging. This count is reported per OHM-Profile ID-page attempt.
to deliver the message to the AT for the Kth Paging attempt within the QoS paging
sequence. K varies from 1 to 8. Therefore, there are 8 counts, one for each value of K.
Pegging of this count is equivalent to pegging the CR count associated with the Kth
attempt within the QoS paging sequence. In either case, the Kth attempt of the paging
sequence was successful and paging is terminated. This count is reported per OHM-
Profile ID-Page Attempt.
Mobile Terminated DOS message to an AT in lieu of QoS paging. A page is attempted for
a given attempt K within the Paging Sequence. K varies from 1 to 8. Therefore, there are 8
counts, one for each value of K. This count is reported per OHM-Profile ID-Page Attempt.
attempt sequence is aborted due to override from page of higher priority ProfileID. This
count is pegged only when the QoS Paging is active for a ProfileID. This count is reported
per OHM-Profile ID.
............................................................................................................................................................................................................................................................

The formula will be repeated 8 times, once for each page attempt. The metrics can be used
to monitor the success rate of individual page attempts to optimize the paging strategy for
each Profile ID.
metric is new in R29 but can be used in R28.
Formula
-----------------------------------------------------------------------------X 100
Count Descriptions
while waiting for a response to the Kth Paging attempt. K varies from 1 to 8. Therefore,
there are 8 counts, one for each value of K. Note that if the default paging of the service
node is used, then the BEpID will be used for pegging. This count is reported per OHM-
Profile ID. This count, in conjunction with the number of pages or connection requests
received, is used to monitor the effectiveness and efficiency of each page attempt in the
Paging sequence. This information can be used to optimize the paging strategy setting.
be used for pegging. This count is reported per OHM-Profile ID.
area.
............................................................................................................................................................................................................................................................
Formula
-----------------------------------------------------------------------------X 100
Count Descriptions
Active Set Paging to another paging area. Last Seen RNC Paging area is used for default
paging or when QoS Paging is active for a profileID but Paging Enhancements Enable is
set to No. The paging area configured for the subsequent attempt, if non-blank and not
Last Active Set, is used when Paging Enhancements Enable is set to Yes. The method
switch occurs when the T_Page1 timer expires before the AT's next wakeup cycle. Note
that BEpID will be used for pegging when default paging is used. This count is used to
monitor if the T_Page1 timer is set properly.

Formula
-----------------------------------------------------------------------------X 100
Count Descriptions
Last Active Set. Paging de-escalation can only occur on the first page attempt.
............................................................................................................................................................................................................................................................

attempt. The metrics can be used to optimize the paging strategy settings. The peg counts
are defined on an OHM-pageable profile ID-paging attempt number basis. The metric can
only be calculated per RNC Group-profile ID basis since the SM counts are pegged in
different OHMs across the RNC Group. This metric is new in R29.
Formula
-----------------------------------------------------------------------------
Count Descriptions
a given attempt K within the Paging Sequence. For example, if a page attempt for attempt
K triggers a page sent to 10 different sectors, then this count is incremented by 10 for
attempt K. K varies from 1 to 8. Therefore, there are 8 counts, one for each value of K.
Note that if the default paging of the service node is used, then the BEpID will be used for
pegging.
be used for pegging. This count is reported per OHM-Profile ID.

to an AT.
the initial page. The peg counts are defined on an OHM-pageable profile ID-paging
attempt number basis. The metric could be calculated per OHM-profile ID basis, but is
more meaningful per RNC Group-Profile ID since that's how the paging strategy can only
be defined. This metric is effective beginning with R29.
............................................................................................................................................................................................................................................................
Formula
MT_DOS_SUCCESS)
-------------------------------------------------------------------------------------------------- X 100
Count Descriptions

ID. The formula will be repeated 8 times, once for each page attempt.. The metrics can me
used to monitor the success rate of individual DOS page attempts to determine how many
attempts on average are needed for each Profile ID.
Formula
-----------------------------------------------------------------------------------X 100
............................................................................................................................................................................................................................................................
Count Descriptions

sectorcarrier level. These counts measure the number of active connections during the
ustomer data in order to determine what the appropriate critical triggers are and whether
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Call Drop Metrics
Call Drop Metrics

............................................................................................................................................................................................................................................................

Formula
---------------------------------------------------------------------------------------------X 100
Count Definitions
CONN_REL_RLL = Connection Release - RF Link
LostCONN_REL_OTHER_REASON = Connection Release - Other Reasons
AN_INIT_ESTABLISHED_CONN = Number of AN initiated successful connections.
CROSS_CARR_ATTMPT_RCVD_TCC_RCVD = This count is pegged for each
sector-carrier selected for traffic channel allocation by the load balancing algorithm.
CROSS_CARR_ATTMPT_SENT_TCC_RCVD = This count is pegged for each
sector-carrier that received theconnection request. It is pegged against the sector-carrier
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Handoff Metrics
Handoff Metrics
............................................................................................................................................................................................................................................................

("hand-outs") perspective. The peg counts are defined on a per sector-carrier basis. The
formula is revised in R25. The new formula is applicable for releases R25 and later. Note
that the pre-TCA other failures peg count may include some normal connection releases
that occur prior to sending handoff TCA. Therefore the peg count may be inflated and the
success rate calculation may be artificially low.
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
SO_SOR_HOFF_ATTMPT = This count is the number of soft/er handoff attempts being
processed. If there are multiple triggers in a RUM that are being acted upon in a single
TCA, then the count is pegged only once. Note that the count is pegged even if the RUM
with an add trigger is discarded because the connection is already at the maximum number
of active set legs allowed and there are no suitable pilots in the active set that can be
dropped as part of the same TCA. In addition, another count,
............................................................................................................................................................................................................................................................
So_Sor_Hoff_Fail_Max_No_Legs_Reached, is pegged. All of these handoff counts are

pegged on the sector that received Route Update message, i.e., the DRC-pointed sector
(also known as requesting or source sector).
a connection close or session close is received before TCA and prior to completion of the
handoff procedure.
SO_SOR_HOFF_CONN_CLOSE_POSTTCA= The number of soft/softer handoffs when
a connection close or session close is received after TCA but prior to completion of the
handoff procedure.
handoff request cannot be processed because the total number of legs already has reached
the maximum specified by the translation and there is no strong candidate pilot on the
RUM that can replace a weaker active set pilot. Beginning in R25, handoff attempts will
SO_SOR_HOFF_FAIL NO_RESOURCE = Soft-Softer HO Attempt failure due to the
AN's inability to send a TCA because the candidate sector being added is already
supporting the maximum number of connections allowed.
SO_SOR_HOFF_FAIL_NO_AT_RSP = Soft-Softer HO Attempt failure due to no
SO_SOR_HOFF_FAIL_OTHER_PRETCA = These are TCA allocation failures
stemming from issues such as no response from the sector being added (link failures or
misconfigured link between cell/RNC), inability to build/send internal messages, neighbor
list provisioning issues, etc. Basically, it is a catch-all for handoff failures not specifically
pegged.
SO_SOR_HOFF_FAIL_OTHER_POSTTCA = Soft-Softer HO Attempt failure due to
other reasons after TCA is sent.

("handouts") perspective. The peg counts are defined on a per sector-carrier basis. This
metric is new in R26 and is effective with R26. Note that the pre-TCA failures peg count
may include some normal releases that occur prior to TCA. Therefore the peg count may
be inflated and the success rate calculation may be artificially low. he formula is changed
in R28 to subtract the new peg counts measuring hard handoff terminations due to receipt
of a session close or connection close message. The new formula is applicable to releases
R28 and later.
............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------------------------------------------------- X 100
Count Definitions
HHOFF_ATTMPT_REQ = This count is the number of Hard handoff attempts being
processed. A hard handoff is attempted if, after processing a RUM, the AN determines that
an inter-frequency handoff is necessary. All of these handoff counts are pegged on the
sector-carrier that received Route Update message.
HHOFF_CONN_CLOSE_POSTTCA_REQ = This count is the number of inter-frequency
hard handoff attempts that are terminated when a connection close or session close is
received after TCA. It is pegged on the sector-carrier that received the Route Update
HHOFF_CONN_CLOSE_PRETCA_REQ = This count is the number of inter-frequency
received before TCA. It is pegged on the sector-carrier that received the Route Update
HHOFF_FAIL NO_RESOURCE_REQ = Hard HO Attempt failure due to the AN's
inability to send a TCA because the candidate sector-carrier being added is already
supporting the maximum number of connections allowed.
HHOFF_FAIL_NO_AT_RSP_REQ = Hard HO Attempt failure due to no response from
the AT, i.e., a Traffic Channel Complete (TCC) message was not received from the AT in
HHOFF_FAIL_OTHER_PRETCA_REQ = These are TCA allocation failures stemming
from issues such as no response from the sector-carrier being added (link failures or
misconfigured link between cell/RNC), inability to build/send internal messages, neighbor
list provisioning issues, etc. Basically, it is a catch-all for handoff failures not specifically
pegged.
HHOFF_FAIL_OTHER_POSTTCA_REQ = Hard HO Attempt failure due to other
reasons after TCA is sent.
............................................................................................................................................................................................................................................................

Formula
------------------------------------------------------------------------------------------------ X 100
Count Definitions
sectorcarrier
handoffs when a connection close or session close is received before TCA and prior to
handoffs when a connection close or session close is received after TCA but prior to
............................................................................................................................................................................................................................................................

request cannot be processed because the total number of legs has reached the maximum
specified by the translation. Handoff attempts will also be pegged when the maximum
at the target sector-carrier due to other reasons prior to traffic channel assignment
SO_SOR_HOFF_FAIL_OTHER_POSTTCA_TARGET = Soft-Softer HO Attempt failure
at the target sector-carrier due to other reasons after traffic channel assignment

Formula
--------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
interfrequency hard handoff attempts that are terminated when a connection close or
session close is received after TCA. It is pegged on the target sector-carrier.
session close is received before TCA. It is pegged on the target sector-carrier.
sectorcarrier due to no response from the AT.

resources at the candidate cell (message exchange issues between the RNC and the cell). If
a handoff is prevented because of a full active set (applies in case of handoff adds), this is
not even counted as a handoff attempt, so it is not taken into the metric computation.
Instead, it is captured as a separate peg count to reflect optimization needs. One point to
note is that the handoff blocks for most part apply to adds. There is no allocation to be
made for drops - any issues with the allocation process might have already prevented the
add itself.The peg counts are defined on a per sector-carrier basis and are pegged at the
requesting sector. The formula is revised in R25 to more closely match other blocking
formulae and is applicable to all prior releases.
............................................................................................................................................................................................................................................................
Formula
---------------------------------------------------------------------------------------------------- X 100
Coun t Definitions
a connection close or session close is received before TCA and prior to completion of the
handoff procedure.
RUM from the AT, the AN decides to perform soft/er handoff. If the TCA allocation
process succeeds (only needed for an add at the candidate cell, for drop traffic channel
resource de-allocation is performed after receiving TCC), the AN sends TCA to apprise
the AT of the new active set. When the TCA is sent, AN pegs the
SO_SOR_HOFF_ATTMPT_TCA_SENT count. By definition, it signifies a successful
traffic channel resource allocation, but pending TCC from the AT.
handoff request cannot be processed because the total number of legs already has reached
the maximum specified by the translation. Beginning in R25, handoff attempts will also be
............................................................................................................................................................................................................................................................

sources.
the cell).
sector. The metric is new in R26 and is effective with R26. The relative distribution of
individual peg counts that contribute to the blocking can be seen from
HHOFF_FAIL_NO_RESOURCE_REQ
and
Formula
HHOFF_TCA_SENT_REQ)
------------------------------------------------------------------------------------------ X 100
Count Definitions
an inter-frequency handoff is necessary.
............................................................................................................................................................................................................................................................
HHOFF_CONN_CLOSE_PRETCA_REQ = This count is the number of inter-frequency

received before TCA. It is pegged on the sector-carrier that received the Route Update
HHOFF_TCA_SENT_REQ = This count is pegged when a Traffic Channel Assignment
message is sent to perform an inter-frequency hard handoff. Both of these handoff counts
are pegged on the sector-carrier that received Route Update message, i.e., the DRC-
pointed sector (also known as requesting or source sector).

Formula
---------------------------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
handoffs when a connection close or session close is received before TCA and prior to
request cannot be processed because the total number of legs has reached the maximum
specified by the translation. Handoff attempts will also be pegged when the maximum

Formula
-------------------------------------------------------------------------------------- X 100
Count Definitions
session close is received prior to TCA.
............................................................................................................................................................................................................................................................

Formula
------------------------------------------------------------------------------ X 100
Count Definitions
SO_SOR_HOFF_FAIL_NO_AT_RSP = Soft-Softer HO failures due to no response from
the AT in response to a TCA sent by the AN
SO_SOR_HOFF_ATTMPT_TCA_SENT = TCA sent in response to a soft/softer handoff
request.
a connection close or session close is received after TCA but prior to completion of the
handoff procedure.

............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------- X 100
Count Definitions
HHOFF_FAIL_NO_AT_RSP_REQ = Hard HO failures due to no response from the AT in
response to a TCA sent by the AN.
HHOFF_TCA_SENT_REQ = TCA sent in response to a hard handoff request.
HHOFF_CONN_CLOSE_POSTTCA_REQ = This count is the number of inter-frequency
received after TCA. It is pegged on the sector-carrier that received the Route Update
1xEV-DO Percentage of AT-Assisted Interfrequency Handoffs - Requesting Sector

Beginning in R31the performance of AN-directed handoffs between carriers that have
different coverage areas is improved by algorithms using AT messaging of pilot strength
measurements and distance to the BTS. New Service Measurements are added to monitor
the performance of the new feature. Counts are provided only for the requesting sector
since there are no new parameters related to the target sector.
This metric provides the number of AT-assisted interfrequency hard handoff attempts as a
percentage of all Hard Handoff attempts, at the requesting sector.
sector. The metric is new in R31 and is not applicable to prior releases.
............................................................................................................................................................................................................................................................
Formula
DO Percentage of AT-Assisted IFHO - Requesting Sector (%) =
HHOFF_ATTMPT_REQ - (HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ +
HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ)
----------------------------------------------------------------------------------------------------X 100
HHOFF_ATTMPT_REQ
Count Definitions
an inter-frequency handoff is necessary.
HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ = This count is incremented for each
attempt whenever an AN directed interfrequency hard handoff is triggered by pilot
strength evaluation after processing a Route Update message. It is incremented for the
sector-carrier that received the Route Update message that prompted the handoff. It is the
total of all such handoff attempts for a requesting sector-carrier. This count is incremented
even if the Distance-Based Hand-Off feature is disabled.
HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ = This count is incremented for each
attempt whenever an AN directed interfrequency hard handoff is deemed necessary after
processing a Route Update Message and the calculated distance of the AT from each
IFHO enabled sector-carrier in the active set exceeds the respective IFHO upper distance
threshold. It is incremented for the sector-carrier that received the Route Update message
that prompted the handoff. It is the total of all such handoff
1xEV-DO Directed IFHO Triggered by Pilot Strength Success Rate - Requesting Sector (%)
This metric provides the success rate of directed Interfrequency Hard Handoffs that are
triggered by the Pilot Strength measurements for the requesting sector.
sector. This metric is new in R31 and is not applicable to prior releases.
............................................................................................................................................................................................................................................................
Formula
DO AN-Directed HHO Triggered by Pilot Strength Success Rate - Requesting Sector (%)
= (HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ -
HHOFF_NOP_AN_DIRECT_PILOT_REQ -
HHOFF_FAIL_AN_DIRECT_PILOT_REQ)
---------------------------------------------------------------------------------------------------- X 100
(HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ -
HHOFF_NOP_AN_DIRECT_PILOT_REQ)
Count Definitions
HHOFF_ATTMPT_AN_DIRECT_PILOT REQ = This count is incremented for each
HHOFF_NOP_AN_DIRECT_PILOT_REQ = This count is incremented for each AN-
directed hard handoff attempt, triggered by pilot strength measurements, that was not
completed due to a connection/session close prior to the TCA being sent, or a normal AT-
initiated connection release. It is incremented for the sector-carrier that received the Route
Update message that prompted the handoff. It is the total of all such not processed handoff
attempts for a requesting sector-carrier. This count is incremented even if the Distance-
Based Hand-Off feature is disabled.
HHOFF_FAIL_AN_DIRECT_PILOT_REQ = This count is incremented for each failed
AN directed interfrequency hard handoff that was triggered by pilot strength evaluation. It
is incremented for the sector-carrier that received the Route Update message that
prompted the handoff. It is the total of all failures of all such handoff attempts for a
requesting sector-carrier.
1xEV-DO Directed IFHO Triggered by Upper Distance Threshold Success Rate - Requesting
Sector (%)
This metric provides the success rate of directed Interfrequency Hard Handoffs that are
triggered by the upper distance threshold for the requesting sector.
sector. This metric is new in R31 and is not applicable to prior releases.
............................................................................................................................................................................................................................................................
Formula
DO AN-Directed HHO Triggered by Upper Distance Threshold Success Rate -
Requesting Sector (%) = (HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ -
HHOFF_NOP_AN_DIRECT_UPPER_REQ -
HHOFF_FAIL_AN_DIRECT_UPPER_REQ)
--------------------------------------------------------------------------------------------------- X 100
(HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ -
HHOFF_NOP_AN_DIRECT_UPPER_REQ)
Count Definitions
HHOFF_ATTMPT_AN_UPPER_PILOT_REQ = This count is incremented for each
attempt whenever an AN directed interfrequency hard handoff is triggered by the IFHO
upper distance threshold after processing a Route Update message. It is incremented for
the sector-carrier that received the Route Update message that prompted the handoff. It is
the total of all such handoff attempts for a requesting sector-carrier. This count is
incremented even if the Distance-Based Hand-Off feature is disabled.
HHOFF_NOP_AN_DIRECT_UPPER_REQ = This count is incremented for each AN-
directed hard handoff attempt, triggered by the IFHO upper distance threshold, that was
not completed due to a connection/session close prior to the TCA being sent, or a normal
AT-initiated connection release. It is incremented for the sector-carrier that received the
Route Update message that prompted the handoff. It is the total of all such not processed
handoff attempts for a requesting sector-carrier. This count is incremented even if the
Distance-Based Hand-Off feature is disabled.
HHOFF_FAIL_AN_DIRECT_UPPER_REQ = This count is incremented for each failed
AN directed interfrequency hard handoff that was triggered by the IFHO upper distance
threshold. It is incremented for the sector-carrier that received the Route Update message
that prompted the handoff. It is the total of all failures of all such handoff attempts for a
requesting sector carrier.
1xEV-DO Round Trip Delay Measurement Validity Rate

This metric provides the validity rate of the Round Trip Delay (RTD) measurement in the
Route Update Messages on IFHO enabled sector-carriers. The RNC determines the
validity of the measurements by collecting them for a sector-carrier over an interval
defined by the IFHO distance validity check parameter. The validity check is only
performed if the Distance-based HHO feature is enabled and on sectors where the validity
check period is non-zero.
The peg counts are defined on a sector-carrier basis and are pegged on the Reference
sector-carrier. The Reference Sector- Carrier is the sector-carrier that corresponds to the
reference pilot (ReferencePilotPN) in the Route Update Message (RUM). The AT uses this
............................................................................................................................................................................................................................................................
as its timing reference. It is not necessarily the strongest pilot. Since the RTD
measurerments are used to engineer the validity check period which can be set at the
sector level,, the counts have to be summed over all carriers in the sector, therefore the
metric is provided at the sector level. The metric is new in R31 and is not applicable to
prior releases.
Formula
DO RTD Measurement Validity Rate (%) = SUM over CARRIERS IN SECTOR
(HHOFF_VALID_RTD)
--------------------------------------------------------------------------------------------------- X 100
SUM over CARRIERS IN SECTOR (HHOFF_VALID_RTD + HHOFF_INVALID_RTD)
Count Definitions
HHOFF_VALID_RTD = The RNC determines the validity of the AT round trip delay
(RTD) measurements in the Route Update Messages on IFHO enabled sector-carriers in
the active set. The RNC accomplishes this by collecting RTD measurements for a sector-
carrier over an interval defined by the IFHO distance validity check parameter, and
checking the slew rate. The RNC can use the valid RTD measurements in the
interfrequency hard handoff evaluation. When the IFHO distance validity check parameter
is zero, all these RTD measurements are considered valid. This measurement is
incremented on the reference sector-carrier. This service measurement is the total number
of valid RTD measurements in the service measurement interval for the sector-carrier.
HHOFF_INVALID_RTD = The RNC determines the validity of the AT round trip delay
(RTD) measurements in the Route Update Messages on IFHO enabled sector-carriers in
the active set. The RNC accomplishes this by collecting RTD measurements for a sector-
carrier over an interval defined by the IFHO distance validity check parameter, and
checking the slew rate. The RNC does not use the invalid RTD measurements in the
interfrequency hard handoff evaluation. This service measurement is incremented for each
invalid RTD measurement. This measurement is incremented on the reference
sectorcarrier. This service measurement is the total number of invalid RTD measurements
in the service measurement interval for the sector-carrier. When the IFHO distance
validity check parameter is zero for a sector, this count will always be 0 for the carriers on
that sector since the validity check will not be performed.
1xEV-DO Average Distance Between AT and BTS for Pilot Strength Triggered Directed IFHO
Each time an interfrequency hard handoff is triggered by pilot strength measurements, the
RNC records the distance of the AT from the requesting sector. The measurement is either
in miles or kilometers, depending on the value of the Distance Units threshold parameter
set by the user.
............................................................................................................................................................................................................................................................
This metric provides the average distance of the AT from the requesting sector for these
pilot strength triggered IFHOs. It is used by the operator to tune the upper and lower
distance thresholds. The cell design may also need to be evaluated if an unexpected value
is observed.
The peg counts are defined on a sector-carrier basis. The metric is new in R31 and is not
Formula
DO Avg Distance Between AT and BTS for PS Triggered Directed IFHOs =
HHOFF_DIST_AN_DIRECT_PILOT_REQ
----------------------------------------------------------------- X 0.01
HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ
Count Definitions
HHOFF_DIST_AN_DIRECT_PILOT_REQ = Each time an AN-directed interfrequency
hard handoff is triggered by pilot strength measurements, the RNC records the distance of
the AT from the requesting sector. These distance measurements are accumulated in this
service measurement. Post processing can calculate the average AT distance to the
requesting sector for these handoffs by dividing this service measurement by
HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ and then dividing by 100. The result is in
miles or kilometers depending on the Distance Threshold Units parameter.
HHOFF_ATTMPT_AN_DIRECT_PILOT_REQ = This count is incremented for each
1xEV-DO Average Ratio of Pilot Strength and Threshold for IFHO

For each AN directed interfrequency hard handoff that is triggered by the IFHO upper
distance threshold, the RNC records the delta between the sum of the pilot strengths of the
IFHO enabled active legs and the Pilot PN Signal Strength Threshold for Directed Inter
Frequency Handoff for the requesting sector carrier.
This metric provides the average delta (ratio) between the pilot strengths and the threshold
in dB. It is used by the operator to tune the IFHO Upper Distance threshold and/or the
Pilot PN Signal Strength threshold for Directed IFHOs. The peg counts are defined on a
............................................................................................................................................................................................................................................................
The metric is new in R31 and is not applicable to prior releases.
Formula
DO Avg Ratio of Pilot Strength to Threshold (dB) = 10 *log *
HHOFF_PILOT_DELTA_AN_DIRECT_UPPER_REQ / 1000
----------------------------------------------------------------------------------------------
HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ
Count Definitions
HHOFF_PILOT_DELTA_AN_DIRECT_UPPER_REQ = For each AN directed
interfrequency hard handoff that is triggered by the IFHO upper distance threshold, the
RNC records the delta between the sum of the pilot strengths of the IFHO enabled active
legs and the Pilot PN Signal Strength Threshold for Directed Inter Frequency Handoff for
the requesting sector carrier. This count is the sum of the deltas for the measurement
interval.
HHOFF_ATTMPT_AN_DIRECT_UPPER_REQ = This count is incremented for each
AN-directed hard handoff attempt, triggered by the IFHO upper distance threshold, that
was not completed due to a connection/session close prior to the TCA being sent, or a
normal AT-initiated connection release. It is incremented for the sector-carrier that
received the Route Update message that prompted the handoff. It is the total of all such not
processed handoff attempts for a requesting sector-carrier. This count is incremented even
if the Distance-Based Hand-Off feature is disabled.

R24 and later.
............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------- X 100
Count Definitions
SO_SOR_HOFF_FAIL_NO_AT_RSP_TARGET = Soft-Softer HO failures due to no
response from the AT in response to a TCA sent by the AN.
soft/softer handoff request.
handoffs when a connection close or session close is received after TCA but prior to

Formula
--------------------------------------------------------------------------------- X 100
............................................................................................................................................................................................................................................................
Count Definitions
HHOFF_FAIL_NO_AT_RSP_TARGET = Hard HO failures due to no response from the
AT in response to a TCA sent by the AN.
HHOFF_TCA_SENT_TARGET = TCA sent in response to a hard handoff request.
HHOFF_CONN_CLOSE_POSTTCA_TARGET = This count is the number of inter-
frequency hard handoff attempts that are terminated when a connection close or session
close is received after TCA but prior to completion of the handoff process.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Data Transmission Metrics

............................................................................................................................................................................................................................................................

The AT requests the re-transmission when it encounters a gap in sequence number in its
receive queue. In essence, if a RLP packet with sequence N is missed, it is not until the
receipt of packet N+1 before the AT senses the loss. At this point, the AT sends a NAK
(negative acknowledgement) and requests the AN to resend the lost data.
in RLP NAKs.
Formula
DO forward retransmission rate (%) =
RLP_RETXED_FTC
------------------------------------------ X 100
RLP_TXED_FTC
Count Definitions
the AT via RLP NAKs. In 1xEV-DO, there is only one retry allowed. If the AT is unable to
receive the original RLP data on the forward link which it is able to identify by seeing a
gap in sequence number on successive RLP packets, it requests the AN to resend the
............................................................................................................................................................................................................................................................
missing data by send a NAK message. The NAK message contains the starting sequencing
number as well as the length of the missing block of data. When the AT receives the re-
transmitted data, it plugs the gap and goes on with further processing. If it still does not
receive data within a certain period of sending the NAK, then it is up to the higher layers
to recover. The purpose of implementing RLP layer in a wireless data network is to
present the upper layers with an extremely low error probability channel. The upper layers
were designed a while back for wired connections, and do not operate well on a lossy
channel.
traffic channel of a given sector. It is raw user payload plus any overhead bytes from
protocol layers above RLP (Application/TCP/IP/PPP), including any data that could not
be delivered to the end user even after the single RLP retry. It does not include RLP layer
overhead bytes or RLP layer re-transmissions.

in RLP NAKs.
releases.
............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------------------------X 100
Count Definitions
RLP octet that is re-transmitted to an AT in response to a NAK recevied from the previous
tranmission. It is the total of all octets retransmitted on the forward traffic channels for a
sector-carrier.
octet that is re-transmitted to an AT in response to a NAK recevied from the previous
tranmission. It is the total of all octets retransmitted on the forward traffic channels for a
sector-carrier.This count shall not include the RLP octets retransmitted on FTC when
DARQ is turned on.
RLP octet transmitted to an AT and it shall not include any octets that may be used for
padding at the MAC layer. It is the total of all octets transmitted on the forward traffic
a sector-carrier. This count shall not include any of the re-transmitted RLP octets.

............................................................................................................................................................................................................................................................
RLP NAKs.
releases.
Formula
---------------------------------------------------------------------------------------------------- X 100
Count Definitions
Effort RLP octet that is re-transmitted to an AT when DARQ is turned on. It is the total of
all octets retransmitted on the forward traffic channels for a sector-carrier.
Push-to-Talk RLP octet that is re-transmitted to an AT when DARQ is turned on. It is the
total of all octets retransmitted on the forward traffic channels for a sector-carrier.
Conversational Speech (with or without ROHC) RLP octet that is retransmitted to an AT
when DARQ is turned on. It is the total of all octets retransmitted on the forward traffic
............................................................................................................................................................................................................................................................

Conversational Video (with or without ROHC) RLP octet that is retransmitted to an AT
when DARQ is turned on. It is the total of all octets retransmitted on the forward traffic
SMC RLP octet that is re-transmitted to an AT due to DARQ is turned on. It is the total of
all octets retransmitted on the forward traffic channels for a sector-carrier.
channels for a sector-carrier. This count shall not include any of the re-transmitted RLP
octets.
Speach (with or without ROHC) RLP octet transmitted to an AT and it shall not include
any octets that may be used for padding at the MAC layer. It is the total of all octets
transmitted on the forward traffic channels for a sector-carrier. This count shall not include
Video (with or without ROHC) RLP octet transmitted to an AT and it shall not include any
octets that may be used for padding at the MAC layer. It is the total of all octets

............................................................................................................................................................................................................................................................
perfectly fine.
releases. The new formula only includes BE and SMC flows since CS and CV do not have
re-transmission on the reverse link.
The formula is corrected in R31 to account for the fact that RLP_RXED_RTC includes
octets for all flows. The new formula is applicable to R30.
Formula
MISSING_RLP_REQ_RTC_BE + MISSING_RLP_REQ_RTC_SMC
---------------------------------------------------------------------------------------------------X 100
RLP_RXED_RTC- RLP_RCVD_RTC_CPS - RLP_RCVD_RTC_CS -
RLP_RCVD_RTC_CV
Count Definitions
DRC pointed sector.
protocol layers above RLP (Application/TCP/IP/PPP). It does not include RLP layer
overhead bytes, RLP layer re-transmissions or any data lost in transit even after the single
RLP retry by the AT.
RLP_RCVD_RTC_CPS = This count shall be incremented for each CPS RLP octet
received at the TP. It is the total of all octets received on the reverse traffic channels for a
sector-carrier.
............................................................................................................................................................................................................................................................
RLP_RCVD_RTC_CS = This count shall be incremented for each CS RLP octet received
at the TP. It is the total of all octets received on the reverse traffic channels for a sector-
carrier.
RLP_RCVD_RTC_CV = This count shall be incremented for each CV RLP octet received
at the TP. It is the total of all octets.

retransmission from the AT got corrupted). However, the issues that led to the
retransmissions in the first place may also contribute to a higher re-transmission failure
rate (RF link degradation, AT taking longer than usual on a hybrid mode periodic search of
releases. Note that this metric is only for retransmission failures of BE and SMC octets
since CS and CV octets are not retransmitted. Separate peg counts are available to measure
missing octets never received for CS and CV flows.
Formula
(MISSING_RLP_NEVER_RXED_RTC_BE +
MISSING_RLP_NEVER_RXED_RTC_SMC)
-------------------------------------------------------------------------------------------X100
............................................................................................................................................................................................................................................................
Count Definitions
MISSING_RLP_NEVER_RXED_RTC_BE = This count is incremented for each BE RLP
octet that was missing from the RLP receive buffer when the buffer's contents were passed
to the higher layer protocol. It is the total of all BE octets not received for the reverse
traffic channels on a sector-carrier.
MISSING_RLP_NEVER_RXED_RTC_SMC = This count is incremented for each SMC
passed to the higher layer protocol. It is the total of all SMC octets not received for the
reverse traffic channels on a sector-carrier. This count is pegged against the DRC pointed
sector.
DRC pointed sector.

This metric provides a measure of the error rate for CS and CV packets on the reverse link.
CS and CV packets are not retransmitted if the packet does not reach the AN. However,
the missing packets are noted and the appropriate counts are pegged.
This metric is defined on a per sector-carrier basis. The metric is new and effective in R30
and is not applicable to prior releases. Note that this metric is only for transmission
failures of CS and CV octets. There are separate metrics for the retransmission rate and
retransmission failure rates of BE and SMC octets.
Formula
DO reverse transmission error rate for CS and CV (%) =
(MISSING_RLP_NEVER_RXED_RTC_CV +
MISSING_RLP_PACKET_NEVER_RXED_RTC_CS)
-------------------------------------------------------------------------------------------X100
(RLP_RCVD_RTC_CV+ RLP_RCVD_RTC_CS)
............................................................................................................................................................................................................................................................
Count Definitions
MISSING_RLP_NEVER_RXED_RTC_CV = This count is incremented for each CV
passed to the higher layer protocol. It is the total of all CV octets not received for the
reverse traffic channels on a sector-carrier.
MISSING_RLP_PACKET_NEVER_RXED_RTC_CS = This count is incremented for
each CS RLP octet that was missing from the RLP receive buffer when the buffer's
contents were passed to the higher layer protocol. It is the total of all CS octets not
received for the reverse traffic channels on a sector-carrier. This count is pegged against
the DRC pointed sector.
RLP_RCVD_RTC_CV = This count is incremented for each CV RLP octet received on
the RL. It is the total of all CV octets for the reverse traffic channels for a sector-carrier.
This count is pegged against the DRC pointed sector.
RLP_RCVD_RTC_CS = This count is incremented for each CS RLP octet received on the
RL . It is the total of all CS octets for the reverse traffic channels for a sector-carrier. This
count is pegged against the DRC pointed sector.

MAC layer. The formula is changed in R24 to account for the peg counts being MAC layer
Formula
............................................................................................................................................................................................................................................................
------------------------------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
............................................................................................................................................................................................................................................................

Formula
-----------------------------------------------------------------------------------------------------------
10 ^ 6
Count Definitions
FTC by the SBEVM to the AT at a nominal rate of 4.8 kbps for both Rel 0 and Rev A
traffic.
traffic.
traffic.
traffic.
............................................................................................................................................................................................................................................................

traffic.
the FTC by the SBEVM to the AT at a nominal rate of 153.6 kbps for both Rel 0 and Rev
A traffic.
A traffic.
A traffic.
A traffic.
A traffic.
FTC by the SBEVM to the AT at a nominal rate of 1536 kbps for both Rel 0 and Rev A
traffic.
A traffic.
A traffic.
traffic.

formula is defined at the sector-carrier level and can be aggregated to higher level
network.elements. The composite formula is: =
............................................................................................................................................................................................................................................................
+
--------------------------------------------------------------------------------------- =
10 ^ 6

............................................................................................................................................................................................................................................................
sector.
............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
( ((EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^ 8) * 2,160,000) -
(EVM_FTC_NUM_SLOT_rate)) * 0.001667, where the summations are over all sector-
carriers being aggregated.
Formula
............................................................................................................................................................................................................................................................
------------------------------------------------------------------------------------------------------------
Count Definitions
EVM_FWD_PACKETS_307_2_L_TOTAL_COUNT= Total MAC packets transmitted on
forward traffic channels at 307.2 kbps - long format (1024bits/packet)
EVM_FWD_PACKETS_614_4_L_TOTAL_COUNT= Total MAC packets transmitted on
forward traffic channels at 614.4 kbps - long format (1024 bits/packet)
............................................................................................................................................................................................................................................................

measurement hour used for forward link traffic data transmission (divide by 10^6 to get
percentage)
This data rate metric can be interpreted as a measure of RF efficiency of the sector. This
metric utilizes the actual number of slots used to send the data rather than the percent busy
slots count used by the EVM. Note that since the metric in the denominator counts up the
actual active transmission slots it's not counting multiple times if there are multiple ATs in
the queue. These considerations point out that the metric does not represent
............................................................................................................................................................................................................................................................
higher rates.
hardware, etc.).
EVM.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------
Count Definitions
traffic.
traffic.
traffic.
traffic.
traffic.
............................................................................................................................................................................................................................................................

A traffic.
A traffic.
A traffic.
A traffic.
A traffic.
traffic.
A traffic.
A traffic.
traffic.
on the FTC by the SBEVM to the AT at a nominal rate of 4.8 kbps for both Rel 0 and Rev
A traffic.
A traffic.
data on the FTC by the SBEVM to the AT at a nominal rate of 19.2 kbps for both Rel 0 and
Rev A traffic.
............................................................................................................................................................................................................................................................

Rev A traffic.
Rev A traffic.
data on the FTC by the SBEVM to the AT at a nominal rate of 153.6 kbps for both Rel 0
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
data on the FTC by the SBEVM to the AT at a nominal rate of 1536 kbps for both Rel 0
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
............................................................................................................................................................................................................................................................

=
+
EVM_FTC_TOT_BYTES_2457_6 + EVM_FTC_TOT_BYTES_3072)) /1000
--------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
sectorcarrier. It uses the active usage peg count which measures the number of users either
Formula
-----------------------------------------------------------------------------------------------------------
Count Definitions
traffic.E
traffic.
traffic.
............................................................................................................................................................................................................................................................

traffic.
traffic.
A traffic.
A traffic.
A traffic.
A traffic.
A traffic.
traffic.
A traffic.
A traffic.
traffic.
shall be incremented by the number of users who have data to send for any flow (BE, or
EF), either waiting to be scheduled or in the process of transmission.
............................................................................................................................................................................................................................................................
This count shall be incremented based on the users (not flows) as long as they have data to
be served regardless of whether the DRC is 0, or there is a DRC erasure, or the cover is not
pointing to sector. Only one sector shall peg each user towards this count.
If a multi-slot packet terminates early and there are no more packets (scheduled or not),
the user shall no longer be counted in the measurement as soon as the ACK is received on
the reverse link. If the transmission goes on till the maximum allowed continuations, the
pegging shall be stopped at the last continuation (no need to wait for the last
ACK/NACK).
This count shall be pegged on a Rev A capable carrier (a carrier equipped with a SBEVM)
for both Rev A and Rel 0 traffic.

856 standards for the forward link. Therefore, a metric such as active connections is
onlyof secondary value to quantify the forward link usage (secondary in the sense that the
operator may still want to make sure that a given sector does not outrun any other
forwardlink constraints, such as max of 64 MAC indices allowed by the standards). But
the primary way to characterize forward link loading requires one to look at the percentage
of slots being used in an hour to serve traffic users. A higher utilization increases the
users.
releases beginning with R22. Note that the peg count measures only those slots used
foractual traffic transmission so the control slot counts do not have to be subtracted.
Formula
............................................................................................................................................................................................................................................................
Count Definitions
measurement hour that were actually used for forward link traffic data transmission
(divide by 10^6 to get percentage)

per second.
The peg counts are measured at the RLP layer. The metric carries a sector level?
connotation rather than a per user? view given the denominator includes the total traffic
channel slots used in an hour. So it reflects the average RF conditions the sector serves.
The RLP byte count is closer to the actual user traffic with less overhead than either MAC
layer or physical layer packet counts, which can be padded with dummy bits to fill the
packet.
retransmitted RLP packets not reaching the end user (typically ~0.02% for a 1%
retransmission rate).
some small amount of data gets transmitted to both the old & the new cells, resulting in
double pegging at the TP.
amount of error stemming from pegging bytes on the older sector a little while longer than
actual virtual softer handoff transfer. There is no impact if RLP bytes are viewed on a per-
cell basis or RNC/SN wide The impact of the second and third issues is most noticeable at
very low loading points where RLP bytes appear larger than the MAC data volume on a
............................................................................................................................................................................................................................................................
given sector. Given the above issues, RLP data rate should only be viewed as an estimate
of actual rate, although it is not far off the mark especially at moderate to high loading
points.
Formula
--------------------------------------------------------------------
Count Definitions
protocol layers above RLP (Application/TCP/IP/PPP), including any data that could not
be delivered to the end user even after the single RLP retry. It does not include RLP layer
overhead bytes or RLP layer re-transmissions.
............................................................................................................................................................................................................................................................
per second. The metric is defined on a per sector-carrier basis for sectors equipped with an
SBEVM and is defined only for the one hour measurement interval. It cannot be directly
summed to obtain results for longer time periods. The individual counts must be rolled up
and then the data rate can be calculated. The peg counts are measured at the RLP layer.
The metric carries a . ector level ? connotation rather than a B er user ? view given the
Formula
---------------------------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
octets.
any octets that may be used for padding at the MAC layer.
It is the total of all octets transmitted on the forward traffic channels for a sector-carrier.
A traffic.
A traffic.
Rev A traffic.
............................................................................................................................................................................................................................................................

Rev A traffic.
Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.
and Rev A traffic.

............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------

This metric gives the average data rate for Best Effort (BE) traffic on the forward link at
the RLP layer in kilobits per second. The metric is defined on a per sector-carrier basis for
sectors equipped with an SBEVM and is defined only for the one hour measurement
interval. It cannot be directly summed to obtain results for longer time periods. The
individual counts must be rolled up and then the data rate can be calculated. The peg
counts are measured at the RLP layer.
The metric carries a sector-carrier level connotation rather than a per user view given
the denominator includes the total traffic channel slots used for BE data in an hour. So it
reflects the average RF conditions the sector-carrier serves. The RLP byte count is closer
to the actual user traffic with less overhead than either MAC layer or physical layer packet
of RF conditions at the time the user was served. Note that there are 2,160,000 slots in one
milliseconds).
regarding the use of the metric discussed in the prior metrics for the EVM do not apply to
sector-carriers equipped with an SBEVM. The only remaining potential source of
............................................................................................................................................................................................................................................................
This metric is new in R30 and is not applicable to prior releases. Note that the same packet
can carry BE and EF traffic and both busy slots counts would be pegged. So the sum of the
total busy slots for BE plus total busy slots for EF won't necessarily equal the total busy
slots count.
Formula
DO RLP Fwd Link Data Rate BE Traffic (kbps) =
(EVM_RLP_TXED_FTC_BE * 8) / 1000
------------------------------------------------------------------------------------------------------------
(EVM_TOTAL_BUSY_SLOTS_BE * 0.001667)
Count Definitions
a sector-carrier.
EVM_TOTAL_BUSY_SLOTS_BE = This count shall measure the total number of busy
slots on the forward link used for BE (Best Effort) traffic data transmission for the sector-
carrier.
............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------------------------------------------------
Count Definitions
octets.
............................................................................................................................................................................................................................................................
once per slot.
Formula
------------------------------------------------------------------------------------------------------------
Count Definitions
octets.
............................................................................................................................................................................................................................................................

shall be incremented by the number of users who have data to send for any flow (BE, or
EF), either waiting to be scheduled or in the process of transmission. This count shall be
incremented based on the users (not flows) as long as they have data to be served
regardless of whether the DRC is 0, or there is a DRC erasure, or the cover is not pointing
to sector. Only one sector shall peg each user towards this count.
If a multi-slot packet terminates early and there are no more packets (scheduled or not),
the user shall no longer be counted in the measurement as soon as the ACK is received on
the reverse link. If the transmission goes on till the maximum allowed continuations, the
pegging shall be stopped at the last continuation (no need to wait for the last
ACK/NACK).
This count shall be pegged on a Rev A capable carrier (a carrier equipped with a SBEVM)
for both Rev A and Rel 0 traffic.

This metric provides the average user data rate for BE traffic at the RLP layer in kilobits
per second.
The counts are measured at the TP at a sector-carrier level. Measurements are taken every
267 milliseconds and summed at the end of the measurement interval to represent the total
number of RLP bytes sent to the BTS for that sector-carrier and the total number of BE
users with data being sent or waiting to be sent to the BTS for that sector-carrier. The
measurements are made on a sampling of approximately 10% of the active connections
and only data rates above 20 kps are included.
The peg counts are on a sector-carrier basis. This metric is new and effective in R30.0.
............................................................................................................................................................................................................................................................
Formula
DO Average RLP Forward Link User Data Rate - BE (kbps) =
(RLP_SENT_TO_BTS_AT_TP_BE * 8) / 1000
------------------------------------------------------------------------------------------------------------
(USER_PRESENT_AT_TP_BE * 0.267)
Count Definitions
RLP_SENT_TO_BTS_AT_TP_BE = This count measures the total number of Best Effort
(BE) RLP octets sent to the BTS by the TP for all the sampled connections.
For each sampled connection, RNC/TP shall keep track of the RLP octets being sent to the
BTS for BE user data for each sampling interval if the BE user data sent is greater than the
defined threshold for each sampling interval. The measurements collected shall not
include the re-transmitted data. The threshold used for each sampling interval is equivalent
to 20kbps.
USER_PRESENT_AT_TP_BE = This count measures the total number of Best Effort
(BE) users present at the TP for the sampled connections if the user's BE data is greater
than the defined threshold or the user has data arrived but waiting to be sent to the BTS
during the sampling interval. For each sampling measureing interval, this count shall be
incremented by the number of BE users that either have data arrived waiting to be sent, or
sent during the interval for all the sampled connections. The threshold used for each
sampling interval is equivalent to 20kbps.
1xEV-DO Average RLP Forward Link User Data Rate - BE - BTS (kbps)
This metric provides the average user data rate for BE traffic at the RLP layer meaured at
the SBEVM in the BTS.
This metric differs from the previous metric, which is measured at the RNC, in that it
includes all BE octets at the SBEVM instead of sampling octets at the TP. The number of
users with data to send or waiting to be sent are also counted at the SBEVM.
This metric does not account for backhaul delays and is comparable to the other data rate
metrics measured at the BTS.
R31.
............................................................................................................................................................................................................................................................
Formula
DO RLP Avg RLP Forward Link User Data Rate - BE -BTS (kbps) =
((EVM_RLP_TXED_FTC_BE * 8) / 1000)
-----------------------------------------------------------------------------------------------------------
(EVM_ACTIVE_USAGE_BE * 0.001667)
Count Definitions
EVM_ACTIVE_USAGE_BE = For each slot (traffic channel or control channel) , this
count shall be incremented by the number of Best Effort users who have data to send,
either waiting to be scheduled or in the process of transmission and this count be reported
as the summation of all such users across all slots over the entire SM collection interval. If
a user has multiple packets waiting or in the middle of transmission, this count shall be
incremented by 1 in each transmission and intervening slot for the same user. This count
shall be incremented based on the users (not flows) as long as they have data to be served
regardless of whether the DRC is 0, or there is a DRC erasure, or the cover is not pointing
to sector. Only one sector shall peg each user towards this count. If a multi-slot packet
terminates early and there are no more packets (scheduled or not), the user shall no longer
be counted in the measurement as soon as the ACK is received on the reverse link. If the
transmission goes on till the maximum allowed continuations, the pegging shall be
stopped at the last continuation (no need to wait for the last ACK/NACK).
This count shall be pegged during all the intervening slots between the continuation slots,
even if there is no other data in the queue, or if other packets are using these intervening
slots.
This count is only reported for a sector-carrier equipped with an SB-EVM.

This metric provides the percentage of band width not used for traffic packets, i.e., for
control channel signalling messages. The computation includes asynchronous,
synchronous and sub-synchronous signalling messages.
R30.
............................................................................................................................................................................................................................................................
Formula
DO Percent BW Used for Signaling (%) =
(EVM_CC_SLOTS_SYNC_MSG_XMIT +
EVM_CC_SLOTS_SUBSYNC_MSG_XMIT +
EVM_CC_SLOTS_ASYNC_MSG_XMIT)
----------------------------------------------- ------------------------------X 100
2,160,000
Count Definitions
EVM_CC_SLOTS_SYNC_MSG_XMIT = This count measures the total number of slots
used for sending the synchronous signaling messages on the Control Channel for a
sectorcarrier.
This count shall not include the slots used for sending the sub-synchronous signaling
messages.
EVM_CC_SLOTS_SUBSYNC_MSG_XMIT = This count measures the total number of
slots used for sending the sub-synchronous signaling messages on the Control Channel for
a sector-carrier.
EVM_CC_SLOTS_ASYNC_MSG_XMIT = This count measures the total number of
slots used for sending the asynchronous signaling messages on the Control Channel for a
sector-carrier.
EVM_TOTAL_BUSY_PCNT_SLOTS = This count shall measure the percentage of
physical layer slots actually used for forward link traffic data transmission. The count
must be divided by 10^6 to obtain percentage.
............................................................................................................................................................................................................................................................
Formula
------------------------------------------------------------------------------------------------------------
8 * 10^6
Count Definitions
............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------------------------------------
8 * 10 ^ 6
Count Definitions
REV_PACKETS_128_TOTAL_COUNT = The number of actual physical layer packets of
128 bits received on the reverse traffic channel.
............................................................................................................................................................................................................................................................


............................................................................................................................................................................................................................................................
-----------------------------------------------------------------------------------------------------------
8 * 10^6
metric is defined on a per sector-carrier basis. The metric provides a measure of individual
user data rate, a good indicator of average user experience in the network on the reverse
link. Beyond a certain number of users on the sector, the individual user rate begins to
suffer because of the limited bandwidth on the air link. This behavior points to its possible
use in capacity planning for the reverse link.
rates.
Formula:
............................................................................................................................................................................................................................................................
---------------------------------------------------------------------------------------------------
Count Definitions
sectorcarriers equipped with an SBEVM. The metric is defined on a per sector-carrier
basis. The metric provides a measure of individual user data rate, a good indicator of
average user experience in the network on the reverse link. Beyond a certain number of
users on the sector, the individual user rate begins to suffer because of the limited
bandwidth on the air link. This behavior points to its possible use in capacity planning for
the reverse link.
of 6.6 ms.
Formula
............................................................................................................................................................................................................................................................

----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................

----------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
NUM_SUBPKTS_RL_12288) * 0.00667]

Formula
----------------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions

............................................................................................................................................................................................................................................................
Formula
----------------------------------------------------------------------------------------
Count Definitions
............................................................................................................................................................................................................................................................


aggregated to higher level network elements. The composite formula is DO Reverse Link
Composite RLP Throughput (kbps) =
----------------------------------------------------------------------------------------
+ [(NUM_SUBPKTS_RL_128 + NUM_SUBPKTS_RL_256 +
NUM_SUBPKTS_RL_512
NUM_SUBPKTS_RL_12288) * 0.00667]
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Error Statistics
Error Statistics
............................................................................................................................................................................................................................................................

at the AT).
level. The peg counts are only applicable to the EVM. The counts used in this metric will
be reported as 0 for sector-carriers equipped with an SBEVM.
Formula
Count Definitions
that could not be decoded properly and hence were discarded. These are the frames for
which the corresponding Reverse Rate Indicator (RRI) was successfully decoded and
indicated as 9.6kbps or higher, but its traffic channel content did not pass the CRC check.
In other words, only the frames which had traffic content are evaluated for CRC. There is
no traffic content on the 0kbps frame, hence no question of computing a CRC check.
Given that a erased frame, by definition, has a traffic content, this also implies that it will
result in RLP error as well, forcing a re-transmission (assuming the errors occurred on the
first RLP attempt). If there are multiple pilots in the active set, the status of only the
selected frame is pegged. The count is pegged only on the DRC pointed sector.
on the reverse traffic channel (both good and erased). It only includes the frames received
with rates of 9.6kbps or higher. If there are multiple pilots in the active set, status of only
the selected frame is pegged. The count is pegged only on the DRC pointed sector.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Error Statistics

link.
Formula
------------------------------------------------------- X 100
RL_LOLAT_PKTS_RCVD
Count Definitions
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Power Control
Power Control
............................................................................................................................................................................................................................................................

Formula
--------------------------------------------------------------------------------
Count Definitions
outer loop set point used when no reverse link traffic frame is received, i.e., the frame
rateis 0kbps. This is only counted on the DRC pointed sector. The units of the count are
dB/8.
basis.
Formula
---------------------------------------------------------------------------------
Count Definitions
outer loop set point used for frames in which the data rate is 9.6 kbps. This is only counted
on the DRC pointed sector. The units of the count are dB/8.
............................................................................................................................................................................................................................................................

dB/8.
Formula
---------------------------------------------------------------------------------
Count Definitions
link outer loop set point used for frames in which the data rate is 19.2 kbps. This is only
counted on the DRC pointed sector. The units of the count are dB/8.
Formula
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula
---------------------------------------------------------------------------------
Count Definitions
Formula
---------------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
REV_OUTER_LOOP_PC_TOTAL_OUTPUT_1536BPS = Total count for the reverselink
outer loop set point used for frames in which the data rate is 153.6 kbps. This is only
This metric gives the average reverse link power control setpoint per frame for
thosepackets containing 128 bits. The peg counts are defined on a per sector-carrier basis.
Formula
---------------------------------------------------------------------------
Count Definitions
point used for 128 bit frames. This is only counted on the DRC pointed sector. The units of
the count are dB/8.
REV_PACKETS_128_TOTAL_COUNT = The actual number of physical layer packets of
Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
the count are dB/8.
Formula
---------------------------------------------------------------------------
Count Definitions
the count are dB/8.
Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
the count are dB/8.
Formula
---------------------------------------------------------------------------
Count Definitions
point used for 1536 bit frames. This is only counted on the DRC pointed sector. The units
of the count are dB/8.
Formula

---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula
---------------------------------------------------------------------------
Count Definitions
Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula
---------------------------------------------------------------------------
Count Definitions
Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
Formula
---------------------------------------------------------------------------
Count Definitions
Formula
---------------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
set point used for 12288 bit frames. This is only counted on the DRC pointed sector. The
units of the count are dB/8.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Capacity Management Metrics

............................................................................................................................................................................................................................................................

1xEV-DO.
divided again.
Formula
DO Traffic channel usage (erlangs) =
--------------------------------------------------
360
............................................................................................................................................................................................................................................................
Count Definitions
counter every 10 seconds by an amount equal to the number of active connections
(including soft and softer handoff links) present at the time on the given sector. Essentially
it is a single snapshot within the 10 sec period. Since, there are 360 such intervals in an
hour, it is divided by 360 to provide DO Traffic channel usage in a given hour.

Formula
Count Definitions
pointed active users for the sector-carrier. The unit of measure is average value multiplied
by 100.
............................................................................................................................................................................................................................................................
The system measures and sums the total number of DRC pointed active users for the
sector-carrier at the end of each 10-second interval. If there is no DRC pointed sector for a
given connection at the time of pegging, then the last known DRC pointed sector shall be
used. At the end of the SM collection period, the system divides the value by the number
of 10 second periods in the collection interval to get the average and the value is rounded
up to the next hundredth. The system then reports the measurement as (average * 100).
This count shall be pegged only on a carrier equipped with an SBEVM for both Rev A and
Rel 0 traffic.

This metric represents the average number of BE users contending for slot usage. It is
calculated from the average number of active users with BE data to send that are eligible to
be selected by the scheduler and the number of busy slots when BE users are present.
The peg counts are defined on a per sector-carrier basis. This metric is new and effective in
R30.
Formula
DO Average Number of Contending Users - BE =
EVM_AVG_ELIG_USER_BE / 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_SLOTS_BE_USER_PRESENT / 2,160,000
Count Definitions
EVM_AVG_ELIG_USER_BE = This count records the average number of active users
per slot that are eligible to be selected by the scheduler for the sector/carrier.
For each slot, modem/DSP increments the counter by the number of BE flows which have
data waiting to be scheduled and it shall not include the BE flows that are already in the
This count must be divided by 10^6 to obtain the average number of scheduler eligible
users per slot.
EVM_TOTAL_BUSY_SLOTS_BE_USER_PRESENT = This count shall measure the
total number of busy slots on the forward link when BE (Best Effort) users are present for
the sector-carrier.
is used for transmitting BE user data or if there is BE user waiting in the queue.
............................................................................................................................................................................................................................................................

This metric represents the average number of EF flows contending for slot usage. It is
calculated from the average number of active EF flows that are eligible to be selected by
the scheduler and the number of busy slots when EF flows are present.
R30.
Formula
DO Average Number of Contending Flows - EF =
EVM_AVG_ELIG_FLOW_EF / 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_SLOTS_EF_USER_PRESENT / 2,160,000
Count Definitions
EVM_AVG_ELIG_FLOW_EF = This count measures the average number of active EF
(Expedited Forwarding) flows that are eligible to be selected by the scheduler for the
sector-carrier.

This metric represents the average number of users contending for slot usage, regardless of
the type of data being sent. It is calculated from the average number of active users that are
eligible to be selected by the scheduler and the number of busy slots.
R30.
Formula
DO Average Number of Contending Users =
EVM_AVG_ELIG_USER_ALL/ 10 ^6
------------------------------------------------------------------------------------------------------------
EVM_TOTAL_BUSY_PCNT_SLOTS / 10 ^8
Count Definitions
EVM_AVG_ELIG_USER_ALL = This count measures the average number of active
users that are eligible to be selected by the scheduler for the sector-carrier regardless of the
traffic type.
............................................................................................................................................................................................................................................................
For each slot, modem/DSP increments the count by the number of users who have data
waiting to be scheduled and it shall not include the users that are already in the process of
transmission and without data waiting. If a user has multiple flows, e.g. BE and EF in the
backlog, the count shall be incremented only by 1. At the end of SM collection interval,
the system shall calculate the average value by using the summation of all such users
divided by the total number of slots.
legs where the user has EF data waiting, regardless of the state of this user's BE data. If the
erasure-mapped user only has BE data waiting, this count shall be pegged against last
known DRC pointed sector. This count is reported as average * 10^6.

connections.
metric, DO Soft/Softer Handoff Overhead - Measured at TP should now be used. The new
metric is valid for both EVM and SBEVM and is expected to be more accurate since the
counts are all measured at the TP.
Formula
-----------------------------------------------------------------------
............................................................................................................................................................................................................................................................
Count Definitions
counter every 10 seconds by an amount equal to the number of active connections
(including soft and softer handoff links) present at the time on the given sector. Essentially
it is a single snapshot within the 10 sec period.
Since, there are 360 such intervals in an hour, it is divided by 360 to provide DO Traffic
channel usage in a given hour.
pointed active users for the sector-carrier. The unit of measure is average value multiplied
by 100.
The system measures and sums the total number of DRC pointed active users for the
sector-carrier at the end of each 10-second interval. If there is no DRC pointed sector for a
given connection at the time of pegging, then the last known DRC pointed sector shall be
used. At the end of the SM collection period, the system divides the value by the number
of 10 second periods in the collection interval to get the average and the value is rounded
up to the next hundredth. The system then reports the measurement as (average * 100).
This count shall be pegged only on a carrier equipped with an SBEVM for both Rev A and
Rel 0 traffic.
1x EV-DO Soft/Softer Handoff Overhead (Measured at TP)

DRC pointed links on it, as measured at the TP. For example, a ratio of 2.5 indicates that
for every user that this sector-carrier is serving on the forward link, it has 1.5 other users
who are pointing their DRCs to some other sector-carriers.
The peg counts are defined on a sector-carrier basis and measured at the TP. This metric is
new and effective in R30 and is applicable to all connections, both Rel 0 and Rev A for
any type of EVM. This metric replaces the previous metric which is obsolete as of R30.
Formula
DO Soft/Softer Handoff Overhead - Measured at TP =
TOT_ACTIVE_CONN_PER_SECTOR_TP
------------------------------------------------------------------------------------------------------------
TOT_DRC_POINTED_ACTIVE_CONN_PER_SECTOR_TP
............................................................................................................................................................................................................................................................
Count Definitions
TOT_ACTIVE_CONN_PER_SECTOR_TP = This count measures the total number of
active connections for a sector-carrier that the sector is in the active set for the connection.
against all the legs in the active set and at the end of SM collection interval the
accumulated value for the total active connections shall be reported.
TOT_DRC_POINTED_ACTIVE_CONN_PER_SECTOR_TP = This count measures the
total number of active connections for a sector-carrier that the sector is the DRC-Pointed
sector for the connection. Every 10 seconds, RNC/TP shall increment the count by one for
each active connection against the DRC-pointed sector and at the end of SM collection
interval the accumulated value for the total DRC-Pointed active connections shall be
reported.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Quality of Service (QoS) Metrics
Quality of Service (QoS) Metrics

............................................................................................................................................................................................................................................................
thereby providing a value equal to the

beginning in R28.
Formula
ROR_ACCEPTED
-------------------------------------X100
ROR_RECEIVED
Count Definitions
RoR is accepted only when all of the reservations included in the request can be
successfully admitted using the admission evaluation algorithms defined in call processing
(i.e., when sufficient resources are available to support all of the reservations.)
............................................................................................................................................................................................................................................................

............................................................................................................................................................................................................................................................
Formula
RESV_ADMITTED_FL_CS
------------------------------------------------------------------------ X 100
RESV_REQ_FL_CS
Count Definitions
Conversational Speech is included in a ReservationOnRequest that has been accepted.

Formula
----------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CS
Count Definitions
when a FL reservation of Conversational Speech is terminated because number of packets
dropped by the scheduler has exceeded the threshold set in translations.
............................................................................................................................................................................................................................................................

FL reservation of Conversational Speech is terminated because its counterpart in the RL
has been terminated.
Conversational Speech is terminated when a sector that is not supported by either MLPPP
or ethernet has been added to the active set of the AT.

Formula
RESV_ADMITTED_FL_CV
-----------------------------------------------------X 100
RESV_REQ_FL_CV
Count Definitions
Conversational Video is included in a ReservationOnRequest that has been accepted.

............................................................................................................................................................................................................................................................
Formula
--------------------------------------------------------------------------------- X 100
RESV_ADMITTED_FL_CV
Count Descriptions
when a FL reservation of Conversational Video is terminated because number of packets
dropped by the scheduler has exceeded the threshold set in translations.
FL reservation of Conversational Video is terminated because its counterpart in the RL has
been terminated.
Conversational Video is terminated when a sector that is not supported by either MLPPP

............................................................................................................................................................................................................................................................
Formula
-----------------------------------------------------------X 100
RESV_REQ_FL_CPS
Count Definitions
Conversational PTT Speech is included in a ReservationOnRequest that has been
accepted.
RES_REQ_FL_CPS = This count is incremented when a FL reservation of Conversational
PTT Speech is included in a ReservationOnRequest.

Formula
----------------------------------------------------------------------------------X 100
Count Descriptions
of conversational push-to-talk Speech is terminated due to backhaul overload.
when a FL reservation of Conversational PTT Speech is terminated because number of
packets dropped by the scheduler has exceeded the threshold set in translations.
............................................................................................................................................................................................................................................................

FL reservation of Conversational PTT Speech is terminated becauseits counterpart in the
RL has been terminated.
Conversational PTT Speech is terminated when a sector that is not supported by either
MLPPP or ethernet has been added to the active set of the AT.

Formula
--------------------------------------------------------------------------------------------- X 100
RESV_ADMITTED_RL_CS
Count Descriptions
............................................................................................................................................................................................................................................................

RL reservation of Conversational Speech is terminated due to the termination of it's FL
counterpart.
Conversational Speech is terminated when a sector that is not supported by either MLPPP
Formula
------------------------------------------------------------------------X 100
RESV_ADMITTED_RL_CV
Count Descriptions
RL reservation of Conversational Video is terminated due to the termination of its FL
counterpart.
Conversational Video is terminated when a sector that is not supported by either MLPPP
............................................................................................................................................................................................................................................................


Formula
----------------------------------------------------------------------------------X 100
Count Descriptions
of conversational push-to-talk Speech is terminated due to backhaul overload.
of Conversational push-to-talk Speech is terminated due to reverse link RF overload.
RL reservation of Conversational PTT Speech is terminated due to the termination of it's
FL counterpart.
Conversational PTT Speech is terminated when a sector that is not supported by either
MLPPP or ethernet has been added to the active set of the AT.
1xEV-DO Registration Success Rate

............................................................................................................................................................................................................................................................
Formula
-------------------------------------------------------- X 100
Count Descriptions
A11 Broadcast registration reply message is received at the AP from the Broadcast
Serving Node (BSN) in response to the A11 BC registration request previously sent.
registration request message is sent from the AP to the BSN. This count does not include
the A11 Broadcast registration request retries.
1xEV-DO Broadcast Service Request Success Rate

This metric provides the success rate of the BCMCS service request to the BSN. The peg
counts are defined on a per TP basis. This metric is effective beginning in R29.
Formula
------------------------------------------------------------------- X 100
Count Descriptions
successful A11 Broadcast service response message is received at the AP from the
Broadcast Serving Node (BSN) in response to the A11 BC service request previously sent.
service request message is sent from the AP to the BSN. This count does not include the
A11 Broadcast service request retries.
............................................................................................................................................................................................................................................................
Performance Metrics for Alcatel-Lucent Release 31 Metrics Added due to SM Re-Architecture
Metrics Added due to SM Re-Architecture

............................................................................................................................................................................................................................................................
thereby providing a value equal to the old count. The counts are all measured at the RNC.
1xEV-DO Average Degree Out of Sequence Packets, FL CS

This metric replaces the peg count AVG_DEGREE_OUT_SEQ_FL_CS. The peg counts
are defined on a sector-carrier basis. The metric is new in R31 and is not applicable to
prior releases.
Formula
DO Avg Degree Out of Sequence FL CS =
SUM_DEGREE_OUT_SEQ_FL_CS
---------------------------------------------------
NUM_PKTS_OUT_SEQ_FL_CS
Count Definitions
SUM_DEGREE_OUT_SEQ_FL_CS = The degree of out-of-order for a packet stream is
the delta of sequence numbers between two adjacent packets (in the order of their received
time) that is beyond the expected value. If the packet received later has a smaller number,
subtracting the sequence number of the later packet from the earlier packet results in a
positive delta. Packets received in sequence have negative deltas.
This count is the aggregation of all the positive deltas (as defined above) accumulated
within the collection interval for FL Conversational Speech packets. Divide this count by
the number of out-of-sequence FL CS packets, NUM_PKTS_OUT_SEQ_FL_CS, to get
the average degree of out-of-sequence. Notice that the negative deltas are ignored. If no
positive delta is collected in the collection interval, the packet stream is completely in
order. The count should be pegged as zero.
This count and NUM_PKTS_OUT_SEQ_FL_CS replace
AVG_DEGREE_OUT_SEQ_FL_CS.
............................................................................................................................................................................................................................................................
NUM_PKTS_OUT_SEQ_FL_CS = The degree of out-of-order for a packet stream is the

delta of sequence numbers between two adjacent packets (in the order of their received
This count is the number of FL CS packets that have positive deltas (as defined above)
received at BTS during the collection interval. (i.e., the out-of-sequence packets.) It is
used as the denominator with SUM_DEGREE_OUT_SEQ_FL_CS to get the average
degree of out-of-sequence, and it is used as the numerator with TOTAL_PKTS_FL_CS to
get the percentage of out-ofsequence packets.
This count and SUM_DEGREE_OUT_SEQ_FL_CS replace
1xEV-DO Average Degree Out of Sequence Packets, FL CV

This metric replaces the peg count AVG_DEGREE_OUT_SEQ_FL_CV .
Formula
DO Avg Degree Out of Sequence FL CV =
SUM_DEGREE_OUT_SEQ_FL_CV
---------------------------------------------------
NUM_PKTS_OUT_SEQ_FL_CV
Count Definitions
SUM_DEGREE_OUT_SEQ_FL_CV = The degree of out-of-order for a packet stream is
within the collection interval for FL Conversational Video packets. Divide this count by
the number of out-of-sequence FL CV packets, NUM_PKTS_OUT_SEQ_FL_CV, to get
............................................................................................................................................................................................................................................................
This count and NUM_PKTS_OUT_SEQ_FL_CV replace

AVG_DEGREE_OUT_SEQ_FL_CV.
NUM_PKTS_OUT_SEQ_FL_CV = The degree of out-of-order for a packet stream is the
This count is the number of FL CV packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_FL_CV to get the average
degree of out-of-sequence, and it is used as the numerator with TOTAL_PKTS_FL_CV to
This count and SUM_DEGREE_OUT_SEQ_FL_CV replace
This count and TOTAL_PKTS_FL_CV replace the obsolete count
PCNT_OUT_SEQ_FL_CV.
1xEV-DO Average Degree Out of Sequence Packets, RL CS

This metric replaces the peg count AVG_DEGREE_OUT_SEQ_RL_CS.
Formula
DO Avg Degree Out of Sequence RL CS =
SUM_DEGREE_OUT_SEQ_RL_CS
---------------------------------------------------
NUM_PKTS_OUT_SEQ_RL_CS
Count Definitions
SUM_DEGREE_OUT_SEQ_RL_CS = The degree of out-of-order for a packet stream is
within the collection interval for RL Conversational Speech packets. Divide this count by
the number of out-of-sequence RL CS packets, NUM_PKTS_OUT_SEQ_RL_CS, to get
............................................................................................................................................................................................................................................................
This count and NUM_PKTS_OUT_SEQ_RL_CS replace
AVG_DEGREE_OUT_SEQ_RL_CS.
NUM_PKTS_OUT_SEQ_RL_CS = The degree of out-of-order for a packet stream is the
This count is the number of RL CS packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_RL_CS to get the average
degree of out-of-sequence, and it is used as the numerator with TOTAL_PKTS_RL_CS to
This count and SUM_DEGREE_OUT_SEQ_RL_CS replace
This count and TOTAL_PKTS_RL_CS replace the obsolete count
PCNT_OUT_SEQ_RL_CS.
1xEV-DO Average Degree Out of Sequence Packets, RL CV

This metric replaces the peg count AVG_DEGREE_OUT_SEQ_RL_CV .
Formula
DO Avg Degree Out of Sequence RL CV =
SUM_DEGREE_OUT_SEQ_RL_CV
---------------------------------------------------
NUM_PKTS_OUT_SEQ_RL_CV
Count Definitions
SUM_DEGREE_OUT_SEQ_FL_CV = The degree of out-of-order for a packet stream is
............................................................................................................................................................................................................................................................
within the collection interval for RL Conversational Video packets. Divide this count by
the number of out-of-sequence RL CV packets, NUM_PKTS_OUT_SEQ_RL_CV, to get
This count and NUM_PKTS_OUT_SEQ_RL_CV replace
AVG_DEGREE_OUT_SEQ_RL_CV.
NUM_PKTS_OUT_SEQ_RL_CV = The degree of out-of-order for a packet stream is the
This count is the number of RL CV packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_RL_CV to get the average
degree of out-of-sequence, and it is used as the numerator with TOTAL_PKTS_RL_CV to
This count and SUM_DEGREE_OUT_SEQ_RL_CV replace
This count and TOTAL_PKTS_RL_CV replace the obsolete count
PCNT_OUT_SEQ_RL_CV.
1xEV-DO Percentage of Out of Sequence Packets, FL CS

This metric replaces the peg count PCNT_OUT_SEQ_FL_CS.
Formula
DO Percentage of Out of Sequence Pkts FL CS (%) =
NUM_PKTS_OUT_SEQ_FL_CS
--------------------------------------------------- X100
TOTAL_PKTS_FL_CS
............................................................................................................................................................................................................................................................
Count Definitions
NUM_PKTS_OUT_SEQ_FL_CS = The degree of out-of-order for a packet stream is the

positive delta. Packets received in sequence have negative deltas. This count is the number
of FL CS packets that have positive deltas (as defined above) received at BTS during the
collection
interval. (i.e., the out-of-sequence packets.) It is used as the denominator with
SUM_DEGREE_OUT_SEQ_FL_CS to get the average degree of out-of-sequence, and it
is used as the numerator with TOTAL_PKTS_FL_CS to get the percentage of out-
ofsequence packets.
This count and SUM_DEGREE_OUT_SEQ_FL_CS replace
This count and TOTAL_PKTS_FL_CS replace the obsolete count
PCNT_OUT_SEQ_FL_CS.
TOTAL_PKTS_FL_CS = This count is the number of FL CS packets received at BTS
during the collection interval. It is used as the denominator with
NUM_PKTS_OUT_SEQ_FL_CS to get the percentage of out-of-sequence packets.
1xEV-DO Percentage of Out of Sequence Packets, FL CV

This metric replaces the peg count PCNT_OUT_SEQ_FL_CV.
Formula
DO Percentage of Out of Sequence Pkts FL CV (%) =
NUM_PKTS_OUT_SEQ_FL_CV
--------------------------------------------------- X100
TOTAL_PKTS_FL_CV
............................................................................................................................................................................................................................................................
Count Definitions
NUM_PKTS_OUT_SEQ_FL_CV = The degree of out-of-order for a packet stream is the
This count is the number of FL CV packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_FL_CV to get the average
degree of out-of-sequence, and it is used as the numerator with TOTAL_PKTS_FL_CV to
This count and SUM_DEGREE_OUT_SEQ_FL_CV replace
This count and TOTAL_PKTS_FL_CV replace the obsolete count
PCNT_OUT_SEQ_FL_CV.
TOTAL_PKTS_FL_CV = This count is the number of FL CV packets received at BTS
during the collection interval. It is used as the denominator with
NUM_PKTS_OUT_SEQ_FL_CV to get the percentage of out-of-sequence packets.
This count and NUM_PKTS_OUT_SEQ_FL_CV replace the obsolete count
PCNT_OUT_SEQ_FL_CV.
1xEV-DO Percentage of Out of Sequence Packets, RL CS

This metric replaces the peg count PCNT_OUT_SEQ_RL_CS.
Formula
DO Percentage of Out of Sequence Pkts RL CS (%) =
NUM_PKTS_OUT_SEQ_RL_CS
--------------------------------------------------- X100
ROUTE_PROTCL_PKTS_RL_CS
............................................................................................................................................................................................................................................................
Count Definitions
NUM_PKTS_OUT_SEQ_RL_CS = The degree of out-of-order for a packet stream is the
This count is the number of RL CS packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_RL_CS to get the average
degree of out-of-sequence, and it is used as the numerator with
ROUTE_PROTCL_PKTS_RL_CS to get the percentage of out-ofsequence packets.
This count and SUM_DEGREE_OUT_SEQ_RL_CS replace
This count and ROUTE_PROTCL_PKTS_RL_CS replace the obsolete count
PCNT_OUT_SEQ_RL_CS.
ROUTE_PROTCL_PKTS_RL_CS = This count is incremented for each RP packet
received for Conversational Speech, and is the total of all such CS Rp packets received on
the reverse traffic channels for a sector-carrier.
It is used as the denominator with NUM_PKTS_OUT_SEQ_RL_CS to get the percentage
of out-of-sequence packets.
1xEV-DO Percentage of Out of Sequence Packets, RL CV

This metric replaces the peg count PCNT_OUT_SEQ_RL_CV.
Formula
DO Percentage of Out of Sequence Pkts RL CV (%) =
NUM_PKTS_OUT_SEQ_RL_CV
--------------------------------------------------- X100
ROUTE_PROTCL_PKTS_RL_CV
............................................................................................................................................................................................................................................................
Count Definitions
NUM_PKTS_OUT_SEQ_RL_CV = The degree of out-of-order for a packet stream is the
This count is the number of RL CV packets that have positive deltas (as defined above)
used as the denominator with SUM_DEGREE_OUT_SEQ_RL_CV to get the average
degree of out-of-sequence, and it is used as the numerator with
ROUTE_PROTCL_PKTS_RL_CV to get the percentage of out-ofsequence packets.
This count and SUM_DEGREE_OUT_SEQ_RL_CV replace
This count and ROUTE_PROTCL_PKTS_RL_CV replace the obsolete count
PCNT_OUT_SEQ_RL_CV.
ROUTE_PROTCL_PKTS_RL_CV = This count is incremented for each RP packet
received for Conversational Video, and is the total of all such CV RP packets received on
the reverse traffic channels for a sector-carrier.
It is used as the denominator with NUM_PKTS_OUT_SEQ_RL_CV to get the percentage
of out-of-sequence packets
............................................................................................................................................................................................................................................................
1xEV-DO Performance Metric

............................................................................................................................................................................................................................................................
Overview
The purpose of this section is to describe new and modified Primitive Calculations
(PCALCS) that support 1XEV-DO Performance Metrics in IBM Prospect. for Alcatel-
Lucent R31.
Prospect. This chapter includes
1 previously supported 1xEV-DO performance metrics (see: Modified 1xEV-DO
Performance Metrics for Prospect R31 (p. 22-2))
There are also 15 new PCALCs ( see: New 1xEV-DO Performance Metrics in
Release 31 (p. 22-5))
Prospect R31 also supports earlier RNC releases and the descriptions of existing
releases:
25
26
............................................................................................................................................................................................................................................................
Modified 1xEV-DO Performance Metrics for Prospect R31

............................................................................................................................................................................................................................................................

Valid Releases: For backward compatibility, Prospect will use the following existing
PCALC for RNC R27 - R29
DOp_ReTXRevLnk = 100.0 * MissRLPRqRTC / RLPRXRTC
Notes:
Prospect Name 1xEV-DO Name Prospect Traffic Entity

MissRLPRqRTC MISSING_RLP_REQ_RTC 1xEV_SectorCarrier
The PCALC introduced in Prospect R30 for RNC R30 is replaced with the following
PCALC that is valid for RNC R30 and later.
DOp_ReTXRevLnk = 100.0 * (MissingRLPReqRTC_BE + MissingRLPReqRTC_SMC) /
(RLPRXRTC - RLPRcvdRTC_CPS - RLPRcvdRTC_CS - RLPRcvdRTC_CV)
Notes:
1. Mapping between Prospect names and 1xEV-DO names
............................................................................................................................................................................................................................................................

MissingRLPReqRTC_BE MISSING_RLP_REQ_RTC_ IxEV_SectorCarrier
BE
MissingRLPReqRTC_SMC MISSING_RLP_REQ_RTC_
SMC
RLPRcvdRTC_CPS RLP_RCVD_RTC_CPS
RLPRcvdRTC_CS RLP_RCVD_RTC_CS
RLPRcvdRTC_CV RLP_RCVD_RTC_CV
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Obsolete 1xEV-DO Performance Metrics in
Release 31 Release 31
Obsolete 1xEV-DO Performance Metrics in Release 31

............................................................................................................................................................................................................................................................
No 1xEV-DO metrics become obsolete in Prospect R31.
............................................................................................................................................................................................................................................................
1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent New 1xEV-DO Performance Metrics in Release
Release 31 31
New 1xEV-DO Performance Metrics in Release 31

............................................................................................................................................................................................................................................................
1xEV-DO Percentage of AT-Assisted Interfrequency Handoffs Requesting Sector

DOp_PcntATAssistIFHO_ReqSect = 100.0 * (HardHOAtt -
(HHOFFAttmptANDirectPilotReq + HHOFFAttmptANDirectUpperReq))/HardHOAtt
Notes:

HardHOAtt HHOFF_ATTMPT_REQ IxEV_SectorCarrier
HHOFFAttmptANDirectPilot HHOFF_ATTMPT_AN_DIR
Req ECT_PILOT_REQ
HHOFFAttmptANDirectUpp HHOFF_ATTMPT_AN_DIR
erReq ECT_UPPER_REQ
1xEV-DO Directed IFHO Triggered by Pilot Strength Success Rate-Requesting Sector

DOp_DrIFHOTrgPilStrSucRate_ReqSect = 100.0 * (HHOFFAttmptANDirectPilotReq -
HHOFFNOPANDirectPilotReq - HHOFFFailANDirectPilotReq)/(
HHOFFAttmptANDirectPilotReq HHOFFNOPANDirectPilotReq)
Notes:
Prospect Name 1xEVDO Name Prospect Traffic Entity

HHOFFAttmptANDirectPilot HHOFF_ATTMPT_AN_DIR IxEV_SectorCarrier
Req ECT_PILOT_REQ
HHOFFNOPANDirectPilotR HHOFF_NOP_AN_DIRECT
eq _PILOT_REQ
HHOFFFailANDirectPilotRe HHOFF_FAIL_AN_DIRECT
q _PILOT_REQ
............................................................................................................................................................................................................................................................
Release 31 31
1xEV-DO Directed IFHO Triggered by Upper Distance Threshold Success Rate-Requesting Sector
DOp_DrIFHOTrgUpDstThrshSucRate_ReqSect = 100.0 *
(HHOFFAttmptANDirectUpperReq - HHOFFNOPANDirectUpperReq
HHOFFFailANDirectUpperReq)/( HHOFFAttmptANDirectUpperReq
HHOFFNOPANDirectUpperReq)
Notes:

HHOFFAttmptANDirectUpp HHOFF_ATTMPT_AN_DIR IxEV_SectorCarrier
erReq ECT_UPPER_REQ
HHOFFNOPANDirectUpper HHOFF_NOP_AN_DIRECT
Req _UPPER_REQ
HHOFFFailANDirectUpperR HHOFF_FAIL_AN_DIRECT
eq _UPPER_REQ
1xEV-DO Round Trip Delay Measurement Validity Rate

Prospect Traffic Report Entity: IxEV_Sector
DOp_RTDMeasValidity = 100.0 * HHOFFValidRTD/(HHOFFValidRTD +
HHOFFInvalidRTD)
Notes:
1. Note that this metric is evaluated at the IxEV_Sector level (i.e., the counts are summed over
carriers)

HHOFFValidRTD HHOFF_VALID_RTD IxEV_SectorCarrier
HHOFFInvalidRTD HHOFF_INVALID_RTD
............................................................................................................................................................................................................................................................
Release 31 31
1xEV-DO Average Distance Between AT and BTS for Pilot Strength Triggered Directed IFHO
DO_AvgDstATBTSPilStrTrgDirIFHO = 0.01 * HHOFFDistANDirectPilotReq/
HHOFFAttmptANDirectPilotReq
Notes:

HHOFFDistANDirectPilotRe HHOFF_DIST_AN_DIREC IxEV_SectorCarrier
q T_PILOT_REQ
HHOFFAttmptANDirectPilot HHOFF_ATTMPT_AN_DIR
Req ECT_PILOT_REQ
1xEV-DO Average Ratio of Pilot Strength and Threshold for IFHO

DO_AvgRatioPilStrThrshIFHO = 10.0 * log
((HHOFFPilotDeltaANDirectUpperReq/1000.0)/ HHOFFAttmptANDirectUpperReq)
Notes:

HHOFFPilotDeltaANDirectU HHOFF_PILOT_DELTA_A IxEV_SectorCarrier
pperReq N_DIRECT_UPPER_REQ
HHOFFAttmptANDirectUpp HHOFF_ATTMPT_AN_DIR
erReq ECT_UPPER_REQ
1xEV-DO Average RLP Forward Link User Data Rate BE BTS (kbps)
DO_AvgRLPFLUsrDataRate_BE_BTS = (8.0 * RLPTxedFTC_BE/1000.0)/(0.001667 *
ActiveUsage_BE)
............................................................................................................................................................................................................................................................
Release 31 31
Notes:

RLPTxedFTC_BE EVM_RLP_TXED_FTC_BE IxEV_SectorCarrier
ActiveUsage_BE EVM_ACTIVE_USAGE_BE
1xEV-DO Average Degree Out of Sequence Packets, FL CS

AvgDegreeOutSeqFL_CS = SumDegreeOutSeqFL_CS / NumPktsOutSeqFL_CS
Notes:
1. The PCALC AvgDegreeOutSeqFL_CS will replace the peg count AvgDegreeOutSeqFL_CS, which is
obsolete in R31 and later. For backward

SumDegreeOutSeqFL_CS SUM_DEGREE_OUT_SEQ IxEV_SectorCarrier
_FL_CS
NumPktsOutSeqFL_CS NUM_PKTS_OUT_SEQ_FL
_CS
1xEV-DO Average Degree Out of Sequence Packets, FL CV

AvgDegreeOutSeqFL_CV = SumDegreeOutSeqFL_CV / NumPktsOutSeqFL_CV
Notes:
1. The PCALC AvgDegreeOutSeqFL_CV will replace the peg count AvgDegreeOutSeqFL_CV, which is
obsolete in R31 and later. For backward compatibility, the PCALC will transparently replace the peg
count in PCALCs, UDCs, templates, etc, beginning with R31
............................................................................................................................................................................................................................................................
Release 31 31

SumDegreeOutSeqFL_CV SUM_DEGREE_OUT_SEQ IxEV_SectorCarrier
_FL_CV
NumPktsOutSeqFL_CV NUM_PKTS_OUT_SEQ_FL
_CV
1xEV-DO Average Degree Out of Sequence Packets, RL CS

AvgDegreeOutSeqRL_CS = SumDegreeOutSeqRL_CS / NumPktsOutSeqRL_CS
Notes:
1. The PCALC AvgDegreeOutSeqRL_CS will replace the peg count AvgDegreeOutSeqRL_CS,
which is obsolete in R31 and later. For backward compatibility, the PCALC will transparently
replace the peg count in PCALCs, UDCs, templates, etc, beginning with R31.

SumDegreeOutSeqRL_CS SUM_DEGREE_OUT_SEQ IxEV_SectorCarrier
_RL_CS
NumPktsOutSeqRL_CS NUM_PKTS_OUT_SEQ_RL
_CS
1xEV-DO Average Degree Out of Sequence Packets, RL CV

AvgDegreeOutSeqRL_CV = SumDegreeOutSeqRL_CV / NumPktsOutSeqRL_CV
Notes:
1. The PCALC AvgDegreeOutSeqRL_CV will replace the peg count
AvgDegreeOutSeqRL_CV, which is obsolete in R31 and later. For backward compatibility,
the PCALC will transparently replace the peg count in PCALCs, UDCs, templates, etc,
beginning with R31
............................................................................................................................................................................................................................................................
Release 31 31

SumDegreeOutSeqRL_CV SUM_DEGREE_OUT_SEQ IxEV_SectorCarrier
_RL_CV
NumPktsOutSeqRL_CV NUM_PKTS_OUT_SEQ_RL
_CV
1xEV-DO Percentage of Out of Sequence Packets, FL CS

PcntOutSeqFL_CS = 100.0 * NumPktsOutSeqFL_CS / TotalPktsFL_CS
Notes:
1. The PCALC PcntOutSeqFL_CS will replace the peg count PcntOutSeqFL_CS, which is
obsolete in R31 and later. For backward compatibility, the PCALC will transparently replace
the peg count in PCALCs, UDCs, templates, etc, beginning with R31.

TotalPktsFL_CS TOTAL_PKTS_FL_CS NUM_PKTS_OUT_SEQ_FL
_CS
NumPktsOutSeqFL_CS NUM_PKTS_OUT_SEQ_FL
_CS
1xEV-DO Percentage of Out of Sequence Packets, FL CV

PcntOutSeqFL_CV = 100.0 * NumPktsOutSeqFL_CV / TotalPktsFL_CV
Notes:
1. The PCALC PcntOutSeqFL_CV will replace the peg count PcntOutSeqFL_CV, which is
............................................................................................................................................................................................................................................................
Release 31 31

TotalPktsFL_CS TOTAL_PKTS_FL_CV IxEV_SectorCarrier
NumPktsOutSeqFL_CV NUM_PKTS_OUT_SEQ_FL
_CV
1xEV-DO Percentage of Out of Sequence Packets, RL CS

PcntOutSeqRL_CS = 100.0 * NumPktsOutSeqRL_CS / RouteProtclPktsRL_CS
Notes:
1. The PCALC PcntOutSeqRL_CS will replace the peg count PcntOutSeqRL_CS, which is
Prospect Name 1xEV-DO Prospect Name Prospect Traffic Entity

RouteProtclPktsRL_CS RouteProtclPktsRL_CS IxEV_SectorCarrier
NumPktsOutSeqRL_CS NUM_PKTS_OUT_SEQ_RL
_CS
1xEV-DO Percentage of Out of Sequence Packets, RL CV

PcntOutSeqRL_CV = 100.0 * NumPktsOutSeqRL_CV / RouteProtclPktsRL_CV
Notes:
1. The PCALC PcntOutSeqRL_CV will replace the peg count PcntOutSeqRL_CV, which is obsolete in
R31 and later. For backward compatibility, the PCALC will transparently replace the peg count in
PCALCs, UDCs, templates, etc, beginning with R31.
............................................................................................................................................................................................................................................................
Release 31 31

RouteProtclPktsRL_CV RouteProtclPktsRL_CV IxEV_SectorCarrier
NumPktsOutSeqRL_CV NUM_PKTS_OUT_SEQ_RL
_CV
............................................................................................................................................................................................................................................................

HSD Formulas Details

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HSD Formulas Details

Uploaded by

Copyright:

Available Formats

CDMA 1xEV-DO

1xEV-DO Radio Access System

Copyright 2008 Alcatel-Lucent.

Copyright 2008 Alcatel-Lucent. All rights reserved.

Mandatory customer information

Interference information: Part 15 of FCC rules

About this information product

3 Performance Metrics for Release 22

4 1xEV-DO Metrics in Watchmark Prospect for Release 22

5 Performance Metrics for Release 23

7 Performance Metrics for Release 24

8 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 24

9 Performance Metrics for Release 25

10 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 25

11 Performance Metrics for Release 26

12 1xEV-DO Metrics in Watchmark Prospect for Alcatel-Lucent Release 26

13 Performance Metrics for Release 27

15 Performance Metrics for Release 28

16 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 28

17 Performance Metrics for Release 29

18 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 29

19 Performance Metrics for Release 30

20 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 30

21 Performance Metrics for Alcatel-Lucent Release 31

22 1xEV-DO Metrics in IBM Prospect for Alcatel-Lucent Release 31

1-1 RLP and MAC protocol layers ................................................................................................... 1-11

Reason for reissue

Information product support

for R22 through R24:

for R25 through R28:

for R28 through R30

Session Management Metrics

Packet Data Reactivation Metrics

Call Setup/Connection Setup Metrics

For classification based on the purpose of the connection - primarily 3 connection

For classification based on which end initiates it - three types:

Call Drop/Connection Drop Metrics

Data Throughput Metrics/Data Transmission Metrics

Figure 1-1 RLP and MAC protocol layers

Capacity Management Metrics

Metrics Added Due to SM Re-Architecture

Watchmark/IBM Prospect for Alcatel-Lucent

1xEV-DO 1X Evolution Data Optimized

A11-PCF PCF to PDSN Signaling Interface

BCMCS Broadcast/Multicast Service

BSC Base Station Controller

BSN Broadcast Serving Node

BTS Base Transceiver Station

CDMA Code Division Multiple Access

CPS Conversational Push-to-Talk Speech

DRC Data Rate Control

ECPC Executive Cellular Processor Complex

ESN Equipment Serial Number

EVM 1xEV-DO Modem

FRPH Frame Relay Protocol Handler

FTC Forward Traffic Channel

HSPD High Speed Packet Data

IUP Inter-User Priority

IWF Inter Working Function

FRBC Frame Relay Bearer Channel

L2TP Layer 2 Tunneling Protocol

LLC Link layer Connection

OHM Overhead Manager

PAF Physical Antenna Face