GSM Stats Application

GSM Statistics Application
Maintenance Information
68P02901W56-T
© 2003 - 2009 Motorola, Inc. All Rights Reserved.

Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Jan 2010
Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Maintenance information: GSM Statistics Application

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 1: Introduction to statistics

Introduction to GSM Statistics Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Types of raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Statistic usages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Statistics history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Chapter 2: Statistical operations

Enabling/disabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Displaying statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Setting the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Displaying the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Displaying the statistic interval start times . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Setting statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Displaying statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Chapter 3: BSS statistics

BSS statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
BSS_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
BSS_OVLD_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
HO_REQ_MSC_PROTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
INTRA_BSS_HO_CAUSE_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
MA_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
MSC_OVLD_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
NUM_SUSP_RESU_RCVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
PAGE_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
ROUTING_SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
ROUTING_UNKNOWN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
SCCP_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
SIF_SIO_TX_DPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
68P02901W56-T i
Jan 2010
Contents
Chapter 4: Cell statistics

Cell statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
ACCESS_PER_PCH_CS_PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
ACCESS_PER_PCH_CS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
ACCESS_PER_PCH_ PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
ACCESS_PER_PPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
ALLOC_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
ALLOC_SDCCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
ALLOC_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
ALLOC_TCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
ALLOC_TCH_FAIL_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
ALLOC_TCH_FAIL_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
ALLOC_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
ALLOC_TCH_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
ALLOC_TCH_SIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
AMR_DECREASE_THRESH_ADJUST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
AMR_FR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
AMR_FR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
AMR_FR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
AMR_FR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
AMR_HR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
AMR_HR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
AMR_HR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
AMR_HR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
AMR_INCREASE_THRESH_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
ASSIGNMENT_REDIRECTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
AVAILABLE_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
AVAILABLE_TCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
AVAILABLE_TCH_DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
AVAILABLE_TCH_EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
AVAILABLE_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
AVAILABLE_TCH_PGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
BAD_HO_REFNUM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
BUSY_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60
BUSY_TCH_DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
BUSY_TCH_EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62
BUSY_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
BUSY_TCH_PGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
CALL_SP_VERS_DOWNGRADE_MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
CALLS_QUEUED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
CHAN_REQ_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
CHAN_REQ_MS_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
CIPHER_MODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
CLASSMK_UPDATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
CLR_CMD_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
CLR_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73
CLR_REQ_CALL_SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
CONGEST_EXIST_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
CONGEST_STAND_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
CONN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
CONN_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
CS_PAGING_MSGS_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
DL_LLC_DATA_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
ii 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Contents
DL_LLC_TRANS_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
ER_INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
ER_INTRA_CELL_HO_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
FLOW_CONTROL_BARRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
HO_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
HO_REQ_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
HO_REQ_ACK_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
IA_IAR_MSGS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
IDLE_TCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
IN_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
IN_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113
MA_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
MS_ACCESS_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
MS_TCH_USAGE_BY_TYPE_PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120
MT_LCS_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122
MT_SUPP_ON_SIGNALLING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
NUM_CELL_RESEL_CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124
NUM_CELL_RESEL_CELL_PCCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-125
NUM_CELL_RESEL_CELL_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-126
NUM_EMERG_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-127
NUM_EMERG_REJECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-128
NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-129
NUM_EMERG_TERM_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-130
NUM_HO_3G_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-131
NUM_HO_FROM_3G_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
NUM_HO_FROM_3G_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-133
NUM_HO_TO_3G_RES_ALLOC_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
NUM_HO_TO_3G_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-135
NUM_MULTIRAT_MS_ORIG_CALL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-136
NUM_OF_SMS_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
OK_ACC_PROC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141
OUT_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
OUT_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
PACKET_SYSINFO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
PACKET_SYSINFO_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147
PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-148
PAGING_REQUESTS_CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149
PAGING_REQUESTS_PS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-150
PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-151
PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
PFC_ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-153
PFC_ADMISSION_TRAFFIC_CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-155
PFC_DOWNGRADE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157
PFC_DOWNGRADE_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159
68P02901W56-T iii
Jan 2010
Contents
PFC_GBR_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-161
PFC_GBR_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-163
PFC_PREEMPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-165
PFC_PREEMPTIONS_TRAFFIC_CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167
PFC_REJ_DGRD_PRMPT_CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-168
PFC_REJECT_CAUSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
PFC_REJECTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-173
PFC_REJECTION_TRAFFIC_CLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-175
PFC_TRANSFER_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-176
PFC_UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-178
PPCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
PREEMPT_CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181
QUEUE_PREEMPT_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-182
RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185
RF_LOSSES_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187
RF_LOSSES_TCH_SIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-189
RSS_ALLOC_RESERVE_BLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-190
SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-191
SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
SDCCH_HANDOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-193
SECOND_ASSIGN_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194
SMS_INIT_ON_SDCCH_HO_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-195
SIGNALLING_HANDOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-196
SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-198
SMS_NO_BCAST_MSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-199
T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-200
TCH_CONG_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-202
TCH_CONG_INNER_ZONE_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-203
TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204
TCH_CONGESTION_EN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-205
TCH_CONGESTION_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-206
TCH_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-207
TCH_PREEMPT_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-208
TCH_PREEMPT_FAIL_NO_CAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-209
TCH_PREEMPT_FAIL_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-210
TCH_PREEMPT_RQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-211
TCH_PREEMPT_NO_Q_ALLOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-212
TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-213
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214
TCH_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-215
TCH_USAGE_EXT_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-217
TCH_USAGE_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-218
TIMER_EXP_PAP_CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-219
TOTAL_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-220
UL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-221
UL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-223
UL_LLC_DATA_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-225
UL_LLC_TRANS_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-227
ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-229
ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-230
Chapter 5: Neighbor statistics

Introduction to neighbor statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
IN_INTRA_BSS_NC_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
IN_INTRA_BSS_NC_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
NUM_CELL_RESEL_NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
iv 68P02901W56-T
Jan 2010
NUM_CELL_RESEL_NEI_PCCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
NUM_CELL_RESEL_NEI_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
OUT_HO_NC_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
OUT_HO_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Chapter 6: Carrier and timeslot statistics

Carrier and timeslot statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
ALLOC_SDCCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
ALLOC_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
BUSY_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
BUSY_TCH_CARR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
CHAN_DL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
CHAN_UL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
DL_EGPRS_BACKHAUL_DEMAND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
DL_EGPRS_BACKHAUL_USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
EGPRS_64K_CHANNEL_WIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
FER_AMR_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
FER_AMR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
FER_GSM_FR_EFR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
FER_GSM_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
RBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
U_BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
UL_EGPRS_BACKHAUL_DEMAND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
UL_EGPRS_BACKHAUL_USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37
UPLINK_PATH_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38
Chapter 7: GPROC and DPROC statistics

CPU_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
DSP_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
GCI_FOR_16KPD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
MSGS_DISCARD_ON_GPROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
PFC_REJ_DGRD_PRMPT_PRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
PROCESSOR_CRITICAL_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
PROCESSOR_SAFE_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
PRP_PD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
RSL_LCF_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
TOTAL_GCI_FOR_PD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Chapter 8: Ethernet statistics

ETH_RX_BYTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
ETH_RX_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
ETH_RX_PKT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
ETH_TX_BYTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
ETH_TX_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
ETH_TX_PKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
PSI_TRAU_FILL_FRAME_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
68P02901W56-T v
Jan 2010
Contents
Chapter 9: LMTL statistics

LMTL statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
LMTP_CONGESTION_LOST_MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
LMTP_MSU_DISCARDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
LMTP_CHANGEBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
LMTP_CHANGEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
LMTP_LOCAL_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
LMTP_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
LMTP_LINKFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
LMTP_LOCAL_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
LMTP_LOCAL_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
LMTP_MGT_INHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
LMTP_MGT_UNINHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
LMTP_MSU_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
LMTP_MSU_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
LMTP_NEG_ACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
LMTP_RE_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
LMTP_REMOTE_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
LMTP_REMOTE_PROC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
LMTP_RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
LMTP_SIF_SIO_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
LMTP_SIF_SIO_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
LMTP_SL_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
LMTP_SL_ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
LMTP_REMOTE_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
LMTP_SL_ERROR_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
LMTP_SL_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
LMTP_SL_FIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
LMTP_START_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30
LMTP_STOP_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31
LMTP_SU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
LMTP_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
LMTP_SIB_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
LMTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
LMTP_SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Chapter 10: BSS statistics for Location Services support

BSS statistics for Location Services support subgroups . . . . . . . . . . . . . . . . . . . . . 10-2
BSSLAP_ABORT_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
BSSLAP_ABORT_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
BSSLAP_MS_POS_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
BSSLAP_MS_POS_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
BSSLAP_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
BSSLAP_RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
BSSLAP_TA_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
BSSLAP_TA_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
BSSLAP_TOA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12
BSSMAP_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
BSSMAP_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
BSSMAP_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
BSSMAP_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
BSSMAP_PERF_LOC_RESP_MSGS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
BSSMAPLE_CONLESS_INFO_RCV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
BSSMAPLE_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
BSSMAPLE_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
BSSMAPLE_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
vi 68P02901W56-T
Jan 2010
BSSMAPLE_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Chapter 11: MTL statistics

MTL statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
BUSY_CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
CONGESTION_LOST_MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
MSU_DISCARDED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
MTP_CHANGEBACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
MTP_CHANGEOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
MTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
MTP_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
MTP_LINKFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
MTP_LOCAL_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
MTP_LOCAL_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
MTP_MGT_INHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
MTP_MGT_UNINHIBIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
MTP_MSU_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
MTP_MSU_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
MTP_NEG_ACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19
MTP_RE_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
MTP_REMOTE_MGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
MTP_REMOTE_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
MTP_RESTORATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23
MTP_SIF_SIO_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24
MTP_SIF_SIO_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
MTP_SL_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26
MTP_SL_ALIGNMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
MTP_SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
MTP_SL_ERROR_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-29
MTP_SL_ERROR_RATE_HSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
MTP_SL_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-31
MTP_SL_FIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
MTP_START_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-33
MTP_STOP_RPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
MTP_SU_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
MTP_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
SIB_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-37
SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-38
SL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-39
SL_STOP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-40
Chapter 12: CBL, GSL, OML, RSL, and XBL statistics

X.25/LAP-D Level: X.25 and LAP-D statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
ATER_CHANNEL_REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
ATER_CHANNEL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
ATER_PREEMPT_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
ATER_PREEMPT_ATMPT_SWOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
ATER_PREEMPT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
ATER_PREEMPT_FAIL_SWOVER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
ATER_PREEMPT_RQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
EXT_UL_EXITS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
EXT_UL_USF_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
FRMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
I_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-14
I_FRAMES_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
INVALID_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
68P02901W56-T vii
Jan 2010
Contents
LAP-D_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
MSGS_DISCARD_ON_RSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
N2_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19
RSL_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
RSL_RX_OCTETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
RSL_TX_OCTETS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
SABM_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23
Chapter 13: PCU statistics

PCU statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
AIR_DL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
AIR_DL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
AIR_UL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
AIR_UL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
AVG_SIMUL_DL_TBFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13
AVG_SIMUL_UL_TBFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
BLOCKED_DL_TBFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
CH_REQ_UNSVCD_PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
CHANNEL_REQS_REC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
CHANNEL_REQS_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
CODING_SCHEME_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
CONG_REL_DL_SCTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27
CS_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29
CS12_ON_32K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30
CS1234_ON_64K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
CS1_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
CS2_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
CS3_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34
CS4_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
DL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
DL_BLER_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
DL_BLER_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
DL_BLER_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42
DL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
DL_BLER_MCS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-46
DL_BLER_MCS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
DL_BLER_MCS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50
DL_BLER_MCS5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-52
DL_BLER_MCS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-54
DL_BLER_MCS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-56
DL_BLER_MCS8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58
DL_BLER_MCS9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
DL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62
DL_LLC_FRAMES_GB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-64
DL_LLC_FRAMES_PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-65
DL_MEAN_TBF_DURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-66
DL_MEAN_USER_TRAFFIC_PER_TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-67
DL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-69
DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-70
DL_RADIO_BLKS_1_TS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-71
DL_RADIO_BLKS_2_TS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-73
DL_RADIO_BLKS_3_TS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-76
DL_RADIO_BLKS_4_TS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-79
DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-82
DL_RLC_DDTR_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-84
viii 68P02901W56-T
Jan 2010
DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-85
DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-87
DL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-89
DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-91
DL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-93
DL_TBF_INTERLEAVING_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-94
DL_TBF_TIME_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-95
DL_TBF_TIME_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-96
DL_TBF_TIME_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-97
DL_TBF_TIME_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-98
DL_THROUGHPUT_TERMINAL_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-99
EGPRS_64K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-103
EGPRS_64K_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-104
EGPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-105
EGPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-106
G_RACH_UNSVCD_BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-107
GBL_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-108
GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-109
GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-110
GBL_DL_PKT_COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-112
GBL_DL_PKT_INV_NSVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-113
GBL_FLOW_CTRL_SENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-114
GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-115
GBL_RESOUR_DIST_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-116
GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-117
GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-118
GBL_UL_PKT_COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-120
GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-121
GPRS_32K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-122
GPRS_32K_DL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-123
GPRS_32K_UL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-124
GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-125
GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-126
GPRS_AVAIL_PDTCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-127
GPRS_CELL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-129
GPRS_CELL_RESELECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-131
GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-132
GPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-133
GPRS_PAGING_OVERFLOW_RATE_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-134
GPRS_PAGING_OVERFLOW_RATE_PPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-135
GPRS_PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-136
GPRS_PPCH_PAGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-137
GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-138
GPRS_RACH_ARRIVAL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-140
IDLE_PDTCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-142
IMM_ASSGN_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-147
MCS1_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-149
MCS2_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-150
MCS3_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-151
MCS4_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-152
MCS5_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-153
68P02901W56-T ix
Jan 2010
Contents
MCS6_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-154
MCS7_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-155
MCS8_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-156
MCS9_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-157
NO_PDTCH_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-158
NO_PDTCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-159
PACCH_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-160
PDU_DISCARD_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-161
PDU_DISCARD_LLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-162
PRP_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-164
PS_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-166
TBF_DL_ASGN_PACCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-167
TBF_REL_PACCH_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-168
TBF_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-169
UL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-170
UL_BLER_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-172
UL_BLER_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-174
UL_BLER_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-175
UL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-177
UL_BLER_MCS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-179
UL_BLER_MCS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-181
UL_BLER_MCS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-183
UL_BLER_MCS5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-185
UL_BLER_MCS6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-187
UL_BLER_MCS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-189
UL_BLER_MCS8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-191
UL_BLER_MCS9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-193
UL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-195
UL_CHANNEL_REQUESTS_REJECTION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 13-197
UL_CHANNEL_REQUESTS_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 13-198
UL_LLC_FRAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-200
UL_MEAN_TBF_DURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-201
UL_MEAN_USER_TRAFFIC_PER_TBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-203
UL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-205
UL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-206
UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-207
UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-215
UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-223
UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-225
UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-227
UL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-229
UL_TBF_TIME_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-230
UL_TBF_TIME_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-231
UL_TBF_TIME_8PSK_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-232
UL_TBF_TIME_8PSK_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-233
UL_TBF_TIME_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-234
UL_THROUGHPUT_TERMINAL_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-238
x 68P02901W56-T
Jan 2010
Chapter 14: BSS-SMLC statistics

BSS-based SMLC statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
L_ROUTING_SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
L_ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
L_SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
L_SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
L_SCCP_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
L_SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
L_SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
L_SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
PAGE_REQ_FROM_SMLC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
Chapter 15: Web MMI statistics

MMI statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Chapter 16: Call model statistics

CALL_DURATION (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
CALL_SETUP_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
HANDOVERS_PER_CALL (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
IMSI_DETACHES_TO_CALLS (Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
INTRA_BSS_HO_TO_ALL_HO (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
LOCATION_UPDATE_FACTOR (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
LOCATION_UPDATES_TO_CALLS (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
PAGES_PER_CALL (PPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
PAGES_PER_SECOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
PAGING_RATE (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
SMS_TO_CALL_RATIO (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
Chapter 17: Key statistics

Key statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
ATTEMPT_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
CELL_TCH_ALLOCATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
CELL_TCH_ASSIGNMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
CS1_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
CS2_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
CS3_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
CS4_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
CS1_USE_UL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
CS2_USE_UL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
CS3_USE_UL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
CS4_USE_UL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
DL_BIAS_EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
DL_BIAS_GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
DL_LLC_TRAFFIC_VOLUME_INDICATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
DL_PDTCH_UTILISATION_BY_ALLOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
DL_PDTCH_UTILISATION_BY_TRAFFIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
DL_PDTCH_UTILISATION_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30
68P02901W56-T xi
Jan 2010
Contents
DLDC_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38
DL_RLC_MAC_OVERHEAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39
DL_RLC_MAC_WINDOW_STALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-40
DL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-42
DL_TBF_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-43
DL_TERMINAL_TYPE_ACTIVITY_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-44
DL_USER_TRAFFIC_EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-48
DL_USER_TRAFFIC_GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-50
GPRS_PAGING_OVERFLOW_RATE_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-51
GPRS_PAGING_OVERFLOW_RATE_PPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-52
HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
HANDOVER_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
HSP_MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
HSP_MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-58
IN_3G_HO_FAIL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-59
IN_3G_HO_SUCC_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-60
LLC_ABNORMAL_TBF_RELEASES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
LLC_BUFFER_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-62
MCS1_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63
MCS2_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-64
MCS3_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65
MCS4_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-66
MCS5_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-67
MCS6_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
MCS7_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-69
MCS8_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
MCS9_USE_DL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
MCS1_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-72
MCS2_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
MCS3_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-76
MCS4_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-78
MCS5_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80
MCS6_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-81
MCS7_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-82
MCS8_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-83
MCS9_USE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-84
LLC_DISCARDS_ON_CELL_RESELECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-85
MEAN_ARRIVAL_TIME_BETWEEN_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-86
MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-87
MEAN_TBF_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-88
MEAN_TCH_BUSY_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-89
MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-90
MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-91
NC2_CELL_RESELECTION_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 17-92
OUT_3G_HO_FAIL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-93
OUT_3G_HO_REQ_SUCC_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-94
OUT_3G_HO_SUCC_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-95
RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-96
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-98
SDCCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-99
SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-100
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-101
xii 68P02901W56-T
Jan 2010
SUCCESS_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-103
SUCCESS_INTERNAL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-104
TBF_DROP_RATE_ON_PACCH_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-105
TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-106
TCH_BLOCKING_RATE_INNER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-107
TCH_BLOCKING_RATE_OUT_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-108
TCH_CARRIER_MEAN_HOLDING_TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-110
TCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-111
TCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-112
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-114
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-116
TCH_TRAFFIC_CARRIED_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-118
TCH_TRAFFIC_CARRIED_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-119
TOTAL_CALLS_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-120
UL_CHANNEL_REQUESTS_REJECTION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 17-121
UL_CHANNEL_REQUESTS_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 17-122
UL_LLC_TRAFFIC_VOLUME_INDICATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-124
UL_PDTCH_UTILISATION_BY_ALLOCATION . . . . . . . . . . . . . . . . . . . . . . . . . . 17-125
UL_PDTCH_UTILISATION_BY_TRAFFIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-126
UL_PDTCH_UTILISATION_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-127
UL_RLC_MAC_OVERHEAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-131
UL_TBF_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-132
UL_TBF_INTERLEAVING_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-133
UL_TBF_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-134
UL_TERMINAL_TYPE_ACTIVITY_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-135
UL_USER_TRAFFIC_EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-139
UL_USER_TRAFFIC_GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-141
UNSUCCESS_INTERNAL_HO_NOREEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-142
UNSUCCESS_INTERNAL_HO_REEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-143
Chapter 18: Network health reports

Network health statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . 18-13
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . 18-15
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . 18-17
CALL_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
CELL_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
DL_BANDWIDTH_INDICATOR_EGPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
DL_BANDWIDTH_INDICATOR_GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
GPRS_MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
HO_BLKD_BSP_OVERLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
HO_CAUSE_ADJ_CH_INTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
HO_CAUSE_BAND_HO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34
68P02901W56-T xiii
Jan 2010
Contents
HO_CAUSE_BAND_REASSGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-35
HO_CAUSE_CONGEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
HO_CAUSE_DISTANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-37
HO_CAUSE_DLINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38
HO_CAUSE_DLLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
HO_CAUSE_DLQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
HO_CAUSE_PWRBGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41
HO_CAUSE_UPINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42
HO_CAUSE_UPLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-43
HO_CAUSE_UPQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-44
HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-45
IMMEDIATE_ASSIGN_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-47
IMMEDIATE_ASSIGN_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48
IMMEDIATE_ASSIGN_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . 18-49
IMMEDIATE_ASSIGN_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-50
IN_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51
IN_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
IN_INTRA_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-54
INCOMING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55
INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-56
INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-58
INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-59
INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
MA_REQ_SDCCH_PG_RSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-62
MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63
MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
MEAN_TIME_BETWEEN_DROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-65
MEAN_TIME_BETWEEN_HOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66
NUM_HO_FROM_3G_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-67
NUM_HO_TO_3G_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-68
OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69
OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70
OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS. . . . . . . . . . . . . . . . . . . . . . . . . . 18-72
OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . 18-73
OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-74
OUT_INTRA_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . . . . . . . 18-76
OUT_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-77
OUTGOING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
PAGING_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-82
INTER_BSS_HO_ATTEMPT_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-83
INTRA_BSS_HO_ATTEMPT_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84
INTRA_CELL_HO_ATTEMPT_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-85
RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-86
RF_ASSIGN_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-88
RF_ASSIGN_FAIL_RATE_RECOVERED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-89
RF_ASSIGN_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-90
SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-91
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-92
SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-93
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-94
SDCCH_USAGE_ACCESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-96
xiv 68P02901W56-T
Jan 2010
SDCCH_USAGE_CALL_REESTABLISH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-98
SDCCH_USAGE_EMERGENCY_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-100
SDCCH_USAGE_IMSI_DETACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-102
SDCCH_USAGE_LOCATION_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-103
SDCCH_USAGE_MS_ORIGINATED_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-105
SDCCH_USAGE_MS_ORIGINATED_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-107
SDCCH_USAGE_SMS_ORIGINATED_SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-109
SDCCH_USAGE_PAGING_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-111
SDCCH_USAGE_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-113
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF . . . . . . . . . . . . . . . . . 18-115
SPILL_OVER_FACTOR_DIRECTED_RETRY. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-116
SPILL_OVER_FACTOR_MULTIBAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-117
TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-118
TCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-120
TCH_CONGESTION_TIME_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-121
TCH_CONGESTION_TIME_INNER_ZONE_HR . . . . . . . . . . . . . . . . . . . . . . . . . . 18-122
TCH_CONGESTION_TIME_OUTER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-123
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-124
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-126
TCH_TRAFFIC_CARRIED_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-128
TCH_TRAFFIC_CARRIED_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-129
UL_BANDWIDTH_INDICATOR_EGPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-130
UL_BANDWIDTH_INDICATOR_GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-132
Chapter 19: Ladder diagrams

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Ladder diagram constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
GSM call model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Call procedure milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Call setup and handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Assignment to TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
Intra-cell handover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-36
Enhanced 2G/3G handover and reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-41
Network assisted cell change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44
Call clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-47
Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-51
Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-53
Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-55
Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
Intra-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-58
Inter-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-62
Interband assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
Band Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-69
MTL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-71
GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-76
Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-81
Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-87
Chapter 20: Impacts on statistics

Extended GSM (EGSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Approximate equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
68P02901W56-T xv
Jan 2010
Contents
Frequently Asked Questions (FAQs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10
Chapter 21: Statistics history

History of raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
xvi 68P02901W56-T
Jan 2010
List
of
Figures
List of Figures
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 1-1: Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . 1-10

Figure 1-2: Histogram of a weighted distribution statistic . . . . . . . . . . . . . . . . . . . . 1-12
Figure 1-3: Diagram of immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . 1-18
Figure 5-1: Notation used in handover examples . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Figure 5-2: Internal cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Figure 19-1: Diagram of immediate assignment failure . . . . . . . . . . . . . . . . . . . . . 19-3
Figure 19-2: Handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Figure 19-3: Connection establishment successful . . . . . . . . . . . . . . . . . . . . . . . . 19-11
Figure 19-4: Connection establishment successful with FCS enabled . . . . . . . . . . . . . . 19-12
Figure 19-5: Connection establishment failure. . . . . . . . . . . . . . . . . . . . . . . . . . 19-13
Figure 19-6: Immediate assignment blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Figure 19-7: Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Figure 19-8: Connection establishment (mobile terminated call) successful . . . . . . . . . . . 19-16
Figure 19-9: Connection establishment (mobile terminated call) successful with FCS enabled . . 19-17
Figure 19-10: TCH assignment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-18
Figure 19-11: TCH assignment successful with FCS enabled . . . . . . . . . . . . . . . . . . 19-19
Figure 19-12: Immediate assignment failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Figure 19-13: TCH assignment blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
Figure 19-14: TCH assignment fail-recovered to SDCCH . . . . . . . . . . . . . . . . . . . . 19-22
Figure 19-15: Handover (intra-cell) successful. . . . . . . . . . . . . . . . . . . . . . . . . . 19-23
Figure 19-16: Handover (intra-cell) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24
Figure 19-17: Handover (intra-cell) fail-recovered to source channel . . . . . . . . . . . . . . 19-25
Figure 19-18: Handover (intra-cell) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Figure 19-19: Handover (inter-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Figure 19-20: Handover (inter-BSS) blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28
Figure 19-21: Handover (inter-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . 19-29
Figure 19-22: Handover (inter-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Figure 19-23: Inter-BSS handover failure with lost MS . . . . . . . . . . . . . . . . . . . . . 19-31
Figure 19-24: Inter-BSS handover directed retry external . . . . . . . . . . . . . . . . . . . . 19-32
Figure 19-25: Inter-BSS handover failure when the timer expires . . . . . . . . . . . . . . . . 19-33
Figure 19-26: Inter-BSS handover failure due to equipment failure . . . . . . . . . . . . . . . 19-34
Figure 19-27: Inter-BSS handover failure because of call clearing in both NS and MSS . . . . . 19-35
Figure 19-28: Handover (intra-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . 19-36
Figure 19-29: Handover (intra-BSS) blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
Figure 19-30: Handover (intra-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . 19-38
Figure 19-31: Handover (intra-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39
Figure 19-32: Intra-BSS handover standard directed retry . . . . . . . . . . . . . . . . . . . 19-40
Figure 19-33: 2G/3G handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-42
Figure 19-34: 2G/3G handover failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-43
Figure 19-35: Cell selection agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-44
Figure 19-36: No target cell information before sending a PCCC . . . . . . . . . . . . . . . . 19-45
Figure 19-37: New target cell for the MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-45
Figure 19-38: No target cell information before sending a PCCO . . . . . . . . . . . . . . . . 19-46
Figure 19-39: Reselection not required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-46
Figure 19-40: BSS initiated call clearing-cipher mode fail . . . . . . . . . . . . . . . . . . . . 19-47
68P02901W56-T xvii
Jan 2010
List of Figures
Figure 19-41: BSS initiated call clearing (RF loss on an SDCCH) . . . . . . . . . . . . . . . . 19-48
Figure 19-42: BSS initiated call clearing (RF loss on a TCH). . . . . . . . . . . . . . . . . . . 19-49
Figure 19-43: BSS initiated call clearing (queuing timeout) . . . . . . . . . . . . . . . . . . . 19-50
Figure 19-44: MS originated short message service (point-to-point) . . . . . . . . . . . . . . . 19-51
Figure 19-45: MS terminated short message service (point-to-point) . . . . . . . . . . . . . . 19-52
Figure 19-46: Intra-BSS congestion relief handover procedure . . . . . . . . . . . . . . . . . 19-54
Figure 19-47: Intra-BSS directed retry procedure . . . . . . . . . . . . . . . . . . . . . . . . 19-56
Figure 19-48: Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-57
Figure 19-49: Successful intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . 19-59
Figure 19-50: Unsuccessful interband handover with fail-recovered source cell . . . . . . . . 19-60
Figure 19-51: Unsuccessful interband handover . . . . . . . . . . . . . . . . . . . . . . . . 19-61
Figure 19-52: Successful inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . 19-63
Figure 19-53: Inter-BSS handover unsuccessful with fail-recovered source cell . . . . . . . . . 19-64
Figure 19-54: Inter-BSS handover unsuccessful due to invalid frequency supported. . . . . . . 19-65
Figure 19-55: Invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . 19-66
Figure 19-56: Intra-BSS handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . 19-67
Figure 19-57: Unsuccessful band reassign . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-68
Figure 19-58: RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-70
Figure 19-59: MTL link scenario (Part I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-72
Figure 19-60: MTL link transition scenarios (Part II) . . . . . . . . . . . . . . . . . . . . . . 19-73
Figure 19-61: MTL link transition scenarios (Part III) . . . . . . . . . . . . . . . . . . . . . . 19-74
Figure 19-62: MTL link transition scenarios (Part IV) . . . . . . . . . . . . . . . . . . . . . . 19-75
Figure 19-63: GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-76
Figure 19-64: GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-77
Figure 19-65: CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-78
Figure 19-66: GBL_PAGING_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-79
Figure 19-67: GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-80
Figure 19-68: CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-81
Figure 19-69: Accessibility CHANNEL_REQ_REJECT . . . . . . . . . . . . . . . . . . . . . . 19-82
Figure 19-70: CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-83
Figure 19-71: GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH . . . . . . . . . . . 19-84
Figure 19-72: Accessibility and GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 19-85
Figure 19-73: GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . 19-86
Figure 19-74: AIR_DL_TBF_FAILURES termination . . . . . . . . . . . . . . . . . . . . . . . 19-87
Figure 19-75: AIR_DL_TBF_FAILURES data transfer DDTR mode establishment . . . . . . . . 19-88
Figure 19-76: AIR_UL_TBF_FAILURE establishment and termination . . . . . . . . . . . . . . 19-89
Figure 19-77: AIR_UL_TBF_FAILURE data transfer . . . . . . . . . . . . . . . . . . . . . . . 19-90
Figure 19-78: DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-91
Figure 19-79: UL_PDTCH_SEIZURE one-phase access . . . . . . . . . . . . . . . . . . . . . 19-92
Figure 19-80: UL_PDTCH_SEIZURE two-phase access . . . . . . . . . . . . . . . . . . . . . 19-93
Figure 20-1: Approximate equality procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Figure 20-2: Phantom RACHs illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
xviii 68P02901W56-T
Jan 2010
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 2-1: Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45

Table 3-1: INTRA_BSS_HO_CAUSE_SUCC bins . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Table 3-2: NUM_SUSP_RESU_RCVD bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Table 4-1: ACCESS_PER_PPCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Table 4-2: AMR_FR_DL_ADAPTATION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Table 4-3: AMR_FR_DL_CODEC_MODE_USAGE bins . . . . . . . . . . . . . . . . . . . . . . 4-35
Table 4-4: AMR_FR_UL_ADAPTATION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Table 4-5: AMR_FR_UL_CODEC_MODE_USAGE bins . . . . . . . . . . . . . . . . . . . . . . 4-37
Table 4-6: AMR_HR_DL_ADAPTATION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Table 4-7: AMR_HR_DL_CODEC_MODE_USAGE bins . . . . . . . . . . . . . . . . . . . . . . 4-39
Table 4-8: AMR_HR_UL_ADAPTATION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Table 4-9: AMR_HR_UL_CODEC_MODE_USAGE bins . . . . . . . . . . . . . . . . . . . . . . 4-41
Table 4-10: ASSIGNMENT_REDIRECTION bins . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Table 4-11: Default bin ranges for BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . 4-56
Table 4-12: Default bin ranges for BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
Table 4-13: CALL_SP_VERS_DOWNGRADE_MONITOR bins (0–2) . . . . . . . . . . . . . . . . 4-65
Table 4-14: CALL_SP_VERS_DOWNGRADE_MONITOR bins (3) . . . . . . . . . . . . . . . . . 4-65
Table 4-15: CALLS_QUEUED bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
Table 4-16: CHAN_REQ_CAUSE_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
Table 4-17: CLR_CMD_FROM_MSC bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
Table 4-18: CLR_REQ_TO_MSC bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
Table 4-19: CLR_REQ_CALL_SETUP bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
Table 4-20: CS_PAGING_MSGS_FROM_MSC bins . . . . . . . . . . . . . . . . . . . . . . . . 4-81
Table 4-21: DL_LLC_DATA_VOLUME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Table 4-22: DL_LLC_TRANS_TIME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
Table 4-23: ER_INTRA_CELL_HO_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
Table 4-24: ER_INTRA_CELL_HO_SUC bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
Table 4-25: HO_FAIL_NO_RESOURCES bins. . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
Table 4-26: HO_REQ_FROM_MSC bins (0–5) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Table 4-27: HO_REQ_FROM_MSC bins (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Table 4-28: HO_REQ_ACK_TO_MSC bins (0–5). . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Table 4-29: HO_REQ_ACK_TO_MSC bins (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Table 4-30: IA_IAR_MSGS_PER_AGCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
Table 4-31: IN_INTER_BSS_HO bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
Table 4-32: IN_INTRA_BSS_HO bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
Table 4-33: INTERBAND_ACTIVITY bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
Table 4-34: INTRA_CELL_HO bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
Table 4-35: MA_COMPLETE_TO_MSC bins (0–5) . . . . . . . . . . . . . . . . . . . . . . . . 4-111
Table 4-36: MA_COMPLETE_TO_MSC bins (6). . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
Table 4-37: MA_REQ_FROM_MSC bins (0–5) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Table 4-38: MA_REQ_FROM_MSC bins (6). . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
Table 4-39: MS_ACCESS_BY_TYPE bins (0–7) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Table 4-40: MS_TCH_USAGE_BY_TYPE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
Table 4-41: MS_TCH_USAGE_BY_TYPE_PCS bins . . . . . . . . . . . . . . . . . . . . . . . . 4-120
Table 4-42: Bin update scenarios for NUM_CELL_RESEL_CELL . . . . . . . . . . . . . . . . . 4-124
68P02901W56-T xix
Jan 2010
List of Tables
Table 4-43: NUM_OF_SMS_INIT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137

Table 4-44: OK_ACC_PROC bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
Table 4-45: OUT_INTER_BSS_HO bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
Table 4-46: OUT_INTRA_BSS_HO bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
Table 4-47: PACKET_SYSINFO_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
Table 4-48: PACKET_SYSINFO_RESP bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147
Table 4-49: PFC_ADMISSION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-153
Table 4-50: PFC_ADMISSION_TRAFFIC_CLASS bins . . . . . . . . . . . . . . . . . . . . . . 4-155
Table 4-51: PFC_DOWNGRADE_FAILURE bins . . . . . . . . . . . . . . . . . . . . . . . . . 4-157
Table 4-52: PFC_DOWNGRADE_SUCCESS bins . . . . . . . . . . . . . . . . . . . . . . . . . 4-159
Table 4-53: PFC_GBR_DL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-161
Table 4-54: PFC_GBR_UL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-163
Table 4-55: PFC_PREEMPTIONS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-165
Table 4-56: PFC_PREEMPTIONS_TRAFFIC_CLASS bins . . . . . . . . . . . . . . . . . . . . . 4-167
Table 4-57: PFC_REJ_DGRD_PRMPT_CELL bins . . . . . . . . . . . . . . . . . . . . . . . . . 4-168
Table 4-58: PFC_REJECT_CAUSES bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
Table 4-59: PFC_REJECTION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-173
Table 4-60: PFC_REJECTION_TRAFFIC_CLASS bins. . . . . . . . . . . . . . . . . . . . . . . 4-175
Table 4-61: PFC_TRANSFER_DELAY bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-176
Table 4-62: PFC_UPGRADE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-178
Table 4-63: PPCH_Q_PAGE_DISCARD bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
Table 4-64: PREEMPT_CAP bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181
Table 4-65: QUEUE_PREEMPT_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-182
Table 4-66: RF_LOSSES_SD bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183
Table 4-67: RF_LOSSES_TCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185
Table 4-68: RF_LOSSES_TCH_HR bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187
Table 4-69: SDCCH_HANDOVER bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-193
Table 4-70: SMS_INIT_ON_SDCCH_HO_OUT bins . . . . . . . . . . . . . . . . . . . . . . . . 4-195
Table 4-71: SIGNALLING_HANDOVER bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-196
Table 4-72: T bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-200
Table 4-73: TCH_PREEMPT_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-208
Table 4-74: TCH_PREEMPT_RQD bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-211
Table 4-75: TCH_Q_REMOVED bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-214
Table 4-76: TIMER_EXP_PAP_CONV bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-219
Table 4-77: UL_RLC_NACK_BLKS bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-221
Table 4-78: UL_RLC_STALLED_BLKS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-223
Table 4-79: UL_LLC_DATA_VOLUME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-225
Table 4-80: UL_LLC_TRANS_TIME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-227
Table 4-81: ZONE_CHANGE_ATMPT bins (0–4) . . . . . . . . . . . . . . . . . . . . . . . . . 4-229
Table 4-82: ZONE_CHANGE_SUC bins (0–4). . . . . . . . . . . . . . . . . . . . . . . . . . . 4-230
Table 5-1: Neighbor cell statistics pegged . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Table 5-2: Bin update scenarios for NUM_CELL_RESEL_NEI . . . . . . . . . . . . . . . . . . 5-10
Table 5-3: OUT_HO_NC_CAUSE_ATMPT bins (0–11). . . . . . . . . . . . . . . . . . . . . . . 5-13
Table 6-1: Statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Table 6-2: CHAN_REQ_MS_FAIL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Table 6-3: FER_AMR_FR bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
Table 6-4: FER_AMR_FR Quality number conversion (n is the value of fer_meas_period) . . . . 6-18
Table 6-5: FER_AMR_HR bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Table 6-6: FER_AMR_HR Quality number conversion (n is the value of fer_meas_period) . . . . 6-20
Table 6-7: FER_GSM_FR_EFR bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Table 6-8: FER_GSM_FR_EFR Quality number conversion (n is the value of fer_meas_period) . . 6-22
Table 6-9: FER_GSM_HR bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Table 6-10: FER_GSM_HR Quality number conversion (n is the value of fer_meas_period) . . . 6-25
Table 6-11: Default bin ranges for INTF_ON_IDLE. . . . . . . . . . . . . . . . . . . . . . . . 6-26
Table 6-12: Signal level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Table 6-13: RBER Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30
Table 6-14: Bin ranges for ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
Table 6-15: Statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
xx 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application List of Tables
Table 7-1: PFC_REJ_DGRD_PRMPT_PRP bins . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Table 11-1: BUSY CICS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Table 12-1: ATER_CHANNEL_STATUS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Table 12-2: EXT_UL_EXITS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Table 12-3: EXT_UL_USF_USAGE bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Table 13-1: AIR_DL_TBF_FAILURES bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Table 13-2: AIR_UL_TBF_FAILURES bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Table 13-3: BLOCKED_DL_TBFS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15
Table 13-4: CH_REQ_UNSVCD_PCU bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Table 13-5: CHANNEL_REQS_REC bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-20
Table 13-6: CHANNEL_REQS_SUCCESS bins . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Table 13-7: CODING_SCHEME_CHANGE bins. . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Table 13-8: Bin ranges for DL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
Table 13-9: Bin ranges for DL_BLER_CS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38
Table 13-10: Bin ranges for DL_BLER_CS3 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Table 13-11: Bin ranges for DL_BLER_CS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42
Table 13-12: Bin ranges for DL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Table 13-15: Bin range for DL_BLER_MCS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-50
Table 13-21: DL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-62
Table 13-22: Bin ranges for DL_LLC_FRAMES_GB . . . . . . . . . . . . . . . . . . . . . . . . 13-64
Table 13-23: Bin ranges for DL_LLC_FRAMES_PCU . . . . . . . . . . . . . . . . . . . . . . . 13-65
Table 13-24: Bin ranges for DL_RADIO_BLKS_1_TS . . . . . . . . . . . . . . . . . . . . . . . 13-71
Table 13-25: Pegging method for DL_RADIO_BLKS_1_TS statistic . . . . . . . . . . . . . . . . 13-72
Table 13-32: Bin ranges for DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . 13-82
Table 13-33: Pegging method for DL_RLC_ACK_NEW_BLKS statistic . . . . . . . . . . . . . . 13-83
Table 13-34: Bin ranges for DL_RLC_DDTR_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 13-84
Table 13-35: Bin ranges for DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 13-85
Table 13-36: Pegging method for DL_RLC_NACK_BLKS statistic . . . . . . . . . . . . . . . . 13-86
Table 13-37: Bin ranges for DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 13-87
Table 13-38: Pegging method for DL_RLC_RETX_BLKS statistic . . . . . . . . . . . . . . . . . 13-88
Table 13-39: Bin ranges for DL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . 13-89
Table 13-40: Pegging method for DL_RLC_STALLED_BLKS statistic . . . . . . . . . . . . . . . 13-90
Table 13-41: Bin ranges for DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . 13-91
Table 13-42: Pegging method for DL_RLC_UNACK_NEW_BLKS statistic . . . . . . . . . . . . 13-92
Table 13-43: EGPRS_64K_CHANNELS_SWITCHED bins. . . . . . . . . . . . . . . . . . . . . 13-103
Table 13-44: G_RACH_UNSVCD_BTS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-107
Table 13-45: GBL_DL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . 13-110
Table 13-46: GBL_UL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . 13-118
Table 13-47: GPRS_32K_CHANNELS_SWITCHED bins . . . . . . . . . . . . . . . . . . . . . 13-122
Table 13-48: Bin ranges for GPRS_CELL_CONGESTION. . . . . . . . . . . . . . . . . . . . . 13-129
Table 13-49: GPRS_CHANNELS_SWITCHED bins . . . . . . . . . . . . . . . . . . . . . . . . 13-132
Table 13-50: Default bin ranges for GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . 13-138
Table 13-51: Default bin ranges for GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . 13-140
Table 13-52: IMM_ASSGN_CAUSE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-147
Table 13-53: Bin descriptions for PDU_DISCARD_FR . . . . . . . . . . . . . . . . . . . . . . 13-161
68P02901W56-T xxi
Jan 2010
List of Tables
Table 13-54: Bin descriptions for PDU_DISCARD_LLC . . . . . . . . . . . . . . . . . . . . . . 13-162

Table 13-55: Mapping between timeslots pending service and PRP load (prp_fanout_mode=1) . . 13-164
Table 13-56: Mapping between timeslots pending service and PRP load (prp_fanout_mode=2) . . 13-164
Table 13-57: PRP load range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-165
Table 13-58: Bin ranges for UL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-170
Table 13-61: Bin ranges for UL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . 13-177
Table 13-70: UL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-195
Table 13-71: Bin ranges for UL_LLC_FRAMES . . . . . . . . . . . . . . . . . . . . . . . . . . 13-200
Table 13-72: Bin ranges for UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . 13-207
Table 13-73: Pegging method for UL_RADIO_BLKS_8PSK_1_TS statistic . . . . . . . . . . . . 13-207
Table 13-75: Pegging method for UL_RADIO_BLKS_8PSK_2_TS statistic . . . . . . . . . . . . 13-209
Table 13-78: Bin ranges for UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . 13-215
Table 13-82: Bin ranges for UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . 13-223
Table 13-83: Pegging method for UL_RLC_ACK_NEW_BLKS statistic . . . . . . . . . . . . . . 13-223
Table 13-84: Bin ranges for UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 13-225
Table 13-85: Pegging method for UL_RLC_RETX_BLKS statistic . . . . . . . . . . . . . . . . . 13-225
Table 13-86: Bin ranges for UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . 13-227
Table 13-87: Pegging method for UL_RLC_UNACK_NEW_BLKS statistic . . . . . . . . . . . . 13-227
Table 15-1: Location of MMI PCU real-time statistics descriptions. . . . . . . . . . . . . . . . 15-2
Table 15-2: Location of MMI BSC/BTS real-time statistics descriptions . . . . . . . . . . . . . 15-2
Table 17-1: Key statistic descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Table 18-1: Average block size used for EGPRS coding schemes . . . . . . . . . . . . . . . . . 18-23
Table 18-2: Average block size used for GPRS coding schemes . . . . . . . . . . . . . . . . . 18-26
Table 18-3: Average block size used for EGPRS coding schemes . . . . . . . . . . . . . . . . . 18-130
Table 18-4: Average block size used for GPRS coding schemes . . . . . . . . . . . . . . . . . 18-132
Table 19-1: Call setup and handover statistics matrix . . . . . . . . . . . . . . . . . . . . . . 19-7
Table 20-1: MS access to a traffic channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Table 20-2: Impact due to increased handovers . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Table 20-3: Impact due to congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5
Table 21-1: History of raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2
xxii 68P02901W56-T
Jan 2010
About
This
Manual
Maintenance information: GSM Statistics

Application
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is covered in this manual?
The manual provides context information and detailed descriptions of the GSR10 raw, key, and
network health statistics sets supported by Motorola GSM cellular equipment.
Detailed information on previous GSR statistical information, for example, GSR8 and GSR9, can
be obtained from the appropriate GSM Statistics Application manual.
The target audience for this manual is GSM network operators and administrators.
68P02901W56-T 1
Jan 2010
Revision history
Revision history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following sections show the revision status of this document.
Version information
The following table describes the changes made to this document:
Version Date of issue Description

R Jan 2008 GSM Software Release 8
S May 2009 GSM Software Release 9
T Jan 2010 GSM Software Release 10
Release information
This section describes the changes in this document between release GSR9 and GSR10.
• Gb over IP
• CTU4
Resolution of Service Requests
The following Service Requests are resolved in this document:
Service
CMBP Number Description
Request
N/A N/A N/A
2 68P02901W56-T
Jan 2010
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Purpose
Motorola documents provide the information to operate, install, and maintain Motorola
equipment. It is recommended that all personnel engaged in such activities be properly trained
by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
Document banner definitions
A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY — UNDER DEVELOPMENT
68P02901W56-T 3
Jan 2010
Text conventions
Text conventions
The following conventions are used in Motorola documents to represent keyboard input text,
screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.

Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental

variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences
Special key sequences are represented as follows:
CTRL-c or CTRL+C Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or Press the Ctrl, Shift, and C keys at the same time.
CTRL+SHIFT+C
ALT-f or ALT+F Press the Alt and F keys at the same time.
ALT+SHIFT+F11 Press the Alt, Shift and F11 keys at the same time.
¦ Press the pipe symbol key.
RETURN or ENTER Press the Return or Enter key.
4 68P02901W56-T
Jan 2010
Contacting Motorola
Contacting Motorola
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Motorola appreciates feedback from the users of our documents.
24–hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24–hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Ordering documents and CD-ROMs
With internet access available, to view, download, or order documents (original or revised), visit
the Motorola customer web page at https://mynetworksupport.motorola.com, or contact your
Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Questions and comments
Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
• The document type
• The document title, part number, and revision character
• The page number with the error
• A detailed description of the error and if possible the proposed solution
68P02901W56-T 5
Jan 2010
Errors
6 68P02901W56-T
Jan 2010
Chapter
Introduction to statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistics are pieces of numerical data which have been collected and systematically
categorized. In GSM terms, the data collected is generated from network and system events.
This data is categorized as a raw statistic type and used to determine system quality of service.
This categorization of data allows the network operators and administrators to gauge service
accessibility, integrity, and retainability.
The following topics are described:

• Introduction to GSM Statistics Manual on page 1-2.
• Types of raw statistics on page 1-6.
• Statistic usages on page 1-13.
• Ladder diagrams on page 1-18.
• Statistics history on page 1-19.
68P02901W56-T 1-1
Jan 2010
Introduction to GSM Statistics Manual Chapter 1: Introduction to statistics
Introduction to GSM Statistics Manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistics
This manual describes the statistical measurements generated by the BSS in response to the
monitored network and system events. The statistics include statistical measurements defined
in the GSM Technical Specification 12.04, plus additional Motorola defined statistics.
NOTE
To facilitate easy access, the statistics are presented in alphabetical order.
Network management and planning
Network operators can use raw and processed statistics for the following network management
and planning functions:
• Quality of service monitoring
Service accessibility
Service integrity
Service retainability
• Fault finding
• Optimization
• Network planning
• Installation and commissioning
Raw statistics
The BSS generates raw statistics for reporting individual network performance. The OMC-R
processes raw statistics to create key, network health and custom statistics. These statistics
include call processing, interface, and processor utilization measurements.
Call statistics
Call processing functions and features generate statistics that show how the system is
performing.
1-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Key statistics
Interface statistics
Terrestrial interface activities generate interface statistics that show the activity on the
interface links and their conditions. The interface links are the physical connections between
the MS, BSS, and MSC network elements.
Processor utilization statistics
Processor utilization statistics show the percentage of GPROC utilization.
NOTE
If CTU2 is used in the system, processor utilization statistics are not supported.
Key statistics
Key statistics are generated at the OMC-R by processing raw statistics generated by the BSS,
using predefined algorithms. These statistics:
• Provide an overall indication of the condition of the system.
• Allow comparisons of similar time periods over a span of time.
• Detect congestion trends and possible performance degradation.
Key statistics are also provided to facilitate the monitoring of the most important network
parameters. For example, various handover failure statistics can be combined and averaged
over the total number of calls, to produce a handover failure rate key statistic.
The following are the key statistics groupings:

• Call Summary
• Channel Usage
• Connection Establishment
• RF Loss Summary
• MTL Utilization
Network health statistics
Network health statistics are calculated at the OMC-R using a combination of raw and key
statistics. These statistics are used to create BSS network performance reports. These reports
provide an indication of the health of the network from the perspective of the subscribers.
68P02901W56-T 1-3
Jan 2010
Custom statistics Chapter 1: Introduction to statistics
The following are the network health report groupings:

• Health check
• GPRS performance
• Handover performance
• TCH congestion
• SDCCH congestion
• Paging performance
• Radio performance
Custom statistics
The OMC-R permits the creation of custom statistics using the algebraic combination of existing
raw and key statistics. Refer to the manual Installation and Configuration: GSM System
Configuration (68P02901W17) manual for procedures on creating custom statistics.
Statistic terms
This manual contains the following statistical terms throughout this manual:
Application process - The process responsible for creating and pegging a statistic.
Bin - A collection area used for the storage of cumulative values for distribution and counter
array statistics.
• Distribution statistics:
The use of a bin is for measuring the frequency of an event. The measurement is done
by time (weighted distributions) or by occurrences (normal distributions). There are ten
bins (numbered 0 - 9). Each bin has a low to high range.
• Counter array statistics:
The use of a bin is for counting the number of occurrences on a per scenario or cause basis.
The number of bins varies based on the number of causes being tracked.
Cumulative value - The total value for the entire interval.
Default time interval - The key statistics default time interval is 0.5 hours when computing
all key statistics.
The interval used for two key statistics, TCH_MEAN_HOLDING_TIME and

SDCCH_MEAN_HOLDING_TIME, is specified in seconds. To convert the default value of 0.5
hours to seconds, multiply the 0.5 hours by 3600.
Interval - A recording time in which a statistic is pegged. The default time is 30-minute
intervals and there are 12 intervals of data stored at the BSS.
Interval expiry - The end of an interval.
Maximum value - The highest reported value for the interval.
1-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Statistic terms
Mean value - The average value for the interval.
Minimum value - The lowest reported value for the interval.
Number of periods - The value used in calculating the mean duration. This value is
incremented by one, every time the duration timer is stopped.
Number of samples - The value used in calculating the mean for distributions. For a normal
distribution, this value is incremented by one, each time a value is reported. The time difference
increments this value for a weighted distribution, since the last reported value.
Peg - A peg is a single incremental action modifying the value of a statistic.
Pegging - Pegging refers to recording a statistical value.
Reported value - The value reported by the application process pegging the statistic.
SUM - In the key and network health statistic formulae, SUM is the arithmetic total of
a mathematical formula for one or more cells selected in the OMC-R GUI Performance
Management window. The mathematical formula can include a single raw statistic or a set of
arithmetic functions.
Temporary value - This value is used in weighted distributions. The application process
supplies both the reported value and the temporary value. The reported value is used to update
a bin. The temporary value is stored for updating a bin at interval expiry.
Threshold value - The threshold value can be set in the configuration management database
using the MMI. When the reported value for a statistic equals the threshold value, an alarm
is sent from the BSS to the OMC-R. Thresholds can also be specified for individual bins in
counter array statistics.
68P02901W56-T 1-5
Jan 2010
Types of raw statistics Chapter 1: Introduction to statistics
Types of raw statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
The BSS reports the following six types of statistics:

• Counter
• Counter array
• Gauge
• Duration
• Normal distribution
• Weighted distribution
Counter statistics
A counter statistic is the cumulative value of an event reported by an application process. The
application process increments or pegs the counter statistic by the reported value during an
interval. The ALLOC_SDCCH statistic is an example of a counter statistic.
Threshold event reporting
A counter statistic can have a user specified threshold that can generate an alarm when
reached. The BSS reports only one alarm to the OMC for a specific statistic during an interval.
Maximum value
The maximum value of a counter statistic is 4294967294 (HEX= 0xfffffffe). If a counter statistic
reaches the maximum value, it remains at that value until the interval expiry.
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the counter
statistic value, then resets it to zero.
1-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Counter array statistics
Counter array statistics
Counter array statistics are:

• The total number of times an event occurs and a breakdown of the causes.
• The reasons why the event occurred during an interval.

When an event occurs, the BSS increments the individual cause or reason by the value reported
by the application at the interval expiry. The OK_ACC_PROC statistic is an example of
a counter array statistic.
Display convention
The convention used in this manual for presenting a specific bin of a counter
array statistic is COUNTER ARRAY STATISTIC NAME[bin name]. For example,
OK_ACC_PROC[CM_REESTABLISH] is the CM_REESTABLISH bin of the OK_ACC_PROC
counter array statistic.
Counter array bins
A bin is a storage area in a counter array for cumulative cause or reason values. The number
of bins in a counter array statistic depends on the number of causes or reasons associated
with a specific event.
Maximum value
The maximum value for the total and individual cumulative values is 65534 (HEX=0xfffe). If a
bin count reaches this value during a period, the bin contents remains at the maximum value
until the interval expiry.
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the counter
array total values and the values of the individual bins and then resets them to zero.
Gauge statistics
Gauge statistics report the maximum and mean values of a statistic for an interval. The
IDLE_TCH_INTF_BANDO statistic is an example of a gauge statistic.
While a gauge statistic can result in the report of a reported negative value, the cumulative
value cannot be a negative value. The BSS checks the cumulative before calculating the mean
value, and if the result is a negative number, it sets the mean to zero.
Threshold event reporting
A gauge statistic can have a user specified threshold that can generate an alarm when the
threshold is reached. The BSS only reports one alarm to the OMC for a specific statistic during
an interval.
68P02901W56-T 1-7
Jan 2010
Duration statistics Chapter 1: Introduction to statistics
Interval expiry
Interval expiry is the end of a statistic interval. At the interval expiry, the BSS saves the mean
and maximum gauge statistic values and then resets them to zero.
Duration statistics
A duration statistic is a group of values associated with the timing of events controlled by an
application process. The duration statistics include the total duration, mean, maximum, and
minimum values. The FLOW_CONTROL_BARRED statistic is an example of a duration statistic.
Total duration
The OMC reports only the total duration.
The total duration is the length of time an event occurs during an interval. It is a cumulative
value reported in milliseconds. When the event starts, the BSS saves the start time of the day
(in milliseconds). When the event ends, the BSS saves the stop time of day (in milliseconds).
The BSS calculates the total duration using the following formula:
stop time - start time
Wraparound to next day
The BSS automatically checks the time of the day to determine the interval. If the start time is
greater than the stop time, the BSS calculates the total duration using the following formula:
(86400000 - start time) + stop time
Mean value
The BSS calculates the mean duration by dividing the total duration by the period counter. The
BSS increments the period counter each time a measured event occurs during an interval.
mean = total time / period counter
Maximum value
The maximum value of a duration statistic is 86400000 (the number of milliseconds in 24 hours).
1-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Normal distribution statistics
Interval expiry
Interval expiry is the end of a statistic interval. The following processes occur at the interval
expiry:
• If no events occur during the interval, the BSS sets the duration minimum value to zero.
The BSS saves this minimum value and then resets it to 0xffffffff.
• The BSS saves the duration mean and maximum values and then resets them to zero.
• The BSS resets the period counter and cumulative values to zero.
• The BSS stops and resets any active timers.
Normal distribution statistics
Normal distribution statistics are the number of times the reported value of an event falls
within a specified range. A distribution statistic is a single row array of ten bins, numbered
0-9. The BSS also saves the minimum reported value, the maximum reported value, and a
calculated mean of the reported values. The OMC reports only the distribution mean, maximum,
and minimum values.
Bins
Each bin represents a range of values reported by an application. Each time an application
reports a value, the BSS increments the bin corresponding to the reported value by one. The
BSS also increments the sample count by one and calculates the total of all the reported values
during the interval. The disp_stats command displays the individual bin values.
The operator can specify the range of values represented by each bin or use the system defaults.
Each bin represents a range of values depending on the focus of the statistical analysis. Narrow
bin ranges permit closer examination of the periods of greatest activity.
Mean value
The BSS calculates the mean value by dividing the cumulative total of the reported values
by the sample count.
NOTE
If there are gaps in the bin ranges, some occurrences of reported events are not
included in the bin counts. For example, if the assigned range of values of two
adjacent bins are 10-15 and 17-20, a reported event with a value of 16 is not recorded.
The mean value does not account for the unrecorded event.
68P02901W56-T 1-9
Jan 2010
Weighted distribution statistics Chapter 1: Introduction to statistics
Histogram
A normal distribution statistic can be illustrated as a histogram. Figure 1-1 shows that the range
of values assigned to bin 0 is 0-10, bin 1 is 11-20, and bin 7 is 71-80. The histogram shows that
each of bin 0 and bin 1 contains two occurrences and bin 7 contains one occurrence.
Figure 1-1 Histogram of a normal distribution statistic

5
COUNT 2
0
0 1 2 3 4 5 6 7 8 9
BINS
ti-GSM-Normal distribution-00343-ai-sw
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
• The mean value is calculated. If the number of reported events is not equal to zero, the
mean value is calculated by dividing the cumulative value of all the reported events by
the number of reported events.
• The distribution minimum value is saved and reset to 0xffffffff. If no value was received
during the interval, the duration minimum value is set to zero.
• The distribution mean value and maximum value are saved and reset to zero.
• The number of reported events and the cumulative value are reset to zero.
• The values in each of the ten bins are saved and reset to zero.
Weighted distribution statistics
Weighted distribution statistics are the length of time that the reported value of an event falls
within a specified range. These statistics are placed in a single row array of ten bins, numbered
0-9, and a mean duration of the reported events. The minimum and maximum durations of the
reported values are also saved and reported at the end of the interval.
1-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Weighted distribution statistics
Bins
Each bin is defined to represent a range of values. Each time an application process reports
a value, the bin corresponding to the reported value is incremented by the length of time the
reported value stays within the bin's specified range. This allows the number of times a reported
value falls within a specific range to be used to calculate the mean.
The range of values that can be assigned to each of the ten bins in the array is variable. The
range of values can be sized based on the focus of the analysis to be performed. For example,
when measuring a statistic, the range of values assigned to the bins can be assigned to reflect
the periods of greatest activity. By narrowing the bin ranges, the periods of greatest activity can
be more closely examined.
NOTE
If there are gaps in the bin ranges, some occurrences of the reported events are
not included in the bin counts. For example, if the assigned range of the values of
two adjacent bins are 10-15 and 17-20, a reported event with a value of 16 is not
recorded. The mean value does not account for the unrecorded event.
Wraparound to next day
A check is automatically made to determine the interval. If the start time is greater than the
stop time, the total duration is calculated using the following formula:
(86400000 - start time) + stop time
Mean value
The mean value is the statistical average of all the reported values divided by the number
of reported events.
NOTE
The mean for a weighted distribution statistic is not a duration value and is not
calculated using the bin values.
Histogram
A weighted distribution statistic can be illustrated as a histogram. Figure 1-2 shows that the
range of values assigned to bin 0 is 0-10 and bin 7 is 71-80. The following histogram shows that
the duration of the event reporting values from 0-10 was 40 milliseconds, and the duration of
the events reporting values from 71-80 was 20 milliseconds.
68P02901W56-T 1-11
Jan 2010
Weighted distribution statistics Chapter 1: Introduction to statistics
Figure 1-2 Histogram of a weighted distribution statistic

50
40
30
COUNT 20
10
0
0 1 2 3 4 5 6 7 8 9
BINS
ti-GSM-Weighted distribution-00344-ai-sw
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
• Stop any running timers.
• The mean value is calculated. If the number of reported events is not equal to zero, the
mean value is calculated by dividing the cumulative value of all the reported events by
the number of reported events.
• The distribution minimum value is saved and reset to 0xffffffff. If no value was received
during the expired interval, the duration minimum value is to 0.
• The distribution mean value and maximum value are saved and reset to zero.
• The number of reported events and the cumulative value are reset to zero.
• The values in each of the ten bins are saved and reset to zero.
1-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Statistic usages
Statistic usages
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Quality of service monitoring
Quality of service is determined by the statistics related to service accessibility, integrity, and
retainability.
Statistics associated with the following processes are used to determine service accessibility:
• MS registration
• MS paging
• Network accessibility
• Call set up time
• Call release time
• Call release delay
Service integrity
Statistics associated with the following processes are used to determine service integrity:
• Call clarity
• Interference
Statistics associated with premature releases are used to determine service retainability.
Service accessibility is associated with the following call setup and clearing processes:
• MS registration and paging
• Network accessibility
• Call set up time
68P02901W56-T 1-13
Jan 2010
Service accessibility Chapter 1: Introduction to statistics
• Call release time
• Call release delay
MS registration and paging
Cells are grouped in location areas. A Mobile Station (MS) is typically paged only in the cells of
one location area when an incoming call arrives. Therefore, the MS informs the MSC of the
location area in which the subscriber is to be paged. It does so by a location updating procedure.
The best outcome of the procedure is available when the network indicates that normal service
is available.
Several outcomes are possible when the registration is not successful, either due to:
• the procedure running correctly and the network providing a meaningful answer, possibly
denying service.
• the procedure running incorrectly and the network providing an answer that is
meaningless.
After updating the MS location, the MSC can page when an incoming call arrives. The MSC
provides the concerned BSC with the ID of the MS to be paged and the list of the cells in which
the paging is to be issued. The BSC is in charge of managing the grouping and scheduling of
paging messages and initial assignment of messages.
Network accessibility
A registered MS can access the network. Access denial is divided into three main categories:
• Call blocking.
No signaling channel (SDCCH) is available.
No Traffic Channel (TCH) is available.
• Failure to maintain a signaling channel or traffic channel.

MS is moving out of range, for example, into a garage.
MS is being switched off.
A hardware failure (MS or BSS).
• Refusal by the MSC for network access.
Failure to gain network access is pegged in BSS statistics. For a detailed analysis,
investigate the MSC statistics, as it is an MSC process.
1-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Service integrity
Call set-up time
Post-selection delay and answer signal delay determine the call set-up time.
• Post-selection delay: the time interval between dialing the last digit on the fixed network,
or pressing the send button on an MS, to receiving the appropriate tone. One possible
reason for this delay is that all resources have been allocated to other calls, which can
result in a queuing delay.
• Answer signal delay: the time taken in connecting the called terminal through to the
calling terminal, once the called terminal has gone off hook.
The raw statistics TCH_DELAY and CALLS_QUEUED are associated with call set-up time and
answer signal delay.
Call release time
Call release time is the time taken to release the call from the moment the end button is pressed
or after the handset on the fixed network is replaced.
Call release delay
Call release delay is the time between releasing one call and being able to originate another.
The only aspect of concern to the BSS is queuing. All other areas are transparent to the BSS.
Service integrity
Service integrity is determined by the processes affecting the following:

• Call clarity
• Lack of interference
• Correct tones and announcements
Call clarity
Call clarity is measured by the uplink-downlink path loss difference on the air interface. The
raw statistic PATH_BALANCE is the only measurement associated with call clarity.
Lack of interference
The lack of interference is measured by the bit error rate and the interference level on monitored
idle channels. The raw statistics BER and INTF_ON_IDLE are the only measurements
associated with lack of interference.
68P02901W56-T 1-15
Jan 2010
Service retainability Chapter 1: Introduction to statistics
Correct tones and announcements
Subscriber perceptions of service integrity are influenced by the delivery of correct tones and
announcements when using the system. No statistics are available to measure correct tones
and announcements.
Service retainability is determined by the lack of premature releases. The following factors can
affect a premature release:
• Base ceases to detect the RF signaling from the MS.
• MS fails to reach the target channel on handover.
• Call releases due to equipment failure (MSC, base site, or MS).
• Call is lost due to preemptive emergency call.
A subscriber perceives a premature release as a dropped call. Refer to the Ladder diagrams in
Chapter 19 Ladder diagrams.
Fault finding
GSM statistics can be used to find certain classes of faults in the cellular system. A set of
statistics which can be used to perform this function is identified in this section.
Monitoring Faults
Hard failures are normally identified though alarm surveillance. However, it is possible for a
system component to deteriorate over time, while still continuing to function. The deterioration
can manifest itself in multiple ways such as an increase in dropped call rate, or a lower call
completion rate. Monitoring of these system parameters over time can provide the operator with
an early indication of performance degradation due to deterioration in hardware components.
Types of faults
Example of the types of faults that can be identified using statistics include:
• Damaged antennas
• Frequency drift
• Electromechanical problems
Problems with remote combiners
Noisy channels
1-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Optimization
Optimization
Optimization of system parameters is necessary to ensure that the installed cellular

infrastructure is utilized as efficiently as possible. Statistics can be used to monitor and verify
the effects of optimization activities. For example, if handover thresholds are adjusted, statistics
can be used to verify that the new threshold results in an improved handover success rate.
Optimization of a GSM network is a process, whereby several BSS database parameters are
fine-tuned from their default values, and antenna installations are adjusted to improve call
success rate and quality.
By optimizing a network, the performance of the cellular equipment is verified and a benchmark
is obtained for the system that can be used for subsequent expansion. The results can also be
used to modify the original data used in the frequency planning tool.
Network planning
It is possible to determine whether the network is correctly dimensioned for the offered traffic
load. Statistics that monitor resource utilization and congestion can be used to determine when
the network expansion or contraction is required.
Installation and commissioning
Installation and commissioning of cellular equipment is a complex procedure that must be

verified after completion. Part of the verification procedure uses statistics to ensure that the
system is operational.
Drive testing is currently one of the means used to verify installation of the network. Statistics
can be used to verify the data collected during drive testing. Thus, ensuring that all components
of the system are operational.
NOTE
This activity is currently supported with the help of the Call Trace feature.
68P02901W56-T 1-17
Jan 2010
Ladder diagrams Chapter 1: Introduction to statistics
Ladder diagrams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
About ladder diagrams
The relationship between statistics and call processing elements and functions are graphically
represented as ladder diagrams in Chapter 19 Ladder diagrams.
Ladder diagrams show the relationships between the MS, BSS, and MSC elements, represented
as vertical lines.
The message-flow between the network elements is presented as horizontal lines representing
a sequential flow of events. Arrows are used to indicate the direction of the message-flow.
Message names are placed above the directional line.
Intermediate network element functions are placed on the vertical lines as a sequential
reference. Parallel functions can also be included as separate vertical lines for additional
reference.
Statistics associated with the individual messages are located immediately below the directional
line. All the statistics that can be generated as a result of the process flow is listed on the
diagram.
Example
Figure 1-3 Diagram of immediate assignment failure

MS BSS MSC
CHANNEL REQUEST (RACH)
OK_ACC_PROC_SUC_RACH
(SEE NOTE)
IMMEDIATE ASSIGNMENT (AGCH)
TIMEOUT
CHAN_REQ_MS_FAIL
NOTE: RSS Abis does additional filtering of RACH.
ti-GSM-Immediate assignment-00345-ai-sw
1-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Statistics history
Statistics history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
It is both useful and important to understand when specific statistics have been introduced into
the system. As the system develops, new statistics can be introduced or existing statistics can be
modified, replaced or removed. Chapter 21 Statistics history shows a history of statistics from
release 1650 to the present in tabular form. The intention is to help maintenance personnel
track the development of the statistics by the release number.
68P02901W56-T 1-19
Jan 2010
Statistics history Chapter 1: Introduction to statistics
1-20 68P02901W56-T
Jan 2010
Chapter
Statistical operations
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistical data can be employed in various ways to describe the operation of the system. The
view an operator gets of how the system is performing can be shown through the way statistics
are displayed. The topics described here show how statistical property displays can be enabled
and configured.
The following topics are described:

• Enabling/disabling a statistic on page 2-2.
• Displaying enabled statistics on page 2-15.
• Displaying statistic values on page 2-21.
• Setting the statistic interval on page 2-38.
• Displaying the statistic interval on page 2-39.
• Displaying the statistic interval start times on page 2-40.
• Setting statistic properties on page 2-42.
• Displaying statistic properties on page 2-49.
68P02901W56-T 2-1
Jan 2010
Enabling/disabling a statistic Chapter 2: Statistical operations
Enabling/disabling a statistic
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Statistics must be enabled to obtain statistical data. The stat_mode command enables and
disables a statistic. Refer to the manual Technical Description: BSS Command Reference
(68P02901W23) for a detailed description of the stat_mode command.
Default enabled statistics
Per cell statistics
The default mode at start-up for the following per cell statistics is enabled. These statistics are
also enabled when a cell is added:
• ACCESS_PER_PCH
• ALLOC_SDCCH
• ALLOC_SDCCH_FAIL
• ALLOC_TCH
• ALLOC_TCH_FAIL
• BUSY_SDCCH
• BUSY_TCH
• IN_INTER_BSS_HO
• IN_INTRA_BSS_HO
• INTRA_CELL_HO
• MA_CMD_TO_MS_BLKD
• MA_REQ_FROM_MSC
• OK_ACC_PROC
• OUT_INTER_BSS_HO
• OUT_INTRA_BSS_HO
• RF_LOSSES_SD
• TOTAL_CALLS
2-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Enabling a statistic
Per timeslot statistics
The default mode at start-up for the following per timeslot statistics is enabled:
• RF_LOSSES_TCH
• CHAN_REQ_MS_FAIL
Enabling a statistic
A statistic is enabled by entering the stat_mode command using the following syntax:
stat_mode <meas_type> on [<location>] [<cell_desc>]
Where: Is:
meas_type the statistic being enabled
on enable mode
location the location of the statistic being enabled, if necessary
cell_desc the cell name or number, if necessary
Example 1
stat_mode rf_losses_tch on cell_name=mid34a
Where: Is:
rf_losses_tch statistic
on enable mode
cell_name=mid34a cell name
System response
COMMAND ACCEPTED
Example 2
stat_mode HO_BLKD_BSP_OVERLOAD on cell 0 0 1 0 1 1 1
Where: Is:
HO_BLKD_BSP_OVERLOAD statistic
on enable mode
cell 0 0 1 0 1 1 1 cell description
System response
COMMAND ACCEPTED
68P02901W56-T 2-3
Jan 2010
Enabling a statistic Chapter 2: Statistical operations
Example 3
stat_mode MA_CMD_TO_MS_BLKD on cell 0 0 1 0 1 1 1
Where: Is:
MA_CMD_TO_MS_BLKD statistic
on enable mode
System response
COMMAND ACCEPTED
Example 4
stat_mode PROCESSOR_SAFE_OVERLOAD on
Where: Is:
PROCESSOR_SAFE_OVERLOAD statistic
on enable mode
System response
COMMAND ACCEPTED
Example 5
stat_mode MTP_SL_ERROR_RATE_HSP on
Where: Is:
MTP_SL_ERROR_RATE_HSP statistic
on enable mode
System response
COMMAND ACCEPTED
2-4 68P02901W56-T
Jan 2010
NOTE
This statistic cannot be enabled if the Increased Network Capacity feature is not
implemented.
Example 6
stat_mode UL_RADIO_BLKS_8PSK_3_TS on cell 0 0 1 0 1 1 1
Where: Is:
UL_RADIO_BLKS_8PSK_3_TS statistic
on enable mode
System response
COMMAND ACCEPTED
Example 7
stat_mode UL_RADIO_BLKS_GMSK_4_TS on cell 0 0 1 0 1 1 1
Where: Is:
UL_RADIO_BLKS_GMSK_4_TS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
The system rejects enabling of the statistic, when EDA or EGPRS feature is restricted.
68P02901W56-T 2-5
Jan 2010
Example 8
stat_mode UL_TBF_TIME_GMSK_3_TS on cell 0 0 1 0 1 1 1
Where: Is:
UL_TBF_TIME_GMSK_3_TS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
The system rejects enabling of the statistic, when EDA or EGPRS feature is restricted.
Example 9
stat_mode PSI_TRAU_FILL_FRAME_TX on
Where: Is:
PSI_TRAU_FILL_FRAME_TX statistic
on enable mode
System response
COMMAND ACCEPTED
Example 10
stat_mode RSL_LINK_INS on
Where: Is:
RSL_LINK_INS statistic
on enable mode
System response
COMMAND ACCEPTED
2-6 68P02901W56-T
Jan 2010
Example 11
stat_mode RSL_RX_OCTETS on
Where: Is:
RSL_RX_OCTETS statistic
on enable mode
System response
COMMAND ACCEPTED
Example 12
stat_mode RSL_TX_OCTETS on
Where: Is:
RSL_TX_OCTETS statistic
on enable mode
System response
COMMAND ACCEPTED
Example 13
stat_mode RF_LOSSES_SD on 1 cell_number=0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_SD statistic
on enable mode
1 location
cell_number=0 0 1 0 1 1 1 cell description
System response
COMMAND ACCEPTED
68P02901W56-T 2-7
Jan 2010
Example 14
stat_mode RF_LOSSES_TCH_HR on 1 cell_number=0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_TCH_HR statistic
on enable mode
1 location
System response
COMMAND ACCEPTED
Example 15
stat_mode RF_LOSSES_TCH on 1 cell_number=0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_TCH statistic
on enable mode
1 location
System response
COMMAND ACCEPTED
2-8 68P02901W56-T
Jan 2010
Example 16
stat_mode PFC_ADMISSION_TRAFFIC_CLASS on cell 0 0 1 0 1 1 1
Where: Is:
PFC_ADMISSION_TRAFFIC_CLASS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
This statistic cannot be enabled if the QoS feature is not implemented.
Example 17
stat_mode PFC_REJECTION_TRAFFIC_CLASS on cell 0 0 1 0 1 1 1
Where: Is:
PFC_REJECTION_TRAFFIC_CLASS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
68P02901W56-T 2-9
Jan 2010
Example 18
stat_mode PFC_PREEMPTIONS_TRAFFIC_CLASS on cell 0 0 1 0 1 1 1
Where: Is:
PFC_PREEMPTIONS_TRAFFIC_CLASS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
Example 19
stat_mode PFC_TRANSFER_DELAY on cell 0 0 1 0 1 1 1
Where: Is:
PFC_TRANSFER_DELAY statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
This statistic cannot be enabled if the QoS Phase 2 feature is not implemented.
2-10 68P02901W56-T
Jan 2010
Example 20
stat_mode UL_RLC_STALLED_BLKS on cell 0 0 1 0 1 1 1
Where: Is:
UL_RLC_STALLED_BLKS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
The system rejects enabling of the statistic, when GPRS feature is restricted.
Example 21
stat_mode EXT_UL_EXITS on cell 0 0 1 0 1 1 1
Where: Is:
EXT_UL_EXITS statistic
on enable mode
System response
COMMAND ACCEPTED
NOTE
The system rejects enabling of the statistic, when the Extended UL and GPRS feature
is restricted.
68P02901W56-T 2-11
Jan 2010
Example 22
stat_mode IA_IAR_MSGS_PER_AGCH on 1 cell_number=0 0 1 0 1 1 1
Where: Is:
IA_IAR_MSGS_PER_AGCH statistic
on enable mode
1 location
System response
Command accepted
Example 23
stat_mode CS_PAGING_MSGS_FROM_MSC on 1 cell_number=0 0 1 0 1 1 1
Where: Is:
CS_PAGING_MSGS_FROM_MSC statistic
on enable mode
1 location
System response
Command Accepted
Example 24
This example enables the CELL statistic UL_LLC_DATA_VOLUME when the GPRS features
are unrestricted.
stat_mode UL_LLC_DATA_VOLUME on cell 0 0 1 0 1 1 1
Where: Is:
UL_LLC_DATA_VOLUME statistic
on mode
0010111 cell description
System response
COMMAND ACCEPTED
2-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Disabling a statistic
Disabling a statistic
A statistic is disabled by entering the stat_mode command using the following syntax:
stat_mode <meas_type> off [<location>] [<cell_desc>]
Where: Is:
meas_type the statistic being disabled
off disable mode
location the location of the statistic being disabled, if necessary
Example 1
stat_mode mtp_link_ins off
Where: Is:
mtp_link_ins statistic
off disable mode
System response
COMMAND ACCEPTED
Example 2
stat_mode MTP_SL_ERROR_RATE_HSP off
Where: Is:
off disable mode
System response
COMMAND ACCEPTED
68P02901W56-T 2-13
Jan 2010
Disabling a statistic Chapter 2: Statistical operations
Example 3
stat_mode IA_IAR_MSGS_PER_AGCH off 1 cell_number=0 0 1 0 1 1 1
Where: Is:
off disable mode
1 location
System Response
Command Accepted
2-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying enabled statistics
Displaying enabled statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
A listing of the currently enabled statistics can be displayed using the disp_enable_stat
command. Refer to the manual Technical Description: BSS Command Reference (68P02901W23)
for a detailed description of the disp_enable_stat command.
Specific listings can be generated based on the arguments entered with the disp_enable_stat
command, including:
• No argument - A listing of all currently enabled statistics is displayed.
• BSS - A listing of all the currently enabled BSS-wide statistics is displayed.
• cell_desc - A listing of all the currently enabled statistics for the specified cell is displayed.
• location - A listing of all the currently enabled statistics for the specified site is displayed.
• meas_type - A listing of all the currently enabled statistics for the specified measurement
type is displayed.
Displaying all enabled statistics
A listing of all the enabled statistics can be displayed by entering the disp_enable_stat
command using the following syntax:
disp_enable_stat
System response
Enabled Non-Cell Statistics

ma_req_from_msc_fail
page_req_from_msc_fail
ho_req_msc_proto
mtp_sl_fail
mtp_sl_fibr
mtp_sl_ack
mtp_sl_error_rate
mtp_sl_congestion
mtp_sl_alignment
mtp_su_error
mtp_neg_acks
mtp_changeover
68P02901W56-T 2-15
Jan 2010
Displaying all enabled statistics Chapter 2: Statistical operations
mtp_changeback
mtp_restoration
mtp_start_rpo
mtp_stop_rpo
mtp_mgt_inhibit
mtp_mgt_uninhibit
mtp_re_tx
mtp_sif_sio_rx
mtp_msu_tx
mtp_msu_rx
sl_congestion
sl_stop_congestion
msu_discarded
congestion_lost_msu
sif_sio_rx_opc
sif_sio_tx_dpc
sif_sio_type
routing_syntax
routing_unknown
sccp_msgs
sccp_msgs_tx
sccp_msgs_rx
invalid_frames_rx
i_frames_rx
i_frames_tx
sabm_tx frmr
n2_expiry
mtp_link_ins
mtp_unavailable
mtp_local_mgt
mtp_remote_mgt
mtp_linkfail
mtp_remote_proc
mtp_local_busy
mtp_congestion
cpu_usage
. . . .
Enabled Statistics for Cell 001 01 03e7h 0028h
egprs_avail_pdtch
rf_losses_tch
rf_losses_sd
intra_cell_ho
2-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying all enabled statistics
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
. . . .
tch_delay
intf_on_idle
busy_tch
busy_sdcch
ber
. . . .
NOTE
The remaining cell statistics follow until all the enabled statistics have been displayed.
Example 1
This example shows the interaction required to display the status of the RSL_LINK_INS
statistic.
disp_enable_stat RSL_LINK_INS
Where: Is:
System response
Statistics RSL_LINK_INS is enabled.
Example 2
This example shows the interaction required to display the status of the RSL_RX_OCTETS
statistic.
disp_enable_stat RSL_RX_OCTETS
Where: Is:
68P02901W56-T 2-17
Jan 2010
System response
Statistics RSL_RX_OCTETS is enabled.
Example 3
This example shows the interaction required to display the status of the RSL_TX_OCTETS
statistic.
disp_enable_stat RSL_TX_OCTETS
Where: Is:
System response
Statistics RSL_TX_OCTETS is enabled.
Example 4
This example shows the interaction required to display the enabled statistics under BSS.
disp_enable_stat BSS
System response
. . . .
RSL_RX_OCTETS
RSL_TX_OCTETS
RSL_LINK_INS
(Existing statistics output unchanged)
Example 5
This example shows the interaction required to display the enabled statistics under
cell 0 0 1 0 1 1 1
Where: Is:
2-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying all enabled statistics
System response
Enabled Statistics for Cell 001 01 0001h 0001h
-----------------------------------------------
ACCESS_PER_PCH
. . . .
PFC_TRANSFER_DELAY
PFC_GBR_DL
PFC_GBR_UL
(Existing statistics output unchanged)
Example 6
This command displays the enabled statistics by CELL, location, or all statistics in the system.
disp_enable_stat 1
Where: Is:
1 site location
System Response
Enabled Statistics for Cell 0 0 1 0 1 1 2

rf_losses_tch
rf_losses_sd
rf_losses_tch_hr
intra_cell_ho
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
IA_IAR_MSGS_PER_AGCH
cs_paging_msgs_from_msc
68P02901W56-T 2-19
Jan 2010
Example 7
This example displays all the enabled statistics for all cells at site 1.
disp_enable_stat 1
Where: Is:
1 site location
System response
Enabled statistics for Cell 0 0 1 01 0001h 0001h

...
UL_LLC_DATA_VOLUME
DL_LLC_DATA_VOLUME
UL_LLC_TRANS_TIME
DL_LLC_TRANS_TIME
...
2-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying statistic values
Displaying statistic values

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The current value of an individual statistic for a specific interval can be displayed using the
disp_stats command. Displayed information can represent incremental (peg count) or duration
values, depending on the specified statistic. Refer to the manual Technical Description: BSS
Command Reference (68P02901W23) for a detailed description of the disp_stats command.
NOTE
The value of a statistic for the current interval cannot be displayed. The
disp_interval command can be used to display completed intervals.
When counter array statistics are displayed, the values for the individual bins are displayed. A
total value of all the bins can also be displayed for some counter array statistics. Refer to the
descriptions of individual counter array statistics.
The disp_stats command is entered using one of the following syntax:
disp_stats <interval> <meas_type> <cell_desc>

disp_stats <interval> <meas_type> <board_desc>
Where: Is:
interval a completed statistical interval
meas_type the name of the statistic to be displayed
board_desc the board_id, if necessary
When using the disp_stats command to display a per link statistic, the generated output
reports all the links for a specified board.
68P02901W56-T 2-21
Jan 2010
Description Chapter 2: Statistical operations
Example 1
This example shows the interaction required to display the value of a counter array statistic
which includes a total value.
disp_stats 5 out_ho_cause_atmpt cell_number=5 4 3 2 1 61986 34944
Where: Is:
5 interval
out_ho_cause_atmpt statistic
5 4 3 2 1 61986 34944 cell_number
System response
SITE: 0 CELL #: LAC = f222h CI = 8880h
MEAS_TYPE: OUT_HO_CAUSE_ATMPT
Total: 110
Uplink Quality
10
Uplink Level
20
Downlink Quality
10
Downlink Level
10
Distance
10
Uplink Interference
10
Downlink Interference
10
Power Budget
10
Congestion
10
Adjacent Channel Interference : 10
2-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Description
Example 2
This example shows the interaction required to display the properties for the
EXT_UL_USF_USAGE statistic.
disp_stats 1 HO_BLKD_BSP_OVERLOAD cell 0 0 1 0 1 1 1
Where: Is:
EXT_UL_USF_USAGE a counter array statistic
System response
STATISTIC: EXT_UL_USF_USAGE SITE: 1

TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN# Cause
0 Uplink Dummy Control Blocks.
1 Non-dummy Control Blocks.
2 No activity (ext_utbf_nodata = 1).
ALARM ALARM ALARM
CELL # MODE BIN SEVERITY THRESHOLD
------------------------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) ENABLED N/A N/A N/A
Example 3
This example shows the interaction required to display the value of HO_BLKD_BSP_OVERLOAD
statistic.
disp_stats 1 HO_BLKD_BSP_OVERLOAD cell 0 0 1 0 1 1 1
Where: Is:
1 interval
HO_BLKD_BSP_OVERLOAD statistic
System response
SITE: 1 CELL #: LAC-0001h CI-0001h

MEAS TYPE: HO_BLKD_BSP_OVERLOAD
Counter: 100
BIN# Cause Sub-Counter Value
0 NO channel 0
1 BSP overload 0
68P02901W56-T 2-23
Jan 2010
Example 4
This example shows the interaction required to display the value of MA_CMD_TO_MS_BLKD
statistic.
disp_stats 1 MA_CMD_TO_MS_BLKD cell 0 0 1 0 1 1 1
Where: Is:
1 interval
System response

MEAS TYPE: MA_CMD_TO_MS_BLKD
Total Counter: 0
0 NO channel 0
1 BSP overload 0
Example 5
This example shows the interaction required to display the value of

PROCESSOR_SAFE_OVERLOAD statistic.
disp_stats 0 PROCESSOR_SAFE_OVERLOAD
Where: Is:
0 interval
PROCESSOR_SAFE_OVERLOAD statistic
System response
SITE: 0 GPROC Board #: 277 (0x0115)

MEAS TYPE: PROCESSOR_SAFE_OVERLOAD
Duration Value (ms): 0 Duration Mean (ms): 0
Duration MAX. (ms): 0 Duration Min. (ms): 0
2-24 68P02901W56-T
Jan 2010
Example 6

PROCESSOR_CRITICAL_OVERLOAD statistic.
disp_stats 0 PROCESSOR_CRITICAL_OVERLOAD
Where: Is:
0 interval
PROCESSOR_CRITICAL_OVERLOAD statistic
System response
MEAS TYPE: PROCESSOR_CRITICAL_OVERLOAD
Example 7

MTP_SL_ERROR_RATE_HSP statistic.
disp_stats 6 mtp_sl_error_rate_hsp board_id 0113h
Where: Is:
6 interval
mtp_sl_error_rate_hsp statistic
board_id 0113h board description
System response
SITE: 0 MTL Link #: 1
MEAS TYPE: MTP_SL_ERROR_RATE_HSP
Counter: 0
68P02901W56-T 2-25
Jan 2010
Example 8
This example shows the interaction required to display the value of UL_TBF_TIME_GMSK_3_TS
statistic.
disp_stats 1 UL_TBF_TIME_GMSK_3_TS cell 0 0 1 0 1 1 1
Where: Is:
1 interval
UL_TBF_TIME_GMSK_3_TS statistic
System Response

MEAS TYPE: UL_TBF_TIME_GMSK_3_TS
Counter: 100
Example 9
This example shows the interaction required to display the value of UL_RA-
DIO_BLKS_GMSK_3_TS statistic.
disp_stats 1 UL_RADIO_BLKS_GMSK_3_TS cell 0 0 1 0 1 1 1
Where: Is:
1 interval
UL_RADIO_BLKS_GMSK_3_TS statistic
System Response

MEAS TYPE: UL_RADIO_BLKS_GMSK_3_TS
Total Counter: 0
0 CS-1 0
1 CS-2 0
2 CS-3 0
3 CS-4 0
4 MCS-1 0
5 MCS-2 0
6 MCS-3 0
7 MCS-4 0
2-26 68P02901W56-T
Jan 2010
Example 10
This example shows the interaction required to display the value of UL_RA-
DIO_BLKS_8PSK_4_TS statistic.
disp_stats 1 UL_RADIO_BLKS_8PSK_4_TS cell 0 0 1 0 1 1 1
Where: Is:
1 interval
UL_RADIO_BLKS_8PSK_4_TS statistic
System Response

MEAS TYPE: UL_RADIO_BLKS_8PSK_4_TS
Total Counter: 0
0 CS-1 0
1 CS-2 0
2 CS-3 0
3 CS-4 0
4 MCS-1 0
5 MCS-2 0
6 MCS-3 0
7 MCS-4 0
8 MCS-5 0
9 MCS-6 0
10 MCS-7 0
11 MCS-8 0
12 MCS-9 0
Example 11
This example shows the interaction required to display the value of PSI_TRAU_FILL_FRAME_TX
statistic.
disp_stats 0 PSI_TRAU_FILL_FRAME_TX
Where: Is:
0 interval
PSI_TRAU_FILL_FRAME_TX statistic
68P02901W56-T 2-27
Jan 2010
System response
SITE: 0 PSI Board #: 0107h
ETH Port #: 0
MEAS TYPE: PSI_TRAU_FILL_FRAME_TX
Counter: 145
Example 12
This example shows the interaction required to display the value of ETH_RX_ERROR statistic.
disp_stats 0 ETH_RX_ERROR
Where: Is:
0 interval
ETH_RX_ERROR statistic
System response
SITE: PCU DPROC Board #: 1105h
ETH Port #: 0
MEAS TYPE: ETH_RX_ERROR
Counter: 145
Example 13
This example shows the interaction required to display the value of RSL_LINK_INS statistic.
disp_stats 0 RSL_LINK_INS board_id=0113h
Where: Is:
0 interval
board_id=0113h board description
System response
SITE: 0 RSL Link #: 1
MEAS TYPE: RSL_LINK_INS
2-28 68P02901W56-T
Jan 2010
Example 14
This example shows the interaction required to display the value of RSL_RX_OCTETS statistic.
disp_stats 0 RSL_RX_OCTETS board_id=0118h
Where: Is:
0 interval
System response
MEAS TYPE: RSL_RX_OCTETS
Counter: 100
Example 15
This example shows the interaction required to display the value of RSL_TX_OCTETS statistic.
disp_stats 0 RSL_TX_OCTETS board_id=0118h
Where: Is:
0 interval
System response
MEAS TYPE: RSL_TX_OCTETS
Counter: 100
68P02901W56-T 2-29
Jan 2010
Example 16
This example shows the interaction required to display the value of RF_LOSSES_SD statistic.
disp_stats 1 RF_LOSSES_SD cell_number= 0 0 1 0 1 1 1
Where: Is:
1 interval
cell_number= 0 0 1 0 1 1 1 cell description
System response
RTF ID: 0 0 TIMESLOT: 0
MEAS TYPE: RF_LOSSES_SD
Total counter: 5
0 RX quality in uplink direction 1
1 RX quality in downlink direction 1
2 RX level in uplink direction 1
3 RX level in downlink direction 1
4 Others 1
Example 17
This example shows the interaction required to display the value of RF_LOSSES_TCH statistic.
disp_stats 1 RF_LOSSES_TCH cell_number= 0 0 1 0 1 1 1
Where: Is:
1 interval
System response
2-30 68P02901W56-T
Jan 2010

MEAS TYPE: RF_LOSSES_TCH
Total counter: 6
4 Timing Advance 0
5 Sharp decrease of signal level 1
6 Others 1
. . . .

Total counter: 6
4 Timing Advance 0
6 Others 1
. . . .

Total counter: 6
4 Timing Advance 0
6 Others 1
. . . .
68P02901W56-T 2-31
Jan 2010
Example 18
This example shows the interaction required to display the value of RF_LOSSES_TCH_HR
statistic.
disp_stats 1 RF_LOSSES_TCH_HR cell_number= 0 0 1 0 1 1 1
Where: Is:
1 interval
RF_LOSSES_TCH_HR statistic
System response
MEAS TYPE: RF_LOSSES_TCH_HR
Total counter: 6
4 Timing Advance 0
6 Others 1
. . . .

Total counter: 6
4 Timing Advance 0
6 Others 1
2-32 68P02901W56-T
Jan 2010

Total counter: 6
4 Timing Advance 0
6 Others 1
Example 19

PFC_PREEMPTIONS_TRAFFIC_CLASS statistic.
disp_stats 0 PFC_PREEMPTIONS_TRAFFIC_CLASS cell 0 0 1 0 1 1 1
Where: Is:
0 interval
PFC_PREEMPTIONS_TRAFFIC_CLASS statistic
System response
SITE: 1 CELL #: LAC=0001h CI=0001h
MEAS TYPE: PFC_PREEMPTIONS_TRAFFIC_CLASS
Total Count: 6
Preemption of Streaming: 1
Preemption of Interactive THP1: 1
Preemption of Background: 1
Preemption of Best Effort and PFC Unaware: 1
68P02901W56-T 2-33
Jan 2010
Example 20
This example shows the interaction required to display the value of PFC_PREEMPTIONS
statistic.
disp_stats 0 PFC_PREEMPTIONS cell 0 0 1 0 1 1 1
Where: Is:
0 interval
PFC_PREEMPTIONS statistic
System response
SITE: 1 CELL #: LAC=0001h CI=0001h
MEAS TYPE: PFC_PREEMPTIONS
Total Count: 14
Preemptions of PFCs with priority level 1 : 1
2-34 68P02901W56-T
Jan 2010
Example 21
This example shows the interaction required to display the value of EXT_UL_EXITS statistic.
disp_stats 1 EXT_UL_EXITS cell 0 0 1 0 1 1 1
Where: Is:
1 interval
EXT_UL_EXITS statistic
System response

MEAS TYPE: EXT_UL_EXITS
Total Count: 0
Arrival of new RLC data block: 0
Extended uplink duration expires: 0
Congestion in the cell: 0
Example 22
This example shows the interaction required to display the value of EXT_UL_USF_USAGE
statistic.
Where: Is:
1 interval
EXT_UL_USF_USAGE statistic

MEAS TYPE: EXT_UL_USF_USAGE
Total Count: 0
Uplink Dummy Control Blocks: 0
Non-dummy Control Blocks: 0
No activity (ext_utbf_nodata= 1): 0
68P02901W56-T 2-35
Jan 2010
Example 23
This example shows the interaction required to display the value of IA_IAR_MSGS_PER_AGCH
statistic.
disp_stats 1 IA_IAR_MSGS_PER_AGCH cell_number= 0 0 1 0 1 1 1
Where: Is:
1 interval
System response

MEAS TYPE: IA_IAR_MSGS_PER_AGCH
Total counter: 8
0 IA CS messages sent over CCCH 1
1 IA PS messages sent over CCCH 1
2 IAR CS messages sent over CCCH 1
3 IAR PS messages sent over CCCH 1
4 IA CS messages discarded 1
5 IA PS messages discarded 1
6 IAR CS messages discarded 1
7 IAR PS messages discarded 1
2-36 68P02901W56-T
Jan 2010
Example 24
This example shows the interaction required to display the value of CS_PAGING_
MSGS_FROM_MSC statistic.
disp_stats 1 CS_PAGING_MSGS_FROM_MSC cell_number= 0 0 1 0 1 1 1
Where: Is:
1 interval
CS_PAGING_MSGS_FROM_MSC statistic
System response

MEAS TYPE: CS_PAGING_MSGS_FROM_MSC
Total counter: 7
0 received paging messages on SCCP_Pre MTL-LCF 1
1 received paging messages on SCCP_Pre RSL-LCF 1
2 received paging messages on RRSM 1
3 received paging messages on RSS Abis 1
4 received paging messages on RSS L1 1
5 discarded paging messages on SCCP_Pre RSL-LCF due to Cell OOS 1
6 discarded paging messages exceeds max_pagenum_per_sec 1
68P02901W56-T 2-37
Jan 2010
Setting the statistic interval Chapter 2: Statistical operations
Setting the statistic interval

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The stat_interval is a non statistical parameter that is used to specify the interval. Refer to
the manual Technical Description: BSS Command Reference (68P02901W23) for a detailed
description of the stat_interval parameter.
In normal operations, the OMC-R calculates key statistics and health indicators based on the
default interval of 30 minutes. If the interval is changed to 60 minutes, it must be reset to
30 minutes for normal operations.
NOTE
The OMC-R can calculate key statistics at 60-minute intervals, if it is configured to
handle 60 minute statistic files.
The stat_interval is specified by entering the chg_element command using the following syntax:
chg_element stat_interval <30 or 60> <location>
Where: Is:
stat_interval parameter name
30 or 60 valid values for the parameter, in minutes
location a BSS-wide parameter and 0 is the only valid value for this argument
Example
This example shows the interaction required to change the statistical interval to 60 minutes.
chg_element stat_interval 60 0
Where: Is:
60 60 minutes
0 location
System response
COMMAND ACCEPTED
2-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying the statistic interval
Displaying the statistic interval

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The stat_interval is a non-statistical parameter that is used to specify the interval. The current
interval can be displayed using the disp_element command using the following syntax:
disp_element stat_interval <location>
Where: Is:
location a BSS-wide parameter and 0 is the only valid value for this argument.
Example
This example shows the interaction required to display the statistical interval.
chg_element stat_interval 0
Where: Is:
0 location
System response
stat_interval = 30
68P02901W56-T 2-39
Jan 2010
Displaying the statistic interval start times Chapter 2: Statistical operations
Displaying the statistic interval start times

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The starting times of the statistic intervals can be displayed by entering the disp_interval
command. Refer to the manual Technical Description: BSS Command Reference (68P02901W23)
for a detailed description of the disp_interval command. No arguments are required with
the command.
On startup, the first start time (interval 0) corresponds to current time of the system clock. The
second start time (interval 1) automatically becomes synchronized to the next hour (:00) or half
hour (:30), depending upon the current statistic interval.
Example
This example shows the interaction required to display the starting times of the statistical
intervals where the statistic interval is 30 and the disp_interval command was entered at 1230.
disp_interval
System response
Interval Start Time (HH:MM:SS)

-------- --------------------
0 09:08:48
1 09:30:00
2 10:00:00
3 10:30:00
4 11:00:00
5 11:30:00
6 12:00:00
7 12:30:00
8 None
9 None
10 None
11 None
The displayed starting times depend on the time of the day when the disp_interval command
is entered. When the command is entered, the current set of 12 start times is presented. If the
command is entered after interval 11 would be completed, the listing displays the next set
of 12 interval start times.
2-40 68P02901W56-T
Jan 2010
Example
If the disp_interval command is entered at 1501, the following output is displayed.
System response
Interval Start Time (HH:MM:SS)

-------- --------------------
0 15:00:00
1 09:30:00
2 10:00:00
3 10:30:00
4 11:00:00
5 11:30:00
6 12:00:00
7 12:30:00
8 13:00:00
9 13:30:00
10 14:00:00
11 14:30:00
68P02901W56-T 2-41
Jan 2010
Setting statistic properties Chapter 2: Statistical operations
Setting statistic properties

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The properties for statistics (except for the statistic interval) can be changed using the
chg_stat_prop command. Refer to the manual Technical Description: BSS Command Reference
(68P02901W23) for a detailed description of the chg_stat_prop command.
The specific properties that can be changed are dependent on the statistic type.
• The alarm threshold can be changed for counter, counter array, and gauge statistics, if
an alarm is associated with the statistic.
• Bin ranges can be changed for normal and weighted statistics.
• Properties cannot be changed for total time (duration) statistics.
Setting a threshold
Some counter and gauge statistics can be associated with alarms. Threshold values can be
specified for these statistics. An alarm is sent to the Operations and Maintenance Center -
Radio (OMC-R) when the threshold is reached.
A threshold is specified by entering the chg_stat_prop command using the following syntax:
chg_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: Is:
meas_type a counter or gauge statistic
location the location of the statistic whose threshold is being set, if necessary
NOTE
• The threshold cannot be set for non-alarming statistics.

• The system rejects the setting of statistic properties when the corresponding
feature is restricted.
Example 1
This example shows the interaction required to change the alarm threshold for the rf_losses_tch
statistic for cell_name=mn14b at site 1.
chg_stat_prop rf_losses_tch cell_name=mn14b
2-42 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Setting a threshold
Where: Is:
rf_losses_tch statistic
cell_name=mn14b cell name
System response
Enter the Alarm threshold for counter array total value: 500
COMMAND ACCEPTED
Example 2
This example shows the interaction required to change the alarm threshold for the
MA_CMD_TO_MS_BLKD statistic at site 1.
chg_stat_prop MA_CMD_TO_MS_BLKD cell 0 0 1 0 1 1 1
Where: Is:
System response
Enter the threshold for bin 0: 100
Enter the threshold for bin 1: 200
COMMAND ACCEPTED
Example 3
MTP_SL_ERROR_RATE_HSP statistic at site 1.
chg_stat_prop MTP_SL_ERROR_RATE_HSP
Where: Is:
System response
Enter the alarm threshold: 50
COMMAND ACCEPTED
68P02901W56-T 2-43
Jan 2010
Setting a threshold Chapter 2: Statistical operations
Example 4
RF_LOSSES_SD statistic.
chg_stat_prop RF_LOSSES_SD cell_number= 0 0 1 0 1 1 1
Where: Is:
System response
COMMAND ACCEPTED
Example 5
RF_LOSSES_TCH statistic.
chg_stat_prop RF_LOSSES_TCH cell_number= 0 0 1 0 1 1 1
Where: Is:
System response
COMMAND ACCEPTED
Example 6
This example changes the properties of the cell statistic UL_LLC_TRANS_TIME when GPRS
feature is unrestricted/restricted.
chg_stat_prop UL_LLC_TRANS_TIME cell 0 0 1 0 1 1 1
Where: Is:
UL_LLC_TRANS_TIME statistic
0010111 cell description
System Response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.
2-44 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Counter statistics
Counter statistics
Counter statistics that can be assigned a threshold are presented in Table 2-1.
Table 2-1 Counter statistics
Statistical name Alarm severity Valid values Basis

min: 1
ALLOC_SDCCH_FAIL Major cell
MAX: 2147483647
min: 1
ALLOC_TCH_FAIL Major cell
MAX: 2147483647
min: 1
ATER_PREEMPT_FAIL Warning AXCDR
MAX: 2147483647
min: 1
BAD_HO_REFNUM_MS Warning cell
MAX: 2147483647
min: 1
CHAN_REQ_MS_BLK Minor cell
MAX: 2147483647
min: 1
CIPHER_MODE_FAIL Minor cell
MAX: 2147483647
min: 1
CLASSMK_UPDATE_FAIL Minor cell
MAX: 2147483647
min: 1
CONGESTION_LOST_MSU Warning SS7 link
MAX: 2147483647
min: 1 X.25 link or
FRMR Warning
MAX: 2147483647 LAP-D link
min: 1
HO_REQ_MSC_FAIL Warning cell
MAX: 2147483647
min: 1
HO_REQ_MSC_PROTO Warning BSS
MAX: 2147483647
min: 1 X.25 link or
INVALID_FRAMES_RX Warning
min: 1
MA_CMD_TO_MS_BLKD Minor cell
MAX: 2147483647
min: 1
MA_FAIL_FROM_MS Warning cell
MAX: 2147483647
min: 1
MA_REQ_FROM_MSC_FAIL Warning BSS
MAX: 2147483647
min: 1
MSU_DISCARDED Warning SS7 link
MAX: 2147483647
min: 1
MTP_NEG_ACKS Warning SS7 link
MAX: 2147483647
min: 1
MTP_RE_TX Warning SS7 link
MAX: 2147483647
min: 1
MTP_SL_ACK Major SS7 link
MAX: 2147483647
Continued
68P02901W56-T 2-45
Jan 2010
Counter statistics Chapter 2: Statistical operations
Table 2-1 Counter statistics (Continued)

Statistical name Alarm severity Valid values Basis
min: 1
MTP_SL_ALIGNMENT Minor SS7 link
MAX: 2147483647
min: 1
MTP_SL_CONGESTION Major SS7 link
MAX: 2147483647
min: 1
MTP_SL_ERROR_RATE Major SS7 link
MAX: 2147483647
MTP_SL_ERROR_ min: 1
Major SS7 link
RATE_HSP MAX: 2147483647
min: 1
MTP_SL_FAIL Major SS7 link
MAX: 2147483647
min: 1
MTP_SL_FIBR Major SS7 link
MAX: 2147483647
min: 1
MTP_START_RPO Warning SS7 link
MAX: 2147483647
min: 1
MTP_SU_ERROR Warning SS7 link
MAX: 2147483647
min: 1 X.25 link or
N2_EXPIRY Warning
min: 1
PAGE_REQ_FROM_MSC_FAIL Minor BSS
MAX: 2147483647
min: 1
PCH_Q_PAGE_DISCARD Minor cell
MAX: 2147483647
min: 1
RF_LOSSES_SD Major cell
MAX: 65535
min: 1
RF_LOSSES_TCH Major timeslot
MAX: 65535
min: 1
ROUTING_SYNTAX Warning BSS
MAX: 2147483647
min: 1
ROUTING_UNKNOWN Warning BSS
MAX: 2147483647
RSL_LCF_ min: 1
Warning BSC GPROC
CONGESTION MAX: 2147483647
min: 1
SL_CONGESTION Warning SS7 link
MAX: 2147483647
TCH_PREEMPT_FAIL_ min: 1
Warning cell
NO_CAND MAX: 2147483647
The maximum value that can be assigned to a threshold (2147483647) is set as the default
value upon initialization of the CM database.
The default for the maximum value in the Valid Values column is 2147483647.
2-46 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Setting bin ranges
Setting bin ranges
Distribution statistics include ten bins, numbered 0 to 9. Each bin represents a range of
values. When events are reported, the bin corresponding to the reported value is incremented.
The range of values for the individual bin in a distribution statistic can be specified with the
chg_stat_prop command using the following syntax:
chg_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: Is:
meas_type a normal or weighted distribution statistic
location the location of the statistic whose bin range is being set, if necessary
NOTE
The bin ranges for the BER statistic cannot be modified.
The range of values, to be measured by the statistic, must be considered when assigning
values for the individual bins in the distribution. For example, if the possible range of values
to be measured is from 0 to 100, then the minimum value for bin 0 is 0, and the maximum
value for bin 9 is 100.
Ensure that the gaps in the range of values covered are avoided when assigning the minimum
and maximum values for the individual bins. For example, if bin 0 covers values from 0 to 10
and bin 1 covers values from 12 to 15, a gap exists for the value 11. This can cause any report of
a value equal to 11 to be ignored.
Bin minimum and maximum can be set to the same value for the same bin. This allows a specific
value to be reported within the overall distribution. For example, if the minimum and maximum
values for a bin are both specified to be 10, the bin is pegged each time a value of 10 is reported.
Default ranges
Distribution statistics have default ranges for bins.
68P02901W56-T 2-47
Jan 2010
Setting bin ranges Chapter 2: Statistical operations
Example
This example shows the interaction required to change the minimum and maximum values for
two bins of the BUSY_TCH statistic for all cells at site 1.
chg_stat_prop busy_tch 1 all
Where: Is:
busy_tch meas_type
1 location
all all cells at the specified site
System response
Enter the bin number(s): 0,1
Enter the min value for bin 0: 0
Enter the MAX value for bin 0: 5
Enter the min value for bin 1: <return>
Enter the MAX value for bin 1: 7
COMMAND ACCEPTED
2-48 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying statistic properties
Displaying statistic properties

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The properties of individual statistics can be displayed using the disp_stat_prop command.
The information and presentation format are dependent upon the statistic type, including:
• Alarm severity and threshold values are displayed for counter and gauge statistics.
• Bin ranges are displayed for normal and weighted statistics.
• The cause is displayed for the counter array statistics.
• Only the mode and type are displayed for the duration statistics.
Displaying a counter statistic
Counter statistic properties are displayed by entering the disp_stat_prop command using
the following syntax:
disp_stat_prop <meas_type> <location> [<cell_desc>]
Where: Is:
meas_type a counter statistic
location the location of the statistic whose properties are being displayed, if required
cell_desc the cell name or number, if required
Example 1
This example shows the interaction required to display the properties for the TOTAL_CALLS
statistic for all cells at site 1.
disp_stat_prop total_calls 1 all
Where: Is:
total_calls meas_type
1 location
all all cells at the specified location
68P02901W56-T 2-49
Jan 2010
Displaying a counter statistic Chapter 2: Statistical operations
System response
STATISTIC: TOTAL_CALLS SITE: 1
TYPE: PER CELL OBJECT: COUNTER
ALARM ALARM
CELL # MODE SEVERITY THRESHOLD
--------------------------------------------------------------------
543 21 61698 (f102h)34776 (87d8h) ENABLED NO ALARM N/A
543 21 61698 (f102h)34778 (87dah) ENABLED NO ALARM N/A
543 21 61698 (f102h)34779 (87dbh) ENABLED NO ALARM N/A
543 21 61698 (f102h)34780 (87dch) ENABLED NO ALARM N/A
Example 2
HO_BLKD_BSP_OVERLOAD statistic at site 1.
disp_stat_prop HO_BLKD_BSP_OVERLOAD cell 0 0 1 0 1 1 1
Where: Is:
HO_BLKD_BSP_OVERLOAD a counter statistic
System response
STATISTIC: HO_BLKD_BSP_OVERLOAD SITE: 1
ALARM ALARM
----------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A
Example 3
MTP_SL_ERROR_RATE_HSP statistic at site 0.
disp_stat_prop MTP_SL_ERROR_RATE_HSP
Where: Is:
MTP_SL_ERROR_RATE_HSP a counter statistic
2-50 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying a counter statistic
System response
STATISTIC: MTP_SL_ERROR_RATE_HSP SITE: 0
TYPE: PER Link OBJECT: COUNTER
ALARM ALARM
----------------------------------------------------------------
N/A ENABLED Major 50
Example 4
UL_TBF_TIME_8PSK_3_TS statistic at site 1.
disp_stat_prop UL_TBF_TIME_8PSK_3_TS cell 0 0 1 0 1 1 1
Where: Is:
UL_TBF_TIME_8PSK_3_TS a counter statistic
System Response
STATISTIC: UL_TBF_TIME_8PSK_3_TS SITE: 1

TYPE: PER Cell OBJECT: COUNTER
ALARM ALARM
----------------------------------------------------------------
Example 5
This example shows the interaction required to display the properties for the ETH_RX_ERROR
statistic at site 0.
disp_stat_prop eth_rx_error
Where: Is:
ETH_RX_ERROR a counter statistic
System response
STATISTIC: ETH_RX_ERROR SITE: 0
TYPE: PER ETH OBJECT: COUNTER
ALARM ALARM
----------------------------------------------------------------
N/A ENABLED NO ALARM N/A
68P02901W56-T 2-51
Jan 2010
Displaying a counter statistic Chapter 2: Statistical operations
Example 6
This example shows the interaction required to display the properties for the RSL_RX_OCTETS
disp_stat_prop RSL_RX_OCTETS
Where: Is:
RSL_RX_OCTETS a counter statistic
System response
STATISTIC: RSL_RX_OCTETS SITE: 0
TYPE: PER LINK OBJECT: COUNTER
ALARM ALARM
----------------------------------------------------------------
Example 7
This example shows the interaction required to display the properties for the RSL_TX_OCTETS
disp_stat_prop RSL_TX_OCTETS
Where: Is:
RSL_TX_OCTETS a counter statistic
System response
STATISTIC: RSL_TX_OCTETS SITE: 0
TYPE: PER LINK OBJECT: COUNTER
ALARM ALARM
----------------------------------------------------------------
2-52 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying a counter statistic
Example 8
CS_PAGING_MSGS_FROM_MSC statistic at site 1.
disp_stat_prop CS_PAGING_MSGS_FROM_MSC cell 0 0 1 0 1 1 1
Where: Is:
CS_PAGING_MSGS_FROM_MSC a counter statistic
System Response
STATISTIC: CS_PAGING_MSGS_FROM_MSC SITE: 1

ALARM ALARM ALARM
----------------------------------------------------------------------------
68P02901W56-T 2-53
Jan 2010
Displaying a gauge statistic Chapter 2: Statistical operations
Displaying a gauge statistic
Gauge statistic properties are displayed by entering the disp_stat_prop command using the
following syntax:
disp_stat_prop <meas_type> <location> [<cell_desc>]
Where: Is:
meas_type a gauge statistic
Example
This example shows the interaction required to display the properties for the AVAILABLE_TCH
statistic for cell_number=5 4 3 2 1 61698 34776 at site 1.
disp_stat_prop available_tch cell_number=5 4 3 2 1 61698 34776
Where: Is:
available_tch meas_type
cell_number=5 4 3 2 1 61698 34776 cell_desc
System response
STATISTIC: AVAILABLE_TCH SITE: 1
TYPE: PER CELL OBJECT: GAUGE
ALARM ALARM
--------------------------------------------------------------------
2-54 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying a distribution statistic
Displaying a distribution statistic
Distribution statistic properties are displayed by entering the disp_stat_prop command using
disp_stat_prop <meas_type><location> [<cell_desc>]
Where: Is:
meas_type a distribution statistic
Example
This example shows the interaction required to display the properties for the BUSY_TCH
statistic for cell_number=5 4 3 2 1 61698 34776 at site 1.
disp_stat_prop busy_tch cell_number=5 4 3 2 1 61698 34776
Where: Is:
busy_tch meas_type
5 4 3 2 1 61698 34776 cell_desc
68P02901W56-T 2-55
Jan 2010
Displaying a distribution statistic Chapter 2: Statistical operations
System response
STATISTIC: BUSY_TCH SITE: 13
TYPE: PER CELL OBJECT: DISTRIB
CELL # MODE BIN MIN MAX

-------------------------------------------------------------------------
543 21 61698 (f102h)34776 (87d8h) ENABLED 0 0 0
1 1 2
2 3 4
3 5 6
4 7 8
5 9 10
6 11 12
7 13 14
8 15 16
9 17 400
2-56 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying a counter array statistic
Displaying a counter array statistic
Counter array statistic properties are displayed by entering the disp_stat_prop command
using the following syntax:
Where: Is:
meas_type a counter array statistic
Example 1
OUT_HO_CAUSE_ATMPT statistic.
disp_stat_prop out_ho_cause_atmpt cell_number=5 4 3 2 1 62259 8736
Where: Is:
out_ho_cause_atmpt a counter array statistic
5 4 3 2 1 62259 8736 cell number
System response
STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 62
BIN # CAUSE
------------------------
0 Uplink Quality
1 Uplink Level
2 Downlink Quality
3 Downlink Level
4 Distance
5 Uplink Interference
6 Downlink Interference
7 Power Budget
8 Congestion
9 Adjacent Channel Interference
10 Band re-assignment
11 Band Handover
ALARM ALARM ALARM
----------------------------------------------------------------------------
001 01 5 (0005h) 866 (0362h) ENABLED N/A N/A N/A
68P02901W56-T 2-57
Jan 2010
Displaying a counter array statistic Chapter 2: Statistical operations
Example 2
UL_RADIO_BLKS_GMSK_3_TS statistic.
disp_stat_prop UL_RADIO_BLKS_GMSK_3_TS cell 0 0 1 0 1 1 1
Where: Is:
UL_RADIO_BLKS_GMSK_3_TS a counter array statistic
System response
STATISTIC: UL_RADIO_BLKS_GMSK_3_TS SITE: 2

TYPE: PER BSS OBJECT: COUNTER ARRAY
BIN# Cause
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
ALARM ALARM
--------------------------------------------------------------
2-58 68P02901W56-T
Jan 2010
Example 3
This example shows the interaction required to display the properties for the RF_LOSSES_SD
statistic.
disp_stat_prop RF_LOSSES_SD 1 cell_number= 0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_SD a counter array statistic
1 location
System response
STATISTIC: RF_LOSSES_SD SITE: 1
BIN# Cause
0 RX quality in uplink direction.
1 RX quality in downlink direction.
2 RX level in uplink direction.
3 RX level in downlink direction.
4 Others.
ALARM ALARM ALARM
----------------------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) ENABLED total value Major 32767
68P02901W56-T 2-59
Jan 2010
Example 4
This example shows the interaction required to display the properties for the RF_LOSSES_TCH
statistic.
disp_stat_prop RF_LOSSES_TCH 1 cell_number= 0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_TCH a counter array statistic
1 location
System response
STATISTIC: RF_LOSSES_TCH SITE: 1
TYPE: PER TIME SLOT OBJECT: COUNTER ARRAY
BIN# Cause
4 Timing Advance.
5 Sharp decrease of signal level.
6 Others.
ALARM ALARM ALARM
----------------------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) ENABLED total value Major 32767
Example 5
RF_LOSSES_TCH_HR statistic.
disp_stat_prop RF_LOSSES_TCH_HR 1 cell_number= 0 0 1 0 1 1 1
Where: Is:
RF_LOSSES_TCH_HR a counter array statistic
1 location
2-60 68P02901W56-T
Jan 2010
System response
STATISTIC: RF_LOSSES_TCH_HR SITE: 1
TYPE: PER TIME SLOT OBJECT: COUNTER ARRAY
BIN# Cause
4 Timing Advance.
5 Sharp decrease of signal level.
6 Others.
ALARM ALARM
------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) DISABLED NO ALARM N/A
Example 6
PFC_PREEMPTIONS_TRAFFIC_CLASS statistic.
disp_stat_prop PFC_PREEMPTIONS_TRAFFIC_CLASS cell 0 0 1 0 1 1 1
Where: Is:
PFC_PREEMPTIONS_TRAFFIC_CLASS a counter array statistic
System response
STATISTIC: PFC_PREEMPTIONS_TRAFFIC_CLASS SITE: 1
BIN# Cause
0 Preemption of Streaming.
1 Preemption of Interactive THP1.
4 Preemption of Background.
5 Preemption of Best Effort and PFC Unaware.
ALARM ALARM ALARM
--------------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) DISABLED N/A N/A N/A
68P02901W56-T 2-61
Jan 2010
Example 7
PFC_PREEMPTIONS statistic.
disp_stat_prop PFC_PREEMPTIONS cell 0 0 1 0 1 1 1
Where: Is:
PFC_PREEMPTIONS a counter array statistic
System response
STATISTIC: PFC_PREEMPTIONS SITE: 1
BIN# Cause
0 Downgraded PFCs with priority level 1
ALARM ALARM ALARM
--------------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) DISABLED N/A N/A N/A
2-62 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Example 9
Example 8
This example shows the interaction required to display the properties for the TCH_Q_REMOVED
statistic.
disp_stat_prop tch_q_removed cell=0 0 1 0 1 15939 1
Where: Is:
tch_q_removed a counter array statistic
cell=0 0 1 0 1 15939 1 cell description
System response
STATISTIC: TCH_Q_REMOVED SITE: 10
BIN# Cause
0 Number of times an assignment resource is failed in the outer zone and
allocated to outer zone.
1 Number of times an assignment resource is failed in the inner zone and
allocated to inner zone.
2 Number of times a handover is requested.
3 Number of times an assignment resource is failed in the inner zone and
allocated to outer zone.
4 Number of times an assignment resource is failed in the outer zone and
allocated to inner zone.
ALARM ALARM ALARM
--------------------------------------------------------------------
001 01 15939 (3E43h) 1 (0001h) ENABLED N/A N/A N/A
Example 9
IA_IAR_MSGS_PER_AGCH statistic.
disp_stat_prop IA_IAR_MSGS_PER_AGCH cell 0 0 1 0 1 1 1
Where: Is:
IA_IAR_MSGS_PER_AGCH a counter array statistic
System Response
68P02901W56-T 2-63
Jan 2010
Example 9 Chapter 2: Statistical operations
STATISTIC: IA_IAR_MSGS_PER_AGCH SITE: 1

BIN# Cause
0 IA CS messages sent over CCCH
1 IA PS messages sent over CCCH
2 IAR CS messages sent over CCCH
3 IAR PS messages sent over CCCH
4 IA CS messages discarded
5 IA PS messages discarded
6 IAR CS messages discarded
7 IAR PS messages discarded
ALARM ALARM
------------------------------------------------------------
001 01 1 (0001h) 1 (0001h) DISABLED NO ALARM N/A
2-64 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Displaying a duration statistic
Displaying a duration statistic
Duration statistic properties are displayed by entering the disp_stat_prop command using
Where: Is:
meas_type a duration statistic
Example 1
FLOW_CONTROL_BARRED statistic.
disp_stat_prop flow_control_barred cell_number=5 4 3 2 1 62259 8736
Where: Is:
flow_control_barred a duration statistic
5 4 3 2 1 62259 8736 cell number
System response
STATISTIC: FLOW_CONTROL_BARRED SITE: 2
TYPE: PER CELL OBJECT: TOTAL TIME
ALARM ALARM
--------------------------------------------------------------
543 21 62259 (f333h) 8736 (2220h) ENABLED NO ALARM N/A
68P02901W56-T 2-65
Jan 2010
Displaying a duration statistic Chapter 2: Statistical operations
Example 2
PROCESSOR_SAFE_OVERLOAD statistic.
disp_stat_prop PROCESSOR_SAFE_OVERLOAD
Where: Is:
PROCESSOR_SAFE_OVERLOAD a duration statistic
System response
STATISTIC: PROCESSOR_SAFE_OVERLOAD SITE: 0
TYPE: OTHER OBJECT: TOTAL TIME
ALARM ALARM
--------------------------------------------------------------
Example 3
This example shows the interaction required to display the properties for the RSL_LINK_INS
statistic.
disp_stat_prop RSL_LINK_INS
Where: Is:
RSL_LINK_INS a duration statistic
System response
STATISTIC: RSL_LINK_INS SITE: 0
TYPE: PER LINK OBJECT: TOTAL TIME
ALARM ALARM
--------------------------------------------------------------
2-66 68P02901W56-T
Jan 2010
Chapter
BSS statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS statistics are captured from the events occurring at the BSS. They are categorized into
subgroups, each of which are described in BSS statistics subgroups on page 3-2.
68P02901W56-T 3-1
Jan 2010
BSS statistics subgroups Chapter 3: BSS statistics
BSS statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS statistics are organized into the following major subgroups:

• BSS C7 utilization on page 3-2.
• Intra-BSS handover on page 3-2.
• Intra-BSS resume on page 3-2.
• SCCP performance and utilization on page 3-2.
• RSL congestion control on page 3-3.
BSS C7 utilization
BSS C7 utilization statistics track the number of messages received and transmitted on the
signaling links. This information indicates the activity level on the Signaling Links (SLs). The
following are BSS C7 utilization statistics:
• SIF_SIO_RX_OPC on page 3-20.
• SIF_SIO_TX_DPC on page 3-21.
• SIF_SIO_TYPE on page 3-22.
Intra-BSS handover
A single counter array statistic tracks the number of successful intra-BSS handovers:
INTRA_BSS_HO_CAUSE_SUCC on page 3-8.
Intra-BSS resume
A large counter array statistic tracks the number of SUSPEND and RESUME responses
received, not received, and for different reasons RESUME is not triggered per BSS:
NUM_SUSP_RESU_RCVD on page 3-12.
SCCP performance and utilization
SCCP performance and utilization statistics track the performance of the Signaling Connection
Control Part (SCCP) protocol layer of the ITU-TSS C7.
3-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RSL congestion control
The SCCP manages the establishment and release of call related connections. A connection is
established for each transaction. For example, location update and service request, both BSS,
and MSC maintain the contexts related to the transaction; these contexts may be identified
using the SCCP reference number. This information indicates the performance level and quality
of the SCCP. The following are the SCCP performance and utilization statistics:
• BSS_AVAILABILITY on page 3-4.
• HO_REQ_MSC_PROTO on page 3-7.
• MA_REQ_FROM_MSC_FAIL on page 3-10.
• MSC_OVLD_MSGS_RX on page 3-11.
• PAGE_REQ_FROM_MSC_FAIL on page 3-14.
• ROUTING_SYNTAX on page 3-15.
• ROUTING_UNKNOWN on page 3-16.
• SCCP_MSGS on page 3-17.
• SCCP_MSGS_RX on page 3-18.
• SCCP_MSGS_TX on page 3-19.
RSL congestion control
RSL Congestion Control statistics are PM statistics that track the amount of time a processor
was in a congested state and the count of BSS Overload messages during RSL congestion. RSL
Congestion Control statistic BSS_OVLD_MSGS_TX on page 3-6 is described here.
68P02901W56-T 3-3
Jan 2010
BSS_AVAILABILITY Chapter 3: BSS statistics
BSS_AVAILABILITY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSS_AVAILABILITY statistic is used to calculate the availability trend of the BSS to
determine resource requirements required to avoid congestion problems.
• BSS_AVAILABILITY_MEAN: the mean value of BSS_AVAILABILITY.
• BSS_AVAILABILITY_MAX: the maximum value of BSS_AVAILABILITY.
NOTE
This Key Statistic is not available at the OMC now, but users can build their own
custom statistic using the formula provided.
Formula
 
AV AILABLE− T CH+
 
 GP RS− AV AIL− P DT CH+ 
 
 
 EGP RS− AV AIL− P DT CH+ 
BLAN KED− T S
BSS− AVAILABILITY = ∗ 100%
AVAIL− TCH− CAPABLE− TS
NOTE
• BLANKED_TCH
When IST feature is enabled and the time slots are configured to 64 PDTCHs at
the carrier A, then the same timeslot at carrier B is blanked out. The timeslot
at carrier B is blanked_tch.
• AVAIL_TCH_CAPABILE_TS
AVAIL_TCH_CAPABILE_TS includes all the possible time slots which may
provide the traffic service.
3-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Analysis
Analysis
Usage Congestion.
Network planning.
Basis Cell.
Type Percentage.
Raw AVAILABLE_TCH
Statistics GPRS_AVAIL_PDTCH
EGPRS_AVAIL_PDTCH
68P02901W56-T 3-5
Jan 2010
BSS_OVLD_MSGS_TX Chapter 3: BSS statistics
BSS_OVLD_MSGS_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of BSS Overload messages that have been sent from the BSS
to the MSC. The BSS sends Overload messages to the MSC when the first RSL-LCF board is
congested. The BSS sends this statistic to the OMC-R periodically.
Pegging
This statistic is pegged each time an Overload message is sent from the BSS to the MSC.
Analysis
This statistic is used for trend analysis of RSL congestion status on a BSS basis.
Reference GSM TS 12.04 and GSM TS 8.08

Usage RSL Congestion Control and Trend analysis.
Basis BSS.
Type Counter.
Alarm None
3-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_REQ_MSC_PROTO
HO_REQ_MSC_PROTO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of Handover Request messages received from the MSC that fail
message validation. Validation failure may occur due to protocol errors which may occur, if the
message is badly formatted or incompatible database elements exist in the BSS and MSC.
Pegging
This statistic is pegged each time a Handover Request message from the MSC fails message
validation at the BSS. Currently, this statistic is not pegged.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
message validation failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 17. BSS: HO Request from the MSC protocol
error - PM alarm is generated. Refer to the manual Maintenance Information: Alarm Handling
at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.5.2.2.

Usage Handover and Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-T 3-7
Jan 2010
INTRA_BSS_HO_CAUSE_SUCC Chapter 3: BSS statistics
INTRA_BSS_HO_CAUSE_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of successful intra BSS handovers on a per-cause basis. A total
count of all successful results is also maintained.
Table 3-1 INTRA_BSS_HO_CAUSE_SUCC bins
Bin Cause Description

0 UPLINK_QUALITY Handovers due to uplink quality.
1 UPLINK_LEVEL Handovers due to uplink level.
2 DOWNLINK_QUALITY Handovers due to downlink quality.
3 DOWNLINK_LEVEL Handovers due to downlink level.
4 DISTANCE Handovers due to distance.
5 UPLINK_INTERFERENCE Handovers due to uplink interference.
6 DOWNLINK_INTERFERENCE Handovers due to downlink interference.
7 POWER_BUDGET Handovers due to power budget.
8 CONGESTION Handovers due to congestion.
Pegging
The bin corresponding to the cause of the successful handover is pegged each time a Handover
Performed message is sent from the BSS to the MSC.
Full-rate to half-rate congestion-based Intra-cell handovers cause the CONGESTION bin to

be pegged.
Half-rate quality based Intra-cell handovers cause the DOWNLINK_INTERFERENCE or

UPLINK_INTERFERENCE bins to be pegged.
3-8 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis permitting early identification of problems before
they affect service.
Reference GSM 12.04, 4.21, B.1.1.11.

GSM 12.04, 8.08, 3.2.1.9, and 3.2.1.25.
Usage Radio resource allocation, Quality of service monitoring, Network planning,
and Optimization.
Basis BSS.
Type Counter array.
68P02901W56-T 3-9
Jan 2010
MA_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics
MA_REQ_FROM_MSC_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of Assignment Request messages received from the MSC that
fail message validation. Validation failure may occur due to protocol errors which may occur, if
the message is badly formatted or incompatible database elements exist in the BSS and MSC.
Pegging
This statistic pegs each time an Assignment Request message from the MSC fails message
validation at the BSS.
Analysis
failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. BSS: MS assignment request from MSC
protocol error - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.2.2.5 and 3.2.1.3.

Usage Radio resource allocation and Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MSC_OVLD_MSGS_RX
MSC_OVLD_MSGS_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of MSC Overload messages that have been received by the BSS
from the MSC. This statistic pegs independent of the MSC Overload Control feature being
enabled or disabled.
Pegging
This statistic pegs each time an Overload message is received by the BSS from the MSC.
Analysis
In systems without the MSC Overload Control feature, this statistic can be used to determine if
the MSC feature should be acquired, if not currently installed.
Reference GSM-BSS-MOC-EFP-001, v1.1, 2238-7

Usage Quality of service and Network planning.
Basis BSS.
Type Counter.
68P02901W56-T 3-11
Jan 2010
NUM_SUSP_RESU_RCVD Chapter 3: BSS statistics
NUM_SUSP_RESU_RCVD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the following information:

• Number of responses received for SUSPEND and RESUME.
• Number of responses not received for SUSPEND and RESUME.
• Number of occurrences the RESUME is not triggered due to different reasons.
Pegging
This statistic is pegged for every response received, not received and resume procedure not
initiated.
Table 3-2 NUM_SUSP_RESU_RCVD bins
Bin Description
0 BSC receives SUSPEND-ACK message.
1 BSC receives SUSPEND-NACK message with cause value Suspend NACK received
from SGSN.
2 BSC receives SUSPEND-NACK message with cause value no response.
3 BSC does not receive any response for Suspend procedure.
4 BSC receives RESUME-ACK message.
5 BSC receives RESUME-NACK message with cause value Resume NACK received
from SGSN.
6 BSC receives RESUME-NACK message with cause value no response.
7 BSC does not receive any response for RESUME procedure.
8 BSC detects MS handover to different RA.
9 Unused.
10 BSC receives SUSPEND-NACK or RESUME-NACK message with cause value
GPRS cell OOS.
NOTE
Refer to for detailed values of each bin.
3-12 68P02901W56-T
Jan 2010
Analysis
Reference None
Usage Optimization
Basis BSS
Type Large Counter Array
Alarm None
NOTE
The BSC does not support the chg_stat_prop command for the
NUM_SUSP_RESU_RCVD statistic. This command cannot be used to change
NUM_SUSP_RESU_RCVD information.
68P02901W56-T 3-13
Jan 2010
PAGE_REQ_FROM_MSC_FAIL Chapter 3: BSS statistics
PAGE_REQ_FROM_MSC_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of Page Request messages received from the MSC that fail
message validation. Validation failure may occur due to protocol errors which may occur, if the
message is badly formatted. A protocol error does not indicate paging success or failure.
Pegging
This statistic pegs each time a Page Request message from the MSC fails message validation
at the BSS.
Analysis
failures that are acceptable in normal system operations. The Cell Identifier List is not verified
until the page is about to be sent to the cells.
If the specified threshold is exceeded, the 0. BSS: Paging request from MSC protocol error
- PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
(68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Usage Quality of service monitoring (Paging analysis) and Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ROUTING_SYNTAX
ROUTING_SYNTAX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of SCCP messages with syntax errors.
Pegging
This statistic pegs when a syntax error is detected in an SCCP message.
Analysis
SCCP is an SS7 protocol used in transferring signaling messages between the BSC and MSC.
Excessive syntax errors can result in degraded SCCP performance. A threshold value should be
assigned to this statistic which reflects the maximum number of SCCP messages with syntax
errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. BSS: Routing failure - syntax error detected
- PM alarm is generated. Refer to the manual Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization, and Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-T 3-15
Jan 2010
ROUTING_UNKNOWN Chapter 3: BSS statistics
ROUTING_UNKNOWN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of invalid signaling point codes (SPCs) that a BSC has received
from the MSC.
Pegging
This statistic pegs whenever an invalid SPC is received from the MSC.
Analysis
An SPC is the destination address for a message routed by the networking functions of the
MTP3 protocol. If the BSC receives an incorrect SPC, it cannot route the message correctly.
invalid SPCs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. BSS: Routing failure - reason unknown - PM
alarm is generated. Refer to the manual Maintenance Information: Alarm Handling at the
OMC-R (68P02901W26) for troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization, and Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SCCP_MSGS
SCCP_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages either transmitted or received over
an SL.
Pegging
This statistic pegs when SCCP messages are transmitted or received on the signaling link.
Analysis
This statistic can be used for trend analysis of SCCP performance and utilization.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Basis BSS.
Type Counter.
68P02901W56-T 3-17
Jan 2010
SCCP_MSGS_RX Chapter 3: BSS statistics
SCCP_MSGS_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages received on an SL for class 0 or class 2.
Pegging
This statistic pegs when SCCP messages are received on the signaling link.
Analysis
This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
3-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SCCP_MSGS_TX
SCCP_MSGS_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages transmitted on an SL for class 0 or
class 2.
Pegging
This statistic pegs when SCCP messages are transmitted on the signaling link.
Analysis
This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
68P02901W56-T 3-19
Jan 2010
SIF_SIO_RX_OPC Chapter 3: BSS statistics
SIF_SIO_RX_OPC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SIF and SIO octets received on all SLs for a particular
BSS.
Pegging
This statistic pegs each time Signal Information Fields (SIF) or Service Information Octets (SIO)
are received across all signaling links to a BSS.
Analysis
This statistic can be used for trend analysis of the activity on all SLs for a particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 utilization.
Basis BSS.
Type Counter.
3-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SIF_SIO_TX_DPC
SIF_SIO_TX_DPC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of Signal Information Fields (SIF) and Service Information
Octets (SIO) octets transmitted on all SLs of a particular BSS by the Destination Point Code
(DPC).
Pegging
This statistic pegs each time SIF or SIO are transmitted across all signaling links to a BSS.
Analysis
A DPC is a part of the label in a signaling message that uniquely identifies, in a signaling
network, the destination point of the message. This statistic can be used for trend analysis of
the activity of the signaling links on a BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
68P02901W56-T 3-21
Jan 2010
SIF_SIO_TYPE Chapter 3: BSS statistics
SIF_SIO_TYPE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of SIF MTP, TEST, and SCCP SIO octets transmitted or received
on an SL on an SIO basis.
Pegging
This statistic pegs each time SIF or SIO octets are transmitted or received on each signaling link.
Analysis
This statistic can be used for trend analysis of the activity of the signaling links on a BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
3-22 68P02901W56-T
Jan 2010
Chapter
Cell statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Cell statistics are captured from the events occurring in a cell. They are categorized into
subgroups, each of which are described in Cell statistics subgroups on page 4-2.
68P02901W56-T 4-1
Jan 2010
Cell statistics subgroups Chapter 4: Cell statistics
Cell statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Cell statistics are organized into the following major subgroups:

• Adaptive Multi-Rate on page 4-2.
• Assignment redirection on page 4-3.
• Call clearing on page 4-3.
• Concentric cell on page 4-3.
• Connection establishment on page 4-4.
• Directed retry on page 4-5.
• Emergency call access on page 4-5.
• Enhanced 2G/3G handover and reselection on page 4-5.
• Enhanced Multi-level Precedence and Preemption service on page 4-6.
• Extended range cell on page 4-6.
• General handover on page 4-6.
• Inter-BSS handover on page 4-7.
• Interference bands on page 4-7.
• Intra-cell handover on page 4-7.
• Multiband on page 4-8.
• Network assist cell change on page 4-8.
• GPRS Quality of Service on page 4-9.
• GPRS System information on page 4-9.
• TCH assignment on page 4-10.
• Usage congestion on page 4-10.
Adaptive Multi-Rate
Adaptive Multi-Rate (AMR) statistics are used to gauge performance of systems using the AMR
link adaptation. The following are AMR statistics:
• AMR_DECREASE_THRESH_ADJUST on page 4-33.
• AMR_FR_DL_ADAPTATION on page 4-34.
4-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Assignment redirection
• AMR_FR_DL_CODEC_MODE_USAGE on page 4-35.
• AMR_FR_UL_ADAPTATION on page 4-36.
• AMR_FR_UL_CODEC_MODE_USAGE on page 4-37.
• AMR_HR_DL_ADAPTATION on page 4-38.
• AMR_HR_DL_CODEC_MODE_USAGE on page 4-39.
• AMR_HR_UL_ADAPTATION on page 4-40.
• AMR_HR_UL_CODEC_MODE_USAGE on page 4-41.
• AMR_INCREASE_THRESH_ADJUST on page 4-42.
Assignment redirection
Assignment redirection statistics track the number of times a call assignment is redirected to
another cell. The statistic ASSIGNMENT_REDIRECTION on page 4-43 is the only assignment
redirection statistic.
Call clearing
Call clearing statistics track the number of calls lost due to RF failures, cipher mode failures, or
procedure timeouts. The following are call clearing statistics:
• CIPHER_MODE_FAIL on page 4-70.
• CLR_REQ_TO_MSC on page 4-73.
• RF_LOSSES_SD on page 4-183.
• RF_LOSSES_TCH on page 4-185.
• RF_LOSSES_TCH_HR on page 4-187.
• RF_LOSSES_TCH_SIG on page 4-189.
Concentric cell
Concentric cell statistics track concentric cell feature processes. The following are concentric
cell statistics:
• TCH_CONG_INNER_ZONE on page 4-202.
• TCH_CONG_INNER_ZONE_HR on page 4-203.
• TCH_USAGE_INNER_ZONE on page 4-218.
• ZONE_CHANGE_ATMPT on page 4-229.
68P02901W56-T 4-3
Jan 2010
Connection establishment Chapter 4: Cell statistics
• ZONE_CHANGE_SUC on page 4-230.
Connection establishment
Connection establishment statistics track access, allocation, channel request, and MSC page
request functions. The following are connection establishment statistics:
• ACCESS_PER_AGCH on page 4-12.
• ACCESS_PER_PCH_CS_PS on page 4-13.
• ACCESS_PER_PCH_CS on page 4-15.
• ACCESS_PER_PCH_ PS on page 4-17.
• ACCESS_PER_PPCH on page 4-19.
• ACCESS_PER_RACH on page 4-21.
• ALLOC_SDCCH on page 4-22.
• ALLOC_SDCCH_FAIL on page 4-23.
• ALLOC_TCH on page 4-24.
• ALLOC_TCH_FAIL on page 4-25.
• ALLOC_TCH_FAIL_HR on page 4-26.
• ALLOC_TCH_HR on page 4-30.
• ALLOC_TCH_FAIL_INNER_ZONE on page 4-28.
• ALLOC_TCH_INNER_ZONE on page 4-31.
• ALLOC_TCH_SIG on page 4-32.
• CALL_SP_VERS_DOWNGRADE_MONITOR on page 4-65.
• CHAN_REQ_CAUSE_ATMPT on page 4-68.
• CHAN_REQ_MS_BLK on page 4-69.
• CONN_REFUSED on page 4-78.
• CONN_REQ_TO_MSC on page 4-80.
• CS_PAGING_MSGS_FROM_MSC on page 4-81.
• DL_LLC_DATA_VOLUME on page 4-83.
• DL_LLC_TRANS_TIME on page 4-85.
• IA_IAR_MSGS_PER_AGCH on page 4-96.
• OK_ACC_PROC on page 4-139.
• OK_ACC_PROC_SUC_RACH on page 4-141.
4-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Directed retry
• PAGE_REQ_FROM_MSC on page 4-148.
• UL_LLC_DATA_VOLUME on page 4-225.
• UL_LLC_TRANS_TIME on page 4-227.
Directed retry
Directed retry statistics track congestion processes associated with the directed retry feature.
The following are directed retry statistics:
• CONGEST_EXIST_HO_ATMPT on page 4-76.
• CONGEST_STAND_HO_ATMPT on page 4-77.
Emergency call access
Emergency call access statistics track emergency call processes. The following are emergency
call access statistics:
• NUM_EMERG_ACCESS on page 4-127.
• NUM_EMERG_REJECTED on page 4-128.
• NUM_EMERG_TCH_KILL on page 4-129.
• NUM_EMERG_TERM_SDCCH on page 4-130.
Enhanced 2G/3G handover and reselection
Enhanced 2G/3G handover and reselection statistics are captured from the events occurring
due to enhanced 2G/3G handover and reselection. The following are enhanced 2G/3G handover
and reselection statistics:
• NUM_HO_3G_ATTEMPTS on page 4-131.
• NUM_HO_TO_3G_RES_ALLOC_SUCC on page 4-134.
• NUM_HO_TO_3G_SUCCESS on page 4-135.
• NUM_HO_FROM_3G_ATTEMPTS on page 4-132.
• NUM_HO_FROM_3G_SUCCESS on page 4-133.
• NUM_MULTIRAT_MS_ORIG_CALL on page 4-136.
68P02901W56-T 4-5
Jan 2010
Enhanced Multi-level Precedence and Preemption service Chapter 4: Cell statistics
Enhanced Multi-level Precedence and Preemption service
Enhanced Multi-level Precedence and Preemption service statistics are captured from the
events occurring due to multilevel and preemption. The following are Enhanced Multi-level
Precedence and Preemption service statistics:
• PREEMPT_CAP on page 4-181.
• QUEUE_PREEMPT_ATMPT on page 4-182.
• TCH_PREEMPT_ATMPT on page 4-208.
• TCH_PREEMPT_FAIL_NO_CAND on page 4-209.
• TCH_PREEMPT_FAIL_TIMEOUT on page 4-210.
• TCH_PREEMPT_NO_Q_ALLOC on page 4-212.
• TCH_PREEMPT_RQD on page 4-211.
Extended range cell
Extended range statistics track extended range feature processes. The following are extended
range cell statistics:
• ER_INTRA_CELL_HO_ATMPT on page 4-87.
• ER_INTRA_CELL_HO_SUC on page 4-88.
• TCH_USAGE_EXT_RANGE on page 4-217.
General handover
General handover statistics track processes common to all types of handovers. The following
are handover statistics:
• BAD_HO_REFNUM_MS on page 4-55.
• HO_FAIL_NO_RESOURCES on page 4-90.
4-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Inter-BSS handover
Inter-BSS handover
Inter-BSS handover statistics track inter-BSS handover processes. The following are inter-BSS
handover statistics:
• HO_REQ_ACK_TO_MSC on page 4-94.
• HO_REQ_FROM_MSC on page 4-92.
• HO_REQ_MSC_FAIL on page 4-93.
• IN_INTER_BSS_HO on page 4-102.
• OUT_INTER_BSS_HO on page 4-142.
Interference bands
Interference band statistics track the number of idle TCHs per interference band:
• IDLE_TCH_INTF_BAND0 on page 4-97.
Intra-BSS handover
Intra-BSS handover statistics track intra-BSS handover processes. The following are intra-BSS
handover statistics:
• IN_INTRA_BSS_HO on page 4-103.
• T on page 4-200.
• OUT_INTRA_BSS_HO on page 4-144.
Intra-cell handover
Intra-cell handover statistics track intra-cell handover processes. INTRA_CELL_HO on page

4-106 is the only intra-cell handover statistic.
68P02901W56-T 4-7
Jan 2010
Multiband Chapter 4: Cell statistics
Multiband
Multiband statistics track multiband feature processes. The following are multiband statistics:
• ASSIGNMENT_REDIRECTION on page 4-43.
• INTERBAND_ACTIVITY on page 4-105.
• MS_ACCESS_BY_TYPE on page 4-118.
• MS_TCH_USAGE_BY_TYPE on page 4-119.
• MS_TCH_USAGE_BY_TYPE on page 4-119.
• T on page 4-200.
Network assist cell change
Network assist cell change statistics are captured from the events occurring in the network
assist cell. The following are network assist cell change statistics:
• NUM_CELL_RESEL_CELL on page 4-124.
• NUM_CELL_RESEL_CELL_PCCN on page 4-125.
• NUM_CELL_RESEL_CELL_SUCC on page 4-126.
NOTE
There are statistics that capture PCCC and PCCO attempts to neighbor cells. These
are shown in Network assist neighbor cell change statistics on page 5-7.
4-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS Quality of Service
GPRS Quality of Service
BSS GPRS Quality of Service statistics are captured from the events occurring in the BSS. The
following are GPRS Quality of Service statistics:
• DL_LLC_DATA_VOLUME on page 4-83.
• PFC_ADMISSION on page 4-153.
• PFC_ADMISSION_TRAFFIC_CLASS on page 4-155.
• PFC_DOWNGRADE_FAILURE on page 4-157.
• PFC_DOWNGRADE_SUCCESS on page 4-159.
• PFC_GBR_DL on page 4-161.
• PFC_GBR_UL on page 4-163.
• PFC_PREEMPTIONS on page 4-165.
• PFC_PREEMPTIONS_TRAFFIC_CLASS on page 4-167.
• PFC_REJ_DGRD_PRMPT_CELL on page 4-168.
• PFC_REJECTION on page 4-173.
• PFC_REJECTION_TRAFFIC_CLASS on page 4-175.
• PFC_REJECT_CAUSES on page 4-170.
• PFC_TRANSFER_DELAY on page 4-176.
• PFC_UPGRADE on page 4-178.
• TIMER_EXP_PAP_CONV on page 4-219.
• UL_LLC_DATA_VOLUME on page 4-225.
• UL_RLC_NACK_BLKS on page 4-221.
• UL_RLC_STALLED_BLKS on page 4-223.
GPRS System information
These statistics are captured from GPRS system information events occurring in GPRS R4 phase
1. The following are GPRS Release 4 Phase 1 GPRS system information events:
• PACKET_SYSINFO_REQ on page 4-146.
• PACKET_SYSINFO_RESP on page 4-147.
• RSS_ALLOC_RESERVE_BLOCK on page 4-190.
68P02901W56-T 4-9
Jan 2010
TCH assignment Chapter 4: Cell statistics
TCH assignment
TCH assignment statistics track successful, unsuccessful, and total traffic channel assignment
processes. The following are TCH assignment statistics:
• MA_CMD_TO_MS on page 4-109.
• MA_CMD_TO_MS_BLKD on page 4-116.
• MA_FAIL_FROM_MS on page 4-113.
• MA_REQ_FROM_MSC on page 4-114.
• TCH_Q_REMOVED on page 4-214.
• TOTAL_CALLS on page 4-220.
Usage congestion
Usage congestion statistics track congestion processes not related to the directed retry feature.
The following are usage congestion statistics:
• AVAILABLE_SDCCH on page 4-44.
• AVAILABLE_TCH on page 4-46.
• AVAILABLE_TCH_DCS1800 on page 4-48.
• AVAILABLE_TCH_EGSM on page 4-50.
• AVAILABLE_TCH_HR on page 4-52.
• AVAILABLE_TCH_PGSM on page 4-53.
• BUSY_SDCCH on page 4-56.
• BUSY_TCH on page 4-58.
• BUSY_TCH_CARR on page 4-60.
• BUSY_TCH_DCS1800 on page 4-61.
• BUSY_TCH_EGSM on page 4-62.
• BUSY_TCH_HR on page 4-63.
• BUSY_TCH_PGSM on page 4-64.
• CALLS_QUEUED on page 4-67.
• CLASSMK_UPDATE_FAIL on page 4-71.
• FLOW_CONTROL_BARRED on page 4-89.
• MA_COMPLETE_TO_MSC on page 4-111.
• MA_FAIL_FROM_MS on page 4-113.
4-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Usage congestion
• MA_REQ_FROM_MSC on page 4-114.
• PAGING_REQUESTS_CS on page 4-149.
• PAGING_REQUESTS_PS on page 4-150.
• PCH_AGCH_Q_LENGTH on page 4-151.
• PCH_Q_PAGE_DISCARD on page 4-152.
• PPCH_Q_PAGE_DISCARD on page 4-180.
• SDCCH_CONGESTION on page 4-191.
• SECOND_ASSIGN_ATMPT on page 4-192.
• SECOND_ASSIGN_SUC on page 4-194.
• SMS_INIT_ON_TCH on page 4-198.
• SMS_NO_BCAST_MSG on page 4-199.
• TCH_CONGESTION on page 4-204.
• TCH_CONGESTION_EN on page 4-205
• TCH_CONGESTION_HR on page 4-206.
• TCH_DELAY on page 4-207.
• TCH_Q_LENGTH on page 4-213.
• TCH_USAGE on page 4-215.
68P02901W56-T 4-11
Jan 2010
ACCESS_PER_AGCH Chapter 4: Cell statistics
ACCESS_PER_AGCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_AGCH statistic tracks Immediate Assignment messages sent on the Access
Grant Channel (AGCH) of a cell.
Access Grants for more than one MS may be contained in one Access Grant message. An Access
Grant for more than one MS is pegged only once. This count includes Immediate Assignment,
Immediate Extended, and Immediate Assignment Reject messages sent on the AGCH of a cell.
Pegging
This statistic pegs when an Access Grant message is sent on the AGCH to signal the availability
of an allocated channel.
Analysis
This statistic can be used for trend analysis of Intermediate Assignment messages sent on
the AGCH of a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.

GSM 4.08, 3.8.0, 3.3.1.2.1, 7.1.2, 9.1.17-19.
GSM 12.04, 3.1.0, B.1.1.10.
Usage Radio resource allocation statistics and Network planning.
Basis Cell.
Type Counter.
NOTE
This statistic is affected by phantom Random Access CHannel (RACH). The level of
congestion on the AGCH cannot be determined using current statistics
4-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ACCESS_PER_PCH_CS_PS
ACCESS_PER_PCH_CS_PS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_PCH_CS_PS statistic tracks the number of paging request messages sent
on the air interface.
This statistic counts both Circuit Switched (CS) and Packet Switched (PS) paging on Page
Channel (PCH). Both CS and PS page within the paging request message and the statistic
measures the number of paging request messages sent on the PCH.
A paging message could contain up to four pages for paging by TMSI and up to two pages
for paging by IMSI.
The statistic is calibrated to count the number of attempts made to send the message.
Pegging
This statistic pegs on receiving requests that:

• Succeeded (resulted in channel assignment).
• Failed (did not result in channel assignment).
NOTE
This statistic is pegged for both GPRS and EGPRS events.
Analysis
This statistic can be used for trend analysis of Paging Request messages sent on the PCH of
a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.

GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Usage Radio resource allocation and Network planning.
Basis Cell.
Type Individual Counter.
68P02901W56-T 4-13
Jan 2010
Analysis Chapter 4: Cell statistics
NOTE
If the MS does not answer the first request, the ACCESS_PER_PCH_CS_PS
statistic pegs for the second time. This situation arises because the BSS is unable
to distinguish between a paging message retry to one MS and an attempt to page
a different connection.
4-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ACCESS_PER_PCH_CS
ACCESS_PER_PCH_CS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_PCH_CS statistic tracks the number of paging request messages sent
This statistic counts Circuit Switched (CS) paging only on Page Channel (PCH). This statistic is
obtained by measuring the number of paging request messages sent on the PCH.
for paging by IMSI.
The statistic is calibrated to count the number of attempts made to send the message.
Pegging

NOTE
Analysis
a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.

GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Basis Cell.
68P02901W56-T 4-15
Jan 2010
NOTE
If the MS does not answer the first request, the ACCESS_PER_PCH_CS statistic pegs
for the second time. This situation arises because the BSS is unable to distinguish
between a paging message retry to one MS and an attempt to page a different
connection.
4-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ACCESS_PER_PCH_ PS
ACCESS_PER_PCH_ PS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_PCH_PS statistic tracks the number of paging request messages sent
This statistic counts Packet Switched (PS) paging only on Page Channel (PCH). This statistic is
obtained by measuring the number of paging request messages sent on the PCH.
for paging by IMSI.
Pegging

NOTE
Analysis
a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.

GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Basis Cell.
68P02901W56-T 4-17
Jan 2010
NOTE
If the MS does not answer the first request, the ACCESS_PER_PCH_PS statistic pegs
for the second time. This situation arises because the BSS is unable to distinguish
between a paging message retry to one MS and an attempt to page a different
connection.
4-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ACCESS_PER_PPCH
ACCESS_PER_PPCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_PPCH statistic tracks the number of attempted transmissions of Packet

Paging Request messages sent on the Packet Paging Channel (PPCH).
Table 4-1 ACCESS_PER_PPCH bins
Bin Description
0 Both CS and PS pages within the PACKET PAGING REQUEST message.
1 Only CS pages within the PACKET PAGING REQUEST message.
2 Only PS pages within the PACKET PAGING REQUEST message.
Pegging
This statistic is obtained by measuring the number of Packet Paging Requests sent on the
PPCH. The number of attempts are counted.
NOTE
Analysis
This statistic can be used for trend analysis of Packet Paging Request messages sent on the
PPCH of a cell.
Reference GSM 4.03, 3.0.3, 4.3.2.1.

GSM 4.08, 3.8.0, 3.3.2.1, 7.1.1 and 9.1.21-23.
GSM 12.04, 3.1.0, B.1.1.10.
Basis Cell.
Type Counter array.
68P02901W56-T 4-19
Jan 2010
NOTE
If the MS does not answer the first page, the ACCESS_PER_PPCH statistic pegs a
second time. This is because there is no way for the BSS to distinguish between a
retry of a page to one MS and an attempt to page a different MS.
4-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ACCESS_PER_RACH
ACCESS_PER_RACH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_RACH statistic tracks Channel Request messages received by the BSS on
the Random Access CHannel (RACH) of a cell for Circuit Switched (CS) and Packet Switched
(PS) related messages.
A Channel Request message is used by the MS to request allocation of a dedicated channel (to
be used as an SDCCH) by the network, in response to a paging message (incoming call) from the
network, or as a result of an outgoing call/supplementary short message service dialed from the
MS. It is also used as a part of the call reestablishment procedure.
Pegging
This statistic pegs received requests that:

• Succeeded (resulting in channel assignment).
Analysis
This statistic can be used for trend analysis of Channel Request messages sent on the RACH of
a cell.
Reference GSM 4.08, 3.8.0, 3.3.1.1, 3.3.2.2, 4.5.1.6, 5.5.4, 7.1.2, 9.1.8 and 9.2.4.
GSM 4.03, 3.03 and 4.3.2.1.
GSM 12.04, 3.2.0, B.1.1.10.
Usage RF loss, Congestion, Quality of service monitoring and Network
planning.
Basis Cell.
Type Counter.
NOTE
This statistic is affected by phantom RACHs. The counter is incremented at least once
for each phantom RACH. For more information refer Phantom RACHs on page 20-7 .
68P02901W56-T 4-21
Jan 2010
ALLOC_SDCCH Chapter 4: Cell statistics
ALLOC_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_SDCCH statistic is the sum of the number of times an SDCCH is successfully
seized. If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are configured.
A Channel Request message is used by the MS to request allocation of a dedicated channel (to
be used as an SDCCH) by the network, in response to a paging message (incoming call) from the
network or as a result of an outgoing call/supplementary short message service dialed from the
MS. It is also used as a part of the call reestablishment procedure.
SDCCH seizure is caused by immediate assignment, handover, and channel assignment

procedures. Congestion is signaled by the Immediate Assignment Reject or the
Assignment/Handover Failure message.
Pegging
This statistic pegs each time an Immediate Assignment message is sent by the BSS. An
Immediate Assignment message is sent upon:
• Successful handover on an SDCCH channel.
• Successful immediate assignment on an SDCCH channel.
Analysis
This statistic can be used for trend analysis of SDCCH seizures.
Reference GSM 12.04, 3.1.0, B.1.3.3.

GSM 4.08, 3.8.0, 3.3.12, 3.4.3.1, 3.4.4.1, 9.1.2 to 9.1.4, 9.1.14 to 9.1.19.
Usage RF loss, Congestion, Quality of service monitoring (Call set-up), Network
planning, Ladder (Immediate assignment successful, Intra-cell handover,
Inter-BSS handover, Connection establishment, Intra-BSS handover) and
Key statistics (SDCCH_BLOCKING_RATE, SDCCH_CONGESTION,
SDCCH_MEAN_HOLDING_TIME and SDCCH_RF_LOSS_RATE).
Basis Cell.
Type Counter.
NOTE
This statistic is affected by phantom RACHs. For more information refer Phantom
RACHs on page 20-7 .
4-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ALLOC_SDCCH_FAIL
ALLOC_SDCCH_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_SDCCH_FAIL statistic tracks the number of times that an attempt at SDCCH
seizure was rejected because of SDCCH congestion.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics is incremented. Congestion is

signaled by the Immediate Assignment Reject or the Assignment/Handover Failure message.
Pegging
This statistic pegs when an Immediate Assignment Reject message is sent to the MS in response
to a channel request because no SDCCH channels were available to be allocated. It is also
pegged in the target cell when rejecting a handover due to a lack of resources.
Analysis
SDCCH failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH failed
Reference GSM 12.04, 3.1.0, B.1.3.4.

GSM 4.08, 3.8.0, 3.3.1.2.2, 3.4.3.3, 3.4.4.4, 9.1.4, 9.1.16 and 9.1.19.
Usage RF loss, Congestion, Quality of service monitoring (Call set-up).
Network planning, Fault finding, and Optimization.
Ladder: Immediate assignment blocked and Connection establishment.
Key statistics (SDCCH_BLOCKING_RATE and SDCCH_CONGESTION).
Basis Cell.
Type Counter.
Alarm Major.
NOTE
68P02901W56-T 4-23
Jan 2010
ALLOC_TCH Chapter 4: Cell statistics
ALLOC_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH statistic tracks the number of successful TCH allocations within a cell for
both call originations and hand-ins.
Pegging
This statistic pegs for successful TCH allocations within a cell as a result of a call establishment
or hand-in attempt:
• Successful allocation due to call establishment including successful allocations due to
directed retries.
• Successful allocation due to intra-cell hand-in.
• Successful allocation due to inter-cell/intra-cell hand-in.
• Successful allocation due to inter-BSS hand-in.
This statistic pegs before the transmission of the assignment/handover command to the MS
and, therefore, does not take into account the success or failure of the assignment/hand-in
from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations.
Usage Quality of service monitoring: Call setup.

Network planning.
Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cell handover,
Assignment to TCH.
Key statistics (CELL_TCH_ALLOCATIONS, CELL_TCH_ASSIGNMENTS,
TCH_BLOCKING_RATE, TCH_BLOCKING_RATE_OUT_ZONE,
TCH_MEAN_ARRIVAL_RATE, TCH_MEAN_HOLDING_TIME and
TCH_RF_LOSS_RATE).
Basis Cell.
Type Counter.
4-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ALLOC_TCH_FAIL
ALLOC_TCH_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH_FAIL statistic tracks the number of unsuccessful full rate and half rate
allocations of a TCH within a cell for both call origination and hand-in. Cases involving
Immediate Assignment Reject are also included in the peg count.
Pegging
This statistic pegs when an attempt to allocate a TCH in a cell fails due to a lack of resources:
• Unsuccessful allocation due to call establishment including unsuccessful allocations due
to directed retries.
• Unsuccessful allocation due to intra-cell hand-in.
• Unsuccessful allocation due to inter-cell/intra cell hand-in.
• Unsuccessful allocation due to inter-BSS hand-in.
The BSS pegs the ALLOC_TCH_FAIL statistic every time a TCH allocation fails to allocate a TCH.
The AMR Half Rate and GSM Half Rate channel modes are pegged as a generic half rate channel.
Analysis
TCH failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 25. CELL: Attempt at allocating a TCH failed
Usage Quality of service (Call set-up), Fault finding, Optimization, Network planning and
Ladder (Inter-BSS handover, Intra-BSS handover and Assignment to TCH).
Key statistics (TCH_BLOCKING_RATE, TCH_BLOCKING_RATE_OUT_ZONE
and TCH_MEAN_ARRIVAL_RATE).
Basis Cell.
Type Counter.
Alarm Major.
68P02901W56-T 4-25
Jan 2010
ALLOC_TCH_FAIL_HR Chapter 4: Cell statistics
ALLOC_TCH_FAIL_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic tracks the number of unsuccessful allocations of a half rate AMR and/or GSM TCH
within a cell for both call origination and hand-in. Cases involving Immediate Assignment Reject
are also included in the peg count.
Pegging
This statistic pegs when an attempt to allocate a half rate AMR and/or GSM TCH in a cell fails
due to a lack of resources:
NOTE
Upon failure to allocate a channel, the channel allocation failure statistic is pegged
for all the allowed channel rates. Here are some channel allocation failure scenarios:
• If there is a speech call for which the channel type is full rate and half rate,
a failure in allocating a channel results in both ALLOC_TCH_FAIL and
ALLOC_TCH_FAIL_HR being pegged.
• ALLOC_TCH_FAIL_HR is pegged for a speech call for which the channel type
specifies both full rate and half rate (with half rate preferred) but result in a full
rate channel being allocated.
• When there is a failure to allocate a half rate channel, both ALLOC_TCH_FAIL
and ALLOC_TCH _FAIL_HR are pegged.
4-26 68P02901W56-T
Jan 2010
• If the channel type is half rate preferred or full rate non-preferred, or full rate
preferred or half rate non-preferred and neither channel type is allocated (a
complete TCH allocation failure scenario), the ALLOC_TCH_FAIL is pegged
once and ALLOC_TCH_FAIL_HR is pegged once.
• When the non-preferred channel type is successfully assigned a channel, a
failure shall be pegged for the preferred type.
Analysis
half rate AMR and/or GSM TCH failures due to congestion that are acceptable in normal system
operations.
NOTE
No alarms are generated for this statistic.
Reference None.
Usage Quality of service (Call set-up), Fault finding, Optimization, Network
planning and Ladder (Inter-BSS handover, Intra-BSS handover and
Assignment to TCH).
Basis Cell.
Type Counter.
68P02901W56-T 4-27
Jan 2010
ALLOC_TCH_FAIL_INNER_ZONE Chapter 4: Cell statistics
ALLOC_TCH_FAIL_INNER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH_FAIL_INNER_ZONE statistic tracks the number of unsuccessful full rate and
half rate allocations of a TCH within a cell for both call origination and hand-in for inner zone.
Cases involving Immediate Assignment Reject are also included in the peg count.
Pegging
This statistic pegs when an attempt to allocate a TCH in a cell fails due to lack of resources:
The BSS pegs the ALLOC_TCH_FAIL_INNER_ZONE statistic every time a TCH allocation fails
to allocate a TCH for inner zone.
The AMR Half Rate and GSM Half Rate channel modes are pegged as generic half rate channel.
Analysis
TCH failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 25. CELL: Attempt at allocating a TCH failed - PM
alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
Usage Quality of service: Call setup.

Fault finding.
Optimization.
Network planning.
Assignment to TCH.
Key statistics: TCH_BLOCKING_RATE,
TCH_BLOCKING_RATE_OUT_ZONE and
TCH_MEAN_ARRIVAL_RATE.
4-28 68P02901W56-T
Jan 2010
Basis Cell.
Type Counter.
Alarm Major.
68P02901W56-T 4-29
Jan 2010
ALLOC_TCH_HR Chapter 4: Cell statistics
ALLOC_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic tracks the number of successful half rate AMR and/or GSM TCH allocations within
a cell for both call originations and hand ins.
Pegging
This statistic pegs for successful half rate AMR and/or GSM TCH allocations within a cell as a
result of a call establishment or hand in attempt:
incoming directed retries.
• Successful allocation due to intra-cell hand in.
• Successful allocation due to incoming inter-cell/intra-cell hand in.
• Successful allocation due to incoming inter-BSS hand in.
Analysis
This statistic can be used for trend analysis of half rate AMR and/or GSM TCH allocations.
Reference None.
Usage Quality of service monitoring (Call setup), Network planning and Ladder
(Intra-BSS handover, Inter-BSS handover, Intra-cell handover and
Assignment to TCH).
Basis Cell.
Type Counter.
4-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ALLOC_TCH_INNER_ZONE
ALLOC_TCH_INNER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH_INNER_ZONE statistic tracks the number of successful TCH allocations

within a cell for both call originations and hand-ins for inner zone.
Pegging
This statistic pegs for successful TCH allocations within a cell inner zone as a result of a call
establishment or hand-in attempt:
directed retries.
• Successful allocation due to intra-cell hand-in.
• Successful allocation due to inter-cell/intra-cell hand-in.
• Successful allocation due to inter-BSS hand-in.
This statistic pegs before the transmission of the assignment/handover command to the MS
and, therefore, does not take into account the success or failure of the assignment/hand-in
from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations.

Network planning.
Ladder: Intra-BSS handover, Inter-BSS handover, Intra-cell handover, and
Assignment to TCH.
Key statistics: CELL_TCH_ALLOCATIONS,
CELL_TCH_ASSIGNMENTS, TCH_BLOCKING_RATE,
TCH_BLOCKING_RATE_OUT_ZONE, TCH_MEAN_ARRIVAL_RATE,
TCH_MEAN_HOLDING_TIME and TCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.
68P02901W56-T 4-31
Jan 2010
ALLOC_TCH_SIG Chapter 4: Cell statistics
ALLOC_TCH_SIG
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH_SIG statistic counts the number of successful TCH allocations within a cell
for both call originations and hand-ins when the FCS call is using Signaling TCH at Immediate
Assignment. Hand-in allocations include intra–cell, incoming intra–BSS, incoming inter–BSS,
and incoming directed retry scenarios.
Pegging
This statistic is pegged before the transmission of the Assignment or Handover Command
message to the MS, and therefore does not represent a count of TCH seizures by the MS from
the RF perspective.
Analysis
Reference None.

Network planning.
Assignment to TCH.
Basis Cell.
Type Counter.
4-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AMR_DECREASE_THRESH_ADJUST
AMR_DECREASE_THRESH_ADJUST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that

the BSS MS monitor decreases the C/I codec mode adaptation thresholds for AMR calls on a
per-cell basis.
Pegging
This statistic pegs each time that the BSS MS monitor decreases the downlink codec mode
adaptation thresholds due to inaccurate C/I estimation by the MS.
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-T 4-33
Jan 2010
AMR_FR_DL_ADAPTATION Chapter 4: Cell statistics
AMR_FR_DL_ADAPTATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_FR_DL_ADAPTATION statistic keeps a count of the number of times the codec mode
is adapted on the downlink of full-rate AMR calls on a per-cell basis.
NOTE
There are up to four codecs in the Active Codec Set (ACS) and the format of this
statistic allows for these. The codecs are referenced sequentially from the lowest
speech coding rate to the highest. The lowest speech coding rate is called the 1st
codec. If there are less than four codecs in the ACS, the higher bit rates are not
valid and contain the value zero.
Table 4-2 AMR_FR_DL_ADAPTATION bins
Bin Description
0 AMR full-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR full-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR full-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR full-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR full-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR full-rate DL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time a specific codec mode is adapted on the downlink of full-rate
AMR calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-34 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AMR_FR_DL_CODEC_MODE_USAGE
AMR_FR_DL_CODEC_MODE_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_FR_DL_CODEC_MODE_USAGE statistic keeps a count of each AMR full-rate codec

mode used on the downlink of AMR full-rate calls on a per-cell basis.
Table 4-3 AMR_FR_DL_CODEC_MODE_USAGE bins
Bin Description
0 AMR full-rate DL codec mode usage of AFS 12.2 kbps.
NOTE
The value of each bin and the total value is scaled down by dividing it by 500 in
the pegging process RSS to allow the UWORD variable type to store the maximum
value. The value of this statistic displayed in the OMC should be multiplied by 500
manually to get the actual value.
Pegging
This statistic pegs each time that a specific codec mode is used on the downlink of full-rate
AMR calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-35
Jan 2010
AMR_FR_UL_ADAPTATION Chapter 4: Cell statistics
AMR_FR_UL_ADAPTATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_FR_UL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the uplink of full-rate AMR calls on a per-cell basis.
NOTE
Table 4-4 details the AMR_FR_UL_ADAPTATION bins:

Table 4-4 AMR_FR_UL_ADAPTATION bins
Bin Description
0 AMR full-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR full-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR full-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR full-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR full-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR full-rate UL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time a specific codec mode is adapted on the uplink of full-rate AMR
calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AMR_FR_UL_CODEC_MODE_USAGE
AMR_FR_UL_CODEC_MODE_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_FR_UL_CODEC_MODE_USAGE statistic keeps a count of each AMR full-rate codec

mode used on the uplink of AMR full-rate calls on a per-cell basis.
Table 4-5 AMR_FR_UL_CODEC_MODE_USAGE bins
Bin Description
0 AMR full-rate UL codec mode usage of AFS 12.2 KBPs.
1 AMR full-rate UL codec mode usage of AFS 10.2 kbps.
NOTE
Pegging
This statistic pegs each time a specific codec mode is used on the uplink of full-rate AMR calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-37
Jan 2010
AMR_HR_DL_ADAPTATION Chapter 4: Cell statistics
AMR_HR_DL_ADAPTATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_HR_DL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the downlink of half-rate AMR calls on a per-cell basis.
NOTE
Table 4-6 AMR_HR_DL_ADAPTATION bins
Bin Description
0 AMR half-rate DL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR half-rate DL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR half-rate DL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR half-rate DL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR half-rate DL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR half-rate DL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time a specific codec mode is adapted on the downlink of half-rate
AMR calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AMR_HR_DL_CODEC_MODE_USAGE
AMR_HR_DL_CODEC_MODE_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_HR_DL_CODEC_MODE_USAGE statistic keeps a count of each AMR half-rate codec

mode used on the downlink of AMR half-rate calls on a per-cell basis.
Table 4-7 AMR_HR_DL_CODEC_MODE_USAGE bins
Bin Description
0 AMR half-rate DL codec mode usage of AFS 7.95 kbps.
NOTE
Pegging
This statistic pegs each time a specific codec mode is used on the downlink of half-rate AMR
calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-39
Jan 2010
AMR_HR_UL_ADAPTATION Chapter 4: Cell statistics
AMR_HR_UL_ADAPTATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_HR_UL_ADAPTATION statistic keeps a count of the number of times that the codec
mode is adapted on the uplink of half-rate AMR calls on a per-cell basis.
NOTE
Table 4-8 AMR_HR_UL_ADAPTATION bins
Bin Description
0 AMR half-rate UL codec mode usage adaptation from 1st to 2nd codec mode.
1 AMR half-rate UL codec mode usage adaptation from 2nd to 3rd codec mode.
2 AMR half-rate UL codec mode usage adaptation from 3rd to 4th codec mode.
3 AMR half-rate UL codec mode usage adaptation from 2nd to 1st codec mode.
4 AMR half-rate UL codec mode usage adaptation from 3rd to 2nd codec mode.
5 AMR half-rate UL codec mode usage adaptation from 4th to 3rd codec mode.
Pegging
This statistic pegs each time a specific codec mode is adapted on the uplink of half-rate AMR
calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-40 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AMR_HR_UL_CODEC_MODE_USAGE
AMR_HR_UL_CODEC_MODE_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_HR_UL_CODEC_MODE_USAGE statistic keeps a count of each AMR half-rate codec

mode used on the uplink of AMR half-rate calls on a per-cell basis.
Table 4-9 AMR_HR_UL_CODEC_MODE_USAGE bins
Bin Description
0 AMR half-rate UL codec mode usage of AFS 7.95 kbps.
NOTE
Pegging
This statistic pegs each time a specific codec mode is used on the uplink of half-rate AMR calls.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-41
Jan 2010
AMR_INCREASE_THRESH_ADJUST Chapter 4: Cell statistics
AMR_INCREASE_THRESH_ADJUST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AMR_INCREASE_THRESH_ADJUST statistic keeps a count of the number of times that

the BSS MS monitor increases the C/I codec mode adaptation thresholds for AMR calls on a
per-cell basis.
Pegging
This statistic pegs each time that the BSS MS monitor increases the downlink codec mode
adaptation thresholds due to inaccurate C/I estimation by the MS.
Analysis
Reference None.
Basis Cell.
Type Counter.
4-42 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ASSIGNMENT_REDIRECTION
ASSIGNMENT_REDIRECTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ASSIGNMENT_REDIRECTION statistic tracks the number of times a call assignment is

redirected to another cell.
Table 4-10 ASSIGNMENT_REDIRECTION bins

0 DIRECTED_RETRY Tracks the handovers that were executed as the result of
standard directed retry.
1 DURING_ASSIGNMENTS Tracks the handovers that occurred during the assignment
for normal radio reasons.
2 MULTIBAND_BAND Tracks the handovers that were executed as the result of
multiband reassign procedure.
Pegging
This statistic pegs whenever a call assignment is redirected to another cell.
Analysis
This statistic can be used for trend analysis of the number of successful internal and external
handovers performed as the result of standard directed retry mechanisms.
Reference GSM 8.08, 4.90.

GSM 3.09, 4.50.
GSM 4.08, 4.11.0.
Usage Quality of service, Network planning and Key statistics
(CALL_SETUP_SUCCESS_RATE, TCH_MEAN_HOLDING_TIME and
TCH_RF_LOSS_RATE).
Basis Cell.
Type Counter array.
68P02901W56-T 4-43
Jan 2010
AVAILABLE_SDCCH Chapter 4: Cell statistics
AVAILABLE_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AVAILABLE_SDCCH statistic tracks the average number of available SDCCHs that are
in use or available for use.
The SDCCH is available when its administrative state is unlocked or shutting down and its
operational state is enabled. The SDCCH is unavailable when its administrative state is locked
and its operational state is disabled.
Pegging
If a channel does not fall into one of the above five interference band categories, the channel is
considered to be in interference band 6, and it is neither used for allocation nor be counted
as AVAILABLE_SDCCH.
The AVAILABLE_SDCCH statistic tracks the number of the available SDCCH channels and
pegs whenever a change in the SDCCH availability is detected. This could occur due to SDCCH
channel reconfiguration, DRI state transition, or high interference level on the SDCCH time
slots. Each one of these causes certain SDCCH channels to become unusable for a fixed period.
In CRM, all idle channels (SDCCH, TCH) are categorized by the interference bands from band 1
to band 5. RSS determines the interference bands of all idle channels accordingly and sends
RF Resource Indication Received messages to the CRM periodically. If a channel does not fall
into one of the above five interference band categories, the channel is considered to be in
interference band 6, and it is neither used for allocation nor be counted as AVAILABLE_SDCCH.
The statistic pegs whenever there is a change in the channel configuration for any channel in
the cell (if the number of TCHs has not changed, it is pegged with the same value as before).
This statistic pegs when a change in SDCCH availability is detected.
NOTE
In CRM all idle channels, for instance SDCCH, TCH are categorized by the
interference bands from band 1 to band 5. RSS determines the interference bands of
all idle channels accordingly and sends RF Resource Indication Received messages to
the CRM periodically. If a channel does not fall into one of the above five interference
band categories, the channel is considered to be in interference band 6, and it is
neither used for allocation nor counted as AVAILABLE_SDCCH.
4-44 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of SDCCH availability.
By comparing the number of available SDCCHs to the total number of SDCCHs in a system, a
percentage of utilization can be calculated. An analysis of the utilization information can be
used to determine the requirement for additional resources before problems occur.
Reference GSM 12.04, 4.2.1, B.2.1.21

Usage Congestion and Network planning.
Basis Cell.
Type Gauge.
68P02901W56-T 4-45
Jan 2010
AVAILABLE_TCH Chapter 4: Cell statistics
AVAILABLE_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AVAILABLE_TCH statistic tracks the mean and MAX number of available TCHs that are
in use or available for use.
The TCH is available when its administrative state is unlocked or shutting down, and its
operational state is enabled. The TCH is unavailable when its administrative state is locked
This statistic is modified to exclude all PDTCHs, both switchable and reserved unless the
switchable PDTCH is configured as TCH.
This statistic is obtained by maintaining the current and total number of available TCH and the
amount of time each TCH is available over the statistical period. The corresponding mean
and maximum number of TCH available are then computed. The TCH is available when its
administrative state is unlocked or shutting down, and the operational state is enabled. It is
unavailable when its administrative state changes to locked or the operational state changes to
disabled. The available number of TCH is then incremented or decremented when there is a
change in TCH states as described earlier.
This statistic counts only those traffic channels, which are configured as TCH at the time of
measurement. Switchable PDTCHs are included only if they are configured as TCHs.
NOTE
The value of this statistic may decrease because the idle TCH may be configured as
the additional switchable PDTCH.
Pegging
the cell (if the number of TCHs has not changed, it is pegged with the same value as before).
This statistic pegs when a change in TCH availability is detected.
Analysis
This statistic can be used for trend analysis of TCH availability.
4-46 68P02901W56-T
Jan 2010
By comparing the number of available TCHs to the total number of TCHs in a system, a
percentage of utilization can be calculated. An analysis of the utilization information can be
used to determine the requirement for additional resources before problems occur.
Reference GSM 12.04, 4.2.1, B.2.1.10

Usage Congestion, Network planning, and Key statistics (BSS_AVAILABILITY and
MEAN_TCH_BUSY_TIME).
Basis Cell.
Type Gauge.
68P02901W56-T 4-47
Jan 2010
AVAILABLE_TCH_DCS1800 Chapter 4: Cell statistics
AVAILABLE_TCH_DCS1800
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AVAILABLE_TCH_DCS1800 statistic tracks the mean and MAX number of available half
rate and full rate DCS1800 capable TCHs that are in use or available for use.
NOTE
The AVAILABLE_TCH_DCS1800 statistic tracks half rate TCHs in the same manner
as full rate TCHs.
The TCH is available when its administrative state is unlocked or shutting down and its
This statistic is modified to exclude all PDTCHs.
and maximum number of available TCH are then computed. The TCH is available when its
Pegging
The statistic pegs whenever there is a change in the channel configuration for any DCS1800
channel in the cell. This shall cover channel allocation including reconfiguration to/from a
generic timeslot for assignment/clearing of a full rate call when half rate (GSM and/or AMR)
is in use.
4-48 68P02901W56-T
Jan 2010
Analysis
AVAILABLE_TCH_DCS1800 is used with BUSY_TCH_DCS1800 to track DCS1800 layer

utilization as a function of maximum available capacity.
Reference None.
Usage This statistic tracks the mean and maximum number of available
DCS1800 TCHs that are in use or available for use within a cell.
Basis Cell.
Type Gauge.
68P02901W56-T 4-49
Jan 2010
AVAILABLE_TCH_EGSM Chapter 4: Cell statistics
AVAILABLE_TCH_EGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AVAILABLE_TCH_EGSM statistic tracks the mean and MAX number of available half rate
and full rate EGSM capable TCHs that are in use or available for use.
NOTE
AVAILABLE_TCH_EGSM tracks half rate TCHs in the same manner as full rate TCHs.
Pegging
The statistic pegs whenever there is a change in the channel configuration for any EGSM
channel in the cell. This covers channel allocation including reconfiguration to/from a generic
timeslot for assignment/clearing of a full rate call when half rate (GSM and/or AMR) is in use.
NOTE
An idle half rate capable TCH counts as two available resources.
4-50 68P02901W56-T
Jan 2010
Analysis
AVAILABLE_TCH_EGSM is used with BUSY_TCH_EGSM to track EGSM layer utilization as a

function of maximum available capacity.
Reference None.
Usage This statistic tracks the mean and maximum number of available EGSM
TCHs that are in use or available for use within a cell.
Basis Cell.
Type Gauge.
68P02901W56-T 4-51
Jan 2010
AVAILABLE_TCH_HR Chapter 4: Cell statistics
AVAILABLE_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or GSM
TCH channels in use or available to be used within the cell.
This statistic is modified to exclude all PDTCHs.
Pegging
The statistic pegs whenever there is a change in the half rate AMR and/or GSM channel
configuration in the cell (if the number of TCHs has not changed, it is pegged with the same
value as before).
NOTE
An idle generic timeslot is counted as one available full rate channel and two available
half rate channels.
Analysis
Reference None.
Usage Radio resource allocation, Quality of service monitoring, Network
planning, and Service retain ability.
Basis Cell.
Type Gauge statistic.
4-52 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AVAILABLE_TCH_PGSM
AVAILABLE_TCH_PGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AVAILABLE_TCH_PGSM statistic tracks the mean and MAX number of available half rate
and full rate PGSM capable TCHs that are in use or available.
NOTE
AVAILABLE_TCH_PGSM tracks half rate TCHs in the same manner as full rate TCHs.
administrative state is unlocked or shutting down and the operational state is enabled. The
TCH is unavailable when its administrative state changes to locked or the operational state
changes to disabled. The available number of TCH is then incremented or decremented when
there is a change in TCH states as described earlier.
Pegging
The statistic pegs whenever there is a change in the channel configuration for any PGSM
channel in the cell. This covers channel allocation including reconfiguration to/from a generic
timeslot for assignment/clearing of a full rate call when half rate (GSM and/or AMR) is in use.
NOTE
An idle half rate capable TCH counts as two available resources.
68P02901W56-T 4-53
Jan 2010
Analysis
AVAILABLE_TCH_PGSM is used with BUSY_TCH_PGSM to track PGSM layer utilization

as a function of maximum available capacity.
Reference None.
Usage This statistic tracks the mean and maximum number of available PGSM TCHs
that are in use or available for use within a cell.
Basis Cell.
Type Gauge.
4-54 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BAD_HO_REFNUM_MS
BAD_HO_REFNUM_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BAD_HO_REFNUM_MS statistic tracks the number of times an MS has accessed a channel
with a Handover Reference Number that the BSS was not expecting.
Pegging
This statistic is pegged once for each time an MS has accessed a channel with a Handover
Reference Number that the BSS was not expecting. This field is a non formatted random
number. The BSS compares only what it received with what it expected. For example, potentially
up to four times for each logical handover, detect it for the SDCCH processed at the BSS.
The MS continues to attempt access until a good Handover Reference Number is received,
therefore, the handover can be successful and the statistic pegs. This statistic pegs if the
handover fails and recovers, or fails and loses the MS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of MS
accesses of channels with Handover Reference Numbers that the BSS was not expecting that
are acceptable in normal system operations.
High values reported for this statistic are not because a handover access meant for one cell
can be detected by another. But because the channel at the target cell is susceptible for
detection during the time between the channel activation and when the MS arrives. This is like
Phantom RACHs.
If the specified threshold is exceeded, the 19. CELL: Bad HO reference numbers from the
MS - PM alarm is generated. Refer to the manual Maintenance Information: Alarm Handling at
Reference GSM 4.08, 3.8.0, 3.4.4.2.1, 3.4.4.2.2 and 9.1.13.

Usage Handover and Fault finding.
Basis Cell.
Type Counter.
Alarm Warning.
68P02901W56-T 4-55
Jan 2010
BUSY_SDCCH Chapter 4: Cell statistics
BUSY_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_SDCCH statistic tracks the number of SDCCHs allocated during an interval.
This is a weighted distribution statistic and produces a mean value indicating the average
number of SDCCHs in use during the interval.
The bin ranges may be changed using the chg_stat_prop command. The default bin ranges for
the BUSY_SDCCH statistic are shown in Table 4-11.
This statistic is affected by phantom RACHs. For more information refer Phantom RACHs
on page 20-7 .
Table 4-11 Default bin ranges for BUSY_SDCCH
Bin Range
0 0 - 0
1 1 - 2
2 3 - 4
3 5 - 6
4 7 - 8
5 9 - 10
6 11 - 12
7 13 - 14
8 15 - 16
9 17 - 400
Pegging
The individual bin values are incremented by the length of time that the number of allocated
SDCCHs fall within the bin range of values. Bin values are pegged each time an SDCCH is
allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are pegged.
4-56 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of the amount of RF signaling traffic in the cell
SDCCHs. An analysis of the allocation information can be used to determine the requirement
for additional resources before problems occur.
Reference GSM 12.04, 3.1.0, B.1.3.2.

Usage RF loss, Congestion, Quality of service monitoring, Network planning,
Optimization and Key statistics (SDCCH_MEAN_HOLDING_TIME and
SDCCH _TRAFFIC_CARRIED).
Basis Cell.
Type Weighted distribution.
68P02901W56-T 4-57
Jan 2010
BUSY_TCH Chapter 4: Cell statistics
BUSY_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_TCH statistic tracks the number of full rate and half rate TCHs allocated during
an interval.
This is a weighted distribution statistic and produces a mean value indicating the average
number of TCHs in use during the interval. It is an indication of the average capacity for
additional traffic in the cell. This statistic includes TCHs used as a Dedicated Control CHannel
(DCCH) in immediate assignment mode. The BUSY_TCH time includes the guard time (the time
allowed between ending a call and being allowed to start another). Since the channel is not
available to be used again until the guard timer expires, it is not considered to be free until then.
the BUSY_TCH statistic are shown in Table 4-12.
Table 4-12 Default bin ranges for BUSY_TCH
Bin Range
0 0 - 0
1 1 - 2
2 3 - 4
3 5 - 6
4 7 - 8
5 9 - 10
6 11 - 12
7 13 - 14
8 15 - 16
9 17 - 400
Pegging
The individual bin values are incremented by the length of time that the number of allocated
full rate and half rate TCHs fall within the bin range of values. Bin values peg each time a
TCH is allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are pegged.
4-58 68P02901W56-T
Jan 2010
Analysis
The value of this statistic is not dependent on the number of transceivers. Rather it is dependent
on the number (however large) of simultaneously busy channels. The only dependence on the
number of transceivers is that the value reported may be larger if more traffic channels are
used simultaneously.
TCHs. An analysis of the allocation information can be used to determine the requirement for
additional resources before problems occur.
Reference GSM 12.04, 3.1.0, B1.1.1. GSM 4.08, 3.8.0, 3.3.1.2.1.
Usage RF loss, Congestion, Quality of service monitoring, Network planning,

Optimization and Key statistics (MEAN_TCH_BUSY_TIME,
TCH_MEAN_HOLDING_TIME and TCH_TRAFFIC_CARRIED).
Basis Cell.
68P02901W56-T 4-59
Jan 2010
BUSY_TCH_CARR Chapter 4: Cell statistics
BUSY_TCH_CARR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_TCH_CARR statistic tracks the number of full rate and half rate TCHs allocated
during an interval.
This is a gauge statistic and produces a mean value indicating the average number of TCHs in
use during the interval. It is an indication of the average capacity for additional traffic in the
cell. This statistic includes TCHs used as a Dedicated Control CHannel (DCCH) in immediate
assignment mode. The BUSY_TCH_CARR time includes the guard time (the time allowed
between ending a call and being allowed to start another). Since the channel is not available to
be used again until the guard timer expires, it is not considered to be free until then.
Pegging
This statistic pegs when a change in the number of full rate and half rate TCHs in use are
detected.
Analysis

Usage Congestion, Network planning, Optimization and Key statistic
(TCH_CARRIER_MEAN_HOLDING_TIME).
Basis Carrier.
Type Gauge.
4-60 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BUSY_TCH_DCS1800
BUSY_TCH_DCS1800
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
It is used with AVAILABLE_TCH_DCS1800 to give an indication of the average utilization of the

DCS1800 band. This is used in comparison with the EGSM and DCS1800 utilization figures
to indicate band related traffic distribution within the cell for optimization of the IMRM band
weights.
Pegging
The BUSY_TCH_DCS1800 statistic pegs each time a DCS1800 capable TCH is allocated or
de-allocated. This statistic pegs for both allocation and de-allocation of full rate and half rate
TCHs.
Analysis
The AMR Half Rate and GSM Half Rate channel modes are included when pegging this statistic.
Reference None.
Usage This statistic tracks the mean and maximum number of DCS1800 traffic
channels allocated during an interval.
Basis Cell.
Type Gauge.
68P02901W56-T 4-61
Jan 2010
BUSY_TCH_EGSM Chapter 4: Cell statistics
BUSY_TCH_EGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
It is used with AVAILABLE_TCH_EGSM to give an indication of the average utilization of the

EGSM band. This is used in comparison with the EGSM and DCS1800 utilization figures to
indicate band related traffic distribution within the cell for optimization of the IMRM band
weights.
Pegging
The BUSY_TCH_EGSM statistic pegs each time an EGSM capable TCH is allocated or
de-allocated. This statistic pegs for both allocation and de-allocation of full rate and half rate
TCHs.
Analysis
Reference None.
Usage This statistic tracks the mean and maximum number of EGSM traffic channels
allocated during an interval.
Basis Cell.
Type Gauge.
4-62 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BUSY_TCH_HR
BUSY_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or
GSM TCH channels in use.
Pegging
This statistic is updated each time an allocation or de-allocation of a half rate AMR and/or
GSM TCH channel occurs.
Analysis
Reference None.
Usage Radio resource allocation, Quality of service monitoring,
Network planning, Service retain ability and Key statistic
(TCH_MEAN_HOLDING_TIME).
Basis Cell.
68P02901W56-T 4-63
Jan 2010
BUSY_TCH_PGSM Chapter 4: Cell statistics
BUSY_TCH_PGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
It is used with AVAILABLE_TCH_PGSM to give an indication of the average utilization of the

PGSM band. This is used in comparison with the EGSM and DCS1800 utilization figures to
indicate band related traffic distribution within the cell for optimization of the IMRM band
weights.
Pegging
The BUSY_TCH_PGSM statistic pegs each time a PGSM capable TCH is allocated or de-allocated.
This statistic pegs for both allocation and de-allocation of full rate and half rate TCHs.
Analysis
Reference None.
Usage This statistic tracks the mean and maximum number of PGSM traffic
channels allocated during an interval.
Basis Cell.
Type Gauge.
4-64 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SP_VERS_DOWNGRADE_MONITOR
CALL_SP_VERS_DOWNGRADE_MONITOR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of call rejects and call downgrades due to not supporting the
requested speech versions.
The statistic keeps a count of the number of times that the codec mode was downgraded for
EFR, HR AMR FR AMR and GSM HR calls on a per-BSS basis.
Table 4-13 CALL_SP_VERS_DOWNGRADE_MONITOR bins (0–2)

0 EFR_REQUEST_DOWNGRADE Pegged when the call is downgraded due to CIC
capabilities: Assignment request for or including
EFRH and over request for or including EFRIn-call
modification request for or including EFR.
1 AMR_FR_CALL_DOWNGRADE Pegged when the full-rate AMR call is downgraded.
2 AMR_HR_CALL_DOWNGRADE Pegged when the half-rate AMR call is downgraded.
With the Half Rate feature unrestricted, the statistic also keeps a count of the number of times
that the codec mode was downgraded for GSM HR calls on a per-BSS basis. The additional
bin is as follows:
Table 4-14 CALL_SP_VERS_DOWNGRADE_MONITOR bins (3)

3 GSM_HR_CALL_DOWNGRADE Pegged when the half-rate GSM call is downgraded.
Pegging
The bin corresponding to the cause of the call downgrade or reject is as indicated in description
earlier.
68P02901W56-T 4-65
Jan 2010
Analysis
This statistic can be used for analysis of non-support of requested speech versions. No alarms
are raised by this statistic.
Reference GSM 08.08

planning, and Optimization.
Basis BSS.
Type Counter array.
4-66 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALLS_QUEUED
CALLS_QUEUED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALLS_QUEUED statistic tracks the Assignment Requests and Handover Requests that
are queued during an interval. If queuing has been allowed and no resources exist, the CRM
queues an assignment request and informs the RRSM with a force queue message.
Pegging
This statistic pegs when queuing is enabled for an assignment request and available queue
blocks are used to queue the call successfully. The bins pegged according to the assignment
request type are as shown in Table 4-15.
Table 4-15 CALLS_QUEUED bins

0 ASSIGN_REQ The number of ASSIGNMENT REQUEST messages that are queued.
1 HO_REQ The number of HANDOVER REQUEST messages that are queued.
Analysis
calls queued for each cell on the BSS that are acceptable in normal system operations.
If the specified threshold is exceeded, the 20. CELL: Number of calls queued - PM alarm
is generated. Refer to the manual Maintenance Information: Alarm Handling at the OMC-R
Reference GSM 3.01, 3.1.1, 4.1.

GSM 4.08, 3.8.0, 5.2.1.1.10 and 5.2.2.8.
GSM 8.08, 3.9.2, 3.1.17.
Usage Quality of service monitoring (queuing delay), Network planning,
Optimization, Fault finding, and Ladder (BSS initiated call clearing).
Basis Cell.
Type Counter array.
Alarm Warning.
68P02901W56-T 4-67
Jan 2010
CHAN_REQ_CAUSE_ATMPT Chapter 4: Cell statistics
CHAN_REQ_CAUSE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_REQ_CAUSE_ATMPT statistic tracks the number of Channel Request messages

received by the network from an MS (or LMU) by cause. A total count of all successful results
is also tracked.
Table 4-16 CHAN_REQ_CAUSE_ATMPT bins

0 ORIGINATING_CALL Number of MS requests for originating service.
1 EMERGENCY_CALL Number of MS requests for emergency call service.
2 CM_REESTABLISH Number of failed MS requests for service in which the call
recovered to the original cell.
3 LOCATION_UPDATE Number of MS location update requests.
4 PAGE_RESPONSE Number of MS page request responses.
5 LMU_ESTABLISHMENT Number of channel requests from Location Measurement
Unit devices. (An LMU is a special device used for certain
kinds of Location Services).
Pegging
This statistic pegs the cause of each Channel Request message received by the network from
an MS.
Analysis
This statistic can be used for trend analysis of the type of Channel Request messages that are
received from MSs. This information can be used to determine the requirement for additional
resources before problems occur.
Reference GSM 12.04, 4.21, B.2.1.6.

GSM 4.08, v4.15.0, 9.1.8.
and Key statistic (MEAN_ARRIVAL_TIME_BETWEEN_CALLS).
Basis Cell.
Type Counter array.
4-68 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CHAN_REQ_MS_BLK
CHAN_REQ_MS_BLK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_REQ_MS_BLK statistic tracks the number of times an MS has been refused
access to a channel.
An Immediate Assignment Reject message was sent to the MS on CCCH. This event indicates
that the MS has requested allocation of a dedicated channel, and the network has responded by
refusing immediate access to a channel. Pegging of this counter indicates that there are no
channels available for assignment in the cell. The counter pegs once for each Channel Request
Reference in the message announcing the blocking. The cell is therefore fully used, and it is not
possible to hand over existing calls into the cell or set up new calls in the cell.
If adjacent cells that are candidates for handover are unable to provide the MS with a radio
resource, it is impossible for the MS to initiate a call. Handover of calls may be prevented.
This results in call blocking and loss.
Pegging
This statistic pegs when an Immediate Assignment Reject message is sent to the MS on CCCH
thus indicating that there are no channels available for assignment in the cell.
Analysis
This statistic can be used for trend analysis of the number of times channel access has been
denied. This information can be used to determine the requirement for additional resources.
Reference GSM 4.08, 3.8.0, 4.5.1.1,8 and 9.1.27a

Usage Radio resource and allocation.
Fault finding.
Network planning.
Quality of service monitoring: Call setup.
Ladder: Immediate assignment blocked
Key statistic:
SUCCESS_IMMED_ASSIGN_PROC.
Basis Cell.
Type Counter.
NOTE
68P02901W56-T 4-69
Jan 2010
CIPHER_MODE_FAIL Chapter 4: Cell statistics
CIPHER_MODE_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CIPHER_MODE_FAIL statistic pegs when an internal Motorola-defined timer in the BSS
expires to indicate that the MS did not respond to the Cipher Mode Command message with the
Cipher Mode Complete message within the allowable time period or responded improperly. It
indicates that the MS probably did not switch correctly into encrypted communication mode
when commanded to do so.
Pegging
This statistic pegs when the MS fails to respond to a Cipher Mode Command from the BSS.
Analysis
times that MS failures to respond to BSS Cipher Mode Command messages are acceptable in
normal system operations.
If the specified threshold is exceeded, the 6. CELL: Cipher mode command from MSC failed
Reference GSM 4.08, 3.8.0,8 and 9.1.9.

GSM 8.08, 3.9.2, 3.1.14 and 3.2.1.30.
Usage Classmark update and cipher mode.
Quality of service monitoring.
Fault finding.
Ladder: BSS initiated call clearing.
Basis Cell.
Type Counter.
Alarm Minor.
4-70 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CLASSMK_UPDATE_FAIL
CLASSMK_UPDATE_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CLASSMK_UPDATE_FAIL statistic tracks the number of classmark updates containing

errors. The classmark update procedure allows the MS to inform the network of a change to
its classmark.
Pegging
This statistic pegs when the validation of the Classmark Update message from the MS fails.
Analysis
classmark updates containing errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. CELL: Class-mark update from MS protocol
Reference GSM 4.08, 3.8.0,8 and 10.5.1.5-6.

GSM 8.08, 3.9.2, 3.1.13 and 3.2.1.29.
Usage Classmark update and cipher mode.
Fault finding.
Basis Cell.
Type Counter.
Alarm Minor.
68P02901W56-T 4-71
Jan 2010
CLR_CMD_FROM_MSC Chapter 4: Cell statistics
CLR_CMD_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commands received
from the MSC for SDCCH and TCH resources thereby allowing the analysis of dropped calls.
Pegging
This statistic pegs when a Clear command is received from the MSC.
Table 4-17 CLR_CMD_FROM_MSC bins

0 CLR_CMD_FROM_MSC_SD Counts the number of clear commands received from
the MSC for an SDCCH.
1 CLR_CMD_FROM_MSC_FR Counts the number of clear commands received from
the MSC for a Full Rate TCH.
2 CLR_CMD_FROM_MSC_HR Counts the number of clear commands received from

the MSC for a Half Rate TCH.
Analysis
This statistic can be used for trend analysis of the number of Clear commands received from the
MSC. This information can be used to identify and correct problems before they become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.
Usage Radio resource allocation.
Fault finding.
Network planning.
Basis Cell.
Type Counter array.
4-72 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CLR_REQ_TO_MSC
CLR_REQ_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CLR_REQ_TO_MSC statistic separately tracks the number of Clear Request messages sent
to the MSC for SDCCH and TCH resources.
Generating
The Clear Request message may be generated due to one of the following:
• No radio resources available to allocate from the BSS, call queuing is enabled, and the
maximum call delay has been exceeded.
• Radio interface message failure.
• Protocol error.
• Ciphering algorithm not supported.
Sending
All Clear Requests are sent per GSM 8.08 specifications. The Clear Request messages are sent to
the MSC because of radio channel failure or a timeout during a procedure. In this case a timeout
means that a required message was not received during a procedure. The procedures are:
• Immediate Assignment.
• Assignment.
• Channel Mode Modify.
• Ciphering.
• Handover - Intra-cell, Inter-cell, and External.
Pegging
This statistic pegs when the BSS sends a Clear Request message to the MSC.
CLR_REQ_TO_MSC is pegged for numerous reasons related to timer expiry. It is a mix of both
the GSM and internal Motorola timers. Normal release of a call either from an MS or Land site
never causes it to be pegged. A call must have at least been assigned to an SDCCH or TCH
for this to be pegged. It is not pegged when on an AGCH overload. RF loss is the major cause
of pegging.
68P02901W56-T 4-73
Jan 2010
Table 4-18 CLR_REQ_TO_MSC bins

0 CLR_REQ_TO_MSC_SD Counts the number of clear requests sent to the MSC for
an SDCCH.
1 CLR_REQ_TO_MSC_FR Counts the number of clear requests sent to the MSC for
a Full Rate TCH.
2 CLR_REQ_TO_MSC_HR Counts the number of clear requests sent to the MSC for a
Half Rate TCH.
CLR_REQ_TO_MSC is not pegged when the CONN_REFUSED statistic is pegged. However,

there are some cases where CLR_REQ_TO_MSC is pegged and no associated statistic is
pegged. For example, if during an assignment the BSS determines that the cell is barred,
CLR_REQ_TO_MSC is pegged but no associated statistic is pegged.
Analysis
This statistic can be used for trend analysis of the number of Clear Request messages sent to the
MSC. This information can be used to identify and correct problems before they become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2, 3.2.1.20. and 3.1.9.2.
Fault finding.
Network planning.
Ladder: BSS initiated call clearing, handover (Intra-cell) fail/lost,
handover (Intra-BSS) fail/lost.
NOTE
Adding up the statistics in the ladder diagrams is not total
CLR_REQ_TO_MSC.
Basis Cell.
Type Counter array.
4-74 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CLR_REQ_CALL_SETUP
CLR_REQ_CALL_SETUP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
A Clear Request message is sent to MSC after Assignment Complete or Handover Complete
on traffic channel when the call is dropped. This statistic with four bins records the Clear
request messages sent to MSC in all conditions. The statistic represents the number of calls
dropped in every condition.
Pegging
CLR_REQ_CALL_SETUP is pegged when a Clear Request message is sent to MSC during an

unsuccessful call setup. This statistic has four bins to record the Clear Request message sent to
MSC.
Table 4-19 CLR_REQ_CALL_SETUP bins
Bin Scenario Description

0 CALL_SETUP_PRE_COMPLETE_ SD The number of Clear Request message sent
to MSC for an SDCCH before Assignment
Complete or Handover Complete.
1 CALL_SETUP_PRE_COMPLETE_ The number of Clear Request message sent to
TCH MSC for a TCH/F or TCH/H before Assignment
2 CALL_SETUP_POST_COMPLETE_ The number of Clear Request message sent to
SD MSC for an SDCCH after Handover Complete.
3 CALL_SETUP_POST_COMPLETE_ The number of Clear Request message sent to
TCH MSC for a TCH/F or TCH/H after Assignment
Analysis
This statistic can be used for obtaining the number of dropped calls with respect to the number
of Clear Request messages sent to MSC.
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-75
Jan 2010
CONGEST_EXIST_HO_ATMPT Chapter 4: Cell statistics
CONGEST_EXIST_HO_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONGEST_EXIST_HO_ATMPT statistic tracks the number of attempted inter-cell

handover (internal or external to the BSS) of calls on a TCH due to TCH congestion from the
source cell.
Pegging
This statistic pegs each time a congestion relief handover is attempted. This statistic is pegged
for both internal inter-cell and external handovers.
Analysis
This statistic can be used for trend analysis of the number of internal and external handover
attempts due to TCH congestion from source cells.

GSM 3.09, 4.50.
GSM 4.08, 4.11.0.
Usage Optimization.
Network planning.
Basis Cell.
Type Counter.
4-76 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CONGEST_STAND_HO_ATMPT
CONGEST_STAND_HO_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONGEST_STAND_HO_ATMPT statistic tracks the number of attempted handovers of

an MS due to standard Directed Retry procedure caused by TCH congestion from the source
cell. These inter-cell handovers (internal or external to the BSS) involve changing the channel
mode during the handover.
Pegging
This statistic pegs each time a Directed Retry handover procedure is attempted for both
inter-cell and external handovers.
Analysis
This statistic can be used for trend analysis of the number of attempted internal or external
handovers due to standard Directed Retry mechanisms caused by TCH congestion.

GSM 3.09, 4.50.
GSM 4.08, 4.11.0.
Usage Optimization.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 4-77
Jan 2010
CONN_REFUSED Chapter 4: Cell statistics
CONN_REFUSED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONN_REFUSED statistic tracks the number of SCCP connection refused (CREF)
messages received from the MSC.
Pegging
This statistic pegs when the MSC sends the BSS an SCCP Connection Refused (CREF) message.
The MSC may send an SCCP Connection Refused message in response to a BSS generated SCCP
Connection Request (CR) message, as a result of:
• MS access for a location update.
• MS originated call establishment.
• MS terminated call establishment.
• SMS activity.
• Supplementary service activity.
• IMSI detach.
• Call reestablishment.
For example, if an association exists for the identity of the MS requesting a connection, the
connection request is refused, and this statistic pegs.
Analyze MSC statistics to determine why the CONN_REFUSED statistic is pegged.
NOTE
Some MSCs may generate a Connection Refused Message during a successful IMSI
Detach rather than a Connection Confirm, so a high value for the CONN_REFUSED
statistic cannot indicate a system problem. The MSC performance during IMSI Detach
procedures should be investigated before interpreting the CONN_REFUSED statistic.
4-78 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of the reasons for connections refused from the
MSC. This is an MSC procedure.
Reference GSM 8.06, 3.5.0, 6.1.

GSM 8.08, 3.9.2, 3.1.16.
Usage Originated call and service/connection request.
Optimization.
Network planning.
Ladder: Connection establishment failure.
Basis Cell.
Type Counter.
68P02901W56-T 4-79
Jan 2010
CONN_REQ_TO_MSC Chapter 4: Cell statistics
CONN_REQ_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONN_REQ_TO_MSC statistic tracks the number of connection requests that the BSS
sends to the MSC.
Pegging
The statistic pegs only for connection establishments initiated by the BSS. This message is sent
by the MS when it is requesting set-up of the connections for several types of transactions,
including location updates, connection establishments (including reestablishment on failure,
short message transfer, and supplementary service requests), and paging responses.
Analysis
This statistic can be used for trend analysis of the number of connection requests sent from
the BSS to the MSC.
Reference GSM 8.06, 3.5.0, 6.1.

GSM 8.08, 3.9.2, 3.1.16.
Network planning.
Ladder: Connection establishment successful, connection establishment
failure.
Basis Cell.
Type Counter.
4-80 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CS_PAGING_MSGS_FROM_MSC
CS_PAGING_MSGS_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS_PAGING_MSGS_FROM_MSC statistic tracks the number of received CS paging

request messages on specified pegging point between A interface and Air interface for NOM2
and NOM3.
10 received paging messages represents 1 unit. CS from SGSN is not included.
Pegging
This statistics is pegged when a CS paging request message is received between A interface
and Air interface.
Table 4-20 CS_PAGING_MSGS_FROM_MSC bins
Bin Description
0 number of received paging messages per cell at point 1 on SCCP_Pre MTL-LCF.
1 number of received paging messages per cell at point 2 on SCCP_Pre RSL-LCF.
2 number of received paging messages per cell at point 5 on RRSM.
3 number of received paging messages per cell at point 7 on RSS Abis.
4 number of received paging messages per cell at point 8 on RSS L1.
5 number of discard paging messages due to Cell OOS per cell at point 2 on SCCP_Pre
RSL-LCF.
6 number of discard paging messages due to exceed the limitation defined by
max_pagenum_per_sec.
NOTE
Each unit of bin value stands for 10 received messages, maximum value of each
bin is only 655340.
68P02901W56-T 4-81
Jan 2010
Analysis
This statistic provides mechanism to know the number of paging messages discarded between A
interface and Air interface.
Reference None.
Usage
Basis Cell.
Type Medium counter array.
4-82 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_LLC_DATA_VOLUME
DL_LLC_DATA_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_LLC_DATA_VOLUME statistic counts the volume of downlink LLC data sent on the air
interface per traffic class PDU’s for a given cell per traffic class.
Pegging
The DL_LLC_DATA_VOLUME statistic pegs during a given time interval. The bins represent the
volume of data on the downlink for various class types and ARP values as shown in Table 4-21.
The unit of measurement is 10 Kbytes for bins 0 to 5 and 1 Kbyte for bin 6.
Table 4-21 DL_LLC_DATA_VOLUME bins
Bin Display Name Description

0 DL_LLC_DATA_STREAM Volume of data on the downlink for Streaming.
1 DL_LLC_DATA_VOL_THP1 Volume of data on the downlink for Interactive THP1.
4 DL_LLC_DATA_VOL_BCKGRND Volume of data on the downlink for Background.
5 DL_LLC_DATA_VOL_BEST_EFF Volume of data on the downlink for Best Effort and
PFC_unaware user data local TLLI. Unit size is 10
Kbytes.
6 DL_LLC_DATA_VOL_SIG Volume of data on the downlink for Signaling and
PFC unaware non-local TLLI. Unit size is 1 Kbyte.
Round up on 1 Kbyte modulo upon the monitoring
period expiration.
NOTE
• When ARP is disabled, all volume of LLC is pegged against ARP3.

• When QoS is disabled all volume of LLC is pegged against Best Effort and
Signaling bins. PFC_unaware PFC data is pegged against the Best Effort and
Signaling bins.
• Downlink PAP, SMS and Signalling LLC data is not pegged.
The recommended statistical measurement interval is 30 minutes.
68P02901W56-T 4-83
Jan 2010
Analysis
This statistic is obtained by measuring the volume of downlink LLC data sent on the air
interface per traffic class.
Reference None.
Usage GPRS Quality of Service.
Basis Cell.
4-84 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_LLC_TRANS_TIME
DL_LLC_TRANS_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the cumulative length in the number of 10 seconds and 100 ms units
(depending on the bin) to transmit all DL LLC PDUs for a given cell per traffic class.
Pegging
The DL_LLC_TRANS_TIME statistic pegs during a given time interval. The bins represent the
volume of data on the downlink for various class types and ARP values as shown in Table 4-22.
Table 4-22 DL_LLC_TRANS_TIME bins
Bin Name Description

0 DL_LLC_TRANS_TIME_STREAM LLC transmission time for Streaming.
1 DL_LLC_TRANS_TIME_THP1 LLC transmission time for Interactive
THP1
THP2
THP3
4 DL_LLC_TRANS_TIME_BCKGRND. LLC transmission time for Background
5 DL_LLC_TRANS_TIME_BEST_EFF LLC transmission time for Best Effort
and PFC unaware user data Local TLLI
6 DL_LLC_TRANS_TIME_SIG LLC transmission time for Signaling and
PFC unaware non-local TLLI.
NOTE
• When ARP is disabled, LLC transmission time is pegged against ARP3.

• When QoS is disabled LLC transmission time is pegged against Best Effort and
Signaling bins.
• Downlink PAP and SMS data are not pegged.
68P02901W56-T 4-85
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
4-86 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ER_INTRA_CELL_HO_ATMPT
ER_INTRA_CELL_HO_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ER_INTRA_CELL_HO_ATMPT statistic tracks the number of attempted intra-cell

handovers between normal range and extended range channels in an extended range cell. A
total count of attempted handover is also maintained.
This statistic may be enabled only if the Extended Range Cell feature is unrestricted and
enabled for the cell.
Table 4-23 ER_INTRA_CELL_HO_ATMPT bins
Bin Procedures Description

0 NORM_TO_EXT_HO Number of intra-cell handover attempts from normal range
channels to the extended range channels.
1 EXT_TO_NORM_HO Number of intra-cell handover attempts from the extended
range channels to the normal range channels.
Pegging
This statistic pegs each time a handover is attempted between a normal channel and an
extended channel in an extended range cell.
Analysis
This statistic can be used for trend analysis of the attempted intra-cell handovers between the
normal and extended range channels in an extended range cell. The number of attempted
extended range intra-cell handovers can be used to determine the number of extended range
time slots to configure in an extended range cell.
Reference None.
Usage Quality of service.
Network planning.
Radio resource allocation.
Basis Cell.
Type Counter array.
68P02901W56-T 4-87
Jan 2010
ER_INTRA_CELL_HO_SUC Chapter 4: Cell statistics
ER_INTRA_CELL_HO_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ER_INTRA_CELL_HO_SUC tracks the number of successful intra-cell handovers between

normal range and extended range channels in an extended range cell. The values reported for
this statistic can be used to configure normal and extended range traffic channels in a cell. A
total count of the attempted handover is also maintained.
This statistic may be enabled only if the Extended Range Cell feature is unrestricted and
Table 4-24 ER_INTRA_CELL_HO_SUC bins

0 NORM_TO_EXT_HO Number of successful intra-cell handovers from the normal
range channels to the extended range channels.
1 EXT_TO_NORM_HO Number of successful intra-cell handovers from the extended
range channels to the normal range channels.
Pegging
This statistic pegs each time a handover is successful between a normal channel and an
extended channel in an extended range cell. No other intra_cell handover statistic is pegged
when one of the bins of the ER_INTRA_CELL_HO_SUC statistic is pegged.
Analysis
This statistic can be used for trend analysis of the successful intra-cell handovers between the
normal and extended range channels in an extended range cell. The number of successful
extended range intra-cell handovers can be used to determine the number of extended range
time slots to configure in an extended range cell.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-88 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application FLOW_CONTROL_BARRED
FLOW_CONTROL_BARRED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The FLOW_CONTROL_BARRED statistic tracks the duration for which access classes are
barred as a result of flow control. This statistic gives an indication when flow control actions
have been taken to prevent overload.
Pegging
The statistic duration is started when any of the access classes are barred due to flow control
and stopped when the last access class which was barred due to flow control is unbarred.
Analysis
This statistic can be used for trend analysis of the access classes barred as a result of flow
control.
Usage Quality of Service.

Network Planning.
Optimization.
Basis Cell.
Type Duration (total time in milliseconds).
68P02901W56-T 4-89
Jan 2010
HO_FAIL_NO_RESOURCES Chapter 4: Cell statistics
HO_FAIL_NO_RESOURCES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_FAIL_NO_RESOURCES tracks the number of handover failures due to a lack of

available resources.
Table 4-25 HO_FAIL_NO_RESOURCES bins

0 INTRA_BSS Number of intra-BSS handover failures due to a lack of
1 INTER_BSS Number of inter-BSS handover failures due to a lack of
2 INTRA_CELL Number of intra-cell handover failures due to a lack of
3 INTRA_BSS_DYNET Number of BTS Dynamic Allocation intra-BSS handover
failures due to a lack of available resources.
4 INTER_BSS_DYNET Number of BTS Dynamic Allocation inter-cell handover
5 INTRA_CELL_DYNET Number of BTS Dynamic Allocation intra-cell handover
Pegging
These individual bins are incremented on a per-scenario basis.
Analysis
This statistic can be used for trend analysis of the handover failures due to a lack of resources,
such as:
• The target cell is barred for some reason, such as hardware failure.
• The channel is unavailable; that is there is congestion at the target cell and the queue
timer is expired.
• Incoming handovers are turned off at the target.
• The speech algorithm at the target BSS is not supported by the MS.
• An SCCP connection is not allocated; that is CRM runs out of SCCP numbers.
4-90 68P02901W56-T
Jan 2010
Reference Metric.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-T 4-91
Jan 2010
HO_REQ_FROM_MSC Chapter 4: Cell statistics
HO_REQ_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_REQ_FROM_MSC statistic tracks the number of handover requests for each channel
type and speech version.
Table 4-26 HO_REQ_FROM_MSC bins (0–5)
Bin Procedures
0 PM_FR
1 PM_EFR
2 PM_AMR_FR
3 PM_AMR_HR
4 PM_SDCCH_CHAN
5 PM_Other
When the Half Rate feature is unrestricted, the HO_REQ_FROM_MSC bin table introduces bin
procedure PM_GSM_HR as shown:
Table 4-27 HO_REQ_FROM_MSC bins (6)
Bin Procedure
6 PM_GSM_HR
Pegging
This statistic pegs the handover request for each channel type and speech version in the
appropriate bin.
Analysis
Reference GSM 8.08.

Network planning.
Ladder: TCH assignment successful, TCH assignment fail-recovered to
SDCCH, TCH assignment blocked.
Basis Cell.
Type Counter array.
4-92 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_REQ_MSC_FAIL
HO_REQ_MSC_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_REQ_MSC_FAIL statistic tracks the number of handover request failure messages
sent to the MSC, except for, no channel resources available. This message is sent to notify
the MSC that the BSS could not reserve the radio resource that the MSC requested in the
Handover Request message.
Pegging
This statistic pegs in the source or target cell depending on where the failure occurs.
This statistic pegs in the source cell if the handover failure originates from the MS. This
indicates that the MS has reverted back to its original channel.
This statistic pegs in the target cell if the handover failure message originates from the target
cell. This could indicate one of the following problems: terrestrial circuit unavailable, terrestrial
circuit in use, ciphering algorithm not supported, or radio resources unavailable.
This statistic is not pegged if resources are not available in the target cell.
Analysis
handover failures for any reason other than lack of channel resources that are acceptable in
If the specified threshold is exceeded, the 18. CELL: HO failure to the MSC due to
all possible errors except no channels - PM alarm is generated. Refer to the manual
Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting
information.
Reference GSM 8.08, 3.9.2, 3.1.5.3.2, 3.2.1.8 and 3.2.1.16.

Usage Handover, Fault finding, and Ladder (Handover (Inter-BSS) blocked).
Basis Cell.
Type Counter.
Alarm Warning.
NOTE
If the cell has never been the target for a failed handover. HO_REQ_MSC_FAIL
can be equal to INTER_BSS_MS_FAIL
68P02901W56-T 4-93
Jan 2010
HO_REQ_ACK_TO_MSC Chapter 4: Cell statistics
HO_REQ_ACK_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named HO_REQ_MSC_OK.
Description
The HO_REQ_ACK_TO_MSC statistic tracks the number of handover request acknowledge

messages sent to the MSC for each channel type and speech version by the destination cell in
an inter-BSS (external) handover.
Table 4-28 HO_REQ_ACK_TO_MSC bins (0–5)

0 PM_FR Counts the number of full rate handover request acknowledgments
sent to the MSC.
1 PM_EFR Counts the number of enhanced full rate handover request
acknowledgments sent to the MSC.
2 PM_AMR_FR Counts the number of Adaptive Multi-Rate full rate handover
request acknowledgments sent to the MSC.
3 PM_AMR_HR Counts the number of Adaptive Multi-Rate half rate handover
request acknowledgments sent to the MSC.
4 PM_SIGNALLING Counts the number of SDCCH channel handover request
5 PM_DATA Counts the number of data handover request acknowledgments
sent to the MSC.
When the Half Rate feature is unrestricted, the HO_REQ_ACK_TO_MSC bin table introduces
bin procedure PM_GSM_HR as shown:
Table 4-29 HO_REQ_ACK_TO_MSC bins (6)
Bin Procedure Description

6 PM_GSM_HR Counts the number of GSM half rate handover request
4-94 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Pegging
Pegging
This statistic pegs for each channel type and speech version when the BSS sends a Handover
Request Acknowledge message to the MSC. This message is sent to notify the MSC that the BSS
has reserved the radio resource that the MSC asked for in the Handover Request message.
Analysis
This statistic can be used for trend analysis of successful radio resource reservations per
channel type and speech version by the BSS in response to MSC Handover Request messages.
Reference GSM 08.08, 3.9.2, 3.1.5.3.1, 3.2.1.8 and 3.2.1.10.

Usage Handover.
Network planning.
Ladder: Handover (Inter-BSS) successful, handover (Inter-BSS)
fail/recovered.
Basis Cell.
Type Counter array.
68P02901W56-T 4-95
Jan 2010
IA_IAR_MSGS_PER_AGCH Chapter 4: Cell statistics
IA_IAR_MSGS_PER_AGCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IA_IAR_MSGS_PER_AGCH statistic tracks the number of Immediate Assignment (IA)

or Immediate Assignment Reject (IAR) messages sent over CCCH or discarded when AGCH
is overloaded respectively.
1 Unit represents 1 IA or IAR message sent or discarded respectively.
Table 4-30 IA_IAR_MSGS_PER_AGCH bins
Bin Description
0 the number of IA CS messages sent over CCCH.
1 the number of IA PS messages sent over CCCH.
2 the number of IAR CS messages sent over CCCH.
3 the number of IAR PS messages sent over CCCH.
4 the number of IA CS messages discarded.
5 the number of IA PS messages discarded.
6 the number of IAR CS messages discarded.
7 the number of IAR PS messages discarded.
Pegging
This statistic pegs the appropriate bin for each occurrence of Immediate Assignment (IA) or
Immediate Assignment Reject (IAR) message for each of the following causes:
• IA or IAR message is packing on CCCH.
• IA or IAR message is discarded when AGCH is overloaded.
Analysis
This statistic provides an indication of the number of IA and IAR messages servicing on CCCH
for various causes.
Reference None.
Usage
Basis Cell.
4-96 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IDLE_TCH_INTF_BAND0
IDLE_TCH_INTF_BAND0
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IDLE_TCH_INTF_BAND0 statistic tracks the maximum and mean number of idle traffic
channels (TCHs) for interference band 0. An idle TCH falls into band 0 if its average interference
band is less than the value of the element interfer_bands, 0.
NOTE
• Idle TCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle TCHs.
• The value of this statistic may decrease because the idle TCH may be configured
as the additional switchable PDTCH.
Pegging
This statistic is reported periodically using the rf_res_ind_period element.
Analysis
This statistic can be used for trend analysis of idle traffic channels.
Reference GSM 12.04, 4.2.1, B.2.1.13.
Usage Service integrity.

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-T 4-97
Jan 2010
IDLE_TCH_INTF_BAND1 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
4-98 68P02901W56-T
Jan 2010
IDLE_TCH_INTF_BAND2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-T 4-99
Jan 2010
IDLE_TCH_INTF_BAND3 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
4-100 68P02901W56-T
Jan 2010
IDLE_TCH_INTF_BAND4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-T 4-101
Jan 2010
IN_INTER_BSS_HO Chapter 4: Cell statistics
IN_INTER_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTER_BSS_HO statistic tracks incoming inter-BSS handover procedures on a

per-scenario basis (including 3G to 2G handovers). A total value for this statistic is not
meaningful and is not displayed.
Table 4-31 IN_INTER_BSS_HO bins

0 IN_INTER_BSS_HO_SUCCESS_RATE Number of successful incoming inter-BSS
handovers.
1 IN_INTER_BSS_MS_NO_SEIZE Number of times an MS does not seize an
allocated channel.
This statistic is not currently pegged.
2 IN_INTER_BSS_EQUIP_FAIL Number of incoming inter-BSS handovers that
fail due to equipment failure.
3 IN_INTER_BSS_HO_CLEARED Number of incoming inter-BSS handovers
aborted due to call clearing. This scenario
corresponds to the receipt of a Clear Command,
SCCP Released, or Release Done (internal
message) during the handover procedure.
Pegging
These individual bins are incremented on a per cause basis.
Analysis
This statistic can be used for trend analysis of incoming inter-BSS handover procedures on a
per scenario basis.
Reference Metrica, GSM 12.04, 3.1.0, B.1.1.7.

Fault finding, Handover and Key statistics (CELL_TCH_ASSIGNMENTS,
RF_LOSS_RATE, TCH_MEAN_HOLDING_TIME and
TCH_RF_LOSS_RATE).
Basis Cell.
Type Counter array.
4-102 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IN_INTRA_BSS_HO
IN_INTRA_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_HO statistic tracks incoming intra-BSS handover procedures on a per

scenario basis. A total value for this statistic is not meaningful and is not displayed.
Table 4-32 IN_INTRA_BSS_HO bins

0 IN_INTRA_BSS_HO_SUCCESS_RATE Number of successful incoming intra-cell
handovers.
1 IN_INTRA_BSS_HO_LOSTMS Number of failed incoming intra-BSS
handovers that also failed to recover to the
original cell.
2 IN_INTRA_BSS_EQUIP_FAIL Number of failed incoming intra-BSS
handovers that fail due to equipment failure.
3 IN_INTRA_BSS_HO_RETURN Number of failed incoming intra-BSS
handovers that recover to the original
cell/channel.
4 IN_INTRA_BSS_HO_CLEARED Number of incoming intra-BSS handovers
aborted due to call clearing. This scenario
corresponds to the receipt of a Clear
Command, SCCP Released, or Release Done
(internal message) during the handover
procedure.
Pegging
These individual bins are incremented on a per-scenario basis.
68P02901W56-T 4-103
Jan 2010
Analysis
This statistic can be used for trend analysis of incoming intra-BSS handover procedures on a
per scenario basis.
Reference Metrica, GSM 12.04, 3.1.0, B.1.1.7.

planning, Service retainability, Fault finding, Handover and
Key statistics (CELL_TCH_ASSIGNMENTS, RF_LOSS_RATE,
TCH_MEAN_HOLDING_TIME and TCH_RF_LOSS_RATE).
Basis Cell.
Type Counter array.
4-104 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTERBAND_ACTIVITY
INTERBAND_ACTIVITY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTERBAND_ACTIVITY statistic tracks inter-band handover attempts in the BSS.

Assignment and handover failures due to incorrect or unsupported frequency information are
also tracked. The Multiband option must be enabled for this statistic to be enabled, disabled, or
displayed.
Table 4-33 INTERBAND_ACTIVITY bins

0 PGSM_HO_ATMPT Attempts to handover to base GSM band.
1 EGSM_HO_ATMPT Attempts to handover to extended GSM band.
2 DCS1800_HO_ATMPT Attempts to handover to DSC1800 band.
3 PCS1900_HO_ATMPT Attempts to handover to PCS1900 band.
4 PGSM_HO_FAIL Handover failures to base GSM band.
5 EGSM_HO_FAIL Handover failures to extended GSM band.
6 DCS1800_HO_FAIL Handover failures to DCS1800 band.
7 PCS1900_HO_FAIL Handover failures to PCS1900 band.
8 INVALID_FREQ_ASGN Frequency not implemented for assignment request.
9 INVALID_FREQ_HO Frequency not implemented for handover.
Pegging
This individual bins are incremented on a per-cause basis. For inter-band handovers, the bin of
the destination frequency is pegged.
Analysis
This statistic can be used for trend analysis of inter-band handover attempts in the BSS on a
per-cause basis.
Reference None.
Usage Handover, Quality of service monitoring, Network planning and Service

retainability.
Basis Cell.
Type Counter array.
68P02901W56-T 4-105
Jan 2010
INTRA_CELL_HO Chapter 4: Cell statistics
INTRA_CELL_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO statistic tracks intra-cell handovers on a per-scenario basis.
This statistic is enhanced to count the number of congestion/quality related handovers:

• full-rate to full-rate intra-cell handovers.
• full-rate to half-rate intra-cell handovers.
• half-rate to half-rate intra-cell handovers.
• half-rate to full-rate intra-cell handovers.
A total value for this statistic is not meaningful and is not displayed.
Table 4-34 INTRA_CELL_HO bins
0 INTRA_CELL_HO_REQ Number of times an intra-cell handover

is considered the best option by the
handover evaluator process.
1 INTRA_CELL_HO_ATMPT_FR_FR Number of assignment commands sent
to MS during a full-rate to full-rate
intra-cell handover.
2 INTRA_CELL_HO_ATMPT_HR_HR Number of assignment commands sent
to MS during a half-rate to half-rate
3 INTRA_CELL_HO_ATMPT_HR_FR Number of assignment commands sent
to MS during a half-rate to full-rate
4 INTRA_CELL_HO_ATMPT_FR_HR Number of assignment commands sent
to MS during a full-rate to half-rate
5 INTRA_CELL_HO_SUC Number of successful intra-cell
handovers.
Continued
4-106 68P02901W56-T
Jan 2010
Table 4-34 INTRA_CELL_HO bins (Continued)

6 INTRA_CELL_HO_LOSTMS Number of failed intra-cell handovers

that also failed to recover to the original
cell.
7 INTRA_CELL_HO_RETURN Number of failed intra-cell handovers
that recovered to the original
cell/channel.
8 INTRA_CELL_EQUIP_FAIL Number of attempted intra-cell handover
failures due to equipment failure.
9 INTRA_CELL_HO_CLEARED Number of intra-cell handover cleared.
10 INTRA_CELL_HO_ATMPT_SD_TO_SD Number of assignment commands sent
to the MS during an SDCCH to SDCCH
Pegging
INTRA_CELL_HO_REQ is pegged just before sending the intra-cell handover message.
INTRA_CELL_HO_ATMPT_XX_YY is pegged after the channel activation message is received

and just before the assignment command is sent to the MS.
NOTE
The intracell handover bin pegged depends on the speech rate involved and may
include the change of speech rate, which pegs the associated bin (FR_FR, HR_HR,
HR_FR, or FR_HR).
INTRA_CELL_HO_SUC is pegged each time a handover performed message is sent to the MS.
INTRA_CELL_HO_LOSTMS is pegged when a radio channel released message is received.
INTRA_CELL_HO_RETURN is pegged when a, revert to old channel, message is received.
INTRA_CELL_EQUIP_FAIL is pegged when an, assignment failure, message contains an

equipment failure cause or KSW/highway fault.
INTRA_CELL_HO_CLEARED is pegged every time a call is cleared down during an intra-cell

handover.
68P02901W56-T 4-107
Jan 2010
Analysis
This statistic can be used for trend analysis of intra-cell handovers on a per scenario basis.

Network planning.
Fault finding.
Service retainability.
Key statistics:
HANDOVER_FAILURE_RATE,
HANDOVER_SUCCESS_RATE,
SUCCESS_INTERNAL_HO,
UNSUCCESS_INTERNAL_HO_NORESET,
UNSUCCESS_INTERNAL_HO_RESET.
Basis Cell.
Type Counter array.
Reference Metrica.
GSM 12.04, 3.1.0, B.1.1.6.
GSM 8.08, 3.9.2, 3.1.6, 3.2.1.25.
GSM 4.08, 3.8.0, 9.1.3.
4-108 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MA_CMD_TO_MS
MA_CMD_TO_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_CMD_TO_MS statistic tracks the number of Assignment Commands sent to the MS.
Pegging
This statistic pegs when the BSS initiates the channel assignment procedure by sending an
Assignment Command to the MS on the main SDCCH. Assignment Command is sent to the MS
at call setup (traffic channel assignment) and at intra-cell handovers. This causes the MS to:
• Release its link layer connections.
• Disconnect from its current physical channels.
• Switch to the assigned channels.
• Initiate re-establishment of the lower layer connections.
Analysis
This statistic can be used for trend analysis of BSS initiated channel assignment procedures
to the MS.
Reference GSM 4.08, 3.8.0, 3.4.3.1 and 9.1.2.

Call setup.
Ladder: TCH assignment successful, TCH assignment fail-recovered
to SDCCH, handover (Intra-cell) successful, handover (Intra-cell)
fail-recovered, handover (Intra-cell) fail-lost.
Basis Cell.
Type Counter.
68P02901W56-T 4-109
Jan 2010
MA_COMPLETE_FROM_MS Chapter 4: Cell statistics
MA_COMPLETE_FROM_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_COMPLETE_FROM_MS statistic tracks the number of Assignment Complete

messages received from MSs.
Pegging
This statistic pegs when the BSS receives an Assignment Complete message from the MS.
Analysis
This statistic can be used for trend analysis.
Reference GSM 12.04, 4.2.1, B.2.1.15

Quality of service: Call set-up.
Network planning.
Ladder: TCH assignment successful.
Basis Cell.
Type Counter.
4-110 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MA_COMPLETE_TO_MSC
MA_COMPLETE_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_COMPLETE_TO_MSC statistic tracks the number of successful assignment

completions for each channel and speech version.
Table 4-35 MA_COMPLETE_TO_MSC bins (0–5)

0 PM_FR Counts the number of full rate assignment requests forwarded from
the MS to the MSC.
1 PM_EFR Counts the number of enhanced full rate assignment requests
forwarded from the MS to the MSC.
2 PM_AMR_FR Counts the number of Adaptive Multi-rate full rate assignment
requests forwarded from the MS to the MSC.
3 PM_AMR_HR Counts the number of Adaptive Multi-rate half rate assignment
requests forwarded from the MS to the MSC.
4 PM_SIGNALLING Counts the number of SDCCH channel assignment requests
5 PM_DATA Counts the number of data assignment requests forwarded from
the MS to the MSC.
When the Half Rate feature is unrestricted, the MA_COMPLETE_TO_MSC bin table introduces
bin procedure PM_GSM_HR as shown:
Table 4-36 MA_COMPLETE_TO_MSC bins (6)

6 PM_GSM_HR Counts the number of GSM half rate assignment requests
Pegging
This statistic pegs when the Assignment Complete message from the MS is forwarded on to
the MSC.
68P02901W56-T 4-111
Jan 2010
Analysis
This statistic can be used for trend analysis of successful assignment completions per channel
type and speech version.
Reference GSM 08.08,12.04, 4.2.1, B.2.1.15

Quality of service: Call set-up.
Network planning.
Basis Cell.
Type Counter array.
4-112 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MA_FAIL_FROM_MS
MA_FAIL_FROM_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_FAIL_FROM_MS statistic tracks the number of Assignment Failure messages received
from MSs. An Assignment Failure message can be received at call setup (traffic channel
assignment) and at intra cell handovers.
Pegging
This statistic pegs when the BSS receives an Assignment Failure message from the MS. If the
MS detects a lower layer failure on the new channels before the Assignment Complete message
has been sent:
• It deactivates the new channels.
• Reactivates the old channels.
• Reconnects any TCHs.
• Triggers establishment of the main signaling link.
• It then sends the Assignment Failure message on the main DCCH. This statistic pegs for
channel assignment failures at intra-cell handovers for new calls and channel assignment
failures at handover.
Analysis
assignment failures for MSs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 23. CELL: Mobile assignment failure from MS

GSM 12.07, 3.0.2, 2.8.6.c.
GSM 4.08, 3.8.0, 3.4.3.3 and 9.1.4.
Usage Radio resource allocation, Quality of service monitoring (Call setup), Fault
finding, Ladder (TCH assignment fail-recovered to SDCCH and handover
(Intra-cell) fail-recovered).
Basis Cell.
Type Counter.
Alarm Warning.
68P02901W56-T 4-113
Jan 2010
MA_REQ_FROM_MSC Chapter 4: Cell statistics
MA_REQ_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_REQ_FROM_MSC statistic tracks the number of times the MSC asked the BSS to
allocate radio resources. The MSC sends the BSS an Assignment request message containing
details of the type of resource required. The type of resource is based on the MSC analysis of
the call control information received from the MS.
Table 4-37 MA_REQ_FROM_MSC bins (0–5)

0 PM_FR Counts the number of full rate assignment requests from the MSC.
1 PM_EFR Counts the number of enhanced full rate assignment requests
from the MSC.
2 PM_AMR_FR Counts the number of Adaptive Multi-rate full rate assignment
requests from the MSC.
3 PM_AMR_HR Counts the number of Adaptive Multi-rate half rate assignment
requests from the MSC.
4 PM_SIGNALLING Counts the number of SDCCH channel assignment requests from
the MSC.
5 PM_DATA Counts the number of data assignment requests from the MSC.
When the Half Rate feature is unrestricted, the MA_REQ_FROM_MSC bin table introduces bin
procedure PM_GSM_HR as shown:
Table 4-38 MA_REQ_FROM_MSC bins (6)

6 PM_GSM_HR Counts the number of GSM half rate assignment requests from the
MSC.
Pegging
This statistic pegs the radio resource request for each preferred speech version made to
a BSS by the MSC.
4-114 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of MSC request to the BSS to allocate radio
resources.

Network planning.
Ladder: TCH assignment successful, TCH assignment fail-recovered to
SDCCH, TCH assignment blocked.
Basis Cell.
Type Counter array.
68P02901W56-T 4-115
Jan 2010
MA_CMD_TO_MS_BLKD Chapter 4: Cell statistics
MA_CMD_TO_MS_BLKD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_CMD_TO_MS_BLKD statistic tracks the number of times an assignment request from
the MSC could not be processed (assignment command could not be generated and sent to the
MS) as there were no traffic channels available at the cell due to congestion or lack of essential
resources, for instance, extended timeslots.
Pegging
This statistic is pegged by the BSS when the MSC requests the BSS to allocate radio resource to
an MS, and the BSS finds it has no channels available to allocate. The pegging of this statistic
indicates no channels were available in the currently allocated cell. It is indicated by an
Assignment Failure message with cause: No radio resource available.
The statistic is pegged into appropriate bin when the BSP CPU is overloaded.
If queuing is enabled the statistic is pegged when the BSS queuing related timer bss_t11
expires. If the BSS assignment_successful timer is set shorter than the BSS bssmap_t11 timer
then this statistic is not pegged. It is recommended that the assignment_successful timer be
always set greater than the bssmap_t11 timer.
Analysis
times traffic channels that may be congested due to a lack of radio resources that are acceptable
in normal system operations.
The alarm, CELL: Mobile Assign Command to MS Blocked (No Channel Available) - PM
is raised if the threshold for bin 0 is reached.
The alarm CELL: Mobile Assign Command to MS Blocked BSP CPU Overload - PM is
raised if the threshold for bin 1 is reached. The procedure for PM alarm process is followed
by these two alarms.
NOTE
In the formula of key statistic CALL_SETUP_BLOCKING_RATE, the row statistic
MA_CMD_TO_MS_BLKD represents the sum of two bins.
4-116 68P02901W56-T
Jan 2010
If the specified threshold is exceeded, the 2. CELL: Mobile assign command to MS

blocked (no channel available) - PM alarm is generated. Refer to the manual Maintenance
Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.

Quality of service monitoring: Call setup and handover.
Fault finding.
Network planning.
Optimization.
Ladder: TCH assignment blocked.
Basis Cell.
Type Counter array.
Alarm Minor.
68P02901W56-T 4-117
Jan 2010
MS_ACCESS_BY_TYPE Chapter 4: Cell statistics
MS_ACCESS_BY_TYPE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MS_ACCESS_BY_TYPE statistic tracks the number of system accesses by the various types
of MSs. The type of MS is included in the MS Classmark 3 information.
This statistic may be enabled only if the Multiband feature is unrestricted and enabled for
the cell.
Table 4-39 MS_ACCESS_BY_TYPE bins (0–7)
Bin MS Type Description

0 MS_PGSM_ONLY Base GSM band only.
1 MS_DCS1800_ONLY DCS1800 band only.
2 MS_PCS1900_ONLY PCS1900 band only.
3 MS_PGSM_EGSM Base and extended GSM bands.
4 MS_PGSM_DCS1800 Base GSM and DCS1800 bands.
5 MS_PGSM_EGSM_DCS1800 Base GSM, extended GSM, and DCS1800 bands.
6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.
7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, and PCS1900 bands.
Pegging
The MS_ACCESS_BY_TYPE statistic is pegged by RRSM after the sending of the initial layer 3
information by the MS, on receipt of the classmark of the MS. It can also be pegged if the MS
sends a CLASSMARK CHANGE message while in dedicated mode.
Analysis
This statistic can be used for trend analysis of system accesses by MS type.
Usage Quality of Service monitoring.

Network planning.
Basis Cell.
Type Counter array.
4-118 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MS_TCH_USAGE_BY_TYPE
MS_TCH_USAGE_BY_TYPE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MS_TCH_USAGE_BY_TYPE statistic tracks the length of time spent on TCHs by the
various types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.
For example, if MS_TCH_USAGE_BY_TYPE = 31, the call duration was 3.1 minutes or 186
seconds). The type of MS is included in the MS Classmark 3 information.
This statistic may only be enabled if the Multiband feature is unrestricted and enabled for
the cell.
Table 4-40 MS_TCH_USAGE_BY_TYPE bins
Bin MS Type Description

0 MS_PGSM_ONLY Base GSM band only.
1 MS_DCS1800_ONLY DCS1800 band only.
2 MS_PCS1900_ONLY PCS1900 band only.
3 MS_PGSM_EGSM Base and extended GSM bands.
4 MS_PGSM_DCS1800 Base GSM and DCS1800 bands.
5 MS_PGSM_EGSM_DCS1800 Base GSM, extended GSM, and DCS1800 bands.
6 MS_PGSM_PCS1900 Base GSM and PCS1900 bands.
7 MS_PGSM_EGSM_PCS1900 Base GSM, extended GSM, and PCS1900 bands.
Pegging
Each bin is updated by the cell resource manager when the duration for an active channel is
recorded. A total duration is calculated which is the sum for all channels usage time by MSs
in a given cell.
Analysis
This statistic can be used for trend analysis of active channel usage. This information can be
used to identify problems before they can affect service.
Usage Service accessibility.

Network planning.
Basis Cell.
Type Counter array.
68P02901W56-T 4-119
Jan 2010
MS_TCH_USAGE_BY_TYPE_PCS Chapter 4: Cell statistics
MS_TCH_USAGE_BY_TYPE_PCS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MS_TCH_USAGE_BY_TYPE_PCS statistic tracks the length of time spent on TCHs by the
various types of MSs. Duration is measured in deciminutes. (One deciminute equals six seconds.
For example, if MS_TCH_USAGE_BY_TYPE_PCS = 31, the call duration was 3.1 minutes or 186
seconds). The type of MS is included in the MS Classmark 3 information.
This statistic may only be enabled if either the PCS1900 or GSM850 frequency band is allowed
on the BSS and the Multiband feature is unrestricted and enabled for the cell.
Table 4-41 MS_TCH_USAGE_BY_TYPE_PCS bins
Bin Description
0 GSM850 only capable MSs.
1 DCS1800-PCS1900 capable MSs.
2 PGSM-DCS1800-PCS1900 capable MSs.
3 PGSM-EGSM-DCS1800-PCS1900 capable MSs.
4 PGSM-GSM850 capable MSs.
5 PGSM-EGSM-GSM850 capable MSs.
6 GSM850-DCS1800 capable MSs.
7 PGSM-GSM850-DCS1800 capable MSs.
8 PGSM-EGSM-GSM850-DCS1800 capable MSs.
9 GSM850-PCS1900 capable MSs.
10 PGSM-GSM850-PCS1900 capable MSs.
11 PGSM-EGSM-GSM850-PCS1900 capable MSs.
12 GSM850-PCS1900-DCS1800 capable MSs.
13 PGSM-GSM850-PCS1900-DCS1800 capable MSs.
14 PGSM-EGSM-GSM850-PCS1900-DCS1800 capable MSs.
Pegging
Each bin is updated by the cell resource manager when the duration for an active channel is
recorded. A total duration is calculated which is the sum for all channels usage time by MSs
in a given cell.
4-120 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of active channel usage. This information can be
used to identify problems before they can affect service.

Network planning.
Basis Cell.
Type Counter array.
68P02901W56-T 4-121
Jan 2010
MT_LCS_ON_SDCCH Chapter 4: Cell statistics
MT_LCS_ON_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of MS-terminated SDCCH sessions for Location Services.
Pegging
This statistic is pegged each time there is an MT LMU on an SDCCH.
It is also pegged for a MT call when any LCS transaction occurs while the MS is on an SDCCH
or TCH-signaling. Any of the following messages received over the A-interface are considered
LCS transaction initiations:
• BSSLAP TA Request.
• BSSLAP MS Position Command.
• BSSMAP Perform Location Request (only applies in the case of a BSS based SMLC).
Analysis
Reference GSM 03.71 v7.4.0.

Usage Fault finding.
Key statistic:
CALL_SETUP_SUCCESS_RATE.
Basis Cell.
Type Counter.
4-122 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MT_SUPP_ON_SIGNALLING
MT_SUPP_ON_SIGNALLING
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic MT_SUPP_ON_SIGNALLING tracks the total number of MS-terminated SDCCH or

signaling TCH sessions for supplementary service, which is originally established through the
paging procedure and is completed through the use of an SDCCH or signalling TCH, without a
SAPI 3 (SMS) or CS call connection being established.
This statistic is subtracted from the denominator of the Call Set-Up Success Rate calculation
to ensure that the accuracy of the Call Set-Up Success rate is not compromised by mobile
terminated supplementary service transactions initiated by the MSC. This statistic is pegged
once per connection.
Pegging
This statistic is pegged when the first DTAP REGISTER message is received from the MSC
for a mobile terminated connection (a connection originally established through the paging
procedure) that is completed through the use of an SDCCH or signalling TCH, without a SAPI 3
(SMS) or CS call connection being established.
Analysis
Reference None.
Key statistic:
CALL_SETUP_SUCCESS_RATE.
Basis Cell.
Type Counter.
68P02901W56-T 4-123
Jan 2010
NUM_CELL_RESEL_CELL Chapter 4: Cell statistics
NUM_CELL_RESEL_CELL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_CELL statistic measures the total number of PCCC and PCCO attempts
to a cell due to either congestion relief or RF based cell reselection.
One unit represents ten attempts by the BSS to send a PCCC or PCCO message.
Pegging
The NUM_CELL_RESEL_CELL statistic pegs on a per-cell basis. Table 4-42 shows the scenarios
used to update the counter bins associated with this statistic. The corresponding per neighbor
statistics are pegged using a separate counter: NUM_CELL_RESEL_NEI on page 5-10.
Table 4-42 Bin update scenarios for NUM_CELL_RESEL_CELL
Bin Scenario
0 Attempted PCCC due to NACC network agrees with the MSs decision.
1 Attempted PCCO due to NACC network overrides the MSs decision.
2 Attempted PCCO due to microcellular algorithm.
3 Attempted PCCO due to congestion relief.
4 Attempted PCCO due to RF based NC2.
Analysis
Reference None.
Usage Cell change information tracking.
Basis Cell.
Type Counter array.
4-124 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_CELL_RESEL_CELL_PCCN
NUM_CELL_RESEL_CELL_PCCN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_CELL_PCCN statistic measures the total number of PCCN requests by

MSs.
One unit represents one attempts by an MS to send a PCCN.
Pegging
The NUM_CELL_RESEL_CELL_PCCN statistic pegs the number of PCCN received on a per-cell

basis. The corresponding per neighbor statistics are pegged using a separate counter:
NUM_CELL_RESEL_NEI_PCCN on page 5-11.
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-T 4-125
Jan 2010
NUM_CELL_RESEL_CELL_SUCC Chapter 4: Cell statistics
NUM_CELL_RESEL_CELL_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_CELL_SUCC statistic measures the total number of successful PCCC

and PCCO attempts to a cell due to either congestion relief or RF based cell reselection. A cell
reselection is not detectable under the following circumstances:
• TLLI changing after an inter RAC cell reselection.
• Cell change taking too long so that the previous context is deleted at the PCU.
• The target cell being on another PCU.

One unit represents one successful cell reselections due to PCCC/PCCO.
Pegging
NCRM pegs the NUM_CELL_RESEL_CELL_SUCC statistic on a per-cell basis for every

successful cell reselection detectable by the PCU due to PCCC/PCCO. The corresponding per
neighbor statistics are pegged using a separate counter: NUM_CELL_RESEL_NEI_SUCC on
page 5-12.
Analysis
Reference None.
Basis Cell.
Type Counter.
4-126 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_EMERG_ACCESS
NUM_EMERG_ACCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_EMERG_ACCESS statistic tracks the number of emergency calls that access the
system.
Pegging
This statistic pegs after the receipt of an emergency RACH.
Analysis
This statistic can be used for trend analysis of emergency call accesses.
Usage Quality of Service monitoring.

Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 4-127
Jan 2010
NUM_EMERG_REJECTED Chapter 4: Cell statistics
NUM_EMERG_REJECTED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_EMERG_REJECTED statistic tracks the number of times an emergency call accesses
the system and has to be immediately rejected because there are no resources and another
call cannot be preempted to allow it access.
Pegging
This statistic pegs the number of emergency calls that are rejected because all channels were
occupied by other emergency or high priority calls.
Analysis
This statistic can be used for trend analysis of emergency call accesses that failed because all
channels were occupied by other emergency or high priority calls.

Network planning.
Basis Cell.
Type Counter.
4-128 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_EMERG_TCH_KILL
NUM_EMERG_TCH_KILL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_EMERG_TCH_KILL statistic tracks the number of times a call is lost due to
emergency call preemption and not to other factors, such as RF losses.
The active channel with the lowest priority is the one that releases a TCH. Additionally,
emergency calls are not preempted by other emergency calls.
Pegging
This statistic pegs the number of active calls that are terminated in order to make a TCH
available for an emergency call. This situation arises if all TCHs are occupied and an emergency
access requires a channel. This statistic pegs only if the emergency preemption feature is
enabled.
Analysis
This statistic can be used for trend analysis of the number of times that calls are lost due
to emergency call preemption only.

Network planning.
Basis Cell
Type Counter.
68P02901W56-T 4-129
Jan 2010
NUM_EMERG_TERM_SDCCH Chapter 4: Cell statistics
NUM_EMERG_TERM_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_EMERG_TERM_SDCCH statistic tracks the number of emergency accesses

terminated after SDCCH congestion. Used to indicate that an emergency call was allocated an
SDCCH but could not be allocated a TCH.
Pegging
This statistic pegs each time an emergency call is assigned to an SDCCH but must be terminated
because no TCHs are available to complete the call. This statistic is pegged regardless of the
status of the emergency preemption feature.
Analysis
This statistic can be used for trend analysis of the number of times that emergency accesses are
terminated after SDCCH congestion.

Network planning.
Basis Cell.
Type Counter.
4-130 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_HO_3G_ATTEMPTS
NUM_HO_3G_ATTEMPTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_3G_ATTEMPTS statistic counts the number of handover attempts made into a
3G cell from a 2G network.
Pegging
The BSS pegs the NUM_HO_3G_ATTEMPTS statistic after sending a BSSMAP HANDOVER
REQUIRED message containing a Cell Identification Discriminator value of 1000 to the MSC.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
68P02901W56-T 4-131
Jan 2010
NUM_HO_FROM_3G_ATTEMPTS Chapter 4: Cell statistics
NUM_HO_FROM_3G_ATTEMPTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_FROM_3G_ATTEMPTS statistic counts the number of handover attempts made

into a 2G Cell from a 3G network.
NOTE
The 3G network can be either WCDMA or TD-SCDMA technology.
Pegging
The BSS pegs the NUM_HO_FROM_3G_ATTEMPTS statistic after receiving a BSSMAP

HANDOVER REQUEST from the MSC where the Cell Identification Discriminator value
indicates 1011.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
4-132 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_HO_FROM_3G_SUCCESS
NUM_HO_FROM_3G_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_FROM_3G_SUCCESS statistic counts the number of successful handovers made

NOTE
The 3G network can be either WCDMA or TD-SCDMA technology.
Pegging
The BSS pegs the NUM_HO_FROM_3G_SUCCESS statistic whenever a successful handover

is made into a 2G Cell from a 3G network.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
68P02901W56-T 4-133
Jan 2010
NUM_HO_TO_3G_RES_ALLOC_SUCC Chapter 4: Cell statistics
NUM_HO_TO_3G_RES_ALLOC_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_TO_3G_RES_ALLOC_SUCC statistic counts the number of times a required 3G

resource has been allocated to allow a handover to the 3G network to proceed.
Pegging
The BSS pegs the NUM_HO_TO_3G_RES_ALLOC_SUCC statistic after receiving a BSSMAP

HANDOVER COMMAND message from the MSC where the Layer 3 information element
contains the HANDOVER TO UTRAN COMMAND.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
4-134 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_HO_TO_3G_SUCCESS
NUM_HO_TO_3G_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_TO_3G_SUCCESS statistic counts the number of successful handovers made

Pegging
The BSS pegs the NUM_HO_TO_3G_SUCCESS statistic after receiving a BSSMAP CLEAR
COMMAND from the MSC which corresponds to a BSSMAP HANDOVER COMMAND where the
Layer 3 information contained the HANDOVER TO UTRAN COMMAND.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
68P02901W56-T 4-135
Jan 2010
NUM_MULTIRAT_MS_ORIG_CALL Chapter 4: Cell statistics
NUM_MULTIRAT_MS_ORIG_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_MULTIRAT_MS_ORIG_CALL counts the number of times an MS reports that it

is 3G capable.
Pegging
The BSS pegs the NUM_MULTIRAT_MS_ORIG_CALL statistic after receiving an RR UTRAN

CLASSMARK CHANGE message from a MultiRAT MS as part of the early classmark sending
procedures at call establishment.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
4-136 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_OF_SMS_INIT
NUM_OF_SMS_INIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic NUM_OF_SMS_INIT tracks the number of times a SAPI3 connection occurs on an
SDCCH or a signaling TCH, the number of times a SAPI3 successful connection relates to an
SDCCH or a signaling TCH, and also tracks the number of times a successful incoming handover
SAPI3 connection occurred or is successfully established on an SDCCH or a signaling TCH.
Table 4-43 NUM_OF_SMS_INIT bins

0 SMS_INIT_ON_SDCCH The SMS_INIT_ON_SDCCH_REQ statistic
_REQ tracks at a cell level the number of
requests to establish a SAPI3 connection
on an SDCCH for Short Message Service
(SMS). Any repeated attempts to establish
a SAPI3 connection do not cause this
statistic to peg.
1 SMS_INIT_ON_TCH The SMS_INIT_ON_TCH_FCS_REQ
_FCS_REQ statistic tracks at a cell level the number of
on a signaling TCH for Short Message
Service (SMS). Any repeated attempts to
establish a SAPI3 connection do not cause
this statistic to peg.
2 SMS_INIT_ON_SIG The SMS_INIT_ON_SIG_HO_IN_REQ
_HO_IN_REQ statistic tracks at a cell level the number of
on an SDCCH or a signaling TCH for Short
Message Service (SMS) after an incoming
handover. Any repeated attempts to
establish a SAPI3 connection do not cause
this statistic to peg.
3 SMS_INIT_ON_SDCCH The SMS_INIT_ON_SDCCH_SUC statistic
_SUC tracks at a cell level the number of SAPI3
connections successfully established on an
SDCCH for Short Message Service (SMS).
Any repeated successful establishment
of a SAPI3 connection do not cause this
statistic to peg.
Continued
68P02901W56-T 4-137
Jan 2010
Pegging Chapter 4: Cell statistics
Table 4-43 NUM_OF_SMS_INIT bins (Continued)

4 SMS_INIT_ON_TCH The SMS_INIT_ON_TCH_FCS_SUC
_FCS_SUC statistic tracks at a cell level the number
of SAPI3 connections successfully
established on a signaling TCH for Short
Message Service (SMS). Any repeated
successful establishment of a SAPI3
connection do not cause this statistic to
peg.
5 SMS_INIT_ON_SIG The SMS_INIT_ON_SIG_HO_IN_SUC
_HO_IN_SUC statistic tracks at a cell level the number
of SAPI3 connections successfully
established on an SDCCH or a signaling
TCH for Short Message Service (SMS)
after an incoming handover. Any repeated
successful establishment of a SAPI3
connection do not cause this statistic to
peg.
Pegging
The statistic SMS_INIT_ON_SDCCH_REQ is incremented when an SDCCH is used by a Service

Access Point (SAPI3) connection.
The statistic SMS_INIT_ON_TCH_FCS_REQ is incremented when a signaling TCH is used by

a Service Access Point (SAPI3) connection.
The statistic SMS_INIT_ON_SIG_HO_IN_REQ is incremented when one successful incoming

handover Service Access Point (SAPI3) connection occurs related to an SDCCH or a signaling
TCH.
The statistic SMS_INIT_ON_SDCCH_SUC is incremented when there is one successful Service

Access Point (SAPI3) connection related to an SDCCH.
The statistic SMS_INIT_ON_TCH_FCS_SUC is incremented when there is a successful Service

Access Point (SAPI3) connection related to a signaling TCH.
The statistic SMS_INIT_ON_SIG_HO_IN_SUC is incremented when one successful incoming

handover Service Access Point (SAPI3) connection is successfully established related to an
SDCCH or a signaling TCH.
4-138 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OK_ACC_PROC
OK_ACC_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OK_ACC_PROC tracks successful accesses by procedure. A total count of all successful
accesses is also maintained.
Table 4-44 OK_ACC_PROC bins

0 CM_SERV_REQ_CALL Number of MS requests for originating service.
1 CM_SERV_REQ_SMS Number of MS requests for SMS service.
2 CM_SERV_REQ_SUPP Number of MS requests for supplementary services.
3 CM_SERV_REQ_EMERG Number of MS requests for emergency call service.
4 CM_REESTABLISH Number of failed MS requests for service in which the
call recovered to the original cell.
5 LOCATION_UPDATE Number of MS location update requests.
6 IMSI_DETACH Number of received IMSI detach messages.
7 PAGE_RESPONSE Number of MS page request responses.
8 LOC_FLW_ON_REQ_SMS Location Update follow-on request- SMS.
9 LOC_FLW_ON_REQ_NORM Location Update follow-on request- Normal.
10 LOCATION _SERVICES Number of Location Measurement Unit (LMU) service
requests for location services.
NOTE
LOCATION_SERVICES is stored in column cm_lcs_request of the OMC database.
Pegging
This statistic pegs the total number of successful results per procedure including location
services.
68P02901W56-T 4-139
Jan 2010
Analysis
This statistic can be used for trend analysis of the number of successful accesses by procedure.
Reference GSM 12.04, 4.21, B.3.1.2.

GSM 4.08, 4.12, 3.15, 3.3.2.2, 4.4.1, 4.4.4.1, 4.5.1.1, 4.5.1.1,
4.5.1.6, 5.5.4, 7.3.1, 9.2.9, 9.2.12, 9.2.15, and 9.45.
Network planning.
Ladder: Immediate assignment successful.
Key Statistics: CALL_SETUP_SUCCESS_RATE,
MEAN_INTER_ARRIVAL_TIME,
RF_LOSS_RATE,
SDCCH_MEAN_HOLDING_TIME,
SDCCH_RF_LOSS_RATE.
Basis Cell.
Type Counter array.
4-140 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OK_ACC_PROC_SUC_RACH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OK_ACC_PROC_SUC_RACH statistic tracks successful Channel Request messages on

the RACH of a cell.
This message is used by the MS to request allocation of a dedicated channel (to be used as an
SDCCH) by the network, in response to a paging message (incoming call) from the network or
as a result of an outgoing call/supplementary short message service dialed from the MS.
Pegging
This statistic pegs what it determines to be a valid Channel Request (RACH). This does not
necessarily result in a seizure attempt of an SDCCH.
Analysis
This statistic can be used for trend analysis of the number of successful channel requests on
the RACH of a cell.
Reference GSM 4.08, 3.8.0, 3.3.1. 3.3.2.2, 4.5.1.6, 5.5.4, 9.1.8 and 9.2.4.
GSM 12.04, 3.1.0, B.1.2.1.
Usage Radio resource allocation. Ladder: Immediate assignment
successful, Immediate assignment blocked, Immediate
assignment failure.
Key statistics:
ATTEMPT_IMMED_ASSIGN_PROC,
SUCCESS_IMMED_ASSIGN_PROC.
Basis Cell.
Type Counter.
NOTE
68P02901W56-T 4-141
Jan 2010
OUT_INTER_BSS_HO Chapter 4: Cell statistics
OUT_INTER_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO statistic tracks a range of handover actions associated with

outgoing inter-BSS handovers (including 2G –> 3G handovers). A total value for this statistic is
not meaningful and is not displayed.
Table 4-45 OUT_INTER_BSS_HO bins

0 OUT_INTER_BSS_REQ_TO_MSC Number of outgoing inter-BSS handover requests
to the MSC.
1 OUT_INTER_BSS_HO_ATMPT Number of assignment commands sent to MS
during an inter-BSS handover.
2 OUT_INTER_BSS_HO_SUC Number of successful inter-BSS handovers.
3 OUT_INTER_BSS_HO_LOSTMS Number of failed intra-BSS handovers in which
the MS also failed to recover to the original BSS.
This statistic is not currently pegged.
4 OUT_INTER_BSS_HO_RETURN Number of failed inter-BSS handovers in which
the MS recovered to the original BSS/channel.
5 OUT_INTER_BSS_HO_EQUIP_FAIL Number of CLRCMD equipment failure
messages in one interval.
6 OUT_INTER_BSS_HO_CLEARED Number of outgoing inter-BSS handovers aborted
due to call clearing in both the MS and NSS.
This scenario corresponds to the receipt of a
Clear Command, SCCP Released, or Release
Done (internal message) during the handover
procedure.
7 OUT_INTER_BSS_HO_FAIL Number of CLRCMD radio interface message
failure messages and radio interface failure
messages.
Pegging
OUT_INTER_BSS_REQ_TO_MSC is pegged when a BSSMAP Handover Required message is

sent to the MSC.
OUT_INTER_BSS_HO_ATMPT is pegged when a RR Handover Command message is forwarded

to the MS.
OUT_INTER_BSS_HO_SUC is pegged when a BSSMAP Clear Command message with cause

value 0x0b (HO Successful) is received from the MSC during an inter BSS HO procedure.
OUT_INTER_BSS_HO_LOSTMS is currently not used/pegged by BSS software.
4-142 68P02901W56-T
Jan 2010
OUT_INTER_BSS_HO_RETURN is pegged when a RR HO Failure message is recieved from the

MS in response to a RR Handover Command related to an inter BSS HO.
OUT_INTER_BSS_HO_EQUIP_FAIL is pegged when a BSSMAP Clear Command message with

cause value 0x20h (Equipment Failure) is received from the MSC during an inter BSS HO
procedure.
OUT_INTER_BSS_HO_CLEARED is pegged when a BSSMAP Clear Command message with

cause value 0x09h (Call Control) is received from the MSC during an inter BSS HO procedure.
OUT_INTER_BSS_HO_FAIL is pegged when a BSSMAP Clear Command message with cause

value 0x00h (Radio Interface Message Failure) or 0x01h (Radio Interface Failure) is received
from the MSC during an inter BSS HO procedure.
Analysis
This statistic can be used for trend analysis of inter-BSS handovers on a per handover scenario
basis.
Reference GSM 8.08, 3.9.2, 3.1.5.3.1 and 3.2.1.11. GSM 4.08, 3.8.0,
9.1.16 and 3.4.4.4.
GSM 3.1.5.1.1 and 3.2.1.9.
GSM 12.04, 3.2.0, B.1.1.8.
GSM 3.1.9.3 and 3.2.1.21.
Metrica.
Network planning.
Fault finding.
Key statistics:
HANDOVER_SUCCESS_RATE.
Basis Cell.
Type Counter array.
68P02901W56-T 4-143
Jan 2010
OUT_INTRA_BSS_HO Chapter 4: Cell statistics
OUT_INTRA_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTRA_BSS_HO statistic tracks a range of handover actions associated with outgoing
intra-BSS handovers. A total value for this statistic is not meaningful and is not displayed.
Table 4-46 OUT_INTRA_BSS_HO bins

0 OUT_INTRA_BSS_HO_REQ Number of times an intra-BSS Handover
Recognized message is received. This message
is sent when the system recognizes a handover
is required.
1 OUT_INTRA_BSS_HO_PRI_BLK Number of times an intra-BSS handover to the
primary target cell was blocked.
2 OUT_INTRA_BSS_HO_ATMPT Number of assignment commands sent to MS
during an intra-BSS handover.
3 OUT_INTRA_BSS_HO_SUC Number of successful intra-BSS handovers.
4 OUT_INTRA_BSS_HO_LOSTMS Number of failed intra-BSS handovers in which
the MS also failed to recover to the original BSS.
5 OUT_INTRA_BSS_HO_RETURN Number of failed intra-BSS handovers in which
the MS recovered to the original BSS/channel.
6 OUT_INTRA_BSS_EQUIP_FAIL Number of attempted intra-BSS handover failures
due to equipment failure.
7 OUT_INTRA_BSS_HO_CLEARED Number of outgoing intra-BSS handovers aborted
due to call clearing. This scenario corresponds to
the receipt of a Clear Command, SCCP Released,
or Release Done (internal message) during the
handover procedure.
Pegging
OUT_INTRA_BSS_HO_REQ is pegged each time an intra-BSS handover message is received.
OUT_INTRA_BSS_HO_PRI_BLK is pegged when resources not available message is received.
OUT_INTRA_BSS_HO_ATMPT is pegged when the initiate handover message is sent.
OUT_INTRA_BSS_HO_SUC is pegged when a handover performed message is sent.
OUT_INTRA_BSS_HO_LOSTMS is pegged if the MS fails to return to the original channel during

a handover attempt.
OUT_INTRA_BSS_HO_RETURN is pegged when an unsuccessful handover message is received.
4-144 68P02901W56-T
Jan 2010
OUT_INTRA_BSS_EQUIP_FAIL is pegged when an assignment failure message contains an

equipment failure cause or KSW/highway fault.
OUT_INTRA_BSS_HO_CLEARED is pegged when a call is cleared down during an intra-BSS

handover.
Analysis
This statistic can be used for trend analysis of intra-BSS handovers on a per (handover) scenario
basis.
Reference GSM 4.08, 3.8.0, 3.4.4.4.

GSM 8.08, 3.9.2, 3.2.1.16 and 3.2.1.20.
GSM 4.08, 3.8.0, 3.4.4.4 & 7.3.6 and 9.1.16.
GSM 8.08, 3.9.2, 3.1.5.3.2 and 3.2.1.16.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.1.1.
GSM 4.08, 3.8.0, 3.4.4.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.3.1.
GSM12.04, 3.2.0, B.1.1.9.
GSM 8.08, 3.9.2, 3.1.7 and 3.1.5.2.1 and 3.2.1.12 & 3.2.1.25.
Metrica.
Network planning.
Fault finding.
Key statistics:
HANDOVER_SUCCESS_RATE,
SUCCESS_INTERNAL_HO,
UNSUCCESS_INTERNAL_HO_REEST,
UNSUCCESS_INTERNAL_HO_NOREEST.
Basis Cell.
Type Counter array.
68P02901W56-T 4-145
Jan 2010
PACKET_SYSINFO_REQ Chapter 4: Cell statistics
PACKET_SYSINFO_REQ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PACKET_SYSINFO_REQ statistic tracks MS requests for BCCH/PBCCH GPRS system

information on a per-cell basis.
Pegging
The BSS pegs the PACKET_SYSINFO_REQ statistic whenever a request for BCCH/PBCCH
GPRS system information is received from the MS.
For a given PACKET SI/PSI STATUS request, only one bin in the counter array is pegged. The
bin definitions are shown in Table 4-47.
Table 4-47 PACKET_SYSINFO_REQ bins
Bin Description
0 Valid normal PACKET SI STATUS message or valid normal PACKET PSI STATUS
message received from the MS. For the purposes of this statistic, a valid, normal
message is any valid PACKET SI/PSI STATUS request which is not recorded by bin
1, bin 2, or bin 3.
1 Invalid PACKET SI STATUS message or invalid PACKET PSI STATUS message received
from the MS. Unexpected messages are also considered invalid.
2 PACKET SI STATUS message or PACKET PSI STATUS message not handled because
of resource limitations [for example, congestion, or an event which indicates that the
MS cannot handle BSS response messages (for example, abnormal release of an
MS's TBFs or MS changes serving cells)].
3 Valid PACKET SI STATUS message or valid PACKET PSI STATUS message received
from the MS requesting GPRS system information changemarks.
Analysis
Reference 3GPP TS GERAN 44.060 Mobile Station (MS) – Base Station System
(BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC)
protocol section 5.5.1.4 and 5.5.1.4.3.
Usage GPRS system information/Packet system information.
Basis Cell.
Type Counter array.
4-146 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PACKET_SYSINFO_RESP
PACKET_SYSINFO_RESP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PACKET_SYSINFO_RESP statistic tracks BSS responses to MS requests for BCCH/PBCCH

GPRS system information on a per-cell basis.
Pegging
The BSS pegs the PACKET_SYSINFO_RESP statistic for each RLC/MAC block sent in response
to an MS request for PBCCH/BCCH GPRS system information.
Each PACKET SI/PSI STATUS request generates zero or more response messages.
For a given downlink control message, only one bin in the counter array is pegged. The bin
definitions are shown in Table 4-48.
Table 4-48 PACKET_SYSINFO_RESP bins
Bin Description
0 PACKET SERVING CELL DATA message scheduled in response to a PACKET SI
STATUS or PACKET PSI STATUS message.
1 Non encapsulated PSI message scheduled in response to a PACKET PSI STATUS
message.
2 PSI1 or PSI13 message scheduled in response to an MS request with an out of date
PBCCH_CHANGE_MARK or BCCH_CHANGE_MARK.
Analysis
Reference 3GPP TS GERAN 44.060 Mobile Station (MS) – Base Station System
(BSS) interface; Radio Link Control/ Medium Access Control (RLC/MAC)
protocol section 5.5.1.4 and 5.5.1.4.3.
Usage GPRS system information/Packet system information.
Basis Cell.
Type Counter array
68P02901W56-T 4-147
Jan 2010
PAGE_REQ_FROM_MSC Chapter 4: Cell statistics
PAGE_REQ_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGE_REQ_FROM_MSC statistic tracks the number of paging requests received from the
MSC or CS paging request received from the SGSN with Gs interface. This message is sent by
the network when attempting to locate the MS. Each Page message refers to only one MS. The
BSS in turn transmits a paging message which may include identities for more than one MS
(see ACCESS_PER_PCH).
Pegging
This statistic pegs the number of Paging messages received from the MSC or CS paging request
messages received from SGSN with Gs interface by the BSS. This statistic is pegged when a
Paging message is received pertaining to the cell in which the MS is paged.
Analysis
This statistic can be used for trend analysis of the number of paging requests received from the
MSC or the CS paging request messages from SGSN with Gs interface.
Reference GSM 4.08, 3.8.0, 3.3.2.1. GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.
Usage Quality of service monitoring: Paging analysis.
Basis Cell.
Type Counter.
4-148 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PAGING_REQUESTS_CS
PAGING_REQUESTS_CS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_REQUESTS_CS statistic tracks the number of paging requests received to be

transmitted to the CS.
This statistic is obtained by measuring the number of paging requests received from the
network for transmission on the PCH.
This statistic accounts for any Circuit Switched (CS) paging message that makes use of a PCH
block. This statistic is like PCH_Q_PAGE_DISCARD except that the messages are sent, not
discarded.
Pegging
This statistic pegs every multiframe for each message going over a paging block (PCH).
Analysis
This statistic can be used for trend analysis of the number of paging requests received.
Reference 3GPP TS Release 5.

Basis Cell.
68P02901W56-T 4-149
Jan 2010
PAGING_REQUESTS_PS Chapter 4: Cell statistics
PAGING_REQUESTS_PS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_REQUESTS_PS statistic tracks the number of paging requests received to be

transmitted to the PS.
This statistic is obtained by measuring the number of paging requests received from the
network for transmission to the PCH.
This statistic accounts for any Packet Switched (PS) paging message that makes use of a PCH
block. This statistic is like PCH_Q_PAGE_DISCARD except that the messages are sent, not
discarded.
Pegging
This statistic pegs every multiframe for each message going over a paging block (PCH).
Analysis
a cell.

Basis Cell.
4-150 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PCH_AGCH_Q_LENGTH
PCH_AGCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PCH_AGCH_Q_LENGTH statistic tracks the mean number of messages reported in the
PCH-AGCH queue.
The statistic is modified to support Circuit Switched (CS) pages only.
Pegging
This statistic pegs once per paging multiframe, by summing the total number of messages in
the paging queue. At the end of the interval, the mean number of messages are calculated and
reported.
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.
Reference GSM 12.04, 4.2.1, B.2.1.1

Usage Quality of service: Paging analysis.
Optimization.
Network planning.
Basis Cell.
Type Gauge.
Alarm Minor.
68P02901W56-T 4-151
Jan 2010
PCH_Q_PAGE_DISCARD Chapter 4: Cell statistics
PCH_Q_PAGE_DISCARD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PCH_Q_PAGE_DISCARD statistic tracks the number of paging messages discarded from
the PCH queue before they could be transmitted.
A page may be discarded from the queue for the following reasons: queue overflow, priority
insertion causing an overflow, and an in_queue timer expiry. The only cause for discarding
pages in the Motorola BSS is queue overflow.
The statistic is modified to count both Circuit Switched (CS) and Packet Switch (PS) pages.
The bins are:

• CS pages discarded.
• PS pages discarded.
This statistic is obtained by measuring the number of Paging requests, which are discarded from
the PCH queue before they could be transmitted. Pages can be discarded from the queues
(assuming that queuing is in operation) for some reasons, including queue overflow, priority
insertion in the queue causing an overflow and in-queue timer expiry.
Pegging
This statistic pegs each time a page from the MSC is overwritten while in the queue.
The statistic also pegs for CS and PS pages as well as the assignments which the BSS was
going to send over the PCH.
Analysis
paging messages that may be discarded from the PCH queue that are acceptable in normal
system operations.
Reference GSM 12.04, 4.2.1, B.2.1.8

Optimization.
Network planning.
Basis Cell.
Type Counter.
Alarm Major.
4-152 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_ADMISSION
PFC_ADMISSION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_ADMISSION statistic counts the number of successful admissions of a PFC.
Pegging
The PFC_ADMISSION statistic is pegged every time an admission of a PFC is successful with or
without self downgrade. The bin pegged depends on the the ARP IE or traffic class/precedence
class of the PFC as shown in Table 4-49.
Table 4-49 PFC_ADMISSION bins

0 PFC_ADMISSION_LVL_1 Admission successful – priority level 1
NOTE
• When QoS is disabled, no bins are pegged.
68P02901W56-T 4-153
Jan 2010
Analysis
Reference None.
Basis Cell.
Type Extra large counter array.
4-154 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_ADMISSION_TRAFFIC_CLASS
PFC_ADMISSION_TRAFFIC_CLASS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_ADMISSION_TRAFFIC_CLASS statistic is pegged upon successful admission of a

PFC. The PFC may have to be self downgraded for admission. Based on the traffic class of the
PFC after admission the bins are pegged. No bins are pegged when QoS is disabled.
Pegging
Bin 0 is not pegged when Streaming is disabled. The Conversational PFCs is admitted as the
Streaming traffic class and pegged in bin 0. The Best Effort and PFC_unaware are pegged
in the same bin, since if PFC_unaware MS arrives in downlink first and its downlink data is
tagged with PFI of 0, BSS has to peg its admission under the PFC as Best Effort.
Table 4-50 PFC_ADMISSION_TRAFFIC_CLASS bins
Bin Description
0 Admission successful - Streaming.
1 Admission successful - Interactive THP1.
4 Admission successful - Background.
5 Admission successful - SMS.
6 Admission successful - Signaling.
7 Admission successful - Best Effort and PFC_unaware.
NOTE

• PFC-unaware PFCs for signaling is pegged as Signaling (bin 1).
68P02901W56-T 4-155
Jan 2010
Analysis
This statistic is pegged every time an admission of a PFC is successful with or without self
downgrade.
Reference None.
Basis Cell.
4-156 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_DOWNGRADE_FAILURE
PFC_DOWNGRADE_FAILURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_DOWNGRADE_FAILURE statistic counts the number of downgrade failures of PFCs

in a given statistical measurement interval.
Pegging
The PFC_DOWNGRADE_FAILURE statistic is pegged every time a PFC downgrade fails. The
bin pegged depends on the priority level of the PFC as shown in Table 4-51.
Table 4-51 PFC_DOWNGRADE_FAILURE bins

0 PFC_DNGRADEFAIL_LEVEL_1 Downgrade failures of PFCs with priority level 1
NOTE
• When ARP is disabled, all downgrade successes are pegged against ARP3.
68P02901W56-T 4-157
Jan 2010
Analysis
The PFC_DOWNGRADE_FAILURE statistic counts the number of downgrade failures of PFCs

in a given statistical measurement interval.
Reference None.
Basis Cell.
4-158 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_DOWNGRADE_SUCCESS
PFC_DOWNGRADE_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_DOWNGRADE_SUCCESS statistic counts the number of successfully downgraded

PFCs in a given statistical measurement interval.
Pegging
The PFC_DOWNGRADE_SUCCESS statistic is pegged every time an already admitted PFC is

successfully downgraded. The bin pegged depends on the priority level of the PFC as shown in
Table 4-52.
Table 4-52 PFC_DOWNGRADE_SUCCESS bins

0 PFC_DNGRADESUCC_LVL_1 Downgraded PFCs with priority level 1
NOTE
When QoS is disabled, no bins are pegged.
68P02901W56-T 4-159
Jan 2010
Analysis
Reference None.
Basis Cell.
4-160 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_GBR_DL
PFC_GBR_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_GBR_DL statistic is pegged every time a real-time traffic class PFC is admitted. The
bin pegged depends on the guaranteed bit rate in the negotiated ABQP of the PFC for downlink.
No bins are pegged when streaming_enabled equals 0.
Pegging
The bins are pegged based on the guaranteed bit rate of the PFC for downlink.
Table 4-53 PFC_GBR_DL bins

0 PFC_GBR_DL_1_4 Guaranteed bit rate within the range (1kbps<=GBR< 4kbps)
11 PFC_GBR_DL_96_200 Guaranteed bit rate within the range (96kbps<=GBR<
200kbps)
576kbps)
8640kbps)
68P02901W56-T 4-161
Jan 2010
Analysis
The PFC_GBR_DL statistic counts the number of real-time traffic class PFCs which are admitted
with guaranteed bit rate for downlink in the ABQP parameters.
Reference None.
Basis Cell.
4-162 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_GBR_UL
PFC_GBR_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_GBR_UL statistic is pegged every time a real-time traffic class PFC is admitted. The
bin pegged depends on the guaranteed bit rate in the negotiated ABQP of the PFC for uplink.
No bins are pegged when streaming_enabled equals 0.
Pegging
The bins are pegged based on the guaranteed bit rate of the PFC for downlink.
Table 4-54 PFC_GBR_UL bins

0 PFC_GBR_UL_1_4 Guaranteed bit rate within the range (1kbps<=GBR< 4kbps)
11 PFC_GBR_UL_96_200 Guaranteed bit rate within the range (96kbps<=GBR<
200kbps)
576kbps)
8640kbps)
68P02901W56-T 4-163
Jan 2010
Analysis
The PFC_GBR_UL statistic counts the number of real-time traffic class PFCs which are admitted
with guaranteed bit rate for uplink in the ABQP parameters.
Reference None.
Basis Cell.
4-164 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_PREEMPTIONS
PFC_PREEMPTIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_PREEMPTIONS statistic counts the number of PFCs preempted in each traffic class,
for each ARP value.
When the total cell resources are sufficient, but 64k resources are insufficient, egprs mobiles
with low priority may be preempted and move from 64k PDs to 16k/32k PDs. This may also
cause some rejections. BSC statistics rejection and preemption due to lack of cell resources
are pegged.
Pegging
The PFC_PREEMPTIONS statistic is pegged every time PFCs are preempted due to admission
control or retention procedures. The bin pegged depends on the traffic class as shown in
Table 4-55.
Table 4-55 PFC_PREEMPTIONS bins

0 PFC_PREEMPTIONS_LVL_1 Preemptions of PFCs with priority level 1
68P02901W56-T 4-165
Jan 2010
NOTE
• Preemption of PFC_unaware PFCs is pegged against the bins for Best Effort
PFCs.
• When ARP is disabled, all preemption are pegged against ARP3.
• Since the BSS does not preempt PFCs with ARP rank 6, bins 0, 3, 6 and 12
are not pegged.
Analysis
The PFC_PREEMPTIONS statistic counts the number of PFCs preempted in each traffic class,
for each ARP priority level value.
Reference None.
Basis Cell.
4-166 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_PREEMPTIONS_TRAFFIC_CLASS
PFC_PREEMPTIONS_TRAFFIC_CLASS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_PREEMPTIONS_TRAFFIC_CLASS statistic counts the number of PFCs preempted in

each Traffic Class. No bins are pegged when QoS is disabled.
Pegging
The bins are pegged based on the traffic class of the PFC as shown inTable 4-56.
Table 4-56 PFC_PREEMPTIONS_TRAFFIC_CLASS bins

0 PREEMPTIONS_TRFC_CLASS_STRM Streaming.
1 PREEMPTIONS_TRFC_CLASS_THP1 Interactive THP1.
4 PREEMPTIONS_TRFC_CLASS_BGRN Background.
5 PREEMPTIONS_TRFC_CLASS_EFF Best Effort and PFC Unaware.
Analysis
This statistic is pegged every time a PFC is preempted due to admission control or retention
procedures.
Reference None.
Usage GPRS Quality of Service
Basis Cell.
68P02901W56-T 4-167
Jan 2010
PFC_REJ_DGRD_PRMPT_CELL Chapter 4: Cell statistics
PFC_REJ_DGRD_PRMPT_CELL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_REJ_DGRD_PRMPT_CELL statistic counts the number of PFC requests rejected,

downgraded, or preempted by the PCU due to a lack of PRP or cell resources. It also keeps
track of the number of PFC downgrades and preemption due to cell or PRP retentions on a
per cell basis.
are pegged.
Pegging
The PFC_REJ_DGRD_PRMPT_CELL statistic pegs whenever a PCU preempts, rejects, or

downgrades a PFC request due to a lack of cell or board resources or whenever a PFC is
downgraded or preempted for cell or board retention purposes on a per cell basis. Table 4-57
describes the causes for preemption, rejection, or downgrade and describes what action the
operator can take to reduce the number of these in the future.
Table 4-57 PFC_REJ_DGRD_PRMPT_CELL bins
Bin Cause Description of cause Remedial action

0 Rejection due The PCU does not have enough MTBR Increase the number of
to lack of cell in the cell to admit a PFC. GPRS timeslots in the
resources. cell.
1 Rejection due The PCU does not have enough MTBR Adjust the MTBR
to lack of PRP in the board to admit a PFC. commitments for
resources. different traffic classes.
2 Downgrade due The PCU does not have enough MTBR Adjust the MTBR
to lack of cell in the cell to maintain a PFC’s current commitments for
resources. commitment and has reduced the different traffic classes.
PFC’s MTBR due to the admission of
a higher priority PFC.
3 Downgrade due The PCU does not have enough MTBR Adjust the MTBR
to lack of PRP on the PRP to maintain a PFC’s commitments for
resources. current commitment and has reduced different traffic classes.
the PFC’s MTBR due to the admission
of a higher priority PFC.
Continued
4-168 68P02901W56-T
Jan 2010
Table 4-57 PFC_REJ_DGRD_PRMPT_CELL bins (Continued)

4 Preemption due The PCU does not have enough Adjust the MTBR
to lack of cell MTBR in the cell to maintain a PFC’s commitments for
resources. commitments due to a change in different traffic classes.
available resources or admission
of a higher priority PFC and has
preempted the PFC.
to lack of PRP MTBR on the PRP to maintain a commitments for
resources. PFC’s commitments due to admission different traffic classes.
of a higher priority PFC and has
preempted the PFC.
6 Downgrade due to The PCU does not have enough MTBR Increase the resources in
cell retention. in the cell to retain all the active PFC’s the cell.
commitments in the event of resource
shrinkage and has reduced the PFC’s
MTBR for cell retention purposes.
7 Downgrade due to The PCU does not have enough MTBR Increase the resources
PRP retention. on the PRP to retain all the active on the PRP.
PFC’s commitments in the event of
resource shrinkage and has reduced
the PFC’s MTBR for PRP retention
purposes.
8 Preemption due to The PCU does not have enough Increase the resources in
cell retention. MTBR in the cell to maintain a PFC’s the cell.
shrinkage and has preempted the PFC
for cell retention purposes.
9 Preemption due to The PCU does not have enough MTBR Increase the resources
PRP retention. on the PRP to maintain a PFC’s on the PRP.
shrinkage and has preempted the PFC
for PRP retention purposes.
NOTE
Bins 7 and 9 are not pegged.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-169
Jan 2010
PFC_REJECT_CAUSES Chapter 4: Cell statistics
PFC_REJECT_CAUSES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_REJECT_CAUSES statistic counts the number of PFC requests rejected by the PCU.
are pegged.
Pegging
The PFC_REJECT_CAUSES statistic is pegged whenever PCU rejects a PFC request due to a
lack of resources. The bin pegged depends on the problem resource. Table 4-58 describes
the causes for rejection and the action the operator can take to reduce the number of PFC
rejections in the future.
Table 4-58 PFC_REJECT_CAUSES bins
Remedial
Bin Display Name Cause Description of cause
action
0 PFC_MAX_PER_ Maximum Other than the pre-defined Reduce the
MS_EXCEEDED PFCs per MS PFCs, the BSS supports up to 4 number of
exceeded. negotiable PFCs simultaneously simultaneous
for each MS. Any subsequent negotiable
negotiable PFC requests from PFCs an MS
that MS is rejected under this is trying to
limitation. activate.
1 PFC_OUT_OF_ Out of TBF The PCU does not have all TBF
TBF_THP1 resources for resources required to service the
THP1. TBF for the requested THP/traffic
class; this includes timeslot
availability, USFs, TAIs and TFIs.
availability, USFs, TAIs, and TFIs.
Continued
4-170 68P02901W56-T
Jan 2010
Table 4-58 PFC_REJECT_CAUSES bins (Continued)

Remedial
Bin Display Name Cause Description of cause
action
TBF_BCKGRND resources for resources required to service the
Background. TBF for the requested THP/traffic
TBF_EFF_ resources for resources required to service the
UNAWARE Best Effort. TBF for the requested THP/traffic
TBF_SMS resources for resources required to service the
SMS. TBF for the requested THP/traffic
TBF_SIGNALLING resources for resources required to service the
Signaling. TBF for the requested THP/traffic
TBF_PAP resources for resources required to service the
PAP. TBF for the requested THP/traffic
9 PFC_STREAM_ Streaming The PCU cannot meet the ABQP Increase the
ABQP_NOT_MET ABQP cannot for the requested streaming PFC. Streaming
be met. transfer delay
or resource
avalibility,
or decrease
GBR.
10 PFC_OUT_OF_ Out of PFC The PCU has exhausted storage Reduce the
PFC_STORAGE storage. for PFCs. duration of
Packet Flow
Timer at the
SGSN.
11 PFC_MS_ MS The PCU cannot meet the MTBR or Decrease the
CAPABILITY Capability. GBR for the requested PFC due to MTBRs.
multislot capability of the mobile.
NOTE
When QoS is disabled, no bins are pegged.
68P02901W56-T 4-171
Jan 2010
Analysis
Reference None.
Basis Cell.
4-172 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_REJECTION
PFC_REJECTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_REJECTION statistic counts the number of unsuccessful admissions of a PFC.
are pegged.
Pegging
The PFC_REJECTION statistic is pegged every time an admission of a negotiable or Best Effort
PFC is unsuccessful. The bin pegged depends on the priority level of the PFC as shown in
Table 4-59.
Table 4-59 PFC_REJECTION bins

0 PFC_RJCT_LVL_1 Admission unsuccessful – priority level 1
NOTE
• When ARP is disabled, all unsuccessful admissions are pegged against ARP3.
68P02901W56-T 4-173
Jan 2010
Analysis
Reference None.
Basis Cell.
4-174 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PFC_REJECTION_TRAFFIC_CLASS
PFC_REJECTION_TRAFFIC_CLASS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_REJECTION_TRAFFIC_CLASS statistic is pegged for unsuccessful admissions of

PFCs. The bins are pegged based on the traffic class of PFC. No bins are pegged when QoS is
disabled. Bin 0 is not pegged when Streaming is disabled. The Conversational PFCs can only be
admitted as Streaming traffic class and are pegged in bin 0 if the admission is unsuccessful. The
Best Effort and PFC_unaware are pegged in the same bin, since if PFC_unaware MS arrives
in downlink first and its downlink data is tagged with PFI of 0, BSS has to peg its rejection
under the PFC as Best Effort.
Pegging
The PFC_REJECTION_TRAFFIC_CLASS statistic is pegged for unsuccessful admissions of

PFCs. The bin pegged depends on the PFC type as shown inTable 4-60.
Table 4-60 PFC_REJECTION_TRAFFIC_CLASS bins

0 PFC_RJCT_TRFC_CLS_STRM Admission unsuccessful - Streaming.
1 PFC_RJCT_TRFC_CLS_THP1 Admission unsuccessful - Interactive THP1.
2 PFC_RJCT_TRFC_CLS_THP2 Admission unsuccessful - Interactive THP2.
3 PFC_RJCT_TRFC_CLS_THP3 Admission unsuccessful - Interactive THP 3.
4 PFC_RJCT_TRFC_CLS_BGRN Admission unsuccessful - Background.
5 PFC_RJCT_TRFC_CLS_SMS Admission unsuccessful - SMS.
6 PFC_RJCT_TRFC_CLS_SIGNALLING Admission unsuccessful - Signaling.
7 PFC_RJCT_TRFC_CLS_UNAWARE Admission unsuccessful - Best Effort and
PFC_unaware.
Analysis
This statistic is pegged upon unsuccessful admission of a PFC.
Reference None.
Basis Cell.
68P02901W56-T 4-175
Jan 2010
PFC_TRANSFER_DELAY Chapter 4: Cell statistics
PFC_TRANSFER_DELAY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_TRANSFER_DELAY statistic is pegged every time a real-time traffic class PFC is
admitted. The bin pegged depends on the transfer delay value in the negotiated ABQP of the
PFC. No bins are pegged when streaming_enabled equals 0.
Pegging
The bins are pegged based on the transfer delay value of the PFC as shown in Table 4-61.
Table 4-61 PFC_TRANSFER_DELAY bins
0 PFC_TRANSFER_DELAY_LVL_1 Transfer delay within the range (10ms<=delay<

40ms).
70ms).
100ms).
130ms).
150ms).
300ms).
450ms).
600ms).
750ms).
950ms).
1500ms).
2000ms).
Continued
4-176 68P02901W56-T
Jan 2010
Table 4-61 PFC_TRANSFER_DELAY bins (Continued)

2500ms).
3000ms).
4000ms).
Analysis
The PFC_TRANSFER_DELAY statistic counts the number of real-time traffic class PFCs which
are admitted with transfer delay in the ABQP parameters.
Reference None.
Basis Cell.
68P02901W56-T 4-177
Jan 2010
PFC_UPGRADE Chapter 4: Cell statistics
PFC_UPGRADE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_UPGRADE statistic counts the number of upgraded PFCs in a given statistical
measurement interval.
Pegging
The PFC_UPGRADE statistic pegs every time PFC is upgraded. The bin pegged depends on the
priority level of the PFC as shown in Table 4-62.
Table 4-62 PFC_UPGRADE bins
Bin Display name Description

0 PFC_UPGRADE_LVL_1 Upgraded PFCs with priority
level 1
level 2
level 3
level 4
level 5
level 6
level 7
Continued
4-178 68P02901W56-T
Jan 2010
Table 4-62 PFC_UPGRADE bins (Continued)

Bin Display name Description
level 8
level 9
level 10
level 11
level 12
level 13
level 14
NOTE
• When ARP is disabled, all upgrades are pegged against ARP3.
Analysis
Reference None.
Basis Cell.
68P02901W56-T 4-179
Jan 2010
PPCH_Q_PAGE_DISCARD Chapter 4: Cell statistics
PPCH_Q_PAGE_DISCARD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PPCH_Q_PAGE_DISCARD statistic tracks the number of Packet Paging Request messages
discarded from the PPCH queue before they could be transmitted.
A page may be discarded from the queue for the following reasons: queue overflow, priority
insertion causing an overflow, and an in_queue timer expiry. The only cause for discarding
pages in the Motorola BSS is queue overflow.
Table 4-63 PPCH_Q_PAGE_DISCARD bins
Bin Description
0 CS pages discarded.
1 PS pages discarded.
Pegging
This statistic pegs each time a Packet Paging Request is discarded from the PPCH queue.
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.8

Optimization.
Network planning.
Basis Cell.
Type Counter array.
4-180 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PREEMPT_CAP
PREEMPT_CAP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PREEMPT_CAP statistic represents the number of calls that have the capability (pci=1)
to trigger preemption within the BSS. This statistic can only be enabled if the eMLPP feature
is unrestricted.
Pegging
The PREEMPT_CAP statistic is split into four bins which are pegged depending on the type of
preemption capable request received from the MSC. Details are shown in Table 4-64.
Table 4-64 PREEMPT_CAP bins

1 ASSIGN_REQ An ASSIGNMENT REQUEST which has PCI=1.
2 HO_REQ A HANDOVER REQUEST which has PCI=1.
3 INT_HO_REQ An Imperative Internal Handover request which has PCI=1.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-T 4-181
Jan 2010
QUEUE_PREEMPT_ATMPT Chapter 4: Cell statistics
QUEUE_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The QUEUE_PREEMPT_ATMPT statistic tracks the number of times the Queuing preemption
mechanism removes a lower priority queued request from the queue to enable a higher priority
request to be queued.
Pegging
The QUEUE_PREEMPT_ATMPT statistic is split into three bins which are pegged depending
on the type of service being removed from the queue due to preemption. Details are shown in
Table 4-65.
Table 4-65 QUEUE_PREEMPT_ATMPT bins

0 ASSIGN_REQ The number of queued ASSIGNMENT REQUESTs removed from the
queue due to preemption.
1 HO_REQ The number of queued HANDOVER REQUESTs removed from the
queue due to preemption.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-182 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF_LOSSES_SD
RF_LOSSES_SD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_LOSSES_SD statistic tracks the number of calls lost while using an SDCCH. If a TCH is
reconfigured as an SDCCH, only the SDCCH statistics are configured.
Pegging
The RF_LOSSES_SD statistic pegs the number of calls terminated on the SDCCH due to RF
problems.
This statistic pegs the lost calls after the call has been established on SDCCH, but not when
the CHAN_REQ_MS_FAIL statistic is pegged. It is subdivided into five bins, according to the
cause, as listed in Table 4-66.
Table 4-66 RF_LOSSES_SD bins
Bin Description
0 RX quality in uplink direction
1 RX quality in downlink direction
2 RX level in uplink direction
3 RX level in downlink direction
4 Others
The BTS implements an algorithm to determine the bin to be pegged. The Others bin includes
the following:
• After analyzing the measurement report, the statistic cannot be classified to bin 0 to bin 3.
• There is no measurement report available.

When a dropped call occurs, the algorithm analyzes the UL and DL measurement reports in the
BTS and generates a reason code. The BTS then pegs the statistic.
Analysis
The statistic is measured at pre-defined intervals of 30 minutes or 60 minutes. A UWORD is

expected for each bin. One unit represents one dropped call.
68P02901W56-T 4-183
Jan 2010
If the specified threshold is exceeded, the 0. CELL: Radio frequency losses while using
an SDCCH - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.04, 3.1.0, B.1.1.5.

GSM 4.08, 3.8.0, 3.5.2 and 9.1.27a and 10.5.2.19.
Usage RF loss.
Congestion.
Fault finding.
Installation and commissioning.
Key statistics:
RF_LOSS_RATE,
SDCCH_RF_LOSS_RATE.
Basis Cell.
Alarm Major.
4-184 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF_LOSSES_TCH
RF_LOSSES_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate
TCH, excluding in signaling mode.
NOTE
RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS on a per
timeslot level. The OMC-R rolls the information up to the cell level and refers to this
information as RF_LOSSES_TCH_ROLL.
Pegging
The RF_LOSSES_TCH statistic pegs the number of full rate and half rate calls that were
terminated on TCH due to RF problems.
The RF_LOSSES_TCH statistic is the total number of all bin values. It is composed of calls lost
while using a TCH, excluding in signaling mode. If a TCH is reconfigured as an SDCCH, only the
SDCCH statistics are configured. The statistic counts the number of call drops and is further
subdivided into seven bins, according to the cause, as listed in Table 4-67.
Table 4-67 RF_LOSSES_TCH bins
Bin Description
4 Timing Advance (not implemented in GSR10)
5 Sharp decrease of signal level
6 Others
the following:

When a dropped call occurs due to RF problems on TCH, the algorithm analyzes the UL and DL
measurement reports in the BTS and generates a reason code. The BTS then pegs the statistic.
68P02901W56-T 4-185
Jan 2010
Analysis

expected for each bin. One unit represents one dropped call.
If the specified threshold is exceeded, the 0. TIMESLOT: Radio frequency losses while
using a TCH– PM for RF_LOSSES_TCH statistic is generated.
Reference GSM 12.04, 3.1.0, B.1.1.5.

GSM 4.08, 3.8.0, 3.5.2, 9.1.27a and 10.5.2.19.
Usage RF loss.
Congestion.
Fault finding Installation and commissioning.
Key Statistics:
RF_LOSS_RATE,
TCH_RF_LOSS_RATE.
Basis Timeslot.
Alarm Major.
NOTE
RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency
hopping environment, this statistic cannot be useful at channel level; therefore, roll to
cell level.
4-186 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF_LOSSES_TCH_HR
RF_LOSSES_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic tracks the number of calls lost while using a half rate AMR and/or GSM TCH.
Pegging
This statistic pegs the number of the calls that were terminated on AMR or GSM TCH due
to RF problems.
The statistic is further subdivided into seven bins, according to the cause for the call being
dropped, as listed in Table 4-68.
Table 4-68 RF_LOSSES_TCH_HR bins
Bin Description
4 Timing Advance (not implemented in GSR10)
5 Sharp decrease of signal level
6 Others
the following:

When a dropped call occurs due to RF problems on TCH, the algorithm analyzes the UL and DL
measurement reports in the BTS and generates a reason code. The BTS then pegs the statistic.
Analysis

expected for each bin. One unit represents one dropped call. There is no alarm associated
with this statistic.
Reference None
Continued
68P02901W56-T 4-187
Jan 2010
Usage RF loss.
Congestion.
Fault finding.
Basis Timeslot.
4-188 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF_LOSSES_TCH_SIG
RF_LOSSES_TCH_SIG
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_LOSSES_TCH_SIG statistic tracks the number of calls lost while using a full rate or
half rate TCH in signaling mode.
NOTE
RF_LOSSES_TCH_SIG is the BSS MMI name of the statistic kept by the BSS on a
per timeslot level. The OMC-R rolls the information up to the cell level and refers
to this information as RF_LOSSES_TCH_SIG_ROLL.
Pegging
This statistic pegs the number of full rate and half rate calls that were terminated in signaling
mode because of RF problems. It is composed of calls lost while using a TCH in signaling mode.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are configured.
Analysis
Reference GSM 12.04, 3.1.0, B.1.1.5.

GSM 4.08, 3.8.0, 3.5.2, 9.1.27a and 10.5.2.19.
Usage RF loss.
Congestion.
Fault finding.
Key Statistic: RF_LOSS_RATE, TCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter.
68P02901W56-T 4-189
Jan 2010
RSS_ALLOC_RESERVE_BLOCK Chapter 4: Cell statistics
RSS_ALLOC_RESERVE_BLOCK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RSS_ALLOC_RESERVE_BLOCK statistic gives the reduction in the number of Packet

Uplink Assignments (PUA) in response to Packet Resource Request (PRR) following software
upgrade.
The RSS_ALLOC_RESERVE_BLOCK statistic is used to account for the change in the system
behavior with software upgrade. With the new cell statistic, the formula for evaluating the
two-phase access-success-rate accounts for the fact that not all single blocks request for a
two-phase access. The formula is defined by the key statistic UL_TBF_SUCCESS_RATE.
Pegging
This statistic is pegged when a single block requests for a two-phase access in an RSS function.
Analysis
This statistic is used for calculation of two-phase access-success-rate.
Reference None.
Usage System information.
Fault finding.
Basis Cell.
Type Counter.
4-190 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_CONGESTION
SDCCH_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_CONGESTION statistic tracks the amount of time that no SDCCH channel was
available in a cell.
Pegging
This statistic records the sum of the duration of periods when all the SDCCH channels in a
cell were busy. The statistic also collects the mean, maximum, and minimum time of SDCCH
congestion. If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are recorded.
Although the mean, maximum and minimum values are collected for this statistic, they can only
be viewed through the MMI using the disp_stats command.
Analysis
This statistic can be used for trend analysis of the length of time during which SDCCH channels
were not available.
Reference GSM 12.04, 3.1.0, B.1.3.5.

Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
NOTE
68P02901W56-T 4-191
Jan 2010
SECOND_ASSIGN_ATMPT Chapter 4: Cell statistics
SECOND_ASSIGN_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SECOND_ASSIGN_ATMPT statistic tracks the number of times the network initiated a
second assignment procedure on receipt of an Assignment Failure message from the MS.
Pegging
The BSS only attempts (initiates) a second assignment procedure on receipt of an Assignment
Failure message if the per BSS element second_asgnmnt is set.
Analysis
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
4-192 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_HANDOVER
SDCCH_HANDOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_HANDOVER statistic measures the number of an SDCCH handover.
Pegging
The SDCCH_HANDOVER statistic is pegged when any of the following conditions occur:
• A Clear Command is received in state 12 with cause value Handover Successful for an
SDCCH handover (outgoing inter BSS handover).
• An SDCCH handover is initiated (Incoming inter BSS handover).
• A successful internal inter cell SDCCH handover (incoming and outgoing intra BSS SDCCH
handover).
The SDCCH_HANDOVER statistic pegs the appropriate bin once for each occurrence of an
SDCCH handover and also keeps a total of all of the bins. The bins are shown in Table 4-69.
Table 4-69 SDCCH_HANDOVER bins

0 OUTGOING_INTRA_BSS_HO_SUC Outgoing intra BSS handover success.
1 OUTGOING_INTER_BSS_HO_SUC Outgoing inter BSS handover success.
2 INCOMING_INTRA_BSS_HO_SUC Incoming intra BSS handover success.
3 INCOMING_INTER_BSS_HO_ATMPT Incoming inter BSS handover attempt.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-193
Jan 2010
SECOND_ASSIGN_SUC Chapter 4: Cell statistics
SECOND_ASSIGN_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SECOND_ASSIGN_SUC statistic tracks the number of times that a second assignment
procedure initiated by the network is successfully completed, upon receipt of an Assignment
Complete message from the MS.
Pegging
The BSS only attempts (initiates) a second assignment procedure on receipt of an Assignment
Failure message if the per BSS element second_asgnmnt is set.
Analysis
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
4-194 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SMS_INIT_ON_SDCCH_HO_OUT
SMS_INIT_ON_SDCCH_HO_OUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SMS_INIT_ON_SDCCH_HO_OUT statistic measures the number of an outgoing SDCCH

handover over SAPI3 (SMS).
Pegging
The SMS_INIT_ON_SDCCH_HO_OUT statistic when an existing SAPI3 connection is

disconnected due to any of the following:
• RRSM transition 51, when RRSM receives a Channel Activation Ack from RSS for an
intra cell handover.
• RRSM transition 40, when RRSM receives an Initiate Handover message from SSM for
an internal or external inter cell handover.
The SMS_INIT_ON_SDCCH_HO_OUT statistic pegs the appropriate bin once for each
occurrence of an sms disconnection on an SDCCH handover-out and also keeps a total of all of
the bins. The bins are shown in Table 4-70.
Table 4-70 SMS_INIT_ON_SDCCH_HO_OUT bins

0 SMS_SDCCH_HO Intra cell handover
_OUT_INTRA_CELL
1 SMS_SDCCH_HO Inter cell handover
_OUT_INTER_CELL
Analysis
Reference None
Basis Cell.
Type Counter array.
68P02901W56-T 4-195
Jan 2010
SIGNALLING_HANDOVER Chapter 4: Cell statistics
SIGNALLING_HANDOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SIGNALLING_HANDOVER statistic tracks the number of SDCCH handovers and TCH
signalling handovers.
Table 4-71 SIGNALLING_HANDOVER bins

0 SIG_INTRA_CELL_HO Number of assignment commands sent to
_ATMPT the MS during an intra-cell handover on
SDCCH or TCH signalling.
1 SIG_INTRA_CELL_HO Number of successful intra-cell handovers
_SUC occurring on SDCCH or TCH signalling.
2 SIG_INTRA_CELL_HO Number of failed intra-cell handovers
_LOSTMS occurring on SDCCH or TCH signalling that
also failed to recover to the original cell.
3 SIG_OUT_INTRA_BSS Number of successful outgoing intra-BSS
_HO_SUC handovers occurring on SDCCH or TCH
signalling.
4 SIG_OUT_INTRA_BSS Number of handover commands sent to
_HO_ATMPT MS during an outgoing intra-BSS handover
occurring on SDCCH or TCH signalling.
5 SIG_OUT_INTRA_BSS Number of failed outgoing intra-BSS
_HO_LOSTMS handovers occurring on SDCCH or TCH
signalling in which the MS also failed to
recover to the original BSS.
6 SIG_OUT_INTER_BSS Number of handover commands sent to
_HO_ATMPT MS during an outgoing inter-BSS handover
7 SIG_OUT_INTER_BSS Number of CLRCMD radio interface
_HO_FAIL message failure messages in one interval
during the outgoing inter-BSS handover
8 SIG_OUT_INTER_BSS Number of CLRCMD equipment failure
_HO_EQUIP_FAIL messages in one interval during the
outgoing inter-BSS handover occurring on
SDCCH or TCH signalling.
9 SIG_IN_INTRA_BSS Number of successful incoming intra-cell
signalling.
Continued
4-196 68P02901W56-T
Jan 2010
Table 4-71 SIGNALLING_HANDOVER bins (Continued)

10 SIG_IN_INTRA_BSS Number of failed incoming intra-BSS
_HO_LOSTMS handovers occurring on SDCCH or TCH
signalling that also failed to recover to the
original cell.
11 SIG_IN_INTER_BSS Number of successful incoming inter-BSS
signalling.
Pegging
SIG_INTRA_CELL_HO_ATMPT is pegged after the channel activation message is received and

just before the assignment command is sent to the MS.
SIG_INTRA_CELL_HO_SUC is pegged each time an intra-cell handover performed message is

sent to the MS.
SIG_INTRA_CELL_HO_LOSTMS is pegged when a radio channel released message is received.
SIG_OUT_INTRA_BSS_HO_SUC is pegged when a handover performed message is sent.
SIG_OUT_INTRA_BSS_HO_ATMPT is pegged when the initiate handover message is sent.
SIG_OUT_INTRA_BSS_HO_LOSTMS is pegged if the MS fails to return to the original channel

during a handover attempt.
SIG_OUT_INTER_BSS_HO_ATMPT is pegged when the handover command is forwarded to

the MS.
SIG_OUT_INTER_BSS_HO_FAIL is pegged if the MS returns a case of radio interface failure

in the handover failure message.
SIG_OUT_INTER_BSS_HO_EQUIP_FAIL is pegged if the MS returns a case of equipment failure

in the handover failure message.
SIG_IN_INTRA_BSS_HO_SUC is pegged after the handover successful message is received.
SIG_IN_INTRA_BSS_HO_LOSTMS is pegged during an intra-BSS handover when

MT_BOTH_CHANS_RLSD, timer T3103, or MTU expire.
SIG_IN_INTER_BSS_HO_SUC is pegged when a handover successful message is received.
68P02901W56-T 4-197
Jan 2010
SMS_INIT_ON_TCH Chapter 4: Cell statistics
SMS_INIT_ON_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SMS_INIT_ON_TCH statistic tracks how many Short Message Service (SMS) transactions
occurred on a cell related to a TCH.
This statistic can be used to keep track of the number of times a Service Access Point (SAPI3)
connection is created, an sms requires a logical SAPI3 connection. Additionally, the statistic
can be used to determine how TCHs are being utilized (for example, for SMS as opposed to
normal voice traffic).
Pegging
This statistic is incremented upon successful SAPI3 connection related to a TCH.
Analysis
This statistic can be used for trend analysis of how many SMS transactions occurred on a
cell related to a TCH.
Usage Originated call and service/connection

request.
Basis Cell.
Type Counter.
4-198 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SMS_NO_BCAST_MSG
SMS_NO_BCAST_MSG
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SMS_NO_BCAST_MSG statistic tracks the number of times that a message has been
broadcast on a per cell basis.
Pegging
This statistic pegs each time a message is broadcast on the CBCH.
Analysis
This statistic can be used for trend analysis of how many times a message has been broadcast
on a per cell basis.

Basis Cell.
Type Counter.
68P02901W56-T 4-199
Jan 2010
T Chapter 4: Cell statistics
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The T statistic tracks the number of handover attempts per cell per cause. The handover
attempts include cases involving outgoing inter-cell handovers.
Table 4-72 T bins

0 UPQUAL Number of times an outgoing inter-cell handover is attempted
due to the Uplink signal quality in source cell.
1 UPLEVEL Number of times an outgoing inter-cell handover is attempted
due to the Uplink signal level in source cell.
2 DOWNQUAL Number of times an outgoing inter-cell handover is attempted
due to the Downlink signal quality in source cell.
3 DOWNLEVEL Number of times an outgoing inter-cell handover is attempted
due to the Downlink signal level in source cell.
4 DISTANCE Number of times an outgoing inter-cell handover is attempted
due to a weakening signal strength to/from MS because of the
distance from signal source.
5 UPINTERF Number of times an outgoing inter-cell handover is attempted
due to the Uplink signal interference in source cell.
6 DOWNINTERF Number of times an outgoing inter-cell handover is attempted
due to the Downlink signal interference in source cell.
7 POWERBDGT Number of times an outgoing inter-cell handover is attempted
due to the power budget assessment of signal strength in the
source cell.
8 CONGESTION Number of times an outgoing inter-cell handover is attempted
due to traffic channel (TCH) congestion in the source cell.
9 ADJ_CHAN_INTF Number of times an outgoing inter-cell handover is attempted
due to adjacent channel interference.
10 BAND_RE_ASSIGN Number of times an outgoing inter-cell handover is attempted
due to band reassignment in source cell.
11 BAND_HANDOVER Number of times an outgoing inter-cell handover is attempted
due to band handover.
Pegging
This statistic pegs the total number of handover attempts out of a specific cell and the cause
for each attempt. This statistic is pegged at the source cell.
4-200 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of the number of handover attempts per cell per
cause.
Reference GSM 12.04, 4.2.1, B.1.1.11
Usage Handover.
Quality of service.
Network planning.
Ladder: Intra-BSS handover.
Optimization.
Fault finding.
Basis Cell.
Type Counter array.
68P02901W56-T 4-201
Jan 2010
TCH_CONG_INNER_ZONE Chapter 4: Cell statistics
TCH_CONG_INNER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONG_INNER_ZONE statistic tracks the total length of time in which all of the full
rate TCHs in the inner zone of a concentric cell are busy. The Concentric Cell option must be
enabled for this statistic to be enabled, disabled, or displayed.
Pegging
The timer for this statistic is started when all TCHs belonging to full rate TCHs in the inner zone
are busy. The timer is stopped when an inner zone full rate TCH is freed.
Analysis
This statistic can be used for trend analysis of the length of time in which all of the full rate
TCHs in the inner zone of a concentric cell are busy.
Reference None.
Usage Network planning.
Basis Cell.
Type Duration.
4-202 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_CONG_INNER_ZONE_HR
TCH_CONG_INNER_ZONE_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic tracks the duration of time when there are no half rate AMR and/or GSM TCHs
available in the inner zone of a concentric cell or dual band cell.
Pegging
When the last inner zone half rate AMR and/or GSM TCH available is allocated a timer is
started. This timer is stopped when at least one inner zone half rate TCH becomes idle.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Duration.
68P02901W56-T 4-203
Jan 2010
TCH_CONGESTION Chapter 4: Cell statistics
TCH_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION statistic indicates the amount of time that no full rate TCH channels
were available in that cell.
The TCH_CONGESTION statistic is used only for outer zone resources when full rate TCH
congestion is being measured for Concentric Cells.
A congestion (or blocking) state occurs when all full rate channels available to traffic within a
cell (the number may vary over time due to failure or maintenance actions) are busy, where
busy means unavailable for allocation to a new call attempt.
Pegging
This statistic pegs the sum of the duration of periods when all full rate TCHs were busy.
The statistic also reports the mean, maximum and minimum time of full rate TCH congestion. If
a full rate TCH is configured as an SDCCH only the SDCCH statistics are configured.
Analysis
Reference GSM 12.04, 3.1.0, B.1.1.12

Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
4-204 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_CONGESTION_EN
TCH_CONGESTION_EN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_EN statistic indicates the time during which the incoming full rate
call is not served immediately as there are no TCH channels available in the cell.
Pegging
When the external queue is not set, the pegging timer for the enhancement TCH Congestion
statistic starts when an incoming full rate call is not served since there are no idle TCH channels
available in the cell. The timer stops when an idle channel is available.
When the external queue is set, the pegging timer for the enhancement TCH Congestion statistic
starts when an incoming full rate call is not served since there are no idle TCH channels available
in the cell. The timer stops when the incoming call gets the TCH channel or the call is dropped.
Analysis
Reference GSM 12.04, 3.1.0, B.1.1.12.

Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
68P02901W56-T 4-205
Jan 2010
TCH_CONGESTION_HR Chapter 4: Cell statistics
TCH_CONGESTION_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic tracks the duration of time when there are no half rate AMR and/or GSM TCH
channels available. For concentric cell or dual band cells, this measurement indicates half rate
AMR and/or GSM TCH congestion for the outer zone.
Pegging
When the last available half rate AMR and/or GSM TCH channel is allocated, a timer is started.
This timer is stopped when at least one half rate TCH channel becomes idle.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Duration.
4-206 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_DELAY
TCH_DELAY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_DELAY statistic tracks the mean delay and the statistical distribution of the delay
between an assignment request or handover request and a TCH being allocated for each cell
on the BSS.
As more calls (in proportion to the total number of calls) are queued, the mean delay is longer.
Queuing is only done if the assignment or Handover Request indicates that queuing is allowed
for that request. This statistic measures the queuing delay effectively. It is possible to have
assignments and handovers for which there is no delay in resource allocation. These no-delay
assignments are included in the mean delay statistic.
Pegging
A timer is started when the request is queued and stopped when the request is allocated.
Analysis
This statistic can be used for trend analysis of the queuing delay for a traffic channel being
allocated to a cell.
Reference GSM 12.04, 3.1.0, B.1.1.3.

GSM 3.01, 3.1.1, 4.1.
GSM 8.08, 3.9.2, 3.1.17.
GSM 4.08, 3.8.0, 5.2.1.1.10 and 5.2.2.8.
Usage Quality of service monitoring: Queuing delay.
Network planning.
Optimization.
Basis Cell.
Type Normal distribution.
68P02901W56-T 4-207
Jan 2010
TCH_PREEMPT_ATMPT Chapter 4: Cell statistics
TCH_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_PREEMPT_ATMPT statistic tracks the number of times the TCH preemption
mechanism is successful in finding and releasing resource(s) to satisfy a preempting
request. A single preempting request may preempt up to two active candidates to satisfy
the incoming request. For example, an FR only request preempts two HR candidates. The
TCH_PREEMPT_ATMPT statistic also captures the service type of the request causing the
preemption and the service type(s) of the preempted candidates.
Pegging
The TCH_PREEMPT_ATMPT statistic is split into four bins which are pegged depending on
the type of service triggering the preemption and the type of service being preempted. Details
are shown in Table 4-73.
Table 4-73 TCH_PREEMPT_ATMPT bins

0 CS-CS Point-to-point calls causing preemption of point-to-point calls.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-208 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_PREEMPT_FAIL_NO_CAND
TCH_PREEMPT_FAIL_NO_CAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_PREEMPT_FAIL_NO_CAND statistic tracks the number of times the TCH preemption
mechanism is unsuccessful due to the inability of finding a candidate resource to preempt.
Pegging
The BSS pegs the TCH_PREEMPT_FAIL_NO_CAND statistic when TCH preemption is

unsuccessful.
Analysis
times the TCH preemption mechanism is unsuccessful.
If the specified threshold is exceeded, the 28. CELL: TCH Preemption Failure Statistic
Alarm is generated. Refer to the manual Maintenance Information: Alarm Handling at the
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 4-209
Jan 2010
TCH_PREEMPT_FAIL_TIMEOUT Chapter 4: Cell statistics
TCH_PREEMPT_FAIL_TIMEOUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_PREEMPT_FAIL_TIMEOUT statistic tracks the number of times a preempting

request triggering the TCH preemption mechanism successfully, fails to be allocated a TCH
(resulting in a timeout). This can occur due to the preempted resources being used by higher
priority requests or due to problems on the Um interface during release of the preempted
candidates.
Pegging
The BSS pegs the TCH_PREEMPT_FAIL_TIMEOUT statistic when TCH preemption is

unsuccessful due to TCH resources not being made available following successful triggering
of the TCH preemption mechanism (resulting in a timeout).
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter.
4-210 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_PREEMPT_RQD
TCH_PREEMPT_RQD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_PREEMPT_RQD statistic tracks the number of times the TCH preemption mechanism
is triggered.
The BSS triggers TCH preemption when a request with preemption capability (PCI = 1 and
priority level less than 14) is unable to be allocated a resource immediately. Triggering of the
TCH preemption mechanism is dependent on the eMLPP feature being unrestricted and enabled.
Pegging
The TCH_PREEMPT_RQD statistic is split into four bins which are pegged depending on the
type of request which is triggering the TCH preemption mechanism. Details are shown in
Table 4-74.
Table 4-74 TCH_PREEMPT_RQD bins

1 ASSIGN_REQ TCH preemption mechanism triggered by an ASSIGNMENT REQUEST.
2 HO_REQ TCH preemption mechanism triggered by a HANDOVER REQUEST.
3 INT_HO_REQ TCH preemption mechanism triggered by an Imperative Internal
Handover request.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-T 4-211
Jan 2010
TCH_PREEMPT_NO_Q_ALLOC Chapter 4: Cell statistics
TCH_PREEMPT_NO_Q_ALLOC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of times the TCH preemption mechanism successfully allocates
a traffic channel after TCH preemption without queuing has been triggered. This statistic
contributes to the overall TCH blocking rate calculation.
Pegging
The BSS pegs the TCH_PREEMPT_NO_Q_ALLOC statistic when the BSS successfully allocates
a TCH after triggering TCH preemption without external queuing.
There are two bins:

• TCH_PREEMPT_NO_Q_ALLOC_ALL: Counts all successful TCH allocation after
preemption without external queuing in either zone.
• TCH_PREEMPT_NO_Q_ALLOC_IZ: Counts all successful TCH allocation after preemption

without external queuing in the inner zone.
Successful TCH allocation after preemption without external queuing in the outer
zone can be calculated by subtracting the TCH_PREEMPT_NO_Q_ALLOC_IZ from
TCH_PREEMPT_NO_Q_ALLOC_ALL.
Analysis
Reference None.
Usage Quality of service monitoring.
Network planning.
Fault finding.
Basis Cell.
Type Small Counter Array.
4-212 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_Q_LENGTH
TCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_Q_LENGTH statistic tracks the arithmetic mean of the number of queued TCH
assignment procedures. Queuing is done due to the Call Queuing feature, Emergency Call
Preemption, EGSM, and Directed Retry.
Pegging
This measurement is obtained by sampling the TCH queue length and reporting the current
length. The mean TCH queue length includes the number of queued assignment and external
handover requests.
Analysis
This statistic can be used for trend analysis of the number of queued TCH assignment
procedures.
Reference GSM 12.04, 4.2.1, B.2.1.15

Usage Quality of service: Network accessibility.
Network planning.
Optimization.
Basis Cell.
68P02901W56-T 4-213
Jan 2010
TCH_Q_REMOVED Chapter 4: Cell statistics
TCH_Q_REMOVED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_Q_REMOVED statistic tracks when a queued call is assigned to a Traffic Channel
(TCH).
Table 4-75 TCH_Q_REMOVED bins

0 ASSIGN_REQ_OZ_OZ Number of times an assignment resource is failed in the
outer zone and allocated to outer zone.
1 ASSIGN_REQ_IZ_IZ Number of times an assignment resource is failed in the
inner zone and allocated to inner zone.
2 HO_REQ_OZ_OZ Number of times a handover is requested.
3 ASSIGN_REQ_IZ_OZ Number of times an assignment resource is failed in the
inner zone and allocated to outer zone.
4 ASSIGN_REQ_OZ_IZ Number of times an assignment resource is failed in the
outer zone and allocated to inner zone.
Pegging
These bins are pegged upon removal of either an assignment request or handover request
from the TCH queue.
Analysis
This statistic can be used for trend analysis of the number of queued TCH assignment
procedures.
Reference None.
Usage Quality of service: Network accessibility.
Network planning.
Optimization.
Key statistics:
TCH_BLOCKING_RATE,
TCH_BLOCKING_RATE_INNER_Z,
TCH_BLOCKING_RATE_OUT_ZONE,
TCH_MEAN_ARRIVAL_RATE.
Basis Cell.
Type Counter array.
4-214 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_USAGE
TCH_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_USAGE statistic gives an indication of the total amount of traffic carried by the cell.
Active means connected (capable of transmitting circuit mode user data) and activated, for
example, used as a DCCH.
The TCH_USAGE statistic is used only for outer zone resources when TCH usage is being
measured for Concentric Cells.
The TCH_USAGE statistic measures only the usage of normal range channels in Extended
Range Cells.
Both TCH_USAGE and BUSY_TCH include the guard timer value. This is a counter value. The
sum equals the amount of time in milliseconds the TCH was busy, kept by internal timers.
Therefore, when the interval expires, TCH usage cannot be reported until the next interval.
Exercise caution if using this value over short interval periods. For example:
• Interval 0 starts.
• TCH 0 starts call - internal timer starts.
• TCH 1 starts call - internal timer starts.
• TCH 0 ends call - internal timer stops.
• TCH_USAGE counter incremented by time.
• Difference for TCH 0.
• Interval 0 expires.
The value reported for the interval only includes the call for TCH0.
• Interval 1 starts.
• TCH 1 ends a call - internal timer stopped.
• TCH_USAGE counter incremented by time.
• Difference for TCH 1.
Pegging
This statistic is the sum of the time that each TCH was active with a call for all TCHs on the cell.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics are configured.
68P02901W56-T 4-215
Jan 2010
Analysis
This statistic can be used for trend analysis of the total amount of traffic carried by the cell.
Reference GSM 4.08, 3.8.0, 3.1.4.

Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
Type Counter.
4-216 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_USAGE_EXT_RANGE
TCH_USAGE_EXT_RANGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_USAGE_EXT_RANGE statistic tracks the number of extended range traffic channels
in use.
This statistic may only be enabled if the Extended Range Cell feature is unrestricted and
Pegging
This statistic pegs each time an extended range traffic channel is used.
Analysis
This statistic can be used for trend analysis of the number of extended range traffic channels
in use.
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 4-217
Jan 2010
TCH_USAGE_INNER_ZONE Chapter 4: Cell statistics
TCH_USAGE_INNER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_USAGE_INNER_ZONE statistic tracks the usage of TCHs belonging to carriers in the
inner zone of a concentric cell. The Concentric Cell option must be enabled for this statistic to
be enabled, disabled, or displayed.
The TCH_USAGE statistic is used only for outer zone resources when the Concentric Cells
feature is unrestricted.
Pegging
This statistic pegs when a TCH belonging to a carrier in the inner zone is used.
Analysis
This statistic can be used for trend analysis of the usage of TCHs belonging to carriers in
the inner zone of a concentric cell.
Reference None.
Basis Cell.
Type Counter.
4-218 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TIMER_EXP_PAP_CONV
TIMER_EXP_PAP_CONV
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TIMER_EXP_PAP_CONV statistic counts the following:

• The number of times the RA_Capability_Update guard Timer (T5), the CREATE_BSS_PFC
guard timer (T6) or the MODIFY_BSS_PFC guard timer (T8) expires.
• PFT expires.
• The number of times a PAP flow is converted to Best Effort due to final T6 expiry.
• The PAPs created due to the MS sending another channel request because of T3168 expiry.
Pegging
The TIMER_EXP_PAP_CONV statistic is pegged every time T5, T6, T8, PFT expires or there is a
PAP to Best Effort conversion. Table 4-76 shows the bins associated with this statistic.
Table 4-76 TIMER_EXP_PAP_CONV bins
Bin Description
0 T5 expires.
1 T6 expires.
2 T8 expires.
3 PFT expiry with Downlink TBF active.
4 PAP created on T3168 expiry.
5 PAP to Best Effort conversion on final T6 expiry.
NOTE
When QoS is disabled, only bin 0 (T5 expires) is pegged.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-219
Jan 2010
TOTAL_CALLS Chapter 4: Cell statistics
TOTAL_CALLS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TOTAL_CALLS statistic tracks the total number of calls originated for each cell on the BSS.
Pegging
This statistic indicates the number of circuit-oriented calls that are originated in the cell. It is
pegged only once per connection at the time of the first successful TCH assignment procedure.
Subsequent channel changes, for example voice to data, are not counted.
This statistic does not necessarily peg all successful calls. It only pegs calls that have been
assigned to the TCH. For example, if the call fails to send a Direct Transfer Application Part
(DTAP) Connect Acknowledge, it still looks successful to the base.
NOTE
This statistic is not pegged on the short message service
Analysis
This statistic can be used for trend analysis of the total number of calls originated for each
cell on the BSS.
Reference GSM 4.08, 3.8.0, 5.2.

Usage Originated call and service/connection
request.
Network planning.
Key statistics:
CALL_SETUP_SUCCESS_RATE,
RF_LOSS_RATE,
TCH_MEAN_HOLDING_TIME,
TCH_MEAN_ARRIVAL_RATE,
TCH_RF_LOSS_RATE,
TOTAL_CALLS_KEY.
Basis Cell.
Type Counter.
4-220 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_NACK_BLKS
UL_RLC_NACK_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_NACK_BLKS statistic counts the GPRS/EGPRS RLC blocks that are sent due
to an explicit NACK from the BSS.
100 RLC radio blocks represent 1 unit. The translation of actual radio blocks are counted to
units at the end of the statistic interval. The maximum statistical interval is 60 minutes.
Pegging
The RLC radio blocks are counted as per the coding scheme.
Table 4-77 UL_RLC_NACK_BLKS bins
Bin
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
NOTE
Refer DL_RLC_NACK_BLKS on page 13-85 statistic for detailed bin description.
68P02901W56-T 4-221
Jan 2010
Analysis
This UL_RLC_NACK_BLKS statistic can be used with UL_RLC_STALLED_BLKS volume to

calculate the abnormal UL RLC Retransmission rate.
Reference None.

Basis Cell.
Type Extra-large counter array.
4-222 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_STALLED_BLKS
UL_RLC_STALLED_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_STALLED_BLKS statistic counts the GPRS/EGPRS UL RLC blocks sent due to
any RLC window stall in the cell.
100 RLC radio blocks represents 1 unit. The translation of actual radio blocks are counted to
units at the end of the statistic interval. The maximum statistical interval is 60 minutes.
Pegging
When the window is stalled, all UL radio blocks sent during this period are pegged as stalled.
The RLC radio blocks are counted as per the coding scheme.
Table 4-78 UL_RLC_STALLED_BLKS bins
Bin
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
NOTE
Refer DL_RLC_STALLED_BLKS on page 13-89 statistic for detailed bin description.
68P02901W56-T 4-223
Jan 2010
Analysis
The UL_RLC_STALLED_BLKS statistic can be used with UL_RLC_NACK_BLKS volume to

calculate the abnormal UL RLC Retransmission rate.
Reference None.

Basis Cell.
Type Extra-large counter array.
4-224 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_LLC_DATA_VOLUME
UL_LLC_DATA_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_LLC_DATA_VOLUME statistic counts the volume of uplink LLC data sent on the air
interface per traffic class PDUs for a given cell per traffic class.
Pegging
The UL_LLC_DATA_VOLUME statistic pegs during a given time interval. The bins represent
the volume of data on the uplink for various class types and ARP values as shown in Table 4-79.
The unit of measurement for the bins is 10 Kbytes for bins 0 to 5 and 1 Kbyte for bin 6.
Table 4-79 UL_LLC_DATA_VOLUME bins

0 UL_LLC_DATA_STREAM Volume of data on the uplink for Streaming.
1 UL_LLC_DATA_VOL_THP1 Volume of data on the uplink for Interactive THP1.
4 UL_LLC_DATA_VOL_BCKGRND Volume of data on the uplink for Background.
5 UL_LLC_DATA_VOL_BEST_EFF Volume of data on the uplink for Best Effort and PFC
unaware user data local TLLI. Unit size is 10Kbytes.
6 UL_LLC_DATA_VOL_SIG Volume of data on the uplink for Signaling and PFC
unaware non-local TLLI. Unit size is 1 Kbyte. Round
up on 1 Kbyte modulo upon the monitoring period
expiration.
NOTE
• When ARP is disabled, all volume of LLC is pegged against ARP3.

• When QoS is disabled all volume of LLC is pegged against Best Effort and
Signaling bins. PFC_unaware PFC data is pegged the Best Effort and Signaling
bins.
• Uplink PAP, SMS and Signaling LLC data will not be pegged.
The recommended statistical measurement interval is 30 minutes.
68P02901W56-T 4-225
Jan 2010
Analysis
Reference None.

Basis Cell.
4-226 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_LLC_TRANS_TIME
UL_LLC_TRANS_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the cumulative length in the number of 100 ms units to transmit all UL
LLC PDUs for a given cell per traffic class.
Pegging
The UL_LLC_TRANS_TIME statistic pegs during a given time interval. The bins represent the
volume of data on the uplink for various class types and ARP values as shown in Table 4-80. The
measurement unit is 10 seconds for bins 0 to 5 and 100 ms for bin 6.
Table 4-80 UL_LLC_TRANS_TIME bins

0 UL_LLC_TRANS_TIME_STREAM LLC transmission time for Streaming
1 UL_LLC_TRANS_TIME_THP1 LLC transmission time for
Interactive THP1
Interactive THP2
Interactive THP3
4 UL_LLC_TRANS_TIME_BCKGRND. LLC transmission time for
Background
5 UL_LLC_TRANS_TIME_BEST_EFF LLC transmission time for Best
Effort and PFC_unaware user data
Local TLLI
6 UL_LLC_TRANS_TIME_SIG LLC transmission time for Signaling
and PFC unaware non-local TLLI
NOTE
• When ARP is disabled, LLC transmission time is pegged against ARP3.

• When QoS is disabled LLC transmission time is pegged against Best Effort and
Signaling bins.
• Downlink PAP and SMS data are not pegged.
68P02901W56-T 4-227
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
4-228 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ZONE_CHANGE_ATMPT
ZONE_CHANGE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ZONE_CHANGE_ATMPT statistic tracks attempts of each type of concentric cell specific
handover. The Concentric Cell option must be enabled for this statistic to be enabled, disabled,
or displayed.
Table 4-81 ZONE_CHANGE_ATMPT bins (0–4)

0 INNER_TO_OUTER_ZONE Number of handover attempts from inner
zone to outer zone.
1 OUTER_TO_INNER_ZONE Number of handover attempts from outer
zone to inner zone.
2 INTRA_ZONE Number of intra-zone handover attempts.
3 TCH_ASSIGN_TO_INNER_ZONE Number of TCH assignment attempts to inner
zone cells.
4 IN_INTER_CELL_HO_TO_IN_ZONE Number of internal inter-cell handover
attempts to inner zone.
Pegging
Each bin is pegged when a corresponding concentric cell handover is attempted.
Analysis
This statistic can be used for trend analysis of the attempts of each type of concentric cell
specific handover.
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 4-229
Jan 2010
ZONE_CHANGE_SUC Chapter 4: Cell statistics
ZONE_CHANGE_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ZONE_CHANGE_SUC statistic tracks each type of successful Concentric Cell specific
handover. The Concentric Cell option must be enabled for this statistic to be enabled, disabled,
or displayed.
Table 4-82 ZONE_CHANGE_SUC bins (0–4)

0 INNER_TO_OUTER_ZONE Number of successful handovers from inner zone
to outer zone.
1 OUTER_TO_INNER_ZONE Number of successful handovers from outer zone
to inner zone.
2 INTRA_ZONE Number of successful intra-zone handovers.
3 TCH_ASSIGN_TO_INNER_ZONE Number of successful TCH assignments to inner
zone cells.
4 IN_INTER_CELL_HO_TO_IN_ZONE Number of successful internal inter-cell handovers
to inner zone.
Pegging
Each bin is pegged when a corresponding concentric cell handover is successful.
Analysis
This statistic can be used for trend analysis of each type of successful concentric cell specific
handover.
Reference None.
Basis Cell.
Type Counter array.
4-230 68P02901W56-T
Jan 2010
Chapter
Neighbor statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
When the BSS is configured to control inter-cell handovers and events occurring in the network
assist cell, there are statistics which may be used to track these events.
The inter-cell handover statistics provide the destination cell of an outgoing handover or the
origination cell of an incoming handover. The statistics also track handover information for a
pair of source and neighbor cells.
Neighbor statistics are described in Introduction to neighbor statistics on page 5-2.
68P02901W56-T 5-1
Jan 2010
Introduction to neighbor statistics Chapter 5: Neighbor statistics
Introduction to neighbor statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following terms are used in the description of neighbor cells:

• Source cell - the cell in which a handover is initiated. Each source cell may have up to
32 target (neighbor) cells.
• Target cell - the neighbor cell into which the MS may be handed over. There is no limit on
the number of source cells that may handover calls to a target cell.
The following limitations apply to neighbor statistics:

• Each neighbor statistic can be enabled for a maximum of 16 cells in a BSS. The cells for
which each of the statistics are enabled do not have to be the same.
When the copy_cell command is used to copy a cell for which one or more of the neighbor
statistics is enabled, all the statistics for the cell created by the copy_cell command is
disabled. The individual statistics for the new cell are enabled individually including the
neighbor statistics.
• IN_INTRA_BSS_NC_ATMPT and IN_INTRA_BSS_NC_SUC statistics are incremented in

the target cell and can only be pegged for up to 32 source cells.
• OUT_HO_NC_CAUSE_ATMPT and OUT_HO_NC_SUC statistics are incremented in the

source cell and can only be pegged for up to 32 target cells.
• If the BSS is configured to have the MSC control intra-BSS handovers, the incoming per
cell statistics are affected, and cannot be used to track handovers.
Outgoing neighbor cell statistics
Outgoing neighbor statistics track the number of attempted and successful handovers from a
source cell into a neighbor cell. The outgoing neighbor statistics are:
• OUT_HO_NC_CAUSE_ATMPT on page 5-13.
• OUT_HO_NC_SUC on page 5-15.
Example of tracked statistics
In this example, cell_0 has 32 neighbors (cell_1 through cell_32), and the
OUT_HO_NC_CAUSE_ATMPT statistic is enabled at cell_0.
The BSS tracks the intra-BSS handover attempts originating in cell_0 that hand into cell_1
through cell_32.
Example showing effects of the del_neighbor command
If the del_neighbor command is used to delete one of the neighbor cells of a source cell, only
the statistics for the remaining neighbor cells are pegged.
5-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Incoming neighbor statistics
OUT_HO_NC_CAUSE_ATMPT statistic is enabled at cell_0. The del_neighbor command is
used to delete cell_32 as a neighbor cell of cell_0.
The BSS tracks intra-BSS handover attempts originating in cell_0 that hand into cell_1 through
cell_31.
Example showing effects of the add_neighbor command
If the del_neighbor command is used to delete one of the neighbor cells of a source cell, only
the statistics for the remaining neighbor cells are pegged.
OUT_HO_NC_CAUSE_ATMPT statistic is enabled at cell_0. The add_neighbor command is
used to add cell_32 as a neighbor cell of cell_0.
The BSS tracks intra-BSS handover attempts originating in cell_0 that hand into cell_1 through
cell_32.
Incoming neighbor statistics
Incoming neighbor statistics track the number of attempted and successful handovers into a
neighbor cell from a source cell. Handovers are tracked for only 32 cells for each neighbor cell,
even if a neighbor cell has more than 32 source cells. The incoming neighbor statistics are:
• IN_INTRA_BSS_NC_ATMPT on page 5-8.
• IN_INTRA_BSS_NC_SUC on page 5-9.
Choosing source cells
An algorithm chooses which source cells to track for the incoming neighbor statistics. The
source cells are chosen with the following priority:
• Reciprocal neighbors are chosen. A reciprocal neighbor occurs when both the source cell
and the target cell have each other as a neighbor.
• Each cell is sequentially checked, starting at 0 (local cell ID), until a source which has
not been selected is found.
Effect of the del_neighbor or add_neighbor commands
When neighbor cells are added or deleted from a cell in which the incoming neighbor statistics
are enabled, the following checks are performed:
• If the cell is tracking 32 source cells, no changes are made.
• If the cell is not tracking 32 source cells, a check is done to see if new ones can be tracked.
• If new source cells can be added, reciprocal neighbors are added first, followed by
non-reciprocal neighbors, which are chosen by sequentially looking through the database.
68P02901W56-T 5-3
Jan 2010
Incoming neighbor statistics Chapter 5: Neighbor statistics
Example of tracked statistics
In this example, the BSS has 90 cells (cell_0 through cell_89), cell_1 through cell_10 have cell_0
as a neighbor, and the IN_INTRA_BSS_NC_ATMPT statistic is enabled at cell_0.
The BSS tracks intra-BSS handover attempts that hand into cell_0 originating from cell_1
through cell_10.
Example of when there are more than 32 neighbor cells
In this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 as neighbors. Cell_1
through cell_50 each have cell_0 as a neighbor. The incoming neighbor statistics are enabled at
cell_0. While cell_1 through cell_50 can hand into cell_0, the BSS can only track 32 of these cells.
The reciprocal neighbors (cell_1 through cell_16) are chosen for tracking first. Because another
16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50 are not
tracked because the 32 cell limit has been reached.
Example of when a reciprocal neighbor is added
16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50 are tracked
because the 32 cell limit has been reached.
A new neighbor (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbor
pair. The cells being tracked is not changed just because a new reciprocal neighbor pair has
been added because it is at the maximum number of cells it can track.
Example of when a neighbor cell is deleted
16 cells may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50 are tracked
because the 32 cell limit has been reached.
A new neighbor (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbor
pair. The cells being tracked is not changed just because a new reciprocal neighbor pair has
been added because it is at the maximum number of cells it can track.
Neighbor cell_0 is deleted from cell_18. When this cell is deleted, cell_0 only tracks 31 source
cells. Because 32 cells may be tracked, a search is done to see if there are any reciprocal
neighbors.
Since cell_45 was added creating a reciprocal pair, cell_45 would now be tracked. If a reciprocal
pair had not been available, cell_33 would have been chosen as the next non-reciprocal source
not tracked.
5-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Examples of notation and initial situation
Examples of notation and initial situation
The following are examples of typical handover situations to show how neighbor cell statistics
are pegged.
Notation
An example of the notation used in the examples is shown in Figure 5-1.
Figure 5-1 Notation used in handover examples
IN_INTRA_BSS_NC_ATMPT: 0 (B-A)
stat name peg count source cell_B and target cell_A
ti-GSM-Notation used in HO examples-00346-ai-sw
Initial situation
Table 5-1 shows an example of three cells: cell_A, cell_B, and cell_C. All four neighbor cell
statistics are enabled at cell_A. For this example, all cells are internal to the same BSS as
shown in Figure 5-2.
Figure 5-2 Internal cells
cell_A cell_B
cell_C
ti-GSM-Internal cells-00347-ai-sw
68P02901W56-T 5-5
Jan 2010
Examples of notation and initial situation Chapter 5: Neighbor statistics
Table 5-1 Neighbor cell statistics pegged
Neighbor status Initial peg count Peg source target

cell_B is a neighbor of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (B-A)
cell_A is a neighbor of cell_B IN_INTRA_BSS_NC_SUC 0 (B-A)
cell_C is a neighbor of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (C-A)
cell_A is a neighbor of cell_C IN_INTRA_BSS_NC_SUC 0 (C-A)
OUT_HO_NC_CAUSE_ATMPT 0 (A-B)
OUT_HO_NC_SUC 0 (A-B)
OUT_HO_NC_CAUSE_ATMPT 0 (A-C)
OUT_HO_NC_SUC 0 (A-C)
Successful handover (B-A)
an MS that originated in cell_B performs a successful handover into cell_A. The following
statistics are updated:
IN_INTRA_BSS_NC_ATMPT 1 (B-A)
IN_INTRA_BSS_NC_SUC 1 (B-A)
IN_INTRA_BSS_NC_ATMPT 0 (C-A)
IN_INTRA_BSS_NC_SUC 0 (C-A)
Successful handover (A-C)
The MS, which is now in cell_A, performs another successful handover into cell_C. The following
statistics are update:
5-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Network assist neighbor cell change statistics
Unsuccessful handover (C-A)
The MS in cell_C attempts a handover into cell_A, but is unsuccessful. The following statistics
are updated:
Network assist neighbor cell change statistics
Network assist cell change statistics are captured from the events occurring in the network
assist cell. The following are the statistics which track PCCC and PCCO attempts to the
neighbor cells:
• NUM_CELL_RESEL_NEI on page 5-10.
• NUM_CELL_RESEL_NEI_PCCN on page 5-11.
• NUM_CELL_RESEL_NEI_SUCC on page 5-12.
NOTE
There are statistics that capture PCCC and PCCO attempts to non-neighbor cells.
These are shown in Network assist cell change on page 4-8.
68P02901W56-T 5-7
Jan 2010
IN_INTRA_BSS_NC_ATMPT Chapter 5: Neighbor statistics
IN_INTRA_BSS_NC_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_NC_ATMPT statistic tracks the number of intra-BSS handover attempts

into a cell. and the location of the cell originating the handover attempt. Allows study of the
handover performance of a specific cell for each of its source cells. Provides information to
determine quality of service and to support optimization.
This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic is
enabled, a maximum of 32 source cells can be tracked.
Pegging
This statistic is pegged in the target cell against a specific source cell. This is done each time
the SSM decides to perform an intra-BSS handover where the target is an internal neighbor
which is first placed in the Handover Recognized message.
Analysis
This statistic can be used for trend analysis of the number of handover attempts into a cell and
the location of the cells originating the handover attempts.
Reference GSM 12.04, 4.0.0, B.2.2.1GSM 4.08, 8.08, 8.58

Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Basis NCell (Neighbor cell).
Type Counter.
5-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IN_INTRA_BSS_NC_SUC
IN_INTRA_BSS_NC_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_NC_SUC statistic tracks the successful incoming internal inter-cell

handovers per originating cell.
This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic is
enabled, a maximum of 32 source cells can be tracked.
Pegging
This statistic is pegged in the target cell upon notification of a successful intra-BSS handover
from a specific cell.
Analysis
This statistic can be used for trend analysis of incoming internal inter-cell handovers per
originating cell.
Reference GSM 12.04, 4.0.0, B.2.2.2GSM 4.08, 8.08, 8.58

Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Type Counter.
68P02901W56-T 5-9
Jan 2010
NUM_CELL_RESEL_NEI Chapter 5: Neighbor statistics
NUM_CELL_RESEL_NEI
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_NEI statistic measures the total number of PCCC and PCCO attempts
to a neighbor cell due to either congestion relief or RF based cell reselection. This statistic is
supported for a maximum of 16 cells with 32 GPRS neighbor cells for each cell.
One unit represents one attempt by the BSS to send a PCCC or PCCO message.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI statistic on a per-neighbor basis. Table 5-2 shows the
scenarios used to update the counter bins associated with this statistic. The corresponding per
cell statistic is pegged using a separate counter: NUM_CELL_RESEL_CELL on page 4-124.
Table 5-2 Bin update scenarios for NUM_CELL_RESEL_NEI
Bin Scenario
0 Attempted PCCC due to NACC network agrees with the MSs decision.
1 Attempted PCCO due to NACC network overrides the MSs decision.
2 Attempted PCCO due to microcellular algorithm.
3 Attempted PCCO due to congestion relief.
4 Attempted PCCO due to RF based NC2.
Analysis
Reference None.
Type Counter array.
5-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_CELL_RESEL_NEI_PCCN
NUM_CELL_RESEL_NEI_PCCN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_NEI_PCCN statistic measures the total number of PCCN attempts

by MSs to a neighbor cell. This statistic is supported for a maximum of 16 cells with 32 GPRS
neighbor cells for each cell.
One unit represents one PCCN received from the MS.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI_PCCN statistic on a per-neighbor basis when a PCCN

request is received for the neighbor cell. The corresponding per cell statistic is pegged using a
separate counter: NUM_CELL_RESEL_CELL_PCCN on page 4-125.
Analysis
Reference None.
Type Counter.
68P02901W56-T 5-11
Jan 2010
NUM_CELL_RESEL_NEI_SUCC Chapter 5: Neighbor statistics
NUM_CELL_RESEL_NEI_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_CELL_RESEL_NEI_SUCC statistic measures the total number of successful

PCCC and PCCO attempts to a neighbor cell due to either congestion relief or RF based cell
reselection that can be detected by the PCU. A cell reselection is not detectable under the
following circumstances:
• TLLI changing after an inter RAC cell reselection.
• Cell change taking too long so that the previous context is deleted at the PCU.
• The target cell being on another PCU.

One unit represents one successful cell reselection due to PCCC/PCCO.
This statistic is supported for a maximum of 16 cells with 32 GPRS neighbor cells for each cell.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI_SUCC statistic on a per-neighbor basis for every

successful cell resections to the neighbor cell due to PCCC/PCCO. The corresponding per cell
statistic is pegged using a separate counter: NUM_CELL_RESEL_CELL_SUCC on page 4-126.
Analysis
Reference None.
Type Counter.
5-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_HO_NC_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_HO_NC_CAUSE_ATMPT statistic tracks the number of handovers per neighbor per
cause. This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic
is enabled, a maximum of 32 target cells can be tracked.
This statistic provides information to determine quality of service and to support optimization. It
allows study of the handover performance of a specific cell for each of its neighboring target
cells.
Inter-band handovers are also tracked when the Multiband Handover feature is enabled. (Refer
to the description for Bin 10.)
Table 5-3 OUT_HO_NC_CAUSE_ATMPT bins (0–11)

0 UPQUAL Handovers due to uplink quality.
1 UPLEVEL Handovers due to uplink level.
2 DOWNQUAL Handovers due to downlink quality.
3 DOWNLEVEL Handovers due to downlink level.
4 DISTANCE Handovers due to distance.
5 UPINTERF Handovers due to uplink interference.
6 DOWNINTERF Handovers due to downlink interference.
7 POWERBDGT Handovers due to power budget.
8 CONGESTION Handovers due to congestion.
9 ADJ_CHAN_INTF Handovers due to adjacent channel interference.
10 BAND_RE_ASSIGN Handovers due to band reassignment.
11 BAND_HANDOVER Handovers between bands.
Pegging
This statistic pegs the total number of handover attempts out of a specific cell, the location of
the target cell, and the cause for each attempt. This statistic is pegged at the source cell.
68P02901W56-T 5-13
Jan 2010
Analysis Chapter 5: Neighbor statistics
Analysis
This statistic can be used for trend analysis of handover attempts per neighbor on a per cause
basis.
Reference GSM 12.04, 4.0.0, B.2.2.3GSM 4.08, 8.08, 8.58GSM

12.04, 4.2.1
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Ladder: Intra-BSS handover.
Type Counter array.
5-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_HO_NC_SUC
OUT_HO_NC_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_HO_NC_SUC statistic tracks the number of successful outgoing inter-cell handovers
per target cell. This statistic can be enabled for a maximum of 16 cells. For each cell where the
statistic is enabled, a maximum of 32 target cells can be tracked.
Pegging
This statistic pegs the total number of successful handovers out of a specific cell and the location
of the target cell for each successful handover.
Analysis
This statistic can be used for trend analysis of handover performance of specific cells for each of
its neighboring target cells.
Reference GSM 12.04, 4.0.0, B.2.2.4

GSM 4.08, 8.08, 8.58
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Type Counter.
68P02901W56-T 5-15
Jan 2010
Analysis Chapter 5: Neighbor statistics
5-16 68P02901W56-T
Jan 2010
Chapter
Carrier and timeslot statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Carrier and timeslot statistics are captured from events occurring in a carrier. They are
categorized into subgroups, each of which are described in Carrier and timeslot statistics
subgroups on page 6-2.
68P02901W56-T 6-1
Jan 2010
Carrier and timeslot statistics subgroups Chapter 6: Carrier and timeslot statistics
Carrier and timeslot statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Carrier and timeslot statistics are organized into the following major subgroups:
• Downlink RXQUAL (BER) on page 6-2.
• Uplink RXQUAL (U_BER) on page 6-2.
• Link balance verification on page 6-2.
• Timing advance on page 6-2.
• Miscellaneous on page 6-3.
• VersaTRAU on page 6-3.
• Usage congestion on page 6-3.
Downlink RXQUAL (BER)
Downlink receive quality statistics are used to track the Bit Error Rate (BER) of active channels.
The statistic BER on page 6-6 is the only downlink RXQUAL statistic.
Uplink RXQUAL (U_BER)
Uplink receive quality statistics are used to track the Bit Error Rate (BER) of active channels.
The statistic U_BER on page 6-34 is the only uplink RXQUAL statistic.
Link balance verification
Link balance verification statistics are used to track the link balance between air interface of
the uplink and downlink path loss. The following are the link balance statistics:
• CHAN_DL_TX_PWR_LVL on page 6-10.
• CHAN_UL_TX_PWR_LVL on page 6-13.
• PATH_BALANCE on page 6-28.
• UPLINK_PATH_LOSS on page 6-38.
Timing advance
The timing advance statistic ROC on page 6-32 is used to monitor the timing advance
measurements.
6-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Miscellaneous
Miscellaneous
Miscellaneous statistics are used to track several unrelated carrier and timeslot statistics. The
following are the miscellaneous carrier statistics:
• CHAN_REQ_MS_FAIL on page 6-11.
• FER_AMR_FR on page 6-17.
• FER_AMR_HR on page 6-19.
• FER_GSM_FR_EFR on page 6-21.
• FER_GSM_HR on page 6-24.
• INTF_ON_IDLE on page 6-26.
• RBER on page 6-30.
NOTE
If many statistics have been enabled for some BSS configurations, missing statistics
at the OMC PM report is displayed for the affected statistic intervals.
VersaTRAU
VersaTRAU statistics measure backhaul data associated with the VersaTRAU feature. The
following are the VersaTRAU statistics:
• DL_EGPRS_BACKHAUL_DEMAND on page 6-14.
• DL_EGPRS_BACKHAUL_USED on page 6-15.
• EGPRS_64K_CHANNEL_WIDTH on page 6-16.
• UL_EGPRS_BACKHAUL_DEMAND on page 6-36.
• UL_EGPRS_BACKHAUL_USED on page 6-37.
Usage congestion
Usage congestion statistics track the congestion processes not related to the directed retry
feature. The following are the usage congestion statistics:
• BUSY_TCH_CARR on page 6-8.
• BUSY_TCH_CARR_HR on page 6-9.
68P02901W56-T 6-3
Jan 2010
ALLOC_SDCCH_CARR Chapter 6: Carrier and timeslot statistics
ALLOC_SDCCH_CARR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_SDCCH_CARR statistic is the sum of the number of SDCCH allocations per
carrier within a cell.
Pegging
This statistic pegs each time an Immediate Assignment message is sent by the BSS. An
Immediate Assignment message is sent upon:
• Successful handover on an SDCCH channel.
• Successful immediate assignment on an SDCCH channel.
Analysis
This statistic can be used for trend analysis of SDCCH allocations and allows the calculation of
the mean hold time of an SDCCH per carrier.
Reference GSM 12.04, 3.1.0, B.1.3.3.

GSM 4.08, 3.8.0, 3.3.12, 3.4.3.1, 3.4.4.1, 9.1.2 to 9.1.4, 9.1.14 to 9.1.19.
Usage RF loss.
Congestion.
Quality of service monitoring: Call set-up.
Network planning.
Ladder: Immediate assignment successful, Intra-cell handover, Inter-BSS
handover, Connection establishment, Intra-BSS handover.
Basis Carrier.
Type Counter.
NOTE
RACHs on page 20-7.
6-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ALLOC_TCH_CARR
ALLOC_TCH_CARR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_TCH_CARR statistic provides the number of successful TCH allocations per carrier
within a cell for both call originations and hand-ins.
Pegging
This statistic pegs for successful TCH allocations per carrier within a cell as a result of a call
establishment or hand-in attempt:
directed retries.
• Successful allocation due to intra-cell hand in.
• Successful allocation due to inter-cell/intra-cell hand in.
• Successful allocation due to inter-BSS hand in.
This statistic is pegged before the transmission of the assignment/handover command to the
MS and, therefore, does not take into account the success or failure of the assignment/hand
in from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations and allows the calculation of the
mean hold time of a TCH per carrier.

Network planning.
Assignment to TCH.
Key statistics:
CELL_TCH_ALLOCATIONS,
TCH_CARRIER_MEAN_HOLDING_TIME,
TCH_MEAN_ARRIVAL_RATE,
TCH_MEAN_HOLDING_TIME,
TCH_RF_LOSS_RATE.
Basis Carrier.
Type Counter.
68P02901W56-T 6-5
Jan 2010
BER Chapter 6: Carrier and timeslot statistics
BER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for active
channels. The bit error rate value corresponds to the RXQUAL downlink measurement reports.
BER statistic measurements are reported only when the channel is active.
NOTE
BER on SDCCH channels are affected by phantom RACHs. BER on TCHs are not
affected. For a cell with a non-combined BCCH configuration, there are no values
presented on timeslot 0.
Pegging
The statistic pegs every 480 ms (corresponding to each SACCH multiframe).
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL values:
Table 6-1 Statistic values
RXQUAL BER (min to MAX)

0 0 to 0.2
1 0.2 to 0.4
2 0.4 to 0.8
3 0.8 to 1.6
4 1.6 to 3.2
5 3.2 to 6.4
6 6.4 to 12.8
7 greater than 12.8
NOTE
The bin ranges for this statistic cannot be changed.
6-6 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of the BER for active channels.
Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.

GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.
Usage RF loss.
Congestion.
Fault finding.
Basis Timeslot.
68P02901W56-T 6-7
Jan 2010
BUSY_TCH_CARR Chapter 6: Carrier and timeslot statistics
BUSY_TCH_CARR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_TCH_CARR statistic tracks the number of full rate and half rate TCHs allocated
during an interval.
This is a gauge statistic and produces a mean value indicating the average number of TCHs in
use during the interval. It is an indication of the average capacity for additional traffic in the
cell. This statistic includes TCHs used as a Dedicated Control CHannel (DCCH) in immediate
assignment mode. The BUSY_TCH_CARR time includes the guard time (the time allowed
between ending a call and starting another). Since the channel is not available to be used again
until the guard timer expires, it is not considered to be free until then.
Pegging
This statistic pegs when a change in the number of full rate and half rate TCHs in use are
detected.
Analysis

Usage Congestion.
Network planning.
Optimization.
Key statistic:
TCH_CARRIER_MEAN_HOLDING_TIME.
Basis Carrier.
Type Gauge.
6-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BUSY_TCH_CARR_HR
BUSY_TCH_CARR_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or GSM
TCH channels in use on a per-carrier basis.
Pegging
This statistic is updated each time an allocation or deallocation of a half rate AMR and/or
GSM TCH channel occurs.
Analysis
Reference None.
Network planning.
Service retain ability.
Basis Carrier.
68P02901W56-T 6-9
Jan 2010
CHAN_DL_TX_PWR_LVL Chapter 6: Carrier and timeslot statistics
CHAN_DL_TX_PWR_LVL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_DL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum BSS
(downlink) transmit power level. The reported value is in dBm units.
Pegging
This statistic pegs every SACCH multiframe.
Analysis
This statistic can be used for trend analysis of mean BSS transmit power levels.
Reference GSM 12.04, 4.2.1, B.2.1.28.

Usage Fault finding and Quality of service.
Basis Carrier.
6-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CHAN_REQ_MS_FAIL
CHAN_REQ_MS_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_REQ_MS_FAIL statistic tracks the number of times the BSS times out while waiting
for the MS to establish on the TCH/SDCCH, that was assigned to it during the immediate
assignment procedure.
An Immediate Assign message is sent to the MS on the Access Grant Channel (AGCH) and a
TCH/SDCCH is allocated. When the MS does not reply with a SABM on that TCH/SDCCH, the
allocated channel is relinquished, and the request forgotten.
This may be a normal occurrence on few occasions such as, when the MS is moving out of range,
the MS is failing, or the MS is switched off. However, frequent occurrences of this event within
a short period and/or geographically clustered may indicate a hardware failure.
NOTE
CHAN_REQ_MS_FAIL is the BSS MMI name of the statistic kept by the BSS on a
per-timeslot level. The OMC-R rolls the information up to the cell level and refers
to this information as CHAN_REQ_MS_FAIL_ROLL.
Pegging
This statistic pegs when the MS does not reply with Set Asynchronous Balanced Mode (SABM)
on the TCH/SDCCH. The bin pegged depends on the channel type that the MS failed on as
shown in Table 6-2.
Table 6-2 CHAN_REQ_MS_FAIL bins
Bin Description
0 MS failed while on an SDCCH.
1 MS failed while on a half rate TCH.
2 MS failed while on a full rate TCH.
68P02901W56-T 6-11
Jan 2010
Analysis Chapter 6: Carrier and timeslot statistics
Analysis
BSS timeouts while waiting for an MS to establish on the TCH/SDCCH assigned during the
immediate assignment procedure that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH failed
Reference GSM 4.08, 3.8.0, 3.3.1.4 and 9.1.17.

Usage Radio resource and allocation.
Fault finding.
Ladder: Immediate assignment blocked.
Key statistic:
SDCCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter array.
Alarm Minor.
NOTE
RACHs on page 20-7.
6-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CHAN_UL_TX_PWR_LVL
CHAN_UL_TX_PWR_LVL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_UL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum MS (uplink)
transmit power levels. The value is reported in dBm units.
Pegging
This statistic pegs every SACCH multiframe.
Analysis
This statistic can be used for trend analysis of mean MS transmit power levels.
Reference GSM 12.04, 4.2.1, B.2.1.29.

Usage Fault finding and Quality of service.
Basis Carrier.
68P02901W56-T 6-13
Jan 2010
DL_EGPRS_BACKHAUL_DEMAND Chapter 6: Carrier and timeslot statistics
DL_EGPRS_BACKHAUL_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_EGPRS_BACKHAUL_DEMAND statistic measures the mean and maximum value of

the demand for the downlink backhaul associated with an EGPRS RTF. This is the maximum
backhaul that the system could have used to service all the active data transfers if there were
no limits on the downlink backhaul associated with the RTF. It is obtained by maintaining the
mean and maximum values for backhaul demand for the downlink backhaul, associated with an
EGPRS over the statistical period.
Pegging
The DL_EGPRS_BACKHAUL_DEMAND statistic pegs every block period based on the

amount of backhaul requested (before any backhaul related restriction) and later applied in
the downlink by PDCHs on an EGPRS carrier.
Analysis
Reference None.
Usage VersaTRAU.
Basis Carrier.
Type Gauge.
Units
The unit for DL_EGPRS_BACKHAUL_DEMAND is in bytes. It includes the RLC blocks as well as
the VersaTRAU header, sampled every 20 ms RLC block period.
6-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_EGPRS_BACKHAUL_USED
DL_EGPRS_BACKHAUL_USED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_EGPRS_BACKHAUL_USED statistic measures the mean and maximum value for the
actual amount of downlink backhaul used for an EGPRS RTF. This is the actual backhaul that
the system used to service all the active data transfers on an EGPRS carrier, after accounting
for any coding scheme downgrades and radio block omissions in the downlink. It is obtained
by maintaining the mean and maximum values for backhaul usage for the downlink backhaul
associated with an EGPRS over the statistical period.
Pegging
The DL_EGPRS_BACKHAUL_USED statistic pegs every block period based on the amount
of backhaul used (accounting for any downgrades or preemptions due to backhaul related
restrictions) in the downlink by PDCHs on an EGPRS carrier.
Analysis
Reference None.
Usage VersaTRAU.
Basis Carrier.
Type Gauge.
Units
The unit for DL_EGPRS_BACKHAUL_USED is in bytes. It includes the RLC blocks as well as
68P02901W56-T 6-15
Jan 2010
EGPRS_64K_CHANNEL_WIDTH Chapter 6: Carrier and timeslot statistics
EGPRS_64K_CHANNEL_WIDTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_64K_CHANNEL_WIDTH statistic measures the mean and maximum value for the
VersaChannel width on a per-carrier basis for an EGPRS carrier. It is obtained by maintaining
the current width of the VersaChannel and the amount of time the width is unchanged over
the statistical period.
Pegging
The EGPRS_64K_CHANNEL_WIDTH statistic pegs whenever there is a change in the width of

the VersaChannel associated with a carrier.
Analysis
Reference None.
Usage VersaTRAU.
Basis Carrier.
Type Gauge.
Units
The unit for EGPRS_64K_CHANNEL_WIDTH is in bytes. It includes the RLC blocks as well as
6-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application FER_AMR_FR
FER_AMR_FR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The uplink FER_AMR_FR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for AMR full- rate calls. The
measurement period over which the calculation is made is a multiple of 480 ms.
During this FER measuring period, a multiple of 24 speech frames are decoded and the ratio is
calculated. The multiple is configured through the fer_meas_period parameter. The lookup
table is constructed based on the fer_meas_period parameter value. The ratio is converted to a
FER_AMR_FR Quality number between 0 and 9 using the lookup table.
For example:
• If fer_meas_period = 1, two bad frames out of 24 result in a ratio of 0.083:1. From
Table 6-4, this relates to an FER_AMR_FR Quality number of 2.
• If fer_meas_period= 2, then 2 bad frames out of 48 (24*2) result in a ratio of 0.0417:1.

From Table 6-4, this relates to an FER_AMR_FR Quality number of 2 (the ratio range is
from 0.0832/2 to 0.1240/2).
Pegging
This statistic pegs the uplink frame erasure rate for AMR full-rate calls for each carrier in a cell.
Table 6-3 FER_AMR_FR bins
Bin Description
0 Number of Erased frames per 24*N speech frame period is 0.
9 Number of Erased frames per 24*N speech frame period is 9~24*N.
68P02901W56-T 6-17
Jan 2010
Units Chapter 6: Carrier and timeslot statistics
Units
The FER_AMR_FR is reported using values 0 to 9 as follows.

Table 6-4 FER_AMR_FR Quality number conversion (n is the value of
fer_meas_period)
FER_AMR_HR
Quality FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416/n
1 0.0417/n to 0.0832/n
2 0.0833/n to 0.1249/n
3 0.1250/n to 0.1666/n
4 0.1667/n to 0.2082/n
5 0.2083/n to 0.2499/n
6 0.2500/n to 0.2916/n
7 0.2917/n to 0.3332/n
8 0.3333/n to 0.3749/n
9 0.3750/n to 1.0000
NOTE
For a cell with a non-combined BCCH configuration, there are no values presented
on TS 0.
FER_AMR_FR Quality is measured on a carrier basis for active channels after decoding
de-interleaving and error correction. Data for this statistic is reported by firmware to the
RSS/HO software process where it is pegged.
There are common adjustable bins for all FER counters. The values of the bins can be adjusted
by the operator.
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios with
regards to quality.
Reference None.
Usage Quality of service, Fault finding, RF loss, Congestion.
Basis Carrier.
6-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application FER_AMR_HR
FER_AMR_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The uplink FER_AMR_HR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for AMR half rate calls. The
FER_AMR_HR Quality number between 0 and 9 using the lookup table.
For example:
• If fer_meas_period= 1, 2 bad frames out of 24 result in a ratio of 0.083:1. From Table 6-6,
this relates to an FER_AMR_HR Quality number of 2.
• If fer_meas_period= 2, then two bad frames out of 48 (24*2) result in a ratio of 0.0417:1.
From Table 6-6, this relates to an FER_AMR_HR Quality number of 2 (the ratio range is
from 0.0832/2 to 0.1240/2).
Pegging
This statistic pegs the uplink frame erasure rate for AMR half rate calls for each carrier in a cell.
Table 6-5 FER_AMR_HR bins
Bin Description
68P02901W56-T 6-19
Jan 2010
Units
The FER_AMR_HR is reported using values 0 to 9 as follows.

Table 6-6 FER_AMR_HR Quality number conversion (n is the value of
fer_meas_period)
FER_AMR_HR
Quality FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416/n
1 0.0417/n to 0.0832/n
2 0.0833/n to 0.1249/n
3 0.1250/n to 0.1666/n
4 0.1667/n to 0.2082/n
5 0.2083/n to 0.2499/n
6 0.2500/n to 0.2916/n
7 0.2917/n to 0.3332/n
8 0.3333/n to 0.3749/n
9 0.3750/n to 1.0000
NOTE
on TS 0.
FER_AMR_HR Quality is measured on a carrier basis for active channels after decoding
by the operator.
Analysis
regards to quality.
Reference None.
Basis Carrier.
6-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application FER_GSM_FR_EFR
FER_GSM_FR_EFR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named FER.
Description
The uplink FER_GSM_FR_EFR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for non-AMR calls. The
FER_GSM_FR_EFR Quality number between 0 and 9 using the lookup table.
For example:
• If fer_meas_period= 1, 2 bad frames out of 24 result in a ratio of 0.083:1. From Table 6-8,
this relates to an FER_GSM_FR_EFR Quality number of 2.

From Table 6-8, this relates to an FER_GSM_FR_EFR Quality number of 2 (the ratio
range is from 0.0832/2 to 0.1240/2).
Pegging
This statistic pegs the uplink frame erasure rate for non_AMR calls for each carrier in a cell.
Table 6-7 FER_GSM_FR_EFR bins
Bin Description
Continued
68P02901W56-T 6-21
Jan 2010
Table 6-7 FER_GSM_FR_EFR bins (Continued)

Bin Description
Units
The FER_GSM_FR_EFR is reported using values 0 to 9 as follows.

Table 6-8 FER_GSM_FR_EFR Quality number conversion (n is the value of
fer_meas_period)
FER_GSM_FR_EFR
FER ratio (min:1 to max:1)
Quality number
0 0.0000 to 0.0416/n
1 0.0417/n to 0.0832/n
2 0.0833/n to 0.1249/n
3 0.1250/n to 0.1666/n
4 0.1667/n to 0.2082/n
5 0.2083/n to 0.2499/n
6 0.2500/n to 0.2916/n
7 0.2917/n to 0.3332/n
8 0.3333/n to 0.3749/n
9 0.3750/n to 1.0000
NOTE
on TS 0.
FER_GSM_FR_EFR Quality is measured on a carrier basis for active channels after decoding
by the operator.
6-22 68P02901W56-T
Jan 2010
Analysis
regards to quality.
Reference None.
Usage Quality of service, Fault finding, RF loss, and Congestion.
Basis Carrier.
68P02901W56-T 6-23
Jan 2010
FER_GSM_HR Chapter 6: Carrier and timeslot statistics
FER_GSM_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The uplink FER_GSM_HR Quality statistic is derived from a ratio of successfully decoded
good speech frames against unsuccessfully decoded bad frames for GSM half rate calls. The
FER_GSM_HR Quality number between 0 and 9 using the lookup table.
For example:
• If fer_meas_period= 1, 2 bad frames out of 24 result in a ratio of 0.083:1. From
Table 6-10, this relates to an FER_GSM_HR Quality number of 2.

From Table 6-10, this relates to an FER_GSM_HR Quality number of 2 (the ratio range is
from 0.0832/2 to 0.1240/2).
Pegging
This statistic pegs the uplink frame erasure rate for GSM half rate calls for each carrier in a cell.
Table 6-9 FER_GSM_HR bins
Bin Description
6-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Units
Units
The FER_GSM_HR is reported using values 0 to 9 as follows.

Table 6-10 FER_GSM_HR Quality number conversion (n is the value of
fer_meas_period)
FER_GSM_HR
FER ratio (min:1
Quality
to max:1)
number
0 0.0000 to 0.0416/n
1 0.0417/n to 0.0832/n
2 0.0833/n to 0.1249/n
3 0.1250/n to 0.1666/n
4 0.1667/n to 0.2082/n
5 0.2083/n to 0.2499/n
6 0.2500/n to 0.2916/n
7 0.2917/n to 0.3332/n
8 0.3333/n to 0.3749/n
9 0.3750/n to 1.0000
NOTE
on TS 0.
FER_GSM_HR Quality is measured on a carrier basis for active channels after decoding,
de-interleaving, and error correction. Data for this statistic is reported by firmware to the
by the operator.
Analysis
regards to quality.
Reference None.
Basis Carrier.
68P02901W56-T 6-25
Jan 2010
INTF_ON_IDLE Chapter 6: Carrier and timeslot statistics
INTF_ON_IDLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTF_ON_IDLE statistic indicates the maximum, minimum, and mean interference levels
experienced on idle channels as determined by the BSS.
the INTF_ON_IDLE statistic are shown in Table 6-11.
Table 6-11 Default bin ranges for INTF_ON_IDLE
Bin Range
0 0 - 5
1 6 - 10
2 11 - 15
3 16 - 20
4 21 - 25
5 26 - 30
6 31 - 35
7 36 - 40
8 41 - 45
9 46 - 65
Table 6-12 provides an indication of the interference on a channel by recording the

measurements of the received signal strength taken when the channel is idle. This measurement
parallels the activity of the channel selection algorithm of the Cell Resource Manager which
uses the same data to rank idle channels, giving preference to the channels with a lower
interference level. The measured signal level is mapped to an RXLEV value between 0 and 63.
Each RXLEV value corresponds to a dBm value, as shown in Table 6-12.
Table 6-12 Signal level
RXLEV value dBm level

0 less than -110 dBm
1 -110 dBm to -109 dBm
2 -109 dBm to -108 dBm
62 -49 dBm to -48 dBm
63 greater than -48 dBm
6-26 68P02901W56-T
Jan 2010
Pegging
This statistic pegs every 480 ms.
Analysis
This statistic can be used for trend analysis of interference levels experienced on idle channels.
Reference GSM 12.04, 3.2.0, B.1.1.13.

GSM 5.08, 3.6.0, 8.1-8.5 and Appendix A.3.ii.
Usage RF loss and congestion.
Network planning.
Fault finding.
Basis Timeslot.
68P02901W56-T 6-27
Jan 2010
PATH_BALANCE Chapter 6: Carrier and timeslot statistics
PATH_BALANCE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PATH_BALANCE statistic tracks the maximum, minimum, and mean link balance on the air
interface between the uplink and downlink path loss.
NOTE
The actual value for path_balance depends on the type of RF combining used.
Pegging
This statistic is pegged by the value calculated by the following equation:
path_balance = path loss + 110
where:
path loss = uplink path loss - downlink path loss
where:
uplink path loss = actual MS txpower - RXLEV_ul
downlink path loss = actual BTS txpower - RXLEV_dl
NOTE
The RXLEV_ul and RXLEV_dl values reflect the latest reported value and are not
averaged values. PATH_BALANCE is not pegged when either RXLEV_ul or RXLEV_dl
is equal to 63 (-47 dBm).
The range of values for this statistic is 0 to 220 with a long-term average of 110 with normal
use. A deviation of ±10 is acceptable, but this is to be understood as a practical guide and not
as product tolerance. If the deviation is greater than ±10, the RF path should be checked.
NOTE
If a low noise amplifier (LNA) is fitted, a deviation of -20 is possible.
6-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Mismatch of Horizon and Horizon macro database and hardware
Typically, the path loss should be similar in both the uplink and downlink directions. When
diversity gain is enabled, the path balance is just below 110, indicating a lower uplink path loss.
Mismatch of Horizon and Horizon macro database and hardware
The path_balance statistic is incorrect if the Horizon and Horizon macro cabinet and database
are mismatched. The following table describes the two mismatch scenarios between the cabinet
and database.
If Then
the Horizon cabinet is the SITE alarm 28 data configuration and Horizon
equipped with Horizon macro hardware mismatch is generated. Operators should change
database, the path_balance either the hardware or the database accordingly.
statistic is incorrect. Consult the manual, Maintenance Information: Alarm
Handling At The OMC-R (68P02901W26).
the Horizon macro cabinet the SITE alarm 28 data configuration and Horizon
is equipped with Horizon hardware mismatch is generated. Operators should change
database, the path_balance either the hardware or the database accordingly.
statistic is incorrect. Consult the manual, Maintenance Information: Alarm
Handling At The OMC-R (68P02901W26).
NOTE
If the Horizon macro booster unit is faulty or not present, the path_balance statistic
is incorrect. Operators should disregard this statistic until the booster is replaced.
Network planners should check with the OMC operator to determine if any Horizon
macro alarms (SITE alarms 25, 26 or 27) have been generated.
Analysis
This statistic can be used for trend analysis of the link balance on the air interface between
the uplink and downlink path loss.
Reference None.
Usage Quality of service: Service integrity.
Optimization.
Fault finding.
Basis Carrier.
Unit dB.
68P02901W56-T 6-29
Jan 2010
RBER Chapter 6: Carrier and timeslot statistics
RBER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RBER (Residual Bit Error Rate) Quality statistic is derived from a ratio of the number of
bits in the error to total number of bits received, within error detected speech frames defined as
good. The measurement period over which the calculation is made is 480 ms.
During this period, 24 speech frames are decoded and the ratio is calculated. By referring to a
lookup table, the ratio is converted to an RBER Quality number between 0 and 7.
NOTE
RBER is supported only by MMI actions. It not reported to the OMC-R at the end of
the statistical interval period.
Pegging
Every 480 ms, during the SACCH multi-frame by the RSS/HO process.
Units
The RBER statistic is reported using values 0 to 7.
Table 6-13 RBER Quality number conversion
RBER
RBER ratio (min:1
Quality
to max:1)
number
0 0 to 0.2
1 0.2 to 0.4
2 0.4 to 0.8
3 0.8 to 1.6
4 1.6 to 3.2
5 3.2 to 6.4
6 6.4 to 12.8
7 12.8 or greater
The bin ranges for this statistic are fixed and cannot be altered by the operator.
6-30 68P02901W56-T
Jan 2010
Analysis
regards to quality.
Reference None.
Fault finding.
RF loss.
Congestion.
Basis Carrier.
68P02901W56-T 6-31
Jan 2010
ROC Chapter 6: Carrier and timeslot statistics
ROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ROC statistic tracks the maximum, minimum and mean Range Of Carrier between BSS and
MS on a per-carrier basis. The range of carrier value corresponds to the Timing Advance (TA)
measurement reports. ROC statistic measurements are only reported for active channels.
The bin ranges for the ROC statistic correspond to some user definable TA ranges up to a
maximum of ten bins. The default bin ranges are shown in Table 6-14.
Table 6-14 Bin ranges for ROC
Bin TA Range
0 0 to 6
1 7 to 13
2 14 to 20
3 21 to 27
4 28 to 34
5 35 to 41
6 42 to 48
7 49 to 54
8 55 to 63
9 64 to 219
NOTE
These bins are not displayed at the OMC but can be displayed at the MMI. To set and
display the bin ranges refer to the chg_stat_prop and disp_stat_prop commands
in Chapter 2.
Pegging
6-32 68P02901W56-T
Jan 2010
Analysis
Basis Carrier.
68P02901W56-T 6-33
Jan 2010
U_BER Chapter 6: Carrier and timeslot statistics
U_BER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The U_BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for active
channels. The bit error rate value corresponds to the RXQUAL uplink measurement reports.
U_BER statistic measurements are reported only when the channel is active.
NOTE
on timeslot 0.
Pegging
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL values:
Table 6-15 Statistic values
RXQUAL BER (min to MAX) Assumed

0 0 to 0.2 0.14
1 0.2 to 0.4 0.28
2 0.4 to 0.8 0.57
3 0.8 to 1.6 1.13
4 1.6 to 3.2 2.26
5 3.2 to 6.4 4.53
6 6.4 to 12.8 9.05
7 greater than 12.8 18.1
NOTE
The bin ranges for this statistic cannot be changed.
6-34 68P02901W56-T
Jan 2010
Analysis
This statistic can be used to provide monitoring of uplink RXQUAL performance.
Reference GSM 4.08, 3.8.0, 3.4.1.2 and 9.1.20 and 10.5.2.11.

GSM 5.08, 3.6.0,8.2 and Appendix A.3.i.
Usage RF loss.
Congestion.
Fault finding.
Basis Timeslot.
68P02901W56-T 6-35
Jan 2010
UL_EGPRS_BACKHAUL_DEMAND Chapter 6: Carrier and timeslot statistics
UL_EGPRS_BACKHAUL_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_EGPRS_BACKHAUL_DEMAND statistic measures the mean and maximum value

of the demand for the uplink backhaul associated with an EGPRS RTF. This is the maximum
backhaul that the system could have used to service all the active data transfers if there were
no limits on the uplink backhaul associated with the RTF. It is obtained by maintaining the
mean and maximum values for backhaul demand for the uplink backhaul associated with an
EGPRS over the statistical period.
Pegging
The UL_EGPRS_BACKHAUL_DEMAND statistic pegs every block period based on the amount
of backhaul requested (before any backhaul related restriction) and switches applied in the
uplink by PDCHs on an EGPRS carrier.
Analysis
Reference None.
Usage VersaTRAU.
Basis Carrier.
Type Gauge.
Units
The unit for UL_EGPRS_BACKHAUL_DEMAND is in bytes. It includes the RLC blocks as well
as the VersaTRAU header, sampled every 20 ms RLC block period.
6-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_EGPRS_BACKHAUL_USED
UL_EGPRS_BACKHAUL_USED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_EGPRS_BACKHAUL_USED statistic measures the mean and maximum value for the
actual amount of uplink backhaul used for an EGPRS RTF. This is the actual backhaul that the
system used to service all the active data transfers on an EGPRS carrier, after accounting
for any coding scheme downgrades and radio block omissions in the uplink. It is obtained
by maintaining the mean and maximum values for backhaul usage for the uplink backhaul
associated with an EGPRS over the statistical period.
Pegging
The UL_EGPRS_BACKHAUL_USED statistic pegs every block period based on the amount
of backhaul used (accounting for any substitutions or omissions due to backhaul related
restrictions) in the uplink by PDCHs on an EGPRS carrier.
Analysis
Reference None.
Usage VersaTRAU.
Basis Carrier.
Type Gauge.
Units
The unit for UL_EGPRS_BACKHAUL_USED is in bytes. It includes the RLC blocks as well as
68P02901W56-T 6-37
Jan 2010
UPLINK_PATH_LOSS Chapter 6: Carrier and timeslot statistics
UPLINK_PATH_LOSS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UPLINK_PATH_LOSS statistic tracks the minimum, mean, and maximum uplink losses on
a per-carrier basis. Reported values can be used to create a profile of the radio link propagation
losses experienced by MSs served in the cell.
Pegging
This statistic is pegged every SACCH multiframe for each active call.
Analysis
This statistic can be used for trend analysis of the uplink losses on a per carrier basis.
Reference None.
Usage RF Loss.
Quality of Service.
Basis Carrier.
6-38 68P02901W56-T
Jan 2010
Chapter
GPROC and DPROC statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
GPROC and DPROC statistics track the utilization of the processing units found in various
hardware components in the BSS, for example GPROC and DPROC devices. The following
GPROC/DPROC statistics are described here:
• CPU_USAGE on page 7-2.
• DSP_USAGE on page 7-3
• GCI_FOR_16KPD_DEMAND on page 7-4.
• MSGS_DISCARD_ON_GPROC on page 7-7.
• PFC_REJ_DGRD_PRMPT_PRP on page 7-8.
• PROCESSOR_CRITICAL_OVERLOAD on page 7-11.
• PROCESSOR_SAFE_OVERLOAD on page 7-12.
• PRP_PD_DEMAND on page 7-13.
• RSL_LCF_CONGESTION on page 7-14.
• TOTAL_GCI_FOR_PD_DEMAND on page 7-15.
NOTE
If CTU2 is used in the system, processor utilization statistics are not supported.
68P02901W56-T 7-1
Jan 2010
CPU_USAGE Chapter 7: GPROC and DPROC statistics
CPU_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CPU_USAGE statistic tracks CPU usage. Monitoring of CPU usage allows the operator to
determine if the GPROC, DPROC, MPROC, PPROC or BBU devices at a particular site are being
over utilized, under utilized or properly utilized.
This statistic is updated from the reports generated by the internal executive system, which
tracks when CPU usage changes.
Pegging
{34371G}
This statistic records the maximum, minimum, and mean values of the short-term processor
utilization measurement (from which the 30 minute mean or 60 minutes mean, statistic Mean
Utilization, is calculated). This statistic is recorded for each GPROC , DPROC, MPROC, PPROC,
or BBU under the control of a BSS.
Analysis
This statistic can be used for trend analysis of GPROC, DPROC, MPROC, PPROC, or BBU
utilization.
Reference GSM 12.07,3.0.2,4.3 bullet 1.
Usage Processor utilization.

Network planning.
Optimization.
Basis GPROC, DPROC, MPROC, and PPROC
{34371G} BBU
NOTE
{34371G}
The (R)CTU4 does not support CPU usage statistics.
7-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DSP_USAGE
DSP_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{34371G}
Description
The DSP_USAGE statistic tracks the DSP usage. Monitoring the DSP usage allows the operator
to determine if each DSP core on the BBUs is being over utilized, under utilized or properly
utilized.
This statistic is updated from the reports generated by the firmware, which tracks when the
DSP usage changes.
Pegging
This statistic records the maximum, minimum, and mean values of the short-term processor
utilization measurement, from which the 30-minute mean or 60 minute mean, statistic Mean
Utilization, is calculated.
This statistic is recorded for each DSP core under the control of a BBU.
This statistic includes ten bins. 0 to 9 bins of these statistics represent a range between 0% to
100%. Each time the firmware reports a value, the BSS increments the bin corresponding to the
reported value by one. The BSS also increments the sample count by one and calculates the
total of all the reported values during the interval.
NOTE
The pegging interval for DSP usage messages from the firmware to the RSS is 30
seconds.
Analysis
This statistic can be used for trend analysis of DSP core utilization.
Reference None
Network planning.
Optimization.
Basis {34371G} DSP Core.
68P02901W56-T 7-3
Jan 2010
GCI_FOR_16KPD_DEMAND Chapter 7: GPROC and DPROC statistics
GCI_FOR_16KPD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GCI_FOR_16KPD_DEMAND counts the mean and maximum number of dynamically

mapped GCIs demanded for 16 K PDTCH on a PRP/PXP DPROC or PPROC in a given statistical
measurement interval. One unit represents one GCI demanded.
NOTE
The demanded number of GCIs presented by this statistic could be greater than the
in-service resources of PRP/PXP DPROCs or PPROCs or GDSs.
Pegging
This statistic is pegged by CB whenever GCI demand for 16K PDTCH is increased or decreased
on a PRP/PXP DPROC or PPROC. The count is increased/decreased by 1 for every 16K PDTCH
supported; it also pegs at the end of an interval.
Analysis
Reference None.
Usage This statistic indicates the mean and maximum number of GCIs
demanded for 16K PDTCHs on a PRP/PXP DPROC or PPROC.
Basis PRP/PXP DPROC and PPROC.
Type Gauge.
7-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GCI_FOR_32KPD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

mapped GCIs demanded for 32K PDTCH on a PRP/PXP DPROC or PPROC in a given statistical
NOTE
Pegging
This statistic is pegged by CB whenever GCI demand for 32K PDTCH is increased or decreased
on a PRP/PXP DPROC or PPROC. The count is increased/decreased by 2 for every 32K PDTCH
supported; it also pegs at the end of an interval.
Analysis
Reference None.
Type Gauge.
68P02901W56-T 7-5
Jan 2010
GCI_FOR_64KPD_DEMAND Chapter 7: GPROC and DPROC statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

mapped GCIs demanded for 64K PDTCH on a PRP/PXP DPROC or PPROC in a given statistical
NOTE
Pegging
This statistic is pegged by CB whenever GCI demand for 64K PDTCH (4 GCIs) is increased or
decreased on a PRP/PXP DPROC or PPROC. The count is increased/decreased by 4 for every
64K PDTCH supported; it also pegs at the end of an interval.
Analysis
Reference None.
Type Gauge.
7-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MSGS_DISCARD_ON_GPROC
MSGS_DISCARD_ON_GPROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of messages discarded on each destination GPROC by RSL
congestion control operation or token ring congestion.
Pegging
This statistic is pegged each time a downlink message (including MTL-LCF to RSL-LCF, MCU to
DRI) is discarded on a GPROC by the RSL Congestion Control operation.
Analysis
This statistic is used for trend analysis of RSL congestion status.
Reference GSM TS 12.04, GSM TS8.08

Usage RSL Congestion Control.
Quality of service.
Trend analysis.
Basis GPROC.
Type Counter.
Alarm None.
68P02901W56-T 7-7
Jan 2010
PFC_REJ_DGRD_PRMPT_PRP Chapter 7: GPROC and DPROC statistics
PFC_REJ_DGRD_PRMPT_PRP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PFC_REJ_DGRD_PRMPT_PRP statistic counts the number of PFC requests rejected,

downgraded, or preempted by the PCU due to a lack of PRP or cell resources. It also tracks the
number of PFC downgrades and preemption due to cell or PRP retentions on a per-board basis.
are pegged.
Pegging
The PFC_REJ_DGRD_PRMPT_PRP statistic pegs whenever a PCU preempts, rejects, or

downgrades a PFC request due to a lack of cell or board resources or whenever a PFC is
downgraded or preempted for cell or board retention purposes on a per-board basis. Table 7-1
describes the causes for preemption, rejection, or downgrade and describes what action the
operator can take to reduce these numbers in the future.
Table 7-1 PFC_REJ_DGRD_PRMPT_PRP bins
0 Rejection due The PCU does not have enough Increase the number of
to lack of cell MTBR in the cell to admit a PFC or GPRS time slots in the
resources. BSS cannot admit the PFC due to cell.
MS’s capability.
1 Rejection due The PCU does not have enough Adjust the MTBR
to lack of PRP MTBR in the board to admit a PFC. commitments for
resources. different traffic classes.
2 Downgrade due The PCU does not have enough Adjust the MTBR
to lack of cell MTBR in the cell to maintain a commitments for
resources. PFC’s current commitment and has different traffic classes.
reduced the PFC’s MTBR due to
the admission of a higher priority
PFC.
3 Downgrade due The PCU does not have enough Adjust the MTBR
to lack of PRP MTBR in the PRP to maintain a commitments for
resources. PFC’s current commitment and has different traffic classes.
reduced the PFC’s MTBR due to
the admission of a higher priority
PFC.
Continued
7-8 68P02901W56-T
Jan 2010
Table 7-1 PFC_REJ_DGRD_PRMPT_PRP bins (Continued)
to lack of cell MTBR in the cell to maintain commitments for
resources. a PFC’s commitments due to a different traffic classes.
change in available resources or
admission of a higher priority PFC
and has preempted the PFC.
to lack of PRP MTBR on the PRP to maintain commitments for
resources. a PFC’s commitments due to different traffic classes.
admission of a higher priority PFC
and has preempted the PFC.
6 Downgrade due to The PCU does not have enough Increase the resources in
cell retention. MTBR in the cell to retain all the the cell.
active PFCs’ commitments in the
event of resource shrinkage and
has reduced the PFC’s MTBR for
cell retention purposes.
7 Downgrade due to The PCU does not have enough Increase the resources
PRP retention. MTBR on the PRP to retain all the on the PRP.
active PFCs’ commitments in the
has reduced the PFC’s MTBR for
PRP retention purposes.
8 Preemption due to The PCU does not have enough Increase the resources in
cell retention. MTBR in the cell to maintain the cell.
a PFC’s commitments in the
has preempted the PFC for cell
retention purposes.
9 Preemption due to The PCU does not have enough Increase the resources
PRP retention. MTBR on the PRP to maintain on the PRP.
a PFC’s commitments in the
has preempted the PFC for PRP
retention purposes.
NOTE
Bins 7 and 9 are not pegged.
68P02901W56-T 7-9
Jan 2010
Analysis Chapter 7: GPROC and DPROC statistics
Analysis
Reference None.
Type Counter array.
7-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PROCESSOR_CRITICAL_OVERLOAD
PROCESSOR_CRITICAL_OVERLOAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PROCESSOR_CRITICAL_OVERLOAD statistic tracks the duration of the BSP board

in critical-overload state.
The critical-overload state of a BSP board occurs when BSP CPU utilization is above the
BSP critical-overload threshold.
The BSP overload protection mechanism attempts to move the BSP from critical-overload
state into safe-overload state by dropping non-imperative handover messages from the BTS
and rejecting assignment request from MSC.
The PROCESSOR_CRITICAL_OVERLOAD statistic provides a measurement of total time of a

processor working in critical-overload state.
Pegging
This statistic is started when the BSP CPU utilization is above the BSP critical-overload
threshold, and the statistic is stopped when BSP CPU utilization falls below the BSP
critical-overload threshold.
Analysis
This statistic provides a measurement of total time of a processor working in critical-overload

state.
Reference None
Usage Quality of service monitoring
Basis BSC GPROC
Type Duration
68P02901W56-T 7-11
Jan 2010
PROCESSOR_SAFE_OVERLOAD Chapter 7: GPROC and DPROC statistics
PROCESSOR_SAFE_OVERLOAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PROCESSOR_SAFE_OVERLOAD statistic tracks the duration of the BSP board in

safe-overload state.
The safe-overload state of a BSP board occurs when BSP CPU utilization is above the BSP
safe-overload threshold and below the critical-overload threshold.
The BSP overload protection mechanism attempts to prevent the BSP moving from
safe-overload state into critical-overload state by dropping non-imperative handover
messages and rejecting assignment request from MSC.
Pegging
This statistic is pegged when the BSP CPU utilization is above the BSP safe-overload threshold
and below BSP critical-overload threshold.
Analysis
This statistic provides a measurement of total time of a processor working in the safe-overload
state.
Reference None
Usage Quality of service monitoring
Basis BSC GPROC
Type Duration
7-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PRP_PD_DEMAND
PRP_PD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
PRP_PD_DEMAND counts the number of dynamically mapped PRP PDTCHs demanded on a

PRP/PXP DPROC or PPROC. One unit represents one PRP PDTCH demanded.
NOTE
• The demanded PDTCHs may be INS or OOS. Therefore, this statistic does not
indicate if there is data transfer in the demanded PDTCHs.
• The demanded number of PRP PDTCHs presented by this statistic could be
greater than the in-service resources of PRP/PXP DPROCs or PPROCs or GDSs.
Pegging
This statistic is pegged by CB whenever PRP PDTCH demand is increased or decreased on a

PRP/PXP DPROC or PPROC; it also pegs at the end of an interval.
Analysis
Reference None.
Usage This statistic tracks the mean and maximum number of PRP PDTCHs
demanded on a per PRP basis.
Type Gauge.
68P02901W56-T 7-13
Jan 2010
RSL_LCF_CONGESTION Chapter 7: GPROC and DPROC statistics
RSL_LCF_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic indicates the amount of time that an RSL-LCF board is in a congested state. The
BSS sends this duration statistic to the OMC-R periodically.
Pegging
The timer for this statistic is started when more than a certain percentage of RSLs on an LCF
board is congested, and the timer is stopped when less than a certain percentage of RSLs on
an LCF board is congested.
Analysis
This statistic is used for trend analysis of RSL congestion status on an LCF basis.
A threshold value should be assigned to this statistic reflecting the maximum percentage of
congested RSLs on an LCF board at which the timer is started, and the minimum percentage of
congested RSLs on an LCF board at which the timer is stopped.
Whenever this statistic timer is started, the 19:GPROC: RSL links congestion alarm is
generated until the timer stops, indicating that normal state has resumed. Refer to the manual
Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting
information.
Reference GSM TS 12.04, GSM TS 8.08

Usage RSL Congestion Control trend analysis.
Quality of service.
Fault finding.
Basis BSC GPROC.
Type Duration.
Alarm Warning.
7-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TOTAL_GCI_FOR_PD_DEMAND
TOTAL_GCI_FOR_PD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
TOTAL_GCI_FOR_PD_DEMAND counts the mean and maximum number of dynamically

mapped GCIs demanded for all PDTCHs on a PRP/PXP DPROC or PPROC in a given statistical
NOTE
Pegging
This statistic is pegged by CB whenever GCI demand for any PDTCH (16K, 32K, 64K) is
increased or decreased on a PRP/PXP DPROC or PPROC; it also pegs at the end of an interval
Analysis
Reference None.
Usage This statistic indicates the mean and maximum number of total GCIs
demanded for all PDTCHs on a PRP/PXP DPROC or PPROC.
Basis PRP/PXP and PPROC.
Type Gauge.
68P02901W56-T 7-15
Jan 2010
Analysis Chapter 7: GPROC and DPROC statistics
7-16 68P02901W56-T
Jan 2010
Chapter
Ethernet statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Ethernet statistics track the processor utilization of the Ethernet link. The following Ethernet
statistics are described here:
• ETH_RX_BYTE on page 8-2.
• ETH_RX_ERROR on page 8-3.
• ETH_RX_PKT on page 8-4.
• ETH_TX_BYTE on page 8-5.
• ETH_TX_ERROR on page 8-6.
• ETH_TX_PKT on page 8-7.
• PSI_TRAU_FILL_FRAME_TX on page 8-8.
68P02901W56-T 8-1
Jan 2010
ETH_RX_BYTE Chapter 8: Ethernet statistics
ETH_RX_BYTE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_RX_BYTE statistic tracks the total number of bytes of data received on the Ethernet
Link.
1000 bytes is equal to one unit. The translation of actual bytes counted to units is done at the
end of the statistic interval.
Pegging
The statistic counts each byte in the Ethernet packet that is received on the Ethernet link
of the PSI board or DPROC board.
Analysis
The ETH_RX_BYTE statistic counts the total number of received bytes per ETH device on a PSI
card or DPROC card. The count is taken for every 1000 events.
Reference None.
Basis ETH.
Type Counter.
8-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ETH_RX_ERROR
ETH_RX_ERROR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_RX_ERROR statistic tracks the number of times erroneous Ethernet packets are
received on the Ethernet Link.
One unit represents one erroneous Ethernet packet.
Pegging
The statistic pegs each time an erroneous Ethernet packet is received on the Ethernet link of
the PSI/DPROC(PXP) board.
Analysis
The ETH_RX_ERROR statistic counts the number of Ethernet receive errors per ETH device on
a PSI card or DPROC card.
Reference None.
Basis ETH.
Type Counter.
68P02901W56-T 8-3
Jan 2010
ETH_RX_PKT Chapter 8: Ethernet statistics
ETH_RX_PKT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_RX_PKT statistic tracks the total number of Ethernet packets received on the
Ethernet link.
One unit represents one Ethernet packet.
Pegging
The statistic pegs each time an Ethernet packet is received on the Ethernet link of the
PSI/DPROC(PXP) board.
Analysis
The ETH_RX_PKT statistic counts the number of received packets per ETH device on a PSI
card or DPROC card.
Reference None.
Basis ETH.
Type Counter.
8-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ETH_TX_BYTE
ETH_TX_BYTE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_TX_BYTE statistic tracks the total number of bytes of data transmitted on the
Ethernet Link.
1000 bytes is equal to one unit. The translation of actual bytes counted to units is done at the
end of the statistic interval.
Pegging
The statistic counts each byte in the Ethernet packet that is transmitted on the Ethernet link of
the PSI/DPROC(PXP) board.
Analysis
The ETH_TX_BYTE statistic counts the number of transmitted bytes per ETH device on a PSI
card or DPROC card. The count is taken for every 1000 events.
Reference None.
Basis ETH.
Type Counter.
68P02901W56-T 8-5
Jan 2010
ETH_TX_ERROR Chapter 8: Ethernet statistics
ETH_TX_ERROR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_TX_ERROR statistic tracks the number of erroneous packets transmitted on the
Ethernet Link.
One unit represents one erroneous packet.
Pegging
The statistic pegs each time the transmitted erroneous packets on the Ethernet link of the
Analysis
The ETH_TX_ERROR statistic counts the number of Ethernet Transmit errors per ETH device
on a PSI card or DPROC card.
Reference None.
Basis ETH.
Type Counter.
8-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ETH_TX_PKT
ETH_TX_PKT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ETH_TX_PKT statistic tracks the total number of Ethernet packets transmitted on the
Ethernet link.
One unit represents one Ethernet packet.
Pegging
The statistic pegs each time an Ethernet packet is transmitted on the Ethernet link of the
Analysis
The ETH_TX_PKT statistic counts the number of transmitted packets per ETH device on a
PSI card or DPROC card.
Reference None.
Basis ETH.
Type Counter.
68P02901W56-T 8-7
Jan 2010
PSI_TRAU_FILL_FRAME_TX Chapter 8: Ethernet statistics
PSI_TRAU_FILL_FRAME_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PSI_TRAU_FILL_FRAME_TX statistic tracks the total number of the fill frames replacing
TRAU data. When a TRAU frame through the Ethernet link is not received from the PCU in time,
a fill frame sent to the channel coder is required to keep the TRAU in synchronization.
One unit represents one fill frame.
Pegging
The statistic pegs each time a TRAU fill frame is sent to the channel coder.
Analysis
The PSI_TRAU_FILL_FRAME_TX statistic counts the TRAU fill transmit frames generated on a
per ETH device basis on the PSI board or DPROC board.
Reference None.
Usage Network utilization.
Basis ETH.
Type Counter.
8-8 68P02901W56-T
Jan 2010
Chapter
LMTL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Location Services Message Transfer Link (LMTL) statistics are used to track the events for the
Location Services Message Transfer Part (LMTP) of the ITU-TSS No. 7 protocol on the BSC
to MSC interface. They are categorized into subgroups, each of which are described in LMTL
statistics subgroups on page 9-2.
68P02901W56-T 9-1
Jan 2010
LMTL statistics subgroups Chapter 9: LMTL statistics
LMTL statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
LMTL statistics are organized into the following major subgroups:

• LMTP C7 availability on page 9-2.
• LMTP C7 performance on page 9-2.
• LMTP C7 utilization on page 9-3.
LMTP C7 availability
LMTP C7 availability statistics are used to track the duration of signaling link outages and
inhibitions (local and remote) for the LMTP of the ITU-TSS Number 7 protocol on the BSC to
MSC interface. The following are the MTP C7 availability statistics:
• LMTP_LINKFAIL on page 9-10.
• LMTP_LOCAL_BUSY on page 9-11.
• LMTP_LOCAL_MGT on page 9-12.
• LMTP_MGT_INHIBIT on page 9-13.
• LMTP_MGT_UNINHIBIT on page 9-14.
• LMTP_REMOTE_MGT on page 9-19.
• LMTP_REMOTE_PROC on page 9-20.
• LMTP_START_RPO on page 9-30.
• LMTP_STOP_RPO on page 9-31.
• LMTP_UNAVAILABLE on page 9-33.
LMTP C7 performance
LMTP C7 performance statistics are used to track the different types of failure and recovery
situations for the LMTP of the ITU-TSS Number 7 protocol on the BSC to MSC interface. The
following are the LMTP C7 performance statistics:
• LMTP_CHANGEBACK on page 9-6.
• LMTP_CHANGEOVER on page 9-7.
• LMTP_LINK_INS on page 9-9.
• LMTP_NEG_ACKS on page 9-17.
9-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP C7 utilization
• LMTP_REMOTE_SL_CONGESTION on page 9-26.
• LMTP_RESTORATION on page 9-21.
• LMTP_SL_ACK on page 9-24.
• LMTP_SL_ALIGNMENT on page 9-25.
• LMTP_SL_ERROR_RATE on page 9-27.
• LMTP_SL_FAIL on page 9-28.
• LMTP_SL_FIBR on page 9-29.
• LMTP_SU_ERROR on page 9-32.
LMTP C7 utilization
LMTP C7 utilization statistics are used to track the number of messages received, transmitted,
and retransmitted on signaling links, and supply information on signaling link congestion for
the LMTP of the ITU-TSS Number 7 protocol on the BSC to MSC interface. The following are
the LMTP C7 utilization statistics:
• LMTP_CONGESTION_LOST_MSU on page 9-4.
• LMTP_MSU_DISCARDED on page 9-5.
• LMTP_CONGESTION on page 9-35.
• LMTP_RE_TX on page 9-18.
• LMTP_MSU_RX on page 9-15.
• LMTP_MSU_TX on page 9-16.
• LMTP_SIB_RX on page 9-34.
• LMTP_SIB_TX on page 9-36.
• LMTP_SIF_SIO_RX on page 9-22.
• LMTP_SIF_SIO_TX on page 9-23.
• LMTP_LOCAL_SL_CONGESTION on page 9-8.
68P02901W56-T 9-3
Jan 2010
LMTP_CONGESTION_LOST_MSU Chapter 9: LMTL statistics
LMTP_CONGESTION_LOST_MSU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CONGESTION_LOST_MSU statistic tracks the number of times Message Signaling

Units (MSU) are being lost due to Lb-interface Signaling Link (SL) congestion.
Pegging
This statistic pegs for each congestion event on the Lb-interface which results in MSUs being
lost.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
MSUs due to SL congestion, that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. LMTL: SL congestion events resulting in
loss of MSUs - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
9-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_MSU_DISCARDED
LMTP_MSU_DISCARDED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_DISCARDED statistic tracks the number of MSUs discarded due to

Lb-interface Signaling Link (SL) congestion.
Pegging
This statistic pegs each time an MSU is discarded due to Lb-interface SL congestion.
Analysis
MSUs being discarded due to SL congestion, that are acceptable in normal system operations.
If the specified threshold is exceeded, the 10. LMTL: MSUs discarded due to SL congestion
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 9-5
Jan 2010
LMTP_CHANGEBACK Chapter 9: LMTL statistics
LMTP_CHANGEBACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CHANGEBACK statistic tracks the number of local automatic change backs that
have been successfully completed.
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signaling
Link (SL) is diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic change backs that have been
successfully completed.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 performance.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
9-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_CHANGEOVER
LMTP_CHANGEOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CHANGEOVER statistic tracks the number of local automatic changeovers that
have been successfully completed. This indicates that MTP traffic is being transferred from a Lb
interface Signaling Link (SL) that is going out-of-service to an alternate SL.
Pegging
This statistic pegs when MTP traffic is changed over to an alternate Lb interface SL.
Analysis
out of sequence messages between a BSS and an SMLC that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-7
Jan 2010
LMTP_LOCAL_SL_CONGESTION Chapter 9: LMTL statistics
LMTP_LOCAL_SL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_SL_CONGESTION statistic tracks once for each onset of congestion across
the Lb-interface Signaling Link (SL).
There are two types of congestion that may occur across a Lb interface SL: local congestion (that
is, the MTP L2 of the BSS detects that the TX queue is full) and remote congestion (that is, the
BSS-based SMLC is congested). Both types of congestion may exist across a Lb-interface SL at
one time; however, regardless of congestion type, the statistic is pegged only upon the entrance
into the congested state of the Lb-interface SL. Thus, if the Lb-interface SL is locally congested
and remote congestion is detected, the statistic is not pegged. Likewise, if the Lb-interface SL is
remotely congested and local congestion is detected, the statistic is not pegged.
Pegging
The statistic pegs each time the Lb-interface SL goes into the congestion state at the local site.
Analysis
congestion onsets that are acceptable in normal system operations.
If the specified threshold is exceeded, the 12. LMTL:SL Congestion Indications - PM

alarm is generated.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
9-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_LINK_INS
LMTP_LINK_INS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LINK_INS statistic tracks the length of time that a Lb-interface Signaling Link (SL)
is in the in-service state.
Pegging
The timer for this statistic is started when an SL is brought into service. The timer is stopped
when the Lb-interface SL is removed from service.
Analysis
This statistic can be used for trend analysis of the utilization of in-service SLs.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
68P02901W56-T 9-9
Jan 2010
LMTP_LINKFAIL Chapter 9: LMTL statistics
LMTP_LINKFAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LINKFAIL statistic tracks the duration of the Lb-interface Signaling Link (SL)
unavailability due to SL failure. It records the total time a particular SL is out-of-service while
trying to align to the SMLC.
Pegging
This statistic timer is started when the SL fails. It is stopped when the SL comes back into
service.
Analysis
This statistic can be used for analysis of SL unavailability due to SL failure.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage MTP C7 availability.
Fault finding.
Basis Lb SS7_LINK.
9-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_LOCAL_BUSY
LMTP_LOCAL_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_BUSY statistic tracks the total time congestion present on the local end of
the Lb-interface Signaling Link (SL).
Pegging
This statistic is started when a congestion is detected on a Lb-interface SL. The statistic is
stopped when normal operation is resumed.
Analysis
This statistic can be used for trend analysis on congestion duration on the local end of the SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis Lb SS7_LINK.
68P02901W56-T 9-11
Jan 2010
LMTP_LOCAL_MGT Chapter 9: LMTL statistics
LMTP_LOCAL_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_MGT statistic tracks the total time that a local Lb-interface Signaling Link
(SL) is inhibited due to local management actions.
Pegging
This statistic is started each time the SL is inhibited due to local management actions, and
stopped when the link is enabled.
Analysis
This statistic can be used for trend analysis on inhibited local SLs due to local management
action.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Duration (total time).
9-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_MGT_INHIBIT
LMTP_MGT_INHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MGT_INHIBIT statistic tracks the number of times the Lb-interface Signaling Link
(SL) is inhibited by the operator.
Pegging
This statistic is started each time the Lb-interface SL is inhibited by the operator.
Analysis
This statistic can be used for trend analysis on inhibited SLs using the shutdown command on
the associated MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-13
Jan 2010
LMTP_MGT_UNINHIBIT Chapter 9: LMTL statistics
LMTP_MGT_UNINHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MGT_UNINHIBIT statistic tracks the number of times the Lb-interface Signaling
Link (SL) is uninhibited by the operator.
Pegging
This statistic is pegged each time the SL is uninhibited by the operator.
Analysis
This statistic can be used for trend analysis on uninhibited SLs using the unlock command on
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
9-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_MSU_RX
LMTP_MSU_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs) received on a
Lb-interface signaling link.
Pegging
This statistic pegs each time MSUs are received over the Lb-interface signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-15
Jan 2010
LMTP_MSU_TX Chapter 9: LMTL statistics
LMTP_MSU_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs) transmitted
on a Lb-interface signaling link.
Pegging
This statistic pegs each time MSUs are transmitted over the Lb-interface signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
9-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_NEG_ACKS
LMTP_NEG_ACKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_NEG_ACKS statistic tracks the number of out-of-sequence messages between a BSS
and the BSS-based SMLC across the Lb-interface signaling link.
Pegging
This statistic pegs when the BSS detects out of order messages to the SMLC and requests
retransmission.
Analysis
out of sequence messages between a BSS and an SMLC that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks received
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 9-17
Jan 2010
LMTP_RE_TX Chapter 9: LMTL statistics
LMTP_RE_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the
SMLC because the SMLC has requested retransmission. This indicates how much the BSS and
an SMLC are off in message sequencing by the number of octets retransmitted.
Pegging
This statistic pegs the number of octets retransmitted by the BSS to the SMLC.
Analysis
octet retransmissions that are acceptable in normal system operations.
If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted - PM

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
9-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_REMOTE_MGT
LMTP_REMOTE_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_REMOTE_MGT statistic tracks the total time a Lb-interface Signaling Link (SL) is
remotely inhibited by the SMLC.
Pegging
This statistic pegs the duration of the Lb-interface SL inhibition due to remote management
action.
Analysis
This statistic can be used for trend analysis of remote management SL inhibition actions.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Duration (total time in milliseconds (ms).
68P02901W56-T 9-19
Jan 2010
LMTP_REMOTE_PROC Chapter 9: LMTL statistics
LMTP_REMOTE_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_REMOTE_PROC statistic tracks the time that a remote processor is out of service.
Pegging
This statistic pegs when a remote processor outage is identified, and stopped when the
processor outage condition ceases.
Analysis
This statistic can be used for trend analysis of remote processor outage occurrences in the
BSS-based SMLC.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
9-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_RESTORATION
LMTP_RESTORATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_RESTORATION statistic tracks the number of times user traffic is allowed on a
Lb-interface Signaling Link (SL) that is in service and not inhibited. This statistic does not
track recovery from link fail.
Pegging
This statistic pegs when the Lb-interface SL starts carrying user traffic. This happens when the
Lb-interface SL comes into service, is uninhibited, or recovers from a remote processor outage.
Analysis
This statistic can be used for trend analysis of used traffic being allowed on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-21
Jan 2010
LMTP_SIF_SIO_RX Chapter 9: LMTL statistics
LMTP_SIF_SIO_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or
Service Information Octets (SIO) that are received over a Lb-interface signaling link.
Pegging
This statistic pegs each time an SIF or SIO is received over a Lb-interface signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
9-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_SIF_SIO_TX
LMTP_SIF_SIO_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are transmitted over a signaling link by the BSC to the SMLC.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over a signaling link by the BSC to
the SMLC.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-23
Jan 2010
LMTP_SL_ACK Chapter 9: LMTL statistics
LMTP_SL_ACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_ACK statistic tracks the number of times that the link was lost due to a
Lb-interface MTP layer 2 T7 timer expiry.
Pegging
This statistic pegs each time the link is lost due to a timer that expires when an acknowledgment
from the BSS-based SMLC is not received.
Analysis
acknowledgments of MSUs not being received by the BSC that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 2. LMTL: SL failure - excessive delay of ACK -
PM alarm is generated. Refer to the manual Maintenance Information: Alarm Handling at the
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
9-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_SL_ALIGNMENT
LMTP_SL_ALIGNMENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attempts to align an

out-of-service LMTL.
Pegging
This statistic pegs each time an out-of-service Signaling Link (SL) unsuccessfully tries to align
with the Lb-interface.
Analysis
unsuccessful attempts to align an out-of-service SL to the Lb-interface that are acceptable in
If the specified threshold is exceeded, the 5. LMTL: SL alignment failure - PM alarm is

generated. Refer to the manual Maintenance Information: Alarm Handling at the OMC-R
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Minor.
68P02901W56-T 9-25
Jan 2010
LMTP_REMOTE_SL_CONGESTION Chapter 9: LMTL statistics
LMTP_REMOTE_SL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_REMOTE_SL_CONGESTION statistic tracks the number of times the remote

congestion timer expires for the Lb-interface signaling link.
Pegging
This statistic pegs each time the remote congestion timer expires.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of
occurrences of excessive congestion duration at the remote Signaling Link (SL) that are
acceptable in normal system operations.
If the specified threshold is exceeded, the 4. LMTL: SL failure - excessive duration of

congestion - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
9-26 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_SL_ERROR_RATE
LMTP_SL_ERROR_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_ERROR_RATE statistic tracks the number of times that a Lb-interface Signaling
Link (SL) is lost due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.
Pegging
This statistic pegs each time the Lb-interface SL is lost due to the SUERM timer expiration.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an
SL may be lost due to SUERM timer expiration that are acceptable in normal system operations.
If the specified threshold is exceeded, the 3. LMTL: SL failure - excessive error rate - PM
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
TU-TSS Q.703 - (102).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-T 9-27
Jan 2010
LMTP_SL_FAIL Chapter 9: LMTL statistics
LMTP_SL_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_FAIL statistic tracks the Lb-interface Signaling Link (SL) failure for all causes
except, operator interaction, through the MMI.
Pegging
This statistic is pegged when a Lb-interface SL fails for any reason except operator interaction
through the MMI.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of SL
failures, excluding those caused by the operator's interaction with the MMI, that are acceptable
in normal system operations.
If the specified threshold is exceeded, the 0. LMTL: SL failure - all reasons - PM alarm is
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
9-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_SL_FIBR
LMTP_SL_FIBR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_FIBR statistic tracks the number of out-of-sequence messages between a BSC
and the BSS-based SMLC that result in a Lb-interface Signaling Link (SL) going out-of-service.
This statistic is like the LMTP_NEG_ACKS statistic, but signals a more severe condition.
Pegging
This statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator
Bit (FIB) caused by the de-synchronization of the Backward Sequence Number (BSN) and
Forward Sequence Number (FSN).
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times
an SL may be lost due to the detection of an abnormal FIB that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 1. LMTL: SL failure - abnormal FIBR/BSNR -

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-T 9-29
Jan 2010
LMTP_START_RPO Chapter 9: LMTL statistics
LMTP_START_RPO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_START_PRO statistic tracks the number of times a processor outage occurs in
the BSS-based SMLC.
Pegging
This statistic is pegged each time the BSS is notified that the BSS-based SMLC has experienced
a processor outage.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of remote
processor outages that are acceptable in normal system operations.
If the specified threshold is exceeded, the 8. LMTL: Start of remote processor outage
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
9-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_STOP_RPO
LMTP_STOP_RPO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_STOP_RPO statistic tracks the number of times a processor outage condition
has ceased in the BSS-based SMLC.
Pegging
This statistic pegs each time the remote processor outage stops.
Analysis
This statistic can be used for trend analysis of remote processor outage condition is no longer
present.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
68P02901W56-T 9-31
Jan 2010
LMTP_SU_ERROR Chapter 9: LMTL statistics
LMTP_SU_ERROR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SU_ERROR statistic tracks the number of times erroneous signal units are received
on the Lb-interface Signaling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the Lb-interface SS7 SL.
Analysis
erroneous signal units may be received on the SL that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 6. LMTL: Number of signal units in error - PM
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.
9-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_UNAVAILABLE
LMTP_UNAVAILABLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_UNAVAILABLE statistic tracks the total time a Lb-interface Signaling Link (SL) is
out-of-service for all reasons including those caused by operator intervention.
Pegging
This statistic records the duration of Lb-interface SL unavailability for all reasons, including
those caused by operator intervention through the MMI.
Analysis
This statistic can be used for trend analysis of the duration of SL outages, including those
caused by operator interaction.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis Lb SS7_LINK.
68P02901W56-T 9-33
Jan 2010
LMTP_SIB_RX Chapter 9: LMTL statistics
LMTP_SIB_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIB_RX statistic tracks the number of Status Indication Busy LSSU messages
received over a Lb-interface Signaling Link (SL).
Pegging
This statistic is pegged each time the BSS receives a Status Indication Busy (SIB) LSSU message
across the Lb-interface signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis Lb SS7_Link.
Type Counter.
9-34 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LMTP_CONGESTION
LMTP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CONGESTION statistic tracks the time the Lb-interface Signaling Link (SL) is
congested.
Pegging
The timer for this statistic is started when a congestion is detected on a Lb interface signaling
link. The timer is stopped when normal operation is resumed.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis Lb SS7_Link.
Type Duration.
68P02901W56-T 9-35
Jan 2010
LMTP_SIB_TX Chapter 9: LMTL statistics
LMTP_SIB_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIB_TX statistic tracks the number of Status Indication Busy LSSU messages
transmitted over a Lb-interface Signaling Link (SL).
Pegging
This statistic is pegged each time the BSS transmits a Status Indication Busy (SIB) LSSU
message across the Lb-interface signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_Link.
Type Counter.
9-36 68P02901W56-T
Jan 2010
Chapter
10
BSS statistics for Location Services support

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS statistics for Location Services (LS) support are collected and used for the supported BSS
LS. Existing cell connection establishment statistics as described in are pegged for location
services and specific LS events are captured using BSS LS statistics described in this chapter.
These subgroups are described in BSS statistics for Location Services support subgroups on
page 10-2.
68P02901W56-T 10-1
Jan 2010
BSS statistics for Location Services support subgroups Chapter 10: BSS statistics for Location Services support
BSS statistics for Location Services support subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS statistics for Location Services (LS) support are organized into the following subgroups:
• Location service on page 10-2.
Connection establishment statistics track access and channel request functions. The following
statistics are connection establishment statistics and are pegged for location services:
• CHAN_REQ_CAUSE_ATMPT on page 4-68.
• OK_ACC_PROC on page 4-139.
Location service
The following are specific location service statistics:

• BSSLAP_ABORT_RCV on page 10-4.
• BSSLAP_ABORT_SENT on page 10-5.
• BSSLAP_MS_POS_CMD on page 10-6.
• BSSLAP_MS_POS_RESP on page 10-7.
• BSSLAP_REJ on page 10-8.
• BSSLAP_RESET on page 10-9.
• BSSLAP_TA_REQ on page 10-10.
• BSSLAP_TA_RESP on page 10-11.
• BSSLAP_TOA_REQ on page 10-12.
• BSSMAP_CONLESS_INFO_RCV on page 10-13.
• BSSMAP_CONLESS_INFO_SENT on page 10-14.
• BSSMAP_PERF_LOC_ABORT_MSGS on page 10-15.
• BSSMAP_PERF_LOC_REQ_MSGS on page 10-16.
• BSSMAP_PERF_LOC_RESP_MSGS on page 10-17.
• BSSMAPLE_CONLESS_INFO_RCV on page 10-18.
10-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Location service
• BSSMAPLE_CONLESS_INFO_SENT on page 10-19.
• BSSMAPLE_PERF_LOC_ABORT_MSGS on page 10-20.
• BSSMAPLE_PERF_LOC_REQ_MSGS on page 10-21.
• BSSMAPLE_PERF_LOC_RESP_MSGS on page 10-22.
68P02901W56-T 10-3
Jan 2010
BSSLAP_ABORT_RCV Chapter 10: BSS statistics for Location Services support
BSSLAP_ABORT_RCV
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_ABORT_RCV statistic tracks the number of BSSLAP abort messages received.
Pegging
This statistic pegs each time a BSSLAP abort message is received.
Analysis
Reference GSM 03.71 v7.4.0, sect. 8.4.

GSM 08.71 v7.2.0, sect. 2.2.7.
Fault finding.
Basis BSS.
Type Counter.
10-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSLAP_ABORT_SENT
BSSLAP_ABORT_SENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_ABORT_SENT statistic tracks the number of BSSLAP abort messages sent.
Pegging
This statistic pegs each time a BSSLAP abort message is sent.
Analysis

GSM 08.71 v7.2.0, sect. 2.2.7.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-5
Jan 2010
BSSLAP_MS_POS_CMD Chapter 10: BSS statistics for Location Services support
BSSLAP_MS_POS_CMD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_MS_POS_CMD statistic tracks the number of BSSLAP MS position command

messages received.
Pegging
This statistic pegs each time a BSSLAP MS position command message is received.
Analysis
Reference GSM 03.71 v7.4.0, sect. 10.2, 10.3.

GSM 08.71 v7.2.0, sect. 2.2.9.
Fault finding.
Basis BSS.
Type Counter.
10-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSLAP_MS_POS_RESP
BSSLAP_MS_POS_RESP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_MS_POS_RESP statistic tracks the number of BSSLAP MS position response

messages sent.
Pegging
This statistic pegs each time a BSSLAP MS position response message is sent.
Analysis
Reference GSM 03.71 v7.4.0, sect. 10.2, 10.3.

GSM 08.71 v7.2.0, sect. 2.2.10.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-7
Jan 2010
BSSLAP_REJ Chapter 10: BSS statistics for Location Services support
BSSLAP_REJ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_REJ statistic tracks the number of BSSLAP reject messages sent.
Pegging
This statistic pegs each time a BSSLAP reject message is sent.
Analysis

GSM 08.71 v7.2.0, sect. 2.2.5.
Fault finding.
Basis BSS.
Type Counter.
10-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSLAP_RESET
BSSLAP_RESET
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_RESET statistic tracks the number of BSSLAP reset messages sent.
Pegging
This statistic pegs each time a BSSLAP reset message is sent.
Analysis

GSM 08.71 v7.2.0, sect. 2.2.6.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-9
Jan 2010
BSSLAP_TA_REQ Chapter 10: BSS statistics for Location Services support
BSSLAP_TA_REQ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_TA_REQ statistic tracks the number of BSSLAP TA request messages received.
Pegging
This statistic pegs each time a BSSLAP TA request message is received.
Analysis
Reference GSM 03.71 v7.4.0, sect. 8.2, 8.3, 8.4.

GSM 08.71 v7.2.0, sect. 2.2.1.
Fault finding.
Basis BSS.
Type Counter.
10-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSLAP_TA_RESP
BSSLAP_TA_RESP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_TA_RESP statistic tracks the number of BSSLAP TA response messages sent.
Pegging
This statistic pegs each time a BSSLAP TA response message is sent.
Analysis

GSM 08.71 v7.2.0, sect. 2.2.2.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-11
Jan 2010
BSSLAP_TOA_REQ Chapter 10: BSS statistics for Location Services support
BSSLAP_TOA_REQ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSLAP_TOA_REQ statistic tracks the number of BSSLAP TOA request messages
received.
Pegging
This statistic pegs each time a BSSLAP TOA request message is received.
Analysis

GSM 08.71 v7.2.0, sect. 2.2.3.
Fault finding.
Basis BSS.
Type Counter.
10-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSMAP_CONLESS_INFO_RCV
BSSMAP_CONLESS_INFO_RCV
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAP_CONLESS_INFO_RCV statistic tracks the number of BSSMAP connectionless

information messages received.
Pegging
This statistic pegs each time a BSSMAP connectionless information message is received.
Analysis

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-13
Jan 2010
BSSMAP_CONLESS_INFO_SENT Chapter 10: BSS statistics for Location Services support
BSSMAP_CONLESS_INFO_SENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAP_CONLESS_INFO_SENT statistic tracks the number of BSSMAP connectionless

information messages sent.
Pegging
This statistic pegs each time a BSSMAP connectionless information message is sent.
Analysis

Fault finding.
Basis BSS.
Type Counter.
10-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSMAP_PERF_LOC_ABORT_MSGS
BSSMAP_PERF_LOC_ABORT_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAP_PERF_LOC_ABORT_MSGS statistic tracks the number of BSSMAP perform

location abort messages received on the A-interface.
Pegging
This statistic pegs each time a BSSMAP perform location abort message is received on
the A-interface.
Analysis
Reference GSM 03.71 v7.4.0, sect 7.11.

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-15
Jan 2010
BSSMAP_PERF_LOC_REQ_MSGS Chapter 10: BSS statistics for Location Services support
BSSMAP_PERF_LOC_REQ_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAP_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAP perform

location request messages received on the A-interface.
Pegging
This statistic pegs each time a BSSMAP perform location request message is received
on A-interface.
Analysis
Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.

Fault finding.
Basis BSS.
Type Counter.
10-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSMAP_PERF_LOC_RESP_MSGS
BSSMAP_PERF_LOC_RESP_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAP_PERF_LOC_RESP_MSGS statistic tracks the number of BSSMAP perform

location response messages sent on A-interface.
Pegging
This statistic pegs each time a BSSMAP perform location response message is sent on
A-interface.
Analysis
Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-17
Jan 2010
BSSMAPLE_CONLESS_INFO_RCV Chapter 10: BSS statistics for Location Services support
BSSMAPLE_CONLESS_INFO_RCV
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAPLE_CONLESS_INFO_RCV statistic tracks the number of Lb-interface

BSSMAP-LE connectionless information messages received.
Pegging
This statistic pegs each time a BSSMAP-LE connectionless information message is received.
Analysis

Fault finding.
Basis BSS.
Type Counter.
10-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSMAPLE_CONLESS_INFO_SENT
BSSMAPLE_CONLESS_INFO_SENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAPLE_CONLESS_INFO_SENT statistic tracks the number of Lb-interface

BSSMAP-LE connectionless information messages sent.
Pegging
This statistic pegs each time a BSSMAP-LE connectionless information message is sent.
Analysis
Reference GSM 03.71 v7.4.0, sect. 7.8,

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-19
Jan 2010
BSSMAPLE_PERF_LOC_ABORT_MSGS Chapter 10: BSS statistics for Location Services support
BSSMAPLE_PERF_LOC_ABORT_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAPLE_PERF_LOC_ABORT_MSGS statistic tracks the number of BSSMAP-LE

perform location abort messages sent on the Lb-interface.
Pegging
This statistic pegs each time a BSSMAP-LE perform location abort message is sent on
Lb-interface.
Analysis
Reference GSM 03.71 v7.4.0, sect 7.11GSM 09.31 v7.1.0, sect 9.3.
Fault finding.
Basis BSS.
Type Counter.
10-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BSSMAPLE_PERF_LOC_REQ_MSGS
BSSMAPLE_PERF_LOC_REQ_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAPLE_PERF_LOC_REQ_MSGS statistic tracks the number of BSSMAP-LE perform

location request messages sent on the Lb-interface.
Pegging
This statistic pegs each time a BSSMAP-LE perform location request message is sent on
Lb-interface.
Analysis
Reference GSM 03.71 v7.4.0, sect 7.5, 7.6, 7.7, 7.11, 8.1GSM 09.31 v7.1.0, sect 9.1.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-T 10-21
Jan 2010
BSSMAPLE_PERF_LOC_RESP_MSGS Chapter 10: BSS statistics for Location Services support
BSSMAPLE_PERF_LOC_RESP_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BSSMAPLE_PERF_LOC_RESP_MSGS statistic tracks the number of BSSMAP-LE

perform location response messages received on the Lb-interface.
Pegging
This statistic pegs each time a BSSMAP-LE perform location response message is received
on the Lb-interface.
Analysis

GSM 09.31 v7.1.0, sect. 9.2
Fault finding.
Basis BSS.
Type Counter.
10-22 68P02901W56-T
Jan 2010
Chapter
11
MTL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Message Transfer Link (MTL) statistics are used to track the events for the Message Transfer
Part (MTP) of the ITU-TSS No. 7 protocol on the BSC to MSC interface. They are categorized
into subgroups, each of which is described in MTL statistics subgroups on page 11-2.
68P02901W56-T 11-1
Jan 2010
MTL statistics subgroups Chapter 11: MTL statistics
MTL statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MTL statistics are organized into the following major subgroups:

• MTP C7 availability on page 11-2.
• MTP C7 performance on page 11-2.
• MTP C7 utilization on page 11-3.
MTP C7 availability
MTP C7 availability statistics are used to track the duration of signaling link outages and
inhibitions (local and remote) for the MTP of the ITU-TSS No.7 protocol on the BSC to MSC
interface. The following are the MTP C7 availability statistics:
• MTP_LINKFAIL on page 11-12.
• MTP_LOCAL_BUSY on page 11-13.
• MTP_LOCAL_MGT on page 11-14.
• MTP_MGT_INHIBIT on page 11-15.
• MTP_MGT_UNINHIBIT on page 11-16.
• MTP_REMOTE_MGT on page 11-21.
• MTP_REMOTE_PROC on page 11-22.
• MTP_START_RPO on page 11-33.
• MTP_STOP_RPO on page 11-34.
• MTP_UNAVAILABLE on page 11-36.
MTP C7 performance
MTP C7 performance statistics are used to track the different types of failure and recovery
situations for the MTP of the ITU-TSS Number 7 protocol on the BSC to MSC interface. The
following are the MTP C7 performance statistics:
• MTP_CHANGEBACK on page 11-8.
• MTP_CHANGEOVER on page 11-9.
• MTP_LINK_INS on page 11-11.
• MTP_NEG_ACKS on page 11-19.
11-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP C7 utilization
• MTP_RESTORATION on page 11-23.
• MTP_SL_ACK on page 11-26.
• MTP_SL_ALIGNMENT on page 11-27.
• MTP_SL_CONGESTION on page 11-28.
• MTP_SL_ERROR_RATE on page 11-29.
• MTP_SL_ERROR_RATE_HSP on page 11-30.
• MTP_SL_FAIL on page 11-31.
• MTP_SL_FIBR on page 11-32.
• MTP_SU_ERROR on page 11-35.
MTP C7 utilization
MTP C7 utilization statistics are used to track the number of messages received, transmitted,
and retransmitted on signaling links and supply information on signaling link congestion for
the MTP of the ITU-TSS Number 7 protocol on the BSC to MSC interface. The following are
the MTP C7 utilization statistics:
• BUSY_CICS on page 11-4.
• CONGESTION_LOST_MSU on page 11-6.
• MSU_DISCARDED on page 11-7.
• MTP_CONGESTION on page 11-10.
• MTP_MSU_RX on page 11-17.
• MTP_MSU_TX on page 11-18.
• MTP_RE_TX on page 11-20.
• MTP_SIF_SIO_RX on page 11-24.
• MTP_SIF_SIO_TX on page 11-25.
• SIB_RX on page 11-37.
• SL_CONGESTION on page 11-39.
• SL_STOP_CONGESTION on page 11-40.
68P02901W56-T 11-3
Jan 2010
BUSY_CICS Chapter 11: MTL statistics
BUSY_CICS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_CICS statistic tracks the number of BUSY CICS during an interval. These weighted
distribution statistics produce a mean value indicating the average number of CICs in use
during the interval.
The bin ranges may be changed using the chg_stat_prop command.
The default bin ranges for the BUSY_CICS statistic are:

Table 11-1 BUSY CICS bins
Bin Range
0 0 to 199
1 200 to 399
2 400 to 799
3 800 to 1199
4 1200 to 1599
5 1600 to 2199
6 2200 to 3199
7 3200 to 4199
8 4200 to 5199
9 5200 to 6200
Pegging
This statistic is pegged each time an allocation or de-allocation of a CIC is detected. It is an

indication of the amount of active calls under the MSC.
The individual bins values are incremented by the length of time that the number of allocated
CICs fall within the bin ranges.
11-4 68P02901W56-T
Jan 2010
Analysis
Since each call is routed through the MSC (even intra-BSS and intra-cell), the number of CICs
represent the number of calls in progress under that MSC for this BSS.
Reference None.
Network planning.
Optimization.
Basis BSS.
68P02901W56-T 11-5
Jan 2010
CONGESTION_LOST_MSU Chapter 11: MTL statistics
CONGESTION_LOST_MSU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONGESTION_LOST_MSU statistic tracks the number of times Message Signaling Units
(MSU) are being lost due to Signaling Link (SL) congestion.
Pegging
This statistic pegs for each congestion event which results in MSUs being lost.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost
MSUs due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. MTL: SL congestion events resulting in loss
of MSUs - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
11-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MSU_DISCARDED
MSU_DISCARDED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MSU_DISCARDED statistic tracks the number of MSUs discarded while there is congestion
on the Signaling Link (SL).
Pegging
This statistic pegs each time an MSU is discarded while there is congestion on the SL.
Analysis
MSUs being discarded due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 10. MTL: MSUs discarded due to SL congestion
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 11-7
Jan 2010
MTP_CHANGEBACK Chapter 11: MTL statistics
MTP_CHANGEBACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CHANGEBACK statistic tracks the number of local automatic change backs that
have been successfully completed.
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signaling
Link (SL) is diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic change backs that have been
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
11-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_CHANGEOVER
MTP_CHANGEOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CHANGEOVER statistic tracks the number of local automatic changeovers that
have been successfully completed. This indicates that MTP traffic is being transferred from a
Signaling Link (SL) that is going out-of-service to an alternate SL.
Pegging
This statistic pegs when MTP traffic is changed over to an alternate SL.
Analysis
This statistic can be used for trend analysis of local automatic changeovers that have been
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
68P02901W56-T 11-9
Jan 2010
MTP_CONGESTION Chapter 11: MTL statistics
MTP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CONGESTION statistic tracks the length of time that a signaling link is congested.
This can be used to indicate signaling link congestion.
Pegging
The timer for this statistic is started when a congestion is detected on a signaling link. The timer
is stopped when normal operation is resumed.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_LINK.
11-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_LINK_INS
MTP_LINK_INS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LINK_INS statistic tracks the length of time that a signaling link (SL) is in the
in-service state.
Pegging
The timer for this statistic is started when an SL is brought into service. The timer is stopped
when the SL is removed from service.
Analysis
This statistic can be used for trend analysis of the utilization of in-service SLs.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Key statistics: MTL_UTILISATION_RX,
MTL_UTILISATION_TX.
Basis SS7_LINK.
68P02901W56-T 11-11
Jan 2010
MTP_LINKFAIL Chapter 11: MTL statistics
MTP_LINKFAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LINKFAIL statistic tracks the duration of Signaling Link (SL) unavailability due to SL
failure. It records the total time a particular SL is out-of-service while trying to align.
Pegging
This statistic pegs each time the SL tries to align with the A interface while it is out-of-service.
The statistic timer is started when the SL fails. It is stopped when the SL comes back into
service.
Analysis
This statistic can be used for analysis of SL unavailability due to SL failure.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
11-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_LOCAL_BUSY
MTP_LOCAL_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LOCAL_BUSY statistic tracks the total time congestion is present on the local end
of the Signaling Link (SL).
Pegging
This statistic is started when a congestion is detected on an SL. The statistic is stopped when
normal operation is resumed.
Analysis
This statistic can be used for trend analysis on congestion duration on the local end of the SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_LINK.
68P02901W56-T 11-13
Jan 2010
MTP_LOCAL_MGT Chapter 11: MTL statistics
MTP_LOCAL_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LOCAL_MGT statistic tracks the total time that a local Signaling Link (SL) is
inhibited due to local management actions.
Pegging
This statistic is started each time the SL is inhibited due to local management actions and
stopped when the link is enabled.
Analysis
This statistic can be used for trend analysis on inhibited local SLs due to local management
action.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
11-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_MGT_INHIBIT
MTP_MGT_INHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MGT_INHIBIT statistic tracks the number of times the Signaling Link (SL) is
inhibited using the shutdown command on the MTP link.
Pegging
This statistic is started each time the SL is inhibited by the user entering the shutdown command
on the associated MTP link.
Analysis
This statistic can be used for trend analysis on inhibited SLs using the shutdown command on
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
68P02901W56-T 11-15
Jan 2010
MTP_MGT_UNINHIBIT Chapter 11: MTL statistics
MTP_MGT_UNINHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MGT_UNINHIBIT statistic tracks the number of times the Signaling Link (SL) is
uninhibited using the unlock command on the MTP link.
Pegging
This statistic is started each time the SL is uninhibited using the unlock command on an SL that
was previously inhibited.
Analysis
This statistic can be used for trend analysis on uninhibited SLs using the unlock command on
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
11-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_MSU_RX
MTP_MSU_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs) received on
a particular signaling link.
Pegging
This statistic pegs each time MSUs are received over the signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Key statistic:
MTL_UTILISATION_RX.
Basis SS7_LINK.
Type Counter.
68P02901W56-T 11-17
Jan 2010
MTP_MSU_TX Chapter 11: MTL statistics
MTP_MSU_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs) transmitted on
a particular signaling link.
Pegging
This statistic pegs each time MSUs are transmitted over the signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Key statistic:
MTL_UTILISATION_TX.
Basis SS7_LINK.
Type Counter.
11-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_NEG_ACKS
MTP_NEG_ACKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_NEG_ACKS statistic tracks when the messages between a BSS and an MSC get
out of sequence.
Pegging
This statistic pegs when the BSS detects out of order messages to the MSC and request
retransmission.
Analysis
out-of-sequence messages between a BSS and an MSC that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 7. MTL: SL number of negative acks received
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 11-19
Jan 2010
MTP_RE_TX Chapter 11: MTL statistics
MTP_RE_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_RE_TX statistic tracks the number of octets that the BSS has retransmitted to the
MSC because the MSC has requested retransmission. This indicates how much the BSS and an
MSC are off in message sequencing by the number of octets retransmitted.
Pegging
This statistic pegs the number of octets retransmitted by the BSS to the MSC.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Warning.
11-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_REMOTE_MGT
MTP_REMOTE_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_REMOTE_MGT statistic tracks the total time a Signaling Link (SL) was remotely
inhibited.
Pegging
This statistic pegs the duration of the SL inhibition due to remote management action until
uninhibited.
Analysis
This statistic can be used for trend analysis of remote management SL inhibition actions.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
68P02901W56-T 11-21
Jan 2010
MTP_REMOTE_PROC Chapter 11: MTL statistics
MTP_REMOTE_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_REMOTE_PROC statistic tracks the time that a remote processor is out-of-service.
Pegging
This statistic pegs when a remote processor outage is identified, and stopped when the
processor outage condition ceases.
Analysis
This statistic can be used for trend analysis of remote processor outages.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
11-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_RESTORATION
MTP_RESTORATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_RESTORATION statistic tracks the number of times a user traffic is allowed on a
Signaling Link (SL) that is in service and not inhibited. This statistic does not track recovery
from link fail.
Pegging
This statistic pegs when the SL starts carrying user traffic. This happens when the SL comes
into service, is uninhibited, or recovers from a remote processor outage.
Analysis
This statistic can be used for trend analysis of used traffic being allowed on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
68P02901W56-T 11-23
Jan 2010
MTP_SIF_SIO_RX Chapter 11: MTL statistics
MTP_SIF_SIO_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SIF_SIO_RX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are received over a signaling link.
Pegging
This statistic pegs each time an SIF or SIO is received over the signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Key statistic:
MTL_UTILISATION_RX.
Basis SS7_LINK.
Type Counter.
11-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_SIF_SIO_TX
MTP_SIF_SIO_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or Service
Information Octets (SIO) that are transmitted over a signaling link.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over the signaling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Key statistic:
MTL_UTILISATION_TX.
Basis SS7_LINK.
Type Counter.
68P02901W56-T 11-25
Jan 2010
MTP_SL_ACK Chapter 11: MTL statistics
MTP_SL_ACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ACK statistic tracks the number of times that the link was lost because a timer
expired due to an acknowledgment that a Message Signal Unit (MSU) was not sent.
Pegging
This statistic pegs each time the link is lost due to a timer that expires when an acknowledgment
of an MSU is not sent.
Analysis
acknowledgments of MSUs not being sent that are acceptable in normal system operations.
If the specified threshold is exceeded, the 2. MTL: SL failure - excessive delay of ACK -
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Major.
11-26 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_SL_ALIGNMENT
MTP_SL_ALIGNMENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attempts to align an

out-of-service Signaling Link (SL) with the A interface.
Pegging
This statistic pegs each time an out-of-service SL unsuccessfully tries to align with the A
interface.
Analysis
unsuccessful attempts to align an out-of-service SL to the A interface that are acceptable in
If the specified threshold is exceeded, the 5. MTL: SL alignment failure - PM alarm is

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Minor.
68P02901W56-T 11-27
Jan 2010
MTP_SL_CONGESTION Chapter 11: MTL statistics
MTP_SL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_CONGESTION statistic tracks the number of times the remote site is congested.
Pegging
This statistic pegs each time the remote congestion timer expires.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of
occurrences of excessive congestion duration at the remote that are acceptable in normal
system operations.
If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration of

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Major.
11-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_SL_ERROR_RATE
MTP_SL_ERROR_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ERROR_RATE statistic tracks the number of times that a Signaling Link (SL) is
lost due to the expiration of the Signal Unit Error Rate Monitor (SUERM) timer.
Pegging
This statistic pegs each time the SL is lost due to the SUERM timer expiration. (Refer to
ITU-TSS specification Q. 703, Section 102.)
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times an
SL may be lost due to SUERM timer expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 3. MTL: SL failure - excessive error rate - PM
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-T 11-29
Jan 2010
MTP_SL_ERROR_RATE_HSP Chapter 11: MTL statistics
MTP_SL_ERROR_RATE_HSP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ERROR_RATE_HSP statistic tracks the number of times a Signaling Link (SL) is
lost due to the Error internal monitoring threshold (TE) is reached during the monitoring period.
Pegging
MTPL2 sends a DL_DISCONNECT_IND to MTP L3 and MTP L3 pegs this statistic each time
DL_DISCONNECT_IND is received.
Analysis
For HSP MTL, the MTP_SL_ERROR_RATE_HSP statistic tracks the number of times a
Signaling Link (SL) is lost due to the Error internal monitoring threshold (TE) is reached during
the monitoring period. This statistic can be used to analyses MTP C7 performance and locate
fault on SL.
Reference ITU-TSS Q703, A10.2

Fault finding.
Basis MTL.
Type Counter.
Alarm Major.
11-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_SL_FAIL
MTP_SL_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_FAIL statistic tracks Signaling Link (SL) failure for all causes except, those
caused by operator interaction through the MMI.
Pegging
This statistic pegs when an SL fails for any reason except those caused by operator interaction
through the MMI.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of SL
failures, excluding those caused by operator interaction with the MMI, that are acceptable in
If the specified threshold is exceeded, the 0. MTL: SL failure - all reasons - PM alarm is
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.
68P02901W56-T 11-31
Jan 2010
MTP_SL_FIBR Chapter 11: MTL statistics
MTP_SL_FIBR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_FIBR statistic tracks the messages between a BSS and a remote site, which are
out of sequence, causing the Signaling Link (SL) to go out-of-service. This statistic is like the
MTP_NEG_ACKS statistic but signals a more severe condition.
Pegging
This statistic pegs when the SL is lost due to the detection of an abnormal Forward Indicator
Bit (FIB) caused by the de-synchronization of the Backward Sequence Number (BSN) and
Forward Sequence Number (FSN).
Analysis
an SL may be lost due to the detection of an abnormal FIB that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 1. MTL: SL failure - abnormal FIBR/BSNR - PM

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.
11-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_START_RPO
MTP_START_RPO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_START_PRO statistic tracks the number of times a remote processor outage occurs.
Pegging
This statistic pegs each time a remote processor outage condition is identified.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of remote
processor outages that are acceptable in normal system operations.
If the specified threshold is exceeded, the 8. MTL: Start of remote processor outage - PM
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 11-33
Jan 2010
MTP_STOP_RPO Chapter 11: MTL statistics
MTP_STOP_RPO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_STOP_RPO statistic tracks the number of times a remote processor outage condition
stops.
Pegging
This statistic pegs each time the remote processor outage stops.
Analysis
This statistic can be used for trend analysis of remote processor outages and restoration.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
11-34 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTP_SU_ERROR
MTP_SU_ERROR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SU_ERROR statistic tracks the number of times erroneous signal units are received
on the Signaling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the SL.
Analysis
erroneous signal units may be received on the SL that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 6. MTL: Number of signal units in error - PM
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 11-35
Jan 2010
MTP_UNAVAILABLE Chapter 11: MTL statistics
MTP_UNAVAILABLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_UNAVAILABLE statistic tracks the total time a Signaling Link (SL) is out-of-service
for all reasons including those caused by operator intervention.
Pegging
This statistic records the duration of SL unavailability for all reasons, including those caused
by operator intervention through the MMI.
Analysis
This statistic can be used for trend analysis of the duration of SL outages, including those
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis SS7_LINK.
11-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SIB_RX
SIB_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SIB_RX statistic provides a means of calculating MTL utilization by counting the number of
Status Indication Busy LSSU messages received.
Pegging
This statistic pegs each receipt of a Status Indication Busy (SIB) LSSU message on a per
signaling link basis.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Key statistic:
MTL_UTILISATION_RX.
Basis SS7_Link.
Type Counter.
68P02901W56-T 11-37
Jan 2010
SIB_TX Chapter 11: MTL statistics
SIB_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SIB_TX statistic provides a means of calculating MTL utilization by counting the number of
Status Indication Busy LSSU messages transmitted.
Pegging
This statistic pegs each transmission of a Status Indication Busy (SIB) LSSU message on
a per-signaling link basis.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Key statistic:
MTL_UTILISATION_TX.
Basis SS7_Link.
Type Counter.
11-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SL_CONGESTION
SL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SL_CONGESTION statistic tracks the number of times the remote congestion timer expires
due to excessive duration of Signaling Link (SL) failure.
Pegging
This statistic pegs each time the remote congestion timer expires due to excessive duration of
congestion on an SL failure.
Analysis
remote congestion timer expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration of

Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_Link.
Type Counter.
Alarm Warning.
68P02901W56-T 11-39
Jan 2010
SL_STOP_CONGESTION Chapter 11: MTL statistics
SL_STOP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SL_STOP_CONGESTION statistic tracks Signaling Link (SL) congestion stoppage.
Pegging
This statistic is pegged each time the signaling link congestion indication stops.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Network planning.
Fault finding.
Basis SS7_Link.
Type Counter.
11-40 68P02901W56-T
Jan 2010
Chapter
12
CBL, GSL, OML, RSL, and XBL statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25/LAP-D statistics included here, are used to track BSS data transmission information. These
statistics relate to the events on the following links:
• Cell Broadcast Link (CBL).
• GPRS Signaling Link (GSL).
• Operation and Maintenance Link (OML).
• Radio System Link (RSL).
• RXCDR to BSC Link (XBL).
• AXCDR to BSC Link (XBL).

The statistics are listed in X.25/LAP-D Level: X.25 and LAP-D statistics on page 12-2.
68P02901W56-T 12-1
Jan 2010
X.25/LAP-D Level: X.25 and LAP-D statistics Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
X.25/LAP-D Level: X.25 and LAP-D statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25 and LAP-D statistics are used to track BSS data transmission information. The following
are the X.25 and LAP-D statistics:
• ATER_CHANNEL_REQUEST on page 12-3.
• ATER_CHANNEL_STATUS on page 12-4.
• ATER_PREEMPT_ATMPT on page 12-6.
• ATER_PREEMPT_ATMPT_SWOVER on page 12-7.
• ATER_PREEMPT_FAIL on page 12-8.
• ATER_PREEMPT_FAIL_SWOVER on page 12-9.
• ATER_PREEMPT_RQD on page 12-10.
• FRMR on page 12-13.
• I_FRAMES_RX on page 12-14.
• I_FRAMES_TX on page 12-15.
• INVALID_FRAMES_RX on page 12-16.
• LAP-D_CONGESTION on page 12-17.
• MSGS_DISCARD_ON_RSL on page 12-18.
• N2_EXPIRY on page 12-19.
• RSL_LINK_INS on page 12-20.
• RSL_RX_OCTETS on page 12-21.
• RSL_TX_OCTETS on page 12-22.
• SABM_TX on page 12-23.
12-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ATER_CHANNEL_REQUEST
ATER_CHANNEL_REQUEST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_CHANNEL_REQUEST counts the number of Ater channels requested.
Pegging
This statistic pegs whenever an Ater channel is requested.
Analysis
Reference None.
Fault finding.
Basis AXCDR.
Type Counter.
68P02901W56-T 12-3
Jan 2010
ATER_CHANNEL_STATUS Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
ATER_CHANNEL_STATUS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_CHANNEL_STATUS statistic tracks the Ater channel status on a per XBL linkset
basis.
Table 12-1 ATER_CHANNEL_STATUS bins

1 ATER_CHAN_REQ_FAIL Counts the number of Ater channels requested
but could not be allocated.
2 CALL_SETUP_FAIL_COMM_ERR Counts the number of call setup failures due to
BSC-RXCDR communication errors.
3 INIT_HO_CIC_FAIL_COMM_ERR Counts the number of internal call handovers and
CIC remaps due to BSS-RXCDR communication
errors.
4 ATER_SWITCH_FAIL_COMM_ERR Counts the number of Ater switchover failures
due to BSC-RXCDR communication errors.
5 CALL_SETUP_FAIL_NO_ATER Counts the number of call setups that fail due to
no available Ater channels.
6 INIT_HO_CIC_FAIL_NO_ATER Counts the number of internal call handovers and
CIC remaps due to no available Ater channels.
7 ATER_SWITCH_FAIL_NO_ATER Counts the number of Ater switchover failures
due to no available Ater channels.
8 BSC_INIT_BLOCK_CIC_LOW_ATER Counts the number of times BSC-initiated
blocking of CICs is invoked. The statistic pegs
when the Ater channels available to an associated
RXCDR fall below a pre-set value, termed as the
CIC blocking threshold.
NOTE
The pegging occurs only when the
BSC is operating in EAC mode.
All remaining CICs are routed through the

associated RXCDR. The BSC automatically blocks
all these idle CICs at the Mobile System Control
(MSC).
Continued
12-4 68P02901W56-T
Jan 2010
Table 12-1 ATER_CHANNEL_STATUS bins (Continued)

NOTE
All out-of-service (OOS) and idle CICs
have Low Ater Resources reason set.
Pegging
This statistic pegs the number of events relating to ATER allocation and assignment scenarios
on a per XBL linkset basis.
Analysis
Reference None.
Fault finding.
Basis AXCDR.
Type Counter array.
68P02901W56-T 12-5
Jan 2010
ATER_PREEMPT_ATMPT Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
ATER_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_PREEMPT_ATMPT statistic tracks the number of times the Ater preemption
mechanism is successful in finding a resource to preempt (excluding switchover scenarios).
Pegging
The BSS pegs the ATER_PREEMPT_ATMPT statistic when the Ater preemption mechanism is
successful in finding a resource to preempt (excluding switchover scenarios).
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
12-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ATER_PREEMPT_ATMPT_SWOVER
ATER_PREEMPT_ATMPT_SWOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_PREEMPT_ATMPT_SWOVER statistic tracks the number of times the Ater

preemption mechanism is successful in finding a resource to preempt due to switchover
scenarios.
Pegging
The BSS pegs the ATER_PREEMPT_ATMPT_SWOVER statistic when the Ater preemption
mechanism is successful in finding a resource to preempt due to switchover scenarios.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
68P02901W56-T 12-7
Jan 2010
ATER_PREEMPT_FAIL Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
ATER_PREEMPT_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_PREEMPT_FAIL statistic tracks the number of times the Ater preemption mechanism
fails to allocate a resource (for non-switchover cases only).
Pegging
The BSS pegs the ATER_PREEMPT_FAIL statistic when Ater preemption fails due to a conflict
between BSS mechanisms or when there are multiple failures in preemption mechanism.
NOTE
For multiple failures, the ATER_PREEMPT_FAIL statistic pegs only once.
Analysis
times the Ater preemption mechanism is unsuccessful.
If the specified threshold is exceeded, the 0. AXCDR: PM Alarm is generated. Refer to

the manual Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
troubleshooting information.
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
12-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application ATER_PREEMPT_FAIL_SWOVER
ATER_PREEMPT_FAIL_SWOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of times the Ater preemption mechanism fails to allocate a
resource (for switchover cases only).
Pegging
The BSS pegs the ATER_PREEMPT_FAIL_SWOVER statistic when Ater preemption fails due to a
conflict between BSS mechanisms or when there are multiple failures in preemption mechanism.
NOTE
For multiple failures, the ATER_PREEMPT_FAIL_SWOVER statistic pegs only once.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
68P02901W56-T 12-9
Jan 2010
ATER_PREEMPT_RQD Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
ATER_PREEMPT_RQD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATER_PREEMPT_RQD statistic tracks the number of times the ATER preemption
mechanism is triggered.
The BSS triggers the Ater preemption mechanism when no 8 kbps or 16 kbps resources are
available to satisfy the requirements of a request with preemption capability (PCI = 1 and
priority level less than 14).
Pegging
The BSS pegs the ATER_PREEMPT_RQD statistic when Ater preemption is triggered.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
12-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application EXT_UL_EXITS
EXT_UL_EXITS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EXT_UL_EXITS statistic gives the total number of exits from extended uplink TBF mode to
normal uplink transfer mode or normal uplink TBF release.
Pegging
This statistic pegs the ending of extended uplink TBF. BSS pegs the appropriate bin. Different
bins and method of collection is as follows:
Table 12-2 EXT_UL_EXITS bins
Bin Description
0 This bin is pegged when network exits out of extended
uplink TBF mode to normal uplink transfer mode due to
arrival of new RLC data block.
uplink TBF mode to normal release the uplink TBF due to
the expiry of extended uplink duration.
uplink TBF mode to preemptively release uplink TBF due
to congestion in the cell. For congestion release details
refer to PCU4510.
Analysis
The EXT_UL_EXITS statistic tracks the number of exits from extended uplink TBF mode.
Reference None.
Usage Performance management.

Basis Cell.
Type Counter array.
68P02901W56-T 12-11
Jan 2010
EXT_UL_USF_USAGE Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
EXT_UL_USF_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EXT_UL_USF_USAGE statistic provides the number of control blocks received during
extended uplink TBF mode. It also provides the number of times no activity is recorded at the
PCU during extended uplink TBF mode when ext_utbf_nodata is one.
Pegging
This statistic is pegged based on the type of block received on assigned USF during extended
uplink mode. Different bins and method of collection is as follows:
Table 12-3 EXT_UL_USF_USAGE bins
Bin Description
0 This bin is pegged when Uplink Dummy Control Blocks are
received during extended uplink TBF mode.
1 This bin is pegged when non-dummy Control Blocks are
received during extended uplink TBF mode.
2 This bin is pegged when ext_utbf_nodata is one and no
activity is recorded on the USF assigned during extended
uplink TBF mode.
Analysis
This statistic provides block count for which a non-real data block is received by the PCU
during extended uplink TBF mode.
Reference None.
Basis Cell.
Type Counter array.
12-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application FRMR
FRMR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The FRMR statistic tracks the number of frames that were rejected because the frames were
not recoverable.
Pegging
This statistic pegs each time a frame that is not recoverable, is received.
Analysis
Reference ITU-TSS Q.920 - 1ITU-TSS X.20 - X.32

Usage X.25/LAP-D.
Fault finding.
Basis X25_LINK/LAP-D_LINK.
Type Counter.
Alarm Warning.
68P02901W56-T 12-13
Jan 2010
I_FRAMES_RX Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
I_FRAMES_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The I_FRAMES_RX statistic tracks the number of Information Frames (I-Frames) received.
Pegging
This statistic pegs when an I-Frame is received.
Analysis
Reference ITU-TSS Q.920 - 1.

ITU-TSS X.20 - X.32.
Usage X.25/LAP-D.
Type Counter.
12-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application I_FRAMES_TX
I_FRAMES_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The I_FRAMES_TX statistic tracks the number of Information Frames (I-Frames) transmitted.
Pegging
This statistic pegs when an I-Frame is transmitted.
Analysis

Usage X.25/LAP-D.
Type Counter.
68P02901W56-T 12-15
Jan 2010
INVALID_FRAMES_RX Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
INVALID_FRAMES_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INVALID_FRAMES_RX statistic tracks the number of invalid frames received.
Pegging
This statistic is pegged whenever an invalid frame is received.

• X.25
On the OML (BSS-OMC-R).
On the CBL (BSS-CBC).
• LAP-D
On the RSL (BSS-BTS link).
On the XBL (BSC-RXCDR link).
Analysis

Usage X.25/LAP-D.
Fault finding.
Type Counter.
Alarm Warning.
12-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LAP-D_CONGESTION
LAP-D_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LAP-D_CONGESTION statistic tracks the time that the LAP-D link is congested. This
indicates the time period in milliseconds when the sending speed of the BSC/BTS processes
is more than the link transmit capability and provides a way of monitoring when more links
need to be added.
NOTE
• The exec-dlsp process has a bigger buffer to hold outgoing messages therefore
the messages are not dropped even during the congestion period.
• The LAP-D_CONGESTION statistic is not applicable to OML link.
Pegging
This statistic pegs when the transmit buffer gets full and stops when the buffer is available again.
Analysis

Usage LAP-D.
Fault finding.
Basis LAP-D_LINK.
Type Duration.
68P02901W56-T 12-17
Jan 2010
MSGS_DISCARD_ON_RSL Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
MSGS_DISCARD_ON_RSL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of discard-eligible messages discarded on each RSL by RSL
congestion control operation.
Pegging
This statistic is pegged each time downlink messages are discarded by the RSL Congestion
Control operation on each RSL.
Analysis
This statistic is used for trend analysis of RSL congestion status.
Reference GSM TS 12.04, GSM TS8.08

Quality of service.
Trend analysis.
Basis RSL.
Type Counter.
Alarm None.
12-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application N2_EXPIRY
N2_EXPIRY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The N2_EXPIRY statistic tracks the number of link alignment retries attempted without success.
Pegging
This statistic pegs when the retry count threshold has been exceeded.
Analysis

Usage X.25/LAP-D.
Fault finding.
Type Counter.
Alarm Minor.
68P02901W56-T 12-19
Jan 2010
RSL_LINK_INS Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
RSL_LINK_INS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RSL_LINK_INS statistic tracks the time that an RSL link is in service within a predefined
interval.
Pegging
This statistic is started when the RSL link is in service and ends when the RSL link becomes
OOS within a predefined interval.
Analysis
Reference None.
Quality of service.
Basis RSL link.
Type Duration.
12-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RSL_RX_OCTETS
RSL_RX_OCTETS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RSL_RX_OCTETS statistic collects the total length of octets transmitted over the RSL link
from BTS to BSC when the RSL link is in service within a predefined interval.
Pegging
The BSC collects the octets transmitted over an RSL uplink when an RSL link is in service. This
statistic provides a cumulative length of octets transmitted over an RSL link from BTS to BSC.
NOTE
The octets count for pre GPROC3-2 boards (not including retransmissions and
supervisory frames) is based on payload and LAP-D header information. This does not
apply to GPROC3-2 boards as the LAP-D protocol is provided by software.
OMC can use the following formula to calculate the key statistics:
RSL− RX− (RSL− RX− OCTECTS∗ 8)

=
UTILISATION (RSL− LINK− INS/1000)∗ (rsl− link− rate ∗ 16000)
The RSL link can be either 16 or 64 kbit/s. In the formula above, an rsl_link_rate of 1 indicates
16 kbit/s bandwidth, 4 indicates 64 kbit/s bandwidth.
Analysis
Reference None.
Usage Uplink utilization.
Trouble shooting.
RSL provisioning.
Basis RSL link.
Type Counter.
68P02901W56-T 12-21
Jan 2010
RSL_TX_OCTETS Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
RSL_TX_OCTETS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RSL_TX_OCTETS statistic collects the total length of octets transmitted over the RSL link
from BSC to BTS when the RSL link is in service within a predefined interval.
Pegging
The BSC collects the octets transmitted over an RSL downlink when an RSL link is in service.
This statistic provides a cumulative length of octets transmitted over an RSL link from BSC to
BTS.
The BSC collects the octets transmitted over an RSL downlink when an RSL link is in service.
This statistic provides a cumulative length of octets transmitted over an RSL link from BSC to
BTS.
OMC can use the following formula to calculate the key statistics:
RSL− TX− (RRSL− TX− OCTECTS∗ 8)

=
UTILISATION (RSL− LINK− INS/1000)∗ (rsl− link− rate ∗ 16000)
The RSL link can be either 16 kbit/s or 64 kbit/s. In the formula above, an rsl_link_rate of 1
indicates 16 kbit/s bandwidth, 4 indicates 64 kbit/s bandwidth.
Analysis
Reference None.
Usage Downlink utilization.
Trouble shooting.
RSL provisioning.
Basis RSL link.
Type Counter.
12-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SABM_TX
SABM_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SABM_TX statistic tracks the links that come into service.
Pegging
This statistic is pegged for all Set Asynchronous Balanced Mode (SABM) frames.
Analysis

Usage X.25/LAP-D.
Type Counter.
68P02901W56-T 12-23
Jan 2010
Analysis Chapter 12: CBL, GSL, OML, RSL, and XBL statistics
12-24 68P02901W56-T
Jan 2010
Chapter
13
PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PCU statistics are captured from the events occurring at the Packet Control Unit (PCU). They are
categorized into subgroups, each of which is described in PCU statistics subgroups on page 13-2.
68P02901W56-T 13-1
Jan 2010
PCU statistics subgroups Chapter 13: PCU statistics
PCU statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PCU statistics are organized into the following major subgroups:

• GBL statistics on page 13-2.
• Accessibility statistics on page 13-3.
• Throughput statistics on page 13-4.
• Utilization statistics on page 13-8.
GBL statistics
The GBL device refers to the configured number of time slots on an E1 link between the PCU
and the Serving GPRS Support Node (SGSN). This interface is referred to as the Gb interface.
The Gb interface allows many users to be multiplexed over a common physical resource. GPRS
signaling and user data are sent on the same physical resource; that is, no dedicated physical
resources are allocated for signaling purposes.
The GBL measurement types are listed as follows:

• CELL_FLUSH_REQS on page 13-17.
• GBL_AVAILABILITY on page 13-108.
• GBL_DL_DATA_THRPUT on page 13-109.
• GBL_DL_DATA_THRPUT_HIST on page 13-110.
• GBL_DL_PKT_COUNT on page 13-112
• GBL_DL_PKT_INV_NSVC on page 13-113
• GBL_FLOW_CTRL_SENT on page 13-114.
• GBL_PAGING_REQS on page 13-115.
• GBL_RESOUR_DIST_IND on page 13-116
• GBL_UL_DATA_THRPUT on page 13-117.
• GBL_UL_DATA_THRPUT_HIST on page 13-118.
• GBL_UL_PKT_COUNT on page 13-120
• GBL_UNAVAILABLE on page 13-121.
13-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Accessibility statistics
Accessibility statistics
Accessibility statistics measure how effectively GPRS resources are being accessed. These
measurements assist the operator in planning the necessary resources required for the MS
to efficiently access the network.
The accessibility statistics include the following:

• CH_REQ_UNSVCD_PCU on page 13-18.
• CHANNEL_REQS_REC on page 13-20.
• CHANNEL_REQS_REJECT on page 13-22.
• CHANNEL_REQS_SUCCESS on page 13-23.
• CODING_SCHEME_CHANGE on page 13-25.
• CS12_ON_32K_CHAN on page 13-30.
• CS1_USE_DL on page 13-32.
• EGPRS_64K_CHANNELS_SWITCHED on page 13-103.
• EGPRS_64K_NOT_AVAIL on page 13-104.
• EGPRS_DL_ASGN_PCCCH on page 13-106.
• G_RACH_UNSVCD_BTS on page 13-107.
• GPRS_32K_CHANNELS_SWITCHED on page 13-122.
• GPRS_32K_DL_NOT_AVAIL on page 13-123.
• GPRS_32K_UL_NOT_AVAIL on page 13-124.
• GPRS_ACCESS_PER_AGCH on page 13-125.
• GPRS_ACCESS_PER_RACH on page 13-126.
• GPRS_CELL_RESELECT_FAIL on page 13-131.
• GPRS_CHANNELS_SWITCHED on page 13-132.
• GPRS_DL_ASGN_PCCCH on page 13-133.
• GPRS_PAGING_OVERFLOW_RATE_PPCH on page 13-135.
• GPRS_PAGING_OVERFLOW_RATE_PCH on page 13-134.
68P02901W56-T 13-3
Jan 2010
Throughput statistics Chapter 13: PCU statistics
• GPRS_PCH_AGCH_Q_LENGTH on page 13-136.
• GPRS_PPCH_PAGCH_Q_LENGTH on page 13-137.
• GPRS_PRR_BLK_USG on page 13-138.
• GPRS_RACH_ARRIVAL on page 13-140.
• MCS1_USE_DL on page 13-149
• NO_PDTCH_AVAIL on page 13-158.
• NO_PDTCH_AVAIL_TIME on page 13-159.
Throughput statistics
The throughput statistics are listed as follows:

• AIR_DL_CONTROL_BLKS on page 13-9.
• AIR_DL_TBF_FAILURES on page 13-10.
• AIR_UL_CONTROL_BLKS on page 13-11.
• AIR_UL_TBF_FAILURES on page 13-12.
• CONG_REL_DL_SCTS on page 13-27.
• DL_BLER_CS1 on page 13-36.
• DL_BLER_MCS1 on page 13-44.
13-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Throughput statistics
• DL_BUSY_PDTCH on page 13-62
• DL_LLC_FRAMES_GB on page 13-64.
• DL_LLC_FRAMES_PCU on page 13-65.
• DL_PDTCH_Q_LENGTH on page 13-69.
• DL_PDTCH_SEIZURE on page 13-70.
• DL_RADIO_BLKS_1_TS on page 13-71.
• DL_RLC_ACK_NEW_BLKS on page 13-82
• DL_RLC_DDTR_BLKS on page 13-84
• DL_RLC_NACK_BLKS on page 13-85.
• DL_RLC_RETX_BLKS on page 13-87.
• DL_RLC_STALLED_BLKS on page 13-89.
• DL_RLC_UNACK_NEW_BLKS on page 13-91.
• DL_TBF_FAILURE_RATE on page 13-93.
• DL_TBF_TIME_1_TS on page 13-95.
• DL_THROUGHPUT_TERMINAL_1_TS on page 13-99.
68P02901W56-T 13-5
Jan 2010
Throughput statistics Chapter 13: PCU statistics
• EGPRS_64K_CHANNELS_SWITCHED on page 13-103
• EGPRS_64K_NOT_AVAIL on page 13-104
• EGPRS_AVAIL_PDTCH on page 13-105
• EGPRS_DL_ASGN_PCCCH on page 13-106
• ETH_RX_BYTE on page 8-2.
• ETH_RX_ERROR on page 8-3.
• ETH_RX_PKT on page 8-4.
• ETH_TX_BYTE on page 8-5.
• ETH_TX_ERROR on page 8-6.
• ETH_TX_PKT on page 8-7.
• EXT_UL_EXITS on page 12-11.
• EXT_UL_USF_USAGE on page 12-12.
• GBL_DL_DATA_THRPUT on page 13-109.
• GBL_DL_DATA_THRPUT_HIST on page 13-110.
• GBL_UL_DATA_THRPUT on page 13-117.
• GBL_UL_DATA_THRPUT_HIST on page 13-118.
• GPRS_AVAIL_PDTCH on page 13-127.
• IDLE_PDTCH_INTF_BAND1 on page 13-143.
• IMM_ASSGN_CAUSE on page 13-147.
• PRP_LOAD on page 13-164.
• PSI_TRAU_FILL_FRAME_TX on page 8-8.
• UL_BLER_CS1 on page 13-170.
• UL_BLER_MCS1 on page 13-177.
13-6 68P02901W56-T
Jan 2010
• UL_BUSY_PDTCH on page 13-195.
• UL_CHANNEL_REQUESTS_REJECTION_RATE on page 13-197.
• UL_CHANNEL_REQUESTS_SUCCESS_RATE on page 13-198.
• UL_LLC_FRAMES on page 13-200.
• UL_PDTCH_Q_LENGTH on page 13-205.
• UL_PDTCH_SEIZURE on page 13-206.
• UL_RADIO_BLKS_8PSK_1_TS on page 13-207.
• UL_RADIO_BLKS_GMSK_1_TS on page 13-215.
• UL_RLC_ACK_NEW_BLKS on page 13-223.
• UL_RLC_RETX_BLKS on page 13-225.
• UL_RLC_UNACK_NEW_BLKS on page 13-227.
• UL_TBF_FAILURE_RATE on page 13-229.
• UL_TBF_TIME_8PSK_1_TS on page 13-230.
• UL_TBF_TIME_GMSK_1_TS on page 13-234.
68P02901W56-T 13-7
Jan 2010
Utilization statistics Chapter 13: PCU statistics
• UL_THROUGHPUT_TERMINAL_1_TS on page 13-238
• UL_THROUGHPUT_TERMINAL_2_TS on page 13-240.
Utilization statistics
Utilization statistics measure how effectively GPRS resources are being utilized. These
measurements assist the operator in planning the necessary resources required for the MS to
efficiently use the network.
The utilization statistics include the following:

• CS_PAGE_REQS on page 13-29.
• GPRS_CELL_CONGESTION on page 13-129.
• PACCH_PAGE_REQS on page 13-160.
• PDU_DISCARD_FR on page 13-161.
• PDU_DISCARD_LLC on page 13-162.
• PS_PAGE_REQS on page 13-166.
• TBF_DL_ASGN_PACCH on page 13-167.
• TBF_REL_PACCH_LOST on page 13-168.
• TBF_SESSIONS on page 13-169.
13-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AIR_DL_CONTROL_BLKS
AIR_DL_CONTROL_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_DL_CONTROL_BLKS statistic tracks the number of downlink control Radio Link
Control (RLC) blocks sent by the Packet Control Unit (PCU). Examples for downlink control
blocks are:
• Packet Uplink ACK/NACK.
• Packet Uplink Assignment.
• Packet Downlink Assignment.
• Packet Timeslot Reconfigure.
• Packet Power Control/Timing Advance.
• Packet Cell Change Order.
Retransmissions of control blocks are included in this statistic.
Pegging
This statistic is pegged for each control block sent down.
NOTE
Analysis
This statistic can be used for the trend analysis of the number of Radio Link Control blocks
sent by the PCU.
Reference None.
Basis Cell.
Type Counter.
68P02901W56-T 13-9
Jan 2010
AIR_DL_TBF_FAILURES Chapter 13: PCU statistics
AIR_DL_TBF_FAILURES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_DL_TBF_FAILURES statistic tracks the total number of downlink Temporary Block
Flow (TBF) that are abnormally released in the different phases (identified in the bins) due
to radio failures in a cell.
Table 13-1 AIR_DL_TBF_FAILURES bins
Bin Description
0 Establishment.
1 Data transfer.
2 Delayed TBF release mode.
3 Termination.
To see the relationship between the MS, BSS, and MSC for this statistic, refer to Throughput
statistics on page 19-87 in Chapter 19 Ladder diagrams.
Pegging
This statistic pegs each time a downlink TBF is established, and later abnormally released due
to radio failures in a cell during a statistical measurement interval. The statistic pegs the
appropriate bin depending on the phase where the TBF was abnormally released.
NOTE
Analysis
Reference None
Usage Performance management
Basis Cell.
Type Counter array.
13-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AIR_UL_CONTROL_BLKS
AIR_UL_CONTROL_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_UL_CONTROL_BLKS statistic tracks the number of uplink control Radio Link Control
(RLC) blocks received by the PCU. Examples for Uplink control blocks are:
• Packet Downlink ACK/NACK.
• Packet Control Acknowledgment.
• Packet Resource Request.
• Uplink Dummy Control Block.
Retransmissions of control blocks are included in this statistic.
Pegging
This statistic is pegged for each control block the network receives from the MS.
NOTE
Analysis
This statistic can be used for the trend analysis of Radio Link Control blocks sent by the MS.
Reference None.
Basis Cell.
Type Counter.
68P02901W56-T 13-11
Jan 2010
AIR_UL_TBF_FAILURES Chapter 13: PCU statistics
AIR_UL_TBF_FAILURES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_UL_TBF_FAILURES statistic tracks the total number of uplink Temporary Block
Flow (TBF) that are abnormally released in the different phases (identified in the bins) due
to radio failures in a cell.
Table 13-2 AIR_UL_TBF_FAILURES bins
Bin Description
0 Establishment.
1 Data transfer.
2 Ext UL TBF mode

3 Termination.
statistics on page 19-87.
Pegging
This statistic pegs each time an uplink TBF is established, and later abnormally released due
to radio failures in a cell during a statistical measurement interval. The statistic pegs the
appropriate bin depending on the phase where the TBF was abnormally released.
NOTE
Analysis
Reference None
Basis Cell.
Type Counter array.
13-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AVG_SIMUL_DL_TBFS
AVG_SIMUL_DL_TBFS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The gauge statistic AVG_SIMUL_DL_TBFS measures the average number of simultaneous

downlink TBFs per cell.
Pegging
The average simultaneous DL TBFs are calculated over a sample period of 80 ms. GTS pegs
the average number of DL TBFs that were active over 80 ms.
DL-TBF is considered successfully established when:

• The first PDAN (Packet Downlink ACK/NACK) is received by the network.
DL-TBF is considered being closed when:

• The final PDAN is received by the network and timer T3193 has expired.
• The downlink TBF includes the final super-coattail and T3193 has expired.
• An abnormal downlink TBF termination occurs.
Analysis
Reference None.
Usage Measures the average number of simultaneous downlink TBFs per cell.
Basis Cell
Type Gauge.
68P02901W56-T 13-13
Jan 2010
AVG_SIMUL_UL_TBFS Chapter 13: PCU statistics
AVG_SIMUL_UL_TBFS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The gauge statistic AVG_SIMUL_UL_TBFS measures the average number of simultaneous

uplink TBFs per cell.
Pegging
The average simultaneous active UL TBFs are calculated over a sample period of 80 ms. GTS
pegs the average number of UL TBFs that were active over 80 ms.
UL-TBF is considered being established successfully when:

• A Packet Uplink Assignment (PUA), Immediate Assignment or Packet Timeslot Reconfigure
(PTR) is sent to the MS.
UL-TBF is considered being closed when:

• A final PUAK CA (Packet Uplink Assignment ACK/NACK Control Acknowledgment) is
received by the network.
• An abnormal uplink TBF termination occurs.
NOTE
FPUAK CA cannot be received by the MS due to cell reselections or if the MS is
not waiting for the CA to close the uplink TBF. In that case, the uplink TBF has to
be considered closed after waiting for the CA timeout (The uplink TBF duration is
measured as longer than it is in reality, as in this case).
Analysis
Reference None.
Usage Measures the average number of simultaneous uplink TBFs per cell.
Basis Cell
Type Gauge.
13-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application BLOCKED_DL_TBFS
BLOCKED_DL_TBFS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The counter array statistic BLOCKED_DL_TBF counts the number of occurrences of blocked
downlink TBF establishment for various causes.
Pegging
The BLOCKED_DL_TBFS statistic pegs the appropriate bin for each occurrence of a blocked
downlink TBF establishment due to the following failure causes:
• Insufficient RSL bandwidth.
• Insufficient resources for any of the following reasons:

Maximum number of DL TBFs per PDCH is reached (4 TBFs/PDCH).
No TFI available.
Insufficient memory.
Maximum PRP load is reached.
• TBF rejected because of Quality of Service constraints:

PFC establish failure due to budgeted TSZ MTBR check and the PFC is the only
one at TBF.
PFC establish failure due to current TSZ TSu check and the PFC is the only one at TBF.
PFC establish failure due to board-level TSu check and the PFC is the only one at TBF.
Table 13-3 BLOCKED_DL_TBFS bins

0 INSUFF_RSL_BANDWIDTH Occurrence of a blocked downlink TBF establishment
because of insufficient RSL bandwidth.
1 INSUFF_RESOURCE Occurrence of a blocked downlink TBF establishment
because of insufficient resources.
2 TBF_REJ_QOS_CONSTRAIN TBF rejected because of Quality of Service constraints.
68P02901W56-T 13-15
Jan 2010
Analysis Chapter 13: PCU statistics
Analysis
Reference None.
Usage Counts the number of occurrences of blocked downlink TBF establishments
for various causes.
Basis Cell
Type Small counter array.
13-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CELL_FLUSH_REQS
CELL_FLUSH_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CELL_FLUSH_REQS statistic tracks the number of flush requests received on the GBL(s)
per-cell basis.
Pegging
This statistic is pegged each time a flush request is received on the GBL to flush the Logical
Link Control (LLC) Protocol Data Unit (PDU) for a particular MS.
Analysis
This statistic can be used for the trend analysis of the number of flush messages received
by the BSS.
Reference None.
Congestion.
Basis Cell
Type Counter.
NOTE
This statistic was previously known as GBL_FLUSH_REQS.
68P02901W56-T 13-17
Jan 2010
CH_REQ_UNSVCD_PCU Chapter 13: PCU statistics
CH_REQ_UNSVCD_PCU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CH_REQ_UNSVCD_PCU statistic tracks the total number of uplink GPRS channel requests
unserviced by the PCU.
This statistic represents the major reasons for not servicing GPRS channel requests at the PCU.
Minor condition scenarios, such as the channel request being received in a wrong MS/TBF state
due to system race conditions, and various system delays are minimal and are not covered
in any of the bins earlier.
Pegging
This statistic is pegged for each channel request unserviced by the PCU.
Table 13-4 CH_REQ_UNSVCD_PCU bins

1 CH_REC_PCU_R_BW RACH - RSL bandwidth limitation. The RSL traffic
has reached the limitation and resources cannot be
assigned for a RACH.
2 CH_REC_PCU_R_RTD RACH - Round Trip Delay (RTD)/timeout. The
RACH is not serviced due to RACH is too old to be
processed.
3 CH_REC_PCU_R_IR RACH - Insufficient resources. The RACH cannot
be serviced because the PCU lacks the necessary
resources to establish a TBF.
4 CH_REC_PCU_P_RTD PRACH - Round Trip Delay (RTD)/timeout. The
PRACH is not serviced due to PRACH is too old to
be processed.
5 CH_REC_PCU_P_IR PRACH - Insufficient resources. The PRACH cannot
be serviced because the PCU lacks the necessary
6 CH_REC_PCU_PR_RTD PRR - Round Trip Delay (RTD)/timeout. The PRR is
not serviced due to PRR is too old to be processed.
7 CH_REC_PCU_PR_IR PRR - Insufficient resources. The PRR cannot be
serviced because the PCU lacks the necessary
8 CH_REC_PCU_PD_IR PDAK - Insufficient resources. The channel request
in the PDAK cannot be serviced because the PCU
lacks the necessary resources to establish a TBF.
13-18 68P02901W56-T
Jan 2010
NOTE
Analysis
This statistic can be used for the trend analysis of the PCU.
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 13-19
Jan 2010
CHANNEL_REQS_REC Chapter 13: PCU statistics
CHANNEL_REQS_REC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHANNEL_REQS_REC statistic tracks the number of channel or resource request

messages received by the PCU.
Table 13-5 CHANNEL_REQS_REC bins
Bin OMC-R Name Description

0 CHANNEL_REQS_REC_P_C A GPRS One-Phase Access Channel request
is received.
1 CHANNEL_REQS_REC_P_P A GPRS One-Phase access packet channel
request on PCCCH is received.
2 CHANNEL_REQS_REC_B_C A GPRS single block allocation on CCCH is
received.
3 CHANNEL_REQS_REC_B_P A GPRS single block allocation on PCCCH
is received.
4 CHANNEL_REQS_REC_P_R A GPRS Packet Resource Request (PRR)
message is received (second phase of two
phase access).
5 CHANNEL_REQS_REC_CP_A A GPRS Channel Request in Packet
Downlink ACK/NACK (PDAK) message is
received.
6 CHANNEL_REQS_REC_E_C An Enhanced One-Phase (EOP) access
indication is received.
7 CHANNEL_REQS_REC_EGPRS_1PH_CC EGPRS One-Phase access on CCCH is
received.
8 CHANNEL_REQS_REC_EGPRS_1PH_PCC An EGPRS One-Phase access on PCCCH is
received.
9 CHANNEL_REQS_REC_EGPRS_SBK_CC An EGPRS Single Block Allocation on CCCH
is received.
10 CHANNEL_REQS_REC_EGPRS_SBK_PCC An EGPRS Single Block Allocation on
PCCCH is received.
11 CHANNEL_REQS_REC_EGPRS_PKRS_RQ An EGPRS Packet Resource Request is
received.
12 CHANNEL_REQS_REC_EGPRS_CRQPDAK An EGPRS Channel Request in Packet
Downlink ACK/NACK (PDAK) message is
received.
NOTE
The OMC displays the bins alphabetically.
13-20 68P02901W56-T
Jan 2010
To see the relationship between the MS, BSS, and MSC for this statistic, refer to Accessibility
Pegging
This statistic pegs for each channel request message received. The bin that is incremented is
determined by the channel request message type.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 13-21
Jan 2010
CHANNEL_REQS_REJECT Chapter 13: PCU statistics
CHANNEL_REQS_REJECT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHANNEL_REQS_REJECT statistic tracks the number of rejections by the PCU for
packet channel or resource requests. The PCU rejects such requests because the resources
are unavailable.
Pegging
This statistic pegs when a Packet Access Reject message is sent to the MS in response to a
UL Request in PDAK or to a Packet Resource Request (two-phase access) when there are no
resources left to allocate. No retransmissions are pegged.
NOTE
Analysis
Reference None.
Congestion.
Basis Cell.
Type Counter.
13-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CHANNEL_REQS_SUCCESS
CHANNEL_REQS_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of channel or resource requests that are allocated a TBF
resource successfully.
This statistic specifically counts the number of ASSIGNMENT messages sent to the MS.
Re-transmissions are excluded.
Table 13-6 CHANNEL_REQS_SUCCESS bins

0 CHANNEL_REQS_SUCCESS_P_C A GPRS One-Phase Access Packet
Immediate Assignment (PIA) is sent on
CCCH.
1 CHANNEL_REQS_SUCCESS_P_P A GPRS One-Phase Access Packet Uplink
Assignment (PUA) is sent on PCCCH.
2 CHANNEL_REQS_SUCCESS_B_C A GPRS Single Block Allocation PIA is sent
on CCCH.
3 CHANNEL_REQS_SUCCESS_B_P A GPRS Single Block Allocation PUA is sent
on CCCH.
4 CHANNEL_REQS_SUCCESS_P_R A GPRS PUA (in response to Packet
Resource Request) is sent to establish a
TBF (only the first PUA is counted).
5 CHANNEL_REQS_SUCCESS_PKTS A GPRS Packet Timeslot Reconfiguration
(PTR) is sent to establish a new TBF or to
re-assign the downlink TBF (only the first
PTR is counted).
6 CHANNEL_REQS_SUCCESS_E_C An Enhanced One-Phase (EOP) Access
indication is received on CCCH.
7 CHANNEL_REQS_SUCCESS_CP_A A GPRS PUA in response to a channel
request received in a Packet Downlink
ACK.
8 CHANNEL_REQS_SUCCESS_E_1P_CCC An EGPRS One-Phase Access Immediate
Assignment (IA) is sent on CCCH.
9 CHANNEL_REQS_SUCCESS_E_1P_PCCC An EGPRS One-Phase Access Packet Uplink
Assignment (PUA) is sent on PCCCH.
10 CHANNEL_REQS_SUCCESS_E_SB_CCC An EGPRS Single Block Allocation PIA is
sent on CCCH.
Continued
68P02901W56-T 13-23
Jan 2010
Pegging Chapter 13: PCU statistics
Table 13-6 CHANNEL_REQS_SUCCESS bins (Continued)

11 CHANNEL_REQS_SUCCESS_E_SB_PCCC An EGPRS Single Block Allocation PUA is
sent on PCCCH.
12 CHANNEL_REQS_SUCCESS_E_PUAPRR An EGPRS PUA (in response to Packet
Resource Request (PRR)) is sent to establish
a TBF (only the first PUA is counted).
13 CHANNEL_REQS_SUCCESS_E_PTR An EGPRS PTR is sent to establish a new
TBF or to re-assign the downlink TBF (only
the first PTR is counted).
14 CHANNEL_REQS_SUCCESS_E_PUAPDAK An EGPRS PUA in response to a channel
request in a PDAK.
NOTE
The OMC displays the bins alphabetically.
Pegging
This statistic pegs for each channel request message granted on the downlink. The bin that
is incremented is determined by the channel request message type. Retransmissions are not
pegged.
Analysis
The statistic can be used for the trend analysis of the number of successful uplink GPRS calls
made by a particular CELL.

Congestion.
Basis Cell.
Type Counter array.
13-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CODING_SCHEME_CHANGE
CODING_SCHEME_CHANGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CODING_SCHEME_CHANGE statistic is obtained by measuring the number of coding

scheme upgrades (from lower to higher coding scheme) and coding scheme downgrades (from
higher to lower coding scheme) for the uplinks and downlinks in a statistical measurement
period.
NOTE
• Controls blocks (always sent at CS-1) results in this statistic not being pegged.
• Downlink coding scheme transitions for dummy blocks (when entering and
exiting super-coattail) is not be counted.
The bins are defined in Table 13-7.

Table 13-7 CODING_SCHEME_CHANGE bins

0 CODING_SCHEME_CHANGE_0 Total number of GPRS coding scheme upgrades
for uplink.
1 CODING_SCHEME_CHANGE_1 Total number of GPRS coding scheme downgrades
for uplink.
2 CODING_SCHEME_CHANGE_2 Total number of GPRS coding scheme upgrades
for downlink.
3 CODING_SCHEME_CHANGE_3 Total number of GPRS coding scheme downgrades
for downlink.
4 CODING_SCHEME_CHANGE_4 Total number of EGPRS coding scheme upgrades
for uplink.
5 CODING_SCHEME_CHANGE_5 Total number of EGPRS coding scheme downgrades
for uplink.
6 CODING_SCHEME_CHANGE_6 Total number of EGPRS coding scheme upgrades
for downlink.
7 CODING_SCHEME_CHANGE_7 Total number of EGPRS coding scheme downgrades
for downlink.
Pegging
The appropriate bin is incremented each time a change in coding scheme occurs.
68P02901W56-T 13-25
Jan 2010
Analysis
This statistic can be used for the trend analysis of the number of Coding Scheme upgrades and
downgrades on the uplink and downlink which may signify that the cell is congested.

Congestion.
Basis Cell.
Type Counter array.
13-26 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CONG_REL_DL_SCTS
CONG_REL_DL_SCTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONG_REL_DL_SCTS statistic tracks the total number of downlink TBF terminations
under the delayed TBF release mode (super-coattail) in a cell, as cell availability goes below
the following thresholds:
• 25 block periods (500 ms) old super-coattail is terminated if the
cell availability reached is ≤ 25%, in a cell with ≤ 3 TS.
cell availability reached is ≤ 10%, in a cell with > 5 TS.
• 15 block periods (300 ms) old super-coattail is terminated if the

cell availability reached is ≤ 30%, in a cell with > 5 TS.
The minimum super-coattail duration is 15 block periods or 300 ms. No super-coattail below 15
block periods is terminated.
NOTE
This statistic is accessible only if the Increased PRP Capacity feature is enabled.
Pegging
This statistic pegs each time an uplink TBF is successfully established and later released
under the delayed TBF release mode to relieve the congestion in a cell during a statistical
measurement interval.
NOTE
68P02901W56-T 13-27
Jan 2010
Analysis
Reference None
Basis Cell.
Type Counter.
13-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CS_PAGE_REQS
CS_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS_PAGE_REQS statistic represents the total number of circuit switched page requests
received by the PCU.
Pegging
One unit represents one CS page request.
Analysis
Reference None.
Basis GBL.
Type Counter.
68P02901W56-T 13-29
Jan 2010
CS12_ON_32K_CHAN Chapter 13: PCU statistics
CS12_ON_32K_CHAN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS12_ON_32K_CHAN statistic tracks the percentage of time in a statistics reporting

period that CS-3, CS-4 capable (32kTRAU) GPRS time slots are used with CS-1 and CS-2 rates.
Pegging
This statistic measures the percentage of blocks for which CS-1 and CS-2 data was transmitted
on a timeslot capable of CS-3 or CS-4 rates.
Analysis
Reference None.
Usage Radio resource allocation statistics.
Network planning.
Basis Cell.
Type Percentage.
13-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CS1234_ON_64K_CHAN
CS1234_ON_64K_CHAN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS1234_ON_64K_CHAN represents the percentage of data blocks encoded with GPRS
coding schemes over the total data blocks (GPRS/EGPRS) carried by 64k TRAUs.
The statistic is not available if the EGPRS feature is restricted.
Pegging
The range is 0% to 100%.
Analysis
Reference None.
Basis Cell.
Type Percentage.
68P02901W56-T 13-31
Jan 2010
CS1_USE_DL Chapter 13: PCU statistics
CS1_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS1_USE_DL key statistic provides usage figures of DL coding scheme CS-1 for GPRS.
Formula
!
DL− RADIO− BLKS− 1− T S− CS− 1 + DL− RADIO− BLKS− 2− T S− CS− 1+
∗ 100
DL− RADIO− BLKS− 3− T S− CS− 1 + DL− RADIO− BLKS− 4− T S− CS− 1
CS1− USE− DL =  
DL− RADIO− BLKS− 1− T S + DL− RADIO− BLKS− 2− T S + DL− RADIO− BLKS− 3− T S+
 
 DL− RADIO− BLKS− 4− T S + DL− RADIO− BLKS− 5− T S + DL− RADIO− BLKS− 6− T S+ 
 
DL− RADIO− BLKS− 7− T S + DL− RADIO− BLKS− 8− T S
Analysis
Type Percentage.
Raw statistics DL_RADIO_BLKS_1_TS,
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
DL_RADIO_BLKS_5_TS,
DL_RADIO_BLKS_6_TS,
DL_RADIO_BLKS_7_TS,
DL_RADIO_BLKS_8_TS
and their bin 0.
13-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CS2_USE_DL
CS2_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
!
DL− RADIO− BLKS− 1− T S− CS− 2 + DL− RADIO− BLKS− 2− T S− CS− 2+
∗ 100
DL− RADIO− BLKS− 3− T S− CS− 2 + DL− RADIO− BLKS− 4− T S− CS− 2
CS2− USE− DL =  
DL− RADIO− BLKS− 1− T S + DL− RADIO− BLKS− 2− T S + DL− RADIO− BLKS− 3− T S+
 
 DL− RADIO− BLKS− 4− T S + DL− RADIO− BLKS− 5− T S + DL− RADIO− BLKS− 6− T S+ 
 
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
DL_RADIO_BLKS_5_TS,
DL_RADIO_BLKS_6_TS,
DL_RADIO_BLKS_7_TS,
DL_RADIO_BLKS_8_TS
and their bin 1.
68P02901W56-T 13-33
Jan 2010
CS3_USE_DL Chapter 13: PCU statistics
CS3_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS3_USE_DL key statistic provides usage figures DL coding scheme CS-3 for GPRS.
Formula
DL− RADIO− BLKS− 1− T S− CS− 3+

DL− RADIO− BLKS− 4− T S− CS− 3
CS3− USE− DL = ∗ 100
DL− RADIO− BLKS− 1− T S+

DL− RADIO− BLKS− 4− T S
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 2
13-34 68P02901W56-T
Jan 2010
CS4_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

DL− RADIO− BLKS− 4− T S− CS− 4
CS4− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 3
68P02901W56-T 13-35
Jan 2010
DL_BLER_CS1 Chapter 13: PCU statistics
DL_BLER_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BLER_CS1 statistic indicates the number of times, measured at statistical intervals,
the BLER of a particular carrier, when using coding scheme 1 to transmit in the downlink
direction, falls into the given range. Each bin represents a range of percentage BLER, with high
value of the range indicated in the bin name.
Pegging
Each bin represents the different range of BLER:
Table 13-8 Bin ranges for DL_BLER_CS1
Bin Range
0 ≥ 0, <5%
1 ≥ 5%, < 10%
2 ≥ 10%, < 15%
3 ≥15%, < 20%
4 ≥ 20%, < 25%
5 ≥ 25%, < 30%
6 ≥ 30%, < 40%
7 ≥ 40%, ≤ 100%
One unit represents 10 DL BLER calculations. For a given carrier using coding scheme 1
in downlink transfer, the calculation is done by using a weighted algorithm that applies on
Ack/Nack bitmaps obtained from currently and previously received PDAK by the PCU. 10X+Y
(1<=Y<=10) calculations is represented as X+1.
The range is 0 to 9,000. PDAKs can be received as frequently as once in every two blocks. So in a
one hour period, there is a maximum of 3,600,000 ms/(2x20 ms) = 90,000 PDAKs being received.
Thus there is at the most 90,000 calculations, and the maximum value is 9,000 for each bin.
13-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Formula
Formula
DL− RLC− NACK− BLKS− CS− 1

DL− BLER− CS− 1 = ! ∗ 100
DL− RLC− NACK− BLKS− CS− 1+
DL− RLC− ACK− NEW− BLKS− CS− 1
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-37
Jan 2010
DL_BLER_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging

Bin Range
0 ≥ 0, < 10%
1 ≥ 10%, < 20%
2 ≥ 20%, < 25%
3 ≥ 25%, < 30%
4 ≥30%, < 35%
5 ≥ 35%, < 40%
6 ≥ 40%, < 65%
7 ≥ 65%, ≤ 100%
13-38 68P02901W56-T
Jan 2010
Formula

DL− BLER− CS− 2 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-39
Jan 2010
DL_BLER_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
This statistic is unavailable if coding scheme 3/4 is disabled.
Pegging
Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 25%
2 ≥ 25%, < 30%
3 ≥ 30%, < 35%
4 ≥ 35%, < 40%
5 ≥ 40%, < 45%
6 ≥ 45%, < 70%
7 ≥ 70%, ≤ 100%
13-40 68P02901W56-T
Jan 2010
Formula

DL− BLER− CS− 3 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-41
Jan 2010
DL_BLER_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
This statistic is unavailable if coding scheme 3/4 is disabled.
Pegging

Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 65%
7 ≥ 65%, ≤ 100%
13-42 68P02901W56-T
Jan 2010
Formula

DL− BLER− CS− 4 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-43
Jan 2010
DL_BLER_MCS1 Chapter 13: PCU statistics
DL_BLER_MCS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BLER_MCS2 statistic indicates the number of times, measured at statistical intervals,
the BLER of a particular carrier, when using EGPRS modulation coding scheme 1 to transmit in
the downlink direction, falls into the given range. Each bin represents a range of percentage
BLER, with high value of the range indicated in the bin name.
The statistic is not available if the EGPRS feature is disabled.
Pegging
Table 13-12 Bin ranges for DL_BLER_MCS1
Bin Range
0 ≥ 0, < 5%
1 ≥ 5%, < 10%
2 ≥ 10%, < 15%
3 ≥ 15%, < 20%
4 ≥ 20%, < 25%
5 ≥ 25%, < 30%
6 ≥ 30%, < 40%
7 ≥ 40%, ≤ 100%
One unit represents 10 DL BLER calculations. For a given carrier using EGPRS modulation
coding scheme 1 in downlink transfer, the calculation is done by using a weighted algorithm
that applies on Ack/Nack bitmaps obtained from currently and previously received PDAK by the
PCU. 10X+Y (1<=Y<=10) calculations is represented as X+1.
one hour period, there is a maximum of 3,600,000ms/(2x20ms) = 90,000 PDAKs being received.
13-44 68P02901W56-T
Jan 2010
Formula
DL− RLC− NACK− BLKS− MCS− 1

DL− BLER− MCS− 1 = ! ∗ 100
DL− RLC− NACK− BLKS− MCS− 1+
DL− RLC− ACK− NEW− BLKS− MCS− 1
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-45
Jan 2010
DL_BLER_MCS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging

Bin Range
0 ≥ 0, < 10%
1 ≥ 10%, < 20%
2 ≥ 20%, < 25%
3 ≥ 25%, < 30%
4 ≥ 30%, < 35%
5 ≥ 35%, < 40%
6 ≥ 40%, < 65%
7 ≥ 65%, ≤ 100%
one hour period, there is a maximum of 3,600,000ms/(2x20ms) = 90,000 PDAKs being received.
13-46 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 2 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-47
Jan 2010
DL_BLER_MCS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 10%
1 ≥ 10%, < 20%
2 ≥ 20%, < 25%
3 ≥ 25%, < 30%
4 ≥ 30%, < 35%
5 ≥ 35%, < 40%
6 ≥ 40%, < 65%
7 ≥ 65%, ≤ 100%
13-48 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 3 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-49
Jan 2010
DL_BLER_MCS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Table 13-15 Bin range for DL_BLER_MCS4
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 65%
7 ≥ 65%, ≤ 100%
13-50 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 4 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-51
Jan 2010
DL_BLER_MCS5
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 25%
2 ≥ 25%, < 30%
3 ≥ 30%, < 35%
4 ≥ 35%, < 40%
5 ≥ 40%, < 45%
6 ≥ 45%, < 70%
7 ≥ 70%, ≤ 100%
13-52 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 5 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-53
Jan 2010
DL_BLER_MCS6
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging

Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 30%
2 ≥ 30%, < 35%
3 ≥ 35%, < 40%
4 ≥ 40%, < 45%
5 ≥ 45%, < 50%
6 ≥ 50%, < 75%
7 ≥ 75%, ≤ 100%
The range is 0 to 9,000. PDAKs can be received as frequently as once in every two blocks. So
in a one hour period, there is a maximum of 3,600,000 ms/(2x20 ms) = 90,000 PDAKs being
received. Thus there is at the most 90,000 calculations, and the maximum number value is
9,000 for each bin.
13-54 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 6 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-55
Jan 2010
DL_BLER_MCS7
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging

Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%, ≤ 100%
13-56 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 7 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-57
Jan 2010
DL_BLER_MCS8
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%, ≤ 100%
O unit represents 10 DL BLER calculations. For a given carrier using EGPRS modulation coding
scheme 8 in downlink transfer, the calculation is done by using a weighted algorithm that
applies on Ack/Nack bitmaps obtained from currently and previously received PDAK by the PCU.
10X+Y (1<=Y<=10) calculations is represented as X+1.
13-58 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 8 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-59
Jan 2010
DL_BLER_MCS9
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 35%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%, ≤ 100%
13-60 68P02901W56-T
Jan 2010
Formula

DL− BLER− MCS− 9 = ! ∗ 100
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-61
Jan 2010
DL_BUSY_PDTCH Chapter 13: PCU statistics
DL_BUSY_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean, MAX, and min number of the occupied Packet Data Channels
(PDCH) carrying downlink packet traffic.
This statistic is obtained by sampling the PDTCHs, which are carrying packet traffic, at every
packet-scheduling period (20 millisecond).
Table 13-21 shows the ranges for each bin (measured in milliseconds).
NOTE
The busy PDTCH number may increase as the additional switchable PDTCH is
allocated for GPRS congested cell.
Table 13-21 DL_BUSY_PDTCH bins
Bin Range
0 No PDTCH is busy
1 1-2 PDTCH are busy
Pegging
This statistic pegs every packet-scheduling period (20 millisecond) by sampling the number of
PDTCHs that are carrying downlink packet traffic.
NOTE
13-62 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for downlink
packet traffic.

Congestion.
Basis Cell
68P02901W56-T 13-63
Jan 2010
DL_LLC_FRAMES_GB Chapter 13: PCU statistics
DL_LLC_FRAMES_GB
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_LLC_FRAMES_GB statistic represents the total number of downlink LLC frames
correctly received from the SGSN over the Gb link.
Pegging
Each bin represents a range of the size of frames, with high value of the range indicated in
the bin name.
Table 13-22 Bin ranges for DL_LLC_FRAMES_GB
Bin Name Range

0 DL_LLC_FRAMES_GB_20 0 - 20
6 DL_LLC_FRAMES_GB_1280 641 - 1280
7 DL_LLC_FRAMES_GB_OVER1280 1281 and up
One unit represents 10 LLC frames. 10X+Y (1<=Y<=10) calculations is represented as X+1.
The range is 0 to 65,535. The maximum number of LLC frames received from the SGSN during a
one hour period cannot be accurately estimated. Use the upper limit of a 16-bit unsigned integer.
Analysis
Reference None.
Usage Key statistics:
DL_LLC_TRAFFIC_VOLUME_INDICATOR,
LLC_ABNORMAL_TBF_RELEASES,
LLC_BUFFER_OVERFLOW_RATE,
LLC_DISCARDS_ON_CELL_RESELECTION.
Basis Cell.
Type Counter array.
13-64 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_LLC_FRAMES_PCU
DL_LLC_FRAMES_PCU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_LLC_FRAMES_PCU statistic represents the total number of downlink LLC frames
received from another cell managed by the same PCU.
Pegging
Each bin represents a range which the size of LLC frames falls into:
Table 13-23 Bin ranges for DL_LLC_FRAMES_PCU
Bin Name Range

0 DL_LLC_FRAMES_PCU_20 0 - 20
7 DL_LLC_FRAMES_PCU_OVER1280 1281 and up
The range is 0 to 65,535. The maximum number of LLC frames received from other cells during a
one hour period cannot be accurately estimated. Use the upper limit of a 16-bit unsigned integer.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 13-65
Jan 2010
DL_MEAN_TBF_DURATION Chapter 13: PCU statistics
DL_MEAN_TBF_DURATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_MEAN_TBF_DURATION statistic provides the mean duration of successful TBFs

in the downlink.
Formula
 
DL− T BF− T IM E− 1− T S+
 
 
 DL− T BF− T IM E− 2− T S+ 
  ∗ 0.02
 DL− T BF− T IM E− 3− T S+ 
 
DL− T BF− T IM E− 4− T S
DL− MEAN− TBF− DURATION =  
DL− P DT CH− SEIZU RE−
 
 
 AIR− DL− T BF− F AILU RES− DT − 
 
 AIR− DL− F AILU RES− DR− 
 
AIR− DL− T BF− F AILU RES− T
Analysis

Congestion.
Basis Cell.
Type Seconds.
Raw statistics DL_TBF_TIME_1_TS.
DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
DL_PDTCH_SEIZURE.
AIR_DL_TBF_FAILURES_DT.
AIR_DL_TBF_FAILURES_DR.
AIR_DL_TBF_FAILURES_T.
13-66 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_MEAN_USER_TRAFFIC_PER_TBF
DL_MEAN_USER_TRAFFIC_PER_TBF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_MEAN_USER_TRAFFIC_PER_TBF statistic estimates the mean amount of RLC/MAC

traffic transported in a downlink TBF, excluding retransmitted blocks. Therefore, this key
statistic includes only successful RLC blocks.
Formula
(A1 ∗22)+(A2 ∗33)+(A3 ∗39)+(A4 ∗53)+(A5 ∗22)+(A6 ∗28)+(A7 ∗37)
DL− MEAN− USER− +(A8 ∗44)+(A9 ∗56)+(A10 ∗74)+(A11 ∗112)+(A12 ∗136)+(A13 ∗148)
= ∗100
TRAFFIC− PER− TBF 1024∗DL− PDTCH− SEIZURE
DL− RLC− ACK− NEW− BLKS− CS− 1+

A1 =
DL− RLC− UNACK− NEW− BLKS− CS− 1

A2 =

A3 =

A4 =
68P02901W56-T 13-67
Jan 2010
DL− RLC− ACK− NEW− BLKS− MCS− 1+

A5 =
DL− RLC− UNACK− NEW− BLKS− MCS− 1

A6 =

A7 =

A8 =

A9 =

A10 =

A11 =

A12 =

A13 =
Analysis

Congestion.
Basis Cell.
Type Kbytes per TBF.
Raw statistics Bins 0 to 12 of DL_RLC_ACK_NEW_BLKS and
DL_RLC_UNACK_NEW_BLKS.
13-68 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_PDTCH_Q_LENGTH
DL_PDTCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic is obtained by sampling the Downlink Request Queue. A Downlink Request is
triggered on arrival of LLC-PDUs at the PCU.
Pegging
This statistic pegs every 20 ms. It is incremented when a request is added to the queue and is
decremented when a request is processed, that is, it leaves the queue.
NOTE
This statistic is pegged for both the GPRS and EGPRS events.
Analysis
This statistic can be used for the trend analysis of the average number of downlink messages
waiting for a PDTCH to become available.

Congestion.
Basis Cell.
Type Gauge.
68P02901W56-T 13-69
Jan 2010
DL_PDTCH_SEIZURE Chapter 13: PCU statistics
DL_PDTCH_SEIZURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the successful Packet Data Traffic Channel (PDTCH) seizure on the
downlink. This statistic counts the number of TBF(s) on the downlink. The statistic is obtained by
measuring the receipt of the first RLC block (PDU) on the PDTCH from the network (downlink).
Pegging
This statistic is pegged each time a DL TBF is successfully established and the MS is listening
on the PDTCH. Specifically, it is pegged when the network receives the first DAK from the MS.
NOTE
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink
for a CELL.

Key statistics:
DL_TBF_SUCCESS_RATE,
TBF_DROP_RATE_ON_PACCH_LOST.
Basis Cell.
Type Counter.
13-70 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RADIO_BLKS_1_TS
DL_RADIO_BLKS_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RADIO_BLKS_1_TS statistic counts the total number of RLC radio blocks sent to the
MSs that support a maximum of 1 TS in the downlink direction.
One unit represents 100 RLC radio blocks. The maximum statistical interval is 60 minutes. The
translation of the actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine EGPRS
coding schemes, as shown in Table 13-24.
Table 13-24 Bin ranges for DL_RADIO_BLKS_1_TS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
In coding schemes MCS-7 through MSC-9, there are two RLC blocks in a radio block. The data
shown in the following table is used to determine which statistic must be pegged for possible
combinations of NEW, NACK, ACK_PEND, and STALL when transmitting MCS-7, MCS-8,
or MCS-9.
68P02901W56-T 13-71
Jan 2010
Table 13-25 Pegging method for DL_RADIO_BLKS_1_TS statistic
(RLC block 1, RLC block 2) DL radio block status

(NACK, NACK) NACK
(NACK, NEW) NACK
(NACK, ACK_PEND) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(ACK_PEND, ACK_PEND) ACK_PEND
(NACK, STALL) STALL
(NEW, STALL) STALL
(STALL, STALL) STALL
The DL_RADIO_BLKS_1_TS statistic can be used with DL_TBF_TIME_1_TS to calculate the

effective downlink throughput per terminal type for MS multislot classes supporting one
PDTCH in downlink.
NOTE
An MS can have different MS multislot classes for GPRS (GMSK) and EGPRS (8-PSK).
Pegging
This statistic counts the RLC radio blocks for MSs that support a maximum of 1 TS in the
downlink direction as follows:
• Always pegged for MSs with multislot class 1.
• CS-1 through CS-4 are pegged if the GPRS multislot is Class 1.
• MCS-1 through MCS-9 are pegged if the EGPRS multislot is Class.
For examples, see 3GPP TS05.02, Annex B (normative).
The DL_RADIO_BLKS statistics are only reported for successful TBFs. Bin 0 (CS-1) and bin 4
(MCS-1), do not count super-coattail blocks.
Only RLC data radio blocks are counted. No retransmissions due to any cause are pegged. The
RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Basis Cell
Type Counter array
13-72 68P02901W56-T
Jan 2010
DL_RADIO_BLKS_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
translation of the actual radio blocks counted to units is done at the end of the interval.
The RLC radio blocks are split into the four GPRS channel coding schemes, and the nine EGPRS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-73
Jan 2010

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL

effective downlink throughput per terminal type for MS multislot classes supporting two
PDTCHs in downlink.
NOTE
Pegging
This statistic counts the RLC radio blocks for the MSs that support a maximum of 2 TS in
the downlink direction as follows:
• Always pegged for MSs with multislot class 2, 3, or 5.
• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the MS and its GPRS
multislot is class 2,3, or 5.
• MCS-1 through MCS-9 are pegged if an EGPRS mode TBF is assigned to the MS and the
EGPRS multislot is class 2, 3, or 5.
The DL_RADIO_BLKS statistics are reported only for successful TBFs. Bin 0 (CS-1) and bin 4
Only RLC data radio blocks are counted. No retransmissions due to any other causes are pegged.
The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
13-74 68P02901W56-T
Jan 2010
Analysis
Reference None
Basis Cell
Type Counter array
68P02901W56-T 13-75
Jan 2010
DL_RADIO_BLKS_3_TS Chapter 13: PCU statistics
DL_RADIO_BLKS_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
13-76 68P02901W56-T
Jan 2010

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Multislot class 13 is treated as multislot class 9.

effective downlink throughput per terminal type for MS multislot classes supporting three
PDTCHs in downlink.
NOTE
Pegging
• Always pegged for the MSs with multislot class 4, 6, 7, 9, or 13.
multislot is class 4, 6, 7, 9, or 13.
EGPRS multislot is class 4, 6, 7, 9, or 13.
68P02901W56-T 13-77
Jan 2010
Analysis
Reference None
Basis Cell
Type Counter array
13-78 68P02901W56-T
Jan 2010
DL_RADIO_BLKS_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
translation of actual radio blocks counted to units is done at the end of the interval.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-79
Jan 2010

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL

effective downlink throughput per terminal type for MS multislot classes supporting four
PDTCHs in downlink.
NOTE
Pegging
• Always pegged for the MSs with multislot class 8, 10, 11, 12, or 14 through 29.
multislot is one of class 8, 10, 11, 12, or 14 through 29.
EGPRS multislot is one of class 8, 10, 11, 12, or 14 through 29.
Multislot classes 14–29 is treated as multislot class 10.
13-80 68P02901W56-T
Jan 2010
Analysis
Reference None
Basis Cell
Type Extra large counter array
68P02901W56-T 13-81
Jan 2010
DL_RLC_ACK_NEW_BLKS Chapter 13: PCU statistics
DL_RLC_ACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledged
mode blocks sent for the first time by the PCU over the cell.
Table 13-32 Bin ranges for DL_RLC_ACK_NEW_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
13-82 68P02901W56-T
Jan 2010
Table 13-33 Pegging method for DL_RLC_ACK_NEW_BLKS statistic

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Pegging
This statistic counts the new RLC acknowledged radio blocks that are sent on a cell. The RLC
radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Basis Cell
Type Counter array
68P02901W56-T 13-83
Jan 2010
DL_RLC_DDTR_BLKS Chapter 13: PCU statistics
DL_RLC_DDTR_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_DDTR_BLKS statistic measures the total number of RLC blocks with dummy
LLCs sent in CS1 or MCS1 during the delayed downlink TBF release period over the cell.
The RLC radio blocks are split into two coding schemes, as shown in Table 13-34.
Table 13-34 Bin ranges for DL_RLC_DDTR_BLKS
Bin Range
0 CS-1
1 MCS-1
Pegging
This statistic counts the RLC radio blocks with dummy LLCs (delayed downlink TBF) blocks that
are sent on a cell. The RLC radio blocks are counted per coding scheme, therefore pegging
the appropriate bin. Note that the radio blocks with LLC dummies are always sent using either
CS1 or MCS1.
Analysis
Reference None
Basis Cell
Type Counter array
13-84 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RLC_NACK_BLKS
DL_RLC_NACK_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_NACK_BLKS statistic measures the total number of RLC blocks sent due to an
explicit NACK from the MS.
Table 13-35 Bin ranges for DL_RLC_NACK_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-85
Jan 2010
Table 13-36 Pegging method for DL_RLC_NACK_BLKS statistic

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Pegging
This statistic counts the RLC blocks that are sent due to an explicit NACK from the MS. The RLC
Analysis
Reference None
Basis Cell
Type Counter array
13-86 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RLC_RETX_BLKS
DL_RLC_RETX_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_RETX_BLKS statistic measures the total number of preemptive retransmissions

(or ack pending blocks and acknowledged retransmissions) sent by the PCU over the cell.
Table 13-37 Bin ranges for DL_RLC_RETX_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-87
Jan 2010
Table 13-38 Pegging method for DL_RLC_RETX_BLKS statistic

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Pegging
This statistic counts the RLC ack pending (or preemptive transmissions) radio blocks that
are sent on a cell. The RLC radio blocks are counted per coding scheme, therefore pegging
the appropriate bin.
Analysis
Reference None
Basis Cell
Type Counter array
13-88 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RLC_STALLED_BLKS
DL_RLC_STALLED_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_STALLED_BLKS statistic measures the total number of RLC blocks retransmitted
due to an RLC window stall. That is, if the window is stalled, all DL radio blocks sent during
this period are pegged as stalled. Stalled blocks supersede other types of transmissions of
NEW, NACK, and RETX blocks. For example, a NACK data block sent during a stalled window
condition is treated as a stalled block and gets pegged as such.
Table 13-39 Bin ranges for DL_RLC_STALLED_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-89
Jan 2010
Table 13-40 Pegging method for DL_RLC_STALLED_BLKS statistic

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Pegging
This statistic counts the RLC blocks sent due to any RLC window stall in the cell. The RLC radio
blocks are counted per coding scheme therefore pegging the appropriate bin.
Analysis
Reference None
Basis Cell
Type Counter array
13-90 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RLC_UNACK_NEW_BLKS
DL_RLC_UNACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_UNACK_NEW_BLKS statistic measures the total number of new RLC

unacknowledge mode blocks sent for the first time by the PCU over the cell.
Table 13-41 Bin ranges for DL_RLC_UNACK_NEW_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
68P02901W56-T 13-91
Jan 2010
Table 13-42 Pegging method for DL_RLC_UNACK_NEW_BLKS statistic

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Pegging
This statistic counts the new RLC unacknowledged radio blocks that are sent on a cell. The RLC
Analysis
Reference None
Basis Cell
Type Counter array
13-92 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TBF_FAILURE_RATE
DL_TBF_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_FAILURE_RATE key statistic calculates the rate of abnormally released downlink
TBFs.
Formula
(AIR− DL− TBF− FAILURES − AIR− DL− TBF− FAILURES [bin0])

DL− TBF− FAILURE− RATE = ∗ 100
DL− PDTCH− SEIZURE in OMC-R
Pegging
Change to peg establish bin when downlink TBF is abnormally released due to
PRM_DL_PCTA_CA_ATTEMPTS_EXCEEDED in BSS.
Analysis

Basis Cell.
Type Percentage.
Raw statistics AIR_DL_TBF_FAILURES.
DL_PDTCH_SEIZURE.
68P02901W56-T 13-93
Jan 2010
DL_TBF_INTERLEAVING_ACTIVITY Chapter 13: PCU statistics
DL_TBF_INTERLEAVING_ACTIVITY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_INTERLEAVING_ACTIVITY key statistic provides information about interleaving

TBFs while transmitting in the downlink direction.
Formula
 
DL− T BF− T IM E− 1− T S+
 
 
 DL− T BF− T IM E− 2− T S ∗ 2+ 
  ∗ 0.02
 DL− T BF− T IM E− 3− T S ∗ 3+ 
 
DL− T BF− T IM E− 4− T S ∗ 4
DL− TBF− INTERLEAVENING− ACTIVITY =
DL− BU SY− P DT CH− M EAN ∗
IN T ERV AL ∗ 3600
Analysis

Basis Cell.
Type Average number of TBFs per PDTCH.
DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
DL_BUSY_PDTCH_MEAN.
INTERVAL.
13-94 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TBF_TIME_1_TS
DL_TBF_TIME_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_TIME_1_TS statistic counts the cumulative length in number of 20 ms radio block
periods of all downlink TBFs for MSs that support a maximum of 1 TS in the downlink direction.
The DL_TBF_TIME_1_TS statistic can be used with DL_RADIO_BLKS_1_TS to calculate the

effective downlink throughput per terminal type for MS multislot classes supporting one
PDTCH in downlink.
Pegging
This statistic measures the time of all the TBFs in the downlink for MSs that support a maximum
of 1 TS in the downlink direction as follows:
• Always pegged for MSs with multislot class 1.
• If a GPRS TBF is assigned to the MS and its GPRS multislot is class 1.
• If an EGPRS mode TBF is assigned to the MS and the EGPRS multislot is class 1.
At the end of the statistical interval this statistic provides a cumulative value of all the DL TBF
times for MSs supporting a maximum of 1 TS. The TBF time is measured from the TBF set-up
time to the time the MS acknowledges the full TBF. The TBF time includes all the delayed
downlink TBF release phases except the last one to accurately reflect the perceived throughput.
Analysis
Reference None
Basis Cell
Type Counter
68P02901W56-T 13-95
Jan 2010
DL_TBF_TIME_2_TS Chapter 13: PCU statistics
DL_TBF_TIME_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

effective downlink throughput per terminal type for MS multislot classes supporting two
PDTCHs in downlink.
Pegging
• Always pegged for MSs with multislot class 2, 3 or 5.
• If a GPRS TBF is assigned to the MS and its GPRS multislot is class 2, 3 or 5.
• If an EGPRS mode TBF is assigned to the MS and the EGPRS multislot is class 2, 3 or 5.
Analysis
Reference None
Basis Cell
Type Counter
13-96 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TBF_TIME_3_TS
DL_TBF_TIME_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

effective downlink throughput per terminal type for MS multislot classes supporting three
PDTCHs in downlink.
Pegging
• Always pegged for MSs with multislot class 4, 6, 7, 9, or 13.
• If a GPRS TBF is assigned to the MS and its GPRS multislot is class 4, 6, 7, 9, or 13.
• If an EGPRS mode TBF is assigned to the MS and the EGPRS multislot is class 4, 6, 7,
9, or 13.
Analysis
Reference None
Basis Cell
Type Counter
68P02901W56-T 13-97
Jan 2010
DL_TBF_TIME_4_TS Chapter 13: PCU statistics
DL_TBF_TIME_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_TIME_4_TS statistic counts the cumulative length in number of 20 ms radio

block periods of all the downlink TBFs for the MSs that support a maximum of 4 TS in the
downlink direction.
The DL_TBF_TIME_4_TS statistic can be used in conjunction with DL_RADIO_BLKS_4_TS

to calculate the effective downlink throughput per terminal type for the MS multislot classes
supporting four PDTCHs in the downlink.
Pegging
• Always pegged for the MSs with multislot class 8, 10, 11, 12, or 14 through 29.
• If a GPRS TBF is assigned to the MS and its GPRS multislot is one of class 8, 10, 11,
12, or 14 through 29.
• If an EGPRS mode TBF is assigned to the MS and the EGPRS multislot is one of class
8, 10, 11, 12, or 14 through 29.
times for the MSs supporting a maximum of 4 TS. The TBF time is measured from the TBF
set-up time to the time the MS acknowledges the full TBF. The TBF time includes all the delayed
Analysis
Reference None
Basis Cell
Type Counter
13-98 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_THROUGHPUT_TERMINAL_1_TS
DL_THROUGHPUT_TERMINAL_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_THROUGHPUT_TERMINAL_1_TS key statistic calculates the TBF throughput

performance for MSs that can support a maximum of 1 TS in the downlink direction.
Formula
 
DL− RADIO− BLKS− 1− TS− CS− 1∗22+DL− RADIO− BLKS− 1− TS− CS− 2∗33+
 
 DL− RADIO− BLKS− 1− TS− CS− 3∗39+DL− RADIO− BLKS− 1− TS− CS− 24∗53+ 
 
 
 DL− RADIO− BLKS− 1− TS− MCS− 1∗22+DL− RADIO− BLKS− 1− TS− MCS− 2∗28+ 
 
 DL RADIO BLKS 1 TS MCS 3∗37+DL RADIO BLKS 1 TS MCS 4∗44+ 
 − − − − − − − − − − − −  ∗ 0.8
 
 − − − − − − − − − − − − 
 
 
DL− THROUGHPUT− DL− RADIO− BLKS− 1− TS− MCS− 9∗148
=
TERMINAL− 1− TS DL− TBF− TIME− 1− TS∗0.02
Analysis
Basis Per terminal.

Type kilobytes/second.
Raw statistics Bins 0 to 12 of DL_RADIO_BLKS_1_TS.
DL_TBF_TIME_1_TS.
68P02901W56-T 13-99
Jan 2010
DL_THROUGHPUT_TERMINAL_2_TS Chapter 13: PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
 
 
 
 
 
 − − − − − − − − − − − −  ∗ 0.8
 
 − − − − − − − − − − − − 
 
 
=
Analysis
Basis Per terminal.

DL_TBF_TIME_2_TS.
13-100 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_THROUGHPUT_TERMINAL_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
 
 
 
 
 
 − − − − − − − − − − − −  ∗ 0.8
 
 − − − − − − − − − − − − 
 
 
=
Analysis
Basis Per terminal.

DL_TBF_TIME_3_TS.
68P02901W56-T 13-101
Jan 2010
DL_THROUGHPUT_TERMINAL_4_TS Chapter 13: PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
 
 
 
 
 
 − − − − − − − − − − − −  ∗ 0.8
 
 − − − − − − − − − − − − 
 
 
=
Analysis
Basis Per terminal.

Raw statistics Bins 0–12 of DL_RADIO_BLKS_4_TS.
DL_TBF_TIME_4_TS.
13-102 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application EGPRS_64K_CHANNELS_SWITCHED
EGPRS_64K_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_64K_CHANNELS_SWITCHED statistic counts the number of times the 64 kbps

EGPRS time slots are used for circuit-switched calls in a statistical reporting period on a
per-cell basis.
NOTE
The EGPRS_64K_CHANNELS_SWITCHED statistic value may increase as the
additional switchable PDTCH is allocated for GPRS congested cell.
Pegging
This statistic pegs when a 64 kbps EGPRS timeslot is successfully switched for a point-to-point
call as defined in Table 13-43.
Table 13-43 EGPRS_64K_CHANNELS_SWITCHED bins

0 CS The number of PDTCH of this type to be switched for point-to-point calls.
Analysis
Reference None
Network planning.
Basis Cell
Type Counter array.
68P02901W56-T 13-103
Jan 2010
EGPRS_64K_NOT_AVAIL Chapter 13: PCU statistics
EGPRS_64K_NOT_AVAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_64K_NOT_AVAIL statistic tracks the number of times that a TBF would have been
able to use EGPRS coding schemes due to good radio conditions in the cell but could not do
so because the MS's timeslot assignment was not 64k TRAU.
Pegging
This statistic pegs when an EGPRS capable MS is allocated GPRS resources. This statistic is
pegged when 64k TRAU is disabled or when the MS is allocated GPRS time slots and the radio
conditions would allow usage of EGPRS coding schemes.
Analysis
Reference None
Usage If CS-3,4 is disabled, it counts how often CS-3,4 would have been used resulting
in increased end user throughput.
Basis Cell
Type Counter
13-104 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application EGPRS_AVAIL_PDTCH
EGPRS_AVAIL_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_AVAIL_PDTCH statistic measures the mean and MAX number of available EGPRS
Packet Data Traffic CHannels (PDTCH).
NOTE
The available PDTCH number may increase as the additional switchable PDTCH is
This statistic is obtained by maintaining the current and the total number of available EGPRS
PDTCHs and the amount of time each is available over the statistical period. The PDTCH is
available when its administrative state is unlocked or shutting down and the operational state is
enabled. It is unavailable when its administrative state changes to locked or the operational
state changes to disabled. The available EGPRS PDTCH counts both reserved PDTCHs and
switchable PDTCHs that are configured for use as an EGPRS PDTCHs.
Pegging
This statistic pegs whenever there is a change in the channel configuration for any channel in
the cell (if the number of EGPRS PDTCHs has not changed within the current pegging interval,
it is pegged with the same value as before).
NOTE
This statistic counts the number of time slots available for GPRS. It treats
PBCCH/PCCCH TS the same as regular PDTCH TS, which means that each TS is
counted as 1, even though 4 MS can share a regular TS, while a PBCCH/PCCCH
TS can only be shared by 2 MS.
Analysis
Reference 4.60, 5.08

Basis Cell
Type Gauge
68P02901W56-T 13-105
Jan 2010
EGPRS_DL_ASGN_PCCCH Chapter 13: PCU statistics
EGPRS_DL_ASGN_PCCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_DL_ASGN_PCCCH statistic counts the total number of EGPRS packet downlink
assignments sent on the PCCCH.
Pegging
This statistic pegs whenever an EGPRS packet downlink assignment is sent on PCCCH.
Analysis
Reference None
Basis Cell
Type Counter
13-106 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application G_RACH_UNSVCD_BTS
G_RACH_UNSVCD_BTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The G_RACH_UNSVCD_BTS statistic tracks the total number of uplink GPRS RACH requests
unserviced by the BTS.
Pegging
This statistic is pegged whenever a GPRS RACH request is unserviced by the BTS.
Table 13-44 G_RACH_UNSVCD_BTS bins

0 RSL bandwidth This bin is pegged when the rate of received packet channel
limitation request messages per second exceeds the threshold on the RSL
link, set by percent_traf_cs.
1 No PRR block This bin is pegged while there are no reserved PRR blocks left.
2 AGCH discard This bin can be used to check how many AGCH discards occur
compared to the GPRS_ACCESS_PER_AGCH.
NOTE
Analysis
This statistic can be used for the trend analysis of the BTS.
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 13-107
Jan 2010
GBL_AVAILABILITY Chapter 13: PCU statistics
GBL_AVAILABILITY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_AVAILABILITY statistic measures the availability for a particular Gb link during
a statistical interval.
Formula
(GBL− UNAVAILABLE)
GBL− AVAILABILITY = 100 −
(INTERVAL ∗ 36000)
Analysis

Congestion.
Basis GBL
Type Percentage.
Raw Statistics GBL_UNAVAILABLE.
INTERVAL.
13-108 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GBL_DL_DATA_THRPUT
GBL_DL_DATA_THRPUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_DL_DATA_THRPUT statistic reports the quantity of data transmitted on the downlink
of the Gb link (GBL) during a given time interval. The PCU calculates the instantaneous
throughput in kilobytes per second by dividing the quantity of data transmitted by the time
interval given by the parameter gbl_thrput_period.
Pegging
This statistic is pegged by computing a moving average in kilobytes per second of the
instantaneous throughput samples. The number of samples used for the computation is given by
the parameter num_gbl_dl_thrput_samples.
Analysis
This statistic can be used for the trend analysis of the average downlink throughput of the GBL.
This statistic is stored in the following columns in the gbl_statistics table:

• dl_datathrput_mean.
• dl_datathrput_MAX.
Reference None.
Congestion.
Basis GBL.
Type Gauge.
68P02901W56-T 13-109
Jan 2010
GBL_DL_DATA_THRPUT_HIST Chapter 13: PCU statistics
GBL_DL_DATA_THRPUT_HIST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_DL_DATA_THRPUT_HIST statistic reports the quantity of data transmitted on the

downlink of the GBL during a given time interval.
The PCU calculates the instantaneous throughput in kilobytes per second by dividing the
quantity of data transmitted by the time interval given by the parameter gbl_thrput_period.
There are ten bins in the array. The available ranges are shown in Table 13-45.
Table 13-45 GBL_DL_DATA_THRPUT_HIST bins
Bin Range
0 0 - 30
1 31 - 70
2 71 - 110
3 111 - 140
4 141 - 170
5 171 - 230
6 231 - 300
7 301 - 400
8 401 - 500
9 501 - 600
Pegging
The GBL_DL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samples

in ten bins. See Table 13-45 for the ranges.
13-110 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for the trend analysis of GBL downlink throughput.

• dl_thrput_min.
• dl_thrput_mean.
• dl_thrput_MAX.
Reference None.
Congestion.
Quality of service monitoring: Network accessibility.
Basis GBL.
Type Normal Distribution.
68P02901W56-T 13-111
Jan 2010
GBL_DL_PKT_COUNT Chapter 13: PCU statistics
GBL_DL_PKT_COUNT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26638}
Description
The GBL_DL_PKT_COUNT statistic reports the number of packets transmitted on the downlink
of the GBL when the gb_mode is set to Static IP.
Pegging
This statistic counts the number of NS PDUs received on the downlink of the GBL during a given
time interval when the gb_mode is set to Static IP.
Analysis
Device Type GBL

Statistic Type Counter
Summation Type SUM, SUM, SUM
Unit Packet
Alarmable No
Manageable(Enable/Disable) Yes
13-112 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GBL_DL_PKT_INV_NSVC
GBL_DL_PKT_INV_NSVC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26638}
Description
The GBL_DL_PKT_INV_NSVC statistic reports the number of downlink NS PDUs received from
the invalid NSVC (SGSN IP address is invalid or UDP port is invalid) when the gb_mode is
set to Static IP.
Pegging
This statistic counts the number of NS PDUs received from the invalid NSVC (SGSN IP address
is invalid or UDP port is invalid) on the downlink of the GBL during a given time interval when
the gb_mode is set to Static IP.
Analysis
Device Type GBL

Unit Packet
Manageable (Enable/Disable) Yes
68P02901W56-T 13-113
Jan 2010
GBL_FLOW_CTRL_SENT Chapter 13: PCU statistics
GBL_FLOW_CTRL_SENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_FLOW_CTRL_SENT tracks the number of flow control messages sent by the BSS
to the Serving GPRS Support Node (SGSN).
Each cell has a buffer that holds downlink data. When a cell buffer reaches a predetermined
threshold, a flow control message is sent to the SGSN.
Flow control is performed to match the flow of the downlink data with air throughput.
Pegging
This statistic pegs the number of flow control messages sent by the BSS and is pegged every
time a flow control message is sent.
Analysis
This statistic can be used for trend analysis of the number of flow control messages sent by the
BSS.
Reference None.
Congestion.
Basis Cell.
Type Counter.
13-114 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GBL_PAGING_REQS
GBL_PAGING_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_PAGING_REQS statistic tracks the number of the paging requests received at the
GBL.
Pegging
This statistic pegs each time an MS page request is received at the GBL.
Analysis
This statistic can be used for the trend analysis of the number of circuit switched and packet
switched pages received by the BSS from the SGSN.
Reference None.
Congestion.
Basis PCU.
Type Counter.
68P02901W56-T 13-115
Jan 2010
GBL_RESOUR_DIST_IND Chapter 13: PCU statistics
GBL_RESOUR_DIST_IND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26638}
Description
The GBL_RESOUR_DIST_IND statistic reports the number of resource distribution requests

received from the SGSN at the GBL when the gb_mode is set to Static IP.
Pegging
This statistic counts the number of resource distribution requests received from the SGSN at
the GBL during a given time interval when the gb_mode is set to Static IP.
Analysis
Device Type GBL

Unit Request
Alarmable No
Manageable (Enable/Disable) Yes
13-116 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GBL_UL_DATA_THRPUT
GBL_UL_DATA_THRPUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_UL_DATA_THRPUT statistic reports the quantity of data transmitted on the uplink
of the Gb link (GBL) during a given time interval. The PCU calculates the instantaneous
throughput in kilobytes per second by dividing the quantity of data transmitted by the time
interval given by the parameter gbl_thrput_period.
Pegging
This statistic is pegged by computing a moving average in kilobytes per second of the
instantaneous throughput samples. The number of samples used for the computation is given by
the parameter num_gbl_ul_thrput_samples.
Analysis
This statistic can be used for the trend analysis of the average uplink throughput of the GBL.

• ul_datathrput_mean.
• ul_datathrput_MAX.
Reference None.
Congestion.
Basis GBL.
Type Gauge.
68P02901W56-T 13-117
Jan 2010
GBL_UL_DATA_THRPUT_HIST Chapter 13: PCU statistics
GBL_UL_DATA_THRPUT_HIST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_UL_DATA_THRPUT_HIST statistic reports the quantity of data transmitted on the

uplink of the GBL during a given time interval.
The PCU calculates the instantaneous throughput in kilobytes per second by dividing the
quantity of data transmitted by the time interval given by the parameter gbl_thrput_period.
Pegging
The GBL_UL_DATA_THRPUT_HIST statistic pegs the instantaneous throughput samples in

ten bins. The ranges are shown in Table 13-46.
Table 13-46 GBL_UL_DATA_THRPUT_HIST bins
Bin Range
0 0 - 30
1 31 - 70
2 71 - 110
3 111 - 140
4 141 - 170
5 171 - 230
6 231 - 300
7 301 - 400
8 401 - 500
9 501 - 600
13-118 68P02901W56-T
Jan 2010
Analysis
This statistic can be used for the trend analysis of GBL uplink throughput.

• ul_thrput_min.
• ul_thrput_mean.
• ul_thrput_MAX.
Reference None.
Congestion.
Basis GBL.
68P02901W56-T 13-119
Jan 2010
GBL_UL_PKT_COUNT Chapter 13: PCU statistics
GBL_UL_PKT_COUNT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{26638}
Description
The GBL_UL_PKT_COUNT statistic reports the number of packets transmitted on the uplink of
the GBL when the gb_mode is set to Static IP.
Pegging
This statistic counts the number of NS PDUs transmitted on the uplink of the GBL during a given
time interval when the gb_mode is set to Static IP.
Analysis
Device Type GBL

Unit Packet
Alarmable No
Manageable Yes
(Enable/Disable)
13-120 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GBL_UNAVAILABLE
GBL_UNAVAILABLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_UNAVAILABLE statistic tracks the amount of time in milliseconds that the GBL is
out-of-service.
Pegging
The timer for this statistic is started when the GBL transitions to a state which is not B-U, that
is, when the GBL goes out-of-service. The timer is stopped when the GBL is in the B-U state,
that is, when the GBL returns to service.
Analysis
This statistic can be used for trend analysis of the duration of GBL outages, including those
Reference None.
Usage Network accessibility.
Fault finding.
Basis GBL.
Type Duration.
68P02901W56-T 13-121
Jan 2010
GPRS_32K_CHANNELS_SWITCHED Chapter 13: PCU statistics
GPRS_32K_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic keeps a count of the number of times that CS-3,4 capable GPRS time slots (32k
TRAU) are used for circuit-switched calls in a statistics reporting period on a per-cell basis.
NOTE
The GPRS_32K_CHANNELS_SWITCHED statistic value may increase as the
additional switchable PDTCH is allocated for GPRS congested cell.
Pegging
This statistic pegs when a 32 kbps GPRS timeslot is successfully switched to a circuit switched
call as defined in Table 13-47.
Table 13-47 GPRS_32K_CHANNELS_SWITCHED bins

Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
13-122 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_32K_DL_NOT_AVAIL
GPRS_32K_DL_NOT_AVAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_32K_DL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRS time
slots would have been switched to CS-3,4 due to good radio conditions in the cell, but could not
do so because the MS's timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the MS is allocated 16k TRAU time slots
and the radio conditions would allow usage of CS-3,4.
Analysis
Reference None.
Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would have been used
resulting in increased end user throughput.
Basis Cell.
Type Counter.
68P02901W56-T 13-123
Jan 2010
GPRS_32K_UL_NOT_AVAIL Chapter 13: PCU statistics
GPRS_32K_UL_NOT_AVAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRS time
slots would have been switched to CS-3,4 due to good radio conditions in the cell, but could not
do so because the MS's timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the MS is allocated 16k TRAU time slots
and the radio conditions would allow usage of CS-3,4.
Analysis
Reference None.
Usage If CS-3,4 is disabled, it is counted how often CS-3,4 would have been used
resulting in increased end user throughput.
Basis Cell.
Type Counter.
13-124 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_ACCESS_PER_AGCH
GPRS_ACCESS_PER_AGCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_ACCESS_PER_AGCH statistic tracks the number of Immediate Assignment messages

sent on the Access Grant Channel (AGCH) of a cell for packet data service.
The air interface message on the AGCH for packet immediate assignment and immediate
assignment reject contains only one MS.
Access Grants for more than one MS may be contained in one Access Grant message (Extended
Immediate Assignment). An Access Grant for more than one MS is pegged only once. This
count includes Immediate Assignment, Immediate Extended, and Immediate Assignment Reject
messages sent on the AGCH of a cell.
Pegging
This statistic is pegged when an access grant message is sent on the AGCH on a cell for
packet data service.
Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the
AGCH of a cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 13-125
Jan 2010
GPRS_ACCESS_PER_RACH Chapter 13: PCU statistics
GPRS_ACCESS_PER_RACH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_ACCESS_PER_RACH statistic tracks the number of packet switched Channel

Request messages successfully received on the Random Access CHannel (RACH) for GPRS
purposes.
Pegging
This statistic pegs when a packet switched Channel Request message is sent on the Random
Access CHannel (RACH) of a cell.
NOTE
Analysis
This statistic can be used for trend analysis of the Immediate Assignment messages sent on
the RACH of a cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.
13-126 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_AVAIL_PDTCH
GPRS_AVAIL_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named AVAILABLE_PDTCH.
Description
This statistic measures the mean and maximum number of available Packet Data Traffic
CHannels (PDTCH).
NOTE
The available PDTCH number may increase as the additional switchable PDTCH is
This statistic considers a PBCCH/PCCCH timeslot as a PDTCH. Therefore, these are recorded by
the statistic in its total number of available channels.
This statistic is obtained by maintaining the current and the total number of available PDTCH
and the amount of time each PDTCH is available over the statistical period. The corresponding
mean and maximum number of PDTCH are then computed. The PDTCH is available when its
administrative state is unlocked or shutting down and the operational state is enabled. It is
disabled. The available number of PDTCH is then incremented or decremented when there
is a change in PDTCH states as described above. The available PDTCH counts both reserved
PDTCHs and switchable PDTCHs that are configured as PDTCHs and not as TCHs.
The number of PDTCH = Number of switchable PDTCHs (configured as PDTCHs) + Number

of reserved PDTCHs
Pegging
the cell (if the number of PDTCHs has not changed within the current pegging interval, it is
pegged with the same value as before).
NOTE
This statistic counts the number of timeslots available for GPRS. It treats
PBCCH/PCCCH TS the same as regular PDTCH TS, which means that each TS is
counted as 1, even though 4 MS can share a regular TS, while a PBCCH/PCCCH
TS can be shared only by 2 MS.
68P02901W56-T 13-127
Jan 2010
Analysis
This statistic can be used for trend analysis of PDTCH availability.
By comparing the number of available PDTCHs to the total number of PDTCHs in a cell, a
percentage of GPRS availability in a cell can be calculated. An analysis of the utilization
information can be used to determine the requirement for additional resources before the
problems occur.

Usage Congestion.
Network planning.
Key statistic:
BSS_AVAILABILITY.
Basis Cell.
Type Gauge.
13-128 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_CELL_CONGESTION
GPRS_CELL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_CELL_CONGESTION statistic indicates the number of times, measured each 6

second interval, that the percentage of GPRS timeslot resources in use falls into the given
range. A high congestion rate indicates the low possibility for the system to establish new TBFs.
The distribution information of this statistic illustrates the average packet traffic situation, and
hence can be used to optimize the cell planning and resource allocation. Each bin represents a
percentage congestion range, with high value of the range indicated in the bin name.
NOTE
This statistic also includes information of the EGPRS system should the EGPRS
feature be enabled.
Pegging
This statistic pegs with the higher value of the Uplink/Downlink congestion.
Each bin represents different congestion range as shown below:
Table 13-48 Bin ranges for GPRS_CELL_CONGESTION
Bin Bin name Range

0 GPRS_CONGESTION_25 ≥ 0%, < 25%
12 GPRS_CONGESTION_85≥≥ ≥ 80%, < 85%
Continued
68P02901W56-T 13-129
Jan 2010
Table 13-48 Bin ranges for GPRS_CELL_CONGESTION (Continued)

Bin Bin name Range
15 GPRS_CONGESTION_100 ≥ 95%, ≤ 100%
One unit represents a period of time when the congestion rate falls in the specific range at the
end of a given 6 second duration. The range is 0 to 600.
Analysis
Reference None.
Usage Cell planning.
Resource allocation.
Basis Cell.
Type Counter array.
13-130 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_CELL_RESELECT_FAIL
GPRS_CELL_RESELECT_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_CELL_RESELECT_FAIL statistic tracks the number of Network Controlled cell

reselect failures from the originating cell. Retries are not counted.
Pegging
This statistic pegs when a Packet Cell Change Failure message is sent by an MS.
NOTE
Analysis
This statistic can be used for the analysis of Network Controlled cell reselect failures from
an originating cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-T 13-131
Jan 2010
GPRS_CHANNELS_SWITCHED Chapter 13: PCU statistics
GPRS_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic reports the number of times a 16 kbps Packet Data Traffic Channel (PDTCH) has
been switched to a circuit switched Traffic Channel (TCH).
Pegging
This statistic pegs when a 16 kbps PDTCH is switched to a circuit switched TCH as defined
in Table 13-49.
Table 13-49 GPRS_CHANNELS_SWITCHED bins

Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
13-132 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_DL_ASGN_PCCCH
GPRS_DL_ASGN_PCCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of packet downlink assignment messages received on the
Packet Common Control Channel (PCCCH).
Pegging
This statistic pegs once per packet downlink assignment on the PCCCH.
Analysis

Basis Cell.
Type Counter.
68P02901W56-T 13-133
Jan 2010
GPRS_PAGING_OVERFLOW_RATE_PCH Chapter 13: PCU statistics
GPRS_PAGING_OVERFLOW_RATE_PCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PAGING_OVERFLOW_RATE_PCH key statistic provides the rate of PS paging

messages, which get discarded from the queue due to queue overflow before they get
transmitted.
Formula
GPRS− PAGING− PCH− Q− PAGE− DISCARD− PS ∗ 100

=
OVERFLOW− RATE− PCH ACCESS− PER− PCH− PS
Analysis
Basis Cell.
Type Percentage.
Raw statistics PCH_Q_PAGE_DISCARD_PS.
ACCESS_PER_PCH_PS.
13-134 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_PAGING_OVERFLOW_RATE_PPCH
GPRS_PAGING_OVERFLOW_RATE_PPCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PAGING_OVERFLOW_RATE_PPCH key statistic provides the rate of PS paging

transmitted.
Formula
GPRS− PAGING− PPCH− Q− PAGE− DISCARD− PS ∗ 100

=
OVERFLOW− RATE− PPCH ACCESS− PER− PPCH− PS
Analysis
Basis Cell.
Type Percentage.
Raw statistics PPCH_Q_PAGE_DISCARD_PS.
ACCESS_PER_PPCH_PS.
68P02901W56-T 13-135
Jan 2010
GPRS_PCH_AGCH_Q_LENGTH Chapter 13: PCU statistics
GPRS_PCH_AGCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean Paging CHannel-Access Grant CHannel (PCH-AGCH) queue
length. This statistic is obtained by measuring the arithmetic mean of the number of all
messages waiting for transmission on the PCH-AGCH, for GPRS purpose. This measurement
is obtained once in every paging multi frame, taking the PCH-AGCH queue length and then
taking the arithmetic mean.
Pegging
reported.
NOTE
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.

Usage This statistic is used to assess the impact of GPRS messaging on the CCCH.
For example, the operator could use the statistic to monitor the growth of
GPRS in an area, and possibly replan paging parameters to account for an
increase in GPRS users on the network.
Basis Cell.
Type Gauge.
13-136 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_PPCH_PAGCH_Q_LENGTH
GPRS_PPCH_PAGCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean and MAX of the number of all messages waiting in the Packet
Paging Channel-Packet Access Grant Channel (PPCH-PAGCH) queue. This statistic is obtained
by measuring the arithmetic mean of the number of all messages waiting for transmission on
the PPCH-PAGCH. This measurement is obtained once in every paging multi frame, taking the
PPCH-PAGCH queue length and then taking the arithmetic mean.
Pegging
reported.
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PPCH-PAGCH queue.

Usage This statistic is used to assess the impact of GPRS messaging on the PPCH.
For example, the operator could use the statistic to monitor the growth of
GPRS in an area, and possibly replan paging parameters to account for an
increase in GPRS users on the network.
Basis Cell.
68P02901W56-T 13-137
Jan 2010
GPRS_PRR_BLK_USG Chapter 13: PCU statistics
GPRS_PRR_BLK_USG
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PRR_BLK_USG statistic tracks the mean, minimum, and maximum number of
PRR block usage.
the GPRS_PRR_BLK_USG statistic are shown in Table 13-50.
Table 13-50 Default bin ranges for GPRS_PRR_BLK_USG
Bin Range
0 0 to 2
1 3 to 5
2 6 to 10
3 11 to 20
4 21 to 40
5 41 to 60
6 61 to 80
7 81 to 100
8 101 to 125
9 126 to 160
Pegging
This statistic is measured by obtaining the PRR block usage at predefined interval:
approximately one second (four multiframes) and updating the appropriate bin. At the end of the
report of the statistical interval, the mean, minimum, and maximum PRR block usage is reported.
NOTE
13-138 68P02901W56-T
Jan 2010
Analysis
Reference None.
Basis Cell.
68P02901W56-T 13-139
Jan 2010
GPRS_RACH_ARRIVAL Chapter 13: PCU statistics
GPRS_RACH_ARRIVAL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_RACH_ARRIVAL statistic tracks the mean, minimum, and maximum number of
GPRS RACH request arrivals over CCCH.
the GPRS_RACH_ARRIVAL statistic are shown in Table 13-51.
Table 13-51 Default bin ranges for GPRS_RACH_ARRIVAL
Bin Range
0 0 to 2
1 3 to 5
2 6 to 10
3 11 to 20
4 21 to 40
5 41 to 60
6 61 to 80
7 81 to 100
8 101 to 125
9 126 to 160
Pegging
This statistic is measured by sampling the GPRS RACH over CCCH at a predefined interval:
approximately one second (four multiframes). The total GPRS RACH requests over CCCH
during the time is obtained and the appropriate bin is updated. At the end of the report of the
statistical interval, the mean, minimum, and maximum PRR block usage is reported.
NOTE
13-140 68P02901W56-T
Jan 2010
Analysis
Reference None.
Basis Cell.
68P02901W56-T 13-141
Jan 2010
IDLE_PDTCH_INTF_BAND0 Chapter 13: PCU statistics
IDLE_PDTCH_INTF_BAND0
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IDLE_PDTCH_INTF_BAND0 statistic tracks the maximum and mean number of idle uplink
Packet Data Traffic CHannels (PDTCHs) for interference band 0. An idle PDTCH falls into band
0 if its average interference band is less than the value of the element interfer_bands, 0.
NOTE
Idle PDTCHs are allocated to five interference bands. Each band has an associated
statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can be
allocated for a request. An idle PDTCH falls into band 0 if its idle interference level is less than
the value of the elements interfer_bands 0. The mean and MAX are calculated from the samples.
Analysis
This statistic can be used for trend analysis of idle packet data traffic channels.

Fault finding.
Basis Cell.
Type Gauge.
13-142 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IDLE_PDTCH_INTF_BAND1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-T 13-143
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.
13-144 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IDLE_PDTCH_INTF_BAND3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-T 13-145
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
NOTE
Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.
13-146 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IMM_ASSGN_CAUSE
IMM_ASSGN_CAUSE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the successful immediate assignment procedures, per cause. This
statistic is obtained by measuring the number of IMMEDIATE ASSIGN COMMAND messages
transmitted, per cause. This message contains either an IMMEDIATE ASSIGNMENT message
or IMMEDIATE ASSIGNMENT EXTENDED message. If an IMMEDIATE ASSIGNMENT
EXTENDED message is transmitted, the counter is incremented by two, because it contains
assignment information for two MSs otherwise the counter is incremented by one. The
associated bins, identifiers, and establishment causes are defined in Table 13-52.
Table 13-52 IMM_ASSGN_CAUSE bins

0 orig_call Originating call.
1 emer_call Emergency call.
2 call_re_estb Call re-establishment.
3 loc_upd Location updating.
4 page_resp Paging response.
5 ul_pack_access_gprs GPRS - uplink packet access.
6 dl_pack_access_gprs GPRS - downlink packet access.
7 ul_pack_access_egprs EGPRS uplink packet access
8 dl_pack_access_egprs EGPRS downlink packet access
Pegging
This statistic is pegged once for every time the BSS sends an Immediate Assignment (IA) for any
of the specified purposes over the air. IAs for other purposes are not pegged.
This statistic pegs the cause of each IMMEDIATE ASSIGN COMMAND message. If this message
contains an IMMEDIATE ASSIGNMENT message, the cause is pegged once. If this message
contains an IMMEDIATE ASSIGNMENT EXTENDED message, the cause is pegged twice.
68P02901W56-T 13-147
Jan 2010
Analysis
It represents the total number of IAs pegged during the statistics interval, on a per-cause basis.

Usage The statistic is used for monitoring areas where lots of calls originate: the
operator may wish to charge more for calls made in these high-traffic zones.
It is also used for monitoring the number of calls undergoing
re-establishment. High numbers of calls undergoing re-establishment
means the RF coverage in an area may have a hole.
Comparing the uplink against downlink GPRS usage tells the operator how
to set the Beta value for a cell (Interleaving TBFs feature). This allows
for better throughput based upon the MS subscriber preferences in any
particular area.
Key statistic:
DL_TBF_SUCCESS_RATE.
Basis Cell.
Type Counter array.
13-148 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MCS1_USE_DL
MCS1_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MCS1_USE_DL key statistic provides usage figures for DL coding scheme CS-1 for EGPRS.
Formula
DL− RADIO− BLKS− 1− T S− M CS− 1+

DL− RADIO− BLKS− 4− T S− M CS− 1
MCS1− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 4.
68P02901W56-T 13-149
Jan 2010
MCS2_USE_DL Chapter 13: PCU statistics
MCS2_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MCS2_USE_DL key statistic provides usage figures of DL coding scheme CS-2 for EGPRS.
Formula

MCS2− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 5.
13-150 68P02901W56-T
Jan 2010
MCS3_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS3− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 6.
68P02901W56-T 13-151
Jan 2010
MCS4_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS4− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 7.
13-152 68P02901W56-T
Jan 2010
MCS5_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS5− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 8.
68P02901W56-T 13-153
Jan 2010
MCS6_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS6− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 9.
13-154 68P02901W56-T
Jan 2010
MCS7_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS7− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 10.
68P02901W56-T 13-155
Jan 2010
MCS8_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS8− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 11.
13-156 68P02901W56-T
Jan 2010
MCS9_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS9− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS,
DL_RADIO_BLKS_4_TS,
and their bin 12.
68P02901W56-T 13-157
Jan 2010
NO_PDTCH_AVAIL Chapter 13: PCU statistics
NO_PDTCH_AVAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NO_PDTCH_AVAIL statistic counts the number of times neither switchable nor reserved
PDTCHs are available.
Pegging
When the last PDTCH available is taken for a voice call, the count is incremented.
Analysis
Reference None.
Network accessibility.
Basis Cell.
Type Counter.
13-158 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NO_PDTCH_AVAIL_TIME
NO_PDTCH_AVAIL_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NO_PDTCH_AVAIL_TIME statistic measures the amount of time in millisecond during the
statistical collection period, the time interval between the start and stop of the timer, when
neither switchable nor reserved PDTCHs are available.
Pegging
When the last PDTCH available is taken for a voice call, the timer is started and stopped when
at least one PDTCH becomes available.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum acceptable
time that no PDTCHs are available for any of the start/stop time periods. If the specified
threshold is exceeded, the Total time all PDTCHs are unavailable - PM alarm is generated. Refer
to the manual Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
troubleshooting information.
Reference None.
Network accessibility.
Basis Cell.
Type Duration.
68P02901W56-T 13-159
Jan 2010
PACCH_PAGE_REQS Chapter 13: PCU statistics
PACCH_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PACCH_PAGE_REQS statistic represents the total number of circuit switched and packed
switched page requests sent by the PCU using PACCH channel when the MS is in packet
transfer mode.
Pegging
One unit represents one page request (CS or PS).
Analysis
Reference None.
Basis Cell.
Type Counter.
13-160 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PDU_DISCARD_FR
PDU_DISCARD_FR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PDU_DISCARD_FR statistic indicates the number of uplink and downlink PDU frames
discarded by Frame Relay firmware.
Pegging
Table 13-53 shows the description for each bin.
Table 13-53 Bin descriptions for PDU_DISCARD_FR
Bin Description
0 Downlink CRC errors.
1 Downlink HDLC errors (excluding CRC errors).
2 Uplink errors.
One unit represents one LLC frame. The range is 0 to 65,535. The maximum number of LLC
frames discarded during a one hour period cannot be accurately estimated. Use the uplimit of
a 16-bit unsigned integer.
Analysis
Reference None.
Basis GBL.
Type Counter array.
68P02901W56-T 13-161
Jan 2010
PDU_DISCARD_LLC Chapter 13: PCU statistics
PDU_DISCARD_LLC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PDU_DISCARD_LLC statistic represents the downlink LLC data frames discarded by PCU
due to different scenarios. There are three major causes:
• Buffer overflow.
• Cell reselection.
• Abnormal TBF release.
• Non-conformance to the negotiated QoS Profile.
Pegging
Table 13-54 shows the description for each bin.

Table 13-54 Bin descriptions for PDU_DISCARD_LLC

0 PDU_DSCRD_LLC_CELL Cell buffer overflow.
_BUF_OVRFLW
1 PDU_DSCRD_LLC_MS MS buffer overflow.
_BUF_OVRFLW
2 PDU_DSCRD_LLC_INAB LLC frames are discarded due to a failure
_MOVE_PKT to move the packets between different cells
within the same PCU. The failure to move
the packets could occur on account of any of
the following reasons:
• Disabling or inoperability of Seamless

Cell Reselection feature.
• MS has moved to a further cell before

the packets can be transferred to target
cell buffer.
• A move is detected after a flush

message is received from the SGSN.
• The target cell buffer is full.
Continued
13-162 68P02901W56-T
Jan 2010
Table 13-54 Bin descriptions for PDU_DISCARD_LLC (Continued)

3 PDU_DSCRD_LLC_OUT Discard data in target cell to avoid out of
_SEQ_LLC sequence LLC delivery.
4 PDU_DSCRD_LLC_RESEL LLC frames are discarded due to reception
_INAREA of a flush message from the SGSN, while the
MS moves to a cell within the same routing
area.
5 PDU_DSCRD_LLC_RESEL LLC frames discarded due to reception of a
_OUTAREA flush message from the SGSN, while the MS
moves to a cell in a different routing area.
6 PDU_DSCRD_LLC_ABNORM Discard data due to abnormal TBF release.
_TBFREL
7 PDU_DSCRD_LLC_PFC Discard data due to PFC rejection/deletion.
_REJECT_DELET
8 PDU_DSCRD_LLC Discard data due to non-conformance to the
_NONCON_QOS negotiated QoS Profile such as exceeding
GBR, exceeding MAX SDU size.
One unit represents one LLC frame. The range is 0 to 65,535. The maximum number of LLC
frames discarded during a one hour period cannot be accurately estimated. Use the uplimit of
a 16-bit unsigned integer.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-T 13-163
Jan 2010
PRP_LOAD Chapter 13: PCU statistics
PRP_LOAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the load of the Packet Resource Processor (PRP), PXP baseboard, or
PPROC for PRP processing. According to the capacity requirements, the BSS transfers data for
a certain number of timeslots out of all the timeslots in a PRP, PXP baseboard, or PPROC, as well
as process control messages for rest of timeslots in one 20 millisecond block period. The load of
the PRP, PXP baseboard, or PPROC for PRP processing is determined by measuring the number
of timeslots pending service for data transfers within a 20 millisecond block period.
The number of timeslots pending service increases by one whenever a timeslot is allocated to
the first UL or DL TBF and it decreases by one whenever all UL and DL TBFs on a timeslot are
released or re-allocated to other PRP boards. The statistic value also changes accordingly.
If the PRP load is 100% in prp_fanout_mode=1, it means that 30 timeslots are pending
service. Although the number of timeslots pending service can further increase, the total PRP
throughput does not increase. The maximum PRP load is 400%, which means that a total of
120 timeslots are pending service.
Table 13-55 shows the mapping between the number of timeslots pending service and the
PRP load.
The statistic is kept on a per DPROC basis. The mapping between the number of pending
timeslots service and the prp_load depending on the value of prp_fanout_mode and the
DPROC type are shown in Table 13-55 and Table 13-56.
Table 13-55 Mapping between timeslots pending service and PRP load
(prp_fanout_mode=1)
Number of timeslots pending service in a 20 msec block period

PRP Load
PRP PXP Baseboard PPROC
0-30 0–49 0–21 0-100
31-60 50–98 22–42 101-200
61-90 99–147 43–63 201-300
91-120 148–196 64–84 301-400
Table 13-56 Mapping between timeslots pending service and PRP load
(prp_fanout_mode=2)
Number of timeslots pending service in a 20 msec block period

PRP Load
PRP PXP Baseboard PPROC
0-48 0–98 0–42 0-100
NOTE
When prp_fanout_mode is set to 2, all the timeslots can be used to transfer data
blocks. prp_load should not exceed 100.
13-164 68P02901W56-T
Jan 2010
Table 13-57 shows the PRP load ranges for each bin of this statistic.
Table 13-57 PRP load range
Bin Min MAX

1 0 2
2 3 5
3 6 10
4 11 20
5 21 40
6 41 60
7 61 100
8 101 160
9 161 260
10 261 400
Pegging
This statistic pegs the appropriate bin every 20 millisecond based on the number of timeslots
pending service and the bin range values that the customer configured.
NOTE
Analysis
This statistic measures the load of the PRP, PXP baseboard, or PPROC for PRP processing. The
load of the PRP, PXP baseboard, or PPROC for PRP processing is determined by measuring the
number of pending timeslots service for data transfers within a 20 millisecond block period.
This statistic can be used for trend analysis of the network load on a PRP board. Each bin can be
analyzed to determine the number of occurrences the PRP had a certain percentage of load on it.
Reference None.
Congestion.
Basis
DPROC and PPROC.
68P02901W56-T 13-165
Jan 2010
PS_PAGE_REQS Chapter 13: PCU statistics
PS_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PS_PAGE_REQS statistic represents the total number of packet switched page requests
received by the PCU per GBL.
Pegging
One unit represents one PS page request.
Analysis
Reference None.
Basis GBL.
Type Counter.
13-166 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TBF_DL_ASGN_PACCH
TBF_DL_ASGN_PACCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TBF_DL_ASGN_PACCH statistic represents the total number of Packet Downlink

Assignments and Packet Timeslot Reconfigure sent by the PCU using PACCH channel to
establish new downlink TBF when the mobile is in packet transfer mode.
Pegging
One unit represents one PDA or one PTR.
Analysis
Reference None.
Usage Key statistic:
DL_TBF_SUCCESS_RATE.
Basis Cell.
Type Counter.
68P02901W56-T 13-167
Jan 2010
TBF_REL_PACCH_LOST Chapter 13: PCU statistics
TBF_REL_PACCH_LOST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TBF_REL_PACCH_LOST statistic represents the number of TBFs that are released when
its switchable PDCH is converted to TCH. Only those TBFs whose PACCH are lost due to the
switch are counted.
NOTE
The probability of TBF release due to PACCH lost may increase as the increment of
switchable PDTCH converted to TCH because both the additional switchable PDTCH
stolen by voice call and the de-allocation.
Pegging
One unit represents one TBF.
Analysis
Reference None.
Basis Cell.
Type Counter.
13-168 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TBF_SESSIONS
TBF_SESSIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TBF_SESSIONS statistic indicates the average and maximum ongoing TBFs at the end
of each six second duration on a PRP board.
Pegging
One unit represents one TBF session. The range is 0 to 120. The capacity is measured by the
number of MSs a PRP board can support (120).
Analysis
Reference None.
MEAN_TBF_SESSIONS.
Type Gauge.
68P02901W56-T 13-169
Jan 2010
UL_BLER_CS1 Chapter 13: PCU statistics
UL_BLER_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_BLER_CS1 statistic indicates the number of times, measured at statistical intervals,
the BLER of a particular carrier, when using coding scheme 1 to transmit in the uplink direction,
falls into the given range. Each bin represents a range of percentage BLER, with high value of
the range indicated in the bin name.
Pegging
Table 13-58 Bin ranges for UL_BLER_CS1
Bin Range
0 ≥ 0, < 5%
1 ≥ 5%, < 10%
2 ≥ 10%, < 15%
3 ≥ 15%, < 20%
4 ≥ 20%, < 25%
5 ≥ 25%, < 30%
6 ≥ 30%, < 40%
7 ≥ 40%,≤ 100%
One unit represents 10 UL BLER calculations. For a given carrier using coding scheme
1 in uplink transfer, the calculation is done by using the following equation whenever a
PUA/PTR/PUAK is sent by the PCU.
data blocks not correctly received within a window

Uplink BLER = × 100
window size [in number of blocks]
The window is maintained by PCU as part of MS context. It is updated whenever a data block
is received or missed, and has a maximum size of 128. 10X+Y (1<=Y<=10) calculations is
represented as X+1.
The range is 0 to 18,000. The shortest period between two consecutive PUA/PTR/PUAK cannot
be accurately estimated. Two such messages may be scheduled by the system in a back to
back situation (for example, the next PUAK may be scheduled at the next block period of the
previous PUAK). So in a one hour period, there may be at most 3,600,000 ms or (1 x 20 ms)
= 180,000 PUA/PTR/PUAKs being sent. Thus there is at most 180,000 calculations, and the
maximum value is 18,000 for each bin.
13-170 68P02901W56-T
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-171
Jan 2010
UL_BLER_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 10%
1 ≥ 10%, < 20%
2 ≥ 20%, < 25%
3 ≥ 25%, < 30%
4 ≥ 30%, < 35%
5 ≥ 35%, < 40%
6 ≥ 40%, < 65%
7 ≥ 65%, ≤ 100%

represented as X+1.
be accurately estimated. Two such messages may be scheduled by the system in a back to back
situation (for example, the next PUAK may be scheduled at the next block period of the previous
PUAK). So in a one hour period, there may be at most 3,600,000ms or (1x20ms) = 180,000
PUA/PTR/PUAKs being sent. Thus there is at most 180,000 calculations, and the maximum
value is 18,000 for each bin.
13-172 68P02901W56-T
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-T 13-173
Jan 2010
UL_BLER_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic is not available if Coding Scheme 3/4 feature is disabled.
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-174 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_BLER_CS4
UL_BLER_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic is not available if Coding Scheme 3/4 feature is disabled.
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 65%
7 ≥ 65%, ≤ 100%

represented as X+1.
PUAK). So in a one hour period, there may be at most 3,600,000ms or (1x20 ms) = 180,000
68P02901W56-T 13-175
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-176 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_BLER_MCS1
UL_BLER_MCS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_BLER_MCS1 statistic indicates the number of times, measured at statistical intervals,
the BLER of a particular carrier, when using EGPRS modulation coding scheme 1 to transmit
in the uplink direction, falls into the given range. Each bin represents a range of percentage
Pegging
Table 13-61 Bin ranges for UL_BLER_MCS1
Bin Range
0 ≥ 0, < 5%
1 ≥ 5%, < 10%
2 ≥ 10%, < 15%
3 ≥ 15%, < 20%
4 ≥ 20%, < 25%
5 ≥ 25%, < 30%
6 ≥ 30%, < 40%
7 ≥ 40%,≤ 100%
One unit represents 10 UL BLER calculations. For a given carrier using EGPRS modulation
coding scheme 1 in uplink transfer, the calculation is done by using the following equation
whenever a PUA/PTR/PUAK is sent by the PCU.

represented as X+1.
PUAK). So in a one hour period, there may be at most 3,600,000 ms or (1x20 ms) = 180,000
68P02901W56-T 13-177
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-178 68P02901W56-T
Jan 2010
UL_BLER_MCS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 10%
1 ≥ 10%, < 20%
2 ≥ 20%, < 25%
3 ≥ 25%, < 30%
4 ≥ 30%, < 35%
5 ≥ 35%, < 40%
6 ≥ 40%, < 65%
7 ≥ 65%,≤ 100%

represented as X+1.
situation (that is, the next PUAK may be scheduled at the next block period of the previous
PUAK.). So in a one hour period, there may be at most 3,600,000 ms or (1x20 ms) = 180,000
68P02901W56-T 13-179
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-180 68P02901W56-T
Jan 2010
UL_BLER_MCS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 25%
2 ≥ 25%, < 30%
3 ≥ 30%, < 35%
4 ≥ 35%, < 40%
5 ≥ 40%, < 45%
6 ≥ 45%, < 70%
7 ≥ 70%, ≤ 100%

represented as X+1.
68P02901W56-T 13-181
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-182 68P02901W56-T
Jan 2010
UL_BLER_MCS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging

Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 65%
7 ≥ 65%, ≤ 100%

represented as X+1.
68P02901W56-T 13-183
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-184 68P02901W56-T
Jan 2010
UL_BLER_MCS5
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 25%
2 ≥ 25%, < 30%
3 ≥ 30%, < 35%
4 ≥ 35%, < 40%
5 ≥ 40%, < 45%
6 ≥ 45%, < 70%
7 ≥ 70%,≤ 100%

represented as X+1.
68P02901W56-T 13-185
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-186 68P02901W56-T
Jan 2010
UL_BLER_MCS6
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 15%
1 ≥ 15%, < 30%
2 ≥ 30%, < 35%
3 ≥ 35%, < 40%
4 ≥ 40%, < 45%
5 ≥ 45%, < 50%
6 ≥ 50%, < 75%
7 ≥ 75%,≤ 100%

represented as X+1.
68P02901W56-T 13-187
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-188 68P02901W56-T
Jan 2010
UL_BLER_MCS7
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%,≤ 100%

represented as X+1.
68P02901W56-T 13-189
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-190 68P02901W56-T
Jan 2010
UL_BLER_MCS8
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%, ≤ 100%

represented as X+1.
68P02901W56-T 13-191
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-192 68P02901W56-T
Jan 2010
UL_BLER_MCS9
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Bin Range
0 ≥ 0, < 20%
1 ≥ 20%, < 35%
2 ≥ 35%, < 40%
3 ≥ 40%, < 45%
4 ≥ 45%, < 50%
5 ≥ 50%, < 55%
6 ≥ 55%, < 80%
7 ≥ 80%, ≤ 100%

represented as X+1.
68P02901W56-T 13-193
Jan 2010
Analysis
Reference None.
Basis Carrier.
Type Counter array.
13-194 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_BUSY_PDTCH
UL_BUSY_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean, maximum and minimum number of occupied Packet Data
CHannel (PDCH) carrying uplink packet traffic.
NOTE
The busy PDTCH number may increase as the additional switchable PDTCH is
This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, at every
packet-scheduling period (20 millisecond).
Table 13-70 shows the ranges for each bin (measured in milliseconds).
Table 13-70 UL_BUSY_PDTCH bins
Bin Range
0 No PDTCH is busy
Pegging
This statistic pegs every packet-scheduling period (20 millisecond) by sampling the number of
PDTCHs that are carrying uplink packet traffic.
NOTE
68P02901W56-T 13-195
Jan 2010
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for uplink
packet traffic.

Congestion.
Basis Cell.
13-196 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_CHANNEL_REQUESTS_REJECTION_RATE
UL_CHANNEL_REQUESTS_REJECTION_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_CHANNEL_REQUESTS_REJECTION_RATE key statistic shows the percentage of

uplink channel requests that are rejected by the PCU.
Formula
UL− CHANNEL− REQUESTS− CHANNEL− REQS− REJECT

= ∗100
REJECTION− RATE CHANNEL− REQS− REC
Analysis
Basis Cell.
Type Percentage.
Raw statistics CHANNEL_REQS_REJECT.
CHANNEL_REQS_REC.
68P02901W56-T 13-197
Jan 2010
UL_CHANNEL_REQUESTS_SUCCESS_RATE Chapter 13: PCU statistics
UL_CHANNEL_REQUESTS_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_CHANNEL_REQUESTS_SUCCESS_RATE key statistic monitors the success of uplink

channel requests. This is an important area as the MS needs to access the network before it
can exchange data. Low end-to-end throughput can be rooted in a low UL channel request
success rate.
NOTE
It is not possible to split this formula in a GPRS and an EGPRS part because
an EGPRS channel request might be served with GPRS resources, causing the
CHANNEL_REQS_SUCCESS statistic to be pegged in a GPRS bin.
13-198 68P02901W56-T
Jan 2010
Formula
 
CHANNEL− REQS− SUCCESS− P− C+
 
 CHANNEL− REQS− SUCCESS− P− P+ 
 
 
 CHANNEL− REQS− SUCCESS− P− R+ 
 
 
 CHANNEL− REQS− SUCCESS− E− C+ 
 
 
 CHANNEL− REQS− SUCCESS− E− 1P− CCC+ 
 
 CHANNEL REQS SUCCESS E PUAPRR+ 
 − − − − ∗100
 
 
 CHANNEL− REQS− SUCCESS− E− PTR+ 
 
 
 CHANNEL− REQS− SUCCESS− E− 1P− PCCC+ 
 
 
 CHANNEL− REQS− SUCCESS− CP− A+ 
 
 
 CHANNEL− REQS− SUCCESS− PKTS+ 
 
UL− CHANNEL− REQUESTS− CHANNEL− REQS− SUCCESS− E− PUAPDAK
=
SUCCESS− RATE CHANNEL− REQS− REC− P− C+CHANNEL− REQS− REC− P− P+
CHANNEL− REQS− REC− P− R+CHANNEL− REQS− REC− CP− A+
CHANNEL− REQS− REC− E− C+
CHANNEL− REQS− REC− EGPRS− 1PH− CC+
CHANNEL− REQS− REC− EGPRS− PKRS− RQ+
CHANNEL− REQS− REC− EGPRS− 1PH− PCC+
CHANNEL− REQS− REC− EGPRS− CRQPDAK
Analysis
Type Percentage.
Raw statistics CHANNEL_REQS_SUCCESS (Includes
sum of bins 0, 1, 4,5,6,7,8,9, 12, 13 and 14.
CHANNEL_REQS_REC (Includes sum of
bins 0, 1, 4, 5, 6, 7, 8, 11 and 12.
68P02901W56-T 13-199
Jan 2010
UL_LLC_FRAMES Chapter 13: PCU statistics
UL_LLC_FRAMES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_LLC_FRAMES statistic represents the total number of uplink LLC frames correctly
received by the PCU.
Pegging
Each bin represents a range which the size of LLC frames falls into:
Table 13-71 Bin ranges for UL_LLC_FRAMES
Bin Name Range

0 UL_LLC_FRAMES_20 0 - 20
3 UL_LLC_FRAMES_160 81 - 160
4 UL_LLC_FRAMES_320 161 - 320
5 UL_LLC_FRAMES_640 321 - 640
6 UL_LLC_FRAMES_1280 641 - 1280
7 UL_LLC_FRAMES_OVER1280 1281 and up
The range is 0 to 65,535. The maximum number of LLC frames received from the MS during a
one hour period cannot be accurately estimated. Use the uplimit of a 16-bit unsigned integer.
Analysis
Reference None.
LLC_DISCARDS_ON_CELL_RESELECTION,
UL_LLC_TRAFFIC_VOLUME_INDICATOR.
Basis Cell.
Type Counter array.
13-200 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_MEAN_TBF_DURATION
UL_MEAN_TBF_DURATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_MEAN_TBF_DURATION key statistic provides the mean duration of successful

TBFs in the uplink.
Formula
 
UL− T BF− T IM E− 8P SK− 1− T S+
 
 UL− T BF− T IM E− 8P SK− 2− T S+ 
 
 UL T BF T IM E 8P SK 3 T S+ 
 − − − − − 
 
 UL− T BF− T IM E− 8P SK− 4− T S+ 
 
 
 UL− T BF− T IM E− GM SK− 1− T S+ 
 
 
 UL− T BF− T IM E− GM SK− 2− T S+ 
 
 
 UL− T BF− T IM E− GM SK− 3− T S+ 
UL− T BF− T IM E− GM SK− 4− T S+
UL− MEAN− TBF− DURATION =   ∗ 0.02
UL− P DT CH− SEIZU RE−
 
 AIR− UL− TBF− FAILURES− DT− 
 
 
 AIR− UL− T BF− F AILU RES− T − 
AIR− UL− T BF− F AILU RES− EXT− UL− T BF −
68P02901W56-T 13-201
Jan 2010
Analysis

Congestion.
Basis Cell.
Type Seconds.
Raw statistics UL_TBF_TIME_8PSK_1_TS..
UL_TBF_TIME_8PSK_2_TS.
.UL_TBF_TIME_GMSK_1_TS.
UL_TBF_TIME_GMSK_2_TS.
UL_TBF_TIME_GMSK_4_TS
UL_PDTCH_SEIZURE.
AIR_UL_TBF_FAILURES_DT.
AIR_UL_TBF_FAILURES_T.
AIR_UL_TBF_FAILURES_EXT_UL_TBF.
13-202 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_MEAN_USER_TRAFFIC_PER_TBF
UL_MEAN_USER_TRAFFIC_PER_TBF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_MEAN_USER_TRAFFIC_PER_TBF statistic estimates the mean amount of RLC/MAC

traffic transported in an uplink TBF, excluding retransmitted blocks. Therefore, this key statistic
includes only successful RLC blocks.
Formula
(A1 ∗ 22) + (A2 ∗ 33) + (A3 ∗ 39) + (A4 ∗ 53) + (A5 ∗ 22) + (A6 ∗ 28) + (A7 ∗ 37)
UL− MEAN− USER− + (A8 ∗ 44) + (A9 ∗ 56) + (A10 ∗ 74) + (A11 ∗ 112) + (A12 ∗ 136) + (A13 ∗ 148)
= ∗ 100
TRAFFIC− PER− TBF 1024∗UL− PDTCH− SEIZURE
UL− RLC− ACK− NEW− BLKS− CS− 1+

A1 =
UL− RLC− UNACK− NEW− BLKS− CS− 1

A2 =

A3 =

A4 =
UL− RLC− ACK− NEW− BLKS− MCS− 1+

A5 =
UL− RLC− UNACK− NEW− BLKS− MCS− 1
68P02901W56-T 13-203
Jan 2010

A6 =

A7 =

A8 =

A9 =

A10 =

A11 =

A12 =

A13 =
Analysis

Congestion.
Basis Cell.
Type kbytes per TBF.
Raw statistics Bins 0 to 12 of UL_RLC_ACK_NEW_BLKS and
UL_RLC_UNACK_NEW_BLKS.
13-204 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_PDTCH_Q_LENGTH
UL_PDTCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic is obtained by sampling the Uplink Request Queue. Queued messages are RACH,
PRACH, and PRR.
Pegging
This statistic pegs every 20 ms. It is incremented when a request is added to the queue and is
decremented when a request is processed, that is, leaves the queue.
NOTE
Analysis
This statistic can be used for the trend analysis of the average number of uplink messages
waiting for a PDTCH to become available.
This statistic can be used for trend analysis of the number of queued uplink PDTCH requests.

Congestion.
Basis Cell.
Type Gauge.
68P02901W56-T 13-205
Jan 2010
UL_PDTCH_SEIZURE Chapter 13: PCU statistics
UL_PDTCH_SEIZURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the uplink.
This statistic counts the number of temporary block flows (TBF) on the uplink. The statistic
is obtained by measuring the receipt of the first RLC block (PDU) on the PDTCH from the
MS (uplink).
Pegging
This statistic pegs when the receipt of the first uplink RLC block (PDU) on the PDTCH from
the MS is obtained.
This statistic pegs when:

• The first uplink data block is received during a two-phase uplink TBF establishment.
• A first uplink data block containing a valid Temporary Logical Link Identity (TLLI) is
received during a one-phase uplink TBF establishment.
NOTE
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink
for a CELL.

Key statistic:
Basis Cell.
Type Counter.
13-206 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RADIO_BLKS_8PSK_1_TS
UL_RADIO_BLKS_8PSK_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RADIO_BLKS_8PSK_1_TS statistic counts the total number of RLC radio blocks
received from EGPRS MSs capable of 8PSK on the uplink that support a maximum of 1 TS in the
uplink direction (MS multislot classes 1, 2, 4, and 8).
One unit represents 100 RLC radio blocks. The maximum recommended interval is 60 minutes.
The translation of actual radio blocks counted to units is performed at the end of the interval.
The RLC radio blocks are split into the four GPRS coding schemes (CS-1 through CS-4) and nine
EGPRS coding schemes (MCS-1 through MCS-9), as shown in Table 13-72.
Table 13-72 Bin ranges for UL_RADIO_BLKS_8PSK_1_TS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
Table 13-73 Pegging method for UL_RADIO_BLKS_8PSK_1_TS statistic
(RLC block 1, RLC block 2) UL radio block status

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
(RETRANS, RETRANS) RETRANS
68P02901W56-T 13-207
Jan 2010
Multislot class 30, 35 and 40 are treated as multislot class 8.
The UL_RADIO_BLKS_8PSK_1_TS statistic can be used in conjunction with

UL_TBF_TIME_8PSK_1_TS to calculate the effective uplink throughput per EGPRS terminal
type (MS multislot classes 1, 2, 4 and 8).
NOTE
Pegging
This statistic counts the RLC radio blocks for EGPRS MSs capable of 8PSK on the uplink that
support a maximum 1 TS in the uplink direction. Only RLC radio blocks are counted. No
retransmissions due to any cause shall be pegged in this statistic. The RLC radio blocks are
counted per coding scheme, therefore pegging the appropriate bin.
This statistic also pegs for 8PSK MSs whose multislot class is not known before the end of the
UL TBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
The UL_RADIO_BLKS statistics are only reported for successful TBFs. Bin 0 (CS-1) and bin 4
Analysis
Reference None.
Basis Cell.
13-208 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
received from EGPRS MSs capable of 8PSK on the uplink that support a maximum of 2 TS in
the uplink direction (MS multislot classes 3, 5, 6, 9, and 10).
One unit represents 100 RLC radio blocks. The maximum recommended interval is 60 minutes.
The translation of actual radio blocks counted to units is performed at the end of the interval.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
Table 13-75 Pegging method for UL_RADIO_BLKS_8PSK_2_TS statistic

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
68P02901W56-T 13-209
Jan 2010
Multislot class 7 that support greater than 2 timeslots on the uplink is treated as 2 uplink
capable.
Multislot class 13 is treated as class 9 and multislot class 14-29, 31-34, 36-39 and 41-45 are
treated as class 10.
The UL_RADIO_BLKS_8PSK_2_TS statistic can be used in conjunction with

UL_TBF_TIME_8PSK_2_TS to calculate the effective uplink throughput per EGPRS terminal
type (MS multislot classes 3, 5, 6, 9 and 10).
NOTE
Pegging
This statistic counts the RLC radio blocks for EGPRS MSs capable of 8PSK on the uplink that
support a maximum 2 TS in the uplink direction. Only RLC radio blocks are counted. No
retransmissions due to any cause are pegged in this statistic. The RLC radio blocks are counted
per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Basis Cell
Type Counter array
13-210 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
received from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 3 TS in
the uplink direction (mobile multislot class 11).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The
translation of actual radio blocks counted to units is performed at the end of the interval.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplink
that support a maximum 3 TS in the uplink direction. Only RLC radio blocks are counted. No
68P02901W56-T 13-211
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
13-212 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
received from EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 4 TS in
the uplink direction (mobile multislot class 12).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
Data Type for each bin is Default.
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles capable of 8PSK on the uplink
that support a maximum 4 TS in the uplink direction. Only RLC radio blocks are counted. No
68P02901W56-T 13-213
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
13-214 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RADIO_BLKS_GMSK_1_TS
UL_RADIO_BLKS_GMSK_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RADIO_BLKS_GMSK_1_TS statistic counts the total number of RLC radio blocks
received from GPRS and EGPRS MSs that support a maximum of 1 TS in the uplink direction (MS
multislots classes 1, 2, 4 and 8). The EGPRS MS is not capable of supporting 8PSK in the uplink.
This statistic also pegs MSs whose multislot class is not known before the end of the UL TBF.
The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
The RLC radio blocks are split into the four GPRS channel coding schemes, and the four GMSK
EGPRS coding schemes, as shown in Table 13-78.
Table 13-78 Bin ranges for UL_RADIO_BLKS_GMSK_1_TS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Multislot class 30, 35 and 40 is treated as multislot class 8.
The UL_RADIO_BLKS_GMSK_1_TS statistic can be used in conjunction with

UL_TBF_TIME_GMSK_1_TS to calculate the effective uplink throughput per terminal type
(MS multislot classes 1, 2, 4 and 8).
NOTE
68P02901W56-T 13-215
Jan 2010
Pegging
uplink direction. Only RLC radio block is counted. No retransmissions due to any cause are
pegged in this statistic. The RLC radio blocks are counted per coding scheme therefore pegging
Analysis
Reference None.
Basis Cell.
13-216 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
received from GPRS mobiles and EGPRS mobiles not capable of supporting 8PSK in the uplink
that support a maximum of 2 TS in the uplink direction (mobile multislot classes 3, 5, 6, 9 and
10). The EGPRS mobile is not capable of supporting 8PSK in the uplink.
This statistic also pegs MSs whose multislot class is not known before the end of the UL TBF.
The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
The RLC radio blocks are split into the four GPRS channel coding schemes and the four GMSK
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Multislot class 7 that support greater than 2 timeslots on the uplink is treated as 2 uplink
capable.
Multislot class 13 is treated as multislot class 9 and multislot class 14-29, 31-34, 36-39 and
41-45 is treated as class 10.
Multislot class 13 is treated as multislot class 9.
Multislot classes 14–29 is treated as multislot class 10.
The UL_RADIO_BLKS_GMSK_2_TS statistic can be used in conjunction with

UL_TBF_TIME_GMSK_2_TS to calculate the effective uplink throughput per terminal type (MS
multislot classes 3, 5, 6, 9 and 10).
NOTE
68P02901W56-T 13-217
Jan 2010
Pegging
uplink direction. Only RLC radio blocks are counted. No retransmissions due to any cause
are pegged in this statistic. The RLC radio blocks are counted per coding scheme therefore
pegging the appropriate bin.
Analysis
Reference None.
Basis Cell.
13-218 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
that support a maximum of 3 TS in the uplink direction (mobile multislot classes 11). The
EGPRS mobile is not capable of supporting 8PSK in the uplink.
This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF.
The accuracy of this statistic is reduced due to these unknown multi-slot cases.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is performed at the end of the interval.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 3 TS in the
68P02901W56-T 13-219
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
13-220 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
that support a maximum of 4 TS in the uplink direction (mobile multislot classes 12). The
EGPRS mobile is not capable of supporting 8PSK in the uplink.
This statistic also pegs mobiles whose multislot class is not known before the end of the UL TBF.
The accuracy of this statistic is reduced due to these unknown multi-slot cases.
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation
of actual radio blocks counted to units is performed at the end of the interval.
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 4 TS in the
68P02901W56-T 13-221
Jan 2010
Analysis
Reference None.
Usage
Basis Cell.
13-222 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_ACK_NEW_BLKS
UL_RLC_ACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledge
mode blocks received by the PCU over the cell.
Table 13-82 Bin ranges for UL_RLC_ACK_NEW_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
Table 13-83 Pegging method for UL_RLC_ACK_NEW_BLKS statistic

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
68P02901W56-T 13-223
Jan 2010
Pegging
This statistic counts the new RLC acknowledged radio blocks that are received on a cell. The
Analysis
Reference None
Basis Cell
Type Counter array
13-224 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_RETX_BLKS
UL_RLC_RETX_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_RETX_BLKS statistic measures the total number of preemptive retransmissions

(or ack pending blocks and acknowledged retransmissions) received by the PCU over the cell.
Table 13-84 Bin ranges for UL_RLC_RETX_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
Table 13-85 Pegging method for UL_RLC_RETX_BLKS statistic

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
68P02901W56-T 13-225
Jan 2010
Pegging
This statistic counts the RLC ack pending (or preemptive transmissions) radio blocks that are
received on a cell. The RLC radio blocks are counted per coding scheme, therefore pegging
Analysis
Reference None
Basis Cell
Type Counter array
13-226 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_UNACK_NEW_BLKS
UL_RLC_UNACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_UNACK_NEW_BLKS statistic measures the total number of new RLC

unacknowledge mode blocks received by the PCU over the cell.
Table 13-86 Bin ranges for UL_RLC_UNACK_NEW_BLKS
Bin Range
0 CS-1
1 CS-2
2 CS-3
3 CS-4
4 MCS-1
5 MCS-2
6 MCS-3
7 MCS-4
8 MCS-5
9 MCS-6
10 MCS-7
11 MCS-8
12 MCS-9
or MCS-9.
Table 13-87 Pegging method for UL_RLC_UNACK_NEW_BLKS statistic

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
68P02901W56-T 13-227
Jan 2010
Pegging
This statistic counts the new RLC unacknowledged radio blocks that are received on a cell. The
Analysis
Reference None
Basis Cell
Type Counter array
13-228 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_FAILURE_RATE
UL_TBF_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_FAILURE_RATE key statistic calculates the rate of abnormally released downlink
TBFs.
Formula
UL− TBF− FAILURE− AIR− UL− TBF− FAILURES∗100

=  
RATE CHAN N EL− REQS− SU CCESS− P− C+
 
 
 CHAN N EL− REQS− SU CCESS− P− P + 
 
 
 CHAN N EL− REQS− SU CCESS− P− R+ 
 
 
 CHAN N EL− REQS− SU CCESS− P KT S+ 
 
 
 
 CHAN N EL− REQS− SU CCESS− E− C+ 
 
 
 CHAN N EL− REQS− SU CCESS− CP− A+ 
 
 
 CHAN N EL− REQS− SU CCESS− E− 1P− CCC+ 
 
 CHAN N EL REQS SU CCESS E 1P P CCC+ 
 − − − − − 
 
 CHAN N EL− REQS− SU CCESS− E− P U AP RR+ 
 
 
 CHAN N EL− REQS− SU CCESS− E− P T R+ 
 
 
 CHAN N EL− REQS− SU CCESS− E− P U AP DAK+ 
 
 
 DT M− REQ− SU C− DT M− U L− T BF− SDCCH+ 
 
 DT M− REQ− SU C− DT M− U L− T BF− T CH+ 
 
DT M− REQ− SU C− P A− U L− T BF− T CH
Analysis

Basis Cell.
Type Percentage.
Raw statistics AIR_UL_TBF_FAILURES.
Bins 0, 1, 4, 5, 6, 7, 8, 9, 12, 13 and 14 of
CHANNEL_REQS_SUCCESS.
68P02901W56-T 13-229
Jan 2010
UL_TBF_TIME_8PSK_1_TS Chapter 13: PCU statistics
UL_TBF_TIME_8PSK_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_TIME_8PSK_1_TS statistic measures the duration in time (the cumulative length
in number of 20 ms radio block periods) of the uplink TBFs for EGPRS MSs that support a
maximum of 1 TS and capable of 8PSK in the uplink direction.
The UL_TBF_TIME_8PSK_1_TS statistic can be used in conjunction with

UL_RADIO_BLKS_8PSK_1_TS to calculate the effective uplink throughput per EGPRS terminal
type (MS multislot classes 1, 2, 4 and 8).
Pegging
This statistic pegs the time of all the TBFs in the uplink for MSs that support a maximum of
1 TS and capable of 8PSK in the uplink direction. At the end of the statistical interval this
statistic provides a cumulative value of all the UL TBF times for MSs supporting a maximum
of 1 TS. The TBF time starts with the set-up of the TBF and finishes when all the uplink RLC
radio blocks have been received without error.
This statistic also pegs for 8PSK MSs whose multislot class is not known before the end of the
UL TBF. The accuracy of this statistic may be reduced due to these unknown multi-slot cases.
Analysis
Reference None
Basis Cell
Type Counter
13-230 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_TIME_8PSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
in number of 20 ms radio block periods) of the uplink TBFs for EGPRS MSs that support a
The UL_TBF_TIME_8PSK_2_TS statistic can be used in conjunction with

UL_RADIO_BLKS_8PSK_2_TS to calculate the effective uplink throughput per EGPRS terminal
Pegging
This statistic pegs the time of all the TBFs in the uplink for MSs that support a maximum of
2 TS and capable of 8PSK in the uplink direction. At the end of the statistical interval this
statistic provides a cumulative value of all the UL TBF times for MSs supporting a maximum
Analysis
Reference None
Basis Cell
Type Counter
68P02901W56-T 13-231
Jan 2010
UL_TBF_TIME_8PSK_3_TS Chapter 13: PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
in number of 20 ms radio block periods) of the uplink TBFs for EGPRS mobiles that support a
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum
of 3 TS and capable of 8PSK in the uplink direction. At the end of the statistical interval this
statistic provides a cumulative value of all the UL TBF times for mobiles supporting a maximum
Analysis
Reference None.
Usage
Basis Cell.
Type Counter.
13-232 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_TIME_8PSK_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
in number of 20 ms radio block periods) of the uplink TBFs for EGPRS mobiles that support a
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles that support a maximum
of 4 TS and capable of 8PSK in the uplink direction. At the end of the statistical interval this
statistic provides a cumulative value of all the UL TBF times for mobiles supporting a maximum
Analysis
Reference None.
Usage
Basis Cell.
Type Counter.
68P02901W56-T 13-233
Jan 2010
UL_TBF_TIME_GMSK_1_TS Chapter 13: PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_TIME_GMSK_1_TS statistic counts the cumulative length in number of 20 ms

radio block periods of all uplink TBFs for MSs that support a maximum of 1 TS in the uplink
direction and not capable of supporting 8PSK in the uplink.
This statistic also pegs for MSs whose multislot class is not known before the end of the UL TBF.
The accuracy of this statistic may be reduced due to these unknown multislot cases.
The UL_TBF_TIME_GMSK_1_TS statistic can be used in conjunction with

UL_RADIO_BLKS_GMSK_1_TS to calculate the effective uplink throughput per terminal type
(MS multislot classes 1, 2, 4 and 8).
Pegging
This statistic measures the time of all the TBFs in the uplink for MSs that support a maximum
of 1 TS in the uplink direction. At the end of the statistical interval this statistic provides a
cumulative value of all the UL TBF times for MSs supporting a maximum of 1 TS. The TBF
time starts with the set-up of the TBF and finishes when all the uplink RLC radio blocks have
been received without error.
Analysis
Reference None
Basis Cell
Type Counter
13-234 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_TIME_GMSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

radio block periods of all uplink TBFs for GPRS and EGPRS MSs that support a maximum of 2
TS in the uplink direction. The EGPRS MS is not capable of supporting 8PSK in the uplink.
The UL_TBF_TIME_GMSK_2_TS statistic can be used in conjunction with

UL_RADIO_BLKS_GMSK_2_TS to calculate the effective uplink throughput per terminal
Pegging
This statistic measures the time of all the TBFs in the uplink for MSs that support a maximum
cumulative value of all the UL TBF times for MSs supporting a maximum of 2 TS. The TBF
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-T 13-235
Jan 2010
UL_TBF_TIME_GMSK_3_TS Chapter 13: PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

radio block periods of all uplink TBFs for GPRS and EGPRS mobiles that support a maximum of
3 TS in the uplink direction. The EGPRS mobile is not capable of supporting 8PSK in the uplink.
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum
cumulative value of all the UL TBF times for mobiles supporting a maximum of 3 TS. The TBF
Analysis
Reference None.
Usage
Basis Cell.
Type Counter.
13-236 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_TIME_GMSK_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

radio block periods of all uplink TBFs for GPRS and EGPRS mobiles that support a maximum of
4 TS in the uplink direction. The EGPRS mobile is not capable of supporting 8PSK in the uplink.
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum
cumulative value of all the UL TBF times for mobiles supporting a maximum of 4 TS. The TBF
Analysis
Reference None.
Usage
Basis Cell.
Type Counter.
68P02901W56-T 13-237
Jan 2010
UL_THROUGHPUT_TERMINAL_1_TS Chapter 13: PCU statistics
UL_THROUGHPUT_TERMINAL_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_THROUGHPUT_TERMINAL_1_TS key statistic calculates the TBF throughput

performance for MSs that can support a maximum of 1 TS in the uplink direction.
Formula
UL− THROUGHPUT− (A + B + C + D) ∗ 0.8

=
TERMINAL− 1− TS (UL− TBF− TIME− 8PSK− 1− TS+UL− TBF− TIME− GMSK− 1− TS)∗0.02
UL− RADIO− BLKS− 8PSK− 1− TS− CS− 2 ∗ 33+

A=
UL− RADIO− BLKS− 8PSK− 1− TS− CS− 1 ∗ 22
UL− RADIO− BLKS− GMSK− 1− TS− CS− 2 ∗ 33+

B=
UL− RADIO− BLKS− GMSK− 1− TS− CS− 1 ∗ 22
UL− RADIO− BLKS− GMSK− 1− TS− MCS− 2 ∗ 28+

C=
UL− RADIO− BLKS− GMSK− 1− TS− MCS− 1 ∗ 22
13-238 68P02901W56-T
Jan 2010
UL− RADIO− BLKS− 8PSK− 1− TS− MCS− 2 ∗ 28+


D=
UL− RADIO− BLKS− 8PSK− 1− TS− MCS− 9 ∗ 148
Analysis
Basis Per terminal.

Raw statistics Bins 0 to 12 of UL_RADIO_BLKS_8PSK_1_TS.
Bins 0 to 7 of UL_RADIO_BLKS_GMSK_1_TS.
68P02901W56-T 13-239
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
UL− THROUGHPUT− (A + B + C + D) ∗ 0.8

=
TERMINAL− 1− 2− TS (UL− TBF− TIME− 8PSK− 2− TS+UL− TBF− TIME− GMSK− 2− TS)∗0.02

A=
UL− RADIO− BLKS− 8PSK− 2− TS− CS− 1 ∗ 22

B=
UL− RADIO− BLKS− GMSK− 2− TS− CS− 1 ∗ 22

C=
UL− RADIO− BLKS− GMSK− 2− TS− MCS− 1 ∗ 22
13-240 68P02901W56-T
Jan 2010


D=
UL− RADIO− BLKS− 8PSK− 2− TS− MCS− 9 ∗ 148
Analysis
Basis Per terminal.

68P02901W56-T 13-241
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
(A + B + C + D) ∗ 0.8
U L− T HROU GHP U T− T ERM IN AL− 3− T S = !
U L− T BF− T IM E− 8P SK− 3− T S+
∗ 0.02
U L− T BF− T IM E− GM SK− 3− T S
U L− RADIO− BLKS− 8P SK− 3− T S− CS− 1 ∗ 22+

A=
U L− RADIO− BLKS− 8P SK− 3− T S− CS− 4 ∗ 53
U L− RADIO− BLKS− 8P SK− 3− T S− M CS− 1 ∗ 22+

B = U L− RADIO− BLKS− 8P SK− 3− T S− M CS− 5 ∗ 56+
U L− RADIO− BLKS− 8P SK− 3− T S− M CS− 9 ∗ 148
13-242 68P02901W56-T
Jan 2010
U L− RADIO− BLKS− GM SK− 3− T S− CS− 1 ∗ 22+

C=
U L− RADIO− BLKS− GM SK− 3− T S− CS− 4 ∗ 53
U L− RADIO− BLKS− GM SK− 3− T S− M CS− 1 ∗ 22+

D=
U L− RADIO− BLKS− GM SK− 3− T S− M CS− 4 ∗ 44
Analysis
Basis Per terminal.

68P02901W56-T 13-243
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
(A + B + C + D) ∗ 0.8
U L− T HROU GHP U T− T ERM IN AL− 4− T S = !
∗ 0.02

A=
U L− RADIO− BLKS− 8P SK− 4− T S− CS− 4 ∗ 53

B = U L− RADIO− BLKS− 8P SK− 4− T S− M CS− 5 ∗ 56+
U L− RADIO− BLKS− 8P SK− 4− T S− M CS− 9 ∗ 148
13-244 68P02901W56-T
Jan 2010

C=
U L− RADIO− BLKS− GM SK− 4− T S− CS− 4 ∗ 53

D=
U L− RADIO− BLKS− GM SK− 4− T S− M CS− 4 ∗ 44
Analysis
Basis Per terminal.

68P02901W56-T 13-245
Jan 2010
13-246 68P02901W56-T
Jan 2010
Chapter
14
BSS-SMLC statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS-based Serving Mobile Location Centre (SMLC) statistics track events on the signaling
link. They are categorized into subgroups, each of which are described in BSS-based SMLC
statistics subgroups on page 14-2.
68P02901W56-T 14-1
Jan 2010
BSS-based SMLC statistics subgroups Chapter 14: BSS-SMLC statistics
BSS-based SMLC statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS-based Serving Mobile Location Centre (SMLC) statistics are organized into two major
subgroups:
• BSS C7 utilization on page 14-2.
• SCCP performance and utilization on page 14-2.
BSS C7 utilization
BSS-based SMLC C7 utilization statistics track the number of messages received and
transmitted on the signaling links. This information indicates the activity level on the Signaling
Links (SLs). The following are BSS C7 utilization statistics:
• L_SIF_SIO_RX_OPC on page 14-8.
• L_SIF_SIO_TX_DPC on page 14-9.
• L_SIF_SIO_TYPE on page 14-10.
SCCP performance and utilization
SCCP performance and utilization statistics track the performance of the Signaling Connection
Control Part (SCCP) protocol layer of the ITU-TSS C7.
The SCCP manages the establishment and release of call related connections. A connection is
established for each transaction. For example, location update and service request, both BSS,
and BSS-based SMLC maintain contexts related to the transaction; these contexts may be
identified using the SCCP reference number. This information indicates the performance level
and quality of the SCCP. The following are the SCCP performance and utilization statistics:
• L_ROUTING_SYNTAX on page 14-3.
• L_ROUTING_UNKNOWN on page 14-4.
• L_SCCP_MSGS on page 14-5.
• L_SCCP_MSGS_RX on page 14-6.
• L_SCCP_MSGS_TX on page 14-7.
• L_SIF_SIO_RX_OPC on page 14-8.
• L_SIF_SIO_TX_DPC on page 14-9.
• L_SIF_SIO_TYPE on page 14-10.
• PAGE_REQ_FROM_SMLC_FAIL on page 14-11.
14-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application L_ROUTING_SYNTAX
L_ROUTING_SYNTAX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of SCCP messages with syntax errors.
Pegging
This statistic pegs when a syntax error is detected in an SCCP message on the Lb-interface.
Analysis
SCCP is an SS7 protocol used in transferring signaling messages between the BSC and
BSS-based SMLC. Excessive syntax errors can result in degraded SCCP performance.
SCCP messages with syntax errors that are acceptable in normal system operations.
If the specified threshold is exceeded, the 18. BSS: Routing failure - syntax error detected
(SMLC) - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-T 14-3
Jan 2010
L_ROUTING_UNKNOWN Chapter 14: BSS-SMLC statistics
L_ROUTING_UNKNOWN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of invalid signaling point codes (SPCs) that a BSC has received
from the BSS-based SMLC.
Pegging
This statistic pegs whenever an invalid SPC is received from the BSS-based SMLC.
Analysis
An SPC is the destination address for a message routed by the networking functions of the MTP3
protocol. If the BSC receives an incorrect SPC, it cannot route the message correctly.
invalid SPCs that are acceptable in normal system operations.
If the specified threshold is exceeded, the 19. BSS: Routing failure - reason unknown
(SMLC) - PM alarm is generated. Refer to the manual Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
14-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application L_SCCP_MSGS
L_SCCP_MSGS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages either transmitted or received between
the BSC and BSS-based SMLC over a Lb-interface.
Pegging
This statistic pegs when SCCP messages are transmitted or received on the signaling link
between the BSC and BSS-based SMLC.
Analysis
BSS-based SMLC. This statistic can be used for trend analysis of SCCP performance and
utilization.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
68P02901W56-T 14-5
Jan 2010
L_SCCP_MSGS_RX Chapter 14: BSS-SMLC statistics
L_SCCP_MSGS_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages received by the BSC from BSS-based
SMLC over a Lb-interface for class 0 or class 2.
This statistic switches the appropriate device value so that the OMC can store it in the relevant
column of the database:
• the number of SCCP messages received for class 0 is stored in l_sccp_msgs_rx_0.
• the number of SCCP messages received for class 2 is stored in l_sccp_msgs_rx_2.
Pegging
This statistic pegs when SCCP messages are received on the signaling link between the BSC
and BSS-based SMLC.
Analysis
BSS-based SMLC. This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
14-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application L_SCCP_MSGS_TX
L_SCCP_MSGS_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SCCP messages transmitted by the BSC to BSS-based
SMLC over the Lb-interface for class 0 or class 2.
• the number of SCCP messages transmitted for class 0 is stored in l_sccp_msgs_tx_0.
• the number of SCCP messages transmitted for class 2 is stored in l_sccp_msgs_tx_2.
Pegging
This statistic pegs when SCCP messages are transmitted on the signaling link.
Analysis
BSS-based SMLC. This statistic can be used for trend analysis of the activity over the
Lb-interface.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
68P02901W56-T 14-7
Jan 2010
L_SIF_SIO_RX_OPC Chapter 14: BSS-SMLC statistics
L_SIF_SIO_RX_OPC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of SIF and SIOs received on all SLs for the BSS from
BSS-based SMLC.
Pegging
This statistic pegs each time Signal Information Fields (SIF) or Service Information Octets (SIO)
are received across all signaling links between the BSS and BSS-based SMLC.
Analysis
BSS-based SMLC. This statistic can be used for trend analysis of the activity on all Lb-interface
SLs for a particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
14-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application L_SIF_SIO_TX_DPC
L_SIF_SIO_TX_DPC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the total number of Signal Information Fields (SIF) and Service Information
Octets (SIO) transmitted on all SLs of the BSS to the Lb-interface Destination Point Code (DPC).
Pegging
This statistic pegs each time SIF or SIO are transmitted across all signaling links from the BSS
to the BSS-based SMLC (as indicated by the Lb-interface (DPC)).
Analysis
A DPC is part of the label in a signaling message that uniquely identifies, in a signaling network,
the destination point of the message. This statistic can be used for trend analysis of the activity
of the signaling links on a BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
68P02901W56-T 14-9
Jan 2010
L_SIF_SIO_TYPE Chapter 14: BSS-SMLC statistics
L_SIF_SIO_TYPE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of SIF MTP, TEST, and SCCP SIOs transmitted or received on
all Lb-interface SLs.
• the number of SIF SCCP SIOs is stored in l_sif_sio_type.
• the number of SIF MTP SIOs is stored in l_sif_sio_type_mtp.
• the number of SIF TEST SIOs is stored in l_sif_sio_type_test.
Pegging
This statistic pegs each time SIF or SIOs are transmitted or received on all signaling links
between BSS and BSS-based SMLC.
Analysis
This statistic can be used for trend analysis of the activity of the signaling links on a BSS over
the Lb-interface.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis BSS.
Type Counter.
14-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PAGE_REQ_FROM_SMLC_FAIL
PAGE_REQ_FROM_SMLC_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of page request messages received from the BSS-based SMLC
that fail message validation at the BSS.
Pegging
This statistic pegs each time a page request message from the BSS-based SMLC fails message
validation at the BSS.
Analysis
failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 20. BSS: Paging request from SMLC protocol
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-T 14-11
Jan 2010
Analysis Chapter 14: BSS-SMLC statistics
14-12 68P02901W56-T
Jan 2010
Chapter
15
Web MMI statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The MMI statistics are categorized as PCU real-time statistics and MMI BSC/BTS real-time
statistics. The descriptions for these are given elsewhere in the manual and are referenced
in MMI statistics subgroups on page 15-2.
68P02901W56-T 15-1
Jan 2010
MMI statistics subgroups Chapter 15: Web MMI statistics
MMI statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMU statistics are organized into the following major subgroups:

• MMI PCU real-time statistics on page 15-2.
• MMI BSC/BTS real-time statistics on page 15-2.
MMI PCU real-time statistics
The following MMI PCU real-time statistics are documented elsewhere in this manual.
Table 15-1 indicates the location of these descriptions.
Table 15-1 Location of MMI PCU real-time statistics descriptions
MMI PCU statistic Location in manual

CELL_FLUSH_REQS CELL_FLUSH_REQS on page 13-17
CHANNEL_REQS_REJ CHANNEL_REQS_REJECT on page 13-22
GBL_PAGING_REQS GBL_PAGING_REQS on page 13-115
GBL_UNAVAILABLE GBL_UNAVAILABLE on page 13-121
MMI BSC/BTS real-time statistics
The following MMI BSC/BTS real-time statistics are documented elsewhere in this manual.
Table 15-2 indicates the location of these descriptions.
Table 15-2 Location of MMI BSC/BTS real-time statistics descriptions
MMI BSC/BTS statistic Location in manual

ALLOC_SDCCH_FAIL ALLOC_SDCCH_FAIL on page 4-23
ALLOC_TCH_FAIL ALLOC_TCH_FAIL on page 4-25
HO_FAIL_NO_RESOURCES HO_FAIL_NO_RESOURCES on page 4-90
HO_REQ_MSC_FAIL HO_REQ_MSC_FAIL on page 4-93
MA_CMD_TO_MS_BLKD MA_CMD_TO_MS_BLKD on page 4-116
RF_LOSSES_TCH RF_LOSSES_TCH on page 4-185
15-2 68P02901W56-T
Jan 2010
Chapter
16
Call model statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Call model parameter values can be derived from the GSM network statistics collected at
the OMC-R.
All the statistics used for determining the call model parameters must be collected during busy
hours and averaged over a reasonable period (three months or more).
The call model parameters should be averaged over the entire network or at the BSC level
for equipment dimensioning purposes. This gives more scope of averaging out the load from
the network entities.
The following are call model statistics:

• CALL_DURATION (T) on page 16-2.
• CALL_SETUP_BLOCKING_RATE on page 16-3.
• HANDOVERS_PER_CALL (H) on page 16-4.
• IMSI_DETACHES_TO_CALLS (Id) on page 16-6.
• INTRA_BSS_HO_TO_ALL_HO (i) on page 16-8.
• LOCATION_UPDATE_FACTOR (L) on page 16-9.
• LOCATION_UPDATES_TO_CALLS (I) on page 16-10.
• PAGES_PER_CALL (PPC) on page 16-12.
• PAGES_PER_SECOND on page 16-13.
• PAGING_RATE (P) on page 16-14.
• SMS_TO_CALL_RATIO (S) on page 16-15.
Refer to the manual System Information: BSS Equipment Planning (68P02900W21) for further
information on the call model parameters.
68P02901W56-T 16-1
Jan 2010
CALL_DURATION (T) Chapter 16: Call model statistics
CALL_DURATION (T)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the average call duration.
Formula
P
N
BUSY− TCH− MEAN ∗ stat− interval− in− sec
I=1
T=
P
N
(TOTAL− CALL + ASSIGNMENT− REDIRECTION)
I=1
Where: Is:
N the number of cells.
stat_interval_in_sec the interval over which BUSY_TCH_CARR_MEAN values are
measured. It is 3600 if hourly values are used and 86400 if daily
values are used.
Analysis

Optimization.
Basis Cell.
Units Seconds
Raw Statistics BUSY_TCH_MEAN.
TOTAL_CALLS.
ASSIGNMENT_REDIRECTION.
16-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SETUP_BLOCKING_RATE
CALL_SETUP_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the percentage of attempts to allocate a TCH call setup that are blocked.
Formula
CALL− SETUP− MA− CMD− TO− MS− BLKD

= ∗ 100%
BLOCKING− RATE MA− REQ− FROM− MSC
Analysis

Optimization.
Basis Cell.
Units Percentage.
Raw Statistics MA_CMD_TO_MS_BLKD.
MA_REQ_FROM_MSC.
68P02901W56-T 16-3
Jan 2010
HANDOVERS_PER_CALL (H) Chapter 16: Call model statistics
HANDOVERS_PER_CALL (H)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the number of Handovers per call where the handovers may be inter-BSS,
intra-BSS, or intra-cell.
Formula
 
INTRA− CELL− HO− ATMPT− FR− FR+
 
 INTRA− CELL− HO− ATMPT− FR− HR+ 
 
 INTRA CELL HO ATMPT HR HR+ 
 − − − − − 
 
 INTRA− CELL− HO− ATMPT− HR− FR+ 
 
 
 OUT− INTRA− BSS− HO− ATMPT+ 
 
OUT− INTER− BSS− HO− ATMPT
H =
(TOTAL− CALLS + ASSGINMENT− REDIRECTION)
Where: Is:
NOTE
The TOTAL_CALLS parameter is the count of the total circuit-switched calls in a cell.
It should be summed for all the cells in the BSC, when used in the previous formula.
16-4 68P02901W56-T
Jan 2010
Analysis

Optimization.
Basis Cell.
Raw Statistics OUT_INTRA_BSS_HO_ATMPT.

OUT_INTER_BSS_HO_ATMPT.
INTRA_CELL_HO (the value used in this formula is the sum of bins 1 to 4
of this counter array statistic).
TOTAL_CALLS.
68P02901W56-T 16-5
Jan 2010
IMSI_DETACHES_TO_CALLS (Id) Chapter 16: Call model statistics
IMSI_DETACHES_TO_CALLS (I ) d
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of IMSI detaches per call.
Formula
IMSI− DETACH
Id =  
CM− SERV− REQ− CALL
 
 
 
 
 + CM− SERV− REQ− SM S 
 
 
 
 
 
 + CM− SERV− REQ− EM ERG 
 
 
 
 
 
 + CM− REEST ABLISH 
 
 
 
 
 + P AGE− RESP ON SE 
 
 
 
 
 + LOC− F LW− ON− REQ− N ORM 
 
 
 
 
 + LOC− F LW− ON− REQ− SM S 
 
 
 
 
 − SM S− IN IT− ON− SDCCH 
 
 
 
 − SM S− IN IT− ON− SDCCH− REQ 
 
 
 
 − SM S− IN IT− ON− T CH− F CS 
 
 
 
 − SM S− IN IT− ON− T CH− F CS− REQ 
 
 
 + SM S− IN IT− ON− SDCCH− HO− IN− 
 
 
 
 + SM S− IN IT− ON− SIG− HO− IN− REQ 
 
 − M T− LCS− ON− SDCCH 
 
16-6 68P02901W56-T
Jan 2010
Analysis

Optimization.
Basis Cell.
Raw Statistics IMSI_DETACH
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV_REQ_EMERG
CM_REESTABLISH
PAGE_RESPONSE
LOC_FLW_ON_REQ_NORM
LOC_FLW_ON_REQ_SMS
SMS_INIT_ON_SDDCH
SMS_INIT_ON_SDDCH_REQ
SMS_INIT_ON_TCH_FCS
SMS_INIT_ON_TCH_FCS_REQ
SMS_INIT_ON_SDCCH_HO_IN
SMS_INIT_ON_SIG_HO_IN_REQ
MT_LCS_ON_SDCCH
68P02901W56-T 16-7
Jan 2010
INTRA_BSS_HO_TO_ALL_HO (i) Chapter 16: Call model statistics
INTRA_BSS_HO_TO_ALL_HO (i)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of intra-BSS handovers to all handovers.
Formula
 
 
 
 
 INTRA− CELL− HO− ATMPT− HR− HR+ 
 
 INTRA CELL HO ATMPT HR FR+ 
 − − − − − 
OUT− INTRA− BSS− HO− ATMPT
i =  
 
 
 
 INTRA− CELL− HO− ATMPT− HR− HR+ 
 
 
 INTRA− CELL− HO− ATMPT− HR− FR+ 
 
 OUT− INTRA− BSS− HO− ATMPT+ 
 
OUT− INTER− BSS− HO− ATMPT
Where: Is:
Analysis

Optimization.
Basis Cell.
INTRA_CELL_HO (the value used in this formula is the sum of bins 1 to 4
TOTAL_CALLS.
16-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LOCATION_UPDATE_FACTOR (L)
LOCATION_UPDATE_FACTOR (L)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic is calculated using the ratio of location updates per call (l) and the ratio of IMSI
detaches per call (Id). For networks with IMSI detach disabled, the location update factor
equals the ratio of location updates per call (l).
IMSI detach types determine the way the MSC clears the connection with the BSS after
receiving the IMSI detach. When using IMSI detach type 1, the MSC clears the SCCP
connection, a clearing procedure that involves only one uplink (average size of 42 bytes) and
one downlink message (average size of 30 bytes). When using IMSI detach type 2, the MSC
sends the CLEAR COMMAND and the BSS sends CLEAR COMPLETE, and so on, which involves
three uplink (average size of 26 bytes) and three downlink messages (average size of 30 bytes).
A location update procedure itself takes five downlink messages (average size of 30 bytes) and
six uplink messages (average size of 26 bytes).
Hence, an IMSI detach (type1) takes a total of 2/11 (approximately 0.2) of the number of
messages as a location update and an IMSI detach (type 2) takes 6/11 (approximately 0.5) of
the messages of a location update.
Formula
If IMSI detach is enabled, then depending on whether short message sequence (type 1) or long
message sequence (type 2) is used, L is calculated as:
• L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled that is Id=0)
• L = LOCATION_UPDATES_TO_CALLS + 0.2* IMSI_DETACHES_TO_CALLS (type 1)
• L = LOCATION_UPDATES_TO_CALLS + 0.5* IMSI_DETACHES_TO_CALLS (type 2)
Analysis

Optimization.
Basis Cell.
Call Model LOCATION_UPDATES_TO_CALLS.
Statistics IMSI_DETACHES_TO_CALLS.
68P02901W56-T 16-9
Jan 2010
LOCATION_UPDATES_TO_CALLS (I) Chapter 16: Call model statistics
LOCATION_UPDATES_TO_CALLS (I)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of location updates to calls.
Formula
LOCATION− UPDATE
l =  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 + SM S− IN IT− ON− SDCCH− HO− IN− 
 
 
 
 
 
 
16-10 68P02901W56-T
Jan 2010
Analysis

Optimization.
Basis Cell.
Raw Statistics LOCATION_UPDATE
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV_REQ_EMERG
CM_REESTABLISH
PAGE_RESPONSE
LOC_FLW_ON_REQ_NORM
LOC_FLW_ON_REQ_SMS
SMS_INIT_ON_SDCCH
SMS_INIT_ON_SDCCH_REQ
SMS_INIT_ON_TCH_FCS
MT_LCS_ON_SDCCH
68P02901W56-T 16-11
Jan 2010
PAGES_PER_CALL (PPC) Chapter 16: Call model statistics
PAGES_PER_CALL (P ) PC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the number of pages per call.
Formula
P
N
PAGE− REQ− FROM− MSC
i=1
Ppc =
P
N
(TOTAL− CALLS + ASSIGNMENT− REDIRECTION)
i=1
Where: Is:
N the number of cells under the BSC.
Analysis

Optimization.
Basis Cell.
Call Model/Raw PAGE_REQ_FROM_MSC.
Statistics TOTAL_CALLS.
PAGING_RATE.
CALL_DURATION.
16-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PAGES_PER_SECOND
PAGES_PER_SECOND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the number of pages per second.
Formula

PAGES− PER− SECOND =
(INTERVAL− SUM ∗ 3600)
Analysis

Optimization.
Basis Cell.
Raw Statistics PAGE_REQ_FROM_MSC.
INTERVAL_SUM.
68P02901W56-T 16-13
Jan 2010
PAGING_RATE (P) Chapter 16: Call model statistics
PAGING_RATE (P)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The paging rate is the summation of the paging messages sent to each location area averaged
over the interval period.
NOTE
Formula
P
N
i=1
P =
stat− interval− in− seconds [ith location area in BSC]
Where: Is:
N the number of location areas.
NOTE
PAGE_REQ_FROM_MSC should be the maximum per cell value for each location
area.
Analysis

Optimization.
Basis Cell.
16-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SMS_TO_CALL_RATIO (S)
SMS_TO_CALL_RATIO (S)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of SMSs to calls.
Formula
 
SM S− IN IT− ON− SDCCH
 
 + SM S− IN IT− ON− SDCCH− REQ 
 
 
 + SM S− IN IT− ON− T CH 
 
 
 
 + SM S− IN IT− ON− T CH− F CS 
 
 
 + SM S− IN IT− ON− T CH− F CS− REQ 
 
S =  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 + SM S− IN IT− ON− SDCCH− HO− IN 
 
 
 
 
 
 
68P02901W56-T 16-15
Jan 2010
Analysis Chapter 16: Call model statistics
Analysis

Optimization.
Basis Cell.
Raw Statistics SMS_INIT_ON_SDCCH
SMS_INIT_ON_SDCCH_REQ
SMS_INIT_ON_TCH
SMS_INIT_ON_TCH_FCS
CM_SERV_REQ_CALL
CM_SERV_REQ_SMS
CM_SERV_REQ_EMERG
CM_REESTABLISH
PAGE_RESPONSE
LOC_FLW_ON_REQ_NORM
LOC_FLW_ON_REQ_SMS
SMS_INIT_ON_SDDCH
SMS_INIT_ON_SDDCH_REQ
SMS_INIT_ON_TCH_FCS
MT_LCS_ON_SDCCH
16-16 68P02901W56-T
Jan 2010
Chapter
17
Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Key statistics are a set of calculated values providing an operator with a summary of system
performance during a specific statistics collection interval. They are designed to give an overall
indication of the condition of the system and allow comparison of similar time periods to detect
performance changes and trends.
Key statistics are also provided to facilitate the monitoring of the most important network
parameters. Key statistics are calculated at the OMC-R using various BSS raw statistics.
Different statistics are combined at the OMC-R using a predefined formula to produce a new
statistic. For example, various handover failure statistics may be combined and averaged over
the total number of calls to produce a handover failure rate key statistic.
Key statistics may be displayed in the Performance Management window of the OMC-R.
They key statistics are categorized into subgroups, each of which are described in Key statistics
subgroups on page 17-2.
68P02901W56-T 17-1
Jan 2010
Key statistics subgroups Chapter 17: Key statistics
Key statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Key statistics are organized into the following major subgroups:

• Call summary on page 17-2.
• Channel usage on page 17-2.
• RF loss summary on page 17-4.
• MTL utilization on page 17-4.
• Radio link on page 17-5.
Call summary
Call summary statistics are used to determine assignment and handover performance of one or
more cells. The following are call summary statistics:
• CALL_SETUP_SUCCESS_RATE on page 17-7.
• HANDOVER_FAILURE_RATE on page 17-53.
• HANDOVER_SUCCESS_RATE on page 17-55.
• IN_3G_HO_FAIL_RATE on page 17-59
• IN_3G_HO_SUCC_RATE on page 17-60
• OUT_3G_HO_FAIL_RATE on page 17-93
• OUT_3G_HO_REQ_SUCC_RATE on page 17-94
• OUT_3G_HO_SUCC_RATE on page 17-95
• SUCCESS_INTERNAL_HO on page 17-104.
• TOTAL_CALLS_KEY on page 17-120.
• UNSUCCESS_INTERNAL_HO_NOREEST on page 17-142.
• UNSUCCESS_INTERNAL_HO_REEST on page 17-143.
Channel usage
Channel usage statistics are used to determine PDTCH, SDCCH, and TCH performance levels.
The following are channel usage statistics:
17-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Channel usage
• DL_PDTCH_UTILISATION_BY_ALLOCATION on page 17-28.
• DL_PDTCH_UTILISATION_1_TS on page 17-30.
• DL_PDTCH_UTILISATION_5_TS on page 17-34
• DLDC_USAGE on page 17-38
• DL_PDTCH_UTILISATION_BY_TRAFFIC on page 17-29.
• DL_USER_TRAFFIC_EGPRS on page 17-48.
• DL_USER_TRAFFIC_GPRS on page 17-50.
• MEAN_TCH_BUSY_TIME on page 17-89.
• SDCCH_MEAN_HOLDING_TIME on page 17-99.
• SDCCH_TRAFFIC_CARRIED on page 17-101.
• TCH_BLOCKING_RATE on page 17-106.
• TCH_BLOCKING_RATE_INNER_Z on page 17-107.
• TCH_BLOCKING_RATE_OUT_ZONE on page 17-108.
• TCH_CARRIER_MEAN_HOLDING_TIME on page 17-110.
• TCH_MEAN_ARRIVAL_RATE on page 17-111.
• TCH_MEAN_HOLDING_TIME on page 17-112.
• TCH_RF_LOSS_RATE on page 17-114.
• TCH_TRAFFIC_CARRIED on page 17-116.
• UL_PDTCH_UTILISATION_BY_ALLOCATION on page 17-125.
• UL_PDTCH_UTILISATION_BY_TRAFFIC on page 17-126.
• UL_PDTCH_UTILISATION_1_TS on page 17-127.
68P02901W56-T 17-3
Jan 2010
Connection establishment Chapter 17: Key statistics
• UL_USER_TRAFFIC_EGPRS on page 17-139.
• UL_USER_TRAFFIC_GPRS on page 17-141.
Connection statistics are used to determine the number and interval of attempted and successful
assignment requests. The following are connection establishment statistics:
• ATTEMPT_IMMED_ASSIGN_PROC on page 17-6.
• MEAN_ARRIVAL_TIME_BETWEEN_CALLS on page 17-86.
• MEAN_INTER_ARRIVAL_TIME on page 17-87.
• SUCCESS_IMMED_ASSIGN_PROC on page 17-103.
RF loss summary
RF loss summary statistics are used to determine TCH assignments within a cell and the rate of
RF lost calls. The following are RF loss summary statistics:
• CELL_TCH_ALLOCATIONS on page 17-8.
• CELL_TCH_ASSIGNMENTS on page 17-9.
• RF_LOSS_RATE on page 17-96.
• SDCCH_RF_LOSS_RATE on page 17-100.
MTL utilization
MTL utilization statistics are used to provide a measure of MTL utilization from the MSC to BSS
and from the BSS to MSC. The following are MTL utilization statistics:
• HSP_MTL_UTILISATION_RX on page 17-57.
• HSP_MTL_UTILISATION_TX on page 17-58.
• MTL_UTILISATION_RX on page 17-90.
• MTL_UTILISATION_TX on page 17-91.
17-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Radio link
Radio link
Radio link statistics are used to provide a measure of the performance of the radio channels and
the level of traffic carried by the network. The following are radio link statistics:
• DL_BIAS_EGPRS on page 17-22.
• DL_BIAS_GPRS on page 17-24.
• DL_LLC_TRAFFIC_VOLUME_INDICATOR on page 17-26.
• DL_TBF_SUCCESS_RATE on page 17-43.
• LLC_ABNORMAL_TBF_RELEASES on page 17-61.
• LLC_BUFFER_OVERFLOW_RATE on page 17-62.
• LLC_DISCARDS_ON_CELL_RESELECTION on page 17-85.
• MEAN_TBF_SESSIONS on page 17-88.
• TBF_DROP_RATE_ON_PACCH_LOST on page 17-105.
• UL_LLC_TRAFFIC_VOLUME_INDICATOR on page 17-124.
Key statistics description template
Table 17-1is a template used in the key statistic descriptions:

Table 17-1 Key statistic descriptions
Key statistic Description

Description: A general description of what the statistic measures.
Formula: Arithmetic calculation of key statistic from raw statistics.
Reference: References to other sections of this document or other documents.
Usage: Lists the network operation-related uses of the statistic.
Basis: The level at which the statistic is pegged, for example, cell, BSS.
Type: The statistic type (counter, percentage, and so on).
Raw Statistic: The raw statistics associated with this key statistic. The convention used
for presenting a specific bin of a counter array statistic is statistic name
[bin name]. For example, OK_ACC_PROC[CM_REESTABLISH] is the
CM_REESTABLISH bin of the OK_ACC_PROC counter array statistic.
Note: Used to qualify or stress information.
NOTE
The template headings are used as required and are not present for all statistics.
68P02901W56-T 17-5
Jan 2010
ATTEMPT_IMMED_ASSIGN_PROC Chapter 17: Key statistics
ATTEMPT_IMMED_ASSIGN_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATTEMPT_IMMED_ASSIGN_PROC statistic tracks the number of attempted immediate

assignment procedures.
Formula
ATTEMPT− IMMED− ASSIGN− PROC = OK− ACC− PROC− SUC− RACH
Analysis

Optimization.
Basis Cell or BSS.
Type Counter.
Raw OK_ACC_PROC_SUC_RACH.
Statistics
17-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SETUP_SUCCESS_RATE
CALL_SETUP_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that results
in a successful TCH access. Network accesses which do not require a TCH are excluded, for
example, location updates, SMS, and Supplementary Service attempts.
Formula
CALL− SETUP− (TOTAL− CALLS + ASSGN− REDIRECT) ∗ 100

=  
SUCCESS− RATE CM− SERV− REQ− CALL + CM− SERV− REQ− SM S
 
 + CM− SERV− REQ− EM ERG + CM− REEST ABLISH 
 
 
 + P AGE− RESP ON SE + LOC− F LW− ON− REQ− N ORM 
 
 
 
 − SM S− IN IT− ON− SDCCH− REQ − SM S− IN IT− ON− T CH− F CS− REQ 
 
+ SM S− IN IT− ON− SIG− HO− IN− REQ − M T− LCS− ON− SDCCH
Analysis

Fault finding.
Service accessibility.
Basis Cell.
Type Percentage.
Raw ASSIGNMENT_REDIRECTION (the value used in this formula is the sum of

Statistics bins 0 to 2 of this counter array statistic).
MT_LCS_ON_SDCCH.
OK_ACC_PROC[CM_REESTABLISH].
OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_EMERG].
OK_ACC_PROC[CM_SERV_REQ_SMS].
OK_ACC_PROC[LOC_FLW_ON_REQ_NORM].
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].
OK_ACC_PROC[PAGE_RESPONSE].
OK_ACC_PROC[IMM_SETUP].
OK_ACC_PROC[IMM_SETUP2].SMS_INIT_ON_SDCCH_REQ.
SMS_INIT_ON_SDCCH_HO_IN_REQ.
SMS_INIT_ON_TCH_FCS_REQ.
TOTAL_CALLS.
68P02901W56-T 17-7
Jan 2010
CELL_TCH_ALLOCATIONS Chapter 17: Key statistics
CELL_TCH_ALLOCATIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CELL_TCH_ALLOCATIONS statistic tracks number of successful allocations of a TCH

within a cell for both call originations and hand-ins.
Formula
CELL− TCH− ALLOCATIONS = SUM (ALLOC− TCH)
Analysis

Basis Cell.
Type Counter.
Raw ALLOC_TCH.
Statistics
17-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CELL_TCH_ASSIGNMENTS
CELL_TCH_ASSIGNMENTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CELL_TCH_ASSIGNMENTS statistic is the sum of the total number of calls, the total
number of successful incoming inter-BSS call handovers, and the total number of incoming
intra-BSS call handovers.
Formula
TOTAL− CALLS + IN− INTER− BSS− HO

[IN− INTER− BSS− HO− SUCCESS− RATE] +
CELL− TCH− ASSIGNMENTS =
IN− INTRA− BSS− HO
[IN− INTRA− BSS− HO− SUCCESS− RATE]
Analysis

Basis Cell.
Type Counter.
Raw TOTAL_CALLS.
Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUCCESS_RATE].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUCCESS_RATE].
68P02901W56-T 17-9
Jan 2010
CS1_USE_DL Chapter 17: Key statistics
CS1_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
DL− RADIO− BLKS− 1− TS− CS− 1+

DL− RADIO− BLKS− 4− TS− CS− 1
CS1− USE− DL = ∗ 100
DL− RADIO− BLKS− 1− TS+
DL− RADIO− BLKS− 4− TS
Analysis
Type Percentage.
Raw statistics Bin 0 of DL_RADIO_BLKS_1_TS,
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_3_TS, and
DL_RADIO_BLKS_4_TS.
17-10 68P02901W56-T
Jan 2010
CS2_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

CS2− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-11
Jan 2010
CS3_USE_DL Chapter 17: Key statistics
CS3_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS3_USE_DL key statistic provides usage figures DL coding scheme CS-3 for GPRS.
Formula

CS3− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_4_TS.
17-12 68P02901W56-T
Jan 2010
CS4_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

CS4− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_2_TS,
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-13
Jan 2010
CS1_USE_UL Chapter 17: Key statistics
CS1_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CS1_USE_UL key statistic provides usage figures of UL coding scheme CS-1 for GPRS.
Formula
 
U L− RADIO− BLKS− 8P SK− 1− T S− CS− 1+
 
 U L− RADIO− BLKS− 8P SK− 2− T S− CS− 1+ 
 
 U L RADIO BLKS 8P SK 3 T S CS 1+ 
 − − − − − − − 
 
 
 
 U L− RADIO− BLKS− GM SK− 1− T S− CS− 1+ 
 
 
 
 
 U L− RADIO− BLKS− GM SK− 3− T S− CS− 1+ 
U L− RADIO− BLKS− GM SK− 4− T S− CS− 1+
CS1− USE− UL =   ∗ 100
U L− RADIO− BLKS− 8P SK− 1− T S+
 
 U L− RADIO− BLKS− 8P SK− 2− T S+ 
 
 U L RADIO BLKS 8P SK 3 T S+ 
 − − − − − 
 
 
 
 U L− RADIO− BLKS− GM SK− 1− T S+ 
 
 
 
 
 U L− RADIO− BLKS− GM SK− 3− T S+ 
U L− RADIO− BLKS− GM SK− 4− T S+
17-14 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
Raw statistics UL_RADIO_BLKS_8PSK_1_TS,
UL_RADIO_BLKS_8PSK_2_TS,
UL_RADIO_BLKS_8PSK_3_TS.
UL_RADIO_BLKS_GMSK_1_TS,
UL_RADIO_BLKS_GMSK_3_TS.
and their bin 0.
68P02901W56-T 17-15
Jan 2010
CS2_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
CS2− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-16 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 1.
68P02901W56-T 17-17
Jan 2010
CS3_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
CS3− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-18 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 2.
68P02901W56-T 17-19
Jan 2010
CS4_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
CS4− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-20 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 3.
68P02901W56-T 17-21
Jan 2010
DL_BIAS_EGPRS Chapter 17: Key statistics
DL_BIAS_EGPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BIAS_EGPRS statistic measures the ratio of downlink to uplink EGPRS traffic in the
cell. This provides information about the characteristics of the applications being used in a cell
in terms of the predominant direction of transmission. If the majority of cell traffic is in the
downlink direction, the optimization activities should be focused on downlink GPRS resources.
Formula
A+B
DL− BIAS− EGPRS =
C+D

A = DL− RLC− ACK− NEW− BLKS− MCS− 5+
DL− RLC− UNACK− NEW− BLKS− MCS− 1+

B = DL− RLC− UNACK− NEW− BLKS− MCS− 5+
17-22 68P02901W56-T
Jan 2010

C = UL− RLC− ACK− NEW− BLKS− MCS− 5+
UL− RLC− ACK− NEW− BLKS− MCS− 9
UL− RLC− UNACK− NEW− BLKS− MCS− 1+

D = UL− RLC− UNACK− NEW− BLKS− MCS− 5+
Analysis

Congestion.
Basis Cell.
Type Ratio.
Raw statistics Bins 4 to 12 of DL_RLC_ACK_NEW_BLKS,
DL_RLC_UNACK_NEW_BLKS,
UL_RLC_ACK_NEW_BLKS and
68P02901W56-T 17-23
Jan 2010
DL_BIAS_GPRS Chapter 17: Key statistics
DL_BIAS_GPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BIAS_GPRS statistic measures the ratio of downlink to uplink GPRS traffic in the cell.
This provides information about the characteristics of the applications being used in a cell
in terms of the predominant direction of transmission. If the majority of cell traffic is in the
downlink direction then optimization activities should be focused on downlink GPRS resources.
Formula

DL− RLC− UNACK− NEW− BLKS− CS− 1+
DL− BIAS− GPRS =
UL− RLC− UNACK− NEW− BLKS− CS− 1+

17-24 68P02901W56-T
Jan 2010
Analysis

Congestion.
Basis Cell.
Type Ratio.
Raw statistics Bins 0 to 3 of DL_RLC_ACK_NEW_BLKS, UL_RLC_ACK_NEW_BLKS,
DL_RLC_UNACK_NEW_BLKS and UL_RLC_UNACK_NEW_BLKS.
68P02901W56-T 17-25
Jan 2010
DL_LLC_TRAFFIC_VOLUME_INDICATOR Chapter 17: Key statistics
DL_LLC_TRAFFIC_VOLUME_INDICATOR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_LLC_TRAFFIC_VOLUME_INDICATOR statistic gives an indication about the volume

of downlink LLC traffic for a certain cell. The formula uses the average of the bin ranges to
calculate the traffic and therefore is an indication of the real traffic, not the exact traffic
measurement.
Formula
 (DL LLC FRAMES GB 20 + DL LLC FRAMES PCU 20) ∗ 10+ 

− − − − − − − −
 (DL− LLC− FRAMES− GB− 40 + DL− LLC− FRAMES− PCU− 40) ∗ 30+ 
 
 
 (DL− LLC− FRAMES− GB− 80 + DL− LLC− FRAMES− PCU− 80) ∗ 60+ 
  
 
 DL− LLC− FRAMES− GB− 160+ 
  ∗ 120+ 
 
 
 DL− LLC− FRAMES− PCU− 160 
  
 
  ∗ 240+ 
DL− LLC  
TRAFFIC−  
  10
=  ∗
VOLUME−  DL− LLC− FRAMES− GB− 640+  1000
  ∗ 480+ 
INDICATOR  
 DL LLC FRAMES PCU 640 
 − − − − 
  
 
  ∗ 960+ 
 
 
  
 DL− LLC− FRAMES− GB− OVER− 1280+ 
 
  ∗ 1460 
 
 DL− LLC− FRAMES− PCU− OVER− 1280 
17-26 68P02901W56-T
Jan 2010
Analysis
Usage Gb link bandwidth dimensioning.

Basis Cell.
Type Units = kB.
Raw DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_20].
statistics DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_40].
DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_80].
DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_OVER1280].
DL_LLC_FRAMES_PCU[DL_LLC_FRAMES_GB_20].
DL_LLC_FRAMES_PCU[DL_LLC_FRAMES_GB_OVER1280].
68P02901W56-T 17-27
Jan 2010
DL_PDTCH_UTILISATION_BY_ALLOCATION Chapter 17: Key statistics
DL_PDTCH_UTILISATION_BY_ALLOCATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_PDTCH_UTILISATION_BY_ALLOCATION key statistic shows the ratio of busy

PDTCHs to available PDTCHs in a cell while transmitting in the downlink direction.
NOTE
The utilization may decrease as the additional switchable PDTCH is allocated for
GPRS congested cell.
Formula
DL− PDTCH− UTILISATION− DL− BUSY− PDTCH− MEAN ∗ 100

=
BY− ALLOCATION GPRS− AVAIL− PDTCH− MEAN+
EGPRS− AVAIL− PDTCH− MEAN
Analysis
Basis Cell.
Type Percentage.
Raw statistics DL_BUSY_PDTCH_MEAN.
GPRS_AVAIL_PDTCH_MEAN.
EGPRS_AVAIL_PDTCH_MEAN.
17-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_PDTCH_UTILISATION_BY_TRAFFIC
DL_PDTCH_UTILISATION_BY_TRAFFIC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_PDTCH_UTILISATION_BY_TRAFFIC key statistic monitors the utilization of GPRS

resources per cell, to detect where the GPRS traffic including data and control blocks is high
compared to the GPRS capacity of the cell while transmitting in the downlink direction.
Formula
  
DL− RLC− ACK− NEW− BLKS+
    
 DL− RLC− UNACK− NEW− BLKS+  
  AIR− DL− 
 DL RLC NACK BLKS+  
 − − −  ∗100 +    ∗ 100
  
 DL− RLC− RETX− BLKS+  CONTROL− BLKS 
  
DL− PDTCH−
DL− RLC− DDTR− BLKS
UTILISATION− = !
GPRS− AVAIL− PDTCH− MEAN+
BY− TRAFFIC ∗ INTERVAL ∗ 3600 ∗ 50
Analysis
Usage GPRS resource allocation.

Basis Cell.
Type Percentage.
Raw statistics DL_RLC_ACK_NEW_BLKS.
DL_RLC_NACK_BLKS.
DL_RLC_DDTR_BLKS.
AIR_DL_CONTROL_BLKS.
DL_RLC_RETX_BLKS.
68P02901W56-T 17-29
Jan 2010
DL_PDTCH_UTILISATION_1_TS Chapter 17: Key statistics
DL_PDTCH_UTILISATION_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_PDTCH_UTILISATION_1_TS key statistic provides the PDTCH utilization rate for MSs
that support a maximum of 1 TS in the downlink direction. It compares the maximum possible
number of RLC/MAC blocks per terminal type with the actual sent data blocks per terminal type.
Formula
DL− PDTCH− DL− RADIO− BLKS− 1− TS

= ∗ 10000
UTILISATION− 1− TS DL− TBF− TIME− 1− TS
Analysis
Usage PDTCH utilization.

Basis Per terminal.
Type Percentage.
Raw statistics DL_RADIO_BLKS_1_TS.
DL_TBF_TIME_1_TS.
17-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_PDTCH_UTILISATION_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

= ∗ 10000
UTILISATION− 2− TS DL− TBF− TIME− 2− TS ∗ 2
Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_2_TS.
68P02901W56-T 17-31
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

= ∗ 10000
Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_3_TS.
17-32 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

= ∗ 10000
Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_4_TS.
68P02901W56-T 17-33
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
DL− RADIO− BLKS− 5− TS ∗ 10000

DL− PDTCH− UTILISATION− 5− TS =
(DL− TBF− TIME− 5− TS ∗ 5)
Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_5_TS.
17-34 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_6_TS.
68P02901W56-T 17-35
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

Analysis

Basis Per terminal.
Type Percentage.
DL_TBF_TIME_7_TS.
17-36 68P02901W56-T
Jan 2010
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

Analysis

Basis Per terminal.
Type Percentage.

DL_TBF_TIME_8_TS.
68P02901W56-T 17-37
Jan 2010
DLDC_USAGE Chapter 17: Key statistics
DLDC_USAGE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DLDC_USAGE key statistic provides usage figures for downlink dual carrier allocation.
Formula
(DL− RADIO− BLKS− DLDC ∗ 100)

DLDC− USAGE = !
DL− RADIO− BLKS− 5− T S + DL− RADIO− BLKS− 6− T S+
Analysis
Type Percentage.
Raw statistics DL_RADIO_BLKS_DLDC,
DL_RADIO_BLKS_5_TS,
DL_RADIO_BLKS_6_TS,
DL_RADIO_BLKS_7_TS,DL_RADIO_BLKS_8_TS
17-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_RLC_MAC_OVERHEAD
DL_RLC_MAC_OVERHEAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_MAC_OVERHEAD key statistic provides the percentage of overhead RLC/MAC

blocks (retransmissions due to NACK, preemptive retransmissions, super coattail blocks, control
blocks) in relation to the total amount of RLC/MAC blocks, which describes the efficiency of
the RLC/MAC layer.
Formula
  
DL− RLC− NACK− BLKS+  
   AIR− DL−
 DL− RLC− RETX− BLKS+  ∗ 100 +    ∗ 100
  
CONTROL− BLKS
DL− RLC− MAC− DL− RLC− DDTR− BLKS
=  
OVERHEAD DL− RLC− ACK− NEW− BLKS+
   
 DL− RLC− UNACK− NEW− BLKS+ 
  AIR− DL−
 DL RLC NACK BLKS+ 
 − − −  ∗ 100 +  
 
 DL− RLC− RETX− BLKS+  CONTROL− BLKS
 
DL− RLC− DDTR− BLKS
Analysis
Usage Coding Scheme Usage

Statistics, BLER Statistics and
MEAN_USER_THROUGHPUT_PER_TIMESLOT.
Type Percentage
Raw statistics DL_RLC_NACK_BLKS.
DL_RLC_RETX_BLKS.
DL_RLC_DDTR_BLKS.
AIR_DL_CONTROL_BLKS.
DL_RLC_ACK_NEW_BLKS.
68P02901W56-T 17-39
Jan 2010
DL_RLC_MAC_WINDOW_STALL Chapter 17: Key statistics
DL_RLC_MAC_WINDOW_STALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This key statistic calculates the percentage of RLC blocks, which are retransmitted due to
an RLC window stall.
Formula
DL− RLC− MAC− DL− RLC− STALLED− BLKS− CS− 1

= ∗ 100
WINDOW− STALL− CS1 DL− RLC− ACK− NEW− BLKS− CS− 1

= ∗ 100

= ∗ 100

= ∗ 100
DL− RLC− MAC− DL− RLC− STALLED− BLKS− MCS− 1

= ∗ 100
WINDOW− STALL− MCS1 DL− RLC− ACK− NEW− BLKS− MCS− 1

= ∗ 100

= ∗ 100

= ∗ 100

= ∗ 100
17-40 68P02901W56-T
Jan 2010

= ∗ 100

= ∗ 100

= ∗ 100

= ∗ 100
Analysis
Type Percentage.
Raw statistics Bins 0 to 12 of DL_RLC_STALLED_BLKS
and DL_RLC_ACK_NEW_BLKS.
68P02901W56-T 17-41
Jan 2010
DL_TBF_FAILURE_RATE Chapter 17: Key statistics
DL_TBF_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_FAILURE_RATE key statistic calculates the rate of abnormally released downlink
TBFs.
Formula
(AIR− DL− TBF− FAILURES − AIR− DL− TBF− FAILURES [bin0])

DL− TBF− FAILURE− RATE = ∗ 100
DL− PDTCH− SEIZURE in OMC-R
Pegging
Change to peg establish bin when downlink TBF is abnormally released due to
PRM_DL_PCTA_CA_ATTEMPTS_EXCEEDED in BSS.
Analysis

Basis Cell.
Type Percentage.
Raw statistics AIR_DL_TBF_FAILURES.
DL_PDTCH_SEIZURE.
17-42 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TBF_SUCCESS_RATE
DL_TBF_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_SUCCESS_RATE statistic monitors downlink TBF success.
Formula
DL− PDTCH− SEIZURE

DL− TBF− SUCCESS− RATE = ∗ 100
T BF− DL− ASGN− P ACCH + GP RS− DL− ASGN− P CCCH
+ EGP RS− DL− ASGN− P CCCH
Analysis
Usage Cell accessibility.

Basis Cell.
Type Percentage.
Raw DL_PDTCH_SEIZURE.
statistics TBF_DL_ASGN_PACCH.
GPRS_DL_ASGN_PCCCH.
EGPRS_DL_ASGN_PCCCH.
68P02901W56-T 17-43
Jan 2010
DL_TERMINAL_TYPE_ACTIVITY_1_TS Chapter 17: Key statistics
DL_TERMINAL_TYPE_ACTIVITY_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TERMINAL_TYPE_ACTIVITY_1_TS key statistic calculates the percentage of activity

per terminal type for MSs that support a maximum of 1 TS in the downlink direction.
Formula
DL− TERMINAL− TYPE− DL− TBF− TIME− 1− TS

= ∗ 100
ACTIVITY− 1− TS DL− TBF− TIME− 1− TS + DL− TBF− TIME− 2− TS
DL− TBF− TIME− 3− TS + DL− TBF− TIME− 4− TS
Analysis

THROUGHPUT_PER_TERMINAL_TYPE.
PDTCH_UTILISATION_PER_TERMINAL_TYPE.
Resource planning.
Basis Per terminal type.
Type Percentage.
Raw DL_TBF_TIME_1_TS.
statistics DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
17-44 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TERMINAL_TYPE_ACTIVITY_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula

= ∗ 100
Analysis

Resource planning.
Type Percentage.
DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
68P02901W56-T 17-45
Jan 2010
DL_TERMINAL_TYPE_ACTIVITY_3_TS Chapter 17: Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula

= ∗ 100
Analysis

Resource planning.
Type Percentage.
DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
17-46 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_TERMINAL_TYPE_ACTIVITY_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula

= ∗ 100
Analysis

Resource planning.
Type Percentage.
DL_TBF_TIME_2_TS.
DL_TBF_TIME_3_TS.
DL_TBF_TIME_4_TS.
68P02901W56-T 17-47
Jan 2010
DL_USER_TRAFFIC_EGPRS Chapter 17: Key statistics
DL_USER_TRAFFIC_EGPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_USER_TRAFFIC_EGPRS statistic gives the EGPRS downlink traffic volume, excluding
retransmitted and other overhead blocks and measured at the RLC/MAC layer.
Formula
  
  ∗ 22+ 
 
 DL− RLC− UNACK− NEW− BLKS− MCS− 1 
  
 
 DL− RLC− ACK− NEW− BLKS− MCS− 2+ 
  ∗ 28+ 
 
 
  
 DL RLC ACK NEW BLKS MCS 3+ 
 − − − − − − 
  ∗ 37+ 
 
  
 
  
 ∗ 44+ 
 
  
 DL RLC ACK NEW BLKS MCS 5+ 
 − − − − − − 
  ∗ 56+  ∗ 100
 
  
 
  ∗ 74+ 
 
 DL RLC UNACK NEW BLKS MCS 6 
 − − − − − − 
  
 
  ∗ 112+ 
 
  
 
  
 ∗ 136+ 
 DL RLC UNACK NEW BLKS MCS 8 
 − − − − − − 
  
 
  ∗ 148 
DL− USER− TRAFFIC− EGPRS =
1024
17-48 68P02901W56-T
Jan 2010
Analysis

Congestion.
Basis Cell.
Type kbytes.
Raw Statistics Bins 4 to 12 of DL_RLC_ACK_NEW_BLKS and
68P02901W56-T 17-49
Jan 2010
DL_USER_TRAFFIC_GPRS Chapter 17: Key statistics
DL_USER_TRAFFIC_GPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_USER_TRAFFIC_GPRS statistic gives the GPRS downlink traffic volume, excluding
Formula
  
  ∗ 22+ 
 DL RLC UNACK NEW BLKS CS 1 
 − − − − − − 
  
 
 DL− RLC− ACK− NEW− BLKS− CS− 2+ 
  ∗ 33+ 
 
 DL− RLC− UNACK− NEW− BLKS− CS− 2 
 
   ∗ 100
 
  ∗ 39+ 
 
 DL− RLC− UNACK− NEW− BLKS− CS− 3 
  
 
  ∗ 53 
DL− USER− TRAFFIC− GPRS=
1024
Analysis

Congestion.
Basis Cell.
Type kbytes.
Raw Statistics Bins 0 to 3 of DL_RLC_ACK_NEW_BLKS and
17-50 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_PAGING_OVERFLOW_RATE_PCH
GPRS_PAGING_OVERFLOW_RATE_PCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PAGING_OVERFLOW_RATE_PCH key statistic provides the rate of PS paging

transmitted.
Formula
GPRS− PAGING− PCH− Q− PAGE− DISCARD− PS ∗ 100

=
OVERFLOW− RATE− PCH ACCESS− PER− PCH− PS
Analysis
Basis Cell.
Type Percentage.
Raw statistics PCH_Q_PAGE_DISCARD_PS.
ACCESS_PER_PCH_PS.
68P02901W56-T 17-51
Jan 2010
GPRS_PAGING_OVERFLOW_RATE_PPCH Chapter 17: Key statistics
GPRS_PAGING_OVERFLOW_RATE_PPCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PAGING_OVERFLOW_RATE_PPCH key statistic provide the rate of PS paging

transmitted.
Formula
GPRS− PAGING− PPCH− Q− PAGE− DISCARD− PS ∗ 100

=
OVERFLOW− RATE− PPCH ACCESS− PER− PPCH− PS
Analysis
Basis Cell.
Type Percentage.
Raw statistics PPCH_Q_PAGE_DISCARD_PS.
ACCESS_PER_PPCH_PS.
17-52 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HANDOVER_FAILURE_RATE
HANDOVER_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HANDOVER_FAILURE_RATE statistic tracks the percentage of handovers that are

attempted from the source cell (the cell for which the statistic is presented) that failed to
successfully reach the target cell and failed to successfully recover to the source cell, that is,
the handover failed and the call dropped. A handover attempt is counted when a handover
command is sent to the MS.
Congestion on the target cell does not result in the BSS sending a handover command to the MS
therefore this measurement is not impacted by target cell congestion.
Formula
INTRA− CELL− HO [INTRA− CELL− HO− LOSTMS] +

OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− LOSTMS] +
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT] −
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− SUC] −
HANDOVER−
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− RETURN] ∗
FAILURE− = 100%
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT] +
RATE  
 
 INTRA− CELL− HO− ATMPT− HR− FR+ 
INTRA− CELL− HO 

+

 INTRA− CELL− HO− ATMPT− FR− HR+ 
INTRA− CELL− HO− ATMPT− HR− HR
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− ATMPT]
68P02901W56-T 17-53
Jan 2010
Analysis Chapter 17: Key statistics
Analysis

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.
Raw INTRA_CELL_HO (the value used in this formula is bin 6 and the sum of bins
Statistics 1 to 4 of this counter array statistic).
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].
17-54 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HANDOVER_SUCCESS_RATE
HANDOVER_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HANDOVER_SUCCESS_RATE statistic tracks the percentage of handovers attempted from

the source cell (cell for which the statistic is presented) that successfully reached the target cell.
A handover attempt is counted when a handover command is sent to the MS. This key statistic
includes inter-BSS Handover and the 2G->3G Handover (because of OUT_INTER_BSS_HO
includes 2G->3G handover).
Formula
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− SUC] +

INTRA− CELL− HO [INTRA− CELL− HO− SUC] +
HANDOVER− OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− SUC]
= ∗100%
SUCCESSRATE OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT]+
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− ATMPT] +
INTRA− CELL− HO [INTRA− CELL− HO − ATMPT− FR− FR] +
INTRA− CELL− HO [INTRA− CELL− HO− ATMPT− HR− HR] +
INTRA− CELL− HO [INTRA− CELL− HO− ATMPT− FR− HR] +
INTRA− CELL− HO [INTRA− CELL− HO− ATMPT− HR− FR] +
INTRA− CELL− HO− ATMPT− SD− TO− SD
68P02901W56-T 17-55
Jan 2010
For pure 2G-2G HSR, the suggested formula is:
2G− HANDOVER SUCCESS RATE (%) =
 
 
 
 
 
 OUT− INTER− BSS− HO− SUC − NUM− HO− TO− 3G− SUCCESS+ 
 
 INTRA− CELL− HO− SUC = OUT− INTRA− BSS− HO− SUC 
 
  ∗100
 OUT− INTER− BSS− HO− ATMPT − NUM− HO− TO− 3G− SUCCESS+ 
 
 
 INTRA− CELL− HO− ATMPT− FR− FR+INTRA− CELL− HO− ATMPT− HR− HR+ 
 
 
 INTRA− CELL− HO− ATMPT− HR− FR + INTRA− CELL− HO− ATMPT− FR− HR+ 
OUT− INTRA− BSS− HO− ATMPT+INTRA− CELL− HO− ATMPT− SD− TO− SD
NOTE
HANDOVER_SUCCESS_RATE + HANDOVER_FAILURE_RATE are not equal to
100% because the calls that fail and recover to the source cell are not included in
either of these key statistics.
Analysis

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.
Raw INTRA_CELL_HO (the value used in this formula is bin 5 and the sum of bins
Statistics 1 to 4 of this counter array statistic).
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].
17-56 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HSP_MTL_UTILISATION_RX
HSP_MTL_UTILISATION_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HSP_MTL_UTILISATION_RX statistic provides a measure of high speed MTL utilization

for the MSC to BSS direction.
Formula
HSP− MTL− (MTP− MSU− RX ∗ 9 + MTP− SIF− SIO− RX + SIB− RX ∗ 10)

= ∗ 800
UTILISATION− RX (MTP− LINK− INS ∗ MTL− LINK− RATE)
NOTE
MTL_LINK_RATE is the bandwidth of MTL. It equals to MTL_Rate * 64. The MTL_Rate
indicates the number of DS0 channels equipped as MTL. For example, if MTL_Rate
is 1, it means one DS0 channel is equipped as MTL, the bandwidth of MTL is 1 * 64
kbps = 64 kbps. If MTL_Rate is 31, the whole span of E1 is equipped as MTL. This
formula is valid only when MTL_Rate is 31.
Analysis
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_RX.
Statistics MTP_SIF_SIO_RX.
SIB_RX.
MTP_LINK_INS.
68P02901W56-T 17-57
Jan 2010
HSP_MTL_UTILISATION_TX Chapter 17: Key statistics
HSP_MTL_UTILISATION_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HSP_MTL_UTILISATION_TX statistic provides a measure of high speed MTL utilization

for the BSS to MSC direction.
Formula
HSP− MTL− (MTP− MSU− TX ∗ 9 + MTP− SIF− SIO− TX + SIB− TX ∗ 10)

= ∗ 800
UTILISATION− TX (MTP− LINK− INS ∗ MTL− LINK− RATE)
NOTE
Analysis
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_TX.
Statistics MTP_SIF_SIO_TX.
SIB_TX.
MTP_LINK_INS.
17-58 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IN_3G_HO_FAIL_RATE
IN_3G_HO_FAIL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_3G_HO_FAIL_RATE measures the failure rate of handover from 3G to 2G. This statistic
is the inverse of incoming 3G handover success rate.
Formula
(NUM− HO− FROM− 3G− SUCC ESS ∗ 100)

IN− 3G− FAIL− RATE = 100 −
NUM− HO− FROM− 3G− ATTEMPTS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics NUM_HO_FROM_3G_SUCCESS.
NUM_HO_FROM_3G_ATTEMPTS.
68P02901W56-T 17-59
Jan 2010
IN_3G_HO_SUCC_RATE Chapter 17: Key statistics
IN_3G_HO_SUCC_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_3G_HO_SUCC_RATE measures the success rate of incoming handover from 3G to 2G

system. It is calculated as a ratio of the number of successful incoming handovers and the
number of incoming attempts. This must be made available as per cell, per BSS, and network
Key Performance Indicator (KPI).
Formula
NUM− HO− FROM− 3G− SUCCESS

IN− 3G− HO− SUCC− RATE = ∗ 100
NUM− HO− FROM− 3G− ATTEMPTS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics NUM_HO_FROM_3G_SUCCESS.

NUM_HO_FROM_3G_ATTEMPTS.
17-60 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LLC_ABNORMAL_TBF_RELEASES
LLC_ABNORMAL_TBF_RELEASES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LLC_ABNORMAL_TBF_RELEASES statistic calculates the percentage of discarded LLC

blocks due to abnormal TBF releases.
Formula
 
 PDU− DISCARD− LLC− 
 
LLC− ABNORMAL−  [PDU− DISCARD− LLC− ABNORMAL− TBFREL] 
=
    ∗ 100

TBF− RELEASES  DL− LLC− FRAMES− PCU+ 
  DL− LLC− FRAMES− GB+  ∗ 10 
UL− LLC− FRAMES
Analysis
Usage Tracking radio problems/failures.

Utilization.
Basis Cell.
Type Percentage.
Raw statistics PDU_DISCARD_LLC[PDU_DSCRD_LLC_ABNORM_TBFREL]
DL_LLC_FRAMES_PCU
DL_LLC_FRAMES_GB
UL_LLC_FRAMES.
68P02901W56-T 17-61
Jan 2010
LLC_BUFFER_OVERFLOW_RATE Chapter 17: Key statistics
LLC_BUFFER_OVERFLOW_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LLC_BUFFER_OVERFLOW_RATE statistic calculates the percentage of discarded LLC

blocks due to buffer overflows.
Formula
!
P DU− DSCRD− LLC− CELL− BU F− OV RF LW +
∗ 100
LLC− BUFFER P DU− DSCRD− LLC− M S− BU F− OV RF LW
=  
OVERFLOW− RATE DL− LLC− FRAMES− PCU+
 DL− LLC− FRAMES− GB+  ∗ 10
UL− LLC− FRAMES
Analysis
Usage Buffer management.

Basis Cell.
Type Percentage.
Raw PDU_DISCARD_LLC
statistics [PDU_DSCRD_LLC_CELL_BUF_OVRFLW].
PDU_DISCARD_LLC[PDU_DSCRD_LLC_MS_BUF_OVRFLW].
DL_LLC_FRAMES_PCU.
DL_LLC_FRAMES_GB.
UL_LLC_FRAMES.
17-62 68P02901W56-T
Jan 2010
MCS1_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MCS1_USE_DL key statistic provides usage figures for DL coding scheme CS-1 for EGPRS.
Formula
DL− RADIO− BLKS− 1− TS− MCS− 1+

DL− RADIO− BLKS− 4− TS− MCS− 1
MCS1− USE− DL = ∗ 100
Analysis
Type Percentage.
and their bin 4.
68P02901W56-T 17-63
Jan 2010
MCS2_USE_DL Chapter 17: Key statistics
MCS2_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS2− USE− DL = ∗ 100
Analysis
Type Percentage.
Raw statistics DL_RADIO_BLKS_1_TS_MCS_2.
DL_RADIO_BLKS_2_TS_MCS_2.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
17-64 68P02901W56-T
Jan 2010
MCS3_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS3− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-65
Jan 2010
MCS4_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS4− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
17-66 68P02901W56-T
Jan 2010
MCS5_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS5− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-67
Jan 2010
MCS6_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS6− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
17-68 68P02901W56-T
Jan 2010
MCS7_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS7− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-69
Jan 2010
MCS8_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS8− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
17-70 68P02901W56-T
Jan 2010
MCS9_USE_DL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula

MCS9− USE− DL = ∗ 100
Analysis
Type Percentage.
DL_RADIO_BLKS_1_TS.
DL_RADIO_BLKS_2_TS.
DL_RADIO_BLKS_3_TS.
DL_RADIO_BLKS_4_TS.
68P02901W56-T 17-71
Jan 2010
MCS1_USE_UL Chapter 17: Key statistics
MCS1_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MCS1_USE_UL key statistic provides usage figures of UL coding scheme MCS-1 for EGPRS.
Formula
 
U L− RADIO− BLKS− 8P SK− 1− T S− M CS− 1+
 
 U L− RADIO− BLKS− 8P SK− 2− T S− M CS− 1+ 
 
 U L RADIO BLKS 8P SK 3 T S M CS 1+ 
 − − − − − − − 
 
 
 
 U L− RADIO− BLKS− GM SK− 1− T S− M CS− 1+ 
 
 
 
 
 U L− RADIO− BLKS− GM SK− 3− T S− M CS− 1+ 
U L− RADIO− BLKS− GM SK− 4− T S− M CS− 1+
MCS1− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-72 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 4.
68P02901W56-T 17-73
Jan 2010
MCS2_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MCS2_USE_UL key statistic provides usage figures of UL coding scheme CS-2 for EGPRS.
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
MCS2− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-74 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 5.
68P02901W56-T 17-75
Jan 2010
MCS3_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
MCS3− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-76 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 6.
68P02901W56-T 17-77
Jan 2010
MCS4_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 − − − − − − − 
 
 
 
 
 
 
 
MCS4− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
17-78 68P02901W56-T
Jan 2010
Analysis
Type Percentage.
and their bin 7.
68P02901W56-T 17-79
Jan 2010
MCS5_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 
 U L− RADIO− BLKS− 8P SK− 3− T S− M CS− 5+ 
MCS5− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
Analysis
Type Percentage.
Raw statistics UL_RADIO_BLKS_8PSK_1_TS_MCS_5,
UL_RADIO_BLKS_8PSK_2_TS_MCS_5,
UL_RADIO_BLKS_8PSK_3_TS_MCS_5.
UL_RADIO_BLKS_8PSK_4_TS_MCS_5
17-80 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MCS6_USE_UL
MCS6_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 
MCS6− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
Analysis
Type Percentage.
68P02901W56-T 17-81
Jan 2010
MCS7_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 
MCS7− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
Analysis
Type Percentage.
17-82 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MCS8_USE_UL
MCS8_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 
MCS8− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
Analysis
Type Percentage.
68P02901W56-T 17-83
Jan 2010
MCS9_USE_UL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
 
 
 
 
MCS9− USE− UL =   ∗ 100
 
 
 − − − − − 
 
 
 
 
 
 
 
Analysis
Type Percentage.
17-84 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application LLC_DISCARDS_ON_CELL_RESELECTION
LLC_DISCARDS_ON_CELL_RESELECTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LLC_DISCARDS_ON_CELL_RESELECTION statistic calculates the percentage of discarded

LLC blocks due to cell reselections.
Formula
 
P DU− DSCRD− LLC− RESEL− IN AREA
 
 + P DU− DSCRD− LLC− RESEL− OU T AREA 
 
LLC− DISCARDS + P DU− DSCRD− LLC− IN AB− M OV E− P KT
ON− CELL =   ∗ 100
DL− LLC− FRAMES− PCU
RESELECTION  +DL− LLC− FRAMES− GB  ∗ 10
+UL− LLC− FRAMES
Analysis
Usage Mobility management.

Handover.
Basis Cell.
Type Percentage.
Raw PDU_DISCARD_LLC[PDU_DSCRD_LLC_RESEL_INAREA].
statistics PDU_DISCARD_LLC[PDU_DSCRD_LLC_RESEL_OUTAREA].
DL_LLC_FRAMES_PCU.
DL_LLC_FRAMES_GB.
UL_LLC_FRAMES.
68P02901W56-T 17-85
Jan 2010
MEAN_ARRIVAL_TIME_BETWEEN_CALLS Chapter 17: Key statistics
MEAN_ARRIVAL_TIME_BETWEEN_CALLS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_ARRIVAL_TIME_BETWEEN_CALLS statistic tracks the amount of time between

consecutive normal and emergency call attempts originated from an MS.
Formula
MEAN− ARRIVAL− TIME SUM (INTERVAL) ∗

= 3600
BETWEEN− CALLS CHAN− REQ− CAUSE− ATMPT
[ORIGINATING− CALL] +
CHAN− REQ− CAUSE− ATMPT
[EMERGENCY− CALL]
Analysis

Fault finding.
Optimization.
Basis Cell.
Type Duration (in seconds).
Raw INTERVAL.
Statistics CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL].
CHAN_REQ_CAUSE_ATMPT[EMERGENCY_CALL].
17-86 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MEAN_INTER_ARRIVAL_TIME
MEAN_INTER_ARRIVAL_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_INTER_ARRIVAL_TIME statistic is the arithmetic mean of the sum of the time
intervals between consecutive normal, SMS, supplementary, and emergency requests for service.
Formula
MEAN− INTER− SUM (INTERVAL) ∗

= 3600
ARRIVAL− TIME OK− ACC− PROC [CM− SERV− REQ− CALL] +
OK− ACC− PROC [CM− SERV− REQ− SMS] +
OK− ACC− PROC [CM− SERV− REQ− SUPP] +
OK− ACC− PROC [CM− SERV− REQ− EMERG]
Analysis

Optimization.
Basis BSS.
Raw INTERVAL.
Statistics OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_SUPP].
68P02901W56-T 17-87
Jan 2010
MEAN_TBF_SESSIONS Chapter 17: Key statistics
MEAN_TBF_SESSIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TBF_SESSIONS statistic indicates the average number of ongoing TBFs at the end of each 6
second duration on a PRP board.
Formula
MEAN− TBF− SESSIONS = TBF− SESSIONS− MEAN
Analysis
Usage PRP bandwidth.

Basis PRP.
Type Gauge.
Raw TBF_SESSIONS.
statistics
17-88 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MEAN_TCH_BUSY_TIME
MEAN_TCH_BUSY_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_TCH_BUSY_TIME statistic tracks the arithmetic mean of the busy time for traffic
channels in a cell.
Formula
(BUSY− TCH− MEAN)

MEAN− TCH− BUSY− TIME = ∗ INTERVAL ∗ 3600
(AVAILABLE− TCH− MEAN)
Analysis
Usage Optimization.
Network planning.
Basis Cell.
Raw AVAILABLE_TCH.
Statistics BUSY_TCH.
68P02901W56-T 17-89
Jan 2010
MTL_UTILISATION_RX Chapter 17: Key statistics
MTL_UTILISATION_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTL_UTILISATION_RX statistic provides a measure of 64K MTL utilization for the MSC to
BSS direction.
Formula
MTL− (MTP− MSU− RX ∗ 6 + MTP− SIF− SIO− RX + SIB− RX ∗ 7)

= ∗ 800
UTILISATION− RX (MTP− LINK− INS ∗ MTL− LINK− RATE)
An explanation as to how the formula was derived is shown in the following expanded version:
((MTP− MSU− RX ∗ 6bytes/msu) + MTP− SIF− SIO− RX) +

MTL− (SIB− RX ∗ 7bytes/sib)
= ∗ 8bits/bytes
UTILISATION− RX (MTP− LINK− INS/1000) ∗ (MTL− Rate ∗ 64000bps)
NOTE
Analysis
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_RX.
Statistics MTP_SIF_SIO_RX.
SIB_RX.
MTP_LINK_INS.
17-90 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTL_UTILISATION_TX
MTL_UTILISATION_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTL_UTILISATION_TX statistic provides a measure of 64K MTL utilization for the BSS to
MSC direction.
Formula
MTL− (MTP− MSU− TX ∗ 6 + MTP− SIF− SIO− TX + SIB− TX ∗ 7)

= ∗ 800
UTILISATION− TX (MTP− LINK− INS ∗ MTL− LINK− RATE)
An explanation as to how the formula was derived is shown in the following expanded version:
((MTP− MSU− TX ∗ 6bytes/msu) + MTP− SIF− SIO− TX) +

MTL− (SIB− TX ∗ 7bytes/sib)
= ∗ 8bits/bytes
UTILISATION− TX (MTP− LINK− INS/1000) ∗ (MTL− Rate ∗ 64000bps)
NOTE
Analysis
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_TX.
Statistics MTP_SIF_SIO_TX.
SIB_TX.
MTP_LINK_INS.
68P02901W56-T 17-91
Jan 2010
NC2_CELL_RESELECTION_SUCCESS_RATE Chapter 17: Key statistics
NC2_CELL_RESELECTION_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NC2_CELL_RESELECTION_SUCCESS_RATE key statistic can be used to identify

problems associated with the Network Controlled cell reselection feature.
Formula
NC2− CELL− RESELECTION− 1 − GPRS− CELL− RESELECT− FAIL

= ∗ 100
SUCCESS− RATE GPRS− CELL− RESELECT− ATMPT
Analysis
Usage Network controlled cell re-selection.

Type Percentage.
Raw statistics GPRS_CELL_RESELECT_FAIL.
GPRS_CELL_RESELECT_ATMPT.
17-92 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_3G_HO_FAIL_RATE
OUT_3G_HO_FAIL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_3G_HO_FAIL_RATE measures the failure rate of handover from 2G to 3G system.

This statistic is the inverse of outgoing 3G handover success rate.
Formula
(NUM− HO− TO− 3G− SUCCESS ∗ 100)

OUT− 3G− HO− FAIL− RATE = 100 −
NUM− HO− TO− 3G− RES− ALLOC− SUCC
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics NUM_HO_TO_3G_SUCCESS.
NUM_HO_TO_3G_RES_ALLOC_SUCC.
68P02901W56-T 17-93
Jan 2010
OUT_3G_HO_REQ_SUCC_RATE Chapter 17: Key statistics
OUT_3G_HO_REQ_SUCC_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_3G_HO_REQ_SUCC_RATE measures the success rate of handover request from BSS,
which results in MSC to act on it and a resource is allocated in 3G to receive the mobile. This
statistic measures, the response of the UTRAN system in accommodating handover request
from 2G system.
Formula

OUT− 3G− HO− REQ− SUCC− RATE = ∗ 100
NUM− HO− TO− 3G− ATTEMPTS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics NUM_HO_TO_3G_RES_ALLOC_SUCC.
NUM_HO_TO_3G_ATTEMPTS.
17-94 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_3G_HO_SUCC_RATE
OUT_3G_HO_SUCC_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_3G_HO_SUCC_RATE statistic measures the success rate of handover from 2G to 3G

system. It is calculated as a ratio of the number of successful outgoing handovers and the
number of handover attempts to 3G system. This statistic must be available as per cell, per BSS,
and per network Key Performance Indicator (KPI).
Formula
NUM− HO− TO− 3G− SUCCESS

OUT− 3G− HO− SUCC− RATE = ∗ 100
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics NUM_HO_TO_3G_SUCCESS.
NUM_HO_TO_3G_RES_ALLOC_SUCC.
68P02901W56-T 17-95
Jan 2010
RF_LOSS_RATE Chapter 17: Key statistics
RF_LOSS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_LOSS_RATE statistic compares the total number of RF losses (while using both SDCCH
and TCH) with the number of calls set-up in the cell plus the number of calls handed in to the
cell. It indicates the cell/system ability to preserve calls.
Formula
 
RF− LOSSES− SD
 
 + RF− LOSSES− T CH− ROLL 
 
+ RF− LOSSES− T CH− SIG− ROLL
(RF− LOSS− RATE)=   ∗100
 
 
 
 + CM− SERV− REQ− SU P P 
 
 + CM SERV REQ EM ERG 
 − − − 
 
 
 
 + LOCAT ION− U P GRADE 
 
 
 
 
 + IM SI− DET ACH 
 
 + IN IN T ER BSS HO SU C 
 − − − − 
+ IN− IN T RA− BSS− HO− SU C
NOTE
Handovers may relate to SDCCHs (as opposed to TCHs). In this case, the accuracy
of the statistic is affected. For the most part this effect is expected to be negligible.
nTCH = Number of TCHs in cell.
17-96 68P02901W56-T
Jan 2010
Analysis

Fault finding and optimization.
Basis Cell.
Type Percentage.
Raw IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUCCESS_RATE].
Statistics IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUCCESS_RATE].
OK_ACC_PROC.
RF_LOSSES_TCH.
RF_LOSSES_SD.
68P02901W56-T 17-97
Jan 2010
SDCCH_BLOCKING_RATE Chapter 17: Key statistics
SDCCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an

SDCCH that were blocked due to no available SDCCH resources. This statistic includes
incoming SDCCH handover attempts.
Formula
(ALLOC− SDCCH− FAIL) ∗

SDCCH− BLOCKING− RATE = 100
(ALLOC− SDCCH + ALLOC− SDCCH− FAIL)
Analysis
Usage Service Accessibility.

Quality of Service monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw ALLOC_SDCCH.
Statistics ALLOC_SDCCH_FAIL.
17-98 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_MEAN_HOLDING_TIME
SDCCH_MEAN_HOLDING_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls on SDCCH

channels in seconds.
Formula
(BUSY− SDCCH− MEAN ∗ INTERVAL− SUM)

SDCCH− MEAN− HOLDING− TIME =
ALLOC− SDCCH
NOTE
Analysis

Optimization.
Basis Cell.
Type Total Time (in seconds).
Raw Statistics ALLOC_SDCCH.
BUSY_SDCCH.
INTERVAL_SUM (total statistics collection interval, measured in hours).
68P02901W56-T 17-99
Jan 2010
SDCCH_RF_LOSS_RATE Chapter 17: Key statistics
SDCCH_RF_LOSS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_RF_LOSS_RATE statistic compares the total number of RF losses (while using
an SDCCH), as a percentage of the total number of call attempts for SDCCH channels. This
statistic is intended to give an indication of how good the cell/system is at preserving calls.
Formula
SDCCH− RF− RF− LOSSES− SD

= ∗ 100
LOSS− RATE ALLOC− SDCCH−
(CHAN− REQ− MS− FAIL [1] + ...+
CHAN− REQ− MS− FAIL [nSDCCH]
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_SDCCH.
Statistics CHAN_REQ_MS_FAIL [SDCCH].
RF_LOSSES_SD.
17-100 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED
SDCCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHs

measured in Erlangs.
Formula
SDCCH− TRAFFIC− CARRIED = BUSY− SDCCH− MEAN
For an individual cell over m statistics intervals:
P
m
BUSY− SDCCH− MEAN [ ]
=1
SDCCH− TRAFFIC− CARRIED =
m
For n cells over an individual statistics interval:
n
X
SDCCH− TRAFFIC− CARRIED = BUSY− SDCCH− MEAN [ ]
=1
For n cells over m statistics intervals:
 
P
m
n
X  =1 BUSY − SDCCH− MEAN [ ]

SDCCH− TRAFFIC− CARRIED =  
 m 
=1
NOTE
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic channels
during a collection interval. Where BUSY_SDCCH_MEAN [x] is BUSY_SDCCH_MEAN
for statistical interval x.
68P02901W56-T 17-101
Jan 2010
Analysis
Usage RF Loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.
17-102 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SUCCESS_IMMED_ASSIGN_PROC
SUCCESS_IMMED_ASSIGN_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SUCCESS_IMMED_ASSIGN_PROC statistic tracks the number of successful immediate

assignment procedures.
Formula
OK− ACC− PROC− SUC− RACH−

SUCCESS− IMMED− ASSIGN− PROC =
CHAN− REQ− MS− BLK−
Analysis

Optimization.
Basis Cell or BSS.
Type Counter.
Raw CHAN_REQ_MS_BLK
Statistics OK_ACC_PROC_SUC_RACH.
68P02901W56-T 17-103
Jan 2010
SUCCESS_INTERNAL_HO Chapter 17: Key statistics
SUCCESS_INTERNAL_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SUCCESS_INTERNAL_HO statistic tracks the number of successful internal handovers.
Formula
INTRA− CELL− HO [INTRA− CELL− HO− SUC] +

SUCCESS− INTERNAL− HO =
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− SUC]
Analysis

Optimization.
Quality of service.
Basis Cell.
Type Counter.
Raw INTRA_CELL_HO[INTRA_CELL_HO_SUC].
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].
17-104 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TBF_DROP_RATE_ON_PACCH_LOST
TBF_DROP_RATE_ON_PACCH_LOST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TBF_DROP_RATE_ON_PACCH_LOST statistic represents the percentage of TBFs that are

released when its switchable PDCH is converted to TCH. This key statistic shows the direct
effect of timeslot stealing. An increased percentage of dropped TBFs due to switches indicates
that more fixed PDTCHs should be configured.
NOTE
• Only those TBFs, whose PACCH are lost due to the switch to TCH are considered.
• This statistic value may increase as the raw statistic TBF_REL_PACCH_LOST
may increase.
Formula
 
 
TBF− DROP− RATE  TBF− REL− PACCH− LOST 
=
 DL PDTCH SEIZURE + UL PDTCH SEIZURE
 ∗ 100

ON− PACCH− LOST  − − − − 
AIR− DL− TBF− FAILURES− ET + AIR− UL− TBF− FAILURES− ET
Analysis
Usage PDTCH configuration.

Utilization.
Basis Cell.
Type Percentage.
Raw TBF_REL_PACCH_LOST
statistics DL_PDTCH_SEIZURE
UL_PDTCH_SEIZURE
AIR_DL_TBF_FAILURES_ET
AIR_UL_TBF_FAILURES_ET
68P02901W56-T 17-105
Jan 2010
TCH_BLOCKING_RATE Chapter 17: Key statistics
TCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_BLOCKING_RATE statistic provides the percentage of all requests for TCH resources
(originations and handins) which fail due to no available TCH resources.
Formula
ALLOC− TCH− FAIL − ASSIGN− REQ− OZ− OZ−

ASSIGN− REQ− IZ− IZ − ASSIGN− REQ− OZ− IZ−
ASSIGN− REQ− IZ− OZ − HO− REQ− OZ− OZ−
TCH− PREEMPT− NO− Q− ALLOC
TCH− BLOCKING− RATE = ∗100
ALLOC− TCH + ALLOC− TCH− FAIL−
ASSIGN− REQ− OZ− OZ − ASSIGN− REQ− IZ− IZ−
ASSIGN− REQ− OZ− IZ − ASSIGN− REQ− IZ− OZ−
HO− REQ− OZ− OZ − TCH− PREEMPT− NO− Q− ALLOC
Analysis

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_TCH.
Statistics ALLOC_TCH_FAIL.
ASSIGN_REQ_OZ_OZ.
ASSIGN_REQ_IZ_IZ.
ASSIGN_REQ_OZ_IZ.
ASSIGN_REQ_IZ_OZ.
HO_REQ_OZ_OZ.
TCH_PREEMPT_NO_Q_ALLOC.
17-106 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_BLOCKING_RATE_INNER_Z
TCH_BLOCKING_RATE_INNER_Z
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_BLOCKING_RATE_INNER_Z statistic provides the percentage of all requests for

inner zone TCH resources (originations and hand ins) which fail due to no available TCH
resources.
Formula
ALLOC− TCH− FAIL− INNER− Z−

ASSIGN− REQ− IZ− IZ−
ASSIGN− REQ− IZ− OZ−
TCH− BLOCKING− TCH− PREEMPT− NO− Q− ALLOC− IZ ∗
= 100
RATE− INNER− Z ALLOC− TCH− INNER− Z+
ALLOC− TCH− FAIL− INNER− Z−
ASSIGN− REQ− IZ− IZ−
ASSIGN− REQ− IZ− OZ−
TCH− PREEMPT− NO− Q− ALLOC− IZ
Analysis

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_TCH_INNER_ZONE.
Statistics ALLOC_TCH_FAIL_INNER_ZONE.
TCH_PREEMPT_NO_Q_ALLOC_IZ.
ASSIGN_REQ_IZ_IZ.
ASSIGN_REQ_IZ_OZ.
68P02901W56-T 17-107
Jan 2010
TCH_BLOCKING_RATE_OUT_ZONE Chapter 17: Key statistics
TCH_BLOCKING_RATE_OUT_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_BLOCKING_RATE_OUT_ZONE statistic provides the percentage of all requests

for outer zone TCH resources (originations and hand ins) which fail due to no available TCH
resources.
Formula
 
ALLOC− T CH− F AIL−
 
 ALLOC− T CH− F AIL− IN N ER− Z− 
 
 ASSIGN REQ OZ OZ− 
 − − − 
 
 ASSIGN− REQ− OZ− IZ− 
 
 
 HO− REQ− OZ − OZ− 
 
 
 T CH− P REEM P T− N O− Q− ALLOC− ALL− 
 
TCH− BLOCKING− T CH− P REEM P T− N O− Q− ALLOC− IZ ∗
=   100
RATE− OUT− ZONE ALLOC− T CH−
 
 ALLOC− T CH− IN N ER− Z+ 
 
 
 ALLOC− T CH− F AIL− 
 
 ALLOC T CH F AIL IN N ER Z− 
 − − − − 
 
 ASSIGN− REQ− OZ− OZ− 
 
 
 
 
 HO− REQ− OZ − OZ− 
  
 
 T CH− P REEM P T− N O− Q− ALLOC− ALL− 
 
T CH− P REEM P T− N O− Q− ALLOC− IZ
17-108 68P02901W56-T
Jan 2010
Analysis

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_TCH_FAIL.
Statistics ALLOC_TCH_FAIL_INNER_ZONE.
ALLOC_TCH.
ALLOC_TCH_INNER_ZONE.
TCH_PREEMPT_NO_Q_ALLOC_ALL.
TCH_PREEMPT_NO_Q_ALLOC_IZ.
ASSIGN_REQ_OZ_IZ.
ASSIGN_REQ_OZ_OZ.
HO_REQ_OZ_OZ.
68P02901W56-T 17-109
Jan 2010
TCH_CARRIER_MEAN_HOLDING_TIME Chapter 17: Key statistics
TCH_CARRIER_MEAN_HOLDING_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CARRIER_MEAN_HOLDING_TIME statistic tracks the average duration of calls

in traffic channel (TCH) carriers in seconds.
Formula
TCH− CARRIER− MEAN BUSY− TCH− CARR ∗ (INTERVAL− SUM ∗ 3600)

=
HOLDING− TIME ALLOC− TCH− CARR
Analysis

Basis Carrier.
Raw BUSY_TCH_CARR_MEAN.
Statistics INTERVAL_SUM.
ALLOC_TCH_CARR.
17-110 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_MEAN_ARRIVAL_RATE
TCH_MEAN_ARRIVAL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate in calls per
interval for the cell in question.
Formula
 
ALLOC− T CH + ALLOC− T CH− F AIL−
 
 ASSIGN− REQ− OZ− OZ− 
 
 ASSIGN REQ IZ IZ− 
 − − − 
 
 
 
 ASSIGN− REQ− IZ− OZ− 
 
 
 HO− REQ− OZ− OZ− 
T CH− P REEM P T− N O− Q− ALLOC− ALL
TCH− MEAN− ARRIVAL− RATE =
INTERVAL− SUM
NOTE
The arrival rate of calls includes both calls set up on traffic channels within a cell and
handovers into the cell.
Analysis

Basis Cell.
Type Counter (calls/interval).
Raw ALLOC_TCH.
Statistics ALLOC_TCH_FAIL.
TCH_Q_REMOVED.
68P02901W56-T 17-111
Jan 2010
TCH_MEAN_HOLDING_TIME Chapter 17: Key statistics
TCH_MEAN_HOLDING_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls on traffic

channels (TCH) in seconds.
Formula
Cell Level
BUSY− TCH− MEAN∗

TCH− MEAN− INTERVAL− LENGTH
=
HOLDING− TIME TOTAL− CALLS+
[IN− INTRA− BSS− HO− SUCCESS− RATE] +
IN− INTER− BSS− HO
[IN− INTER− BSS− HO− SUCCESS− RATE]
BSS Level

TCH− MEAN INTERVAL− LENGTH
=
ASSIGNMENT− REDIRECTION [DIRECTED− RETRY] +
ASSIGNMENT− REDIRECTION [DURING− ASSIGNMENT] +
ASSIGNMENT− REDIRECTION [MULTIBAND− BAND] +
IN− INTER− BSS− HO
Network Level

TCH− MEAN− INTERVAL− LENGTH
=
ASSIGNMENT− REDIRECTION [DURINGASSIGNMENT] +
ASSIGNMENT− REDIRECTION [MULTIBAND− BAND]
17-112 68P02901W56-T
Jan 2010
NOTE
The numerator and denominator may peg on different intervals (where a call extends
across multiple collection boundaries). This affects the accuracy of the statistic for
the period. Therefore, this statistic should be used as a trend rather than focusing
on specific values.
Analysis

Basis Cell, BSS, or network.
Type Duration.
Raw BUSY_TCH_MEAN.
Statistics TOTAL_CALLS.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUCCESS_RATE].
ASSIGNMENT_REDIRECTION (the value used in this formula is the sum of
bins 0 to 2 of this counter array statistic).
68P02901W56-T 17-113
Jan 2010
TCH_RF_LOSS_RATE Chapter 17: Key statistics
TCH_RF_LOSS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that are abnormally
released due to a failure on the radio interface.
Formula
Cell Level
TCH− RF− RF− LOSSES− TCH ∗

= 100
LOSS− RATE TOTAL− CALLS + IN− INTRA− BSS
[IN− INTRA− BSS− HO− SUCCESS− RATE] + IN− INTER− BSS
BSS Level

= 100
LOSS− RATE TOTAL− CALLS+
ASSIGNMENT− REDIRECTION [DIRECTED− ENTRY] +
ASSIGNMENT− REDIRECTION [DURING− ASSIGNMENTS] +
IN− INTER− BSS− HO [IN− INTER− BSS− HO− SUCCESS− RATE]
Network Level

= 100
17-114 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
RF_LOSSES_TCH.
TOTAL_CALLS.
68P02901W56-T 17-115
Jan 2010
TCH_TRAFFIC_CARRIED Chapter 17: Key statistics
TCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs.
Formula
For an individual cell for an individual statistics interval:
TCH− TRAFFIC− CARRIED = BUSY− TCH− MEAN
P
m
(BUSY− TCH− MEAN [x])
x=1
TCH− TRAFFIC− CARRIED =
m
n
!
X
TCH− TRAFFIC− CARRIED = BUSY− TCH− MEAN [x]
x=1
 !
P
m
n 
BUSY− TCH− MEAN [x] 
X  x=1 
TCH− TRAFFIC− CARRIED =  
 m 
x=1  
17-116 68P02901W56-T
Jan 2010
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Raw BUSY_TCH_MEAN.
Statistics
68P02901W56-T 17-117
Jan 2010
TCH_TRAFFIC_CARRIED_FR Chapter 17: Key statistics
TCH_TRAFFIC_CARRIED_FR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED_FR statistic tracks the mean number of full rate busy TCHs.
Formula
(BUSY− TCH− MEAN − BUSY− TCH− HR− MEAN)

TCH− TRAFFIC− CARRIED− FR =
INTERVAL− SUM
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
BUSY_TCH_HR_MEAN.
INTERVAL_SUM.
17-118 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_TRAFFIC_CARRIED_HR
TCH_TRAFFIC_CARRIED_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED_HR statistic tracks the mean number of half rate busy TCHs.
Formula
BUSY− TCH− HR− MEAN

TCH− TRAFFIC− CARRIED− HR =
INTERVAL− SUM
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Raw Statistics BUSY_TCH_HR_MEAN.
INTERVAL_SUM.
68P02901W56-T 17-119
Jan 2010
TOTAL_CALLS_KEY Chapter 17: Key statistics
TOTAL_CALLS_KEY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TOTAL_CALLS_KEY statistic tracks the number of calls for one or more cells during
the interval.
Formula
TOTAL− CALLS− KEY = (TOTAL− CALLS)
Analysis

Fault finding.
Basis Cell.
Type Counter.
Raw Statistics TOTAL_CALLS.
17-120 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_CHANNEL_REQUESTS_REJECTION_RATE
UL_CHANNEL_REQUESTS_REJECTION_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_CHANNEL_REQUESTS_REJECTION_RATE key statistic shows the percentage of

uplink channel requests that are rejected by the PCU.
Formula
UL− CHANNEL− REQUESTS− CHANNEL− REQS− REJECT

= ∗100
REJECTION− RATE CHANNEL− REQS− REC
Analysis
Basis Cell.
Type Percentage.
Raw statistics CHANNEL_REQS_REJECT.
CHANNEL_REQS_REC.
68P02901W56-T 17-121
Jan 2010
UL_CHANNEL_REQUESTS_SUCCESS_RATE Chapter 17: Key statistics
UL_CHANNEL_REQUESTS_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_CHANNEL_REQUESTS_SUCCESS_RATE key statistic monitors the success of uplink

channel requests. This is an important area as the MS needs to access the network before it
can exchange data. Low end-to-end throughput can be rooted in a low UL channel request
success rate.
NOTE
It is not possible to split this formula in a GPRS and an EGPRS part because
an EGPRS channel request might be served with GPRS resources, causing the
CHANNEL_REQS_SUCCESS statistic to be pegged in a GPRS bin.
17-122 68P02901W56-T
Jan 2010
Formula
 
CHANNEL− REQS− SUCCESS− P− C+
 
 CHANNEL− REQS− SUCCESS− P− P+ 
 
 
 CHANNEL− REQS− SUCCESS− P− R+ 
 
 
 CHANNEL− REQS− SUCCESS− E− C+ 
 
 
 CHANNEL− REQS− SUCCESS− E− 1P− CCC+ 
 
 CHANNEL REQS SUCCESS E PUAPRR+ 
 − − − − ∗100
 
 
 CHANNEL− REQS− SUCCESS− E− PTR+ 
 
 
 CHANNEL− REQS− SUCCESS− E− 1P− PCCC+ 
 
 
 CHANNEL− REQS− SUCCESS− CP− A+ 
 
 
 CHANNEL− REQS− SUCCESS− PKTS+ 
 
UL− CHANNEL− REQUESTS− CHANNEL− REQS− SUCCESS− E− PUAPDAK
=
SUCCESS− RATE CHANNEL− REQS− REC− P− C+CHANNEL− REQS− REC− P− P+
CHANNEL− REQS− REC− E− C+
CHANNEL− REQS− REC− EGPRS− 1PH− CC+
Analysis
Type Percentage.
Raw statistics CHANNEL_REQS_SUCCESS (Includes
sum of bins 0, 1, 4, 5, 6, 7, 8, 9, 12, 13 and
14.
CHANNEL_REQS_REC (Includes sum of
bins 0, 1, 4, 5, 6, 7, 8, 11 and 12.
68P02901W56-T 17-123
Jan 2010
UL_LLC_TRAFFIC_VOLUME_INDICATOR Chapter 17: Key statistics
UL_LLC_TRAFFIC_VOLUME_INDICATOR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_LLC_TRAFFIC_VOLUME_INDICATOR statistic gives an indication about the volume of

uplink LLC traffic for a certain cell. The formula uses the average of the bin ranges to calculate
the traffic and therefore is an indication of the real traffic, not the exact traffic measurement.
Formula
 
(UL− LLC− FRAMES− 20 ∗ 10) +
 
 (UL− LLC− FRAMES− 40 ∗ 30) + 
 
 (UL LLC FRAMES 80 ∗ 60) + 
UL− LLC−  − − − 
 
TRAFFIC−  (UL− LLC− FRAMES− 160 ∗ 120) + 
  10
= ∗
VOLUME−  (UL− LLC− FRAMES− 320 ∗ 240) +  1000
 
INDICATOR  
 (UL− LLC− FRAMES− 640 ∗ 480) + 
 
 
 (UL− LLC− FRAMES− 1280 ∗ 960) + 
(UL− LLC− FRAMES− OVER1280 ∗ 1460)
Analysis
Usage Gb link bandwidth dimensioning.

Basis Cell
Type Units = kB.
Raw statistics UL_LLC_FRAMES[UL_LLC_FRAMES_20].
UL_LLC_FRAMES[UL_LLC_FRAMES_40].
UL_LLC_FRAMES[UL_LLC_FRAMES_OVER1280].
17-124 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_PDTCH_UTILISATION_BY_ALLOCATION
UL_PDTCH_UTILISATION_BY_ALLOCATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_PDTCH_UTILISATION_BY_ALLOCATION key statistic shows the ratio of busy

PDTCHs to available PDTCHs in a cell while transmitting in the uplink direction.
NOTE
The utilization may decrease as the additional switchable PDTCH is allocated for
GPRS congested cell.
Formula
UL− PDTCH− UTILISATION− UL− BUSY− PDTCH− MEAN ∗ 100

=
BY− ALLOCATION GPRS− AVAIL− PDTCH− MEAN+
Analysis
Basis Cell.
Type Percentage.
Raw statistics UL_BUSY_PDTCH_MEAN.
68P02901W56-T 17-125
Jan 2010
UL_PDTCH_UTILISATION_BY_TRAFFIC Chapter 17: Key statistics
UL_PDTCH_UTILISATION_BY_TRAFFIC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_PDTCH_UTILISATION_BY_TRAFFIC key statistic monitors the utilization of GPRS

resources per cell, to detect where the GPRS traffic including data and control blocks is high
compared to the GPRS capacity of the cell while transmitting in the uplink direction.
Formula
  
U L− RLC− ACK− N EW− BLKS+
∗100+
   
 U L− RLC− U N ACK− N EW− BLKS+  
  AIR− UL−  ∗ 100
    
 U L− RLC− RET X− BLKS+  
UL− PDTCH−
U L− RLC− N ACK− BLKS CONTROL − BLKS
UTILISATION− = !
GP RS− AV AIL− P DT CH− M EAN +
BY− TRAFFIC ∗ INTERVAL− SUM ∗ 3600 ∗ 50
EGP RS− AV AIL− P DT CH− M EAN
Analysis
Usage GPRS resource allocation.

Basis Cell.
Type Percentage.
Raw statistics UL_RLC_ACK_NEW_BLKS.
UL_RLC_RETX_BLKS.
UL_RLC_NACK_BLKS.
AIR_UL_CONTROL_BLKS.
17-126 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_PDTCH_UTILISATION_1_TS
UL_PDTCH_UTILISATION_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_PDTCH_UTILISATION_1_TS key statistic provides the PDTCH utilization rate for MSs
that support a maximum of 1 TS in the uplink direction. It compares the maximum possible
Formula
UL− RADIO− BLKS− 8PSK− 1− TS+

UL− PDTCH− UL− RADIO− BLKS− GMSK− 1− TS
= ∗ 10000
UTILISATION− 1− TS UL− TBF− TIME− 8PSK− 1− TS+
UL− TBF− TIME− GMSK− 1− TS
Analysis

Basis Per terminal.
Type Percentage.
Raw statistics UL_RADIO_BLKS_8PSK_1_TS.
68P02901W56-T 17-127
Jan 2010
UL_PDTCH_UTILISATION_2_TS Chapter 17: Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
UL− RADIO− BLKS− 8PSK− 2− TS+

UL− PDTCH− UL− RADIO− BLKS− GMSK− 2− TS
= ! ∗ 10000
UTILISATION− 2− TS UL− TBF− TIME− 8PSK− 2− TS+
∗2
UL− TBF− TIME− GMSK− 2− TS
Analysis

Basis Per terminal.
Type Percentage.
17-128 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_PDTCH_UTILISATION_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
!
∗ 10000
U L− RADIO− BLKS− GM SK− 3− T S
U L− P DT CH− U T ILISAT ION− 3− T S = !
∗3
Analysis

Basis Per terminal.
Type Percentage.
68P02901W56-T 17-129
Jan 2010
UL_PDTCH_UTILISATION_4_TS Chapter 17: Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
!
∗ 10000
U L− RADIO− BLKS− GM SK− 4− T S
U L− P DT CH− U T ILISAT ION− 4− T S = !
∗4
Analysis

Basis Per terminal.
Type Percentage.
17-130 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_RLC_MAC_OVERHEAD
UL_RLC_MAC_OVERHEAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RLC_MAC_OVERHEAD key statistic provides the percentage of overhead RLC/MAC

blocks (retransmissions due to NACK, preemptive retransmissions, super coattail blocks, control
blocks) in relation to the total amount of RLC/MAC blocks, which describes the efficiency of
the RLC/MAC layer while transmitting in the uplink direction.
Formula
  
AIR− UL−
UL− RLC− RETX− BLKS ∗ 100 +    ∗ 100
UL− RLC− MAC− CONTROL− BLKS
=  
OVERHEAD UL− RLC− ACK− NEW− BLKS+  
  AIR− UL−
 UL− RLC− UNACK− NEW− BLKS+  ∗ 100 +  
 
CONTROL− BLKS
UL− RLC− RETX− BLKS
Analysis
Usage Coding Scheme Usage

Statistics, BLER Statistics and
MEAN_USER_THROUGHPUT_PER_TIMESLOT.
Type Percentage
Raw statistics UL_RLC_UNACK_NEW_BLKS.
UL_RLC_RETX_BLKS.
AIR_UL_CONTROL_BLKS.
UL_RLC_ACK_NEW_BLKS.
68P02901W56-T 17-131
Jan 2010
UL_TBF_FAILURE_RATE Chapter 17: Key statistics
UL_TBF_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_FAILURE_RATE key statistic calculates the rate of faulty downlink TBFs.
Formula
UL− TBF− FAILURE− AIR− UL− TBF− FAILURES∗100

=  
RATE CHANNEL− REQS− SUCCESS− P− C+CHANNEL− REQS− SUCCESS− P− P+
 
 CHANNEL− REQS− SUCCESS− P− R+CHANNEL− REQS− SUCCESS− PKTS+ 
 
 CHANNEL REQS SUCCESS E C+CHANNEL REQS SUCCESS CP A+ 
 − − − − − − − − 
 
 CHANNEL− REQS− SUCCESS− E− 1P− CCC+CHANNEL− REQS− SUCCESS− E− 1P− PCCC+ 
 
 
 CHANNEL− REQS− SUCCESS− E− PUAPRR+CHANNEL− REQS− SUCCESS− E− PTR+ 
 
CHANNEL− REQS− SUCCESS− E− PUAPDAK
Analysis

Basis Cell.
Type Percentage.
Raw statistics AIR_UL_TBF_FAILURES.
CHANNEL_REQS_SUCCESS_P_C.
CHANNEL_REQS_SUCCESS_P_P.
CHANNEL_REQS_SUCCESS_P_R.
CHANNEL_REQS_SUCCESS_PKTS.
CHANNEL_REQS_SUCCESS_E_C.
CHANNEL_REQS_SUCCESS_CP_A.
CHANNEL_REQS_SUCCESS_E_1P_CCC.
CHANNEL_REQS_SUCCESS_E_1P_PCCC.
CHANNEL_REQS_SUCCESS_E_PUAPRR.
CHANNEL_REQS_SUCCESS_E_PTR.
CHANNEL_REQS_SUCCESS_E_PUAPDAK.
17-132 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TBF_INTERLEAVING_ACTIVITY
UL_TBF_INTERLEAVING_ACTIVITY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_INTERLEAVING_ACTIVITY key statistic provides information about interleaving

TBFs while transmitting in the uplink direction.
Formula
  
   +
 U L− T BF− T IM E− GM SK− 1− T S 
 
   
 
 U L− T BF− T IM E− 8P SK− 2− T S+ 
   ∗ 2+ 
 
 
   
 U L− T BF− T IM E− 8P SK− 3− T S+ 
 
   ∗ 3+ 
 
   
 
 U L− T BF− T IM E− 8P SK− 4− T S+ 
   ∗ 4+ 
UL− TBF− INTERLEAVING− U L− T BF− T IM E− GM SK− 4− T S
= ∗ 0.02
ACTIVITY U L− BU SY− P DT CH− M EAN ∗
IN T ERV AL− SU M ∗ 3600
Analysis

Basis Cell.
Type Average number of TBFs per PDTCH.
Raw UL_TBF_TIME_8PSK_1_TS.
statistics UL_TBF_TIME_GMSK_1_TS.
UL_BUSY_PDTCH_MEAN.
68P02901W56-T 17-133
Jan 2010
UL_TBF_SUCCESS_RATE Chapter 17: Key statistics
UL_TBF_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_SUCCESS_RATE key statistic measures the success of uplink TBF establishment
by providing the percentage of MSs that have requested an uplink TBF resource and successfully
send data using this TBF.
Formula
UL− PDTCH− SEIZURE∗100

UL− TBF− SUCCESS− RATE =
CHANNEL− REQS− REC− P− C+CHANNEL− REQS− REC− P− P+
CHANNEL− REQS− REC− E− C+CHANNEL− REQS− REC− EGPRS− 1PH− CC+
Analysis
Usage Cell accessibility.

Basis Cell.
Type Percentage.
Raw statistics UL_PDTCH_SEIZURE.
CHANNEL_REQS_REC_P_C.
CHANNEL_REQS_REC_P_P.
CHANNEL_REQS_REC_P_R.
CHANNEL_REQS_REC_CP_A.
CHANNEL_REQS_REC_E_C.
CHANNEL_REQS_REC_EGPRS_1PH_CC.
CHANNEL_REQS_REC_EGPRS_1PH_PCC.
CHANNEL_REQS_REC_EGPRS_PKRS_RQ.
CHANNEL_REQS_REC_EGPRS_CRQPDAK.
17-134 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TERMINAL_TYPE_ACTIVITY_1_TS
UL_TERMINAL_TYPE_ACTIVITY_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TERMINAL_TYPE_ACTIVITY_1_TS key statistic calculates the percentage of activity

per terminal type for MSs that support a maximum of 1 TS in the uplink direction.
Formula
UL− TERMINAL− TYPE− U L− T BF− T IM E− GM SK− 1− T S
= ∗ 100
ACTIVITY− 1− TS U L− T BF− T IM E− 8P SK− 1− T S+
U L− T BF− T IM E− GM SK− 1− T S+
Analysis

Resource planning.
Type Percentage.
Raw statistics UL_TBF_TIME_8PSK_1_TS.
68P02901W56-T 17-135
Jan 2010
UL_TERMINAL_TYPE_ACTIVITY_2_TS Chapter 17: Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
!
UL− TERMINAL− TYPE− U L− T BF− T IM E− GM SK− 2− T S+
=   ∗ 100
 
 U L− T BF− T IM E− 8P SK− 2− T S+ 
 
 U L T BF T IM E 8P SK 3 T S+ 
 − − − − − 
 
 U L− T BF− T IM E− 8P SK− 4− T S+ 
 
 
 U L− T BF− T IM E− GM SK− 1− T S+ 
 
 
 
 
 U L− T BF− T IM E− GM SK− 3− T S+ 
Analysis

Resource planning.
Type Percentage.
17-136 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_TERMINAL_TYPE_ACTIVITY_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
!
=   ∗ 100
 
 U L− T BF− T IM E− 8P SK− 2− T S+ 
 
 − − − − − 
 
 U L− T BF− T IM E− 8P SK− 4− T S+ 
 
 
 
 
 
 
Analysis

Resource planning.
Type Percentage.
68P02901W56-T 17-137
Jan 2010
UL_TERMINAL_TYPE_ACTIVITY_4_TS Chapter 17: Key statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
!
=   ∗ 100
 
 U L− T BF− T IM E− 8P SK− 2− T S+ 
 
 − − − − − 
 
 U L− T BF− T IM E− 8P SK− 4− T S+ 
 
 
 
 
 
 
Analysis

Resource planning.
Type Percentage.
17-138 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_USER_TRAFFIC_EGPRS
UL_USER_TRAFFIC_EGPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_USER_TRAFFIC_EGPRS statistic gives the EGPRS uplink traffic volume, excluding
Formula
  
  ∗ 22+ 
 
 UL− RLC− UNACK− NEW− BLKS− MCS− 1 
  
 
 UL− RLC− ACK− NEW− BLKS− MCS− 2+ 
  ∗ 28+ 
 
 
  
 UL RLC ACK NEW BLKS MCS 3+ 
 − − − − − − 
  ∗ 37+ 
 
  
 
  
 ∗ 44+ 
 
  
 UL RLC ACK NEW BLKS MCS 5+ 
 − − − − − − 
  ∗ 56+  ∗ 100
 
  
 
  ∗ 74+ 
 
 UL RLC UNACK NEW BLKS MCS 6 
 − − − − − − 
  
 
  ∗ 112+ 
 
  
 
  
 ∗ 136+ 
 UL RLC UNACK NEW BLKS MCS 8 
 − − − − − − 
  
 
  ∗ 148 
UL− USER− TRAFFIC− EGPRS =
1024
68P02901W56-T 17-139
Jan 2010
Analysis

Congestion.
Basis Cell.
Type kbytes.
Raw Statistics UL_RLC_ACK_NEW_BLKS and UL_RLC_UNACK_NEW_BLKS (the value
used is bins 4 to 12).
17-140 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UL_USER_TRAFFIC_GPRS
UL_USER_TRAFFIC_GPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_USER_TRAFFIC_GPRS statistic gives the GPRS uplink traffic volume, excluding
Formula
  
  ∗ 22+ 
 UL RLC UNACK NEW BLKS CS 1 
 − − − − − − 
  
 
 UL− RLC− ACK− NEW− BLKS− CS− 2+ 
  ∗ 33+ 
 
 UL− RLC− UNACK− NEW− BLKS− CS− 2 
 
   ∗ 100
 
  ∗ 39+ 
 
 UL− RLC− UNACK− NEW− BLKS− CS− 3 
  
 
  ∗ 53 
UL− USER− TRAFFIC− GPRS=
1024
Analysis
Usage Congestion.
Network planning.
Basis Cell.
Type kbytes
Raw Statistics UL_RLC_ACK_NEW_BLKS and UL_RLC_UNACK_NEW_BLKS (the values
used are bins 0 to 3).
68P02901W56-T 17-141
Jan 2010
UNSUCCESS_INTERNAL_HO_NOREEST Chapter 17: Key statistics
UNSUCCESS_INTERNAL_HO_NOREEST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UNSUCCESS_INTERNAL_HO_NOREEST statistic tracks the number of unsuccessful

internal handovers that result in dropping the call.
Formula
UNSUCCESS− INTERNAL− INTRA− CELL− HO [INTRA− CELL− HO− LOSTMS] +

=
HO− NOREEST OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− LOSTMS]
Analysis

Quality of service.
Fault finding.
Basis Cell or BSS.
Type Counter
Raw INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS].
17-142 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application UNSUCCESS_INTERNAL_HO_REEST
UNSUCCESS_INTERNAL_HO_REEST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UNSUCCESS_INTERNAL_HO_REEST statistic tracks the number of unsuccessful internal

handovers with successful recovery to the originating cell or channel.
Formula
SUCCESS−
INTRA− CELL− HO [INTRA− CELL− HO− RETURN] +
INTERNAL− =
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− RETURN]
HO− REEST
Analysis

Fault finding.
Quality of service.
Basis Cell or BSS.
Type Counter.
Raw INTRA_CELL_HO[INTRA_CELL_HO_RETURN].
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].
68P02901W56-T 17-143
Jan 2010
17-144 68P02901W56-T
Jan 2010
Chapter
18
Network health reports

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Network health statistics quantify BSS performance from a subscriber perspective. A

combination of raw and other network health statistics are used by the OMC-R to calculate
these statistics.
Network health statistics are available for display with the Cell device statistics in the OMC-R
Performance Management window.
They network health statistics are categorized into subgroups, each of which are described in
Network health statistics subgroups on page 18-2.
68P02901W56-T 18-1
Jan 2010
Network health statistics subgroups Chapter 18: Network health reports
Network health statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Network health statistics are organized into the following major subgroups:
• GPRS performance on page 18-2.
• Handover performance on page 18-2.
• Health check on page 18-4.
• Paging performance on page 18-5.
• Radio performance on page 18-5.
• SDCCH congestion on page 18-5.
• TCH congestion on page 18-6.
GPRS performance
The following statistics provide key performance metric for the GPRS system:
• AIR_INTERFACE_BW_CS1 on page 18-7.
• DL_BANDWIDTH_INDICATOR_EGPRS on page 18-23.
• DL_BANDWIDTH_INDICATOR_GPRS on page 18-26.
• GPRS_MEAN_INTER_ARRIVAL_TIME on page 18-31.
• UL_BANDWIDTH_INDICATOR_EGPRS on page 18-130.
• UL_BANDWIDTH_INDICATOR_GPRS on page 18-132.
Handover performance
The following statistics provide general handover information:

• HO_BLKD_BSP_OVERLOAD on page 18-32.
• HO_CAUSE_ADJ_CH_INTERF on page 18-33.
• HO_CAUSE_BAND_HO on page 18-34.
• HO_CAUSE_BAND_REASSGN on page 18-35.
18-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover performance
• HO_CAUSE_CONGEST on page 18-36.
• HO_CAUSE_DISTANCE on page 18-37.
• HO_CAUSE_DLINTERF on page 18-38.
• HO_CAUSE_DLLEVEL on page 18-39.
• HO_CAUSE_DLQUAL on page 18-40.
• HO_CAUSE_PWRBGT on page 18-41.
• HO_CAUSE_UPINTERF on page 18-42.
• HO_CAUSE_UPLEVEL on page 18-43.
• HO_CAUSE_UPQUAL on page 18-44.
• HO_PER_CALL on page 18-45.
• IN_INTER_BSS_HO_SUCCESS_RATE on page 18-51.
• IN_INTER_CELL_HO_SUCCESS_RATE on page 18-52.
• IN_INTRA_BSS_HO_SUCCESS_RATE on page 18-54.
• INCOMING_HO_VOLUME on page 18-55.
• INTERNAL_LOST on page 18-56.
• INTERNAL_RECOVERED on page 18-57.
• INTERNAL_SUCCESS on page 18-58.
• INTRA_CELL_HO_FAIL_LOST_MS on page 18-59.
• INTRA_CELL_HO_FAIL_RECOVERED on page 18-60.
• INTRA_CELL_HO_SUCCESS_RATE on page 18-61.
• MEAN_TIME_BETWEEN_DROPS on page 18-65.
• MEAN_TIME_BETWEEN_HOs on page 18-66.
• OUT_INTER_BSS_HO_FAIL_LOST_MS on page 18-69.
• OUT_INTER_BSS_HO_FAIL_RECOVERED on page 18-70.
• OUT_INTER_BSS_HO_SUCCESS_RATE on page 18-71.
• OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS on page 18-72.
• OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED on page 18-73.
• OUT_INTER_CELL_HO_SUCCESS_RATE on page 18-74.
• OUT_INTRA_BSS_HO_FAIL_LOST_MS on page 18-75.
• OUT_INTRA_BSS_HO_SUC on page 18-77.
68P02901W56-T 18-3
Jan 2010
Health check Chapter 18: Network health reports
• OUTGOING_HO_VOLUME on page 18-78.
• INTER_BSS_HO_ATTEMPT_RATE on page 18-83.
• INTRA_BSS_HO_ATTEMPT_RATE on page 18-84.
• INTRA_CELL_HO_ATTEMPT_RATE on page 18-85.
Health check
The following statistics provide health check information:

• CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS on page 18-13.
• CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS on page 18-15.
• CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE on page 18-17.
• CALL_SUCCESS_RATE on page 18-19.
• CALL_VOLUME on page 18-21.
• CELL_CONGESTION_TIME on page 18-22
• DROP_CALL_RATE on page 18-28.
• IMMEDIATE_ASSIGN_BLOCKING_RATE on page 18-47.
• IMMEDIATE_ASSIGN_FAILURE_RATE on page 18-48.
• IMMEDIATE_ASSIGN_MEAN_ARRIVAL_RATE on page 18-49.
• IMMEDIATE_ASSIGN_SUCCESS_RATE on page 18-50.
• NUM_HO_FROM_3G_FAIL on page 18-67.
• NUM_HO_TO_3G_FAIL on page 18-68.
• RANKING_FORMULA on page 18-86.
• SDCCH_BLOCKING_RATE on page 18-92.
• SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF on page 18-115.
• SPILL_OVER_FACTOR_DIRECTED_RETRY on page 18-116.
• SPILL_OVER_FACTOR_MULTIBAND on page 18-117.
18-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Paging performance
Paging performance
The following statistics provide paging performance information:

• AIR_INTERFACE_PAGING on page 18-11.
• MA_REQ_SDCCH_PG_RSP on page 18-62.
• MSC_PAGING on page 18-64.
• PAGING_COMPRESSION_RATE on page 18-79.
• PAGING_OVERFLOW_RATE on page 18-80.
• PAGING_RESPONSE on page 18-81.
• PAGING_SUCCESS_RATE on page 18-82.
Radio performance
The following statistics provide radio performance information:

• ASSIGNMENT_SUCCESS_RATE on page 18-12.
• OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS on page 18-72.
• OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED on page 18-73.
• OUT_INTER_CELL_HO_SUCCESS_RATE on page 18-74.
• RF_ASSIGN_FAIL_RATE_LOST_MS on page 18-88.
• RF_ASSIGN_FAIL_RATE_RECOVERED on page 18-89.
• RF_ASSIGN_SUCCESS_RATE on page 18-90.
• TCH_RF_LOSS_RATE on page 18-124.
SDCCH congestion
The following statistics provide SDCCH congestion information:

• SDCCH_ACCESSES on page 18-91.
• SDCCH_BLOCKING_RATE on page 18-92.
• SDCCH_CONGESTION_TIME on page 18-93.
• SDCCH_TRAFFIC_CARRIED on page 18-94.
68P02901W56-T 18-5
Jan 2010
TCH congestion Chapter 18: Network health reports
• SDCCH_USAGE_ACCESS_FAILURE on page 18-96.
• SDCCH_USAGE_CALL_REESTABLISH on page 18-98.
• SDCCH_USAGE_EMERGENCY_CALL on page 18-100.
• SDCCH_USAGE_IMSI_DETACH on page 18-102.
• SDCCH_USAGE_LOCATION_UPDATE on page 18-103.
• SDCCH_USAGE_MS_ORIGINATED_CALL on page 18-105.
• SDCCH_USAGE_MS_ORIGINATED_SMS on page 18-107.
• SDCCH_USAGE_SMS_ORIGINATED_SS on page 18-109.
• SDCCH_USAGE_PAGING_RESPONSE on page 18-111.
• SDCCH_USAGE_SMS on page 18-113.
TCH congestion
The following statistics provide TCH congestion information:

• MAX_TCH_BUSY on page 18-63.
• TCH_ACCESSES on page 18-118.
• TCH_CONGESTION_TIME on page 18-120.
• TCH_CONGESTION_TIME_INNER_ZONE on page 18-121.
• TCH_CONGESTION_TIME_OUTER_ZONE on page 18-123.
18-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AIR_INTERFACE_BW_CS1
AIR_INTERFACE_BW_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_INTERFACE_BW_CS1 statistic provides the maximum bandwidth available in kilobits

per second in a cell for GPRS coding scheme 1.
Formula
AIR− INTERFACE− BW− CS1 = GPRS− AVAIL− PDTCH ∗ 9.05 cos
Analysis

Basis Cell.
Type Counter.
Raw Statistics GPRS_AVAIL_PDTCH.
68P02901W56-T 18-7
Jan 2010
AIR_INTERFACE_BW_CS2 Chapter 18: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
AIR− INTERFACE− BW− CS2 = GPRS− AVAIL− PDTCH ∗ 13.4
Analysis

Basis Cell.
Type Counter.
18-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AIR_INTERFACE_BW_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
Analysis

Basis Cell.
Type Counter.
68P02901W56-T 18-9
Jan 2010
AIR_INTERFACE_BW_CS4 Chapter 18: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description

Formula
Analysis

Basis Cell.
Type Counter.
18-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application AIR_INTERFACE_PAGING
AIR_INTERFACE_PAGING
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The AIR_INTERFACE_PAGING statistic tracks the total number of paging requests messages
sent on the air interface.
Formula
ACCESS− PER− PCH [ACCESS− PER− PCH− PS− CS] +

AIR− INTERFACE−
= ACCESS− PER− PCH [ACCESS− PER− PCH− CS] +
PAGING
ACCESS− PER− PCH [ACCESS− PER− PCH− PS]
Analysis

Basis Cell.
Type Counter.
Raw Statistics ACCESS_PER_PCH (the value used in this formula is the sum of bins 0
to 2 of this counter array statistic).
68P02901W56-T 18-11
Jan 2010
ASSIGNMENT_SUCCESS_RATE Chapter 18: Network health reports
ASSIGNMENT_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ASSIGNMENT_SUCCESS_RATE statistic measures the success rate of the A-interface

assignment procedure which also automatically includes the impact of the air interface
assignment procedure.
Formula
MA− COMPLETE− TO− MSC ∗

ASSIGNMENT− SUCCESS− RATE = 100
MA− REQ− FROM− MSC
Analysis

Quality of service.
Basis Cell.
Type Percentage.
Raw Statistics MA_COMPLETE_TO_MSC.
MA_REQ_FROM_MSC.
18-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS statistic provides the

percentage of air interface call set-up assignment commands that are sent to over the air
interface which result in the MS failing to access the target channel and failing to recover to
the original channel. This statistic includes the impact of successful second assignments and
intra-cell handover assignment attempts.
NOTE
Formula
 
MA− CMD− TO− MS−
 MA− COMPLETE− FROM− MS−  −
 MA− FAIL− FROM− MS 

INTRA− CELL− HO
 [INTRA− CELL− HO− ATMPT− FR− FR] + 
 
 INTRA− CELL− HO 
 
 [INTRA CELL HO ATMPT HR HR] + 
 − − − − − 
 −
 
 [INTRA− CELL− HO− ATMPT− FR− HR] + 
 
 INTRA− CELL− HO 
[INTRA− CELL− HO− ATMPT− HR− FR]
INTRA− CELL− HO− SUC−
CALL− SETUP− RF−
INTRA− CELL− HO− RETURN ∗
ASSIGNMENT− FAIL− RATE− =   100
 MA− CMD− TO− MS− 
LOST− MS INTRA− CELL− HO
 
 
  [INTRA− CELL− HO− ATMPT− FR− FR] + 
 
  
 INTRA− CELL− HO  
 
  [INTRA− CELL− HO− ATMPT− HR− HR] + 
 
  − 
  
  [INTRA CELL HO ATMPT FR HR] +  
 − − − − −
 
  
 
SECOND− ASSIGN− ATMPT
68P02901W56-T 18-13
Jan 2010
Analysis Chapter 18: Network health reports
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw MA_CMD_TO_MS.
Statistics MA_FAIL_FROM_MS.
INTRA_CELL_HO_SUC.
INTRA_CELL_HO_RETURN.
SECOND_ASSIGN_ATMPT.
INTRA_CELL_HO (the value used in this formula is the sum of bins 1 to 4 of
this counter array statistic).
18-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_
RECOVERED_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS statistic provides the

percentage of air interface call set-up assignment commands that are sent over the air interface
which result in the MS failing to access the target channel and after successfully recovering
to the original channel. This statistic includes the impact of successful second assignments
and intra-cell handover assignment attempts.
NOTE
Formula
MA− FAIL− FROM− MS−

INTRA− CELL− HO− RETURN−
CALL− SETUP− RF−
SECOND− ASSIGN− ATMPT ∗
ASSIGNMENT− FAIL− RATE =   100
RECOVERED− MS INTRA CELL HO
 − −− 
 
 
  
  
  [INTRA− CELL− HO− ATMPT− HR− HR] +  
 −
 
  [INTRA CELL HO ATMPT FR HR] +   
 − − − − −
 
  
 
68P02901W56-T 18-15
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS.
MA_FAIL_FROM_MS.
INTRA_CELL_HO_RETURN.
18-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE statistic provides the percentage of

air interface call set-up assignment commands that are successfully sent over the air interface
which result in the MS accessing the target channel. This statistic includes the impact of
successful second assignments and intra-cell handover assignment attempts.
NOTE
Formula
CALL− SETUP− RF− MA− COMPLETE− FROM− MS−

INTRA− CELL− HO− SUC ∗
ASSIGNMENT− SUCCESS− =   100
RATE  INTRA− CELL= HO 
 
 
  
 
  [INTRA− CELL− HO− ATMPT− HR− HR] + 
 
  − 
  
  [INTRA CELL HO ATMPT FR HR] +  
 − − − − −
 
  
 
68P02901W56-T 18-17
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
MA_COMPLETE_FROM_MS.
INTRA_CELL_HO_SUC.
18-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_SUCCESS_RATE
CALL_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic represents the portion of MS call transactions with normal completions at the
radio subsystem, providing an overall indication of network performance from a subscriber
perspective.
A combination of the CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATE network health

statistics is used to calculate this statistic. The raw statistics used to calculate these health
statistics are included in the raw statistics listing.
Formula
CALL− SUCCESS−
= (((F1 ∗ 100) /F2) ∗ (1 − (((F3 ∗ 100) /F4) /100)))
RATE
Where: Is:
F1 (S1 + S2)
F2 (S3 + S4 + S5 + S6 + S7 + S8 + S9 - S10 - S11 - S12 + S13)
F3 (S14 + S15 + S16 + S17 + S18)
F4 (S1 + S19 + S20)
S1 TOTAL_CALLS
S2 ASSGN_REDIRECT
S3 CM_SERV_REQ_CALL
S4 CM_SERV_REQ_SMS
S5 CM_SERV_REQ_EMERG
S6 CM_REESTABLISH
S7 PAGE_RESPONSE
S8 LOC_FLW_ON_REQ_NORM
S9 LOC_FLW_ON_REQ_SMS
S10 MT_LCS_ON_SDCCH
S11 SMS_INIT_ON_SDCCH_REQ
S12 SMS_INIT_ON_TCH_FCS_REQ
S13 SMS_INIT_ON_SIG_HO_IN_REQ
S14 RF_LOSSES_TCH_ROLL
Continued
68P02901W56-T 18-19
Jan 2010
Where: Is:
S15 (INTRA_CELL_HO_LOSTMS - SIG_INTRA_CELL_HO_
LOSTMS)
S16 (OUT_INTRA_BSS_HO_LOSTMS -
SIG_OUT_INTRA_BSS_HO_LOSTMS)
S17 (OUT_INTER_BSS_HO_FAIL -
SIG_OUT_INTER_BSS_HO_FAIL)
S18 (OUT_INTER_BSS_HO_EQUIP_FAIL -
SIG_OUT_INTER_BSS_HO_EQUIP_FAIL)
S19 (IN_INTRA_BSS_HO_SUC - SIG_IN_INTRA_BSS_HO_SUC)
S20 (IN_INTER_BSS_HO_SUC - SIG_IN_INTER_BSS_HO_SUC)
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION.
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
OK_ACC_PROC[IMM_SETUP2].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_FAIL].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_EQUIP_FAIL].
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH_REQ.
TOTAL_CALLS.
18-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application CALL_VOLUME
CALL_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_VOLUME statistic tracks the number of call setups which result in a successful
TCH access.
Formula
TOTAL− CALLS+
CALL− VOLUME =
Analysis

Basis Cell.
Type Counter.
Raw Statistics ASSIGNMENT_REDIRECTION (the value used in this formula is the sum of
TOTAL_CALLS.
68P02901W56-T 18-21
Jan 2010
CELL_CONGESTION_TIME Chapter 18: Network health reports
CELL_CONGESTION_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CELL_CONGESTION_TIME key statistic indicates the amount of time a cell was congested
more than 25%. This data can then be used to identify busy cells.
Formula
 
GPRS− CONGESTION− 30 + GPRS− CONGESTION− 35+
 GPRS− CONGESTION− 40 + GPRS− CONGESTION− 45+ 
 
 
CELL− CONGESTION−  GPRS CONGESTION 60 + GPRS CONGESTION 65+ 
 − − − − 
=   ∗ 6
TIME  GPRS− CONGESTION− 70 + GPRS− CONGESTION− 75+ 
 
 
 GPRS− CONGESTION− 90 + GPRS− CONGESTION− 95+ 
GPRS− CONGESTION− 100
Analysis
Usage Cell congestion analysis.

Basis Cell.
Type Time interval.
Raw Statistics GPRS_CELL_CONGESTION[GPRS_CONGESTION_30].
GPRS_CELL_CONGESTION[GPRS_CONGESTION_35].
18-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application DL_BANDWIDTH_INDICATOR_EGPRS
DL_BANDWIDTH_INDICATOR_EGPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BANDWIDTH_INDICATOR_EGPRS statistic provides the average downlink block size

as a function of the average used coding schemes shown in Table 18-1.
Table 18-1 Average block size used for EGPRS coding schemes
Coding scheme Blocks

MCS-1 22
MCS-2 28
MCS-3 37
MCS-4 44
MCS-5 56
MCS-6 74
MCS-7 112
MCS-8 136
MCS-9 148
68P02901W56-T 18-23
Jan 2010
Formula Chapter 18: Network health reports
Formula
DL− BANDWIDTH− A+B+C+D

=  MCS−9
P 
INDICATOR− EGPRS
(DL− RLC− ACK− NEW− BLKS) +
 MCS−1 
 
 MCS−9
P 
 (DL− RLC− UNACK− NEW− BLKS) + 
 
 MCS−1 
 
 P
MCS−9 
 (DL− RLC− RETX− BLKS) + 
 
 MCS−1 
 P
MCS−9 
(DL− RLC− NACK− BLKS)
MCS−1
where:
(DL− RLC− ACK− NEW− BLKS [MCS − 1]) ∗ 22+

A = (DL− RLC− ACK− NEW− BLKS [MCS − 5]) ∗ 56+
(DL− RLC− ACK− NEW− BLKS [MCS − 9]) ∗ 148
(DL− RLC− UNACK− NEW− BLKS [MCS − 1]) ∗ 22+

B = (DL− RLC− UNACK− NEW− BLKS [MCS − 5]) ∗ 56+
(DL− RLC− UNACK− NEW− BLKS [MCS − 9]) ∗ 148
18-24 68P02901W56-T
Jan 2010
(DL− RLC− RETX− BLKS [MCS − 1]) ∗ 22+

C = (DL− RLC− RETX− BLKS [MCS − 5]) ∗ 56+
(DL− RLC− RETX− BLKS [MCS − 9]) ∗ 148
(DL− RLC− NACK− BLKS [MCS − 1]) ∗ 22+

D = (DL− RLC− NACK− BLKS [MCS − 5]) ∗ 56+
(DL− RLC− NACK− BLKS [MCS − 9]) ∗ 148
Analysis

Radio resource allocation (provides a single figure for average coding
scheme usage).
Basis Cell.
Type Counter.
Raw Statistics DL_RLC_ACK_NEW_BLKS.
DL_RLC_RETX_BLKS.
DL_RLC_NACK_BLKS.
68P02901W56-T 18-25
Jan 2010
DL_BANDWIDTH_INDICATOR_GPRS Chapter 18: Network health reports
DL_BANDWIDTH_INDICATOR_GPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_BANDWIDTH_INDICATOR_GPRS statistic provides the average downlink block size

as a function of the average used coding schemes shown in Table 18-2.
Table 18-2 Average block size used for GPRS coding schemes

CS-1 22
CS-2 33
CS-3 39
CS-4 53
18-26 68P02901W56-T
Jan 2010
Formula
 
(DL− RLC− ACK− NEW− BLKS [CS − 1]) ∗ 22+
 (DL− RLC− ACK− NEW− BLKS [CS − 2]) ∗ 33+ 
 
 (DL RLC ACK NEW BLKS [CS − 3]) ∗ 39+ 
 − − − − 
 
 (DL− RLC− ACK− NEW− BLKS [CS − 4]) ∗ 53+ 
 
 (DL− RLC− UNACK− NEW− BLKS [CS − 1]) ∗ 22+ 
 
 
 
 (DL RLC UNACK NEW BLKS [CS − 4]) ∗ 53+ 
 − − − − 
 
 (DL− RLC− RETX− BLKS [CS − 1]) ∗ 22+ 
 
 (DL − RLC− RETX− BLKS [CS − 2]) ∗ 33+ 
 
 
 
 
 (DL− RLC− NACK− BLKS [CS − 1]) ∗ 22+ 
 
 (DL− RLC− NACK− BLKS [CS − 2]) ∗ 33+ 
 
 (DL− RLC− NACK− BLKS [CS − 3]) ∗ 39+ 
DL− BANDWIDTH− (DL− RLC− NACK− BLKS [CS − 4]) ∗ 53
=  CS−4P 
INDICATOR− GPRS
(DL− RLC− ACK− NEW− BLKS) +
 CS−1 
 
 CS−4
P 
 (DL− RLC− UNACK− NEW− BLKS) + 
 
 CS−1 
 
 P
CS−4 
 (DL− RLC− RETX− BLKS) + 
 
 CS−1 
 P
CS−4 
(DL− RLC− NACK− BLKS)
CS−1
Analysis

scheme usage).
Basis Cell.
Type Counter.
Raw Statistics DL_RLC_ACK_NEW_BLKS.
DL_RLC_RETX_BLKS.
DL_RLC_NACK_BLKS.
68P02901W56-T 18-27
Jan 2010
DROP_CALL_RATE Chapter 18: Network health reports
DROP_CALL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DROP_CALL_RATE statistic tracks the percentage of MSs which have successfully
accessed a TCH, and experience an abnormal release caused by either radio or equipment
problems. This includes RF losses and losses during handovers.
NOTE
The frequency of dropped calls during inter BSS handovers are less compared to those
during intra BSS or intra cell handovers, or those unrelated to handovers. The impact
on the accuracy of statistics during inter BSS handovers is therefore relatively small.
Formula
Cell Level
 
RF− LOSSES− TCH− ROLL+
  
 IN T RA− CELL− HO− LOST M S− 
 + 
 
 SIG IN T RA CELL HO LOST M S 
 − − − − 
  
 
 OU T− IN T RA− BSS− HO− LOST M S− 
 + 
 
 SIG− OU T− IN T RA− BSS− HO− LOST M S 
 
  
 OU T− IN T ER− BSS− HO− F AIL− 
 
 + 
 
 SIG− OU T− IN T ER− BSS− HO− F AIL 
 
  
 OU T− IN T ER− BSS− HO− EQU IP− F AIL− 
 
  
DROP− CALL− SIG− OU T− IN T ER− BSS− HO− EQU IP− F AIL
=   ∗ 100%
RATE TOTAL− CALLS+
   
 IN− IN T ER− BSS− HO− SU C− 
  
 +
 SIG IN IN T ER BSS HO SU C 
 − − − − − 
  
 
 IN− IN T RA− BSS− HO− SU C− 
  
SIG− IN− IN T RA− BSS− HO− SU C
18-28 68P02901W56-T
Jan 2010
BSS Level
 
  
 + 
 
 − − − − 
  
 
 + 
 
 
  
 
 + 
 
 
  
 
  
=   ∗ 100%
RATE TOTAL− CALLS+
 
 ASSGN− REDIRECT+ 
  
 
 IN− IN T ER− BSS− HO− SU C− 
 
SIG− IN− IN T ER− BSS− HO− SU C
PLMN Level
 
  
 + 
 
 − − − − 
  
 
 + 
 
 
  
 
 + 
 
 
  
 
  
= ! ∗ 100%
RATE T OT AL− CALLS+
ASSGN− REDIRECT
68P02901W56-T 18-29
Jan 2010
Analysis

Type Percentage.
RF_LOSSES_TCH.
TOTAL_CALLS.
18-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application GPRS_MEAN_INTER_ARRIVAL_TIME
GPRS_MEAN_INTER_ARRIVAL_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_MEAN_INTER_ARRIVAL_TIME statistic tracks the GPRS channel request (RACH)

arrival rate in RACHs per interval for the concerned BSS.
Formula
BSS− GPRS− ACCESS− PER− RACH

GPRS− MEAN− INTER− ARRIVAL− TIME =
INTERVAL− SUM
Analysis

Type Counter (RACHs per Interval).
Raw INTERVAL_SUM (statistics collection interval, measured in hours).
Statistics BSS_GPRS_ACCESS_PER_RACH.
68P02901W56-T 18-31
Jan 2010
HO_BLKD_BSP_OVERLOAD Chapter 18: Network health reports
HO_BLKD_BSP_OVERLOAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_BLKD_BSP_OVERLOAD statistic tracks the number of non-imperative handover

recognized messages dropped by the BSC due to BSP CPU overload.
Pegging
The statistic is pegged when the BSC drops a non-imperative handover recognized message
from BTS due to BSP CPU overload.
Analysis
This statistic provides a measurement for the number of non-imperative handover recognized
message dropped by BSP overload control mechanism.
Reference None
Usage Handover performance
Basis Cell
Type Counter
18-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_ADJ_CH_INTERF
HO_CAUSE_ADJ_CH_INTERF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_ADJ_CH_INTERF statistic provides the percentage of all handovers due

to adjacent channel interference.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [ADJ− CH− INTERF] ∗

= 100
ADJ− CH− INTERF OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-33
Jan 2010
HO_CAUSE_BAND_HO Chapter 18: Network health reports
HO_CAUSE_BAND_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_BAND_HO statistic provides the percentage of all handovers due to band
handover.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [BAND− HANDOVER] ∗

= 100
BAND− HO OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-34 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_BAND_REASSGN
HO_CAUSE_BAND_REASSGN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_BAND_REASSGN statistic provides the percentage of all handovers due to

band reassignment.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [BAND− RE− ASSIGN] ∗

= 100
BAND− REASSGN OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-35
Jan 2010
HO_CAUSE_CONGEST Chapter 18: Network health reports
HO_CAUSE_CONGEST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_CONGEST statistic provides the percentage of all handovers due to congestion
(directed retry or congestion relief).
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [CONGESTION] ∗

= 100
CONGEST OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_DISTANCE
HO_CAUSE_DISTANCE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DISTANCE statistic provides the percentage of all handovers due to distance
(timing advance).
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [DISTANCE] ∗

= 100
DISTANCE OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-37
Jan 2010
HO_CAUSE_DLINTERF Chapter 18: Network health reports
HO_CAUSE_DLINTERF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLINTERF statistic provides the percentage of all handovers due to downlink
interference.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [DOWNINTERF] ∗

= 100
DLINTERF OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_DLLEVEL
HO_CAUSE_DLLEVEL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLLEVEL statistic provides the percentage of all handovers due to downlink
level.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [DOWNLEVEL] ∗

= 100
DLLEVEL OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-39
Jan 2010
HO_CAUSE_DLQUAL Chapter 18: Network health reports
HO_CAUSE_DLQUAL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLQUAL statistic provides the percentage of all handovers due to downlink
quality.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [DOWNQUAL] ∗

= 100
DLQUAL OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-40 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_PWRBGT
HO_CAUSE_PWRBGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_PWRBGT statistic provides the percentage of all handovers due to power
budget.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [POWERBGDT] ∗

= 100
PWRBGT OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-41
Jan 2010
HO_CAUSE_UPINTERF Chapter 18: Network health reports
HO_CAUSE_UPINTERF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPINTERF statistic provides the percentage of all handovers due to uplink
interference.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [UPINTERF] ∗

= 100
UPINTERF OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-42 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_CAUSE_UPLEVEL
HO_CAUSE_UPLEVEL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPLEVEL statistic provides the percentage of all handovers due to uplink
level.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [UPLEVEL] ∗

= 100
UPLEVEL OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
68P02901W56-T 18-43
Jan 2010
HO_CAUSE_UPQUAL Chapter 18: Network health reports
HO_CAUSE_UPQUAL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPQUAL statistic provides the percentage of all handovers due to uplink
quality.
Formula
HO− CAUSE− OUT− HO− CAUSE− ATMPT [UPQUAL] ∗

= 100
UPQUAL OUT− HO− CAUSE− ATMPT
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics T.
18-44 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application HO_PER_CALL
HO_PER_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_PER_CALL statistic tracks the average number of successful handovers per call.
Formula
Cell Level
(OUT− INTER− BSS− HO− SUC+

OUT− INTRA− BSS− HO− SUC + INTRA− CELL− HO− SUC)
HO− PER− CALL =
TOTAL− CALLS
BSS Level

HO− PER− CALL =
TOTAL− CALLS+
Network Level

HO− PER− CALL =
TOTAL− CALLS+
68P02901W56-T 18-45
Jan 2010
Analysis

Fault finding.
Type Counter.
INTRA_CELL_HO[INTRA_CELL_HO_SUC].
TOTAL_CALLS.
18-46 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IMMEDIATE_ASSIGN_BLOCKING_RATE
IMMEDIATE_ASSIGN_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named SDCCH_SETUP_BLOCKING_RATE.
Description
The IMMEDIATE_ASSIGN_BLOCKING_RATE statistic tracks the percentage of attempts to

allocate an SDCCH that were blocked due to no available SDCCH resources for call origination
only. This statistic does not include incoming SDCCH handover attempts.
Formula
CHAN− REQ− MS− BLK ∗

IMMEDIATE− ASSIGN− BLOCKING− RATE = 100
OK− ACC− PROC− SUC− RACH
Analysis
Usage Service Accessibility.

GPRS Quality of Service monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics CHAN_REQ_MS_BLK.
OK_ACC_PROC_SUC_RACH.
68P02901W56-T 18-47
Jan 2010
IMMEDIATE_ASSIGN_FAILURE_RATE Chapter 18: Network health reports
IMMEDIATE_ASSIGN_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named SDCCH_ACCESS_FAILURE_RATE.
Description
The IMMEDIATE_ASSIGN_FAILURE_RATE statistic calculates the proportion of resource

assignment activations that fail to achieve MS access.
Formula
IMMEDIATE− ASSIGN− CHAN− REQ− MS− FAIL

= ∗ 100
FAILURE− RATE OK− ACC− PROC− SUC− RACH−
CHAN− REQ− MS− BLK
Analysis

Basis Cell.
Type Percentage.
Raw statistics CHAN_REQ_MS_FAIL.
OK_ACC_PROC_SUC_RACH.
CHAN_REQ_MS_BLK.
18-48 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IMMEDIATE_ASSIGN_MEAN_ARRIVAL_RATE
IMMEDIATE_ASSIGN_MEAN_ARRIVAL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named SDCCH_MEAN_ARRIVAL_RATE.
Description
The IMMEDIATE_ASSIGN_MEAN_ARRIVAL_TIME statistic tracks the call arrival (set-up) rate

for the SDCCHs in the cell measured in calls per interval.
Formula
 
 
 
 
 
 
 
 
 
 + LOCAT ION− U P DAT E 
 
 
 + P AGE− RESP ON SE 
IMMEDIATE− ASSIGN− + IM SI− DET ACH
=
MEAN− ARRIVAL− RATE INTERVAL− SUM
Analysis

Basis Cell.
Type Counter (calls per interval).
Raw Statistics INTERVAL (statistics collection interval, measured in hours).
OK_ACC_PROC (the value used in this formula is the sum of the bins 0 to 7
and 11 to 15 of this counter array statistic).
68P02901W56-T 18-49
Jan 2010
IMMEDIATE_ASSIGN_SUCCESS_RATE Chapter 18: Network health reports
IMMEDIATE_ASSIGN_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
NOTE
This statistic was previously named SDCCH_ACCESS_SUCCESS_RATE.
Description
The IMMEDIATE_ASSIGN_SUCCESS_RATE statistic calculates the proportion of SDCCH

activation which is followed by successful MS access.
Formula
 
 
 
 
 
 
 
 
 
 + LOCAT ION− U P DAT E 
 
 
 + IM SI− DET ACH 
 
 
IMMEDIATE− ASSIGN− + CM− LCS− REQU EST
= ! ∗ 100
SUCCESS− RATE OK− ACC− P ROC− SU C− RACH
− CHAN− REQ− M S− BLK
Analysis

Basis Cell.
Type Counter (calls per interval).
Raw Statistics OK_ACC_PROC_SUC_RACH.
CHAN_REQ_MS_BLK.
OK_ACC_PROC (the value used in this formula is the sum of bins 0 to 7 and
11 to 15 of this counter array statistic).
18-50 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application IN_INTER_BSS_HO_SUCCESS_RATE
IN_INTER_BSS_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTER_BSS_HO_SUCCESS_RATE statistic tracks the percentage of incoming

inter-BSS handover commands that are sent over the air interface which result in the MS
successfully accessing the target channel.
NOTE
Formula
IN− INTER− BSS− IN− INTER− BSS− HO− SUCCESS− RATE ∗

100
HO− SUCCESS− RATE = HO− REQ− ACK− TO− MSC
Analysis

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics IN_INTER_BSS_HO_SUCCESS_RATE.
HO_REQ_ACK_TO_MSC.
68P02901W56-T 18-51
Jan 2010
IN_INTER_CELL_HO_SUCCESS_RATE Chapter 18: Network health reports
IN_INTER_CELL_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTER_CELL_HO_SUCCESS_RATE statistic tracks the percentage of incoming

inter-cell handover commands that are sent over the air interface which result in the MS
NOTE
Formula
IN− INTER− BSS− HO− SUCCESS− RATE+
IN− INTER− CELL− IN− INTRA− BSS− HO− SUCCESS− RATE ∗

100
HO− SUCCESS− RATE = IN− INTRA− BSS− HO
[IN− INTRA− BSS− HO− RETURN] +
[IN− INTRA− BSS− HO− LOSTMS] +
[IN− INTRA− BSS− HO− CLEARED] +
[IN− INTRA− BSS− HO− FAIL] +
HO− REQ− ACK− TO− MSC
18-52 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics IN_INTRA_BSS_HO_SUCCESS_RATE.
IN_INTER_BSS_HO_SUCCESS_RATE.
IN_INTRA_BSS_HO (the value used in this formula is the sum of bins 0 to 4
HO_REQ_ACK_TO_MSC.
68P02901W56-T 18-53
Jan 2010
IN_INTRA_BSS_HO_SUCCESS_RATE Chapter 18: Network health reports
IN_INTRA_BSS_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_HO_SUCCESS_RATE statistic tracks the percentage of incoming

intra-BSS handover commands that are sent over the air interface which result in the MS
NOTE
Formula
IN− INTRA− BSS− IN− INTRA− BSS− HO− SUCCESS− RATE ∗

100
HO− SUCCESS− RATE = IN− INTRA− BSS− HO
[IN− INTRA− BSS− HO− RETURN] +
[IN− INTRA− BSS− HO− LOSTMS] +
[IN− INTRA− BSS− HO− CLEARED] +
[IN− INTRA− BSS− HO− FAIL]
Analysis

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics IN_INTRA_BSS_HO_SUCCESS_RATE.
IN_INTRA_BSS_HO (the value used in this formula is the sum of bins 0
18-54 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INCOMING_HO_VOLUME
INCOMING_HO_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INCOMING_HO_VOLUME statistic provides the number of successful incoming handovers.
Formula
Cell Level
IN− INTER− BSS− HO [IN− INTER− BSS− HO− SUCCESS− RATE] +

INCOMING− HO− VOLUME =
IN− INTRA− BSS− HO [IN− INTRA− BSS− HO− SUCCESS− RATE]
BSS Level
INCOMING− HO− VOLUME = IN− INTER− BSS− HO [IN− INTER− BSS− HO− SUCCESS− RATE]
Analysis

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUCCESS_RATE].
68P02901W56-T 18-55
Jan 2010
INTERNAL_LOST Chapter 18: Network health reports
INTERNAL_LOST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTERNAL_LOST statistic tracks the percentage of BSS internal handover commands that
are sent over the air interface which result in the MS failing to access the target and failing
to recover to the original channel; that is, the call drops. This statistic includes intra-BSS
and intra-cell handovers.
Formula
!
OU T− IN T RA− BSS− HO− LOST M S+
∗ 100
IN T RA− CELL− HO− LOST M S
INTERNAL− LOST =  
OU T− IN T RA− BSS− HO− AT M P T +
 
 IN T RA− CELL− HO− AT M P T− F R− F R+ 
 
 
 IN T RA− CELL− HO− AT M P T− HR− HR+ 
 
 IN T RA CELL HO AT M P T HR F R+ 
 − − − − − 
IN T RA− CELL− HO− AT M P T− F R− HR
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics INTRA_CELL_HO (the value used in this formula is the sum of bins 1 to 4 of
18-56 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTERNAL_RECOVERED
INTERNAL_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTERNAL_RECOVERED statistic tracks the percentage of BSS internal handover

commands that are sent over the air interface which result in the MS failing to access the target
channel and successfully recovering to the original channel. This statistic includes intra-BSS
and intra-cell handovers.
Formula
 
OU T− IN T RA− BSS− HO− RET U RN +
  ∗ 100
INTERNAL− IN T RA− CELL− HO− RET U RN
=  
RECOVERED OU T− IN T RA− BSS− HO− AT M P T +
 
 
 
 
 
 
 IN T RA− CELL− HO− AT M P T− HR− F R+ 
 
Analysis

Fault finding.
Basis Cell.
Type Percentage.
INTRA_CELL_HO[INTRA_CELL_HO_RETURN].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].
68P02901W56-T 18-57
Jan 2010
INTERNAL_SUCCESS Chapter 18: Network health reports
INTERNAL_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTERNAL_SUCCESS statistic tracks the percentage of BSS internal handover commands
that are sent over the air interface which result in the MS successfully accessing the target
channel. This statistic includes intra-BSS and intra-cell handovers.
Formula
!
OU T− IN T RA− BSS− HO− SU C+
∗ 100
INTERNAL− IN T RA− CELL− HO− SU C
=  
SUCCESS OU T− IN T RA− BSS− HO− AT M P T +
 
 
 
 
 IN T RA CELL HO AT M P T HR F R+ 
 − − − − − 
Analysis

Fault finding.
Basis Cell.
Type Percentage.
18-58 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTRA_CELL_HO_FAIL_LOST_MS
INTRA_CELL_HO_FAIL_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO_FAIL_LOST_MS statistic tracks the percentage of intra-cell assignment

commands that are sent over the air interface which result in the MS failing to access the target
channel and failing to recover to the original channel; that is, the call drops.
Formula
INTRA− CELL− HO− INTRA− CELL− HO− LOSTMS∗ 100

 
FAIL− LOST− MS = IN T RA− CELL− HO− AT M P T− F R− F R+
 
 
 
 IN T RA− CELL− HO− AT M P T− HR− F R+ 
Analysis

Fault finding.
Type Percentage.
Raw Statistics INTRA_CELL_HO (the value used in this formula is bin 6 and the sum of bins
68P02901W56-T 18-59
Jan 2010
INTRA_CELL_HO_FAIL_RECOVERED Chapter 18: Network health reports
INTRA_CELL_HO_FAIL_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO_FAIL_RECOVERED statistic tracks the percentage of intra-cell

assignment commands that are sent over the air interface which result in the MS failing to
access the target channel and after successfully recovering to the original channel.
Formula
INTRA− CELL− HO INTRA− CELL− HO− RETURN∗ 100

 
FAIL− RECOVERED = IN T RA− CELL− HO− AT M P T− F R− F R+
 
 
 
Analysis

Fault finding.
Type Percentage.
Raw Statistics INTRA_CELL_HO (the value used in this formula is bin 7 and the sum of bins
18-60 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTRA_CELL_HO_SUCCESS_RATE
INTRA_CELL_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO_SUCCESS_RATE statistic tracks the percentage of intra-cell assignment

commands that are sent over the air interface which result in the MS successfully accessing
the target channel.
Formula
INTRA− CELL− HO− INTRA− CELL− HO− SUC ∗ 100

 
SUCCESS− RATE = IN T RA− CELL− HO− AT M P T− F R− F R+
 
 
 
Analysis

Fault finding.
Type Percentage.
Raw Statistics INTRA_CELL_HO (the value used in this formula is bin 5 and the sum of
68P02901W56-T 18-61
Jan 2010
MA_REQ_SDCCH_PG_RSP Chapter 18: Network health reports
MA_REQ_SDCCH_PG_RSP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The number of assignment requests on SDCCH for prepaid service of Ericsson MSC.
Pegging
When receiving a paging response, MSC sends an assignment for the requirement of another
SDCCH assigned for subscriber billing information to be transmitted (remaining credit
available). BSS does not assign an SDCCH as the mobile already has one. This statistic is
pegged at CP/RRSM and the call is carried out.̀
Analysis
Basis Cell.
Type Counter.
18-62 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MAX_TCH_BUSY
MAX_TCH_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MAX_TCH_BUSY statistic tracks the maximum number of simultaneously busy TCHs.
Formula
MAX− TCH− BUSY = BUSY− TCH [MAX]
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Counter.
Raw Statistics BUSY_TCH[MAX].
68P02901W56-T 18-63
Jan 2010
MSC_PAGING Chapter 18: Network health reports
MSC_PAGING
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MSC_PAGING statistic tracks the total number of BSSMAP paging messages received
over the A-interface from the MSC.
Formula
MSC− PAGING = PAGE− REQ− FROM− MSC
Analysis

Basis Cell.
Type Counter.
18-64 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MEAN_TIME_BETWEEN_DROPS
MEAN_TIME_BETWEEN_DROPS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_TIME_BETWEEN_DROPS statistic tracks the mean time interval between dropped
calls due to the loss of the radio link.
Formula
MEAN− TIME− (BUSY− TCH− MEAN) ∗ INTERVAL− SUM ∗ 3600

 
BETWEEN− DROPS = RF− LOSSES− TCH− ROLL+
 INTRA− CELL− HO [INTRA− CELL− HO− LOSTMS] + 
 
 OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− LOSTMS] + 
 
 OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− FAIL] + 
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− EQUIP− FAIL]
Analysis

Fault finding.
Basis Cell.
Type Time interval.
RF_LOSSES_TCH_ROLL.
68P02901W56-T 18-65
Jan 2010
MEAN_TIME_BETWEEN_HOs Chapter 18: Network health reports
MEAN_TIME_BETWEEN_HOs
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_TIME_BETWEEN_HOs statistic tracks the mean time interval between inter
cell handovers.
Formula
MEAN− TIME− BUSY− TCH− MEAN ∗ INTERVAL− SUM

BETWEEN− HOs = OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− SUC] +
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− SUC] +
INTRA− CELL− HO [INTRA− CELL− HO− SUC]
Analysis

Fault finding.
Basis Cell.
Type Time interval (in seconds).
18-66 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application NUM_HO_FROM_3G_FAIL
NUM_HO_FROM_3G_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_FROM_3G_FAIL statistic calculates the number of attempted handovers from a

3G network to a 2G Cell that failed.
Formula
NUM− HO− FROM− 3G− ATTEMPTS−

NUM− HO− FROM− 3G− FAIL =
NUM− HO− FROM− 3G− SUCCESS
Analysis
Usage Network health.

Handover.
Basis Cell.
Type Counter.
Raw statistics NUM_HO_FROM_3G_ATTEMPTS.
NUM_HO_FROM_3G_SUCCESS.
68P02901W56-T 18-67
Jan 2010
NUM_HO_TO_3G_FAIL Chapter 18: Network health reports
NUM_HO_TO_3G_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_HO_TO_3G_FAIL statistic calculates the number of attempted handovers from a

2G network to a 3G Cell that failed.
Formula
NUM− HO− TO− 3G− ATTEMPTS−

NUM− HO− TO− 3G− FAIL =
NUM− HO− TO− 3G− SUCCESS
Analysis
Usage Network health.

Handover.
Basis Cell.
Type Counter.
Raw statistics NUM_HO_TO_3G_ATTEMPTS.
NUM_HO_TO_3G_SUCCESS.
18-68 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTER_BSS_HO_FAIL_LOST_MS
OUT_INTER_BSS_HO_FAIL_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of inter-BSS

handover commands that are sent over the air interface which result in the MS failing to access
the target channel and failing to recover to the original channel; that is, the call drops.
Formula
 
OUT− INTER− BSS− HO
 [OUT− INTER− BSS− HO− FAIL] + 
 
 OUT− INTER− BSS− HO 
OUT− INTER− BSS− HO− FAIL [OUT− INTER− BSS− HO− EQUIP− FAIL] ∗
100
LOST− MS = OUT− INTER− BSS− HO− ATMPT
Analysis

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].
68P02901W56-T 18-69
Jan 2010
OUT_INTER_BSS_HO_FAIL_RECOVERED Chapter 18: Network health reports
OUT_INTER_BSS_HO_FAIL_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO_FAIL_RECOVERED statistic tracks the percentage of inter-BSS

the target channel and after successfully recovering to the original channel.
Formula
OUT− INTER− BSS−

OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− RETURN]
HO− FAIL = ∗ 100
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT]
RECOVERED
Analysis

Fault finding.
Basis BSS.
Type Percentage.
18-70 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTER_BSS_HO_SUCCESS_RATE
OUT_INTER_BSS_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO_SUCCESS_RATE statistic tracks the percentage of inter-BSS

handover commands that are sent over the air interface which result in the MS successfully
accessing the target channel.
Formula
OUT− INTER− BSS− HO− OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− SUC] ∗
100
SUCCESS− RATE = OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT]
Analysis

Fault finding.
Basis BSS.
Type Percentage.
68P02901W56-T 18-71
Jan 2010
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS Chapter 18: Network health reports
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS statistic tracks the percentage of inter-cell

the target channel and failing to recover to the original channel; that is, the call drops. This
statistic does not include intra-cell handovers.
Formula
 
OUT− INTRA− BSS− HO− LOSTMS+
 OUT− INTER− BSS− HO− FAIL+ 
 
OUT− INTER− CELL− HO−  OUT− INTER− BSS− HO− EQUIP− FAIL ∗
= 

 100

FAIL− RATE− LOST− MS  OUT− INTRA− BSS− HO− ATMPT+ 
 OUT− INTER− BSS− HO− ATMPT 
Analysis

Fault finding.
Basis Cell.
Type Percentage.
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_FAIL]
18-72 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED
OUT_INTER_CELL_HO_FAIL_RATE_
RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED statistic tracks the percentage of

inter-cell handover commands that are sent over the air interface which result in the MS failing
to access the target channel and after successfully recovering to the original channel. This
statistic does not include intra-cell handovers.
Formula
OUT− INTER− OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− RETURN] +
CELL− HO− FAIL− OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− RETURN] ∗
= 100
FAIL− RATE− OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− ATMPT] +
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− ATMPT]
RECOVERED
Analysis

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-T 18-73
Jan 2010
OUT_INTER_CELL_HO_SUCCESS_RATE Chapter 18: Network health reports
OUT_INTER_CELL_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_SUCCESS_RATE statistic tracks the percentage of inter-cell

handover commands that results in the MS successfully accessing the target channel. This
statistic includes intra-BSS and inter-BSS inter-cell handovers.
Formula

OUT− INTER− CELL− OUT− INTRA− BSS− HO− SUC) ∗
100
HO− SUCCESS− RATE = (OUT− INTRA− BSS− HO− ATMPT+
OUT− INTER− BSS− HO− ATMPT)
Analysis

Fault finding.
Basis Cell.
Type Percentage.
18-74 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTRA_BSS_HO_FAIL_LOST_MS
OUT_INTRA_BSS_HO_FAIL_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTRA_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of intra-BSS

the target channel and failing to recover to the original channel; that is, the call drops.
NOTE
Formula
OUT− INTRA− BSS− HO− FAIL OUT− INTRA− BSS− HO− LOST− MS ∗
= 100
LOST− MS OUT− INTER− BSS− HO− ATMPT
Analysis

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].
68P02901W56-T 18-75
Jan 2010
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS Chapter 18: Network health reports
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS statistic tracks the percentage of

intra-BSS handover commands that are sent over the air interface which result in the MS failing
to access the target channel and after successfully recovering to the original channel.
NOTE
Formula
OUT− INTRA−
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− RETURN]
BSS− HO− FAIL = ∗ 100
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− ATMPT]
RECOVERED− MS
Analysis

Fault finding.
Basis BSS.
Type Percentage.
18-76 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTRA_BSS_HO_SUC
OUT_INTRA_BSS_HO_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTRA_BSS_HO_SUC statistic tracks the percentage of intra-BSS handover

commands that are sent over the air interface which result in the MS successfully accessing
the target channel.
NOTE
Formula
OUT− INTRA− BSS− OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− SUC] ∗
= 100
HO− SUC OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− ATMPT]
Analysis

Fault finding.
Basis BSS.
Type Percentage.
68P02901W56-T 18-77
Jan 2010
OUTGOING_HO_VOLUME Chapter 18: Network health reports
OUTGOING_HO_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUTGOING_HO_VOLUME statistic tracks the number of successful outgoing handovers.
Formula
OUT− INTER− BSS− HO [OUT− INTER− BSS− HO− SUC] +

OUT− GOING− HO− VOLUME =
OUT− INTRA− BSS− HO [OUT− INTRA− BSS− HO− SUC]
Analysis

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].
18-78 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PAGING_COMPRESSION_RATE
PAGING_COMPRESSION_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_COMPRESSION_RATE statistic provides a measure of page packing on the air

interface.
Formula
ACCESS− PER− PCH [ACCESS− PER− PCH− PS− CS] +

ACCESS− PER− PCH [ACCESS− PER− PCH− CS] +
PAGING−
ACCESS− PER− PCH [ACCESS− PER− PCH− PS] ∗
COMPRESSION− = 100
PAGING− REQUESTS [PAGING− REQUESTS− CS] +
RATE
PAGING− REQUESTS [PAGING− REQUESTS− PS]
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ACCESS_PER_PCH (the value used in this formula is the sum of bins 0 to 2
PAGING_REQUESTS (the value used in this formula is the sum of bins 1
and 2 of this counter array statistic).
68P02901W56-T 18-79
Jan 2010
PAGING_OVERFLOW_RATE Chapter 18: Network health reports
PAGING_OVERFLOW_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_OVERFLOW_RATE statistic tracks the percentage of pages which are dropped
from the BSS paging queue due to paging queue overflow. There are two formulas based on the
paging purpose (circuit switched or packet switched).
Formula
Circuit switched
PAGING− OVERFLOW− PCH− PAGE− Q− DISCARD [CS] ∗

= 100
RATE− CS PAGING− REQUESTS [PAGING− REQUESTS− CS]
Packet switched
PAGING− OVERFLOW− PCH− PAGE− Q− DISCARD [PS] ∗

= 100
RATE− PS PAGING− REQUESTS [PAGING− REQUESTS− PS]
Analysis

Fault finding.
Type Percentage.
Raw Statistics PCH_PAGE_Q_DISCARD[CS].
PCH_PAGE_Q_DISCARD[PS].
PAGING_REQUESTS[PAGING_REQUESTS_CS].
PAGING_REQUESTS[PAGING_REQUESTS_PS].
18-80 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application PAGING_RESPONSE
PAGING_RESPONSE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_RESPONSE statistic tracks the volume of MSs which respond to a page through
a successful SDCCH access.
Formula
PAGING− RESPONSE = OK− ACC− PROC [PAGE− RESPONSE]
Analysis

Fault finding.
Type Counter.
Raw Statistic OK_ACC_PROC[PAGE_RESPONSE].
68P02901W56-T 18-81
Jan 2010
PAGING_SUCCESS_RATE Chapter 18: Network health reports
PAGING_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGING_SUCCESS_RATE statistic tracks the percentage of pages which receive a

successful response from an MS. This statistic is measured on a location area basis.
Formula
P
OK− ACC− PROC [PAGE− RESPONSE] ∗
PAGING− SUCCESS− RATE = 100
PAGING− REQUEST [CS]
where SUM (OK_ACC_PROC[PAGE_RESPONSE]) is summed across all cells in the location

area and assuming that paging is configured on a location area basis, PAGE_REQ_FROM_MSC
is the maximum value occurring on any cell within the LAC.
Analysis

Fault finding
Basis Location area.
Type Percentage.
Raw Statistics OK_ACC_PROC[PAGE_RESPONSE].
PAGE_REQ_FROM_MSC.
18-82 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTER_BSS_HO_ATTEMPT_RATE
INTER_BSS_HO_ATTEMPT_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTER_BSS_HO_ATTEMPT_RATE statistic calculates the percentage of all inter-BSS

handover attempts.
NOTE
Formula
INTER− BSS− HO− OUT− INTER− BSS− HO− ATMPT ∗

= 100
ATTEMPT− RATE INTRA− CELL− HO
[INTRA− CELL− HO− ATMPT− FR− FR] +
INTRA− CELL− HO
[INTRA− CELL− HO− ATMPT− HR− HR] +
INTRA− CELL− HO
[INTRA− CELL− HO− ATMPT− FR− HR] +
INTRA− CELL− HO
[INTRA− CELL− HO− ATMPT− HR− FR] +
OUT− INTRA− BSS− HO
[OUT− INTRA− BSS− HO− ATMPT] +
[OUT− INTER− BSS− HO− ATMPT]
Analysis

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO_ATMPT.
68P02901W56-T 18-83
Jan 2010
INTRA_BSS_HO_ATTEMPT_RATE Chapter 18: Network health reports
INTRA_BSS_HO_ATTEMPT_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_BSS_HO_ATTEMPT_RATE statistic calculates the percentage of all intra-BSS

handover attempts.
NOTE
Formula
INTRA− BSS− HO− OUT− INTRA− BSS− HO− ATMPT ∗

= 100
INTRA− CELL− HO
INTRA− CELL− HO
INTRA− CELL− HO
Analysis

Fault finding.
Basis BSS.
Type Percentage.
18-84 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application INTRA_CELL_HO_ATTEMPT_RATE
INTRA_CELL_HO_ATTEMPT_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO_ATTEMPT_RATE statistic calculates the percentage of all intra-cell

handover attempts.
NOTE
Formula
INTRA− CELL− HO− INTRA− CELL− HO− ATMPT ∗

= 100
INTRA− CELL− HO
INTRA− CELL− HO
INTRA− CELL− HO
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics INTRA_CELL_HO_ATMPT.
68P02901W56-T 18-85
Jan 2010
RANKING_FORMULA Chapter 18: Network health reports
RANKING_FORMULA
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RANKING_FORMULA statistic provides a measure by which cells can be ranked by

performance. This permits cells requiring optimization to be identified. The value of this
statistic increases as cells have high calling volumes and low call success rates. High values for
this statistic indicate which cells which should be optimized first.
A combination of the CALL_SUCCESS_RATE and CALL_SETUP_SUCCESS_RATE network

health statistics is used to calculate this statistic. The raw statistics used to calculate these
health statistics are included in the raw statistics listing.
Formula
RAN KIN G− (100 − (((F1 ∗ 100) /F2) ∗ (1 − (((F3 ∗ 100) /F4) /100))))
=
F ORM U LA 100 − ((F1 ∗ 100) /F2) ∗ (1 − (((F3 ∗ 100) /F4/100) ∗ S1) / (F1 ∗ 100) /F2)
Where: Is:
F1 (S1 + S2)
F2 (S3 + S4 + S5 + S6 + S7 + S8 + S9 - S10 - S11 - S12 + S13)
F3 (S14 + S15 + S16 + S17 + S18)
F4 (S1 + S19 + S20)
S1 TOTAL_CALLS
S2 ASSGN_REDIRECT
S3 CM_SERV_REQ_CALL
S4 CM_SERV_REQ_SMS
S5 CM_SERV_REQ_EMERG
S6 CM_REESTABLISH
S7 PAGE_RESPONSE
S8 LOC_FLW_ON_REQ_NORM
S9 LOC_FLW_ON_REQ_SMS
S10 SMS_INIT_ON_SDCCH_REQ
S11 SMS_INIT_ON_TCH_FCS_REQ
S12 MT_LCS_ON_SDCCH
S13 SMS_INIT_ON_SDCCH_HO_IN_REQ
Continued
18-86 68P02901W56-T
Jan 2010
Where: Is:
S14 RF_LOSSES_TCH_ROLL
S15 (INTRA_CELL_HO_LOSTMS -
SIG_INTRA_CELL_HO_LOSTMS)
S16 (OUT_INTRA_BSS_HO_LOSTMS -
SIG_OUT_INTRA_BSS_HO_LOSTMS)
S17 (OUT_INTER_BSS_HO_FAIL -
SIG_OUT_INTER_BSS_HO_FAIL)
S18 (OUT_INTER_BSS_HO_EQUIP_FAIL -
SIG_OUT_INTER_BSS_HO_EQUIP_FAIL)
S19 (IN_INTRA_BSS_HO_SUC - SIG_IN_INTRA_BSS_HO_SUC)
S20 (IN_INTER_BSS_HO_SUC - SIG_IN_INTER_BSS_HO_SUC)
Analysis
Usage Optimization.
Basis Cell.
Type Counter.
MT_LCS_ON_SDCCH.
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
OK_ACC_PROC[IMM_SETUP2].
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH_REQ.
TOTAL_CALLS.
68P02901W56-T 18-87
Jan 2010
RF_ASSIGN_FAIL_RATE_LOST_MS Chapter 18: Network health reports
RF_ASSIGN_FAIL_RATE_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_ASSIGN_FAIL_RATE_LOST_MS statistic provides the percentage of assignment

commands that are sent to over the air interface which result in the MS failing to access the
target channel and failing to recover to the original channel; that is, the call drops. This statistic
includes intra-cell handover assignment attempts.
Formula
(MA− CMD− TO− MS − MA− COMPLETE− FROM− MS−

RFASSIGN− FAIL− MA− FAIL− FROM− MS) ∗
100
RATE− LOST= MS = MA− CMD− TO− MS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
MA_FAIL_FROM_MS.
18-88 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF_ASSIGN_FAIL_RATE_RECOVERED
RF_ASSIGN_FAIL_RATE_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_ASSIGN_FAIL_RATE_RECOVERED statistic provides the percentage of assignment

commands that are sent over the air interface which result in the MS failing to access the
target channel and after successfully recovering to the original channel. This statistic includes
intra-cell handover assignment attempts.
Formula
MA− FAIL− FROM− MS ∗

RF− ASSIGN− FAIL− RATE− RECOVERED = 100
MA− CMD− TO− MS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
MA_FAIL_FROM_MS.
68P02901W56-T 18-89
Jan 2010
RF_ASSIGN_SUCCESS_RATE Chapter 18: Network health reports
RF_ASSIGN_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_ASSIGN_SUCCESS_RATE statistic provides the percentage of assignment commands

that are successfully sent over the air interface which result in the MS accessing the target
channel. This statistic includes intra-cell handover assignment attempts.
Formula
MA− COMPLETE− FROM− MS ∗

RF− ASSIGN− SUCCESS− RATE = 100
MA− CMD− TO− MS
Analysis

Fault finding.
Basis Cell.
Type Percentage.
18-90 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_ACCESSES
SDCCH_ACCESSES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_ACCESSES statistic tracks the number of SDCCH activations which result in a
successful seizure by the MS.
Formula
ALLOC− SDCCH−
SDCCH− ACCESSES = CHAN− REQ− MS− FAIL [1] + ...
+CHAN− REQ− MS− FAIL [nSDCCH]
Analysis
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Basis Cell.
Type Counter.
CHAN_REQ_MS_FAIL [SDCCH].
68P02901W56-T 18-91
Jan 2010
SDCCH_BLOCKING_RATE Chapter 18: Network health reports
SDCCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate an

SDCCH that were blocked due to no available SDCCH resources. This statistic includes
incoming SDCCH handover attempts.
Formula
ALLOC− SDCCH− FAIL ∗

SDDCH− BLOCKING− RATE = 100
(ALLOC− SDCCH + ALLOC− SDCCH− FAIL)
Analysis

Quality of Service Monitoring.
Network planning.
Basis Cell.
Type Percentage.
ALLOC_SDCCH_FAIL.
18-92 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_CONGESTION_TIME
SDCCH_CONGESTION_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all
SDCCHs are busy.
Formula
SDCCH− CONGESTION
SDCCH− CONGESTION− TIME =
1000
Analysis
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration (seconds).
Raw Statistics SDCCH_CONGESTION.
68P02901W56-T 18-93
Jan 2010
SDCCH_TRAFFIC_CARRIED Chapter 18: Network health reports
SDCCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHs

measured in Erlangs.
Formula
SDCCH− TRAFFIC− CARRIED = BUSY− SDCCH− MEAN
P
m
BUSY− SDCCH− MEAN [ ]
=1
SDCCH− TRAFFIC− CARRIED =
m
n
X
SDCCH− TRAFFIC− CARRIED = BUSY− SDCCH− MEAN [ ]
=1
 
P
m
n
X  =1 BUSY − SDCCH− MEAN [ ]

SDCCH− TRAFFIC− CARRIED =  
 m 
=1
NOTE
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic channels
during a collection interval. Where BUSY_SDCCH_MEAN [x] is BUSY_SDCCH_MEAN
for statistical interval x.
18-94 68P02901W56-T
Jan 2010
Analysis
Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.
68P02901W56-T 18-95
Jan 2010
SDCCH_USAGE_ACCESS_FAILURE Chapter 18: Network health reports
SDCCH_USAGE_ACCESS_FAILURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_ACCESS_FAILURE statistic tracks the percentage of immediate

assignment SDCCH activations that fail to achieve successful SDCCH access.
NOTE
Formula
SDCCH− USAGE− CHAN− REQ− MS− FAIL ∗

= 100
ACCESS− FAILURE (OK− ACC− PROC [CM− SERV− REQ− CALL] +
OK− ACC− PROC [CM− SERV− REQ− EMERG] +
OK− ACC− PROC [PAGE− RESPONSE] +
OK− ACC− PROC [CM− REESTABLISH] +
OK− ACC− PROC [LOCATION− UPDATE] +
OK− ACC− PROC [IMSI− DETACH] +
CHAN− REQ− MS− FAIL)
18-96 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[LOCATION_UPDATE].
OK_ACC_PROC[IMSI_DETACH].
CHAN_REQ_MS_FAIL.
68P02901W56-T 18-97
Jan 2010
SDCCH_USAGE_CALL_REESTABLISH Chapter 18: Network health reports
SDCCH_USAGE_CALL_REESTABLISH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_CALL_REESTABLISH statistic tracks the percentage of immediate

assignment SDCCH activations that are due to call re-establish attempts.
NOTE
Formula
SDCCH− USAGE− CALL− OK− ACC− PROC [CM− REESTABLISH]

= ∗ 100
REESTABLISH (OK− ACC− PROC [CM− SERV− REQ− CALL] +
18-98 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-T 18-99
Jan 2010
SDCCH_USAGE_EMERGENCY_CALL Chapter 18: Network health reports
SDCCH_USAGE_EMERGENCY_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_EMERGENCY_CALL statistic tracks the percentage of immediate

assignment SDCCH activations that are due to MS originated emergency call attempts.
NOTE
Formula
SDCCH− USAGE− EMERGENCY− OK− ACC− PROC [CM− SERV− REQ− EMERG]
= ∗ 100
CALL (OK− ACC− PROC [CM− SERV− REQ− CALL] +
18-100 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-T 18-101
Jan 2010
SDCCH_USAGE_IMSI_DETACH Chapter 18: Network health reports
SDCCH_USAGE_IMSI_DETACH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_IMSI_DETACH statistic tracks the percentage of immediate assignment

SDCCH activations that are due to IMSI detach attempts.
NOTE
Formula
OK− ACC− PROC [IMSI− DETACH] ∗

SDCCH− USAGE− IMSI− DETACH = 100
(OK− ACC− PROC [CM− SERV− REQ− CALL] +
Analysis
Usage Quality of service, Fault finding, and Service accessibility.

Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-102 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_LOCATION_UPDATE
SDCCH_USAGE_LOCATION_UPDATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_LOCATION_UPDATE statistic tracks the percentage of immediate

assignment SDCCH activations that are due to location update attempts.
NOTE
Formula
SDCCH− USAGE− OK− ACC− PROC [CM− SERV− LOCATION− UPDATE]

= ∗ 100
LOCATION− UPDATE (OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-103
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-104 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_MS_ORIGINATED_CALL
SDCCH_USAGE_MS_ORIGINATED_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_MS_ORIGINATED_CALL statistic tracks the percentage of immediate

assignment SDCCH activations that are due to non-emergency MS originated call attempts.
NOTE
Formula
SDCCH− USAGE− MS− OK− ACC− PROC [CM− SERV− REQ− CALL]
= ∗ 100
ORIGINATED− CALL (OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-105
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-106 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_MS_ORIGINATED_SMS
SDCCH_USAGE_MS_ORIGINATED_SMS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_MS_ORIGINATED_SMS statistic tracks the percentage of immediate

assignment SDCCH activations that are due to non-emergency MS originated SMS attempts.
NOTE
Formula
SDCCH− USAGE− MS− OK− ACC− PROC [CM− SERV− REQ− SMS]
= ∗ 100
ORIGINATED− SMS (OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-107
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-108 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_SMS_ORIGINATED_SS
SDCCH_USAGE_SMS_ORIGINATED_SS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_SMS_ORIGINATED_SS statistic tracks the percentage of immediate

assignment SDCCH activations that are due to non-emergency MS originated Supplementary
Service (SS) attempts.
NOTE
Formula
SDCCH− USAGE− SMS− OK− ACC− PROC [CM− SERV− REQ− SUPP]
= ∗ 100
ORIGINATED− SS (OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-109
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-110 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_PAGING_RESPONSE
SDCCH_USAGE_PAGING_RESPONSE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_PAGING_RESPONSE statistic tracks the percentage of immediate

assignment SDCCH activations that are due to MS terminated transaction attempts (for
example, calls, SMSs, or Supplementary Services).
NOTE
Formula
SCCCH− USAGE− PAGING− OK− ACC− PROC [PAGE− RESPONSE]

= ∗ 100
RESPONSE (OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-111
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
18-112 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SDCCH_USAGE_SMS
SDCCH_USAGE_SMS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_SMS statistic tracks the percentage of immediate assignment SDCCH

activations that are due to MS originated or MS terminated SMS attempts.
NOTE
Formula
SMS− INIT− ON− SDCCH− REQ ∗

SDCCH− USAGE− SMS = 100
(OK− ACC− PROC [CM− SERV− REQ− CALL] +
68P02901W56-T 18-113
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics SMS_INIT_ON_SDCCH_REQ.
CHAN_REQ_MS_FAIL.
18-114 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF
SPILL_OVER_FACTOR_ATTEMPTS_AT_
CONGESTION_RELIEF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF statistic tracks the

percentage of successful call set-ups initiated in a cell which caused an existing call to be
subject to a congestion relief handover attempt.
NOTE
• It is not possible to run PM report for the SPILL_OVER_FACTOR_AT-

TEMPTS_AT_CONGESTION_RELIEF statistic since the PM GUI does not
support it.
• This Key Statistic is not available at the OMC now, but users can build their own
Formula
SPILL− OVER−
FACTOR−
CONGEST− EXIST− HO− ATMPT
ATTEMPTS− = ∗ 100
TOTAL− CALLS+
AT− CONGESTION−
RELIEF
ASSIGNMENT− REDIRECTION [DURING− ASSIGNMENTS]+
Analysis

Basis Cell.
Type Percentage.
Raw Statistics CONGEST_EXIST_HO_ATMPT.
ASSIGNMENT_REDIRECTION (the value used in this formula is the sum of
TOTAL_CALLS.
68P02901W56-T 18-115
Jan 2010
SPILL_OVER_FACTOR_DIRECTED_RETRY Chapter 18: Network health reports
SPILL_OVER_FACTOR_DIRECTED_RETRY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SPILL_OVER_FACTOR_DIRECTED_RETRY statistic tracks the percentage of successful

call set-ups initiated in a cell which complete TCH assignment in a neighboring cell through
directed retry or a handover during assignment.
NOTE
• It is not possible to run PM report for the SPILL_OVER_FACTOR_DI-

RECTED_RETRY statistic since the PM GUI does not support it.
Formula

SPILL− OVER−
ASSIGNMENT− REDIRECTION [DURING− ASSIGNMENTS]
FACTOR− = ∗ 100%
TOTAL− CALLS+
DIRECTED− RETRY
Analysis

Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (the value used in this formula uses bins 0
TOTAL_CALLS.
18-116 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application SPILL_OVER_FACTOR_MULTIBAND
SPILL_OVER_FACTOR_MULTIBAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SPILL_OVER_FACTOR_MULTIBAND statistic tracks the percentage of successful call

set-ups initiated in a cell which completed TCH assignment in a neighboring cell through a
multiband handover.
NOTE
• It is not possible to run PM report for the SPILL_OVER_FACTOR_MULTIBAND

statistic since the PM GUI does not support it.
Formula
SPILL− OVER−
ASSIGNMENT− REDIRECTION [MULTIBAND− BAND] ∗
FACTOR− = 100
TOTAL− CALLS+
MULTIBAND ASSIGNMENT− REDIRECTION [DIRECTED− RETRY] +
Analysis

Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (the value used in this formula uses the
TOTAL_CALLS.
68P02901W56-T 18-117
Jan 2010
TCH_ACCESSES Chapter 18: Network health reports
TCH_ACCESSES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_ACCESSES statistic tracks the number of TCH activations which result in a successful
seizure by the MS.
Formula
Cell Level
TOTAL− CALLS+
TCH− ACCESSES = IN− INTER− BSS− HO− SUCCESS− RATE+
IN− INTRA− BSS− HO− SUCCESS− RATE
BSS Level
TOTAL− CALLS+
IN− INTER− BSS− HO− SUCCESS− RATE+
TCH− ACCESSES = ASSIGNMENT− REDIRECTION [DIRECTED− RETRY] +
Network Level
TOTAL− CALLS+
TCH− ACCESSES = ASSIGNMENT− REDIRECTION [DIRECTED− ENTRY] +
18-118 68P02901W56-T
Jan 2010
Analysis
Usage Handover.
Quality of service.
Network planning.
Type Counter.
TOTAL_CALLS.
68P02901W56-T 18-119
Jan 2010
TCH_CONGESTION_TIME Chapter 18: Network health reports
TCH_CONGESTION_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all TCHs
are busy.
Formula
(TCH− CONGESTION + TCH− CONGESTION− HR)

TCH− CONGESTION− TIME =
1000
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
Additional TCH_CONGESTION_HR.
Raw Statistic
for Half Rate
18-120 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_CONGESTION_TIME_INNER_ZONE
TCH_CONGESTION_TIME_INNER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_TIME_INNER_ZONE statistic tracks the amount of time in seconds

that all inner zone TCHs are busy.
Formula
!
TCH− CONGESTION− INNER− ZONE+
TCH− CONGESTION− TIME− TCH− CONGESTION− INNER− ZONE− HR
=
INNER− ZONE 1000
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION_INNER_ZONE.
TCH_CONGESTION_INNER_ZONE_HR
68P02901W56-T 18-121
Jan 2010
TCH_CONGESTION_TIME_INNER_ZONE_HR Chapter 18: Network health reports
TCH_CONGESTION_TIME_INNER_ZONE_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_TIME_INNER_ZONE_HR statistic tracks the amount of time in

seconds that all half rate inner zone TCHs are busy.
Formula
TCH− CONGESTION− TIME−

= TCH− CONG− INNER− ZONE− HR/1000
INNER− ZONE− HR
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION_INNER_ZONE_HR
18-122 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_CONGESTION_TIME_OUTER_ZONE
TCH_CONGESTION_TIME_OUTER_ZONE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_TIME_OUTER_ZONE statistic tracks the amount of time in seconds

that all outer zone TCHs are busy.
Formula
!
TCH− CONGESTION+
TCH− CONGESTION− TIME− TCH− CONGESTION− HR
=
OUTER− ZONE 1000
When the Half Rate feature is unrestricted, the following formula tracks the amount of time in
seconds that all outer zone half rate TCHs are busy:
TCH− CONGESTION− TIME− TCH− CONGESTION− HR

=
OUTER− ZONE− HR 1000
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
Additional TCH_CONGESTION_HR.
Raw Statistic
for Half Rate
68P02901W56-T 18-123
Jan 2010
TCH_RF_LOSS_RATE Chapter 18: Network health reports
TCH_RF_LOSS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_RF_LOSS_RATE statistic tracks the percentage of TCH resources that are abnormally
released due to a failure on the radio interface.
Formula
Cell Level
TCH− RF−
RF− LOSSES− TCH
LOSS− =   ∗ 100
TOTAL− CALLS+
RATE  
 IN− INTRA− BSS− HO [IN− INTRA− BSS− HO− SUCCESS− RATE] + 
 
BSS Level

= 100
ASSIGNMENT− REDIRECTION [DIRECTED− ENTRY] +
Network Level

= 100
18-124 68P02901W56-T
Jan 2010
Analysis

Fault finding.
Basis Cell.
Type Percentage.
RF_LOSSES_TCH.
TOTAL_CALLS.
68P02901W56-T 18-125
Jan 2010
TCH_TRAFFIC_CARRIED Chapter 18: Network health reports
TCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs.
Formula
For an individual cell for an individual statistics interval:
TCH− TRAFFIC− CARRIED = BUSY− TCH− MEAN
x=m
X
x=1
x=n
X
x=1
 x=m 
P
x=n
X  x=1 BUSY − TCH− MEAN [x]

TCH− TRAFFIC− CARRIED =  
 m 
x=1
18-126 68P02901W56-T
Jan 2010
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
68P02901W56-T 18-127
Jan 2010
TCH_TRAFFIC_CARRIED_FR Chapter 18: Network health reports
TCH_TRAFFIC_CARRIED_FR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED_FR statistic tracks the mean number of full rate busy TCHs.
Formula
(BUSY− TCH− MEAN − BUSY− TCH− HR− MEAN)

TCH− TRAFFIC− CARRIED− FR =
INTERVAL− SUM
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
BUSY_TCH_HR_MEAN.
18-128 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH_TRAFFIC_CARRIED_HR
TCH_TRAFFIC_CARRIED_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED_HR statistic tracks the mean number of half rate busy TCHs.
Formula
BUSY− TCH− HR− MEAN

TCH− TRAFFIC− CARRIED− HR =
INTERVAL− SUM
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Raw BUSY_TCH_HR_MEAN.
Statistics INTERVAL_SUM.
68P02901W56-T 18-129
Jan 2010
UL_BANDWIDTH_INDICATOR_EGPRS Chapter 18: Network health reports
UL_BANDWIDTH_INDICATOR_EGPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_BANDWIDTH_INDICATOR_EGPRS statistic provides the average uplink block size as

a function of the average used coding schemes shown in Table 18-3.
Table 18-3 Average block size used for EGPRS coding schemes

MCS-1 22
MCS-2 28
MCS-3 37
MCS-4 44
MCS-5 56
MCS-6 74
MCS-7 112
MCS-8 136
MCS-9 148
Formula
UL− BANDWIDTH− A+B+C

=  MCS−9
P 
INDICATOR− EGPRS
(UL− RLC− ACK− NEW− BLKS) +
 MCS−1 
 MCS−9 
 P 
 
 MCS−1 (UL− RLC− UNACK− NEW− BLKS) + 
 
 P
MCS−9 
(UL− RLC− RETX− BLKS)
MCS−1
18-130 68P02901W56-T
Jan 2010
where:
(UL− RLC− ACK− NEW− BLKS [MCS − 1]) ∗ 22+

A = (UL− RLC− ACK− NEW− BLKS [MCS − 5]) ∗ 56+
(UL− RLC− ACK− NEW− BLKS [MCS − 9]) ∗ 148
(UL− RLC− UNACK− NEW− BLKS [MCS − 1]) ∗ 22+

B = (UL− RLC− UNACK− NEW− BLKS [MCS − 5]) ∗ 56+
(UL− RLC− UNACK− NEW− BLKS [MCS − 9]) ∗ 148
(UL− RLC− RETX− BLKS [MCS − 1]) ∗ 22+

C = (UL− RLC− RETX− BLKS [MCS − 5]) ∗ 56+
(UL− RLC− RETX− BLKS [MCS − 9]) ∗ 148
Analysis

scheme usage).
Basis Cell.
Type Counter.
Raw Statistics UL_RLC_ACK_NEW_BLKS.
UL_RLC_RETX_BLKS.
68P02901W56-T 18-131
Jan 2010
UL_BANDWIDTH_INDICATOR_GPRS Chapter 18: Network health reports
UL_BANDWIDTH_INDICATOR_GPRS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_BANDWIDTH_INDICATOR_GPRS statistic provides the average uplink block size as a

function of the average used coding schemes shown in Table 18-4.
Table 18-4 Average block size used for GPRS coding schemes

CS-1 22
CS-2 33
CS-3 39
CS-4 53
Formula
 
(UL− RLC− ACK− NEW− BLKS [CS − 1]) ∗ 22+
 (UL− RLC− ACK− NEW− BLKS [CS − 2]) ∗ 33+ 
 
 
 
 
 (UL− RLC− UNACK− NEW− BLKS [CS − 1]) ∗ 22+ 
 
 
 
 (UL RLC UNACK NEW BLKS [CS − 4]) ∗ 53+ 
 − − − − 
 
 (UL− RLC− RETX− BLKS [CS − 1]) ∗ 22+ 
 
 (UL − RLC− RETX− BLKS [CS − 2]) ∗ 33+ 
 
 (UL− RLC− RETX− BLKS [CS − 3]) ∗ 39+ 
UL− BANDWIDTH− (UL− RLC− RETX− BLKS [CS − 4]) ∗ 53
=  CS−4P 
INDICATOR− GPRS
(UL− RLC− ACK− NEW− BLKS) +
 CS−1 
 CS−4 
 P 
 
 CS−1 (UL− RLC− UNACK− NEW− BLKS) + 
 
 P
CS−4 
(UL− RLC− RETX− BLKS)
CS−1
18-132 68P02901W56-T
Jan 2010
Analysis

scheme usage).
Basis Cell.
Type Counter.
Raw Statistics UL_RLC_ACK_NEW_BLKS.
UL_RLC_RETX_BLKS.
68P02901W56-T 18-133
Jan 2010
18-134 68P02901W56-T
Jan 2010
Chapter
19
Ladder diagrams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
68P02901W56-T 19-1
Jan 2010
Introduction Chapter 19: Ladder diagrams
Introduction
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Ladder diagrams show the relationships between MS, BSS, and MSC when a message flows
between these network elements. The following topics are described in this chapter:
• Ladder diagram constructs on page 19-3.
• GSM call model on page 19-4.
• Call procedure milestones on page 19-6.
• Call setup and handover on page 19-7.
• Assignment to TCH on page 19-18.
• Intra-cell handover on page 19-23.
• Inter-BSS handover on page 19-27.
• Enhanced 2G/3G handover and reselection on page 19-41.
• Network assisted cell change on page 19-44.
• Call clearing on page 19-47.
• Short message service on page 19-51.
• Congestion relief on page 19-53.
• Directed retry on page 19-55.
• Flow control on page 19-57.
• Intra-BSS interband activity on page 19-58.
• Inter-BSS interband activity on page 19-62.
• Interband assignment on page 19-66.
• Band Reassignment on page 19-67.
• RSL link scenarios on page 19-69.
• MTL link scenarios on page 19-71.
• GBL statistics on page 19-76.
• Accessibility statistics on page 19-81.
• Throughput statistics on page 19-87.
19-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Ladder diagram constructs
Ladder diagram constructs

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Ladder diagrams are used to:

• Show the relationships between the MS, BSS, and MSC elements represented as vertical
lines.
• Provide a visual aid in tracing the statistical processes involved when an event occurs.
The message flows between the network elements are presented as horizontal lines representing
a sequential flow of events. Arrows indicate the direction of the message flow. Message names
are placed above the directional line.
Intermediate network element functions are placed on the vertical lines as a sequential
reference. Parallel functions may also be included as separate vertical lines for additional
reference.
Statistics associated with individual messages are located immediately below the directional
line. All the statistics that may be generated as the result of the process flow is listed on the
diagram.
As an example, Figure 19-1 shows the relationships associated with an immediate assignment
failure.
Figure 19-1 Diagram of immediate assignment failure
68P02901W56-T 19-3
Jan 2010
GSM call model Chapter 19: Ladder diagrams
GSM call model

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The GSM call model comprises:

• BSS functions
• BSC functions
• MSC functions
• Handover procedure
BSS functions
The GSM BSS is a combination of digital and RF equipment, which provides the radio
Air interface linking subscribers into the network and providing them with service. The
BSS function communicates with the Mobile Switching Center (MSC), the Operations and
Maintenance Center - Radio (OMC-R), and the Mobile Subscribers (MSs).
BSC functions
The main functions of the BSC include managing the radio channels and transferring control
messages to and from the MS. Control channels and bearer channels are always under the
control of the BSC. However, many types of call handling messages do not directly affect the
BSC and for these the BSC serves simply as a relay point between the MSC and the MS.
The BSC also incorporates a digital switching matrix. No fixed correspondence exists between
the radio channels at the BSS and the terrestrial circuits, which connect the BSS to the MSC.
While the BSC selects the radio channel, the terrestrial circuit is selected by the MSC, and it
is the BSCs switching matrix that is used to connect the two together. The switching matrix
also allows the BSC to perform handovers between the BTSs under its control without involving
the MSC (intra-BSS and intra-cell).
MSC functions
The MSC handles the call set up procedures and controls the location registration and handover
procedures for all except intra-BSS and intra-cell handovers. MSC controlled intra-BSS
handovers can be set as an option at the switch. Location registration (and location update)
allows MSs to report changes in their locations enabling automatic completion of MS-terminated
calls.
19-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover procedure
Handover procedure
The handover procedure preserves call connections as MSs move from one radio coverage area
to another during an established call. Handovers within cells controlled by a single BSC are
handled by that BSC (intra-BSS and intra-cell). When handovers are between cells controlled by
different BSCs, the primary control is at the MSC (inter-BSS). Handovers can also be performed
between BSSs connected to two different MSCs (inter-MSC handover). In this case, GSM
specifications define standard procedures allowing the two MSCs to coordinate the handover.
Figure 19-2 Handover procedure
68P02901W56-T 19-5
Jan 2010
Call procedure milestones Chapter 19: Ladder diagrams
Call procedure milestones

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
A general description of the milestones in a call procedure is explained in the following

paragraphs.
Call procedure
Bids
The first call procedure milestone is a request for service or resource (channel assignment
request). The MS checks the possibility of calling, before attempting to make a call.
Bids - bids blocked
A bid is made for a resource (channel assignment request) but, if all channels are busy, due to
other subscribers making phone calls, the bid is blocked. Further bids are requested until a no
blocking situation exists.
Bids - attempts
A bid is made and accepted to use a resource (channel assignment request). Now an attempt is
made to assign the user to that resource, for example with a traffic channel assignment there
is an assignment request from the MSC, but at this time the assignment to the TCH is not
complete. Hence, the connection is not complete.
Bids - attempts - successes
An attempt has been made to assign a resource (channel assignment request) and the
assignment is successful, hence the connection is complete.
Bids - attempt - failures (dropped)
An attempt is made to assign a resource (channel assignment request) but the assignment fails.
It is not possible to recover the call and the call is lost.
Bids - attempt - fail - recovered
A resource is allocated to an MS which it found to be unusable. The call in progress was not lost
but was able to revert to its previous radio resource.
19-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Call setup and handover
Call setup and handover

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistics describe the behavior of the major call processing scenarios.
Statistics matrix
The call setup and handover statistics are shown as a matrix against call processing scenarios
in Table 19-1. Each call processing scenario is broken out into six call procedure milestones
shown in the vertical columns of the matrix.
Table 19-1 Call setup and handover statistics matrix
Milestones
Procedure Failed
Bids Blocked Attempts Success Failed lost
recovered
ImmediateOK_ACC_ CHAN_REQ_ See note 3 OK_ACC_ CHAN_REQ_ N/A
Assign PROC_RACH MS_BLK and PROC MS_FAIL
ment and ALLOC_ ALLOC_SDCCH_ CAUSE_IN_RACH
SDCCH FAIL (see note (see note 5)
(see note 1) 2)
Connection - - CONN_REQ_ - CONN_ N/A
Establish TO_MSC REFUSED
ment
Assign MA_REQ_ MA_CMD_ MA_CMD_ TOTAL_CALLS For further MA_FAIL_
ment FROM_MSC TO_MS_ TO_MSC and study FROM_MS
to TCH BLKDALLOC_ MA_COMPLETE_
at call TCH_FAIL TO_MSCALLOC_
set-up TCH
Handover INTRA_CELL_ ALLOC_SDCCH_ INTRA_ INTRA_CELL_ INTRA_ INTRA_
Intra-cell HO_REQ FAIL or CELL_ HO CELL_ CELL_
HO_FAIL_ HO_ATMPT HO_LOSTMS HO_FAIL
NO_ and and
RESOURCES MA_CMD_ MA_FAIL_
(INTER_BSS) TO_MS FROM_MS
or
ALLOC_TCH_
FAIL
Continued
68P02901W56-T 19-7
Jan 2010
Statistics matrix Chapter 19: Ladder diagrams
Table 19-1 Call setup and handover statistics matrix (Continued)

Milestones
Procedure Failed
Bids Blocked Attempts Success Failed lost
recovered
Handover OUT_INTRA_ OUT_INTRA_ OUT_ OUT_INTRA_ OUT_INTRA_ OUT_
Intra-BSS BSS_HO_ HO_PRI _BLK INTRA_ BSS_HO and BSS_HO INTRA_
(outgoing) REQ or BSS_HO OUT_HO_ _LOSTMS BSS_HO_
HO_FAIL_ _ATMPT NC_SUC FAIL
NO_ and
RESOURCES OUT_HO_
(INTRA_BSS) CAUSE_ATMPT
and
OUT_HO_
NC_CAUSE
_ATMPT
Handover OUT_INTER_ HO_FAIL_ OUT_ OUT_INTER_ OUT_INTER_ OUT_
Inter-BSS BSS_REQ _ NO_ INTER_ BSS_HO BSS_HO INTER_
(outgoing) TO_MSC RESOURCES BSS_HO _SUC _LOSTMS BSS_HO
(INTER_BSS) _ATMPT _RETURN
and
OUT_HO_
CAUSE_AT
MPT and
OUT_HO_
NC_CAUSE
_ATMPT
Handover For further For further IN_INTRA_ IN_INTRA_ IN_INTRA_ IN_
Intra-BSS study study ALLOC_ BSS_NC_ BSS_HO_SUC BSS_HO_ INTRA_
(incoming) SDCCH_ ATMPT or and LOSTMS BSS_HO_
FAIL or ALLOC_ IN_INTRA_ RETURN
ALLOC_TCH_ SDCCH or BSS_NC_SUC
FAIL ALLOC_TCH
Handover For further For further HO_REQ_ IN_INTER_ IN_INTER_ IN_
Inter-BSS study study see note ACK_TO_ BSS_HO BSS_HO INTER_
(incoming) 4 ALLOC_ MSC [IN_INTER_ BSS_HO
SDCCH_ ALLOC_ BSS_MS_ [IN_INTER_
FAIL or SDCCH or NO_SEIZE] BSS_MS_
ALLOC_TCH_ ALLOC_TCH NO_SEIZE]
FAIL
NOTE
The following refer to the call setup and handover matrix:
• OK_ACC_PROC_SUC_RACH may be, but is not necessarily equal to

ALLOC_SDCCH because they are pegged by different processes and
filtering takes place between the two pegs. ALLOC_SDCCH is pegged
at the target cell for SDCCH Handovers. If OK_ACC_PROC_SUC_RACH
is less than ALLOC_SDCCH, some of the ALLOC_SDCCH pegs are due
to SDCCH Handovers into the cell. And if ALLOC_SDCCH is less than
OK_ACC_PROC_SUC_RACH, some of the RACHs have been filtered between
the two pegs.
19-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Statistics matrix
• CHAN_REQ_MS_BLK may be, but is not necessarily equal to

ALLOC_SDCCH_FAIL. ALLOC_SDCCH_FAIL is pegged for Immediate
Assignment and also for SDCCH Handovers. CHAN_REQ_MS_BLK
is only pegged for Immediate Assignment. CHAN_REQ_MS_BLK and
ALLOC_SDCCH_FAIL only peg on SDCCH blocking.
• The total failed dropped calls is given by:
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]-)
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]-) (OUT_IN-
TER_BSS_HO[OUT_INTER_BSS_HO_LOST_MS])
• The statistic HO_REQ_MSC_FAIL covers all cases except for blocking (no
resources available).
• A phantom RACH or badly formed (invalid) channel request was detected, so no
resource was allocated and the call set-up procedure ended.
68P02901W56-T 19-9
Jan 2010
Connection establishment Chapter 19: Ladder diagrams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-3 to Figure 19-8 show the ladder diagrams for the connection establishment
procedures. Figure 19-3 shows that connection establishment is successful after immediate
assignment is successful, while Figure 19-8 shows successful MS-terminated connection
establishment.
Successful MS originated
Figure 19-3 shows a successful MS generated connection establishment.
NOTE
RSS Abis does additional filtering of RACH.
19-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Successful MS originated
Figure 19-3 Connection establishment successful
MS BSS MSC
OK_ACC_PROC_SUC_RACH (SEE NOTE)
ACCESS_PER_RACH
(for one of the causes)
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
IMMEDIATE ASSIGNMENT (AGCH) ACCESS_PER_AGCH
SABM + INITIAL LAYER 3 MESSAGE (SDCCH)

OK_ACC_PROC[CM SERV. REQ. - CALL]
- or -
OK_ACC_PROC[CM REESTABLISHMENT]
{ - or -
OK_ACC_PROC[PAGE RESPONSE]
- or -
OK_ACC_PROC[LOCATION UPDATE]
- or -
OK_ACC_PROC[IMSI DETACH]
IMMEDIATE ASSIGNMENT
CONNECTION REQUEST
< CR + COMPLETE LAYER 3 MSG.>
CONN_REQ_TO_MSC
CONNECTION CONFIRM
CONNECTION ESTABLISHMENT
MOBILE ORIGINATED
ti-GSM-Connection establishment successful-00350-ai-sw
68P02901W56-T 19-11
Jan 2010
Successful MS originated Chapter 19: Ladder diagrams
Figure 19-4 shows a successful MS generated connection establishment with FCS enabled.
Figure 19-4 Connection establishment successful with FCS enabled
MS BSS MSC
OK_ACC_PROC_SUC_RACH (SEE NOTE)
ACCESS_PER_RACH
ALLOC_TCH
ACCESS_PER_AGCH
IMMEDIATE ASSIGNMENT (AGCH)
SABM + INITIAL LAYER 3 MESSAGE (TCH)

OK_ACC_PROC[CM SERV. REQ. - CALL]
- or -
OK_ACC_PROC[CM REESTABLISHMENT]
{ - or -
OK_ACC_PROC[PAGE RESPONSE]
- or -
OK_ACC_PROC[LOCATION UPDATE]
- or -
OK_ACC_PROC[IMSI DETACH]
IMMEDIATE ASSIGNMENT
CONNECTION REQUEST
< CR + COMPLETE LAYER 3 MSG.>
CONN_REQ_TO_MSC
CONNECTION CONFIRM
CONNECTION ESTABLISHMENT
MOBILE ORIGINATED
19-12 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Failure
Failure
Figure 19-5 shows a connection establishment failure.
Figure 19-5 Connection establishment failure
68P02901W56-T 19-13
Jan 2010
Immediate assignment blocked Chapter 19: Ladder diagrams
Immediate assignment blocked
Figure 19-6 shows an immediate assignment blocked.
Figure 19-6 Immediate assignment blocked
19-14 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Immediate assignment failure
Immediate assignment failure
Figure 19-7 shows an immediate assignment failure.
Figure 19-7 Immediate assignment failure
68P02901W56-T 19-15
Jan 2010
Successful MS terminated call Chapter 19: Ladder diagrams
Successful MS terminated call
Figure 19-8 shows a successful connection establishment (MS terminated call).
NOTE
Figure 19-8 Connection establishment (mobile terminated call) successful
19-16 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Successful MS terminated call
Figure 19-9 shows a successful connection establishment (MS terminated call) with FCS
enabled.
Figure 19-9 Connection establishment (mobile terminated call) successful with FCS
enabled
68P02901W56-T 19-17
Jan 2010
Assignment to TCH Chapter 19: Ladder diagrams
Assignment to TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-10 to Figure 19-14 show the ladder diagrams for the assignment to TCH procedures.
Assignment successful
Figure 19-10 shows a successful TCH assignment.
NOTE
• Pegged for the first successful TCH assignment.

• Pegged to start the length of time spent on TCH by various types of MS. Will not
be pegged after the TCH is deallocated.
Figure 19-10 TCH assignment successful
19-18 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Assignment successful
Figure 19-11 shows a successful TCH assignment.
Figure 19-11 TCH assignment successful with FCS enabled
68P02901W56-T 19-19
Jan 2010
Immediate assignment failure Chapter 19: Ladder diagrams
Immediate assignment failure
Figure 19-12 shows an immediate assignment failure.
Figure 19-12 Immediate assignment failure

MS BSS MSC
(SEE NOTE )
NOTE:
ti-GSM-TCH assignmentiImmediate assignment failure-00356-ai-sw
19-20 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application TCH assignment blocked
TCH assignment blocked
Figure 19-13 shows a TCH assignment blocked.
Figure 19-13 TCH assignment blocked
68P02901W56-T 19-21
Jan 2010
Fail recovered Chapter 19: Ladder diagrams
Fail recovered
Figure 19-14 shows a TCH assignment fail-recovered to an SDCCH.
Figure 19-14 TCH assignment fail-recovered to SDCCH
19-22 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Intra-cell handover
Intra-cell handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-15 to Figure 19-18 show the ladder diagrams for the intra-cell handover procedure.
Intra-cell handovers deal with channels within the same cell; that is, the Target Cell = Source
Cell.
Handover successful
Figure 19-15 shows a successful intra-cell handover.
Figure 19-15 Handover (intra-cell) successful
ti-GSM-Intracell HO successful-00359-ai-sw
68P02901W56-T 19-23
Jan 2010
Handover blocked Chapter 19: Ladder diagrams
Handover blocked
Figure 19-16 shows an intra-cell handover blocked.
Figure 19-16 Handover (intra-cell) blocked
19-24 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Fail recovered
Fail recovered
Figure 19-17 shows an intra-cell handover fail-recovered to a source channel.
Figure 19-17 Handover (intra-cell) fail-recovered to source channel

MS MS
(SOURCE CHANNEL) BSS (TARGET CHANNEL)
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
ASSIGNMENT FAILURE
(SEE NOTE 2)
MA_FAIL_FROM_MS
INTRA_CELL_HO (INTRA_CELL_HO_FAIL)
NOTES:
1. Need for handover is recognized within the BSS.
2. Failure to access target channel.
NOTE:
The intracell handover may include the change of speech rate, which will subsequently will peg
the associated bin (FR_FR, HR_HR, HR_FR or FR_HR).
ti-GSM-Intracell HO fail recovered-00361-ai-sw
68P02901W56-T 19-25
Jan 2010
Fail lost Chapter 19: Ladder diagrams
Fail lost
Figure 19-18 shows an intra-cell handover fail-lost.
Figure 19-18 Handover (intra-cell) fail-lost

MS MS
(SOURCE CHANNEL) BSS (TARGET CHANNEL)
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
TIMEOUT
MSC
INTRA_CELL_HO (INTRA_CELL_HO_LOSTMS)
CLEAR (SEE NOTE 2)
REQUEST
CLR_REQ_TO_MSC
NOTES:
2. Failure to access target channel and no message receive on source channel prior to timer expiry.
NOTE:
The intracell handover may include the change of speech rate, which will subsequently will peg
the associated bin (FR_FR, HR_HR, HR_FR or FR_HR).
ti-GSM-Intracell HO fail lost-00362-ai-sw
19-26 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Inter-BSS handover
Inter-BSS handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-19 to Figure 19-22 show the ladder diagrams for the inter-BSS handover procedure.
Handover successful
Figure 19-19 shows a successful inter-BSS handover.
Figure 19-19 Handover (inter-BSS) successful
MS (SOURCE BSS MS (TARGET

BSS CHANNEL
CHANNEL (SOURCE) MSC (TARGET)
SOURCE CELL) TARGET CELL)
HANDOVER
REQUIRED (SEE NOTE 1) HANDOVER
OUT_INTER_BSS_HO REQUEST HO_REQ_FROM_MSC
(OUT_INTER_BSS_
REQ_TO_MSC) ALLOC_TCH
HANDOVER REQUEST or ALLOC_SDCCH
HANDOVER ACKNOWLEDGE
HANDOVER COMMAND
COMMAND HO_REQ_ACK_TO_MSC
OUT_INTER_BSS_HO (SEE NOTE 2)
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_
ATMPT
HANDOVER
OUT_HO_NC_ COMPLETE
CAUSE_ATMPT
HANDOVER IN_INTER_BSS_HO
CLEAR COMPLETE (IN_INTER_BSS_
COMMAND HO_SUC)
OUT_INTER_BSS_HO
(OUT_INTER_BSS
HO_SUC)
OUT_HO_NC_SUC
NOTES:
2. BAD_HO_REFNUM_MS pegs each time a handover access burst (actual or phantom) is
detected that contains a bad handover reference number.
ti-GSM-Intercell HO successful-00363-ai-sw
68P02901W56-T 19-27
Jan 2010
Handover blocked Chapter 19: Ladder diagrams
Handover blocked
Figure 19-20 shows an inter-BSS handover blocked.
Figure 19-20 Handover (inter-BSS) blocked

MS
(SOURCE MS (TARGET
CHANNEL BSS CHANNEL
BSS
SOURCE CELL) (SOURCE) MSC (TARGET) TARGET CELL)
HANDOVER HANDOVER
REQUIRED REQUEST
(SEE NOTE 1) HO_REQ_FROM_MSC
OUT_INTER_BSS_HO ALLOC_TCH_FAIL
(OUT_INTER_BSS_
HO_FAIL_NO_RESOURCES
REQ_TO_MSC) (INTER_BSS_HO)
HANDOVER FAILURE
(SEE NOTE 4)
HO_REQ_MSC_FAIL
HANDOVER (SEE NOTE 3)
REQUIRED
(SEE NOTE 2)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
REQ_TO_MSC)
NOTES:
2. If a need for handover continues to exist after timer expiry.
3. This pegs due to causes other than resource unavailable.
4. Reference GSM 8.08 Section 3.2.2.5 for valid "handover failure" causes.
ti-GSM-Intercell HO blocked-00364-ai-sw
19-28 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Fail recovered
Fail recovered
Figure 19-21 shows an inter-BSS handover fail-recovered.
Figure 19-21 Handover (inter-BSS) fail-recovered

MS
(SOURCE MS (TARGET
CHANNEL BSS BSS CHANNEL
SOURCE CELL) (SOURCE) MSC (TARGET) TARGET CELL)
HANDOVER REQUIRED
HANDOVER
(SEE NOTE 1)
REQUEST
HO_REQ_FROM_MSC
OUT_INTER_BSS_HO ALLOC_TCH
(OUT_INTER_BSS_REQ_
HANDOVER REQUEST or ALLOC_SDCCH
TO_MSC)
COMMAND
HANDOVER HO_REQ_ACK_TO_MSC
COMMAND (SEE NOTE 2)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_ATMPT
HANDOVER
FAILURE
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
RETURN)
HANDOVER
FAILURE
HO_REQ_MSC_FAIL
NOTES:
2. BAD_HO_REFNUM_MS pegs each time a handover access burst (actual or phantom) is
detected which contains a bad handover reference number.
ti-GSM-Intercell HO fail recovered-00365-ai-sw
68P02901W56-T 19-29
Jan 2010
Fail lost Chapter 19: Ladder diagrams
Fail lost
Figure 19-22 shows an inter-BSS handover fail-lost.
Figure 19-22 Handover (inter-BSS) fail-lost

MS
(SOURCE MS (TARGET
CHANNEL BSS BSS CHANNEL
SOURCE CELL) (SOURCE) (TARGET) TARGET CELL)
MSC
HANDOVER
RECOGNIZED
HANDOVER HANDOVER
REQUIRED REQUEST
HO_REQ_FROM_MSC
HANDOVER
REQUEST
COMMAND
HANDOVER
COMMAND
(SEE NOTE)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
LOSTMS)
NOTE:
After the handover command is sent to the MS, any of the following messages may be received
at the source BSS: SCCP_RELEASED, RELEASED_DONE, MTG_EXP, RADIO_CHAN_RLSD.
ti-GSM-Intercell HO fail lost-00366-ai-sw
19-30 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Fail lost (MS)
Fail lost (MS)
Figure 19-23 shows an inter-BSS handover failure with lost MS.
Figure 19-23 Inter-BSS handover failure with lost MS
68P02901W56-T 19-31
Jan 2010
Standard directed retry (external) Chapter 19: Ladder diagrams
Standard directed retry (external)
Figure 19-24 shows an inter-BSS handover directed retry external.
Figure 19-24 Inter-BSS handover directed retry external
19-32 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTER_HO_FAIL (Timer expires)
OUT_INTER_HO_FAIL (Timer expires)
Figure 19-25 shows an inter-BSS handover failure when the timer expires at the source BSS.
Figure 19-25 Inter-BSS handover failure when the timer expires
68P02901W56-T 19-33
Jan 2010
OUT_INTER_EQUIP_FAIL (Equipment Failure) Chapter 19: Ladder diagrams
OUT_INTER_EQUIP_FAIL (Equipment Failure)
Figure 19-26 shows an inter-BSS handover failure due to equipment failure.
Figure 19-26 Inter-BSS handover failure due to equipment failure
19-34 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application OUT_INTER_HO_CLEARED (Call clearing)
OUT_INTER_HO_CLEARED (Call clearing)
Figure 19-27 shows an inter-BSS handover failure because of call clearing in both NS and MSS.
Figure 19-27 Inter-BSS handover failure because of call clearing in both NS and MSS
68P02901W56-T 19-35
Jan 2010
Intra-BSS handover Chapter 19: Ladder diagrams
Intra-BSS handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-28 to Figure 19-31 show the ladder diagrams for the intra-BSS handover procedure.
Handover successful
Figure 19-28 shows a successful intra-BSS handover.
Figure 19-28 Handover (intra-BSS) successful
ti-GSM-IntraBSS HO successful-00369-ai-sw
19-36 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover- blocked
Handover- blocked
Figure 19-29 shows an intra-BSS handover-blocked.
Figure 19-29 Handover (intra-BSS) blocked
68P02901W56-T 19-37
Jan 2010
Fail-recovered Chapter 19: Ladder diagrams
Fail-recovered
Figure 19-30 shows an intra-BSS handover fail-recovered.
Figure 19-30 Handover (intra-BSS) fail-recovered

MS
(SOURCE CHANNEL BSS MS (TARGET CHANNEL
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH or ALLOC_SDCCH
(SEE NOTE 2)
HANDOVER COMMAND
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
HANDOVER FAILURE IN_INTRA_BSS_NC_ATMPT
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_RETURN)
(SEE NOTE 3)
NOTES:
2. BAD_HO_REFNUM_MS pegs each time a handover access burst (actual or phantom)
is detected that contains a bad handover reference number.
3. Failure to access channel in target cell.
ti-GSM-IntraBSS HO fail recovered-00371-ai-sw
19-38 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Fail-lost
Fail-lost
Figure 19-31 shows an intra-BSS handover fail-lost.
Figure 19-31 Handover (intra-BSS) fail-lost

MS MS (TARGET
(SOURCE CHANNEL CHANNEL
SOURCE CELL) BSS TARGET CELL)
OUT_INTRA_BSS_HO
(SEE NOTE 1)
HANDOVER COMMAND ALLOC_SDCCH or ALLOC_TCH

OUT_INTRA_BSS_HO
_ATMPT (SEE NOTE 2)
IN_INTRA_BSS_NC_ATMPT
OUT_INTRA_BSS_NC_ATMPT
MSC TIMEOUT
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_LOSTMS)
CLEAR (SEE NOTE 3)
REQUEST
CLR_REQ_TO_MSC
NOTES:
2. BAD_HO_REFNUM_MS pegs each time a handover access burst (actual or phantom) is detected
that contains a bad handover reference number.
3. Failure to access channel in target cell and no message received on channel in source cell
prior to timer expiry.
ti-GSM-IntraBSS HO fail lost-00372-ai-sw
68P02901W56-T 19-39
Jan 2010
Standard directed retry (internal) Chapter 19: Ladder diagrams
Standard directed retry (internal)
Figure 19-32 displays the ladder diagram for intra-BSS handover standard directed retry.
Figure 19-32 Intra-BSS handover standard directed retry
ti-GSM-IntraBSS HO failure directed retry-00373-ai-sw
19-40 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Enhanced 2G/3G handover and reselection
Enhanced 2G/3G handover and reselection

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-33 and Figure 19-34 show the ladder diagrams for enhanced 2G/3G handover and
cell reselection procedures.
68P02901W56-T 19-41
Jan 2010
2G/3G handover successful Chapter 19: Ladder diagrams
2G/3G handover successful
Figure 19-33 shows a successful 2G/3G handover scenario.
Figure 19-33 2G/3G handover successful
RNS CN BSS Multi-RAT

MSC
(3G MSC) MS
HANDOVER REQUIRED
BSSMAP BSSMAP
PREPARE HANDOVER
MAP/E MAP/E
NUM_HO_3G_ATTEMPTS
RELOCATION REQUEST
RANAP RANAP
RELOCATION REQUEST
ACKNOWLEDGE
RANAP RANAP
PREPARE HANDOVER
RESPONSE
MAP/E MAP/E
HANDOVER COMMAND
BSSMAP BSSMAP
OUT_HO_NC_CAUSE_
ATMPT
INTER SYSTEM TO UTRAN
RELOCATION DETECT HANDOVER COMMAND
RANAP RANAP RR RR
DCCH : HANDOVER TO UTRAN COMPLETE

RRC
RRC
RELOCATION COMPLETE
RANAP RANAP
SEND END SIGNAL

REQUEST
MAP/E MAP/E
CLEAR COMMAND
BSSMAP BSSMAP
NUM_HO_TO_3G_
SUCCESS
CLEAR COMPLETE OUT_HO_NC_SUC
BSSMAP BSSMAP
SEND END
SIGNAL RESPONSE
MAP/E MAP/E
ti-GSM-2G3G HO successful-00374-ai-sw
19-42 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application 2G/3G handover failure
2G/3G handover failure
Figure 19-34 shows a 2G/3G handover failure scenario.
Figure 19-34 2G/3G handover failure
RNS CN BSS Multi-RAT

MSC
(3G MSC) MS
HANDOVER REQUIRED
BSSMAP BSSMAP
PREPARE HANDOVER
MAP/E MAP/E
NUM_HO_3G_ATTEMPTS
RELOCATION REQUEST
RANAP RANAP
RELOCATION REQUEST
ACKNOWLEDGE
RANAP RANAP
PREPARE HANDOVER
RESPONSE
MAP/E MAP/E
HANDOVER COMMAND
BSSMAP BSSMAP
OUT_HO_NC_CAUSE_
ATMPT
INTER SYSTEM TO UTRAN
HANDOVER COMMAND
RR RR
HANDOVER FAILURE
(SEE NOTE)
RR RR
HANDOVER FAILURE
BSSMAP BSSMAP
68P02901W56-T 19-43
Jan 2010
Network assisted cell change Chapter 19: Ladder diagrams
Network assisted cell change

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-35 to Figure 19-39 show the ladder diagrams for network assisted cell change
procedures.
NACC cell selection agreement
Figure 19-35 shows the scenario where the network agrees with the MS target cell reselection.
Figure 19-35 Cell selection agreement
BSS MS
PCCN
PNCD
PCCC
ti-GSM-Stats-MS target agree NACC-eps-sw
19-44 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application No target cell information before sending a PCCC
No target cell information before sending a PCCC
Figure 19-36 shows the scenario where the network has no target cell information before
sending a PCCC.
Figure 19-36 No target cell information before sending a PCCC
BSS MS
PCCN
PCCC
ti-GSM-Stats-MS target no info PCCC NACC-eps-sw
New target cell for the MS
Figure 19-37 shows the scenario where the network evaluates a new target cell for the MS.
Figure 19-37 New target cell for the MS
BSS MS
PCCN
PNCD
PCCO
NUM_CELL_RESEL_CELL
ti-GSM-Stats-MS target eval NACC-eps-sw
68P02901W56-T 19-45
Jan 2010
No target cell information before sending a PCCO Chapter 19: Ladder diagrams
No target cell information before sending a PCCO
Figure 19-38 shows the scenario where the network has no target cell information before
sending a PCCO.
Figure 19-38 No target cell information before sending a PCCO
BSS MS
PCCN
PCCO
NUM_CELL_RESEL_CELL
ti-GSM-Stats-MS target no info PCCO NACC-eps-sw
NACC reselection not required
Figure 19-39 shows the scenario where the network evaluates that reselection is not required
for the MS.
Figure 19-39 Reselection not required
BSS MS
PCCN
PMO (NC2)
PMR(s)
PNCD
PCCO
NUM_CELL_RESEL_CELL
ti-GSM-Stats-cell resel not needed NACC-eps-sw
19-46 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Call clearing
Call clearing
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-40 to Figure 19-43 show the ladder diagrams for the call clearing procedures.
Cipher mode fail
Figure 19-40 shows BSS initiated call clearing - cipher mode fail.
Figure 19-40 BSS initiated call clearing-cipher mode fail
68P02901W56-T 19-47
Jan 2010
RF loss on an SDCCH Chapter 19: Ladder diagrams
RF loss on an SDCCH
Figure 19-41 shows BSS initiated call clearing (RF loss on an SDCCH).
Figure 19-41 BSS initiated call clearing (RF loss on an SDCCH)
19-48 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RF loss on a TCH
RF loss on a TCH
Figure 19-42 shows BSS initiated call clearing - RF loss on a TCH.
Figure 19-42 BSS initiated call clearing (RF loss on a TCH)
68P02901W56-T 19-49
Jan 2010
Queuing timeout Chapter 19: Ladder diagrams
Queuing timeout
Figure 19-43 shows BSS initiated call clearing (queuing timeout).
Figure 19-43 BSS initiated call clearing (queuing timeout)
19-50 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Short message service
Short message service

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-44 and Figure 19-45 show the ladder diagrams for the short message service
procedures.
MS originated
Figure 19-44 shows MS originated short message service (point-to-point).
Figure 19-44 MS originated short message service (point-to-point)
68P02901W56-T 19-51
Jan 2010
MS terminated Chapter 19: Ladder diagrams
MS terminated
Figure 19-45 shows MS terminated short message service (point-to-point).
Figure 19-45 MS terminated short message service (point-to-point)
19-52 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Congestion relief
Congestion relief
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Intra-BSS congestion relief example
Figure 19-46 shows an example of the relationships associated with an intra-BSS congestion
relief handover procedure. In this example, an MS attempts to access a TCH in the cell which is
congested and one (or possibly multiple) MS is handed out to free a TCH.
68P02901W56-T 19-53
Jan 2010
Intra-BSS congestion relief example Chapter 19: Ladder diagrams
Figure 19-46 Intra-BSS congestion relief handover procedure
ti-GSM-IntraBSS congestion relief HO-00387-ai-sw
19-54 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Directed retry
Directed retry
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Intra-BSS directed retry example
Figure 19-47 shows an example of the relationships associated with an intra-BSS directed
retry procedure.
68P02901W56-T 19-55
Jan 2010
Intra-BSS directed retry example Chapter 19: Ladder diagrams
Figure 19-47 Intra-BSS directed retry procedure
ti-GSM-IntraBSS directed retry-00388-ai-sw
19-56 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Flow control
Flow control
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
FLOW_CONTROL_BARRED measures the duration for which access classes are barred as a
result of flow control. The statistic duration is started when any of the access classes are
barred due to flow control and stopped when the last access class which was barred due to
flow control is unbarred.
Example
Figure 19-48 shows an example of the relationships associated with an access procedure.
Figure 19-48 Access procedure

BSS
START OF ACCESS CLASS

FLOW_CONTROL_BARRED
BARRING DUE TO FLOW
CONTROL.
DURATION
LAST ACCESS CLASS UN

BARRED FROM FLOW CON
TROL ACTIONS.
ti-GSM-Access procedure-00389-ai-sw
68P02901W56-T 19-57
Jan 2010
Intra-BSS interband activity Chapter 19: Ladder diagrams
Intra-BSS interband activity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-49 to Figure 19-51 show intra-BSS interband activity handover ladder diagrams.
These diagrams specifically show the outgoing handover statistics. By only showing outgoing
handover statistics, a better focus is placed on the pegging aspects of INTERBAND_ACTIVITY.
For a complete handover statistic pegging description (outgoing and incoming) refer to the
general handover ladder diagrams in this chapter.
19-58 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover successful
Handover successful
Figure 19-49 shows an established call on TCH with a subsequent successful intra-BSS
handover to a PGSM cell.
Figure 19-49 Successful intra-BSS handover
INTERBAND_ACTIVITY will peg different bins:
68P02901W56-T 19-59
Jan 2010
Handover unsuccessful (fail recovered) Chapter 19: Ladder diagrams
Handover unsuccessful (fail recovered)
Figure 19-50 shows an established call on TCH with a subsequent handover attempt to a PGSM
cell. The handover is unsuccessful with MS fail recovered to source cell (original channel).
Figure 19-50 Unsuccessful interband handover with fail-recovered source cell
19-60 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover
unsuccessful (fail recovered due to invalid frequency supported)
Handover unsuccessful (fail recovered due to invalid frequency

supported)
Figure 19-51 shows an established call on TCH with subsequent intra-BSS handover attempt
to PGSM cell. The handover is unsuccessful due to invalid frequency supported with MS fail
recovered to source cell (original channel).
Figure 19-51 Unsuccessful interband handover
for EGSM target cells, bins EGSM_HO_ATMPT & EGSM_HO_FAIL peg
68P02901W56-T 19-61
Jan 2010
Inter-BSS interband activity Chapter 19: Ladder diagrams
Inter-BSS interband activity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 19-52 to Figure 19-54 show inter-BSS interband activity handover ladder diagrams.
These diagrams specifically show the outgoing handover statistics. By only showing outgoing
handover statistics, a better focus is placed on the pegging aspects of INTERBAND_ACTIVITY.
For a complete handover statistic pegging description (outgoing and incoming) refer to the
general handover ladder diagrams in this chapter.
19-62 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover successful
Handover successful
Figure 19-52 shows an established call on TCH with a subsequent successful inter-BSS
handover to a PGSM cell.
Figure 19-52 Successful inter-BSS handover

MS (SOURCE BSS MS (TARGET
MSC BSS
CHANNEL (SOURCE) CHANNEL
(TARGET)
HANDOVER
REQUIRED (SEE NOTE 1)
HANDOVER
OUT_INTER_BSS_HO REQUEST
(OUT_INTER_BSS_RE ALLOC_TCH
Q_TO_MSC)
HANDOVER REQUEST MS_ACCESS_BY_TYPE
ACKNOWLEDGE (SEE NOTE 2)
HANDOVER
COMMAND
HANDOVER
COMMAND OUT_INTER_BSS_HO HO_REQ_ACK_TO_MSC
(OUT_INTER_BSS_HO_ (SEE NOTE 3)
ATMPT)
OUT_HO_CAUSE_
ATMPT
OUT_HO_NC_CAUSE_A
TMPT (BAND
HANDOVER) (SEE NOTE 4)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT)
HANDOVER
(SEE NOTE 5)
HANDOVER COMPLETE
CLEAR COMPLETE
COMMAND
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO
_SUC)
OUT_HO_NC_SUC
NOTES:
2. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability; MSC must have
Classmark Update message from the mobile so that the target BSS can peg the MS access
type.
which contains a band handover reference number.
4. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT and
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover.
Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level,
etc). Band handover triggered handovers are done to move the mobile from its current
frequency band to a preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will
peg. For example, the above ladder diagram applies for other frequency bands, except that
for DCS1800 target cells, bin DCS1800_HO_ATMPT pegs
for PCS1900 target cells, bin PCS1900_HO_ATMPT pegs
for EGSM target cells, bin EGSM_HO_ATMPT pegs
ti-GSM-InterBSS HO successful-00393-ai-sw
68P02901W56-T 19-63
Jan 2010
Figure 19-53 shows an established call on TCH with a subsequent inter-BSS handover attempt
to a PGSM cell. The handover is unsuccessful with MS fail recovered to source cell (original
channel).
Figure 19-53 Inter-BSS handover unsuccessful with fail-recovered source cell

MS (SOURCE BSS MSC BSS MS (TARGET
CHANNEL (SOURCE) (TARGET) CHANNEL
HANDOVER
REQUEST
(OUT_INTER_BSS_RE
MS_ACCESS_BY_TYPE
Q_TO_MSC) HANDOVER REQUEST (SEE NOTE 2)
COMMAND
HANDOVER
COMMAND OUT_INTER_BSS_HO HO_REQ_ACK_TO_MSC
(OUT_INTER_BSS_HO_ (SEE NOTE 3)
ATMPT)
OUT_HO_CAUSE_
ATMPT
OUT_HO_NC_CAUSE_A
TMPT (BAND
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT)
HANDOVER (SEE NOTE 5)
FAILURE
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO
_RETURN)
INTERBAND_ACTIVITY
(PGSM_HO_FAIL)
(SEE NOTE 5)
HANDOVER
FAILURE
HO_REQ_MSC_FAIL
NOTES:
Classmark Update message from the mobile so that the target BSS can peg the MS access
type.
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover.
Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level,
etc). Band handover triggered handovers are done to move the mobile from its current
frequency band to a preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg.
For example, the above ladder diagram applies for other frequency bands, except that
for DCS1800 target cells, bins DCS1800_HO_ATMPT and DCS1800_HO_FAIL peg
for PCS1900 target cells, bins PCS1900_HO_ATMPT and PCS1900_HO_FAIL peg
for EGSM target cells, bins EGSM_HO_ATMPT and EGSM_HO_FAIL peg
ti-GSM-InterBSS HO fail recovered source cell-00394-ai-sw
19-64 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Handover
unsuccessful fail recovered due to invalid frequency supported
Handover unsuccessful fail recovered due to invalid frequency

supported
Figure 19-54 shows an established call on a TCH with subsequent inter-BSS handover attempt
to a PGSM cell. The handover is unsuccessful due to invalid frequency supported with MS fail
recovered to source cell (original channel).
Figure 19-54 Inter-BSS handover unsuccessful due to invalid frequency supported

MS (SOURCE BSS MSC BSS MS (TARGET
CHANNEL (SOURCE) (TARGET) CHANNEL
SOURCE CELL) HANDOVER TARGET CELL)
REQUEST
(OUT_INTER_BSS_REQ
_TO_MSC) MS_ACCESS_BY
HANDOVER REQUEST _TYPE (SEE NOTE 2)
COMMAND
HANDOVER
COMMAND HO_REQ_ACK_TO_MSC
OUT_INTER_BSS_HO (SEE NOTE 3)
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_
ATMPT
OUT_HO_NC_CAUSE_A
TMPT (BAND
INTERBAND_ACTIVITY
HANDOVER (PGSM_HO_ATMPT)
FAILURE (SEE NOTE 5)
REASON- OUT_INTER_BSS_HO
FREQUENCY (OUT_INTER_BSS_HO
NOT _RETURN)
IMPLEMENTED
INTERBAND_ACTIVITY
(PGSM_HO_FAIL)
(SEE NOTE 5)
INTERBAND_ACTIVITY
(INVALID_FREQ_HO)
HANDOVER
FAILURE
REASON-
FREQUENCY
NOT
IMPLEMENTED
NOTES: HO_REQ_MSC_FAIL
Classmark Update message from the mobile so that the target BSS can peg the MS access type.
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover. Other
causes are possible and valid as well (like powerbudget, uplink quality, downlink level, etc). Band
handover triggered handovers are done to move the mobile from its current frequency band to a
preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg.
For example, the above ladder diagram applies for other frequency bands, except that
INTERBAND_ACTIVITY will peg different bins. Examples
for DCS1800 target cells, bins DCS1800_HO_ATMPT and DCS1800_HO_FAIL peg
ti-GSM-InterBSS HO fail invalid frequency -00395-ai-sw
68P02901W56-T 19-65
Jan 2010
Interband assignment Chapter 19: Ladder diagrams
Interband assignment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Interband activity invalid frequency at assignment
Figure 19-55 shows an invalid frequency at assignment.
Figure 19-55 Invalid frequency at assignment

MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH
MS_ACCESS_BY_TYPE (SEE NOTE)
ASSIGNMENT
COMMAND
MA_CMD_TO_MS
ASSIGNMENT
FAILURE
REASON-
FREQUENCY NOT
IMPLEMENTED
INTERBAND_ACTIVITY (INVALID_FREQ_ASGN)
MA_FAIL_FROM_MS
ASSIGNMENT FAILURE
REASON-FREQUENCY NOT IMPLEMENTED
NOTE: MS_ACCESS_BY_TYPE pegs the bin that matches the MS capability.
ti-GSM-Invalid freq assignment-00396-ai-sw
19-66 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Band Reassignment
Band Reassignment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 19-56 and Figure 19-57 show band reassign ladder diagrams. These diagrams specifically
show the outgoing handover statistics. By only showing outgoing handover statistics, a better
focus is placed on the pegging aspects of the band reassign cause.
Handover successful
Figure 19-56 shows an intra-BSS handover attempt of an MS from an SDCCH in the source
cell (frequency band PGSM) to a TCH in a target cell (frequency band DCS1800). The MS is
a dual-mode PGSM/DCS1800 capable MS.
Figure 19-56 Intra-BSS handover successful

MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
ALLOC_TCH (TARGET CELL)
MS_ACCESS_BY_TYPE (TARGET CELL)

(MS_PGSM_DCS1800)
HANDOVER
COMMAND
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_RE_ASSIGN)
INTERBAND_ACTIVITY
HANDOVER (DCS1800_HO_ATMPT)
COMPLETE
(RECEIVED FROM OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC)
TARGET CELL)
OUT_HO_NC_SUC
ti-GSM-IntraBSS HO successful-00397-ai-sw
68P02901W56-T 19-67
Jan 2010
Figure 19-57 shows an unsuccessful band reassign.
Figure 19-57 Unsuccessful band reassign

MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
ALLOC_TCH (TARGET CELL)
MS_ACCESS_BY_TYPE (TARGET CELL)

(MS_PGSM_DCS1800)
HANDOVER
COMMAND
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_RE_ASSIGN)
INTERBAND_ACTIVITY
(DCS1800_HO_ATMPT)
HANDOVER
FAILURE
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_RETURN)
INTERBAND_ACTIVITY
(DCS1800_HO_FAIL)
ti-GSM-Unsuccessful band reassign-00398-ai-sw
19-68 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application RSL link scenarios
RSL link scenarios

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 19-58 shows a ladder diagram scenario for the Radio Signaling Link (RSL) link.
68P02901W56-T 19-69
Jan 2010
Introduction Chapter 19: Ladder diagrams
Figure 19-58 RSL link scenarios
19-70 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTL link scenarios
MTL link scenarios

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to MTL link scenarios
Figure 19-59 to Figure 19-62 show four ladder diagrams as scenarios for the Message Transfer
Link (MTL) link.
68P02901W56-T 19-71
Jan 2010
MTL link (operator initiated outage) Chapter 19: Ladder diagrams
MTL link (operator initiated outage)
Figure 19-59 MTL link scenario (Part I)
NOTE
Lock of MTL or associated device transitions operator and admin states from B-U
to D-L
Unlock of MTL or associated device transitions operator and admin states from D-L to
B-U.
19-72 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTL link (transition scenarios Part II)
MTL link (transition scenarios Part II)
Figure 19-60 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait.
Figure 19-60 MTL link transition scenarios (Part II)
68P02901W56-T 19-73
Jan 2010
MTL link (transition scenarios Part III) Chapter 19: Ladder diagrams
MTL link (transition scenarios Part III)
Figure 19-61 shows an MTL transition from B-U to D-U and D-U to B-U with reason 'Wait MMS
not in service'.
Figure 19-61 MTL link transition scenarios (Part III)
19-74 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application MTL link (transition scenarios Part IV)
MTL link (transition scenarios Part IV)
Figure 19-62 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait
improper timeslot mapping between BSC and MSC.
Figure 19-62 MTL link transition scenarios (Part IV)
68P02901W56-T 19-75
Jan 2010
GBL statistics Chapter 19: Ladder diagrams
GBL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to GBL statistics
Figure 19-63 to Figure 19-67 show how the GBL statistics function within the BSS/PCU.
GBL_DL_DATA_THRPUT
Figure 19-63 shows GBL_DL_DATA_THRPUT.
Figure 19-63 GBL_DL_DATA_THRPUT
DLCI = 45 DLCI = 45
DLCI = 55
Bearer chan 1
DLCI = 55
ti-GSM-GBL_DL_DATA_THRPUT-00404-ai-sw
19-76 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Introduction to GBL statistics
GBL_FLOW_CTRL_SENT
Figure 19-64 is a ladder diagram detailing the statistic GBL_FLOW_CTRL_SENT when it is

pegged. It also shows the request and the response messages sent from the BSS/PCU to the
SGSN.
Figure 19-64 GBL_FLOW_CTRL_SENT
68P02901W56-T 19-77
Jan 2010
Introduction to GBL statistics Chapter 19: Ladder diagrams
CELL_FLUSH_REQS
Figure 19-65 illustrates the statistic CELL_FLUSH_REQS when it is pegged. It also shows the
request and the response sent from the SGSN to the PS.
Figure 19-65 CELL_FLUSH_REQS
19-78 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Introduction to GBL statistics
GBL_PAGING_REQS
Figure 19-66 is a ladder diagram detailing the statistic GBL_PAGING_REQS when it is pegged.
It also shows the request and the response messages sent from the SGSN to the BSS/PCU
and the MS.
Figure 19-66 GBL_PAGING_REQS
68P02901W56-T 19-79
Jan 2010
Introduction to GBL statistics Chapter 19: Ladder diagrams
GBL_UL_DATA_THRPUT
Figure 19-67 illustrates the statistic GBL_UL_DATA_THRPUT.
Figure 19-67 GBL_UL_DATA_THRPUT
19-80 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Accessibility statistics
Accessibility statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to accessibility statistics
Figure 19-68 through Figure 19-73 illustrate accessibility statistics.
CHANNEL_REQS_REC
Figure 19-68 illustrates the ladder diagram for CHANNEL_REQS_REC.
Figure 19-68 CHANNEL_REQS_REC
68P02901W56-T 19-81
Jan 2010
Introduction to accessibility statistics Chapter 19: Ladder diagrams
CHANNEL_REQS_REJECT
Figure 19-69 is a ladder diagram detailing the statistic CHANNEL_REQS_REJECT when it is

pegged. It also shows the request and the response messages sent from the BSS/PCU to the MS.
Figure 19-69 Accessibility CHANNEL_REQ_REJECT
19-82 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Introduction to accessibility statistics
CHANNEL_REQS_SUCCESS
Figure 19-70 illustrates the ladder diagram for CHANNEL_REQS_SUCCESS.
Figure 19-70 CHANNEL_REQS_SUCCESS
MS
68P02901W56-T 19-83
Jan 2010
Channel request (RACH) and immediate assignment (AGCH)
Figure 19-71 is a ladder diagram detailing the statistics GPRS_ACCESS_PER_RACH and

GPRS_ACCESS_PER_AGCH when pegging occurs. It also shows the request and the response
messages sent from the BSS/PCU to the MS.
Figure 19-71 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH
BSS/PCU M
S
Channel Request (RACH)
GPRS_ACCESS_PER_RACH
GPRS_ACCESS_PER_AGCH
Immediate Assignment (AGCH)
ti-GSM-GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH-00412-ai-sw
19-84 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Introduction to accessibility statistics
Accessibility and GBL statistics
Figure 19-72 is a ladder diagram detailing the statistics GBL_PAGING_REQS,

GPRS_ACCESS_PER_RACH, and GPRS_ACCESS_PER_AGCH when pegging occurs. It also
shows the request and response messages sent from the SGSN to the BSS/PCU and to the MS.
Figure 19-72 Accessibility and GBL statistics
MS
68P02901W56-T 19-85
Jan 2010
GPRS_CHANNELS_SWITCHED
Figure 19-73 details the GPRS_CHANNELS_SWITCHED statistic.
Figure 19-73 GPRS_CHANNELS_SWITCHED
SW SW SW SW RES RES RES

TCH
GPRS GPRS GPRS GPRS GPRS GPRS GPRS
SW SW SW RES RES RES

TCH TCH
GPRS GPRS GPRS GPRS GPRS GPRS
ti-GSM-GPRS_CHANNELS_SWITCHED-00414-ai-sw
19-86 68P02901W56-T
Jan 2010
Throughput statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to throughput statistics
Figure 19-74 through Figure 19-80 show throughput statistics diagrams.
AIR_DL_TBF_FAILURES
Figure 19-74 and Figure 19-75 illustrate ladder diagrams for AIR_DL_TBF_FAILURES
termination and data transfer DDTR mode establishment respectively.
Figure 19-74 AIR_DL_TBF_FAILURES termination
68P02901W56-T 19-87
Jan 2010
Introduction to throughput statistics Chapter 19: Ladder diagrams
Figure 19-75 AIR_DL_TBF_FAILURES data transfer DDTR mode establishment
19-88 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Introduction to throughput statistics
AIR_UL_TBF_FAILURES
Figure 19-76 and Figure 19-77 illustrate ladder diagrams for AIR_UL_TBF_FAILURES
establishment/termination and data transfer respectively.
Figure 19-76 AIR_UL_TBF_FAILURE establishment and termination
68P02901W56-T 19-89
Jan 2010
Figure 19-77 AIR_UL_TBF_FAILURE data transfer
DL_PDTCH_SEIZURE
Figure 19-78 illustrates the ladder diagram for DL_PDTCH_SEIZURE.
19-90 68P02901W56-T
Jan 2010
Figure 19-78 DL_PDTCH_SEIZURE
UL_PDTCH_SEIZURE
Figure 19-79 and Figure 19-80 illustrate ladder diagrams for UL_PDTCH_SEIZURE one-phase
and two-phase access respectively.
68P02901W56-T 19-91
Jan 2010
Figure 19-79 UL_PDTCH_SEIZURE one-phase access
19-92 68P02901W56-T
Jan 2010
Figure 19-80 UL_PDTCH_SEIZURE two-phase access
68P02901W56-T 19-93
Jan 2010
19-94 68P02901W56-T
Jan 2010
Chapter
20
Impacts on statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The collection, interpretation, and accuracy of GSM statistics may be affected by some factors,
for example, new software and hardware features. Although not all the factors are directly
related to statistics, they all have a definite impact on them. The factors described here are
listed below. Also provided is a list of frequently asked questions with answers.
• Extended GSM (EGSM) on page 20-2.
• Approximate equality on page 20-6.
• Phantom RACHs on page 20-7.
• Frequently Asked Questions (FAQs) on page 20-10.
68P02901W56-T 20-1
Jan 2010
Extended GSM (EGSM) Chapter 20: Impacts on statistics
Extended GSM (EGSM)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Overview of EGSM
EGSM900 (Extended GSM) provides the BSS with a further range of frequencies for MS and
BSS transmit. EGSM MSs can use the extended frequency band as well as the primary band,
while non-EGSM MSs cannot use the extended frequency band. A GSM900 cell can contain both
GSM900 and EGSM900 carrier hardware.
Requirements
Although EGSM provides additional frequencies for use, several functions must remain in the
original GSM900 band. Functions that must be performed in the GSM900 band are:
• BCCH carrier frequency.
• SDCCH configuration.
• TCH allocation for immediate assignment.
Channel allocation
Channel allocation for an EGSM MS proceeds in a way such that the search is between
extended then primary band frequencies, starting from best to worst interference bands until
a channel is found.
Forced handovers
To avoid blocking of non-EGSM MSs, an extended band MS using a primary resource can be
forced to handover to an idle extended band resource with an interference band residing above
or meeting a specified threshold.
The database parameter egsm_handover_threshold indicates the range of interference bands

allowed for handing over an extended MS using a primary resource that is required by a
non-EGSM MS. Allowed interference bands are those above or meeting a specified threshold,
which are considered quality resources. The operator also has the option to disallow forced
handovers by disabling the egsm_handover_threshold flag.
Factors impacting statistics
Factors that contribute to the impacting of statistic values are:

• The relative number of primary and extended band resources at a cell compared to the
number of EGSM and non-EGSM capable MSs trying to access the cell.
• The egsm_handover_threshold flag value.
20-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Factors impacting statistics
The following examples illustrate the impact of the EGSM feature on statistics:
Example 1: MS access to a traffic channel
The following conditions must apply:

• EGSM MSs have used up the primary resources in the cell.
• Non-EGSM MSs are attempting to access the cell.
• The egsm_handover_threshold flag either does not allow or limits handovers from
primary resources to extended resources.
It is more difficult for non-EGSM MSs to access a TCH since EGSM MSs are occupying the
primary resources.
The statistics impacted are shown in Table 20-1.

Table 20-1 MS access to a traffic channel
Statistic Value
MA_CMD_TO_MS_BLKD is higher
MA_COMPLETE_TO_MSC is lower
BUSY_TCH MAX/mean value is lower
TOTAL_CALLS is lower
TCH_CONGESTION is lower (See note)
TCH_USAGE is lower
TCH_DELAY is higher
NOTE
TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not
just the primary band TCHs, even though congestion exists for the primary MSs in
this example.
68P02901W56-T 20-3
Jan 2010
Factors impacting statistics Chapter 20: Impacts on statistics
Example 2: Impact due to increased handovers

• The egsm_handover_flag encourages the handovers of EGSM MSs.
• Many EGSM MSs occupy primary resources.
• Non-EGSM MSs attempt to access the cell.
More intra-cell handovers are attempted to move the EGSM MSs off primary resources to
open up primary resources for non-EGSM MSs.
The statistics impacted are shown in Table 20-2.

Table 20-2 Impact due to increased handovers
Statistic Value
INTRA_CELL_HO is higher
INTRA_CELL_HO_REQ is higher
INTRA_CELL_HO_LOSTMS is higher
INTRA_CELL_HO_ATMPT is higher
INTRA_CELL_HO_FAIL is higher
MA_CMD_TO_MS is higher
MA_FAIL_TO_MS is higher
BAD_HO_REFNUM_MS is higher
CLR_REQ_TO_MSC is higher
ALLOC_SDCCH_FAIL is higher
20-4 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Factors impacting statistics
Example 3: Impact due to congestion

• A network has mostly non-EGSM MSs accessing the system. Although extended resources
are available, they are used infrequently.
• Primary resources are used up by non-EGSM MSs.
The cell experiences congestion when other non-EGSM MSs try to access the cell, despite the
fact that not all the resources have been allocated.
The statistics impacted are shown Table 20-3.

Table 20-3 Impact due to congestion
Statistic Value
MA_CMD_TO_MS_BLKD is higher
MA_COMPLETE_TO_MSC is lower
BUSY_TCH MAX/mean value is lower
TOTAL_CALLS is lower
TCH_CONGESTION is lower (See note)
TCH_USAGE is lower
TCH_DELAY is higher
NOTE
TCH_CONGESTION is lower because it is pegged when all TCHs are busy, not
just the primary band TCHs, even though congestion exists for the primary MSs in
this example.
68P02901W56-T 20-5
Jan 2010
Approximate equality Chapter 20: Impacts on statistics
Approximate equality
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Approximate equality
Statistics are kept by processes at the BTS and BSC. When comparing statistics, minor
discrepancies between different statistics may occur because when the statistic interval expires,
a procedure may be in progress and not all statistics related to that procedure have been
pegged. These statistics are pegged in the following interval upon completion of the procedure.
Example
Figure 20-1 is an example of approximate equality.
Figure 20-1 Approximate equality procedure
Although the procedure TCH assignment was successful, the statistics file for the 9:00 to
9:30 interval shows the statistic MA_REQ_FROM_MSC incremented with no corresponding
MA_CMD_TO_MS and TOTAL_CALLS values. Also, the 9:30 to 10:00 interval shows the
statistics MA_CMD_TO_MS, TOTAL_CALLS, and MA_COMPLETE_TO_MSC incremented
with no corresponding MA_REQ_FROM_MSC value.
20-6 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Phantom RACHs
Phantom RACHs
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description of Phantom RACHs
Phantom RACHs occur primarily as the result of sporadic noise and interference. Channel
requests from distant MSs can be affected by such noise when MS power output is low. If an
MS output is high, any transmitted signals can cause interference to other co-channel and
adjacent channel cells. It is unlikely in a Motorola implementation that cells using similar
frequencies are finely synchronized. This could happen by chance as each BTS does not have
frame synchronization. It is possible though for partial synchronization to occur and contribute
to the phantom RACH problem.
Diagram of Phantom RACHs procedure
Figure 20-2 provides a graphic illustration of phantom RACHs.
Figure 20-2 Phantom RACHs illustration
CHANNEL CODER RSS LAYER 1 RSS ABIS CALL PROCESSING

CHANNEL REQUEST
(unrecognized message OK_ACC_PROC_SUC_RACH
counter)
ACCESS_PER_RACH
(1 + unrecognized message
counter)
CHANNEL REQUEST
CHANNEL REQUEST
ALLOC_SDCCH
(CHAN_REQ_MS_FAIL)
ti-GSM-PhantomRACHs-00437-ai-sw
68P02901W56-T 20-7
Jan 2010
Process of Phantom RACHs occurrences Chapter 20: Impacts on statistics
Process of Phantom RACHs occurrences
The following process describes the chain of events that take place when a phantom RACH
occurs:
Procedure 20-1 Phantom RACHs occurrences
1 The channel coder decodes the message on the Random Access Channel
from the radio. If the channel coder cannot decode the message because a
field is unrecognizable, the channel coder pegs an internal counter for the
unrecognized message.
If the channel coder decodes the message, the channel coder forwards the
channel request to RSS Layer 1 and included in the message is the peg
count of unrecognized messages.
2 RSS layer 1 pegs the OK_ACC_PROC_SUC_RACH statistic once for the
channel request and pegs the ACCESS_PER_RACH statistic once for the
channel request plus the peg count sent by the Channel Coder. RSS layer 1
does no filtering of the RACH
3 RSS Abis receives the channel request and verifies the one-byte message
from the MS. It verifies that the three most significant bits represent a valid
establishment cause (see GSM4.08, 3.11.0, section 9.1.8 for the valid causes
for Phase 1). If the three bits are verified, the RSS Abis sends a channel
request to Call Processing.
NOTE
The other five bits of the eight-bit message are non formatted
five-bit field, which cannot be verified.
4 Call Processing does no filtering of the channel request, it attempts to
allocate an SDCCH and pegs the ALLOC_SDCCH statistic. If the MS does
not respond to the Immediate Assignment, that is, no MS ever existed for
the RACH or the MS is far away, or turned off, the CHAN_REQ_MS_FAIL
statistic is pegged.
There are three levels of filtering the RACH:
• At the Channel Coder.
• At RSS Abis.
• After attempt to allocate resource (due to guard timers expiring).
20-8 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Raw statistics affected
Raw statistics affected
The following statistics may be affected by phantom RACHs:

• ACCESS_PER_RACH.
• ACCESS_PER_AGCH.
• ALLOC_SDCCH.
• ALLOC_SDCCH_FAIL.
• OK_ACC_PROC_SUC_RACH.
• CHAN_REQ_MS_BLK.
• CHAN_REQ_MS_FAIL.
• SDCCH_CONGESTION.
• BUSY_SDCCH.
• BER (SDCCH affected but not TCH).
ACCESS_PER_RACH is pegged for each phantom RACH. The remainder of the above statistics
are affected depending on whether the apparent channel request from the MS is known to Call
Processing (Layer 3). RSS (Layer 2) filters out RACHs that are invalid. Specifically, Channel
Request messages received through the RACH that have invalid (reserved) values in the
establishment cause field (reference GSM 04.08) are filtered by the RSS. Therefore, a lot of
phantom RACHs never make it up to the Call Processing processes because of the gating
(filtering) function performed by the RSS.
68P02901W56-T 20-9
Jan 2010
Frequently Asked Questions (FAQs) Chapter 20: Impacts on statistics
Frequently Asked Questions (FAQs)

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Assignment failure
Q: What happens after an ASSIGNMENT FAILURE from the MS?
A: If an Assignment Failure is received from the MS during call set-up, the Assignment Failure is
forwarded to the MSC and the MSC (at its discretion) clears the call. If the Assignment Failure
is received during a BSS-controlled intra-cell handover, the call reverts back to the old channel.
Q: After an ASSIGNMENT FAILURE from the MS is the call lost or does the system send another
ASSIGNMENT COMMAND?
A: As explained earlier, during call set up the MSC decides whether to clear the call. Whether
the Assignment Command is retried is up to the MSC. If the Assignment Failure is received
during intra-cell handover, the call reverts back to the old channel and could send another
Assignment Command to the MS if the BSS chooses to do another intra-cell handover.
Counters and SDCCH reconfiguration
Q: Whether the following counters work correctly after an SDCCH reconfiguration? That is
when a TCH is used as an SDCCH:
• ALLOC_SDCCH.
• ALLOC_SDCCH_FAIL.
• BUSY_SDCCH.
• BUSY_TCH.
• RF_LOSSES_SD.
• RF_LOSSES_TCH.
• SDCCH_CONGESTION.
• TCH_CONGESTION.
• TCH_USAGE.
A: For example, SDCCH congestion timer gets started when there are no free SDCCHs available
at the cell. If a TCH gets reconfigured to eight SDCCHs, the congestion timer stops because the
cell is no longer congested as far as SDCCHs are concerned. The statistics reflect the current
status of the system. The reconfiguration issue should not affect the accuracy of the statistics.
20-10 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application Dynamic SDCCH configuration
Dynamic SDCCH configuration
Q: If configuration of SDCCHs, for example, can occur manually or more importantly occur
dynamically during a busy period, would the previous peg information for that half hour period
be lost, and would this affect key statistic results?
A: No, CHAN_REQ_MS_FAIL (the statistic which is pegged per channel) is not deleted when
the channel is configured or reconfigured. The process pegging creates the statistic for all
possible SDs. This statistic is never deleted, so that the statistic for each half hour shows the
amount of pegs for the channel for the entire half hour.
Established call loss
Q: Is failed handover and RF_LOSSES_TCH the only possible reason for losing an established
call?
A: A call could also be lost because of other procedure failures, like ciphering and Mode Modify.
Location update reject
Q: Why is there no value for LOCATION UPDATE REJECT?
A: The BSS should not have to peg Location Update Rejects. Location Update Rejects is a DTAP
procedure and the MSC should track Location Update Rejects.
Phantom RACHs
Q: How can it be determined how many phantom RACHs have been assigned to an SDCCH?
A: CHAN_REQ_MS_FAIL pegs due to timeout, if the MS is out of range or switched off. After
the SDCCH is allocated, an attempt is made to communicate with the MS, and it does not
respond (because it never existed to begin with).
Q: Does updated BTS hardware affect Phantom RACHs?
A: ACCESS_PER_RACH counts reduce considerably between BTS5s and BTS4Ds (3000 > 300),
which have full diversity.
Q: What happens after an SDCCH has been seized by a phantom RACH? Whether
CLR_REQ_TO_MSC, CHAN_REQ_MS_FAIL and RF_LOSSES_SD be pegged?
A: Only CHAN_REQ_MS_FAIL is pegged. CLR_REQ_TO_MSC and RF_LOSSES_SD is not

pegged for phantom RACHs.
68P02901W56-T 20-11
Jan 2010
Phantom RACHs Chapter 20: Impacts on statistics
20-12 68P02901W56-T
Jan 2010
Chapter
21
Statistics history
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistics can be added, modified, replaced, or removed as developing software release are
introduced. The tables in History of raw statistics on page 21-2 show a history of statistic
development for raw statistics. The aim is to help maintenance personnel track how statistics of
interest have evolved or are evolving between software releases.
68P02901W56-T 21-1
Jan 2010
History of raw statistics Chapter 21: Statistics history
History of raw statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 21-1 shows the history of raw statistics from release 1650 to the present.
Table 21-1 History of raw statistics
Release Statistic name Associated feature Action

1650 NO_PDTCH_AVAIL_TIME 3725 - Multi-Carrier GPRS Added
1650 NO_PDTCH_AVAIL 3725 - Multi-Carrier GPRS Added
1650 GBL_FLUSH_REQS 3750 - GPRS Stats Removed
1650 CELL_FLUSH_REQS 3750 - GPRS Stats Added
1650 UL_PDTCH_SEIZURE 3750 - GPRS Stats Added
1650 DL_PDTCH_SEIZURE 3750 - GPRS Stats Added
1650 CHANNEL_REQS_SUCCESS 3750 - GPRS Stats Added
1650 AVAILABLE_PDTCH 3750 - GPRS Stats Added
1650 AVAILABLE_TCH 3750 - GPRS Stats Modified
1650 UL_BUSY_PDTC 3750 - GPRS Stats Added
1650 DL_BUSY_PDTCH 3750 - GPRS Stats Added
1650 TOTAL_AIR_UL_AVAILABLE_BW 3750 - GPRS Stats Removed
1650 TOTAL_AIR_DL_AVAILABLE_BW 3750 - GPRS Stats Removed
1650 UL_PDTCH_CONGESTION 3750 - GPRS Stats Added
1650 DL_PDTCH_CONGESTION 3750 - GPRS Stats Added
1650 UL_PDTCH_Q_LENGTH 3750 - GPRS Stats Added
1650 DL_PDTCH_Q_LENGTH 3750 - GPRS Stats Added
1650 CODING_SCHEME_CHANGE 3750 - GPRS Stats Added
1650 GPRS_ACCESS_PER_PCH 3750 - GPRS Stats Removed
1650 ACCESS_PER_PCH 3750 - GPRS Stats Modified
1650 PAGING_REQUESTS 3750 - GPRS Stats Added
1650 PCH_Q_PAGE_DISCARD 3750 - GPRS Stats Modified
1650 PCH_AGCH_Q_LENGTH 3750 - GPRS Stats Modified
1650 GPRS_PCH_AGCH_Q_LENGTH 3750 - GPRS Stats Added
1650 IMM_ASSGN_CAUSE 3750 - GPRS Stats Added
1650 IDLE_PDTCH_INTF_BAND0 3750 - GPRS Stats Added
Continued
21-2 68P02901W56-T
Jan 2010
Maintenance information: GSM Statistics Application History of raw statistics
Table 21-1 History of raw statistics (Continued)

1650 AIR_DL_DATA_BLKS 3750 - GPRS Stats Modified
1650 AIR_UL_DATA_BLKS 3750 - GPRS Stats Modified
1650 CALL_SP_VERS_REQUEST_ 3938 - Call Downgrade on Added
MONITOR CIC Capability Mismatch
1650 GPRS_CELL_RESELECT_ATMPT 3969/4050 - Network Added
Controlled Cell
Reselection
1650 GPRS_CELL_RESELECT_FAIL 3969/4050 - Network Added
Controlled Cell
Reselection
1650 UL_PDTCH_CONGESTION 3969/4050 - Network Modified
Controlled Cell
Reselection
1650 DL_PDTCH_CONGESTION 3969/4050 - Network Modified
Controlled Cell
Reselection
1650 GPRS_MS_NEIGHBOR_STRONG 3969/4050 - Network Added
Controlled Cell
Reselection
1650 LMTL Traffic Stats 3974 - Location Services Added
1650 LOCATION_SERVICES 3974 - Location Services Added
1650 CHAN_REQ_CAUSE_ATMPT 3974 - Location Services Modified
1650 OK_ACC_PROC 3974 - Location Services Modified
1650 MT_LCS_ON_SDCCH 3974 - Location Services Added
1650 UL_CHAN_ASGN_DURATION 4253 - GPRS Interleaving Removed
TBFs
1650 DL_CHAN_ASGN_DURATION 4253 - GPRS Interleaving Removed
TBFs
1650 AIR_DL_CONTROL_BLKS 4253 - GPRS Interleaving Added
TBFs
1650 AIR_UL_CONTROL_BLKS 4253 - GPRS Interleaving Added
TBFs
1650 PRP_LOAD 4253 - GPRS Interleaving Added
TBFs
1650 ALLOC_TCH_CARR PR 150281 Added
1650 ALLOC_SDCCH_CARR PR 150281 Added
1650 ROC PR 154956 Added
1650 U_BER PR 154956 Added
1650 CLR_CMD_FROM_MSC PR 150371 Added
Continued
68P02901W56-T 21-3
Jan 2010

1650 CLR_REQ_TO_MSC PR 150280 Modified
1650 LAP-D_CONGESTION PR 154656 Added
1650 ALLOC_TCH_INNER_ZONE PR 170229 Added
1650 ALLOC_TCH_FAIL_INNER_ZONE PR 170229 Added
1650 TCH_Q_REMOVED_INNER_ZONE PR 170229 Added
1700 CHANNEL_REQS_REC 3723 - PBCCH/PCCCH Modified
1700 CHANNEL_REQS_SUCCESS 3723 - PBCCH/PCCCH Modified
1700 AVAILABLE_PDTCH 3723 - PBCCH/PCCCH Modified
1700 ACCESS_PER_PPCH 3723 - PBCCH/PCCCH Added
1700 PPCH_Q_PAGE_DISCARD 3723 - PBCCH/PCCCH Added
1700 GPRS_PPCH_PAGCH_Q_LENGTH 3723 - PBCCH/PCCCH Added
1700 GPRS_DL_ASGN_PCCCH 3723 - PBCCH/PCCCH Added
1700 G_RACH_UNSVCD_BTS 4441 - Enhanced Added
Scheduling
1700 CH_REQ_UNSVCD_PCU 4441 - Enhanced Added
Scheduling
1700 GPRS_PRR_BLK_USG 4441 - Enhanced Added
Scheduling
1700 GPRS_RACH_ARRIVAL 4441 - Enhanced Added
Scheduling
1700 AIR_DL_TBF_FAILURES 4445 - GPRS Performance Added
Enhancements Under
Load
1700 AIR_UL_TBF_FAILURES 4445 - GPRS Performance Added
Enhancements Under
Load
1700 CONG_REL_DL_SCTS 4445 - GPRS Performance Added
Enhancements Under
Load
1700 GBL_PAGING_REQS 4040 Modified
1700 PRP_LOAD 4040 Modified
AMR 1700 MA_REQ_FROM_MSC 4322 - AMR Modified
AMR 1700 HO_REQ_FROM_MSC 4322 - AMR Added
AMR 1700 EFR_REQ_FROM_MSC 4322 - AMR Removed
AMR 1700 MA_COMPLETE_TO_MSC 4322 - AMR Modified
AMR 1700 HO_REQ_ACK_TO_MSC 4322 - AMR Added
AMR 1700 HO_REQ_MSC_OK 4322 - AMR Removed
Continued
21-4 68P02901W56-T
Jan 2010

AMR 1700 FER_NON_AMR 4322 - AMR Added
AMR 1700 FER 4322 - AMR Removed
AMR 1700 FER_AMR_FR 4322 - AMR Added
AMR 1700 FER_AMR_HR 4322 - AMR Added
AMR 1700 INTRA_CELL_HO_ATMPT 4322 - AMR Removed
AMR 1700 INTRA_CELL_HO_ATMPT_FR_FR 4322 - AMR Added
AMR 1700 INTRA_CELL_HO_ATMPT_HR_HR 4322 - AMR Added
AMR 1700 INTRA_CELL_HO_ATMPT_HR_FR 4322 - AMR Added
AMR 1700 INTRA_CELL_HO_ATMPT_FR_HR 4322 - AMR Added
AMR 1700 TCH_CONGESTION_HR_AMR 4322 - AMR Added
AMR 1700 TCH_CONG_INNER_ZONE_HR_AMR 4322 - AMR Added
AMR 1700 BUSY_TCH_HR_AMR 4322 - AMR Added
AMR 1700 AVAILABLE_TCH_HR_AMR 4322 - AMR Added
AMR 1700 RF_LOSSES_TCH_HR_AMR 4322 - AMR Added
AMR 1700 ALLOC_TCH_HR_AMR 4322 - AMR Added
AMR 1700 ALLOC_TCH_FAIL_HR_AMR 4322 - AMR Added
AMR 1700 CALL_SP_VERS_REQUEST_ 4322 - AMR Modified
MONITOR
AMR 1700 BUSY_TCH 4322 - AMR Modified
AMR 1700 BUSY_TCH_CARR 4322 - AMR Modified
AMR 1700 TCH_CONGESTION 4322 - AMR Modified
AMR 1700 TCH_CONGESTION_HR_AMR 4322 - AMR Modified
AMR 1700 RF_LOSSES_TCH 4322 - AMR Modified
AMR 1700 ALLOC_TCH 4322 - AMR Modified
AMR 1700 ALLOC_TCH_FAIL 4322 - AMR Modified
AMR 1700 ALLOC_TCH_HR_AMR 4322 - AMR Modified
AMR 1700 ALLOC_TCH_FAIL_HR_AMR 4322 - AMR Modified
AMR 1700 AMR_FR_UL_CODEC_MODE_USAGE 4322 - AMR Added
AMR 1700 AMR_FR_DL_CODEC_MODE_USAGE 4322 - AMR Added
AMR 1700 AMR_HR_UL_CODEC_MODE_USAGE 4322 - AMR Added
AMR 1700 AMR_HR_DL_CODEC_MODE_USAGE 4322 - AMR Added
AMR 1700 AMR_FR_UL_ADAPTATION 4322 - AMR Added
AMR 1700 AMR_FR_DL_ADAPTATION 4322 - AMR Added
AMR 1700 AMR_HR_UL_ADAPTATION 4322 - AMR Added
Continued
68P02901W56-T 21-5
Jan 2010

AMR 1700 AMR_HR_DL_ADAPTATION 4322 - AMR Added
AMR 1700 AMR_INCREASE_THRESH_ADJUST 4322 - AMR Added
AMR 1700 AMR_DECREASE_THRESH_ADJUST 4322 - AMR Added
AMR 1700 ATER_CHANNEL_STATUS 4084 - AMR Added
AMR 1700 ATER_EMERG_PREEMPT_STATUS 4084 - AMR Added
AMR 1700 FER SR 1100790 Re-added
1740 AIR_DL_DATA_BLKS 23658 - EGPRS Removed
1740 AIR_UL_DATA_BLKS 23658 - EGPRS Removed
1740 MS_CLASS_1_10_REQ 23658 - EGPRS Removed
1740 CHANNEL_REQS_REC 23658 - EGPRS Modified
1740 CHANNEL_REQS_SUCCESS 23658 - EGPRS Modified
1740 IMM_ASSGN_CAUSE 23658 - EGPRS Modified
1740 CODING_SCHEME_CHANGE 23658 - EGPRS Modified
1740 AVAILABLE_PDTCH 23658 - EGPRS Renamed
1740 GPRS_AVAILABLE_PDTCH. 23658 - EGPRS Added
1740 EGPRS_AVAILABLE_PDTCH 23658 - EGPRS Added
1740 EGPRS_64K_CHANNELS_SWITCHED23658 - EGPRS Added
1740 EGPRS_64K_NOT_AVAIL 23658 - EGPRS Added
1740 EGPRS_DL_ASGN_PCCCH 23658 - EGPRS Added
1740 DL_RADIO_BLKS_1_TS 23658 - EGPRS Added
1740 DL_TBF_TIME_1_TS 23658 - EGPRS Added
1740 UL_RADIO_BLKS_GMSK_1_TS 23658 - EGPRS Added
1740 UL_RADIO_BLKS_GMSK_2_TS 23658 - EGPRS Added
1740 UL_TBF_TIME_GMSK_1_TS 23658 - EGPRS Added
1740 UL_TBF_TIME_GMSK_2_TS 23658 - EGPRS Added
1740 UL_RADIO_BLKS_8PSK_1_TS 23658 - EGPRS Added
Continued
21-6 68P02901W56-T
Jan 2010

1740 UL_RADIO_BLKS_8PSK_2_TS 23658 - EGPRS Added
1740 UL_TBF_TIME_8PSK_1_TS 23658 - EGPRS Added
1740 UL_TBF_TIME_8PSK_2_TS 23658 - EGPRS Added
1740 DL_RLC_ACK_NEW_BLKS 23658 - EGPRS Added
1740 DL_RLC_UNACK_NEW_BLKS 23658 - EGPRS Added
1740 DL_RLC_RETX_BLKS 23658 - EGPRS Added
1740 DL_RLC_STALLED_BLKS 23658 - EGPRS Added
1740 DL_RLC_NACK_BLKS 23658 - EGPRS Added
1740 DL_RLC_DDTR_BLKS 23658 - EGPRS Added
1740 UL_RLC_ACK_NEW_BLKS 23658 - EGPRS Added
1740 UL_RLC_UNACK_NEW_BLKS 23658 - EGPRS Added
1740 UL_RLC_RETX_BLKS 23658 - EGPRS Added
1740 SDCCH_HO SR 259561 Added
1740 SMS_INIT_ON_SDCCH_HO_ SR 259561 Added
1760 MA_REQ_FROM_MSC 22064 - GSM_HR Modified
1760 MA_COMPLETE_TO_MSC 22064 - GSM_HR Modified
1760 HO_REQ_FROM_MSC 22064 - GSM_HR Modified
1760 HO_REQ_ACK_TO_MSC 22064 - GSM_HR Modified
1760 FER_GSM_HR 22064 - GSM_HR Added
1760 FER_NON_AMR 22064 - GSM_HR Removed
1760 FER_GSM_FR_EFR 22064 - GSM_HR Added
1760 TCH_CONGESTION 22064 - GSM_HR Modified
1760 TCH_CONGESTION_HR_AMR 22064 - GSM_HR Removed
1760 TCH_CONGESTION_HR 22064 - GSM_HR Added
1760 TCH_CONG_INNER_ZONE 22064 - GSM_HR Modified
1760 TCH_CONG_INNER_ZONE_HR_AMR 22064 - GSM_HR Removed
1760 TCH_CONG_INNER_ZONE_HR 22064 - GSM_HR Added
1760 BUSY_TCH 22064 - GSM_HR Modified
1760 BUSY_TCH_CARR 22064 - GSM_HR Modified
1760 BUSY_TCH_HR_AMR 22064 - GSM_HR Removed
1760 BUSY_TCH_HR 22064 - GSM_HR Added
1760 BUSY_TCH_CARR_HR_AMR 22064 - GSM_HR Removed
1760 BUSY_TCH_CARR_HR 22064 - GSM_HR Added
1760 AVAILABLE_TCH 22064 - GSM_HR Modified
Continued
68P02901W56-T 21-7
Jan 2010

1760 AVAILABLE_TCH_HR_AMR 22064 - GSM_HR Removed
1760 AVAILABLE_TCH_HR 22064 - GSM_HR Added
1760 RF_LOSSES_TCH 22064 - GSM_HR Modified
1760 RF_LOSSES_TCH_HR_AMR 22064 - GSM_HR Removed
1760 RF_LOSSES_TCH_HR 22064 - GSM_HR Added
1760 ALLOC_TCH 22064 - GSM_HR Modified
1760 ALLOC_TCH_FAIL 22064 - GSM_HR Modified
1760 ALLOC_TCH_HR_AMR 22064 - GSM_HR Removed
1760 ALLOC_TCH_HR 22064 - GSM_HR Added
1760 ALLOC_TCH_FAIL_HR_AMR 22064 - GSM_HR Removed
1760 ALLOC_TCH_FAIL_HR 22064 - GSM_HR Added
1760 CALL_SP_VERS_DOWNGRADE_ 22064 - GSM_HR Modified
MONITOR
1760 MA_REQ_SDCCH_PG_RSP PR 180867 Added
1760 DL_BUSY_PDTCH PR 183169 Modified
1760 UL_BUSY_PDTCH PR 183169 Modified
1800 GPRS_CONGESTION 22577 - GPRS Statistics Added
1800 TBF_SESSIONS 22577 - GPRS Statistics Added
1800 DL_BLER_CS1 22577 - GPRS Statistics Added
1800 UL_BLER_CS1 22577 - GPRS Statistics Added
1800 DL_BLER_MCS1 22577 - GPRS Statistics Added
Continued
21-8 68P02901W56-T
Jan 2010

1800 UL_BLER_MCS1 22577 - GPRS Statistics Added
1800 PDU_DISCARD_FR 22577 - GPRS Statistics Added
1800 PDU_DISCARD_LLC 22577 - GPRS Statistics Added
1800 DL_LLC_FRAMES_GB 22577 - GPRS Statistics Added
1800 DL_LLC_FRAMES_PCU 22577 - GPRS Statistics Added
1800 UL_LLC_FRAMES 22577 - GPRS Statistics Added
1800 PS_PAGE_REQS 22577 - GPRS Statistics Added
1800 CS_PAGE_REQS 22577 - GPRS Statistics Added
1800 PACCH_PAGE_REQS 22577 - GPRS Statistics Added
1800 TBF_DL_ASGN_PACCH 22577 - GPRS Statistics Added
1800 TBF_REL_PACCH_LOST 22577 - GPRS Statistics Added
1800 CS1234_ON_64K_CHAN 22577 - GPRS Statistics Added
1800 DL_PDTCH_CONGESTION 22577 - GPRS Statistics Removed
1800 UL_PDTCH_CONGESTION 22577 - GPRS Statistics Removed
1800 GBL_LINK_INS 22577 - GPRS Statistics Removed
1800 RBER 22577 - GPRS Statistics Modified
1800 NUM_CELL_RESEL_NEI 22708/23706 - Network Added
Assisted Cell Change
1800 NUM_CELL_RESEL_CELL 22708/23706 - Network Added
1800 NUM_CELL_RESEL_CELL_PCCN 22708/23706 - Network Added
1800 NUM_CELL_RESEL_CELL_SUCC 22708/23706 - Network Added
1800 NUM_CELL_RESEL_NEI_SUCC 22708/23706 - Network Added
Continued
68P02901W56-T 21-9
Jan 2010

1800 NUM_CELL_RESEL_NEI_PCCN 22708/23706 - Network Added
1800 GPRS_CELL_RESELECT_ATMPT 22708/23706 - Network Removed
1800 GPRS_MS_NEIGHBOR_STRONG 22708/23706 - Network Removed
1800 PFC_ADMISSION_SUCCESS 23956 - BSS Quality of Added
Service
1800 PFC_ADMISSION_SUCCESS_OTHER 23956 - BSS Quality of Added
Service
1800 PFC_ADMISSION_REJECTION 23956 - BSS Quality of Added
Service
1800 PFC_ADMISSION_REJECTION_ 23956 - BSS Quality of Added
OTHER Service
1800 PFC_DOWNGRADE_SUCCESS 23956 - BSS Quality of Added
Service
1800 PFC_DOWNGRADE_FAILURE is 23956 - BSS Quality of Added
added Service
1800 PFC_PREEMPTIONS 23956 - BSS Quality of Added
Service
1800 PFC_REJ_DGRD_PRMPT_PRP 23956 - BSS Quality of Added
Service
1800 PFC_REJ_DGRD_PRMPT_CELL 23956 - BSS Quality of Added
Service
1800 PFC_REJECT_CAUSES 23956 - BSS Quality of Added
Service
1800 DL_LLC_DATA_VOLUME 23956 - BSS Quality of Added
Service
1800 UL_LLC_DATA_VOLUME 23956 - BSS Quality of Added
Service
1800 PFC_UPGRADE is added 23956 - BSS Quality of Added
Service
1800 TIMER_EXP_PAP_CONV 23956 - BSS Quality of Added
Service
1800 PRP_PD_DEMAND 22100 - PDTCH Added
Configured
1800 GCI_FOR_64KPD_DEMAND 22100 - PDTCH Added
Configured
Configured
Continued
21-10 68P02901W56-T
Jan 2010

Configured
1800 TOTAL_GCI_FOR_PD_DEMAND 22100 - PDTCH Added
Configured
1800 OUT_INTER_BSS_HO_EQUIP_FAIL 22103 - Changes to Modified
OUT_INTER_BSS_HO
1800 OUT_INTER_BSS_HO_CLEARED 22103 - Changes to Modified
OUT_INTER_BSS_HO
1800 OUT_INTER_BSS_HO_FAIL 22103 - Changes to Added
OUT_INTER_BSS_HO
1800 BSS_OVLD_MSGS_TX 24660 - RSL Congestion Added
Control
1800 RSL_LCF_CONGESTION 24660 - RSL Congestion Added
Control
1800 MSGS_DISCARD_ON_GPROC 24660 - RSL Congestion Added
Control
1800 MSGS_DISCARD_ON_RSL 24660 - RSL Congestion Added
Control
1800 PACKET_SYSINFO_RESP 24303 - Release 4 Added
Compliance (Phase 1)
1800 PACKET_SYSINFO_REQ_ 24303 - Release 4 Added
Compliance (Phase 1)
1800 TCH_PREEMPT_RQD 24347 - Enhanced Added

Multi-level Precedence
and Preemption service
1800 TCH_PREEMPT_ATMPT 24347 - Enhanced Added
1800 TCH_PREEMPT_CAP 24347 - Enhanced Added
1800 TCH_PREEMPT_FAIL_NO_CAND 24347 - Enhanced Added
1800 TCH_PREEMPT_FAIL_TIMEOUT 24347 - Enhanced Added
1800 TCH_Q_REMOVED 24347 - Enhanced Modified
Continued
68P02901W56-T 21-11
Jan 2010

1800 ATER_EMERG_PREEMPT_STATUS 24347 - Enhanced Removed
1800 ATER_PREEMPT_RQD 24347 - Enhanced Added
1800 ATER_PREEMPT_ATMPT 24347 - Enhanced Added
1800 QUEUE_PREEMPT_ATMPT 24347 - Enhanced Added
1800 CALLS_QUEUED 24347 - Enhanced Modified
1800 ATER_PREEMPT_ATMPT_SWOVER 24347 - Enhanced Added
1800 ATER_PREEMPT_FAIL 24347 - Enhanced Added
1800 ATER_PREEMPT_FAIL_SWOVER 24347 - Enhanced Added
1800 NUM_HO_3G_ATTEMPTS 22879 - Enhanced 2G-3G Added
CS Handover
1800 NUM_HO_TO_3G_RES_ALLOC_ 22879 - Enhanced 2G-3G Added
SUCC CS Handover
1800 NUM_HO_TO_3G_SUCCESS 22879 - Enhanced 2G-3G Added
CS Handover
1800 NUM_T3121_EXPIRY 22879 - Enhanced 2G-3G Added
CS Handover
1800 NUM_HO_FROM_3G_ATTEMPTS 22879 - Enhanced 2G-3G Added
CS Handover
1800 NUM_HO_FROM_3G_SUCCESS 22879 - Enhanced 2G-3G Added
CS Handover
1800 NUM_MULTIRAT_MS_ORIG_CALL 22879 - Enhanced 2G-3G Added
CS Handover
1800 OUT_HO_NC_SUC 22879 - Enhanced 2G-3G Modified
CS Handover
1800 OUT_HO_NC_CAUSE_ATMPT 22879 - Enhanced 2G-3G Modified
CS Handover
1800 ALLOC_TCH 24620 - Fast Call Setup Modified
Continued
21-12 68P02901W56-T
Jan 2010

1800 ALLOC_TCH_FAIL 24620 - Fast Call Setup Modified
1800 ALLOC_TCH_CARR 24620 - Fast Call Setup Modified
1800 ALLOC_TCH_HR 24620 - Fast Call Setup Modified
1800 ALLOC_TCH_HR_FAIL 24620 - Fast Call Setup Modified
1800 ALLOC_TCH_SIG SR 2213866 Added
1800 CHAN_REQ_MS_FAIL 24620 - Fast Call Setup Modified
1800 CHAN_REQ_MS_BLK 24620 - Fast Call Setup Modified
1800 OK_ACC_PROC 24620 - Fast Call Setup Modified
1800 INV_EST_CAUSE_ON_RACH 24620 - Fast Call Setup Removed
1800 AVAILABLE_TCH_PGSM 22404 - Intelligent Added
Multi-Layer Resource
Management
1800 AVAILABLE_TCH_EGSM 22404 - Intelligent Added
Management
1800 AVAILABLE_TCH_DCS1800 22404 - Intelligent Added
Management
1800 BUSY_TCH_PGSM 22404 - Intelligent Added
Management
1800 BUSY_TCH_EGSM 22404 - Intelligent Added
Management
1800 BUSY_TCH_DCS1800 22404 - Intelligent Added
Management
1800 EGPRS_64k_CHANNEL_WIDTH 23769 - Versa Trau Added
1800 UL_EGPRS_BACKHAUL_DEMAND 23769 - Versa Trau Added
1800 DL_EGPRS_BACKHAUL_DEMAND 23769 - Versa Trau Added
1800 UL_EGPRS_BACKHAUL_USED 23769 - Versa Trau Added
1800 DL_EGPRS_BACKHAUL_USED 23769 - Versa Trau Added
1800 AVG_SIMUL_DL_TBFS 28486 - CMCC Statistics Added
Enhancements
1800 AVG_SIMUL_UL_TBFS 28486 - CMCC Statistics Added
Enhancements
1800 BLOCKED_DL_TBFS 28486 - CMCC Statistics Added
Enhancements
1800 CLR_REQ_CALL_SETUP SR 528457 Added
Continued
68P02901W56-T 21-13
Jan 2010

1800 RF_LOSSES_TCH_SIG SR 2213866 Added
1900 RSL_TX_OCTETS 22266 Added
1900 RSL_RX_OCTETS 22266 Added
1900 RSL_LINK_INS 22266 Added
1900 HO_BLKD_BSP_OVERLOAD 23306 Added
1900 MA_CMD_TO_MS_BLKD 23306 Modified
1900 PROCESSOR_CRITICAL_OVERLOAD 23306 Added
1900 PROCESSOR_SAFE_OVERLOAD 23306 Added
1900 RF_LOSSES_TCH 25867 Modified
1900 RF_LOSSES_TCH_HR 25867 Modified
1900 RF_LOSSES_SD 25867 Modified
1900 DL_LLC_DATA_VOLUME 27703A Modified
1900 PDU_DISCARD_LLC 27703A Modified
1900 PFC_ADMISSION 27703A Modified
1900 PFC_ADMISSION_TRAFFIC_CLASS 27703A Modified
1900 PFC_DOWNGRADE_FAILURE 27703A Modified
1900 PFC_DOWNGRADE_SUCCESS 27703A Modified
1900 PFC_GBR_DL 27703A Added
1900 PFC_GBR_UL 27703A Added
1900 PFC_PREEMPTIONS 27703A Modified
1900 PFC_PREEMPTIONS_TRAFFIC_ 27703A Added
CLASS
1900 PFC_REJECT_CAUSES 27703A Modified
1900 PFC_REJECTION 27703A Modified
1900 PFC_REJECTION_TRAFFIC_CLASS 27703A Modified
1900 PFC_TRANSFER_DELAY 27703A Added
1900 PFC_UPGRADE 27703A Modified
1900 UL_LLC_DATA_VOLUME 27703A Modified
1900 NUM_SUSP_RESU_RCVD 27717 Added
1900 MTP_SL_ERROR_RATE_HSP 28337 Added
1900 MTL_UTILISATION_RX 28337 Modified
1900 MTL_UTILISATION_TX 28337 Modified
1900 CPU_USAGE 28351 Modified
Continued
21-14 68P02901W56-T
Jan 2010

1900 ETH_RX_BYTE 28351 Added
1900 ETH_RX_ERROR 28351 Added
1900 ETH_RX_PKT 28351 Added
1900 ETH_TX_BYTE 28351 Added
1900 ETH_TX_ERROR 28351 Added
1900 ETH_TX_PKT 28351 Added
1900 GCI_FOR_16KPD_DEMAND 28351 Modified
1900 PFC_REJ_DGRD_PRMPT_PRP 28351 Modified
1900 PRP_PD_DEMAND 28351 Modified
1900 PSI_TRAU_FILL_FRAME_TX 28351 Added
1900 TBF_SESSIONS 28351 Modified
1900 TOTAL_GCI_FOR_PD_DEMAND 28351 Modified
1900 AVG_SIMUL_UL_TBFS 28486 - CMCC Statistics Modified
Enhancements
1900 BLOCKED_DL_TBFS 28486 - CMCC Statistics Modified
Enhancements
1900 BSS_AVAILABLITLY Modified
1900 RSS_ALLOC_RESERVE_BLOCK Added
1900 PFC_ADMISSION_OTHER 27703A Removed
1900 PFC_REJECTION_OTHER 27703A Removed
1900 UPLINK_PDTCH_BLOCKING_RATE Removed
1900 GPRS_DL_ACT_TS Removed
1900 GPRS_UL_ACT_TS Removed
1900 CELL_UPDATE Removed
1900 UL_TBF_SUCCESS_RATE_EGPRS Removed
1900 UL_TBF_SUCCESS_TO_SEIZURE_ Removed
RATE
1900 INTRA_CELL_HO_SUCCESS_RATE Modified
1900 UL_MEAN_TBF_DURATION Modified
1900 UL_TBF_FAILURE_RATE Modified
1900 LLC_BUFFER_OVERFLOW_RATE Modified
1900 INTERNAL_SUCCESS Modified
Continued
68P02901W56-T 21-15
Jan 2010

1900 INTERNAL_RECOVERED Modified
1900 INTERNAL_LOST Modified
1900 INTRA_CELL_HO_SUCCESS_RATE Modified
1900 INTRA_CELL_HO_FAIL_RECOVERED Modified
1900 INTRA_CELL_HO_FAIL_LOST_MS Modified
1900 HANDOVERS_PER_CALL Modified
1900 INTRA_BSS_HO_TO_ALL_HO (i) Modified
1900 TCH_Q_REMOVED 24347 - Enhanced Modified
1900 PAGE_REQ_FROM_MSC Modified
1900 BSS_AVAILABILITY SR 2213866 Modified
1900 RF_LOSSES_TCH SR 2213866 Modified
1900 TCH_CONGESTION_EN 35035 – TCH Congestion Added
Statistics Enhancement
1a00 GBL_RESOUR_DIST_IND 26638 – Gb over IP Added
1a00 GBL_DL_PKT_INV_NSVC 26638 – Gb over IP Added
1a00 GBL_DL_PKT_COUNT 26638 – Gb over IP Added
1a00 GBL_UL_PKT_COUNT 26638 – Gb over IP Added
1a00 CPU_USAGE 34371G – CTU4 Modified
1a00 DSP_USAGE 34371G – CTU4 Added
1a00 SMS_TO_CALL_RATIO Modified
1a00 LOCATION_UPDATES_TO_CALLS Modified
(I)
1a00 IMSI_DETACHES_TO_CALLS (Id) Modified
1a00 NUM_CELL_RESEL_CELL_PCCN Modified
1a00 HANDOVER_SUCCESS_RATE Modified
1a00 U_BER Modified
1a00 OUT_INTER_BSS_HO Modified
1a00 TBF_DROP_RATE_ON_PACCH_LOST Modified
21-16 68P02901W56-T
Jan 2010
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ACCESS_PER_AGCH . . . . . . . . . . . 4-12 AMR_FR_UL_CODEC_MODE_USAGE . . . 4-37

ACCESS_PER_PPCH . . . . . . . . . . . 4-19 AMR_HR_DL_ADAPTATION . . . . . . . . 4-38
ACCESS_PER_RACH . . . . . . . . . . . 4-21 AMR_HR_DL_CODEC_MODE_USAGE. . . 4-39
Accessibility statistics . . . . . . . . . . . 19-81 AMR_HR_UL_ADAPTATION . . . . . . . . 4-40
ADJ_CHAN_INTF . . . . . . . . . . . . . 4-200 AMR_HR_UL_CODEC_MODE_USAGE. . . 4-41
AIR_DL_CONTROL_BLKS . . . . . . . . . 13-9 AMR_INCREASE_THRESH_ADJUST . . . 4-42
AIR_DL_TBF_FAILURES. . . . . . . . . . 13-10 approximate equality . . . . . . . . . . . 20-6
AIR_INTERFACE_BW_CS1 . . . . . . . . 18-7 assignment to TCH
AIR_INTERFACE_BW_CS2 . . . . . . . . 18-8 assignment successful . . . . . . . . . 19-18
AIR_INTERFACE_BW_CS3 . . . . . . . . 18-9 fail recovered . . . . . . . . . . . . . . 19-22
AIR_INTERFACE_BW_CS4 . . . . . . . . 18-10 immediate assignment failure . . . . . . 19-20
AIR_INTERFACE_PAGING . . . . . . . . 18-11 TCH assignment blocked . . . . . . . . 19-21
AIR_UL_CONTROL_BLKS . . . . . . . . . 13-11 ASSIGNMENT_REDIRECTION . . . . . . 4-43
AIR_UL_TBF_FAILURES . . . . . . . . . 13-12 ASSIGNMENT_SUCCESS_RATE . . . . . 18-12
ALLOC_SDCCH . . . . . . . . . . . . . . 4-22 ATER_CHANNEL_REQUEST . . . . . . . 12-3
ALLOC_SDCCH_CARR . . . . . . . . . . . 6-4 ATER_CHANNEL_STATUS . . . . . . . . 12-4
ALLOC_SDCCH_FAIL . . . . . . . . . . . 4-23 ATER_PREEMPT_ATMPT . . . . . . . . . 12-6
ALLOC_TCH . . . . . . . . . . . . . . . 4-24 ATER_PREEMPT_ATMPT_SWOVER . . . . 12-7
ALLOC_TCH_CARR . . . . . . . . . . . . . 6-5 ATER_PREEMPT_FAIL . . . . . . . . . . 12-8
ALLOC_TCH_FAIL. . . . . . . . . . . . . 4-25 ATER_PREEMPT_FAIL_SWOVER . . . . . 12-9
ALLOC_TCH_FAIL_HR . . . . . . . . . . 4-26 ATER_PREEMPT_RQD . . . . . . . . . . 12-10
ALLOC_TCH_FAIL_INNER_ZONE . . . . . 4-28 ATTEMPT_IMMED_ASSIGN_PROC . . . . 17-6
ALLOC_TCH_HR . . . . . . . . . . . . . 4-30 AVAILABLE_SDCCH . . . . . . . . . . . 4-44
ALLOC_TCH_SIG . . . . . . . . . . . . . 4-32 AVAILABLE_TCH . . . . . . . . . . . . . 4-46
AMR_DECREASE_THRESH_ADJUST . . . 4-33 AVAILABLE_TCH_DCS1800 . . . . . . . . 4-48
AMR_FR_DL_ADAPTATION . . . . . . . . 4-34 AVAILABLE_TCH_EGSM . . . . . . . . . 4-50
AMR_FR_DL_CODEC_MODE_USAGE . . . 4-35 AVAILABLE_TCH_PGSM . . . . . . . . . 4-53
AMR_FR_UL_ADAPTATION . . . . . . . . 4-36
BAD_HO_REFNUM_MS . . . . . . . . . . 4-55 BSSLAP_ABORT_RCV . . . . . . . . . . . 10-4

Band reassignment BSSLAP_ABORT_SENT . . . . . . . . . . 10-5
introduction BSSLAP_MS_POS_CMD . . . . . . . . . . 10-6
fail recovered . . . . . . . . . . . . . 19-68 BSSLAP_MS_POS_RESP . . . . . . . . . 10-7
handover successful . . . . . . . . . 19-67 BSSLAP_REJ . . . . . . . . . . . . . . . 10-8
handover unsuccessful . . . . . . . . 19-68 BSSLAP_RESET . . . . . . . . . . . . . . 10-9
BAND_HANDOVER . . . . . . . . . . . . 4-200 BSSLAP_TA_REQ . . . . . . . . . . . . . 10-10
BAND_RE_ASSIGN . . . . . . . . . . . . 4-200 BSSLAP_TA_RESP. . . . . . . . . . . . . 10-11
BER . . . . . . . . . . . . . . . . . . . . . 6-6 BSSLAP_TOA_REQ . . . . . . . . . . . . 10-12
BSC BSSMAP_CONLESS_INFO_RCV. . . . . . 10-13
functions . . . . . . . . . . . . . . . . 19-4 BSSMAP_CONLESS_INFO_SENT . . . . . 10-14
BSS BSSMAP_PERF_LOC_ABORT_MSGS . . . 10-15
functions . . . . . . . . . . . . . . . . 19-4 BSSMAP_PERF_LOC_REQ_MSGS . . . . . 10-16
BSS_AVAILABILITY . . . . . . . . . . . . . 3-4 BSSMAP_PERF_LOC_RESP_MSGS . . . 10-17,
BSS_OVLD_MSGS_TX . . . . . . . . . . . . 3-6 10-21
68P02901W56-T IX-1
Jan 2010
Index
BSSMAPLE_CONLESS_INFO_RCV . . . . 10-18 BUSY_TCH_CARR . . . . . . . . . . . 4-60, 6-8

BSSMAPLE_CONLESS_INFO_SENT . . . 10-19 BUSY_TCH_CARR_HR . . . . . . . . . . . 6-9
BSSMAPLE_PERF_LOC_ABORT_MSGS . . 10-20 BUSY_TCH_DCS1800 . . . . . . . . . . . 4-61
BSSMAPLE_PERF_LOC_RESP_MSGS . . . 10-22 BUSY_TCH_EGSM . . . . . . . . . . . . 4-62
BUSY_CICS . . . . . . . . . . . . . . . . 11-4 BUSY_TCH_HR . . . . . . . . . . . . 4-52, 4-63
BUSY_SDCCH. . . . . . . . . . . . . . . 4-56 BUSY_TCH_PGSM . . . . . . . . . . . . 4-64
BUSY_TCH . . . . . . . . . . . . . . . . 4-58
C_SETUP_TCH_BLOCKING_RATE . . . . 16-3 CHAN_UL_TX_PWR_LVL . . . . . . . . . 6-13

C_SP_VERS_DOWNGRADE_MONITOR . . 4-65 CHANNEL_REQS_REC . . . . . . . . . . 13-20
C_SUCCESS_RATE . . . . . . . . . . . . 18-19 CHANNEL_REQS_REJ . . . . . . . . . . 13-22
C_VOLUME . . . . . . . . . . . . . . . . 18-21 CHANNEL_REQS_SUCCESS . . . . . . . 13-23
call clearing chg_stat_prop . . . . . . . . . . . . . . . 2-47
cipher mode fail. . . . . . . . . . . . . 19-47 chg_stat_prop command . . . . . . . . . 2-42
queueing timeout . . . . . . . . . . . . 19-50 CIPHER_MODE_FAIL . . . . . . . . . . . 4-70
RF loss on a TCH . . . . . . . . . . . . 19-49 CLASSMK_UPDATE_FAIL . . . . . . . . . 4-71
RF loss on an SDCCH . . . . . . . . . . 19-48 CLR_CMD_FROM_MSC . . . . . . . . . . 4-72
Call model statistics. . . . . . . . . . . . 16-1 CLR_REQ_CALL_SETUP . . . . . . . . . 4-75
C_SETUP_TCH_BLOCKING_RATE . . . 16-3 CLR_REQ_TO_MSC . . . . . . . . . . . . 4-73
HANDOVERS_PER_C (H) . . . . . . . . 16-4 cm_lcs_request . . . . . . . . . . . . . . 4-139
IMSI_DETACHES_TO_C (Id) . . . . . . 16-6 CM_REESTABLISH . . . . . . . . . . . . 4-139
INTRA_BSS_HO_TO__HO (i) . . . . . . 16-8 CM_SERV_REQ_C . . . . . . . . . . . . . 4-139
LOCATION_UPDATE_FACTOR (L). . . . 16-9 CM_SERV_REQ_EMERG . . . . . . . . . 4-139
LOCATION_UPDATES_TO_CS (I) . . . . 16-10 CM_SERV_REQ_SMS . . . . . . . . . . . 4-139
PAGES_PER_C (PPC) . . . . . . . . . . 16-12 CM_SERV_REQ_SUPP . . . . . . . . . . 4-139
PAGES_PER_SECOND . . . . . . . . . 16-13 CODING_SCHEME_CHANGE . . . . . . . 13-25
PAGING_RATE (P). . . . . . . . . . . . 16-14 CONG_REL_DL_SCTS . . . . . . . . . . . 13-27
SMS_TO_C_RATIO (S). . . . . . . . . . 16-15 CONGEST_EXIST_HO_ATMPT . . . . . . 4-76
call procedure CONGEST_STAND_HO_ATMPT . . . . . . 4-77
bids . . . . . . . . . . . . . . . . . . . 19-6 CONGESTION . . . . . . . . . . . . . . 4-200
bids-attempt-fail-recovered . . . . . . . 19-6 Congestion relief
bids-attempt-failures . . . . . . . . . . 19-6 intra-BSS . . . . . . . . . . . . . . . . 19-53
bids-attempts . . . . . . . . . . . . . . 19-6 CONGESTION_LOST_MSU . . . . . . . . 11-6
bids-attempts-successes. . . . . . . . . 19-6 CONN_REFUSED . . . . . . . . . . . . . 4-78
bids-bids blocked . . . . . . . . . . . . 19-6 CONN_REQ_TO_MSC . . . . . . . . . . . 4-80
call setup and handover matrix . . . . . . 19-7 connection establishment
call statistics failure
call_statistics . . . . . . . . . . . . . . 4-120 failute . . . . . . . . . . . . . . . . . 19-13
CALL_SETUP_RF_ASSIGN- immediate assignment blocked . . . . . 19-14
MENT_FAIL_RATE_LOST_MS . . . . . . . 18-13 immediate assignment failure . . . . . . 19-15
CALL_SETUP_RF_ASSIGN- successful
MENT_FAIL_RATE_RECOVERED_MS . . . 18-15 mobile originated . . . . . . . . . . . 19-10
CALL_SETUP_RF_ASSIGNMENT_SUC- mobile terminated call . . . . . . . . 19-16
CESS_RATE . . . . . . . . . . . . . . . . 18-17 Counter array statistics . . . . . . . . . . . 1-7
cell statistics Counter array bins . . . . . . . . . . . . 1-7
introduction . . . . . . . . . . . . . . . . 4-2 Interval expiry . . . . . . . . . . . . . . 1-7
CELL_FLUSH_REQS . . . . . . . . . . . 13-17 Maximum values . . . . . . . . . . . . . 1-7
CELL_TCH_ASSIGNMENTS. . . . . . . . 17-9 Counter statistics . . . . . . . . . . . 1-6, 2-45
CELL_TCH_OCATIONS . . . . . . . . . . 17-8 Interval expiry . . . . . . . . . . . . . . 1-6
CH_REQ_UNSVCD_PCU . . . . . . . . . 13-18 Maximum value . . . . . . . . . . . . . . 1-6
CHAN_DL_TX_PWR_LVL . . . . . . . . . 6-10 Threshold event reporting . . . . . . . . 1-6
CHAN_REQ_CAUSE_ATMPT . . . . . 4-68, 10-2 CPU_USAGE . . . . . . . . . . . . . . . . 7-2
CHAN_REQ_MS_BLK . . . . . . . . . . . 4-69 CS_PAGE_REQS. . . . . . . . . . . . . . 13-29
CHAN_REQ_MS_FAIL . . . . . . . . . . . 6-11 CS_QUEUED . . . . . . . . . . . . . . . 4-67
IX-2 68P02901W56-T
Jan 2010
Index
CS12_ON_32K_CHAN . . . . . . . . . . . 13-30 Custom statistics . . . . . . . . . . . . . . 1-4

CS1234_ON_64K_CHAN . . . . . . . . . 13-31
default values . . . . . . . . . . . . . . . . 2-2 DL_BLER_MCS5 . . . . . . . . . . . . . 13-52

Dictionary = br DL_BLER_MCS6 . . . . . . . . . . . . . 13-54
Average call duration . . . . . . . . . . 16-2 DL_BLER_MCS7 . . . . . . . . . . . . . 13-56
C_DURATION . . . . . . . . . . . . . . 16-2 DL_BLER_MCS8 . . . . . . . . . . . . . 13-58
Call model statistics DL_BLER_MCS9 . . . . . . . . . . . . . 13-60
C_DURATION . . . . . . . . . . . . . 16-2 DL_BUSY_PDTCH . . . . . . . . . . . . . 13-62
Directed retry DL_EGPRS_64K_CHANNEL_WIDTH . . . 6-16
intra-BSS . . . . . . . . . . . . . . . . 19-55 DL_EGPRS_BACKHAUL_DEMAND . . . . 6-14
disabling a statistic DL_EGPRS_BACKHAUL_USED . . . . . . 6-15
disable a statistic . . . . . . . . . . . . 2-13 DL_LLC_DATA_VOLUME . . . . . . . . . 4-83
disp_interval command . . . . . . . . . . 2-40 DL_LLC_FRAMES_GB . . . . . . . . . . . 13-64
disp_stat_prop command . . . . . . . . . 2-49 DL_LLC_FRAMES_PCU . . . . . . . . . . 13-65
disp_stats command. . . . . . . . . . . . 2-21 DL_LLC_TRAFFIC_VOLUME_INDICA-
Displaying a counter array statistic . . . . 2-57 TOR . . . . . . . . . . . . . . . . . . . . 17-26
Displaying a counter statistic . . . . . . . 2-49 DL_PDTCH_Q_LENGTH . . . . . . . . . . 13-69
Displaying a distribution statistic . . . . . 2-55 DL_PDTCH_SEIZURE . . . . . . . . . . . 13-70
Displaying a duration statistic . . . . . . 2-65 DL_RADIO_BLKS_1_TS . . . . . . . . . . 13-71
Displaying a gauge statistic . . . . . . . . 2-54 DL_RADIO_BLKS_2_TS . . . . . . . . . . 13-73
Displaying statistic properties . . . . . . 2-49 DL_RADIO_BLKS_3_TS . . . . . . . . . . 13-76
Displaying a counter array statistic . . . 2-57 DL_RADIO_BLKS_4_TS . . . . . . . . . . 13-79
Displaying a counter statistic . . . . . . 2-49 DL_RLC_ACK_NEW_BLKS . . . . . . . . 13-82
Displaying a distribution statistic . . . . 2-55 DL_RLC_DDTR_BLKS . . . . . . . . . . . 13-84
Displaying a duration statistic . . . . . 2-65 DL_RLC_NACK_BLKS . . . . . . . . . . . 13-85
Displaying a gauge statistic . . . . . . . 2-54 DL_RLC_RETX_BLKS . . . . . . . . . . . 13-87
Displaying statistic values. . . . . . . . . 2-21 DL_RLC_STED_BLKS . . . . . . . . . . . 13-89
Displaying the statistics interval . . . . . 2-39 DL_RLC_UNACK_NEW_BLKS . . . . . . . 13-91
Displaying the statistics interval start DL_TBF_TIME_1_TS . . . . . . . . . . . 13-95
times . . . . . . . . . . . . . . . . . . . 2-40 DL_TBF_TIME_2_TS . . . . . . . . . . . 13-96
DISTANCE . . . . . . . . . . . . . . . . 4-200 DL_TBF_TIME_3_TS . . . . . . . . . . . 13-97
Distribution statistics . . . . . . . . . . . . 1-9 DL_TBF_TIME_4_TS . . . . . . . . . . . 13-98
DL_BANDWIDTH_INDICATOR_EG- DOWNINTERF . . . . . . . . . . . . . . 4-200
PRS . . . . . . . . . . . . . . . . . . . . 18-23 DOWNLEVEL . . . . . . . . . . . . . . . 4-200
DL_BANDWIDTH_INDICATOR_GPRS . . . 18-26 DOWNQUAL . . . . . . . . . . . . . . . 4-200
DL_BLER_CS1 . . . . . . . . . . . . . . 13-36 DROP_CALL_RATE . . . . . . . . . . . . 18-28
DL_BLER_CS2 . . . . . . . . . . . . . . 13-38 Duration statistics . . . . . . . . . . . . . 1-8
DL_BLER_CS3 . . . . . . . . . . . . . . 13-40 Interval expiry . . . . . . . . . . . . . . 1-8
DL_BLER_CS4 . . . . . . . . . . . . . . 13-42 Maximum value . . . . . . . . . . . . . . 1-8
DL_BLER_MCS1 . . . . . . . . . . . . . 13-44 Period counter and mean value . . . . . . 1-8
DL_BLER_MCS2 . . . . . . . . . . . . . 13-46 Total duration . . . . . . . . . . . . . . . 1-8
DL_BLER_MCS3 . . . . . . . . . . . . . 13-48 Wraparound to next day. . . . . . . . . . 1-8
DL_BLER_MCS4 . . . . . . . . . . . . . 13-50
EGPRS_64K_CHAN- EGSM (extended GSM) . . . . . . . . . . 20-2

NELS_SWITCHED . . . . . . . . . . . 13-103 enabling a statistic
EGPRS_64K_NOT_AVAIL . . . . . . . . 13-104 enable a statistic . . . . . . . . . . . . . 2-3
EGPRS_AVAIL_PDTCH . . . . . . . . . 13-105 ER_INTRA_CELL_HO_ATMPT . . . . . . . 4-87
EGPRS_DL_ASGN_PCCCH . . . . . . . 13-106 ER_INTRA_CELL_HO_SUC . . . . . . . . 4-88
68P02901W56-T IX-3
Jan 2010
Index
feature FER_AMR_FR . . . . . . . . . . . . . . . 6-17

23306 . . . . . . . . . . . . . . . . . . . 7-1 FER_AMR_HR. . . . . . . . . . . . . . . 6-19
26740 . . . . . . . . . . . . . . . . . . 13-6 FER_GSM_FR_EFR . . . . . . . . . . . . 6-21
27703A . . 4-9, 4-153 to 4-154, 4-157, 4-159, FER_GSM_HR. . . . . . . . . . . . . . . 6-24
4-161, 4-163, 4-166 to 4-167, 4-170, 4-173, FLOW_CONTROL_BARRED . . . . . . . . 4-89
4-176, 4-225, 13-162 to 13-163 FRMR . . . . . . . . . . . . . . . . . . . 12-13
28000 . . . . . . . . . . . . 13-164 to 13-165
28351 . . . . . . . . 13-164 to 13-165, 13-169
G_RACH_UNSVCD_BTS . . . . . . . . . 13-107 GCI_FOR_64KPD_DEMAND. . . . . . . . . 7-6

Gauge statistics . . . . . . . . . . . . . . . 1-7 GPRS performance . . . . . . . . . . . . 18-2
Interval expiry . . . . . . . . . . . . . . 1-7 GPRS_32K_CHANNELS_SWITCHED . . 13-122
Threshold event reporting . . . . . . . . 1-7 GPRS_32K_DL_NOT_AVAIL . . . . . . . 13-123
Gb interface. . . . . . . . . . . . . . . . 13-2 GPRS_32K_UL_NOT_AVAIL . . . . . . . 13-124
GBL statistics . . . . . . . . . . . . . . . 19-76 GPRS_ACCESS_PER_AGCH . . . . . . . 13-125
GBL_DL_DATA_THRPUT . . . . . . . . 13-109 GPRS_ACCESS_PER_RACH . . . . . . . 13-126
GBL_DL_DATA_THRPUT_HIST . . . . . 13-110 GPRS_AVAIL_PDTCH . . . . . . . . . . 13-127
GBL_FLOW_CTRL_SENT . . . . . . . . 13-114 GPRS_CELL_CONGESTION . . . . . . . 13-129
GBL_FLUSH_REQS GPRS_CELL_RESELECT_FAIL . . . . . 13-131
see CELL_FLUSH_REQS . . . . . . . . 13-17 GPRS_CHANNELS_SWITCHED . . . . . 13-132
GBL_PAGING_REQS . . . . . . . . . . 13-115 GPRS_DL_ASGN_PCCCH . . . . . . . . 13-133
GBL_UL_DATA_THRPUT . . . . . . . . 13-117 GPRS_PCH_AGCH_Q_LENGTH . . . . . 13-136
GBL_UL_DATA_THRPUT_HIST . . . . . 13-118 GPRS_PPCH_PAGCH_Q_LENGTH
GBL_UNAVAILABLE . . . . . . . . . . 13-121 GPRS_PCH_AGCH_Q_LENGTH . . . . 13-137
GCI_FOR_16KPD_DEMAND. . . . . . . . . 7-4 GPRS_PRR_BLK_USG . . . . . . . . . . 13-138
GCI_FOR_32KPD_DEMAND. . . . . . . . . 7-5 GPRS_RACH_ARRIVAL . . . . . . . . . 13-140
handover . . . . . . . . . . . . . . . . . 19-5 HO_CAUSE_DISTANCE . . . . . . . . . . 18-37

handover performance . . . . . . . . . . 18-2 HO_CAUSE_DLINTERF . . . . . . . . . . 18-38
Handover successful HO_CAUSE_DLLEVEL . . . . . . . . . . 18-39
band reassignment HO_CAUSE_DLQUAL . . . . . . . . . . . 18-40
introduction . . . . . . . . . . . . . . 19-67 HO_CAUSE_PWRBGT . . . . . . . . . . . 18-41
HANDOVER_FAILURE_RATE . . . . . . . 17-53 HO_CAUSE_UPINTERF . . . . . . . . . . 18-42
HANDOVER_SUCCESS_RATE. . . . . . . 17-55 HO_CAUSE_UPLEVEL . . . . . . . . . . 18-43
Handovers HO_CAUSE_UPQUAL . . . . . . . . . . . 18-44
ratio per call . . . . . . . . . . . . . . 16-4 HO_FAIL_NO_RESOURCES . . . . . . . . 4-90
HANDOVERS_PER_C . . . . . . . . . . . 16-4 HO_PER_C . . . . . . . . . . . . . . . . 18-45
health check . . . . . . . . . . . . . . . 18-4 HO_REQ_ACK_TO_MSC . . . . . . . . . . 4-94
HO_CAUSE_ADJ_CH_INTERF . . . . . . . 18-33 HO_REQ_FROM_MSC. . . . . . . . . . . 4-92
HO_CAUSE_BAND_HO . . . . . . . . . . 18-34 HO_REQ_MSC_FAIL . . . . . . . . . . . 4-93
HO_CAUSE_BAND_REASSGN . . . . . . 18-35 HO_REQ_MSC_PROTO . . . . . . . . . . . 3-7
HO_CAUSE_CONGEST . . . . . . . . . . 18-36
IX-4 68P02901W56-T
Jan 2010
Index
I_FRAMES_RX . . . . . . . . . . . . . . 12-14 Interband activity

I_FRAMES_TX . . . . . . . . . . . . . . 12-15 inter-BSS
IDLE_PDTCH_INTF_BAND0 . . . . . . 13-142 fail recovered . . . . . . . . . . . . . 19-64
IDLE_PDTCH_INTF_BAND1 . . . . . . 13-143 handover successful . . . . . . . . . 19-63
IDLE_PDTCH_INTF_BAND2 . . . . . . 13-144 handover unsuccessful . . . . . . . . 19-64
IDLE_PDTCH_INTF_BAND3 . . . . . . 13-145 invalid frequency supported . . . . . 19-65
IDLE_PDTCH_INTF_BAND4 . . . . . . 13-146 intra-BSS
IDLE_TCH_INTF_BAND0 . . . . . . . . . 4-97 fail recovered . . . . . . . . . . . . . 19-60
IDLE_TCH_INTF_BAND1 . . . . . . . . . 4-98 handover unsuccessful . . . . . . . . 19-60
IDLE_TCH_INTF_BAND2 . . . . . . . . . 4-99 invalid frequency supported . . . . . 19-61
IDLE_TCH_INTF_BAND3 . . . . . . . . . 4-100 Interband assignment
IDLE_TCH_INTF_BAND4 . . . . . . . . . 4-101 invalid frequency . . . . . . . . . . . . 19-66
IMM_ASSGN_CAUSE . . . . . . . . . . 13-147 INTERBAND_ACTIVITY . . . . . . . . . . 4-105
IMMEDIATE_ASSIGN_BLOCK- INTERNAL_LOST . . . . . . . . . . . . . 18-56
ING_RATE. . . . . . . . . . . . . . . . . 18-47 INTERNAL_RECOVERED . . . . . . . . . 18-57
IMMEDIATE_ASSIGN_FAIL- INTERNAL_SUCCESS . . . . . . . . . . 18-58
URE_RATE . . . . . . . . . . . . . . . . 18-48 INTF_ON_IDLE . . . . . . . . . . . . . . 6-26
IMMEDIATE_ASSIGN_MEAN_AR- Intra-BSS
RIVAL_TIME . . . . . . . . . . . . . . . 18-49 congestion relief . . . . . . . . . . . . 19-53
IMMEDIATE_ASSIGN_SUC- directed retry . . . . . . . . . . . . . . 19-55
CESS_RATE . . . . . . . . . . . . . . . . 18-50 intra-BSS handover
IMSI detaches fail-lost . . . . . . . . . . . . . . . . . 19-39
ratio per call . . . . . . . . . . . . . . 16-6 fail-recovered . . . . . . . . . . . . . . 19-38
IMSI_DETACH . . . . . . . . . . . . . . 4-139 handover blocked . . . . . . . . . . . . 19-37
IMSI_DETACHES_TO_C . . . . . . . . . . 16-6 handover successful. . . . . . . . . . . 19-36
IN_3G_HO_FAIL_RATE . . . . . . . . . . 17-59 standard directed retry
IN_3G_HO_SUCC_RATE. . . . . . . . . . 17-60 internal . . . . . . . . . . . . . . . . 19-40
IN_INTER_BSS_EQUIP_FAIL . . . . . . . 4-102 Intra-BSS handovers . . . . . . . . . . . 16-8
IN_INTER_BSS_HO . . . . . . . . . . . . 4-102 INTRA_BSS_HO_CAUSE_SUCC . . . . . . . 3-8
IN_INTER_BSS_HO_CLEARED . . . . . . 4-102 INTRA_BSS_HO_TO__HO . . . . . . . . . 16-8
IN_INTER_BSS_HO_SEIZE . . . . . . . . 4-102 intra-cell handover
IN_INTER_BSS_HO_SUC . . . . . . . . . 18-51 fail lost . . . . . . . . . . . . . . . . . 19-26
IN_INTER_BSS_HO_SUCCESS_RATE . . . 4-102 fail recovered . . . . . . . . . . . . . . 19-25
IN_INTER_CELL_HO_SUC . . . . . . . . 18-52 handover blocked . . . . . . . . . . . . 19-24
IN_INTER_CELL_HO_TO_IN_ZONE . . . . 4-229 handover successful. . . . . . . . . . . 19-23
to 4-230 INTRA_CELL_EQUIP_FAIL . . . . . . . . 4-107
IN_INTRA_BSS_EQUIP_FAIL . . . . . . . 4-103 INTRA_CELL_HO . . . . . . . . . . . . . 4-106
IN_INTRA_BSS_HO . . . . . . . . . . . . 4-103 INTRA_CELL_HO_ATMPT_FR_FR . . . . . 4-106
IN_INTRA_BSS_HO_CLEARED . . . . . . 4-103 INTRA_CELL_HO_ATMPT_FR_HR. . . . . 4-106
IN_INTRA_BSS_HO_LOSTMS . . . . . . . 4-103 INTRA_CELL_HO_ATMPT_HR_FR. . . . . 4-106
IN_INTRA_BSS_HO_RETURN . . . . . . . 4-103 INTRA_CELL_HO_ATMPT_HR_HR . . . . 4-106
IN_INTRA_BSS_HO_SUC . . . . . 4-103, 18-54 INTRA_CELL_HO_ATMPT_SD_TO_SD . . . 4-107
IN_INTRA_BSS_NC_ATMPT . . . . . . . . . 5-8 INTRA_CELL_HO_ATTEMPT_RATE . . . . 18-85
IN_INTRA_BSS_NC_SUC . . . . . . . . . . 5-9 INTRA_CELL_HO_CLEARED . . . . . . . 4-107
INCOMING_HO_VOLUME . . . . . . . . 18-55 INTRA_CELL_HO_FAIL_LOST_MS . . . . 18-59
INNER_TO_OUTER_ZONE . . . 4-229 to 4-230 INTRA_CELL_HO_FAIL_RECOVERED. . . 18-60
inter-BSS handover INTRA_CELL_HO_LOSTMS . . . . . . . . 4-107
fail lost . . . . . . . . . . . . . . . . . 19-30 INTRA_CELL_HO_REQ . . . . . . . . . . 4-106
fail lost mobile . . . . . . . . . . . . . 19-31 INTRA_CELL_HO_RETURN . . . . . . . . 4-107
fail recovered . . . . . . . . . . . . . . 19-29 INTRA_CELL_HO_SUC . . . . . . . . . . 4-106
handover blocked . . . . . . . . . . . . 19-28 INTRA_CELL_HO_SUCCESS_RATE . . . . 18-61
handover successful. . . . . . . . . . . 19-27 INTRA_ZONE . . . . . . . . . . 4-229 to 4-230
standard directed retry INVALID_FRAMES_RX . . . . . . . . . . 12-16
external . . . . . . . . . . . . . . . . 19-32
68P02901W56-T IX-5
Jan 2010
Index
key statistics . . . . . . 1-3, 17-2, 17-4 to 17-5 key statistics (contd.)

ATTEMPT_IMMED_ASSIGN_PROC . . . 17-6 SDCCH_TRAFFIC_CARRIED . . . . . 17-101
call summary . . . . . . . . . . . . . . 17-2 SUCCESS_IMMED_ASSIGN_PROC . . 17-103
CELL_TCH_ASSIGNMENTS. . . . . . . 17-9 SUCCESS_INTERNAL_HO . . . . . . 17-104
CELL_TCH_OCATIONS . . . . . . . . . 17-8 TCH_BLOCKING_RATE . . . . . . . . 17-106
channel usage. . . . . . . . . . . . . . 17-2 TCH_BLOCKING_RATE_INNER_Z . . 17-107
connection establishment . . . . . . . . 17-4 TCH_BLOCK-
HANDOVER_FAILURE_RATE . . . . . . 17-53 ING_RATE_OUT_ZONE . . . . . . . . 17-108
HANDOVER_SUCCESS_RATE. . . . . . 17-55 TCH_CARRIER_MEAN_HOLD-
loss summary . . . . . . . . . . . . . . 17-4 ING_TIME. . . . . . . . . . . . . . . 17-110
MEAN_ARRIVAL_TIME_BE- TCH_MEAN_ARRIVAL_RATE . . . . . 17-111
TWEEN_CS . . . . . . . . . . . . . . . 17-86 TCH_MEAN_HOLDING_TIME. . . . . 17-112
MEAN_INTER_ARRIVAL_TIME . . . . . 17-87 TCH_TRAFFIC_CARRIED . . . 17-116, 18-126
MEAN_TCH_BUSY_TIME . . . . . . . . 17-89 template . . . . . . . . . . . . . . . . 17-5
MTL_UTILISATION_RX . . . . . . . . . 17-90 TOTAL_CS_KEY . . . . . . . . . . . . 17-120
MTL_UTILISATION_TX . . . . . . . . . 17-91 UNSUCCESS_INTER-
RF_LOSS_RATE . . . . . . . . . . . . . 17-96 NAL_HO_NOREEST . . . . . . . . . . 17-142
SDCCH_BLOCKING_RATE . . . . . . . 17-98 UNSUCCESS_INTER-
SDCCH_MEAN_HOLDING_TIME . . . . 17-99 NAL_HO_REEST . . . . . . . . . . . 17-143
SDCCH_RF_LOSS_RATE . . . . . . . 17-100
L_ROUTING_SYNTAX . . . . . . . . . . . 14-3 LMTP_MSU_DISCARDED . . . . . . . . . . 9-5

L_ROUTING_UNKNOWN . . . . . . . . . 14-4 LMTP_MSU_RX . . . . . . . . . . . . . . 9-15
L_SCCP_MSGS . . . . . . . . . . . . . . 14-5 LMTP_MSU_TX . . . . . . . . . . . . . . 9-16
L_SCCP_MSGS_RX . . . . . . . . . . . . 14-6 LMTP_NEG_ACKS . . . . . . . . . . . . 9-17
l_sccp_msgs_rx_0 . . . . . . . . . . . . . 14-6 LMTP_RE_TX . . . . . . . . . . . . . . . 9-18
l_sccp_msgs_rx_2 . . . . . . . . . . . . . 14-6 LMTP_REMOTE_MGT. . . . . . . . . . . 9-19
L_SCCP_MSGS_TX . . . . . . . . . . . . 14-7 LMTP_REMOTE_PROC . . . . . . . . . . 9-20
l_sccp_msgs_tx_0 . . . . . . . . . . . . . 14-7 LMTP_RESTORATION . . . . . . . . . . 9-21
l_sccp_msgs_tx_2 . . . . . . . . . . . . . 14-7 LMTP_SIB_RX. . . . . . . . . . . . . . . 9-34
L_SIF_SIO_RX_OPC . . . . . . . . . . . . 14-8 LMTP_SIB_TX . . . . . . . . . . . . . . . 9-36
L_SIF_SIO_TX_OPC . . . . . . . . . . . . 14-9 LMTP_SIF_SIO_RX . . . . . . . . . . . . 9-22
l_sif_sio_type . . . . . . . . . . . . . . . 14-10 LMTP_SIF_SIO_TX . . . . . . . . . . . . 9-23
L_SIF_SIO_TYPE . . . . . . . . . . . . . 14-10 LMTP_SL_ACK . . . . . . . . . . . . . . 9-24
l_sif_sio_type_mtp . . . . . . . . . . . . . 14-10 LMTP_SL_ALIGNMENT . . . . . . . . . . 9-25
l_sif_sio_type_test . . . . . . . . . . . . . 14-10 LMTP_SL_CONGESTION . . . . . . . . . 9-26
LAPD_CONGESTION . . . . . . . . . . . 12-17 LMTP_SL_ERROR_RATE . . . . . . . . . 9-27
LLC_ABNORMAL_TBF_RELEASES . . . . 17-61 LMTP_SL_FAIL . . . . . . . . . . . . . . 9-28
LLC_BUFFER_OVERFLOW_RATE . . . . . 17-62 LMTP_SL_FIBR . . . . . . . . . . . . . . 9-29
LLC_DISCARDS_ON_CELL_RESELEC- LMTP_START_RPO . . . . . . . . . . . . 9-30
TION . . . . . . . . . . . . . . . . . . . 17-85 LMTP_STOP_RPO . . . . . . . . . . . . . 9-31
LMTP_CHANGEBACK. . . . . . . . . . . . 9-6 LMTP_SU_ERROR . . . . . . . . . . . . 9-32
LMTP_CHANGEOVER. . . . . . . . . . . . 9-7 LMTP_UNAVAILABLE . . . . . . . . . . . 9-33
LMTP_CONGESTION . . . . . . . . . . . 9-35 LOC_FLW_ON_REQ_NORM . . . . . . . . 4-139
LMTP_LINK_INS . . . . . . . . . . . . . . 9-9 LOC_FLW_ON_REQ_SMS . . . . . . . . . 4-139
LMTP_LINKFAIL . . . . . . . . . . . . . 9-10 Location updates
LMTP_LOCAL_BUSY . . . . . . . . . . . 9-11 ratio per call . . . . . . . . . . . . . . 16-10
LMTP_LOCAL_MGT . . . . . . . . . . . . 9-12 LOCATION_SERVICES . . . . . . . . . . 4-139
LMTP_LOCAL_SL_CONGESTION . . . . . . 9-8 LOCATION_UPDATE . . . . . . . . . . . 4-139
LMTP_MGT_INHIBIT . . . . . . . . . . . 9-13 LOCATION_UPDATE_FACTOR . . . . . . 16-9
LMTP_MGT_UNINHIBIT . . . . . . . . . 9-14 LOCATION_UPDATES_TO_CS. . . . . . . 16-10
IX-6 68P02901W56-T
Jan 2010
Index
MA_CMD_TO_MS MSGS_DISCARD_ON_RSL . . . . . . . . 12-18

MS_CMD_TO_MS . . . . . . . . . . . . 4-109 MSU_DISCARDED . . . . . . . . . . . . 11-7
MA_CMD_TO_MS_BLKD . . . . . . . . . 4-116 MT_LCS_ON_SDCCH . . . . . . . . . . . 4-122
MA_COMPLETE_TO_MS . . . . . . . . . 4-110 MTL
MA_COMPLETE_TO_MSC. . . . . . . . . 4-111 operator initiated outage . . . . . . . . 19-72
MA_FAIL_FROM_MS . . . . . . . . . . . 4-113 transition scenarios . . . . . . . . . . . 19-73
MA_REQ_FROM_MSC. . . . . . . . . . . 4-114 MTL_UTILISATION_RX . . . . . . . . . . 17-90
MA_REQ_FROM_MSC_FAIL. . . . . . . . 3-10 MTL_UTILISATION_TX . . . . . . . . . . 17-91
MAX_TCH_BUSY . . . . . . . . . . . . . 18-63 MTP_CHANGEBACK . . . . . . . . . . . 11-8
MEAN_ARRIVAL_TIME_BE- MTP_CHANGEOVER . . . . . . . . . . . 11-9
TWEEN_CS . . . . . . . . . . . . . . . . 17-86 MTP_CONGESTION. . . . . . . . . . . . 11-10
MEAN_INTER_ARRIVAL_TIME . . . . . . 17-87 MTP_LINK_INS . . . . . . . . . . . . . . 11-11
MEAN_TBF_SESSIONS . . . . . . . . . . 17-88 MTP_LINKFAIL . . . . . . . . . . . . . . 11-12
MEAN_TCH_BUSY_TIME . . . . . . . . . 17-89 MTP_LOCAL_BUSY . . . . . . . . . . . . 11-13
MEAN_TIME_BETWEEN_DROPS . . . . . 18-65 MTP_LOCAL_MGT . . . . . . . . . . . . 11-14
MEAN_TIME_BETWEEN_HOs . . . . . . 18-66 MTP_MGT_INHIBIT . . . . . . . . . . . . 11-15
MMI BSC/BTS statistics MTP_MGT_UNINHIBIT . . . . . . . . . . 11-16
HO_FAIL_NO_RESOURCES . . . . . . . 15-2 MTP_MSU_RX . . . . . . . . . . . . . . 11-17
HO_REQ_MSC_FAIL . . . . . . . . . . 15-2 MTP_MSU_TX. . . . . . . . . . . . . . . 11-18
MA_CMD_TO_MS_BLKD . . . . . . . . 15-2 MTP_NEG_ACKS . . . . . . . . . . . . . 11-19
OC_SDCCH_FAIL . . . . . . . . . . . . 15-2 MTP_RE_TX . . . . . . . . . . . . . . . . 11-20
OC_TCH_FAIL. . . . . . . . . . . . . . 15-2 MTP_REMOTE_MGT . . . . . . . . . . . 11-21
RF_LOSSES_TCH . . . . . . . . . . . . 15-2 MTP_REMOTE_PROC . . . . . . . . . . . 11-22
MMI PCU statistic MTP_RESTORATION . . . . . . . . . . . 11-23
CELL_FLUSH_REQS . . . . . . . . . . 15-2 MTP_SIF_SIO_RX . . . . . . . . . . . . . 11-24
CHANNEL_REQS_REJ . . . . . . . . . 15-2 MTP_SIF_SIO_TX . . . . . . . . . . . . . 11-25
GBL_PAGING_REQS . . . . . . . . . . 15-2 MTP_SL_ACK . . . . . . . . . . . . . . . 11-26
GBL_UNAVAILABLE . . . . . . . . . . 15-2 MTP_SL_ALIGNMENT . . . . . . . . . . 11-27
Monitoring faults . . . . . . . . . . . . . 1-16 MTP_SL_CONGESTION . . . . . . . . . . 11-28
MS_ACCESS_BY_TYPE . . . . . . . . . . 4-118 MTP_SL_ERROR_RATE . . . . . . . . . . 11-29
MS_TCH_USAGE_BY_TYPE . . . . . . . . 4-119 MTP_SL_FAIL . . . . . . . . . . . . . . . 11-31
MS_TCH_USAGE_BY_TYPE_PCS . . . . . 4-120 MTP_SL_FIBR. . . . . . . . . . . . . . . 11-32
MSC functions MTP_START_RPO . . . . . . . . . . . . . 11-33
MSC function . . . . . . . . . . . . . . 19-4 MTP_STOP_RPO . . . . . . . . . . . . . 11-34
MSC_OLVD_MSGS_RX . . . . . . . . . . 3-11 MTP_SU_ERROR . . . . . . . . . . . . . 11-35
MSC_PAGING . . . . . . . . . . . . . . . 18-64 MTP_UNAVAILABLE . . . . . . . . . . . 11-36
MSGS_DISCARD_ON_GPROC . . . . . . . . 7-7
N2_EXPIRY . . . . . . . . . . . . . . . . 12-19 Network health statistics (contd.)

Network health statistics . . . . . . . . . . 1-3 CALL_SETUP_RF_ASSIGN-
AIR_INTERFACE_BW_CS1 . . . . . . . 18-7 MENT_FAIL_RATE_RECOV-
AIR_INTERFACE_BW_CS2 . . . . . . . 18-8 ERED_MS . . . . . . . . . . . . . . . . 18-15
AIR_INTERFACE_BW_CS3 . . . . . . . 18-9 CALL_SETUP_RF_ASSIGNMENT_SUC-
AIR_INTERFACE_BW_CS4 . . . . . . . 18-10 CESS_RATE . . . . . . . . . . . . . . . 18-17
AIR_INTERFACE_PAGING . . . . . . . 18-11 CELL_CONGESTION_TIME . . . . . . . 18-22
ASSIGNMENT_SUCCESS_RATE . . . . 18-12 DL_BANDWIDTH_INDICATOR_EG-
C_SETUP_SUCCESS_RATE . . . . . . . 17-7 PRS . . . . . . . . . . . . . . . . . . . 18-23
C_SUCCESS_RATE . . . . . . . . . . . 18-19 DL_BANDWIDTH_INDICA-
C_VOLUME . . . . . . . . . . . . . . . 18-21 TOR_GPRS . . . . . . . . . . . . . . . 18-26
CALL_SETUP_RF_ASSIGN- DROP_CALL_RATE . . . . . . . . . . . 18-28
MENT_FAIL_RATE_LOST_MS . . . . . . 18-13 GPRS performance . . . . . . . . . . . 18-2
68P02901W56-T IX-7
Jan 2010
Index
Network health statistics (contd.) Network health statistics (contd.)

handover performance . . . . . . . . . 18-2 radio performance reports . . . . . . . 18-5
health check . . . . . . . . . . . . . . 18-4 RANKING_FORMULA . . . . . . . . . . 18-86
HO_CAUSE_ADJ_CH_INTERF . . . . . . 18-33 RF_ASSIGN_FAIL_RATE_LOST_MS . . . 18-88
HO_CAUSE_BAND_HO . . . . . . . . . 18-34 RF_ASSIGN_FAIL_RATE_RECOV-
HO_CAUSE_BAND_REASSGN . . . . . 18-35 ERED . . . . . . . . . . . . . . . . . . 18-89
HO_CAUSE_CONGEST . . . . . . . . . 18-36 RF_ASSIGNMENT_SUCCESS_RATE . . 18-90
HO_CAUSE_DISTANCE . . . . . . . . . 18-37 SDCCH congestion . . . . . . . . . . . 18-5
HO_CAUSE_DLINTERF . . . . . . . . . 18-38 SDCCH_ACCESSES . . . . . . . . . . . 18-91
HO_CAUSE_DLLEVEL . . . . . . . . . 18-39 SDCCH_BLOCKING_RATE . . . . . . . 18-92
HO_CAUSE_DLQUAL . . . . . . . . . . 18-40 SDCCH_CONGESTION_TIME . . . . . . 18-93
HO_CAUSE_PWRBGT . . . . . . . . . . 18-41 SDCCH_TRAFFIC_CARRIED . . . . . . 18-94
HO_CAUSE_UPINTERF . . . . . . . . . 18-42 SDCCH_USAGE_ACCESS_FAILURE. . . 18-96
HO_CAUSE_UPLEVEL . . . . . . . . . 18-43 SDCCH_USAGE_CALL_REESTAB-
HO_CAUSE_UPQUAL . . . . . . . . . . 18-44 LISH . . . . . . . . . . . . . . . . . . 18-98
HO_PER_CALL . . . . . . . . . . . . . 18-45 SDCCH_USAGE_EMER-
IN_INTER_BSS_HO_SUC . . . . . . . . 18-51 GENCY_CALL . . . . . . . . . . . . . 18-100
IN_INTER_CELL_HO_SUC . . . . . . . 18-52 SDCCH_USAGE_IMSI_DETACH. . . . 18-102
IN_INTRA_BSS_HO_SUC . . . . . . . . 18-54 SDCCH_USAGE_LOCATION_UP-
INCOMING_HO_VOLUME . . . . . . . 18-55 DATE . . . . . . . . . . . . . . . . . 18-103
INTERNAL_LOST . . . . . . . . . . . . 18-56 SDCCH_USAGE_MS_ORIGI-
INTERNAL_RECOVERED . . . . . . . . 18-57 NATED_CALL . . . . . . . . . . . . . 18-105
INTERNAL_SUCCESS . . . . . . . . . 18-58 SDCCH_USAGE_MS_ORIGI-
INTRA_BSS_HO_ATTEMPT_RATE. . . . 18-84 NATED_SMS . . . . . . . . . . . . . 18-107
INTRA_CELL_HO_ATTEMPT_RATE . . . 18-85 SDCCH_USAGE_PAGING_RE-
INTRA_CELL_HO_FAIL_LOST_MS . . . 18-59 SPONSE . . . . . . . . . . . . . . . 18-111
INTRA_CELL_HO_FAIL_RECOV- SDCCH_USAGE_SMS . . . . . . . . . 18-113
ERED . . . . . . . . . . . . . . . . . . 18-60 SDCCH_USAGE_SMS_ORIGI-
INTRA_CELL_HO_SUCCESS_RATE . . . 18-61 NATED_SS . . . . . . . . . . . . . . 18-109
MA_REQ_SDCCH_PG_RSP . . . . . . . 18-62 SPILL_OVER_FACTOR_ATTEMPTS_AT_CON-
MAX_TCH_BUSY . . . . . . . . . . . . 18-63 GESTION_RELIEF . . . . . . . . . . 18-115
MEAN_TIME_BETWEEN_DROPS . . . . 18-65 SPILL_OVER_FACTOR_DI-
MEAN_TIME_BETWEEN_HOs . . . . . 18-66 RECTED_RETRY . . . . . . . . . . . 18-116
MSC_PAGING . . . . . . . . . . . . . . 18-64 SPILL_OVER_FACTOR_MULTI-
OUT_IN- BAND . . . . . . . . . . . . . . . . . 18-117
TER_BSS_HO_FAIL_LOST_MS . . . . . 18-69 TCH congestion . . . . . . . . . . . . . 18-6
OUT_INTER_BSS_HO_FAIL_RECOV- TCH_ACCESSES . . . . . . . . . . . 18-118
ERED . . . . . . . . . . . . . . . . . . 18-70 TCH_CONGESTION_TIME . . . . . . 18-120
OUT_INTER_BSS_HO_SUC- TCH_CONGESTION_TIME_IN-
CESS_RATE . . . . . . . . . . . . . . . 18-71 NER_ZONE . . . . . . . . . . . . . . 18-121
OUT_IN- TCH_CONGES-
TER_CELL_HO_FAIL_RATE_LOST_MS . . 18-72 TION_TIME_OUTER_ZONE . . . . . . 18-123
OUT_INTER_CELL_HO_FAIL_RATE_RECOV- TCH_RF_LOSS_RATE . . . . . 17-114, 18-124
ERED . . . . . . . . . . . . . . . . . . 18-73 UL_BANDWIDTH_INDICATOR_EG-
OUT_INTER_CELL_HO_SUC- PRS . . . . . . . . . . . . . . . . . . 18-130
CESS_RATE . . . . . . . . . . . . . . . 18-74 UL_BANDWIDTH_INDICA-
OUT_IN- TOR_GPRS . . . . . . . . . . . . . . 18-132
TRA_BSS_HO_FAIL_LOST_MS . . . . . 18-75 network interface statistics
OUT_INTRA_BSS_HO_FAIL_RECOV- BSSLAP_ABORT_RCV . . . . . . . . . . 10-4
ERED_MS . . . . . . . . . . . . . . . . 18-76 BSSLAP_ABORT_SENT . . . . . . . . . 10-5
OUT_INTRA_BSS_HO_SUC . . . . . . . 18-77 BSSLAP_MS_POS_CMD . . . . . . . . . 10-6
OUTGOING_HO_VOLUME . . . . . . . 18-78 BSSLAP_MS_POS_RESP . . . . . . . . 10-7
paging performance. . . . . . . . . . . 18-5 BSSLAP_REJ . . . . . . . . . . . . . . 10-8
PAGING_COMPRESSION_RATE. . . . . 18-79 BSSLAP_RESET . . . . . . . . . . . . . 10-9
PAGING_OVERFLOW_RATE. . . . . . . 18-80 BSSLAP_TA_REQ . . . . . . . . . . . . 10-10
PAGING_RESPONSE . . . . . . . . . . 18-81 BSSLAP_TA_RESP. . . . . . . . . . . . 10-11
PAGING_SUCCESS_RATE . . . . . . . . 18-82 BSSLAP_TOA_REQ . . . . . . . . . . . 10-12
PERCENTAGE_INTER_BSS_HO . . . . . 18-83 BSSMAP_CONLESS_INFO_RCV . . . . 10-13
IX-8 68P02901W56-T
Jan 2010
Index
network interface statistics (contd.) network interface statistics (contd.)

BSSMAP_CONLESS_INFO_SENT . . . . 10-14 LMTP_SIF_SIO_TX . . . . . . . . . . . 9-23
BSSMAP_PERF_LOC_ABORT_MSGS . . 10-15 LMTP_SL_ACK . . . . . . . . . . . . . 9-24
BSSMAP_PERF_LOC_REQ_MSGS . . . . 10-16 LMTP_SL_ALIGNMENT . . . . . . . . . 9-25
BSSMAP_PERF_LOC_RESP_MSGS . . . 10-17 LMTP_SL_CONGESTION . . . . . . . . 9-26
BSSMAPLE_CONLESS_INFO_RCV . . . 10-18 LMTP_SL_ERROR_RATE . . . . . . . . 9-27
BSSMAPLE_CONLESS_INFO_SENT . . 10-19 LMTP_SL_FAIL . . . . . . . . . . . . . 9-28
BSSMAPLE_PERF_LOC_ABORT_MSGS . . 10-20 LMTP_SL_FIBR . . . . . . . . . . . . . 9-29
BSSMAPLE_PERF_LOC_REQ_MSGS . . 10-21 LMTP_START_RPO . . . . . . . . . . . 9-30
BSSMAPLE_PERF_LOC_RESP_MSGS . . 10-22 LMTP_STOP_RPO . . . . . . . . . . . . 9-31
L_ROUTING_SYNTAX . . . . . . . . . . 14-3 LMTP_SU_ERROR . . . . . . . . . . . 9-32
L_ROUTING_UNKNOWN . . . . . . . . 14-4 LMTP_UNAVAILABLE. . . . . . . . . . 9-33
L_SCCP_MSGS . . . . . . . . . . . . . 14-5 NO_PDTCH_AVAIL . . . . . . . . . . . 13-158
L_SCCP_MSGS_RX . . . . . . . . . . . 14-6 NO_PDTCH_AVAIL_TIME . . . . . . . . 13-159
L_SCCP_MSGS_TX . . . . . . . . . . . 14-7 Normal distribution statistics . . . . . . . . 1-9
L_SIF_SIO_RX_OPC . . . . . . . . . . . 14-8 Bins . . . . . . . . . . . . . . . . . . . . 1-9
L_SIF_SIO_TX_OPC . . . . . . . . . . . 14-9 Histogram. . . . . . . . . . . . . . . . . 1-9
L_SIF_SIO_TYPE . . . . . . . . . . . . 14-10 Interval expiry . . . . . . . . . . . . . . 1-9
LMTP_CHANGEBACK. . . . . . . . . . . 9-6 Mean value . . . . . . . . . . . . . . . . 1-9
LMTP_CHANGEOVER. . . . . . . . . . . 9-7 NUM_CELL_RESEL_CELL . . . . . . . . 4-124
LMTP_CONGESTION_LOST_MSU . . . . 9-4 NUM_CELL_RESEL_CELL_PCCN . . . . . 4-125
LMTP_LINK_INS . . . . . . . . . . . . . 9-9 NUM_CELL_RESEL_CELL_SUCC . . . . . 4-126
LMTP_LINKFAIL . . . . . . . . . . . . 9-10 NUM_CELL_RESEL_NEI . . . . . . . . . 5-10
LMTP_LOCAL_BUSY . . . . . . . . . . 9-11 NUM_CELL_RESEL_NEI_PCCN. . . . . . 5-11
LMTP_LOCAL_MGT . . . . . . . . . . . 9-12 NUM_CELL_RESEL_NEI_SUCC. . . . . . 5-12
LMTP_LOCAL_SL_CONGESTION . . . . . 9-8 NUM_EMERG_ACCESS . . . . . . . . . . 4-127
LMTP_MGT_INHIBIT . . . . . . . . . . 9-13 NUM_EMERG_REJECTED . . . . . . . . 4-128
LMTP_MGT_UNINHIBIT . . . . . . . . 9-14 NUM_EMERG_TCH_KILL . . . . . . . . . 4-129
LMTP_MSU_DISCARDED . . . . . . . . . 9-5 NUM_EMERG_TERM_SDCCH . . . . . . 4-130
LMTP_MSU_RX . . . . . . . . . . . . . 9-15 NUM_HO_3G_ATTEMPTS . . . . . . . . . 4-131
LMTP_MSU_TX . . . . . . . . . . . . . 9-16 NUM_HO_FROM_3G_ATTEMPTS . . . . . 4-132
LMTP_NEG_ACKS . . . . . . . . . . . 9-17 NUM_HO_FROM_3G_SUCCESS . . . . . 4-133
LMTP_RE_TX . . . . . . . . . . . . . . 9-18 NUM_HO_TO_3G_RES_ALLOC_SUCC . . 4-134
LMTP_REMOTE_MGT. . . . . . . . . . 9-19 NUM_HO_TO_3G_SUCCESS . . . . . . 4-135,
LMTP_REMOTE_PROC . . . . . . . . . 9-20 18-67 to 18-68
LMTP_RESTORATION . . . . . . . . . 9-21 NUM_MULTIRAT_MS_ORIG_CALL . . . . 4-136
LMTP_SIF_SIO_RX . . . . . . . . . . . 9-22 NUM_OF_SMS_INIT . . . . . . . . . . . 4-137
OK_ACC_PROC . . . . . . . . . . . 4-139, 10-2 OUT_INTER_BSS_HO_LOSTMS . . . . . . 4-142

OK_ACC_PROC_SUC_RACH. . . . . . . . 4-141 OUT_INTER_BSS_HO_RETURN. . . . . . 4-142
OUT_3G_HO_FAIL_RATE . . . . . . . . . 17-93 OUT_INTER_BSS_HO_SUC . . . . . . . . 4-142
OUT_3G_HO_REQ_SUCC_RATE . . . . . . 17-94 OUT_INTER_BSS_HO_SUC-
OUT_3G_HO_SUCC_RATE . . . . . . . . 17-95 CESS_RATE . . . . . . . . . . . . . . . . 18-71
OUT_HO_CAUSE_ATMPT . . . . . . . . . 4-200 OUT_INTER_BSS_REQ_TO_MSC . . . . . 4-142
OUT_HO_NC_CAUSE_ATMPT . . . . . . . 5-13 OUT_IN-
OUT_HO_NC_SUC . . . . . . . . . . . . 5-15 TER_CELL_FAIL_RATE_LOST_MS . . . . 18-72
OUT_INTER_BSS_EQUIP_FAIL . . . . . . 4-142 OUT_INTER_CELL_HO_FAIL_RATE_RECOV-
OUT_INTER_BSS_HO . . . . . . . . . . . 4-142 ERED . . . . . . . . . . . . . . . . . . . 18-73
OUT_INTER_BSS_HO_ATMPT. . . . . . . 4-142 OUT_INTER_CELL_HO_SUC-
OUT_INTER_BSS_HO_CLEARED . . . . . 4-142 CESS_RATE . . . . . . . . . . . . . . . . 18-74
OUT_INTER_BSS_HO_FAIL . . . . . . . . 4-142 OUT_INTRA_BSS_EQUIP_FAIL . . . . . . 4-144
OUT_INTER_BSS_HO_FAIL_LOST_MS . . 18-69 OUT_INTRA_BSS_HO . . . . . . . . . . . 4-144
OUT_INTER_BSS_HO_FAIL_RECOV- OUT_INTRA_BSS_HO_ATMPT. . . . . . . 4-144
ERED . . . . . . . . . . . . . . . . . . . 18-70 OUT_INTRA_BSS_HO_CLEARED . . . . . 4-144
68P02901W56-T IX-9
Jan 2010
Index
OUT_INTRA_BSS_HO_FAIL_LOST_MS . . 18-75 OUT_INTRA_BSS_HO_REQ . . . . . . . . 4-144

OUT_INTRA_BSS_HO_FAIL_RECOV- OUT_INTRA_BSS_HO_RETURN. . . . . . 4-144
ERED_MS . . . . . . . . . . . . . . . . . 18-76 OUT_INTRA_BSS_HO_SUC . . . . 4-144, 18-77
OUT_INTRA_BSS_HO_LOSTMS . . . . . . 4-144 OUTER_TO_INNER_ZONE . . . 4-229 to 4-230
OUT_INTRA_BSS_HO_PRI_BLK . . . . . . 4-144 OUTGOING_HO_VOLUME . . . . . . . . 18-78
PACCH_PAGE_REQS . . . . . . . . . . 13-160 PDU_DISCARD_FR . . . . . . . . . . . 13-161

PACKET_SYSINFO_REQ . . . . . . . . . 4-146 PDU_DISCARD_LLC . . . . . . . . . . 13-162
PACKET_SYSINFO_RESP . . . . . . . . . 4-147 PERCENTAGE_INTER_BSS_HO . . . . . . 18-83
PAGE_REQ_FROM_MSC . . . . . . . . . 4-148 PERCENTAGE_INTRA_BSS_HO . . . . . . 18-84
PAGE_REQ_FROM_MSC_FAIL . . . . . . 3-14 PFC_ADMISSION . . . . . . . . . . . . . 4-153
PAGE_REQ_FROM_SMLC_FAIL . . . . . . 14-11 PFC_DOWNGRADE_FAILURE . . . . . . . 4-157
PAGE_RESPONSE. . . . . . . . . . . . . 4-139 PFC_DOWNGRADE_SUCCESS . . . . . . 4-159
PAGES_PER_C . . . . . . . . . . . . . . 16-12 PFC_PREEMPTIONS . . . . . . . . . . . 4-165
PAGES_PER_SECOND . . . . . . . . . . 16-13 PFC_REJ_DGRD_PRMPT_CELL . . . . . . 4-168
paging performance. . . . . . . . . . . . 18-5 PFC_REJ_DGRD_PRMPT_PRP . . . . . . . . 7-8
PAGING_COMPRESSION_RATE. . . . . . 18-79 PFC_REJECT_CAUSES . . . . . . . . . . 4-170
PAGING_OVERFLOW_RATE. . . . . . . . 18-80 PFC_REJECTION . . . . . . . . . . . . . 4-173
PAGING_RATE . . . . . . . . . . . . . . 16-14 PFC_UPGRADE . . . . . . . . . . . . . . 4-178
PAGING_RESPONSE . . . . . . . . . . . 18-81 phantom RACHs . . . . . . . . . . . . . 20-7
PAGING_SUCCESS_RATE . . . . . . . . . 18-82 raw statistics affected. . . . . . . . . . 20-9
PATH_BALANCE . . . . . . . . . . . . . 6-28 POWERBDGT . . . . . . . . . . . . . . . 4-200
PCH_AGCH_Q_LENGTH . . . . . . . . . 4-151 PPCH_Q_PAGE_DISCARD
PCH_Q_PAGE_DISCARD PPCH_Q_PAGE_DISACRD . . . . . . . . 4-180
PCH_Q_PAGE_DISACRD . . . . . . . . 4-152 PREEMPT_CAP . . . . . . . . . . . . . . 4-181
PCU statistics . . . . . . . . . . . . . . . 13-1 PRP_LOAD . . . . . . . . . . . . . . . 13-164
Accessibility. . . . . . . . . . . . . . . 13-3 PRP_PD_DEMAND . . . . . . . . . . . . 7-13
GBL . . . . . . . . . . . . . . . . . . . 13-2 PS_PAGE_REQS . . . . . . . . . . . . . 13-166
Throughput . . . . . . . . . . . . . . . 13-4
Utilization. . . . . . . . . . . . . . . . 13-8
Questions and answers . . . . . . . . . . 20-10
radio performance reports . . . . . . . . 18-5 Raw statistics . . . . . . . . . . . . . . . . 1-2

CALL_SETUP_RF_ASSIGN- RBER . . . . . . . . . . . . . . . . . . . 6-30
MENT_FAIL_RATE_LOST_MS . . . . . . 18-13 RF_ASSIGN_FAIL_RATE_LOST_MS . . . . 18-88
CALL_SETUP_RF_ASSIGN- RF_ASSIGN_FAIL_RATE_RECOV-
MENT_FAIL_RATE_RECOV- ERED . . . . . . . . . . . . . . . . . . . 18-89
ERED_MS . . . . . . . . . . . . . . . . 18-15 RF_ASSIGNMENT_SUCCESS_RATE . . . 18-90
CALL_SETUP_RF_ASSIGNMENT_SUC- RF_LOSS_RATE . . . . . . . . . . . . . . 17-96
CESS_RATE . . . . . . . . . . . . . . . 18-17 RF_LOSSES_SD . . . . . . . . . . . . . . 4-183
INTRA_BSS_HO_ATTEMPT_RATE. . . . 18-84 RF_LOSSES_TCH . . . . . . . . . . . . . 4-185
INTRA_CELL_HO_ATTEMPT_RATE . . . 18-85 RF_LOSSES_TCH_HR . . . . . . . 4-187, 4-189
PERCENTAGE_INTER_BSS_HO . . . . . 18-83 ROC . . . . . . . . . . . . . . . . . . . . 6-32
RF_ASSIGNMENT_SUCCESS_RATE . . 18-90 ROUTING_SYNTAX . . . . . . . . . . . . 3-15
RANKING_FORMULA . . . . . . . . . . . 18-86 ROUTING_UNKNOWN . . . . . . . . . . 3-16
IX-10 68P02901W56-T
Jan 2010
Index
RSL RSL_LCF_CONGESTION . . . . . . . . . 7-14

Congestion Control . . . . . . . . . . . . 3-3
link scenarios . . . . . . . . . . . . . . 19-69
SABM_TX . . . . . . . . . . . . . . . . . 12-23 SECOND_ASSIGN_SUC . . . . . . . . . . 4-194

SCCP_MSGS . . . . . . . . . . . . . . . 3-17 Setting a statistic interval . . . . . . . . . 2-38
SCCP_MSGS_RX . . . . . . . . . . . . . 3-18 Setting a threshold . . . . . . . . . . . . 2-42
SCCP_MSGS_TX . . . . . . . . . . . . . 3-19 counter statistics . . . . . . . . . . . . 2-45
SDCCH congestion . . . . . . . . . . . . 18-5 Setting statistic properties . . . . . . . . 2-42
SDCCH_ACCESSES . . . . . . . . . . . . 18-91 Setting a threshold . . . . . . . . . . . 2-42
SDCCH_BLOCKING_RATE . . . . 17-98, 18-92 short message service
SDCCH_CONGESTION . . . . . . . . . . 4-191 mobile originated . . . . . . . . . . . . 19-51
SDCCH_CONGESTION_TIME . . . . . . . 18-93 mobile terminated . . . . . . . . . . . 19-52
SDCCH_HANDOVER . . . . . . . . . . . 4-193 SIB_RX . . . . . . . . . . . . . . . . . . 11-37
SDCCH_MEAN_HOLDING_TIME . . . . . 17-99 SIB_TX . . . . . . . . . . . . . . . . . . 11-38
SDCCH_RF_LOSS_RATE . . . . . . . . 17-100 SIF_SIO_RX_OPC . . . . . . . . . . . . . 3-20
SDCCH_TRAFFIC_CARRIED . . . 17-101, 18-94 SIF_SIO_TX_OPC . . . . . . . . . . . . . 3-21
SDCCH_USAGE_ACCESS_FAILURE. . . . 18-96 SIF_SIO_TYPE . . . . . . . . . . . . . . 3-22
SDCCH_USAGE_CALL_REESTAB- SIGNALLING_HANDOVER . . . . . . . . 4-196
LISH . . . . . . . . . . . . . . . . . . . 18-98 SL_CONGESTION. . . . . . . . . . . . . 11-39
SDCCH_USAGE_EMER- SL_STOP_CONGESTION . . . . . . . . . 11-40
GENCY_CALL . . . . . . . . . . . . . . 18-100 SMS
SDCCH_USAGE_IMSI_DETACH. . . . . 18-102 ratio per call . . . . . . . . . . . . . . 16-15
SDCCH_USAGE_LOCATION_UP- SMS_INIT_ON_TCH . . . . . . . . . . . . 4-198
DATE . . . . . . . . . . . . . . . . . . 18-103 SMS_NO_BCAST_MSG . . . . . . . . . . 4-199
SDCCH_USAGE_MS_ORIGI- SMS_TO_C_RATIO . . . . . . . . . . . . 16-15
NATED_CALL . . . . . . . . . . . . . . 18-105 SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGES-
SDCCH_USAGE_MS_ORIGI- TION_RELIEF . . . . . . . . . . . . . . 18-115
NATED_SMS . . . . . . . . . . . . . . 18-107 SPILL_OVER_FACTOR_DI-
SDCCH_USAGE_PAGING_RE- RECTED_RETRY . . . . . . . . . . . . 18-116
SPONSE . . . . . . . . . . . . . . . . 18-111 SPILL_OVER_FACTOR_MULTIBAND . . 18-117
SDCCH_USAGE_SMS . . . . . . . . . . 18-113 stat_interval command . . . . . . . 2-38 to 2-39
SDCCH_USAGE_SMS_ORIGI- stat_mode command . . . . . . . . . . . . 2-2
NATED_SS . . . . . . . . . . . . . . . 18-109 SUCCESS_IMMED_ASSIGN_PROC . . . 17-103
SECOND_ASSIGN_ATMPT . . . . . . . . 4-192 SUCCESS_INTERNAL_HO . . . . . . . 17-104
TBF_DL_ASGN_PACCH . . . . . . . . . 13-167 TCH_CONGESTION_HR . . . . . . . . . 4-206

TBF_DROP_RATE_ON_PACCH_LOST . . 17-105 TCH_CONGESTION_TIME . . . . . . . 18-120
TBF_REL_PACCH_LOST. . . . . . . . . 13-168 TCH_CONGESTION_TIME_IN-
TBF_SESSIONS . . . . . . . . . . . . . 13-169 NER_ZONE . . . . . . . . . . . . . . . 18-121
TCH congestion . . . . . . . . . . . . . . 18-6 TCH_CONGES-
TCH_ACCESSES . . . . . . . . . . . . 18-118 TION_TIME_OUTER_ZONE . . . . . . . 18-123
TCH_ASSIGN_TO_INNER_ZONE . . . . . 4-229 TCH_DELAY. . . . . . . . . . . . . . . . 4-207
to 4-230 TCH_MEAN_ARRIVAL_RATE . . . . . . 17-111
TCH_BLOCKING_RATE . . . . . . . . . 17-106 TCH_MEAN_HOLDING_TIME. . . . . . 17-112
TCH_BLOCKING_RATE_INNER_Z . . . 17-107 TCH_PREEMPT_ATMPT. . . . . . . . . . 4-208
TCH_BLOCKING_RATE_OUTER_Z . . . 17-108 TCH_PREEMPT_FAIL_NO_CAND . . . . . 4-209
TCH_CONG_INNER_ZONE . . . . . . . . 4-202 TCH_PREEMPT_FAIL_TIMEOUT . . . . . 4-210
TCH_CONG_INNER_ZONE_HR . . . . . . 4-203 TCH_PREEMPT_RQD . . . . . . . . . . . 4-211
TCH_CONGESTION. . . . . . . . . . . . 4-204 TCH_Q_LENGTH . . . . . . . . . . . . . 4-213
68P02901W56-T IX-11
Jan 2010
Index
TCH_Q_REMOVED . . . . . . . . . . . . 4-214 Throughput statistics . . . . . . . . . . . 19-87

TCH_RF_LOSS_RATE . . . . . . 17-114, 18-124 TIMER_EXP_PAP_CONV . . . . . . . . . 4-219
TCH_TRAFFIC_CARRIED . . . . 17-116, 18-126 TOTAL_CS . . . . . . . . . . . . . . . . 4-220
TCH_USAGE . . . . . . . . . . . . . . . 4-215 TOTAL_CS_KEY . . . . . . . . . . . . . 17-120
TCH_USAGE_EXT_RANGE . . . . . . . . 4-217 TOTAL_GCI_FOR_PD_DEMAND. . . . . . 7-15
TCH_USAGE_INNER_ZONE . . . . . . . 4-218
U_BER . . . . . . . . . . . . . . . . . . 6-34 UL_LLC_TRAFFIC_VOLUME_INDICA-

UL_BANDWIDTH_INDICATOR_EG- TOR . . . . . . . . . . . . . . . . . . . 17-124
PRS . . . . . . . . . . . . . . . . . . . 18-130 UL_PDTCH_Q_LENGTH. . . . . . . . . 13-205
UL_BANDWIDTH_INDICA- UL_PDTCH_SEIZURE . . . . . . . . . . 13-206
TOR_GPRS . . . . . . . . . . . . . . . 18-132 UL_RADIO_BLKS_8PSK_1_TS . . . . . . 13-207
UL_BLER_CS1 . . . . . . . . . . . . . 13-170 UL_RADIO_BLKS_8PSK_2_TS . . . . . . 13-209
UL_BLER_CS2 . . . . . . . . . . . . . 13-172 UL_RADIO_BLKS_GMSK_1_TS . . . . . 13-215
UL_BLER_CS3 . . . . . . . . . . . . . 13-174 UL_RADIO_BLKS_GMSK_2_TS . . . . . 13-217
UL_BLER_CS4 . . . . . . . . . . . . . 13-175 UL_RLC_ACK_NEW_BLKS . . . . . . . 13-223
UL_BLER_MCS1 . . . . . . . . . . . . 13-177 UL_RLC_RETX_BLKS . . . . . . . . . . 13-225
UL_BLER_MCS2 . . . . . . . . . . . . 13-179 UL_RLC_UNACK_NEW_BLKS . . . . . . 13-227
UL_BLER_MCS3 . . . . . . . . . . . . 13-181 UL_TBF_TIME_8PSK_1_TS . . . . . . . 13-230
UL_BLER_MCS4 . . . . . . . . . . . . 13-183 UL_TBF_TIME_8PSK_2_TS . . . . . . . 13-231
UL_BLER_MCS5 . . . . . . . . . . . . 13-185 UL_TBF_TIME_GMSK_1_TS . . . . . . . 13-234
UL_BLER_MCS6 . . . . . . . . . . . . 13-187 UL_TBF_TIME_GMSK_2_TS . . . . . . . 13-235
UL_BLER_MCS7 . . . . . . . . . . . . 13-189 UNSUCCESS_INTER-
UL_BLER_MCS8 . . . . . . . . . . . . 13-191 NAL_HO_NOREEST . . . . . . . . . . . 17-142
UL_BLER_MCS9 . . . . . . . . . . . . 13-193 UNSUCCESS_INTER-
UL_BUSY_PDTCH . . . . . . . . . . . . 13-195 NAL_HO_REEST . . . . . . . . . . . . 17-143
UL_EGPRS_BACKHAUL_DEMAND . . . . 6-36 UPINTERF . . . . . . . . . . . . . . . . 4-200
UL_EGPRS_BACKHAUL_USED . . . . . . 6-37 UPLEVEL . . . . . . . . . . . . . . . . . 4-200
UL_LLC_DATA_VOLUME . . . . . . . . . 4-225 UPLINK_PATH_LOSS . . . . . . . . . . . 6-38
UL_LLC_FRAMES . . . . . . . . . . . . 13-200 UPQUAL . . . . . . . . . . . . . . . . . 4-200
Weighted distribution statistics . . . . . . 1-10 Weighted distribution statistics (contd.)

Bins . . . . . . . . . . . . . . . . . . . 1-10 Mean value . . . . . . . . . . . . . . . 1-10
Histogram. . . . . . . . . . . . . . . . 1-10 Wraparound to next day. . . . . . . . . 1-10
Interval expiry . . . . . . . . . . . . . 1-10
ZONE_CHANGE_ATMPT . . . . . . . . . 4-229 ZONE_CHANGE_SUC . . . . . . . . . . . 4-230
IX-12 68P02901W56-T
Jan 2010

GSM Stats Application

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

GSM Stats Application

Uploaded by

Copyright:

Available Formats

GSM Statistics Application

© 2003 - 2009 Motorola, Inc. All Rights Reserved.

Maintenance information: GSM Statistics Application

Chapter 1: Introduction to statistics

Chapter 2: Statistical operations

Chapter 3: BSS statistics

Chapter 4: Cell statistics

Chapter 5: Neighbor statistics

Chapter 6: Carrier and timeslot statistics

Chapter 7: GPROC and DPROC statistics

Chapter 8: Ethernet statistics

Chapter 9: LMTL statistics

Chapter 10: BSS statistics for Location Services support

Chapter 11: MTL statistics

Chapter 12: CBL, GSL, OML, RSL, and XBL statistics

Chapter 13: PCU statistics

Chapter 14: BSS-SMLC statistics

Chapter 15: Web MMI statistics

Chapter 16: Call model statistics

Chapter 17: Key statistics

Chapter 18: Network health reports

Chapter 19: Ladder diagrams

Chapter 20: Impacts on statistics

Frequently Asked Questions (FAQs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-10

Chapter 21: Statistics history

Figure 1-1: Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . 1-10

Table 2-1: Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45

Table 4-43: NUM_OF_SMS_INIT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137

Table 7-1: PFC_REJ_DGRD_PRMPT_PRP bins . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Table 13-54: Bin descriptions for PDU_DISCARD_LLC . . . . . . . . . . . . . . . . . . . . . . 13-162

Maintenance information: GSM Statistics

What is covered in this manual?

The following sections show the revision status of this document.

The following table describes the changes made to this document:

Version Date of issue Description

Resolution of Service Requests

The following Service Requests are resolved in this document:

Document banner definitions

Characters typed in at the keyboard are shown like this sentence.

Messages, prompts, file listings, directories, utilities, and environmental

Special key sequences

Special key sequences are represented as follows:

Motorola appreciates feedback from the users of our documents.

Ordering documents and CD-ROMs

Questions and comments

• The document title, part number, and revision character

• The page number with the error

• A detailed description of the error and if possible the proposed solution

The following topics are described:

• Types of raw statistics on page 1-6.

• Statistic usages on page 1-13.

• Ladder diagrams on page 1-18.

• Statistics history on page 1-19.

Introduction to GSM Statistics Manual

Network management and planning

• Installation and commissioning

Processor utilization statistics

Processor utilization statistics show the percentage of GPROC utilization.

• Allow comparisons of similar time periods over a span of time.

• Detect congestion trends and possible performance degradation.

The following are the key statistics groupings:

Network health statistics

The following are the network health report groupings:

• Counter array statistics: