MotorolaStatistics GSR8

MAINTENANCE INFORMATION
GSM STATISTICS APPLICATION

GSM SOFTWARE RELEASE 8
GSR8
FIELD TRIAL - UNDER DEVELOPMENT
68P02901W56-R
DEVELOPMENT
FIELD TRIAL –
68P02901W56-R
GSR8
MAINTENANCE INFORMATION
UNDER
GSM STATISTICS APPLICATION
GSM SOFTWARE RELEASE 8
Maintenance Information: GSM
Statistics Application
© 1994 - 2005 Motorola, Inc. 68P02901W56-R

All Rights Reserved FIELD TRIAL - UNDER DEVELOPMENT 15 Jun 2005
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or other media.
Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs, including the exclusive right to
copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer programs contained in the Motorola products
described in this document may not be copied or reproduced 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, except for the rights that arise by operation of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or disclosed only in
accordance with the terms of the agreement. Software and documentation are copyright 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.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any inaccuracies or omissions
in this document, or from the use of the information obtained herein. Motorola 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 does not assume any liability arising out of the application or use of any product or circuit described herein;
neither does it convey license under its patent rights of others.
Trademarks
Motorola and the Motorola logo are registered trademarks of Motorola Inc.
M-Cell™, Taskfinder™ and intelligence everywhere™ are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
CE Compliance
The CE mark confirms Motorola Ltd’s 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 the CNRC help desk, contact details below:
Email: csc.emea@motorola.com
Tel: +44 (0) 1793 565 444
FIELD TRIAL - UNDER DEVELOPMENT 15 Jun 2005

Table
of
Contents
Contents
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Maintenance Information: GSM Statistics Application

Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Manual amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1: Introduction to statistics

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

Enabling/disabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Displaying statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Setting the statistic interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Displaying the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Displaying the statistic interval start times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Setting statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Displaying statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Chapter 3: BSS statistics

BSS statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
HO_REQ_MSC_PROTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
INTRA_BSS_HO_CAUSE_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
MA_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
MSC_OVLD_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
PAGE_REQ_FROM_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
ROUTING_SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
68P02901W56-R i
15 Jun 2005 FIELD TRIAL - UNDER DEVELOPMENT
Contents
SCCP_MSGS_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
VGCS_TALKER_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
VGCS_VBS_SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
VGCS_VBS_SETUP_ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
VGCS_VBS_SETUP_REFUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Chapter 4: Cell statistics

Cell statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
ACCESS_PER_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
ACCESS_PER_PPCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
ALLOC_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
ALLOC_SDCCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
ALLOC_TCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
ALLOC_TCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
ALLOC_TCH_FAIL_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
ALLOC_TCH_FAIL_VGCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
ALLOC_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
AMR_DECREASE_THRESH_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
AMR_FR_DL_ADAPTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
AMR_FR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
AMR_FR_UL_ADAPTATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
AMR_FR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
AMR_HR_DL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
AMR_HR_DL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
AMR_HR_UL_ADAPTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
AMR_HR_UL_CODEC_MODE_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
AMR_INCREASE_THRESH_ADJUST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
ASSIGNMENT_REDIRECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
AVAILABLE_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
AVAILABLE_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
AVAILABLE_TCH_DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
AVAILABLE_TCH_EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
AVAILABLE_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
AVAILABLE_TCH_PGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
BAD_HO_REFNUM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
BUSY_TCH_CARR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
BUSY_TCH_DCS1800 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
BUSY_TCH_EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
BUSY_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
BUSY_TCH_PGSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
CALL_SP_VERS_DOWNGRADE_MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
CALLS_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
CHAN_REQ_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63
CHAN_REQ_MS_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
CIPHER_MODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65
CLASSMK_UPDATE_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
CLR_CMD_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
ii 68P02901W56-R
Maintenance Information: GSM Statistics Application Contents
CLR_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68
CONGEST_EXIST_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70
CONGEST_STAND_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71
CONN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72
CONN_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74
DL_LLC_DATA_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75
ER_INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77
ER_INTRA_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
FLOW_CONTROL_BARRED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-80
HO_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
HO_REQ_MSC_FAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
HO_REQ_ACK_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85
IDLE_TCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
IN_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
IN_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95
INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
MA_REQ_FROM_MSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105
MS_ACCESS_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107
MS_TCH_USAGE_BY_TYPE_PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108
MT_LCS_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
NUM_CELL_RESEL_CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111
NUM_CELL_RESEL_CELL_PCCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112
NUM_CELL_RESEL_CELL_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113
NUM_EMERG_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-114
NUM_EMERG_REJECTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-115
NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-116
NUM_EMERG_TERM_SDCCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-117
NUM_HO_3G_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
NUM_HO_FROM_3G_ATTEMPTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-119
NUM_HO_FROM_3G_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-120
NUM_HO_TO_3G_RES_ALLOC_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-121
NUM_HO_TO_3G_SUCCESS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122
NUM_MULTIRAT_MS_ORIG_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123
NUM_T3121_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-124
OK_ACC_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-125
OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-127
OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-128
OUT_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-130
OUT_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-132
PACKET_SYSINFO_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
PACKET_SYSINFO_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-136
PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-137
68P02901W56-R iii
Contents
PAGING_REQUESTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-138
PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
PFC_ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-141
PFC_ADMISSION_OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143
PFC_DOWNGRADE_FAILURE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
PFC_DOWNGRADE_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
PFC_PREEMPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-148
PFC_REJ_DGRD_PRMPT_CELL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-150
PFC_REJECT_CAUSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
PFC_REJECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-155
PFC_REJECTION_OTHER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157
PFC_UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158
PPCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-160
PREEMPT_CAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-161
QUEUE_PREEMPT_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-162
RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-163
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164
SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-166
SDCCH_HANDOVERs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167
SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-169
SECOND_ASSIGN_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
SMS_INIT_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-171
SMS_INIT_ON_SDCCH_HO_IN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-172
SMS_INIT_ON_SDCCH_HO_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-173
SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-174
SMS_NO_BCAST_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-175
TCH_CONG_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-176
TCH_CONG_INNER_ZONE_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-177
TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-178
TCH_CONGESTION_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-179
TCH_DELAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180
TCH_PREEMPT_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181
TCH_PREEMPT_FAIL_NO_CAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183
TCH_PREEMPT_FAIL_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184
TCH_PREEMPT_RQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185
TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-186
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187
TCH_USAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-188
TCH_USAGE_EXT_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-190
TCH_USAGE_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-191
TIMER_EXP_PAP_CONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
TOTAL_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194
UL_LLC_DATA_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-195
VGCS_FR_TCH_BUSY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-197
VGCS_HR_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-198
VGCS_VBS_ASSIGN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-199
VGCS_VBS_ASSIGN_REQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-200
VGCS_VBS_ASSIGN_RESULT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-201
ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-202
ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-203
Chapter 5: Neighbour statistics

Introduction to neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
iv 68P02901W56-R
IN_INTRA_BSS_NC_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
IN_INTRA_BSS_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
NUM_CELL_RESEL_NEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
NUM_CELL_RESEL_NEI_PCCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
NUM_CELL_RESEL_NEI_SUCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
OUT_HO_NC_CAUSE_ATMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
OUT_HO_NC_SUC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Chapter 6: Carrier and timeslot statistics

Carrier and timeslot statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
ALLOC_SDCCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
ALLOC_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
BUSY_TCH_CARR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
BUSY_TCH_CARR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
CHAN_DL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
CHAN_UL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
DL_EGPRS_BACKHAUL_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
DL_EGPRS_BACKHAUL_USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
EGPRS_64K_CHANNEL_WIDTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
FER_AMR_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
FER_AMR_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
FER_GSM_FR_EFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
FER_GSM_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
RBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
RF_LOSSES_TCH_HR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35
ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36
U_BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37
UL_EGPRS_BACKHAUL_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
UL_EGPRS_BACKHAUL_USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40
UPLINK_PATH_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Chapter 7: GPROC and DPROC statistics

CPU_USAGE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
GCI_FOR_16KPD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
PFC_REJ_DGRD_PRMPT_PRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
PRP_PD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
TOTAL_GCI_FOR_PD_DEMAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Chapter 8: LMTL statistics

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

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

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

X.25/LAPD Level: X.25 and LAPD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
ATER_CHANNEL_REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
ATER_CHANNEL_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
ATER_PREEMPT_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
ATER_PREEMPT_ATMPT_SWOVER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
ATER_PREEMPT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
ATER_PREEMPT_FAIL_SWOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
ATER_PREEMPT_RQD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
FRMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
I_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
I_FRAMES_TX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
INVALID_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-14
LAPD_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
N2_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
SABM_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
68P02901W56-R vii
Contents
Chapter 12: PCU statistics

PCU statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
AIR_DL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
AIR_DL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
AIR_UL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
AIR_UL_TBF_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
CELL_FLUSH_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
CH_REQ_UNSVCD_PCU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15
CHANNEL_REQS_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
CODING_SCHEME_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20
CONG_REL_DL_SCTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
CS_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
CS12_ON_32K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
CS1234_ON_64K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26
DL_BLER_CS1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
DL_BLER_CS2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
DL_BLER_CS3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-29
DL_BLER_CS4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
DL_BLER_MCS1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
DL_BLER_MCS2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-35
DL_BLER_MCS3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-37
DL_BLER_MCS4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
DL_BLER_MCS5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41
DL_BLER_MCS6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-43
DL_BLER_MCS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-45
DL_BLER_MCS8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-47
DL_BLER_MCS9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-49
DL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
DL_LLC_FRAMES_GB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
DL_LLC_FRAMES_PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
DL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-55
DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-56
DL_RADIO_BLKS_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
DL_RADIO_BLKS_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-60
DL_RADIO_BLKS_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-63
DL_RADIO_BLKS_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-66
DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-69
DL_RLC_DDTR_BLKS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71
DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72
DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
DL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-76
DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-78
DL_TBF_TIME_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-80
DL_TBF_TIME_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-81
DL_TBF_TIME_3_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-82
DL_TBF_TIME_4_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-83
EGPRS_64K_CHANNELS_SWITCHED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-84
EGPRS_64K_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-85
EGPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-86
EGPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-87
G_RACH_UNSVCD_BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-88
GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-89
viii 68P02901W56-R
GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90
GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-92
GBL_PAGING_REQS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-93
GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-94
GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-95
GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-97
GPRS_32K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-98
GPRS_32K_DL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-99
GPRS_32K_UL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-100
GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-101
GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-102
GPRS_AVAIL_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-103
GPRS_CELL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-105
GPRS_CELL_RESELECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-107
GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-108
GPRS_DL_ASGN_PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-109
GPRS_PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-110
GPRS_PPCH_PAGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-111
GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-112
GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-114
IDLE_PDTCH_INTF_BAND0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-116
IMM_ASSGN_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-121
NO_PDTCH_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-123
NO_PDTCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-124
PACCH_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-125
PDU_DISCARD_FR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-126
PDU_DISCARD_LLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-127
PRP_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-129
PS_PAGE_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-131
TBF_DL_ASGN_PACCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-132
TBF_REL_PACCH_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-133
TBF_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-134
UL_BLER_CS1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-135
UL_BLER_CS2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-137
UL_BLER_CS3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-139
UL_BLER_CS4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-140
UL_BLER_MCS1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-142
UL_BLER_MCS2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-144
UL_BLER_MCS3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-146
UL_BLER_MCS4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-148
UL_BLER_MCS5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-150
UL_BLER_MCS6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-152
UL_BLER_MCS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-154
UL_BLER_MCS8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-156
UL_BLER_MCS9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-158
UL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-160
UL_LLC_FRAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-162
UL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-163
UL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-164
UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-165
68P02901W56-R ix
Contents
UL_RADIO_BLKS_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-167
UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-169
UL_RADIO_BLKS_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-171
UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-173
UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-175
UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-177
UL_TBF_TIME_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-179
UL_TBF_TIME_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-180
UL_TBF_TIME_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-181
UL_TBF_TIME_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-182
Chapter 13: BSS-SMLC statistics

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

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

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

Key statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
ATTEMPT_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
CELL_TCH_ALLOCATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
CELL_TCH_ASSIGNMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
DL_LLC_TRAFFIC_VOLUME_INDICATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-12
DL_TBF_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
HANDOVER_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
LLC_ABNORMAL_TBF_RELEASES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17
LLC_BUFFER_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
x 68P02901W56-R
LLC_DISCARDS_ON_CELL_RESELECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
MEAN_ARRIVAL_TIME_BETWEEN_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21
MEAN_TBF_SESSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-22
MEAN_TCH_BUSY_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-23
MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-25
RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-26
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-28
SDCCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-29
SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-30
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31
SUCCESS_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-33
SUCCESS_INTERNAL_HO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-34
TBF_DROP_RATE_ON_PACCH_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-35
TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-36
TCH_BLOCKING_RATE_INNER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-37
TCH_BLOCKING_RATE_OUTER_Z . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
TCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
TCH_MEAN_HOLDING_TIME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-40
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-43
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-45
TOTAL_CALLS_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-47
UL_LLC_TRAFFIC_VOLUME_INDICATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-48
UNSUCCESS_INTERNAL_HO_NOREEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-49
UNSUCCESS_INTERNAL_HO_REEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-50
Chapter 17: Network health reports

Network health statistics subgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
ASSIGNMENT_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . 17-15
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . . 17-17
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
CELL_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-24
CELL_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
DL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30
GPRS_DL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32
GPRS_UL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-33
HO_CAUSE_ADJ_CH_INTERF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34
HO_CAUSE_BAND_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-35
HO_CAUSE_BAND_REASSGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-36
HO_CAUSE_CONGEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-37
68P02901W56-R xi
Contents
HO_CAUSE_DISTANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-38
HO_CAUSE_DLINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39
HO_CAUSE_DLLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-40
HO_CAUSE_DLQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41
HO_CAUSE_PWRBGT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-42
HO_CAUSE_UPINTERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-43
HO_CAUSE_UPLEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-44
HO_CAUSE_UPQUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-45
HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-46
IMMEDIATE_ASSIGN_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-47
IMMEDIATE_ASSIGN_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-48
IMMEDIATE_ASSIGN_MEAN_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-49
IMMEDIATE_ASSIGN_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-50
IN_INTER_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-52
IN_INTER_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
IN_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
INCOMING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-56
INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-58
INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-59
INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-60
INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-62
MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63
MEAN_TIME_BETWEEN_DROPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-64
MEAN_TIME_BETWEEN_HOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65
NUM_HO_FROM_3G_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-66
NUM_HO_TO_3G_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-67
OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-69
OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS. . . . . . . . . . . . . . . . . . . . . . . 17-72
OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-73
OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . 17-74
OUT_INTRA_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-75
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-76
OUT_INTRA_BSS_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-77
OUTGOING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-78
PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-79
PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-80
PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-81
PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-82
PERCENTAGE_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-83
PERCENTAGE_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-84
PERCENTAGE_INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-85
RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-86
RF_ASSIGN_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-88
RF_ASSIGN_FAIL_RATE_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-89
RF_ASSIGNMENT_SUCCESS_RATE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-90
SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-91
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-92
SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-93
xii 68P02901W56-R
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-94
SDCCH_USAGE_ACCESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-96
SDCCH_USAGE_CALL_REESTABLISH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-97
SDCCH_USAGE_EMERGENCY_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-98
SDCCH_USAGE_IMSI_DETACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-99
SDCCH_USAGE_LOCATION_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-100
SDCCH_USAGE_MS_ORIGINATED_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-101
SDCCH_USAGE_MS_ORIGINATED_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-102
SDCCH_USAGE_SMS_ORIGINATED_SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-103
SDCCH_USAGE_PAGING_RESPONSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-104
SDCCH_USAGE_SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-105
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF . . . . . . . . . . . . . . . . . . 17-106
SPILL_OVER_FACTOR_DIRECTED_RETRY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-107
SPILL_OVER_FACTOR_MULTIBAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-108
TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-109
TCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-111
TCH_CONGESTION_TIME_INNER_ZONE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-112
TCH_CONGESTION_TIME_OUTER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-113
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-114
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-116
UL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-118
UPLINK_PDTCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-122
Chapter 18: Ladder diagrams

Ladder diagram constructs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Phone call model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Call procedure milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Call setup and handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Assignment to TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Intra-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
Enhanced 2G/3G handover and reselection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-36
Network assisted cell change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
Call clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-42
Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-46
Congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-48
Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-50
Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
Intra-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53
Inter-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-56
Interband assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
Band Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-63
MTL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-65
GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70
Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-74
Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-80
Voice Group Call Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-88
68P02901W56-R xiii
Contents
Chapter 19: Impacts on statistics

Extended GSM (EGSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Approximate equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Questions and answers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
xiv 68P02901W56-R
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-19
Figure 5-1: Notation used in handover examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Figure 5-2: Internal cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Figure 18-1: Diagram of immediate assignment failure. . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
Figure 18-2: Handover procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Figure 18-3: Connection establishment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Figure 18-4: Connection establishment failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Figure 18-5: Immediate assignment blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Figure 18-6: Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Figure 18-7: Connection establishment (mobile terminated call) successful . . . . . . . . . . . . . . . . 18-15
Figure 18-8: TCH assignment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-16
Figure 18-9: Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Figure 18-10: TCH assignment blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Figure 18-11: TCH assignment fail-recovered to SDCCH . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Figure 18-12: Handover (intra-cell) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-19
Figure 18-13: Handover (intra-cell) blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
Figure 18-14: Handover (intra-cell) fail-recovered to source channel . . . . . . . . . . . . . . . . . . . 18-21
Figure 18-15: Handover (intra-cell) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Figure 18-16: Handover (inter-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
Figure 18-17: Handover (inter-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Figure 18-18: Handover (inter-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
Figure 18-19: Handover (inter-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
Figure 18-20: Inter-BSS handover failure with lost mobile . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Figure 18-21: Inter-BSS handover directed retry external . . . . . . . . . . . . . . . . . . . . . . . . 18-30
Figure 18-22: Handover (intra-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-31
Figure 18-23: Handover (intra-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
Figure 18-24: Handover (intra-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
Figure 18-25: Handover (intra-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34
Figure 18-26: Intra-BSS handover standard directed retry . . . . . . . . . . . . . . . . . . . . . . . . 18-35
Figure 18-27: 2G/3G handover successful. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-37
Figure 18-28: 2G/3G handover failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-38
Figure 18-29: Cell selection agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-39
Figure 18-30: No target cell information before sending a PCCC . . . . . . . . . . . . . . . . . . . . . 18-40
Figure 18-31: New target cell for the MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-40
Figure 18-32: No target cell information before sending a PCCO . . . . . . . . . . . . . . . . . . . . . 18-41
Figure 18-33: Reselection not required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-41
Figure 18-34: BSS initiated call clearing-cipher mode fail . . . . . . . . . . . . . . . . . . . . . . . . 18-42
Figure 18-35: BSS initiated call clearing (RF loss on an SDCCH) . . . . . . . . . . . . . . . . . . . . 18-43
Figure 18-36: BSS initiated call clearing (RF loss on a TCH) . . . . . . . . . . . . . . . . . . . . . . . 18-44
Figure 18-37: BSS initiated call clearing (queueing timeout) . . . . . . . . . . . . . . . . . . . . . . . 18-45
68P02901W56-R xv
List of Figures
Figure 18-38: MS originated short message service (point-to-point) . . . . . . . . . . . . . . . . . . . . 18-46

Figure 18-39: MS terminated short message service (point-to-point) . . . . . . . . . . . . . . . . . . . 18-47
Figure 18-40: Intra-BSS congestion relief handover procedure . . . . . . . . . . . . . . . . . . . . . . 18-49
Figure 18-41: Intra-BSS directed retry procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-51
Figure 18-42: Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
Figure 18-43: Successful intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-53
Figure 18-44: Unsuccessful interband handover with fail-recovered source cell . . . . . . . . . . . . . . 18-54
Figure 18-45: Unsuccessful interband handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-55
Figure 18-46: Successful inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-57
Figure 18-47: Inter-BSS handover unsuccessful with fail-recovered source cell . . . . . . . . . . . . . . 18-58
Figure 18-48: Inter-BSS handover unsuccessful due to invalid frequency supported . . . . . . . . . . . . 18-59
Figure 18-49: Invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-60
Figure 18-50: Intra-BSS handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-61
Figure 18-51: Unsuccessful band reassign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-62
Figure 18-52: RSL link scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-64
Figure 18-53: MTL link scenario (Part I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-66
Figure 18-54: MTL link transition scenarios (Part II) . . . . . . . . . . . . . . . . . . . . . . . . . . 18-67
Figure 18-55: MTL link transition scenarios (Part III) . . . . . . . . . . . . . . . . . . . . . . . . . . 18-68
Figure 18-56: MTL link transition scenarios (Part IV) . . . . . . . . . . . . . . . . . . . . . . . . . . 18-69
Figure 18-57: GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-70
Figure 18-58: GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71
Figure 18-59: CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-71
Figure 18-60: GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-72
Figure 18-61: GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-73
Figure 18-62: CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-74
Figure 18-63: Accessibility CHANNEL_REQ_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-75
Figure 18-64: CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-76
Figure 18-65: GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . 18-77
Figure 18-66: Accessibility and GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-78
Figure 18-67: GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-79
Figure 18-68: AIR_DL_TBF_FAILURES termination . . . . . . . . . . . . . . . . . . . . . . . . . . 18-81
Figure 18-69: AIR_DL_TBF_FAILURES data transfer DDTR mode establishment . . . . . . . . . . . . 18-82
Figure 18-70: AIR_UL_TBF_FAILURE establishment and termination . . . . . . . . . . . . . . . . . . 18-83
Figure 18-71: AIR_UL_TBF_FAILURE data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . 18-84
Figure 18-72: DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-85
Figure 18-73: UL_PDTCH_SEIZURE one-phase access . . . . . . . . . . . . . . . . . . . . . . . . . 18-86
Figure 18-74: UL_PDTCH_SEIZURE two-phase access . . . . . . . . . . . . . . . . . . . . . . . . . 18-87
Figure 18-75: Immediate channel assignment (service subscriber) . . . . . . . . . . . . . . . . . . . . 18-89
Figure 18-76: Immediate channel assignment (dispatcher) . . . . . . . . . . . . . . . . . . . . . . . . 18-90
Figure 18-77: Delayed channel assignment (dispatcher) . . . . . . . . . . . . . . . . . . . . . . . . . 18-91
Figure 18-78: Dedicated channel allocation for calling service subscriber . . . . . . . . . . . . . . . . . 18-92
Figure 18-79: Unsuccessful VGCS setup at the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-93
Figure 18-80: Unsuccessful VGCS/VBS assignment at the BSS . . . . . . . . . . . . . . . . . . . . . 18-94
Figure 18-81: Notification response procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-95
Figure 18-82: Uplink grant inside one BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-96
Figure 18-83: Uplink grant for multiple BSSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-97
Figure 18-84: Unsuccessful uplink allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-98
Figure 18-85: Move talker to dedicated channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-99
Figure 18-86: Uplink release by the talker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-100
Figure 18-87: Uplink reply procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-101
Figure 18-88: VGCS call termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-102
Figure 19-1: Approximate equality procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Figure 19-2: Phantom RACHs illustration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
xvi 68P02901W56-R
List
of
Tables
List of Tables
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 2: Service requests resolved in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 3: CDCNs incorporated in this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Table 2-1: Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Table 3-1: VGCS_VBS_SETUP_REFUSE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Table 4-1: ALLOC_TCH_FAIL_VGCS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Table 4-2: Default bin ranges for BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Table 4-3: Default bin ranges for BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Table 4-4: CALLS_QUEUED bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61
Table 4-5: DL_LLC_DATA_VOLUME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76
Table 4-6: Bin update scenarios for NUM_CELL_RESEL_CELL . . . . . . . . . . . . . . . . . . . . 4-111
Table 4-7: PACKET_SYSINFO_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Table 4-8: PACKET_SYSINFO_RESP bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-136
Table 4-9: PFC_ADMISSION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
Table 4-10: PFC_ADMISSION_OTHER bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143
Table 4-11: PFC_DOWNGRADE_FAILURE bins. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
Table 4-12: PFC_DOWNGRADE_SUCCESS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146
Table 4-13: PFC_PREEMPTIONS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149
Table 4-14: PFC_REJ_DGRD_PRMPT_CELL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-150
Table 4-15: PFC_REJECT_CAUSES bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152
Table 4-16: PFC_REJECTION bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-156
Table 4-17: PFC_REJECTION_OTHER bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157
Table 4-18: PFC_UPGRADE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158
Table 4-19: PREEMPT_CAP bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-161
Table 4-20: QUEUE_PREEMPT_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-162
Table 4-21: SDCCH_HANDOVER bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167
Table 4-22: SMS_INIT_ON_SDCCH_HO_OUT bins . . . . . . . . . . . . . . . . . . . . . . . . . . 4-173
Table 4-23: TCH_PREEMPT_ATMPT bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-181
Table 4-24: TCH_PREEMPT_RQD bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185
Table 4-25: TIMER_EXP_PAP_CONV bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192
Table 4-26: UL_LLC_DATA_VOLUME bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-196
Table 4-27: VGCS_VBS_ASSIGN_FAIL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-199
Table 5-1: Neighbour cell statistics pegged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Table 5-2: Bin update scenarios for NUM_CELL_RESEL_NEI . . . . . . . . . . . . . . . . . . . . . 5-11
Table 6-1: CHAN_REQ_MS_FAIL bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Table 6-2: FER_AMR_FR Quality number conversion. . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Table 6-3: FER_AMR_HR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Table 6-4: FER_GSM_FR_EFR Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . 6-24
Table 6-5: FER_GSM_HR Quality number conversion. . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Table 6-6: Default bin ranges for INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
Table 6-7: Signal level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Table 6-8: RBER Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
68P02901W56-R xvii
List of Tables
Table 6-9: Bin ranges for ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36

Table 7-1: PFC_REJ_DGRD_PRMPT_PRP bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Table 10-1: BUSY CICS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Table 12-1: CODING_SCHEME_CHANGE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Table 12-2: Bin ranges for DL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Table 12-6: Bin ranges for DL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
Table 12-9: Bin range for DL_BLER_MCS4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-39
Table 12-10: Bin ranges for DL_BLER_MCS5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-41
Table 12-15: DL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-51
Table 12-16: Bin ranges for DL_LLC_FRAMES_GB . . . . . . . . . . . . . . . . . . . . . . . . . . 12-53
Table 12-17: Bin ranges for DL_LLC_FRAMES_PCU . . . . . . . . . . . . . . . . . . . . . . . . . 12-54
Table 12-18: Bin ranges for DL_RADIO_BLKS_1_TS . . . . . . . . . . . . . . . . . . . . . . . . . 12-57
Table 12-22: Bin ranges for DL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 12-69
Table 12-23: Bin ranges for DL_RLC_DDTR_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-71
Table 12-24: Bin ranges for DL_RLC_NACK_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-72
Table 12-25: Bin ranges for DL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-74
Table 12-26: Bin ranges for DL_RLC_STALLED_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 12-76
Table 12-27: Bin ranges for DL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . 12-78
Table 12-28: EGPRS_64K_CHANNELS_SWITCHED bins . . . . . . . . . . . . . . . . . . . . . . . 12-84
Table 12-29: GBL_DL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . 12-90
Table 12-30: GBL_UL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . 12-95
Table 12-31: GPRS_32K_CHANNELS_SWITCHED bins . . . . . . . . . . . . . . . . . . . . . . . . 12-98
Table 12-32: Bin ranges for GPRS_CELL_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . 12-106
Table 12-33: GPRS_CHANNELS_SWITCHED bins . . . . . . . . . . . . . . . . . . . . . . . . . . 12-108
Table 12-34: Default bin ranges for GPRS_PRR_BLK_USG . . . . . . . . . . . . . . . . . . . . . . . 12-112
Table 12-35: Default bin ranges for GPRS_RACH_ARRIVAL . . . . . . . . . . . . . . . . . . . . . . 12-114
Table 12-36: IMM_ASSGN_CAUSE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-121
Table 12-37: Bin descriptions for PDU_DISCARD_FR . . . . . . . . . . . . . . . . . . . . . . . . . 12-126
Table 12-38: Bin descriptions for PDU_DISCARD_LLC . . . . . . . . . . . . . . . . . . . . . . . . 12-127
Table 12-39: Mapping between timeslots pending service and PRP load. . . . . . . . . . . . . . . . . . 12-129
Table 12-40: PRP load range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-130
Table 12-41: Bin ranges for UL_BLER_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-135
Table 12-44: Bin ranges for UL_BLER_MCS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-142
xviii 68P02901W56-R
List of Tables

Table 12-53: UL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-160
Table 12-54: Bin ranges for UL_LLC_FRAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-162
Table 12-55: Bin ranges for UL_RADIO_BLKS_8PSK_1_TS . . . . . . . . . . . . . . . . . . . . . . 12-165
Table 12-56: Bin ranges for UL_RADIO_BLKS_8PSK_2_TS . . . . . . . . . . . . . . . . . . . . . . 12-167
Table 12-57: Bin ranges for UL_RADIO_BLKS_GMSK_1_TS . . . . . . . . . . . . . . . . . . . . . 12-169
Table 12-58: Bin ranges for UL_RADIO_BLKS_GMSK_2_TS . . . . . . . . . . . . . . . . . . . . . 12-171
Table 12-59: Bin ranges for UL_RLC_ACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . . . 12-173
Table 12-60: Bin ranges for UL_RLC_RETX_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . 12-175
Table 12-61: Bin ranges for UL_RLC_UNACK_NEW_BLKS . . . . . . . . . . . . . . . . . . . . . . 12-177
Table 14-1: Location of MMI PCU real-time stats descriptions . . . . . . . . . . . . . . . . . . . . . . 14-2
Table 14-2: Location of MMI BSC/BTS real-time stats descriptions . . . . . . . . . . . . . . . . . . . 14-3
Table 16-1: Key statistic descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Table 18-1: Call setup and handover statistics matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . 18-7
Table 19-1: MS access to a traffic channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Table 19-2: Impact due to increased handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Table 19-3: Impact due to congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
68P02901W56-R xix
List of Tables
This page intentionally left blank.
xx 68P02901W56-R
About
This
Manual
Maintenance Information: GSM Statistics

Application
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
What is Covered In This Manual?

The manual provides context information and detailed descriptions of the GSR8 raw, key and network health
statistics sets supported by Motorola GSM cellular equipment.
Detailed information on previous GSR statistical information, for example, GSR6 and GSR7, can be obtained
from the appropriate GSM Statistics Application manual.
The target audience for this manual is GSM network operators and administrators.
68P02901W56-R 1
Issue status of this manual

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following shows the issue status of this manual since it was first released.
Version information
The following table lists the versions of this manual in order of issue:
Table 1 Manual version history
Manual
Date of issue Remarks
issue
O 03 Oct 1994 Original issue - Software release 1.2.2.x
A 30 Dec 1994 Issue A - Software release 1.2.3.x
B 01 Sep 1995 Issue B - Software release 1.3.0.x
C 28 Mar 1997 Issue D - Software release 1.4.1.x
D 28 Mar 1997 Issue D - Software release 1.4.1.x
E 29 Aug 1997 Issue E - GSM Software Release 2
F 27 Apr 1998 Issue F - GSM Software Release 3
G 12 Mar 1999 Issue G - GSM Software Release 4
H 14 Jul 2000 Issue H - GSM Software Release 1.6.1.3
J 31 Jul 2001 Issue J - GSM Software Release 5
K 31 May 2002 Issue K - GSM Software Release 5.1
L 30 Nov 2002 Issue L - GSM Software Release 6
M 02 May 2003 Issue M - GSM Software Release 6 (Horizon II)
P 13 Nov 2003 Issue P - GSM Software Release 7
Q 09 Sep 2004 Issue Q - GSM Software Release 7 Half Rate
R 15 Jun 2005 Issue R - GSM Software release GSR8 - Field Trial
Resolution of service requests
The following Service Requests are now resolved in this manual:
2 68P02901W56-R
Table 2 Service requests resolved in this manual
Service GMR
Remarks
Request Number
259561 N/A Changed statistic “SDCCH_HO” to “SDCCH_HAN-
DOVER”.
1127856 N/A Added HO_REQ_FROM_MSC statistic to all inter-BSS
handover ladder diagrams in Chapter 19.
1129160 N/A Clarified that UL_RADIO_BLKS_xxSK_y_TS statistics are
reported only for successful TBFs.
Incorporation of CDCNs
The following CDCNs are now incorporated in this manual:

Table 3 CDCNs incorporated in this manual
GMR
CDCN Remarks
Number
N/A N/A
68P02901W56-R 3
General information
General information
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
• Motorola disclaims all liability whatsoever, implied or express, 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 customers behalf, to abide by the instructions, system
parameters or recommendations made in this manual
• If this manual was obtained when attending a Motorola training course, it will not be 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 corrections
will be supplied automatically by Motorola in the form of General Manual Revisions (GMRs)
or Customer Documentation Change Notices (CDCNs).
Purpose
Motorola cellular communications manuals are intended to instruct and assist personnel in the operation,
installation and maintenance of the Motorola cellular infrastructure equipment and ancillary devices. It is
recommended that all personnel engaged in such activities be properly trained by Motorola.
Failure to comply with Motorola’s operation, installation and maintenance

instructions may, in exceptional circumstances, lead to serious injury or death.
These manuals are not intended to replace the system and equipment training offered by Motorola, although
they can be used to supplement and enhance the knowledge gained through such training.
Feature references
Most of the manuals in the set, of which this manual is part, are revised to accommodate features released
at Motorola General System Releases (GSRn) or GPRS Support Node (GSNn) releases. In these manuals,
new and amended features are tagged to help users to assess the impact on installed networks. The tags are
the appropriate Motorola Roadmap DataBase (RDB) numbers or Research and Development Prioritization
(RDP) numbers. The tags include index references which are listed in the manual Index. The Index includes
the entry feature which is followed by a list of the RDB or RDP numbers for the released features, with
page references and hot links in electronic copy.
4 68P02901W56-R
General information
The tags have the format: {nnnn} or {nnnnn}

Where: is:
{nnnn} the RDB number
{nnnnn} the RDP number
The tags are positioned in text as follows:
New and amended feature information Tag position in text

Complete new sections of content as follows: In the heading immediately after the heading
content as follows:
• All sections under a main heading
• Main heading {nnnn}
• All paragraphs under subheadings
• Subheading {nnnn}
Single paragraphs of new or amended text. Immediately before the affected paragraph.
New or amended complete Figures and Tables After the Figure or Table number and before
the title text.
Warning, Caution and Notes. Immediately before the affected text in the
Warning, Caution or Note.
General command syntax, operator input (in On a separate line immediately above the
special fonts). affected item or immediately before the
affected item.
Computer output displays (in special fonts). On a separate line immediately above the
affected item or immediately before the
affected item.
For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software
release, refer to the manual System Information: GSM Overview (68P02901W01), or to the manual System
Information: GPRS Overview (68P02903W01), or to the manual System Information: UMTS Overview
(68P02905W21).
Cross references
Throughout this manual, references are made to external publications, chapter numbers and section names.
The references to external publications are shown in italics, chapter and section name cross references
are emphasised blue in text.
This manual is divided into uniquely identified and numbered chapters that, in turn, 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.
68P02901W56-R 5
General information
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the GSM and GPRS
network is encrypted. In order to comply with the export and import requirements of particular countries,
this encryption occurs at different levels as individually standardised, or may not be present at all in some
parts of the network in which it is normally implemented. The manual set, of which this manual is a part,
covers encryption as if fully implemented. Because the rules differ in individual countries, limitations
on the encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
Text conventions
The following conventions are used in the Motorola cellular infrastructure manuals to represent keyboard
input text, screen output text and special key sequences.
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c Press the Control and c keys at the same time.

ALT-f Press the Alt and f keys at the same time.
¦ Press the pipe symbol key.
CR or RETURN Press the Return key.
6 68P02901W56-R
Reporting safety issues
Reporting safety issues

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Whenever a safety issue arises, carry out the following procedure in all instances. Ensure that all site
personnel are familiar with this procedure.
Procedure
Whenever a safety issue arises:
Procedure 1 Safety issue reporting
1 Make the equipment concerned safe, for example by removing power.

2 Make no further attempt to adjust or rectify the equipment.
3 Report the problem directly to the Customer Network Resolution Centre, Swindon +44
(0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written
report by fax, Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax).
4 Collect evidence from the equipment under the guidance of the Customer Network
Resolution Centre.
68P02901W56-R 7
Warnings and cautions

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The following describes how warnings and cautions are used in this manual and in all manuals of this
Motorola manual set.
Warnings
A definition and example follow below:
Definition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical injury, or ill
health. This includes hazards introduced during maintenance, for example, the use of adhesives and solvents,
as well as those inherent in the equipment.
Example and format
Do not look directly into fibre optic cables or data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre
optic cables connected to data in/out connectors.
Failure to comply with warnings
Observe all warnings during all phases of operation, installation and maintenance of the equipment described
in the Motorola manuals. Failure to comply with these warnings, or with specific warnings elsewhere in
the Motorola manuals, or on the equipment itself, violates safety standards of design, manufacture and
intended use of the equipment. Motorola assumes no liability for the customer’s failure to comply with
these requirements.
Cautions
A definition and example follow below:
8 68P02901W56-R
Definition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of equipment
within a system. However, this presents no danger to personnel.
Example and format
Do not use test equipment that is beyond its due calibration date; arrange for
calibration to be carried out.
68P02901W56-R 9
General warnings
General warnings
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following specific warnings during all phases of operation, installation and maintenance of
the equipment described in the Motorola manuals:
• Potentially hazardous voltage.
• Electric shock.
• RF radiation.
• Laser radiation.
• Heavy equipment.
• Parts substitution.
• Battery supplies.
• Lithium batteries,
Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola manuals, violates
safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for
the customer’s failure to comply with these requirements.
Warning labels
Warnings particularly applicable to the equipment are positioned on the equipment. Personnel working with
or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning
labels must not be removed, painted over or obscured in any way.
Specific warnings
Specific warnings used throughout the GSM manual set are shown below, and will be incorporated into
procedures as applicable.
These must be observed by all personnel at all times when working with the equipment, as must any other
warnings given in text, in the illustrations and on the equipment.
10 68P02901W56-R
General warnings
Potentially hazardous voltage
This equipment operates from a potentially hazardous voltage of 230 V a.c. single
phase or 415 V a.c. three phase supply. To achieve isolation of the equipment from
the a.c. supply, the a.c. input isolator must be set to off and locked.
When working with electrical equipment, reference must be made to the Electricity at Work Regulations 1989
(UK), or to the relevant electricity at work legislation for the country in which the equipment is used.
Motorola GSM equipment does not utilise high voltages.
Electric shock
Do not touch the victim with your bare hands until the electric circuit is broken.
Switch off. If this is not possible, protect yourself with dry insulating material and
pull or push the victim clear of the conductor.
ALWAYS send for trained first aid or medical assistance IMMEDIATELY.
In cases of low voltage electric shock (including public supply voltages), serious injuries and even death,
may result. Direct electrical contact can stun a casualty causing breathing, and even the heart, to stop. It
can also cause skin burns at the points of entry and exit of the current.
In the event of an electric shock it may be necessary to carry out artificial respiration. ALWAYS send for
trained first aid or medical assistance IMMEDIATELY.
If the casualty is also suffering from burns, flood the affected area with cold water to cool, until trained
first aid or medical assistance arrives.
68P02901W56-R 11
General warnings
RF radiation
High RF potentials and electromagnetic fields are present in this equipment

when in operation. Ensure that all transmitters are switched off when any
antenna connections have to be changed. Do not key transmitters connected
to unterminated cavities or feeders.
Relevant standards (USA and EC), to which regard should be paid when working with RF equipment are:
• ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to
Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz
• CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10
kHz to 300 GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser
radiation can come from either the data in/out connectors or unterminated fibre
optic cables connected to data in/out connectors.
Lifting equipment
When dismantling heavy assemblies, or removing or replacing equipment, a

competent responsible person must ensure that adequate lifting facilities are
available. Where provided, lifting frames must be used for these operations.
When dismantling heavy assemblies, or removing or replacing equipment, the competent responsible person
must ensure that adequate lifting facilities are available. Where provided, lifting frames must be used for
these operations. When equipment has to be manhandled, reference must be made to the Manual Handling
of Loads Regulations 1992 (UK) or to the relevant manual handling of loads legislation for the country in
which the equipment is used.
12 68P02901W56-R
General warnings
Parts substitution
Do not install substitute parts or perform any unauthorized modification of

equipment, because of the danger of introducing additional hazards. Contact
Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with stand-by battery supplies. Use
only insulated tools.
Lithium batteries
Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

lithium batteries must not be removed or replaced. Any boards containing
defective lithium batteries must be returned to Motorola for repair.
Contact your local Motorola office for how to return defective lithium batteries.
68P02901W56-R 13
General cautions
General cautions
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Observe the following cautions during operation, installation and maintenance of the equipment described
in the Motorola manuals. Failure to comply with these cautions or with specific cautions elsewhere in the
Motorola manuals may result in damage to the equipment. Motorola assumes no liability for the customer’s
failure to comply with these requirements.
Caution labels
Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the
equipment. Caution labels must not be removed, painted over or obscured in any way.
Specific cautions
Cautions particularly applicable to the equipment are positioned within the text of this manual. These must be
observed by all personnel at all times when working with the equipment, as must any other cautions given
in text, on the illustrations and on the equipment.
Fibre optics
Fibre optic cables must not be bent in a radius of less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices. These metal oxide semiconductor

(MOS) devices are susceptible to damage from electrostatic charge. See the
section Devices sensitive to static in the preface of this manual for further
information.
14 68P02901W56-R
Devices sensitive to static
Devices sensitive to static

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of insulation that is
susceptible to damage from electrostatic charge. Such a charge applied to the leads of the device could
cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high insulation packing
material or by use of unearthed soldering irons.
MOS devices are normally despatched from the manufacturers with the leads short circuited together, for
example, by metal foil eyelets, wire strapping, or by inserting the leads into conductive plastic foam. Provided
the leads are short circuited it is safe to handle the device.
Special handling techniques
In the event of one of these devices having to be replaced, observe the following precautions when handling
the replacement:
• Always wear an earth strap which must be connected to the electrostatic point (ESP) on the
equipment.
• Leave the short circuit on the leads until the last moment. It may be necessary to replace the
conductive foam by a piece of wire to enable the device to be fitted.
• Do not wear outer clothing made of nylon or similar man made material. A cotton overall
is preferable.
• If possible work on an earthed metal surface or anti-static mat. Wipe insulated plastic work
surfaces with an anti-static cloth before starting the operation.
• All metal tools should be used and when not in use they should be placed on an earthed surface.
• Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic
damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and
pins, they should be transferred directly from their packing to the equipment (or the other way around) and
never left exposed on the workbench.
68P02901W56-R 15
Motorola manual set
Motorola manual set

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The Motorola manual sets provide the information needed to operate, install and maintain the Motorola
equipment. Manuals for the GSM, GPRS and UMTS products are available on the following media:
• Printed hard copy.
• Electronic, as fully navigable PDF files on:

◦ The Motorola customer support web site at:
(https://mynetworksupport.motorola.com/index.asp).
◦ CD-ROM produced in support of a major system software release.
Each CD-ROM includes all manuals related to a specified main GSM, GPRS or UMTS software release,
together with current versions of appropriate hardware manuals, and has additional navigation facilities. A
snapshot copy of on-line documentation is also included, though it will not be updated in line with subsequent
point releases.
The CD-ROM does not include Release Notes or documentation supporting specialist products such as
MARS or COP.
Ordering manuals and CD-ROMs
Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs.
All orders must be placed with your Motorola Local Office or Representative.
16 68P02901W56-R
Manual amendment
Manual amendment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Changes to a manual that occur after the printing date are incorporated into the manual using either Customer
Documentation Change Notices (CDCNs) or General Manual Revisions (GMRs).
• Small changes are published in CDCNs. These describe the changes rather than replacing large
sections of the manual. They are sent directly to customers and Motorola Local Offices and
are accessible on the Motorola Extranet.
CDCNs are numbered in sequence using the format:
◦ Shortened manual order number
◦ Issue identifier
◦ CDCN number
For example: 01W23-M-CDCN01 would be the first CDCN produced for 68P2901W23–M.
• Major changes are effected by publishing a GMR. GMRs are also produced in order to
incorporate CDCNs when the numbers applying to a particular manual become significant. In
this case, the CDCNs numbers are listed in Table 3 in the issue status section of the manual.
GMRs are issued to correct Motorola manuals as and when required. A GMR has the same
identity as the target manual. Each GMR is identified by a number in a sequence that starts at
01 for each manual at each issue.
GMR availability
GMRs are published as follows:
• Printed hard copy - Complete replacement content or loose leaf pages with amendment list.
◦ Remove and replace pages in this manual, as detailed on the GMR instruction sheet.
• Motorola service web - Updated at the same time as hard copies.
• CD-ROM - Updated periodically as required.
CDCN availability
CDCNs are published as follows:
• PDF distributed electronically - Description of changes, occasionally with replacement

loose leaf pages.
• Motorola service web - Updated at the same time as hard copies.
68P02901W56-R 17
Manual amendment
CDCN instructions
When a CDCN is incorporated in this manual, the record below is completed to record the amendment.
Retain the instruction sheet that accompanies each CDCN and insert it in a suitable place in this manual for
future reference.
18 68P02901W56-R
Manual amendment
CDCN amendment record
Record the manual insertion of CDCNs in this manual in the following table:
CDCN number Incorporated by (signature) Date
68P02901W56-R 19
Manual amendment
20 68P02901W56-R
Chapter
1
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, categorized as a raw statistic type
and used to determine system quality of service. This allows 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-14
68P02901W56-R 1-1
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 monitored network
and system events. The statistics include statistical measurements defined in the GSM Technical Specification
12.04, plus additional Motorola-defined statistics.
To facilitate easy access, the statistics are presented in alphabetical order.
Network management and planning
Network operators may 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.
1-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual
Call statistics
Call processing functions and features generate statistics that show how the system is performing.
Interface statistics
Terrestrial interface activities generate interface statistics that show the activity on and condition of the
interface links. 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.
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 are designed to give an overall indication of the condition of the system and
allow comparisons of similar time periods over a span of time, to help 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 may 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
networks health from the subscribers perspective.
68P02901W56-R 1-3
Introduction to GSM Statistics Manual 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 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 can be done by time (weighted
distributions) or by occurrences (normal distributions). There are 10 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_HOLD-
ING_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 period of 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.
1-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Introduction to GSM Statistics Manual
Maximum value - The highest reported value for the interval.

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 for durations. 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. For a weighted distribution, this value is
incremented by the time difference 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 may 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 (which is used to update a bin) and the temporary value (which 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 may also be specified for individual bins in counter array statistics.
68P02901W56-R 1-5
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 may have a user specified threshold that can generate an alarm when reached. The BSS
only reports 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 will remain 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-R
Maintenance Information: GSM Statistics Application Types of raw statistics
Counter array statistics
Counter array statistics are the total number of times an event occurs and a breakdown of the causes or 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 will remain 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 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_BAND0 statistic is an example of a gauge statistic.
While a gauge statistic may result in the report of a reported negative value, the cumulative value may not be
a negative value. The BSS checks the cumulative before calculating the mean value, and if the result is a
negative number, it will set the mean zero.
Threshold event reporting

A gauge statistic may have a user specified threshold that can generate an alarm when reached. The BSS only
reports one alarm to the OMC for a specific statistic during an interval.
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 then resets them to zero.
68P02901W56-R 1-7
Duration statistics
A duration statistic is a group of values associated with 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 only reports 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 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 day to determine if the interval started before midnight and
ended after midnight. 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).
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 is to zero. The
BSS saves this minimum value then resets it to 0xffffffff.
• The BSS saves the duration mean and maximum values then resets them to zero.
• The BSS resets the period counter and cumulative values to zero.
• The BSS stops and resets any active timers.
1-8 68P02901W56-R
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 10 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 only reports 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 reported values during the interval. The disp_stats command
displays the individual bin values.
The operator may specify the range of values represented by each bin or use the system defaults. The range of
values to be represented by each bin is dependent on the focus of the statistical analysis. Narrow bin ranges
permit closer examination of 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.
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-R 1-9
Histogram
A normal distribution statistic may be illustrated as a histogram. Figure 1-1 shows 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 bins 0 and 1 each contain
two occurrences and bin 7 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
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
1. The mean value is calculated. If the number of reported events is not equal to 0, the mean
value is calculated by dividing the cumulative value of all of the reported events by the
number of reported events.
2. The distribution minimum value is saved and reset to 0xffffffff. If no value was received during
the interval, the duration minimum value is to 0.
3. The distribution mean value and maximum value are saved and reset to 0.
4. The number of reported events and the cumulative value are reset to 0.
5. The values in each of the 10 bins are saved and reset to 0.
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 10 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-R
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 may be assigned to each of the 10 bins in the array is variable. The range of values
may 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 may be assigned to reflect the periods of greatest activity. By narrowing
the bin ranges, the periods of greatest activity may be more closely examined.
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.
Wraparound to next day

A check is automatically made to determine if the interval started before midnight and ended after midnight.
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 of the reported values divided by the number of reported events.
The mean for a weighted distribution statistic is not a duration value and is not calculated
using the bin values.
68P02901W56-R 1-11
Histogram
A weighted distribution statistic may be illustrated as a histogram. Figure 1-2 shows 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.
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
1-12 68P02901W56-R
Interval expiry
Interval expiry is the end of a statistic interval. The following events occur at the interval expiry:
1. Stop any running timers.
2. The mean value is calculated. If the number of reported events is not equal to 0, the mean
value is calculated by dividing the cumulative value of all of the reported events by the
number of reported events.
3. 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.
4. The distribution mean value and maximum value are saved and reset to 0.
5. The number of reported events and the cumulative value are reset to 0.
6. The values in each of the 10 bins are saved and reset to 0.
68P02901W56-R 1-13
Statistic usages Chapter 1: Introduction to statistics
Statistic usages
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Quality of service monitoring
Quality of service is determined by statistics related to service accessibility, integrity, and retainability.
Service accessibility
Statistics associated with the following processes are used to determine service accessibility:
• Mobile registration.
• Mobile 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.
Service retainability
Statistics associated with premature releases are used to determine service retainability.
Service accessibility
Service accessibility is associated with the following call setup and clearing processes:
• Mobile registration and paging.
• Network accessibility.
• Call set up time.
• Call release time.
• Call release delay.
1-14 68P02901W56-R
Maintenance Information: GSM Statistics Application Statistic usages
Mobile registration and paging

Cells are grouped in location areas, and a mobile station (MS) is typically paged only in the cells of one
location area when an incoming call arrives. Therefore, the MS must inform the MSC of the location area in
which the subscriber should be paged. It does so by a location updating procedure.
The best outcome of the procedure is when the network indicates 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 or the procedure running
incorrectly and the network providing an answer that is meaningless.
If the MS satisfactorily updates its location, it can then be paged by the MSC when an incoming call arrives.
The MSC provides the concerned BSC with the ID of the MS to be paged and the list of cells in which the
paging should 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 should be able to access the network. Access denial is divided into three main categories:
• Call blocking.
◦ No signalling channel (SDCCH) is available.
◦ No Traffic Channel (TCH) is available.
• Failure to maintain a signalling channel or traffic channel.

◦ Mobile is moving out of range, for example, into a garage.
◦ Mobile is being switched off.
◦ A hardware failure (MS or BSS).
• Refusal by the MSC for network access.

Failure to gain access to the network is pegged in BSS statistics, but for a more detailed picture
MSC statistics would have to be investigated, as it is an MSC process.
Call set-up time

Call set-up time is affected by post-selection delay and answer signal delay.
• Post-selection delay.
Post-selection delay is the time from dialling the last digit on the fixed network, or pressing the
“send" button on a MS, to receiving the appropriate tone. One possible reason for this delay is
that all resources have been allocated to other calls, which may result in a queueing delay.
• Answer signal delay.

Answer signal delay is 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.
68P02901W56-R 1-15
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 is replaced on the fixed network).
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 queueing. 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.
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
Service retainability is determined by the lack of premature releases. A premature release may be affected by
one of the following factors:
• The base ceases to detect the RF signalling from the mobile.
• The MS fails to reach the target channel on handover.
• The call releases due to equipment failure (MSC, base site, or MS).
• The call is lost due to emergency call preemption.
A subscriber perceives a premature release as a dropped call. Refer to the Ladder diagrams in Chapter 18,
"Ladder diagrams".
1-16 68P02901W56-R
Maintenance Information: GSM Statistics Application Statistic usages
Fault finding
GSM statistics can be used to find certain classes of faults in the cellular system. A set of statistics which may
be used to perform this function is identified in this section.
Monitoring Faults
Hard failures are normally identified via alarm surveillance. However, it is possible for a system component
to deteriorate over time, while still continuing to function. The deterioration may manifest itself in a number
of 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 may be identified using statistics include:
• Damaged antennas.
• Frequency drift.
• Electromechanical problems.
◦ Problems with remote combiners.
◦ Noisy channels.
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 may 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 obtained
for the system that may be used for subsequent expansion. The results may also be used to modify the
original data used in the frequency planning tool.
Network planning
It is possible to determine whether or not 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 needs
to be expanded, (or contracted, if resources are being under utilized).
68P02901W56-R 1-17
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, in order to ensure that all components of the system
are operational.
This activity is currently supported via the Call Trace feature
1-18 68P02901W56-R
Maintenance Information: GSM Statistics Application Ladder diagrams
Ladder diagrams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
About ladder diagrams
The relationship between statistics and call processing elements and functions are graphically represented as
ladder diagrams in Chapter 18, "Ladder diagrams".
Ladder diagrams show the relationships between the MS, BSS, and MSC elements, represented as vertical
lines.
The message flows between the network elements are 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 may also be included as separate vertical lines for additional reference.
Statistics associated with individual messages are located immediately below the directional line. All of the
statistics that may be generated as the result of the process flow will be 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.
68P02901W56-R 1-19
Ladder diagrams Chapter 1: Introduction to statistics
1-20 68P02901W56-R
Chapter
2
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-6
• "Displaying statistic values" on page 2-9
• "Setting the statistic interval" on page 2-11
• "Displaying the statistic interval" on page 2-12
• "Displaying the statistic interval start times" on page 2-13
• "Setting statistic properties" on page 2-15
• "Displaying statistic properties" on page 2-20
68P02901W56-R 2-1
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 Technical Description: BSS Command Reference (68P02901W23) for a detailed description
of the stat_mode command.
2-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Enabling/disabling a statistic
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.
68P02901W56-R 2-3
Enabling/disabling a statistic Chapter 2: Statistical operations
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 required
cell_desc the cell name or number, if
required
Example
stat_mode rf_losses_tch on cell_name=mid34a
Where: is:
rf_losses_tch meas_type
on enable mode
cell_name=mid34a cell_desc
System response:
COMMAND ACCEPTED
2-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Enabling/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 required
required
Example
stat_mode mtp_link_ins off
Where: is:
mtp_link_ins meas_type
off disable mode
System response:
COMMAND ACCEPTED
68P02901W56-R 2-5
Displaying enabled statistics Chapter 2: Statistical operations
Displaying enabled statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
A listing of the currently enabled statistics may be displayed using the disp_enable_stat command. Refer
to the Technical Description: BSS Command Reference (68P02901W23) for a detailed description of the
disp_enable_stat command.
Specific listings may be generated based on the arguments entered with the disp_enable_stat command,
including:
• No argument - A listing of all currently enabled statistics will be presented.
• BSS - A listing of all of the currently enabled BSS-wide statistics will be presented.
• cell_desc - A listing of all of the currently enabled statistics for the specified cell will
be presented.
• location - A listing of all of the currently enabled statistics for the specified site will be
presented.
• meas_type - A listing of all of the currently enabled statistics for the specified measurement
type will be presented.
Displaying all enabled statistics
A listing of all of the enabled statistics may 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
mtp_changeback
mtp_restoration
2-6 68P02901W56-R
Maintenance Information: GSM Statistics Application Displaying enabled statistics
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
in_inter_ho
out_inter_ho
intra_bss_ho
access_per_rach
.
.
.
tch_delay
intf_on_idle
busy_tch
busy_sdcch
ber
.
.
68P02901W56-R 2-7
Displaying enabled statistics Chapter 2: Statistical operations
The remaining cell statistics follow until all of the enabled statistics have been displayed.
2-8 68P02901W56-R
Maintenance Information: GSM Statistics Application Displaying statistic values
Displaying statistic values

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The current value of individual statistics for a specific interval can be displayed using the disp_stats
command. Displayed information may represent incremental (peg count) or duration values, depending on
the specified statistic. Refer to the Technical Description: BSS Command Reference (68P02901W23) for a
detailed description of the disp_stats command.
The value of a statistic for the current interval cannot be displayed. The disp_interval command
may 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 of the bins may also be displayed for some counter array statistics. Refer to the descriptions of individual
counter array statistics.
The disp_stats command is entered using the 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
required
board_desc the board_id, if required
When using the disp_stats command to display a per link statistic, the generated output will report all links
for a specified board.
68P02901W56-R 2-9
Displaying statistic values Chapter 2: Statistical operations
Example
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-10 68P02901W56-R
Maintenance Information: GSM Statistics Application Setting the statistic interval
Setting the statistic interval

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The stat_interval is a nonstatistical parameter that is used to specify the interval. Refer to the Technical
Description: BSS Command Reference (68P02901W23) for a detailed description of the stat_interval
parameter.
In normal operations, key statistics and health indicators are calculated by the OMC-R 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.
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 This is 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
68P02901W56-R 2-11
Displaying the statistic interval Chapter 2: Statistical operations
Displaying the statistic interval

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The stat_interval is a non-statistical parameter that is used to specify the interval. The current interval may be
displayed using the disp_element command using the following syntax:
disp_element stat_interval <location>
Where: is:
location This is 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
2-12 68P02901W56-R
Maintenance Information: GSM Statistics Application Displaying the statistic interval start times
Displaying the statistic interval start times

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The starting times of the statistic intervals may be displayed by entering the disp_interval command. Refer
to the 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 day that 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.
68P02901W56-R 2-13
Displaying the statistic interval start times Chapter 2: Statistical operations
Example
If the disp_interval command is entered at 1501, the following output displays:
disp_interval
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
2-14 68P02901W56-R
Maintenance Information: GSM Statistics Application Setting statistic properties
Setting statistic properties

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The properties for statistics (except for the statistic interval) may be changed using the chg_stat_prop
command. Refer to the Technical Description: BSS Command Reference (68P02901W23) for a detailed
description of the chg_stat_prop command.
The specific properties that may be changed are dependent on the statistic type.
• The alarm threshold may be changed for counter, counter array and gauge statistics if an alarm
is associated with the statistic.
• Bin ranges may be changed for normal and weighted statistics.
• Properties may not be changed for total time (duration) statistics.
Setting a threshold
Some counter and gauge statistics may be associated with alarms. Threshold values may be specified for
these statistics. An alarm is sent to the Operations and Maintenance Centre - 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 required
required
68P02901W56-R 2-15
Setting statistic properties Chapter 2: Statistical operations
Example
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
Where: is:
rf_losses_tch meas_type
cell_name=mn14b cell_desc
System response:
Enter the alarm threshold: 500
COMMAND
ACCEPTED
Counter statistics
Counter statistics that may be assigned a threshold are presented in Table 2-1.
Table 2-1 Counter statistics
Statistical name Alarm severity Valid values Basis

ALLOC_SDCCH_FAIL Major min: 1 max: 2147483647 cell
ALLOC_TCH_FAIL Major min: 1 max: 2147483647 cell
{24347} ATER_PREEMPT_FAIL Warning min: 1 max: 2147483647 AXCDR
BAD_HO_REFNUM_MS Warning min: 1 max: 2147483647 cell
CHAN_REQ_MS_BLK Minor min: 1 max: 2147483647 cell
CIPHER_MODE_FAIL Minor min: 1 max: 2147483647 cell
CLASSMK_UPDATE_FAIL Minor min: 1 max: 2147483647 cell
CONGESTION_LOST_MSU Warning min: 1 max: 2147483647 SS7 link
FRMR Warning min: 1 max: 2147483647 X.25 link or
LAPD link
HO_REQ_MSC_FAIL Warning min: 1 max: 2147483647 cell
HO_REQ_MSC_PROTO Warning min: 1 max: 2147483647 BSS
INVALID_FRAMES_RX Warning min: 1 max: 2147483647 X.25 link or
LAPD link
MA_CMD_TO_MS_BLKD Minor min: 1 max: 2147483647 cell
MA_FAIL_FROM_MS Warning min: 1 max: 2147483647 cell
MA_REQ_FROM_MSC_FAIL Warning min: 1 max: 2147483647 BSS
MSU_DISCARDED Warning min: 1 max: 2147483647 SS7 link
Cont.
2-16 68P02901W56-R
Table 2-1 Counter statistics (Continued)

Statistical name Alarm severity Valid values Basis
MTP_NEG_ACKS Warning min: 1 max: 2147483647 SS7 link
MTP_RE_TX Warning min: 1 max: 2147483647 SS7 link
MTP_SL_ACK Major min: 1 max: 2147483647 SS7 link
MTP_SL_ALIGNMENT Minor min: 1 max: 2147483647 SS7 link
MTP_SL_CONGESTION Major min: 1 max: 2147483647 SS7 link
MTP_SL_ERROR_RATE Major min: 1 max: 2147483647 SS7 link
MTP_SL_FAIL Major min: 1 max: 2147483647 SS7 link
MTP_SL_FIBR Major min: 1 max: 2147483647 SS7 link
MTP_START_RPO Warning min: 1 max: 2147483647 SS7 link
MTP_SU_ERROR Warning min: 1 max: 2147483647 SS7 link
N2_EXPIRY Warning min: 1 max: 2147483647 X.25 link or
LAPD link
PAGE_REQ_FROM_MSC_FAIL Minor min: 1 max: 2147483647 BSS
PCH_Q_PAGE_DISCARD Minor min: 1 max: 2147483647 cell
RF_LOSSES_SD Major min: 1 max: 2147483647 cell
RF_LOSSES_TCH Major min: 1 max: 2147483647 timeslot
ROUTING_SYNTAX Warning min: 1 max: 2147483647 BSS
ROUTING_UNKNOWN Warning min: 1 max: 2147483647 BSS
SL_CONGESTION Warning min: 1 max: 2147483647 SS7 link
{24347}TCH_PRE- Warning min: 1 max: 2147483647 cell
EMPT_FAIL_NO_CAND
The maximum value that may 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.
68P02901W56-R 2-17
Setting statistic properties Chapter 2: Statistical operations
Setting bin ranges
Distribution statistics include 10 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
bins in a distribution statistic may 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
bin range is being set, if required
required
The bin ranges for the BER statistic may not be modified.
Bin ranges
Distribution statistics include 10 bins, numbered 0 to 9. 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 should be 0,
and the maximum value for bin 9 should be 100.
Gaps in the range of values covered should be 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 would exist for the value 11. This would cause any report of a value equal to 11 to be ignored.
Bin minimums and maximums may 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.
2-18 68P02901W56-R
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>
7
Enter the max value for bin 1: 7
COMMAND
ACCEPTED
68P02901W56-R 2-19
Displaying statistic properties Chapter 2: Statistical operations
Displaying statistic properties

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The properties of individual statistics may 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.
• The mode and type only are displayed for the duration statistics.
2-20 68P02901W56-R
Maintenance Information: GSM Statistics Application Displaying statistic properties
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
properties are being displayed, if
required
required
Example
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
System response:
STATISTIC: TOTAL_CALLS SITE: 1
TYPE: PER CELL OBJECT: COUNTER
CELL # MODE ALARM SEVERITY ALARM 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
68P02901W56-R 2-21
Displaying a gauge statistic
Gauge statistic properties are displayed by entering the disp_stat_prop command using the following syntax:
Where: is:
meas_type a gauge statistic
required
required
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 1 cell_number=5 4 3 2 1 61698 34776
Where: is:
available_tch meas_type
1 location
cell_number=5 4 3 2 1 61698 34776 cell_desc
System response:
STATISTIC: AVAILABLE_TCH SITE: 1
TYPE: PER CELL OBJECT: GAUGE
CELL # MODE ALARM SEVERITY ALARM THRESHOLD

--------- --------- --------- ---------
2-22 68P02901W56-R
Displaying a distribution statistic
Distribution statistic properties are displayed by entering the disp_stat_prop command using the following
syntax:
Where: is:
meas_type a distribution statistic
required
required
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 1 cell_number=5 4 3 2 1 61698 34776
Where: is:
busy_tch meas_type
1 location
5 4 3 2 1 61698 34776 cell_desc
68P02901W56-R 2-23
System response:
STATISTIC: BUSY_TCH SITE: 1
TYPE: PER CELL OBJECT: DISTRIB
CELL # MODE BIN MIN MAX

--------- --------- --------- --------- ---------
543 21 61698 (f102h)34776 ENABLED 0 0 1
(87d8h)
1 2 3
2 4 5
3 6 7
4 8 9
5 10 11
6 12 13
7 14 15
8 16 2147174832
9 214174833 2141749879
2-24 68P02901W56-R
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
required
required
Example
This example shows the interaction required to display the properties for the 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 meas_type
5 4 3 2 1 62259 8736 cell_desc
68P02901W56-R 2-25
System response:
STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 2
TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN # CAUSE
--------- ---------
0 ENABLED NO ALARM
1 ENABLED NO ALARM
2 ENABLED NO ALARM
3 ENABLED NO ALARM
4 ENABLED NO ALARM
5
6
7
8
9
CELL # MODE
------------------------- -------
543 21 62259 (f333h) 8736 (2220h) DISABLED
2-26 68P02901W56-R
Displaying a duration statistic
Duration statistic properties are displayed by entering the disp_stat_prop command using the following
syntax:
Where: is:
meas_type a duration statistic
required
required
Example
This example shows the interaction required to display the properties for the FLOW_CONTROL_BARRED
statistic.
disp_stat_prop flow_control_barred 2 5 4 3 2 1 62259 8736
Where: is:
flow_control_barred meas_type
2 location
5 4 3 2 1 62259 8736 cell_desc
System response:
STATISTIC: FLOW_CONTROL_BARRED SITE: 2
TYPE: PER CELL OBJECT: TOTAL TIME
CELL # MODE
------------------ ---------
543 21 62259 (f333h) 8736 (2220h) DISABLED
68P02901W56-R 2-27
2-28 68P02901W56-R
Chapter
3
BSS statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS statistics are captured from events occurring at the BSS. They are categorized into subgroups, each of
which are described in "BSS statistics subgroups" on page 3-2.
68P02901W56-R 3-1
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.
• "SCCP performance and utilization" on page 3-2.
• {24349} "Voice Group Call Services" on page 3-3.
BSS C7 utilization
BSS C7 utilization statistics track the number of messages received and transmitted on the signalling
links. This information indicates the activity level on the Signalling Links (SLs). The following are BSS
C7 utilization statistics:
• "SIF_SIO_RX_OPC" on page 3-15.
• "SIF_SIO_TX_DPC" on page 3-16.
• "SIF_SIO_TYPE" on page 3-17.
Intra-BSS handover
A single counter array statistic tracks the number of successful intra-BSS handovers:
"INTRA_BSS_HO_CAUSE_SUCC" on page 3-5.
SCCP performance and utilization
SCCP performance and utilization statistics track the performance of the Signalling Connection Control
Part (SCCP) protocol layer of the ITU-TSS C7.
3-2 68P02901W56-R
Maintenance Information: GSM Statistics Application BSS statistics subgroups
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
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:
• "HO_REQ_MSC_PROTO" on page 3-4.
• "MA_REQ_FROM_MSC_FAIL" on page 3-7.
• "MSC_OVLD_MSGS_RX" on page 3-8.
• "PAGE_REQ_FROM_MSC_FAIL" on page 3-9.
• "ROUTING_SYNTAX" on page 3-10.
• "ROUTING_UNKNOWN" on page 3-11.
• "SCCP_MSGS" on page 3-12.
• "SCCP_MSGS_RX" on page 3-13.
• "SCCP_MSGS_TX" on page 3-14.
Voice Group Call Services
{24349}
Voice Group Call Services (VGCS) statistics track VGCS events between the BSS and the MSC. The
following are VGCS statistics:
• "VGCS_TALKER_IND" on page 3-18.
• "VGCS_VBS_SETUP" on page 3-19.
• "VGCS_VBS_SETUP_ACK" on page 3-20.
• "VGCS_VBS_SETUP_REFUSE" on page 3-21.

.
68P02901W56-R 3-3
HO_REQ_MSC_PROTO Chapter 3: BSS statistics
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 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.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-4 68P02901W56-R
Maintenance Information: GSM Statistics Application INTRA_BSS_HO_CAUSE_SUCC
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.
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.
{24349} In two channel mode, the talker is essentially maintained within the BSS as a point-to-point call and
hence the existing statistical trigger points implemented within the BSS cover the talker.
68P02901W56-R 3-5
INTRA_BSS_HO_CAUSE_SUCC Chapter 3: BSS statistics
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.
Optimization.
Basis BSS.
Type Counter array.
3-6 68P02901W56-R
Maintenance Information: GSM Statistics Application MA_REQ_FROM_MSC_FAIL
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
A threshold value should be assigned to this statistic which reflects the maximum number of failures that are
acceptable in normal system operations.
If the specified threshold is exceeded, the 7. BSS: Mobile assignment 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.2.2.5 and 3.2.1.3.

Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-R 3-7
MSC_OVLD_MSGS_RX Chapter 3: BSS statistics
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 independently 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.
Network planning.
Basis BSS.
Type Counter.
3-8 68P02901W56-R
Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_MSC_FAIL
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
A threshold value should be assigned to this statistic which reflects the maximum number of 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
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Usage Quality of service monitoring: Paging analysis.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-R 3-9
ROUTING_SYNTAX Chapter 3: BSS statistics
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 signalling 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
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Usage SCCP performance and utilization.
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
3-10 68P02901W56-R
Maintenance Information: GSM Statistics Application ROUTING_UNKNOWN
ROUTING_UNKNOWN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of invalid signalling 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 will not be able to correctly route the message. A threshold value
should be assigned to this statistic which reflects the maximum number of 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 Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
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-R 3-11
SCCP_MSGS Chapter 3: BSS statistics
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 signalling link.
Analysis
SCCP is an SS7 protocol used in transferring signalling messages between the BSC and MSC. 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.
3-12 68P02901W56-R
Maintenance Information: GSM Statistics Application SCCP_MSGS_RX
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 signalling link.
Analysis
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-R 3-13
SCCP_MSGS_TX Chapter 3: BSS statistics
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 signalling link.
Analysis
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-14 68P02901W56-R
Maintenance Information: GSM Statistics Application SIF_SIO_RX_OPC
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 signalling links to a BSS.
Analysis
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.
68P02901W56-R 3-15
SIF_SIO_TX_DPC Chapter 3: BSS statistics
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 signalling links to a BSS.
Analysis
A DPC is part of the label in a signalling message that uniquely identifies, in a signalling network, the
destination point of the message. This statistic can be used for trend analysis of the activity of the signalling
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-16 68P02901W56-R
Maintenance Information: GSM Statistics Application SIF_SIO_TYPE
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 signalling link.
Analysis
This statistic can be used for trend analysis of the activity of the signalling 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-R 3-17
VGCS_TALKER_IND Chapter 3: BSS statistics
VGCS_TALKER_IND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_TALKER_IND statistic counts the number of transitions from IDLE to BUSY that are performed
due to successful applications of the uplink access mechanism.
Pegging
The VGCS_TALKER_IND statistic is pegged for the following successful uplink scenarios:
• The BSS enters a state where it is waiting for the MS to establish on the VGC channel. This
occurs when an UPLINK REQUEST ACKNOWLEDGE message is received from the MSC
and the TALKER INDICATION message is transmitted from the MS.
• The BSS sends an UPLINK REQUEST CONFIRMATION message containing the stored
TALKER INDICATION message to the MSC.
Analysis
Reference None.
Usage Voice Group Call Services.
Basis VGCS.
Type Counter.
3-18 68P02901W56-R
Maintenance Information: GSM Statistics Application VGCS_VBS_SETUP
VGCS_VBS_SETUP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_VBS_SETUP statistic counts the number of VGCS/VBS SETUP messages received by the BSS
from the MSC. That is, the number of times the BSS is instructed to establish a voice group call.
Pegging
The BSS pegs the VGCS_VBS_SETUP statistic upon receipt of a VGCS/VBS SETUP message from
the MSC.
Analysis
Reference None.
Basis BSS.
Type Counter.
68P02901W56-R 3-19
VGCS_VBS_SETUP_ACK Chapter 3: BSS statistics
VGCS_VBS_SETUP_ACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_VBS_SETUP_ACK statistic counts the number of VGCS/VBS SETUP ACK messages
transmitted by the BSS to the MSC. That is, the number of acknowledgments to valid requests for a voice
group call.
Pegging
The BSS pegs the VGCS_VBS_SETUP_ACK BSS statistic if VGCS CC registration passes.
.
Analysis
Reference None.
Basis BSS.
Type Counter.
3-20 68P02901W56-R
Maintenance Information: GSM Statistics Application VGCS_VBS_SETUP_REFUSE
VGCS_VBS_SETUP_REFUSE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_VBS_SETUP_REFUSE statistic counts the number of VGCS/VBS SETUP REFUSE messages
transmitted by the BSS to the MSC. That is, the number of invalid requests for a voice group call.
Pegging
The VGCS_VBS_SETUP_REFUSE statistic is split into 2 bins which are pegged depending on the Service
Flag of the incoming VGCS/VBS SETUP. Details are shown in Table 3-1.
Table 3-1 VGCS_VBS_SETUP_REFUSE bins

0 VGCS This type of request is rejected due to a
number of reasons. For example, the BSS
has reached maximum capacity or the VGCS
feature is restricted or disabled.
1 VBS This feature is not supported at this time so
a request for this service shall always be
rejected.
Analysis
Reference None.
Basis BSS.
Type Counter array.
68P02901W56-R 3-21
VGCS_VBS_SETUP_REFUSE Chapter 3: BSS statistics
3-22 68P02901W56-R
Chapter
4
Cell statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Cell statistics are captured from events occurring in a cell. They are categorized into subgroups, each of which
are described in "Cell statistics subgroups" on page 4-2.
68P02901W56-R 4-1
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-3.
• "Assignment redirection" on page 4-3.
• "Call clearing" on page 4-3.
• "Concentric cell" on page 4-4.
• "Connection establishment" on page 4-4.
• "Directed retry" on page 4-5.
• "Emergency call access" on page 4-5.
• {22879} "Enhanced 2G/3G handover and reselection" on page 4-5.
• {24347} "Enhanced Multi-level Precedence and Pre-emption 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.
• "Intra-BSS handover" on page 4-7.
• "Interference bands" on page 4-7.
• "Intra-cell handover" on page 4-7.
• "Multiband" on page 4-8.
• {22708/23706} "Network assist cell change" on page 4-8.
• {23956} "GPRS Quality of Service" on page 4-9.
• {24303} "GPRS System information" on page 4-9.
• "TCH assignment" on page 4-10.
• "Usage congestion" on page 4-10.
• {24349} "Voice Group Call Services" on page 4-12.
4-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Cell statistics subgroups
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-29.
• "AMR_FR_DL_ADAPTATION" on page 4-30.
• "AMR_FR_DL_CODEC_MODE_USAGE" on page 4-31.
• "AMR_FR_UL_ADAPTATION" on page 4-32.
• "AMR_FR_UL_CODEC_MODE_USAGE" on page 4-33.
• "AMR_HR_DL_ADAPTATION" on page 4-34.
• "AMR_HR_DL_CODEC_MODE_USAGE" on page 4-35.
• "AMR_HR_UL_ADAPTATION" on page 4-36.
• "AMR_HR_UL_CODEC_MODE_USAGE" on page 4-37.
• "AMR_INCREASE_THRESH_ADJUST" on page 4-38.
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-39 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-65.
• "CLR_REQ_TO_MSC" on page 4-68.
• "RF_LOSSES_SD" on page 4-163.
• "RF_LOSSES_TCH" on page 4-164.
68P02901W56-R 4-3
Concentric cell
Concentric cell statistics track concentric cell feature processes. The following are concentric cell statistics:
• "TCH_CONG_INNER_ZONE" on page 4-176.
• "TCH_CONG_INNER_ZONE_HR" on page 4-177.
• "TCH_USAGE_INNER_ZONE" on page 4-191.
• "ZONE_CHANGE_ATMPT" on page 4-202.
• "ZONE_CHANGE_SUC" on page 4-203.
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-13.
• "ACCESS_PER_PCH" on page 4-14.
• "ACCESS_PER_PPCH" on page 4-16.
• "ACCESS_PER_RACH" on page 4-18.
• "ALLOC_SDCCH" on page 4-19.
• "ALLOC_SDCCH_FAIL" on page 4-21.
• "ALLOC_TCH" on page 4-22.
• "ALLOC_TCH_FAIL" on page 4-23.
• "ALLOC_TCH_FAIL_HR" on page 4-25.
• "ALLOC_TCH_HR" on page 4-28.
• "CALL_SP_VERS_DOWNGRADE_MONITOR" on page 4-59.
• "CHAN_REQ_CAUSE_ATMPT" on page 4-63.
• "CHAN_REQ_MS_BLK" on page 4-64.
• "CONN_REFUSED" on page 4-72.
• "CONN_REQ_TO_MSC" on page 4-74.
• "OK_ACC_PROC" on page 4-125.
• "OK_ACC_PROC_SUC_RACH" on page 4-127.
• "PAGE_REQ_FROM_MSC" on page 4-137.
4-4 68P02901W56-R
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-70.
• "CONGEST_STAND_HO_ATMPT" on page 4-71.
Emergency call access
Emergency call access statistics track emergency call processes. The following are emergency call access
statistics:
• "NUM_EMERG_ACCESS" on page 4-114.
• "NUM_EMERG_REJECTED" on page 4-115.
• "NUM_EMERG_TCH_KILL" on page 4-116.
• "NUM_EMERG_TERM_SDCCH" on page 4-117.
Enhanced 2G/3G handover and reselection
{22879}
Enhanced 2G/3G handover and reselection statistics are captured from 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-118.
• "NUM_HO_TO_3G_RES_ALLOC_SUCC" on page 4-121.
• "NUM_HO_TO_3G_SUCCESS" on page 4-122.
• "NUM_HO_FROM_3G_ATTEMPTS" on page 4-119.
• "NUM_HO_FROM_3G_SUCCESS" on page 4-120.
• "NUM_MULTIRAT_MS_ORIG_CALL" on page 4-123.
• "NUM_T3121_EXPIRY" on page 4-124.
68P02901W56-R 4-5
Enhanced Multi-level Precedence and Pre-emption service
{24347}
Enhanced Multi-level Precedence and Pre-emption service statistics are captured from events occurring
due to multilevel and pre-emption. The following are Enhanced Multi-level Precedence and Pre-emption
service statistics:
• "PREEMPT_CAP" on page 4-161.
• "QUEUE_PREEMPT_ATMPT" on page 4-162.
• "TCH_PREEMPT_ATMPT" on page 4-181.
• "TCH_PREEMPT_FAIL_NO_CAND" on page 4-183.
• "TCH_PREEMPT_FAIL_TIMEOUT" on page 4-184.
• "TCH_PREEMPT_RQD" on page 4-185.
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-77.
• "ER_INTRA_CELL_HO_SUC" on page 4-78.
• "TCH_USAGE_EXT_RANGE" on page 4-190.
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-49.
• "HO_FAIL_NO_RESOURCES" on page 4-80.
4-6 68P02901W56-R
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-85.
• "HO_REQ_FROM_MSC" on page 4-82.
• "HO_REQ_MSC_FAIL" on page 4-83.
• "IN_INTER_BSS_HO" on page 4-92.
• "OUT_INTER_BSS_HO" on page 4-130.
Interference bands
Interference band statistics track the number of idle TCHs per interference band:
• "IDLE_TCH_INTF_BAND0" on page 4-87.
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-93.
• "OUT_HO_CAUSE_ATMPT" on page 4-128.
• "OUT_INTRA_BSS_HO" on page 4-132.
Intra-cell handover
Intra-cell handover statistics track intra-cell handover processes. "INTRA_CELL_HO" on page 4-96 is
the only intra-cell handover statistic.
68P02901W56-R 4-7
Multiband
Multiband statistics track multiband feature processes. The following are multiband statistics:
• "ASSIGNMENT_REDIRECTION" on page 4-39.
• "INTERBAND_ACTIVITY" on page 4-95.
• "MS_ACCESS_BY_TYPE" on page 4-106.
• "MS_TCH_USAGE_BY_TYPE" on page 4-107.
• "MS_TCH_USAGE_BY_TYPE" on page 4-107.
• "OUT_HO_CAUSE_ATMPT" on page 4-128.
Network assist cell change
{22708/23706}
Network assist cell change statistics are captured from events occurring in the network assist cell. The
following are network assist cell change statistics:
• "NUM_CELL_RESEL_CELL" on page 4-111.
• "NUM_CELL_RESEL_CELL_PCCN" on page 4-112.
• "NUM_CELL_RESEL_CELL_SUCC" on page 4-113.
There are statistics that capture PCCC and PCCO attempts to neighbour cells. These are shown in
"Network assist neighbour cell change statistics" on page 5-7.
4-8 68P02901W56-R
GPRS Quality of Service
{23956}
BSS GPRS Quality of Service statistics are captured from events occurring in the BSS. The following
are GPRS Quality of Service statistcs:
• "TIMER_EXP_PAP_CONV" on page 4-192.
• "PFC_ADMISSION" on page 4-141.
• "PFC_ADMISSION_OTHER" on page 4-143.
• "PFC_REJECTION" on page 4-155.
• "PFC_REJECTION_OTHER" on page 4-157.
• "PFC_REJECT_CAUSES" on page 4-152.
• "DL_LLC_DATA_VOLUME" on page 4-75.
• "UL_LLC_DATA_VOLUME" on page 4-195.
• "PFC_UPGRADE" on page 4-158.
• "PFC_DOWNGRADE_SUCCESS" on page 4-146.
• "PFC_DOWNGRADE_FAILURE" on page 4-144.
• "PFC_PREEMPTIONS" on page 4-148.
• "PFC_REJ_DGRD_PRMPT_CELL" on page 4-150.
GPRS System information
{24303}
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-134.
• "PACKET_SYSINFO_RESP" on page 4-136.
68P02901W56-R 4-9
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-98.
• "MA_CMD_TO_MS_BLKD" on page 4-105.
• "MA_FAIL_FROM_MS" on page 4-102.
• "MA_REQ_FROM_MSC" on page 4-103.
• "TCH_Q_REMOVED" on page 4-187.
• "TOTAL_CALLS" on page 4-194.
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-40.
• "AVAILABLE_TCH" on page 4-41.
• {22404} "AVAILABLE_TCH_DCS1800" on page 4-42.
• {22404} "AVAILABLE_TCH_EGSM" on page 4-44.
• "AVAILABLE_TCH_HR" on page 4-46.
• {22404} "AVAILABLE_TCH_PGSM" on page 4-47.
• "BUSY_SDCCH" on page 4-50.
• "BUSY_TCH" on page 4-52.
• "BUSY_TCH_CARR" on page 4-54.
• {22404} "BUSY_TCH_DCS1800" on page 4-55.
• {22404} "BUSY_TCH_EGSM" on page 4-56.
• "BUSY_TCH_HR" on page 4-57.
• {22404} "BUSY_TCH_PGSM" on page 4-58.
• "CALLS_QUEUED" on page 4-61.
• "CLASSMK_UPDATE_FAIL" on page 4-66.
• "FLOW_CONTROL_BARRED" on page 4-79.
4-10 68P02901W56-R
• "MA_COMPLETE_TO_MSC" on page 4-100.
• "MA_FAIL_FROM_MS" on page 4-102.
• "MA_REQ_FROM_MSC" on page 4-103.
• "PAGING_REQUESTS" on page 4-138.
• "PCH_AGCH_Q_LENGTH" on page 4-139.
• "PCH_Q_PAGE_DISCARD" on page 4-140.
• "PPCH_Q_PAGE_DISCARD" on page 4-160
• "SDCCH_CONGESTION" on page 4-166.
• "SECOND_ASSIGN_ATMPT" on page 4-169.
• "SECOND_ASSIGN_SUC" on page 4-170.
• "SMS_INIT_ON_SDCCH" on page 4-171.
• "SMS_INIT_ON_SDCCH_HO_IN" on page 4-172
• "SMS_INIT_ON_TCH" on page 4-174.
• "SMS_NO_BCAST_MSG" on page 4-175.
• "TCH_CONGESTION" on page 4-178.
• "TCH_CONGESTION_HR" on page 4-179.
• "TCH_DELAY" on page 4-180.
• "TCH_Q_LENGTH" on page 4-186.
• "TCH_USAGE" on page 4-188.
68P02901W56-R 4-11
{24349}
Voice Group Call Services (VGCS) statistics track VGCS events between the BSS and the MSC. The
following are VGCS statistics:
• "ALLOC_TCH_FAIL_VGCS" on page 4-27.
• "VGCS_FR_TCH_BUSY" on page 4-197.
• "VGCS_HR_TCH_BUSY" on page 4-198.
• "VGCS_VBS_ASSIGN_FAIL" on page 4-199.
• "VGCS_VBS_ASSIGN_REQ" on page 4-200.
• "VGCS_VBS_ASSIGN_RESULT" on page 4-201.
4-12 68P02901W56-R
Maintenance Information: GSM Statistics Application ACCESS_PER_AGCH
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 only pegged 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.
Network planning.
Basis Cell.
Type Counter.
This statistic is affected by phantom Random Access CHannel (RACH).The level of congestion
on the AGCH cannot be determined using current statistics
68P02901W56-R 4-13
ACCESS_PER_PCH Chapter 4: Cell statistics
ACCESS_PER_PCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ACCESS_PER_PCH statistic tracks the number of Paging Request messages sent on the air interface.
A paging message could contain up to four pages for paging by TMSI and up to two pages for paging by IMSI.
This statistic is modified to count both Circuit Switched (CS) and Packet Switch (PS) paging on Page
Channel (PCH).
This statistic is obtained by measuring the number of PAGING REQUEST messages sent on the PCH. This
statistic counts the number of attempts.
The bins are:

0 ACCESS_PER_PCH_PS_CS Both CS and PS pages within the PAGING
REQUEST message.
1 ACCESS_PER_PCH_CS Only CS pages within the PAGING REQUEST
message
2 ACCESS_PER_PCH_PS Only PS pages within the PAGING REQUEST
message.
Pegging
This statistic pegs received requests that:
• Succeeded (resulting in channel assignment).
• Failed (did not result in channel assignment).
This statistic is pegged for both GPRS and EGPRS events.
4-14 68P02901W56-R
Maintenance Information: GSM Statistics Application ACCESS_PER_PCH
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.
Network planning.
Basis Cell.
Type Counter array.
The ACCESS_PER_PCH statistic pegs a second time if the MS does not answer the first page.
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 mobile.
68P02901W56-R 4-15
ACCESS_PER_PPCH Chapter 4: Cell statistics
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).
The bins are:
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.
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.
Network planning.
Basis Cell.
Type Counter array.
4-16 68P02901W56-R
Maintenance Information: GSM Statistics Application ACCESS_PER_PPCH
The ACCESS_PER_PPCH statistic pegs a second time if the MS does not answer the first page.
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 mobile.
68P02901W56-R 4-17
ACCESS_PER_RACH Chapter 4: Cell statistics
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 dialled from the MS. It is also used as part
of the call re-establishment procedure.
Pegging
This statistic pegs received requests that:
• Succeeded (resulting in channel assignment).
• Failed (did not result 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.
Network planning.
Basis Cell.
Type Counter.
This statistic is affected by phantom RACHs. The counter is incremented at least once for each
phantom RACH.
4-18 68P02901W56-R
Maintenance Information: GSM Statistics Application ALLOC_SDCCH
ALLOC_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ALLOC_SDCCH statistic is the sum of the number of times a SDCCH is successfully seized. If a TCH
is reconfigured as an SDCCH, only the SDCCH statistics will be 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 dialled from the MS. It is also used as part
of the call re-establishment procedure.
SDCCH seizure is caused by immediate assignment, handover, and channel assignment procedures.
Congestion is signalled 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 will be sent upon:
• Successful handover on an SDCCH channel.
• Successful immediate assignment on an SDCCH channel.
This statistic peg for reasons other than calls requiring a traffic channel, such as location updates.
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.
Key statistic: SDCCH_CONGESTION.
Basis Cell.
Type Counter.
68P02901W56-R 4-19
ALLOC_SDCCH Chapter 4: Cell statistics
This statistic is affected by phantom RACHs.
4-20 68P02901W56-R
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 signalled 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 - PM alarm
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.
Network planning.
Fault finding.
Optimization.
Ladder: Immediate assignment blocked, Connection establishment.
Key statistic : SDCCH_CONGESTION.
Basis Cell.
Type Counter.
Alarm Major.
68P02901W56-R 4-21
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.
{24349} This statistic pegs when a VGC channel is successfully allocated.
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: TCH_MEAN_AR-
RIVAL_RATE, TCH_MEAN_HOLDING_TIME,
CELL_TCH_ASSIGNMENTS, TCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.
4-22 68P02901W56-R
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.
{24349} In two channel mode the talker is essentially maintained within the BSS as a point-to-point call
and hence the existing statistical trigger points implemented within the BSS will cover the talker with no
additional change to the BSS.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of TCH failures due
to congestion that are acceptable in normal system operations.
68P02901W56-R 4-23
ALLOC_TCH_FAIL Chapter 4: Cell statistics
If the specified threshold is exceeded, the 25. CELL: Attempt at allocating an TCH failed - PM alarm
Usage Quality of service: Call set-up.
Fault finding.
Optimization.
Network planning Ladder: Inter-BSS handover, Intra-BSS
handover, Assignment to TCH.
Key statistics: TCH_MEAN_ARRIVAL_RATE.
Basis Cell.
Type Counter.
Alarm Major.
4-24 68P02901W56-R
Maintenance Information: GSM Statistics Application ALLOC_TCH_FAIL_HR
ALLOC_TCH_FAIL_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The ALLOC_TCH_FAIL_HR statistic replaces ALLOC_TCH_FAIL_HR_AMR.
Description
The statistic tracks the number of unsuccessful allocations of a half rate AMR and/or GSM TCH {24349} or
VGCS 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{24349} or VGCS 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.
{24349} This statistic pegs when a half rate VGC channel is unsuccessfully allocated.
68P02901W56-R 4-25
ALLOC_TCH_FAIL_HR Chapter 4: Cell statistics
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 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 resulting 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.
• If the channel type is half rate preferred/full rate non-preferred OR full rate preferred/half
rate non-preferred and neither channel type is allocated (a complete TCH allocation failure
scenario), the ALLOC_TCH_FAIL shall be pegged twice and ALLOC_TCH_FAIL_HR
stat shall be pegged once. That is, once for failed FR and once for failed HR.
• When the non-preferred channel type is successfully assigned a channel, a failure shall be
pegged for the preferred type.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of half rate AMR
and/or GSM TCH failures due to congestion that are acceptable in normal system operations.
There is no alarm generated with respect to this statistic.
Reference None.
Usage Quality of service: Call set-up.
Fault finding.
Optimization.
Network planning
Ladder: Inter-BSS handover, Intra-BSS handover, Assignment to
TCH.
Basis Cell.
Type Counter.
4-26 68P02901W56-R
Maintenance Information: GSM Statistics Application ALLOC_TCH_FAIL_VGCS
ALLOC_TCH_FAIL_VGCS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The ALLOC_TCH_FAIL_VGCS statistic represents the number of times a VGCS/VBS ASSIGNMENT

REQUEST has failed to allocate a channel to satisfy the request.
Pegging
The ALLOC_TCH_FAIL_VGCS statistic is pegged if the VGCS allocation fails due to unavailability of
radio resource and the MSC has not specified a delay to be allowed. If a delay has been allowed, the statistic
will be pegged if, due to radio resource unavailability, a CLEAR REQUEST message is sent to the MSC.
This statistic has two bins which are pegged depending on whether the failure occurs for a full rate or
half rate request. Details are shown in Table 4-1.
Table 4-1 ALLOC_TCH_FAIL_VGCS bins

0 FR The number of full rate requests failing to
allocate a resource.
1 HR The number of half rate requests failing to
allocate a resource.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-27
ALLOC_TCH_HR Chapter 4: Cell statistics
ALLOC_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The ALLOC_TCH_HR statistic replaces ALLOC_TCH_HR_AMR.
Description
The statistic tracks the number of successful half rate AMR and/or GSM TCH{24349} or VGCS allocations
within a cell for both call originations and hand ins.
Pegging
This statistic pegs for successful half rate AMR and/or GSM TCH{24349} or VGCS 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
incoming directed retries.
• 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 {24349} or VGCS allocations.
Reference None.
Network planning.
Basis Cell.
Type Counter.
4-28 68P02901W56-R
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.
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-R 4-29
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.
There are up to four codecs in the Active Codec Set (ACS) and the format of this statistic allows
for this. 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.
The bins are:
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 that a specific codec mode is adapted on the downlink of full-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-30 68P02901W56-R
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.
The bins are:
Bin Description
0 AMR full-rate DL codec mode usage of AFS 12.2kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the downlink of full-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-31
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.
The bins are:
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 that a specific codec mode is adapted on the uplink of full-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-32 68P02901W56-R
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.
The bins are:
Bin Description
0 AMR full-rate UL codec mode usage of AFS 12.2kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the uplink of full-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-33
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.
The bins are:
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 that a specific codec mode is adapted on the downlink of half-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-34 68P02901W56-R
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.
The bins are:
Bin Description
0 AMR half-rate DL codec mode usage of AFS 7.95kbps
Pegging
This statistic pegs each time that a specific codec mode is used on the downlink of half-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-35
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.
The bins are:
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 that a specific codec mode is adapted on the uplink of half-rate AMR calls.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-36 68P02901W56-R
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.
Pegging
This statistic pegs each time that a specific codec mode is used on the uplink of half-rate AMR calls.
The bins are:
Bin Description
0 AMR half-rate UL codec mode usage of AFS 7.95kbps
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-37
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.
Reference None.
Network planning.
Basis Cell.
Type Counter.
4-38 68P02901W56-R
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.

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.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-39
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.
{24349} The BSS maintains a count of the number of available resources during a statistical interval. This
involves counting the idle and busy channels within the cell, some of these resources will be VGCS related
and hence need to be included in the calculation of the cell capacity.
Pegging
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 will be pegged with the same value as before).
This statistic pegs when a change in SDCCH availability is detected.
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.
Network planning.
Basis Cell.
Type Gauge.
4-40 68P02901W56-R
Maintenance Information: GSM Statistics Application AVAILABLE_TCH
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 and its operational state is disabled.
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 and is unavailable when the 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 above.
This statistic only counts those traffic channels, which are configured as TCH at the time of measurement.
Switchable PDTCHs will be included only if they are configured as TCHs.
Pegging
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 will be 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.
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.
Basis Cell.
Type Gauge.
68P02901W56-R 4-41
AVAILABLE_TCH_DCS1800 Chapter 4: Cell statistics
AVAILABLE_TCH_DCS1800
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
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.
AVAILABLE_TCH_DCS1800 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 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-42 68P02901W56-R
Maintenance Information: GSM Statistics Application AVAILABLE_TCH_DCS1800
Analysis
AVAILABLE_TCH_DCS1800 is used in conjunction with BUSY_TCH_DCS1800 to track DCS1800 layer
utilisation 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-R 4-43
AVAILABLE_TCH_EGSM Chapter 4: Cell statistics
AVAILABLE_TCH_EGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
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.
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.
An idle half rate capable TCH counts as two available resources.
4-44 68P02901W56-R
Maintenance Information: GSM Statistics Application AVAILABLE_TCH_EGSM
Analysis
AVAILABLE_TCH_EGSM is used in conjunction with BUSY_TCH_EGSM to track EGSM layer utilisation
as a function of maximum available capacity.
Reference None.
EGSM TCHs that are in use or available for use within a cell.
Basis Cell.
Type Gauge.
68P02901W56-R 4-45
AVAILABLE_TCH_HR Chapter 4: Cell statistics
AVAILABLE_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The AVAILABLE_TCH_HR statistic replaces AVAILABLE_TCH_HR_AMR.
Description
The statistic reports a maximum and average value for the amount of half rate AMR and/or GSM
TCH{24349} or VGC channels in use or available to be used within the cell.
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 will be pegged with the same value as before). This statistic
pegs when a change in half rate TCH availability {24349} or half rate VGC channel availability is detected.
An idle generic timeslot is counted as one available full rate channel and two available half
rate channels.
Reference None.
Network planning.
Service retainability.
Basis Cell.
Type Gauge statistic.
4-46 68P02901W56-R
Maintenance Information: GSM Statistics Application AVAILABLE_TCH_PGSM
AVAILABLE_TCH_PGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
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.
AVAILABLE_TCH_PGSM 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 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.
An idle half rate capable TCH counts as two available resources.
68P02901W56-R 4-47
AVAILABLE_TCH_PGSM Chapter 4: Cell statistics
Analysis
AVAILABLE_TCH_PGSM is used in conjunction with BUSY_TCH_PGSM to track PGSM layer utilisation
as a function of maximum available capacity.
Reference None.
PGSM TCHs that are in use or available for use within a cell.
Basis Cell.
Type Gauge.
4-48 68P02901W56-R
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 a 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 a MS has accessed a channel with a Handover Reference Number
that the BSS was not expecting. This field is an unformatted random number. The BSS only compares what it
received with what it expected, for example, potentially up to four times for each logical handover detect
for the SDCCH processed at the BSS.
The MS will continue to attempt access until a good Handover Reference Number is received, therefore,
the handover can be successful and the statistic will still peg. This statistics pegs if the handover fails and
recovers, or fails and loses the mobile.
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 may not be because a handover access meant for one cell can be detected
by another, but the channel at the target cell is susceptible during the time between channel activation and
when the MS actually arrives. This is similar to “Phantom RACHs."
If the specified threshold is exceeded, the 19. CELL: Bad HO reference numbers from the MS - PM alarm
will be generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
Reference GSM 4.08, 3.8.0, 3.4.4.2.1, 3.4.4.2.2 and 9.1.13.

Usage Handover.
Fault finding.
Basis Cell.
Type Counter.
Alarm Warning.
68P02901W56-R 4-49
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 will produce 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-2.
Table 4-2 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
{24349} The BSS maintains a count of the number of busy resources during a statistical interval. This
involves counting the busy channels within the cell, some of these resources will be VGCS related and hence
need to be included in the calculation of the cell capacity.
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 a SDCCH is allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be pegged.
4-50 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_SDCCH
Analysis
This statistic can be used for trend analysis of the amount of RF signalling 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.
Network planning.
Optimization.
Key statistic: SDCCH_MEAN_HOLDING_TIME, SDCCH
_TRAFFIC_CARRIED.
Basis Cell.
Type Weighted distribution.
68P02901W56-R 4-51
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.
BUSY_TCH statistic are shown in Table 4-3.
Table 4-3 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-52 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_TCH
{24349} This statistic is pegged whenever a full rate VGC channel is allocated or deallocated.
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.
This statistic can be used for trend analysis of the amount of RF signalling traffic in the cell TCHs. An
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.
Network planning.
Optimization.
Key statistic: TCH_MEAN_HOLDING_TIME,
TCH_TRAFFIC_CARRIED.
Basis Cell.
68P02901W56-R 4-53
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.
{24349} This statistic is pegged whenever a half rate VGC channel is allocated or deallocated.
Analysis

Usage Congestion.
Network planning.
Optimization.
Basis Carrier.
Type Gauge.
4-54 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_TCH_DCS1800
BUSY_TCH_DCS1800
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
Description
It is used in conjunction 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 utilisation figures to indicate
band related traffic distribution within the cell for optimization of the IMRM band weightings.
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-R 4-55
BUSY_TCH_EGSM Chapter 4: Cell statistics
BUSY_TCH_EGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
Description
It is used in conjunction 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 utilisation figures to indicate band
related traffic distribution within the cell for optimization of the IMRM band weightings.
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
Basis Cell.
Type Gauge.
4-56 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_TCH_HR
BUSY_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The BUSY_TCH_HR statistic replaces BUSY_TCH_HR_AMR.
Description
TCH{24349} or VGC channels in use.
Pegging
This statistic is updated each time an allocation or deallocation of a half rate AMR and/or GSM TCH{24349}
or VGC channel occurs.
Reference None.
Network planning.
Basis Cell.
68P02901W56-R 4-57
BUSY_TCH_PGSM Chapter 4: Cell statistics
BUSY_TCH_PGSM
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22404}
Description
It is used in conjunction 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 utilisation figures to indicate band
related traffic distribution within the cell for optimization of the IMRM band weightings.
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
Basis Cell.
Type Gauge.
4-58 68P02901W56-R
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 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.

0 EFR_REQUEST_DOWNGRADE Pegged when the call is downgraded due
to CIC capabilities:Assignment request for
or including EFRHandover 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:

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 above.
{24349} The BSS triggers if the CIC capability request mechanism for a VGCS request results in a speech
version downgrade, pegs the existing CALL_SP_VERS_DOWNGRADE_MONITOR statistic.
68P02901W56-R 4-59
CALL_SP_VERS_DOWNGRADE_MONITOR Chapter 4: Cell statistics
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

Network planning.
Optimization.
Basis BSS.
Type Counter array.
4-60 68P02901W56-R
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 queueing is enabled for an assignment request and available queue blocks are used
to queue the call successfully. {24349} The bins pegged according to the assignment request type are
as shown in Table 4-4.
Table 4-4 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.
2 VGCS_VBS_ASSIGN_REQ The number of VGCS/VBS ASSIGNMENT
REQUEST messages that are queued.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of calls queued for
each cell on the BSS that are acceptable in normal system operations.
68P02901W56-R 4-61
CALLS_QUEUED Chapter 4: Cell statistics
If the specified threshold is exceeded, the 20. CELL: Number of calls queued - PM alarm will be
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.
Ladder: BSS initiated call clearing.
Basis Cell.
Type {24349} Counter array.
Alarm Warning.
4-62 68P02901W56-R
Maintenance Information: GSM Statistics Application CHAN_REQ_CAUSE_ATMPT
CHAN_REQ_CAUSE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_REQ_CAUSE_ATMPT statistic tracks the number of Channel Request messages received by
the network from a MS (or LMU) by cause. A total count of all successful results is also tracked.

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 a 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 used to determine the requirement for additional resources
Reference GSM 12.04, 4.21, B.2.1.6.

GSM 4.08, v4.15.0, 9.1.8.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-63
CHAN_REQ_MS_BLK Chapter 4: Cell statistics
CHAN_REQ_MS_BLK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHAN_REQ_MS_BLK statistic tracks the number of times a 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 will not be 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
will be impossible for the MS to initiate a call. Handover of calls may be prevented. This will result 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 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
Basis Cell.
Type Counter.
4-64 68P02901W56-R
Maintenance Information: GSM Statistics Application CIPHER_MODE_FAIL
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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 - PM alarm
will be generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
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.
Fault finding.
Ladder: BSS initiated call clearing.
Basis Cell.
Type Counter.
Alarm Minor.
68P02901W56-R 4-65
CLASSMK_UPDATE_FAIL Chapter 4: Cell statistics
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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 error - PM
alarm is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26)
for troubleshooting information.
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.
4-66 68P02901W56-R
Maintenance Information: GSM Statistics Application CLR_CMD_FROM_MSC
CLR_CMD_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commands received from the
MSC for SDCCH, TCH and {24349} VGCS resources thereby allowing the analysis of dropped calls.
{24349} The CLR_CMD_FROM_MSC[VGCS] bin represents the number of CLEAR COMMAND
messages received from the MSC for VGCS resources.
Pegging
This statistic pegs when a Clear command is received from the MSC.

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.
3 {24349} Counts the number of clear commands received
CLR_CMD_FROM_MSC_VGCS from the MSC for VGCS resources.
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.
Fault finding.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-67
CLR_REQ_TO_MSC Chapter 4: Cell statistics
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, TCH and {24349} VGCS 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 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 GSM and internal Motorola timers.
Normal release of a call either from a MS or Land site never cause it to be pegged. A call must have at least
been assigned to an SDCCH or TCH in order for this to be pegged. It is not pegged when on an AGCH
overload. RF loss is the major cause of pegging.
4-68 68P02901W56-R
Maintenance Information: GSM Statistics Application CLR_REQ_TO_MSC

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.
3 {24349} CLR_REQ_TO_MSC_VGCS Counts the number of clear requests sent to the
MSC for VGCS resources.
CLR_REQ_TO_MSC is not pegged when the CONN_REFUSED statistic is pegged. However, there
are a number of 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.
Adding up the statistics in the ladder diagrams will not

total CLR_REQ_TO_MSC.
Basis Cell.
Type Counter array.
68P02901W56-R 4-69
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 handovers (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 handovers 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-70 68P02901W56-R
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 a 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-R 4-71
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 re-establishment.
For example, if an association already exists for the identity of the MS requesting a connection, the connection
request is refused, and this statistic pegs.
Analyse MSC statistics to determine why the CONN_REFUSED statistic is pegged.
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 may not indicate a
system problem. The MSC performance during IMSI Detach procedures should be investigated
before interpreting the CONN_REFUSED statistic.
4-72 68P02901W56-R
Maintenance Information: GSM Statistics Application CONN_REFUSED
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-R 4-73
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 re-establishment 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-74 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_LLC_DATA_VOLUME
DL_LLC_DATA_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The DL_LLC_DATA_VOLUME statistic counts the volume of downlink LLC data sent on the air interface
per traffic class during a given time interval.
10 kilobytes = 1 unit.
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-5.
68P02901W56-R 4-75
DL_LLC_DATA_VOLUME Chapter 4: Cell statistics
Table 4-5 DL_LLC_DATA_VOLUME bins
Bin Description
0 THP1, ARP1
1 THP1, ARP2
2 THP1, ARP3
3 THP2, ARP1
4 THP2, ARP2
5 THP2, ARP3
6 THP3, ARP1
7 THP3, ARP2
8 THP3, ARP3
9 Background, ARP1
10 Background, ARP2
11 Background, ARP3
12 Best Effort, ARP1
• 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, ARP3. PFC_unaware
PFC data is pegged against the Best Effort bins.
• Downlink PAP, SMS and Signalling LLC data will not be pegged.
The recommended statistical measurement interval is 30 minutes.
Analysis
Reference None.
Usage GPRS Quality of Service.
Basis Cell.
Type Counter array.
4-76 68P02901W56-R
Maintenance Information: GSM Statistics Application ER_INTRA_CELL_HO_ATMPT
ER_INTRA_CELL_HO_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ER_INTRA_CELL_HO_ATMPT statistics 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.
Bin Procedures Description

0 NORM_TO_EXT_HO Number of intra-cell handover attempts from
normal range channels to extended range channels.
1 EXT_TO_NORM_HO Number of intra-cell handover attempts from
extended range channels to 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 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 timeslots to configure in an extended range cell.
Reference None.
Network planning.
Radio resource allocation.
Basis Cell.
Type Counter array.
68P02901W56-R 4-77
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 attempted handover is
also maintained.
This statistic may be enabled only if the Extended Range Cell feature is unrestricted and enabled for the cell.

0 NORM_TO_EXT_HO Number of successful intra-cell handovers from
normal range channels to extended range channels.
1 EXT_TO_NORM_HO Number of successful intra-cell handovers from
extended range channels to 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 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 timeslots to configure in an extended range cell.
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-78 68P02901W56-R
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-R 4-79
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.
Bin Scenario Description

0 INTRA_BSS Number of intra-BSS handover failures due to a
lack of available resources.
1 INTER_BSS Number of inter-BSS handover failures due to a
lack of available resources.
2 INTRA_CELL Number of intra-cell handover failures due to a lack
of available resources.
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
resources.
5 INTRA_CELL_DYNET Number of BTS Dynamic Allocation intra-cell
resources.
Pegging
These individual bins are incremented on a per scenario basis.
4-80 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_FAIL_NO_RESOURCES
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.
Reference Metrica.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-81
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.
The bins are:
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:
Bin Procedure
6 PM_GSM_HR
Pegging
This statistic pegs the handover request for each channel type and speech version speech version in the
appropriate bin.
Reference GSM 8.08.

Quality of service monitoring: Call setup.
Network planning.
Ladder: TCH assignment successful, TCH assignment
fail-recovered to SDCCH, TCH assignment blocked.
Basis Cell.
Type Counter array.
4-82 68P02901W56-R
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
A threshold value should be assigned to this statistic which reflects the maximum number of handover failures
for any reason other than lack of channel resources that are acceptable in normal system operations.
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 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.
Ladder: Handover (Inter-BSS) blocked.
Basis Cell.
Type Counter.
Alarm Warning.
68P02901W56-R 4-83
HO_REQ_MSC_FAIL Chapter 4: Cell statistics
HO_REQ_MSC_FAIL can be equal to INTER_BSS_MS_FAIL if the cell has never been

the target for a failed handover.
4-84 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_REQ_ACK_TO_MSC
HO_REQ_ACK_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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.

0 PM_FR Counts the number of full rate handover
request acknowledgements sent to the MSC.
1 PM_EFR Counts the number of enhanced full rate
handover request acknowledgements 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 acknowledgments sent to
the MSC.
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:
Bin Procedure Description

6 PM_GSM_HR Counts the number of GSM half rate
handover request acknowledgments sent to
the MSC.
68P02901W56-R 4-85
HO_REQ_ACK_TO_MSC Chapter 4: Cell statistics
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.
4-86 68P02901W56-R
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.
Idle TCHs are allocated to five interference bands. Each band has an associated statistic
for tracking idle TCHs.
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-R 4-87
IDLE_TCH_INTF_BAND1 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
4-88 68P02901W56-R
IDLE_TCH_INTF_BAND2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-R 4-89
IDLE_TCH_INTF_BAND3 Chapter 4: Cell statistics
IDLE_TCH_INTF_BAND3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
4-90 68P02901W56-R
IDLE_TCH_INTF_BAND4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-R 4-91
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.
A total value for this statistic is not meaningful and is not displayed.

0 IN_INTER_BSS_HO_SUC 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.

Network planning.
Fault finding.
Handover.
Basis Cell.
Type Counter array.
4-92 68P02901W56-R
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.

0 IN_INTRA_BSS_HO_SUC 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
handover procedure.
Pegging
These individual bins are incremented on a per scenario basis.
68P02901W56-R 4-93
IN_INTRA_BSS_HO Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of incoming intra-BSS handover procedures on a per scenario basis.
Reference Metrica.
GSM 8.08, 3.9.2, 3.1.7, 3.1.5.2.1, 3.2.1.12.
Network planning.
Fault finding.
Handover.
Basis Cell.
Type Counter array.
4-94 68P02901W56-R
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.

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.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-95
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.

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 intra-cell handover.
3 INTRA_CELL_HO_ATMPT_HR_FR Number of assignment commands sent to MS
during a half-rate to full-rate intra-cell handover.
4 INTRA_CELL_HO_ATMPT_FR_HR Number of assignment commands sent to MS
during a full-rate to half-rate intra-cell handover.
5 INTRA_CELL_HO_SUC Number of successful intra-cell handovers.
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
9 INTRA_CELL_HO_CLEARED Number of incoming intra-cell handovers aborted
handover procedure.
4-96 68P02901W56-R
Maintenance Information: GSM Statistics Application INTRA_CELL_HO
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.
The intracell handover bin pegged depends on the speech rate involved and may include the change
of speech rate, which subsequently 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.
Analysis
This statistic can be used for trend analysis of intra-cell handovers on a per scenario basis.
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.
Network planning.
Fault finding.
Basis Cell.
Type Counter array.
68P02901W56-R 4-97
MA_CMD_TO_MS Chapter 4: Cell statistics
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.
fail-recovered to SDCCH, handover (Intra-cell) successful,
handover (Intra-cell) fail-recovered, handover (Intra-cell) fail-lost.
Basis Cell.
Type Counter.
4-98 68P02901W56-R
Maintenance Information: GSM Statistics Application MA_COMPLETE_FROM_MS
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.
68P02901W56-R 4-99
MA_COMPLETE_TO_MSC Chapter 4: Cell statistics
MA_COMPLETE_TO_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MA_COMPLETE_TO_MSC statistic tracks the number of successful assignment completions for each
channel and speech version.

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
to the MSC.
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:

6 PM_GSM_HR Counts the number of GSM half rate
to the MSC.
Pegging
This statistic pegs when the Assignment Complete message from the MS is forwarded on to the MSC.
4-100 68P02901W56-R
Maintenance Information: GSM Statistics Application MA_COMPLETE_TO_MSC
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.
68P02901W56-R 4-101
MA_FAIL_FROM_MS Chapter 4: Cell statistics
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 signalling 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 - PM alarm

GSM 12.07, 3.0.2, 2.8.6.c.
GSM 4.08, 3.8.0, 3.4.3.3 and 9.1.4.
Fault finding.
Ladder: TCH assignment fail-recovered to SDCCH, handover
(Intra-cell) fail-recovered.
Basis Cell.
Type Counter.
Alarm Warning.
4-102 68P02901W56-R
Maintenance Information: GSM Statistics Application MA_REQ_FROM_MSC
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.
The bins are:

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
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:

6 PM_GSM_HR Counts the number of GSM half rate assignment
Pegging
This statistic pegs the radio resource request for each preferred speech version made to a BSS by the MSC.
68P02901W56-R 4-103
MA_REQ_FROM_MSC Chapter 4: Cell statistics
Analysis
This statistic can be used for trend analysis of MSC request to the BSS to allocate radio resources.

Network planning.
fail-recovered to SDCCH, TCH assignment blocked.
Basis Cell.
Type Counter array.
4-104 68P02901W56-R
Maintenance Information: GSM Statistics Application MA_CMD_TO_MS_BLKD
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 mobile station) as there
were no traffic channels available at the cell due to congestion.
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.
If queueing is enabled the statistic is pegged when the BSS queueing related timer bss_t11 expires. If the BSS
assignment_successful timer is set shorter than the BSS bssmap_t11 timer then this statistic will not be pegged.
It is recommended that the assignment_successful timer be always set greater than the bssmap_t11 timer.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of times traffic
channels that may be congested due to a lack of radio resources that are acceptable in normal system
operations.
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 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.
Alarm Minor.
68P02901W56-R 4-105
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.
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 whilst in dedicated mode. {24349} When the VGCS allocation mechanism is active, the
MS_ACCESS_BY_TYPE statistic is pegged when a NOTIFICATION MESSAGE is received from a MS
(based on the frequency capabilities derived from the Mobile station classmark 2) and when an IMMEDIATE
SETUP or IMMEDIATE SETUP 2 message (used to request a VGCS) is received.
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-106 68P02901W56-R
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.
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-R 4-107
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.
Bin Description
0 GSM850 only capable mobiles.
1 DCS1800-PCS1900 capable mobiles.
2 PGSM-DCS1800-PCS1900 capable mobiles.
3 PGSM-EGSM-DCS1800-PCS1900 capable mobiles.
4 PGSM-GSM850 capable mobiles.
5 PGSM-EGSM-GSM850 capable mobiles.
6 GSM850-DCS1800 capable mobiles.
7 PGSM-GSM850-DCS1800 capable mobiles.
8 PGSM-EGSM-GSM850-DCS1800 capable mobiles.
9 GSM850-PCS1900 capable mobiles.
10 PGSM-GSM850-PCS1900 capable mobiles.
11 PGSM-EGSM-GSM850-PCS1900 capable mobiles.
12 GSM850-PCS1900-DCS1800 capable mobiles.
13 PGSM-GSM850-PCS1900-DCS1800 capable mobiles.
14 PGSM-EGSM-GSM850-PCS1900-DCS1800 capable mobiles.
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-108 68P02901W56-R
Maintenance Information: GSM Statistics Application MS_TCH_USAGE_BY_TYPE_PCS
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-R 4-109
MT_LCS_ON_SDCCH Chapter 4: Cell statistics
MT_LCS_ON_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of mobile-terminated SDCCH sessions for Location Services.
The statistic has been introduced to allow the Call Setup Success Rate key statistic (see Chapter
17) to work following the introduction of the Location Services feature.
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. 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).
Reference GSM 03.71 v7.4.0.

Usage Fault finding.
Basis Cell.
Type Counter.
4-110 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_CELL_RESEL_CELL
NUM_CELL_RESEL_CELL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
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.
1 unit represents 10 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-6 shows the scenarios used to
update the counter bins associated with this statistic. The corresponding per neighbour statistics are pegged
using a separate counter: "NUM_CELL_RESEL_NEI" on page 5-11.
Table 4-6 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.
68P02901W56-R 4-111
NUM_CELL_RESEL_CELL_PCCN Chapter 4: Cell statistics
NUM_CELL_RESEL_CELL_PCCN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
Description
The NUM_CELL_RESEL_CELL_PCCN statistic measures the total number of PCCN requests by MSs.
1 unit represents 10 attempts by a 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 neighbour statistics are pegged using a separate counter:
"NUM_CELL_RESEL_NEI_PCCN" on page 5-12.
Analysis
Reference None.
Basis Cell.
Type Counter.
4-112 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_CELL_RESEL_CELL_SUCC
NUM_CELL_RESEL_CELL_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
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 (also in a 3x PCU environment).

1 unit represents 10 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 neighbour statistics are pegged
using a separate counter: "NUM_CELL_RESEL_NEI_SUCC" on page 5-13.
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-R 4-113
NUM_EMERG_ACCESS Chapter 4: Cell statistics
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.
4-114 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_EMERG_REJECTED
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 pre-empted 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.
68P02901W56-R 4-115
NUM_EMERG_TCH_KILL Chapter 4: Cell statistics
NUM_EMERG_TCH_KILL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NUM_EMERG_TCH_KILL statistic tracks the number of times a call is lost due to emergency call
pre-emption 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 pre-empted 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 pre-emption 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 pre-emption only.
Network planning.
Basis Cell
Type Counter.
4-116 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_EMERG_TERM_SDCCH
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.
68P02901W56-R 4-117
NUM_HO_3G_ATTEMPTS Chapter 4: Cell statistics
NUM_HO_3G_ATTEMPTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
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.
4-118 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_HO_FROM_3G_ATTEMPTS
NUM_HO_FROM_3G_ATTEMPTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Description
The NUM_HO_FROM_3G_ATTEMPTS statistic counts the number of handover attempts made into a
2G Cell from a 3G network.
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.
68P02901W56-R 4-119
NUM_HO_FROM_3G_SUCCESS Chapter 4: Cell statistics
NUM_HO_FROM_3G_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Description
The NUM_HO_FROM_3G_SUCCESS statistic counts the number of successful handovers made into a
Pegging
The BSS pegs the NUM_HO_FROM_3G_SUCCESS statistic whenever a successful handover is made into a
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
4-120 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_HO_TO_3G_RES_ALLOC_SUCC
NUM_HO_TO_3G_RES_ALLOC_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
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.
68P02901W56-R 4-121
NUM_HO_TO_3G_SUCCESS Chapter 4: Cell statistics
NUM_HO_TO_3G_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Description
The NUM_HO_TO_3G_SUCCESS statistic counts the number of successful handovers made into a
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.
4-122 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_MULTIRAT_MS_ORIG_CALL
NUM_MULTIRAT_MS_ORIG_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Description
The NUM_MULTIRAT_MS_ORIG_CALL counts the number of times a mobile reports that it is 3G capable.
Pegging
The BSS pegs the NUM_MULTIRAT_MS_ORIG_CALL statistic after receiving a 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.
68P02901W56-R 4-123
NUM_T3121_EXPIRY Chapter 4: Cell statistics
NUM_T3121_EXPIRY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Description
The NUM_T3121_EXPIRY statistic counts number of times a channel at the BSS is released before receiving
a CLEAR_COMMAND from MSC for an attempted handover to a 3G network.
Pegging
The BSS pegs the NUM_T3121_EXPIRY statistic whenever the T3121 timer expires during the handover
to UTRAN procedures on the GSM air interface.
Analysis
Reference None.
Usage Handover.
Basis Cell.
Type Counter.
4-124 68P02901W56-R
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.

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.
11 {24349} CM_SERV_REQ_VGCS Number of MS requests for VGCS.
12 {24349} CM_SERV_REQ_VBS Number of MS requests for VBS.
13 {24349} IMM_SETUP Number of MS requests for VGCS.
14 {24349} IMM_SETUP_2 Number of MS requests for VGCS.
15 {24349} NOTIF_RESP Number of MS requests for triggering of the
Notification Response mechanism.
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-R 4-125
OK_ACC_PROC Chapter 4: Cell statistics
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: RF_LOSS_RATE, SDCCH_MEAN_HOLD-
ING_TIME, , SDCCH_RF_LOSS_RATE.
Basis Cell.
4-126 68P02901W56-R
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 a 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 dialled 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.
Basis Cell.
Type Counter.
68P02901W56-R 4-127
OUT_HO_CAUSE_ATMPT Chapter 4: Cell statistics
OUT_HO_CAUSE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_HO_CAUSE_ATMPT statistic tracks the number of handover attempts per cell per cause. The
handover attempts include cases involving outgoing inter-cell handovers.

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.
Cont.
4-128 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_HO_CAUSE_ATMPT

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.
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-R 4-129
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. A total value for this statistic is not meaningful and is not displayed.

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_EQUIP_FAIL Number of {22103} CLRCMD “equipment failure”
messages in one interval.
6 OUT_INTER_BSS_HO_CLEARED Number of outgoing inter-BSS handovers aborted
due to call clearing {22103} 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 {22103} OUT_INTER_BSS_HO_FAIL Number of CLRCMD “radio interface message
failure” messages.
Pegging
OUT_INTER_BSS_REQ_TO_MSC is pegged each time a handover required message is sent to the MSC.
OUT_INTER_BSS_HO_ATMPT is pegged when the handover command is forwarded to the MS.
OUT_INTER_BSS_HO_SUC is pegged when a clear command message is received.
OUT_INTER_BSS_HO_LOSTMS is pegged if a clear command is not received from the MSC and no
handover failure message is received either.
OUT_INTER_BSS_HO_RETURN is pegged each time an unsuccessful handover message is received.
OUT_INTER_BSS_EQUIP_FAIL is pegged if the MS returns {22103} a case of equipment failure in
the handover failure message.
OUT_INTER_BSS_HO_CLEARED is pegged when a call is cleared down during an inter-BSS handover.
4-130 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO
{22103} OUT_INTER_BSS_HO_FAIL is pegged if the MS returns a case of radio interface failure in

the handover failure message.
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.
Basis Cell.
Type Counter array.
68P02901W56-R 4-131
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.

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
needed.
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
7 OUT_INTRA_BSS_HO_CLEARED Number of outgoing intra-BSS handovers aborted
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-132 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_INTRA_BSS_HO
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.
Basis Cell.
Type Counter array.
68P02901W56-R 4-133
PACKET_SYSINFO_REQ Chapter 4: Cell statistics
PACKET_SYSINFO_REQ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24303}
Description
The PACKET_SYSINFO_REQ statistic tracks MS requests for BCCH/PBCCH GPRS system information on
a per-cell basis.
Pegging
The BSS will peg 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 will be pegged. The bin
definitions are shown in Table 4-7.
Table 4-7 PACKET_SYSINFO_REQ bins
Bin Description
0 Valid normal PACKET SI STATUS message or valid normal PACKET
PSI STATUS message received from the mobile. 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 mobile. 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 mobile cannot handle BSS response messages
(for example, abnormal release of a mobile’s TBFs or mobile changes
serving cells)].
3 Valid PACKET SI STATUS message or valid PACKET PSI STATUS
message received from the mobile requesting GPRS system information
changemarks.
4-134 68P02901W56-R
Maintenance Information: GSM Statistics Application PACKET_SYSINFO_REQ
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-R 4-135
PACKET_SYSINFO_RESP Chapter 4: Cell statistics
PACKET_SYSINFO_RESP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24303}
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 will peg the PACKET_SYSINFO_RESP statistic for each RLC/MAC block sent in response to a MS
request for PBCCH/BCCH GPRS system information.
Each PACKET SI/PSI STATUS request will generate zero or more response messages.
For a given downlink control message, only one bin in the counter array will be pegged. The bin definitions
are shown in Table 4-8.
Table 4-8 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 Unencapsulated PSI message scheduled in response to a PACKET PSI
STATUS message.
2 PSI1 or PSI13 message scheduled in response to a 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
4-136 68P02901W56-R
Maintenance Information: GSM Statistics Application PAGE_REQ_FROM_MSC
PAGE_REQ_FROM_MSC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PAGE_REQ_FROM_MSC statistic tracks the number of paging requests received from the MSC.
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 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.
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.
Basis Cell.
Type Counter.
68P02901W56-R 4-137
PAGING_REQUESTS Chapter 4: Cell statistics
PAGING_REQUESTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic accounts for any message making use of a PCH block. This statistic is similar to
PCH_Q_PAGE_DISCARD except the messages are sent, not discarded. This statistic is obtained by
measuring the number of paging requests received from the network for transmission on the PCH.
The bins are:

0 PAGING_REQS_TOT Number of Paging requests received to be
transmitted on the PCH.
1 PAGING_REQS_CS Number of Paging requests received to be
transmitted on the CS .
2 PAGING_REQS_PS Number of Paging requests received to be
transmitted on the PS.
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 Reference Digital cellular telecommunications systems (phase 2+)

Version 7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Counter array.
4-138 68P02901W56-R
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-R 4-139
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 queuing is
in operation) for a number of 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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-140 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_ADMISSION
PFC_ADMISSION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 will depend on the traffic class / traffic handling priority and the ARP
value of the PFC as shown in Table 4-9.
68P02901W56-R 4-141
PFC_ADMISSION Chapter 4: Cell statistics
Table 4-9 PFC_ADMISSION bins
Bin Description
0 THP1, ARP1
1 THP1, ARP2
2 THP1, ARP3
3 THP2, ARP1
4 THP2, ARP2
5 THP2, ARP3
6 THP3, ARP1
7 THP3, ARP2
8 THP3, ARP3
9 Background, ARP1
10 Background, ARP2
11 Background, ARP3
• When ARP is disabled, all successful admissions will be pegged against ARP3.
• When QoS is disabled, no bins are pegged.
• PFC-unaware PFCs for data transfer will be pegged as Best Effort (bins 12-14).
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-142 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_ADMISSION_OTHER
PFC_ADMISSION_OTHER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The PFC_ADMISSION_OTHER statistic counts the number of successful admissions of SMS, Signalling or
PFC_unaware PFCs.
Pegging
The PFC_ADMISSION_OTHER statistic is pegged every time an admission of a SMS, Signalling or
PFC_unaware PFC is successful. The bin pegged will depend on the PFC type as shown in Table 4-10.
Table 4-10 PFC_ADMISSION_OTHER bins
Bin Description
0 SMS
1 Signalling
2 PFC_unaware
• If a PFC_unaware mobile arrives in the downlink first, with downlink data tagged with PFI
= 0, the BSS cannot peg its admission with the PFC_unaware bin (bin 2). Instead, the
PFC_ADMISSION statistic will peg the Best Effort bin.
• PFC-unaware PFCs for signalling will be pegged as Signalling (bin 1).
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-143
PFC_DOWNGRADE_FAILURE Chapter 4: Cell statistics
PFC_DOWNGRADE_FAILURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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
will depend on the traffic handling priority in ABQP and ARP value of the PFC a shown in Table 4-11.
Table 4-11 PFC_DOWNGRADE_FAILURE bins
Bin Description
0 Downgrade from THP1 to THP2, ARP1
• When ARP is disabled, all downgrade successes are pegged against ARP3.
4-144 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_DOWNGRADE_FAILURE
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-145
PFC_DOWNGRADE_SUCCESS Chapter 4: Cell statistics
PFC_DOWNGRADE_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 will depend on the traffic handling priority in ABQP and ARP value of the
PFC a shown in Table 4-12.
Table 4-12 PFC_DOWNGRADE_SUCCESS bins
Bin Description
• When ARP is disabled, all downgrade successes are pegged against ARP3.
4-146 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_DOWNGRADE_SUCCESS
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-147
PFC_PREEMPTIONS Chapter 4: Cell statistics
PFC_PREEMPTIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The PFC_PREEMPTIONS statistic counts the number of PFCs preempted in each traffic class, for each
ARP value.
Pegging
The PFC_PREEMPTIONS statistic is pegged every time PFCs are preempted due to admission control or
retention procedures. The bin pegged will depend on the traffic class as shown in Table 4-13.
4-148 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_PREEMPTIONS
Table 4-13 PFC_PREEMPTIONS bins
Bin Description
0 Preemption of THP1, ARP1
9 Preemption of Background, ARP1
12 Preemption of Best Effort, ARP1
• Preemption of PFC_unaware PFCs is pegged against the bins for Best Effort PFCs.
• When ARP is disabled, all preemptions 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
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-149
PFC_REJ_DGRD_PRMPT_CELL Chapter 4: Cell statistics
PFC_REJ_DGRD_PRMPT_CELL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 preemptions due to cell or PRP retentions on a per cell basis.
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-14 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-14 PFC_REJ_DGRD_PRMPT_CELL bins
Bin Cause Description of cause Remedial action

0 Rejection due to lack The PCU does not have enough MTBR Increase the number of GPRS
of cell resources. in the cell to admit a PFC. timeslots in the cell.
1 Rejection due to lack The PCU does not have enough MTBR Adjust the MTBR
of PRP resources. in the board to admit a PFC. commitments for different
traffic classes.
2 Downgrade due to The PCU does not have enough MTBR Adjust the MTBR
lack of cell resources. in the cell to maintain a PFC’s current commitments for different
commitment and has reduced the PFC’s traffic classes.
MTBR due to the admission of a higher
priority PFC.
lack of PRP resources. on the PRP to maintain a PFC’s current commitments for different
priority PFC.
4 Preemption due to The PCU does not have enough Adjust the MTBR
lack of cell resources. MTBR in the cell to maintain a PFC’s commitments for different
commitments due to a change in traffic classes.
available resources or admission of a
higher priority PFC and has preempted
the PFC.
Cont.
4-150 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_REJ_DGRD_PRMPT_CELL
Table 4-14 PFC_REJ_DGRD_PRMPT_CELL bins (Continued)

5 Preemption due to The PCU does not have enough MTBR Adjust the MTBR
lack of PRP resources. on the PRP to maintain a PFC’s commitments for different
commitments due to admission of a traffic classes.
the PFC.
6 Downgrade due to cell The PCU does not have enough MTBR Increase the resources in the
retention. in the cell to retain all the active PFC’s 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 on the
PRP retention. on the PRP to retain all the active PFC’s PRP.
MTBR for PRP retention purposes.
8 Preemption due to cell The PCU does not have enough Increase the resources in the
retention. MTBR in the cell to maintain a PFC’s cell.
shrinkage and has preemepted the PFC
for cell retention purposes.
9 Preemption due to The PCU does not have enough MTBR Increase the resources on the
PRP retention. on the PRP to maintain a PFC’s PRP.
for PRP retention purposes.
Bins 7 and 9 are not pegged.
Analysis
Reference None.
Usage GPRS Quality of Service
Basis Cell.
Type Counter array.
68P02901W56-R 4-151
PFC_REJECT_CAUSES Chapter 4: Cell statistics
PFC_REJECT_CAUSES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The PFC_REJECT_CAUSES statistic counts the number of PFC requests rejected by the PCU due to a
lack of resources.
Pegging
The PFC_REJECT_CAUSES statistic is pegged whenever PCU rejects a PFC request due to a lack of
resources. The bin pegged will depend on the problem resource. Table 4-15 describes the causes for rejection
and the action the operator can take to reduce the number of PFC rejections in the future.
Table 4-15 PFC_REJECT_CAUSES bins

0 Maximum PFCs per Other than the pre-defined PFCs, the Reduce the number of
MS exceeded. BSS supports up to 4 negotiable PFCs simultaneous negotiable
simultaneously for each mobile. Any PFCs a mobile is trying to
subsequent negotiable PFC requests activate.
from that mobile will be rejected under
this limitation.
1 Out of TBF resources The PCU does not have all TBF
for THP1. resources required to service the TBF
for the requested THP/traffic class; this
includes timeslot availability, USFs,
TAIs, and TFIs.
TAIs, and TFIs.
TAIs, and TFIs.
Cont.
4-152 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_REJECT_CAUSES
Table 4-15 PFC_REJECT_CAUSES bins (Continued)

for Background. resources required to service the TBF
TAIs, and TFIs.
for Best Effort. resources required to service the TBF
TAIs, and TFIs.
for SMS. resources required to service the TBF
TAIs, and TFIs.
for Signalling. resources required to service the TBF
TAIs, and TFIs.
for PAP. resources required to service the TBF
TAIs, and TFIs.
for PFC_unaware. resources required to service the TBF
TAIs, and TFIs.
10 Out of PFC storage. The PCU has exhausted storage for Reduce the duration of
PFCs. Packet Flow Timer at the
SGSN.
11 MS Capability. The PCU cannot meet the MTBR for Decrease the MTBRs or
the requested PFC. increase the capacity of the
mobile.
When QoS is disabled, no bins are pegged.
68P02901W56-R 4-153
PFC_REJECT_CAUSES Chapter 4: Cell statistics
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-154 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_REJECTION
PFC_REJECTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The PFC_REJECTION statistic counts the number of unsuccessful admissions of a PFC.
Pegging
The PFC_REJECTION statistic is pegged every time an admission of a negotiable or Best Effort PFC is
unsuccessful. The bin pegged will depend on the traffic class / traffic handling priority and the ARP value of
the PFC as shown in Table 4-16.
68P02901W56-R 4-155
PFC_REJECTION Chapter 4: Cell statistics
Table 4-16 PFC_REJECTION bins
Bin Description
0 THP1, ARP1
1 THP1, ARP2
2 THP1, ARP3
3 THP2, ARP1
4 THP2, ARP2
5 THP2, ARP3
6 THP3, ARP1
7 THP3, ARP2
8 THP3, ARP3
9 Background, ARP1
10 Background, ARP2
11 Background, ARP3
• When ARP is disabled, all unsuccessful admissions will be pegged against ARP3.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-156 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_REJECTION_OTHER
PFC_REJECTION_OTHER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The PFC_REJECTION_OTHER statistic counts the number of unsuccessful admissions of SMS, Signalling
or PFC_unaware PFCs.
Pegging
The PFC_REJECTION_OTHER statistic is pegged every time an admission of a SMS, Signalling or
PFC_unaware PFC is unsuccessful. The bin pegged will depend on the PFC type as shown in Table 4-17.
Table 4-17 PFC_REJECTION_OTHER bins
Bin Description
0 SMS
1 Signalling
2 PFC_unaware
If a PFC_unaware mobile arrives in the downlink first, with downlink data tagged with
PFI = 0, the BSS cannot peg its rejection with the PFC_unaware bin (bin 2). Instead, the
PFC_REJECTION statistic will peg the Best Effort bin.
When QoS is disabled, no bins are pegged.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-157
PFC_UPGRADE Chapter 4: Cell statistics
PFC_UPGRADE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 will depend on the traffic
handling priority in the ABQP and ARP value of the PFC as shown in Table 4-18.
Table 4-18 PFC_UPGRADE bins
Bin Description
0 Upgrade from THP2 to THP1, ARP1
• When ARP is disabled, all upgrades will be pegged against ARP3.

4-158 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_UPGRADE
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-159
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.
The bins are:
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.
Reference GSM 12.04, 4.2.1, B.2.1.8

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

0 VGCS A VGCS/VBS ASSIGNMENT REQUEST
which has PCI=1.
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-R 4-161
QUEUE_PREEMPT_ATMPT Chapter 4: Cell statistics
QUEUE_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The QUEUE_PREEMPT_ATMPT statistic tracks the number of times the Queuing pre-emption 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 3 bins which are pegged depending on the type of
service being removed from the queue due to pre-emption. Details are shown in Table 4-20.
Table 4-20 QUEUE_PREEMPT_ATMPT bins

0 ASSIGN_REQ The number of queued ASSIGNMENT
REQUESTs removed from the queue due to
pre-emption.
1 HO_REQ The number of queued HANDOVER
REQUESTs removed from the queue due to
pre-emption.
2 VGCS_VBS_ASSIGN_REQ The number of queued VGCS/VBS
ASSIGNMENT REQUESTs removed from
the queue due to pre-emption.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-162 68P02901W56-R
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 a SDCCH. If a TCH is reconfigured
as a SDCCH, only the SDCCH statistics are configured.
Pegging
This statistic pegs the number of calls that were terminated because of RF problems. This statistic will
only peg for lost calls after the call has been established. This statistic will not be pegged when the
CHAN_REQ_MS_FAIL statistic is pegged.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of lost calls while
using a SDCCH that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. CELL: Radio frequency losses while using an SDCCH - PM
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 statistic: RF_LOSS_RATE, SDCCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.
Alarm Major.
68P02901W56-R 4-163
RF_LOSSES_TCH Chapter 4: Cell statistics
RF_LOSSES_TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_LOSSES_TCH statistic tracks the number of calls lost while using a full rate or half rate TCH.
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
This statistic pegs the number of full rate and half rate calls that were terminated because of RF problems.
It is composed of calls lost while using a TCH. If a TCH is reconfigured as an SDCCH, only the SDCCH
statistics are configured.
Analysis
using a TCH that are acceptable in normal system operations.
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 Statistic: RF_LOSS_RATE, TCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter.
Alarm Major.
4-164 68P02901W56-R
Maintenance Information: GSM Statistics Application RF_LOSSES_TCH
RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hopping
environment, this statistic may not be useful at channel level; therefore, roll to cell level.
68P02901W56-R 4-165
SDCCH_CONGESTION Chapter 4: Cell statistics
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.
4-166 68P02901W56-R
Maintenance Information: GSM Statistics Application SDCCH_HANDOVERs
SDCCH_HANDOVERs
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28014}
This functionality is currently not implemented in the GSR8 software load.
Description
The SDCCH_HANDOVER statistic measures SDCCH handover information and is used in the Call Setup
Success Rate key statistic calculation to address an issue where results calculated were greater than 100%.
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 a
SDCCH handover (outgoing inter BSS handover).
• A 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 a SDCCH handover
and will also keep a total of all of the bins. The bins are shown in Table 4-21.
Table 4-21 SDCCH_HANDOVER bins

0 OUT_IN- Outgoing intra BSS handover success.
TRA_BSS_HO_SUC
1 OUT_IN- Outgoing inter BSS handover success.
TER_BSS_HO_SUC
2 IN_IN- Incoming intra BSS handover success.
TRA_BSS_HO_SUC
3 IN_IN- Incoming inter BSS handover attempt.
TER_BSS_HO_ATTMPT
68P02901W56-R 4-167
SDCCH_HANDOVERs Chapter 4: Cell statistics
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-168 68P02901W56-R
Maintenance Information: GSM Statistics Application SECOND_ASSIGN_ATMPT
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.
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
68P02901W56-R 4-169
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.
Reference None.
Usage Congestion.
Basis Cell.
Type Counter.
4-170 68P02901W56-R
Maintenance Information: GSM Statistics Application SMS_INIT_ON_SDCCH
SMS_INIT_ON_SDCCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SMS_INIT_ON_SDCCH statistic tracks how many Short Message Service (SMS) transactions occurred
on a cell.
This statistic can be used to keep track of the number of times a Service Access Point (SAPI3) connection is
created, a SMS requires a logical SAPI3 connection. Additionally, the statistic can be used to determine how
SDCCHs are being used (for example, for SMS as opposed to location update).
Pegging
This statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.
Analysis
This statistic can be used for trend analysis of how many SMS transactions occurred on a cell.
Basis Cell.
Type Counter.
68P02901W56-R 4-171
SMS_INIT_ON_SDCCH_HO_IN Chapter 4: Cell statistics
SMS_INIT_ON_SDCCH_HO_IN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SMS_INIT_ON_SDCCH_HO_IN statistic tracks how many Service Access Point (SAP13) connections
are established over an SDCCH for Short Message Service (SMS) transactions during incoming handovers .
Pegging
This statistic is incremented on one successful Service Access Point (SAPI3) connection related to a SDCCH.
Analysis
This statistic can be used for trend analysis of how many SAP13 connections occurred on a cell.
Basis Cell.
Type Counter.
4-172 68P02901W56-R
Maintenance Information: GSM Statistics Application SMS_INIT_ON_SDCCH_HO_OUT
SMS_INIT_ON_SDCCH_HO_OUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{28014}
Description
The SMS_INIT_ON_SDCCH_HO_OUT statistic measures SDCCH handover information and is used

in the Call Setup Success Rate key statistic calculation to address an issue where results calculated were
greater than 100%.
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 a
SMS disconnection on an SDCCH handover-out and also keeps a total of all of the bins. The bins are
shown in Table 4-22.
Table 4-22 SMS_INIT_ON_SDCCH_HO_OUT bins

0 INTRA_CELL Intra cell handover
1 INTER_CELL Inter cell handover
Analysis
Reference None
Basis Cell.
Type Counter array.
68P02901W56-R 4-173
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, a 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.
Basis Cell.
Type Counter.
4-174 68P02901W56-R
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-R 4-175
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.
{24349} The BSS maintains a duration of the amount of time the cell is within congestion during a statistical
interval. This involves counting the idle channels within the cell, when a resources is allocated for VGCS
the congestion statistics need to be recalculated.
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-176 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_CONG_INNER_ZONE_HR
TCH_CONG_INNER_ZONE_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TCH_CONG_INNER_ZONE_HR statistic replaces

TCH_CONG_INNER_ZONE_HR_AMR.
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.
Reference None.
Network planning.
Basis Cell.
Type Duration.
68P02901W56-R 4-177
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 will only be used 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.
{24349} The BSS maintains a duration of the amount of time the cell is within congestion during a statistical
interval. This involves counting the idle channels within the cell, when a resource is allocated for VGCS
the congestion statistics need to be recalculated.
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 will be configured.
Reference GSM 12.04, 3.1.0, B.1.1.12

Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
{24349} This statistic pegs when a full rate VGC channel is allocated resulting in congestion.
4-178 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_CONGESTION_HR
TCH_CONGESTION_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The TCH_CONGESTION_HR statistic replaces TCH_CONGESTION_HR_AMR.
Description
The statistic tracks the duration of time when there are no half rate AMR and/or GSM TCH{24349} or
VGC 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 {24349} or VGC channel is allocated, a timer is
started. This timer is stopped when at least one half rate TCH {24349} or VGC channel becomes idle.
Reference None.
Network planning.
Basis Cell.
Type Duration.
68P02901W56-R 4-179
TCH_DELAY Chapter 4: Cell statistics
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 will be longer.
Queueing is only done if the assignment or Handover Request indicates that queueing is allowed for that
request. This statistic will measure the queueing 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 queueing 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: Queueing delay.
Network planning.
Optimization.
Basis Cell.
Type Normal distribution.
4-180 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_PREEMPT_ATMPT
TCH_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The TCH_PREEMPT_ATMPT statistic tracks the number of times the TCH pre-emption mechanism is
successful in finding and releasing resource(s) to satisfy a pre-empting request. A single pre-empting request
may pre-empt up to two active candidates to satisfy the incoming request. For example, a FR only request
pre-empts two HR candidates. The TCH_PREEMPT_ATMPT statistic also captures the service type of the
request causing the pre-emption and the service type(s) of the pre-empted candidates.
Pegging
The TCH_PREEMPT_ATMPT statistic is split into 4 bins which are pegged depending on the type of service
triggering the pre-emption and the type of service being pre-empted. Details are shown in Table 4-23.
Table 4-23 TCH_PREEMPT_ATMPT bins

0 CS-CS Point-to-point calls causing pre-emption of
point-to-point calls.
1 VGCS-CS Point-to-point calls causing pre-emption of
VGCS resources.
2 CS-VGCS VGCS requests causing pre-emption of
point-to-point calls.
3 VGCS-VGCS VGCS requests causing pre-emption of VGCS
resources.
• A VGCS resource may be a VGC channel or a TCH allocated to the talking/calling

subscriber. This applies to bin 1 and 3.
• A VGCS request may be a VGCS/VBS ASSIGNMENT REQUEST or a request related to
the talking/calling subscriber. This applies to bin 2 and 3.
68P02901W56-R 4-181
TCH_PREEMPT_ATMPT Chapter 4: Cell statistics
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
4-182 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_PREEMPT_FAIL_NO_CAND
TCH_PREEMPT_FAIL_NO_CAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The TCH_PREEMPT_FAIL_NO_CAND statistic tracks the number of times the TCH pre-emption
mechanism is unsuccessful due to the inability of finding a candidate resource to pre-empt.
Pegging
The BSS pegs the TCH_PREEMPT_FAIL_NO_CAND statistic when TCH pre-emption is unsuccessful.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of times the TCH
pre-emption mechanism is unsuccessful.
If the specified threshold is exceeded, the 28. CELL: TCH Pre-emption Failure Statistic Alarm will be
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-R 4-183
TCH_PREEMPT_FAIL_TIMEOUT Chapter 4: Cell statistics
TCH_PREEMPT_FAIL_TIMEOUT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The TCH_PREEMPT_FAIL_TIMEOUT statistic tracks the number of times a pre-empting request triggering
the TCH pre-emption mechanism successfully, fails to be allocated a TCH (resulting in a timeout). This can
occur due to the pre-empted resources being used by higher priority requests or due to problems on the Um
interface during release of the pre-empted candidates.
Pegging
The BSS pegs the TCH_PREEMPT_FAIL_TIMEOUT statistic when TCH pre-emption is unsuccessful
due to TCH resources not being made available following successful triggering of the TCH pre-emption
mechanism (resulting in a timeout).
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter.
4-184 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_PREEMPT_RQD
TCH_PREEMPT_RQD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The TCH_PREEMPT_RQD statistic tracks the number of times the TCH pre-emption mechanism is triggered.
The BSS triggers TCH pre-emption when a request with pre-emption capability (PCI = 1 and priority level
less than 14) is unable to be allocated a resource immediately. Triggering of the TCH pre-emption mechanism
is dependant on the eMLPP feature being unrestricted and enabled.
Pegging
The TCH_PREEMPT_RQD statistic is split into 4 bins which are pegged depending on the type of request
which is triggering the TCH pre-emption mechanism. Details are shown in Table 4-24.
Table 4-24 TCH_PREEMPT_RQD bins

0 VGCS TCH pre-emption mechanism triggerd by a
VGCS/VBS ASSIGNMENT REQUEST from
the MSC or via the Notification Response
mechanism.
1 ASSIGN_REQ TCH pre-emption mechanism triggered by an
ASSIGNMENT REQUEST.
2 HO_REQ TCH pre-emption mechanism triggered by a
HANDOVER REQUEST.
3 INT_HO_REQ TCH pre-emption mechanism triggered by an
Imperative Internal Handover request.
Analysis
Reference None.
Network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 4-185
TCH_Q_LENGTH Chapter 4: Cell statistics
TCH_Q_LENGTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_Q_LENGTH statistic tracks the arithmetic mean of the number of queued TCH assignment
procedures. Queueing is done due to the Call Queueing feature, Emergency Call Pre-emption, 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.
4-186 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_Q_REMOVED
TCH_Q_REMOVED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_Q_REMOVED statistic tracks when a queued call is assigned to a Traffic Channel (TCH).

0 ASSIGNMENT_RESOURCE_REQ Number of times an assignment resource is
requested.
1 HO_REQ Number of times a handover is requested.
2 ASSIGNMENT_RESOURCE_REQ_IN- Number of times an assignment resource is
NER_Z requested in the inner zone.
3 HO_REQ_INNER_Z Number of times a handover is requested in the
inner zone.
4 {24349} VGCS_VBS_ASSIGN_REQ Number of times a VGCS request is assigned.
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.
{24349} VGCS.
Basis Cell.
Type Counter array.
68P02901W56-R 4-187
TCH_USAGE Chapter 4: Cell statistics
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 may not 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 will only include 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 will be configured.
{24349} Ths BSS includes the time the VGC channel is active within the existing TCH_USAGE statistic.
4-188 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_USAGE
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.
68P02901W56-R 4-189
TCH_USAGE_EXT_RANGE Chapter 4: Cell statistics
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 enabled for the cell.
Pegging
This statistic pegs each time an extended range traffic channel is used.
{24349} The BSS includes the time the VGC channel is active within the existing
TCH_USAGE_EXT_RANGE statistic.
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.
4-190 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_USAGE_INNER_ZONE
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.
{24349} In two channel mode the talker is essentially maintained within the BSS as a point-to-point call and
hence the existing statistical trigger points implemented within the BSS covers the talker.
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.
68P02901W56-R 4-191
TIMER_EXP_PAP_CONV Chapter 4: Cell statistics
TIMER_EXP_PAP_CONV
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 expiries.
• 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-25 shows the bins associated with this statistic.
Table 4-25 TIMER_EXP_PAP_CONV bins
Bin Description
0 T5 expiries.
1 T6 expiries.
2 T8 expiries.
3 PFT expiry with Downlink TBF active.
4 PAP created on T3168 expiry.
5 PAP to Best Effort conversion on final T6 expiry.
When QoS is disabled, only bin 0 (T5 expiries) is pegged.
4-192 68P02901W56-R
Maintenance Information: GSM Statistics Application TIMER_EXP_PAP_CONV
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-193
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.
This statistic is not pegged on the short message service

{24349} In two channel mode the talker is essentially maintained within the BSS as a point-to-point call and
hence the existing statistical trigger points implemented within the BSS covers the talker.
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.

Quality of service monitoring : Call setup.
Network planning.
Key Statistics: RF_LOSS_RATE, TCH_MEAN_HOLD-
ING_TIME, TCH_MEAN_ARRIVAL_RATE,
TCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.
4-194 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_LLC_DATA_VOLUME
UL_LLC_DATA_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
Description
The UL_LLC_DATA_VOLUME statistic counts the volume of uplink LLC data sent on the air interface per
traffic class during a given time interval.
10 kilobytes = 1 unit.
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-26.
68P02901W56-R 4-195
UL_LLC_DATA_VOLUME Chapter 4: Cell statistics
Table 4-26 UL_LLC_DATA_VOLUME bins
Bin Description
0 THP1, ARP1
1 THP1, ARP2
2 THP1, ARP3
3 THP2, ARP1
4 THP2, ARP2
5 THP2, ARP3
6 THP3, ARP1
7 THP3, ARP2
8 THP3, ARP3
9 Background, ARP1
10 Background, ARP2
11 Background, ARP3
• 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, ARP3. PFC_unaware
PFC data is pegged against the Best Effort bins.
• Uplink PAP, SMS and Signalling LLC data will not be pegged.
The recommended statistical measurement interval is 30 minutes.
Analysis
Reference None.
Basis Cell.
Type Counter array.
4-196 68P02901W56-R
Maintenance Information: GSM Statistics Application VGCS_FR_TCH_BUSY
VGCS_FR_TCH_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_FR_TCH_BUSY statistic represents the number of active full rate resources within the cell in use
for VGCS. This includes VGC channels and dedicated channels associated with the talking subscriber.
Whenever a full rate resource is allocated or deallocated, the VGCS_FR_TCH_BUSY statistic is

recalculated.
Pegging
The BSS pegs the VGCS_FR_TCH_BUSY statistic whenever an active full rate resource is allocated for
the voice group call.
Analysis
Reference None.
Basis Cell.
Type Gauge.
68P02901W56-R 4-197
VGCS_HR_TCH_BUSY Chapter 4: Cell statistics
VGCS_HR_TCH_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_HR_TCH_BUSY statistic represents the number of active half rate resources within the cell in
use for VGCS. This will include VGC channels and dedicated channels associated with the talking subscriber.
Whenever a half rate resource is allocated or deallocated, the VGCS_HR_TCH_BUSY statistic is

recalculated.
Pegging
The BSS pegs the VGCS_HR_TCH_BUSY statistic whenever an active half rate resource is allocated for
the voice group call.
Analysis
Reference None.
Basis Cell.
Type Gauge.
4-198 68P02901W56-R
Maintenance Information: GSM Statistics Application VGCS_VBS_ASSIGN_FAIL
VGCS_VBS_ASSIGN_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_VBS_ASSIGN_FAIL statistic counts the number of VGCS/VBS ASSIGNMENT FAILURE

messages transmitted by the BSS to the MSC. That is, the number of times a voice call service assignment fails.
Pegging
The VGCS_VBS_ASSIGN_FAIL statistic is split into 2 bins which are pegged depending on the Service Flag
of the incoming VGCS/VBS ASSIGNMENT REQUEST. Details are shown in Table 4-27.
Table 4-27 VGCS_VBS_ASSIGN_FAIL bins

0 VGCS This type of request is rejected due to a
number of reasons. For example, the BSS has
reached maximum capacity, the VGCS feature
is restricted or disabled or resources are not
available.
1 VBS This feature is not supported at this time so
a request for this service shall always be
rejected.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 4-199
VGCS_VBS_ASSIGN_REQ Chapter 4: Cell statistics
VGCS_VBS_ASSIGN_REQ
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_VBS_ASSIGN_REQ statistic counts the number of VGCS/VBS ASSIGNMENT REQUEST

messages received by the BSS from the MSC. That is, the number of times the BSS is requested to assign
the correct radio resources to a voice group call.
Pegging
The BSS pegs the VGCS_VBS_ASSIGN_REQ statistic upon receipt of a VGCS/VBS ASSIGNMENT
REQUEST message from the MSC.
Analysis
Reference None.
Basis Cell.
Type Counter.
4-200 68P02901W56-R
Maintenance Information: GSM Statistics Application VGCS_VBS_ASSIGN_RESULT
VGCS_VBS_ASSIGN_RESULT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Description
The VGCS_ASSIGN_RESULT statistic counts the number of VGCS/VBS ASSIGNMENT RESULT

messages transmitted by the BSS to the MSC upon initial establishment. That is, the result to the voice
group call request for radio resources.
Pegging
The BSS pegs the VGCS_VBS_ASSIGN_RESULT statistic on transmission of an ASSIGNMENT RESULT
message.
A VGCS_VBS_ASSIGN_RESULT message can be sent multiple times during the life of the VGC for
a particular cell. The statistic is not pegged upon every occurrence, it is only pegged upon the initial
establishment of the VGC in the cell.
A result may be:
• A successful allocation of resources to the voice call service request.
• No resource allocation at this time, however, if the MSC has specified a delay to be allowed,
then a successful allocation message may be sent later when resources become available.
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-R 4-201
ZONE_CHANGE_ATMPT Chapter 4: Cell statistics
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.

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.
4-202 68P02901W56-R
Maintenance Information: GSM Statistics Application ZONE_CHANGE_SUC
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.

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.
68P02901W56-R 4-203
ZONE_CHANGE_SUC Chapter 4: Cell statistics
4-204 68P02901W56-R
Chapter
5
Neighbour statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
When the BSS is configured to control inter-cell handovers {22708/23706} 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 and keep track of handover information for a pair of source and neighbour cells.
Neighbour statistics are described in "Introduction to neighbour statistics" on page 5-2.
68P02901W56-R 5-1
Introduction to neighbour statistics Chapter 5: Neighbour statistics
Introduction to neighbour statistics

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

• Source cell - the cell in which a handover is initiated. Each source cell may have up to 32
target (neighbour) cells.
• Target cell - the neighbour 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 neighbour statistics:
• Each neighbour 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 neighbour
statistics is enabled, all of the statistics for the cell created by the copy_cell command will
be disabled. The individual statistics for the new cell will have to be enabled individually
including the neighbour 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 may not be used to track handovers.
Outgoing neighbour cell statistics
Outgoing neighbour statistics track the number of attempted and successful handovers from a source cell into
a neighbour cell. The outgoing neighbour statistics are:
• "OUT_HO_NC_CAUSE_ATMPT" on page 5-14.
• "OUT_HO_NC_SUC" on page 5-16.
5-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Introduction to neighbour statistics
Example of tracked statistics

In this example, cell_0 has 32 neighbours (cell_1 through cell_32), and the OUT_HO_NC_CAUSE_ATMPT
statistic is enabled at cell_0.
The BSS tracks the following types of intra-BSS handover attempts:
• Originating in cell_0 that hand into cell_1.
• .
• .
Example showing effects of the del_neighbor command

If the del_neighbor command is used to delete one of the neighbour cells of a source cell, only the statistics
for the remaining neighbour cells are pegged.
statistic is enabled at cell_0. The del_neighbor command is used to delete cell_32 as a neighbour cell
of cell_0.
The BSS will track intra-BSS handover attempts:
• originating in cell_0 that hand into cell_1
• .
• .
Example showing effects of the add_neighbor command

If the del_neighbor command is used to delete one of the neighbour cells of a source cell, only the statistics
for the remaining neighbour cells will be pegged.
statistic is enabled at cell_0. The add_neighbor command is used to add cell_32 as a neighbour cell of cell_0.
• originating in cell_0 that hand into cell_2.
• .
• .
68P02901W56-R 5-3
Incoming neighbour statistics
Incoming neighbour statistics track the number of attempted and successful handovers into a neighbour cell
from a source cell. Handovers are tracked for only 32 cells for each neighbour cell, even if a neighbour cell
has more than 32 source cells. The incoming neighbour statistics are:
• "IN_INTRA_BSS_NC_ATMPT" on page 5-9.
• "IN_INTRA_BSS_NC_SUC" on page 5-10.
Choosing source cells

An algorithm chooses which source cells to track for the incoming neighbour statistics. The source cells
are chosen with the following priority:
1. Reciprocal neighbours are chosen. A reciprocal neighbour occurs when both the source cell
and the target cell have each other as a neighbour.
2. Each cell is sequentially checked, starting at 0 (local cell ID), until a source which has not
already been selected is found.
Effect of the del_neighbor or add_neighbor commands

When neighbour cells are added or deleted from a cell in which the incoming neighbour statistics are enabled,
the following checks are performed:
1. If the cell is already tracking 32 source cells, no changes are made.
2. If the cell is not tracking 32 source cells, a check is done to see if new ones can be tracked.
3. If new source cells can be added, reciprocal neighbours are added first, followed by
non-reciprocal neighbours, which are chosen by sequentially looking through the database.
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
neighbour, and the IN_INTRA_BSS_NC_ATMPT statistic is enabled at cell_0.
• that hand into cell_0 originating from cell_1
• .
• .
5-4 68P02901W56-R
Example of when there are more than 32 neighbour cells

In this example, the network has 50 cells. Cell_0 has cell_1 through cell_16 as neighbours. Cell_1 through
cell_50 each have cell_0 as a neighbour. The incoming neighbour 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 neighbours (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 neighbour is added

may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50 are tracked because the 32
A new neighbour (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbour pair. The
cells being tracked will not be changed just because a new reciprocal neighbour pair has been added because it
is already at the maximum number of cells it can track.
Example of when a neighbour cell is deleted

may be tracked, cell_17 through cell_32 are chosen. Cell_33 through cell_50 are tracked because the 32
A new neighbour (cell_45) is added to cell_0. Cell_0 and cell_45 now make a reciprocal neighbour pair. The
cells being tracked will not be changed just because a new reciprocal neighbour pair has been added because it
is already at the maximum number of cells it can track.
Neighbour 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 neighbours.
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 already tracked.
Examples of notation and initial situation
The following are examples of typical handover situations to show how neighbour cell statistics are pegged.
68P02901W56-R 5-5
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)
sta t na me peg count source cell_B a nd ta rget cell_A
Initial situation
Table 5-1 shows an example of three cells: cell_A, cell_B, and cell_C. All four neighbour 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
Table 5-1 Neighbour cell statistics pegged
Peg source
Neighbour status Initial peg count
target
cell_B is a neighbour of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (B-A)
cell_A is a neighbour of cell_B IN_INTRA_BSS_NC_SUC 0 (B-A)
cell_C is a neighbour of cell_A and IN_INTRA_BSS_NC_ATMPT 0 (C-A)
cell_A is a neighbour 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)
5-6 68P02901W56-R
Successful handover (B-A)

A 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 updated.
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 neighbour cell change statistics
{22708/23706}
68P02901W56-R 5-7
Network assist cell change statistics are captured from events occurring in the network assist cell. The
following are statistics which track PCCC and PCCO attempts to neighbour cells:
• "NUM_CELL_RESEL_NEI" on page 5-11.
• "NUM_CELL_RESEL_NEI_PCCN" on page 5-12.
• "NUM_CELL_RESEL_NEI_SUCC" on page 5-13.
There are statistics that capture PCCC and PCCO attempts to non-neighbour cells. These are
shown in "Network assist cell change" on page 4-8.
5-8 68P02901W56-R
Maintenance Information: GSM Statistics Application IN_INTRA_BSS_NC_ATMPT
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 neighbour which is placed first
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 (Neighbour cell).
Type Counter.
68P02901W56-R 5-9
IN_INTRA_BSS_NC_SUC Chapter 5: Neighbour statistics
IN_INTRA_BSS_NC_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_NC_SUC statistic tracks the successful incoming internal inter-cell handovers per
originating cell.
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.
5-10 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_CELL_RESEL_NEI
NUM_CELL_RESEL_NEI
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
Description
The NUM_CELL_RESEL_NEI statistic measures the total number of PCCC and PCCO attempts to a
neighbour cell due to either congestion relief or RF based cell reselection. This statistic is supported for a
maximum of 16 cells with 32 GPRS neighbour cells for each cell.
1 unit represents 1 attempt by the BSS to send a PCCC or PCCO message.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI statistic on a per-neighbour 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-111.
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.
68P02901W56-R 5-11
NUM_CELL_RESEL_NEI_PCCN Chapter 5: Neighbour statistics
NUM_CELL_RESEL_NEI_PCCN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
Description
The NUM_CELL_RESEL_NEI_PCCN statistic measures the total number of PCCN attempts by MSs to
a neighbour cell. This statistic is supported for a maximum of 16 cells with 32 GPRS neighbour cells for
each cell.
1 unit represents 1 PCCN received from the MS.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI_PCCN statistic on a per-neighbour basis when a PCCN request
is received for the neighbour cell. The corresponding per cell statistic is pegged using a separate counter:
"NUM_CELL_RESEL_CELL_PCCN" on page 4-112.
Analysis
Reference None.
Type Counter.
5-12 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_CELL_RESEL_NEI_SUCC
NUM_CELL_RESEL_NEI_SUCC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
Description
The NUM_CELL_RESEL_NEI_SUCC statistic measures the total number of successful PCCC and PCCO
attempts to a neighbour 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 (also in a 3x PCU environment).

1 unit represents 1 successful cell reselection due to PCCC/PCCO.
This statistic is supported for a maximum of 16 cells with 32 GPRS neighbour cells for each cell.
Pegging
NCRM pegs the NUM_CELL_RESEL_NEI_SUCC statistic on a per-neighbour basis for every successful
cell reselections 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-113.
Analysis
Reference None.
Type Counter.
68P02901W56-R 5-13
OUT_HO_NC_CAUSE_ATMPT Chapter 5: Neighbour statistics
OUT_HO_NC_CAUSE_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_HO_NC_CAUSE_ATMPT statistic tracks the number of handovers per neighbour per cause.
maximum of 32 target cells can be tracked.
This statistic provides information to determine quality of service and to support optimization. Allows study
of the handover performance of a specific cell for each of its neighbouring target cells.
Inter-band handovers are also tracked when the Multiband Handover feature is enabled. (Refer to the
description for Bin 10, below.)

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.
5-14 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_HO_NC_CAUSE_ATMPT
Analysis
This statistic can be used for trend analysis of handover attempts per neighbour 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.
68P02901W56-R 5-15
OUT_HO_NC_SUC Chapter 5: Neighbour statistics
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
neighbouring 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.
5-16 68P02901W56-R
Chapter
6
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-R 6-1
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:
• "Call clearing" on page 6-2.
• "Downlink RXQUAL (BER)" on page 6-2.
• "Uplink RXQUAL (U_BER)" on page 6-2.
• "Link balance verification" on page 6-3.
• "Timing advance" on page 6-4.
• "Miscellaneous" on page 6-4.
• "VersaTRAU" on page 6-4.
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:
• "RF_LOSSES_TCH_HR" on page 6-35.
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-8 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-37 is the only uplink RXQUAL statistic.
6-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Carrier and timeslot statistics subgroups
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-12.
• "CHAN_UL_TX_PWR_LVL" on page 6-15.
• "PATH_BALANCE" on page 6-29.
• "UPLINK_PATH_LOSS" on page 6-41.
68P02901W56-R 6-3
Carrier and timeslot statistics subgroups Chapter 6: Carrier and timeslot statistics
Timing advance
The timing advance statistic "ROC" on page 6-36 is used to monitor the timing advance measurements.
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-13.
• "FER_AMR_FR" on page 6-19.
• "FER_AMR_HR" on page 6-21.
• "FER_GSM_FR_EFR" on page 6-23.
• "FER_GSM_HR" on page 6-25.
• "INTF_ON_IDLE" on page 6-27.
• "RBER" on page 6-31.
VersaTRAU
{23769}
VersaTRAU statistics measure backhaul data associated with the VersaTRAU feature. The following are
VersaTRAU statistics:
• "DL_EGPRS_BACKHAUL_DEMAND" on page 6-16.
• "DL_EGPRS_BACKHAUL_USED" on page 6-17.
• "EGPRS_64K_CHANNEL_WIDTH" on page 6-18.
• "UL_EGPRS_BACKHAUL_DEMAND" on page 6-39.
• "UL_EGPRS_BACKHAUL_USED" on page 6-40.
6-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Carrier and timeslot statistics subgroups
Usage congestion
Usage congestion statistics track congestion processes not related to the directed retry feature. The following
are usage congestion statistics:
• "BUSY_TCH_CARR" on page 6-10.
• "BUSY_TCH_CARR_HR" on page 6-11.
68P02901W56-R 6-5
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 will be sent upon:
• Successful handover on an SDCCH channel.
• Successful immediate assignment on an SDCCH channel.
This statistic pegs for reasons other than calls requiring a traffic channel, such as location updates.
Analysis
This statistic can be used for trend analysis of SDCCH allocations and allows the calculation of the mean hold
time of a 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.
Network planning.
Ladder: Immediate assignment successful, Intra-cell handover,
Inter-BSS handover, Connection establishment, Intra-BSS
handover.
Basis Carrier.
Type Counter.
6-6 68P02901W56-R
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:
• Successful allocation due to call establishment including successful allocations due to directed
retries.
• 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.
{24349} This statistic pegs when a VGC channel is successfully allocated.
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.
Key statistics: TCH_MEAN_ARRIVAL_RATE,
TCH_MEAN_HOLDING_TIME, CELL_TCH_ALLOCA-
TIONS, TCH_RF_LOSS_RATE.
Basis Carrier.
Type Counter.
68P02901W56-R 6-7
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.
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:
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
The bin ranges for this statistic may not be changed.
6-8 68P02901W56-R
Maintenance Information: GSM Statistics Application BER
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-R 6-9
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 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.
{24349} This statistic is pegged whenever a half rate VGC channel is allocated or deallocated.
Analysis

Usage Congestion.
Network planning.
Optimization.
Basis Carrier.
Type Gauge.
6-10 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_TCH_CARR_HR
BUSY_TCH_CARR_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The BUSY_TCH_CARR_HR statistic replaces BUSY_TCH_CARR_HR_AMR.
Description
TCH{24349} or VGC 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{24349}
or VGC channel occurs.
Reference None.
Network planning.
Basis Carrier.
68P02901W56-R 6-11
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.

Quality of service.
Basis Carrier.
6-12 68P02901W56-R
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 that the BSS times out while waiting for
the MS to establish on the {24620}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
{24620}TCH/SDCCH is allocated. When the MS does not reply with a SABM on that {24620}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 of
time and/or geographically clustered may indicate a hardware failure.
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
{24620}TCH/SDCCH. {24620} The bin pegged will depend on the channel type that the MS failed on
as shown in Table 6-1.
Table 6-1 CHAN_REQ_MS_FAIL bins
Bin Description
0 MS failed while on a SDCCH.
1 MS failed while on a half rate TCH.
2 MS failed while on a full rate TCH.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of BSS timeouts
while waiting for an MS to establish on the {24620} TCH/SDCCH assigned during the immediate assignment
procedure that are acceptable in normal system operations.
68P02901W56-R 6-13
CHAN_REQ_MS_FAIL Chapter 6: Carrier and timeslot statistics
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH failed - PM alarm
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.
Basis Timeslot.
Alarm Minor.
6-14 68P02901W56-R
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.

Quality of service.
Basis Carrier.
68P02901W56-R 6-15
DL_EGPRS_BACKHAUL_DEMAND Chapter 6: Carrier and timeslot statistics
DL_EGPRS_BACKHAUL_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23769}
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 subsequently 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 20ms RLC block period.
6-16 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_EGPRS_BACKHAUL_USED
DL_EGPRS_BACKHAUL_USED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23769}
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 pre-emptions due to backhaul related restrictions) in the downlink by
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 the
68P02901W56-R 6-17
EGPRS_64K_CHANNEL_WIDTH Chapter 6: Carrier and timeslot statistics
EGPRS_64K_CHANNEL_WIDTH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23769}
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 the
6-18 68P02901W56-R
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 480 ms.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to a lookup table, the
ratio is then converted to a FER_AMR_FR Quality number between 0 and 9.
For example: two bad frames out of 24 results in a ratio of 0.083:1. From the lookup table, Table 6-2, this
relates to an FER_AMR_FR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for AMR full-rate calls for each carrier in a cell.
Units
The FER_AMR_FR is reported using values 0 to 9 as follows.
Table 6-2 FER_AMR_FR Quality number conversion
FER_AMR_FR Quality
FER_AMR_FR Quality number
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_AMR_FR Quality is measured on a timeslot 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.
The values of the bins are fixed and are not adjustable by the operator.
68P02901W56-R 6-19
FER_AMR_FR Chapter 6: Carrier and timeslot statistics
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-20 68P02901W56-R
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 measurement period over
ratio is then converted to a FER_AMR_HR Quality number between 0 and 9.
relates to an FER_AMR_HR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for AMR half rate calls for each carrier in a cell.
Units
The FER_AMR_HR is reported using values 0 to 9 as follows.
Table 6-3 FER_AMR_HR Quality number conversion
FER_AMR_HR Quality
FER ratio (min:1 to max:1)
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_AMR_HR Quality is measured on a timeslot basis for active channels after decoding de-interleaving
is pegged.
68P02901W56-R 6-21
FER_AMR_HR Chapter 6: Carrier and timeslot statistics
Analysis
Reference None.
Basis Carrier.
6-22 68P02901W56-R
Maintenance Information: GSM Statistics Application FER_GSM_FR_EFR
FER_GSM_FR_EFR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 measurement period over
ratio is then converted to a FER_GSM_FR_EFR Quality number between 0 and 9.
relates to an FER_GSM_FR_EFR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for non_AMR calls for each carrier in a cell.
Units
The FER_GSM_FR_EFR is reported using values 0 to 9 as follows.
68P02901W56-R 6-23
FER_GSM_FR_EFR Chapter 6: Carrier and timeslot statistics
Table 6-4 FER_GSM_FR_EFR Quality number conversion
FER_GSM_FR_EFR Quality
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_GSM_FR_EFR Quality is measured on a per-timeslot 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.
Analysis
Reference None.
Usage Quality of service,
Fault finding,
RF loss,
Congestion.
Basis Carrier.
6-24 68P02901W56-R
Maintenance Information: GSM Statistics Application FER_GSM_HR
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 measurement period over
ratio is then converted to a FER_GSM_HR Quality number between 0 and 9.
relates to an FER_GSM_HR Quality number of 2.
Pegging
This statistic pegs the uplink frame erasure rate for GSM half rate calls for each carrier in a cell.
Units
The FER_GSM_HR is reported using values 0 to 9 as follows.
68P02901W56-R 6-25
FER_GSM_HR Chapter 6: Carrier and timeslot statistics
Table 6-5 FER_GSM_HR Quality number conversion
FER_GSM_HR Quality
number
0 0.0000 to 0.0416
1 0.0417 to 0.0832
2 0.0833 to 0.1249
3 0.1250 to 0.1666
4 0.1667 to 0.2082
5 0.2083 to 0.2499
6 0.2500 to 0.2916
7 0.2917 to 0.3332
8 0.3333 to 0.3749
9 0.3750 to 1.0000
FER_GSM_HR Quality is measured on a timeslot basis for active channels after decoding de-interleaving
is pegged.
Analysis
Reference None.
Basis Carrier.
6-26 68P02901W56-R
Maintenance Information: GSM Statistics Application INTF_ON_IDLE
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.
INTF_ON_IDLE statistic are shown in Table 6-6.
Table 6-6 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-7 provides an indication of the interference on a channel by recording measurements of 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-7.
68P02901W56-R 6-27
INTF_ON_IDLE Chapter 6: Carrier and timeslot statistics
Table 6-7 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
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.
6-28 68P02901W56-R
Maintenance Information: GSM Statistics Application PATH_BALANCE
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.
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
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.
If a low noise amplifier (LNA) is fitted, a deviation of -20 is possible.
68P02901W56-R 6-29
PATH_BALANCE Chapter 6: Carrier and timeslot statistics
Typically, the path loss should be similar in both the uplink and downlink directions. When diversity gain is
enabled, the path balance will be just below 110, indicating a lower uplink path loss.
Mismatch of Horizon and Horizon macro database and hardware.

The path_balance statistic will be incorrect if the the Horizon and Horizonmacro cabinet and database are
mismatched. The following table describes the two mismatch scenarios between the cabinet and database.
If... Then...
the Horizon cabinet is equipped with Horizonmacro the SITE alarm 28 “data configuration and Horizon
database, the path_balance statistic will be hardware mismatch" will be generatedoperators
incorrect. should change either the hardware or the database
accordingly.
Consult the manual, Maintenance Information:
Alarm Handling At The OMC-R (68P02901W26).
the Horizonmacro cabinet is equipped with Horizon the SITE alarm 28 “data configuration and Horizon
database, the path_balance statistic will be hardware mismatch" will be generated.operators
incorrect. should change either the hardware or the database
accordingly.
Consult the manual, Maintenance Information:
Alarm Handling At The OMC-R (68P02901W26).
If the Horizonmacro 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 Horizonmacro 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.
6-30 68P02901W56-R
Maintenance Information: GSM Statistics Application RBER
RBER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RBER (Residual Bit Error Rate) Quality statistic is derived from a ratio of number of bits in 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.
ratio is converted to an RBER Quality number between 0 and 7.
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-8 RBER Quality number conversion
RBER Quality number RBER ratio (min:1 to max:1)

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 may not be altered by the operator.
68P02901W56-R 6-31
RBER Chapter 6: Carrier and timeslot statistics
Analysis
Reference None.
Fault finding.
RF loss.
Congestion.
Basis {22577} Carrier.
6-32 68P02901W56-R
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.
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
This statistic pegs the number of full rate and half rate calls that were terminated because of RF problems.
It is composed of calls lost while using a TCH. If a TCH is reconfigured as an SDCCH, only the SDCCH
statistics are configured.
Analysis
using a TCH that are acceptable in normal system operations.
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 Statistic: RF_LOSS_RATE, TCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter.
Alarm Major.
68P02901W56-R 6-33
RF_LOSSES_TCH Chapter 6: Carrier and timeslot statistics
RF_LOSSES_TCH is not pegged with any handover failure statistic. In a frequency hopping
environment, this statistic may not be useful at channel level; therefore, roll to cell level.
6-34 68P02901W56-R
Maintenance Information: GSM Statistics Application RF_LOSSES_TCH_HR
RF_LOSSES_TCH_HR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The RF_LOSSES_TCH_HR statistic replaces RF_LOSSES_TCH_HR_AMR.
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 calls that were terminated because of RF problems. It is composed of calls
lost while using a half rate AMR and/or GSM TCH.
Analysis
using a half rate AMR and/or GSM TCH that are acceptable in normal system operations.
Reference None
Usage RF loss.
Congestion.
Fault finding.
Basis Timeslot.
Type Counter.
68P02901W56-R 6-35
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 a number of user definable TA ranges up to a maximum of
10 bins. The default bin ranges are shown in Table 6-9.
Table 6-9 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
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
Basis Carrier.
6-36 68P02901W56-R
Maintenance Information: GSM Statistics Application U_BER
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.
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
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL 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
The bin ranges for this statistic may not be changed.
68P02901W56-R 6-37
U_BER Chapter 6: Carrier and timeslot statistics
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.
6-38 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_EGPRS_BACKHAUL_DEMAND
UL_EGPRS_BACKHAUL_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23769}
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 subsequently applied in the uplink by
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
68P02901W56-R 6-39
UL_EGPRS_BACKHAUL_USED Chapter 6: Carrier and timeslot statistics
UL_EGPRS_BACKHAUL_USED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23769}
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
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 the
6-40 68P02901W56-R
Maintenance Information: GSM Statistics Application UPLINK_PATH_LOSS
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.
68P02901W56-R 6-41
UPLINK_PATH_LOSS Chapter 6: Carrier and timeslot statistics
6-42 68P02901W56-R
Chapter
7
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.
• {22100} "GCI_FOR_16KPD_DEMAND" on page 7-3.
• {23956} "PFC_REJ_DGRD_PRMPT_PRP" on page 7-6.
• {22100} "PRP_PD_DEMAND" on page 7-8.
• {22100} "TOTAL_GCI_FOR_PD_DEMAND" on page 7-9.
If CTU2 is used in the system, processor utilization statistics are not supported.
68P02901W56-R 7-1
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 and DPROC devices at a particular site are being over, under, or properly utilized.
This statistic is updated from reports generated by the internal executive system, which keeps track of when
CPU 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, statistic Mean Utilization, is calculated). This statistic is
recorded for each GPROC and DPROC under the control of a BSS.
Analysis
This statistic can be used for trend analysis of GPROC and DPROC utilization.
Reference GSM 12.07,3.0.2,4.3 bullet 1.

Usage Processor utilization.
Network planning.
Optimization.
Basis GPROC.
7-2 68P02901W56-R
Maintenance Information: GSM Statistics Application GCI_FOR_16KPD_DEMAND
GCI_FOR_16KPD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22100}
Description
GCI_FOR_16KPD_DEMAND counts the mean and maximum number of dynamically mapped GCIs
demanded for 16K PDTCH on a PRP DPROC in a given statistical measurement interval. 1 Unit represents 1
GCI demanded.
The demanded number of GCIs presented by this statistic could be greater than the in-service
resources of PRP DPROCs or GDSs.
Pegging
This statistic is pegged by CB whenever GCI demand for 16K PDTCH is increased or decreased on a
PRP DPROC, 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 DPROC.
Basis DPROC.
Type Gauge.
68P02901W56-R 7-3
GCI_FOR_32KPD_DEMAND Chapter 7: GPROC and DPROC statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22100}
Description
GCI demanded.
Pegging
This statistic is pegged by CB whenever GCI demand for 32K PDTCH is increased or decreased on a
PRP DPROC, the count is increased/decreased by 2 for every 32K PDTCH supported; it also pegs at the
end of an interval.
Analysis
Reference None.
Basis DPROC.
Type Gauge.
7-4 68P02901W56-R
Maintenance Information: GSM Statistics Application GCI_FOR_64KPD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22100}
Description
GCI demanded.
Pegging
This statistic is pegged by CB whenever GCI demand for 64K PDTCH (4 GCIs) is increased or decreased
on a PRP DPROC, the count is increased/decreased by 4 for every 64K PDTCH supported; it also pegs at
the end of an interval.
Analysis
Reference None.
Basis DPROC.
Type Gauge.
68P02901W56-R 7-5
PFC_REJ_DGRD_PRMPT_PRP Chapter 7: GPROC and DPROC statistics
PFC_REJ_DGRD_PRMPT_PRP
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{23956}
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 keeps track of the number of PFC
downgrades and preemptions due to cell or PRP retentions on a per board basis.
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 the number of these in the future.
Table 7-1 PFC_REJ_DGRD_PRMPT_PRP bins

0 Rejection due to lack The PCU does not have enough MTBR Increase the number of GPRS
of cell resources. in the cell to admit a PFC or BSS timeslots in the cell.
cannot admit the PFC due to mobile’s
capability.
1 Rejection due to lack The PCU does not have enough MTBR Adjust the MTBR
of PRP resources. in the board to admit a PFC. commitments for different
traffic classes.
lack of cell resources. in the cell to maintain a PFC’s current commitments for different
priority PFC.
lack of PRP resources. in the PRP to maintain a PFC’s current commitments for different
priority PFC.
4 Preemption due to The PCU does not have enough Adjust the MTBR
lack of cell resources. MTBR in the cell to maintain a PFC’s commitments for different
commitments due to a change in traffic classes.
available resources or admission of a
the PFC.
Cont.
7-6 68P02901W56-R
Maintenance Information: GSM Statistics Application PFC_REJ_DGRD_PRMPT_PRP
Table 7-1 PFC_REJ_DGRD_PRMPT_PRP bins (Continued)

5 Preemption due to The PCU does not have enough MTBR Adjust the MTBR
lack of PRP resources. on the PRP to maintain a PFC’s commitments for different
commitments due to admission of a traffic classes.
the PFC.
6 Downgrade due to cell The PCU does not have enough MTBR Increase the resources in the
retention. in the cell to retain all the active PFCs’ cell.
MTBR for cell retention purposes.
7 Downgrade due to The PCU does not have enough MTBR Increase the resources on the
PRP retention. on the PRP to retain all the active PFCs’ PRP.
MTBR for PRP retention purposes.
8 Preemption due to cell The PCU does not have enough Increase the resources in the
retention. MTBR in the cell to maintain a PFC’s cell.
for cell retention purposes.
9 Preemption due to The PCU does not have enough MTBR Increase the resources on the
PRP retention. on the PRP to maintain a PFC’s PRP.
for PRP retention purposes.
Bins 7 and 9 are not pegged.
Analysis
Reference None.
Basis DPROC.
Type Counter array.
68P02901W56-R 7-7
PRP_PD_DEMAND Chapter 7: GPROC and DPROC statistics
PRP_PD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22100}
Description
PRP_PD_DEMAND counts the number of dynamically mapped PRP PDTCHs demanded on a PRP DPROC.
1 unit represents 1 PRP PDTCH demanded.
• 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 DPROCs or GDSs.
Pegging
This statistic is pegged by CB whenever PRP PDTCH demand is increased or decreased on a PRP DPROC;
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.
Basis DPROC.
Type Gauge.
7-8 68P02901W56-R
Maintenance Information: GSM Statistics Application TOTAL_GCI_FOR_PD_DEMAND
TOTAL_GCI_FOR_PD_DEMAND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22100}
Description
TOTAL_GCI_FOR_PD_DEMAND counts the mean and maximum number of dynamically mapped GCIs
demanded for all PDTCHs on a PRP DPROC in a given statistical measurement interval. 1 Unit represents 1
GCI demanded.
Pegging
This statistic is pegged by CB whenever GCI demand for any PDTCH (16K, 32K, 64K) is increased or
decreased on a PRP DPROC; 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 DPROC.
Basis DPROC.
Type Gauge.
68P02901W56-R 7-9
TOTAL_GCI_FOR_PD_DEMAND Chapter 7: GPROC and DPROC statistics
7-10 68P02901W56-R
Chapter
8
LMTL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Location Services Message Transfer Link (LMTL) statistics are used to track 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 8-2.
68P02901W56-R 8-1
LMTL statistics subgroups Chapter 8: LMTL statistics
LMTL statistics subgroups

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

• "LMTP C7 availablility" on page 8-2.
• "LMTP C7 performance" on page 8-3.
• "LMTP C7 utilization" on page 8-4.
LMTP C7 availablility
LMTP C7 availability statistics are used to track the duration of signalling link outages and inhibitions (local
and remote) for the LMTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. The following
are the MTP C7 availability statistics:
• "LMTP_LINKFAIL" on page 8-11.
• "LMTP_LOCAL_BUSY" on page 8-12.
• "LMTP_LOCAL_MGT" on page 8-13.
• "LMTP_MGT_INHIBIT" on page 8-14.
• "LMTP_MGT_UNINHIBIT" on page 8-15.
• "LMTP_REMOTE_MGT" on page 8-20.
• "LMTP_REMOTE_PROC" on page 8-21.
• "LMTP_START_RPO" on page 8-31.
• "LMTP_STOP_RPO" on page 8-32.
• "LMTP_UNAVAILABLE" on page 8-34.
8-2 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTL statistics subgroups
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 No.7 protocol on the BSC to MSC interface. The following are the LMTP C7
performance statistics:
• "LMTP_CHANGEBACK" on page 8-7.
• "LMTP_CHANGEOVER" on page 8-8.
• "LMTP_LINK_INS" on page 8-10.
• "LMTP_NEG_ACKS" on page 8-18.
• "LMTP_REMOTE_SL_CONGESTION" on page 8-27.
• "LMTP_RESTORATION" on page 8-22.
• "LMTP_SL_ACK" on page 8-25.
• "LMTP_SL_ALIGNMENT" on page 8-26.
• "LMTP_SL_ERROR_RATE" on page 8-28.
• "LMTP_SL_FAIL" on page 8-29.
• "LMTP_SL_FIBR" on page 8-30.
• "LMTP_SU_ERROR" on page 8-33.
68P02901W56-R 8-3
LMTL statistics subgroups Chapter 8: LMTL statistics
LMTP C7 utilization
LMTP C7 utilization statistics are used to track the number of messages received, transmitted and
retransmitted on signalling links and supply information on signalling link congestion for the LMTP of the
ITU-TSS No.7 protocol on the BSC to MSC interface. The following are the LMTP C7 utilization statistics:
• "LMTP_CONGESTION_LOST_MSU" on page 8-5.
• "LMTP_MSU_DISCARDED" on page 8-6.
• "LMTP_CONGESTION" on page 8-36.
• "LMTP_RE_TX" on page 8-19.
• "LMTP_MSU_RX" on page 8-16.
• "LMTP_MSU_TX" on page 8-17.
• "LMTP_SIB_RX" on page 8-35.
• "LMTP_SIB_TX" on page 8-37.
• "LMTP_SIF_SIO_RX" on page 8-23.
• "LMTP_SIF_SIO_TX" on page 8-24.
• "LMTP_LOCAL_SL_CONGESTION" on page 8-9.
8-4 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_CONGESTION_LOST_MSU
LMTP_CONGESTION_LOST_MSU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CONGESTION_LOST_MSU statistic tracks the number of times Message Signalling Units
(MSU) are being lost due to Lb-interface Signalling 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
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.
68P02901W56-R 8-5
LMTP_MSU_DISCARDED Chapter 8: LMTL statistics
LMTP_MSU_DISCARDED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_DISCARDED statistic tracks the number of MSUs discarded due to Lb-interface
Signalling Link (SL) congestion.
Pegging
This statistic pegs each time an MSU is discarded due to Lb-interface SL congestion.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of MSUs are 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 - PM alarm
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.
8-6 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_CHANGEBACK
LMTP_CHANGEBACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CHANGEBACK statistic tracks the number of local automatic changebacks that have been
successfully completed.
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signalling Link (SL) is
diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic changebacks 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.
68P02901W56-R 8-7
LMTP_CHANGEOVER Chapter 8: LMTL statistics
LMTP_CHANGEOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CHANGEOVER statistic tracks the number of local automatic changeovers that have been
successfully completed. This indicates MTP traffic is being transferred from an Lb interface Signalling 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 - PM 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.
8-8 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_LOCAL_SL_CONGESTION
LMTP_LOCAL_SL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_SL_CONGESTION statistic tracks once for each onset of congestion across
the Lb-interface Signalling Link (SL).
There are two types of congestion that may occur across an 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 an 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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.
68P02901W56-R 8-9
LMTP_LINK_INS Chapter 8: LMTL statistics
LMTP_LINK_INS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LINK_INS statistic tracks the length of time that an Lb-interface Signalling 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.
8-10 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_LINKFAIL
LMTP_LINKFAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LINKFAIL statistic tracks the duration of the Lb-interface Signalling 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.
68P02901W56-R 8-11
LMTP_LOCAL_BUSY Chapter 8: LMTL statistics
LMTP_LOCAL_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_BUSY statistic tracks the total time congestion is present on the local end of the
Lb-interface Signalling Link (SL).
Pegging
This statistic is started when congestion is detected on an Lb-interface SL. The statistic is stopped when
normal operation is resumed.
Analysis
This statistic can be used for trend analysis on congestion durations 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.
8-12 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_LOCAL_MGT
LMTP_LOCAL_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_LOCAL_MGT statistic tracks the total time that a local Lb-interface Signalling 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).
68P02901W56-R 8-13
LMTP_MGT_INHIBIT Chapter 8: LMTL statistics
LMTP_MGT_INHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MGT_INHIBIT statistic tracks the number of times the Lb-interface Signalling 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.
8-14 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_MGT_UNINHIBIT
LMTP_MGT_UNINHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MGT_UNINHIBIT statistic tracks the number of times the Lb-interface Signalling 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 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-R 8-15
LMTP_MSU_RX Chapter 8: LMTL statistics
LMTP_MSU_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs) received on a
Lb-interface signalling link.
Pegging
This statistic pegs each time MSUs are received over the Lb-interface signalling 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.
8-16 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_MSU_TX
LMTP_MSU_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs) transmitted on an
Pegging
This statistic pegs each time MSUs are transmitted over the Lb-interface signalling 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-R 8-17
LMTP_NEG_ACKS Chapter 8: LMTL statistics
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 signalling link.
Pegging
This statistic pegs when the BSS detects out of order messages to the SMLC and requests retransmission.
Analysis
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 - PM 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 Warning.
8-18 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_RE_TX
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 peg the number of octets retransmitted by the BSS to the SMLC.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of octet
retransmissions that are acceptable in normal system operations.
If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted - PM alarm is
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-R 8-19
LMTP_REMOTE_MGT Chapter 8: LMTL statistics
LMTP_REMOTE_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_REMOTE_MGT statistic tracks the total time an Lb-interface Signalling 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).
8-20 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_REMOTE_PROC
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.
68P02901W56-R 8-21
LMTP_RESTORATION Chapter 8: LMTL statistics
LMTP_RESTORATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_RESTORATION statistic tracks the number of times user traffic is allowed on an Lb-interface
Signalling 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.
8-22 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SIF_SIO_RX
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 an Lb-interface signalling link.
Pegging
This statistic pegs each time an SIF or SIO is received over an Lb-interface signalling 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-R 8-23
LMTP_SIF_SIO_TX Chapter 8: LMTL statistics
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 signalling link by the BSC to the SMLC.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over a signalling link by the BSC to the SMLC.
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.
8-24 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SL_ACK
LMTP_SL_ACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_ACK statistic tracks the number of times that the link was lost due to an 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 acknowledgement from
the BSS-based SMLC is not received.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
acknowledgements 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
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.
68P02901W56-R 8-25
LMTP_SL_ALIGNMENT Chapter 8: LMTL statistics
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 Signalling Link (SL) unsuccessfully tries to align with the
Lb-interface.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of unsuccessful
attempts to align an out-of-service SL to the Lb-interface that are acceptable in normal system operations.
If the specified threshold is exceeded, the 5. LMTL: SL alignment failure - PM alarm is generated. Refer
to the 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).
Basis Lb SS7_LINK.
Type Counter.
Alarm Minor.
8-26 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_REMOTE_SL_CONGESTION
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 signalling 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 Signalling 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
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.
68P02901W56-R 8-27
LMTP_SL_ERROR_RATE Chapter 8: LMTL statistics
LMTP_SL_ERROR_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_ERROR_RATE statistic tracks the number of times that an Lb-interface Signalling 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 expirations that are acceptable in normal system operations.
If the specified threshold is exceeded, the 3. LMTL: SL failure - excessive error rate - PM alarm is
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.
8-28 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SL_FAIL
LMTP_SL_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SL_FAIL statistic tracks the Lb-interface Signalling Link (SL) failure for all causes except
operator interaction through the MMI.
Pegging
This statistic is pegged when an 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 operator 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 generated. Refer
information.
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-R 8-29
LMTP_SL_FIBR Chapter 8: LMTL statistics
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 an Lb-interface Signalling Link (SL) going out of service. This statistic is
similar to 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
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 - 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.
8-30 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_START_RPO
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 - 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 Warning.
68P02901W56-R 8-31
LMTP_STOP_RPO Chapter 8: LMTL statistics
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.
8-32 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SU_ERROR
LMTP_SU_ERROR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SU_ERROR statistic tracks the number of times erroneous signal units are received on the
Lb-interface Signalling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the Lb-interface SS7 SL.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times 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 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 Warning.
68P02901W56-R 8-33
LMTP_UNAVAILABLE Chapter 8: LMTL statistics
LMTP_UNAVAILABLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_UNAVAILABLE statistic tracks the total time an Lb-interface Signalling Link (SL) is out of
service for all reasons including operator intervention.
Pegging
This statistic records the duration of Lb-interface SL unavailability for all reasons, including 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.
8-34 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SIB_RX
LMTP_SIB_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIB_RX statistic tracks the number of Status Indication Busy LSSU messages received over
an Lb-interface Signalling Link (SL).
Pegging
This statistic is pegged each time the BSS receives a Status Indication Busy (SIB) LSSU message across the
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.
68P02901W56-R 8-35
LMTP_CONGESTION Chapter 8: LMTL statistics
LMTP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_CONGESTION statistic tracks the time the Lb-interface Signalling Link (SL) is congested.
Pegging
The timer for this statistic is started when congestion is detected on an Lb interface signalling link. The
timer is stopped when normal operation is resumed.
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.
8-36 68P02901W56-R
Maintenance Information: GSM Statistics Application LMTP_SIB_TX
LMTP_SIB_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LMTP_SIB_TX statistic tracks the number of Status Indication Busy LSSU messages transmitted over
an Lb-interface Signalling Link (SL).
Pegging
This statistic is pegged each time the BSS transmits a Status Indication Busy (SIB) LSSU message across the
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.
68P02901W56-R 8-37
LMTP_SIB_TX Chapter 8: LMTL statistics
8-38 68P02901W56-R
Chapter
9
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 Chapter 4, "Cell statistics," 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 9-2.
68P02901W56-R 9-1
BSS statistics for Location Services support subgroups Chapter 9: 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 9-3.
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-63.
• "OK_ACC_PROC" on page 4-125.
9-2 68P02901W56-R
Maintenance Information: GSM Statistics Application BSS statistics for Location Services support subgroups
Location service
The following are specific location service statistics :

• "BSSLAP_ABORT_RCV" on page 9-4.
• "BSSLAP_ABORT_SENT" on page 9-5.
• "BSSLAP_MS_POS_CMD" on page 9-6
• "BSSLAP_MS_POS_RESP" on page 9-7
• "BSSLAP_REJ" on page 9-8
• "BSSLAP_RESET" on page 9-9
• "BSSLAP_TA_REQ" on page 9-10
• "BSSLAP_TA_RESP" on page 9-11
• "BSSLAP_TOA_REQ" on page 9-12
• "BSSMAP_CONLESS_INFO_RCV" on page 9-13
• "BSSMAP_CONLESS_INFO_SENT" on page 9-14
• "BSSMAP_PERF_LOC_ABORT_MSGS" on page 9-15
• "BSSMAP_PERF_LOC_REQ_MSGS" on page 9-16
• "BSSMAP_PERF_LOC_RESP_MSGS" on page 9-17
• "BSSMAPLE_CONLESS_INFO_RCV" on page 9-18
• "BSSMAPLE_CONLESS_INFO_SENT" on page 9-19
• "BSSMAPLE_PERF_LOC_ABORT_MSGS" on page 9-20
• "BSSMAPLE_PERF_LOC_REQ_MSGS" on page 9-21
• "BSSMAPLE_PERF_LOC_RESP_MSGS" on page 9-22
68P02901W56-R 9-3
BSSLAP_ABORT_RCV Chapter 9: 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.
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.
9-4 68P02901W56-R
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.

GSM 08.71 v7.2.0, sect. 2.2.7.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-5
BSSLAP_MS_POS_CMD Chapter 9: 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.
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.
9-6 68P02901W56-R
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.
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-R 9-7
BSSLAP_REJ Chapter 9: 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.

GSM 08.71 v7.2.0, sect. 2.2.5.
Fault finding.
Basis BSS.
Type Counter.
9-8 68P02901W56-R
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.

GSM 08.71 v7.2.0, sect. 2.2.6.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-9
BSSLAP_TA_REQ Chapter 9: 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.
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.
9-10 68P02901W56-R
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.

GSM 08.71 v7.2.0, sect. 2.2.2.
Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-11
BSSLAP_TOA_REQ Chapter 9: 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.

GSM 08.71 v7.2.0, sect. 2.2.3.
Fault finding.
Basis BSS.
Type Counter.
9-12 68P02901W56-R
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.

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-13
BSSMAP_CONLESS_INFO_SENT Chapter 9: 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.

Fault finding.
Basis BSS.
Type Counter.
9-14 68P02901W56-R
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.
Reference GSM 03.71 v7.4.0, sect 7.11.

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-15
BSSMAP_PERF_LOC_REQ_MSGS Chapter 9: 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.
Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.

Fault finding.
Basis BSS.
Type Counter.
9-16 68P02901W56-R
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.
Reference GSM 03.71 v7.4.0, sect 7.6, 7.11.

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-17
BSSMAPLE_CONLESS_INFO_RCV Chapter 9: 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.

Fault finding.
Basis BSS.
Type Counter.
9-18 68P02901W56-R
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.
Reference GSM 03.71 v7.4.0, sect. 7.8,

Fault finding.
Basis BSS.
Type Counter.
68P02901W56-R 9-19
BSSMAPLE_PERF_LOC_ABORT_MSGS Chapter 9: 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.
Reference GSM 03.71 v7.4.0, sect 7.11GSM 09.31 v7.1.0, sect 9.3.
Fault finding.
Basis BSS.
Type Counter.
9-20 68P02901W56-R
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.
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-R 9-21
BSSMAPLE_PERF_LOC_RESP_MSGS Chapter 9: 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.

GSM 09.31 v7.1.0, sect. 9.2
Fault finding.
Basis BSS.
Type Counter.
9-22 68P02901W56-R
Chapter
10
MTL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Message Transfer Link (MTL) statistics are used to track 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
are described in "MTL statistics subgroups" on page 10-2.
68P02901W56-R 10-1
MTL statistics subgroups Chapter 10: MTL statistics
MTL statistics subgroups

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

• "MTP C7 availability" on page 10-2.
• "MTP C7 performance" on page 10-3.
• "MTP C7 utilization" on page 10-4.
MTP C7 availability
MTP C7 availability statistics are used to track the duration of signalling 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 10-13.
• "MTP_LOCAL_BUSY" on page 10-14.
• "MTP_LOCAL_MGT" on page 10-15.
• "MTP_MGT_INHIBIT" on page 10-16.
• "MTP_MGT_UNINHIBIT" on page 10-17.
• "MTP_REMOTE_MGT" on page 10-22.
• "MTP_REMOTE_PROC" on page 10-23.
• "MTP_START_RPO" on page 10-33.
• "MTP_STOP_RPO" on page 10-34.
• "MTP_UNAVAILABLE" on page 10-36.
10-2 68P02901W56-R
Maintenance Information: GSM Statistics Application MTL statistics subgroups
MTP C7 performance
MTP C7 performance statistics are used track the different types of failure and recovery situations for
the MTP of the ITU-TSS No.7 protocol on the BSC to MSC interface. The following are the MTP C7
performance statistics:
• "MTP_CHANGEBACK" on page 10-9.
• "MTP_CHANGEOVER" on page 10-10.
• "MTP_LINK_INS" on page 10-12.
• "MTP_NEG_ACKS" on page 10-20.
• "MTP_RESTORATION" on page 10-24.
• "MTP_SL_ACK" on page 10-27.
• "MTP_SL_ALIGNMENT" on page 10-28.
• "MTP_SL_CONGESTION" on page 10-29.
• "MTP_SL_ERROR_RATE" on page 10-30.
• "MTP_SL_FAIL" on page 10-31.
• "MTP_SL_FIBR" on page 10-32.
• "MTP_SU_ERROR" on page 10-35.
68P02901W56-R 10-3
MTL statistics subgroups Chapter 10: MTL statistics
MTP C7 utilization
MTP C7 utilization statistics are used to track the number of messages received, transmitted and retransmitted
on signalling links and supply information on signalling link congestion for the MTP of the ITU-TSS No.7
protocol on the BSC to MSC interface. The following are the MTP C7 utilization statistics:
• "BUSY_CICS" on page 10-5.
• "CONGESTION_LOST_MSU" on page 10-7.
• "MSU_DISCARDED" on page 10-8.
• "MTP_CONGESTION" on page 10-11.
• "MTP_MSU_RX" on page 10-18.
• "MTP_MSU_TX" on page 10-19.
• "MTP_RE_TX" on page 10-21.
• "MTP_SIF_SIO_RX" on page 10-25.
• "MTP_SIF_SIO_TX" on page 10-26.
• "SIB_RX" on page 10-37.
• "SIB_RX" on page 10-37.
• "SL_CONGESTION" on page 10-39.
• "SL_STOP_CONGESTION" on page 10-40.
10-4 68P02901W56-R
Maintenance Information: GSM Statistics Application BUSY_CICS
BUSY_CICS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The BUSY_CICS statistic tracks the number of BUSY CICS during an interval. This weighted distribution
statistics produces 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 10-1 BUSY CICS
Bin Range
0 0 to 9
1 10 to 49
2 50 to 99
3 100 to 199
4 200 to 399
5 400 to 799
6 800 to 1199
7 1200 to 1599
8 1600 to 2199
9 2200 to 3200
Pegging
This statistic is pegged each time an allocation or deallocation 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.
68P02901W56-R 10-5
BUSY_CICS Chapter 10: MTL statistics
Analysis
Since each call is routed via 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.
Usage Quality of service monitoring.
Network planning.
Optimization.
Basis BSS.
10-6 68P02901W56-R
Maintenance Information: GSM Statistics Application CONGESTION_LOST_MSU
CONGESTION_LOST_MSU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CONGESTION_LOST_MSU statistic tracks the number of times Message Signalling Units (MSU) are
being lost due to Signalling 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
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-R 10-7
MSU_DISCARDED Chapter 10: MTL statistics
MSU_DISCARDED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MSU_DISCARDED statistic tracks the number of MSUs discarded while there is congestion on the
Signalling Link (SL).
Pegging
This statistic pegs each time a MSU is discarded while there is congestion on the SL.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of MSUs are 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 - PM alarm
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.
10-8 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_CHANGEBACK
MTP_CHANGEBACK
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CHANGEBACK statistic tracks the number of local automatic changebacks that have been
successfully completed.
Pegging
This statistic pegs when MTP traffic that has been changed over to an alternate Signalling Link (SL) is
diverted back to the original SL.
Analysis
This statistic can be used for trend analysis of automatic changebacks that have been successfully completed.
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-R 10-9
MTP_CHANGEOVER Chapter 10: MTL statistics
MTP_CHANGEOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CHANGEOVER statistic tracks the number of local automatic changeovers that have been
successfully completed. This indicates MTP traffic is being transferred from a Signalling 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 successfully
completed.
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.
10-10 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_CONGESTION
MTP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_CONGESTION statistic tracks the length of time that a signalling link is congested. This
can be used to indicate signalling link congestion.
Pegging
The timer for this statistic is started when congestion is detected on a signalling link. The timer is stopped
when normal operation is resumed.
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-R 10-11
MTP_LINK_INS Chapter 10: MTL statistics
MTP_LINK_INS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LINK_INS statistic tracks the length of time that a signalling 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).
Basis SS7_LINK.
10-12 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_LINKFAIL
MTP_LINKFAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LINKFAIL statistic tracks the duration of Signalling 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.
68P02901W56-R 10-13
MTP_LOCAL_BUSY Chapter 10: MTL statistics
MTP_LOCAL_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LOCAL_BUSY statistic tracks the total time congestion is present on the local end of the
Pegging
This statistic is started when 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 durations 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.
10-14 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_LOCAL_MGT
MTP_LOCAL_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_LOCAL_MGT statistic tracks the total time that a local Signalling 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.
68P02901W56-R 10-15
MTP_MGT_INHIBIT Chapter 10: MTL statistics
MTP_MGT_INHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MGT_INHIBIT statistic tracks the number of times the Signalling 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 the associated
MTP link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
10-16 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_MGT_UNINHIBIT
MTP_MGT_UNINHIBIT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MGT_UNINHIBIT statistic tracks the number of times the Signalling 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 the associated
MTP link.
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-R 10-17
MTP_MSU_RX Chapter 10: MTL statistics
MTP_MSU_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MSU_RX statistic tracks the number of Message Signal Units (MSUs) received on a particular
signalling link.
Pegging
This statistic pegs each time MSUs are received over the signalling link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
10-18 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_MSU_TX
MTP_MSU_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs) transmitted on a particular
signalling link.
Pegging
This statistic pegs each time MSUs are transmitted over the signalling link.
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-R 10-19
MTP_NEG_ACKS Chapter 10: MTL statistics
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
messages between a BSS and a MSC that are acceptable in normal system operations.
If the specified threshold is exceeded, the 7. MTL: SL number of negative acks received - 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 Warning.
10-20 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_RE_TX
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.
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-R 10-21
MTP_REMOTE_MGT Chapter 10: MTL statistics
MTP_REMOTE_MGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_REMOTE_MGT statistic tracks the total time a Signalling 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.
10-22 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_REMOTE_PROC
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.
68P02901W56-R 10-23
MTP_RESTORATION Chapter 10: MTL statistics
MTP_RESTORATION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_RESTORATION statistic tracks the number of times user traffic is allowed on a Signalling 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.
10-24 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_SIF_SIO_RX
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 signalling link.
Pegging
This statistic pegs each time an SIF or SIO is received over the signalling link.
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-R 10-25
MTP_SIF_SIO_TX Chapter 10: MTL statistics
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 signalling link.
Pegging
This statistic pegs each time an SIF or SIO are transmitted over the signalling link.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 - (3.2 - 3.10).
Basis SS7_LINK.
Type Counter.
10-26 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_SL_ACK
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 acknowledgement 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 acknowledgement of an
MSU is not sent.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of
acknowledgements 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 - PM alarm will
be generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for
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.
68P02901W56-R 10-27
MTP_SL_ALIGNMENT Chapter 10: MTL statistics
MTP_SL_ALIGNMENT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ALIGNMENT statistic tracks the number of unsuccessful attempts to align an out of service
Signalling 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
A threshold value should be assigned to this statistic which reflects the maximum number of unsuccessful
attempts to align an out of service SL to the A interface that are acceptable in normal system operations.
If the specified threshold is exceeded, the 5. MTL: SL alignment failure - PM alarm is generated. Refer
information.
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.
10-28 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_SL_CONGESTION
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 congestion - PM
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.
68P02901W56-R 10-29
MTP_SL_ERROR_RATE Chapter 10: MTL statistics
MTP_SL_ERROR_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_ERROR_RATE statistic tracks the number of times that a Signalling 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
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 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.
10-30 68P02901W56-R
Maintenance Information: GSM Statistics Application MTP_SL_FAIL
MTP_SL_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_FAIL statistic tracks Signalling Link (SL) failure for all causes except operator interaction
through the MMI.
Pegging
This statistic pegs when an 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 operator interaction with the MMI, that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. MTL: SL failure - all reasons - PM alarm is generated. Refer
information.
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-R 10-31
MTP_SL_FIBR Chapter 10: MTL statistics
MTP_SL_FIBR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_SL_FIBR statistic tracks the messages between a BSS and a remote site are out of sequence,
causing the Signalling Link (SL) to go out of service. This statistic is similar to 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
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 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 Major.
10-32 68P02901W56-R
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 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 Warning.
68P02901W56-R 10-33
MTP_STOP_RPO Chapter 10: 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.
10-34 68P02901W56-R
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
Pegging
This statistic pegs each time an erroneous signal unit is received on the SL.
Analysis
A threshold value should be assigned to this statistic reflecting the maximum number of times 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 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 Warning.
68P02901W56-R 10-35
MTP_UNAVAILABLE Chapter 10: MTL statistics
MTP_UNAVAILABLE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTP_UNAVAILABLE statistic tracks the total time a Signalling Link (SL) is out of service for all
reasons including operator intervention.
Pegging
This statistic records the duration of SL unavailability for all reasons, including 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 SS7_LINK.
10-36 68P02901W56-R
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 signalling 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.
Basis SS7_Link.
Type Counter.
68P02901W56-R 10-37
SIB_TX Chapter 10: 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 signalling
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.
Basis SS7_Link.
Type Counter.
10-38 68P02901W56-R
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 on a Signalling 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
A threshold value should be assigned to this statistic which reflects the maximum number of 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 congestion - PM
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-R 10-39
SL_STOP_CONGESTION Chapter 10: MTL statistics
SL_STOP_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SL_STOP_CONGESTION statistic tracks Signalling Link (SL) congestion stoppage.
Pegging
This statistic is pegged each time the signalling link congestion indication stops.
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.
10-40 68P02901W56-R
Chapter
11
CBL, GSL, OML, RSL and XBL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25/LAPD statistics included here, are used to track BSS data transmission information. These statistics
relate to events on the following links:
• Cell Broadcast Link (CBL).
• GPRS Signalling Link (GSL).
• Operation and Maintenance Link (OML).
• Radio System Link (RSL).
• RXCDR to BSC Link (XBL).
• {24347} AXCDR to BSC Link (XBL).

The statistics are listed in "X.25/LAPD Level: X.25 and LAPD statistics" on page 11-2.
68P02901W56-R 11-1
X.25/LAPD Level: X.25 and LAPD statistics Chapter 11: CBL, GSL, OML, RSL and XBL statistics
X.25/LAPD Level: X.25 and LAPD statistics

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
X.25 and LAPD statistics are used to track BSS data transmission information. The following are the X.25
and LAPD statistics:
• "ATER_CHANNEL_REQUEST" on page 11-3.
• "ATER_CHANNEL_STATUS" on page 11-4.
• {24347} "ATER_PREEMPT_ATMPT" on page 11-6.
• {24347} "ATER_PREEMPT_ATMPT_SWOVER" on page 11-7.
• {24347} "ATER_PREEMPT_FAIL" on page 11-8.
• {24347} "ATER_PREEMPT_FAIL_SWOVER" on page 11-9.
• {24347} "ATER_PREEMPT_RQD" on page 11-10.
• "FRMR" on page 11-11.
• "I_FRAMES_RX" on page 11-12.
• "I_FRAMES_TX" on page 11-13.
• "INVALID_FRAMES_RX" on page 11-14.
• "LAPD_CONGESTION" on page 11-15.
• "N2_EXPIRY" on page 11-16.
• "SABM_TX" on page 11-17.
11-2 68P02901W56-R
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-R 11-3
ATER_CHANNEL_STATUS Chapter 11: 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.

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 was invoked. The pegging of this statistic
represents the scenario where the number of
available Ater channels to an associated RXCDR
falls below the darbc_block threshold (the BSC is
operating in dynamic mode). The BSC automatically
blocks at the MSC all remaining idle CICs that are
routed through the associated RXCDR. All OOS
and idle CICs will have the Low Ater Resources
reason set.
11-4 68P02901W56-R
Maintenance Information: GSM Statistics Application ATER_CHANNEL_STATUS
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-R 11-5
ATER_PREEMPT_ATMPT Chapter 11: CBL, GSL, OML, RSL and XBL statistics
ATER_PREEMPT_ATMPT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The ATER_PREEMPT_ATMPT statistic tracks the number of times the Ater pre-emption mechanism is
successful in finding a resource to pre-empt (excluding switchover scenarios).
Pegging
The BSS pegs the ATER_PREEMPT_ATMPT statistic when the Ater pre-emption mechanism is successful
in finding a resource to pre-empt (excluding switchover scenarios).
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
11-6 68P02901W56-R
Maintenance Information: GSM Statistics Application ATER_PREEMPT_ATMPT_SWOVER
ATER_PREEMPT_ATMPT_SWOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The ATER_PREEMPT_ATMPT_SWOVER statistic tracks the number of times the Ater pre-emption
mechanism is successful in finding a resource to pre-empt due to switchover scenarios.
Pegging
The BSS pegs the ATER_PREEMPT_ATMPT_SWOVER statistic when the Ater pre-emption mechanism is
successful in finding a resource to pre-empt due to switchover scenarios.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
68P02901W56-R 11-7
ATER_PREEMPT_FAIL Chapter 11: CBL, GSL, OML, RSL and XBL statistics
ATER_PREEMPT_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The ATER_PREEMPT_FAIL statistic tracks the number of times the Ater pre-emption mechanism fails to
allocate a resource (for non-switchover cases only).
Pegging
The BSS pegs the ATER_PREEMPT_FAIL statistic when Ater pre-emption fails due to a conflict between
BSS mechanisms or when there are multiple failures in pre-emption mechanism.
For multiple failures, the ATER_PREEMPT_FAIL statistic pegs only once.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number of times the Ater
pre-emption mechanism is unsuccessful.
If the specified threshold is exceeded, the 0. AXCDR: PM Alarm will be generated. Refer to the
Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
11-8 68P02901W56-R
Maintenance Information: GSM Statistics Application ATER_PREEMPT_FAIL_SWOVER
ATER_PREEMPT_FAIL_SWOVER
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
This new statistic tracks the number of times the Ater pre-emption mechanism fails to allocate a resource
(for switchover cases only).
Pegging
The BSS pegs the ATER_PREEMPT_FAIL_SWOVER statistic when Ater pre-emption fails due to a conflict
between BSS mechanisms or when there are multiple failures in pre-emption mechanism.
For multiple failures, the ATER_PREEMPT_FAIL_SWOVER statistic pegs only once.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
68P02901W56-R 11-9
ATER_PREEMPT_RQD Chapter 11: CBL, GSL, OML, RSL and XBL statistics
ATER_PREEMPT_RQD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24347}
Description
The ATER_PREEMPT_RQD statistic tracks the number of times the ATER pre-emption mechanism is
triggered.
The BSS triggers the Ater pre-emption mechanism when no 8kbps or 16kbps resources are available to satisfy
the requirements of a request with pre-emption capability (PCI = 1 and priority level less than 14).
Pegging
The BSS shall peg the ATER_PREEMPT_RQD statistic when Ater pre-emption is triggered.
Analysis
Reference None.
Network planning.
Basis AXCDR.
Type Counter.
11-10 68P02901W56-R
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 is received that is not recoverable.
Reference ITU-TSS Q.920 - 1ITU-TSS X.20 - X.32

Usage X.25/LAPD.
Fault finding.
Basis X25_LINK/LAPD_LINK.
Type Counter.
Alarm Warning.
68P02901W56-R 11-11
I_FRAMES_RX Chapter 11: 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.
Reference ITU-TSS Q.920 - 1.

ITU-TSS X.20 - X.32.
Usage X.25/LAPD.
Type Counter.
11-12 68P02901W56-R
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 peg when an I-Frame is transmitted.

Usage X.25/LAPD.
Type Counter.
68P02901W56-R 11-13
INVALID_FRAMES_RX Chapter 11: 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).
• LAPD
◦ On the RSL (BSS-BTS link).
◦ On the XBL (BSC-RXCDR link).

Usage X.25/LAPD.
Fault finding.
Type Counter.
Alarm Warning.
11-14 68P02901W56-R
Maintenance Information: GSM Statistics Application LAPD_CONGESTION
LAPD_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The LAPD_CONGESTION statistic tracks the time that the LAPD or X.25 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.
The exec-dlsp process has a bigger buffer to hold outgoing messages therefore the messages will
not get dropped even during the congestion period.
Pegging
This statistic pegs when the transmit buffer gets full and stops when the buffer is available again.

Usage X.25/LAPD.
Fault finding.
Type Duration.
68P02901W56-R 11-15
N2_EXPIRY Chapter 11: CBL, GSL, OML, RSL and XBL statistics
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.

Usage X.25/LAPD.
Fault finding.
Type Counter.
Alarm Minor.
11-16 68P02901W56-R
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.

Usage X.25/LAPD.
Type Counter.
68P02901W56-R 11-17
SABM_TX Chapter 11: CBL, GSL, OML, RSL and XBL statistics
11-18 68P02901W56-R
Chapter
12
PCU statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PCU statistics are captured from events occurring at the Packet Control Unit (PCU). They are categorized into
subgroups, each of which are described in "PCU statistics subgroups" on page 12-2.
68P02901W56-R 12-1
PCU statistics subgroups Chapter 12: PCU statistics
PCU statistics subgroups

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

• "GBL statistics" on page 12-2.
• "Accessibility statistics" on page 12-2.
• "Throughput statistics" on page 12-4.
• {22577} "Utilisation statistics" on page 12-6.
GBL statistics
The GBL device refers to the configured number of timeslots 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 signalling and user data are sent on the same
physical resource, that is, no dedicated physical resources are required to be allocated for signalling purposes.
The GBL measurement types are listed as follows:
• "CELL_FLUSH_REQS" on page 12-12
• "GBL_DL_DATA_THRPUT" on page 12-89
• "GBL_DL_DATA_THRPUT_HIST" on page 12-90
• "GBL_FLOW_CTRL_SENT" on page 12-92
• "GBL_PAGING_REQS" on page 12-93
• "GBL_UL_DATA_THRPUT" on page 12-94
• "GBL_UL_DATA_THRPUT_HIST" on page 12-95
• "GBL_UNAVAILABLE" on page 12-97
Accessibility statistics
Accessibility statistics measure how effectively GPRS resources are being accessed. These measurements
assist the operator in planning the necessary resources needed for the MS to efficiently access the network.
12-2 68P02901W56-R
Maintenance Information: GSM Statistics Application PCU statistics subgroups
The accessibility statistics include the following:

• "CH_REQ_UNSVCD_PCU" on page 12-13
• "CHANNEL_REQS_REC" on page 12-15
• "CHANNEL_REQS_REJECT" on page 12-17
• "CHANNEL_REQS_SUCCESS" on page 12-18
• "CODING_SCHEME_CHANGE" on page 12-20
• "CS12_ON_32K_CHAN" on page 12-25
• "EGPRS_64K_CHANNELS_SWITCHED" on page 12-84
• "EGPRS_64K_NOT_AVAIL" on page 12-85
• "EGPRS_DL_ASGN_PCCCH" on page 12-87
• "G_RACH_UNSVCD_BTS" on page 12-88
• "GPRS_32K_CHANNELS_SWITCHED" on page 12-98
• "GPRS_32K_DL_NOT_AVAIL" on page 12-99
• "GPRS_32K_UL_NOT_AVAIL" on page 12-100
• "GPRS_ACCESS_PER_AGCH" on page 12-101
• "GPRS_ACCESS_PER_RACH" on page 12-102
• "GPRS_CELL_RESELECT_FAIL" on page 12-107
• "GPRS_CHANNELS_SWITCHED" on page 12-108
• "GPRS_DL_ASGN_PCCCH" on page 12-109
• "GPRS_PCH_AGCH_Q_LENGTH" on page 12-110
• "GPRS_PPCH_PAGCH_Q_LENGTH" on page 12-111
• "GPRS_PRR_BLK_USG" on page 12-112
• "GPRS_RACH_ARRIVAL" on page 12-114
• "NO_PDTCH_AVAIL" on page 12-123
• "NO_PDTCH_AVAIL_TIME" on page 12-124
68P02901W56-R 12-3
Throughput statistics
The throughput statistics are listed as follows:

• "AIR_DL_CONTROL_BLKS" on page 12-8
• "AIR_DL_TBF_FAILURES" on page 12-9
• "AIR_UL_CONTROL_BLKS" on page 12-10
• "AIR_UL_TBF_FAILURES" on page 12-11
• "CONG_REL_DL_SCTS" on page 12-22
• {22577} "DL_BLER_CS1" on page 12-27
• {22577} "DL_BLER_CS2" on page 12-28
• {22577} "DL_BLER_CS3" on page 12-29
• {22577} "DL_BLER_CS4" on page 12-31
• {22577} "DL_BLER_MCS1" on page 12-33
• "DL_BUSY_PDTCH" on page 12-51
• {22577} "DL_LLC_FRAMES_GB" on page 12-53
• {22577} "DL_LLC_FRAMES_PCU" on page 12-54
• "DL_PDTCH_Q_LENGTH" on page 12-55
• "DL_PDTCH_SEIZURE" on page 12-56
• "DL_RADIO_BLKS_1_TS" on page 12-57
12-4 68P02901W56-R
• "DL_RLC_ACK_NEW_BLKS" on page 12-69
• "DL_RLC_DDTR_BLKS" on page 12-71
• "DL_RLC_NACK_BLKS" on page 12-72
• "DL_RLC_RETX_BLKS" on page 12-74
• "DL_RLC_STALLED_BLKS" on page 12-76
• "DL_RLC_UNACK_NEW_BLKS" on page 12-78
• "DL_TBF_TIME_1_TS" on page 12-80
• "EGPRS_AVAIL_PDTCH" on page 12-86
• "GBL_DL_DATA_THRPUT" on page 12-89
• "GBL_DL_DATA_THRPUT_HIST" on page 12-90
• "GBL_UL_DATA_THRPUT" on page 12-94
• "GBL_UL_DATA_THRPUT_HIST" on page 12-95
• "GPRS_AVAIL_PDTCH" on page 12-103
• "IDLE_PDTCH_INTF_BAND1" on page 12-117
• "IMM_ASSGN_CAUSE" on page 12-121
• "PRP_LOAD" on page 12-129
• {22577} "UL_BLER_CS1" on page 12-135
• {22577} "UL_BLER_CS2" on page 12-137
• {22577} "UL_BLER_CS3" on page 12-139
• {22577} "UL_BLER_CS4" on page 12-140
• {22577} "UL_BLER_MCS1" on page 12-142
68P02901W56-R 12-5
• "UL_BUSY_PDTCH" on page 12-160
• {22577} "UL_LLC_FRAMES" on page 12-162
• "UL_PDTCH_Q_LENGTH" on page 12-163
• "UL_PDTCH_SEIZURE" on page 12-164
• "UL_RADIO_BLKS_8PSK_1_TS" on page 12-165
• "UL_RADIO_BLKS_8PSK_2_TS" on page 12-167
• "UL_RADIO_BLKS_GMSK_1_TS" on page 12-169
• "UL_RADIO_BLKS_GMSK_2_TS" on page 12-171
• "UL_RLC_ACK_NEW_BLKS" on page 12-173
• "UL_RLC_RETX_BLKS" on page 12-175
• "UL_RLC_UNACK_NEW_BLKS" on page 12-177
• "UL_TBF_TIME_8PSK_1_TS" on page 12-179
• "UL_TBF_TIME_8PSK_2_TS" on page 12-180
• "UL_TBF_TIME_GMSK_1_TS" on page 12-181
• "UL_TBF_TIME_GMSK_2_TS" on page 12-182
Utilisation statistics
{22577}
Utilisation statistics measure how effectively GPRS resources are being utilised. These measurements assist
the operator in planning the necessary resources needed for the MS to efficiently use the network.
12-6 68P02901W56-R
The utilisation statistics include the following:

• "CS1234_ON_64K_CHAN" on page 12-26
• "CS_PAGE_REQS" on page 12-24
• "GPRS_CELL_CONGESTION" on page 12-105
• "PACCH_PAGE_REQS" on page 12-125
• "PDU_DISCARD_FR" on page 12-126
• "PDU_DISCARD_LLC" on page 12-127
• "PS_PAGE_REQS" on page 12-131
• "TBF_DL_ASGN_PACCH" on page 12-132
• "TBF_REL_PACCH_LOST" on page 12-133
• "TBF_SESSIONS" on page 12-134
68P02901W56-R 12-7
AIR_DL_CONTROL_BLKS Chapter 12: PCU statistics
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.
Analysis
This statistic can be used for the trend analysis of the number of Radio Link Control blocks sent by the PCU.
Reference None.
Usage Performance management.
Basis Cell.
Type Counter.
12-8 68P02901W56-R
Maintenance Information: GSM Statistics Application AIR_DL_TBF_FAILURES
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.
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 18-80 in Chapter 18, "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.
Reference None
Usage Performance management
Basis Cell.
Type Counter array.
68P02901W56-R 12-9
AIR_UL_CONTROL_BLKS Chapter 12: PCU statistics
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.
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.
12-10 68P02901W56-R
Maintenance Information: GSM Statistics Application AIR_UL_TBF_FAILURES
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.
Bin Description
0 Establishment.
1 Data transfer.
2 Termination.
Pegging
This statistic pegs each time that 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.
Reference None
Basis Cell.
Type Counter array.
68P02901W56-R 12-11
CELL_FLUSH_REQS Chapter 12: PCU statistics
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.
This statistic was previously known as GBL_FLUSH_REQS.
12-12 68P02901W56-R
Maintenance Information: GSM Statistics Application CH_REQ_UNSVCD_PCU
CH_REQ_UNSVCD_PCU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CH_REQ_UNSVCD_PCU statistic tracks the total number of uplink GPRS channel requests unservice
by the PCU.
The bins are:
• RACH - RSL bandwidth limitation.
• RACH - Round Trip Delay (RTD) / timeout.
• RACH - Insufficient resources.
• PRACH - Round Trip Delay (RTD) / timeout.
• PRACH - Insufficient resources.
• PRR - Round Trip Delay (RTD) / timeout.
• PRR - Insufficient resources.
• PDAK - Insufficient resources.
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 above.
Pegging
This statistic is pegged for each channel request unserviced by the PCU.
68P02901W56-R 12-13
CH_REQ_UNSVCD_PCU Chapter 12: PCU statistics
Analysis
This statistic can be used for the trend analysis of the PCU.
Reference None.
Basis Cell.
Type Counter array.
12-14 68P02901W56-R
Maintenance Information: GSM Statistics Application CHANNEL_REQS_REC
CHANNEL_REQS_REC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CHANNEL_REQS_REC statistic tracks the number of channel or resource request messages received
by the PCU.
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.
68P02901W56-R 12-15
CHANNEL_REQS_REC Chapter 12: PCU statistics
The OMC displays the bins alphabetically.

To see the relationship between the MS, BSS, and MSC for this statistic, refer to "Accessibility statistics"
Pegging
This statistic pegs for each channel request message received. The bin that is incremented is determined
by the channel request message type.
Reference None.
Basis Cell.
Type Counter array.
12-16 68P02901W56-R
Maintenance Information: GSM Statistics Application CHANNEL_REQS_REJECT
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.
Reference None.
Congestion.
Basis Cell.
Type Counter.
68P02901W56-R 12-17
CHANNEL_REQS_SUCCESS Chapter 12: PCU statistics
CHANNEL_REQS_SUCCESS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic counts the number of channel or resource requests that are actually allocated a TBF resource
successfully.
This statistic specifically counts the number of ASSIGNMENT messages sent to the MS. Re-transmissions
are excluded.

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_CP_A A GPRS PUA in response to a “channel
request” received in a Packet Downlink
ACK.
6 CHANNEL_REQS_SUCCESS_E_C An Enhanced One-Phase (EOP) Access
indication is received on CCCH.
7 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).
8 CHANNEL_REQS_SUCCESS_E_1P_CCC An EOP Access PIA is sent on CCCH.
9 CHANNEL_REQS_SUCCESS_E_1P_PCCC An EOP access PUA is sent on PCCCH.
10 CHANNEL_REQS_SUCCESS_E_SB_CCC An EGPRS Single Block Allocation PIA
is sent on CCCH.
11 CHANNEL_REQS_SUCCESS_E_SB_PCCC An EGPRS Single Block Allocation
PUA is sent on PCCCH.
Cont.
12-18 68P02901W56-R
Maintenance Information: GSM Statistics Application CHANNEL_REQS_SUCCESS

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.
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.
Reference Digital cellular telecommunications systems (phase 2+) Version

7.0.0 Jan 2000 ETSI.
Usage Congestion, network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 12-19
CODING_SCHEME_CHANGE Chapter 12: PCU statistics
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 downgrades (from higher to lower coding scheme)
for uplink and downlink in a statistical measurement period.
Controls blocks (always sent at CS-1) will result in this statistic not being pegged.
Downlink coding scheme transitions for dummy blocks (when entering and exiting super-coattail)
will not be counted.
The bins are defined in Table 12-1:
12-20 68P02901W56-R
Maintenance Information: GSM Statistics Application CODING_SCHEME_CHANGE
Table 12-1 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.
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.

7.0.0 Jan 2000 ETSI.
Usage Congestion, network planning.
Basis Cell.
Type Counter array.
68P02901W56-R 12-21
CONG_REL_DL_SCTS Chapter 12: PCU statistics
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 (500ms) old super-coattail will be 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 (300ms) old super-coattail will be terminated if the:

◦ cell availability reached is ≤ 30%, in a cell with > 5 TS.
The minimum super-coattail duration is 15 block periods or 300ms. No super-coattail below 15 block
periods are terminated.
This statistic is accessible only if the Increased PRP Capacity feature introduced by Enhanced
Scheduling feature RDB 4441 is unrestricted.
Pegging
This statistic pegs each time that an uplink TBF is successfully established and later released under delayed
TBF release mode to relieve the congestion in a cell during a statistical measurement interval.
12-22 68P02901W56-R
Maintenance Information: GSM Statistics Application CONG_REL_DL_SCTS
Reference None
Basis Cell.
Type Counter.
68P02901W56-R 12-23
CS_PAGE_REQS Chapter 12: PCU statistics
CS_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The CS_PAGE_REQS statistic represents the total number of circuit switched page requests received by
the PCU.
Pegging
One unit represents 1 CS page request.
Analysis
Reference None.
Basis GBL.
Type Counter.
12-24 68P02901W56-R
Maintenance Information: GSM Statistics Application CS12_ON_32K_CHAN
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 timeslots 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.
Reference None.
Network planning.
Basis Cell.
Type Percentage.
68P02901W56-R 12-25
CS1234_ON_64K_CHAN Chapter 12: PCU statistics
CS1234_ON_64K_CHAN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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.
12-26 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_BLER_CS1
DL_BLER_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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 12-2 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 will be
represented as X+1.
The range is 0 to 9000. PDAKs can be received as frequently as once in every 2 blocks. So in a one-hour
period, there will be at most 3,600,000ms / (2x20ms) = 90,000 PDAKs being received. Thus there will be at
most 90,000 calculations, and the maximum value will be 9,000 for each bin.
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-27
DL_BLER_CS2 Chapter 12: PCU statistics
DL_BLER_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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.
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-28 68P02901W56-R
DL_BLER_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
This statistics 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%
represented as X+1.
68P02901W56-R 12-29
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-30 68P02901W56-R
DL_BLER_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
This statistics 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%
represented as X+1.
68P02901W56-R 12-31
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-32 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_BLER_MCS1
DL_BLER_MCS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The DL_BLER_MCS2 statistics indicates the number of times, measured at statistical intervals, the BLER of
a particular carrier, when using EDGE 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 EDGE feature is disabled.
Pegging
Table 12-6 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
will be represented as X+1.
68P02901W56-R 12-33
DL_BLER_MCS1 Chapter 12: PCU statistics
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-34 68P02901W56-R
DL_BLER_MCS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The DL_BLER_MCS2 statistic indicates the number of times, measured at statistical intervals, the BLER of
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%
68P02901W56-R 12-35
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-36 68P02901W56-R
DL_BLER_MCS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
68P02901W56-R 12-37
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-38 68P02901W56-R
DL_BLER_MCS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
Pegging
Table 12-9 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%
68P02901W56-R 12-39
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-40 68P02901W56-R
DL_BLER_MCS5
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
68P02901W56-R 12-41
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-42 68P02901W56-R
DL_BLER_MCS6
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
most 90,000 calculations, and the maximum number value will be 9,000 for each bin.
68P02901W56-R 12-43
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-44 68P02901W56-R
DL_BLER_MCS7
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
68P02901W56-R 12-45
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-46 68P02901W56-R
DL_BLER_MCS8
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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
68P02901W56-R 12-47
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-48 68P02901W56-R
DL_BLER_MCS9
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
68P02901W56-R 12-49
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-50 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_BUSY_PDTCH
DL_BUSY_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean, max and min number of occupied Packet Data CHannels (PDCH) carrying
downlink packet traffic.
This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, at every packet-scheduling
period (20 millisecond).
Table 12-15 shows the ranges for each bin (measured in milliseconds).
Table 12-15 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.
68P02901W56-R 12-51
DL_BUSY_PDTCH Chapter 12: PCU statistics
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for downlink packet traffic.

7.0.0 Jan 2000 ETSI.
Usage Network planning, congestion.
Basis Cell
12-52 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_LLC_FRAMES_GB
DL_LLC_FRAMES_GB
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The DL_LLC_FRAMES_GB statistic represents the total number of downlink LLC frames correctly received
from 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 12-16 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 will be represented as X+1.
The range is 0 to 65535. The maximum number of LLC frames received from SGSN during a one-hour period
can’t be accurately estimated. Use the uplimit of a 16-bit unsigned integer.
Analysis
Reference None.
Basis Cell.
Type Counter array.
68P02901W56-R 12-53
DL_LLC_FRAMES_PCU Chapter 12: PCU statistics
DL_LLC_FRAMES_PCU
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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 12-17 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
1 unit represents 10 LLC frames. 10X+Y (1<=Y<=10) calculations will be represented as X+1.
The range is 0 to 65535. The maximum number of LLC frames received from other cells during a one-hour
period can not be accurately estimated. Use the uplimit of a 16-bit unsigned integer.
Analysis
Reference None.
Basis Cell.
Type Counter array.
12-54 68P02901W56-R
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 20ms. It is incremented when a request is added to the queue and is decremented
when a request is processed, that is, leaves the queue.
Analysis
This statistic can be used for the trend analysis of the average number of downlink messages waiting for a
PDTCH to become available.

7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Gauge.
68P02901W56-R 12-55
DL_PDTCH_SEIZURE Chapter 12: PCU statistics
DL_PDTCH_SEIZURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the downlink. The
purpose of this statistic is to count 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 mobile is listening on the
PDTCH. Specifically, it is pegged when the network receives the first DAK from the mobile.
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.

7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Counter.
12-56 68P02901W56-R
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 mobiles that
support a maximum of 1 TS in the downlink direction.
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.
The RLC radio blocks are split into the four GPRS channel coding schemes and the nine EGPRS coding
schemes, as shown in Table 12-18.
Table 12-18 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
68P02901W56-R 12-57
DL_RADIO_BLKS_1_TS Chapter 12: PCU statistics
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.
(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 in conjunction with DL_TBF_TIME_1_TS to

calculate the effective downlink throughput per terminal type for mobile multislot classes supporting one
PDTCH in downlink.
An MS can have different MS multislot classes for GPRS (GMSK) and EGPRS (8-PSK).
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 1 TS in the downlink
direction as follows:
• Always pegged for mobiles 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.
12-58 68P02901W56-R
Analysis
Reference None
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-59
DL_RADIO_BLKS_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
100 RLC radio blocks = 1 unit. The maximum statistical interval is 60 minutes. The translation of 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 coding
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
12-60 68P02901W56-R

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

calculate the effective downlink throughput per terminal type for mobile multislot classes supporting two
PDTCHs in downlink.
Pegging
• Always pegged for mobiles with multislot class 2, 3 or 5.
• CS-1 through CS-4 are pegged if the GPRS TBF is assigned to the mobile 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 mobile and the
EGPRS multislot is class 2, 3 or 5.

68P02901W56-R 12-61
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-62 68P02901W56-R
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
68P02901W56-R 12-63

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

calculate the effective downlink throughput per terminal type for mobile multislot classes supporting three
PDTCHs in downlink.
Pegging
• Always pegged for mobiles 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.

12-64 68P02901W56-R
Analysis
Reference None
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-65
DL_RADIO_BLKS_4_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
12-66 68P02901W56-R

(NACK, NACK) NACK
(NACK, NEW) NACK
(NEW, NEW) NEW
(NEW, ACK_PEND) NEW
(NACK, STALL) STALL
(NEW, STALL) STALL
Multislot classes 14–29 will be treated as multislot class 10.

calculate the effective downlink throughput per terminal type for mobile multislot classes supporting four
PDTCHs in downlink.
Pegging
• Always pegged for mobiles 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.

Only RLC data radio blocks are counted. No retransmissions due to any cause are pegged. The RLC radio
68P02901W56-R 12-67
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-68 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_ACK_NEW_BLKS
DL_RLC_ACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistics DL_RLC_ACK_NEW_BLKS and DL_RLC_UNACK_NEW_BLKS are a

replacement for the AIR_DL_DATA_BLKS statistic (available in GSR4, GSR5, GSR5.1,
GSR6 and GSR7 software releases).
The DL_RLC_ACK_NEW_BLKS statistic measures the total number of new RLC acknowledge mode
blocks sent for the first time by the PCU over the cell.
Table 12-22 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
68P02901W56-R 12-69
DL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics

(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
Usage
Basis Cell
Type Counter array
12-70 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_DDTR_BLKS
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 12-23.
Table 12-23 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
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-71
DL_RLC_NACK_BLKS Chapter 12: PCU statistics
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 mobile.
Table 12-24 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
12-72 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_NACK_BLKS

(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 mobile. The RLC radio
Analysis
Reference None
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-73
DL_RLC_RETX_BLKS Chapter 12: PCU statistics
DL_RLC_RETX_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_RLC_RETX_BLKS statistic measures the total number of pre-emptive retransmissions (or ack
pending blocks and acknowledged retransmissions) sent by the PCU over the cell.
Table 12-25 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
12-74 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_RETX_BLKS

(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 pre-emptive 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
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-75
DL_RLC_STALLED_BLKS Chapter 12: PCU statistics
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 12-26 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
12-76 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_STALLED_BLKS

(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
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-77
DL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics
DL_RLC_UNACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistics DL_RLC_UNACK_NEW_BLKS and DL_RLC_ACK_NEW_BLKS are a

replacement for the AIR_DL_DATA_BLKS statistic (available in GSR4, GSR5, GSR5.1,
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 12-27 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
12-78 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_RLC_UNACK_NEW_BLKS

(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 radio blocks
are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Counter array
68P02901W56-R 12-79
DL_TBF_TIME_1_TS Chapter 12: PCU statistics
DL_TBF_TIME_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_TBF_TIME_1_TS statistic counts the cumulative length in number of 20ms radio block periods of
all downlink TBFs for mobiles that support a maximum of 1 TS in the downlink direction.
The DL_TBF_TIME_1_TS statistic can be used in conjunction with DL_RADIO_BLKS_1_TS to
calculate the effective downlink throughput per terminal type for mobile multislot classes supporting one
PDTCH in downlink.
Pegging
This statistic measures the time of all the TBFs in the downlink for mobiles that support a maximum of 1 TS
in the downlink direction as follows:
• Always pegged for mobiles with multislot class 1.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 1.
• If an EGPRS mode TBF is assigned to the mobile 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
mobiles supporting a maximum of 1 TS. The TBF time is measured from the TBF set-up time to the time the
mobile acknowledges the full TBF. The TBF time includes all the delayed downlink TBF release phases
except the very last one so as to accurately reflect the perceived throughput.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-80 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_TBF_TIME_2_TS
DL_TBF_TIME_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
calculate the effective downlink throughput per terminal type for mobile multislot classes supporting two
PDTCHs in downlink.
Pegging
• Always pegged for mobiles with multislot class 2, 3 or 5.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 2,3 or 5.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 2, 3 or 5.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-R 12-81
DL_TBF_TIME_3_TS Chapter 12: PCU statistics
DL_TBF_TIME_3_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
calculate the effective downlink throughput per terminal type for mobile multislot classes supporting three
PDTCHs in downlink.
Pegging
• Always pegged for mobiles with multislot class 4, 6, 7, 9, or 13.
• If a GPRS TBF is assigned to the mobile and its GPRS multislot is class 4, 6, 7, 9, or 13.
• If an EGPRS mode TBF is assigned to the mobile and the EGPRS multislot is class 4, 6,
7, 9, or 13.
Analysis
Reference None
Usage
Basis Cell
Type Counter
12-82 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_TBF_TIME_4_TS
DL_TBF_TIME_4_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
calculate the effective downlink throughput per terminal type for mobile multislot classes supporting four
PDTCHs in downlink.
Pegging
• Always pegged for mobiles with multislot class 8, 10, 11, 12 or 14 through 29.
• If a GPRS TBF is assigned to the mobile 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 mobile and the EGPRS multislot is one of class
8, 10, 11, 12 or 14 through 29.
Analysis
Reference None
Usage
Basis Cell
Type Counter
68P02901W56-R 12-83
EGPRS_64K_CHANNELS_SWITCHED Chapter 12: PCU statistics
EGPRS_64K_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_64K_CHANNELS_SWITCHED statistic counts the number of times that 64kbps EGPRS
timeslots are used for circuit-switched {24349} or VGCS calls in a statistics reporting period on a per-cell
basis.
Pegging
This statistic pegs when a 64kbps EGPRS timeslot is successfully switched for a point-to-point {24349}
or a voice group call as defined in Table 12-28.
Table 12-28 EGPRS_64K_CHANNELS_SWITCHED bins

0 CS The number of PDTCH of this type to be switched
for point-to-point calls.
1 VGCS The number of PDTCH of this type to be switched
for VGCS.
Analysis
Reference None
Network planning.
VGCS.
Basis Cell
Type Counter array.
12-84 68P02901W56-R
Maintenance Information: GSM Statistics Application EGPRS_64K_NOT_AVAIL
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 because the mobile’s
timeslot assignment was not 64k TRAU.
Pegging
This statistic pegs when an EGPRS capable mobile is allocated GPRS resources. This statistic is pegged
when 64k TRAU is disabled or when the mobile is allocated GPRS timeslots 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
68P02901W56-R 12-85
EGPRS_AVAIL_PDTCH Chapter 12: PCU statistics
EGPRS_AVAIL_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The EGPRS_AVAIL_PDTCH statistic measures the mean and max number of available EGPRS Packet Data
Traffic Channels (PDTCH).
This statistic is obtained by maintaining the current and 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 actually 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).
{24349} This statistics pegs when a full rate VGC channel is allocated from the EGPRS PDTCH pool.
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 only be shared by 2 MS.
Analysis
Reference 4.60, 5.08
Usage
Basis Cell
Type Gauge
12-86 68P02901W56-R
Maintenance Information: GSM Statistics Application EGPRS_DL_ASGN_PCCCH
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
Usage
Basis Cell
Type Counter
68P02901W56-R 12-87
G_RACH_UNSVCD_BTS Chapter 12: PCU statistics
G_RACH_UNSVCD_BTS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The G_RACH_UNSVCD_BTS statistic tracks the total number of uplink GPRS RACH requests unserviced
by the BTS.
The bins are:
• RSL bandwidth limitation.
• No PRR block.
• AGCH discard.
Pegging
This statistic is pegged whenever a GPRS RACH request is unserviced by the BTS.
Analysis
This statistic can be used for the trend analysis of the BTS.
Reference None.
Basis Cell.
Type Counter array.
12-88 68P02901W56-R
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-R 12-89
GBL_DL_DATA_THRPUT_HIST Chapter 12: 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 10 bins in the array. The available ranges are shown in Table 12-29.
Table 12-29 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 10 bins. See
Table 12-29 for the ranges.
12-90 68P02901W56-R
Maintenance Information: GSM Statistics Application GBL_DL_DATA_THRPUT_HIST
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-R 12-91
GBL_FLOW_CTRL_SENT Chapter 12: 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 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.
12-92 68P02901W56-R
Maintenance Information: GSM Statistics Application GBL_PAGING_REQS
GBL_PAGING_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GBL_PAGING_REQS statistic tracks the number of 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-R 12-93
GBL_UL_DATA_THRPUT Chapter 12: PCU statistics
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.
12-94 68P02901W56-R
Maintenance Information: GSM Statistics Application GBL_UL_DATA_THRPUT_HIST
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 10 bins.
The ranges are shown in Table 12-30.
Table 12-30 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
68P02901W56-R 12-95
GBL_UL_DATA_THRPUT_HIST Chapter 12: PCU statistics
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.
12-96 68P02901W56-R
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 he
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 caused by
operator interaction.
Reference None.
Usage Network accessibility.
Fault finding.
Basis GBL.
Type Duration.
68P02901W56-R 12-97
GPRS_32K_CHANNELS_SWITCHED Chapter 12: PCU statistics
GPRS_32K_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic keeps a count of the number of times that CS-3,4 capable GPRS timeslots (32k TRAU) are used
for circuit-switched {24349} or VGCS calls in a statistics reporting period on a per-cell basis.
Pegging
This statistic pegs when a 32kilobits per second GPRS timeslot is successfully switched to a circuit switched
{24349} or a voice group call as defined in Table 12-31.
Table 12-31 GPRS_32K_CHANNELS_SWITCHED bins

0 CS The number of PDTCH of this type to
be switched for point-to-point calls.
1 VGCS The number of PDTCH of this type to
be switched for VGCS.
Analysis
Reference None.
Network planning.
VGCS.
Basis Cell.
Type Counter array.
12-98 68P02901W56-R
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 timeslots
would have been switched to CS-3,4 due to good radio conditions in the cell, but could not because the
mobile’s timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAU timeslots and
the radio conditions would allow usage of CS-3,4.
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-R 12-99
GPRS_32K_UL_NOT_AVAIL Chapter 12: PCU statistics
GPRS_32K_UL_NOT_AVAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 16k TRAU GPRS timeslots
would have been switched to CS-3,4 due to good radio conditions in the cell, but could not because the
mobile’s timeslot assignment was not 32k TRAU.
Pegging
This statistic pegs when 32k TRAU is disabled or when the mobile is allocated 16k TRAU timeslots and
the radio conditions would allow usage of CS-3,4.
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.
12-100 68P02901W56-R
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 only pegged 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-R 12-101
GPRS_ACCESS_PER_RACH Chapter 12: 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.
Analysis
This statistic can be used for trend analysis of Immediate Assignment messages sent on the RACH of a cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.
12-102 68P02901W56-R
Maintenance Information: GSM Statistics Application GPRS_AVAIL_PDTCH
GPRS_AVAIL_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
This statistic was previously named AVAILABLE_PDTCH.
Description
This statistic measures the mean and max number of available Packet Data Traffic CHannels (PDTCH).
This statistic considers a PBCCH/PCCCH timeslot as a PDTCH therefore these will be recorded by the
statistic in its total number of available channels.
This statistic is obtained by maintaining the current and 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 unavailable when its administrative state changes to locked
or the operational state changes to 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 actually configured as PDTCHs and not as TCHs.
The number of PDTCH = Number of switchable PDTCHs (configured as PDTCHs) + Number of reserved
PDTCHs
Pegging
The statistic pegs whenever there is a change in the channel configuration for
any channel in the cell (if the number of PDTCHs has not changed within
the current pegging interval, it will be pegged with the same value as before).
{24349} This statistic pegs when a full rate VGC channel is allocated from the GPRS PDTCH pool.
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 only be shared by 2 MS.
68P02901W56-R 12-103
GPRS_AVAIL_PDTCH Chapter 12: PCU statistics
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 problems occur.

7.0.0 Jan 2000 ETSI.
Usage Congestion.
Network planning.
Basis Cell.
Type Gauge.
12-104 68P02901W56-R
Maintenance Information: GSM Statistics Application GPRS_CELL_CONGESTION
GPRS_CELL_CONGESTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The GPRS_CELL_CONGESTION statistic indicates the number of times, measured each 6 second interval,
that the percentage of GPRS timeslot resources that is 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
This statistic shall also include 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:
68P02901W56-R 12-105
GPRS_CELL_CONGESTION Chapter 12: PCU statistics
Table 12-32 Bin ranges for GPRS_CELL_CONGESTION
Bin Bin name Range

0 GPRS_CONGESTION_25 >= 0%, < 25%
15 GPRS_CONGESTION_100 >= 95%, <= 100%
One unit represents 1 time that 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 and resource allocation.
Basis Cell.
Type Counter array.
12-106 68P02901W56-R
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.
Analysis
This statistic can be used for analysis of Network Controlled cell reselect failures from an originating cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.
68P02901W56-R 12-107
GPRS_CHANNELS_SWITCHED Chapter 12: PCU statistics
GPRS_CHANNELS_SWITCHED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic reports the number of times a 16 kilobits per second Packet Data Traffic Channel (PDTCH) has
been switched to a circuit switched Traffic Channel (TCH) or {24349} or VGCS.
Pegging
This statistic pegs when a 16 kilobits per second PDTCH is switched to a circuit switched TCH{24349}
or VGCS as defined in Table 12-33.
Table 12-33 GPRS_CHANNELS_SWITCHED bins

0 CS The number of PDTCH of this type to be
switched for point-to-point calls.
1 VGCS The number of PDTCH of this type to be
switched for VGCS.
Analysis
Reference None.
Network planning.
VGCS.
Basis Cell.
Type Counter array.
12-108 68P02901W56-R
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.

7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Counter.
68P02901W56-R 12-109
GPRS_PCH_AGCH_Q_LENGTH Chapter 12: 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
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PCH-AGCH queue.

7.0.0 Jan 2000 ETSI.
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.
12-110 68P02901W56-R
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
Analysis
The 12.04 statistic B.2.1.1 is the mean of the number of messages in the PPCH-PAGCH queue.

7.0.0 Jan 2000 ETSI.
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-R 12-111
GPRS_PRR_BLK_USG Chapter 12: PCU statistics
GPRS_PRR_BLK_USG
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_PRR_BLK_USG statistic tracks the mean, minimum, and maximum number of PRR block usage.
GPRS_PRR_BLK_USG statistic are shown in Table 12-34.
Table 12-34 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 a 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.
12-112 68P02901W56-R
Maintenance Information: GSM Statistics Application GPRS_PRR_BLK_USG
Analysis
Reference None.
Basis Cell.
68P02901W56-R 12-113
GPRS_RACH_ARRIVAL Chapter 12: 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.
GPRS_RACH_ARRIVAL statistic are shown in
Table 12-35 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.
12-114 68P02901W56-R
Maintenance Information: GSM Statistics Application GPRS_RACH_ARRIVAL
Analysis
Reference None.
Basis Cell.
68P02901W56-R 12-115
IDLE_PDTCH_INTF_BAND0 Chapter 12: 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.
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 will fall 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.

7.0.0 Jan 2000 ETSI..
Fault finding.
Basis Cell.
Type Gauge.
12-116 68P02901W56-R
Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis

7.0.0 Jan 2000 ETSI.
Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-R 12-117
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis

7.0.0 Jan 2000 ETSI.
Fault finding.
Basis Cell.
Type Gauge.
12-118 68P02901W56-R
Maintenance Information: GSM Statistics Application IDLE_PDTCH_INTF_BAND3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis

7.0.0 Jan 2000 ETSI.
Fault finding.
Basis Cell.
Type Gauge.
68P02901W56-R 12-119
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Pegging
Analysis

7.0.0 Jan 2000 ETSI.
Fault finding.
Basis Cell.
Type Gauge.
12-120 68P02901W56-R
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 12-36.
Table 12-36 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-R 12-121
IMM_ASSGN_CAUSE Chapter 12: PCU statistics
Analysis
It represents the total number of IAs pegged during the statistics interval, on a per-cause basis.

7.0.0 Jan 2000 ETSI.
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 mobile
subscriber preferences in any particular area.
Basis Cell.
Type Counter array.
12-122 68P02901W56-R
Maintenance Information: GSM Statistics Application NO_PDTCH_AVAIL
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.
{24349} This statistic pegs when a VGC channel is allocated from the GPRS pool resulting in no GPRS
resources being available in the cell.
Reference None.
Network accessibility.
Basis Cell.
Type Counter.
68P02901W56-R 12-123
NO_PDTCH_AVAIL_TIME Chapter 12: PCU statistics
NO_PDTCH_AVAIL_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The NO_PDTCH_AVAIL_TIME statistic measures the amount of time in 20 millisecond periods during the
statistical collection period (between timer start and stop), 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.
{24349} This statistic pegs when a VGC channel is allocated from the GPRS pool resulting in no GPRS
resources being available in the cell.
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 Maintenance Information: Alarm
Handling at the OMC-R (68P02901W26) for troubleshooting information.
Reference None.
Network accessibility.
Basis Cell.
Type Duration.
12-124 68P02901W56-R
Maintenance Information: GSM Statistics Application PACCH_PAGE_REQS
PACCH_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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 mobile is in packet transfer mode.
Pegging
One unit represents 1 page request (CS or PS).
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-R 12-125
PDU_DISCARD_FR Chapter 12: PCU statistics
PDU_DISCARD_FR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The PDU_DISCARD_FR statistic indicates the number of uplink and downlink PDU frames discarded by
Frame Relay firmware.
Pegging
Table 12-37 shows the description for each bin.
Table 12-37 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 1 LLC frame. The range is 0 to 65535. 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.
12-126 68P02901W56-R
Maintenance Information: GSM Statistics Application PDU_DISCARD_LLC
PDU_DISCARD_LLC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The PDU_DISCARD_LLC statistic represents the downlink LLC data frames discarded by PCU due to
different scenarios. There are 3 major causes:
• Buffer overflow.
• Cell reselection.
• Abnormal TBF release.
Pegging
Table 12-38 shows the description for each bin.
Table 12-38 Bin descriptions for PDU_DISCARD_LLC
Bin Name Description

0 PDU_DSCRD_LLC_CELL_BUF_OVR- Cell buffer overflow.
FLW
1 PDU_DSCRD_LLC_MS_BUF_OVRFLW MS buffer overflow.
2 PDU_DSCRD_LLC_INAB_MOVE_PKT Buffer discarded due to
inability to move the packets
internally.
3 PDU_DSCRD_LLC_OUT_SEQ_LLC Discard data in target cell to
avoid out of sequence LLC
delivery.
4 PDU_DSCRD_LLC_RESEL_INAREA Discard LLC for cell
reselection within the same
routing area.
5 PDU_DSCRD_LLC_RESEL_OUTAREA Discard LLC for cell
reselection outside the
same routing area.
6 PDU_DSCRD_LLC_ABNORM_TBFREL Discard data due to abnormal
TBF release.
{23956} 7 PDU_DSCRD_LLC_PFC_RE- Discard data due to PFC
JECT_DELET rejection/deletion.
One unit represents 1 LLC frame. The range is 0 to 65535. The maximum number of LLC frames discarded
during a one-hour period can’t be accurately estimated. Use the uplimit of a 16-bit unsigned integer.
68P02901W56-R 12-127
PDU_DISCARD_LLC Chapter 12: PCU statistics
Analysis
Reference None.
Basis Cell.
Type Counter array.
12-128 68P02901W56-R
Maintenance Information: GSM Statistics Application PRP_LOAD
PRP_LOAD
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the load of the Packet Resource Processor (PRP) board. The BSS transfers data for 30
DL and 30 UL TBFs, and processes control messages for 90 UL and 90 DL TBFs in one 20 millisecond block
period. The load of the PRP board is determined by measuring the number of timeslots pending service for
data transfers within a 20 millisecond block period.
Table 12-39 shows the mapping between the number of timeslots pending service and the PRP load.
The statistic is kept on a per DPROC basis.
Table 12-39 Mapping between timeslots pending service and PRP load
Number of timeslots pending service

PRP Load
in a 20 msec block period
0-30 0-100
31-60 101-200
61-90 201-300
91-120 301-400
Table 12-40 shows the PRP load ranges for each bin of this statistic.
68P02901W56-R 12-129
PRP_LOAD Chapter 12: PCU statistics
Table 12-40 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.
Analysis
This statistic can be used for trend analysis of the network load on a PRP board. Each bin can be analysed to
determine the number of occurrences the PRP had a certain percentage of load on it.
Reference None.
Basis This statistic is based on each DPROC.
12-130 68P02901W56-R
Maintenance Information: GSM Statistics Application PS_PAGE_REQS
PS_PAGE_REQS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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 1 PS page request.
Analysis
Reference None.
Basis GBL.
Type Counter.
68P02901W56-R 12-131
TBF_DL_ASGN_PACCH Chapter 12: PCU statistics
TBF_DL_ASGN_PACCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The TBF_DL_ASGN_PACCH statistic represents the total number of Packet Downlink Assignments sent by
the PCU using PACCH channel to establish downlink TBF when the mobile is in packet transfer mode.
Pegging
One unit represents one PDA.
Analysis
Reference None.
Basis Cell.
Type Counter.
12-132 68P02901W56-R
Maintenance Information: GSM Statistics Application TBF_REL_PACCH_LOST
TBF_REL_PACCH_LOST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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.
Pegging
One unit represents one TBF.
Analysis
Reference None.
Basis Cell.
Type Counter.
68P02901W56-R 12-133
TBF_SESSIONS Chapter 12: PCU statistics
TBF_SESSIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The TBF_SESSIONS statistic indicates the average and maximum ongoing TBFs at the end of each 6-second
duration on a PRP board.
Pegging
One unit represents 1 TBF session. The range is 0 to 120. The capacity is measured by the number of
mobiles a PRP board can support (120).
Analysis
Reference None.
Basis PRP.
Type Gauge.
12-134 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_BLER_CS1
UL_BLER_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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.
Pegging
Table 12-41 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.
The window is maintained by PCU as part of mobile 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 will be represented as X+1.
The range is 0 to 18000. The shortest period between 2 consecutive PUA/PTR/PUAK can not 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 very next block period of the previous PUAK.). So in a one-hour period,
there may be at most 3,600,000ms / (1x20ms) = 180,000 PUA/PTR/PUAKs being sent. Thus there will be at
68P02901W56-R 12-135
UL_BLER_CS1 Chapter 12: PCU statistics
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-136 68P02901W56-R
UL_BLER_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
68P02901W56-R 12-137
Analysis
Reference None.
Basis Carrier.
Type Counter array.
12-138 68P02901W56-R
UL_BLER_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
This statistic is not available if Coding Scheme 3/4 feature is disabled.
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-139
UL_BLER_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
or missed, and has a maximum size of 128. 10X+Y (1<=Y<=10) calculations will be represented as X+1
12-140 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-141
UL_BLER_MCS1 Chapter 12: PCU statistics
UL_BLER_MCS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Descripton
The UL_BLER_MCS1 statistic indicates the number of times, measured at statistical intervals, the BLER
of a particular carrier, when using EDGE modulation coding scheme 1 to transmit in the uplink direction,
Pegging
Table 12-44 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.
12-142 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_BLER_MCS1
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-143
UL_BLER_MCS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The UL_BLER_MCS2 statistic indicates the number of times, measured at statistical intervals, the BLER of
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%
sent by the PCU.
12-144 68P02901W56-R
estimated. Two such messages may be scheduled by the system in a back to back situation (that is, the next
PUAK may be scheduled at the very next block period of the previous PUAK.). So in a one-hour period, there
may be at most 3,600,000ms / (1x20ms) = 180,000 PUA/PTR/PUAKs being sent. Thus there will be at most
180,000 calculations, and the maximum value will be 18,000 for each bin.
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-145
UL_BLER_MCS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
sent by the PCU.
12-146 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-147
UL_BLER_MCS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
sent by the PCU.
12-148 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-149
UL_BLER_MCS5
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
1 unit represents 10 UL BLER calculations. For a given carrier using EGPRS modulation coding scheme 5
sent by the PCU.
12-150 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-151
UL_BLER_MCS6
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
sent by the PCU.
12-152 68P02901W56-R
estimated. Two such messages may be scheduled by the system in a back to back situation (e.g., the next
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-153
UL_BLER_MCS7
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
sent by the PCU.
12-154 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-155
UL_BLER_MCS8
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The UL_BLER_MCCS8 statistic indicates the number of times, measured at statistical intervals, the BLER of
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%
sent by the PCU.
12-156 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-157
UL_BLER_MCS9
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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%
sent by the PCU.
12-158 68P02901W56-R
Analysis
Reference None.
Basis Carrier.
Type Counter array.
68P02901W56-R 12-159
UL_BUSY_PDTCH Chapter 12: PCU statistics
UL_BUSY_PDTCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures the mean, max and min number of occupied Packet Data CHannel (PDCH) carrying
uplink packet traffic.
This statistic is obtained by sampling the PDTCH, which are carrying packet traffic, at every packet-scheduling
period (20 millisecond).
Table 12-53 shows the ranges for each bin (measured in milliseconds).
Table 12-53 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.
12-160 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_BUSY_PDTCH
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for uplink packet traffic.

7.0.0 Jan 2000 ETSI.
Basis Cell.
68P02901W56-R 12-161
UL_LLC_FRAMES Chapter 12: PCU statistics
UL_LLC_FRAMES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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 12-54 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
One unit represents 10 LLC frames. 10X+Y (1<=Y<=10) calculations will be represented as X+1.
The range is 0 to 65535. The maximum number of LLC frames received from the mobile during a one-hour
period can not be accurately estimated. Use the uplimit of a 16-bit unsigned integer.
Analysis
Reference None.
Basis Cell.
Type Counter array.
12-162 68P02901W56-R
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 20ms. It is incremented when a request is added to the queue and is decremented
when a request is processed, that is, leaves the queue.
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.

7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Gauge.
68P02901W56-R 12-163
UL_PDTCH_SEIZURE Chapter 12: PCU statistics
UL_PDTCH_SEIZURE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic measures successful Packet Data Traffic CHannel (PDTCH) seizure on the uplink. The purpose
of this statistic is to count 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.
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the downlink for a CELL.

7.0.0 Jan 2000 ETSI.
Basis Cell.
Type Counter.
12-164 68P02901W56-R
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 mobiles capable of 8PSK on the uplink that support a maximum of 1 TS in the uplink direction
(mobile multislot classes 1, 2, 4, and 8).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translation of actual
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 12-55.
Table 12-55 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
68P02901W56-R 12-165
UL_RADIO_BLKS_8PSK_1_TS Chapter 12: PCU statistics
(RLC block 1, RLC block 2) UL radio block status

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
(RETRANS, RETRANS) RETRANS
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 (mobile
multislot classes 1, 2, 4 and 8).
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles 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 mobiles 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 (MCS-1),
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-166 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_8PSK_2_TS
UL_RADIO_BLKS_8PSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RADIO_BLKS_8PSK_2_TS statistic counts the total number of RLC radio blocks received from
EGPRS mobiles capable of 8PSK on the uplink that support a maximum of 2 TS in the uplink direction
(mobile multislot classes 3, 5, 6, 9, and 10).
100 RLC radio blocks = 1 unit. The maximum recommended interval is 60 minutes. The translation of actual
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 12-56.
Table 12-56 Bin ranges for UL_RADIO_BLKS_8PSK_2_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
68P02901W56-R 12-167
UL_RADIO_BLKS_8PSK_2_TS Chapter 12: PCU statistics

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
Multislot class 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.
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 (mobile
multislot classes 3, 5, 6, 9 and 10).
Pegging
This statistic counts the RLC radio blocks for EGPRS mobiles 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
Usage
Basis Cell
Type Counter array
12-168 68P02901W56-R
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 mobiles that support a maximum of 1 TS in the uplink direction (mobile multislots classes
1, 2, 4 and 8). 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 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 12-57.
Table 12-57 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
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 (mobile
68P02901W56-R 12-169
UL_RADIO_BLKS_GMSK_1_TS Chapter 12: PCU statistics
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 1 TS in the 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 the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-170 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_RADIO_BLKS_GMSK_2_TS
UL_RADIO_BLKS_GMSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_RADIO_BLKS_GMSK_2_TS statistic counts the total number of RLC radio blocks 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).
This statistic also pegs mobiles 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 12-58.
Table 12-58 Bin ranges for UL_RADIO_BLKS_GMSK_2_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 7, 11 and 12 that support more than 2 timeslots on the uplink will be treated as 2-uplink capable.
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 (mobile
68P02901W56-R 12-171
UL_RADIO_BLKS_GMSK_2_TS Chapter 12: PCU statistics
Pegging
This statistic counts the RLC radio blocks for mobiles that support a maximum of 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
Usage
Basis Cell
Type Counter array
12-172 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_RLC_ACK_NEW_BLKS
UL_RLC_ACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistics UL_RLC_ACK_NEW_BLKS and UL_RLC_UNACK_NEW_BLKS are a

replacement for the AIR_UL_DATA_BLKS statistic (available in GSR4, GSR5, GSR5.1,
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 12-59 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
68P02901W56-R 12-173
UL_RLC_ACK_NEW_BLKS Chapter 12: PCU statistics

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
Pegging
This statistic counts the new RLC acknowledged radio blocks that are received on a cell. The RLC radio
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-174 68P02901W56-R
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 pre-emptive retransmissions (or ack
pending blocks and acknowledged retransmissions) received by the PCU over the cell.
Table 12-60 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
68P02901W56-R 12-175
UL_RLC_RETX_BLKS Chapter 12: PCU statistics

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
Pegging
This statistic counts the RLC ack pending (or pre-emptive transmissions) radio blocks that are received on a
cell. The RLC radio blocks are counted per coding scheme, therefore pegging the appropriate bin.
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-176 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_RLC_UNACK_NEW_BLKS
UL_RLC_UNACK_NEW_BLKS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The statistics UL_RLC_UNACK_NEW_BLKS and UL_RLC_ACK_NEW_BLKS are a

replacement for the AIR_UL_DATA_BLKS statistic (available in GSR4, GSR5, GSR5.1,
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 12-61 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
68P02901W56-R 12-177
UL_RLC_UNACK_NEW_BLKS Chapter 12: PCU statistics

(NEW, RETRANS) NEW
(RETRANS, NEW) NEW
Pegging
This statistic counts the new RLC unacknowledged radio blocks that are received on a cell. The RLC radio
Analysis
Reference None
Usage
Basis Cell
Type Counter array
12-178 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_TBF_TIME_8PSK_1_TS
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 20ms radio block periods) of the uplink TBFs for EGPRS mobiles 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_RA-
DIO_BLKS_8PSK_1_TS to calculate the effective uplink throughput per EGPRS terminal type (mobile
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles 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 mobiles 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 mobiles 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
Usage
Basis Cell
Type Counter
68P02901W56-R 12-179
UL_TBF_TIME_8PSK_2_TS Chapter 12: PCU statistics
UL_TBF_TIME_8PSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_TIME_8PSK_2_TS statistic measures the duration in time (the cumulative length in number
of 20ms radio block periods) of the uplink TBFs for EGPRS mobiles that support a maximum of 2 TS and
capable of 8PSK in the uplink direction.
The UL_TBF_TIME_8PSK_2_TS statistic can be used in conjunction with UL_RA-
DIO_BLKS_8PSK_2_TS to calculate the effective uplink throughput per EGPRS terminal type (mobile
Pegging
This statistic pegs the time of all the TBFs in the uplink for mobiles 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 mobiles supporting a maximum of 2 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
Usage
Basis Cell
Type Counter
12-180 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_TBF_TIME_GMSK_1_TS
UL_TBF_TIME_GMSK_1_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_TIME_GMSK_1_TS statistic counts the cumulative length in number of 20ms radio block
periods of all uplink TBFs for mobiles 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 mobiles 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_RA-
DIO_BLKS_GMSK_1_TS to calculate the effective uplink throughput per terminal type (mobile multislot
classes 1, 2, 4 and 8).
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles 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 mobiles 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
Usage
Basis Cell
Type Counter
68P02901W56-R 12-181
UL_TBF_TIME_GMSK_2_TS Chapter 12: PCU statistics
UL_TBF_TIME_GMSK_2_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_TBF_TIME_GMSK_2_TS statistic counts the cumulative length in number of 20ms radio block
periods of all uplink TBFs for GPRS and EGPRS mobiles that support a maximum of 2 TS in the uplink
direction. The EGPRS mobile is not capable of supporting 8PSK in the uplink.
The UL_TBF_TIME_GMSK_2_TS statistic can be used in conjunction with UL_RA-
DIO_BLKS_GMSK_2_TS to calculate the effective uplink throughput per terminal type (mobile multislot
classes 3, 5, 6, 9 and 10).
Pegging
This statistic measures the time of all the TBFs in the uplink for mobiles that support a maximum of 2 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 mobiles supporting a maximum of 2 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
Usage
Basis Cell
Type Counter
12-182 68P02901W56-R
Chapter
13
BSS-SMLC statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BSS-based Serving Mobile Location Centre (SMLC) statistics track events on the signalling link. They are
categorized into subgroups, each of which are described in "BSS-based SMLC statistics subgroups" on
page 13-2.
68P02901W56-R 13-1
BSS-based SMLC statistics subgroups Chapter 13: 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 13-2.
• "SCCP performance & utilization" on page 13-2.
BSS C7 utilization
BSS-based SMLC C7 utilization statistics track the number of messages received and transmitted on the
signalling links. This information indicates the activity level on the Signalling Links (SLs). The following are
BSS C7 utilization statistics:
• "L_SIF_SIO_RX_OPC" on page 13-8.
• "L_SIF_SIO_TX_DPC" on page 13-9.
• "L_SIF_SIO_TYPE" on page 13-10.
SCCP performance & utilization
SCCP performance and utilization statistics track the performance of the Signalling 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 13-3.
• "L_ROUTING_UNKNOWN" on page 13-4.
• "L_SCCP_MSGS" on page 13-5.
• "L_SCCP_MSGS_RX" on page 13-6.
• "L_SCCP_MSGS_TX" on page 13-7.
• "L_SIF_SIO_RX_OPC" on page 13-8.
• "L_SIF_SIO_TX_DPC" on page 13-9.
• "L_SIF_SIO_TYPE" on page 13-10.
• "PAGE_REQ_FROM_SMLC_FAIL" on page 13-11.
13-2 68P02901W56-R
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 signalling messages between the BSC and BSS-based SMLC.
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 18. BSS: Routing failure - syntax error detected (SMLC) - PM
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-R 13-3
L_ROUTING_UNKNOWN Chapter 13: BSS-SMLC statistics
L_ROUTING_UNKNOWN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic tracks the number of invalid signalling 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 will not be able to correctly route the message.
A threshold value should be assigned to this statistic which reflects the maximum number of 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
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.
13-4 68P02901W56-R
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 an Lb-interface.
Pegging
This statistic pegs when SCCP messages are transmitted or received on the signalling link between the
BSC and BSS-based SMLC.
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).
Basis BSS.
Type Counter.
68P02901W56-R 13-5
L_SCCP_MSGS_RX Chapter 13: 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
an Lb-interface for class 0 or class 2.
This statistic will switch on 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 will be stored in l_sccp_msgs_rx_0.
• the number of SCCP messages received for class 2 will be stored in l_sccp_msgs_rx_2.
Pegging
This statistic pegs when SCCP messages are received on the signalling link between the BSC and BSS-based
SMLC.
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.
13-6 68P02901W56-R
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.
of the database:
• the number of SCCP messages transmitted for class 0 will be stored in l_sccp_msgs_tx_0.
• the number of SCCP messages transmitted for class 2 will be stored in l_sccp_msgs_tx_2.
Pegging
This statistic pegs when SCCP messages are transmitted on the signalling link.
Analysis
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-R 13-7
L_SIF_SIO_RX_OPC Chapter 13: 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 signalling links between the BSS and BSS-based SMLC.
Analysis
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.
13-8 68P02901W56-R
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 signalling 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 signalling message that uniquely identifies, in a signalling network, the
destination point of the message. This statistic can be used for trend analysis of the activity of the signalling
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-R 13-9
L_SIF_SIO_TYPE Chapter 13: 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.
of the database:
• the number of SIF SCCP SIOs will be stored in l_sif_sio_type.
• the number of SIF MTP SIOs will be stored in l_sif_sio_type_mtp.
• the number of SIF TEST SIOs will be stored in l_sif_sio_type_test.
Pegging
This statistic pegs each time SIF or SIOs are transmitted or received on all signalling links between BSS
and BSS-based SMLC.
Analysis
This statistic can be used for trend analysis of the activity of the signalling 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.
13-10 68P02901W56-R
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
A threshold value should be assigned to this statistic which reflects the maximum number of failures that are
acceptable in normal system operations.
If the specified threshold is exceeded, the 20. BSS: Paging request from SMLC protocol error - PM alarm
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.
68P02901W56-R 13-11
PAGE_REQ_FROM_SMLC_FAIL Chapter 13: BSS-SMLC statistics
13-12 68P02901W56-R
Chapter
14
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 14-2.
68P02901W56-R 14-1
MMI statistics subgroups Chapter 14: Web MMI statistics
MMI statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MMU statistics are organized into the following major subgroups:
• "MMI PCU real-time statistics" on page 14-2.
• "MMI BSC/BTS real-time statistics" on page 14-2.
MMI PCU real-time statistics
The following MMI PCU real-time statistics are documented elsewhere in this manual. Table 14-1 indicates
the location of these descriptions.
Table 14-1 Location of MMI PCU real-time stats descriptions
MMI PCU statistic Location in manual

CELL_FLUSH_REQS "CELL_FLUSH_REQS" on page 12-12
CHANNEL_REQS_REJ "CHANNEL_REQS_REJECT" on page 12-17
GBL_PAGING_REQS "GBL_PAGING_REQS" on page 12-93
GBL_UNAVAILABLE "GBL_UNAVAILABLE" on page 12-97
MMI BSC/BTS real-time statistics
The following MMI BSC/BTS real-time statistics are documented elsewhere in this manual. Table 14-2
indicates the location of these descriptions.
14-2 68P02901W56-R
Maintenance Information: GSM Statistics Application MMI statistics subgroups
Table 14-2 Location of MMI BSC/BTS real-time stats descriptions
MMI BSC/BTS statistic Location in manual

ALLOC_SDCCH_FAIL "ALLOC_SDCCH_FAIL" on page 4-21
ALLOC_TCH_FAIL "ALLOC_TCH_FAIL" on page 4-23
HO_FAIL_NO_RESOURCES "HO_FAIL_NO_RESOURCES" on page 4-80
HO_REQ_MSC_FAIL "HO_REQ_MSC_FAIL" on page 4-83
MA_CMD_TO_MS_BLKD "MA_CMD_TO_MS_BLKD" on page 4-105
RF_LOSSES_TCH "RF_LOSSES_TCH" on page 4-164 and "RF_LOSSES_TCH" on
page 6-33
68P02901W56-R 14-3
MMI statistics subgroups Chapter 14: Web MMI statistics
14-4 68P02901W56-R
Chapter
15
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 of time (3 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 15-2.
• "CALL_SETUP_TCH_BLOCKING_RATE" on page 15-3.
• "HANDOVERS_PER_CALL (H)" on page 15-4.
• "IMSI_DETACHES_TO_CALLS (Id)" on page 15-5.
• "INTRA_BSS_HO_TO_ALL_HO (i)" on page 15-6.
• "LOCATION_UPDATE_FACTOR (L)" on page 15-7.
• "LOCATION_UPDATES_TO_CALLS (I)" on page 15-8.
• "PAGES_PER_CALL (PPC)" on page 15-9.
• "PAGES_PER_SECOND" on page 15-10.
• "PAGING_RATE (P)" on page 15-11.
• "SMS_TO_CALL_RATIO (S)" on page 15-12.
Refer to the System Information: BSS Equipment Planning (68P02900W21) for further information on the
call model parameters.
68P02901W56-R 15-1
CALL_DURATION (T) Chapter 15: Call model statistics
CALL_DURATION (T)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the average call duration.
Formula
_ _ _ _ _
_ _
Where: is:
N the number of cells.
stat_interval_in_sec the interval over which
BUSY_TCH_MEAN values
are measured. It is 3600 if hourly
values are used and 86400 if daily
values are used.

Optimization.
Basis Cell.
Units Seconds
Raw Statistics BUSY_TCH_MEAN.
TOTAL_CALLS.
ASSIGNMENT_REDIRECTION.
15-2 68P02901W56-R
Maintenance Information: GSM Statistics Application CALL_SETUP_TCH_BLOCKING_RATE
CALL_SETUP_TCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the percentage of attempts to allocate a TCH call setup that were blocked.
Formula
_ _ _ _ _ _
_ _ _ _

Optimization.
Basis Cell.
Units Percentage.
Raw Statistics MA_CMD_TO_MS_BLKD.
MA_REQ_FROM_MSC.
68P02901W56-R 15-3
HANDOVERS_PER_CALL (H) Chapter 15: 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
_ _ _ _ _ _ _ _ _
_ _ _
_ _
Where: is:
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.
Optimization.
Basis Cell.
Raw Statistics OUT_INTER_BSS_REQ_TO_MSC.
OUT_INTRA_BSS_HO_ATMPT.
INTRA_CELL_HO_ATMPT.
TOTAL_CALLS.
15-4 68P02901W56-R
Maintenance Information: GSM Statistics Application IMSI_DETACHES_TO_CALLS (Id)
IMSI_DETACHES_TO_CALLS (I ) d
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of IMSI detaches per call.
Formula
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _

Optimization.
Basis Cell.
Raw Statistics OK_ACC_PROC[IMSI_DETACH].
OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_SMS].
OK_ACC_PROC[CM_SERV_REQ_EMERG].
OK_ACC_PROC[PAGE_RESPONSE].
{24349} OK_ACC_PROC[CM_SERV_REQ_VGCS].
{24349} OK_ACC_PROC[IMM_SETUP].
{24349} OK_ACC_PROC[IMM_SETUP2].
SMS_INIT_ON_SDCCH.
68P02901W56-R 15-5
INTRA_BSS_HO_TO_ALL_HO (i) Chapter 15: Call model statistics
INTRA_BSS_HO_TO_ALL_HO (i)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of intra-BSS handovers to all handovers.
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
Where: is:

Optimization.
Basis Cell.
Raw Statistics OUT_INTRA_BSS_HO_ATMPT.
INTRA_CELL_HO_ATMPT.
OUT_INTER_BSS_REQ_TO_MSC.
TOTAL_CALLS.
15-6 68P02901W56-R
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, etc., 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 a 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 i.e. 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)

Optimization.
Basis Cell.
Call Model Statistics LOCATION_UPDATES_TO_CALLS.
IMSI_DETACHES_TO_CALLS.
68P02901W56-R 15-7
LOCATION_UPDATES_TO_CALLS (I) Chapter 15: Call model statistics
LOCATION_UPDATES_TO_CALLS (I)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of location updates to calls.
Formula
{24349}
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _

Optimization.
Basis Cell.
Raw Statistics OK_ACC_PROC[LOCATION UPDATE].
SMS_INIT_ON_SDCCH.
15-8 68P02901W56-R
Maintenance Information: GSM Statistics Application PAGES_PER_CALL (PPC)
PAGES_PER_CALL (P ) PC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the number of pages per call.
Formula
_ _ _
_ _
Where: is:
N the number of cells under the BSC.

Optimization.
Basis Cell.
Call Model/Raw Statistics PAGE_REQ_FROM_MSC.
TOTAL_CALLS.
PAGING_RATE.
CALL_DURATION.
68P02901W56-R 15-9
PAGES_PER_SECOND Chapter 15: Call model statistics
PAGES_PER_SECOND
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the number of pages per second.
Formula
_ _ _
_ _
_

Optimization.
Basis Cell.
Raw Statistics PAGE_REQ_FROM_MSC.
INTERVAL_SUM.
15-10 68P02901W56-R
Maintenance Information: GSM Statistics Application PAGING_RATE (P)
PAGING_RATE (P)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The paging rate is the summation of the paging messages sent to each location area averaged over the
interval period.
Formula
_ _ _
_ _ _
Where: is:
N the number of location areas.
PAGE_REQ_FROM_MSC should be the maximum per cell value for each location area.
Optimization.
Basis Cell.
68P02901W56-R 15-11
SMS_TO_CALL_RATIO (S) Chapter 15: Call model statistics
SMS_TO_CALL_RATIO (S)
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
This statistic provides the ratio of SMSs to calls.
Formula
{24349}
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _

Optimization.
Basis Cell.
Raw Statistics SMS_INIT_ON_SDCCH.
SMS_INIT_ON_TCH.
15-12 68P02901W56-R
Chapter
16
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 16-2.
68P02901W56-R 16-1
Key statistics subgroups Chapter 16: Key statistics
Key statistics subgroups

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

• "Call summary" on page 16-2.
• "Channel usage" on page 16-3.
• "RF loss summary" on page 16-4.
• "MTL utilisation" on page 16-4.
• "Radio link" on page 16-4.
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 16-7.
• "HANDOVER_FAILURE_RATE" on page 16-14.
• "HANDOVER_SUCCESS_RATE" on page 16-15.
• "SUCCESS_INTERNAL_HO" on page 16-34.
• "TOTAL_CALLS_KEY" on page 16-47.
• "UNSUCCESS_INTERNAL_HO_NOREEST" on page 16-49.
• "UNSUCCESS_INTERNAL_HO_REEST" on page 16-50.
16-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Key statistics subgroups
Channel usage
Channel usage statistics are used to determine SDCCH and TCH performance levels. The following
are channel usage statistics:
• "MEAN_TCH_BUSY_TIME" on page 16-23.
• "SDCCH_MEAN_HOLDING_TIME" on page 16-29.
• "SDCCH_TRAFFIC_CARRIED" on page 16-31.
• "TCH_BLOCKING_RATE" on page 16-36.
• "TCH_BLOCKING_RATE_INNER_Z" on page 16-37
• "TCH_BLOCKING_RATE_OUTER_Z" on page 16-38
• "TCH_MEAN_ARRIVAL_RATE" on page 16-39.
• "TCH_MEAN_HOLDING_TIME" on page 16-40.
• "TCH_RF_LOSS_RATE" on page 16-43
• "TCH_TRAFFIC_CARRIED" on page 16-45.
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 16-6.
• "MEAN_ARRIVAL_TIME_BETWEEN_CALLS" on page 16-20.
• "MEAN_INTER_ARRIVAL_TIME" on page 16-21.
• "SUCCESS_IMMED_ASSIGN_PROC" on page 16-33.
68P02901W56-R 16-3
Key statistics subgroups Chapter 16: Key statistics
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 16-10.
• "CELL_TCH_ASSIGNMENTS" on page 16-11.
• "RF_LOSS_RATE" on page 16-26.
• "SDCCH_RF_LOSS_RATE" on page 16-30.
MTL utilisation
MTL utilisation statistics are used to provide a measure of MTL utilisation from the MSC to BSS and from
the BSS to MSC. The following are MTL utilisation statistics:
• "MTL_UTILISATION_RX" on page 16-24.
• "MTL_UTILISATION_TX" on page 16-25.
Radio link
{22577}
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_LLC_TRAFFIC_VOLUME_INDICATOR" on page 16-12.
• "DL_TBF_SUCCESS_RATE" on page 16-13.
• "LLC_ABNORMAL_TBF_RELEASES" on page 16-17.
• "LLC_BUFFER_OVERFLOW_RATE" on page 16-18.
• "LLC_DISCARDS_ON_CELL_RESELECTION" on page 16-19.
• "MEAN_TBF_SESSIONS" on page 16-22.
• "TBF_DROP_RATE_ON_PACCH_LOST" on page 16-35.
• "UL_LLC_TRAFFIC_VOLUME_INDICATOR" on page 16-48.
16-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Key statistics subgroups
Key statistics description template
Table 16-1 is a template used in the key statistic descriptions:
Table 16-1 Key statistic descriptions.
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, etc.).
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.
The template headings are used as required and are not present for all statistics.
68P02901W56-R 16-5
ATTEMPT_IMMED_ASSIGN_PROC Chapter 16: Key statistics
ATTEMPT_IMMED_ASSIGN_PROC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ATTEMPT_IMMED_ASSIGN_PROC statistic tracks the number of attempted immediate assignment

procedures.
Formula
{24620}
_ _ _ _ _ _ _

Optimization.
Basis Cell or BSS.
Type Counter.
Raw Statistics {24620}OK_ACC_PROC_SUC_RACH.
16-6 68P02901W56-R
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 result 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
{28014 / 24349}
68P02901W56-R 16-7
CALL_SETUP_SUCCESS_RATE Chapter 16: Key statistics
Cell Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
BSS Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
16-8 68P02901W56-R
Network Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _

Fault finding.
Service accessibility.
Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formula
is the sum of bins 0 to 2 of this counter array statistic).
MT_LCS_ON_SDCCH.
OK_ACC_PROC[CM_REESTABLISH].
OK_ACC_PROC[LOC_FLW_ON_REQ_NORM].
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].
SMS_INIT_ON_SDCCH.
{28014} SMS_INIT_ON_SDCCH_HO_OUT[INTER_CELL].
{28014} SDCCH_HANDOVER[OUT_INTRA_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[OUT_INTER_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[IN_INTRA_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[IN_IN-
TER_BSS_HO_ATTMPT].
TOTAL_CALLS.
68P02901W56-R 16-9
CELL_TCH_ALLOCATIONS Chapter 16: 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
_ _ _

Basis Cell.
Type Counter.
Raw Statistics ALLOC_TCH.
16-10 68P02901W56-R
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
_
_ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _

Basis Cell.
Type Counter.
Raw Statistics TOTAL_CALLS.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
68P02901W56-R 16-11
DL_LLC_TRAFFIC_VOLUME_INDICATOR Chapter 16: Key statistics
DL_LLC_TRAFFIC_VOLUME_INDICATOR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_
_ _ _ _ _ _ _ _
_
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _
Usage Gb link bandwidth dimensioning.

Basis Cell.
Type Units = kB.
Raw statistics DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_20].
DL_LLC_FRAMES_GB[DL_LLC_FRAMES_GB_40].
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].
16-12 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_TBF_SUCCESS_RATE
DL_TBF_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The DL_TBF_SUCCESS_RATE statistic monitors downlink TBF success.
Formula
_ _
_ _ _
_ _ _
_ _
_ _ _
_ _
_ _ _
Usage Cell accessibility.

Basis Cell.
Type Percentage.
Raw statistics DL_PDTCH_SEIZURE
TBF_DL_ASGN_PACCH
IMM_ASSGN_CAUSE[DL_PACK_ACCESS_GPRS]
IMM_ASSGN_CAUSE[DL_PACK_ACCESS_EGPRS].
68P02901W56-R 16-13
HANDOVER_FAILURE_RATE Chapter 16: Key statistics
HANDOVER_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HANDOVER_FAILURE_RATE statistic tracks the percentage of handovers that were 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 mobile therefore
this measurement is not impacted by target cell congestion.
Formula
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].
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].
16-14 68P02901W56-R
Maintenance Information: GSM Statistics Application HANDOVER_SUCCESS_RATE
HANDOVER_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HANDOVER_SUCCESS_RATE statistic tracks the percentage of handovers that were 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
Handovers.
Congestion on the target cell does not result in the BSS sending a handover command to the mobile therefore
this measurement is not impacted by target cell congestion.
Formula
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
HANDOVER_SUCCESS_RATE + HANDOVER_FAILURE_RATE ? 100% because the calls

that fail and recover to the source cell are not included in either of these key statistics.
68P02901W56-R 16-15
HANDOVER_SUCCESS_RATE Chapter 16: Key statistics

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics 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[INTRA_CELL_HO_SUC].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC].
16-16 68P02901W56-R
Maintenance Information: GSM Statistics Application LLC_ABNORMAL_TBF_RELEASES
LLC_ABNORMAL_TBF_RELEASES
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The LLC_ABNORMAL_TBF_RELEASES statistic calculates the percentage of discarded LLC blocks

due to abnormal TBF releases.
Formula
_ _ _ _ _ _ _ _
_ _ _ _
_ _ _
_ _
Usage Tracking radio problems/failures.

Utilisation.
Basis Cell.
Type Percentage.
Raw statistics PDU_DISCARD_LLC[PDU_DSCRD_LLC_AB-
NORM_TBFREL]
DL_LLC_FRAMES_PCU
DL_LLC_FRAMES_GB
UL_LLC_FRAMES.
68P02901W56-R 16-17
LLC_BUFFER_OVERFLOW_RATE Chapter 16: Key statistics
LLC_BUFFER_OVERFLOW_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The LLC_BUFFER_OVERFLOW_RATE statistic calculates the percentage of discarded LLC blocks

due to buffer overflows.
Formula
_ _
_ _ _ _ _
_ _
_ _ _ _ _ _ _
_ _ _ _
_ _ _
_ _
Usage Buffer management.

Basis Cell.
Type Percentage.
Raw statistics PDU_DIS-
CARD_LLC[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.
16-18 68P02901W56-R
Maintenance Information: GSM Statistics Application LLC_DISCARDS_ON_CELL_RESELECTION
LLC_DISCARDS_ON_CELL_RESELECTION
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
Description
The LLC_DISCARDS_ON_CELL_RESELECTION statistic calculates the percentage of discarded LLC

blocks due to cell reselections.
Formula
_ _
_ _ _ _
_ _
_ _ _ _ _ _
_ _
_ _ _
_ _ _
_ _
Usage Mobility management.

Handover.
Basis Cell.
Type Percentage.
Raw statistics PDU_DISCARD_LLC[PDU_DSCRD_LLC_RE-
SEL_INAREA].
PDU_DISCARD_LLC[PDU_DSCRD_LLC_RESEL_OUTAREA].
DL_LLC_FRAMES_PCU.
DL_LLC_FRAMES_GB.
UL_LLC_FRAMES.
68P02901W56-R 16-19
MEAN_ARRIVAL_TIME_BETWEEN_CALLS Chapter 16: 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
_ _ _
_ _ _ _ _
_ _ _ _

Fault finding.
Optimization.
Basis Cell.
Type Duration (in seconds).
Raw Statistics INTERVAL.
CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL].
CHAN_REQ_HO_CAUSE_ATMPT[EMERGENCY_CALL].
16-20 68P02901W56-R
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
BSS Level
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _

Optimization.
Basis BSS.
Raw Statistics INTERVAL.
OK_ACC_PROC[CM_SERV_REQ_SUPP].
68P02901W56-R 16-21
MEAN_TBF_SESSIONS Chapter 16: Key statistics
MEAN_TBF_SESSIONS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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
_ _ _
Usage PRP bandwidth.

Basis PRP.
Type Gauge.
Raw statistics TBF_SESSIONS.
16-22 68P02901W56-R
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
_ _
_ _ _
_ _
Usage Optimization.
Network planning.
Basis Cell.
Raw Statistics AVAILABLE_TCH.
BUSY_TCH.
68P02901W56-R 16-23
MTL_UTILISATION_RX Chapter 16: Key statistics
MTL_UTILISATION_RX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTL_UTILISATION_RX statistic provides a measure of MTL utilisation for the MSC to BSS direction.
Formula
_ _ _ _ _ _
_ _
_ _
NOTE: As an explanation as to how the formula was derived, refer to the following which shows no number
simplification:
_ _ _ _ _
_
_ _
_ _
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw Statistics MTP_MSU_RX.
MTP_SIF_SIO_RX.
SIB_RX.
MTP_LINK_INS.
16-24 68P02901W56-R
Maintenance Information: GSM Statistics Application MTL_UTILISATION_TX
MTL_UTILISATION_TX
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MTL_UTILISATION_TX statistic provides a measure of MTL utilisation for the BSS to MSC direction.
Formula
_ _ _ _ _ _
_ _
_ _
NOTE: As an explanation as to how the formula was derived, refer to the following which shows no number
simplification:
_ _ _ _ _
_
_ _
_ _
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw Statistics MTP_MSU_TX.
MTP_SIF_SIO_TX.
SIB_TX.
MTP_LINK_INS.
68P02901W56-R 16-25
RF_LOSS_RATE Chapter 16: 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.
16-26 68P02901W56-R
Maintenance Information: GSM Statistics Application RF_LOSS_RATE
Formula
{24349}
_ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
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.
Fault finding and optimization.
Basis Cell.
Type Percentage.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
OK_ACC_PROC: (The value used in this formula is the sum of
bins 0 to {24349} 15 of this counter array statistic).
RF_LOSSES_TCH.
RF_LOSSES_SD.
68P02901W56-R 16-27
SDCCH_BLOCKING_RATE Chapter 16: 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
_ _
_ _
_ _ _
Usage Service Accessibility.

Quality of Service monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics ALLOC_SDCCH.
ALLOC_SDCCH_FAIL.
16-28 68P02901W56-R
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
_ _ _
_ _ _
_

Optimization.
Basis Cell.
Type Total Time (in seconds).
BUSY_SDCCH.
INTERVAL_SUM (total statistics collection interval, measured in
hours).
68P02901W56-R 16-29
SDCCH_RF_LOSS_RATE Chapter 16: 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
{24620}
_ _
_ _ _
_
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL{24620}[SDCCH].
RF_LOSSES_SD.
16-30 68P02901W56-R
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.
68P02901W56-R 16-31
SDCCH_TRAFFIC_CARRIED Chapter 16: Key statistics
Formula
_ _ _ _
For an individual cell over m statistics intervals:
_ _
_ _
For n cells over an individual statistics interval:
_ _ _ _
For n cells over m statistics intervals:
_ _
_ _
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic channels during a
collection interval.Where BUSY_SDCCH_MEAN [κ] is BUSY_SDCCH_MEAN for statistical
interval κ.
Usage RF Loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.
16-32 68P02901W56-R
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
{24620}
_ _ _ _ _ _ _ _ _ _

Optimization.
Basis Cell or BSS.
Type Counter.
Raw Statistics CHAN_REQ_MS_BLK
OK_ACC_PROC_SUC_RACH.
68P02901W56-R 16-33
SUCCESS_INTERNAL_HO Chapter 16: Key statistics
SUCCESS_INTERNAL_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SUCCESS_INTERNAL_HO statistic tracks the number of successful internal handovers.
Formula
_ _ _ _ _
_ _
_ _ _ _ _ _ _

Optimization.
Quality of service.
Basis Cell.
Type Counter.
Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_SUC].
16-34 68P02901W56-R
Maintenance Information: GSM Statistics Application TBF_DROP_RATE_ON_PACCH_LOST
TBF_DROP_RATE_ON_PACCH_LOST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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.
Only those TBFs, whose PACCH are lost due to the switch to TCH are considered.
Formula
_ _ _ _ _
_ _ _ _ _ _
Usage PDTCH configuration.

Utilisation.
Basis Cell.
Type Percentage.
Raw statistics TBF_REL_PACCH_LOST
DL_PDTCH_SEIZURE
UL_PDTCH_SEIZURE
68P02901W56-R 16-35
TCH_BLOCKING_RATE Chapter 16: Key statistics
TCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_BLOCKING_RATE statistic provides the percentage of all requests for TCH resources
(originations and hand ins) which fail due to no available TCH resources.
Formula
_ _
_ _
_ _
_ _
_
_ _
_
_ _
_ _
_ _
_ _
_

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
ALLOC_TCH_FAIL.
ASSIGNMENT_RESOURCE_REQ.
HO_REQ.
16-36 68P02901W56-R
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
_ _ _ _
_ _
_ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _
_ _ _ _
_ _
_ _ _ _
_ _ _ _ _

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ALLOC_TCH_INNER_Z.
ALLOC_TCH_FAIL_INNER_Z.
TCH_Q_REMOVED (Bins 2 and 3 of this counter array statistic).
68P02901W56-R 16-37
TCH_BLOCKING_RATE_OUTER_Z Chapter 16: Key statistics
TCH_BLOCKING_RATE_OUTER_Z
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_BLOCKING_RATE_OUTER_Z 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
_ _
_ _ _ _
_ _
_ _
_ _
_ _ _ _
_ _ _
_ _ _ _ _ _ _
_ _ _
_ _ _
_ _
_ _ _ _
_ _
_ _
_ _
_ _ _ _
_ _ _
_ _ _ _ _

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ALLOC_TCH_FAIL.
ALLOC_TCH_FAIL_INNER_Z.
ALLOC_TCH.
ALLOC_TCH_INNER_Z.
TCH_Q_REMOVED (Bins 0 to 3 of this counter array statistic).
16-38 68P02901W56-R
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
_ _ _ _ _
_ _ _
The arrival rate of calls includes both calls set up on traffic channels within a cell and handovers
into the cell.
Basis Cell.
Type Counter (calls/interval).
ALLOC_TCH_FAIL.
TCH_Q_REMOVED.
68P02901W56-R 16-39
TCH_MEAN_HOLDING_TIME Chapter 16: 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.
16-40 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_MEAN_HOLDING_TIME
Formula
Cell Level
_ _
_ _ _
_ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
BSS Level
_ _
_ _ _
_ _
_ _
_ _
_ _
_ _ _
_ _ _ _
Network Level
_ _
_ _ _
_ _
_ _
_ _
_ _
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.
68P02901W56-R 16-41
TCH_MEAN_HOLDING_TIME Chapter 16: Key statistics
Analysis

Basis Cell, BSS or network.
Type Percentage.
BUSY_TCH_HR_MEAN.
TOTAL_CALLS.
ASSIGNMENT_REDIRECTION (The value used in this formula
16-42 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE
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
_ _
_ _ _
_ _ _ _ _
_ _ _ _
BSS Level
_ _
_ _ _
_
_ _
_ _
_ _
_ _ _ _ _ _
Network Level
_ _
_ _ _
_
_ _
_ _
_ _
68P02901W56-R 16-43
TCH_RF_LOSS_RATE Chapter 16: Key statistics
Analysis

Fault finding.
Basis Cell.
Type Percentage.
IN_INTER_BSS[IN_INTER_HO_SUC].
IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].
RF_LOSSES_TCH.
TOTAL_CALLS.
16-44 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED
TCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.
Formula
For an individual cell for an individual statistics interval:
_ _ _ _
_ _ _ _
where BUSY_TCH_MEAN[j] represents BUSY_TCH_MEAN for statistic interval j.

_ _ _ _
where BUSY_TCH_MEAN[i] represents BUSY_TCH_MEAN for entity i.

_ _ _ _
where BUSY_TCH_MEAN[i,j] represents BUSY_TCH_MEAN for entity i, statistic interval j.
68P02901W56-R 16-45
TCH_TRAFFIC_CARRIED Chapter 16: Key statistics
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).
16-46 68P02901W56-R
Maintenance Information: GSM Statistics Application TOTAL_CALLS_KEY
TOTAL_CALLS_KEY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TOTAL_CALLS_KEY statistic tracks the number of calls for one or more cells during the interval.
Formula
_ _ _

Fault finding.
Basis Cell.
Type Counter.
Raw Statistics TOTAL_CALLS.
68P02901W56-R 16-47
UL_LLC_TRAFFIC_VOLUME_INDICATOR Chapter 16: Key statistics
UL_LLC_TRAFFIC_VOLUME_INDICATOR
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _
_ _ _ _
_ _ _
_ _ _
_ _ _
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].
16-48 68P02901W56-R
Maintenance Information: GSM Statistics Application UNSUCCESS_INTERNAL_HO_NOREEST
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
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _

Quality of service.
Fault finding.
Basis Cell or BSS.
Type Counter
Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS].
68P02901W56-R 16-49
UNSUCCESS_INTERNAL_HO_REEST Chapter 16: Key statistics
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
_ _ _ _ _
_ _ _
_ _ _ _ _ _ _

Fault finding.
Quality of service.
Basis Cell or BSS.
Type Counter.
Raw Statistics INTRA_CELL_HO[INTRA_CELL_HO_RETURN].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN].
16-50 68P02901W56-R
Chapter
17
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 17-2.
68P02901W56-R 17-1
Network health statistics subgroups Chapter 17: Network health reports
Network health statistics subgroups

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Network health statistics are organized into the following major subgroups:
• "GPRS performance" on page 17-3.
• "Handover performance" on page 17-3.
• "Health check" on page 17-6.
• "Paging performance" on page 17-7.
• "Radio performance" on page 17-7.
• "SDCCH congestion" on page 17-8.
• "TCH congestion" on page 17-8.
17-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Network health statistics subgroups
GPRS performance
The following statistics provide key performance metrics for the GPRS system:
• "AIR_INTERFACE_BW_CS1" on page 17-9.
• "CELL_UPDATE" on page 17-25.
• "DL_AIR_INTERFACE_BW_CS1" on page 17-26.
• "GPRS_DL_ACT_TS" on page 17-32.
• "GPRS_UL_ACT_TS" on page 17-33.
• "UL_AIR_INTERFACE_BW_CS1" on page 17-118.
• "UPLINK_PDTCH_BLOCKING_RATE" on page 17-122.
Handover performance
The following statistics provide general handover information:

• "HO_CAUSE_ADJ_CH_INTERF" on page 17-34.
• "HO_CAUSE_BAND_HO" on page 17-35.
• "HO_CAUSE_BAND_REASSGN" on page 17-36.
• "HO_CAUSE_CONGEST" on page 17-37.
• "HO_CAUSE_DISTANCE" on page 17-38.
• "HO_CAUSE_DLINTERF" on page 17-39.
• "HO_CAUSE_DLLEVEL" on page 17-40.
68P02901W56-R 17-3
• "HO_CAUSE_DLQUAL" on page 17-41.
• "HO_CAUSE_PWRBGT" on page 17-42.
• "HO_CAUSE_UPINTERF" on page 17-43.
• "HO_CAUSE_UPLEVEL" on page 17-44.
• "HO_CAUSE_UPQUAL" on page 17-45.
• "HO_PER_CALL" on page 17-46.
• "IN_INTER_BSS_HO_SUC" on page 17-52.
• "IN_INTER_CELL_HO_SUC" on page 17-53.
• "IN_INTRA_BSS_HO_SUC" on page 17-54.
• "INCOMING_HO_VOLUME" on page 17-55.
• "INTERNAL_LOST" on page 17-56.
• "INTERNAL_RECOVERED" on page 17-57.
• "INTERNAL_SUCCESS" on page 17-58.
• "INTRA_CELL_HO_FAIL_LOST_MS" on page 17-59.
• "INTRA_CELL_HO_FAIL_RECOVERED" on page 17-60.
• "INTRA_CELL_HO_SUCCESS_RATE" on page 17-61.
• "MEAN_TIME_BETWEEN_DROPS" on page 17-64.
• "MEAN_TIME_BETWEEN_HOs" on page 17-65.
• "OUT_INTER_BSS_HO_FAIL_LOST_MS" on page 17-68.
• "OUT_INTER_BSS_HO_FAIL_RECOVERED" on page 17-69.
• "OUT_INTER_BSS_HO_SUCCESS_RATE" on page 17-70.
• "OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS" on page 17-71.
• "OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS" on page 17-72.
• "OUT_INTER_CELL_HO_SUCCESS_RATE" on page 17-73.
• "OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS" on page 17-74.
• "OUT_INTRA_BSS_HO_FAIL_LOST_MS" on page 17-75.
• "OUT_INTRA_BSS_HO_SUC" on page 17-77.
• "OUTGOING_HO_VOLUME" on page 17-78.
• "PERCENTAGE_INTER_BSS_HO" on page 17-83.
17-4 68P02901W56-R
• "PERCENTAGE_INTRA_BSS_HO" on page 17-84.
• "PERCENTAGE_INTRA_CELL_HO" on page 17-85.
68P02901W56-R 17-5
Health check
The following statistics provide health check information:

• "CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS" on page 17-15.
• "CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RECOVERED_MS" on page 17-17.
• "CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE" on page 17-18.
• "CALL_SETUP_SUCCESS_RATE" on page 17-19.
• "CALL_SUCCESS_RATE" on page 17-22.
• "CALL_VOLUME" on page 17-23.
• {22577} "CELL_CONGESTION_TIME" on page 17-24
• "DROP_CALL_RATE" on page 17-30.
• {24620} "IMMEDIATE_ASSIGN_BLOCKING_RATE" on page 17-47.
• {24620} "IMMEDIATE_ASSIGN_FAILURE_RATE" on page 17-48.
• {24620} "IMMEDIATE_ASSIGN_MEAN_ARRIVAL_TIME" on page 17-49.
• {24620} "IMMEDIATE_ASSIGN_SUCCESS_RATE" on page 17-50.
• {22879} "NUM_HO_FROM_3G_FAIL" on page 17-66.
• {22879} "NUM_HO_TO_3G_FAIL" on page 17-67.
• "RANKING_FORMULA" on page 17-86.
• "SDCCH_BLOCKING_RATE" on page 17-92.
• "SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF" on page 17-106.
• "SPILL_OVER_FACTOR_DIRECTED_RETRY" on page 17-107.
• "SPILL_OVER_FACTOR_MULTIBAND" on page 17-108.
17-6 68P02901W56-R
Paging performance
The following statistics provide paging performance information:

• "AIR_INTERFACE_PAGING" on page 17-13.
• "MSC_PAGING" on page 17-63.
• "PAGING_COMPRESSION_RATE" on page 17-79.
• "PAGING_OVERFLOW_RATE" on page 17-80.
• "PAGING_RESPONSE" on page 17-81.
• "PAGING_SUCCESS_RATE" on page 17-82.
Radio performance
The following statistics provide radio performance information:

• "ASSIGNMENT_SUCCESS_RATE" on page 17-14.
• "OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS" on page 17-71.
• "OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS" on page 17-72.
• "OUT_INTER_CELL_HO_SUCCESS_RATE" on page 17-73.
• "RF_ASSIGN_FAIL_RATE_LOST_MS" on page 17-88.
• "RF_ASSIGN_FAIL_RATE_RECOVERED" on page 17-89.
• "RF_ASSIGNMENT_SUCCESS_RATE" on page 17-90.
• "TCH_RF_LOSS_RATE" on page 17-114.
68P02901W56-R 17-7
SDCCH congestion
The following statistics provide SDCCH congestion information:

• "SDCCH_ACCESSES" on page 17-91.
• "SDCCH_BLOCKING_RATE" on page 17-92.
• "SDCCH_CONGESTION_TIME" on page 17-93.
• "SDCCH_TRAFFIC_CARRIED" on page 17-94.
• "SDCCH_USAGE_ACCESS_FAILURE" on page 17-96.
• "SDCCH_USAGE_CALL_REESTABLISH" on page 17-97.
• "SDCCH_USAGE_EMERGENCY_CALL" on page 17-98.
• "SDCCH_USAGE_IMSI_DETACH" on page 17-99.
• "SDCCH_USAGE_LOCATION_UPDATE" on page 17-100.
• "SDCCH_USAGE_MS_ORIGINATED_CALL" on page 17-101.
• "SDCCH_USAGE_MS_ORIGINATED_SMS" on page 17-102.
• "SDCCH_USAGE_SMS_ORIGINATED_SS" on page 17-103.
• "SDCCH_USAGE_PAGING_RESPONSE" on page 17-104.
• "SDCCH_USAGE_SMS" on page 17-105.
TCH congestion
The following statistics provide TCH congestion information:

• "MAX_TCH_BUSY" on page 17-62.
• "TCH_ACCESSES" on page 17-109.
• "TCH_CONGESTION_TIME" on page 17-111.
• "TCH_CONGESTION_TIME_INNER_ZONE" on page 17-112.
• "TCH_CONGESTION_TIME_OUTER_ZONE" on page 17-113.
17-8 68P02901W56-R
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
_ _ _ _

Basis Cell.
Type Counter.
Raw Statistics GPRS_AVAIL_PDTCH.
68P02901W56-R 17-9
AIR_INTERFACE_BW_CS2 Chapter 17: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_ _ _ _

Basis Cell.
Type Counter.
17-10 68P02901W56-R
Maintenance Information: GSM Statistics Application AIR_INTERFACE_BW_CS3
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-11
AIR_INTERFACE_BW_CS4 Chapter 17: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_ _ _ _

Basis Cell.
Type Counter.
17-12 68P02901W56-R
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
_ _ _ _ _ _
_ _
_ _ _ _ _
_ _ _ _ _

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-R 17-13
ASSIGNMENT_SUCCESS_RATE Chapter 17: Network health reports
ASSIGNMENT_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The ASSIGNMENT_SUCCESS_RATE statistic measures the success rate of the A-interface assignment
procedure which will also automatically include the impact of the air interface assignment procedure.
Formula
_ _ _
_ _
_ _ _

Quality of service.
Basis Cell.
Type Percentage.
Raw Statistics MA_COMPLETE_TO_MSC.
MA_REQ_FROM_MSC.
17-14 68P02901W56-R
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.
Formula
_ _ _
_ _ _
_ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
68P02901W56-R 17-15
CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_LOST_MS Chapter 17: Network health reports

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS.
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).
17-16 68P02901W56-R
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 subsequently successfully recovering to the original
channel. This statistic includes the impact of successful second assignments and intra-cell handover
assignment attempts.
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _

Fault finding.
Basis Cell.
Type Percentage.
MA_FAIL_FROM_MS.
INTRA_CELL_HO_RETURN.
68P02901W56-R 17-17
CALL_SETUP_RF_ASSIGNMENT_SUCCESS_RATE Chapter 17: Network health reports
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.
Formula
_ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _

Fault finding.
Basis Cell.
Type Percentage.
MA_COMPLETE_FROM_MS.
INTRA_CELL_HO_SUC.
17-18 68P02901W56-R
CALL_SETUP_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CALL_SETUP_SUCCESS_RATE statistic tracks the percentage of call attempts that result 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
{28014 / 24349}
68P02901W56-R 17-19
CALL_SETUP_SUCCESS_RATE Chapter 17: Network health reports
Cell Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
BSS Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
17-20 68P02901W56-R
Network Level
_
_ _
_ _
_ _ _ _
_ _ _ _ _ _
_ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
MT_LCS_ON_SDCCH.
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
SMS_INIT_ON_SDCCH.
{28014} SMS_INIT_ON_SDCCH_HO_OUT[INTER_CELL].
{28014} SDCCH_HANDOVER[OUT_INTRA_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[OUT_INTER_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[IN_INTRA_BSS_HO_SUC].
{28014} SDCCH_HANDOVER[IN_IN-
TER_BSS_HO_ATTMPT].
TOTAL_CALLS.
68P02901W56-R 17-21
CALL_SUCCESS_RATE Chapter 17: Network health reports
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
_ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION.
{22103} OUT_INTER_BSS_HO[OUT_IN-
TER_BSS_HO_FAIL].
TER_BSS_EQUIP_FAIL].
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.
17-22 68P02901W56-R
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
_
_ _
_
_ _
_ _

Basis Cell.
Type Counter.
TOTAL_CALLS.
68P02901W56-R 17-23
CELL_CONGESTION_TIME Chapter 17: Network health reports
CELL_CONGESTION_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22577}
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
_ _ _ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _
_ _ _ _
_ _ _ _
_ _ _ _
_ _
Usage Cell congestion analysis.

Basis Cell.
Type Time interval.
Raw Statistics GPRS_CELL_CONGESTION[GPRS_CONGESTION_30].
GPRS_CELL_CONGESTION[GPRS_CONGESTION_35].
17-24 68P02901W56-R
Maintenance Information: GSM Statistics Application CELL_UPDATE
CELL_UPDATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The CELL_UPDATE statistic measures the number of cell reselections relating to a particular cell.
Formula
_ _ _

Basis Cell.
Type Counter.
Raw Statistics CELL_FLUSH_REQS.
68P02901W56-R 17-25
DL_AIR_INTERFACE_BW_CS1 Chapter 17: Network health reports
DL_AIR_INTERFACE_BW_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DL_AIR_INTERFACE_BW_CS1 statistic provides a reference value in kilobits per second for the
configured downlink bandwidth in a cell in terms of coding scheme 1 for a statistics collection period.
Formula
For GSR6 (Horizon II) the formula is:
_
_ _ _ _

Basis Cell.
Type Counter.
INTERVAL is either 0.5 for a 30 minute collection period or 1 for
a 60 minute collection period.
17-26 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-27
DL_AIR_INTERFACE_BW_CS3 Chapter 17: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
17-28 68P02901W56-R
Maintenance Information: GSM Statistics Application DL_AIR_INTERFACE_BW_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-29
DROP_CALL_RATE Chapter 17: Network health reports
DROP_CALL_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The DROP_CALL_RATE statistic tracks the percentage of MSs which, having successfully accessed a
TCH, subsequently experience an abnormal release caused by either radio or equipment problems. This
includes RF losses and losses during handovers.
Formulas
{22103}
Cell Level
_ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _ _ _ _ _ _
_ _ _ _ _ _ _
{22103}
BSS Level
_ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
_ _ _ _ _ _ _
17-30 68P02901W56-R
Maintenance Information: GSM Statistics Application DROP_CALL_RATE
{22103}
Network Level
_ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
Analysis

Basis Cell, BSS, or network.
Type Percentage.
Raw Statistics ASSIGNMENT_REDIRECTION (The value used in this formula is the
sum of bins 0 to 2 of this counter array statistic).
{22103} OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_FAIL].
{22103} OUT_INTER_BSS_HO[OUT_INTER_BSS_EQUIP_FAIL].
RF_LOSSES_TCH.
TOTAL_CALLS.
68P02901W56-R 17-31
GPRS_DL_ACT_TS Chapter 17: Network health reports
GPRS_DL_ACT_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_DL_ACT_TS statistic measures the utilization of busy downlink PDTCHs in a cell.
Formula
_ _ _ _ _ _

Basis Cell.
Type Counter.
Raw Statistics DL_BUSY_PDTCH.
17-32 68P02901W56-R
Maintenance Information: GSM Statistics Application GPRS_UL_ACT_TS
GPRS_UL_ACT_TS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The GPRS_UL_ACT_TS statistic measures the utilization of busy uplink PDTCHs in a cell.
Formula
_ _ _ _ _ _

Basis Cell.
Type Counter.
Raw Statistics UL_BUSY_PDTCH.
68P02901W56-R 17-33
HO_CAUSE_ADJ_CH_INTERF Chapter 17: Network health reports
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
_ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OUT_HO_CAUSE_ATMPT.
17-34 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_BAND_HO
HO_CAUSE_BAND_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_BAND_HO statistic provides the percentage of all handovers due to band handover.
Formula
_ _ _ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-35
HO_CAUSE_BAND_REASSGN Chapter 17: Network health reports
HO_CAUSE_BAND_REASSGN
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_BAND_REASSGN statistic provides the percentage of all handovers due to band
reassignment.
Formula
_ _ _ _ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-36 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_CONGEST
HO_CAUSE_CONGEST
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_CONGEST statistic provides the percentage of all handovers due to congestion (directed
retry or congestion relief).
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-37
HO_CAUSE_DISTANCE Chapter 17: Network health reports
HO_CAUSE_DISTANCE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DISTANCE statistic provides the percentage of all handovers due to distance (timing
advance).
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-38 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_DLINTERF
HO_CAUSE_DLINTERF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLINTERF statistic provides the percentage of all handovers due to downlink
interference.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-39
HO_CAUSE_DLLEVEL Chapter 17: Network health reports
HO_CAUSE_DLLEVEL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLLEVEL statistic provides the percentage of all handovers due to downlink level.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-40 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_DLQUAL
HO_CAUSE_DLQUAL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_DLQUAL statistic provides the percentage of all handovers due to downlink quality.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-41
HO_CAUSE_PWRBGT Chapter 17: Network health reports
HO_CAUSE_PWRBGT
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_PWRBGT statistic provides the percentage of all handovers due to power budget.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-42 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_UPINTERF
HO_CAUSE_UPINTERF
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPINTERF statistic provides the percentage of all handovers due to uplink interference.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-43
HO_CAUSE_UPLEVEL Chapter 17: Network health reports
HO_CAUSE_UPLEVEL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPLEVEL statistic provides the percentage of all handovers due to uplink level.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-44 68P02901W56-R
Maintenance Information: GSM Statistics Application HO_CAUSE_UPQUAL
HO_CAUSE_UPQUAL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_CAUSE_UPQUAL statistic provides the percentage of all handovers due to uplink quality.
Formula
_ _ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-45
HO_PER_CALL Chapter 17: Network health reports
HO_PER_CALL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The HO_PER_CALL statistic tracks the average number of successful handovers per call.
Formula
Cell Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
BSS Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _
Network Level
_ _ _ _
_ _ _ _ _ _ _
_ _
_
_ _
_ _
_ _

Fault finding.
Basis Cell, BSS or network.
Type Counter.
TOTAL_CALLS.
17-46 68P02901W56-R
Maintenance Information: GSM Statistics Application IMMEDIATE_ASSIGN_BLOCKING_RATE
IMMEDIATE_ASSIGN_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24620}
This statistic was previously named SDCCH_SETUP_BLOCKING_RATE.
Description
The {24620} 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
_ _ _
_ _ _
_ _ _ _
Usage Service Accessibility.

GPRS Quality of Service monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics CHAN_REQ_MS_BLK.
68P02901W56-R 17-47
IMMEDIATE_ASSIGN_FAILURE_RATE Chapter 17: Network health reports
IMMEDIATE_ASSIGN_FAILURE_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24620}
This statistic was previously named SDCCH_ACCESS_FAILURE_RATE.
Description
The {24620} IMMEDIATE_ASSIGN_FAILURE_RATE statistic calculates the proportion of resource

assignment activations that fail to achieve mobile access.
Formula
_ _ _ _ _
_ _ _ _ _
_ _ _

Basis Cell.
Type Percentage.
Raw statistics CHAN_REQ_MS_FAIL.
CHAN_REQ_MS_BLK.
17-48 68P02901W56-R
Maintenance Information: GSM Statistics Application IMMEDIATE_ASSIGN_MEAN_ARRIVAL_TIME
IMMEDIATE_ASSIGN_MEAN_ARRIVAL_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24620}
This statistic was previously named SDCCH_MEAN_ARRIVAL_RATE.
Description
The {24620} 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
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _

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-R 17-49
IMMEDIATE_ASSIGN_SUCCESS_RATE Chapter 17: Network health reports
IMMEDIATE_ASSIGN_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24620}
This statistic was previously named SDCCH_ACCESS_SUCCESS_RATE.
Description
The {24620} IMMEDIATE_ASSIGN_SUCCESS_RATE statistic calculates the proportion of SDCCH

activation which is followed by successful MS access.
17-50 68P02901W56-R
Maintenance Information: GSM Statistics Application IMMEDIATE_ASSIGN_SUCCESS_RATE
Formula
{24620}
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _

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).
68P02901W56-R 17-51
IN_INTER_BSS_HO_SUC Chapter 17: Network health reports
IN_INTER_BSS_HO_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTER_BSS_HO_SUC 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.
Formula
_ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics IN_INTER_BSS_HO_SUC.
HO_REQ_ACK_TO_MSC.
17-52 68P02901W56-R
Maintenance Information: GSM Statistics Application IN_INTER_CELL_HO_SUC
IN_INTER_CELL_HO_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTER_CELL_HO_SUC statistic tracks the percentage of incoming inter-cell handover commands
Formula
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics IN_INTRA_BSS_HO_SUC.
IN_INTER_BSS_HO_SUC.
IN_INTRA_BSS_HO (The value used in this formula is the sum of
HO_REQ_ACK_TO_MSC.
68P02901W56-R 17-53
IN_INTRA_BSS_HO_SUC Chapter 17: Network health reports
IN_INTRA_BSS_HO_SUC
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The IN_INTRA_BSS_HO_SUC statistic tracks the percentage of incoming intra-BSS handover commands
Formula
_ _ _ _ _ _ _
_ _ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics IN_INTRA_BSS_HO_SUC.
IN_INTRA_BSS_HO (The value used in this formula is the sum
of bins 0 to 4 of this counter array statistic).
17-54 68P02901W56-R
Maintenance Information: GSM Statistics Application INCOMING_HO_VOLUME
INCOMING_HO_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INCOMING_HO_VOLUME statistic provides the number of successful incoming handovers.
Formulas
Cell Level
_ _ _ _ _ _ _
_ _
_ _ _ _ _ _ _
BSS Level
_ _ _ _ _ _ _ _ _

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
68P02901W56-R 17-55
INTERNAL_LOST Chapter 17: 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
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-56 68P02901W56-R
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
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
INTRA_CELL_HO[INTRA_CELL_HO_RETURN].
68P02901W56-R 17-57
INTERNAL_SUCCESS Chapter 17: 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
_ _ _ _ _ _ _
_ _ _ _ _
_
_ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-58 68P02901W56-R
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
_ _ _ _ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _

Fault finding.
Type Percentage.
Raw Statistics INTRA_CELL_HO (The value used in this formula is bin 6 and
the sum of bins 1 to 4 of this counter array statistic).
68P02901W56-R 17-59
INTRA_CELL_HO_FAIL_RECOVERED Chapter 17: Network health reports
INTRA_CELL_HO_FAIL_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The INTRA_CELL_HO_FAIL_RECOVERED statistic tracks the percentage of intra-cell assignment

subsequently successfully recovering to the original channel.
Formula
_ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _

Fault finding.
Type Percentage.
17-60 68P02901W56-R
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
_ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _

Fault finding.
Type Percentage.
68P02901W56-R 17-61
MAX_TCH_BUSY Chapter 17: Network health reports
MAX_TCH_BUSY
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MAX_TCH_BUSY statistic tracks the maximum number of simultaneously busy TCHs.
Formula
_ _ _
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Counter.
Raw Statistics BUSY_TCH[MAX].
17-62 68P02901W56-R
Maintenance Information: GSM Statistics Application MSC_PAGING
MSC_PAGING
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MSC_PAGING statistic tracks the total number of BSSMAP paging messages received over the
A-interface from the MSC.
Formula
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-63
MEAN_TIME_BETWEEN_DROPS Chapter 17: Network health reports
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
_ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _ _
Analysis

Fault finding.
Basis Cell.
Type Time interval.
BUSY_TCH_HR_MEAN.
RF_LOSSES_TCH_MEAN.
RF_LOSSES_TCH_HR_AMR_MEAN.
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED].
17-64 68P02901W56-R
Maintenance Information: GSM Statistics Application MEAN_TIME_BETWEEN_HOs
MEAN_TIME_BETWEEN_HOs
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The MEAN_TIME_BETWEEN_HOs statistic tracks the mean time interval between inter cell handovers.
Formula
_ _ _
_ _ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _
Analysis

Fault finding.
Basis Cell.
Type Time interval (in seconds).
BUSY_TCH_HR_MEAN
68P02901W56-R 17-65
NUM_HO_FROM_3G_FAIL Chapter 17: Network health reports
NUM_HO_FROM_3G_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
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
_ _ _ _
_ _ _ _
_ _ _ _
Usage Network health.

Handover.
Basis Cell.
Type Counter.
Raw statistics NUM_HO_FROM_3G_ATTEMPTS.
NUM_HO_FROM_3G_SUCCESS.
17-66 68P02901W56-R
Maintenance Information: GSM Statistics Application NUM_HO_TO_3G_FAIL
NUM_HO_TO_3G_FAIL
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
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
_ _ _ _
_ _ _ _
_ _ _ _
Usage Network health.

Handover.
Basis Cell.
Type Counter.
Raw statistics NUM_HO_TO_3G_ATTEMPTS.
NUM_HO_TO_3G_SUCCESS.
68P02901W56-R 17-67
OUT_INTER_BSS_HO_FAIL_LOST_MS Chapter 17: Network health reports
OUT_INTER_BSS_HO_FAIL_LOST_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of inter-BSS handover

Formula
{22103}
_ _ _
_ _ _ _
_ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].
TER_BSS_HO_FAIL].
17-68 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_INTER_BSS_HO_FAIL_RECOVERED
OUT_INTER_BSS_HO_FAIL_RECOVERED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_BSS_HO_FAIL_RECOVERED 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 a
subsequently successful recovering to the original channel.
Formula
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
68P02901W56-R 17-69
OUT_INTER_BSS_HO_SUCCESS_RATE Chapter 17: Network health reports
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
_ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
17-70 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_FAIL_RATE_LOST_MS
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

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. This statistic does not include
intra-cell handovers.
Formula
{22103}
_ _ _ _
_ _ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
{22103}OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_FAIL]
{22103}OUT_INTER_BSS_HO[OUT_INTER_BSS_EQUIP_FAIL]
68P02901W56-R 17-71
OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS Chapter 17: Network health reports
OUT_INTER_CELL_HO_FAIL_RATE_
RECOVERED_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_FAIL_RATE_RECOVERED_MS 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 a subsequently successful recovering to the original channel. This statistic does not
include intra-cell handovers.
Formula
_ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _
_ _ _
_ _ _ _ _ _ _ _
_ _ _ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-72 68P02901W56-R
Maintenance Information: GSM Statistics Application OUT_INTER_CELL_HO_SUCCESS_RATE
OUT_INTER_CELL_HO_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_SUCCESS_RATE statistic tracks the percentage of inter-cell handover

commands that result in the MS successfully accessing the target channel. This statistic includes intra-BSS
and inter-BSS inter-cell handovers.
Formula
_ _ _ _
_ _ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
68P02901W56-R 17-73
OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS Chapter 17: Network health reports
OUT_INTER_CELL_HO_SUCCESS_RATE_
RECOVERED_MS
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUT_INTER_CELL_HO_SUCCESS_RATE_RECOVERED_MS statistic tracks the percentage of

inter-cell handover commands that are sent over the air interface which result in the MS successfully accessing
the target channel and successfully re-establishing on the original channel.
Formula
_ _ _ _
_ _ _ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO_RETURN.
OUT_INTER_BSS_HO_RETURN.
OUT_INTRA_BSS_HO_ATMPT.
OUT_INTER_BSS_HO_ATMPT.
17-74 68P02901W56-R
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 handover

Formula
_ _ _ _ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT].
68P02901W56-R 17-75
OUT_INTRA_BSS_HO_FAIL_RECOVERED_MS Chapter 17: 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 a subsequently successful recovering to the original channel.
Formula
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
17-76 68P02901W56-R
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.
Formula
_ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
68P02901W56-R 17-77
OUTGOING_HO_VOLUME Chapter 17: Network health reports
OUTGOING_HO_VOLUME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The OUTGOING_HO_VOLUME statistic tracks the number of successful outgoing handovers.
Formula
_ _ _ _ _ _ _
_ _
_ _ _ _ _ _ _

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC].
17-78 68P02901W56-R
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
_ _ _ _ _ _
_ _ _ _ _
_ _ _ _ _ _
_
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics ACCESS_PER_PCH (The value used in this formula is the sum of
PAGING_REQUESTS (The value used in this formula is the sum
of bins 1 and 2 of this counter array statistic).
68P02901W56-R 17-79
PAGING_OVERFLOW_RATE Chapter 17: 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).
Formulas
Circuit switched
_ _ _ _ _
_ _ _ _
Packet switched
_ _ _ _ _
_ _ _ _

Fault finding.
Type Percentage.
Raw Statistics PCH_PAGE_Q_DISCARD[CS].
PCH_PAGE_Q_DISCARD[PS].
PAGING_REQUESTS[PAGING_REQS_CS].
PAGING_REQUESTS[PAGING_REQS_PS].
17-80 68P02901W56-R
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
_ _ _ _

Fault finding.
Type Counter.
Raw Statistic OK_ACC_PROC[PAGE_RESPONSE].
68P02901W56-R 17-81
PAGING_SUCCESS_RATE Chapter 17: 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
_ _ _
_ _
_
where SUM (OK_ACC_PROC[PAGE_RESPONSE]) is summed across all cells in the location area and
assuming paging is configured on a location area basis, PAGE_REQ_FROM_MSC is the maximum value
occurring on any cell within the LAC.
Fault finding
Basis Location area.
Type Percentage.
Raw Statistics OK_ACC_PROC[PAGE_RESPONSE].
PAGE_REQ_FROM_MSC.
17-82 68P02901W56-R
Maintenance Information: GSM Statistics Application PERCENTAGE_INTER_BSS_HO
PERCENTAGE_INTER_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PERCENTAGE_INTER_BSS_HO statistic calculates the percentage of all inter-BSS handover

attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTER_BSS_HO_ATMPT.
68P02901W56-R 17-83
PERCENTAGE_INTRA_BSS_HO Chapter 17: Network health reports
PERCENTAGE_INTRA_BSS_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PERCENTAGE_INTRA_BSS_HO statistic calculates the percentage of all intra-BSS handover

attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _

Fault finding.
Basis BSS.
Type Percentage.
Raw Statistics OUT_INTRA_BSS_HO_ATMPT.
17-84 68P02901W56-R
Maintenance Information: GSM Statistics Application PERCENTAGE_INTRA_CELL_HO
PERCENTAGE_INTRA_CELL_HO
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The PERCENTAGE_INTRA_CELL_HO statistic calculates the percentage of all intra-cell handover

attempts.
Formula
_ _ _ _
_ _ _ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _
_ _ _ _ _
_ _ _
_ _ _ _
_ _ _
_ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics INTRA_CELL_HO_ATMPT.
68P02901W56-R 17-85
RANKING_FORMULA Chapter 17: 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.
17-86 68P02901W56-R
Maintenance Information: GSM Statistics Application RANKING_FORMULA
Formula
_ _ _
_
_ _ _
Usage Optimization.
Basis Cell.
Type Counter.
MT_LCS_ON_SDCCH.
TER_BSS_HO_FAIL].
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.
68P02901W56-R 17-87
RF_ASSIGN_FAIL_RATE_LOST_MS Chapter 17: 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
_ _ _ _ _ _
_ _ _ _ _ _
_ _ _ _ _

Fault finding.
Basis Cell.
Type Percentage.
MA_FAIL_FROM_MS.
17-88 68P02901W56-R
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 subsequently
successfully recovering to the original channel. This statistic includes intra-cell handover assignment attempts.
Formula
_ _ _
_ _ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
MA_FAIL_FROM_MS.
68P02901W56-R 17-89
RF_ASSIGNMENT_SUCCESS_RATE Chapter 17: Network health reports
RF_ASSIGNMENT_SUCCESS_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The RF_ASSIGNMENT_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
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
17-90 68P02901W56-R
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
{24620}
_
_ _ _ _
_ _ _
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Basis Cell.
Type Counter.
CHAN_REQ_MS_FAIL{24620}[SDCCH].
68P02901W56-R 17-91
SDCCH_BLOCKING_RATE Chapter 17: 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
_ _
_ _
_ _ _

Quality of Service Monitoring.
Network planning.
Basis Cell.
Type Percentage.
ALLOC_SDCCH_FAIL.
17-92 68P02901W56-R
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
_
_ _
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration (seconds).
Raw Statistics SDCCH_CONGESTION.
68P02901W56-R 17-93
SDCCH_TRAFFIC_CARRIED Chapter 17: Network health reports
SDCCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHs measured
in Erlangs.
17-94 68P02901W56-R
Maintenance Information: GSM Statistics Application SDCCH_TRAFFIC_CARRIED
Formula
_ _ _ _
_ _
_ _
_ _ _ _
_ _
_ _
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic channels during a
collection interval.Where BUSY_SDCCH_MEAN [κ] is BUSY_SDCCH_MEAN for statistical
interval κ.
Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.
68P02901W56-R 17-95
SDCCH_USAGE_ACCESS_FAILURE Chapter 17: 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.
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

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.
17-96 68P02901W56-R
Maintenance Information: GSM Statistics Application SDCCH_USAGE_CALL_REESTABLISH
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.
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-R 17-97
SDCCH_USAGE_EMERGENCY_CALL Chapter 17: 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 mobile originated emergency call attempts.
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
17-98 68P02901W56-R
Maintenance Information: GSM Statistics Application SDCCH_USAGE_IMSI_DETACH
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.
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-R 17-99
SDCCH_USAGE_LOCATION_UPDATE Chapter 17: Network health reports
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.
Formula
_ _ _ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
17-100 68P02901W56-R
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 mobile originated call attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-R 17-101
SDCCH_USAGE_MS_ORIGINATED_SMS Chapter 17: Network health reports
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 mobile originated SMS attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
17-102 68P02901W56-R
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 mobile originated Supplementary Service (SS) attempts.
Formula
_ _ _ _ _
_ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
68P02901W56-R 17-103
SDCCH_USAGE_PAGING_RESPONSE Chapter 17: Network health reports
SDCCH_USAGE_PAGING_RESPONSE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The SDCCH_USAGE_PAGING_RESPONSE statistic tracks the percentage of immediate assignment

SDCCH activations that are due to mobile terminated transaction attempts (for example, calls, SMSs
or Supplementary Services).
Formula
_ _ _
_ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
CHAN_REQ_MS_FAIL.
17-104 68P02901W56-R
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 mobile originated or mobile terminated SMS attempts.
Formula
_ _ _
_ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _ _ _
_ _ _
_ _ _
_ _ _
_ _ _
_ _ _

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics SMS_INIT_ON_SDCCH.
CHAN_REQ_MS_FAIL.
68P02901W56-R 17-105
SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGESTION_RELIEF Chapter 17: Network health reports
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.
Formula
_ _ _ _ _ _
_ _
_ _
_ _
_ _
_ _

Basis Cell.
Type Percentage.
Raw Statistics CONGEST_EXIST_HO_ATMPT.
ASSIGNMENT_REDIRECTION (The value used in this formula
TOTAL_CALLS.
17-106 68P02901W56-R
Maintenance Information: GSM Statistics Application SPILL_OVER_FACTOR_DIRECTED_RETRY
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 neighbouring cell via directed retry or a
handover during assignment.
Formula
_ _
_ _ _ _ _
_ _
_ _
_ _
_ _

Basis Cell.
Type Percentage.
uses bins 0 to 2 of this counter array statistic).
TOTAL_CALLS.
68P02901W56-R 17-107
SPILL_OVER_FACTOR_MULTIBAND Chapter 17: Network health reports
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 neighbouring cell via a multiband handover.
Formula
_ _ _ _ _
_
_ _
_ _
_ _

Basis Cell.
Type Percentage.
uses the bins 0 to 2 of this counter array statistic).
TOTAL_CALLS.
17-108 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_ACCESSES
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
_
_ _ _ _ _
_ _ _ _
BSS Level
_
_ _ _ _
_ _ _
_ _
_ _
Network Level
_
_ _ _
_ _
_ _
68P02901W56-R 17-109
TCH_ACCESSES Chapter 17: Network health reports
Usage Handover.
Quality of service.
Network planning.
Type Counter.
TOTAL_CALLS.
17-110 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_CONGESTION_TIME
TCH_CONGESTION_TIME
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all TCHs are busy.
Formula
_
_ _
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
68P02901W56-R 17-111
TCH_CONGESTION_TIME_INNER_ZONE Chapter 17: Network health reports
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
_ _ _ _ _ _
_
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION_INNER_Z.
17-112 68P02901W56-R
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
_ _ _ _
_
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:
_ _ _ _ _
_ _
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw Statistics TCH_CONGESTION.
Additional Raw Statistic for Half TCH_CONGESTION_HR.
Rate
68P02901W56-R 17-113
TCH_RF_LOSS_RATE Chapter 17: 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
_ _
_ _ _
_ _ _ _ _
_ _ _ _
BSS Level
_ _
_ _ _
_
_ _
_ _
_ _
_ _ _ _ _ _
Network Level
_ _
_ _ _
_
_ _
_ _
_ _
17-114 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_RF_LOSS_RATE
Analysis

Fault finding.
Basis Cell.
Type Percentage.
IN_INTER_BSS[IN_INTER_HO_SUC].
IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC].
RF_LOSSES_TCH..
TOTAL_CALLS.
68P02901W56-R 17-115
TCH_TRAFFIC_CARRIED Chapter 17: Network health reports
TCH_TRAFFIC_CARRIED
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs measured in Erlangs.
Formula
For an individual cell for an individual statistics interval:
_ _ _ _
_ _ _ _
where BUSY_TCH_MEAN[j] represents BUSY_TCH_MEAN for statistic interval j.

_ _ _ _
where BUSY_TCH_MEAN[i] represents BUSY_TCH_MEAN for entity i.

_ _ _ _
where BUSY_TCH_MEAN[i,j] represents BUSY_TCH_MEAN for entity i, statistic interval j.
17-116 68P02901W56-R
Maintenance Information: GSM Statistics Application TCH_TRAFFIC_CARRIED
Analysis
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw Statistics BUSY_TCH (BUSY_TCH_MEAN).
68P02901W56-R 17-117
UL_AIR_INTERFACE_BW_CS1 Chapter 17: Network health reports
UL_AIR_INTERFACE_BW_CS1
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UL_AIR_INTERFACE_BW_CS1 statistic provides a reference value for the configured uplink
bandwidth in a cell in terms of coding scheme 1 for a statistics collection period.
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
17-118 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS2
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-119
UL_AIR_INTERFACE_BW_CS3 Chapter 17: Network health reports
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
17-120 68P02901W56-R
Maintenance Information: GSM Statistics Application UL_AIR_INTERFACE_BW_CS4
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
Formula
_
_ _ _ _

Basis Cell.
Type Counter.
68P02901W56-R 17-121
UPLINK_PDTCH_BLOCKING_RATE Chapter 17: Network health reports
UPLINK_PDTCH_BLOCKING_RATE
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Description
The UPLINK_PDTCH_BLOCKING_RATE statistic provides the success rate of channel requests in GPRS.
Formula

Quality of Service Monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw Statistics CHANNEL_REQS_REJECT.
CHANNEL_REQS_REC.
17-122 68P02901W56-R
Chapter
18
Ladder diagrams
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 18-3
• "Phone call model" on page 18-4
• "Call procedure milestones" on page 18-6
• "Call setup and handover" on page 18-7
• "Connection establishment" on page 18-11
• "Assignment to TCH" on page 18-16
• "Intra-cell handover" on page 18-19
• "Inter-BSS handover" on page 18-23
• "Intra-BSS handover" on page 18-31
• {22879} "Enhanced 2G/3G handover and reselection" on page 18-36
• {22708/23706} "Network assisted cell change" on page 18-39
• "Call clearing" on page 18-42
• "Short message service" on page 18-46
• "Congestion relief" on page 18-48
• "Directed retry" on page 18-50
• "Flow control" on page 18-52
• "Intra-BSS interband activity " on page 18-53
• "Inter-BSS interband activity " on page 18-56
• "Interband assignment" on page 18-60
• "Band Reassignment" on page 18-61
• "RSL link scenarios" on page 18-63
• "MTL link scenarios " on page 18-65
68P02901W56-R 18-1
Chapter 18: Ladder diagrams
• "GBL statistics" on page 18-70
• "Accessibility statistics" on page 18-74
• "Throughput statistics" on page 18-80
• {24349} "Voice Group Call Services" on page 18-88
18-2 68P02901W56-R
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 of the
statistics that may be generated as the result of the process flow is listed on the diagram.
As an example, Figure 18-1 shows the relationships associated with an immediate assignment failure.
Figure 18-1 Diagram of immediate assignment failure
MS BSS MSC
(SEE NOTE)
TIMEOUT
CHAN_REQ_MS_FAIL
68P02901W56-R 18-3
Phone call model Chapter 18: Ladder diagrams
Phone call model

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The GSM phone call model comprises:

• BSS functions
• BSC functions
• MSC functions
• Handover procedure
BSS functions
The GSM BSS is a combination of digital and RF equipment, the purpose of which is to provide the radio
Air interface linking subscribers into the network and providing them with service. The BSS function is to
communicate with the Mobile Switching Centre (MSC), the Operations and Maintenance Centre - 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.
18-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Phone call model
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 18-2 Handover procedure
OMC-R
MSC BSC
INTER-BSS
BSC BSS
BTS
BTS BTS BTS
INTRA-BSS
TDMA FRAMES
BTS
0 1 2 3 4 5 6 7
NOTE: Intra-cell handovers are performed primarily due to poor quality and not to poor level.
0 1 2 3 4 5 6 7
INTRA-CELL
68P02901W56-R 18-5
Call procedure milestones Chapter 18: Ladder diagrams
Call procedure milestones

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
A general description of the milestones in a call procedureis explained in the following paragraphs.
Call procedure
Bids
The first call procedure milestone is a request for service or resource (channel assignment request). At this
point the MS will check the possibility of making a call, 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 a MS which it found to be unusable. The call in progress was not lost but was able
to revert to its previous radio resource.
18-6 68P02901W56-R
Maintenance Information: GSM Statistics Application Call setup and handover
Call setup and handover

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Statistics describe the behaviour 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 18-1.
Each call processing scenario is broken out into six call procedure milestones shown in the vertical columns of
the matrix.
Table 18-1 Call setup and handover statistics matrix.
Milestones
Procedure Failed
Bids Blocked Attempts Success Failed lost
recovered
Immediate OK_ACC_ CHAN_REQ_ see note 3 OK_ACC_ CHAN_REQ_ N/A
Assignment PROC_RACH MS_BLK PROC MS_FAIL
and AL- and AL- CAUSE_IN_RACH
LOC_SD- LOC_SD- see note 5
CCH see CCH_
note 1 FAIL see
note 2
Connection - - CONN_REQ_ - CONN_RE- N/A
Establish- TO_MSC FUSED
ment
Assignment MA_REQ_ MA_CMD_ MA_CMD_ TO- For further MA_FAIL_
to TCH at FROM_MSC TO_MS_ TO_MSC TAL_CALLS study FROM_MS
call set-up BLKDALLOC_ and
TCH_FAIL MA_COM-
PLETE_
TO_MSCALLOC_
TCH
Cont.
68P02901W56-R 18-7
Call setup and handover Chapter 18: Ladder diagrams
Table 18-1 Call setup and handover statistics matrix. (Continued)

Milestones
Procedure Failed
recovered
Handover IN- AL- IN- IN- IN- IN-
Intra-cell TRA_CELL_ LOC_SD- TRA_CELL_ TRA_CELL_ TRA_CELL_ TRA_CELL_
HO_REQ CCH_ HO_ATMPT HO HO_LOSTMS HO_FAIL
FAIL or and and
HO_FAIL_ MA_CMD_ MA_FAIL_
NO_ RE- TO_MS FROM_MS
SOURCES
(IN-
TER_BSS)
or AL-
LOC_TCH_
FAIL
Handover OUT_IN- OUT_IN- OUT_IN- OUT_IN- OUT_IN- OUT_IN-
Intra-BSS TRA_ TRA_ TRA_ TRA_ TRA_ TRA_
(outgoing) BSS_HO_ HO_PRI BSS_HO BSS_HO BSS_HO BSS_HO_
REQ _BLK _ATMPT and _LOSTMS FAIL
or and OUT_HO_
HO_FAIL_ OUT_HO_ NC_SUC
NO_ RE- CAUSE_AT
SOURCES MPT and
(IN- OUT_HO_
TRA_BSS) NC_CAUSE
_ATMPT
Handover OUT_IN- HO_FAIL_ OUT_IN- OUT_IN- OUT_IN- OUT_IN-
Inter-BSS TER_ NO_ RE- TER_ TER_ TER_ TER_
(outgoing) BSS_REQ _ SOURCES BSS_HO BSS_HO BSS_HO BSS_HO
TO_MSC (IN- _ATMPT _SUC _LOSTMS _RETURN
TER_BSS) and
OUT_HO_
CAUSE_AT
MPT and
OUT_HO_
NC_CAUSE
_ATMPT
Cont.
18-8 68P02901W56-R
Maintenance Information: GSM Statistics Application Call setup and handover
Table 18-1 Call setup and handover statistics matrix. (Continued)

Milestones
Procedure Failed
recovered
Handover For further For further IN_INTRA_ IN_INTRA_ IN_INTRA_ IN_INTRA_
Intra-BSS study study AL- BSS_NC_ BSS_HO_SUC BSS_HO_ BSS_HO_
(incoming) LOC_SD- ATMPT and IN_IN- LOSTMS RETURN
CCH_ or AL- TRA_
FAIL or AL- LOC_SD- BSS_NC_SUC
LOC_TCH_ CCH or AL-
FAIL LOC_TCH
Handover For further For further HO_REQ_ IN_INTER_ IN_INTER_ IN_INTER_
Inter-BSS study study see ACK_TO_MSCBSS_HO BSS_HO BSS_HO
(incoming) note 4 AL- AL- [IN_IN- [IN_IN-
LOC_SD- LOC_SD- TER_ TER_
CCH_ CCH BSS_MS_ BSS_MS_
FAIL or AL- or AL- NO_SEIZE] NO_SEIZE]
LOC_TCH_ LOC_TCH
FAIL
68P02901W56-R 18-9
Call setup and handover Chapter 18: Ladder diagrams
Notes
The following notes refer to the call setup and handover matrix:
1. 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.
2. 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.
3. 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_INTER_BSS_HO[OUT_INTER_BSS_HO_LOST_MS])
4. The statistic HO_REQ_MSC_FAIL covers all cases except for blocking (no resources
available).
5. A phantom RACH or badly formed (invalid) channel request was detected, so no resource was
allocated and the call set-up procedure ended.
18-10 68P02901W56-R
Maintenance Information: GSM Statistics Application Connection establishment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-3 to Figure 18-7 show the ladder diagrams for the connection establishment procedures. Figure 18-3
shows that connection establishment is successful after immediate assignment is successful, while Figure 18-7
shows successful mobile-terminated connection establishment.
68P02901W56-R 18-11
Connection establishment Chapter 18: Ladder diagrams
Successful mobile originated
Figure 18-3 shows a successful mobile generated connection establishment.
Figure 18-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
18-12 68P02901W56-R
Failure
Figure 18-4 shows a connection establishment failure.
Figure 18-4 Connection establishment failure
MS BSS MSC
ACCESS_PER_RACH
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
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]
CONNECTION REQUEST
CONN_REQ_TO_MSC
< CREF>
CONN_REFUSED
CONNECTION NOT ESTABLISHED

68P02901W56-R 18-13
Connection establishment Chapter 18: Ladder diagrams
Immediate assignment blocked
Figure 18-5 shows an immediate assignment blocked.
Figure 18-5 Immediate assignment blocked
MS BSS MSC
ACCESS_PER_RACH
MS_ACCESS_BY_TYPE
ACCESS_PER_AGCH
IMMEDIATE ASSIGNMENT REJECT (AGCH)

{ ALLOC_SDCCH_FAIL
and
CHAN_REQ_MS_BLK
Immediate assignment failure
Figure 18-6 shows an immediate assignment failure.
Figure 18-6 Immediate assignment failure
MS BSS MSC

ACCESS_PER_RACH
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
ACCESS_PER_AGCH
TIMEOUT
CHAN_REQ_MS_FAIL
18-14 68P02901W56-R
Successful mobile terminated call
Figure 18-7 shows a successful connection establishment (mobile terminated call).
Figure 18-7 Connection establishment (mobile terminated call) successful
MS BSS MSC
PAGING
PAGE_REQ_FROM_MSC
PAGING REQUEST
ACCESS_PER_PCH
ACCESS_PER_RACH
(PAGING RESPONSE)
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
ACCESS_PER_AGCH
SABMT INITIAL LAYER 3 MESSAGE (SDCCH)
OK_ACC_PROC (PAGING_RESPONSE)
CONNECTION REQUEST
CONN_REQ_TO_MSC
CONNECTION CONFIRM
< CC>
CONNECTION ESTABLISHMENT
(MOBILE TERMINATED)
68P02901W56-R 18-15
Assignment to TCH Chapter 18: Ladder diagrams
Assignment to TCH
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-8 to Figure 18-11 show the ladder diagrams for the assignment to TCH procedures.
Assignment successful
Figure 18-8 shows a successful TCH assignment.
Figure 18-8 TCH assignment successful
MS BSS MSC
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH
ASSIGNMENT COMMAND (SDCCH)
MA_CMD_TO_MS
ASSIGNMENT COMPLETE (TCH)
MA_COMPLETE_FROM_MS
ASSIGNMENT COMPLETE
TOTAL_CALLS
(SEE NOTE 1)
MA_COMPLETE_TO_MSC
MS_TCH_USAGE_BY_TYPE
(SEE NOTE 2)
NOTES:
1. Pegged for the first successful TCH assignment.
2. Pegged to start the length of time spent on TCH by various typesof MS. Will not
be pegged after the TCH is deallocated.
18-16 68P02901W56-R
Maintenance Information: GSM Statistics Application Assignment to TCH
Immediate assignment failure
Figure 18-9 shows an immediate assignment failure.
Figure 18-9 Immediate assignment failure
MS BSS MSC
(SEE NOTE )
NOTE:
RSS Abis does additional filtering of RACH.
TCH assignment blocked
Figure 18-10 shows a TCH assignment blocked.
Figure 18-10 TCH assignment blocked
MS BSS MSC
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
NOTE: NO RADIO TCH AVAILABLE
ALLOC_TCH_FAIL
MA_CMD_TO_MS_BLKD
ASSIGNMENT FAILURE
68P02901W56-R 18-17
Assignment to TCH Chapter 18: Ladder diagrams
Fail recovered
Figure 18-11 shows a TCH assignment fail-recovered to a SDCCH.
Figure 18-11 TCH assignment fail-recovered to SDCCH
MS BSS MSC
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
ASSIGNMENT COMMAND (SDCCH) ALLOC_TCH
MA_CMD_TO_MS
ASSIGNMENT FAILURE (SDCCH)
MA_FAIL_FROM_MS
ASSIGNMENT FAILURE
NOTE: Failure to access Traffic Channel.
18-18 68P02901W56-R
Maintenance Information: GSM Statistics Application Intra-cell handover
Intra-cell handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-12 to Figure 18-15 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 18-12 shows a successful intra-cell handover.
Figure 18-12 Handover (intra-cell) successful
68P02901W56-R 18-19
Intra-cell handover Chapter 18: Ladder diagrams
Handover blocked
Figure 18-13 shows an intra-cell handover blocked.
Figure 18-13 Handover (intra-cell) blocked
MS BSS MS
(SOURCE CHANNEL) (TARGET CHANNEL)
INTER_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE)
(INTRA_CELL_HO)
ALLOC_TCH_FAIL
NOTE: Need for handover is recognized within the BSS.
18-20 68P02901W56-R
Maintenance Information: GSM Statistics Application Intra-cell handover
Fail recovered
Figure 18-14 shows an intra-cell handover fail-recovered to a source channel.
Figure 18-14 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).
68P02901W56-R 18-21
Intra-cell handover Chapter 18: Ladder diagrams
Fail lost
Figure 18-15 shows an intra-cell handover fail-lost.
Figure 18-15 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).
18-22 68P02901W56-R
Maintenance Information: GSM Statistics Application Inter-BSS handover
Inter-BSS handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-16 to Figure 18-19 show the ladder diagrams for the inter-BSS handover procedure.
Handover successful
Figure 18-16 shows a successful inter-BSS handover.
Figure 18-16 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
OUT_HO_NC_ HANDOVER
CAUSE_ATMPT COMPLETE
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.
68P02901W56-R 18-23
Inter-BSS handover Chapter 18: Ladder diagrams
Handover blocked
Figure 18-17 shows an inter-BSS handover blocked.
Figure 18-17 Handover (inter-BSS) blocked
MS
(SOURCE MS (TARGET
CHANNEL BSS CHANNEL
SOURCE CELL) BSS MSC
(SOURCE) (TARGET) TARGET CELL)
HANDOVER HANDOVER
REQUIRED REQUEST
(SEE NOTE 1) HO_REQ_FROM_MSC
OUT_INTER_BSS_HO ALLOC_TCH_FAIL
(OUT_INTER_BSS_
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.
18-24 68P02901W56-R
Fail recovered
Figure 18-18 shows an inter-BSS handover fail-recovered.
Figure 18-18 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_ or ALLOC_SDCCH
TO_MSC) HANDOVER REQUEST
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.
68P02901W56-R 18-25
Fail lost
Figure 18-19 shows an inter-BSS handover fail-lost.
Figure 18-19 Handover (inter-BSS) fail-lost
MS
(SOURCE MS (TARGET
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.
18-26 68P02901W56-R
Fail lost (mobile)
Figure 18-20 shows an inter-BSS handover failure with lost mobile.
68P02901W56-R 18-27
Figure 18-20 Inter-BSS handover failure with lost mobile
MS
(SOURCE MS (TARGET
HANDOVER REQUIRED
HANDOVER
(SEE NOTE 1) REQUEST
OUT_INTER_BSS_HO HO_REQ_FROM_MSC
(OUT_INTER_BSS_REQ ALLOC_TCH or
_TO_MSC ALLOC_SDCCH
HANDOVER HO_REQ_ACK_TO_MSC
HANDOVER REQUEST
COMMAND ACKNOWLEDGE (SEE NOTE 2)
HANDOVER
COMMAND
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_
ATMPT
TIMEOUT
(SEE
NOTE 3)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
LOSTMS)
CLEAR REQUEST
CLR_REQ_TO_MSC
CLEAR
COMMAND
IN_INTER_BSS_HO
CLEAR (IN_INTER_BSS_MS_
COMPLETE NO_SEIZE)
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. TIMEOUT can occur at source BSS, target BSS, or switch first depending on system timer settings.
18-28 68P02901W56-R
Standard directed retry (external)
Figure 18-21 shows an inter-BSS handover directed retry external.
68P02901W56-R 18-29
Figure 18-21 Inter-BSS handover directed retry external
MS MS (TARGET
(SOURCE CHANNEL BSS BSS CHANNEL
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
CALLS_QUEUED
TCH_Q_LENGTH
QUEUEING INDICATION
(SEE NOTE 1)
ASSIGNMENT FAILURE
CAUSE DIRECTED RETRY
(SEE NOTE 2)
HANDOVER
HANDOVER REQUIRED REQUEST
(SEE NOTE 3) HO_REQ_FROM_MSC
ALLOC_TCH
HANDOVER REQUEST or ALLOC_SDCCH
ACKNOWLEDGE
HANDOVER HO_REQ_ACK_TO_
COMMAND MSC
COMMAND CONGEST_STAND_
HO_ATMPT HANDOVER
OUT_INTER_BSS_HO COMPLETE
(OUT_INTER_BSS_HO_
ATMPT)
IN_INTER_BSS_HO
OUT_HO_CAUSE_ATMPT (IN_INTER_BSS_HO
HANDOVER
(CONGESTION) _SUC)
COMPLETE
OUT_HO_NC_CAUSE_
ATMPT (CONGESTION)
CLEAR COMMAND
ASSIGNMENT_REDI
RECTION
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
HO_SUC)
OUT_HO_NC_SUC
NOTES:
1. Only if queueing is enabled for the cell
2. The necessity in sending this message must align with MSC expectation and is controlled through the
database. Message may be sent after handover required message as controlled by the database.
3. The cause field in this message (either directed retry or handover cause) must align with MSC
expectation and is controlled through the database.
18-30 68P02901W56-R
Maintenance Information: GSM Statistics Application Intra-BSS handover
Intra-BSS handover
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-22 to Figure 18-25 show the ladder diagrams for the intra-BSS handover procedure.
Handover successful
Figure 18-22 shows a successful intra-BSS handover.
Figure 18-22 Handover (intra-BSS) successful
68P02901W56-R 18-31
Intra-BSS handover Chapter 18: Ladder diagrams
Handover- blocked
Figure 18-23 shows an intra-BSS handover-blocked.
Figure 18-23 Handover (intra-BSS) blocked
MS MS (TARGET CHANNEL
(SOURCE CHANNEL BSS TARGET CELL)
SOURCE CELL)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ)
(SEE NOTE 1)
ALLOC_TCH_FAIL or ALLOC_SDCCH_FAIL
HO_FAIL_NO_RESOURCES (INTRA_BSS_HO)
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_PRI_BLK)
(SEE NOTE 2)
NOTES:
1. Need for handover is recognized within the BSS, but no radio channel is available in primary target cell.
2. Handover target cell list should contain at least two cells in order to peg this statistic. if there
is only 1 cell, the statistic will not be pegged.
18-32 68P02901W56-R
Fail-recovered
Figure 18-24 shows an intra-BSS handover fail-recovered.
Figure 18-24 Handover (intra-BSS) fail-recovered
MS
(SOURCE CHANNEL BSS MS (TARGET CHANNEL
OUT_INTRA_BSS_HO
(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.
68P02901W56-R 18-33
Intra-BSS handover Chapter 18: Ladder diagrams
Fail-lost
Figure 18-25 shows an intra-BSS handover fail-lost.
Figure 18-25 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.
18-34 68P02901W56-R
Standard directed retry (internal)
Figure 18-26 displays the ladder diagram for intra-BSS handover standard directed retry.
Figure 18-26 Intra-BSS handover standard directed retry
68P02901W56-R 18-35
Enhanced 2G/3G handover and reselection Chapter 18: Ladder diagrams
Enhanced 2G/3G handover and reselection

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22879}
Figure 18-27 and Figure 18-28 show the ladder diagrams for enhanced 2G/3G handover and cell reselection
procedures.
2G/3G handover successful
Figure 18-27 shows a successful 2G/3G handover scenario.
18-36 68P02901W56-R
Maintenance Information: GSM Statistics Application Enhanced 2G/3G handover and reselection
Figure 18-27 2G/3G handover successful
CN Multi-RAT
RNS MSC BSS
(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
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
OUT_HO_NC_SUC
CLEAR COMPLETE
BSSMAP BSSMAP
SEND END
SIGNAL RESPONSE
MAP/E MAP/E
ti-GSM-Stats-2G 3G handover succ-eps-sw
68P02901W56-R 18-37
Enhanced 2G/3G handover and reselection Chapter 18: Ladder diagrams
2G/3G handover failure
Figure 18-28 shows a 2G/3G handover failure scenario.
Figure 18-28 2G/3G handover failure
CN Multi-RAT
RNS MSC BSS
(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
INTER SYSTEM TO UTRAN

HANDOVER COMMAND
RR RR
HANDOVER FAILURE
(SEE NOTE)
RR RR
HANDOVER FAILURE
BSSMAP BSSMAP
NOTE: The number of attempted handovers from a 2G network to a 3G cell that failed is calculated by the NUM_HO_TO_3G_FAIL statistic.
ti-GSM-Stats-2G 3G handover fail-eps-sw
18-38 68P02901W56-R
Maintenance Information: GSM Statistics Application Network assisted cell change
Network assisted cell change

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{22708/23706}
Figure 18-29 to Figure 18-33 show the ladder diagrams for network assisted cell change procedures.
NACC cell selection agreement
Figure 18-29 shows the scenario where the network agrees with the MS target cell reselection.
Figure 18-29 Cell selection agreement
BSS MS
PCCN
PNCD
PCCC
ti-GSM-Stats-MS target agree NACC-eps-sw
68P02901W56-R 18-39
Network assisted cell change Chapter 18: Ladder diagrams
No target cell information before sending a PCCC
Figure 18-30 shows the scenario where the network has no target cell information before sending a PCCC.
Figure 18-30 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 18-31 shows the scenario where the network evaluates a new target cell for the MS.
Figure 18-31 New target cell for the MS
BSS MS
PCCN
PNCD
PCCO
NUM_CELL_RESEL_CELL
ti-GSM-Stats-MS target eval NACC-eps-sw
18-40 68P02901W56-R
Maintenance Information: GSM Statistics Application Network assisted cell change
No target cell information before sending a PCCO
Figure 18-32 shows the scenario where the network has no target cell information before sending a PCCO.
Figure 18-32 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 18-33 shows the scenario where the network evaluates that reselection is not required for the MS.
Figure 18-33 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
68P02901W56-R 18-41
Call clearing Chapter 18: Ladder diagrams
Call clearing
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-34 to Figure 18-37 show the ladder diagrams for the call clearing procedures.
Cipher mode fail
Figure 18-34 shows BSS initiated call clearing - cipher mode fail.
Figure 18-34 BSS initiated call clearing-cipher mode fail
MS BSS MSC
CIPHERING MODE COMMAND
TIMEOUT
CIPHER_MODE_FAIL
CLEAR REQUEST
CLR_REQ_TO_MSC
18-42 68P02901W56-R
Maintenance Information: GSM Statistics Application Call clearing
RF loss on an SDCCH
Figure 18-35 shows BSS initiated call clearing (RF loss on an SDCCH).
Figure 18-35 BSS initiated call clearing (RF loss on an SDCCH)
MS BSS MSC
MEASUREMENT REPORT (SACCH)


(SEE NOTES 1 AND 2)
TIMEOUT RF_LOSSES_SD
CLEAR REQUEST
CLR_REQ_TO_MSC
NOTES:
1. MS has established on SDCCH, for example, after immediate assignment successful.
2. Message sent on SACCH every 480 milliseconds.
68P02901W56-R 18-43
Call clearing Chapter 18: Ladder diagrams
RF loss on a TCH
Figure 18-36 shows BSS initiated call clearing - RF loss on a TCH.
Figure 18-36 BSS initiated call clearing (RF loss on a TCH)
MS BSS MSC

(SEE NOTES 1 AND 2)
TIMEOUT RF_LOSSES_TCH
CLEAR REQUEST
CLR_REQ_TO_MSC
NOTES:
1. MS has established on TCH, for example, after assignment successful.
2. Message sent on SACCH every 480 milliseconds.
18-44 68P02901W56-R
Maintenance Information: GSM Statistics Application Call clearing
Queueing timeout
Figure 18-37 shows BSS initiated call clearing (queueing timeout).
Figure 18-37 BSS initiated call clearing (queueing timeout)
MS BSS MSC
CALLS QUEUED
QUEUEING INDICATION (SEE NOTE)
TIMEOUT
CLEAR REQUEST
CLR_REQ_TO_MSC
NOTE: TCH assignment attempted, no resources available, and queueing enabled.
68P02901W56-R 18-45
Short message service Chapter 18: Ladder diagrams
Short message service

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-38 and Figure 18-39 show the ladder diagrams for the short message service procedures.
Mobile originated
Figure 18-38 shows MS originated short message service (point-to-point).
Figure 18-38 MS originated short message service (point-to-point)
MSC BSS MS
SAPI 3 REQUEST
ACKNOWLEDGEMENT
SMS_INIT_ON_SDCCH
or
SMS_INIT_ON_TCH
SMS MESSAGE SMS MESSAGE
NOTES:
1. A SAPI 0 mode must exist before the SAPI 3 can be established.
2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCH
and SMS_INIT_ON_TCH is pegged if the MS is on a TCH.
18-46 68P02901W56-R
Maintenance Information: GSM Statistics Application Short message service
Mobile terminated
Figure 18-39 shows mobile terminated short message service (point-to-point).
Figure 18-39 MS terminated short message service (point-to-point)
MSC BSS MS
SMS MESSAGE
SAPI 3 REQUEST
ACKNOWLEDGEMENT
SMS_INIT_ON_SDCCH
or
SMS_INIT_ON_TCH
SMS MESSAGE
NOTES:
1. A SAPI 0 mode must exist before the SAPI 3 can be established.
2. SMS_INIT_ON_SDCCH is pegged if the MS is on an SDCCH
and SMS_INIT_ON_TCH is pegged if the MS is on a TCH.
68P02901W56-R 18-47
Congestion relief Chapter 18: Ladder diagrams
Congestion relief
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Intra-BSS congestion relief example
Figure 18-40 shows the 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.
18-48 68P02901W56-R
Maintenance Information: GSM Statistics Application Congestion relief
Figure 18-40 Intra-BSS congestion relief handover procedure
68P02901W56-R 18-49
Directed retry Chapter 18: Ladder diagrams
Directed retry
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Intra-BSS directed retry example
Figure 18-41 shows an example of the relationships associated with an intra-BSS directed retry procedure.
18-50 68P02901W56-R
Maintenance Information: GSM Statistics Application Directed retry
Figure 18-41 Intra-BSS directed retry procedure
68P02901W56-R 18-51
Flow control Chapter 18: Ladder diagrams
Flow control
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
FLOW_CONTROL_BARRED measures the duration for which access classes are barred as a result of flow
control. The statistic duration will be 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 18-42 shows an example of the relationships associated with an access procedure.
Figure 18-42 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.
18-52 68P02901W56-R
Maintenance Information: GSM Statistics Application Intra-BSS interband activity
Intra-BSS interband activity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-43 to Figure 18-45 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.
Handover successful
Figure 18-43 shows an established call on TCH with a subsequent successful intra-BSS handover to a
PGSM cell.
Figure 18-43 Successful intra-BSS handover

MS BSS MS (TARGET
OUT_INTRA_BSS_HO
ALLOC_TCH (TARGET CELL)
MS_ACCESS_BY_TYPE (TARGET CELL)

(SEE NOTE 1)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_ATMPT)
OUT_HO_CAUSE_ATMPT
(BAND_HANDOVER) (SEE NOTE 2)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT) (SEE NOTE 3)
HANDOVER
COMPLETE
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_SUC)
OUT_HO_NC_SUC
NOTES:
1. MS_ACCESS_BY_TYPE will peg the bin that matches the MS capability
2. Handover cause band handover for statistics OUT_HO_CAUSE_ATMPT an OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-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.
3. 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:
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
68P02901W56-R 18-53
Intra-BSS interband activity Chapter 18: Ladder diagrams
Handover unsuccessful (fail recovered)
Figure 18-44 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 18-44 Unsuccessful interband handover with fail-recovered source cell
MS MS (TARGET
BSS
OUT_INTRA_BSS_HO

(SEE NOTE 1)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT) (SEE NOTE 3)
HANDOVER
FAILURE
OUT_INTRA_BSS_HO
INTERBAND_ACTIVITY
(PGSM_HO_FAIL)
NOTES:
2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-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.
example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY
will peg different bins:
for DCS1800 target cells, bins DCS1800_HO_ATMPT & DCS1800_HO_FAIL peg
for PCS1900 target cells, bins PCS1900_HO_ATMPT & PCS1900_HO_FAIL peg
for EGSM target cells, bins EGSM_HO_ATMPT & EGSM_HO_FAIL peg
18-54 68P02901W56-R
Maintenance Information: GSM Statistics Application Intra-BSS interband activity
Handover unsuccessful (fail recovered due to invalid frequency

supported)
Figure 18-45 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 18-45 Unsuccessful interband handover
MS MS (TARGET
(SOURCE CHANNEL BSS CHANNEL
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ) (SOURCE CELL)

(SEE NOTE 1)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT)
HANDOVER FAILURE
REASON- FREQUENCY OUT_INTRA_BSS_HO
NOT IMPLEMENTED
INTERBAND_ACTIVITY
(PGSM_HO_FAIL) (SEE NOTE 3)
INTERBAND_ACTIVITY
(INVALID_FREQ_HO)
NOTES:
2. Handover cause band handover statistics OUT_HO_CAUSE_ATMPT and OUT_HO_NC_CAUSE_ATMPT
is just one possible valid cause for the intra-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.
example, the above ladder diagram applies for other frequency bands, except that INTERBAND_ACTIVITY
will peg different bins:
for DCS1800 target cells, bins DCS1800_HO_ATMPT & DCS1800_HO_FAIL peg
for PCS1900 target cells, bins PCS1900_HO_ATMPT & PCS1900_HO_FAIL peg
for EGSM target cells, bins EGSM_HO_ATMPT & EGSM_HO_FAIL peg
68P02901W56-R 18-55
Inter-BSS interband activity Chapter 18: Ladder diagrams
Inter-BSS interband activity

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Figure 18-46 to Figure 18-48 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.
Handover successful
Figure 18-46 shows an established call on TCH with a subsequent successful inter-BSS handover to a
PGSM cell.
18-56 68P02901W56-R
Maintenance Information: GSM Statistics Application Inter-BSS interband activity
Figure 18-46 Successful inter-BSS handover
MS (SOURCE BSS MS (TARGET

MSC BSS
CHANNEL (SOURCE) (TARGET) CHANNEL
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
(SEE NOTE 2)
ACKNOWLEDGE
HANDOVER
COMMAND
HANDOVER
COMMAND OUT_INTER_BSS_HO HO_REQ_ACK_TO_MSC
(SEE NOTE 3)
(OUT_INTER_BSS_HO_
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
68P02901W56-R 18-57
Inter-BSS interband activity Chapter 18: Ladder diagrams
Figure 18-47 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 18-47 Inter-BSS handover unsuccessful with fail-recovered source cell
MS (SOURCE BSS MSC BSS MS (TARGET

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)
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
18-58 68P02901W56-R
Maintenance Information: GSM Statistics Application Inter-BSS interband activity
Handover unsuccessful fail recovered due to invalid frequency

supported
Figure 18-48 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 18-48 Inter-BSS handover unsuccessful due to invalid frequency supported
MS (SOURCE BSS MSC BSS MS (TARGET

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
(PGSM_HO_ATMPT)
HANDOVER
(SEE NOTE 5)
FAILURE
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
68P02901W56-R 18-59
Interband assignment Chapter 18: Ladder diagrams
Interband assignment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Interband activity invalid frequency at assignment
Figure 18-49 shows an invalid frequency at assignment.
Figure 18-49 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.
18-60 68P02901W56-R
Maintenance Information: GSM Statistics Application Band Reassignment
Band Reassignment
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 18-50 and Figure 18-51 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 18-50 shows an intra-BSS handover attempt of a 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 mobile.
Figure 18-50 Intra-BSS handover successful
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO

(MS_PGSM_DCS1800)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT)
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
68P02901W56-R 18-61
Band Reassignment Chapter 18: Ladder diagrams
Figure 18-51 shows an unsuccessful band reassign.
Figure 18-51 Unsuccessful band reassign
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO

(MS_PGSM_DCS1800)
HANDOVER
COMMAND OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_ATMPT)
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)
18-62 68P02901W56-R
Maintenance Information: GSM Statistics Application RSL link scenarios
RSL link scenarios

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction
Figure 18-52 shows a ladder diagram scenario for the Radio Signalling Link (RSL) link.
68P02901W56-R 18-63
RSL link scenarios Chapter 18: Ladder diagrams
Figure 18-52 RSL link scenarios
STEP 1:
lock of RSL
lock of associated MSI
lock of associated MMS
front panel reset
MSI board physically removed
transmit and or receive path terminated
RSL LINK
SABM_TX (note 1)
STEP 2 : N2_EXPIRY (note 2)
unlock of RSL
unlock of associated MSI
unlock of associated MMS
front panel reset
MSI physically returned
transmit and or receive path fully restored
RSL LINK
(RSL restoral)
NOTES :
1. SABM_TX will periodically repeat in attempt to restore the RSL connection.
2. N2_EXPIRY may peg depending on the outage. The period this statistic is
updated is dependent on the RSL attributes lapd_n200 and lapd_t200
timer, which get set during the equip of the RSL.
3. If the last RSL to a site goes OOS, then all call processing at the site will
cease as all cells at the site will be barred.
18-64 68P02901W56-R
Maintenance Information: GSM Statistics Application MTL link scenarios
MTL link scenarios

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to MTL link scenarios
Figure 18-53 to Figure 18-56 show four ladder diagrams as scenarios for the Message Transfer Link (MTL)
link.
68P02901W56-R 18-65
MTL link scenarios Chapter 18: Ladder diagrams
MTL link (operator initiated outage)
Figure 18-53 MTL link scenario (Part I)
STEP 1:
lock of MTL
lock of associated MSI/XCDR
lock of associated MMS
front panel reset MTL LINK
MSI/XCDR board physically removed
MTP_UNAVAILABLE timer
started
MTP_LINK_INS timer
stopped
STEP 2:
unlock of MTL
unlock of associated MSI/XCDR
unlock of associated MMS
front panel restore
MTL LINK
MSI/XCDR board physically returned
MTP_RESTORATION
incremented
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
NOTES:
1. Lock of MTL or associated device transitions operator and admin states from
B-U to D-L
2. Unlock of MTL or associated device transitions operator and admin states from
D-L to B-U.
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.NOTE
18-66 68P02901W56-R
MTL link (transition scenarios Part II)
Figure 18-54 shows an MTL transition from B-U to E-U and E-U to B-U with reason Wait.
Figure 18-54 MTL link transition scenarios (Part II)
STEP 1:
(MTL transitions from B-U to E-U with reason Wait)
MTL LINK
MTP_SL_FAIL incremented
MTP_UNAVAILABLE
timer started
MTP_LINK_INS timer
stopped
MTP_LINKFAIL timer
started
MTP_LINK_INS timer
stopped
MTP_SL_ALIGNMENT
incremented
STEP 2:
(MTL transitions from E-U with
reason Wait to B-U
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
68P02901W56-R 18-67
MTL link scenarios Chapter 18: Ladder diagrams
MTL link (transition scenarios Part III)
Figure 18-55 shows an MTL transition from B-U to D-U and D-U to B-U with reason Wait MMS not
in service.
Figure 18-55 MTL link transition scenarios (Part III)
STEP 1:
(MTL transitions from B-U to D-U with reason Wait MMS not in service)
MTL LINK
MTP_UNAVAILABLE
timer started
MTP_LINKFAIL timer
started
MTP_LNK_INS timer
started
STEP 2:
(MTL transitions from D-U with reason Wait MMS not in service
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
18-68 68P02901W56-R
MTL link (transition scenarios Part IV)
Figure 18-56 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 18-56 MTL link transition scenarios (Part IV)
STEP 1:
(MTL transitions from B-U to E-U with reason Wait, with improper
timeslot mapping between BSC and MSC)
MTL LINK
MTP_UNAVAILABLE
timer started
MTP_LINKFAIL timer
started
MTP_LNK_INS timer
started
MTP_LINK_INS timer
stopped
MTP_SL_ERROR_RATE
incremented
MTP_SL_ALIGNMENT incremented
(periodically repeats)
STEP 2:
(MTL transitions from E-U with reason Wait to B-U with improper
timeslot mapping between BSC and MSC
MTL LINK
MTP_RESTORATION
incremented
MTP_LINKFAIL
timer stopped
MTP_UNAVAILABLE
timer stopped
MTP_LINK_INS timer
started
68P02901W56-R 18-69
GBL statistics Chapter 18: Ladder diagrams
GBL statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to GBL statistics
Figure 18-57 to Figure 18-61 show how the GBL statistics function within the BSS/PCU.
GBL_DL_DATA_THRPUT
Figure 18-57 shows GBL_DL_DATA_THRPUT.
Figure 18-57 GBL_DL_DATA_THRPUT
DLCI = 45 DLCI = 45
DLCI = 55
Bearer chan 1
DLCI = 55
18-70 68P02901W56-R
Maintenance Information: GSM Statistics Application GBL statistics
GBL_FLOW_CTRL_SENT
Figure 18-58 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 18-58 GBL_FLOW_CTRL_SENT
BSS/PCU SGSN
BSSGP FLOW CONTROL PDU
GBL_FLOW_CTRL_SENT
BSSGP FLOW CONTROL ACK PDU
CELL_FLUSH_REQS
Figure 18-59 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 18-59 CELL_FLUSH_REQS
SGSN GB FU PS
FLUSH PDU FLUSH PDU
CELL_FLUSH_REQS
68P02901W56-R 18-71
GBL statistics Chapter 18: Ladder diagrams
GBL_PAGING_REQS
Figure 18-60 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 18-60 GBL_PAGING_REQS
SGSN BSS/PCU
MS
BSSGP PS PDU
GBL_PAGING_REQS
PACKET PAGING REQEST (PCH)
Channel Request (RACH)
Immediate Assignment (GCH)
18-72 68P02901W56-R
Maintenance Information: GSM Statistics Application GBL statistics
GBL_UL_DATA_THRPUT
Figure 18-61 illustrates the statistic GBL_UL_DATA_THRPUT.
Figure 18-61 GBL_UL_DATA_THRPUT
DLCI = 45 DLCI = 45
Bearer chan 1
DLCI = 55 DLCI = 55
68P02901W56-R 18-73
Accessibility statistics Chapter 18: Ladder diagrams
Accessibility statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to accessibility statistics
Figure 18-62 through Figure 18-67 illustrate accessibility statistics.
CHANNEL_REQS_REC
Figure 18-62 illustrates the ladder diagram for CHANNEL_REQS_REC.
Figure 18-62 CHANNEL_REQS_REC
BSS / PCU MS
Channel request (RACH, PRACH or PDAK)
CHANNEL_REQS_REC
18-74 68P02901W56-R
Maintenance Information: GSM Statistics Application Accessibility statistics
CHANNEL_REQS_REJ
Figure 18-63 is a ladder diagram detailing the statistic CHANNEL_REQS_REJ when it is pegged. It also
shows the request and the response messages sent from the BSS/PCU to the mobile station.
Figure 18-63 Accessibility CHANNEL_REQ_REJ
BSS/PCU MS
Immediate Assignment (AGCH)
Packet Resource Request
CHANNEL_REQ_REJECT
PACKET ACCESS REJECT
68P02901W56-R 18-75
Figure 18-64 illustrates the ladder diagram for CHANNEL_REQS_SUCCESS.
Figure 18-64 CHANNEL_REQS_SUCCESS
BSS / PCU MS
Channel Request (RACH, PRACH or PDAK)
UL TBF Assignment
18-76 68P02901W56-R
Channel request (RACH) and immediate assignment (AGCH)

Figure 18-65 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 mobile station.
Figure 18-65 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH
BSS/PCU MS
68P02901W56-R 18-77
Accessibility and GBL statistics

Figure 18-66 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 18-66 Accessibility and GBL statistics
SGSN BSS/PCU MS
BSSGP PS PDU
GBL_PAGING_REQS
PACKET PAGING REQEST (PCH)
18-78 68P02901W56-R
GPRS_CHANNELS_SWITCHED
Figure 18-67 details the GPRS_CHANNELS_SWITCHED statistic.
Figure 18-67 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
68P02901W56-R 18-79
Throughput statistics Chapter 18: Ladder diagrams
Throughput statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Introduction to throughput statistics
Figure 18-68 through Figure 18-74 show throughput statistics diagrams.
18-80 68P02901W56-R
Maintenance Information: GSM Statistics Application Throughput statistics
AIR_DL_TBF_FAILURES
Figure 18-68 and Figure 18-69 illustrate ladder diagrams for AIR_DL_TBF_FAILURES termination and
data transfer DDTR mode establishment respectively.
Figure 18-68 AIR_DL_TBF_FAILURES termination
MS PCU
RLC-Data block
FBI = 0 N3101 ++
RLC-Data block
FBI = 1 T3191
No Acknowledgment
RLC-Data block
FBI = 1
RLC-Data block
FBI = 1
Expires
AIR_DL_TBF_FAILURE
Termination
68P02901W56-R 18-81
Figure 18-69 AIR_DL_TBF_FAILURES data transfer DDTR mode establishment
MS PCU
RLC-Data block
w/o polling
RLC-Data block
polling
No Response
N3105 ++
RLC-Data block
N3105 + +
polling
= N3105 max
RLC-Data block
polling T3195 = 5 sec.
Expires
AIR_DL_TBF_FAILURE
Establishment - when first ACK is missing

Data transfer - ongoing TBF
DDTR mode - PCU currently
sends downlink dummy data blocks
(super-coattail) blocks
18-82 68P02901W56-R
AIR_UL_TBF_FAILURES
Figure 18-70 and Figure 18-71 illustrate ladder diagrams for AIR_UL_TBF_FAILURES
establishment/termination and data transfer respectively.
Figure 18-70 AIR_UL_TBF_FAILURE establishment and termination
MS PCU MS PCU
IMM_ASS_CMD RLC_Data_Blk
T3141 CV = 0
PACK_UL_ACK N3103 = 0
No Data PACK_CTRL_ACK
PACK_UL_ACK N3103 + +
PACK_CTRL_ACK
PACK_UL_ACK N3103 + +
=N3103max
Expires
T3169
AIR_UL_TBF_FAILURE
Establishment
Expires
AIR_UL_TBF_FAILURE
Termination
68P02901W56-R 18-83
Figure 18-71 AIR_UL_TBF_FAILURE data transfer
MS PCU
USF_Allocation
N3101 ++
No Data
USF Allocation
N3101 + +
USF Allocation N3101 + +

=N3101max
T3169
Expires
AIR_UL_TBF_FAILURE
Data Transfer
18-84 68P02901W56-R
DL_PDTCH_SEIZURE
Figure 18-72 illustrates the ladder diagram for DL_PDTCH_SEIZURE.
Figure 18-72 DL_PDTCH_SEIZURE
Establishment Mode
PDA
Data
Data w/pol
l
AK
First D
DL PDTCH SEIZURE
Transfer Mode
CIA Block
w/poll
CIA DAK
Delayed TBF
Release Mode
Transfer Mode Data

CIA Block
w/poll
K
CIA DA
Delayed TBF
Release Mode
Termination Mode Final Bloc

k w/poll
AK
Final D
68P02901W56-R 18-85
UL_PDTCH_SEIZURE
Figure 18-73 and Figure 18-74 illustrate ladder diagrams for UL_PDTCH_SEIZURE one-phase and
two-phase access respectively.
Figure 18-73 UL_PDTCH_SEIZURE one-phase access
Immediate
Establishment Mode Assignmen
t
Data
UL PDTCH SEIZURE
Transfer Mode UAK
lock
CV=0 B
Termination Mode Final UAK
CA
18-86 68P02901W56-R
Figure 18-74 UL_PDTCH_SEIZURE two-phase access
Establishment Mode PUA
Data
UL PDTCH SEIZURE
Transfer Mode UAK
lock
CV=0 B
Termination Mode
Final UAK
CA
68P02901W56-R 18-87
Voice Group Call Services Chapter 18: Ladder diagrams

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
{24349}
Figure 18-75 to Figure 18-88 show the ladder diagrams for the Voice Group Call Service (VGCS) procedures.
Immediate channel assignment (service subscriber)
Figure 18-75 shows a service subscriber initiating a VGC establishment successfully resulting in immediate
channel assignment.
18-88 68P02901W56-R
Maintenance Information: GSM Statistics Application Voice Group Call Services
Figure 18-75 Immediate channel assignment (service subscriber)
CS-MS DS-MSs BSS MSC
Stage 1: MS originated connection estblishment

Channel request
(SEE NOTE 1)
ACCESS_PER_RACH
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
ACCESS_PER_AGCH
Immediate assignment
SABM (CM Service Request (CM service type = VGC establishment) or

Immediate setup or Immediate setup 2) (SEE NOTE 2) OK_ACC_PROC[CM_SERV_REQ_VGCS]
- or -
OK_ACC_PROC[CM_SERV_REQ_VBS]
- or -
OK_ACC_PROC[IMM_SETUP]
- or -
OK_ACC_PROC[IMM_SETUP2]
- or -
OK_ACC_PROC[NOTIF_RESP]
UA (CM Service Request or Immediate setup or Immediate setup 2)
(SEE NOTE 3)
CR (Complete Layer 3 Information)
CONN_REQ_TO_MSC
CC
DTAP GCC Setup
Stage 2: VGC Channel establishment
CR
CC
Setup CC-SCCP - one for each
VGCS call in each BSS (SEE NOTE 4)
VGCS/VBS Setup
VGCS_VBS_SETUP
VGCS/VBS Setup Ack.

VGCS_VBS_SETUP_ACK
CR
CC
Setup RC-SCCP - one for each
cell in each VGC (SEE NOTE 5)
VGCS_ASSIGN_RESULT
Request (channel assigned

immediately)
VGCS_VBS_ASSIGN_REQ
VGCS/VBS Assignment
Result (with Chosen channel)
VGCS_ASSIGN_RESULT
TCH_FR_TCH_BUSY or
TCH_HR_TCH_BUSY
TCH_Q_REMOVED
NCH: Notification/NCH with VGC Channel Description)
V FACCH:
- Notification/FACCH with VGC Channel Description)
V-SACCH: System Information

V-FACCH: Uplink Busy
DTAP GCC Connect
NOTE 1: RSS ABIS does additional filtering of RACH.

NOTE 2: CM Service Request (CM service type = VGC establishment or
Immediate Setup or Immediate Setup 2).
NOTE 3: CM Service Request or Immediate Setup or Immediate Setup 2.
NOTE 4: Setup CC-SCCP - one for each VGCS call in each BSS.
NOTE 5: Setup RC-SCCP - one for each cell in each VGC.
ti-GSM-Stats-SS success imm VGCS-eps-sw.eps
68P02901W56-R 18-89
Immediate channel assignment (dispatcher)
Figure 18-76 shows a dispatcher initiating a VGC establishment successfully resulting in immediate channel
assignment.
Figure 18-76 Immediate channel assignment (dispatcher)
DS-MSs BSS MSC

CR
CC
VGCS/VBS Setup
VGCS_VBS_SETUP
VGCS/VBS Setup Ack.

VGCS_VBS_SETUP_ACK
Uplink Release Command
CR
CC

Allocate resource for immediately)
VGC channel
VGCS_VBS_ASSIGN_REQ
VGCS/VBS Assignment
VGCS_ASSIGN_RESULT
VGCS_FR_TCH_BUSY or
VGCS_HR_TCH_BUSY
TCH_Q_REMOVED

V FACCH:
- Notification/FACCH with VGC Channel Description)
V-SACCH: System Information

V-FACCH: Uplink Free
NOTE 2: Setup RC-SCCP - one for each cell in each VGC. ti-GSM-Stats-Disp success imm VGCS-eps-sw.eps
18-90 68P02901W56-R
Delayed channel assignment (dispatcher)
Figure 18-77 shows a dispatcher initiating a VGC establishment successfully resulting in a delayed channel
assignment.
Figure 18-77 Delayed channel assignment (dispatcher)
DS-MSs BSS MSC

CR
CC
VGCS/VBS Setup
VGCS_VBS_SETUP
VGCS/VBS Setup Ack.

VGCS_VBS_SETUP_ACK
CR
CC

No allocation of resource for immediately)
VGC channel
VGCS_VBS_ASSIGN_REQ
VGCS/VBS Assignment
VGCS_ASSIGN_RESULT
VGCS_FR_TCH_BUSY or
VGCS_HR_TCH_BUSY
TCH_Q_REMOVED

V-FACCH: Notification/FACCH with VGC Channel Description)
NOTE 2: Setup RC-SCCP - one for each cell in each VGC.
ti-GSM-Stats-Disp success delay VGCS-eps-sw.eps
68P02901W56-R 18-91
Dedicated channel allocation for calling service subscriber
Figure 18-78 shows dedicated channel allocation for a calling service subscriber.
Figure 18-78 Dedicated channel allocation for calling service subscriber
CS-MS DS-MSs BSS MSC

Assignment Request with Talker
Flag and Group Call reference
Assignment command
Assignment complete
TCH_Q_REMOVED
[ASSIGNMENT_RESOURCE_REQ]
or
Channel mode modify
Channel mode modify acknowledge
Assignment Complete
ti-GSM-Stats-SS DCA VGCS-eps-sw.eps
18-92 68P02901W56-R
Unsuccessful VGCS setup at the BSS
Figure 18-79 shows an unsuccessful VGCS setup at the BSS.
Figure 18-79 Unsuccessful VGCS setup at the BSS
BSS MSC
CR
CC
VGCS call
VGCS/VBS Setup
VGCS_VBS_SETUP
VGCS/VBS Setup Refuse
VGCS_VBS_SETUP_REFUSE
ti-GSM-Stats-Unsucc VGCS setup-eps-sw.
68P02901W56-R 18-93
Unsuccessful VGCS/VBS assignment at the BSS
Figure 18-80 shows an unsuccessful VGCS/VBS assignment at the BSS.
Figure 18-80 Unsuccessful VGCS/VBS assignment at the BSS
BSS MSC
CR
CC
VGCS call
VGCS/VBS Setup
VGCS_VBS_SETUP
VGCS/VBS Setup Ack
VGCS_VBS_SETUP_ACK
CR
CC
cell
VGCS/VBS Assignment Request
VGCS_VBS_ASSIGN_REQ
VGCS/VBS Assignment Failure
VGCS_VBS_ASSIGN_FAIL
ALLOC_TCH_FAIL_VGCS
ti-GSM-Stats-Unsucc VGCS VBS assign-eps-sw.
18-94 68P02901W56-R
Notification response procedure
Figure 18-81 shows the notification response procedure.
Figure 18-81 Notification response procedure
DS-MS BSS MSC

Notification/NCH (No VGC Channel Description)
Channel Request
(SEE NOTE)
ACCESS_PER_RACH
MS_ACCESS_BY_TYPE
ALLOC_SDCCH
ACCESS_PER_AGCH
Immediate Assignment
SABM (Notification Response)
OK_ACC_PROC[NOTIF_RESP]
UA (Notification Response)
Attempt to allocate radio

resource for VGC channel
Successful VGC Channel Allocation on Demand

Channel Release
VGCS/VBS Assignment Result
VGCS_FR_TCH_BUSY or
VGCS_HR_TCH_BUSY
TCH_Q_REMOVED
NCH: Notification/NCH (with VGC Channel Description)

V-SACCH: System Information (notification update indication)
V-FACCH: Uplink free or Uplink busy
or
Unsuccessful VGC Channel Allocation on Demand
Channel Release Clear Request (cause = no radio resource available)

CLR_REQ_TO_MSC
[CLR_REQ_TO_MSC_VGCS]
Clear Command
CLR_CMD_FROM_MSC
[CLR_CMD_FROM_MSC_VGCS]
Clear Complete
Stop sending notification of the RLSD

VGC on the NCH. RLC
NOTE: RSS ABIS does additional filtering of RACH. ti-GSM-Stats-Notif resp proc VGCS-eps-sw.
68P02901W56-R 18-95
Uplink grant inside one BSS
Figure 18-82 shows a successful uplink allocation where a cell is granted an uplink inside one BSS.
Figure 18-82 Uplink grant inside one BSS
LS-MSs UA-MS
in cell 1 in cell 1 Cell 1 BSC MSC
V-FACCH: Uplink Access
V-FACCH: VGCS Uplink Grant
uplink request indication*
Uplink Request
V-FACCH: SABM(Talker Indication)
V-FACCH: UA(Talker Indication)
Talker Indication
Uplink Request
Acknowledge
VGCS_TALKER_IND
Uplink Request
Confirmation(Talker Indication)
The UA-MS in cell 1 captures the uplink of the VGC
LS-MSs UA-MS Cell 2

in cell 2 in cell 2
uplink request indication*
V-FACCH: Uplink Release

LS-MSs in
OT_Cell OT_Cell
UA-MS --> MS initiates Uplink Access request

OT-Cell cell without mobiles initiating uplink access
* “uplink request indication” is not a real BSS internal

message defined in current IDS. It is just a notation to show
-
that cell informs BSC when it grants the VGC uplink to a US
MS.
ti-GSM-Stats-Succ UL One BSS VGCS-eps-sw.
18-96 68P02901W56-R
Uplink grant for multiple BSSs
Figure 18-83 shows a successful uplink allocation where a BSC is granted an uplink for multiple BSSs.
Figure 18-83 Uplink grant for multiple BSSs
OT-MSs UA-MS UG-BSS OT-BSSs MSC


Uplink Request

Uplink Request Acknowledge
VGCS_TALKER_IND
Uplink Request Confirmation (L3 Complete Info)
Uplink Seized Command
The UG-BSS initiates VGC channel to dedicated

channel handover procedure to the UA-MS.
UA-MS --> the MS initiating Uplink Access

OT-MS --> other MS not initiating Uplink Access, they may locate in different BSSs
UG-BSS --> the BSS granting the uplink of VGC to a UA-MS
OT-BSS --> the BSS not granting the uplink of VGC
ti-GSM-Stats-Succ UL Multi BSS VGCS-eps-sw.
68P02901W56-R 18-97
Unsuccessful uplink allocation
Figure 18-84 shows an unsuccessful uplink allocation where the MSC has rejected the uplink request.
Figure 18-84 Unsuccessful uplink allocation
OT-MSs UA-MS UG-BSS MSC

V-FACCH: Uplink free
Uplink Request
Uplink Reject Command

Uplink Seized Command
UA-MS --> the MS initiating Uplink Access

OT-MS --> other MS not initiating Uplink Access
UG-BSS --> the BSS granting the uplink of VGC to a UA-MS
ti-GSM-Stats-Unsucc UL MSC reject VGCS-eps-sw.
18-98 68P02901W56-R
Move talker to dedicated channel
Figure 18-85 shows the scenario where a talker is moved to a dedicated channel using the assignment
procedure.
Figure 18-85 Move talker to dedicated channel
TS-MS TS-MS
Dedicated channel VGC Channel BSS MSC
Uplink Request Confirmation
SCCP CR [Assignment Request]
Successfully moved to
dedicated channel Assignment Command
Guard timer C starts
Assignment Complete
Guard timer C stopped SCCP CC[Assignment Complete]
VGCS_FR_TCH_BUSY or
VGCS_HR_TCH_BUSY
TCH_Q_REMOVED
No dedicated channel allocated

SCCP CREF[Assignment Failure]
Uplink Release Uplink Release Command
Talker return to old VGC channel Guard timer C stopped

Assignment Failure
SCCP CREF[Assignment Failure]

Uplink Release
Talker lost
Timer C expires
SCCP CREF [Assignment Failure]
ti-GSM-Stats-Move talker VGCS-eps-sw.
68P02901W56-R 18-99
Uplink release by the talker
Figure 18-86 shows an uplink release by the talker.
Figure 18-86 Uplink release by the talker
LS-MS TS-MS BSS MSC
Talker on VGC channel

Uplink Release Indication
(cause = call control)
or
Talker on dedicated channel
D-FACCH: Uplink Release
Uplink Release Indication
(cause = call control)
Clear Command
CLR_CMD_FROM_MSC
D-FACCH: Channel Release

Clear Complete
RLSD
RLC
ti-GSM-Stats-UL release VGCS-eps-sw.
18-100 68P02901W56-R
Uplink reply procedure
Figure 18-87 show the uplink reply procedure.
Figure 18-87 Uplink reply procedure
LS-MSs LS-MSs
BSS MSC
in cell 1 in cell 2
V-FACCH: Uplink free (no Uplink Access Request indication)

Start Tul_reply
[2] Tul_reply for for cell 1
cell 1 expires
V-FACCH: Uplink free (Uplink Access Request indication)
Start Tua_burst
for cell 1
V-FACCH: Uplink Access (Establishment cause = Reply on uplink access request)
Cancel Tua_burst
for cell 1
V-FACCH: Uplink free (no Uplink Access Request indication)
Start Tul_reply
for cell 1
V-FACCH: Uplink free (n o Uplink Access Request indication)

Start Tul_reply
Tul_reply for for cell 2
cell 2 expires
V-FACCH: Uplink free (Uplink Access Request indication)
Start Tua_burst Tua_burst
for cell 2 expires for
cell 2
V-FACCH: Channel Release (no Group Channel Description)
Notification/NCH (No Group channel Description)
VGCS/VBS Assignment Result
(Resource de-allocated)
ti-GSM-Stats-UL reply VGCS-eps-sw.
68P02901W56-R 18-101
VGCS call termination
Figure 18-88 shows a VGCS call termination.
Figure 18-88 VGCS call termination
LS-MSs CS-MS BSS MSC

DTAP GCC Termination Request
DTAP GCC Termination
Clear Command
CLR_CMD_FROM_MSC
V-FACCH: Channel Release ( Group Channel Description)
Clear Complete
<RLSD>
<RLC>
Clear Command
CLR_CMD_FROM_MSC
V-FACCH: Channel Release (no Group Channel Description)
Clear Complete
<RLSD>
<RLC>
Clear Command
CLR_CMD_FROM_MSC
Clear Complete
<RLSD>
<RLC>
ti-GSM-Stats-Termination VGCS-eps-sw.
18-102 68P02901W56-R
Chapter
19
Impacts on statistics
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
The collection, interpretation and accuracy of GSM statistics may be affected by a number of factors, for
example, new software and hardware features. Although not all of 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 19-2.
• "Approximate equality" on page 19-6.
• "Phantom RACHs" on page 19-7.
• "Questions and answers" on page 19-10.
68P02901W56-R 19-1
Extended GSM (EGSM) Chapter 19: 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 needed 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.
The following examples illustrate the impact of the EGSM feature on statistics:
19-2 68P02901W56-R
Maintenance Information: GSM Statistics Application Extended GSM (EGSM)
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 19-1.
Table 19-1 MS access to a traffic channel
Statistic Value
MA_CMD_TO_MS_BLKD will be higher
MA_COMPLETE_TO_MSC will be lower
BUSY_TCH max/mean value will be lower
TOTAL_CALLS will be lower
TCH_CONGESTION will be lower (See note)
TCH_USAGE will be lower
TCH_DELAY will be higher
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.
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 of primary resources to open up
primary resources for non-EGSM MSs.
The statistics impacted are shown in Table 19-2.
68P02901W56-R 19-3
Extended GSM (EGSM) Chapter 19: Impacts on statistics
Table 19-2 Impact due to increased handovers
Statistic Value
INTRA_CELL_HO will be higher
INTRA_CELL_HO_REQ will be higher
INTRA_CELL_HO_LOSTMS will be higher
INTRA_CELL_HO_ATMPT will be higher
INTRA_CELL_HO_FAIL will be higher
MA_CMD_TO_MS will be higher
MA_FAIL_TO_MS will be higher
BAD_HO_REFNUM_MS will be higher
CLR_REQ_TO_MSC will be higher
ALLOC_SDCCH_FAIL will be higher
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 completely 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
of the resources have been allocated.
The statistics impacted are shown Table 19-3.
Table 19-3 Impact due to congestion
Statistic Value
MA_CMD_TO_MS_BLKD will be higher
MA_COMPLETE_TO_MSC will be lower
BUSY_TCH max/mean value will be lower
TOTAL_CALLS will be lower
TCH_CONGESTION will be lower (See note)
TCH_USAGE will be lower
TCH_DELAY will be higher
19-4 68P02901W56-R
Maintenance Information: GSM Statistics Application Extended GSM (EGSM)
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-R 19-5
Approximate equality Chapter 19: 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 19-1 is an example of approximate equality.
Figure 19-1 Approximate equality procedure
TCH Assignment Successful Procedure
9:00 9:30 10:00
MA_REQ_FROM_MSC
MA_CMD_TO_MS
MA_COMPLETE_TO_MSC
TOTAL_CALLS
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.
19-6 68P02901W56-R
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 will be 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 19-2 provides a graphic illustration of phantom RACHs.
Figure 19-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)
68P02901W56-R 19-7
Phantom RACHs Chapter 19: Impacts on statistics
Process of Phantom RACHs occurrences
The following process describes the chain of events that take place when a phantom RACH occurs:
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.
The other five bits of the eight-bit message are an unformatted 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).
19-8 68P02901W56-R
Maintenance Information: GSM Statistics Application Phantom RACHs
Raw statistics affected
The following statistics may be affected by phantom RACHs:

• ACCESS_PER_RACH.
• ACCESS_PER_AGCH.
• ALLOC_SDCCH.
• 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 or not 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
via 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-R 19-9
Questions and answers Chapter 19: Impacts on statistics
Questions and answers

■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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 above, during call set up the MSC decides whether or not to clear the call. Whether or not 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: Will the following counters work correctly after an SDCCH reconfiguration? That is when a TCH
is used as an SDCCH:
• ALLOC_SDCCH.
• 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.
19-10 68P02901W56-R
Maintenance Information: GSM Statistics Application Questions and answers
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. This is a DTAP procedure and the MSC
should keep track of this.
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 will not respond (because it
never existed to begin with).
Q: Does updated BTS hardware have any effect on Phantom RACHs?
A: ACCESS_PER_RACH counts reduce considerably between BTS5s and BTS4Ds (3000 > 300), which
have full diversity.
Q: What happens after a SDCCH has been seized by a phantom RACH? Will 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-R 19-11
Questions and answers Chapter 19: Impacts on statistics
19-12 68P02901W56-R
Index
Index
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
24349 . . . . . . . . . . . . . . . . . . . 3-5, 4-50
A
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ACCESS_PER_AGCH . . . . . . . . . . . . . 4-13 AMR_HR_DL_ADAPTATION . . . . . . . . . 4-34

ACCESS_PER_PCH . . . . . . . . . . . . . . 4-14 AMR_HR_DL_CODEC_MODE_USAGE . . . . 4-35
ACCESS_PER_PPCH . . . . . . . . . . . . . 4-16 AMR_HR_UL_ADAPTATION . . . . . . . . . 4-36
ACCESS_PER_RACH . . . . . . . . . . . . . 4-18 AMR_HR_UL_CODEC_MODE_USAGE . . . . 4-37
Accessibility statistics . . . . . . . . . . . . 18-74 AMR_INCREASE_THRESH_ADJUST . . . . . 4-38
ADJ_CHAN_INTF . . . . . . . . . . . . . . 4-128 approximate equality . . . . . . . . . . . . . . 19-6
AIR_DL_CONTROL_BLKS . . . . . . . . . . 12-8 assignment to TCH
AIR_DL_TBF_FAILURES . . . . . . . . . . . 12-9 assignment successful . . . . . . . . . . . 18-16
AIR_INTERFACE_BW_CS1 . . . . . . . . . . 17-9 fail recovered . . . . . . . . . . . . . . . 18-18
AIR_INTERFACE_BW_CS2 . . . . . . . . . 17-10 immediate assignment failure . . . . . . . . 18-17
AIR_INTERFACE_BW_CS3 . . . . . . . . . 17-11 TCH assignment blocked . . . . . . . . . . 18-17
AIR_INTERFACE_BW_CS4 . . . . . . . . . 17-12 ASSIGNMENT_REDIRECTION . . . . . . . . 4-39
AIR_INTERFACE_PAGING . . . . . . . . . 17-13 ASSIGNMENT_RESOURCE. . . . . . . . . 4-187
AIR_UL_CONTROL_BLKS . . . . . . . . . 12-10 ASSIGNMENT_RESOURCE_REQ_IN-
AIR_UL_TBF_FAILURES . . . . . . . . . . 12-11 NER_Z . . . . . . . . . . . . . . . . . . . 4-187
ALLOC_SDCCH . . . . . . . . . . . . . . . 4-19 ASSIGNMENT_SUCCESS_RATE . . . . . . 17-14
ALLOC_SDCCH_CARR . . . . . . . . . . . . 6-6 ATER_CHANNEL_REQUEST . . . . . . . . . 11-3
ALLOC_SDCCH_FAIL . . . . . . . . . . . . 4-21 ATER_CHANNEL_STATUS . . . . . . . . . . 11-4
ALLOC_TCH . . . . . . . . . . . . . . . . . 4-22 ATER_PREEMPT_ATMPT . . . . . . . . . . . 11-6
ALLOC_TCH_CARR . . . . . . . . . . . . . 6-7 ATER_PREEMPT_ATMPT_SWOVER . . . . . 11-7
ALLOC_TCH_FAIL . . . . . . . . . . . . . . 4-23 ATER_PREEMPT_FAIL . . . . . . . . . . . . 11-8
ALLOC_TCH_FAIL_HR . . . . . . . . . . . . 4-25 ATER_PREEMPT_FAIL_SWOVER . . . . . . 11-9
ALLOC_TCH_FAIL_VGCS . . . . . . . . . . 4-27 ATER_PREEMPT_RQD . . . . . . . . . . . 11-10
ALLOC_TCH_HR . . . . . . . . . . . . . . . 4-28 ATTEMPT_IMMED_ASSIGN_PROC . . . . . 16-6
AMR_DECREASE_THRESH_ADJUST . . . . 4-29 AVAILABLE_SDCCH . . . . . . . . . . . . . 4-40
AMR_FR_DL_ADAPTATION . . . . . . . . . 4-30 AVAILABLE_TCH. . . . . . . . . . . . . . . 4-41
AMR_FR_DL_CODEC_MODE_USAGE . . . . 4-31 AVAILABLE_TCH_DCS1800 . . . . . . . . . 4-42
AMR_FR_UL_ADAPTATION . . . . . . . . . 4-32 AVAILABLE_TCH_EGSM . . . . . . . . . . . 4-44
AMR_FR_UL_CODEC_MODE_USAGE . . . . 4-33 AVAILABLE_TCH_PGSM . . . . . . . . . . . 4-47
68P02901W56-R IX-1
Index
B
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
BAD_HO_REFNUM_MS . . . . . . . . . . . 4-49 BSSLAP_TA_RESP . . . . . . . . . . . . . . 9-11

Band reassignment BSSLAP_TOA_REQ . . . . . . . . . . . . . . 9-12
introduction BSSMAP_CONLESS_INFO_RCV . . . . . . . 9-13
fail recovered . . . . . . . . . . . . . . 18-62 BSSMAP_CONLESS_INFO_SENT. . . . . . . 9-14
handover successful . . . . . . . . . . . 18-61 BSSMAP_PERF_LOC_ABORT_MSGS . . . . . 9-15
handover unsuccessful . . . . . . . . . . 18-62 BSSMAP_PERF_LOC_REQ_MSGS . . . . . . 9-16
BAND_HANDOVER . . . . . . . . . . . . 4-129 BSSMAP_PERF_LOC_RESP_MSGS . . . 9-17, 9-21
BAND_RE_ASSIGN . . . . . . . . . . . . . 4-129 BSSMAPLE_CONLESS_INFO_RCV . . . . . . 9-18
BER . . . . . . . . . . . . . . . . . . . . . . 6-8 BSSMAPLE_CONLESS_INFO_SENT . . . . . 9-19
Bin ranges . . . . . . . . . . . . . . . . . . . 2-18 BSSMAPLE_PERF_LOC_ABORT_MSGS . . . 9-20
BSC BSSMAPLE_PERF_LOC_RESP_MSGS . . . . 9-22
functions . . . . . . . . . . . . . . . . . . 18-4 BUSY_CICS. . . . . . . . . . . . . . . . . . 10-5
BSS BUSY_SDCCH . . . . . . . . . . . . . . . . 4-50
functions . . . . . . . . . . . . . . . . . . 18-4 BUSY_TCH . . . . . . . . . . . . . . . . . . 4-52
BSSLAP_ABORT_RCV . . . . . . . . . . . . 9-4 BUSY_TCH_CARR . . . . . . . . . . . 4-54, 6-10
BSSLAP_ABORT_SENT. . . . . . . . . . . . 9-5 BUSY_TCH_CARR_HR . . . . . . . . . . . . 6-11
BSSLAP_MS_POS_CMD . . . . . . . . . . . 9-6 BUSY_TCH_DCS1800. . . . . . . . . . . . . 4-55
BSSLAP_MS_POS_RESP . . . . . . . . . . . 9-7 BUSY_TCH_EGSM . . . . . . . . . . . . . . 4-56
BSSLAP_REJ . . . . . . . . . . . . . . . . . 9-8 BUSY_TCH_HR . . . . . . . . . . . . . 4-46, 4-57
BSSLAP_RESET . . . . . . . . . . . . . . . 9-9 BUSY_TCH_PGSM . . . . . . . . . . . . . . 4-58
BSSLAP_TA_REQ. . . . . . . . . . . . . . . 9-10
C
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
C_SETUP_SUCCESS_RATE . . . . . . . . . 17-19 call procedure (contd.)

C_SETUP_TCH_BLOCKING_RATE . . . . . . 15-3 bids-attempts-successes . . . . . . . . . . . 18-6
C_SP_VERS_DOWNGRADE_MONITOR . . . 4-59 bids-bids blocked . . . . . . . . . . . . . . 18-6
C_SUCCESS_RATE . . . . . . . . . . . . . 17-22 call setup and handover matrix . . . . . . . . . 18-7
C_VOLUME. . . . . . . . . . . . . . . . . 17-23 call statistics
call clearing call_statistics . . . . . . . . . . . . . . . 4-108
cipher mode fail . . . . . . . . . . . . . . 18-42 CALL_SETUP_RF_ASSIGN-
queueing timeout. . . . . . . . . . . . . . 18-45 MENT_FAIL_RATE_LOST_MS . . . . . . . 17-15
RF loss on a TCH . . . . . . . . . . . . . 18-44 CALL_SETUP_RF_ASSIGNMENT_FAIL_RATE_RE-
RF loss on an SDCCH . . . . . . . . . . . 18-43 COVERED_MS . . . . . . . . . . . . . . . 17-17
Call model statistics . . . . . . . . . . . . . . 15-1 CALL_SETUP_RF_ASSIGNMENT_SUC-
C_SETUP_TCH_BLOCKING_RATE . . . . . 15-3 CESS_RATE. . . . . . . . . . . . . . . . . 17-18
HANDOVERS_PER_C (H) . . . . . . . . . 15-4 cell statistics
IMSI_DETACHES_TO_C (Id) . . . . . . . . 15-5 introduction . . . . . . . . . . . . . . . . . 4-2
INTRA_BSS_HO_TO__HO (i) . . . . . . . . 15-6 CELL_FLUSH_REQS . . . . . . . . . . . . 12-12
LOCATION_UPDATE_FACTOR (L) . . . . . 15-7 CELL_TCH_ASSIGNMENTS . . . . . . . . 16-11
LOCATION_UPDATES_TO_CS (I) . . . . . 15-8 CELL_TCH_OCATIONS . . . . . . . . . . . 16-10
PAGES_PER_C (PPC) . . . . . . . . . . . . 15-9 CELL_UPDATE . . . . . . . . . . . . . . . 17-25
PAGES_PER_SECOND . . . . . . . . . . 15-10 CH_REQ_UNSVCD_PCU . . . . . . . . . . 12-13
PAGING_RATE (P) . . . . . . . . . . . . 15-11 CHAN_DL_TX_PWR_LVL . . . . . . . . . . 6-12
SMS_TO_C_RATIO (S) . . . . . . . . . . 15-12 CHAN_REQ_CAUSE_ATMPT . . . 4-63, 9-2 to 9-3
call procedure CHAN_REQ_MS_BLK . . . . . . . . . . . . 4-64
bids . . . . . . . . . . . . . . . . . . . . . 18-6 CHAN_REQ_MS_FAIL . . . . . . . . . . . . 6-13
bids-attempt-fail-recovered . . . . . . . . . . 18-6 CHAN_UL_TX_PWR_LVL . . . . . . . . . . 6-15
bids-attempt-failures . . . . . . . . . . . . . 18-6 CHANNEL_REQS_REC . . . . . . . . . . . 12-15
bids-attempts . . . . . . . . . . . . . . . . 18-6 CHANNEL_REQS_REJ . . . . . . . . . . . 12-17
IX-2 68P02901W56-R
Index
CHANNEL_REQS_SUCCESS . . . . . . . . 12-18 Counter array statistics (contd.)

chg_stat_prop . . . . . . . . . . . . . . . . . 2-18 Interval expiry . . . . . . . . . . . . . . . . 1-7
chg_stat_prop command . . . . . . . . . . . . 2-15 Maximum values. . . . . . . . . . . . . . . 1-7
CIPHER_MODE_FAIL. . . . . . . . . . . . . 4-65 Counter statistics . . . . . . . . . . . . . . 1-6, 2-16
CLASSMK_UPDATE_FAIL . . . . . . . . . . 4-66 Interval expiry . . . . . . . . . . . . . . . . 1-6
CLR_CMD_FROM_MSC . . . . . . . . . . . 4-67 Maximum value . . . . . . . . . . . . . . . 1-6
CLR_REQ_TO_MSC . . . . . . . . . . . . . 4-68 Threshold event reporting. . . . . . . . . . . 1-6
cm_lcs_request. . . . . . . . . . . . . . . . 4-125 CPU_USAGE . . . . . . . . . . . . . . . . . 7-2
CM_REESTABLISH . . . . . . . . . . . . . 4-125 CS_PAGE_REQS . . . . . . . . . . . . . . 12-24
CM_SERV_REQ_C . . . . . . . . . . . . . 4-125 CS_QUEUED . . . . . . . . . . . . . . . . . 4-61
CM_SERV_REQ_EMERG . . . . . . . . . . 4-125 CS12_ON_32K_CHAN . . . . . . . . . . . 12-25
CM_SERV_REQ_SMS . . . . . . . . . . . . 4-125 CS1234_ON_64K_CHAN . . . . . . . . . . 12-26
CM_SERV_REQ_SUPP . . . . . . . . . . . 4-125 Custom statistics . . . . . . . . . . . . . . . . 1-4
CM_SERV_REQ_VBS . . . . . . . . . . . . 4-125
CM_SERV_REQ_VGCS . . . . . . . . . . . 4-125
CODING_SCHEME_CHANGE . . . . . . . 12-20
CONG_REL_DL_SCTS . . . . . . . . . . . 12-22
CONGEST_EXIST_HO_ATMPT . . . . . . . . 4-70
CONGEST_STAND_HO_ATMPT . . . . . . . 4-71
CONGESTION . . . . . . . . . . . . . . . 4-128
Congestion relief
intra-BSS . . . . . . . . . . . . . . . . . 18-48
CONGESTION_LOST_MSU . . . . . . . . . . 10-7
CONN_REFUSED . . . . . . . . . . . . . . . 4-72
CONN_REQ_TO_MSC . . . . . . . . . . . . 4-74
connection establishment
failure
failute. . . . . . . . . . . . . . . . . . 18-13
immediate assignment blocked . . . . . . . 18-14
immediate assignment failure . . . . . . . . 18-14
successful
mobile originated . . . . . . . . . . . . 18-12
mobile terminated call . . . . . . . . . . 18-15
Counter array statistics . . . . . . . . . . . . . 1-7
Counter array bins . . . . . . . . . . . . . . 1-7
D
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
default values . . . . . . . . . . . . . . . . . 2-3 Displaying a distribution statistic . . . . . . . . 2-23

Dictionary = br Displaying a duration statistic . . . . . . . . . . 2-27
Average call duration . . . . . . . . . . . . . 15-2 Displaying a gauge statistic . . . . . . . . . . . 2-22
C_DURATION . . . . . . . . . . . . . . . 15-2 Displaying statistic properties . . . . . . . . . . 2-20
Call model statistics Displaying a counter array statistic . . . . . . 2-25
C_DURATION . . . . . . . . . . . . . . 15-2 Displaying a counter statistic . . . . . . . . . 2-21
Directed retry Displaying a distribution statistic . . . . . . . 2-23
intra-BSS . . . . . . . . . . . . . . . . . 18-50 Displaying a duration statistic . . . . . . . . . 2-27
disabling a statistic Displaying a gauge statistic . . . . . . . . . . 2-22
disable a statistic . . . . . . . . . . . . . . . 2-5 Displaying statistic values. . . . . . . . . . . . 2-9
disp_interval command . . . . . . . . . . . . . 2-13 Displaying the statistics interval . . . . . . . . . 2-12
disp_stat_prop command . . . . . . . . . . . . 2-20 Displaying the statistics interval start times . . . . 2-13
disp_stats command . . . . . . . . . . . . . . 2-9 DISTANCE . . . . . . . . . . . . . . . . . 4-128
Displaying a counter array statistic. . . . . . . . 2-25 Distribution statistics . . . . . . . . . . . . . . 1-9
Displaying a counter statistic . . . . . . . . . . 2-21 DL_AIR_INTERFACE_BW_CS1 . . . . . . . 17-26
68P02901W56-R IX-3
Index
DL_AIR_INTERFACE_BW_CS2 . . . . . . . 17-27 DL_PDTCH_SEIZURE . . . . . . . . . . . 12-56

DL_AIR_INTERFACE_BW_CS3 . . . . . . . 17-28 DL_RADIO_BLKS_1_TS . . . . . . . . . . 12-57
DL_AIR_INTERFACE_BW_CS4 . . . . . . . 17-29 DL_RADIO_BLKS_2_TS . . . . . . . . . . 12-60
DL_BLER_CS1 . . . . . . . . . . . . . . . 12-27 DL_RADIO_BLKS_3_TS . . . . . . . . . . 12-63
DL_BLER_CS2 . . . . . . . . . . . . . . . 12-28 DL_RADIO_BLKS_4_TS . . . . . . . . . . 12-66
DL_BLER_CS3 . . . . . . . . . . . . . . . 12-29 DL_RLC_ACK_NEW_BLKS. . . . . . . . . 12-69
DL_BLER_CS4 . . . . . . . . . . . . . . . 12-31 DL_RLC_DDTR_BLKS . . . . . . . . . . . 12-71
DL_BLER_MCS1 . . . . . . . . . . . . . . 12-33 DL_RLC_NACK_BLKS . . . . . . . . . . . 12-72
DL_BLER_MCS2 . . . . . . . . . . . . . . 12-35 DL_RLC_RETX_BLKS . . . . . . . . . . . 12-74
DL_BLER_MCS3 . . . . . . . . . . . . . . 12-37 DL_RLC_STED_BLKS . . . . . . . . . . . 12-76
DL_BLER_MCS4 . . . . . . . . . . . . . . 12-39 DL_RLC_UNACK_NEW_BLKS . . . . . . . 12-78
DL_BLER_MCS5 . . . . . . . . . . . . . . 12-41 DL_TBF_TIME_1_TS . . . . . . . . . . . . 12-80
DL_BLER_MCS9 . . . . . . . . . . . . . . 12-49 DOWNINTERF . . . . . . . . . . . . . . . 4-128
DL_BUSY_PDTCH . . . . . . . . . . . . . 12-51 DOWNLEVEL. . . . . . . . . . . . . . . . 4-128
DL_EGPRS_64K_CHANNEL_WIDTH . . . . . 6-18 DOWNQUAL . . . . . . . . . . . . . . . . 4-128
DL_EGPRS_BACKHAUL_DEMAND . . . . . 6-16 DROP_C_RATE . . . . . . . . . . . . . . . 17-30
DL_EGPRS_BACKHAUL_USED . . . . . . . 6-17 Duration statistics . . . . . . . . . . . . . . . 1-8
DL_LLC_DATA_VOLUME . . . . . . . . . . 4-75 Interval expiry . . . . . . . . . . . . . . . . 1-8
DL_LLC_FRAMES_GB . . . . . . . . . . . 12-53 Maximum value . . . . . . . . . . . . . . . 1-8
DL_LLC_FRAMES_PCU . . . . . . . . . . 12-54 Period counter and mean value . . . . . . . . 1-8
DL_LLC_TRAFFIC_VOLUME_INDICA- Total duration . . . . . . . . . . . . . . . . 1-8
TOR. . . . . . . . . . . . . . . . . . . . . 16-12 Wraparound to next day . . . . . . . . . . . 1-8
DL_PDTCH_Q_LENGTH . . . . . . . . . . 12-55
E
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
EGPRS_64K_CHANNELS_SWITCHED . . . 12-84 enabling a statistic

EGPRS_64K_NOT_AVAIL . . . . . . . . . . 12-85 enable a statistic . . . . . . . . . . . . . . . 2-4
EGPRS_AVAIL_PDTCH . . . . . . . . . . . 12-86 ER_INTRA_CELL_HO_ATMPT . . . . . . . . 4-77
EGPRS_DL_ASGN_PCCCH . . . . . . . . . 12-87 ER_INTRA_CELL_HO_SUC. . . . . . . . . . 4-78
EGSM (extended GSM) . . . . . . . . . . . . 19-2
F
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
feature FER_AMR_HR . . . . . . . . . . . . . . . . 6-21

22064 . . . . . 4-25, 4-28, 4-46, 4-177, 4-179, 6-11, FER_GSM_FR_EFR . . . . . . . . . . . . . . 6-23
6-35, 16-43, 16-45, 17-30, 17-64 to 17-65, 17-113 FER_GSM_HR . . . . . . . . . . . . . . . . 6-25
4322 . . . . . . . . . . . . . . . . . . . . 18-9 FLOW_CONTROL_BARRED . . . . . . . . . 4-79
FER_AMR_FR . . . . . . . . . . . . . . . . 6-19 FRMR . . . . . . . . . . . . . . . . . . . . 11-11
IX-4 68P02901W56-R
Index
G
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
G_RACH_UNSVCD_BTS . . . . . . . . . . 12-88 GPRS performance . . . . . . . . . . . . . . . 17-3

Gauge statistics . . . . . . . . . . . . . . . . 1-7 GPRS_32K_CHANNELS_SWITCHED . . . . 12-98
Interval expiry . . . . . . . . . . . . . . . . 1-7 GPRS_32K_DL_NOT_AVAIL . . . . . . . . 12-99
Threshold event reporting. . . . . . . . . . . 1-7 GPRS_32K_UL_NOT_AVAIL . . . . . . . . 12-100
Gb interface . . . . . . . . . . . . . . . . . . 12-2 GPRS_ACCESS_PER_AGCH . . . . . . . . 12-101
GBL statistics . . . . . . . . . . . . . . . . 18-70 GPRS_ACCESS_PER_RACH . . . . . . . . 12-102
GBL_DL_DATA_THRPUT. . . . . . . . . . 12-89 GPRS_AVAIL_PDTCH. . . . . . . . . . . . 12-103
GBL_DL_DATA_THRPUT_HIST . . . . . . 12-90 GPRS_CELL_CONGESTION . . . . . . . . 12-105
GBL_FLOW_CTRL_SENT. . . . . . . . . . 12-92 GPRS_CELL_RESELECT_FAIL . . . . . . . 12-107
GBL_FLUSH_REQS GPRS_CHANNELS_SWITCHED . . . . . . 12-108
see CELL_FLUSH_REQS . . . . . . . . . 12-12 GPRS_DL_ACT_TS . . . . . . . . . . . . . 17-32
GBL_PAGING_REQS . . . . . . . . . . . . 12-93 GPRS_DL_ASGN_PCCCH. . . . . . . . . . 12-109
GBL_UL_DATA_THRPUT. . . . . . . . . . 12-94 GPRS_PCH_AGCH_Q_LENGTH . . . . . . 12-110
GBL_UL_DATA_THRPUT_HIST . . . . . . 12-95 GPRS_PPCH_PAGCH_Q_LENGTH
GBL_UNAVAILABLE . . . . . . . . . . . . 12-97 GPRS_PCH_AGCH_Q_LENGTH . . . . . 12-111
GCI_FOR_16KPD_DEMAND . . . . . . . . . 7-3 GPRS_PRR_BLK_USG . . . . . . . . . . . 12-112
GCI_FOR_32KPD_DEMAND . . . . . . . . . 7-4 GPRS_RACH_ARRIVAL . . . . . . . . . . 12-114
GCI_FOR_64KPD_DEMAND . . . . . . . . . 7-5 GPRS_UL_ACT_TS . . . . . . . . . . . . . 17-33
H
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
handover. . . . . . . . . . . . . . . . . . . . 18-5 HO_CAUSE_DLINTERF . . . . . . . . . . 17-39

handover performance . . . . . . . . . . . . . 17-3 HO_CAUSE_DLLEVEL . . . . . . . . . . . 17-40
Handover successful HO_CAUSE_DLQUAL . . . . . . . . . . . 17-41
band reassignment HO_CAUSE_PWRBGT . . . . . . . . . . . 17-42
introduction . . . . . . . . . . . . . . . 18-61 HO_CAUSE_UPINTERF. . . . . . . . . . . 17-43
HANDOVER_FAILURE_RATE . . . . . . . 16-14 HO_CAUSE_UPLEVEL . . . . . . . . . . . 17-44
HANDOVER_SUCCESS_RATE . . . . . . . 16-15 HO_CAUSE_UPQUAL . . . . . . . . . . . 17-45
Handovers HO_FAIL_NO_RESOURCES . . . . . . . . . 4-80
ratio per call . . . . . . . . . . . . . . . . . 15-4 HO_PER_C . . . . . . . . . . . . . . . . . 17-46
HANDOVERS_PER_C. . . . . . . . . . . . . 15-4 HO_REQ . . . . . . . . . . . . . . . . . . 4-187
health check . . . . . . . . . . . . . . . . . . 17-6 HO_REQ_ACK_TO_MSC . . . . . . . . . . . 4-85
HO_CAUSE_ADJ_CH_INTERF . . . . . . . 17-34 HO_REQ_FROM_MSC . . . . . . . . . . . . 4-82
HO_CAUSE_BAND_HO. . . . . . . . . . . 17-35 HO_REQ_INNER_Z . . . . . . . . . . . . . 4-187
HO_CAUSE_BAND_REASSGN . . . . . . . 17-36 HO_REQ_MSC_FAIL . . . . . . . . . . . . . 4-83
HO_CAUSE_CONGEST . . . . . . . . . . . 17-37 HO_REQ_MSC_PROTO . . . . . . . . . . . . 3-4
HO_CAUSE_DISTANCE . . . . . . . . . . 17-38
I
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
I_FRAMES_RX . . . . . . . . . . . . . . . 11-12 IDLE_TCH_INTF_BAND1. . . . . . . . . . . 4-88

I_FRAMES_TX . . . . . . . . . . . . . . . 11-13 IDLE_TCH_INTF_BAND2. . . . . . . . . . . 4-89
IDLE_PDTCH_INTF_BAND0 . . . . . . . . 12-116 IDLE_TCH_INTF_BAND3. . . . . . . . . . . 4-90
IDLE_PDTCH_INTF_BAND1 . . . . . . . . 12-117 IDLE_TCH_INTF_BAND4. . . . . . . . . . . 4-91
IDLE_PDTCH_INTF_BAND2 . . . . . . . . 12-118 IMM_ASSGN_CAUSE. . . . . . . . . . . . 12-121
IDLE_PDTCH_INTF_BAND3 . . . . . . . . 12-119 IMM_SETUP . . . . . . . . . . . . . . . . 4-125
IDLE_PDTCH_INTF_BAND4 . . . . . . . . 12-120 IMM_SETUP_2 . . . . . . . . . . . . . . . 4-125
IDLE_TCH_INTF_BAND0. . . . . . . . . . . 4-87
68P02901W56-R IX-5
Index
IMMEDIATE_ASSIGN_BLOCK- Interband activity (contd.)

ING_RATE . . . . . . . . . . . . . . . . . 17-47 intra-BSS (contd.)
IMMEDIATE_ASSIGN_FAILURE_RATE . . 17-48 invalid frequency supported . . . . . . . 18-55
IMMEDIATE_ASSIGN_MEAN_AR- Interband assignment
RIVAL_TIME . . . . . . . . . . . . . . . . 17-49 invalid frequency . . . . . . . . . . . . . 18-60
IMMEDIATE_ASSIGN_SUCCESS_RATE . . 17-50 INTERBAND_ACTIVITY . . . . . . . . . . . 4-95
IMSI detaches INTERNAL_LOST. . . . . . . . . . . . . . 17-56
ratio per call . . . . . . . . . . . . . . . . . 15-5 INTERNAL_RECOVERED . . . . . . . . . 17-57
IMSI_DETACH . . . . . . . . . . . . . . . 4-125 INTERNAL_SUCCESS . . . . . . . . . . . 17-58
IMSI_DETACHES_TO_C . . . . . . . . . . . 15-5 INTF_ON_IDLE . . . . . . . . . . . . . . . . 6-27
IN_INTER_BSS_EQUIP_FAIL . . . . . . . . . 4-92 Intra-BSS
IN_INTER_BSS_HO . . . . . . . . . . . . . . 4-92 congestion relief . . . . . . . . . . . . . . 18-48
IN_INTER_BSS_HO_CLEARED . . . . . . . . 4-92 directed retry . . . . . . . . . . . . . . . 18-50
IN_INTER_BSS_HO_SEIZE . . . . . . . . . . 4-92 intra-BSS handover
IN_INTER_BSS_HO_SUC . . . . . . . 4-92, 17-52 fail-lost . . . . . . . . . . . . . . . . . . 18-34
IN_INTER_CELL_HO_SUC . . . . . . . . . 17-53 fail-recovered . . . . . . . . . . . . . . . 18-33
IN_INTER_CELL_HO_TO_IN_ZONE . . . . 4-202 handover blocked . . . . . . . . . . . . . 18-32
to 4-203 handover successful . . . . . . . . . . . . 18-31
IN_INTRA_BSS_EQUIP_FAIL . . . . . . . . . 4-93 standard directed retry
IN_INTRA_BSS_HO. . . . . . . . . . . . . . 4-93 internal . . . . . . . . . . . . . . . . . 18-35
IN_INTRA_BSS_HO_CLEARED. . . . . . . . 4-93 Intra-BSS handovers . . . . . . . . . . . . . . 15-6
IN_INTRA_BSS_HO_LOSTMS . . . . . . . . 4-93 INTRA_BSS_HO_CAUSE_SUCC . . . . . . . 3-5
IN_INTRA_BSS_HO_RETURN . . . . . . . . 4-93 INTRA_BSS_HO_TO__HO . . . . . . . . . . 15-6
IN_INTRA_BSS_HO_SUC . . . . . . . 4-93, 17-54 intra-cell handover
IN_INTRA_BSS_NC_ATMPT . . . . . . . . . 5-9 fail lost . . . . . . . . . . . . . . . . . . 18-22
IN_INTRA_BSS_NC_SUC . . . . . . . . . . . 5-10 fail recovered . . . . . . . . . . . . . . . 18-21
INCOMING_HO_VOLUME . . . . . . . . . 17-55 handover blocked . . . . . . . . . . . . . 18-20
INNER_TO_OUTER_ZONE . . . . . 4-202 to 4-203 handover successful . . . . . . . . . . . . 18-19
inter-BSS handover INTRA_CELL_EQUIP_FAIL . . . . . . . . . . 4-96
fail lost . . . . . . . . . . . . . . . . . . 18-26 INTRA_CELL_HO. . . . . . . . . . . . . . . 4-96
fail lost mobile . . . . . . . . . . . . . . . 18-27 INTRA_CELL_HO_ATMPT_FR_FR . . . . . . 4-96
fail recovered . . . . . . . . . . . . . . . 18-25 INTRA_CELL_HO_ATMPT_FR_HR . . . . . . 4-96
handover blocked . . . . . . . . . . . . . 18-24 INTRA_CELL_HO_ATMPT_HR_FR . . . . . . 4-96
handover successful . . . . . . . . . . . . 18-23 INTRA_CELL_HO_ATMPT_HR_HR . . . . . . 4-96
standard directed retry INTRA_CELL_HO_CLEARED . . . . . . . . 4-96
external . . . . . . . . . . . . . . . . . 18-29 INTRA_CELL_HO_FAIL_LOST_MS. . . . . 17-59
Interband activity INTRA_CELL_HO_FAIL_RECOVERED . . . 17-60
inter-BSS INTRA_CELL_HO_LOSTMS . . . . . . . . . 4-96
fail recovered . . . . . . . . . . . . . . 18-58 INTRA_CELL_HO_REQ. . . . . . . . . . . . 4-96
handover successful . . . . . . . . . . . 18-56 INTRA_CELL_HO_RETURN . . . . . . . . . 4-96
handover unsuccessful . . . . . . . . . . 18-58 INTRA_CELL_HO_SUC . . . . . . . . . . . . 4-96
invalid frequency supported . . . . . . . 18-59 INTRA_CELL_HO_SUCCESS_RATE . . . . 17-61
intra-BSS INTRA_ZONE. . . . . . . . . . . . 4-202 to 4-203
fail recovered . . . . . . . . . . . . . . 18-54 INVALID_FRAMES_RX . . . . . . . . . . . 11-14
handover unsuccessful . . . . . . . . . . 18-54
K
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
key statistics . . . . . . . . . 1-3, 16-2 to 16-3, 16-5 key statistics (contd.)

ATTEMPT_IMMED_ASSIGN_PROC . . . . 16-6 channel usage . . . . . . . . . . . . . . . . 16-3
call summary . . . . . . . . . . . . . . . . 16-2 connection establishment . . . . . . . . . . . 16-3
CELL_TCH_ASSIGNMENTS . . . . . . . 16-11 HANDOVER_FAILURE_RATE . . . . . . 16-14
CELL_TCH_OCATIONS . . . . . . . . . 16-10 HANDOVER_SUCCESS_RATE . . . . . . 16-15
IX-6 68P02901W56-R
Index
key statistics (contd.) key statistics (contd.)

loss summary . . . . . . . . . . . . . . . . 16-4 SUCCESS_INTERNAL_HO . . . . . . . . 16-34
MEAN_ARRIVAL_TIME_BE- TCH_BLOCKING_RATE . . . . . . . . . 16-36
TWEEN_CS. . . . . . . . . . . . . . . . 16-20 TCH_BLOCKING_RATE_INNER_Z . . . . 16-37
MEAN_INTER_ARRIVAL_TIME . . . . . 16-21 TCH_BLOCKING_RATE_OUTER_Z . . . 16-38
MEAN_TCH_BUSY_TIME . . . . . . . . 16-23 TCH_MEAN_ARRIVAL_RATE . . . . . . 16-39
MTL_UTILISATION_RX . . . . . . . . . 16-24 TCH_MEAN_HOLDING_TIME . . . . . . 16-40
MTL_UTILISATION_TX . . . . . . . . . 16-25 TCH_TRAFFIC_CARRIED . . . . 16-45, 17-116
RF_LOSS_RATE . . . . . . . . . . . . . 16-26 template . . . . . . . . . . . . . . . . . . . 16-5
SDCCH_BLOCKING_RATE . . . . . . . . 16-28 TOTAL_CS_KEY . . . . . . . . . . . . . 16-47
SDCCH_MEAN_HOLDING_TIME . . . . 16-29 UNSUCCESS_INTER-
SDCCH_RF_LOSS_RATE . . . . . . . . . 16-30 NAL_HO_NOREEST . . . . . . . . . . . 16-49
SDCCH_TRAFFIC_CARRIED . . . . . . . 16-31 UNSUCCESS_INTERNAL_HO_REEST . . 16-50
SUCCESS_IMMED_ASSIGN_PROC . . . 16-33
L
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
L_ROUTING_SYNTAX . . . . . . . . . . . . 13-3 LMTP_MSU_DISCARDED . . . . . . . . . . 8-6

L_ROUTING_UNKNOWN. . . . . . . . . . . 13-4 LMTP_MSU_RX . . . . . . . . . . . . . . . 8-16
L_SCCP_MSGS . . . . . . . . . . . . . . . . 13-5 LMTP_MSU_TX . . . . . . . . . . . . . . . 8-17
L_SCCP_MSGS_RX . . . . . . . . . . . . . . 13-6 LMTP_NEG_ACKS . . . . . . . . . . . . . . 8-18
l_sccp_msgs_rx_0 . . . . . . . . . . . . . . . 13-6 LMTP_RE_TX. . . . . . . . . . . . . . . . . 8-19
l_sccp_msgs_rx_2 . . . . . . . . . . . . . . . 13-6 LMTP_REMOTE_MGT . . . . . . . . . . . . 8-20
L_SCCP_MSGS_TX . . . . . . . . . . . . . . 13-7 LMTP_REMOTE_PROC . . . . . . . . . . . . 8-21
l_sccp_msgs_tx_0 . . . . . . . . . . . . . . . 13-7 LMTP_RESTORATION . . . . . . . . . . . . 8-22
l_sccp_msgs_tx_2 . . . . . . . . . . . . . . . 13-7 LMTP_SIB_RX . . . . . . . . . . . . . . . . 8-35
L_SIF_SIO_RX_OPC . . . . . . . . . . . . . 13-8 LMTP_SIB_TX . . . . . . . . . . . . . . . . 8-37
L_SIF_SIO_TX_OPC . . . . . . . . . . . . . 13-9 LMTP_SIF_SIO_RX . . . . . . . . . . . . . . 8-23
l_sif_sio_type . . . . . . . . . . . . . . . . 13-10 LMTP_SIF_SIO_TX . . . . . . . . . . . . . . 8-24
L_SIF_SIO_TYPE . . . . . . . . . . . . . . 13-10 LMTP_SL_ACK . . . . . . . . . . . . . . . . 8-25
l_sif_sio_type_mtp . . . . . . . . . . . . . . 13-10 LMTP_SL_ALIGNMENT . . . . . . . . . . . 8-26
l_sif_sio_type_test . . . . . . . . . . . . . . 13-10 LMTP_SL_CONGESTION . . . . . . . . . . . 8-27
LAPD_CONGESTION . . . . . . . . . . . . 11-15 LMTP_SL_ERROR_RATE . . . . . . . . . . . 8-28
LLC_ABNORMAL_TBF_RELEASES . . . . 16-17 LMTP_SL_FAIL . . . . . . . . . . . . . . . . 8-29
LLC_BUFFER_OVERFLOW_RATE . . . . . 16-18 LMTP_SL_FIBR. . . . . . . . . . . . . . . . 8-30
LLC_DISCARDS_ON_CELL_RESELEC- LMTP_START_RPO . . . . . . . . . . . . . . 8-31
TION . . . . . . . . . . . . . . . . . . . . 16-19 LMTP_STOP_RPO . . . . . . . . . . . . . . 8-32
LMTP_CHANGEBACK . . . . . . . . . . . . 8-7 LMTP_SU_ERROR . . . . . . . . . . . . . . 8-33
LMTP_CHANGEOVER . . . . . . . . . . . . 8-8 LMTP_UNAVAILABLE . . . . . . . . . . . . 8-34
LMTP_CONGESTION . . . . . . . . . . . . . 8-36 LOC_FLW_ON_REQ_NORM . . . . . . . . 4-125
LMTP_LINK_INS . . . . . . . . . . . . . . . 8-10 LOC_FLW_ON_REQ_SMS . . . . . . . . . 4-125
LMTP_LINKFAIL . . . . . . . . . . . . . . . 8-11 Location updates
LMTP_LOCAL_BUSY. . . . . . . . . . . . . 8-12 ratio per call . . . . . . . . . . . . . . . . . 15-8
LMTP_LOCAL_MGT . . . . . . . . . . . . . 8-13 LOCATION_SERVICES . . . . . . . . . . . 4-125
LMTP_LOCAL_SL_CONGESTION . . . . . . 8-9 LOCATION_UPDATE . . . . . . . . . . . . 4-125
LMTP_MGT_INHIBIT. . . . . . . . . . . . . 8-14 LOCATION_UPDATE_FACTOR . . . . . . . . 15-7
LMTP_MGT_UNINHIBIT . . . . . . . . . . . 8-15 LOCATION_UPDATES_TO_CS . . . . . . . . 15-8
M
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
MA_CMD_TO_MS
68P02901W56-R IX-7
Index
MA_CMD_TO_MS (contd.) MSU_DISCARDED . . . . . . . . . . . . . . 10-8

MS_CMD_TO_MS . . . . . . . . . . . . . 4-98 MT_LCS_ON_SDCCH. . . . . . . . . . . . 4-110
MA_CMD_TO_MS_BLKD. . . . . . . . . . 4-105 MTL
MA_COMPLETE_TO_MS . . . . . . . . . . . 4-99 operator initiated outage . . . . . . . . . . 18-66
MA_COMPLETE_TO_MSC . . . . . . . . . 4-100 transition scenarios . . . . . . . . . . . . . 18-67
MA_FAIL_FROM_MS . . . . . . . . . . . . 4-102 MTL_UTILISATION_RX . . . . . . . . . . 16-24
MA_REQ_FROM_MSC . . . . . . . . . . . 4-103 MTL_UTILISATION_TX . . . . . . . . . . 16-25
MA_REQ_FROM_MSC_FAIL . . . . . . . . . 3-7 MTP_CHANGEBACK . . . . . . . . . . . . . 10-9
MAX_TCH_BUSY. . . . . . . . . . . . . . 17-62 MTP_CHANGEOVER . . . . . . . . . . . . 10-10
MEAN_ARRIVAL_TIME_BETWEEN_CS . . 16-20 MTP_CONGESTION . . . . . . . . . . . . 10-11
MEAN_INTER_ARRIVAL_TIME . . . . . . 16-21 MTP_LINK_INS. . . . . . . . . . . . . . . 10-12
MEAN_TBF_SESSIONS . . . . . . . . . . . 16-22 MTP_LINKFAIL. . . . . . . . . . . . . . . 10-13
MEAN_TCH_BUSY_TIME . . . . . . . . . 16-23 MTP_LOCAL_BUSY . . . . . . . . . . . . 10-14
MEAN_TIME_BETWEEN_DROPS . . . . . 17-64 MTP_LOCAL_MGT . . . . . . . . . . . . . 10-15
MEAN_TIME_BETWEEN_HOs . . . . . . . 17-65 MTP_MGT_INHIBIT . . . . . . . . . . . . 10-16
MMI BSC/BTS statistics MTP_MGT_UNINHIBIT . . . . . . . . . . . 10-17
HO_FAIL_NO_RESOURCES . . . . . . . . 14-2 MTP_MSU_RX . . . . . . . . . . . . . . . 10-18
HO_REQ_MSC_FAIL . . . . . . . . . . . . 14-2 MTP_MSU_TX . . . . . . . . . . . . . . . 10-19
MA_CMD_TO_MS_BLKD . . . . . . . . . 14-2 MTP_NEG_ACKS . . . . . . . . . . . . . . 10-20
OC_SDCCH_FAIL . . . . . . . . . . . . . 14-2 MTP_RE_TX . . . . . . . . . . . . . . . . 10-21
OC_TCH_FAIL . . . . . . . . . . . . . . . 14-2 MTP_REMOTE_MGT . . . . . . . . . . . . 10-22
RF_LOSSES_TCH. . . . . . . . . . . . . . 14-2 MTP_REMOTE_PROC . . . . . . . . . . . 10-23
MMI PCU statistic MTP_RESTORATION . . . . . . . . . . . . 10-24
CELL_FLUSH_REQS . . . . . . . . . . . . 14-2 MTP_SIF_SIO_RX . . . . . . . . . . . . . 10-25
CHANNEL_REQS_REJ . . . . . . . . . . . 14-2 MTP_SIF_SIO_TX. . . . . . . . . . . . . . 10-26
GBL_PAGING_REQS . . . . . . . . . . . . 14-2 MTP_SL_ACK . . . . . . . . . . . . . . . 10-27
GBL_UNAVAILABLE . . . . . . . . . . . . 14-2 MTP_SL_ALIGNMENT . . . . . . . . . . . 10-28
Monitoring faults . . . . . . . . . . . . . . . . 1-17 MTP_SL_CONGESTION . . . . . . . . . . 10-29
MS_ACCESS_BY_TYPE . . . . . . . . . . 4-106 MTP_SL_ERROR_RATE . . . . . . . . . . 10-30
MS_TCH_USAGE_BY_TYPE . . . . . . . . 4-107 MTP_SL_FAIL . . . . . . . . . . . . . . . 10-31
MS_TCH_USAGE_BY_TYPE_PCS . . . . . 4-108 MTP_SL_FIBR . . . . . . . . . . . . . . . 10-32
MSC functions MTP_START_RPO . . . . . . . . . . . . . 10-33
MSC function . . . . . . . . . . . . . . . . 18-4 MTP_STOP_RPO . . . . . . . . . . . . . . 10-34
MSC_OLVD_MSGS_RX MTP_SU_ERROR . . . . . . . . . . . . . . 10-35
Displaying a duration statistic . . . . . . . . . 3-8 MTP_UNAVAILABLE . . . . . . . . . . . . 10-36
MSC_PAGING. . . . . . . . . . . . . . . . 17-63
IX-8 68P02901W56-R
Index
N
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
N2_EXPIRY . . . . . . . . . . . . . . . . . 11-16 Network health statistics (contd.)

Network health statistics . . . . . . . . . . . . 1-3 INTRA_CELL_HO_FAIL_RECOV-
AIR_INTERFACE_BW_CS1 . . . . . . . . . 17-9 ERED . . . . . . . . . . . . . . . . . . . 17-60
AIR_INTERFACE_BW_CS2 . . . . . . . . 17-10 INTRA_CELL_HO_SUCCESS_RATE . . . 17-61
AIR_INTERFACE_BW_CS3 . . . . . . . . 17-11 MAX_TCH_BUSY . . . . . . . . . . . . 17-62
AIR_INTERFACE_BW_CS4 . . . . . . . . 17-12 MEAN_TIME_BETWEEN_DROPS . . . . 17-64
AIR_INTERFACE_PAGING . . . . . . . . 17-13 MEAN_TIME_BETWEEN_HOs . . . . . . 17-65
ASSIGNMENT_SUCCESS_RATE . . . . . 17-14 MSC_PAGING . . . . . . . . . . . . . . 17-63
C_SETUP_SUCCESS_RATE. . . . . 16-7, 17-19 OUT_IN-
C_SUCCESS_RATE . . . . . . . . . . . . 17-22 TER_BSS_HO_FAIL_LOST_MS. . . . . . 17-68
C_VOLUME . . . . . . . . . . . . . . . 17-23 OUT_INTER_BSS_HO_FAIL_RECOV-
CALL_SETUP_RF_ASSIGN- ERED . . . . . . . . . . . . . . . . . . . 17-69
MENT_FAIL_RATE_LOST_MS . . . . . . 17-15 OUT_INTER_BSS_HO_SUC-
CALL_SETUP_RF_ASSIGN- CESS_RATE . . . . . . . . . . . . . . . 17-70
MENT_FAIL_RATE_RECOV- OUT_IN-
ERED_MS . . . . . . . . . . . . . . . . 17-17 TER_CELL_HO_FAIL_RATE_LOST_MS . . 17-71
CALL_SETUP_RF_ASSIGNMENT_SUC- OUT_INTER_CELL_HO_FAIL_RATE_RECOV-
CESS_RATE . . . . . . . . . . . . . . . 17-18 ERED_MS . . . . . . . . . . . . . . . . 17-72
CELL_CONGESTION_TIME . . . . . . . 17-24 OUT_INTER_CELL_HO_SUC-
CELL_UPDATE . . . . . . . . . . . . . . 17-25 CESS_RATE . . . . . . . . . . . . . . . 17-73
DL_AIR_INTERFACE_BW_CS1 . . . . . 17-26 OUT_INTER_CELL_HO_SUCCESS_RATE_RE-
DL_AIR_INTERFACE_BW_CS2 . . . . . 17-27 COVERED_MS . . . . . . . . . . . . . . 17-74
DL_AIR_INTERFACE_BW_CS3 . . . . . 17-28 OUT_IN-
DL_AIR_INTERFACE_BW_CS4 . . . . . 17-29 TRA_BSS_HO_FAIL_LOST_MS . . . . . 17-75
DROP_C_RATE . . . . . . . . . . . . . . 17-30 OUT_INTRA_BSS_HO_FAIL_RECOV-
GPRS performance. . . . . . . . . . . . . . 17-3 ERED_MS . . . . . . . . . . . . . . . . 17-76
GPRS_DL_ACT_TS . . . . . . . . . . . . 17-32 OUT_INTRA_BSS_HO_SUC . . . . . . . 17-77
GPRS_UL_ACT_TS . . . . . . . . . . . . 17-33 OUTGOING_HO_VOLUME . . . . . . . . 17-78
handover performance . . . . . . . . . . . . 17-3 paging performance . . . . . . . . . . . . . 17-7
health check . . . . . . . . . . . . . . . . . 17-6 PAGING_COMPRESSION_RATE . . . . . 17-79
HO_CAUSE_ADJ_CH_INTERF . . . . . . 17-34 PAGING_OVERFLOW_RATE . . . . . . . 17-80
HO_CAUSE_BAND_HO . . . . . . . . . 17-35 PAGING_RESPONSE . . . . . . . . . . . 17-81
HO_CAUSE_BAND_REASSGN . . . . . . 17-36 PAGING_SUCCESS_RATE . . . . . . . . 17-82
HO_CAUSE_CONGEST. . . . . . . . . . 17-37 PERCENTAGE_INTER_BSS_HO . . . . . 17-83
HO_CAUSE_DISTANCE . . . . . . . . . 17-38 PERCENTAGE_INTRA_BSS_HO . . . . . 17-84
HO_CAUSE_DLINTERF . . . . . . . . . 17-39 PERCENTAGE_INTRA_CELL_HO . . . . 17-85
HO_CAUSE_DLLEVEL . . . . . . . . . . 17-40 radio performance reports. . . . . . . . . . . 17-7
HO_CAUSE_DLQUAL . . . . . . . . . . 17-41 RANKING_FORMULA . . . . . . . . . . 17-86
HO_CAUSE_PWRBGT . . . . . . . . . . 17-42 RF_ASSIGN_FAIL_RATE_LOST_MS . . . 17-88
HO_CAUSE_UPINTERF . . . . . . . . . 17-43 RF_ASSIGN_FAIL_RATE_RECOV-
HO_CAUSE_UPLEVEL . . . . . . . . . . 17-44 ERED . . . . . . . . . . . . . . . . . . . 17-89
HO_CAUSE_UPQUAL . . . . . . . . . . 17-45 RF_ASSIGNMENT_SUCCESS_RATE . . . 17-90
HO_PER_C . . . . . . . . . . . . . . . . 17-46 SDCCH congestion . . . . . . . . . . . . . 17-8
IN_INTER_BSS_HO_SUC. . . . . . . . . 17-52 SDCCH_ACCESSES . . . . . . . . . . . 17-91
IN_INTER_CELL_HO_SUC . . . . . . . . 17-53 SDCCH_BLOCKING_RATE . . . . . . . . 17-92
IN_INTRA_BSS_HO_SUC . . . . . . . . 17-54 SDCCH_CONGESTION_TIME . . . . . . 17-93
INCOMING_HO_VOLUME . . . . . . . . 17-55 SDCCH_TRAFFIC_CARRIED . . . . . . . 17-94
INTERNAL_LOST . . . . . . . . . . . . 17-56 SDCCH_USAGE_ACCESS_FAILURE . . . 17-96
INTERNAL_RECOVERED . . . . . . . . 17-57 SDCCH_USAGE_CALL_REESTAB-
INTERNAL_SUCCESS . . . . . . . . . . 17-58 LISH . . . . . . . . . . . . . . . . . . . 17-97
INTRA_CELL_HO_FAIL_LOST_MS . . . 17-59 SDCCH_USAGE_EMER-
GENCY_CALL . . . . . . . . . . . . . . 17-98
68P02901W56-R IX-9
Index
Network health statistics (contd.) network interface statistics (contd.)

SDCCH_USAGE_IMSI_DETACH . . . . . 17-99 L_SCCP_MSGS . . . . . . . . . . . . . . . 13-5
SDCCH_USAGE_LOCATION_UP- L_SCCP_MSGS_RX. . . . . . . . . . . . . 13-6
DATE . . . . . . . . . . . . . . . . . . . 17-100 L_SCCP_MSGS_TX. . . . . . . . . . . . . 13-7
SDCCH_USAGE_MS_ORIGI- L_SIF_SIO_RX_OPC . . . . . . . . . . . . 13-8
NATED_CALL . . . . . . . . . . . . . . 17-101 L_SIF_SIO_TX_OPC . . . . . . . . . . . . 13-9
SDCCH_USAGE_MS_ORIGI- L_SIF_SIO_TYPE . . . . . . . . . . . . . 13-10
NATED_SMS . . . . . . . . . . . . . . . 17-102 LMTP_CHANGEBACK . . . . . . . . . . . 8-7
SDCCH_USAGE_PAGING_RE- LMTP_CHANGEOVER . . . . . . . . . . . 8-8
SPONSE . . . . . . . . . . . . . . . . . 17-104 LMTP_CONGESTION_LOST_MSU . . . . . 8-5
SDCCH_USAGE_SMS . . . . . . . . . . 17-105 LMTP_LINK_INS . . . . . . . . . . . . . . 8-10
SDCCH_USAGE_SMS_ORIGI- LMTP_LINKFAIL . . . . . . . . . . . . . . 8-11
NATED_SS . . . . . . . . . . . . . . . . 17-103 LMTP_LOCAL_BUSY . . . . . . . . . . . 8-12
SPILL_OVER_FACTOR_ATTEMPTS_AT_CON- LMTP_LOCAL_MGT . . . . . . . . . . . . 8-13
GESTION_RELIEF . . . . . . . . . . . . 17-106 LMTP_LOCAL_SL_CONGESTION . . . . . 8-9
SPILL_OVER_FACTOR_DI- LMTP_MGT_INHIBIT . . . . . . . . . . . 8-14
RECTED_RETRY . . . . . . . . . . . . . 17-107 LMTP_MGT_UNINHIBIT . . . . . . . . . . 8-15
SPILL_OVER_FACTOR_MULTI- LMTP_MSU_DISCARDED . . . . . . . . . 8-6
BAND . . . . . . . . . . . . . . . . . . 17-108 LMTP_MSU_RX . . . . . . . . . . . . . . 8-16
TCH congestion . . . . . . . . . . . . . . . 17-8 LMTP_MSU_TX . . . . . . . . . . . . . . 8-17
TCH_ACCESSES . . . . . . . . . . . . . 17-109 LMTP_NEG_ACKS . . . . . . . . . . . . . 8-18
TCH_CONGESTION_TIME . . . . . . . . 17-111 LMTP_RE_TX . . . . . . . . . . . . . . . 8-19
TCH_CONGESTION_TIME_IN- LMTP_REMOTE_MGT . . . . . . . . . . . 8-20
NER_ZONE . . . . . . . . . . . . . . . . 17-112 LMTP_REMOTE_PROC. . . . . . . . . . . 8-21
TCH_CONGES- LMTP_RESTORATION . . . . . . . . . . . 8-22
TION_TIME_OUTER_ZONE . . . . . . . 17-113 LMTP_SIF_SIO_RX. . . . . . . . . . . . . 8-23
TCH_RF_LOSS_RATE . . . . . . 16-43, 17-114 LMTP_SIF_SIO_TX . . . . . . . . . . . . . 8-24
UL_AIR_INTERFACE_BW_CS1 . . . . . 17-118 LMTP_SL_ACK. . . . . . . . . . . . . . . 8-25
UL_AIR_INTERFACE_BW_CS2 . . . . . 17-119 LMTP_SL_ALIGNMENT . . . . . . . . . . 8-26
UL_AIR_INTERFACE_BW_CS3 . . . . . 17-120 LMTP_SL_CONGESTION. . . . . . . . . . 8-27
UL_AIR_INTERFACE_BW_CS4 . . . . . 17-121 LMTP_SL_ERROR_RATE. . . . . . . . . . 8-28
UPLINK_PDTCH_BLOCKING_RATE . . . 17-122 LMTP_SL_FAIL. . . . . . . . . . . . . . . 8-29
network interface statistics LMTP_SL_FIBR . . . . . . . . . . . . . . 8-30
BSSLAP_ABORT_RCV . . . . . . . . . . . 9-4 LMTP_START_RPO. . . . . . . . . . . . . 8-31
BSSLAP_ABORT_SENT . . . . . . . . . . 9-5 LMTP_STOP_RPO . . . . . . . . . . . . . 8-32
BSSLAP_MS_POS_CMD . . . . . . . . . . 9-6 LMTP_SU_ERROR . . . . . . . . . . . . . 8-33
BSSLAP_MS_POS_RESP . . . . . . . . . . 9-7 LMTP_UNAVAILABLE . . . . . . . . . . . 8-34
BSSLAP_REJ . . . . . . . . . . . . . . . . 9-8 NO_PDTCH_AVAIL . . . . . . . . . . . . . 12-123
BSSLAP_RESET . . . . . . . . . . . . . . 9-9 NO_PDTCH_AVAIL_TIME . . . . . . . . . 12-124
BSSLAP_TA_REQ . . . . . . . . . . . . . 9-10 Normal distribution statistics . . . . . . . . . . 1-9
BSSLAP_TA_RESP . . . . . . . . . . . . . 9-11 Bins. . . . . . . . . . . . . . . . . . . . . 1-9
BSSLAP_TOA_REQ . . . . . . . . . . . . 9-12 Histogram . . . . . . . . . . . . . . . . . . 1-9
BSSMAP_CONLESS_INFO_RCV . . . . . . 9-13 Interval expiry . . . . . . . . . . . . . . . . 1-9
BSSMAP_CONLESS_INFO_SENT . . . . . 9-14 Mean value . . . . . . . . . . . . . . . . . 1-9
BSSMAP_PERF_LOC_ABORT_MSGS . . . 9-15 NOTIF_RESP . . . . . . . . . . . . . . . . 4-125
BSSMAP_PERF_LOC_REQ_MSGS . . . . . 9-16 NUM_CELL_RESEL_CELL . . . . . . . . . 4-111
BSSMAP_PERF_LOC_RESP_MSGS. . . . . 9-17 NUM_CELL_RESEL_CELL_PCCN . . . . . 4-112
BSSMAPLE_CONLESS_INFO_RCV . . . . 9-18 NUM_CELL_RESEL_CELL_SUCC . . . . . 4-113
BSSMAPLE_CONLESS_INFO_SENT . . . . 9-19 NUM_CELL_RESEL_NEI . . . . . . . . . . . 5-11
BSSMAPLE_PERF_LOC_ABORT_MSGS . . 9-20 NUM_CELL_RESEL_NEI_PCCN . . . . . . . 5-12
BSSMAPLE_PERF_LOC_REQ_MSGS. . . . 9-21 NUM_CELL_RESEL_NEI_SUCC . . . . . . . 5-13
BSSMAPLE_PERF_LOC_RESP_MSGS . . . 9-22 NUM_EMERG_ACCESS . . . . . . . . . . 4-114
L_ROUTING_SYNTAX . . . . . . . . . . . 13-3 NUM_EMERG_REJECTED . . . . . . . . . 4-115
L_ROUTING_UNKNOWN . . . . . . . . . 13-4
IX-10 68P02901W56-R
Index
NUM_EMERG_TCH_KILL . . . . . . . . . 4-116 NUM_HO_TO_3G_RES_ALLOC_SUCC . . . 4-121

NUM_EMERG_TERM_SDCCH . . . . . . . 4-117 NUM_HO_TO_3G_SUCCESS . . . . . . . . 4-122,
NUM_HO_3G_ATTEMPTS . . . . . . . . . 4-118 17-66 to 17-67
NUM_HO_FROM_3G_ATTEMPTS . . . . . 4-119 NUM_MULTIRAT_MS_ORIG_CALL . . . . 4-123
NUM_HO_FROM_3G_SUCCESS . . . . . . 4-120 NUM_T3121_EXPIRY . . . . . . . . . . . . 4-124
O
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
OK_ACC_PROC. . . . . . . . . . 4-125, 9-2 to 9-3 OUT_INTER_CELL_HO_FAIL_RATE_RECOV-

OK_ACC_PROC_SUC_RACH . . . . . . . . 4-127 ERED_MS. . . . . . . . . . . . . . . . . . 17-72
OUT_HO_CAUSE_ATMPT . . . . . . . . . 4-128 OUT_INTER_CELL_HO_SUC-
OUT_HO_NC_CAUSE_ATMPT . . . . . . . . 5-14 CESS_RATE. . . . . . . . . . . . . . . . . 17-73
OUT_HO_NC_SUC . . . . . . . . . . . . . . 5-16 OUT_INTER_CELL_HO_SUCCESS_RATE_RECOV-
OUT_INTER_BSS_EQUIP_FAIL. . . . . . . 4-130 ERED_MS. . . . . . . . . . . . . . . . . . 17-74
OUT_INTER_BSS_HO . . . . . . . . . . . 4-130 OUT_INTRA_BSS_EQUIP_FAIL . . . . . . 4-132
OUT_INTER_BSS_HO_ATMPT . . . . . . . 4-130 OUT_INTRA_BSS_HO . . . . . . . . . . . 4-132
OUT_INTER_BSS_HO_CLEARED . . . . . 4-130 OUT_INTRA_BSS_HO_ATMPT . . . . . . . 4-132
OUT_INTER_BSS_HO_FAIL . . . . . . . . 4-130 OUT_INTRA_BSS_HO_CLEARED . . . . . 4-132
OUT_INTER_BSS_HO_FAIL_LOST_MS. . . 17-68 OUT_INTRA_BSS_HO_FAIL_LOST_MS . . 17-75
OUT_INTER_BSS_HO_FAIL_RECOV- OUT_INTRA_BSS_HO_FAIL_RECOV-
ERED . . . . . . . . . . . . . . . . . . . . 17-69 ERED_MS. . . . . . . . . . . . . . . . . . 17-76
OUT_INTER_BSS_HO_LOSTMS . . . . . . 4-130 OUT_INTRA_BSS_HO_LOSTMS . . . . . . 4-132
OUT_INTER_BSS_HO_RETURN . . . . . . 4-130 OUT_INTRA_BSS_HO_PRI_BLK . . . . . . 4-132
OUT_INTER_BSS_HO_SUC. . . . . . . . . 4-130 OUT_INTRA_BSS_HO_REQ . . . . . . . . 4-132
OUT_INTER_BSS_HO_SUCCESS_RATE . . 17-70 OUT_INTRA_BSS_HO_RETURN . . . . . . 4-132
OUT_INTER_BSS_REQ_TO_MSC. . . . . . 4-130 OUT_INTRA_BSS_HO_SUC . . . . . 4-132, 17-77
OUT_IN- OUTER_TO_INNER_ZONE . . . . . 4-202 to 4-203
TER_CELL_FAIL_RATE_LOST_MS . . . . . 17-71 OUTGOING_HO_VOLUME . . . . . . . . . 17-78
P
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
PACCH_PAGE_REQS . . . . . . . . . . . . 12-125 PATH_BALANCE . . . . . . . . . . . . . . . 6-29

PACKET_SYSINFO_REQ . . . . . . . . . . 4-134 PCH_AGCH_Q_LENGTH . . . . . . . . . . 4-139
PACKET_SYSINFO_RESP. . . . . . . . . . 4-136 PCH_Q_PAGE_DISCARD
PAGE_REQ_FROM_MSC . . . . . . . . . . 4-137 PCH_Q_PAGE_DISACRD . . . . . . . . . 4-140
PAGE_REQ_FROM_MSC_FAIL . . . . . . . . 3-9 PCU statistics . . . . . . . . . . . . . . . . . 12-1
PAGE_REQ_FROM_SMLC_FAIL . . . . . . 13-11 Accessibility. . . . . . . . . . . . . . . . . 12-2
PAGE_RESPONSE . . . . . . . . . . . . . 4-125 GBL . . . . . . . . . . . . . . . . . . . . 12-2
PAGES_PER_C . . . . . . . . . . . . . . . . 15-9 Throughput . . . . . . . . . . . . . . . . . 12-4
PAGES_PER_SECOND . . . . . . . . . . . 15-10 Utilisation . . . . . . . . . . . . . . . . . . 12-6
paging performance . . . . . . . . . . . . . . 17-7 PDU_DISCARD_FR . . . . . . . . . . . . . 12-126
PAGING_COMPRESSION_RATE . . . . . . 17-79 PDU_DISCARD_LLC . . . . . . . . . . . . 12-127
PAGING_OVERFLOW_RATE . . . . . . . . 17-80 PERCENTAGE_INTER_BSS_HO . . . . . . 17-83
PAGING_RATE . . . . . . . . . . . . . . . 15-11 PERCENTAGE_INTRA_BSS_HO . . . . . . 17-84
PAGING_REQS_CS . . . . . . . . . . . . . 4-138 PERCENTAGE_INTRA_CELL_HO . . . . . 17-85
PAGING_REQS_PS . . . . . . . . . . . . . 4-138 PFC_ADMISSION . . . . . . . . . . . . . . 4-141
PAGING_REQS_TOT . . . . . . . . . . . . 4-138 PFC_ADMISSION_OTHER . . . . . . . . . 4-143
PAGING_REQUESTS . . . . . . . . . . . . 4-138 PFC_DOWNGRADE_FAILURE . . . . . . . 4-144
PAGING_RESPONSE . . . . . . . . . . . . 17-81 PFC_DOWNGRADE_SUCCESS . . . . . . . 4-146
PAGING_SUCCESS_RATE . . . . . . . . . 17-82
68P02901W56-R IX-11
Index
PFC_PREEMPTIONS . . . . . . . . . . . . 4-148 PS_PAGE_REQS . . . . . . . . . . . . . . 12-131

PFC_REJ_DGRD_PRMPT_CELL . . . . . . 4-150
PFC_REJ_DGRD_PRMPT_PRP . . . . . . . . 7-6
PFC_REJECT_CAUSES . . . . . . . . . . . 4-152
PFC_REJECTION . . . . . . . . . . . . . . 4-155
PFC_REJECTION_OTHER . . . . . . . . . 4-157
PFC_UPGRADE . . . . . . . . . . . . . . . 4-158
phantom RACHs . . . . . . . . . . . . . . . . 19-7
raw statistics affected. . . . . . . . . . . . . 19-9
POWERBDGT. . . . . . . . . . . . . . . . 4-128
PPCH_Q_PAGE_DISCARD
PPCH_Q_PAGE_DISACRD . . . . . . . . 4-160
PREEMPT_CAP . . . . . . . . . . . . . . . 4-161
PRP_LOAD . . . . . . . . . . . . . . . . . 12-129
PRP_PD_DEMAND . . . . . . . . . . . . . . 7-8
Q
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
Questions and answers . . . . . . . . . . . . 19-10
R
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
radio performance reports . . . . . . . . . . . . 17-7 RF_LOSSES_TCH . . . . . . . . . . . 4-164, 6-33

CALL_SETUP_RF_ASSIGN- RF_LOSSES_TCH_HR . . . . . . . . . . . . 6-35
MENT_FAIL_RATE_LOST_MS . . . . . . 17-15 ROC . . . . . . . . . . . . . . . . . . . . . 6-36
CALL_SETUP_RF_ASSIGN- ROUTING_SYNTAX . . . . . . . . . . . . . 3-10
MENT_FAIL_RATE_RECOV- ROUTING_UNKNOWN . . . . . . . . . . . . 3-11
ERED_MS . . . . . . . . . . . . . . . . 17-17 RSL
CALL_SETUP_RF_ASSIGNMENT_SUC- link scenarios . . . . . . . . . . . . . . . 18-63
CESS_RATE . . . . . . . . . . . . . . . 17-18
PERCENTAGE_INTER_BSS_HO . . . . . 17-83
PERCENTAGE_INTRA_BSS_HO . . . . . 17-84
PERCENTAGE_INTRA_CELL_HO . . . . 17-85
RF_ASSIGNMENT_SUCCESS_RATE . . . 17-90
RANKING_FORMULA . . . . . . . . . . . 17-86
Raw statistics . . . . . . . . . . . . . . . . . 1-2
RBER . . . . . . . . . . . . . . . . . . . . . 6-31
RF_ASSIGN_FAIL_RATE_LOST_MS . . . . 17-88
RF_ASSIGN_FAIL_RATE_RECOVERED . . 17-89
RF_ASSIGNMENT_SUCCESS_RATE . . . . 17-90
RF_LOSS_RATE . . . . . . . . . . . . . . 16-26
RF_LOSSES_SD. . . . . . . . . . . . . . . 4-163
S
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
SABM_TX . . . . . . . . . . . . . . . . . 11-17 SDCCH congestion. . . . . . . . . . . . . . . 17-8

SCCP_MSGS . . . . . . . . . . . . . . . . . 3-12 SDCCH_ACCESSES. . . . . . . . . . . . . 17-91
SCCP_MSGS_RX . . . . . . . . . . . . . . . 3-13 SDCCH_BLOCKING_RATE . . . . . . 16-28, 17-92
SCCP_MSGS_TX . . . . . . . . . . . . . . . 3-14 SDCCH_CONGESTION . . . . . . . . . . . 4-166
IX-12 68P02901W56-R
Index
SDCCH_CONGESTION_TIME . . . . . . . 17-93 short message service

SDCCH_MEAN_HOLDING_TIME. . . . . . 16-29 mobile originated . . . . . . . . . . . . . 18-46
SDCCH_RF_LOSS_RATE . . . . . . . . . . 16-30 mobile terminated . . . . . . . . . . . . . 18-47
SDCCH_TRAFFIC_CARRIED . . . . . 16-31, 17-94 SIB_RX . . . . . . . . . . . . . . . . . . . 10-37
SDCCH_USAGE_ACCESS_FAILURE . . . . 17-96 SIB_TX . . . . . . . . . . . . . . . . . . . 10-38
SDCCH_USAGE_CALL_REESTABLISH . . 17-97 SIF_SIO_RX_OPC . . . . . . . . . . . . . . . 3-15
SDCCH_USAGE_EMERGENCY_CALL . . . 17-98 SIF_SIO_TX_OPC . . . . . . . . . . . . . . . 3-16
SDCCH_USAGE_IMSI_DETACH . . . . . . 17-99 SIF_SIO_TYPE . . . . . . . . . . . . . . . . 3-17
SDCCH_USAGE_LOCATION_UPDATE . . . 17-100 SL_CONGESTION . . . . . . . . . . . . . 10-39
SDCCH_USAGE_MS_ORIGI- SL_STOP_CONGESTION . . . . . . . . . . 10-40
NATED_CALL . . . . . . . . . . . . . . . 17-101 SMS
SDCCH_USAGE_MS_ORIGI- ratio per call . . . . . . . . . . . . . . . . 15-12
NATED_SMS . . . . . . . . . . . . . . . . 17-102 SMS_INIT_ON_SDCCH . . . . . . . . . . . 4-171
SDCCH_USAGE_PAGING_RESPONSE . . . 17-104 SMS_INIT_ON_SDCCH_HO_IN . . . . . . . 4-172
SDCCH_USAGE_SMS. . . . . . . . . . . . 17-105 SMS_INIT_ON_TCH . . . . . . . . . . . . 4-174
SDCCH_USAGE_SMS_ORIGI- SMS_NO_BCAST_MSG . . . . . . . . . . . 4-175
NATED_SS . . . . . . . . . . . . . . . . . 17-103 SMS_TO_C_RATIO . . . . . . . . . . . . . 15-12
SECOND_ASSIGN_ATMPT . . . . . . . . . 4-169 SPILL_OVER_FACTOR_ATTEMPTS_AT_CONGES-
SECOND_ASSIGN_SUC . . . . . . . . . . 4-170 TION_RELIEF. . . . . . . . . . . . . . . . 17-106
Setting a statistic interval . . . . . . . . . . . . 2-11 SPILL_OVER_FACTOR_DI-
Setting a threshold . . . . . . . . . . . . . . . 2-15 RECTED_RETRY . . . . . . . . . . . . . . 17-107
counter statistics . . . . . . . . . . . . . . . 2-16 SPILL_OVER_FACTOR_MULTIBAND . . . 17-108
Setting statistic properties . . . . . . . . . . . . 2-15 stat_interval command . . . . . . . . . 2-11 to 2-12
Setting a threshold . . . . . . . . . . . . . . 2-15 stat_mode command . . . . . . . . . . . . . . 2-2
SUCCESS_IMMED_ASSIGN_PROC . . . . . 16-33
SUCCESS_INTERNAL_HO . . . . . . . . . 16-34
T
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
TBF_DL_ASGN_PACCH . . . . . . . . . . 12-132 TCH_DELAY . . . . . . . . . . . . . . . . 4-180

TBF_DROP_RATE_ON_PACCH_LOST . . . 16-35 TCH_MEAN_ARRIVAL_RATE . . . . . . . 16-39
TBF_REL_PACCH_LOST . . . . . . . . . . 12-133 TCH_MEAN_HOLDING_TIME . . . . . . . 16-40
TBF_SESSIONS . . . . . . . . . . . . . . . 12-134 TCH_PREEMPT_ATMPT . . . . . . . . . . 4-181
TCH congestion . . . . . . . . . . . . . . . . 17-8 TCH_PREEMPT_FAIL_NO_CAND . . . . . 4-183
TCH_ACCESSES . . . . . . . . . . . . . . 17-109 TCH_PREEMPT_FAIL_TIMEOUT . . . . . . 4-184
TCH_ASSIGN_TO_INNER_ZONE . . . . . . 4-202 TCH_PREEMPT_RQD. . . . . . . . . . . . 4-185
to 4-203 TCH_Q_LENGTH . . . . . . . . . . . . . . 4-186
TCH_BLOCKING_RATE . . . . . . . . . . 16-36 TCH_Q_REMOVED . . . . . . . . . . . . . 4-187
TCH_BLOCKING_RATE_INNER_Z . . . . . 16-37 TCH_RF_LOSS_RATE. . . . . . . . 16-43, 17-114
TCH_BLOCKING_RATE_OUTER_Z. . . . . 16-38 TCH_TRAFFIC_CARRIED . . . . . 16-45, 17-116
TCH_CONG_INNER_ZONE . . . . . . . . . 4-176 TCH_USAGE . . . . . . . . . . . . . . . . 4-188
TCH_CONG_INNER_ZONE_HR. . . . . . . 4-177 TCH_USAGE_EXT_RANGE. . . . . . . . . 4-190
TCH_CONGESTION . . . . . . . . . . . . 4-178 TCH_USAGE_INNER_ZONE . . . . . . . . 4-191
TCH_CONGESTION_HR . . . . . . . . . . 4-179 Throughput statistics . . . . . . . . . . . . . 18-80
TCH_CONGESTION_TIME . . . . . . . . . 17-111 TIMER_EXP_PAP_CONV . . . . . . . . . . 4-192
TCH_CONGESTION_TIME_IN- TOTAL_CS . . . . . . . . . . . . . . . . . 4-194
NER_ZONE . . . . . . . . . . . . . . . . . 17-112 TOTAL_CS_KEY . . . . . . . . . . . . . . 16-47
TCH_CONGES- TOTAL_GCI_FOR_PD_DEMAND . . . . . . . 7-9
TION_TIME_OUTER_ZONE . . . . . . . . 17-113
68P02901W56-R IX-13
Index
U
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
U_BER . . . . . . . . . . . . . . . . . . . . 6-37 UL_LLC_TRAFFIC_VOLUME_INDICA-

UL_AIR_INTERFACE_BW_CS1 . . . . . . . 17-118 TOR. . . . . . . . . . . . . . . . . . . . . 16-48
UL_AIR_INTERFACE_BW_CS2 . . . . . . . 17-119 UL_PDTCH_Q_LENGTH . . . . . . . . . . 12-163
UL_AIR_INTERFACE_BW_CS3 . . . . . . . 17-120 UL_PDTCH_SEIZURE . . . . . . . . . . . 12-164
UL_AIR_INTERFACE_BW_CS4 . . . . . . . 17-121 UL_RADIO_BLKS_8PSK_1_TS . . . . . . . 12-165
UL_BLER_CS1 . . . . . . . . . . . . . . . 12-135 UL_RADIO_BLKS_8PSK_2_TS . . . . . . . 12-167
UL_BLER_CS2 . . . . . . . . . . . . . . . 12-137 UL_RADIO_BLKS_GMSK_1_TS . . . . . . 12-169
UL_BLER_CS3 . . . . . . . . . . . . . . . 12-139 UL_RADIO_BLKS_GMSK_2_TS . . . . . . 12-171
UL_BLER_CS4 . . . . . . . . . . . . . . . 12-140 UL_RLC_ACK_NEW_BLKS. . . . . . . . . 12-173
UL_BLER_MCS1 . . . . . . . . . . . . . . 12-142 UL_RLC_RETX_BLKS . . . . . . . . . . . 12-175
UL_BLER_MCS2 . . . . . . . . . . . . . . 12-144 UL_RLC_UNACK_NEW_BLKS . . . . . . . 12-177
UL_BLER_MCS3 . . . . . . . . . . . . . . 12-146 UL_TBF_TIME_8PSK_1_TS . . . . . . . . . 12-179
UL_BLER_MCS4 . . . . . . . . . . . . . . 12-148 UL_TBF_TIME_8PSK_2_TS . . . . . . . . . 12-180
UL_BLER_MCS5 . . . . . . . . . . . . . . 12-150 UL_TBF_TIME_GMSK_1_TS . . . . . . . . 12-181
UL_BLER_MCS6 . . . . . . . . . . . . . . 12-152 UL_TBF_TIME_GMSK_2_TS . . . . . . . . 12-182
UL_BLER_MCS7 . . . . . . . . . . . . . . 12-154 UNSUCCESS_INTER-
UL_BLER_MCS8 . . . . . . . . . . . . . . 12-156 NAL_HO_NOREEST . . . . . . . . . . . . 16-49
UL_BLER_MCS9 . . . . . . . . . . . . . . 12-158 UNSUCCESS_INTERNAL_HO_REEST . . . 16-50
UL_BUSY_PDTCH . . . . . . . . . . . . . 12-160 UPINTERF . . . . . . . . . . . . . . . . . 4-128
UL_EGPRS_BACKHAUL_DEMAND . . . . . 6-39 UPLEVEL . . . . . . . . . . . . . . . . . . 4-128
UL_EGPRS_BACKHAUL_USED . . . . . . . 6-40 UPLINK_PATH_LOSS . . . . . . . . . . . . . 6-41
UL_LLC_DATA_VOLUME . . . . . . . . . 4-195 UPLINK_PDTCH_BLOCKING_RATE . . . . 17-122
UL_LLC_FRAMES . . . . . . . . . . . . . 12-162 UPQUAL . . . . . . . . . . . . . . . . . . 4-128
V
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
VGCS_FR_TCH_BUSY . . . . . . . . . . . 4-197 VGCS_VBS_ASSIGN_RESULT . . . . . . . 4-201

VGCS_HR_TCH_BUSY . . . . . . . . . . . 4-198 VGCS_VBS_SETUP . . . . . . . . . . . . . . 3-19
VGCS_TALKER_IND . . . . . . . . . . . . . 3-18 VGCS_VBS_SETUP_ACK . . . . . . . . . . . 3-20
VGCS_VBS_ASSIGN_FAIL . . . . . . . . . 4-199 VGCS_VBS_SETUP_REFUSE . . . . . . . . . 3-21
VGCS_VBS_ASSIGN_REQ . . . . . . 4-187, 4-200
W
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
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
Z
■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■
ZONE_CHANGE_ATMPT . . . . . . . . . . 4-202 ZONE_CHANGE_SUC . . . . . . . . . . . 4-203
IX-14 68P02901W56-R

MotorolaStatistics GSR8

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

MotorolaStatistics GSR8

Caricato da

Copyright:

Formati disponibili

MAINTENANCE INFORMATION

GSM STATISTICS APPLICATION

FIELD TRIAL - UNDER DEVELOPMENT

© 1994 - 2005 Motorola, Inc. 68P02901W56-R

Tel: +44 (0) 1793 565 444

FIELD TRIAL - UNDER DEVELOPMENT 15 Jun 2005

Maintenance Information: GSM Statistics Application

Chapter 1: Introduction to statistics

Chapter 2: Statistical operations

Chapter 3: BSS statistics

Chapter 4: Cell statistics

Chapter 5: Neighbour statistics

Chapter 6: Carrier and timeslot statistics

Chapter 7: GPROC and DPROC statistics

Chapter 8: LMTL statistics

Chapter 9: BSS statistics for Location Services support

Chapter 10: MTL statistics

Chapter 11: CBL, GSL, OML, RSL and XBL statistics

Chapter 12: PCU statistics

Chapter 13: BSS-SMLC statistics

Chapter 14: Web MMI statistics

Chapter 15: Call model statistics

Chapter 16: Key statistics

Chapter 17: Network health reports

Chapter 18: Ladder diagrams

Chapter 19: Impacts on statistics

Figure 1-1: Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Figure 18-38: MS originated short message service (point-to-point) . . . . . . . . . . . . . . . . . . . . 18-46

Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Table 6-9: Bin ranges for ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-36

Table 12-52: Bin ranges for UL_BLER_MCS9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-158

This page intentionally left blank.

Maintenance Information: GSM Statistics

What is Covered In This Manual?

Issue status of this manual

Table 1 Manual version history

Resolution of service requests

The following Service Requests are now resolved in this manual:

Table 2 Service requests resolved in this manual

The following CDCNs are now incorporated in this manual:

Failure to comply with Motorola’s operation, installation and maintenance

The tags have the format: {nnnn} or {nnnnn}

The tags are positioned in text as follows:

New and amended feature information Tag position in text

Special key sequences

CTRL-c Press the Control and c keys at the same time.

Reporting safety issues

Whenever a safety issue arises:

Procedure 1 Safety issue reporting

1 Make the equipment concerned safe, for example by removing power.

Warnings and cautions

A definition and example follow below:

Example and format

Failure to comply with warnings

A definition and example follow below:

Example and format

• Potentially hazardous voltage.

Potentially hazardous voltage

Motorola GSM equipment does not utilise high voltages.

High RF potentials and electromagnetic fields are present in this equipment

When dismantling heavy assemblies, or removing or replacing equipment, a

Do not install substitute parts or perform any unauthorized modification of

Lithium batteries, if subjected to mistreatment, may burst and ignite. Defective

Motorola equipment contains CMOS devices. These metal oxide semiconductor