68p02901w56-L-Uk GSM Statistics Application

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5
INTRODUCTION TO STATISTICS STATISTICAL OPERATIONS BSS STATISTICS CELL STATISTICS NEIGHBOUR STATISTICS
CARRIER AND TIMESLOT GPROC AND DPROC LMTL STATISTICS BSS STATS FOR LOCATION MTL STATISTICS
STATISTICS STATISTICS SERVICES SUPPORT
CBL, GSL, OML, RSL AND PCU STATISTICS BSS–SMLC STATISTICS WEB MMI STATISTICS CALL MODEL STATISTICS
XBL STATISTICS
CHAPTER 16 CHAPTER 17 CHAPTER 18 CHAPTER 19 INDEX
KEY STATISTICS NETWORK HEALTH LADDER DIAGRAMS IMPACTS ON STATISTICS
REPORTS
MAINTENANCE INFORMATION
GSM STATISTICS APPLICATION
GSM SOFTWARE RELEASE 6
GSR6
68P02901W56-L
68P02901W56-L
GSR6
MAINTENANCE INFORMATION
GSM STATISTICS APPLICATION
GSM SOFTWARE RELEASE 6
Software Release GSR6
Maintenance Information
GSM Statistics Application
E Motorola 1993 - 2003

All Rights Reserved
Printed in the UK.
Maintenance Information: GSM Statistics Application

14 Feb 2003 68P02901W56-L i
GSR6
Copyrights, notices and trademarks
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
and MOTOROLA are registered trademarks of Motorola Inc.

Intelligence Everywhere, M-Cell and Taskfinder are trademarks of Motorola Inc.
All other brands and corporate names are trademarks of their respective owners.
.
.
.

ii 68P02901W56-L 14 Feb 2003
GSR6
Contents
Issue status of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Motorola manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
GMR amendment record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 1
Introduction to statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
Introduction to GSM Statistics Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Network management and planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Network health statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Custom statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Statistic terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Types of raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Counter array statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Gauge statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–7
Duration statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–8
Normal distribution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
Weighted distribution statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–10
Statistic usages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Quality of service monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Service accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–12
Service integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–13
Service retainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–14
Fault finding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–14
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
Network planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
Installation and commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
Ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
About ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
Chapter 2
Statistical operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Statistical operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Introduction to statistical operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Enabling/disabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Default enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Enabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Disabling a statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–5

14 Feb 2003 68P02901W56-L iii
GSR6
Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Displaying all enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
Displaying statistic values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–8
Setting the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Displaying the statistic interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Displaying the statistic interval start times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12
Setting statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Setting a threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Setting bin ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Displaying statistic properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Displaying a counter statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Displaying a gauge statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Displaying a distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–18
Displaying a counter array statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–19
Displaying a duration statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–20
Chapter 3
BSS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Introduction to BSS Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
BSS C7 utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Enhanced full rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
SCCP performance and utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–3
EFR_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4
HO_REQ_MSC_PROTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5
INTRA_BSS_HO_CAUSE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–6
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
SCCP_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–14
SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–15
SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16
SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–17

iv 68P02901W56-L 14 Feb 2003
GSR6
Chapter 4
Cell statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Introduction to Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Call clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Concentric cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3
Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Emergency call access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
Extended range cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4
General handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Intra-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
Multiband . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5
TCH assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
Usage congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6
DYNET failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
Interference bands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–7
ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–8
ACCESS_PER_PCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–9
ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
ALLOC_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–11
ALLOC_SDCCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–12
ALLOC_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–13
ALLOC_TCH_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–14
ASSIGNMENT_REDIRECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
AVAILABLE_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–16
AVAILABLE_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–17
BAD_HO_REFNUM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–18
BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
BUSY_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–22
CALL_SP_VERS_REQUEST_MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–23
CALLS_QUEUED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–24
CHAN_REQ_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–25
CHAN_REQ_MS_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26
CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–27
CIPHER_MODE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28
CLASSMK_UPDATE_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–29
CLR_CMD_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–30
CLR_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–31
CONGEST_EXIST_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–33
CONGEST_STAND_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–34

14 Feb 2003 68P02901W56-L v
GSR6
CONN_REFUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–35
CONN_REQ_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–36
DYNET_ASSIGN_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–37
DYNET_CALL_REJECTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–38
ER_INTRA_CELL_HO_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–39
ER_INTRA_CELL_HO_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–40
FLOW_CONTROL_BARRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–41
HO_FAIL_NO_RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–42
HO_REQ_MSC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–43
HO_REQ_MSC_OK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–44
IDLE_TCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–45
IN_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–50
IN_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–51
INTERBAND_ACTIVITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–52
INTRA_CELL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–53
INV_EST_CAUSE_ON_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–55
MA_CMD_TO_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–56
MA_COMPLETE_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–57
MA_COMPLETE_TO_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–58
MA_FAIL_FROM_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–59
MA_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–60
MA_CMD_TO_MS_BLKD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–61
MS_ACCESS_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–62
MS_TCH_USAGE_BY_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–63
MS_TCH_USAGE_BY_TYPE_PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–64
MT_LCS_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–65
NUM_EMERG_ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–66
NUM_EMERG_REJECTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–67
NUM_EMERG_TCH_KILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–68
NUM_EMERG_TERM_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–69
OK_ACC_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–70
OK_ACC_PROC_SUC_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–72
OUT_HO_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–73
OUT_INTER_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–75
OUT_INTRA_BSS_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–77

vi 68P02901W56-L 14 Feb 2003
GSR6
PAGE_REQ_FROM_MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–79
PAGING_REQUESTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–80
PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–81
PCH_Q_PAGE_DISCARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–82
RF_LOSSES_SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–83
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–84
SDCCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–85
SECOND_ASSIGN_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–86
SECOND_ASSIGN_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–87
SMS_INIT_ON_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–88
SMS_INIT_ON_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–89
SMS_NO_BCAST_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–90
TCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–91
TCH_CONG_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–92
TCH_DELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–93
TCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–94
TCH_Q_REMOVED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–95
TCH_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–96
TCH_USAGE_EXT_RANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–98
TCH_USAGE_INNER_ZONE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–99
TOTAL_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–100
ZONE_CHANGE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–101
ZONE_CHANGE_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–102
Chapter 5
Neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Introduction to Neighbour Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Neighbour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Outgoing neighbour cell statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
Incoming neighbour statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4
Examples of notation and initial situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–6
IN_INTRA_BSS_NC_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–9
IN_INTRA_BSS_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–10
OUT_HO_NC_CAUSE_ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11
OUT_HO_NC_SUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–13
Chapter 6
Carrier and timeslot statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–1
Carrier and timeslot statistics introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
Description of carrier statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–3
ALLOC_SDCCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–4
ALLOC_TCH_CARR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–5

14 Feb 2003 68P02901W56-L vii
GSR6
BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–6
CHAN_DL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–7
CHAN_REQ_MS_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–8
CHAN_UL_TX_PWR_LVL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–9
FER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–13
RBER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
RF_LOSSES_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–16
ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
U_BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–18
UPLINK_PATH_LOSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–19
Chapter 7
GPROC and DPROC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–1
GPROC and DPROC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–3
CPU_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–4
Chapter 8
LMTL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–1
Introduction to LMTL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–3
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
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

viii 68P02901W56-L 14 Feb 2003
GSR6
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_SIB_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–36
LMTP_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–37
Chapter 9
BSS statistics for Location Services support . . . . . . . . . . . . . . . . . . . . . . . . . 9–1
Introduction to BSS statistics for supported location services . . . . . . . . . . . . . . . . . . . . . 9–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–3
BSSMAP_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–4
BSSMAP_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
BSSMAP_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–6
BSSMAPLE_PERF_LOC_REQ_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–7
BSSMAPLE_PERF_LOC_ABORT_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–8
BSSMAPLE_PERF_LOC_RESP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–9
BSSLAP_TA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–10
BSSLAP_TA_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–11
BSSLAP_TOA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–12
BSSLAP_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–13
BSSLAP_RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–14
BSSLAP_ABORT_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–15
BSSLAP_ABORT_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–16
BSSLAP_MS_POS_CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–17
BSSLAP_MS_POS_RESP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–18
BSSMAP_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–19
BSSMAP_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–20
BSSMAPLE_CONLESS_INFO_RCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–21
BSSMAPLE_CONLESS_INFO_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9–22
Chapter 10
MTL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–1
Introduction to MTL Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3

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

x 68P02901W56-L 14 Feb 2003
GSR6
ATER_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–6
FRMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–8
I_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–9
I_FRAMES_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–10
INVALID_FRAMES_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11
LAPD_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–12
N2_EXPIRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–13
SABM_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–14
Chapter 12
PCU statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–1
PCU Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
Description of Gb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–3
Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–4
Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
Dynamic allocation statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–5
AIR_DL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–6
AIR_DL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
AIR_UL_CONTROL_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–8
AIR_UL_DATA_BLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
AVAILABLE_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–10
CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–11
CHANNEL_REQS_REC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–12
CHANNEL_REQS_REJECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–13
CHANNEL_REQS_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–14
CODING_SCHEME_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–15
CS12_ON_32K_CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–16
DL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–17
DL_PDTCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–18
DL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–19
DL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–20
GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–21
GBL_DL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22
GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–23
GBL_LINK_INS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–24
GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–25
GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–26
GBL_UL_DATA_THRPUT_HIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–27
GBL_UNAVAILABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–28
GPRS_32K_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–29

14 Feb 2003 68P02901W56-L xi
GSR6
GPRS_32K_DL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–30
GPRS_32K_UL_NOT_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–31
GPRS_ACCESS_PER_AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–32
GPRS_CELL_RESELECT_ATTMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–33
GPRS_CELL_RESELECT_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–34
GPRS_ACCESS_PER_RACH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–35
GPRS_CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–36
GPRS_DYNET_FAILURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–37
GPRS_DYNET_RES_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–38
GPRS_DYNET_SWI_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–39
GPRS_MS_NEIGHBOR_STRONG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–40
GPRS_PCH_AGCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–41
IDLE_PDTCH_INTF_BAND0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–42
IMM_ASSGN_CAUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–47
MS_CLASS_1_10_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–49
MS_CLASS_11_20_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–50
MS_CLASS_21_29_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–51
NO_PDTCH_AVAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–52
NO_PDTCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–53
PRP_LOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–54
UL_BUSY_PDTCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–56
UL_PDTCH_CONGESTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–57
UL_PDTCH_Q_LENGTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–58
UL_PDTCH_SEIZURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–59
Chapter 13
BSS-SMLC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–1
Introduction to BSS-based SMLC statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
BSS C7 utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
SCCP performance & utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–3
PAGE_REQ_FROM_SMLC_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–4
L_ROUTING_SYNTAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–5
L_ROUTING_UNKNOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–6
L_SCCP_MSGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–7
L_SCCP_MSGS_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–8
L_SCCP_MSGS_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–9

xii 68P02901W56-L 14 Feb 2003
GSR6
L_SIF_SIO_RX_OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–10
L_SIF_SIO_TX_DPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–11
L_SIF_SIO_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13–12
Chapter 14
Web MMI statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–1
MMI Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14–3
Chapter 15
Call model statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–1
Introduction to call model statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–3
CALL_DURATION (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–4
CALL_SETUP_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–5
HANDOVERS_PER_CALL (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–6
IMSI_DETACHES_TO_CALL (Id) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–7
INTRA_BSS_HO_TO_ALL_HO (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–8
LOCATION_UPDATE_FACTOR (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–9
LOCATION_UPDATES_TO_CALLS (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–10
PAGES_PER_CALL (PPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–11
PAGES_PER_SECOND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–12
PAGING_RATE (P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–13
SMS_TO_CALL_RATIO (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15–14
Chapter 16
Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–1
Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3
Call summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3
Channel usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–3
RF loss summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
MTL utilisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–4
Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5
ATTEMPT_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–6
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–7
CELL_TCH_ALLOCATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–8
CELL_TCH_ASSIGNMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–9
HANDOVER_FAILURE_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–10
HANDOVER_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–11
MEAN_ARRIVAL_TIME_BETWEEN_CALLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–12
MEAN_INTER_ARRIVAL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–13
MEAN_TCH_BUSY_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–14

14 Feb 2003 68P02901W56-L xiii
GSR6
MTL_UTILISATION_RX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–15
MTL_UTILISATION_TX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–16
RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–17
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–18
SDCCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–19
SDCCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–20
SDCCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–21
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–22
SUCCESS_IMMED_ASSIGN_PROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–23
SUCCESS_INTERNAL_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–24
TCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–25
TCH_MEAN_ARRIVAL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–26
TCH_MEAN_HOLDING_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–27
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–28
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–29
TOTAL_CALLS_KEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–31
UNSUCCESS_INTERNAL_HO_NOREEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–32
UNSUCCESS_INTERNAL_HO_REEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–33
Chapter 17
Network health reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–1
Network health statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–3
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–3
GPRS performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–4
Handover performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–5
Health check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–5
Paging performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–5
Radio performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–6
SDCCH congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–6
TCH congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–6
AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–7
AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–11
ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–12
CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–13
CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–14
CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–15
CELL_UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–16
CS1_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–17
CS1_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–18

xiv 68P02901W56-L 14 Feb 2003
GSR6
CS2_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–19
CS2_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–20
CS3_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–21
CS3_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–22
CS4_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–23
CS4_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–24
DL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–25
DOWNLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–29
DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–30
GBL_AVAILABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–31
GPRS_BW_USAGE_DL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–32
GPRS_BW_USAGE_UL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–33
GPRS_DL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–34
GPRS_UL_ACT_TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–35
GPRS_DL_BANDWIDTH_EFFICIENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–36
GPRS_UL_BANDWIDTH_EFFICIENCY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–37
HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–38
INCOMING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–39
INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–40
INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–41
INTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–42
INTRA_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–43
INTRA_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–44
INTRA_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–45
MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–46
MEAN_TIME_BETWEEN_HOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–47
MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–48
OUT_INTER_BSS_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–49
OUT_INTER_BSS_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–50
OUT_INTER_BSS_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–51
OUT_INTER_CELL_HO_FAIL_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–52
OUT_INTER_CELL_HO_FAIL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–53
OUT_INTER_CELL_HO_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–54
OUTGOING_HO_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–55
PAGING_COMPRESSION_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–56
PAGING_OVERFLOW_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–57

14 Feb 2003 68P02901W56-L xv
GSR6
PAGING_RESPONSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–58
PAGING_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–59
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–60
RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–61
RF_ASSIGN_FAIL_RATE_LOST_MS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–62
RF_ASSIGN_FAIL_RATE_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–63
RF_ASSIGNMENT_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–64
SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–65
SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–66
SDCCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–67
SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–68
TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–69
TCH_CONGESTION_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–70
TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–71
TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–72
UL_AIR_INTERFACE_BW_CS1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–73
UPLINK_PDTCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–77
UPLINK_TRAFFIC_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17–78
Chapter 18
Ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–1
Introduction to ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–3
Description of ladder diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–3
Phone call model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
BSS functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
BSC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
MSC functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
Handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–4
Call procedure milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–6
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–6
Call procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–6
Call setup and handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7
Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7
Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Successful mobile originated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–10
Immediate assignment blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–11
Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–11
Successful mobile terminated call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–12

xvi 68P02901W56-L 14 Feb 2003
GSR6
Assignment to TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–13

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–13
Assignment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–13
Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–14
TCH assignment blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–14
Fail recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–15
Intra-cell handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Handover blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Fail recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–17
Fail lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–17
Inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–18
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–18
Handover blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–19
Fail recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–20
Fail lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–21
Fail lost (mobile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–22
Standard directed retry (external) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–23
Intra-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–24
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–24
Handover- blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–25
Fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–25
Fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–26
Standard directed retry (internal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–27
Call clearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–28
Cipher mode fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–28
RF loss on an SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–28
RF loss on a TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–29
Queueing timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–29
Short message service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–30
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–30
Mobile originated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–30
Mobile terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–30
Congestion Relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–31
Intra-BSS congestion relief . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–31
Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–32
Intra-BSS directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–32
Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–33
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–33
Intra-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–34
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–34
Handover unsuccessful (fail recovered) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–35
Handover unsuccessful (fail recovered due to invalid frequency supported) . . . 18–36
Inter-BSS interband activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–37
Handover unsuccessful fail recovered due to invalid frequency supported . . . . . 18–39

14 Feb 2003 68P02901W56-L xvii
GSR6
Interband assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–40

Interband activity invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . 18–40
Band Reassignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–41
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–41
RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–43
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–43
RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–43
MTL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–44
Introduction to MTL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–44
MTL link (operator initiated outage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–44
MTL link (transition scenarios Part II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–45
MTL link (transition scenarios Part III) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–46
MTL link (transition scenarios Part IV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–47
GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–48
Introduction to GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–48
Accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–53
Introduction to accessibility statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–53
Throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–58
Introduction to throughput statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–58
Chapter 19
Impacts on statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–1
Introduction to EGSM, approximate equality, and phantom RACHs . . . . . . . . . . . . . . . . 19–3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–3
Description of EGSM, approximate equality, and phantom RACHs . . . . . . . . . . . 19–3
Extended GSM (EGSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–4
Overview of EGSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–4
Factors impacting statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–5
Approximate equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–8
Description of Approximate equality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–8
Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–9
Description of Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–9
Diagram of Phantom RACHs procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–9
Process of Phantom RACHs occurrences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–10
Raw statistics affected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–11
Questions and answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–12
Assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–12
Counters and SDCCH reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–12
Dynamic SDCCH configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–12
Established call loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–12
Location update reject . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–13
Phantom RACHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I–1

xviii 68P02901W56-L 14 Feb 2003
GSR6
List of Figures
Figure 1-1 Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9

Figure 1-2 Histogram of a weighted distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . 1–11
Figure 1-3 Diagram of immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–16
Figure 18-1 Diagram of immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–3
Figure 18-2 Handover procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–5
Figure 18-3 Connection establishment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–9
Figure 18-4 Connection establishment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–10
Figure 18-5 Immediate assignment blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–11
Figure 18-6 Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–11
Figure 18-7 Connection establishment (mobile terminated call) successful . . . . . . . . . 18–12
Figure 18-8 TCH assignment successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–13
Figure 18-9 Immediate assignment failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–14
Figure 18-10 TCH assignment blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–14
Figure 18-11 TCH assignment fail-recovered to SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . 18–15
Figure 18-12 Handover (intra-cell) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Figure 18-13 Handover (intra-cell) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–16
Figure 18-14 Handover (intra-cell) fail-recovered to source channel . . . . . . . . . . . . . . . 18–17
Figure 18-15 Handover (intra-cell) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–17
Figure 18-16 Handover (inter-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–18
Figure 18-17 Handover (inter-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–19
Figure 18-18 Handover (inter-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–20
Figure 18-19 Handover (inter-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–21
Figure 18-20 Inter-BSS handover failure with lost mobile . . . . . . . . . . . . . . . . . . . . . . . . 18–22
Figure 18-21 Inter-BSS handover directed retry external . . . . . . . . . . . . . . . . . . . . . . . . . 18–23
Figure 18-22 Handover (intra-BSS) successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–24
Figure 18-23 Handover (intra-BSS) blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–25
Figure 18-24 Handover (intra-BSS) fail-recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–25
Figure 18-25 Handover (intra-BSS) fail-lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–26
Figure 18-26 Intra-BSS handover standard directed retry . . . . . . . . . . . . . . . . . . . . . . . . 18–27
Figure 18-27 BSS initiated call clearing–cipher mode fail . . . . . . . . . . . . . . . . . . . . . . . . . 18–28
Figure 18-28 BSS initiated call clearing (RF loss on an SDCCH) . . . . . . . . . . . . . . . . . . 18–28
Figure 18-29 BSS initiated call clearing (RF loss on a TCH) . . . . . . . . . . . . . . . . . . . . . . 18–29
Figure 18-30 BSS initiated call clearing (queueing timeout) . . . . . . . . . . . . . . . . . . . . . . . 18–29
Figure 18-31 MS originated short message service (point-to-point) . . . . . . . . . . . . . . . . 18–30
Figure 18-32 MS terminated short message service (point-to-point) . . . . . . . . . . . . . . . 18–30
Figure 18-33 Intra-BSS congestion relief handover procedure . . . . . . . . . . . . . . . . . . . . 18–31
Figure 18-34 Intra-BSS directed retry procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–32
Figure 18-35 Access procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–33

14 Feb 2003 68P02901W56-L xix
GSR6
Figure 18-36 Successful intra–BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–34

Figure 18-37 Unsuccessful interband handover with fail–recovered source cell . . . . . 18–35
Figure 18-38 Unsuccessful interband handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–36
Figure 18-39 Successful inter-BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–37
Figure 18-40 Inter-BSS handover unsuccessful with fail–recovered source cell . . . . . 18–38
Figure 18-41 Inter-BSS handover unsuccessful due to invalid frequency supported . . 18–39
Figure 18-42 Invalid frequency at assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–40
Figure 18-43 Intra-BSS handover successful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–41
Figure 18-44 Unsuccessful band reassign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–42
Figure 18-45 RSL link scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–43
Figure 18-46 MTL link scenario (Part I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–44
Figure 18-47 MTL link transition scenarios (Part II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–45
Figure 18-48 MTL link transition scenarios (Part III) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–46
Figure 18-49 MTL link transition scenarios (Part IV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–47
Figure 18-50 GBL_DL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–48
Figure 18-51 GBL_FLOW_CTRL_SENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–49
Figure 18-52 CELL_FLUSH_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–50
Figure 18-53 GBL_PAGING_REQS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–51
Figure 18-54 GBL_UL_DATA_THRPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–52
Figure 18-55 Accessibility CHANNEL_REQ_REJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–53
Figure 18-56 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH . . . . 18–54
Figure 18-57 Accessibility and GBL statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–55
Figure 18-58 MS CLASS statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–56
Figure 18-59 CHANNELS_SWITCHED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–57
Figure 18-60 Uplink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–58
Figure 18-61 Downlink data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–59
Figure 19-1 Approximate equality procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–8
Figure 19-2 Phantom RACHs illustration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–9

xx 68P02901W56-L 14 Feb 2003
GSR6
List of Tables
Table 2-1 Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14

Table 4-1 Default bin ranges for BUSY_SDCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–19
Table 4-2 Default bin ranges for BUSY_TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–20
Table 5-1 Neighbour cell statistics pegged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7
Table 6-1 FER Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–10
Table 6-2 Default bin ranges for INTF_ON_IDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
Table 6-3 Signal level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
Table 6-4 RBER Quality number conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–15
Table 6-5 Bin ranges for ROC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–17
Table 10-1 BUSY CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–5
Table 12-1 AIR_DL_DATA_BLKS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–7
Table 12-2 AIR_UL_DATA_BLKS counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–9
Table 12-3 GBL_DL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–22
Table 12-4 GBL_UL_DATA_THRPUT_HIST bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–27
Table 12-5 GPRS_DYNET_RES_REQS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–38
Table 12-6 GPRS_DYNET_SWI_REQS bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–39
Table 12-7 IMM_ASSGN_CAUSE bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–47
Table 12-8 MS_CLASS_1_10_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–49
Table 12-9 MS_CLASS_11_20_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–50
Table 12-10 MS_CLASS_21_29_REQ bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–51
Table 12-11 Mapping between timeslots pending service and PRP load . . . . . . . . . . . . 12–54
Table 12-12 PRP load range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–54
Table 12-13 UL_BUSY_PDTCH bins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12–56
Table 14-1 Location of MMI PCU real-time stats descriptions . . . . . . . . . . . . . . . . . . . . . 14–3
Table 14-2 Location of MMI BSC/BTS PCU real-time stats descriptions . . . . . . . . . . . . 14–3
Table 16-1 Key statistic descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16–5
Table 18-1 Call setup and handover matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–7
Table 19-1 MS access to a traffic channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–5
Table 19-2 Impact due to increased handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–6
Table 19-3 Impact due to congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19–7

14 Feb 2003 68P02901W56-L xxi
GSR6

xxii 68P02901W56-L 14 Feb 2003
GSR6 Issue status of this manual
Issue status of this manual
Introduction
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 manual issue:
Manual Date of Remarks

issue issue
O 3 Oct 94 Original issue – Software release 1.2.2.x
A 30 Dec 94 Issue A – Software release 1.2.3.x
B 1 Sep 95 Issue B – Software release 1.3.0.x
C 31 May 96 Issue C – Software release 1.4.0.x
D 28 Mar 97 Issue D – Software release 1.4.1.x
E 29 Aug 97 Issue E – GSM Software Release 2
F 27 Apr 98 Issue F – GSM Software Release 3
G 12 Mar 99 Issue G – GSM Software Release 4
H 14 Jul 00 Issue H – GSM Software Release 1.6.1.3
J 31 Jul 01 Issue J – GSM Software Release 5
K 31 May 02 Issue K – GSM Software Release 5.1
L 14 Feb 03 Issue L – GSM Software Release 6

14 Feb 2003 68P02901W56-L 1
Issue status of this manual GSR6
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
Service GMR Remarks

Request Number
SR1006967 N/A Path balance modified.
SR1007637 N/A Congestion relief ladder diag amended.
SR1009375 N/A Ref to stats cols added.
SR1011461 N/A MS_ACCESS_BY_TYPE pegging amended.
SR1016595 N/A MS changed to BTS.
SR1017213 N/A TCH_Q_REMOVED statistic added.
SR1018442 N/A Path balance units changed to db.
SR1019869 N/A Units corrected in Chapter12.
SR1021506 N/A CHANNEL_REQS_REJ modified.
SR1025262 N/A Nomenclature has been addressed in Chapter12.
SR1032732 N/A DYN_POW_INCR_XX_Q, DYN_POW_INCR_XX_L,
DYN_POW_RED_XX removed from Chapter 4.
SR1034257 N/A TOTAL_AIR_DL/UL_AVAILABLE_BW stats modified.
SR1034536 N/A GPRS_CHANNELS_SWITCHED description has been
modified in Chapter 12.
SR1034875 N/A CONGEST_ASSIGN_HO_SUC removed from
formulae. ASSIGNMENT_REDIRECTION included.
SR1037679 N/A ASSIGNMENT_SUCCESS_RATE description included
in Chapter 17.
SR1037681 N/A GBL_DL_DATA_THRPUT,
GBL_DL_DATA_THRPUT_HIST,
GBL_UL_DATA_THRPUT,
GBL_UL_DATA_THRPUT_HIST descriptions modified
in chapter 12.
SR1037304 N/A Chapter 4, INTRA CELL, INTRA/INTER BSS pegging
included.
SR1049283 N/A GPRS_CHANNELS_SWITCHED description has been
SR1053116 N/A GPRS_32K_CHANNELS_SWITCHED,
GPRS_32K_DL_NOT_AVAIL and
GPRS_32K_UL_NOT_AVAIL descriptions have been
SR1053368 N/A Quality of Service explanation included in Chapters 12
and 17.
SR1056850 N/A GPRS_ACCESS_PER_RACH description has been

2 68P02901W56-L 14 Feb 2003
GSR6 General information
General information
Important notice
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).
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.
WARNING 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.
About this manual

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

14 Feb 2003 68P02901W56-L 3
General information GSR6
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.
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

New sentence/s or new or amended text. Immediately before the affected text.
Complete new blocks of text as follows: Immediately after the headings as follows:
S Full sections under a main heading S Main heading
S Full paragraphs under subheadings S Subheading
New or amended complete Figures and After the Figure or Table number and
Tables before the title text.
Warning, Caution and Note boxes. Immediately before the affected text in the
box.
General command syntax, operator input On a separate line immediately above the
or displays (in special fonts). 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: Overview
(68P02901W01), or to the manual System Information: GPRS Overview
(68P02903W01).
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.
Cross references
Throughout this manual, cross references are made to the chapter numbers and section
names. The section name cross references are printed bold 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.

4 68P02901W56-L 14 Feb 2003
GSR6 General information
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.

14 Feb 2003 68P02901W56-L 5
Reporting safety issues GSR6
Reporting safety issues
Introduction
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:
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 68437733 (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.

6 68P02901W56-L 14 Feb 2003
GSR6 Warnings and cautions
Warnings and cautions
Introduction
The following describes how warnings and cautions are used in this manual and in all
manuals of this Motorola manual set.
Warnings
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

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

CAUTION Do not use test equipment that is beyond its due calibration date;
arrange for calibration to be carried out.

14 Feb 2003 68P02901W56-L 7
General warnings GSR6
General warnings
Introduction
Observe the following specific warnings during all phases of operation, installation and
maintenance of the equipment described in the Motorola manuals:
S Potentially hazardous voltage
S Electric shock
S RF radiation
S Laser radiation
S Heavy equipment
S Parts substitution
S Battery supplies
S 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.

8 68P02901W56-L 14 Feb 2003
GSR6 General warnings
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.
Potentially hazardous voltage

WARNING This equipment operates from a hazardous voltage of 230 V
ac single phase or 415 V ac three phase supply. To achieve
isolation of the equipment from the ac supply, the ac 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.
NOTE Motorola GSM equipment does not utilise high voltages.
Electric shock
WARNING 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.
RF radiation
WARNING 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:
S 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.
S CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High
Frequency (10 kHz to 300 GHz).

14 Feb 2003 68P02901W56-L 9
General warnings GSR6
Laser radiation
WARNING 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
WARNING 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 equipments have 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.
Parts substitution
WARNING 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
WARNING Do not wear earth straps when working with standby battery
supplies.
Lithium batteries
WARNING 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.

10 68P02901W56-L 14 Feb 2003
GSR6 General cautions
General cautions
Introduction
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
CAUTION Fibre optic cables must not be bent in a radius of less than
30 mm.
Static discharge
CAUTION Motorola equipment contains CMOS devices. These metal
oxide semiconductor (MOS) devices are susceptible to
damage from electrostatic charge. See the section Devices
sensitve to static in the preface of this manual for further
information.

14 Feb 2003 68P02901W56-L 11
Devices sensitive to static GSR6
Devices sensitive to static
Introduction
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 shorted
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are shorted 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:
S Always wear an earth strap which must be connected to the electrostatic point
(ESP) on the equipment.
S 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.
S Do not wear outer clothing made of nylon or similar man made material. A cotton
overall is preferable.
S 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.
S All metal tools should be used and when not in use they should be placed on an
earthed surface.
S 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.

12 68P02901W56-L 14 Feb 2003
GSR6 Motorola manual set
Motorola manual set
Introduction
The following manuals provide the information needed to operate, install and maintain the
Motorola equipment. CD-ROMs are available, with full navigation, for GSM, and GPRS
manual sets.
Each CD-ROM includes all manuals related to a specified main GSM or GPRS software
release, together with current versions of appropriate hardware manuals. A snapshot
copy of online 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.
Generic GSM manuals

The following are the generic manuals in the GSM manual set, these manuals are
release dependent:
Identification/Order
number Name
68P02901W01 System Information: Overview
68P02901W14 * Operating Information: GSM System Operation
68P02901W19 Operating Information: OMC-R System Administration
68P02901W34** Technical Description: OMC-R Database Schema
68P02901W36 Technical Description: BSS Implementation
68P02901W23 Technical Description: BSS Command Reference
68P02901W17 Installation & Configuration: GSM System Configuration
68P02901W43 Installation & Configuration: BSS Optimization
68P02901W47 Installation & Configuration: OMC-R Clean Install
68P02901W26 Maintenance Information: Alarm Handling at the OMC-R
68P02901W58 Maintenance Information: BSS Timers
68P02901W57 Maintenance Information: Device State Transitions
68P02901W51 Maintenance Information: BSS Field Troubleshooting
68P02901W56 Maintenance Information: GSM Statistics Application
68P02901W72 Software Release Notes: BSS/RXCDR
68P02901W74 Software Release Notes: OMC-R System
* Not on paper - In the OMC-R Online Help as Network Operations.

A snapshot of online help is available on CD-ROM.
** Not on paper - On CD-ROM only.

14 Feb 2003 68P02901W56-L 13
Motorola manual set GSR6
Related GSM manuals

The following are related Motorola GSM manuals:
number Name
68P02900W21 System Information: BSS Equipment Planning
68P02900W22 System Information: DataGen
68P02900W76 Software Release Notes: DataGen
68P02900W25 System Information: GSM Advance Operational Impact
68P02900W36 System Information: Network Health Analyst
68P02900W77 Software Release Notes: Network Health Analyst
68P02900W90 System Information: Cell Optimization (COP)
68P02900W94 System Information: Motorola Analysis and Reporting System
(MARS)
68P02900W69 Software Release Notes: Cell Optimization (COP)
68P02900W68 Software Release Notes: Motorola Analysis and Reporting System
(MARS)
68P02901W10 Operating Information: OMC-R System Administration (OSI)
68P02901W39 Installation & Configuration: OSI Clean Install
68P02901W70 Software Release Notes: OMC-R OSI System
Generic GPRS manuals

The following are the generic manuals in the GPRS manual set, these manuals are
release dependent:
number Name
68P02903W01 System Information: GPRS Overview
68P02903W03 Operating Information: OMC-G System Administration
68P02903W37 Operating Information: GSN System Administration
68P02903W46 Technical Description: OMC-G Database Schema
68P02903W18 * Technical Description: GSN Command Reference
68P02903W47 Installation & Configuration: GSN Clean Install
68P02903W04 Installation & Configuration: OMC-G Clean Install
68P02903W19 * Maintenance Information: Alarm Handling at the OMC-G
68P02903W20 Maintenance Information: GSN Statistics Application
68P02903W76 Software Release Notes: GSN System
68P02903W70 Software Release Notes: OMC-G System
* Not on paper - In the OMC-G Online Help as Alarm Handling and

GSN Commands/Parameters. A snapshot of online help is
available on CD-ROM.

14 68P02901W56-L 14 Feb 2003
GSR6 Motorola manual set
Related GPRS manuals

The following are related Motorola GPRS manuals:
number Name
68P02903W02 System Information: GPRS Equipment Planning
68P02903W38 System Information: GSN Advance Operational Impact
BSS service manuals

The following are the Motorola Base Station Subsystem service manuals, these manuals
are not release dependent. The internal organization and makeup of service manual sets
may vary, they may consist of from one to four separate manuals, but they can all be
ordered using the overall catalogue number shown below:
number Name
68P02901W37 Service Manual: BTS
68P02901W38 Service Manual: BSC/RXCDR
68P02901W75 Service Manual: M-Cell2
68P02901W85 Service Manual: M-Cell6
68P02901W95 Service Manual: M-Cellcity and M-Cellcity+
68P02901W65 Service Manual: M-Cellaccess
68P02901W90 Service Manual: M-Cellmicro
68P02902W36 Service Manual: Horizonmicro
68P02902W15 Service Manual: Horizoncompact
68P02902W06 Service Manual: Horizonmacro Indoor
68P02902W12 Service Manual: Horizonmacro Outdoor
68P02902W61 Service Manual: Horizonmicro2 Horizoncompact2
68P02902W66 Service Manual: Horizonmacro 12 Carrier Outdoor
GPRS service manuals

The following are the Motorola GPRS service manuals, these manuals include the
Packet Control Unit (PCU) service manual which becomes part of the BSS for GPRS:
number Name
68P02903W05 Service Manual:GPRS Support Nodes (GSN)
68P02903W10 Service Manual: Packet Control Unit (PCU)
Order number
The Motorola 68P order (catalogue) number is used to order manuals.
Ordering manuals
All orders for Motorola manuals must be placed with your Motorola Local Office or
Representative. Manuals are ordered using the order (catalogue) number.
Manuals are available on the following media:
Printed hard copy
Electronic:
S On the Motorola service web.
S CD-ROM library produced in support of a major system software release.

14 Feb 2003 68P02901W56-L 15
GMR amendment GSR6
GMR amendment
Introduction to GMRs
Changes to a manual that occur after the printing date are incorporated into the manual
using General Manual Revisions (GMRs). 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:
S 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.
S Motorola service web - Updated at the same time as hard copies.
S CD-ROM - Updated periodically as required.

16 68P02901W56-L 14 Feb 2003
GSR6 GMR amendment record
GMR amendment record
GMR instructions
When a GMR is inserted in this manual, the amendment record below is completed to
record the GMR. Retain the instruction sheet that accompanies each GMR and insert it
in a suitable place in this manual for future reference.
Amendment record
Record the insertion of GMRs in this manual in the following table:
GMR number Incorporated by (signature) Date

01 . .
02 . .
03 . .
04 . .
05 . .
06 . .
07 . .
08 . .
09 . .
10 . .
11 . .
12 . .
13 . .
14 . .
15 . .
16 . .
17 . .
18 . .
19 . .
20 . .
21 . .
22 . .
23 . .
24 . .
25 . .

14 Feb 2003 68P02901W56-L 17
GMR amendment record GSR6

18 68P02901W56-L 14 Feb 2003
Chapter 1
Introduction to statistics

14 Feb 2003 68P02901W56-L 1–1
GSR6

1–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to GSM Statistics Manual
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.
Network management and planning

Network operators may use raw and processed statistics for the following network
management and planning functions:
S Quality of service monitoring.
– Service accessibility.
– Service integrity.
– Service retainability.
S Fault finding.
S Optimization.
S Network planning.
S Installation and commissioning.
Raw statistics
The BSS generates raw statistics for reporting individual network performance. The
OMC-R processes raw statistics to create key, network health and custom statistics.
These statistics include call processing, interface, and processor utilization
measurements.
Call statistics
Call processing functions and features generate statistics that show how the system is
performing.
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.

14 Feb 2003 68P02901W56-L 1–3
Introduction to GSM Statistics Manual GSR6
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:
S Call Summary.
S Channel Usage.
S Connection Establishment.
S RF Loss Summary.
S 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.
The following are the network health report groupings:
S Health check.
S GPRS performance.
S Handover performance.
S TCH congestion.
S SDCCH congestion.
S Paging performance.
S 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

1–4 68P02901W56-L 14 Feb 2003
GSR6 Introduction to GSM Statistics Manual
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_HOLDING_TIME, is specified in seconds. To convert the default
value of 0.5 hours to seconds, multiply the 0.5 hours by 3600.
Interval – A recording 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.
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.

14 Feb 2003 68P02901W56-L 1–5
Types of raw statistics GSR6
Types of raw statistics
Introduction
The BSS reports the following six types of statistics:
S Counter.
S Counter array.
S Gauge.
S Duration.
S Normal distribution.
S 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-L 14 Feb 2003
GSR6 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=0xffff). 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
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
mean and maximum gauge statistic values then resets them to zero.

14 Feb 2003 68P02901W56-L 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:
S 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.
S The BSS saves the duration mean and maximum values then resets them to zero.
S The BSS resets the period counter and cumulative values to zero.
S The BSS stops and resets any active timers.

1–8 68P02901W56-L 14 Feb 2003
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.
NOTE If there are gaps in the bin ranges, some occurrences of reported
events are not included in the bin counts. For example, if the
assigned range of values of two adjacent bins are 10–15 and
17–20, a reported event with a value of 16 is not recorded. The
mean value does not account for the unrecorded event.
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
COUNT 2
0
0 1 2 3 4 5 6 7 8 9
BINS

14 Feb 2003 68P02901W56-L 1–9
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.
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.
NOTE
If there are gaps in the bin ranges, some occurrences of reported events are
not included in the bin counts. For example, if the assigned range of values of
two adjacent bins are 10–15 and 17–20, a reported event with a value of 16 is
not recorded. The mean value does not account for the unrecorded event.
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.
NOTE
The mean for a weighted distribution statistic is not a duration value and is not
calculated using the bin values.

1–10 68P02901W56-L 14 Feb 2003
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
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.

14 Feb 2003 68P02901W56-L 1–11
Statistic usages GSR6
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:
S Mobile registration.
S Mobile paging.
S Network accessibility.
S Call set up time.
S Call release time.
S Call release delay.
Service integrity
Statistics associated with the following processes are used to determine service integrity:
S Call clarity.
S 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:
S Mobile registration and paging.
S Network accessibility.
S Call set up time.
S Call release time.
S Call release delay.
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.

1–12 68P02901W56-L 14 Feb 2003
GSR6 Statistic usages
Network accessibility
A registered MS should be able to access the network. Access denial is divided into
three main categories:
S Call blocking.
– No signalling channel (SDCCH) is available.
– No Traffic Channel (TCH) is available.
S 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).
S 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.
S 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.
S 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.
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:
S Call clarity.
S Lack of interference.
S Correct tones and announcements.

14 Feb 2003 68P02901W56-L 1–13
Statistic usages GSR6
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:
S The base ceases to detect the RF signalling from the mobile.
S The MS fails to reach the target channel on handover.
S The call releases due to equipment failure (MSC, base site, or MS).
S 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.
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:
S Damaged antennas.
S Frequency drift.
S Electromechanical problems.
– Problems with remote combiners.
– Noisy channels.

1–14 68P02901W56-L 14 Feb 2003
GSR6 Statistic usages
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).
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.
NOTE This activity is currently supported via the Call Trace feature

14 Feb 2003 68P02901W56-L 1–15
Ladder diagrams GSR6
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_RACH (SEE NOTE)
IMMEDIATE ASSIGNMENT (AGCH)
TIMEOUT
CHAN_REQ_MS_FAIL
NOTE: RSS Abis does additional filtering of RACH.

1–16 68P02901W56-L 14 Feb 2003
Chapter 2
Statistical operations

14 Feb 2003 68P02901W56-L 2–1
GSR6

2–2 68P02901W56-L 14 Feb 2003
GSR6 Statistical operations
Statistical operations
Introduction to statistical operations

This chapter describes the operations associated with statistics, including:
S Enabling and disabling statistics.
S Displaying enabled statistics on a selected basis.
S Displaying statistic values.
S Setting and displaying statistic intervals.
S Setting and displaying statistic properties.

14 Feb 2003 68P02901W56-L 2–3
Enabling/disabling a statistic GSR6
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.
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:
S ACCESS_PER_PCH.
S ALLOC_SDCCH.
S ALLOC_SDCCH_FAIL.
S ALLOC_TCH.
S ALLOC_TCH_FAIL.
S BUSY_SDCCH.
S BUSY_TCH.
S IN_INTER_BSS_HO.
S IN_INTRA_BSS_HO.
S INTRA_CELL_HO.
S MA_CMD_TO_MS_BLKD.
S MA_REQ_FROM_MSC.
S OK_ACC_PROC.
S OUT_INTER_BSS_HO.
S OUT_INTRA_BSS_HO.
S RF_LOSSES_SD.
S TOTAL_CALLS.
Per timeslot statistics

The default mode at start up for the following per timeslot statistics is enabled:
S RF_LOSSES_TCH.
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: meas_type is: 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

2–4 68P02901W56-L 14 Feb 2003
GSR6 Enabling/disabling a statistic
Example
stat_mode rf_losses_tch on cell_name=mid34a
Where: rf_losses_tch is: meas_type

on enable mode
cell_name=mid34a cell_desc
System response:
COMMAND ACCEPTED
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: meas_type is: the statistic being disabled

off disable mode
being disabled, if required
required
Example
stat_mode mtp_link_ins off
Where: mtp_link_ins is: meas_type

off disable mode
System response:
COMMAND ACCEPTED

14 Feb 2003 68P02901W56-L 2–5
Displaying enabled statistics GSR6
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:
S No argument – A listing of all currently enabled statistics will be presented.
S BSS – A listing of all of the currently enabled BSS-wide statistics will be presented.
S cell_desc – A listing of all of the currently enabled statistics for the specified cell
will be presented.
S location – A listing of all of the currently enabled statistics for the specified site will
be presented.
S 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
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

2–6 68P02901W56-L 14 Feb 2003
GSR6 Displaying enabled statistics
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
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
.
.
.
NOTE The remaining cell statistics follow until all of the enabled
statistics have been displayed.

14 Feb 2003 68P02901W56-L 2–7
Displaying statistic values GSR6
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.
NOTE 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: interval is: 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.
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: 5 is: interval

out_ho_cause_atmpt statistic
5 4 3 2 1 61986 34944 cell_number

2–8 68P02901W56-L 14 Feb 2003
GSR6 Displaying statistic values
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

14 Feb 2003 68P02901W56-L 2–9
Setting the statistic interval GSR6
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.
NOTE The OMC-R can calculate key statistics at 60 minute intervals if

it is configured to handle 60 minute statistic files.
The stat_interval is specified by entering the chg_element command using the

following syntax:
chg_element stat_interval <30 or 60> <location>
Where: stat_interval is: 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

60 60 minutes
0 location
System response:
COMMAND ACCEPTED

2–10 68P02901W56-L 14 Feb 2003
GSR6 Displaying the statistic interval
Displaying the statistic interval
Description
The stat_interval is a non-statistical parameter that is used to specify the interval. The
current interval may be displayed using the disp_element command using the following
syntax:
disp_element stat_interval <location>

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

0 location
System response:
stat_interval = 30

14 Feb 2003 68P02901W56-L 2–11
Displaying the statistic interval start times GSR6
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.
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–12 68P02901W56-L 14 Feb 2003
GSR6 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.
S The alarm threshold may be changed for counter and gauge statistics if an alarm
is associated with the statistic.
S Bin ranges may be changed for normal and weighted statistics.
S 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: meas_type is: a counter or gauge

statistic
whose threshold is being
set, if required
required
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: rf_losses_tch is: 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.

14 Feb 2003 68P02901W56-L 2–13
Setting statistic properties GSR6
Table 2-1 Counter statistics

Statistical name Alarm Valid values Basis
severity
ALLOC_SDCCH_FAIL Major min: 1 cell
max: 2147483647
ALLOC_TCH_FAIL Major min: 1 cell
max: 2147483647
BAD_HO_REFNUM_MS Warning min: 1 cell
max: 2147483647
CALLS_QUEUED Warning min: 1 cell
max: 2147483647
CHAN_REQ_MS_BLK Minor min: 1 cell
max: 2147483647
CHAN_REQ_MS_FAIL Minor min: 1 timeslot
max: 2147483647
CIPHER_MODE_FAIL Minor min: 1 cell
max: 2147483647
CLASSMK_UPDATE_FAIL Minor min: 1 cell
max: 2147483647
CONGESTION_LOST_MSU Warning min: 1 SS7 link
max: 2147483647
FRMR Warning min: 1 X.25 link or
max: 2147483647 LAPD link
HO_REQ_MSC_FAIL Warning min: 1 cell
max: 2147483647
HO_REQ_MSC_PROTO Warning min: 1 BSS
max: 2147483647
INVALID_FRAMES_RX Warning min: 1 X.25 link or
MA_CMD_TO_MS_BLKD Minor min: 1 cell
max: 2147483647
MA_FAIL_FROM_MS Warning min: 1 cell
max: 2147483647
MA_REQ_FROM_MSC_FAIL Warning min: 1 BSS
max: 2147483647
MSU_DISCARDED Warning min: 1 SS7 link
max: 2147483647
MTP_NEG_ACKS Warning min: 1 SS7 link
max: 2147483647
MTP_RE_TX Warning min: 1 SS7 link
max: 2147483647
MTP_SL_ACK Major min: 1 SS7 link
max: 2147483647
MTP_SL_ALIGNMENT Minor min: 1 SS7 link
max: 2147483647
MTP_SL_CONGESTION Major min: 1 SS7 link
max: 2147483647

2–14 68P02901W56-L 14 Feb 2003
GSR6 Setting statistic properties
Statistical name Alarm Valid values Basis

severity
MTP_SL_ERROR_RATE Major min: 1 SS7 link
max: 2147483647
MTP_SL_FAIL Major min: 1 SS7 link
max: 2147483647
MTP_SL_FIBR Major min: 1 SS7 link
max: 2147483647
MTP_START_RPO Warning min: 1 SS7 link
max: 2147483647
MTP_SU_ERROR Warning min: 1 SS7 link
max: 2147483647
N2_EXPIRY Warning min: 1 X.25 link or
PAGE_REQ_FROM_MSC_FAIL Minor min: 1 BSS
max: 2147483647
PCH_Q_PAGE_DISCARD Minor min: 1 cell
max: 2147483647
RF_LOSSES_SD Major min: 1 cell
max: 2147483647
RF_LOSSES_TCH Major min: 1 timeslot
max: 2147483647
ROUTING_SYNTAX Warning min: 1 BSS
max: 2147483647
ROUTING_UNKNOWN Warning min: 1 BSS
max: 2147483647
SL_CONGESTION Warning min: 1 SS7 link
max: 2147483647
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.
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: meas_type is: a normal or weighted
distribution statistic
whose bin range is being
set, if required
required
NOTE The bin ranges for the BER statistic may not be modified.

14 Feb 2003 68P02901W56-L 2–15
Setting statistic properties GSR6
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.
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: busy_tch is: 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: <carriage return>
Enter the max value for bin 1: 7
COMMAND ACCEPTED

2–16 68P02901W56-L 14 Feb 2003
GSR6 Displaying statistic properties
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:
S Alarm severity and threshold values are displayed for counter and gauge statistics.
S Bin ranges are displayed for normal and weighted statistics.
S The cause is displayed for the counter array statistics.
S The mode and type only are displayed for the duration statistics.
Displaying a counter statistic

Counter statistic properties are displayed by entering the disp_stat_prop command
using the following syntax:
disp_stat_prop <meas_type> [<location>] [<cell_desc>]
Where: meas_type is: a counter statistic

whose 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: total_calls is: meas_type

1 location
all all cells at the specified
location
System response:
STATISTIC: TOTAL_CALLS SITE: 1
TYPE: PER CELL OBJECT: COUNTER
ALARM ALARM
CELL # MODE SEVERITY
THRESHOLD
––––––––––––––––––– –––– ––––––––
–––––––––
543 21 61698 (f102h) 34776 (87d8h) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34778 (87dah) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34779 (87dbh) ENABLED NO ALARM N/A
543 21 61698 (f102h) 34780 (87dch) ENABLED NO ALARM N/A

14 Feb 2003 68P02901W56-L 2–17
Displaying statistic properties GSR6
Displaying a gauge statistic

Gauge statistic properties are displayed by entering the disp_stat_prop command using
the following syntax:
Where: meas_type is: a gauge statistic
being displayed, if
required
required
Example
CHANNELS_DISABLED 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: available_tch is: meas_type
1 location
cell_number=5 4 3 2 1 cell_desc
61698 34776
System response:
STATISTIC: AVAILABLE_TCH SITE: 1
TYPE: PER CELL OBJECT: GAUGE
ALARM ALARM
CELL # MODE SEVERITY
THRESHOLD
––––––––––––––––––– –––– ––––––––
–––––––––
Displaying a distribution statistic

Distribution statistic properties are displayed by entering the disp_stat_prop command
Where: meas_type is: a distribution statistic
being displayed, if
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

2–18 68P02901W56-L 14 Feb 2003
GSR6 Displaying statistic properties
Where: busy_tch is: meas_type

1 location
5 4 3 2 1 61698 34776 cell_desc
System response:
STATISTIC: BUSY_TCH SITE: 1
TYPE: PER CELL OBJECT: DISTRIB
CELL # MODE BIN# MIN

MAX
––––––––––––––––––– –––– –––– ––––
––––
543 21 61698 (f102h) 34776 (87d8h) ENABLED 0 0
1
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
Displaying a counter array statistic

Counter array statistic properties are displayed by entering the disp_stat_prop
command using the following syntax:
Where: meas_type is: a counter array statistic
being displayed, if
required
required
Example
OUT_HO_CAUSE_ATMPT statistic.
disp_stat_prop out_ho_cause_atmpt cell_number=5 4 3 2 1 62259
8736
Where: out_ho_cause_atmpt is: meas_type
5 4 3 2 1 62259 8736 cell_desc

14 Feb 2003 68P02901W56-L 2–19
Displaying statistic properties GSR6
System response:
STATISTIC: OUT_HO_CAUSE_ATMPT SITE: 2
TYPE: PER CELL OBJECT: COUNTER ARRAY
BIN# CAUSE
–––– –––––
0 Uplink Quality
1 Uplink Level
2 Downlink Quality
3 Downlink Level
4 Distance
5 Uplink Interference
6 Downlink Interference
7 Power Budget
8 Congestion
9 Adjacent Channel Interference
CELL# MODE
–––––––––––––––––––––––––––––––––––––– ––––
543 21 62259 (f333h) 8736 (2220h) DISABLED
Displaying a duration statistic

Duration statistic properties are displayed by entering the disp_stat_prop command
Where: meas_type is: a duration statistic
being displayed, if
required
required
Example
FLOW_CONTROL_BARRED statistic.
disp_stat_prop flow_control_barred 2 5 4 3 2 1 62259 8736
Where: flow_control_barred is: 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

2–20 68P02901W56-L 14 Feb 2003
Chapter 3
BSS statistics

14 Feb 2003 68P02901W56-L 3–1
GSR6

3–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to BSS Statistics
Introduction to BSS Statistics

Description
This chapter includes descriptions of the BSS statistics. BSS statistics are organized into
four major subgroups:
S BSS C7 utilization.
S Enhanced full rate.
S Intra-BSS handover.
S SCCP performance and utilization.
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:
S SIF_SIO_RX_OPC.
S SIF_SIO_TX_DPC.
S SIF_SIO_TYPE.
Enhanced full rate

A single statistic tracks the number of channel requests by MSs capable of Enhanced
Full Rate (EFR) operation.
S EFR_REQ_FROM_MSC.
Intra-BSS handover
A single counter array statistic tracks the number of successful intra-BSS handovers.
S INTRA_BSS_HO_CAUSE_SUC.
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.
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:
S HO_REQ_MSC_PROTO.
S MA_REQ_FROM_MSC_FAIL.
S MSC_OVLD_MSGS_RX.
S PAGE_REQ_FROM_MSC_FAIL.
S ROUTING_SYNTAX.
S ROUTING_UNKNOWN.
S SCCP_MSGS.
S SCCP_MSGS_RX.
S SCCP_MSGS_TX.

14 Feb 2003 68P02901W56-L 3–3
EFR_REQ_FROM_MSC GSR6
EFR_REQ_FROM_MSC
Description
This statistic tracks the number of channel requests for Enhanced Full Rate (EFR) via
the Assignment Request or any Handover Request from the MSC indicating the MS is
EFR capable.
NOTE More than one Assignment Request or Handover Request may

be received from the MSC for a single call. This may occur when
the channel mode procedure occurs, or when more than one
handover occurs for a call. The incidence of these occurrences
should not significantly impact the validity of this statistic.
Pegging
This statistic is pegged each time an Assignment Request or Handover Request is
received from the MSC indicating that the MS is EFR capable.
Analysis
In systems without the EFR feature, this statistic can be used to determine if the EFR
feature should be acquired, if not currently installed.
In systems with the EFR feature, this statistic can be used to track the number of
channel requests by EFR capable MSs.
Reference None.
Usage Quality of service.

Network planning.
Radio resource allocation.
Basis BSS.
Type Counter.

3–4 68P02901W56-L 14 Feb 2003
GSR6 HO_REQ_MSC_PROTO
HO_REQ_MSC_PROTO
Description
This statistic tracks the number of Handover Request messages received from the MSC
that fail message validation. Validation failure may occur due to protocol errors which
may occur if the message is badly formatted or incompatible database elements exist in
the BSS and MSC.
Pegging
This statistic is pegged each time a Handover Request message from the MSC fails
message validation at the BSS. Currently, this statistic is not pegged.
Analysis
A threshold value should be assigned to this statistic which reflects the maximum number
of message validation failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 17. BSS: HO Request from the MSC
protocol error – PM alarm is generated. Refer to the 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.

14 Feb 2003 68P02901W56-L 3–5
INTRA_BSS_HO_CAUSE_SUC GSR6
INTRA_BSS_HO_CAUSE_SUC
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.
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-L 14 Feb 2003
GSR6 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
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.

14 Feb 2003 68P02901W56-L 3–7
MSC_OVLD_MSGS_RX GSR6
MSC_OVLD_MSGS_RX
Description
This statistic tracks the number of OVERLOAD messages that have been received by
the BSS from the MSC. This statistic pegs independently of the MSC Overload Control
feature being enable 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

Network planning.
Basis BSS.
Type Counter.

3–8 68P02901W56-L 14 Feb 2003
GSR6 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
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 is generated. Refer to the Maintenance Information: Alarm Handling at
the OMC (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.
Usage Quality of service monitoring: Paging analysis.

Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 3–9
ROUTING_SYNTAX GSR6
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 is generated. Refer to the Maintenance Information: 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-L 14 Feb 2003
GSR6 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 troubleshooting information.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 3–11
SCCP_MSGS GSR6
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
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-L 14 Feb 2003
GSR6 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
MSC. This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 3–13
SCCP_MSGS_TX GSR6
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
MSC. This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

3–14 68P02901W56-L 14 Feb 2003
GSR6 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
MSC. This statistic can be used for trend analysis of the activity on all SLs for a
particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Usage MTP C7 utilization.
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 3–15
SIF_SIO_TX_DPC GSR6
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-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 3–17
SIF_SIO_TYPE GSR6

3–18 68P02901W56-L 14 Feb 2003
Chapter 4
Cell statistics

14 Feb 2003 68P02901W56-L 4–1
GSR6

4–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to Cell Statistics
Introduction to Cell Statistics
Description
This chapter includes descriptions of the cell statistics. Cell statistics are organized into
the following groups:
S Call clearing.
S Concentric cell.
S Connection establishment.
S Directed retry.
S Emergency call access.
S Extended range cell.
S General handover.
S Inter-BSS handover.
S Intra-BSS handover.
S Intra-cell handover.
S Multiband.
S TCH assignment.
S Usage congestion.
S DYNET failures.
S Interference bands.
Call clearing
Call clearing statistics track the number calls lost due to RF failures, cipher mode
failures, or procedure timeouts. The following are call clearing statistics:
S CIPHER_MODE_FAIL.
S CLASSMK_UPDATE_FAIL.
S CLR_REQ_TO_MSC.
S CLR_CMD_FROM_MSC.
S RF_LOSSES_SD.
S RF_LOSSES_TCH.
Concentric cell
Concentric cell statistics track concentric cell feature processes. The following are
concentric cell statistics:
S TCH_CONG_INNER_ZONE.
S TCH_USAGE_INNER_ZONE.
S ZONE_CHANGE_ATMPT.
S ZONE_CHANGE_SUC.

14 Feb 2003 68P02901W56-L 4–3
Introduction to Cell Statistics GSR6
Connection establishment
Connection establishment statistics track access, allocation, channel request, and MSC
page request functions. The following are connection establishment statistics:
S ACCESS_PER_AGCH.
S ACCESS_PER_PCH.
S ACCESS_PER_RACH.
S ALLOC_SDCCH.
S ALLOC_SDCCH_FAIL.
S ALLOC_TCH.
S ALLOC_TCH_FAIL.
S CHAN_REQ_CAUSE_ATMPT.
S CHAN_REQ_MS_BLK.
S CHAN_REQ_MS_FAIL.
S CONN_REFUSED.
S CONN_REQ_TO_MSC.
S INV_EST_CAUSE_ON_RACH.
S OK_ACC_PROC.
S OK_ACC_PROC_SUC_RACH.
S PAGE_REQ_FROM_MSC.
Directed retry
Directed retry statistics track congestion processes associated with the directed retry
feature. The following are directed retry statistics:
S CONGEST_EXIST_HO_ATMPT.
S CONGEST_STAND_HO_ATMPT.
Emergency call access

Emergency call access statistics track emergency call processes. The following are
emergency call access statistics:
S NUM_EMERG_ACCESS.
S NUM_EMERG_REJECTED.
S NUM_EMERG_TCH_KILL.
S NUM_EMERG_TERM_SDCCH.
Extended range cell

Extended range statistics track extended range feature processes. The following are
extended range cell statistics:
S ER_INTRA_CELL_HO_ATMPT.
S ER_INTRA_CELL_HO_SUC.
S TCH_USAGE_EXT_RANGE.

4–4 68P02901W56-L 14 Feb 2003
General handover
General handover statistics track processes common to all types of handovers. The
following are handover statistics:
S ASSIGNMENT_REDIRECTION.
S BAD_HO_REFNUM_MS.
S HO_FAIL_NO_RESOURCES.
Inter-BSS handover
Inter-BSS handover statistics track inter-BSS handover processes. The following are
inter-BSS handover statistics:
S HO_REQ_MSC_FAIL.
S HO_REQ_MSC_OK.
S IN_INTER_BSS_HO.
S OUT_INTER_BSS_HO.
Intra-BSS handover
Intra-BSS handover statistics track intra-BSS handover processes. The following are
intra-BSS handover statistics:
S IN_INTRA_BSS_HO.
S OUT_HO_CAUSE_ATMPT
S OUT_INTRA_BSS_HO.
Intra-cell handover
Intra-cell handover statistics track intra-cell handover processes. The following is the
only intra-cell handover statistic:
S INTRA_CELL_HO.
Multiband
Multiband statistics track multiband feature processes. The following are multiband
statistics:
S INTERBAND_ACTIVITY.
S MS_ACCESS_BY_TYPE.
S MS_TCH_USAGE_BY_TYPE.
S MS_TCH_USAGE_BY_TYPE_PCS.
S OUT_HO_CAUSE_ATMPT.

14 Feb 2003 68P02901W56-L 4–5
Introduction to Cell Statistics GSR6
TCH assignment
TCH assignment statistics track successful, unsuccessful, and total traffic channel
assignment processes. The following are TCH assignment statistics:
S MA_CMD_TO_MS.
S MA_CMD_TO_MS_BLKD.
S MA_FAIL_FROM_MS.
S MA_REQ_FROM_MSC.
S TCH_Q_REMOVED.
S TOTAL_CALLS.
Usage congestion
Usage congestion statistics track congestion processes not related to the directed retry
feature. The following are usage congestion statistics:
S AVAILABLE_SDCCH.
S AVAILABLE_TCH.
S BUSY_SDCCH.
S BUSY_TCH.
S BUSY_TCH_CARR.
S CAL_SP_VERS_REQUEST_MONITOR.
S CALLS_QUEUED.
S CLASSMK_UPDATE_FAIL.
S FLOW_CONTROL_BARRED.
S MA_COMPLETE_FROM_MS.
S MA_COMPLETE_TO_MSC.
S MT_LCS_ON_SDCCH.
S PAGING_REQUESTS
S PCH_AGCH_Q_LENGTH.
S PCH_Q_PAGE_DISCARD.
S SDCCH_CONGESTION.
S SECOND_ASSIGN_ATMPT.
S SECOND_ASSIGN_SUC.
S SMS_INIT_ON_SDCCH.
S SMS_INIT_ON_TCH.
S SMS_NO_BCAST_MSG.
S TCH_CONGESTION.
S TCH_DELAY.
S TCH_Q_LENGTH.
S TCH_USAGE.

4–6 68P02901W56-L 14 Feb 2003
DYNET failures
Usage DYNET failures statistics track failures of the DYNET. The following are DYNET
failures statistics:
S DYNET_ASSIGN_FAIL.
S DYNET_CALL_REJECTS.
Interference bands
Interference band statistics track the number of idle TCHs per interference band:
S IDLE_TCH_INTF_BAND0.

14 Feb 2003 68P02901W56-L 4–7
ACCESS_PER_AGCH GSR6
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.
NOTE This statistic is affected by phantom Random Access CHannel

(RACH).The level of congestion on the AGCH cannot be
determined using current statistics

4–8 68P02901W56-L 14 Feb 2003
GSR6 ACCESS_PER_PCH
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.
{3750} This statistic is modified to count both Circuit Switched (CS) and Packet Switch
(PS) paging on Page Channel (PCH).
{3750} 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:
S Succeeded (resulting in channel assignment).
S Failed (did not result in channel assignment).
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.
NOTE 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.

14 Feb 2003 68P02901W56-L 4–9
ACCESS_PER_RACH GSR6
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:
S Succeeded (resulting in channel assignment).
S 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.
NOTE This statistic is affected by phantom RACHs. The counter is

incremented at least once for each phantom RACH.

4–10 68P02901W56-L 14 Feb 2003
GSR6 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:
S Successful handover on an SDCCH channel.
S 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.
NOTE This statistic is affected by phantom RACHs.

14 Feb 2003 68P02901W56-L 4–11
ALLOC_SDCCH_FAIL GSR6
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
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 is generated. Refer to the Maintenance Information: Alarm Handling at
the OMC-R (68P02901W26) for troubleshooting information.
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.

4–12 68P02901W56-L 14 Feb 2003
GSR6 ALLOC_TCH
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 peg for successful TCH allocations within a cell as a result of a call
establishment or hand in attempt:
S Successful allocation due to call establishment including successful allocations due
to directed retries.
S Successful allocation due to intra-cell hand in.
S Successful allocation due to inter-cell/intra-cell hand in.
S Successful allocation due to inter-BSS hand in.
This statistic pegs before the transmission of the assignment/handover command to the
MS and, therefore, does not take into account the success or failure of the
assignment/hand in from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations.
Usage Quality of service monitoring: Call setup.

Network planning.
Ladder: Intra-BSS handover, Inter-BSS
handover, Intra-cell handover, Assignment to
TCH.
Key statistics: TCH_MEAN_ARRIVAL_RATE,
TCH_MEAN_HOLDING_TIME,
CELL_TCH_ASSIGNMENTS,
TCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 4–13
ALLOC_TCH_FAIL GSR6
ALLOC_TCH_FAIL
Description
The ALLOC_TCH_FAIL statistic tracks the number of unsuccessful 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:
S Unsuccessful allocation due to call establishment including unsuccessful
allocations due to directed retries.
S Unsuccessful allocation due to inter-cell/intra cell hand in.
S Unsuccessful allocation due to inter-BSS hand in.
Analysis
of TCH failures due to congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 25. CELL: Attempt at allocating an TCH
failed – PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at
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–14 68P02901W56-L 14 Feb 2003
GSR6 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 (SD –> TCH).
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.

14 Feb 2003 68P02901W56-L 4–15
AVAILABLE_SDCCH GSR6
AVAILABLE_SDCCH
Description
The AVAILABLE_SDCCH statistic tracks the average number of available SDCCHs that
are in use or available for use.
The SDCCH is available when its administrative state is unlocked or shutting down
and its operational state is enabled. The SDCCH is unavailable when its administrative
state is locked and its operational state is disabled.
Pegging
{3750} 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–16 68P02901W56-L 14 Feb 2003
GSR6 AVAILABLE_TCH
AVAILABLE_TCH
Description
{3750} 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.
{3750} This statistic is modified to exclude all PDTCHs, both switchable and reserved
unless the switchable PDTCH is configured as TCH.
{3750} 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.
{3750} 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
{3750} 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.

14 Feb 2003 68P02901W56-L 4–17
BAD_HO_REFNUM_MS GSR6
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
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
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.

4–18 68P02901W56-L 14 Feb 2003
GSR6 BUSY_SDCCH
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-1.
This statistic is affected by phantom RACHs.
Table 4-1 Default bin ranges for BUSY_SDCCH

Bin Range
0 0–0
1 1–2
2 3–4
3 5–6
4 7–8
5 9 – 10
6 11 – 12
7 13 – 14
8 15 – 16
9 17 – 400
Pegging
The individual bin values are incremented by the length of time that the number of
allocated SDCCHs fall within the bin range of values. Bin values are pegged each time a
SDCCH is allocated or de-allocated.
If a TCH is reconfigured as an SDCCH, only the SDCCH statistics will be pegged.
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.

14 Feb 2003 68P02901W56-L 4–19
BUSY_TCH GSR6
BUSY_TCH
Description:
The BUSY_TCH statistic tracks the number of 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.
ranges for the BUSY_TCH statistic are shown in Table 4-2.
Table 4-2 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 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.
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.
cell TCHs. An analysis of the allocation information can be used to determine the

4–20 68P02901W56-L 14 Feb 2003
GSR6 BUSY_TCH
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.

14 Feb 2003 68P02901W56-L 4–21
BUSY_TCH_CARR GSR6
BUSY_TCH_CARR
Description
The BUSY_TCH_CARR statistic tracks the number of 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 TCHs in use is detected.
Analysis
cell TCHs. An analysis of the allocation information can be used to determine the
Reference GSM 12.04, 3.1.0, B1.1.1.

GSM 4.08, 3.8.0, 3.3.1.2.1.
Usage Congestion.
Network planning.
Optimization.
Basis Carrier.
Type Gauge.

4–22 68P02901W56-L 14 Feb 2003
GSR6 CALL_SP_VERS_REQUEST_MONIT OR
CALL_SP_VERS_REQUEST_MONITOR
{3938}
Description
This statistic tracks the number of call rejects and call downgrades due to not supporting
requested speech versions.

0 EFR_REQ_REJECT Pegged when the call is rejected
due to CIC capabilities:
Assignment request for or including
EFR
Handover request for or including
EFR
In-call modification request for or
including EFR
1 EFR_REQ_DOWNGRADE Pegged when the call is
downgraded due to CIC capabilities:
EFR
EFR
including EFR
2 AMR_CALL_REQUEST Pegged when the AMR call is

requested:
AMR
AMR
including AMR
Pegging
The bin corresponding to the cause of the call downgrade or reject is as indicated in
description above.
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.

14 Feb 2003 68P02901W56-L 4–23
CALLS_QUEUED GSR6
CALLS_QUEUED
Description
The CALLS_QUEUED statistic tracks the Assignment 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.
This statistic does not track handovers.
Pegging
This statistic pegs when queueing is enabled in an assignment request and available
queue blocks are used to queue the call successfully.
Analysis
of calls queued for each cell on the BSS that are acceptable in normal system
operations.
If the specified threshold is exceeded, the 20. CELL: Number of calls queued – PM
alarm will be generated. Refer to the Maintenance Information: Alarm Handling at the
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 Counter.
Alarm Warning.

4–24 68P02901W56-L 14 Feb 2003
GSR6 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 {3974}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
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.

14 Feb 2003 68P02901W56-L 4–25
CHAN_REQ_MS_BLK GSR6
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–26 68P02901W56-L 14 Feb 2003
GSR6 CHAN_REQ_MS_FAIL
CHAN_REQ_MS_FAIL
Description
This statistic is the number of times that the BSS times out waiting for the MS to
establish on the SDCCH that was assigned to it during the immediate assignment
procedure (see Chapter 6, Carrier and timeslot statistics, CHAN_REQ_MS_FAIL)

14 Feb 2003 68P02901W56-L 4–27
CIPHER_MODE_FAIL GSR6
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
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
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.

4–28 68P02901W56-L 14 Feb 2003
GSR6 CLASSMK_UPDATE_FAIL
CLASSMK_UPDATE_FAIL
Description
The CLASSMK_UPDATE_FAIL statistic tracks the number of classmark updates
containing errors. The classmark update procedure allows the MS to inform the network
of a change to its classmark.
Pegging
This statistic pegs when the validation of the Classmark Update message from the MS
fails.
Analysis
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
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.

14 Feb 2003 68P02901W56-L 4–29
CLR_CMD_FROM_MSC GSR6
CLR_CMD_FROM_MSC
Description
The CLR_CMD_FROM_MSC statistic separately tracks the number of Clear commands
received from the MSC for SDCCH and TCH resources thereby allowing the analysis of
dropped calls.
Pegging
This statistic pegs when a Clear command is received from the MSC.

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
for a Full Rate TCH.
2 CLR_CMD_FROM_MSC_HR Counts the number of clear
for a Half Rate TCH.
Analysis
This statistic can be used for trend analysis of the number of Clear commands received
from the MSC. This information can be used to identify and correct problems before they
become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2,

3.2.1.20. and 3.1.9.2.
Fault finding.
Network planning.
Basis Cell.
Type Counter array.

4–30 68P02901W56-L 14 Feb 2003
GSR6 CLR_REQ_TO_MSC
CLR_REQ_TO_MSC
Description
The CLR_REQ_TO_MSC statistic separately tracks the number of Clear Request
messages sent to the MSC for SDCCH and TCH resources.
Generating
The Clear Request message may be generated due to one of the following:
S No radio resources available to allocate from the BSS, call queuing is enabled, and
the maximum call delay has been exceeded.
S Radio interface message failure.
S Protocol error.
S 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:
S Immediate Assignment.
S Assignment.
S Channel Mode Modify.
S Ciphering.
S 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.

0 CLR_REQ_TO_MSC_SD Counts the number of clear requests
sent to the MSC for an SDCCH.
1 CLR_REQ_TO_MSC_FR Counts the number of clear requests
sent to the MSC for a Full Rate
TCH.
2 CLR_REQ_TO_MSC_HR Counts the number of clear requests
sent to the MSC for a Half Rate
TCH.
CLR_REQ_TO_MSC is not pegged when the CONN_REFUSED statistic is pegged.
However, there are 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.

14 Feb 2003 68P02901W56-L 4–31
CLR_REQ_TO_MSC GSR6
Analysis
This statistic can be used for trend analysis of the number of Clear Request messages
sent to the MSC. This information can be used to identify and correct problems before
they become serious.
Reference GSM 4.08, 3.8.0, 5.4.3. GSM 8.08, 3.9.2,

3.2.1.20. and 3.1.9.2.
Fault finding.
Network planning.
Ladder : BSS initiated call clearing, handover
(Intra-cell) fail/lost, handover (Intra-BSS) fail/lost.
NOTE Adding up the statistics in the ladder diagrams will not total
CLR_REQ_TO_MSC.
Basis Cell.
Type Counter array.

4–32 68P02901W56-L 14 Feb 2003
GSR6 CONGEST_EXIST_HO_ATMPT
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.

14 Feb 2003 68P02901W56-L 4–33
CONGEST_STAND_HO_ATMPT GSR6
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.

4–34 68P02901W56-L 14 Feb 2003
GSR6 CONN_REFUSED
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
S MS access for a location update.
S MS originated call establishment.
S MS terminated call establishment.
S SMS activity.
S Supplementary service activity.
S IMSI detach.
S 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.
NOTE Some MSCs may generate a Connection Refused Message

during a successful IMSI Detach rather than a Connection
Confirm, so a high value for the CONN_REFUSED statistic may
not indicate a system problem. The MSC performance during
IMSI Detach procedures should be investigated before
interpreting the CONN_REFUSED statistic.
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.

14 Feb 2003 68P02901W56-L 4–35
CONN_REQ_TO_MSC GSR6
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–36 68P02901W56-L 14 Feb 2003
GSR6 DYNET_ASSIGN_FAIL
DYNET_ASSIGN_FAIL
Description
The DYNET_ASSIGN_FAIL statistic tracks the number of times assignments have failed
due to insufficient terrestrial backhaul resources on a BTS Dynamic Allocation Network.
Pegging
This statistic pegs each time an assignment procedure fails due to the lack of terrestrial
backing resources.
Usage Quality of service monitoring.

Network planning.
Basis BSS.
Type Counter.
Alarm None.

14 Feb 2003 68P02901W56-L 4–37
DYNET_CALL_REJECTS GSR6
DYNET_CALL_REJECTS
Description
The DYNET_CALL_REJECTS statistic tracks the number of times calls have been
blocked or preempted due to insufficient terrestrial backhaul resources on a BTS
Dynamic Allocation Network.
Bin Procedures Description

0 NON_EMRG_CALL_BLK A non-emergency call is not
allocated a TCH due to the lack of
terrestrial backing resources in a
BTS network.
1 EMRG_CALL_BLK An emergency call is not allocated a
TCH due to the lack of terrestrial
backing resources in a BTS
network.
2 NON_EMRG_RESERVED A non-emergency call is not
allocated a TCH due to the cell
exceeding its reserve amount of
terrestrial backing resources and no
further backing resources are
available.
3 NON_EMRG_PREEMP A non-emergency call is preempted
to provide terrestrial backing
resources for an emergency call.
4 LOSS_OF_RESOURCES An emergency or non-emergency
call is preempted due to the loss of
of terrestrial backing resources.
Pegging
The appropriate bin is incremented when specific calls are rejected or preempted.

Networking planning.
Basis DYNET.
Type Counter array.
Alarm None.

4–38 68P02901W56-L 14 Feb 2003
GSR6 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.

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.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 4–39
ER_INTRA_CELL_HO_SUC GSR6
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

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–40 68P02901W56-L 14 Feb 2003
GSR6 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).

14 Feb 2003 68P02901W56-L 4–41
HO_FAIL_NO_RESOURCES GSR6
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
resources.
2 INTRA_CELL Number of intra-cell handover
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 handover failures due to a
5 INTRA_CELL_DYNET Number of BTS Dynamic Allocation
intra-cell handover failures due to a
Pegging
These individual bins are incremented on a per scenario basis.
Analysis
This statistic can be used for trend analysis of the handover failures due to a lack of
resources, such as:
S The target cell is barred for some reason, such as hardware failure.
S The channel is unavailable, that is there is congestion at the target cell and the
queue timer is expired.
S Incoming handovers are turned off at the target.
S The speech algorithm at the target BSS is not supported by the MS.
S An SCCP connection is not allocated, that is CRM runs out of SCCP numbers.
Reference Metrica.

Network planning.
Basis Cell.
Type Counter array.

4–42 68P02901W56-L 14 Feb 2003
GSR6 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
of handover failures for any reason other than lack of channel resources that are
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.
NOTE HO_REQ_MSC_FAIL can be equal to INTER_BSS_MS_FAIL if

the cell has never been the target for a failed handover.

14 Feb 2003 68P02901W56-L 4–43
HO_REQ_MSC_OK GSR6
HO_REQ_MSC_OK
Description
The HO_REQ_MSC_OK statistic tracks the number of handover acknowledge messages
sent to the MSC by the destination cell in an inter-BSS (external) handover.
Pegging
This statistic pegs 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 by
the BSS in response to MSC Handover Request messages.
Reference GSM 8.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.

4–44 68P02901W56-L 14 Feb 2003
GSR6 IDLE_TCH_INTF_BAND0
IDLE_TCH_INTF_BAND0
Description
The IDLE_TCH_INTF_BAND0 statistic tracks the maximum and mean number of idle
traffic channels (TCHs) for interference band 0. An idle TCH falls into band 0 if its
average interference band is less than the value of the element interfer_bands, 0.
NOTE Idle TCHs are allocated to five interference bands. Each band
has an associated statistic for tracking idle TCHs.
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.

14 Feb 2003 68P02901W56-L 4–45
IDLE_TCH_INTF_BAND1 GSR6
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–46 68P02901W56-L 14 Feb 2003
IDLE_TCH_INTF_BAND2
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.

14 Feb 2003 68P02901W56-L 4–47
IDLE_TCH_INTF_BAND3 GSR6
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–48 68P02901W56-L 14 Feb 2003
IDLE_TCH_INTF_BAND4
Description
Pegging
Analysis
Reference GSM 12.04, 4.2.1, B.2.1.13.

Fault finding.
Basis Cell.
Type Gauge.

14 Feb 2003 68P02901W56-L 4–49
IN_INTER_BSS_HO GSR6
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–50 68P02901W56-L 14 Feb 2003
GSR6 IN_INTRA_BSS_HO
IN_INTRA_BSS_HO
Description
The IN_INTRA_BSS_HO statistic tracks incoming intra-BSS handover procedures on a
per scenario basis. A total value for this statistic is not meaningful and is not displayed.

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
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
handover procedure.
Pegging
These individual bins are incremented on a per scenario basis.
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.
Service retainability.
Fault finding.
Handover.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 4–51
INTERBAND_ACTIVITY GSR6
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.

4–52 68P02901W56-L 14 Feb 2003
GSR6 INTRA_CELL_HO
INTRA_CELL_HO
Description
The INTRA_CELL_HO statistic tracks intra-cell handovers on a per scenario basis. A
total value for this statistic is not meaningful and is not displayed.

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 Number of assignment commands sent to
MS during an intra-cell handover.
2 INTRA_CELL_HO_SUC Number of successful intra-cell handovers.
3 INTRA_CELL_HO_LOSTMS Number of failed intra-cell handovers that
also failed to recover to the original cell.
4 INTRA_CELL_HO_RETURN Number of failed intra-cell handovers that
recovered to the original cell/channel.
5 INTRA_CELL_EQUIP_FAIL Number of attempted intra-cell handover
failures due to equipment failure.
6 INTRA_CELL_HO_CLEARED Number of incoming intra-cell 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
INTRA_CELL_HO_REQ is pegged just before sending the intra–cell handover message.
INTRA_CELL_HO_ATMPT is pegged after the channel activation message is received

and just before the assignment command is sent to the MS.
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.

14 Feb 2003 68P02901W56-L 4–53
INTRA_CELL_HO GSR6
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.

4–54 68P02901W56-L 14 Feb 2003
GSR6 INV_EST_CAUSE_ON_RACH
INV_EST_CAUSE_ON_RACH
Description
The INV_EST_CAUSE statistic tracks the number of RACHs with invalid establishment
cause. This helps to account more fully for occurrences of Phantom RACHs.
Pegging
This statistic pegs when the establishment cause is not validated.
It is possible for invalid Channel Requests not to be pegged by this statistic because the
Channel Requests are precisely formatted to prevent being caught by all the validation
routines (channel coder, RSS Layer 1, RSS Abis). These invalid Channel Requests that
are not pegged are due to phantom RACHs.
Analysis
This statistic can be used for trend analysis of RACHs with invalid establishment causes.
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.
Usage Handover.
Fault finding.
Ladder: Immediate Assignment Failure.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 4–55
MA_CMD_TO_MS GSR6
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:
S Release its link layer connections.
S Disconnect from its current physical channels.
S Switch to the assigned channels.
S Initiate re-establishment of the lower layer connections.
Analysis
This statistic can be used for trend analysis of BSS initiated channel assignment
procedures to the MS.
Reference GSM 4.08, 3.8.0, 3.4.3.1 and 9.1.2.

Call setup.
Ladder: TCH assignment successful, TCH
assignment fail-recovered to SDCCH, handover
(Intra-cell) successful, handover (Intra-cell)
fail-recovered, handover (Intra-cell) fail-lost.
Basis Cell.
Type Counter.

4–56 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 4–57
MA_COMPLETE_TO_MSC GSR6
MA_COMPLETE_TO_MSC
Description
The MA_COMPLETE_TO_MSC statistic tracks the number of successful TCH seizures.
Pegging
This statistic pegs when the Assignment Complete message from the MS is forwarded
on to the MSC.
Analysis
This statistic can be used for trend analysis of successful TCH seizures.
Reference GSM 12.04, 4.2.1, B.2.1.15

Quality of service: Call set-up.
Network planning.
Basis Cell.
Type Counter.

4–58 68P02901W56-L 14 Feb 2003
GSR6 MA_FAIL_FROM_MS
MA_FAIL_FROM_MS
Description
The MA_FAIL_FROM_MS statistic tracks the number of Assignment Failure messages
received from MSs. An Assignment Failure message can be received at call setup
(traffic channel assignment) and at intra cell handovers.
Pegging
This statistic pegs when the BSS receives an Assignment Failure message from the MS.
If the MS detects a lower layer failure on the new channels before the Assignment
Complete message has been sent:
S It deactivates the new channels.
S Reactivates the old channels.
S Reconnects any TCHs.
S Triggers establishment of the main signalling link.
S 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
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 is generated. Refer to the Maintenance Information: Alarm Handling at

GSM 12.07, 3.0.2, 2.8.6.c.
GSM 4.08, 3.8.0, 3.4.3.3 and 9.1.4.
Quality of service monitoring: Call setup.
Fault finding.
Ladder: TCH assignment fail-recovered to
SDCCH, handover (Intra-cell) fail-recovered.
Basis Cell.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 4–59
MA_REQ_FROM_MSC GSR6
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.
Pegging
This statistic pegs the radio resource request made to a BSS by the MSC.
Analysis
This statistic can be used for trend analysis of MSC request to the BSS to allocate radio
resources.

Network planning.
Ladder: TCH assignment successful, TCH
assignment fail-recovered to SDCCH, TCH
assignment blocked.
Basis Cell.
Type Counter.

4–60 68P02901W56-L 14 Feb 2003
GSR6 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
of times traffic channels that may be congested due to a lack of radio resources that are
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.

14 Feb 2003 68P02901W56-L 4–61
MS_ACCESS_BY_TYPE GSR6
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.
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–62 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 4–63
MS_TCH_USAGE_BY_TYPE_PCS GSR6
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.
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.

4–64 68P02901W56-L 14 Feb 2003
GSR6 MT_LCS_ON_SDCCH
MT_LCS_ON_SDCCH
Description
This statistic counts the number of mobile–terminated SDCCH sessions for Location
Services.
NOTE 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.

14 Feb 2003 68P02901W56-L 4–65
NUM_EMERG_ACCESS GSR6
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–66 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 4–67
NUM_EMERG_TCH_KILL GSR6
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–68 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 4–69
OK_ACC_PROC GSR6
OK_ACC_PROC
Description
The OK_ACC_PROC tracks successful accesses by procedure. A total count of all
successful accesses is also maintained.
Bin Procedure Description

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
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 {3974}LOCATION _SERVICES Number of Location Measurement
Unit (LMU) service requests for
location services.
NOTE LOCATION_SERVICES is stored in column cm_lcs_request of

the OMC database.
Pegging
{3974}This statistic pegs the total number of successful results per procedure including
location services.
Analysis
This statistic can be used for trend analysis of the number of successful accesses by
procedure.

4–70 68P02901W56-L 14 Feb 2003
GSR6 OK_ACC_PROC
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_HOLDING_TIME,
SDCCH_MEAN_ARRIVAL_RATE,
SDCCH_RF_LOSS_RATE.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 4–71
OK_ACC_PROC_SUC_RACH GSR6
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.
Immediate assignment blocked, Immediate
assignment failure.
Basis Cell.
Type Counter.

4–72 68P02901W56-L 14 Feb 2003
GSR6 OUT_HO_CAUSE_ATMPT
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.
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.
NOTE When a specific bin is included in descriptions or formulae in this

manual, the convention used for the presentation of the statistic
and the bin identification will be OUT_HO_CAUSE_ATMPT[bin
name]. An example of this convention is
OUT_HO_CAUSE_ATMPT[UPQUAL].
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.

14 Feb 2003 68P02901W56-L 4–73
OUT_HO_CAUSE_ATMPT GSR6
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.

4–74 68P02901W56-L 14 Feb 2003
GSR6 OUT_INTER_BSS_HO
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 attempted inter-BSS
handover failures due to equipment
failure.
6 OUT_INTER_BSS_HO_CLEARED Number of outgoing inter-BSS

handover procedure.
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 a cause 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.

14 Feb 2003 68P02901W56-L 4–75
OUT_INTER_BSS_HO GSR6
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.

4–76 68P02901W56-L 14 Feb 2003
GSR6 OUT_INTRA_BSS_HO
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 due to equipment
failure.
7 OUT_INTRA_BSS_HO_CLEARED Number of outgoing intra-BSS
handover procedure.

14 Feb 2003 68P02901W56-L 4–77
OUT_INTRA_BSS_HO GSR6
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.
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.

4–78 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 4–79
PAGING_REQUESTS GSR6
PAGING_REQUESTS
Description
{3750}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
CS .
2 PAGING_REQS_PS Number of Paging requests
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–80 68P02901W56-L 14 Feb 2003
GSR6 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.
{3750} 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.

14 Feb 2003 68P02901W56-L 4–81
PCH_Q_PAGE_DISCARD GSR6
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.
{3750} The statistic is modified to count both Circuit Switched (CS) and Packet Switch
(PS) pages.
{3750} The bins are:
S CS pages discarded.
S PS pages discarded.
{3750} 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.
{3750} 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
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
Usage Quality of service: Paging analysis.

Optimization.
Network planning.
Basis Cell.
Type Counter.
Alarm Major.

4–82 68P02901W56-L 14 Feb 2003
GSR6 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
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 alarm is generated. Refer to the Maintenance Information:
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.

14 Feb 2003 68P02901W56-L 4–83
RF_LOSSES_TCH GSR6
RF_LOSSES_TCH
Description
The RF_LOSSES_TCH statistic tracks the number of calls lost while using a TCH.
NOTE
RF_LOSSES_TCH is the BSS MMI name of the statistic kept by the BSS
on a per timeslot level. The OMC-R rolls the information up to the cell level
and refers to this information as RF_LOSSES_TCH_ROLL.
Pegging
This statistic pegs the number of 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
of lost calls while 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.
Key Statistic: RF_LOSS_RATE,
TCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter.
Alarm Major.
NOTE 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.

4–84 68P02901W56-L 14 Feb 2003
GSR6 SDCCH_CONGESTION
SDCCH_CONGESTION
Description
The SDCCH_CONGESTION statistic tracks the amount of time that no SDCCH channel
was available in a cell.
Pegging
This statistic records the sum of the duration of periods when all the SDCCH channels in
a cell were busy. The statistic also collects the mean, maximum, and minimum time of
SDCCH congestion. If a TCH is reconfigured as an SDCCH, only the SDCCH statistics
are recorded.
Although the mean, maximum and minimum values are collected for this statistic, they
can only be viewed through the MMI using the disp_stats command.
Analysis
This statistic can be used for trend analysis of the length of time during which SDCCH
channels were not available.
Reference GSM 12.04, 3.1.0, B.1.3.5.
Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis Cell.
Type Duration (total time in milliseconds).

14 Feb 2003 68P02901W56-L 4–85
SECOND_ASSIGN_ATMPT GSR6
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.

4–86 68P02901W56-L 14 Feb 2003
GSR6 SECOND_ASSIGN_SUC
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.

14 Feb 2003 68P02901W56-L 4–87
SMS_INIT_ON_SDCCH GSR6
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.

4–88 68P02901W56-L 14 Feb 2003
GSR6 SMS_INIT_ON_TCH
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.

14 Feb 2003 68P02901W56-L 4–89
SMS_NO_BCAST_MSG GSR6
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.

4–90 68P02901W56-L 14 Feb 2003
GSR6 TCH_CONGESTION
TCH_CONGESTION
Description
The TCH_CONGESTION statistic indicates the amount of time that no TCH channels
were available in that cell.
The TCH_CONGESTION statistic will only be used for outer zone resources when TCH
congestion is being measured for Concentric Cells.
A congestion (or blocking) state occurs when all channels available to traffic within a cell
(the number may vary over time due to failure or maintenance actions) are busy, where
busy means unavailable for allocation to a new call attempt.
Pegging
This statistic pegs the sum of the duration of periods when all TCHs were busy. The
statistic also reports the mean, maximum and minimum time of TCH congestion. If a
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.
Type Duration (total time in milliseconds).

14 Feb 2003 68P02901W56-L 4–91
TCH_CONG_INNER_ZONE GSR6
TCH_CONG_INNER_ZONE
Description
The TCH_CONG_INNER_ZONE statistic tracks the total length of time in which all of the
TCHs in the inner zone of a concentric cell are busy. The Concentric Cell option must be
enabled for this statistic to be enabled, disabled, or displayed.
Pegging
The timer for this statistic is started when all TCHs belonging to TCHs in the inner zone
are busy. The timer is stopped when an inner zone TCH is freed.
Analysis
This statistic can be used for trend analysis of the length of time in which all of the TCHs
in the inner zone of a concentric cell are busy.
Reference None.
Usage Network planning.
Basis Cell.
Type Duration.

4–92 68P02901W56-L 14 Feb 2003
GSR6 TCH_DELAY
TCH_DELAY
Description
The TCH_DELAY statistic tracks the mean delay and the statistical distribution of the
delay between an assignment request or handover request and a TCH being allocated
for each cell on the BSS.
As more calls (in proportion to the total number of calls) are queued, the mean delay 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.

14 Feb 2003 68P02901W56-L 4–93
TCH_Q_LENGTH GSR6
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–94 68P02901W56-L 14 Feb 2003
GSR6 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.
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.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 4–95
TCH_USAGE GSR6
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:
S Interval 0 starts.
S TCH 0 starts call – internal timer starts.
S TCH 1 starts call – internal timer starts.
S TCH 0 ends call – internal timer stops.
S TCH_USAGE counter incremented by time.
S Difference for TCH 0.
S Interval 0 expires.
The value reported for the interval will only include the call for TCH0.
S Interval 1 starts.
S TCH 1 ends a call – internal timer stopped.
S TCH_USAGE counter incremented by time.
S 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.
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.

4–96 68P02901W56-L 14 Feb 2003
GSR6 TCH_USAGE
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 4–97
TCH_USAGE_EXT_RANGE GSR6
TCH_USAGE_EXT_RANGE
Description
The TCH_USAGE_EXT_RANGE statistic tracks the number of extended range traffic
channels in use.
This statistic may only be enabled if the Extended Range Cell feature is unrestricted and
Pegging
This statistic pegs each time an extended range traffic channel is used.
Analysis
This statistic can be used for trend analysis of the number of extended range traffic
channels in use.
Reference None.

Network planning.
Basis Cell.
Type Counter.

4–98 68P02901W56-L 14 Feb 2003
GSR6 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.
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.

14 Feb 2003 68P02901W56-L 4–99
TOTAL_CALLS GSR6
TOTAL_CALLS
Description
The TOTAL_CALLS statistic tracks the total number of calls originated for each cell on
the BSS.
Pegging
This statistic indicates the number of circuit oriented calls that are originated in the cell.
It is pegged only once per connection at the time of the first successful TCH assignment
procedure. Subsequent channel changes, for example voice to data, are not counted.
This statistic does not necessarily peg all successful calls. It only pegs calls that have
been assigned to the TCH. For example, if the call fails to send a Direct Transfer
Application Part (DTAP) Connect Acknowledge, it still looks successful to the base.
NOTE This statistic is not pegged on the short message service
Analysis
This statistic can be used for trend analysis of the total number of calls originated for
each cell on the BSS.
Reference GSM 4.08, 3.8.0, 5.2.

Quality of service monitoring : Call setup.
Network planning.
Key Statistics: RF_LOSS_RATE,
TCH_MEAN_ARRIVAL_RATE,
TCH_RF_LOSS_RATE.
Basis Cell.
Type Counter.

4–100 68P02901W56-L 14 Feb 2003
GSR6 ZONE_CHANGE_ATMPT
ZONE_CHANGE_ATMPT
Description
The ZONE_CHANGE_ATMPT statistic tracks attempts of each type of concentric cell
specific handover. The Concentric Cell option must be enabled for this statistic to be
enabled, disabled, or displayed.

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.

14 Feb 2003 68P02901W56-L 4–101
ZONE_CHANGE_SUC GSR6
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.

4–102 68P02901W56-L 14 Feb 2003
Chapter 5
Neighbour statistics

14 Feb 2003 68P02901W56-L 5–1
GSR6

5–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to Neighbour Statistics
Introduction to Neighbour Statistics
Description
This chapter includes descriptions of the per neighbour statistics.
Neighbour
When the BSS is configured to control inter-cell handovers, four of the handover
statistics may be used to track handovers. These neighbour statistics provide the
destination cell of an outgoing handover or the origination cell of an incoming handover.
Each of the neighbour statistics keep track of handover information for a pair of source
and neighbour cells.
The following are neighbour statistics:
S IN_INTRA_BSS_NC_ATMPT.
S IN_INTRA_BSS_NC_SUC.
S OUT_HO_NC_CAUSE_ATMPT.
S OUT_HO_NC_SUC.
Definitions
Following terms are used in the description of neighbour cells:
S Source cell – the cell in which a handover is initiated. Each source cell may have
up to 32 target (neighbour) cells.
S 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.
Limitations
S 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.
S 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.
S 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.
S 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:
S OUT_HO_NC_CAUSE_ATMPT.
S OUT_HO_NC_SUC.

14 Feb 2003 68P02901W56-L 5–3
Introduction to Neighbour Statistics GSR6
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:
S Originating in cell_0 that hand into cell_1.
S .
S .
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.
OUT_HO_NC_CAUSE_ATMPT 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:
S originating in cell_0 that hand into cell_1
S .
S .
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.
OUT_HO_NC_CAUSE_ATMPT statistic is enabled at cell_0. The add_neighbor
command is used to add cell_32 as a neighbour cell of cell_0.
S originating in cell_0 that hand into cell_2.
S .
S .
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:
S IN_INTRA_BSS_NC_ATMPT.
S IN_INTRA_BSS_NC_SUC.

5–4 68P02901W56-L 14 Feb 2003
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.
S that hand into cell_0 originating from cell_1
S .
S .
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

cell_50 are tracked because the 32 cell limit has been reached.
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.

14 Feb 2003 68P02901W56-L 5–5
Example of when a neighbour cell is deleted

cell_50 are tracked because the 32 cell limit has been reached.
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.
Notation
An example of the notation used in the examples is:
IN_INTRA_BSS_NC_ATMPT: 0 (B–A)
stat name peg count source cell_B and target 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.
cell_A cell_B
cell_C

5–6 68P02901W56-L 14 Feb 2003
Table 5-1 Neighbour cell statistics pegged

Neighbour status Initial peg count Peg source
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)
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.

14 Feb 2003 68P02901W56-L 5–7

5–8 68P02901W56-L 14 Feb 2003
GSR6 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.1

GSM 4.08, 8.08, 8.58
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Basis NCell (Neighbour cell).
Type Counter.

14 Feb 2003 68P02901W56-L 5–9
IN_INTRA_BSS_NC_SUC GSR6
IN_INTRA_BSS_NC_SUC
Description
The IN_INTRA_BSS_NC_SUC statistic tracks the successful incoming internal inter-cell
handovers per originating cell.
This statistic can be enabled for a maximum of 16 cells. For each cell where the statistic
is enabled, a maximum of 32 source cells can be tracked.
Pegging
This statistic is pegged in the target cell upon notification of a successful intra-BSS
handover from a specific cell.
Analysis
This statistic can be used for trend analysis of incoming internal inter-cell handovers per
originating cell.
Reference GSM 12.04, 4.0.0, B.2.2.2

GSM 4.08, 8.08, 8.58
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Type Counter.

5–10 68P02901W56-L 14 Feb 2003
GSR6 OUT_HO_NC_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT
Description
The OUT_HO_NC_CAUSE_ATMPT statistic tracks the number of handovers per
neighbour per cause. This statistic can be enabled for a maximum of 16 cells. For each
cell where the statistic is enabled, a maximum of 32 target cells can be tracked.
This statistic provides information to determine quality of service and to support
optimization. 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.
Analysis
This statistic can be used for trend analysis of handover attempts per neighbour on a per
cause basis.

14 Feb 2003 68P02901W56-L 5–11
OUT_HO_NC_CAUSE_ATMPT GSR6
Reference GSM 12.04, 4.0.0, B.2.2.3

GSM 4.08, 8.08, 8.58
GSM 12.04, 4.2.1
Usage Handover.
Quality of Service.
Network Planning.
Optimization.
Fault Finding.
Ladder: Intra-BSS handover.
Type Counter array.

5–12 68P02901W56-L 14 Feb 2003
GSR6 OUT_HO_NC_SUC
OUT_HO_NC_SUC
Description
The OUT_HO_NC_SUC statistic tracks the number of successful outgoing inter-cell
handovers per target cell. This statistic can be enabled for a maximum of 16 cells. For
each cell where the statistic is enabled, a maximum of 32 target cells can be tracked.
Pegging
This statistic pegs the total number of successful handovers out of a specific cell and the
location of the target cell for each successful handover.
Analysis
This statistic can be used for trend analysis of handover performance of specific cells for
each of its 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.

14 Feb 2003 68P02901W56-L 5–13
OUT_HO_NC_SUC GSR6

5–14 68P02901W56-L 14 Feb 2003
Chapter 6
Carrier and timeslot statistics

14 Feb 2003 68P02901W56-L 6–1
GSR6

6–2 68P02901W56-L 14 Feb 2003
GSR6 Carrier and timeslot statistics introduction
Carrier and timeslot statistics introduction

Description of carrier statistics
This chapter includes descriptions of the carrier statistics which are organized into the
following groups:
S Downlink RXQUAL (BER).
S Uplink RXQUAL (U_BER).
S Link balance verification.
S BTS dynamic allocation.
S Timing advance.
S Miscellaneous.
Downlink RXQUAL (BER)

Downlink receive quality statistics are used to track the Bit Error Rate (BER) of active
channels. The following is the only downlink RXQUAL statistic:
S BER.
Uplink RXQUAL (U_BER)

Uplink receive quality statistics are used to track the Bit Error Rate (BER) of active
channels. The following is the only uplink RXQUAL statistic:
S U_BER.
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:
S CHAN_DL_TX_PWR_LVL.
S CHAN_UL_TX_PWR_LVL.
S PATH_BALANCE.
S UPLINK_PATH_LOSS.
BTS dynamic allocation

BTS dynamic allocation statistics are used to track utilization of dynet channels. The
following are the BTS dynamic allocation statistics:
S ALLOC_SDCCH_CARR.
S ALLOC_TCH_CARR.
Timing advance
The timing advance statistic ROC 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:
S CHAN_REQ_MS_FAIL.
S FER.
S INTF_ON_IDLE.
S RBER.
S RF_LOSSES_TCH.

14 Feb 2003 68P02901W56-L 6–3
ALLOC_SDCCH_CARR GSR6
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:
S Successful handover on an SDCCH channel.
S 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.
Intra-cell handover, Inter-BSS handover,
Connection establishment, Intra-BSS handover.
Basis Carrier.
Type Counter.

6–4 68P02901W56-L 14 Feb 2003
GSR6 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:
S Successful allocation due to call establishment including successful allocations due
to directed retries.
S Successful allocation due to inter-cell/intra-cell hand in.
S Successful allocation due to inter-BSS hand in.
This statistic is pegged before the transmission of the assignment/handover command to
the MS and, therefore, does not take into account the success or failure of the
assignment/hand in from an RF perspective.
Analysis
This statistic can be used for trend analysis of TCH allocations and allows the calculation
of the mean hold time of a TCH per carrier.
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_ARRIVAL_RATE,
CELL_TCH_ALLOCATIONS,
TCH_RF_LOSS_RATE.
Basis Carrier.
Type Counter.

14 Feb 2003 68P02901W56-L 6–5
BER GSR6
BER
Description
The BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for
active channels. The bit error rate value corresponds to the RXQUAL downlink
measurement reports. BER statistic measurements are reported only when the channel
is active.
NOTE BER on SDCCH channels are affected by phantom RACHs.

BER on TCHs are not affected. For a cell with a non-combined
BCCH configuration, there are no values presented on timeslot
0.
Pegging
The statistic pegs every 480 ms (corresponding to each SACCH multiframe).
Units
This statistic is reported using values 0 to 7 that are derived from the RXQUAL values:
RXQUAL BER (min to max)

0 0 to 0.2
1 0.2 to 0.4
2 0.4 to 0.8
3 0.8 to 1.6
4 1.6 to 3.2
5 3.2 to 6.4
6 6.4 to 12.8
7 greater than 12.8
NOTE The bin ranges for this statistic may not be changed.
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.

6–6 68P02901W56-L 14 Feb 2003
GSR6 CHAN_DL_TX_PWR_LVL
CHAN_DL_TX_PWR_LVL
Description
The CHAN_DL_TX_PWR_LVL statistic tracks the maximum, mean, and minimum BSS
(downlink) transmit power level. The reported value is in dBm units.
Pegging
This statistic pegs every SACCH multiframe.
Analysis
This statistic can be used for trend analysis of mean BSS transmit power levels.
Reference GSM 12.04, 4.2.1, B.2.1.28.
Usage Fault finding

Quality of service.
Basis Carrier.

14 Feb 2003 68P02901W56-L 6–7
CHAN_REQ_MS_FAIL GSR6
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 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 SDCCH allocated. When the MS does not reply with a SABM on that 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.
NOTE CHAN_REQ_MS_FAIL is the BSS MMI name of the statistic

kept by the BSS on a per timeslot level. The OMC-R rolls the
information up to the cell level and refers to this information as
CHAN_REQ_MS_FAIL_ROLL.
Pegging
This statistic pegs when the MS does not reply with Set Asynchronous Balanced Mode
(SABM) on the SDCCH.
Analysis
of BSS timeouts while waiting for an MS to establish on the SDCCH assigned during the
immediate assignment procedure that are acceptable in normal system operations.
If the specified threshold is exceeded, the 1. CELL: Attempt at allocating an SDCCH
failed – PM alarm is generated. Refer to the Maintenance Information: Alarm Handling
at the OMC (68P02901W26) for troubleshooting information.
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.
Type Counter.
Alarm Minor.

6–8 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 6–9
FER GSR6
FER
Description
The FER (Frame Erasure Rate) Quality statistic is derived from a ratio of successfully
decoded good speech frames against unsuccessfully decoded bad frames. 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 an FER 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-1, this relates to an FER Quality number of 2.
Pegging
This statistic pegs every 480 ms during the SACCH multi-frame by the RSS/HO process.
Units
The FER is reported using values 0 to 9 and shows the complete lookup table.
Table 6-1 FER Quality number conversion

FER Quality number FER ratio (min:1 to max:1)
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_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.
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 Timeslot.

6–10 68P02901W56-L 14 Feb 2003
GSR6 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.
ranges for the INTF_ON_IDLE statistic are shown in Table 6-2.
Table 6-2 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-3 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-3.
Table 6-3 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.

14 Feb 2003 68P02901W56-L 6–11
INTF_ON_IDLE GSR6
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–12 68P02901W56-L 14 Feb 2003
GSR6 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.
NOTE The actual value for path_balance depends on the type of RF

combining used.
Pegging
This statistic is pegged by the value calculated by the following equation:
path_balance = path loss + 110
where:
path loss = uplink path loss – downlink path loss
where:
uplink path loss = actual MS txpower – rxlev_ul
downlink path loss = actual BTS txpower – rxlev_dl
NOTE The rxlev_ul and rxlev_dl values reflect the latest reported value
and are not averaged values. PATH_BALANCE is not pegged
when either rxlev_ul or rxlev_dl is equal to 63 (–47 dBm).
The range of values for this statistic is 0 to 220 with a long term average of 110 with
normal use. A deviation of ±10 is acceptable, but this is to be understood as a practical
guide and not as product tolerance. If the deviation is greater than ±10, the RF path
should be checked.
NOTE If a low noise amplifier (LNA) is fitted, a deviation of –20 is

possible.
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 Horizonmacro 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.

14 Feb 2003 68P02901W56-L 6–13
PATH_BALANCE GSR6
If... Then...
the Horizon cabinet is the SITE alarm 28 “data configuration
equipped with Horizonmacro and Horizon hardware mismatch” will be
database, the path_balance generated
statistic will be incorrect.
operators should change either the
hardware or the database accordingly.
Consult the manual, Maintenance

Information: Alarm Handling At The OMC
(68P02901W26).
the Horizonmacro cabinet is the SITE alarm 28 “data configuration
equipped with Horizon and Horizon hardware mismatch” will be
database, the path_balance generated.
statistic will be incorrect.
operators should change either the
hardware or the database accordingly.
Consult the manual, Maintenance

Information: Alarm Handling At The OMC
(68P02901W26).
NOTE 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–14 68P02901W56-L 14 Feb 2003
GSR6 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.
During this period, 24 speech frames are decoded and a ratio calculated. By referring to
a lookup table, the ratio is converted to an RBER Quality number between 0 and 7.
NOTE RBER is supported only by MMI actions. It not reported to the

OMC-R at the end of the statistical interval period.
Pegging
Every 480 ms, during the SACCH multi-frame by the RSS/HO process.
Units
The RBER statistic is reported using values 0 to 7.
Table 6-4 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.
Analysis
This statistic can be used for trend analysis for target optimization effects on cell/radios
with regards to quality.
Reference None.
Fault finding.
RF loss.
Congestion.
Basis Timeslot.

14 Feb 2003 68P02901W56-L 6–15
RF_LOSSES_TCH GSR6
RF_LOSSES_TCH
Description
The RF_LOSSES_TCH statistics tracks the number of calls lost while using a TCH.
NOTE RF_LOSSES_TCH is the BSS MMI name of the statistic kept by

the BSS on a per timeslot level. The OMC-R rolls the
information up to the cell level and refers to this information as
RF_LOSSES_TCH_ROLL.
Pegging
This statistic pegs the number of 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 will be configured.
Analysis
of lost calls while using a TCH that are acceptable in normal system operations.
If the specified threshold is exceeded, the 0. TIMESLOT: Radio frequency losses
while using a TCH – PM alarm is generated. Refer to the Maintenance Information:
Alarm Handling at the OMC (68P02901W26) for troubleshooting information.
Reference GSM 12.04, 3.1.0, B.1.1.5.

GSM 4.08, 3.8.0, 3.5.2, 9.1.27a and 10.5.2.19.
Usage RF loss.
Congestion.
Fault finding.
Key Statistic: RF_LOSS_RATE,
TCH_RF_LOSS_RATE.
Basis Timeslot.
Type Counter.
Alarm Major.
NOTE 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–16 68P02901W56-L 14 Feb 2003
GSR6 ROC
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-5.
Table 6-5 Bin ranges for ROC

Bin TA Range
0 0 to 6
1 7 to 13
2 14 to 20
3 21 to 27
4 28 to 34
5 35 to 41
6 42 to 48
7 49 to 54
8 55 to 63
9 64 to 219
NOTE These bins are not displayed at the OMC but can be displayed at
the MMI. To set and display the bin ranges refer to the
chg_stat_prop and disp_stat_prop commands in Chapter 2.
Pegging
Basis Carrier.

14 Feb 2003 68P02901W56-L 6–17
U_BER GSR6
U_BER
Description
The U_BER statistic tracks the minimum, maximum, and mean Bit Error Rate (BER) for
active channels. The bit error rate value corresponds to the RXQUAL uplink
measurement reports. U_BER statistic measurements are reported only when the
channel is active.
NOTE 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
NOTE The bin ranges for this statistic may not be changed.
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–18 68P02901W56-L 14 Feb 2003
GSR6 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.

14 Feb 2003 68P02901W56-L 6–19
UPLINK_PATH_LOSS GSR6

6–20 68P02901W56-L 14 Feb 2003
Chapter 7
GPROC and DPROC statistics

14 Feb 2003 68P02901W56-L 7–1
GSR6

7–2 68P02901W56-L 14 Feb 2003
GSR6 GPROC and DPROC statistics
GPROC and DPROC statistics
Introduction
This chapter includes descriptions of the Generic Processor (GPROC) and Data
Processor (DPROC) statistics. These statistics apply only to the utilization of the
processing units found in various hardware components in the BSS, for example GPROC
and DPROC devices.
Processor utilization
Processor utilization statistic tracks the utilization of the processing units found in various
hardware components in the GPROC and DPROC devices.

14 Feb 2003 68P02901W56-L 7–3
CPU_USAGE GSR6
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–4 68P02901W56-L 14 Feb 2003
Chapter 8
LMTL statistics

14 Feb 2003 68P02901W56-L 8–1
GSR6

8–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to LMTL statistics
Introduction to LMTL statistics

{3974}
Description
This chapter includes descriptions of the Location Services Message Transfer Link
(LMTL) statistics. LMTL statistics are organized into the following groups:
S LMTP C7 availability.
S LMTP C7 performance.
S LMTP C7 utilization.
LMTP C7 availability
MTP 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:
S LMTP_LINKFAIL.
S LMTP_LOCAL_BUSY.
S LMTP_LOCAL_MGT.
S LMTP_MGT_INHIBIT.
S LMTP_MGT_UNINHIBIT.
S LMTP_REMOTE_MGT.
S LMTP_REMOTE_PROC.
S LMTP_START_RPO.
S LMTP_STOP_RPO.
S LMTP_UNAVAILABLE.
LMTP C7 performance
LMTP C7 performance statistics are used to track the different types of failure and
recovery situations for the Location SERVICES Message Transfer Part (LMTP) of the
ITU-TSS No.7 protocol on the BSC to MSC interface. The following are the LMTP C7
performance statistics:
S LMTP_CHANGEBACK.
S LMTP_CHANGEOVER.
S LMTP_LINK_INS.
S LMTP_NEG_ACKS.
S LMTP_RESTORATION.
S LMTP_SL_ACK.
S LMTP_SL_ALIGNMENT.
S LMTP_REMOTE_SL_CONGESTION .
S LMTP_SL_ERROR_RATE.
S LMTP_SL_FAIL.
S LMTP_SL_FIBR.
S LMTP_SU_ERROR.

14 Feb 2003 68P02901W56-L 8–3
Introduction to LMTL statistics GSR6
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:
S LMTP_CONGESTION_LOST_MSU .
S LMTP_MSU_DISCARDED.
S LMTP_CONGESTION .
S LMTP_RE_TX.
S LMTP_MSU_RX.
S LMTP_MSU_TX.
S LMTP_SIB_RX.
S LMTP_SIB_TX.
S LMTP_SIF_SIO_RX.
S LMTP_SIF_SIO_TX .
S LMTP_LOCAL_SL_CONGESTION .

8–4 68P02901W56-L 14 Feb 2003
GSR6 LMTP_CONGESTION_LOST_MSU
LMTP_CONGESTION_LOST_MSU
{3974}
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
of lost MSUs due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. LMTL: SL congestion events resulting
in loss of MSUs – PM alarm is generated. Refer to the Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 8–5
LMTP_MSU_DISCARDED GSR6
LMTP_MSU_DISCARDED
{3974}
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
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 is generated. Refer to the Maintenance Information: 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-L 14 Feb 2003
GSR6 LMTP_CHANGEBACK
LMTP_CHANGEBACK
{3974}
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.

14 Feb 2003 68P02901W56-L 8–7
LMTP_CHANGEOVER GSR6
LMTP_CHANGEOVER
{3974}
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
of out of sequence messages between a BSS and an SMLC that are acceptable in
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks
received – PM alarm is generated. Refer to the Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.

8–8 68P02901W56-L 14 Feb 2003
GSR6 LMTP_LOCAL_SL_CONGESTION
LMTP_LOCAL_SL_CONGESTION
{3974}
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
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.

14 Feb 2003 68P02901W56-L 8–9
LMTP_LINK_INS GSR6
LMTP_LINK_INS
{3974}
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-L 14 Feb 2003
GSR6 LMTP_LINKFAIL
LMTP_LINKFAIL
{3974}
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.

14 Feb 2003 68P02901W56-L 8–11
LMTP_LOCAL_BUSY GSR6
LMTP_LOCAL_BUSY
{3974}
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-L 14 Feb 2003
GSR6 LMTP_LOCAL_MGT
LMTP_LOCAL_MGT
{3974}
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.

14 Feb 2003 68P02901W56-L 8–13
LMTP_MGT_INHIBIT GSR6
LMTP_MGT_INHIBIT
{3974}
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-L 14 Feb 2003
GSR6 LMTP_MGT_UNINHIBIT
LMTP_MGT_UNINHIBIT
{3974}
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
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.

14 Feb 2003 68P02901W56-L 8–15
LMTP_MSU_RX GSR6
LMTP_MSU_RX
{3974}
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-L 14 Feb 2003
GSR6 LMTP_MSU_TX
LMTP_MSU_TX
{3974}
Description
The LMTP_MSU_TX statistic tracks the number of Message Signal Units (MSUs)
transmitted on an Lb-interface signalling link.
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.

14 Feb 2003 68P02901W56-L 8–17
LMTP_NEG_ACKS GSR6
LMTP_NEG_ACKS
{3974}
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
of out of sequence messages between a BSS and an SMLC that are acceptable in
If the specified threshold is exceeded, the 7. LMTL: SL number of negative acks
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-L 14 Feb 2003
GSR6 LMTP_RE_TX
LMTP_RE_TX
{3974}
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
of octet retransmissions that are acceptable in normal system operations.
If the specified threshold is exceeded, the 9.LMTL: Number of octets retransmitted –
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.

14 Feb 2003 68P02901W56-L 8–19
LMTP_REMOTE_MGT GSR6
LMTP_REMOTE_MGT
{3974}
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-L 14 Feb 2003
GSR6 LMTP_REMOTE_PROC
LMTP_REMOTE_PROC
{3974}
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.
Type Duration (total time in milliseconds (ms).

14 Feb 2003 68P02901W56-L 8–21
LMTP_RESTORATION GSR6
LMTP_RESTORATION
{3974}
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-L 14 Feb 2003
GSR6 LMTP_SIF_SIO_RX
LMTP_SIF_SIO_RX
{3974}
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.

14 Feb 2003 68P02901W56-L 8–23
LMTP_SIF_SIO_TX GSR6
LMTP_SIF_SIO_TX
{3974}
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-L 14 Feb 2003
GSR6 LMTP_SL_ACK
LMTP_SL_ACK
{3974}
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
of acknowledgements of MSUs not being received by the BSC that are acceptable in
If the specified threshold is exceeded, the 2. LMTL: SL failure - excessive delay of
ACK – PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at
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.

14 Feb 2003 68P02901W56-L 8–25
LMTP_SL_ALIGNMENT GSR6
LMTP_SL_ALIGNMENT
{3974}
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
of unsuccessful attempts to align an out-of-service SL to the Lb-interface that are
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-L 14 Feb 2003
GSR6 LMTP_REMOTE_SL_CONGESTION
LMTP_REMOTE_SL_CONGESTION
{3974}
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
If the specified threshold is exceeded, the 4. LMTL: SL failure - excessive duration of
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.

14 Feb 2003 68P02901W56-L 8–27
LMTP_SL_ERROR_RATE GSR6
LMTP_SL_ERROR_RATE
{3974}
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
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 –
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-L 14 Feb 2003
GSR6 LMTP_SL_FAIL
LMTP_SL_FAIL
{3974}
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
SL failures, excluding those caused by operator interaction with the MMI, that are
If the specified threshold is exceeded, the 0. LMTL: SL failure - all reasons – PM alarm
is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.

14 Feb 2003 68P02901W56-L 8–29
LMTP_SL_FIBR GSR6
LMTP_SL_FIBR
{3974}
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
times an SL may be lost due to the detection of an abnormal FIB that are acceptable in
If the specified threshold is exceeded, the 1. LMTL: SL failure - abnormal FIBR/BSNR
– PM alarm is generated. Refer to the Maintenance Information: Alarm Handling at the
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Major.

8–30 68P02901W56-L 14 Feb 2003
GSR6 LMTP_START_RPO
LMTP_START_RPO
{3974}
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
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 generated. Refer to the Maintenance Information: Alarm Handling at the
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis Lb SS7_LINK.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 8–31
LMTP_STOP_RPO GSR6
LMTP_STOP_RPO
{3974}
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-L 14 Feb 2003
GSR6 LMTP_SU_ERROR
LMTP_SU_ERROR
{3974}
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
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 –
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.

14 Feb 2003 68P02901W56-L 8–33
LMTP_UNAVAILABLE GSR6
LMTP_UNAVAILABLE
{3974}
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-L 14 Feb 2003
GSR6 LMTP_SIB_RX
LMTP_SIB_RX
{3974}
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 Lb-interface signalling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Network planning.
Fault finding.
Basis Lb SS7_Link.
Type Counter.

14 Feb 2003 68P02901W56-L 8–35
LMTP_SIB_TX GSR6
LMTP_SIB_TX
{3974}
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 Lb-interface signalling link.
Analysis
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Network planning.
Fault finding.
Basis SS7_Link.
Type Counter.

8–36 68P02901W56-L 14 Feb 2003
GSR6 LMTP_CONGESTION
LMTP_CONGESTION
{3974}
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.

14 Feb 2003 68P02901W56-L 8–37
LMTP_CONGESTION GSR6

8–38 68P02901W56-L 14 Feb 2003
Chapter 9
BSS statistics for Location
Services support

14 Feb 2003 68P02901W56-L 9–1
GSR6

9–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to BSS statistics for supported location services
Introduction to BSS statistics for supported location services

{3974}
Description
This chapter includes descriptions of statistics for the supported BSS location services.
Connection establishment statistics track access and channel request functions. The
following statistics are connection establishment statistics and are pegged for location
services:
S CHAN_REQ_CAUSE_ATMPT.
S OK_ACC_PROC.

14 Feb 2003 68P02901W56-L 9–3
BSSMAP_PERF_LOC_REQ_MSGS GSR6
BSSMAP_PERF_LOC_REQ_MSGS
{3974}
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–4 68P02901W56-L 14 Feb 2003
GSR6 BSSMAP_PERF_LOC_ABORT_MSGS
BSSMAP_PERF_LOC_ABORT_MSGS
{3974}
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.

14 Feb 2003 68P02901W56-L 9–5
BSSMAP_PERF_LOC_RESP_MSGS GSR6
BSSMAP_PERF_LOC_RESP_MSGS
{3974}
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.

9–6 68P02901W56-L 14 Feb 2003
GSR6 BSSMAPLE_PERF_LOC_REQ_MSGS
BSSMAPLE_PERF_LOC_REQ_MSGS
{3974}
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.1
GSM 09.31 v7.1.0, sect 9.1.
Fault finding.
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 9–7
BSSMAPLE_PERF_LOC_ABORT_MSGS GSR6
BSSMAPLE_PERF_LOC_ABORT_MSGS
{3974}
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.11

GSM 09.31 v7.1.0, sect 9.3.
Fault finding.
Basis BSS.
Type Counter.

9–8 68P02901W56-L 14 Feb 2003
GSR6 BSSMAPLE_PERF_LOC_RESP_MSGS
BSSMAPLE_PERF_LOC_RESP_MSGS
{3974}
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.
Reference GSM 03.71 v7.4.0, sect. 7.6, 7.7, 7.11.

GSM 09.31 v7.1.0, sect. 9.2
Fault finding.
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 9–9
BSSLAP_TA_REQ GSR6
BSSLAP_TA_REQ
{3974}
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.

GSM 08.71 v7.2.0, sect. 2.2.1.
Fault finding.
Basis BSS.
Type Counter.

9–10 68P02901W56-L 14 Feb 2003
GSR6 BSSLAP_TA_RESP
BSSLAP_TA_RESP
{3974}
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.

14 Feb 2003 68P02901W56-L 9–11
BSSLAP_TOA_REQ GSR6
BSSLAP_TOA_REQ
{3974}
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.
Reference GSM 03.71 v7.4.0, sect. 9.1.

GSM 08.71 v7.2.0, sect. 2.2.3.
Fault finding.
Basis BSS.
Type Counter.

9–12 68P02901W56-L 14 Feb 2003
GSR6 BSSLAP_REJ
BSSLAP_REJ
{3974}
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.

14 Feb 2003 68P02901W56-L 9–13
BSSLAP_RESET GSR6
BSSLAP_RESET
{3974}
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.

9–14 68P02901W56-L 14 Feb 2003
GSR6 BSSLAP_ABORT_SENT
BSSLAP_ABORT_SENT
{3974}
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.

14 Feb 2003 68P02901W56-L 9–15
BSSLAP_ABORT_RCV GSR6
BSSLAP_ABORT_RCV
{3974}
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.

GSM 08.71 v7.2.0, sect. 2.2.7.
Fault finding.
Basis BSS.
Type Counter.

9–16 68P02901W56-L 14 Feb 2003
GSR6 BSSLAP_MS_POS_CMD
BSSLAP_MS_POS_CMD
{3974}
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.

14 Feb 2003 68P02901W56-L 9–17
BSSLAP_MS_POS_RESP GSR6
BSSLAP_MS_POS_RESP
{3974}
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.

9–18 68P02901W56-L 14 Feb 2003
GSR6 BSSMAP_CONLESS_INFO_RCV
BSSMAP_CONLESS_INFO_RCV
{3974}
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.

14 Feb 2003 68P02901W56-L 9–19
BSSMAP_CONLESS_INFO_SENT GSR6
BSSMAP_CONLESS_INFO_SENT
{3974}
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–20 68P02901W56-L 14 Feb 2003
GSR6 BSSMAPLE_CONLESS_INFO_RCV
BSSMAPLE_CONLESS_INFO_RCV
{3974}
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.

14 Feb 2003 68P02901W56-L 9–21
BSSMAPLE_CONLESS_INFO_SENT GSR6
BSSMAPLE_CONLESS_INFO_SENT
{3974}
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.

9–22 68P02901W56-L 14 Feb 2003
Chapter 10
MTL statistics

14 Feb 2003 68P02901W56-L 10–1
GSR6

10–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to MTL Statistics
Introduction to MTL Statistics
Description
This chapter includes descriptions of the Message Transfer Link (MTL) statistics. MTL
statistics are organized into the following Message Transfer Part (MTP) groups:
S MTP C7 availability.
S MTP C7 performance.
S MTP C7 utilization.
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:
S MTP_LINKFAIL.
S MTP_LOCAL_BUSY.
S MTP_LOCAL_MGT.
S MTP_MGT_INHIBIT.
S MPT_MGT_UNINHIBIT.
S MTP_REMOTE_MGT.
S MTP_REMOTE_PROC.
S MTP_START_RPO.
S MTP_STOP_RPO.
S MTP_UNAVAILABLE.
MTP C7 performance
MTP C7 performance statistics are used track the different types of failure and recovery
situations for the Message Transfer Part (MTP) of the ITU-TSS No.7 protocol on the
BSC to MSC interface. The following are the MTP C7 performance statistics:
S MTP_CHANGEBACK.
S MTP_CHANGEOVER.
S MTP_LINK_INS.
S MTP_NEG_ACKS.
S MTP_RESTORATION.
S MTP_SL_ACK.
S MTP_SL_ALIGNMENT.
S MTP_SL_CONGESTION .
S MTP_SL_ERROR_RATE.
S MTP_SL_FAIL.
S MTP_SL_FIBR.
S MTP_SU_ERROR.

14 Feb 2003 68P02901W56-L 10–3
Introduction to MTL Statistics GSR6
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:
S BUSY_CICS.
S CONGESTION_LOST_MSU .
S MSU_DISCARDED.
S MTP_CONGESTION.
S MTP_MSU_RX.
S MTP_MSU_TX.
S MTP_RE_TX.
S MTP_SIF_SIO_RX.
S MTP_SIF_SIO_TX.
S SIB_RX.
S SIB_TX.
S SL_CONGESTION.
S SL_STOP_CONGESTION.

10–4 68P02901W56-L 14 Feb 2003
GSR6 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.
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.

Network planning.
Optimization.
Basis BSS.

14 Feb 2003 68P02901W56-L 10–5
CONGESTION_LOST_MSU GSR6
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
of lost MSUs due to SL congestion that are acceptable in normal system operations.
If the specified threshold is exceeded, the 11. MTL: SL congestion events resulting in
loss of MSUs – PM alarm is generated. Refer to the Maintenance Information: Alarm
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.

10–6 68P02901W56-L 14 Feb 2003
GSR6 MSU_DISCARDED
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
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
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.

14 Feb 2003 68P02901W56-L 10–7
MTP_CHANGEBACK GSR6
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.

10–8 68P02901W56-L 14 Feb 2003
GSR6 MTP_CHANGEOVER
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.

14 Feb 2003 68P02901W56-L 10–9
MTP_CONGESTION GSR6
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.

10–10 68P02901W56-L 14 Feb 2003
GSR6 MTP_LINK_INS
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.

14 Feb 2003 68P02901W56-L 10–11
MTP_LINKFAIL GSR6
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.

10–12 68P02901W56-L 14 Feb 2003
GSR6 MTP_LOCAL_BUSY
MTP_LOCAL_BUSY
Description
The MTP_LOCAL_BUSY statistic tracks the total time congestion is present on the local
end of the Signalling Link (SL).
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.

14 Feb 2003 68P02901W56-L 10–13
MTP_LOCAL_MGT GSR6
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.

10–14 68P02901W56-L 14 Feb 2003
GSR6 MTP_MGT_INHIBIT
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
Analysis
This statistic can be used for trend analysis on inhibited SLs using the shutdown
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis SS7_LINK.
Type Counter.

14 Feb 2003 68P02901W56-L 10–15
MTP_MGT_UNINHIBIT GSR6
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
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-L 14 Feb 2003
GSR6 MTP_MSU_RX
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.

14 Feb 2003 68P02901W56-L 10–17
MTP_MSU_TX GSR6
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.

10–18 68P02901W56-L 14 Feb 2003
GSR6 MTP_NEG_ACKS
MTP_NEG_ACKS
Description
The MTP_NEG_ACKS statistic tracks when the messages between a BSS and an MSC
get out of sequence.
Pegging
This statistic pegs when the BSS detects out of order messages to the MSC and request
retransmission.
Analysis
of out of sequence 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
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.

14 Feb 2003 68P02901W56-L 10–19
MTP_RE_TX GSR6
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.

10–20 68P02901W56-L 14 Feb 2003
GSR6 MTP_REMOTE_MGT
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.
Type Duration (total time in milliseconds (ms)).

14 Feb 2003 68P02901W56-L 10–21
MTP_REMOTE_PROC GSR6
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.
Type Duration (total time in milliseconds (ms)).

10–22 68P02901W56-L 14 Feb 2003
GSR6 MTP_RESTORATION
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.

14 Feb 2003 68P02901W56-L 10–23
MTP_SIF_SIO_RX GSR6
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.

10–24 68P02901W56-L 14 Feb 2003
GSR6 MTP_SIF_SIO_TX
MTP_SIF_SIO_TX
Description
The MTP_SIF_SIO_TX statistic tracks the number of Signal Information Fields (SIF) or
Service Information Octets (SIO) that are transmitted over a 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.

14 Feb 2003 68P02901W56-L 10–25
MTP_SL_ACK GSR6
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
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
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.

10–26 68P02901W56-L 14 Feb 2003
GSR6 MTP_SL_ALIGNMENT
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
of unsuccessful attempts to align an out of service SL to the A interface that are
If the specified threshold is exceeded, the 5. MTL: SL alignment failure – PM alarm is
generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Minor.

14 Feb 2003 68P02901W56-L 10–27
MTP_SL_CONGESTION GSR6
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
occurrences of excessive congestion duration at the remote that are acceptable in
If the specified threshold is exceeded, the 4. MTL: SL failure - excessive duration of
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis SS7_LINK.
Type Counter.
Alarm Major.

10–28 68P02901W56-L 14 Feb 2003
GSR6 MTP_SL_ERROR_RATE
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
times an SL may be lost due to SUERM timer expirations that are acceptable in normal
system operations.
If the specified threshold is exceeded, the 3. MTL: SL failure - excessive error rate –
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.

14 Feb 2003 68P02901W56-L 10–29
MTP_SL_FAIL GSR6
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
SL failures, excluding those caused by operator interaction with the MMI, that are
If the specified threshold is exceeded, the 0. MTL: SL failure - all reasons – PM alarm
is generated. Refer to the Maintenance Information: Alarm Handling at the OMC-R
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.

10–30 68P02901W56-L 14 Feb 2003
GSR6 MTP_SL_FIBR
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
times an SL may be lost due to the detection of an abnormal FIB that are acceptable in
If the specified threshold is exceeded, the 1. MTL: SL failure - abnormal FIBR/BSNR –
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Major.

14 Feb 2003 68P02901W56-L 10–31
MTP_START_RPO GSR6
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
remote processor outages that are acceptable in normal system operations.
If the specified threshold is exceeded, the 8. MTL: Start of remote processor outage –
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis SS7_LINK.
Type Counter.
Alarm Warning.

10–32 68P02901W56-L 14 Feb 2003
GSR6 MTP_STOP_RPO
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.

14 Feb 2003 68P02901W56-L 10–33
MTP_SU_ERROR GSR6
MTP_SU_ERROR
Description
The MTP_SU_ERROR statistic tracks the number of times erroneous signal units are
received on the Signalling Link (SL).
Pegging
This statistic pegs each time an erroneous signal unit is received on the SL.
Analysis
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 –
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.

10–34 68P02901W56-L 14 Feb 2003
GSR6 MTP_UNAVAILABLE
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.

14 Feb 2003 68P02901W56-L 10–35
SIB_RX GSR6
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.

10–36 68P02901W56-L 14 Feb 2003
GSR6 SIB_TX
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.

14 Feb 2003 68P02901W56-L 10–37
SL_CONGESTION GSR6
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
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
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–38 68P02901W56-L 14 Feb 2003
GSR6 SL_STOP_CONGESTION
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.

14 Feb 2003 68P02901W56-L 10–39
SL_STOP_CONGESTION GSR6

10–40 68P02901W56-L 14 Feb 2003
Chapter 11
CBL, GSL, OML, RSL and XBL
statistics

14 Feb 2003 68P02901W56-L 11–1
GSR6

11–2 68P02901W56-L 14 Feb 2003
GSR6 CBL GSL OML RSL and XBL statistics
CBL GSL OML RSL and XBL statistics
Introduction to CBL, GSL, OML, RSL, and XBL statistics

This chapter includes descriptions of the Cell Broadcast Link (CBL), GPRS Signalling
Link (GSL), Operation and Maintenance Link (OML), Radio System Link (RSL), and
RXCDR to BSC Link (XBL) statistics.
X.25/LAPD Level: X.25 and LAPD

X.25 and LAPD statistics are used to track BSS data transmission information. The
following are the X.25 and LAPD statistics:
S ATER_PREEMPT_STATUS.
S ATER_STATUS.
S FRMR.
S I_FRAMES_RX.
S I_FRAMES_TX.
S INVALID_FRAMES_RX.
S LAPD_CONGESTION.
S N2_EXPIRY.
S SABM_TX.

14 Feb 2003 68P02901W56-L 11–3
ATER_PREEMPT_STATUS GSR6
ATER_PREEMPT_STATUS
Description
The ATER_PREEMPT_STATUS statistic tracks the number of calls pre-empted on an
Ater channel.

0 PREEMPT_ATTEMPT Counts the total number of
pre-emptions attempted of calls
using an Ater channel.
1 CALL_LEG_PREEMPT_EMERG_CALL Counts the number of call legs
pre-empted to support an
emergency call. The emergency call
was able to pre-empt a lower priority
call for an Ater resource.
2 CALL_LEG_PREEMPT_PRI_CALL Counts the number of call legs
pre-empted to support a high priority
non-emergency call. The high
priority call was able to pre-empt a
lower priority call for an Ater
resource.
3 PREEMPT_ATMPT_ATER_UNAVAIL Counts the number of pre-emption
attempts initiated due to no Ater
channels available. When a call
assignment fails or a handover fails
due to no available Ater channels,
the BSC will attempt tp pre-empt a
lower priority call to obtain an Ater
resource.
4 PREEMPT_ATMPT_ATER_SWITCH Counts the number of pre-emption
attempts performed due to
switchover of Ater channels.
5 PREEMPT_FAIL_NO_VULN_CALL Counts the number of pre-emption
failures because no call with a lower
priority was found to pre-empt in
which to obtain an ATER resource
(eg a caller with a high priority was
unable to obtain access to the
network because it was fully utilized
with callers of even higher
priorities).
6 PREEMPT_FAIL_COMM_ERR Counts the number of pre-emption
failures due to BSC-RXCDR
communication errors. The BSC
message protocol to pre-empt an
Ater resource has timed out after
continual attempts to coordinate the
pre-emption of the Ater resource
with the RXCDR.

11–4 68P02901W56-L 14 Feb 2003
GSR6 ATER_PREEMPT_STATUS
Pegging
Counts the number of events relating to ATER pre-emption scenarios on a per XBL
linkset basis.
Reference None.
Usage Network planning, Optimization.

Basis AXCDR
Type Counter array.

14 Feb 2003 68P02901W56-L 11–5
ATER_STATUS GSR6
ATER_STATUS
Description
The ATER_STATUS statistic tracks the Ater channel status on a per XBL linkset basis.

0 ATER_CHAN_REQ Counts the number of Ater channels requested.
1 ATER_CHAN_REQ_FAIL Counts the number of Ater channels requested
but could not be allocated.
2 CALL_ASSIGN_FAIL_CO Counts the number of call assignment failures
MM_ERR due to BSC-RXCDR communication errors. The
BSC message protocol to establish an Ater
resource for the handover has timed out after
continual attempts tp allocate the Ater resource
with the RXCDR.
3 HO_FAIL_COMM_ERR Counts the number of handover failures due to
BSS-RXCDR communication errors. The BSC
message protocol to establish an Ater resource
for the handover has timed out after continual
attempts to allocate the Ater resource with the
RXCDR.
4 CALL_ASSIGN_FAIL_NO Counts the number of call assignment failures
_ATER due to no available Ater channels. When an
assignment failure occurs due to no available
Ater channels, the BSC will attempt to pre-empt
any existing calls to obtain an Ater resource. The
ability to pre-empt depends upon the
emergency/priority setting for the call as well as
the emergency/priority settings of existing cal ls.
5 HO_FAIL_NO_ATER Counts the number of handover failures due to

no available Ater channels. When a handover
failure occurs due to no available Ater channels.
the BSC will attempt to pre-empt any existing
calls to obtain an Ater resource. The ability to
pre-empt depends upon the emergency/priority
setting for the call as well as the
emergency/priority settings of existing calls.
6 BSC_INIT_BLK_CICS_LO Counts the number of times the event BSC
W_ATER initiated blocking of CICs occurred. The pegging
of this statistic represents the scenario where the
number of available Ater channels to an
associated RXCDR falls below the
darbc_threshold when the BSC is operating in
the dynamic allocation mode. The BSc
automatically blocks at the MSC all remaining
idle CICs that are routed through the associated
RXCDR. All out of service and idle CICs will
have the “Low Channel Resources to the
RXCDR” reason set.
Pegging
This statistic pegs the number of events relating to ATER allocation and assignment
occasions on a per XBL linkback basis.

11–6 68P02901W56-L 14 Feb 2003
GSR6 ATER_STATUS
Reference None.

Fault finding.
Basis AXCDR.
Type Counter array.

14 Feb 2003 68P02901W56-L 11–7
FRMR GSR6
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 – 1

ITU-TSS X.20 – X.32
Usage X.25/LAPD.
Fault finding.
Basis X25_LINK/LAPD_LINK.
Type Counter.
Alarm Warning.

11–8 68P02901W56-L 14 Feb 2003
GSR6 I_FRAMES_RX
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.

14 Feb 2003 68P02901W56-L 11–9
I_FRAMES_TX GSR6
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.

11–10 68P02901W56-L 14 Feb 2003
GSR6 INVALID_FRAMES_RX
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.
S X.25
– On the OML (BSS–OMC-R).
– On the CBL (BSS–CBC).
S LAPD
– On the RSL (BSS–BTS link).
– On the XBL (BSC–RXCDR link).

Usage X.25/LAPD.
Fault finding.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 11–11
LAPD_CONGESTION GSR6
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.
NOTE 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.

11–12 68P02901W56-L 14 Feb 2003
GSR6 N2_EXPIRY
N2_EXPIRY
Description
The N2_EXPIRY statistic tracks the number of link alignment retries attempted without
success.
Pegging
This statistic pegs when the retry count threshold has been exceeded.

Usage X.25/LAPD.
Fault finding.
Type Counter.
Alarm Minor.

14 Feb 2003 68P02901W56-L 11–13
SABM_TX GSR6
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.

11–14 68P02901W56-L 14 Feb 2003
Chapter 12
PCU statistics

14 Feb 2003 68P02901W56-L 12–1
GSR6

12–2 68P02901W56-L 14 Feb 2003
GSR6 PCU Statistics
PCU Statistics
Introduction
This chapter describes the Packet Control Unit (PCU) statistics. PCU statistics are
organized in the following groups:
S Gb link (GBL) statistics.
S Accessibility statistics.
S Throughput statistics.
S Dynamic allocation statistics.
NOTE
To facilitate easy access, this chapter presents the statistics in alphabetical
order.
Description of Gb interface
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.
GBL statistics
The GBL measurement types are listed as follows:
S CELL_FLUSH_REQS.
S GBL_DL_DATA_THRPUT.
S GBL_DL_DATA_THRPUT_HIST.
S GBL_FLOW_CTRL_SENT.
S GBL_LINK_INS.
S GBL_PAGING_REQS.
S GBL_UL_DATA_THRPUT.
S GBL_UL_DATA_THRPUT_HIST.
S GBL_UNAVAILABLE.

14 Feb 2003 68P02901W56-L 12–3
PCU Statistics GSR6
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.
The accessibility statistics include the following:
S CHANNEL_REQS_REC.
S CHANNEL_REQS_REJECT.
S {3750}{4386} CHANNEL_REQS_SUCCESS.
S {3750} CODING_SCHEME_CHANGE.
S CS12_ON_32K_CHAN.
S {3635} GPRS_32K_CHANNELS_SWITCHED.
S {3635} GPRS_32K_DL_NOT_AVAIL.
S {3635} GPRS_32K_UL_NOT_AVAIL.
S GPRS_ACCESS_PER_AGCH.
S GPRS_ACCESS_PER_RACH.
S {3969} GPRS_CELL_RESELECT_ATTMPT.
S {3969} GPRS_CELL_RESELECT_FAIL.
S GPRS_CHANNELS_SWITCHED.
S {3969} GPRS_MS_NEIGHBOR_STRONG.
S {3750} GPRS_PCH_AGCH_Q_LENGTH.
S MS_CLASS_1_10_REQ.
S {3725}NO_PDTCH_AVAIL.
S {3725}NO_PDTCH_AVAIL_TIME.

12–4 68P02901W56-L 14 Feb 2003
GSR6 PCU Statistics
Throughput statistics
The throughput statistics are listed as follows:
S {4253} AIR_DL_CONTROL_BLKS.
S AIR_DL_DATA_BLKS.
S {4253} AIR_UL_CONTROL_BLKS.
S AIR_UL_DATA_BLKS.
S {3750} AVAILABLE_PDTCH.
S {3750} DL_BUSY_PDTCH.
S {3750}{3969} DL_PDTCH_CONGESTION.
S {3750}{3969} DL_PDTCH_Q_LENGTH.
S {3750} DL_PDTCH_SEIZURE.
S GBL_DL_DATA_THRPUT.
S GBL_DL_DATA_THRPUT_HIST.
S GBL_UL_DATA_THRPUT.
S GBL_UL_DATA_THRPUT_HIST.
S {3750} IDLE_PDTCH_INTF_BAND0.
S {3750} IMM_ASSGN_CAUSE.
S {4253} PRP_LOAD.
S {3750} UL_BUSY_PDTCH.
S {3750}{3969} UL_PDTCH_CONGESTION.
S {3750} UL_PDTCH_Q_LENGTH.
S {3750}{4386} UL_PDTCH_SEIZURE.
Dynamic allocation statistics

The dynamic allocation statistics are listed as follows:
S GPRS_DYNET_FAILURES.
S GPRS_DYNET_RES_REQS.
S GPRS_DYNET_SWI_REQS.

14 Feb 2003 68P02901W56-L 12–5
AIR_DL_CONTROL_BLKS GSR6
AIR_DL_CONTROL_BLKS
{4253}
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). 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–6 68P02901W56-L 14 Feb 2003
GSR6 AIR_DL_DATA_BLKS
AIR_DL_DATA_BLKS
Description
The AIR_DL_DATA_BLKS statistic tracks the number of blocks sent by the PCU to the
MS for each quality of service (QoS) level and coding scheme combination.
NOTE QoS identifies how delay sensitive the traffic is. Currently only
QoS3 is implemented which is the most delay insensitive traffic
class – it is defined as Best Effort.
The bins are defined in Table 12-1.
Table 12-1 AIR_DL_DATA_BLKS counters

0 QOS1_CS1 Quality of service level 1, coding scheme 1
Pegging
The appropriate bin is incremented by the amount of data blocks sent by the PCU to the
MS for the quality of service and coding scheme. Each count is rounded to the nearest
100 blocks.
Reference None.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–7
AIR_UL_CONTROL_BLKS GSR6
AIR_UL_CONTROL_BLKS
{4253}
Description
The AIR_UL_CONTROL_BLKS statistic tracks the number of uplink control Radio Link
Control (RLC) blocks sent by the MS. 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 Radio Link Control blocks sent by the
MS.
Reference None.
Usage Performance management.
Basis Cell.
Type Counter.

12–8 68P02901W56-L 14 Feb 2003
GSR6 AIR_UL_DATA_BLKS
AIR_UL_DATA_BLKS
Description
The AIR_UL_DATA_BLKS statistic tracks the number of data blocks received by the
PCU for each quality of service level and coding scheme combination.
The bins are defined in Table 12-2.
Table 12-2 AIR_UL_DATA_BLKS counters

Pegging
The appropriate bin is incremented by the amount of data blocks received for the quality
of service and coding scheme. The count is rounded to the nearest 100 blocks.
Reference None.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–9
AVAILABLE_PDTCH GSR6
AVAILABLE_PDTCH
{3750}
Description
This statistic measures the mean and max number of available Packet Data Traffic
CHannels (PDTCH).
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, it will be pegged with the
same value as before).
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
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 Digital cellular telecommunications systems

(phase 2+) Version 7.0.0 Jan 2000 ETSI.
Usage Congestion.
Network planning.
Basis Cell.
Type Gauge.

12–10 68P02901W56-L 14 Feb 2003
GSR6 CELL_FLUSH_REQS
CELL_FLUSH_REQS
{3750}
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 flushable messages
received by the BSS.
Reference None.
Congestion.
Basis Cell
Type Counter.
NOTE This statistic was previously known as GBL_FLUSH_REQS.

14 Feb 2003 68P02901W56-L 12–11
CHANNEL_REQS_REC GSR6
CHANNEL_REQS_REC
Description
The CHANNEL_REQS_REC statistic tracks the number of channel or resource request
messages received by the PCU.
Pegging
This statistic pegs for each channel request message received by the PCU.
{4386} This statistic pegs when:
S A one phase channel request is received.
S An Enhanced One–Phase (EOP) access indication is received.
S A Packet Resource Request (PRR) message is received.
S A Packet Downlink Ack/Nack (PDAK) message is received.
Reference None.
Basis Cell.
Type Counter.

12–12 68P02901W56-L 14 Feb 2003
GSR6 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 an packet access reject message is sent to the MS in response
to a packet resource request when there are no resources left to allocate.
Reference None.
Congestion.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–13
CHANNEL_REQS_SUCCESS GSR6
CHANNEL_REQS_SUCCESS
{3750} {4386}
Description
This statistic measures the number of packet resource assignments sent to the mobile.
This statistic counts the number of PACKET UPLINK ASSIGNMENT messages sent to
the MS. Re-transmissions are excluded.
Pegging
This statistic pegs each time a PACKET UPLINK ASSIGNMENT message is sent to the
mobile. Retransmissions are not pegged.
S A one phase Immediate Assignment (IA) is sent.
S An Enhanced One–Phase (EOP) access indication is received.
S A Packet Uplink Assignment (PUA) is initially sent to establish the Temporary
Block Flow (TBF).
S A Packet Timeslot Reconfigure (PTR) is initially sent to establish an uplink TBF
when a downlink TBF is in progress.
Analysis
The statistic can be used for the trend analysis of the number of successful uplink GPRS
calls made by a particular CELL.

Usage Congestion, network planning.
Basis Cell.
Type Counter.

12–14 68P02901W56-L 14 Feb 2003
GSR6 CODING_SCHEME_CHANGE
CODING_SCHEME_CHANGE
{3750}
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.
The bins are:
S Total number of coding scheme upgrades for uplink.
S Total number of coding scheme downgrades for uplink.
S Total number of coding scheme upgrades for downlink.
S Total number of 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.

Usage Congestion, network planning.
Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–15
CS12_ON_32K_CHAN GSR6
CS12_ON_32K_CHAN
{3635}
Description
The CS12_ON_32K_CHAN statistic tracks the percentage of time in a statistics reporting
period that 32 kilobits per second 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.

12–16 68P02901W56-L 14 Feb 2003
GSR6 DL_BUSY_PDTCH
DL_BUSY_PDTCH
{3750}
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).
The bins are:
S No PDTCH is busy (time duration).
S 1-2 PDTCH are busy (time duration).
Pegging
This statistic pegs every packet-scheduling period (20 millisecond) by sampling the
number of PDTCHs that are carrying downlink packet traffic.
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for
downlink packet traffic.

Usage Network planning, congestion.
Basis Cell

14 Feb 2003 68P02901W56-L 12–17
DL_PDTCH_CONGESTION GSR6
DL_PDTCH_CONGESTION
{3750} {3969}
Description
The DL_PDTCH_CONGESTION statistic calculates all available Packet Data Channel
(PDCH) allocated time for downlink. This statistic is obtained by measuring the total
number (in terms of block period – 20 millisecond) of times a cell is congested due to MS
load on the available air resources on the downlink (that is, a 4 timeslot MS allocated in a
cell with 4 PDCHs).
Pegging
This statistic pegs every 20 millisecond when a Packet Data Traffic CHannel (PDTCH) is
not available on the downlink due to congestion.
Analysis
This statistic is totalled in terms of 20 millisecond block periods.

Basis Cell.
Type Counter.

12–18 68P02901W56-L 14 Feb 2003
GSR6 DL_PDTCH_Q_LENGTH
DL_PDTCH_Q_LENGTH
{3750}{3969}
Description
{3969}This statistic is obtained by sampling the Downlink Request Queue. The statistic is
updated at every 8000 millisecond.
NOTE In the current Motorola PCU implementation, there is no

downlink queueing. Downlink requests are always successful.
Pegging
This statistic pegs each time a new message enters the downlink PDTCH queue or when
a message waiting in the downlink PDTCH queue gets processed.
Analysis
This statistic can be used for the trend analysis of the average number of downlink
messages waiting for a PDTCH to become available.

Usage {3969}Network planning, congestion.
Basis Cell.
Type Gauge.

14 Feb 2003 68P02901W56-L 12–19
DL_PDTCH_SEIZURE GSR6
DL_PDTCH_SEIZURE
{3750}
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 pegs when the receipt of the first downlink RLC block (PDU) on the PDTCH
from the network is obtained.
Analysis
This statistic can be used for the trend analysis of the total number of TBFs on the
downlink for a CELL.

Basis Cell.
Type Counter.

12–20 68P02901W56-L 14 Feb 2003
GSR6 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:
S dl_datathrput_mean.
S dl_datathrput_max.
Reference None.
Congestion.
Basis GBL.
Type Gauge.

14 Feb 2003 68P02901W56-L 12–21
GBL_DL_DATA_THRPUT_HIST GSR6
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-3.
Table 12-3 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-3 for the ranges.
Analysis
This statistic can be used for the trend analysis of GBL downlink throughput.
S dl_thrput_min.
S dl_thrput_mean.
S dl_thrput_max.
Reference None.
Congestion.
Quality of service monitoring: Network
accessibility.
Basis GBL.
Type Normal Distribution.

12–22 68P02901W56-L 14 Feb 2003
GSR6 GBL_FLOW_CTRL_SENT
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.
accessibility.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–23
GBL_LINK_INS GSR6
GBL_LINK_INS
Description
The GBL_LINK_INS statistic tracks the amount of time in milliseconds that a specified
GBL is in service.
Pegging
The timer for this statistic starts when the GBL transitions to the B-U state (that is,
returns to service). The timer for this statistic stops when the GBL is no longer in the
B-U state (that is, goes out of service).
Analysis
This statistic can be used for trend analysis of GBL usage.
Reference None.
Usage Network accessibility.
Fault finding.
Protocol utilization.
Basis GBL.
Type Duration.

12–24 68P02901W56-L 14 Feb 2003
GSR6 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 BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 12–25
GBL_UL_DATA_THRPUT GSR6
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.
S ul_datathrput_mean.
S ul_datathrput_max.
Reference None.
Congestion.
Basis GBL.
Type Gauge.

12–26 68P02901W56-L 14 Feb 2003
GSR6 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-4.
There are 10 bins for this array.
Table 12-4 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
Analysis
This statistic can be used for the trend analysis of GBL uplink throughput.
S ul_thrput_min.
S ul_thrput_mean.
S ul_thrput_max.
Reference None.
Congestion.
accessibility.
Basis GBL.

14 Feb 2003 68P02901W56-L 12–27
GBL_UNAVAILABLE GSR6
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.

12–28 68P02901W56-L 14 Feb 2003
GSR6 GPRS_32K_CHANNELS_SWITCHED
GPRS_32K_CHANNELS_SWITCHED
{3635}
Description
This statistic keeps a count of the number of times that 32 kilobits per second GPRS
timeslots are used for circuit–switched 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 call.
Reference None.
Network planning.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–29
GPRS_32K_DL_NOT_AVAIL GSR6
GPRS_32K_DL_NOT_AVAIL
{3635}
Description
The GPRS_32K_DL_NOT_AVAIL statistic tracks the number of times that 32 kilobits per
second GPRS timeslots could not be allocated when needed for downlink coding
schemes 3 and 4 transfers in a statistics reporting period on a per–cell basis.
Pegging
This statistic is pegged when a 32 kilobits per second GPRS air timeslot is needed to
complete a downlink transfer and none is available. There is no specific message
involved in the pegging, the pegging is activated when a downlink request cannot be
serviced.
Reference None.
Network planning.
Basis Cell.
Type Counter.

12–30 68P02901W56-L 14 Feb 2003
GSR6 GPRS_32K_UL_NOT_AVAIL
GPRS_32K_UL_NOT_AVAIL
{3635}
Description
The GPRS_32K_UL_NOT_AVAIL statistic tracks the number of times that 32 kilobits per
second GPRS timeslots could not be allocated when needed for uplink coding schemes 3
and 4 transfers in a statistics reporting period on a per–cell basis.
Pegging
This statistic is pegged when a 32 kilobits per second GPRS air timeslot is needed to
complete an uplink transfer and none is available. There is no specific message involved
in the pegging, the pegging is activated when an uplink request cannot be serviced.
Reference None.
Network planning.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–31
GPRS_ACCESS_PER_AGCH GSR6
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.
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.

12–32 68P02901W56-L 14 Feb 2003
GSR6 GPRS_CELL_RESELECT_ATTMPT
GPRS_CELL_RESELECT_ATTMPT
{3969}
Description
The GPRS_CELL_RESELECT_ATTMPT statistic tracks the number of Network
Controlled cell reselect attempts from the originating cell.
Pegging
This statistic pegs when the BSS initiates a cell change order procedure for an MS in
packet idle mode by sending an Immediate Assignment message with a downlink single
block allocation in a CCCH block monitored by an MS.
Analysis
This statistic can be used for analysis of Network Controlled cell reselect attempts from
an originating cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–33
GPRS_CELL_RESELECT_FAIL GSR6
GPRS_CELL_RESELECT_FAIL
{3969}
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.

12–34 68P02901W56-L 14 Feb 2003
GSR6 GPRS_ACCESS_PER_RACH
GPRS_ACCESS_PER_RACH
Description
{3750} 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.

14 Feb 2003 68P02901W56-L 12–35
GPRS_CHANNELS_SWITCHED GSR6
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).
Pegging
This statistic pegs when a 16 kilobits per second PDTCH is switched to a circuit switched
TCH.
Reference None.
Network planning.
Basis Cell.
Type Counter.

12–36 68P02901W56-L 14 Feb 2003
GSR6 GPRS_DYNET_FAILURES
GPRS_DYNET_FAILURES
Description
The GPRS_DYNET_FAILURES statistic tracks the totals for four different sources of
terrestrial backing failure.
The sources of terrestrial backing failure are listed below.
S Terrestrial resource for a reserved GPRS timeslot is not provided when requested.
S Terrestrial backing is taken from switchable timeslots. This happens for
emergency and non-emergency calls.
S Terrestrial backing is taken from reserved timeslots. This happens for emergency
calls and link failures only.
S When converting a switchable GPRS timeslot from packet to circuit mode and
terrestrial backing is unavailable.

0 RSV_GPRS_BLK Resource unavailable for a reserved timeslot
1 SW_GPRS_PREEMP Resource stolen from a switchable timeslot
2 RSV_GPRS_PREEMP Resource stolen from a reserved timeslot
3 CHANGEOVER_CS_FAIL Changeover to CS mode failed – resources
reserved
Pegging
This statistic is pegged only when both dynamic allocation and GPRS are unrestricted.
This statistic is not pegged if either feature is restricted.
Analysis
This statistic can be used to analyse how effectively terrestrial backing resources are
allocated for a particular site. Bin counts can be observed to determine the effects of
blocking, preemption, and unavailable terrestrial resources with GPRS.
Reference None.
Network accessibility.
Basis Dynet.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–37
GPRS_DYNET_RES_REQS GSR6
GPRS_DYNET_RES_REQS
Description
The GPRS_DYNET_RES_REQS statistic tracks the time that the number of requests for
backing of reserved timeslots were in the queue. Each bin corresponds to a range of
queue lengths.
There are 10 bins for this array. The ranges are shown in Table 12-5.
Table 12-5 GPRS_DYNET_RES_REQS bins

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 – 50
Pegging
When this statistic is pegged, the bin corresponding to the length of the queue is
incremented by one. The maximum and minimum queue length and the average queue
length is reported.
Reference None.
Basis Dynet.

12–38 68P02901W56-L 14 Feb 2003
GSR6 GPRS_DYNET_SWI_REQS
GPRS_DYNET_SWI_REQS
Description
The GPRS_DYNET_SWI_REQS statistic tracks the time that the number of requests for
terrestrial backing of switchable GPRS timeslots were in the Dynamic Allocation queue.
Each bin corresponds to a range of queue lengths.
There are 10 bins for this array. The ranges are shown in Table 12-6.
Table 12-6 GPRS_DYNET_SWI_REQS bins

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 – 50
Pegging
When this statistic is pegged, the bin corresponding to the length of the queue is
incremented by one. The maximum and minimum queue length and the average queue
length are reported.
Reference None.
Basis Dynet.

14 Feb 2003 68P02901W56-L 12–39
GPRS_MS_NEIGHBOR_STRONG GSR6
GPRS_MS_NEIGHBOR_STRONG
{3969}
Description
The GPRS_MS_NEIGHBOR_STRONG statistic tracks the number of GPRS MS(s) for
which the rxlev of any neighbour cell is stronger by a certain threshold than the rxlev of
the serving cell.
Pegging
This statistic pegs whenever a Packet Measurement Report is received from an MS.
Analysis
This statistic is obtained by measuring the number of GPRS MS/s for which the receive
level (rxlev) of any neighbour cell is stronger than the rxlev of the serving cell by a
defined threshold in the Packet Measurement Report message. The counter is
incremented only once for an MS if the multiple Packet Measurement Report shows a
better rxlev than the serving cell.
Reference None.
Network planning.
Basis Cell.
Type Counter.

12–40 68P02901W56-L 14 Feb 2003
GSR6 GPRS_PCH_AGCH_Q_LENGTH
GPRS_PCH_AGCH_Q_LENGTH
{3750}
Description
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
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.

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.

14 Feb 2003 68P02901W56-L 12–41
IDLE_PDTCH_INTF_BAND0 GSR6
IDLE_PDTCH_INTF_BAND0
{3750}
Description
The IDLE_PDTCH_INTF_BAND0 statistic tracks the maximum and mean number of idle
uplink Packet Data Traffic CHannels (PDTCHs) for interference band 0. An idle PDTCH
falls into band 0 if its average interference band is less than the value of the element
interfer_bands, 0.
NOTE Idle PDTCHs are allocated to five interference bands. Each

band has an associated statistic for tracking idle PDTCHs.
Pegging
This statistic is updated at every idle frame receipt. The PDTCH is said to be idle if it can
be allocated for a request. An idle PDTCH 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.

(phase 2+) Version 7.0.0 Jan 2000 ETSI..
Fault finding.
Basis Cell.
Type Gauge.

12–42 68P02901W56-L 14 Feb 2003
GSR6 IDLE_PDTCH_INTF_BAND1
{3750}
Description
interfer_bands, 1.

Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.

14 Feb 2003 68P02901W56-L 12–43
{3750}
Description
interfer_bands, 2.

Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.

12–44 68P02901W56-L 14 Feb 2003
GSR6 IDLE_PDTCH_INTF_BAND3
{3750}
Description
interfer_bands, 3.

Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.

14 Feb 2003 68P02901W56-L 12–45
{3750}
Description
interfer_bands, 4.

Pegging
Analysis

Fault finding.
Basis Cell.
Type Gauge.

12–46 68P02901W56-L 14 Feb 2003
GSR6 IMM_ASSGN_CAUSE
IMM_ASSGN_CAUSE
{3750}
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 as follows:
Table 12-7 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.
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.
Analysis
It represents the total number of IAs pegged during the statistics interval, on a per-cause
basis.


14 Feb 2003 68P02901W56-L 12–47
IMM_ASSGN_CAUSE GSR6
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–48 68P02901W56-L 14 Feb 2003
GSR6 MS_CLASS_1_10_REQ
MS_CLASS_1_10_REQ
Description
The MS_CLASS_1_10_REQ statistic tracks the number of requests received for the MS
classes 1 through 10.
Each bin corresponds to a particular MS class as shown in Table 12-8.
Table 12-8 MS_CLASS_1_10_REQ bins

0 MS_CLASS_1_REQ Number of requests for class 1
Pegging
This is one of three statistics that is pegged every time there is an uplink request from an
MS. The other two are MS_CLASS_11_20_REQ and MS_CLASS_21_29_REQ.
Reference GSM 05.02, 6.2.0, Annex B.

Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–49
MS_CLASS_11_20_REQ GSR6
MS_CLASS_11_20_REQ
Description
The MS_CLASS_11_20_REQ statistic tracks the number of requests received for the
MS classes 11 through 20.

Pegging
This is one of three stats that is pegged every time there is an uplink request from an

Basis Cell.
Type Counter array.

12–50 68P02901W56-L 14 Feb 2003
GSR6 MS_CLASS_21_29_REQ
MS_CLASS_21_29_REQ
Description
The MS_CLASS_21_29_REQ statistic tracks the number of requests received for the
MS classes 21 through 29.

Pegging
This is one of three stats that is pegged every time there is an uplink request from an

Basis Cell.
Type Counter array.

14 Feb 2003 68P02901W56-L 12–51
NO_PDTCH_AVAIL GSR6
NO_PDTCH_AVAIL
{3725}
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.
Reference None.
Basis Cell.
Type Counter.

12–52 68P02901W56-L 14 Feb 2003
GSR6 NO_PDTCH_AVAIL_TIME
NO_PDTCH_AVAIL_TIME
{3725}
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.
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
Reference None.
Basis Cell.
Type Duration.

14 Feb 2003 68P02901W56-L 12–53
PRP_LOAD GSR6
PRP_LOAD
{4253}
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-11 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-11 Mapping between timeslots pending service and PRP load
Number of timeslots pending PRP Load
service in a 20 msec block period
0-30 0-100
31-60 101-200
61-90 201-300
91-120 301-400
Each bin of this statistic represents the following PRP load range.
Table 12-12 PRP load range

Bin Number 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.

12–54 68P02901W56-L 14 Feb 2003
GSR6 PRP_LOAD
Reference None.
Basis This statistic is based on each DPROC.

14 Feb 2003 68P02901W56-L 12–55
UL_BUSY_PDTCH GSR6
UL_BUSY_PDTCH
{3750}
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).
The bins are:
Table 12-13 UL_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 uplink packet traffic.
Analysis
This statistic can be used for trend analysis of the number of PDTCHs that are used for
uplink packet traffic.

Basis Cell.

12–56 68P02901W56-L 14 Feb 2003
GSR6 UL_PDTCH_CONGESTION
UL_PDTCH_CONGESTION
{3750} {3969}
Description
The UL_PDTCH_CONGESTION statistic measures all available Packet Data CHannel
(PDCH) allocated time for uplink. This statistic is obtained by measuring the total
number (in terms of block period – 20 millisecond) of times a cell is congested due to MS
load on the available air resources on the uplink (that is, a 4 timeslot MS allocated in a
cell with 4 PDCHs).
Pegging
This statistic pegs every 20 millisecond when a Packet Data Traffic CHannel (PDTCH) is
not available on the uplink due to congestion.
Analysis
This statistic is totalled in terms of 20 millisecond block periods.

Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–57
UL_PDTCH_Q_LENGTH GSR6
UL_PDTCH_Q_LENGTH
{3750}
Description
{3969}This statistic is obtained by sampling the Uplink Request Queue. The statistic is
updated at every 8000 millisecond.
Pegging
This statistic pegs each time a new message enters the uplink PDTCH queue or when a
message waiting in the uplink PDTCH queue gets processed.
Analysis
This statistic can be used for the trend analysis of the average number of uplink
messages waiting for a PDTCH to become available.
{3969}This statistic can be used for trend analysis of the number of queued uplink
PDTCH requests.

Usage {3969}Network planning, congestion.
Basis Cell.
Type Gauge.

12–58 68P02901W56-L 14 Feb 2003
GSR6 UL_PDTCH_SEIZURE
UL_PDTCH_SEIZURE
{3750}{4386}
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.
S The first uplink data block is received during a two–phase uplink TBF
establishment.
S 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.

Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 12–59
UL_PDTCH_SEIZURE GSR6

12–60 68P02901W56-L 14 Feb 2003
Chapter 13
BSS-SMLC statistics

14 Feb 2003 68P02901W56-L 13–1
GSR6

13–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to BSS-based SMLC statistics
Introduction to BSS-based SMLC statistics

{3974}
Description
This chapter includes descriptions of the BSS-based SMLC statistics. BSS-based
Serving Mobile Location Centre (SMLC) statistics are organized into two major
subgroups:
S BSS C7 utilization.
S SCCP performance and utilization.
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:
S L_SIF_SIO_RX_OPC.
S L_SIF_SIO_TX_DPC.
S L_SIF_SIO_TYPE.
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:
S PAGE_REQ_FROM_SMLC_FAIL.
S L_ROUTING_SYNTAX.
S L_ROUTING_UNKNOWN.
S L_SCCP_MSGS.
S L_SCCP_MSGS_RX.
S L_SCCP_MSGS_TX.
S L_SIF_SIO_RX_OPC.
S L_SIF_SIO_TX_DPC.
S L_SIF_SIO_TYPE.

14 Feb 2003 68P02901W56-L 13–3
PAGE_REQ_FROM_SMLC_FAIL GSR6
PAGE_REQ_FROM_SMLC_FAIL
{3974}
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
of failures that are acceptable in normal system operations.
If the specified threshold is exceeded, the 20. BSS: Paging request from SMLC
Handling at the OMC (68P02901W26) for troubleshooting information.
Reference GSM 8.08, 3.9.2, 3.1.10 and 3.2.1.19.

Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.

13–4 68P02901W56-L 14 Feb 2003
GSR6 L_ROUTING_SYNTAX
L_ROUTING_SYNTAX
{3974}
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
BSS-based SMLC. Excessive syntax errors can result in degraded SCCP performance.
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 alarm is generated. Refer to the Maintenance Information:
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.

14 Feb 2003 68P02901W56-L 13–5
L_ROUTING_UNKNOWN GSR6
L_ROUTING_UNKNOWN
{3974}
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.
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 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).
Fault finding.
Basis BSS.
Type Counter.
Alarm Warning.

13–6 68P02901W56-L 14 Feb 2003
GSR6 L_SCCP_MSGS
L_SCCP_MSGS
{3974}
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
BSS-based SMLC. This statistic can be used for trend analysis of SCCP performance
and utilization.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 13–7
L_SCCP_MSGS_RX GSR6
L_SCCP_MSGS_RX
{3974}
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:
S the number of SCCP messages received for class 0 will be stored in
l_sccp_msgs_rx_0.
S 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
BSS-based SMLC. This statistic can be used for trend analysis of the activity on an SL.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

13–8 68P02901W56-L 14 Feb 2003
GSR6 L_SCCP_MSGS_TX
L_SCCP_MSGS_TX
{3974}
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.
S the number of SCCP messages transmitted for class 0 will be stored in
l_sccp_msgs_tx_0.
S 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
BSS-based SMLC. This statistic can be used for trend analysis of the activity over the
Lb-interface.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

14 Feb 2003 68P02901W56-L 13–9
L_SIF_SIO_RX_OPC GSR6
L_SIF_SIO_RX_OPC
{3974}
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
BSS-based SMLC. This statistic can be used for trend analysis of the activity on all
Lb-interface SLs for a particular BSS.
Reference GSM 12.07, 3.0.2, 2.8.6.a.

ITU-TSS Q.791 – (3.2 – 3.10).
Basis BSS.
Type Counter.

13–10 68P02901W56-L 14 Feb 2003
GSR6 L_SIF_SIO_TX_DPC
L_SIF_SIO_TX_DPC
{3974}
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.

14 Feb 2003 68P02901W56-L 13–11
L_SIF_SIO_TYPE GSR6
L_SIF_SIO_TYPE
{3974}
Description
This statistic tracks the number of SIF MTP, TEST, and SCCP SIOs transmitted or
received on all Lb-interface SLs.
S the number of SIF SCCP SIOs will be stored in l_sif_sio_type.
S the number of SIF MTP SIOs will be stored in l_sif_sio_type_mtp.
S 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–12 68P02901W56-L 14 Feb 2003
Chapter 14
Web MMI statistics

14 Feb 2003 68P02901W56-L 14–1
GSR6

14–2 68P02901W56-L 14 Feb 2003
GSR6 MMI Statistics
MMI Statistics
Introduction
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 Chapter 12
CHANNEL_REQS_REJ Chapter 12
GBL_LINK_INS Chapter 12
GBL_PAGING_REQS Chapter 12
GBL_UNAVAILABLE Chapter 12
The following MMI BSC/BTS real-time statistics are documented elsewhere in this
manual. Table 14-2 indicates the location of these descriptions.
Table 14-2 Location of MMI BSC/BTS PCU real-time stats descriptions

MMI BSC/BTS statistic Location in manual
ALLOC_SDCCH_FAIL Chapter 4
ALLOC_TCH_FAIL Chapter 4
HO_FAIL_NO_RESOURCES Chapter 4
HO_REQ_MSC_FAIL Chapter 4
MA_CMD_TO_MS_BLKD Chapter 4
RF_LOSSES_TCH Chapter 6

14 Feb 2003 68P02901W56-L 14–3
MMI Statistics GSR6

14–4 68P02901W56-L 14 Feb 2003
Chapter 15
Call model statistics

14 Feb 2003 68P02901W56-L 15–1
GSR6

15–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to call model statistics
Introduction to call model statistics
Description
This chapter describes the derivation of call model parameter values 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:
S CALL_DURATION (T).
S CALL_SETUP_BLOCKING_RATE.
S HANDOVERS_PER_CALL (H).
S IMSI_DETACHES_TO_CALLS (Id).
S INTRA_BSS_HO_TO_ALL_HO (i).
S LOCATION_UPDATE_FACTOR (L).
S LOCATION_UPDATES_TO_CALLS (l).
S PAGES_PER_CALL (Ppc).
S PAGES_PER_SECOND.
S PAGING_RATE (P).
S SMS_TO_CALL_RATIO (S).
Refer to the System Information: BSS Equipment Planning (68P02900W21) for further
information on the call model parameters.

14 Feb 2003 68P02901W56-L 15–3
CALL_DURATION (T) GSR6
CALL_DURATION (T)
Description
This statistic provides the average call duration.
Formula
ȍ(BUSY_TCH_MEAN) * stat_interval_in_sec
N
i+1
T+
ȍ(TOTAL_CALLS ) ASSIGNMENT_REDIRECTION)
N
i+1
Where: N is: 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.
NOTE
The ASSIGNMENT_REDIRECTION statistic is only available from software
release GSR5 onwards.

Optimization.
Basis Cell.
Units Seconds
Raw BUSY_TCH_MEAN.
Statistics TOTAL_CALLS.
ASSIGNMENT_REDIRECTION.

15–4 68P02901W56-L 14 Feb 2003
GSR6 CALL_SETUP_BLOCKING_RATE
CALL_SETUP_BLOCKING_RATE
Description
This statistic provides the percentage of attempts to allocate a TCH call setup that were
blocked.
Formula
MA_CMD_TO_MS_BLKD * 100
CALL_SETUP_BLOCKING_RATE +
MA_REQ_FROM_MSC

Optimization.
Basis Cell.
Units Percentage.
Raw MA_CMD_TO_MS_BLKD.
Statistics MA_REQ_FROM_MSC.

14 Feb 2003 68P02901W56-L 15–5
HANDOVERS_PER_CALL (H) GSR6
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
ȍ(OUT_INTER_BSS_REQ_TO_MSC ) OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)

N
i+1
H+
N
i+1
NOTE
The TOTAL_CALLS parameter is the count of the total circuit-switched calls in
a cell. It should be summed for all the cells in the BSC, when used in the
previous formula.

Optimization.
Basis Cell.
Raw OUT_INTER_BSS_REQ_TO_MSC.
Statistics OUT_INTRA_BSS_HO_ATMPT.
INTRA_CELL_HO_ATMPT.
TOTAL_CALLS.

15–6 68P02901W56-L 14 Feb 2003
GSR6 IMSI_DETACHES_TO_CALL (Id)
IMSI_DETACHES_TO_CALL (Id)
Description
This statistic provides the ratio of IMSI detaches per call.
Formula
ȍ OK_ACC_PROC[IMSI_DETACH]
N
i+1
Id +
N
i+1

Optimization.
Basis Cell.
Raw OK_ACC_PROC [IMSI_DETACH].


14 Feb 2003 68P02901W56-L 15–7
INTRA_BSS_HO_TO_ALL_HO (i) GSR6
INTRA_BSS_HO_TO_ALL_HO (i)
Description
This statistic provides the ratio of intra–BSS handovers to all handovers.
Formula
ȍ (OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)
N
i+1
i+
ȍ OUT_INTER_BSS_REQ_TO_MAC ) OUT_INTRA_BSS_HO_ATMPT ) INTRA_CELL_HO_ATMPT)
N
i+1

Optimization.
Basis Cell.
Raw OUT_INTRA_BSS_HO_ATMPT.
Statistics INTRA_CELL_HO_ATMPT.
OUT_INTER_BSS_REQ_TO_MAC.
TOTAL_CALLS.

15–8 68P02901W56-L 14 Feb 2003
GSR6 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:
S L = LOCATION_UPDATES_TO_CALLS (IMSI detach disabled i.e. Id=0 )
S L = LOCATION_UPDATES_TO_CALLS + 0.2* IMSI_DETACHES_TO_CALLS
(type 1)
S L = LOCATION_UPDATES_TO_CALLS + 0.5* IMSI_DETACHES_TO_CALLS
(type 2)

Optimization.
Basis Cell.
Call Model LOCATION_UPDATES_TO_CALLS.

Statistics IMSI_DETACHES_TO_CALLS.

14 Feb 2003 68P02901W56-L 15–9
LOCATION_UPDATES_TO_CALLS (I) GSR6
LOCATION_UPDATES_TO_CALLS (I)
Description
This statistic provides the ratio of location updates to calls.
Formula
ȍ OK_ACC_PROC[LOCATION UPDATE]
N
i+1
I+
N
i+1

Optimization.
Basis Cell.
Raw OK_ACC_PROC [LOCATION UPDATE].


15–10 68P02901W56-L 14 Feb 2003
GSR6 PAGES_PER_CALL (PPC)
PAGES_PER_CALL (PPC)
Description
This statistic provides the number of pages per call.
Formula
ȍ PAGE_REQ_FROM_MSC
N
i+1
P pc +
N
i+1
Where: N is: the number of cells under the BSC.

Optimization.
Basis Cell.
Call PAGE_REQ_FROM_MSC.
Model/Raw TOTAL_CALLS.
Statistics ASSIGNMENT_REDIRECTION.
PAGING_RATE.
CALL_DURATION.

14 Feb 2003 68P02901W56-L 15–11
PAGES_PER_SECOND GSR6
PAGES_PER_SECOND
Description
This statistic provides the number of pages per second.
Formula
PAGE_REQ_FROM_MSC
PAGES_PER_SECOND +
INTERVAL_SUM * 3600

Optimization.
Basis Cell.
Raw Statistics PAGE_REQ_FROM_MSC.
INTERVAL_SUM.

15–12 68P02901W56-L 14 Feb 2003
GSR6 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
ȍ(PAGE_REQ_FROM_MSC)
N
i+1
P+
stat_interval_in_seconds [ith location area in BSC]
Where: N is: the number of location areas.
NOTE
PAGE_REQ_FROM_MSC should be the maximum per cell value for each
location area.

Optimization.
Basis Cell.
Raw PAGE_REQ_FROM_MSC.
Statistics

14 Feb 2003 68P02901W56-L 15–13
SMS_TO_CALL_RATIO (S) GSR6
SMS_TO_CALL_RATIO (S)
Description
This statistic provides the ratio of SMSs to calls.
Formula
(SMS_INIT_ON_SDCCH ) SMS_INIT_ON_TCH)
S + ((
CM_SERV_REQ_CALL ) CM_SERV_REQ_SMS ) CM_SERV_REQ_EMERG ) PAGE_RESPONSE) * (SMS_INIT_ON_SDCCH))

Optimization.
Basis Cell.
Raw SMS_INIT_ON_SDCCH.
Statistics SMS_INIT_ON_TCH.
CM_SERV_REQ_CALL.
CM_SERV_REQ_SMS.
CM_SERV_REQ_EMERG.
PAGE_RESPONSE.

15–14 68P02901W56-L 14 Feb 2003
Chapter 16
Key statistics

14 Feb 2003 68P02901W56-L 16–1
GSR6

16–2 68P02901W56-L 14 Feb 2003
GSR6 Key statistics
Key statistics
Description
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.
The key statistics are divided into the following groups:
S Call summary.
S Channel usage.
S Connection establishment.
S RF loss summary.
S MTL utilisation.
Call summary
Call summary statistics are used to determine assignment and handover performance of
one or more cells. The following are call summary statistics:
S CALL_SETUP_SUCCESS_RATE.
S HANDOVER_FAILURE_RATE.
S HANDOVER_SUCCESS_RATE.
S SUCCESS_INTERNAL_HO.
S TOTAL_CALLS_KEY.
S UNSUCCESS_INTERNAL_HO_NOREEST.
S UNSUCCESS_INTERNAL_HO_REEST.
Channel usage
Channel usage statistics are used to determine SDCCH and TCH performance levels.
The following are channel usage statistics:
S MEAN_TCH_BUSY_TIME.
S SDCCH_BLOCKING_RATE.
S SDCCH_MEAN_ARRIVAL_RATE.
S SDCCH_MEAN_HOLDING_TIME.
S SDCCH_TRAFFIC_CARRIED.
S TCH_BLOCKING_RATE.
S TCH_MEAN_ARRIVAL_RATE.
S TCH_MEAN_HOLDING_TIME.
S TCH_TRAFFIC_CARRIED.

14 Feb 2003 68P02901W56-L 16–3
Key statistics GSR6
Connection statistics are used to determine the number and interval of attempted and
successful assignment requests. The following are connection establishment statistics:
S ATTEMPT_IMMED_ASSIGN_PROC .
S MEAN_ARRIVAL_TIME_BETWEEN_CALLS .
S MEAN_INTER_ARRIVAL_TIME.
S SUCCESS_IMMED_ASSIGN_PROC.
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:
S CELL_TCH_ALLOCATIONS.
S CELL_TCH_ASSIGNMENTS.
S RF_LOSS_RATE.
S SDCCH_RF_LOSS_RATE.
S TCH_RF_LOSS_RATE.
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:
S MTL_UTILISATION_RX.
S MTL_UTILISATION_TX.

16–4 68P02901W56-L 14 Feb 2003
GSR6 Key statistics
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.
NOTE The template headings are used as required and are not present
for all statistics.

14 Feb 2003 68P02901W56-L 16–5
ATTEMPT_IMMED_ASSIGN_PROC GSR6
ATTEMPT_IMMED_ASSIGN_PROC
Description
The ATTEMPT_IMMED_ASSIGN_PROC statistic tracks the number of attempted
immediate assignment procedures.
Formula
ATTEMPT_IMMED_ASSIGN_PROC = (OK_ACC_PROC_RACH −
INV_EST_CAUSE_ON_RACH)

Optimization.
Basis Cell or BSS.
Type Counter.
Raw OK_ACC_PROC_RACH.
Statistics INV_EST_CAUSE_ON_RACH.

16–6 68P02901W56-L 14 Feb 2003
GSR6 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
(TOTAL CALLS + ASSIGNMENT_REDIRECTION )
CALL_SETUP_SUCCESS_RATE= * 100%
(OK_ACC_PROC[CM_SERV_REQ_CALL] +
OK_ACC_PROC[CM_REESTABLISH] +
OK_ACC_PROC[PAGE_RESPONSE] +
OK_PROC[CM_SERV_REQ_SMS] +
OK_ACC_PROC[CM_SERV_REQ_EMERG] +
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL] +
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS] −
SMS_INIT_ON_SDCCH−MT_LCS_ON_SDCCH)

Fault finding.
Service accessibility.
Basis Cell.
Type Percentage.
Raw ASSIGNMENT_REDIRECTION.
Statistics MT_LCS_ON_SDCCH
OK_ACC_PROC[CM_REESTABLISH].
OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_EMERG].
OK_ACC_PROC[CM_SERV_REQ_SMS].
OK_ACC_PROC[LOC_FLW_ON_REQ_NORM].
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS].
OK_ACC_PROC[PAGE_RESPONSE].
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.

14 Feb 2003 68P02901W56-L 16–7
CELL_TCH_ALLOCATIONS GSR6
CELL_TCH_ALLOCATIONS
Description
The CELL_TCH_ALLOCATIONS statistic tracks number of successful allocations of a
TCH within a cell for both call originations and hand ins.
Formula
CELL_TCH_ALLOCATIONS = SUM(ALLOC_TCH)
Basis Cell.
Type Counter.
Raw ALLOC_TCH.
Statistics

16–8 68P02901W56-L 14 Feb 2003
GSR6 CELL_TCH_ASSIGNMENTS
CELL_TCH_ASSIGNMENTS
Description
The CELL_TCH_ASSIGNMENTS statistic is the sum of the total number of calls, the
total number of successful incoming inter-BSS call handovers, and the total number of
incoming intra-BSS call handovers.
Formula
TOTAL_CALLS +
CELL_TCH_ASSIGNMENTS =
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]
Basis Cell.
Type Counter.
Raw TOTAL_CALLS.
Statistics IN_INTER_BSS_HO.
[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO.
[IN_INTRA_BSS_HO_SUC].

14 Feb 2003 68P02901W56-L 16–9
HANDOVER_FAILURE_RATE GSR6
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
(INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] –
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])
HANDOVER_FAILURE_RATE = * 100%
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] +
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT])

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.
Raw INTRA_CELL_HO[INTRA_CELL_HO_ ATMPT].

Statistics 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–10 68P02901W56-L 14 Feb 2003
GSR6 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
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] +
INTRA_CELL_HO[INTRA_CELL_HO_SUC] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])
HANDOVER_SUCCESS_RATE = * 100%
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] +
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT])
NOTE
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.

Optimization.
Fault finding.
Network planning.
Basis Cell.
Type Percentage.

Statistics INTRA_CELL_HO[INTRA_CELL_HO_SUC] .
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ ATMPT].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ ATMPT].
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] .

14 Feb 2003 68P02901W56-L 16–11
MEAN_ARRIVAL_TIME_BETWEEN_CALLS GSR6
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
SUM (INTERVAL)
MEAN_ARRIVAL_TIME_ * 3600
= (CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL] +
BETWEEN_CALLS
CHAN_REQ_CAUSE_ATMPT[EMERGENCY_CALL])

Fault finding.
Optimization.
Basis Cell.
Type Duration (in seconds).
Raw INTERVAL
Statistics CHAN_REQ_CAUSE_ATMPT[ORIGINATING_CALL].
CHAN_REQ_HO_CAUSE_ATMPT[EMERGENCY_CALL].

16–12 68P02901W56-L 14 Feb 2003
GSR6 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
SUM (INTERVAL)
* 3600
MEAN_INTER_ARRIVAL_TIME =
OK_ACC_PROC[CM_SERV_REQ_SMS] +
OK_ACC_PROC[CM_SERV_REQ_SUPP]) +
OK_ACC_PROC[CM_SERV_REQ_EMERG])

Optimization.
Basis BSS.
Raw INTERVAL
Statistics OK_ACC_PROC[CM_SERV_REQ_CALL].
OK_ACC_PROC[CM_SERV_REQ_SUPP].

14 Feb 2003 68P02901W56-L 16–13
MEAN_TCH_BUSY_TIME GSR6
MEAN_TCH_BUSY_TIME
Description
The MEAN_TCH_BUSY_TIME statistic tracks the arithmetic mean of the busy time for
traffic channels in a cell.
Formula
(BUSY_TCH_MEAN)
MEAN_TCH_BUSY_TIME = * INTERVAL * 3600
(AVAILABLE_TCH_MEAN)
Usage Optimization.
Network planning.
Basis Cell.
Raw AVAILABLE_TCH.
Statistics BUSY_TCH.

16–14 68P02901W56-L 14 Feb 2003
GSR6 MTL_UTILISATION_RX
MTL_UTILISATION_RX
Description
The MTL_UTILISATION_RX statistic provides a measure of MTL utilisation for the MSC
to BSS direction.
Formula
((MTP_MSU_RX * 6) + MTP_SIF_SIO_RX) + (SIB_RX * 7)
MTL_UTILISATION_RX = * 100
(MTP_LINK_INS * 8)
NOTE: As an explanation as to how the formula was derived, refer to the following which
shows no number simplification:
((MTP_MSU_RX * 6bytes/msu) + MTP_SIF_SIO_RX) + (SIB_RX * 7bytes/sib)
MTL_UTILISATION_RX = * 100
(MTP_LINK_INS * 1sec/1000msec) * (64000bits per sec/8 bits)
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_RX.
Statistics MTP_SIF_SIO_RX.
SIB_RX.
MTP_LINK_INS.

14 Feb 2003 68P02901W56-L 16–15
MTL_UTILISATION_TX GSR6
MTL_UTILISATION_TX
Description
The MTL_UTILISATION_TX statistic provides a measure of MTL utilisation for the BSS
to MSC direction.
Formula
((MTP_MSU_TX * 6) + MTP_SIF_SIO_TX) + (SIB_TX * 7)
MTL_UTILISATION_TX = * 100
(MTP_LINK_INS * 8)
NOTE: As an explanation as to how the formula was derived, refer to the following which
shows no number simplification:
((MTP_MSU_TX * 6bytes/msu) + MTP_SIF_SIO_TX) + (SIB_TX * 7bytes/sib)
MTL_UTILISATION_TX = * 100
(MTP_LINK_INS * 1sec/1000msec) * (64000bits per sec/8 bits)
Usage Optimization.
Network planning.
Basis MTL.
Type Percentage.
Raw MTP_MSU_TX.
Statistics MTP_SIF_SIO_TX.
SIB_TX.
MTP_LINK_INS.

16–16 68P02901W56-L 14 Feb 2003
GSR6 RF_LOSS_RATE
RF_LOSS_RATE
Description
The RF_LOSS_RATE statistic compares the total number of RF losses (while using both
SDCCH and TCH) with the number of calls set-up in the cell plus the number of calls
handed in to the cell. It indicates the cell/system ability to preserve calls.
Formula
[RF_LOSSES_SD +
( RF_LOSSES_TCH [1] + .... + RF_LOSSES_TCH [nTCH] )]
RF_LOSS_RATE = * 100%
OK_ACC_PROC[CM_SERV_REQ_CALL +
OK_ACC_PROC[CM_SERV_REQ_SMS] + (IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]
OK_ACC_PROC[CM_SERV_REQ_SUPP] + + +
OK_ACC_PROC[CM_SERV_REQ_EMERG] IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])
+ OK_ACC_PROC[CM_REESTABLISH] +
OK_ACC_PROC[LOCATION_UPDATE] +
OK_ACC_PROC[IMSI_DETACH]
+ OK_ACC_PROC[PAGE_RESPONSE]
NOTE
Handovers may relate to SDCCHs (as opposed to TCHs). In this case, the
accuracy of the statistic is affected. For the most part this effect is expected
to be negligible. nTCH = Number of TCHs in cell.

Fault finding and optimization.
Basis Cell.
Type Percentage.
Raw IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
Statistics IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
OK_ACC_PROC: (The value used in this formula is the sum of bins
0 to 7 of this counter array statistic.)
RF_LOSSES_TCH.
RF_LOSSES_SD.

14 Feb 2003 68P02901W56-L 16–17
SDCCH_BLOCKING_RATE GSR6
SDCCH_BLOCKING_RATE
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate
an SDCCH that were blocked due to no available SDCCH resources. This statistic
includes incoming SDCCH handover attempts.
Formula
(ALLOC_SDCCH_FAIL)
SDCCH_BLOCKING_RATE = * 100%
(ALLOC_SDCCH + ALLOC_SDCCH_FAIL)
Usage Service Accessibility.

Quality of Service monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw ALLOC_SDCCH.
Statistics ALLOC_SDCCH_FAIL.

16–18 68P02901W56-L 14 Feb 2003
GSR6 SDCCH_MEAN_ARRIVAL_RATE
SDCCH_MEAN_ARRIVAL_RATE
Description
The SDCCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate for the
SDCCHs in the cell measured in calls per interval.
Formula
OK_ACC_PROC[CM_SERV_REQ_CALL+OK_ACC_PROC[CM_SERV_REQ_SMS]
+OK_ACC_PROC[CM_SERV_REQ_SUPP]+OK_ACC_PROC[CM_SERV_REQ_EMERG]
+OK_ACC_PRO[CM_REESTABLISH] + OK_ACC_PROC[LOCATION_UPDATE]
+ OK_ACC_PROC[IMSI_DETACH] + OK_ACC_PROC[PAGE_RESPONSE]
SDCCH_MEAN_ARRIVAL_TIME =
SUM (INTERVAL)
Basis Cell.
Type Counter (calls per interval).
Raw INTERVAL ( statistics collection interval,

Statistics measured in hours).
OK_ACC_PROC. (The value used in this
formula is the sum of the bins 0 to 7 of this
counter array statistic).

14 Feb 2003 68P02901W56-L 16–19
SDCCH_MEAN_HOLDING_TIME GSR6
SDCCH_MEAN_HOLDING_TIME
Description
The SDCCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls on
SDCCH channels in seconds.
Formula
(BUSY_SDCCH_MEAN * INTERVAL_SUM * 3600)
SDCCH_MEAN_HOLDING_TIME =
ALLOC_SDCCH

Optimization.
Basis Cell.
Type Total Time (in seconds).
Raw ALLOC_SDCCH.
Statistics BUSY_SDCCH.
INTERVAL_SUM (total statistics collection
interval, measured in hours).

16–20 68P02901W56-L 14 Feb 2003
GSR6 SDCCH_RF_LOSS_RATE
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. T his statistic is intended to give an indication of how good the cell/system is at
preserving calls.
Formula
RF_LOSSES_SD
* 100
SDCCH_RF_LOSS_RATE =
(ALLOC_SDCCH CHAN_REQ_MS_FAIL)

Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_SDCCH.
Statistics CHAN_REQ_MS_FAIL.
RF_LOSSES_SD.

14 Feb 2003 68P02901W56-L 16–21
SDCCH_TRAFFIC_CARRIED GSR6
SDCCH_TRAFFIC_CARRIED
Description
The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHs
measured in Erlangs.
Formula
SDCCH_TRAFFIC_CARRIED = BUSY_SDCCH_MEAN
For an individual cell over m statistics intervals:
m
SDCCH_TRAFFIC_CARRIED = S BUSY_SDCCH_MEAN [k]
k= 1
For n cells over an individual statistics interval:
n
k= 1
For n cells over m statistics intervals:
n m
S BUSY_SDCCH_MEAN
SDCCH_TRAFFIC_CARRIED =
Sk= 1
k= 1 [k]
NOTE
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic
channels during a collection interval.
Where BUSY_SDCCH_MEAN [k] is BUSY_SDCCH_MEAN for statistical

interval k.
Usage RF Loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.

16–22 68P02901W56-L 14 Feb 2003
GSR6 SUCCESS_IMMED_ASSIGN_PROC
SUCCESS_IMMED_ASSIGN_PROC
Description
The SUCCESS_IMMED_ASSIGN_PROC statistic tracks the number of successful
immediate assignment procedures.
Formula
SUCCESS_IMMED_ASSIGN_PROC = (OK_ACC_PROC_RACH − INV_EST_CAUSE_ON_RACH
− CHAN_REQ_MS_BLK)

Optimization.
Basis Cell or BSS.
Type Counter.
Raw CHAN_REQ_MS_BLK.
Statistics INV_EST_CAUSE_ON_RACH.
OK_ACC_PROC_RACH.

14 Feb 2003 68P02901W56-L 16–23
SUCCESS_INTERNAL_HO GSR6
SUCCESS_INTERNAL_HO
Description
The SUCCESS_INTERNAL_HO statistic tracks the number of successful internal
handovers.
Formula
SUCCESS_INTERNAL_HO = (INTRA_CELL_HO[INTRA_CELL_HO_SUC] +

Optimization.
Quality of service.
Basis Cell.
Type Counter.
Raw INTRA_CELL_HO[INTRA_CELL_HO_SUC] .
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] .

16–24 68P02901W56-L 14 Feb 2003
GSR6 TCH_BLOCKING_RATE
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
(ALLOC_TCH_FAIL − TCH_Q_REMOVED)
TCH_BLOCKING_RATE = * 100%
(ALLOC_TCH + ALLOC_TCH_FAIL − TCH_Q_REMOVED)

Network planning.
Fault finding.
Basis Cell.
Type Percentage.
Raw ALLOC_TCH.
Statistics ALLOC_TCH_FAIL.
TCH_Q_REMOVED.

14 Feb 2003 68P02901W56-L 16–25
TCH_MEAN_ARRIVAL_RATE GSR6
TCH_MEAN_ARRIVAL_RATE
Description
The TCH_MEAN_ARRIVAL_RATE statistic tracks the call arrival (set-up) rate in calls
per interval for the cell in question.
Formula
(ALLOC_TCH + ALLOC_TCH_FAIL − TCH_Q_REMOVED)
TCH_MEAN_ARRIVAL_RATE =
SUM(INTERVAL)
NOTE
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).
Raw ALLOC_TCH.
Statistics ALLOC_TCH_FAIL.
TCH_Q_REMOVED.

16–26 68P02901W56-L 14 Feb 2003
GSR6 TCH_MEAN_HOLDING_TIME
TCH_MEAN_HOLDING_TIME
Description
The TCH_MEAN_HOLDING_TIME statistic tracks the average duration of calls on traffic
channels (TCH) in seconds.
Formula
(BUSY_TCH_MEAN * INTERVAL_SUM * 3600)
TCH_MEAN_HOLDING_TIME =
ALLOC_TCH
NOTE
The numerator and denominator may peg on different intervals (where a call
extends across multiple collection boundaries). This affects the accuracy of
the statistic for the period. Therefore, this statistic should be used as a trend
rather than focusing on specific values.
Basis Cell.
Type Total Time in seconds.
Raw ALLOC_TCH.
Statistics BUSY_TCH_MEAN.

14 Feb 2003 68P02901W56-L 16–27
TCH_RF_LOSS_RATE GSR6
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
RF_LOSSES_TCH
TCH_RF_LOSS_RATE = (TOTAL_CALLS + IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC] * 100%
IN_INTER_BSS[IN_INTER_BSS_HO_SUC])
BSS Level
RF_LOSSES_TCH
TCH_RF_LOSS_RATE = * 100%
(TOTAL_CALLS + ASSIGNMENT_REDIRECTION +
IN_INTER_BSS[IN_INTER_BSS_HO_SUC])
Network Level RF_LOSSES_TCH * 100%

TCH_RF_LOSS_RATE =
TOTAL_CALLS + ASSIGNMENT_REDIRECTION

Fault finding.
Basis Cell.
Type Percentage.
Statistics IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]
IN_INTER_BSS[IN_INTER_BSS_HO_SUC].
RF_LOSSES_TCH.
TOTAL_CALLS.

16–28 68P02901W56-L 14 Feb 2003
GSR6 TCH_TRAFFIC_CARRIED
TCH_TRAFFIC_CARRIED
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs
Formula
For an individual cell for an individual statistics interval:
TCH_TRAFFIC_CARRIED = BUSY_TCH_MEAN
m
TCH_TRAFFIC_CARRIED = S BUSY_TCH_MEAN [k]
k= 1

n
k= 1
n m
S BUSY_TCH_MEAN [k]
TCH_TRAFFIC_CARRIED =
Sk= 1
k= 1
NOTE
The BUSY_TCH_MEAN statistic reports the mean number of busy traffic
Where BUSY_TCH_MEAN [k] is BUSY_TCH_MEAN for statistical interval k.

14 Feb 2003 68P02901W56-L 16–29
TCH_TRAFFIC_CARRIED GSR6
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw BUSY_TCH (BUSY_TCH_MEAN).

Statistics

16–30 68P02901W56-L 14 Feb 2003
GSR6 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
TOTAL_CALLS_KEY = ( TOTAL_CALLS )

Fault finding.
Basis Cell.
Type Counter.
Raw TOTAL_CALLS.
Statistics

14 Feb 2003 68P02901W56-L 16–31
UNSUCCESS_INTERNAL_HO_NOREEST GSR6
UNSUCCESS_INTERNAL_HO_NOREEST
Description
The UNSUCCESS_INTERNAL_HO_NOREEST statistic tracks the number of
unsuccessful internal handovers that result in dropping the call.
Formula
UNSUCCESS_INTERNAL_HO_NOREEST = INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS]

Quality of service.
Fault finding.
Basis Cell or BSS.
Type Counter
Raw INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] .
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] .

16–32 68P02901W56-L 14 Feb 2003
GSR6 UNSUCCESS_INTERNAL_HO_REEST
UNSUCCESS_INTERNAL_HO_REEST
Description
The UNSUCCESS_INTERNAL_HO_REEST statistic tracks the number of unsuccessful
internal handovers with successful recovery to the originating cell or channel.
Formula
SUCCESS_INTERNAL_HO_REEST = (INTRA_CELL_HO[INTRA_CELL_HO_RETURN] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN])

Fault finding.
Quality of service.
Basis Cell or BSS.
Type Counter.
Raw INTRA_CELL_HO[INTRA_CELL_HO_RETURN] .
Statistics OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] .

14 Feb 2003 68P02901W56-L 16–33
UNSUCCESS_INTERNAL_HO_REEST GSR6

16–34 68P02901W56-L 14 Feb 2003
Chapter 17
Network health reports

14 Feb 2003 68P02901W56-L 17–1
GSR6

17–2 68P02901W56-L 14 Feb 2003
GSR6 Network health statistics
Network health statistics
Description
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.
The network health statistics are organized as a suite of reports, including:
S GPRS performance.
S Handover performance.
S Health check.
S Paging performance.
S Radio performance.
S SDCCH congestion.
S TCH congestion.

14 Feb 2003 68P02901W56-L 17–3
Network health statistics GSR6
GPRS performance
The following statistics provide key performance metrics for the GPRS system:
S AIR_INTERFACE_BW_CS1
S CELL_UPDATE
S CS1_USAGE_DL
S CS1_USAGE_UL
S CS2_USAGE_DL
S CS2_USAGE_UL
S CS3_USAGE_DL
S CS3_USAGE_UL
S CS4_USAGE_DL
S CS4_USAGE_UL
S DL_AIR_INTERFACE_BW_CS1
S DOWNLINK_TRAFFIC_VOLUME
S GBL_AVAILABILITY
S GPRS_BW_USAGE_DL
S GPRS_BW_USAGE_UL
S GPRS_DL_ACT_TS
S GPRS_DL_BANDWIDTH_EFFICIENCY
S GPRS_UL_ACT_TS
S GPRS_UL_BANDWIDTH_EFFICIENCY
S PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK
S UL_AIR_INTERFACE_BW_CS1
S UPLINK_PDTCH_BLOCKING_RATE
S UPLINK_TRAFFIC_VOLUME

17–4 68P02901W56-L 14 Feb 2003
GSR6 Network health statistics
Handover performance
The following statistics provide general handover information:
S HO_PER_CALL.
S INCOMING_HO_VOLUME.
S INTERNAL_LOST.
S INTERNAL_RECOVERED.
S INTERNAL_SUCCESS.
S INTRA_CELL_HO_FAIL_LOST_MS.
S INTRA_CELL_HO_FAIL_RECOVERED.
S INTRA_CELL_HO_SUCCESS_RATE.
S MEAN_TIME_BETWEEN_HOs.
S OUT_INTER_BSS_HO_FAIL_LOST_MS.
S OUT_INTER_BSS_HO_FAIL_RECOVERED.
S OUT_INTER_BSS_HO_SUCCESS_RATE.
S OUT_INTER_CELL_HO_FAIL_LOST_MS.
S OUT_INTER_CELL_HO_FAIL_RECOVERED.
S OUT_INTER_CELL_HO_SUCCESS_RATE.
S OUTGOING_HO_VOLUME .
Health check
The following statistics provide health check information:
S CALL_SETUP_SUCCESS_RATE.
S CALL_SUCCESS_RATE.
S CALL_VOLUME.
S DROP_CALL_RATE.
S RANKING_FORMULA.
S TCH_TRAFFIC_CARRIED
Paging performance
The following statistics provide paging performance information:
S AIR_INTERFACE_PAGING.
S MSC_PAGING.
S PAGING_COMPRESSION_RATE.
S PAGING_OVERFLOW_RATE.
S PAGING_RESPONSE.
S PAGING_SUCCESS_RATE.

14 Feb 2003 68P02901W56-L 17–5
Network health statistics GSR6
Radio performance
The following statistics provide radio performance information:
S ASSIGNMENT_SUCCESS_RATE.
S OUT_INTER_CELL_HO_FAIL_LOST_MS.
S OUT_INTER_CELL_HO_FAIL_RECOVERED.
S OUT_INTER_CELL_HO_SUCCESS_RATE.
S RF_ASSIGN_FAIL_RATE_LOST_MS.
S RF_ASSIGN_FAIL_RATE_RECOVERED.
S TCH_RF_LOSS_RATE.
SDCCH congestion
The following statistics provide SDCCH congestion information:
S SDCCH_ACCESSES.
S SDCCH_CONGESTION_TIME.
S SDCCH_TRAFFIC_CARRIED.
TCH congestion
The following statistics provide TCH congestion information:
S MAX_TCH_BUSY.
S TCH_ACCESSES
S TCH_CONGESTION_TIME .
S TCH_TRAFFIC_CARRIED.

17–6 68P02901W56-L 14 Feb 2003
GSR6 AIR_INTERFACE_BW_CS1
AIR_INTERFACE_BW_CS1
Description
The AIR_INTERFACE_BW_CS1 statistic provides the maximum bandwidth available in
kilobits per second in a cell for GPRS coding scheme 1.
Formula
AIR_INTERFACE_BW_CS1 = AVAILABLE_PDTCH * 9.05

Basis Cell.
Type Counter.
Raw AVAILABLE_PDTCH.
Statistics

14 Feb 2003 68P02901W56-L 17–7
AIR_INTERFACE_BW_CS2 GSR6
Description
Formula

Basis Cell.
Type Counter.
Statistics

17–8 68P02901W56-L 14 Feb 2003
GSR6 AIR_INTERFACE_BW_CS3
Description
Formula

Basis Cell.
Type Counter.
Statistics

14 Feb 2003 68P02901W56-L 17–9
AIR_INTERFACE_BW_CS4 GSR6
Description
Formula

Basis Cell.
Type Counter.
Statistics

17–10 68P02901W56-L 14 Feb 2003
GSR6 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
AIR_INTERFACE_PAGING = ACCESS_PER_PCH

Basis Cell.
Type Counter.
Raw ACCESS_PER_PCH.
Statistics

14 Feb 2003 68P02901W56-L 17–11
ASSIGNMENT_SUCCESS_RATE GSR6
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
MA_COMPLETE_TO_MSC
ASSIGNMENT_SUCCESS_RATE= * 100%
MA_REQ_FROM_MSC

Quality of service.
Basis Cell.
Type Percentage.
Raw MA_COMPLETE_TO_MSC.
Statistics MA_REQ_FROM_MSC

17–12 68P02901W56-L 14 Feb 2003
GSR6 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
(TOTAL CALLS + ASSIGNMENT_REDIRECTION )
CALL_SETUP_SUCCESS_RATE= * 100%
OK_ACC_PROC[CM_REESTABLISH] +
OK_ACC_PROC[PAGE_RESPONSE] +
OK_PROC[CM_SERV_REQ_SMS] +
OK_ACC_PROC[CM_SERV_REQ_EMERG] +
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL] +
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS] −
SMS_INIT_ON_SDCCH−MT_LCS_ON_SDCCH)

Fault finding.
Basis Cell.
Type Percentage.
Statistics MT_LCS_ON_SDCCH
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL]
OK_ACC_PROC[LOC_FLW_ON_REQ_SMS]
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.

14 Feb 2003 68P02901W56-L 17–13
CALL_SUCCESS_RATE GSR6
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
DROP_CALL_RATE
CALL_SUCCESS_RATE = CALL_SETUP_SUCCESS_RATE * 1–
100

Fault finding.
Basis Cell.
Type Percentage.
Statistics IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] .
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED] .
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.

17–14 68P02901W56-L 14 Feb 2003
GSR6 CALL_VOLUME
CALL_VOLUME
Description
The CALL_VOLUME statistic tracks the number of call setups which result in a
successful TCH access.
Formula
CALL_VOLUME = TOTAL_CALLS + ASSIGNMENT_REDIRECTION

Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 17–15
CELL_UPDATE GSR6
CELL_UPDATE
Description
The CELL_UPDATE statistic measures the number of cell reselections relating to a
particular cell.
Formula
CELL_UPDATE = CELL_FLUSH_REQS

Basis Cell.
Type Counter.
Raw CELL_FLUSH_REQS.
Statistics

17–16 68P02901W56-L 14 Feb 2003
GSR6 CS1_USAGE_DL
CS1_USAGE_DL
Description
The CS1_USAGE_DL statistic provides the percentage of Radio Link Control blocks
transmitted by the PCU (downlink) using GPRS coding scheme 1.
Formula
(AIR_DL_DATA_BLKS[QOS1_CS1] + AIR_DL_DATA_BLKS[QOS2_CS1] +
AIR_DL_DATA_BLKS[QOS3_CS1])
CS1_USAGE_DL = * 100%
(AIR_DL_DATA_BLKS)

Basis Cell.
Type Percentage.
Raw AIR_DL_DATA_BLKS[QOS1_CS1].
Statistics AIR_DL_DATA_BLKS[QOS2_CS1].
AIR_DL_DATA_BLKS[QOS3_CS1].
AIR_DL_DATA_BLKS all bins.

14 Feb 2003 68P02901W56-L 17–17
CS1_USAGE_UL GSR6
CS1_USAGE_UL
Description
The CS1_USAGE_UL statistic provides the percentage of Radio Link Control blocks
received by the PCU (uplink) using GPRS coding scheme 1.
Formula
(AIR_UL_DATA_BLKS[QOS1_CS1] + AIR_UL_DATA_BLKS[QOS2_CS1] +
AIR_UL_DATA_BLKS[QOS3_CS1])
CS1_USAGE_UL = * 100%
(AIR_UL_DATA_BLKS)

Basis Cell.
Type Percentage.
Raw AIR_UL_DATA_BLKS[QOS1_CS1].
Statistics AIR_UL_DATA_BLKS[QOS2_CS1].
AIR_UL_DATA_BLKS[QOS3_CS1].
AIR_UL_DATA_BLKS all bins.

17–18 68P02901W56-L 14 Feb 2003
GSR6 CS2_USAGE_DL
CS2_USAGE_DL
Description
Formula
(AIR_DL_DATA_BLKS)

Basis Cell.
Type Percentage.

14 Feb 2003 68P02901W56-L 17–19
CS2_USAGE_UL GSR6
CS2_USAGE_UL
Description
Formula
(AIR_UL_DATA_BLKS)

Basis Cell.
Type Percentage.

17–20 68P02901W56-L 14 Feb 2003
GSR6 CS3_USAGE_DL
CS3_USAGE_DL
Description
Formula
(AIR_DL_DATA_BLKS)

Basis Cell.
Type Percentage.

14 Feb 2003 68P02901W56-L 17–21
CS3_USAGE_UL GSR6
CS3_USAGE_UL
Description
Formula
(AIR_UL_DATA_BLKS)

Basis Cell.
Type Percentage.

17–22 68P02901W56-L 14 Feb 2003
GSR6 CS4_USAGE_DL
CS4_USAGE_DL
Description
Formula
(AIR_DL_DATA_BLKS)

Basis Cell.
Type Percentage.

14 Feb 2003 68P02901W56-L 17–23
CS4_USAGE_UL GSR6
CS4_USAGE_UL
Description
Formula
(AIR_UL_DATA_BLKS)

Basis Cell.
Type Percentage.

17–24 68P02901W56-L 14 Feb 2003
GSR6 DL_AIR_INTERFACE_BW_CS1
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 the formula is:
((AVAILABLE_PDTCH * 90000) * 9.05)

DL_AIR_INTERFACE_BW_CS1 =
(50 * 3600) * INTERVAL
For GSR5.1 the formula is:
(TOTAL_AIR_DL_AVAILABLE_BW * 9.05)
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.
Statistics INTERVAL is either 0.5 for a 30 minute collection
period or 1 for a 60 minute collection period.
TOTAL_AIR_DL_AVAILABLE_BW (GSR5.1).

14 Feb 2003 68P02901W56-L 17–25
DL_AIR_INTERFACE_BW_CS2 GSR6
Description
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.

17–26 68P02901W56-L 14 Feb 2003
GSR6 DL_AIR_INTERFACE_BW_CS3
Description
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.
TOTAL_AIR_DL_AVAILABLE_BW (GSR5.1)

14 Feb 2003 68P02901W56-L 17–27
DL_AIR_INTERFACE_BW_CS4 GSR6
Description
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.

17–28 68P02901W56-L 14 Feb 2003
GSR6 DOWNLINK_TRAFFIC_VOLUME
DOWNLINK_TRAFFIC_VOLUME
Description
The DOWNLINK_TRAFFIC_VOLUME statistic provides a measure of the volume of
downlink Radio Link Control traffic including retransmitted blocks.
Formula
DOWNLINK_TRAFFIC_VOLUME= AIR_DL_DATA_BLKS[QOS3_CS1]) * 22) + * 100%
AIR_DL_DATA_BLKS[QOS3_CS2]) * 32) +
AIR_DL_DATA_BLKS[QOS3_CS3]) * 38) +
AIR_DL_DATA_BLKS[QOS3_CS4]) * 52)
(1024 * 3600 * INTERVAL)

Basis Cell.
Type Percentage.
INTERVAL is either 0.5 for a 30 minute collection

14 Feb 2003 68P02901W56-L 17–29
DROP_CALL_RATE GSR6
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
Cell Level (RF_LOSSES_TCH +
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] +
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED])
DROP_CALL_RATE = * 100
(TOTAL_CALLS +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])
BSS Level (RF_LOSSES_TCH +

INTRA_CELL[INTRA_CELL_HO_LOSTMS] +
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC])
Network Level (RF_LOSSES_TCH +

INTRA_CELL[INTRA_CELL_HO_LOSTMS] +
(TOTAL_CALLS + ASSIGNMENT_REDIRECTION)

Basis Cell, BSS, or network.
Type Percentage.
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] .
OUT_INTER_BSS_HO[OUT_INTRA_BSS_HO_CLEARED] .
RF_LOSSES_TCH.
TOTAL_CALLS.

17–30 68P02901W56-L 14 Feb 2003
GSR6 GBL_AVAILABILITY
GBL_AVAILABILITY
Description
The GBL_AVAILABILITY statistic measures the availability for a particular Gb link
(GBL).
Formula
GBL_LINK_INS
GBL_AVAILABILITY =
(3600000 * INTERVAL)

Basis GBL.
Type Counter.
Raw GBL_LINK_INS.

14 Feb 2003 68P02901W56-L 17–31
GPRS_BW_USAGE_DL GSR6
GPRS_BW_USAGE_DL
Description
The GPRS_BW_USAGE_DL statistic measures the bandwidth usage in the downlink
direction and provides an indication of the adequacy of the deployed cell capacity.
Formula
((AIR_DL_DATA_BLKS * 100) * 100)

GPRS_BW_USAGE_DL =
(AVAILABLE_PDTCH_MEAN * 50 * 3600* INTERVAL)

Basis Cell.
Type Percentage.
Raw AIR_DL_DATA_BLKS.
Statistics AVAILABLE_PDTCH.

17–32 68P02901W56-L 14 Feb 2003
GSR6 GPRS_BW_USAGE_UL
GPRS_BW_USAGE_UL
Description
The GPRS_BW_USAGE_UL statistic measures the bandwidth usage in the uplink
direction and provides an indication of the adequacy of the deployed cell capacity.
Formula
((AIR_UL_DATA_BLKS * 100) * 100)

GPRS_BW_USAGE_UL =
(AVAILABLE_PDTCH_MEAN * 50 * 3600* INTERVAL)

Basis Cell.
Type Percentage.
Raw AIR_UL_DATA_BLKS.

14 Feb 2003 68P02901W56-L 17–33
GPRS_DL_ACT_TS GSR6
GPRS_DL_ACT_TS
Description
The GPRS_DL_ACT_TS statistic measures the utilization of busy downlink PDTCHs in a
cell.
Formula
GPRS_DL_ACT_TS = DL_BUSY_PDTCH_MEAN

Basis Cell.
Type Counter.
Raw DL_BUSY_PDTCH.
Statistics

17–34 68P02901W56-L 14 Feb 2003
GSR6 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
GPRS_UL_ACT_TS = UL_BUSY_PDTCH_MEAN

Basis Cell.
Type Counter.
Raw UL_BUSY_PDTCH.
Statistics

14 Feb 2003 68P02901W56-L 17–35
GPRS_DL_BANDWIDTH_EFFICIENCY GSR6
GPRS_DL_BANDWIDTH_EFFICIENCY
Description
The GPRS_DL_BANDWIDTH_EFFICIENCY statistic measures the utilization of the
GPRS bandwidth allocated in the downlink direction in the cells controlled by the PCU.
Formula

GPRS_DL_BANDWIDTH_EFFICIENCY =
(AVAILABLE_PDTCH * 90000)

GPRS_DL_BANDWIDTH_EFFICIENCY =
(TOTAL_AIR_DL_AVAILABLE_BW)

Basis Cell.
Type Percentage.
Raw AIR_DL_DATA_BLKS.

17–36 68P02901W56-L 14 Feb 2003
GSR6 GPRS_UL_BANDWIDTH_EFFICIENCY
GPRS_UL_BANDWIDTH_EFFICIENCY
Description
The GPRS_UL_BANDWIDTH_EFFICIENCY statistic measures the utilization of the
GPRS bandwidth allocated in the uplink direction in the cells controlled by the PCU.
Formula

GPRS_UL_BANDWIDTH_EFFICIENCY =
(AVAILABLE_PDTCH * 90000)

GPRS_UL_BANDWIDTH_EFFICIENCY =
(TOTAL_AIR_UL_AVAILABLE_BW)

Basis Cell.
Type Percentage.
Raw AIR_UL_DATA_BLKS.
TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1)

14 Feb 2003 68P02901W56-L 17–37
HO_PER_CALL GSR6
HO_PER_CALL
Description
The HO_PER_CALL statistic tracks the average number of successful handovers per
call.
Formula
Cell Level
(OUT_INTER_BSS_HO_SUC +
OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC) * 100%
HO_PER_CALL =
TOTAL_CALLS
BSS Level
OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC)
HO_PER_CALL = * 100%
Network Level
OUT_INTRA_BSS_HO_SUC + INTRA_CELL_HO_SUC)
HO_PER_CALL = * 100%

Fault finding.
Basis Cell.
Type Percentage.
Raw ASSIGNMENT_REDIRECTION
TOTAL_CALLS.

17–38 68P02901W56-L 14 Feb 2003
GSR6 INCOMING_HO_VOLUME
INCOMING_HO_VOLUME
Description
The INCOMING_HO_VOLUME statistic provides the number of successful incoming
handovers.
Formulas
Cell Level
INCOMING_HO_VOLUME = (IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
BSS Level
INCOMING_HO_VOLUME = IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
Statistics IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].

14 Feb 2003 68P02901W56-L 17–39
INTERNAL_LOST GSR6
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
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] +
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS])
INTERNAL_LOST = * 100%
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] +
INTRA_CELL_HO[INTRA_CELL_HO_ATMPT])

Fault finding.
Basis Cell.
Type Percentage.


17–40 68P02901W56-L 14 Feb 2003
GSR6 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
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] +
INTRA_CELL_HO[INTRA_CELL_HO_RETURN])
INTERNAL_RECOVERED = * 100%

Fault finding.
Basis Cell.
Type Percentage.

Statistics INTRA_CELL_HO[INTRA_CELL_HO_RETURN] .
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] .

14 Feb 2003 68P02901W56-L 17–41
INTERNAL_SUCCESS GSR6
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
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] +
INTRA_CELL_HO[INTRA_CELL_HO_SUC])
INTERNAL_SUCCESS =
* 100%

Fault finding.
Basis Cell.
Type Percentage.


17–42 68P02901W56-L 14 Feb 2003
GSR6 INTRA_CELL_HO_FAIL_LOST_MS
INTRA_CELL_HO_FAIL_LOST_MS
Description
The INTRA_CELL_HO_FAIL_LOST_MS statistic tracks the percentage of intra-cell
assignment commands that are sent over the air interface which result in the MS failing
to access the target channel and failing to recover to the original channel; that is, the call
drops.
Formula
INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS]
INTRA_CELL_HO_FAIL_ * 100%
LOST_MS = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

Fault finding.
Type Percentage.
Raw INTRA_CELL_HO[INTRA_CELL_HO_ ATMPT]


14 Feb 2003 68P02901W56-L 17–43
INTRA_CELL_HO_FAIL_RECOVERED GSR6
INTRA_CELL_HO_FAIL_RECOVERED
Description
The INTRA_CELL_HO_FAIL_RECOVERED statistic tracks the percentage of intra-cell
assignment commands that are sent over the air interface which result in the MS failing
to access the target channel and subsequently successfully recovering to the original
channel.
Formula
INTRA_CELL_HO[INTRA_CELL_HO_RETURN]
INTRA_CELL_HO_FAIL_ * 100%
RECOVERED = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

Fault finding.
Type Percentage.

Statistics INTRA_CELL_HO[INTRA_CELL_HO_RETURN] .

17–44 68P02901W56-L 14 Feb 2003
GSR6 INTRA_CELL_HO_SUCCESS_RATE
INTRA_CELL_HO_SUCCESS_RATE
Description
The INTRA_CELL_HO_SUCCESS_RATE statistic tracks the percentage of intra-cell
assignment commands that are sent over the air interface which result in the MS
successfully accessing the target channel.
Formula
INTRA_CELL_HO[INTRA_CELL_HO_SUC]
INTRA_CELL_HO_ * 100%
SUCCESS_RATE = INTRA_CELL_HO[INTRA_CELL_HO_ATMPT]

Fault finding.
Type Percentage.


14 Feb 2003 68P02901W56-L 17–45
MAX_TCH_BUSY GSR6
MAX_TCH_BUSY
Description
The MAX_TCH_BUSY statistic tracks the maximum number of simultaneously busy
TCHs.
Formula
MAX_TCH_BUSY = BUSY_TCH[MAX]
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Counter.
Raw BUSY_TCH[MAX].
Statistics

17–46 68P02901W56-L 14 Feb 2003
GSR6 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
TCH_USAGE
MEAN_TIME_BE
TWEEN_HOs=
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]+
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC]) * 1000

Fault finding.
Basis Cell.
Type Time interval (in seconds).
Raw OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] .
TCH_USAGE.

14 Feb 2003 68P02901W56-L 17–47
MSC_PAGING GSR6
MSC_PAGING
Description
The MSC_PAGING statistic tracks the total number of BSSMAP paging messages
received over the A-interface from the MSC.
Formula
MSC_PAGING = PAGE_REQ_FROM_MSC

Basis Cell.
Type Counter.
Statistics

17–48 68P02901W56-L 14 Feb 2003
GSR6 OUT_INTER_BSS_HO_FAIL_LOST_MS
OUT_INTER_BSS_HO_FAIL_LOST_MS
Description
The OUT_INTER_BSS_HO_FAIL_LOST_MS statistic tracks the percentage of
inter-BSS handover commands that are sent over the air interface which result in the MS
failing to access the target channel and failing to recover to the original channel; that is,
the call drops.
Formula
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –
OUT_INTER_BSS_HO_
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])
FAIL_LOST_MS = * 100%
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]

Fault finding.
Basis BSS.
Type Percentage.
Raw OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ ATMPT].

Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] .

14 Feb 2003 68P02901W56-L 17–49
OUT_INTER_BSS_HO_FAIL_RECOVERED GSR6
OUT_INTER_BSS_HO_FAIL_RECOVERED
Description
The OUT_INTER_BSS_HO_FAIL_RECOVERED statistic tracks the percentage of
failing to access the target channel and a subsequently successful recovering to the
original channel.
Formula
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN]
OUT_INTER_BSS_HO_FAIL_
RECOVERED = * 100%
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]

Fault finding.
Basis BSS.
Type Percentage.


17–50 68P02901W56-L 14 Feb 2003
GSR6 OUT_INTER_BSS_HO_SUCCESS_RATE
OUT_INTER_BSS_HO_SUCCESS_RATE
Description
The OUT_INTER_BSS_HO_SUCCESS_RATE statistic tracks the percentage of
successfully accessing the target channel.
Formula
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC]
OUT_INTER_BSS_HO * 100%
_SUCCESS_RATE = OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]

Fault finding.
Basis BSS.
Type Percentage.

Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] .

14 Feb 2003 68P02901W56-L 17–51
OUT_INTER_CELL_HO_FAIL_LOST_MS GSR6
OUT_INTER_CELL_HO_FAIL_LOST_MS
Description
The OUT_INTER_CELL_HO_FAIL_LOST_MS statistic tracks the percentage of
inter-cell handover commands that are sent over the air interface which result in the MS
the call drops. This statistic does not include intra-cell handovers.
Formula
(OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS]
+ OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] –
OUT_INTER_CELL_HO_FAIL_ OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN])
LOST_MS = * 100%
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT])

Fault finding.
Basis Cell.
Type Percentage.


17–52 68P02901W56-L 14 Feb 2003
GSR6 OUT_INTER_CELL_HO_FAIL_RECOVERED
OUT_INTER_CELL_HO_FAIL_RECOVERED
Description
The OUT_INTER_CELL_HO_FAIL_RECOVERED statistic tracks the percentage of
inter-cell handover commands that are sent over the air interface which result in the MS
failing to access the target channel and a subsequently successful recovering to the
original channel. This statistic does not include intra-cell handovers.
Formula
(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] +
OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN])
OUT_INTER_CELL_HO_FAIL_RECOVERED=
* 100%

Fault finding.
Basis Cell.
Type Percentage.

OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] .

14 Feb 2003 68P02901W56-L 17–53
OUT_INTER_CELL_HO_SUCCESS_RATE GSR6
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 in the MS successfully accessing the target
channel. This statistic includes intra-BSS and inter-BSS inter-cell handovers.
Formula
OUT_INTER_CELL_HO_SUCCESS_RATE = * 100%

Fault finding.
Basis Cell.
Type Percentage.

Statistics OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] .

17–54 68P02901W56-L 14 Feb 2003
GSR6 OUTGOING_HO_VOLUME
OUTGOING_HO_VOLUME
Description
The OUTGOING_HO_VOLUME statistic tracks the number of successful outgoing
handovers.
Formula
Cell Level
OUTGOING_HO_VOLUME =
BSS Level
OUTGOING_HO_VOLUME = OUT_INTER_BSS_HO_SUC

Fault finding.
Basis Cell or BSS.
Type Counter.
Raw OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] .

14 Feb 2003 68P02901W56-L 17–55
PAGING_COMPRESSION_RATE GSR6
PAGING_COMPRESSION_RATE
Description
The PAGING_COMPRESSION_RATE statistic provides a measure of page packing on
the air interface.
Formula
ACCESS_PER_PCH
PAGING_COMPRESSION_RATE = * 100%
PAGE_REQ_FROM_MSC

Fault finding.
Basis Cell.
Type Percentage.
Raw ACCESS_PER_PCH
Statistics PAGE_REQ_FROM_MSC.

17–56 68P02901W56-L 14 Feb 2003
GSR6 PAGING_OVERFLOW_RATE
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.
Formula
PCH_PAGE_Q_DISCARD
PAGING_OVERFLOW_RATE = * 100%
PAGE_REQ_FROM_MSC

Fault finding.
Type Percentage.
Statistics PCH_PAGE_Q_DISCARD.

14 Feb 2003 68P02901W56-L 17–57
PAGING_RESPONSE GSR6
PAGING_RESPONSE
Description
The PAGING_RESPONSE statistic tracks the volume of MSs which respond to a page
through a successful SDCCH access.
Formula
PAGING_RESPONSE = OK_ACC_PROC[PAGE_RESPONSE]

Fault finding.
Type Counter.
Raw Statistic OK_ACC_PROC[PAGE_RESPONSE]

17–58 68P02901W56-L 14 Feb 2003
GSR6 PAGING_SUCCESS_RATE
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
SUM (ACC_PROC[PAGE_RESPONSE])
PAGING_SUCCESS_RATE = * 100%
PAGE_REQ_FROM_MSC
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 OK_ACC_PROC[PAGE_RESPONSE]
Statistics PAGE_REQ_FROM_MSC.

14 Feb 2003 68P02901W56-L 17–59
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK GSR6
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK
Description
The PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK statistic provides a ratio of the
GPRS downlink traffic against the uplink traffic.
Formula
AIR_DL_DATA_BLKS * 100
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK =
AIR_DL_DATA_BLKS + AIR_UL_DATA_BLKS

Basis Cell.
Type Percentage.
Raw AIR_DL_DATA_BLKS
Statistics AIR_UL_DATA_BLKS.

17–60 68P02901W56-L 14 Feb 2003
GSR6 RANKING_FORMULA
RANKING_FORMULA
Description
The RANKING_FORMULA statistic provides a measure by which cells can be ranked by
performance. This permits cells requiring optimization to be identified. The value of this
statistic increases as cells have high calling volumes and low call success rates. High
values for this statistic indicate which cells which should be optimized first.
A combination of the CALL_SUCCESS_RATE and CALL_SETUP_SUCCESS_RATE
network health statistics is used to calculate this statistic. The raw statistics used to
calculate these health statistics are included in the raw statistics listing.
Formula
TOTAL_CALLS
RANKING_FORMULA = (100 – CALL_SUCCESS_RATE) *
Usage Optimization.
Basis Cell.
Type Counter.
MT_LCS_ON_SDCCH.
IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC].
OK_ACC_PROC[LOC_FLW_ON_REQ_NORMAL].
OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_CLEARED] .
RF_LOSSES_TCH.
SMS_INIT_ON_SDCCH.
TOTAL_CALLS.

14 Feb 2003 68P02901W56-L 17–61
RF_ASSIGN_FAIL_RATE_LOST_MS GSR6
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
the call drops. This statistic includes intra-cell handover assignment attempts.
Formula
(MA_CMD_TO_MS – MA_COMPLETE_FROM_MS –
RF_ASSIGN_FAIL_RATE_LOST_MS = MA_FAIL_FROM_MS)
* 100
MA_CMD_TO_MS

Fault finding.
Basis Cell.
Type Percentage.
Raw MA_CMD_TO_MS.
Statistics MA_COMPLETE_FROM_MS.
MA_FAIL_FROM_MS.

17–62 68P02901W56-L 14 Feb 2003
GSR6 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 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
MA_FAIL_FROM_MS
RF_ASSIGN_FAIL_RATE_RECOVERED = * 100
MA_CMD_TO_MS

Fault finding.
Basis Cell.
Type Percentage.
Raw MA_CMD_TO_MS.
Statistics MA_FAIL_FROM_MS.

14 Feb 2003 68P02901W56-L 17–63
RF_ASSIGNMENT_SUCCESS_RATE GSR6
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
MA_COMPLETE_FROM_MS
RF_ASSIGNMENT_SUCCESS_RATE = * 100
MA_CMD_TO_MS

Fault finding.
Basis Cell.
Type Percentage.
Raw Statistics MA_CMD_TO_MS.
MA_COMPLETE_FROM_MS.

17–64 68P02901W56-L 14 Feb 2003
GSR6 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
SDCCH_ACCESSES = (ALLOC_SDCCH – CHAN_REQ_MS_FAIL)
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Basis Cell.
Type Counter.
Raw ALLOC_SDCCH.
Statistics CHAN_REQ_MS_FAIL.

14 Feb 2003 68P02901W56-L 17–65
SDCCH_BLOCKING_RATE GSR6
SDCCH_BLOCKING_RATE
Description
The SDCCH_BLOCKING_RATE statistic tracks the percentage of attempts to allocate
an SDCCH that were blocked due to no available SDCCH resources. This statistic
includes incoming SDCCH handover attempts.
Formula
ALLOC_SDCCH_FAIL
SDCCH_BLOCKING_RATE = * 100%
(ALLOC_SDCCH + ALLOC_SDCCH_FAIL)

Quality of Service Monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw ALLOC_SDCCH.
Statistics ALLOC_SDCCH_FAIL.

17–66 68P02901W56-L 14 Feb 2003
GSR6 SDCCH_CONGESTION_TIME
SDCCH_CONGESTION_TIME
Description
The SDCCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all
SDCCHs are busy.
Formula
SDCCH_CONGESTION
SDCCH_CONGESTION_TIME =
1000
Usage RF loss.
Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration (seconds).
Raw SDCCH_CONGESTION.
Statistics

14 Feb 2003 68P02901W56-L 17–67
SDCCH_TRAFFIC_CARRIED GSR6
SDCCH_TRAFFIC_CARRIED
Description
The SDCCH_TRAFFIC_CARRIED statistic provides the mean number of busy SDCCHs
Formula
SDCCH_TRAFFIC_CARRIED = BUSY_SDCCH_MEAN
m
k= 1

n
k= 1
n m
S BUSY_SDCCH_MEAN
SDCCH_TRAFFIC_CARRIED =
Sk= 1
k= 1 [k]
NOTE
The BUSY_SDCCH_MEAN statistic reports the mean number of busy traffic
Where BUSY_SDCCH_MEAN [k] is BUSY_SDCCH_MEAN for statistical

interval k.
Usage RF loss.
Congestion.
Network planning.
Optimization.
Basis BSS.
Type Counter.
Raw Statistic BUSY_SDCCH.

17–68 68P02901W56-L 14 Feb 2003
GSR6 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
(TOTAL_CALLS +
TCH_ACCESSES = IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +
BSS Level
TCH_ACCESSES = (TOTAL_CALLS + IN_INTER_BSS_HO_SUC +
ASSIGNMENT_REDIRECTION)
Network Level
TCH_ACCESSES = (TOTAL_CALLS + ASSIGNMENT_REDIRECTION)
Usage Handover.
Quality of service.
Network planning.
Type Counter.
TOTAL_CALLS.

14 Feb 2003 68P02901W56-L 17–69
TCH_CONGESTION_TIME GSR6
TCH_CONGESTION_TIME
Description
The TCH_CONGESTION_TIME statistic tracks the amount of time in seconds that all
TCHs are busy.
Formula
TCH_CONGESTION
TCH_CONGESTION_TIME =
1000
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Duration.
Raw TCH_CONGESTION.
Statistics

17–70 68P02901W56-L 14 Feb 2003
GSR6 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
RF_LOSSES_TCH * 100%
TCH_RF_LOSS_RATE =
(TOTAL_CALLS + IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC]
+ IN_INTER_BSS[IN_INTER_BSS_HO_SUC])
BSS Level
RF_LOSSES_TCH
TCH_RF_LOSS_RATE = * 100%
IN_INTER_BSS[IN_INTER_HO_SUC])
Network Level RF_LOSSES_TCH * 100%

TCH_RF_LOSS_RATE =
TOTAL_CALLS + ASSIGNMENT_REDIRECTION

Fault finding.
Basis Cell.
Type Percentage.
Statistics IN_INTER_BSS[IN_INTER_HO_SUC].
IN_INTRA_BSS[IN_INTRA_BSS_HO_SUC]
RF_LOSSES_TCH.
TOTAL_CALLS.

14 Feb 2003 68P02901W56-L 17–71
TCH_TRAFFIC_CARRIED GSR6
TCH_TRAFFIC_CARRIED
Description
The TCH_TRAFFIC_CARRIED statistic tracks the mean number of busy TCHs
Formula
For an individual cell for an individual statistics interval:
TCH_TRAFFIC_CARRIED = BUSY_TCH_MEAN
m
k= 1
n
k= 1
n m
S BUSY_TCH_MEAN [k]
TCH_TRAFFIC_CARRIED =
Sk= 1
k= 1
NOTE The BUSY_TCH_MEAN statistic reports the mean number of

busy traffic channels during a collection interval, where
BUSY_TCH_MEAN [k] is BUSY_TCH_MEAN for statistical
interval k.
Usage Congestion.
Quality of service.
Network planning.
Optimization.
Basis Cell.
Type Units = Erlangs.
Raw BUSY_TCH (BUSY_TCH_MEAN).

Statistics

17–72 68P02901W56-L 14 Feb 2003
GSR6 UL_AIR_INTERFACE_BW_CS1
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

UL_AIR_INTERFACE_BW_CS1 =
(50 * 3600) * INTERVAL
(TOTAL_AIR_UL_AVAILABLE_BW * 9.05)
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.
TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1)

14 Feb 2003 68P02901W56-L 17–73
UL_AIR_INTERFACE_BW_CS2 GSR6
Description
collection period.
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.
TOTAL_AIR_UL_AVAILABLE_BW (GSR5.1).

17–74 68P02901W56-L 14 Feb 2003
GSR6 UL_AIR_INTERFACE_BW_CS3
Description
collection period.
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.

14 Feb 2003 68P02901W56-L 17–75
UL_AIR_INTERFACE_BW_CS4 GSR6
Description
collection period.
Formula

(50 * 3600) * INTERVAL
(50 * 3600) * INTERVAL

Basis Cell.
Type Counter.

17–76 68P02901W56-L 14 Feb 2003
GSR6 UPLINK_PDTCH_BLOCKING_RATE
UPLINK_PDTCH_BLOCKING_RATE
Description
The UPLINK_PDTCH_BLOCKING_RATE statistic provides the success rate of channel
requests in GPRS.
Formula
CHANNEL_REQS_REJECT
UPLINK_PDTCH_BLOCKING_RATE = * 100%
CHANNEL_REQS_REC

Quality of Service Monitoring.
Network planning.
Basis Cell.
Type Percentage.
Raw CHANNEL_REQS_REJECT.
Statistics CHANNEL_REQS_REC.

14 Feb 2003 68P02901W56-L 17–77
UPLINK_TRAFFIC_VOLUME GSR6
UPLINK_TRAFFIC_VOLUME
Description
The UPLINK_TRAFFIC_VOLUME statistic provides a measure of the volume of uplink
Radio Link Control traffic including retransmitted blocks.
Formula
UPLINK_TRAFFIC_VOLUME= AIR_UL_DATA_BLKS[QOS3_CS1]) * 22) + * 100%
AIR_UL_DATA_BLKS[QOS3_CS2]) * 32) +
AIR_UL_DATA_BLKS[QOS3_CS3]) * 38) +
AIR_UL_DATA_BLKS[QOS3_CS4]) * 52)
(1024 * 3600 * INTERVAL)

Basis Cell.
Type Percentage.

17–78 68P02901W56-L 14 Feb 2003
Chapter 18
Ladder diagrams

14 Feb 2003 68P02901W56-L 18–1
GSR6

18–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to ladder diagrams
Introduction to ladder diagrams
Description of 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 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.
Example
Figure 18-1 shows the relationships associated with an immediate assignment failure.
Figure 18-1 Diagram of immediate assignment failure
MS BSS MSC
OK_ACC_PROC_RACH (SEE NOTE)
TIMEOUT
CHAN_REQ_MS_FAIL

14 Feb 2003 68P02901W56-L 18–3
Phone call model GSR6
Phone call model
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. It communicates 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.
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.

18–4 68P02901W56-L 14 Feb 2003
GSR6 Phone call model
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

14 Feb 2003 68P02901W56-L 18–5
Call procedure milestones GSR6
Call procedure milestones
Introduction
A general description of the milestones in a call is 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-L 14 Feb 2003
GSR6 Call setup and handover
Call setup and handover
Description
Statistics describe the behaviour of the major call processing scenarios. Each scenario is
broken out into six milestones as shown in the vertical columns of Table 18-1.
Matrix
Table 18-1 shows the call setup and handover matrix:
Table 18-1 Call setup and handover matrix.

Procedure Milestones
Bids Blocked Attempts Success Failed Failed
lost recovered
Immediate OK_ACC_PROC_RACH CHAN_REQ_MS_BLK see note 3 OK_ACC_PROC CHAN_REQ_MS_FAIL N/A
Assignment and and or
ALLOC_SDCCH_FAIL INV_EST_CAUSE_IN_
ALLOC_SDCCH
see note 2
see note 1 RACH
see note 5
Connection – – CONN_REQ_TO_MSC – CONN_REFUSED N/A

Establishment
Assignment MA_REQ_FROM_MSC MA_CMD_TO_MS_ MA_CMD_TO_MSC TOTAL_CALLS For further study MA_FAIL_FROM_MS

to TCH at call set-up and
BLKD
MA_COMPLETE_TO_MSC
ALLOC_TCH_FAIL
ALLOC_TCH
Handover INTRA_CELL_HO_REQ ALLOC_SDCCH_FAIL INTRA_CELL_HO_AT INTRA_CELL_HO INTRA_CELL_HO_LOSTMS INTRA_CELL_HO_FAIL

Intra-cell or MPT and
HO_FAIL_NO_ and MA_FAIL_FROM_MS
RESOURCES MA_CMD_TO_MS
(INTER_BSS)
or
ALLOC_TCH_FAIL
Handover OUT_INTRA_BSS_HO_ OUT_INTRA_HO_PRI OUT_INTRA_BSS_HO OUT_INTRA_BSS_HO OUT_INTRA_BSS_HO OUT_INTRA_BSS_HO_

Intra-BSS REQ _BLK _ATMPT and _LOSTMS FAIL
(outgoing) and OUT_HO_NC_SUC
or OUT_HO_CAUSE_AT
MPT
HO_FAIL_NO_ and
RESOURCES OUT_HO_NC_CAUSE
(INTRA_BSS) _ATMPT
Handover OUT_INTER_BSS_REQ HO_FAIL_NO_ OUT_INTER_BSS_HO OUT_INTER_BSS_HO OUT_INTER_BSS_HO OUT_INTER_BSS_HO

Inter-BSS _TO_MSC RESOURCES _ATMPT _SUC _LOSTMS _RETURN
(outgoing) (INTER_BSS) and
OUT_HO_CAUSE_AT
MPT
and
OUT_HO_NC_CAUSE
_ATMPT

14 Feb 2003 68P02901W56-L 18–7
Call setup and handover GSR6
Procedure Milestones
Bids Blocked Attempts Success Failed Failed
lost recovered
Handover For further study For further study IN_INTRA_BSS_NC_A IN_INTRA_BSS_HO_SUC IN_INTRA_BSS_HO IN_INTRA_BSS_HO
Intra-BSS ALLOC_SDCCH_FAIL TMPT and _LOSTMS _RETURN
(incoming) or or IN_INTRA_BSS_NC_SUC
ALLOC_TCH_FAIL ALLOC_SDCCH
or
ALLOC_TCH
Handover For further study For further study HO_REQ_MSC_OK IN_INTER_BSS_HO IN_INTER_BSS_HO IN_INTER_BSS_HO
Inter-BSS see note 4 ALLOC_SDCCH [IN_INTER_BSS_MS_ [IN_INTER_BSS_MS_N
(incoming) ALLOC_SDCCH_FAIL or NO_SEIZE] O_SEIZE]
or ALLOC_TCH
ALLOC_TCH_FAIL
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–8 68P02901W56-L 14 Feb 2003
GSR6 Connection establishment
Introduction
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.
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

14 Feb 2003 68P02901W56-L 18–9
Connection establishment GSR6
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


18–10 68P02901W56-L 14 Feb 2003
GSR6 Connection establishment
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

14 Feb 2003 68P02901W56-L 18–11
Connection establishment GSR6
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)

18–12 68P02901W56-L 14 Feb 2003
GSR6 Assignment to TCH
Assignment to TCH
Introduction
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 types of MS. Will not
be pegged after the TCH is deallocated.

14 Feb 2003 68P02901W56-L 18–13
Assignment to TCH GSR6
Immediate assignment failure

Figure 18-9 shows an immediate assignment failure.
Figure 18-9 Immediate assignment failure
MS BSS MSC
OK_ACC_PROC_SUC_RACH
(SEE NOTE 1)
INV_EST_CAUSE_ON_RACH
(SEE NOTE 2)
NOTES:
1. RSS Abis does additional filtering of RACH.
2. RSS Abis filtering detects and invalid channel request on 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

18–14 68P02901W56-L 14 Feb 2003
GSR6 Assignment to TCH
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.

14 Feb 2003 68P02901W56-L 18–15
Intra-cell handover GSR6
Intra-cell handover
Introduction
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

MS MS
(SOURCE CHANNEL) BSS (TARGET CHANNEL)
INTRA_CELL_HO (INTRA_CELL_HO_REQ)
(SEE NOTE)
ASSIGNMENT COMMAND ALLOC_TCH or ALLOC_SDCCH
INTRA_CELL_HO (INTRA_CELL_HO_ATMPT)
MA_CMD_TO_MS
MSC
ASSIGNMENT COMPLETE
HANDOVER INTRA_CELL_HO (INTRA_CELL_HO_SUC)
PERFORMED
NOTE: Need for handover is recognized within the BSS.
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)
HO_FAIL_NO_RESOURCES
(INTRA_CELL_HO)
ALLOC_TCH_FAIL
NOTE: Need for handover is recognized within the BSS.

18–16 68P02901W56-L 14 Feb 2003
GSR6 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
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
MA_CMD_TO_MS
ASSIGNMENT FAILURE
(SEE NOTE 2)
INTRA_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.
Fail lost
Figure 18-15 shows an intra-cell handover fail-lost.
Figure 18-15 Handover (intra-cell) fail-lost
MS MS
(SEE NOTE 1)
ALLOC_TCH
ASSIGNMENT COMMAND
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.

14 Feb 2003 68P02901W56-L 18–17
Inter-BSS handover GSR6
Inter-BSS handover
Introduction
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
BSS MS (SOURCE MS (TARGET

BSS
(SOURCE) CHANNEL CHANNEL
MSC (TARGET)
SOURCE CELL) TARGET CELL)
HANDOVER
REQUIRED (SEE NOTE 1)
INTER_BSS_HO HANDOVER
(OUT_INTER_BSS_ REQUEST
REQ_TO_MSC) ALLOC_TCH
HANDOVER REQUEST or ALLOC_SDCCH
HANDOVER ACKNOWLEDGE
HANDOVER HO_REQ_MSC_OK
COMMAND
COMMAND (SEE NOTE 2)
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
ATMPT)
OUT_HO_CAUSE_
ATMPT
HANDOVER
OUT_HO_NC_
COMPLETE
CAUSE_ATMPT
HANDOVER IN_INTER_BSS_HO
CLEAR COMPLETE (IN_INTER_BSS_
COMMAND HO_SUC)
OUT_INTER_BSS_HO
(OUT_INTER_BSS
HO_SUC)
OUT_HO_NC_SUC
NOTES:
2. BAD_HO_REFNUM pegs each time a handover access burst (actual or phantom) is
detected that contains a bad handover reference number.

18–18 68P02901W56-L 14 Feb 2003
GSR6 Inter-BSS handover
Handover blocked
Figure 18-17 shows an inter-BSS handover blocked.
Figure 18-17 Handover (inter-BSS) blocked
MS
(SOURCE MS (TARGET
CHANNEL BSS BSS CHANNEL
MSC (TARGET)
SOURCE CELL) (SOURCE) TARGET CELL)
HANDOVER
REQUIRED HANDOVER
(SEE NOTE 1) REQUEST ALLOC_TCH_FAIL
OUT_INTER_BSS_HO
(OUT_INTER_BSS_
REQ_TO_MSC) HO_FAIL_NO_RESOURCES
(INTER_BSS_HO)
HANDOVER FAILURE
(SEE NOTE 4)
HO_REQ_MSC_FAIL
(SEE NOTE 3)
HANDOVER
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.

14 Feb 2003 68P02901W56-L 18–19
Fail recovered
Figure 18-18 shows an inter-BSS handover fail-recovered.
Figure 18-18 Handover (inter-BSS) fail-recovered
MS
(SOURCE MS (TARGET
SOURCE CELL) (SOURCE) MSC (TARGET) TARGET CELL)
HANDOVER REQUIRED
(SEE NOTE 1) HANDOVER
REQUEST
ALLOC_TCH
OUT_INTER_BSS_HO
or ALLOC_SDCCH
(OUT_INTER_BSS_REQ_ HANDOVER REQUEST
TO_MSC) ACKNOWLEDGE
HANDOVER
COMMAND HO_REQ_MSC_OK
HANDOVER (SEE NOTE 2)
COMMAND
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:
detected which contains a bad handover reference number.

18–20 68P02901W56-L 14 Feb 2003
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
REQUIRED HANDOVER
REQUEST
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.

14 Feb 2003 68P02901W56-L 18–21
Fail lost (mobile)

Figure 18-20 shows an inter-BSS handover failure with lost mobile.
Figure 18-20 Inter-BSS handover failure with lost mobile
MS
(SOURCE MS (TARGET
MSC (TARGET)
SOURCE CELL) (SOURCE) TARGET CELL)
HANDOVER REQUIRED
(SEE NOTE 1) HANDOVER
REQUEST
OUT_INTER_BSS_HO ALLOC_TCH or
(OUT_INTER_BSS_REQ ALLOC_SDCCH
_TO_MSC
HANDOVER
HANDOVER REQUEST HO_REQ_MSC_OK
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_HO_INTER_BSS_HO
(OUT_INTER_BSS_LOST
MS)
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 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–22 68P02901W56-L 14 Feb 2003
Standard directed retry (external)

Figure 18-21 shows an inter–BSS handover directed retry external.
Figure 18-21 Inter-BSS handover directed retry external
MS MS (TARGET
(SOURCE CHANNEL BSS MSC
BSS CHANNEL
SOURCE CELL) (SOURCE) (TARGET) TARGET CELL)
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 REQUIRED HANDOVER

(SEE NOTE 3) REQUEST ALLOC_TCH
or ALLOC_SDCCH
HANDOVER REQUEST
ACKNOWLEDGE
HANDOVER HO_REQ_MSC_OK
COMMAND (SEE NOTE 2)
HANDOVER
COMMAND CONGEST_STAND_
HO_ATMPT HANDOVER
COMPLETE
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_
ATMPT)
IN_INTER_BSS_HO
OUT_HO_CAUSE_ATMPT (SUCCESSFUL)
(CONGESTION) HANDOVER
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.

14 Feb 2003 68P02901W56-L 18–23
Intra-BSS handover GSR6
Intra-BSS handover
Introduction
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
MS MS (TARGET
(SOURCE CHANNEL BSS CHANNEL
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_REQ)
(SOURCE CELL) (SEE NOTE 1)
ALLOC_TCH or ALLOC_SDCCH
OUT_INTRA_BSS_HO
HANDOVER (OUT_INTRA_BSS_HO_ATMPT) (SOURCE CELL)
COMMAND
IN_INTRA_BSS_NC_ATMPT (TARGET CELL)
OUT_HO_CAUSE_ATMPT (SOURCE CELL)
OUT_HO_NC_CAUSE_ATMPT (SOURCE CELL)

(SEE NOTE 2)
HANDOVER COMPLETE
OUT_INTRA_BSS_HO (OUT_INTRA_BSS_HO_SUC)
(SOURCE CELL)
OUT_HO_NC_SUC (SOURCE CELL)
IN_INTRA_BSS_HO (TARGET CELL) (SEE NOTE 3)
(IN_INTRA_BSS_NC_SUC) (TARGET CELL)
NOTES:
detected that contains a bad handover reference number.
3. Handover performed message sent to MSC by source cell.

18–24 68P02901W56-L 14 Feb 2003
GSR6 Intra-BSS handover
Handover- blocked
Figure 18-23 shows an intra-BSS handover-blocked.
Figure 18-23 Handover (intra-BSS) blocked

MS MS (TARGET
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.
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
SOURCE CELL) CHANNEL
TARGET CELL)
OUT_INTRA_BSS_HO
(SEE NOTE 1)
ALLOC_TCH or ALLOC_SDCCH
HANDOVER COMMAND (SEE NOTE 2)
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 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.

14 Feb 2003 68P02901W56-L 18–25
Intra-BSS handover GSR6
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 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–26 68P02901W56-L 14 Feb 2003
GSR6 Intra-BSS handover
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
MSC BSS MS
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
CALLS_QUEUED
TCH_Q_LENGTH
QUEUEING INDICATION (SEE NOTE 1)
CONGEST_STAND_HO_ATMPT
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT (CONGESTION)
(CONGESTION)
ASSIGNMENT FAILURE CAUSE DIRECTED RETRY
(SEE NOTE 2)
HANDOVER REQUIRED (SEE NOTE 3)

HANDOVER COMMAND HANDOVER COMMAND
(CONGESTION)
IN_INTRA_BSS_HO
(IN_INTRA_BSS_HO_SUC)
ASSIGNMENT COMPLETE OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_SUC)
MA_COMPLETE_TO_MSC
NOTES:
1. Only if queuing 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.

14 Feb 2003 68P02901W56-L 18–27
Call clearing GSR6
Call clearing
Introduction
Figure 18-27 to Figure 18-30 show the ladder diagrams for the call clearing procedures.
Cipher mode fail

Figure 18-27 shows BSS initiated call clearing – cipher mode fail.
Figure 18-27 BSS initiated call clearing–cipher mode fail

MS BSS MSC
CIPHERING MODE COMMAND
TIMEOUT
CIPHER_MODE_FAIL
CLEAR REQUEST
CLR_REQ_TO_MSC
RF loss on an SDCCH
Figure 18-28 shows BSS initiated call clearing (RF loss on an SDCCH).
Figure 18-28 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.

18–28 68P02901W56-L 14 Feb 2003
GSR6 Call clearing
RF loss on a TCH
Figure 18-29 shows BSS initiated call clearing – RF loss on a TCH.
Figure 18-29 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.
Queueing timeout
Figure 18-30 shows BSS initiated call clearing (queueing timeout).
Figure 18-30 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.

14 Feb 2003 68P02901W56-L 18–29
Short message service GSR6
Short message service
Introduction
Figure 18-31 and Figure 18-32 show the ladder diagrams for the short message service
procedures.
Mobile originated
Figure 18-31 shows MS originated short message service (point-to-point).
Figure 18-31 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.
Mobile terminated
Figure 18-32 shows mobile terminated short message service (point-to-point).
Figure 18-32 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.

18–30 68P02901W56-L 14 Feb 2003
GSR6 Congestion Relief
Congestion Relief
Intra-BSS congestion relief
Example
Figure 18-33 shows the relationships associated with an intra-BSS congestion relief
handover procedure. 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.
Figure 18-33 Intra-BSS congestion relief handover procedure
MSC BSS MS
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH_FAIL
CALLS_QUEUED
QUEUEING INDICATION (SEE NOTE) TCH_Q_LENGTH
ALLOC_TCH
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
(CONGESTION)
(CONGESTION)
CONGEST_EXIST_HO_ATMPT
(SEE NOTE)
HANDOVER COMMAND
HANDOVER COMPLETE
IN_INTRA_BSS_HO
OUT_INTRA_BSS_HO
ALLOC_TCH
TCH_Q_REMOVED
(assignment_resource_req)
MA_CMD_TO_MS
ASSIGNMENT COMMAND
ASSIGNMENT COMPLETE
MA_COMPLETE_FROM_MS
ASSIGNMENT COMPLETE
MA_COMPLETE_TO_MSC
TOTAL_CALLS
NOTE: Only if queueing is enabled for the cell.

14 Feb 2003 68P02901W56-L 18–31
Directed retry GSR6
Directed retry
Intra-BSS directed retry
Example
Figure 18-34 shows the relationships associated with an intra-BSS directed retry
procedure.
Figure 18-34 Intra-BSS directed retry procedure
MSC BSS MS
ASSIGNMENT REQUEST
MA_REQ_FROM_MSC
ALLOC_TCH_FAIL
CALLS_QUEUED
QUEUING INDICATION (SEE NOTE 1) TCH_Q_LENGTH
ALLOC_TCH
TCH_Q_REMOVED
(assignment_resource_req)
OUT_INTRA_BSS_HO
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
CONGEST_STAND_HO_ATMPT (SEE NOTE1)

HANDOVER COMMAND
HANDOVER COMPLETE
IN_INTRA_BSS_HO
OUT_INTRA_BSS_HO
ASSIGNMENT COMPLETE (SEE NOTE 2)
MA_COMPLETE_TO–MSC
(DIRECTED RETRY)
NOTES:
1. Only if queuing is enabled for the cell
2. The database element msc_preference indicates that directed retry procedures are limited to
within the BSS. The BSS sends a Handover Performed message, which indicates the new cell ID.

18–32 68P02901W56-L 14 Feb 2003
GSR6 Flow control
Flow control
Description
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-35 shows the relationships associated with an access procedure.
Figure 18-35 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.

14 Feb 2003 68P02901W56-L 18–33
Intra-BSS interband activity GSR6
Intra-BSS interband activity
Introduction
Figure 18-36 to Figure 18-38 show 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-36 shows an established call on TCH with a subsequent successful intra-BSS
handover to a PGSM cell.
Figure 18-36 Successful intra–BSS handover
MS BSS MS (TARGET
(SOURCE CHANNEL CHANNEL
OUT_INTRA_BSS_HO
ALLOC_TCH (TARGET CELL)
MS_ACCESS_BY_TYPE (TARGET CELL) (SEE NOTE 1)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
(BAND_HANDOVER) (SEE NOTE 2)
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT) (SEE NOTE 3)
HANDOVER
COMPLETE
OUT_INTRA_BSS_HO
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 GSM850 target cells, bin gsm_850_ho_atmpt pegs
for DCS1800 target cells, bin, dcs_1800_ho_atmpt pegs
for PCS1900 target cells, bin, pcs_1900_ho_atmpt pegs
for EGSM target cells, bin egsm_ho_atmpt pegs

18–34 68P02901W56-L 14 Feb 2003
GSR6 Intra-BSS interband activity
Handover unsuccessful (fail recovered)

Figure 18-37 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-37 Unsuccessful interband handover with fail–recovered source cell
MS MS (TARGET
OUT_INTRA_BSS_HO
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 GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail peg
for DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail peg
for PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail peg
for EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg

14 Feb 2003 68P02901W56-L 18–35
Intra-BSS interband activity GSR6
Handover unsuccessful (fail recovered due to invalid frequency supported)

Figure 18-38 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-38 Unsuccessful interband handover
MS MS (TARGET
OUT_INTRA_BSS_HO
(OUT_INTRA_BSS_HO_REQ) (SOURCE CELL)
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 GSM850 target cells, bin gsm_850_ho_atmpt & gsm_850_ho_fail peg
for DCS1800 target cells, bins dcs_1800_ho_atmpt & dcs_1800_ho_fail peg
for PCS1900 target cells, bins pcs_1900_ho_atmpt & pcs_1900_ho_fail peg
for EGSM target cells, bins egsm_ho_atmpt & egsm_ho_fail peg

18–36 68P02901W56-L 14 Feb 2003
GSR6 Inter-BSS interband activity
Inter-BSS interband activity
Handover successful
Figure 18-39 shows an established call on TCH with a subsequent successful inter-BSS
handover to a PGSM cell.
Figure 18-39 Successful inter-BSS handover
MS (SOURCE BSS MSC BSS MS (TARGET

CHANNEL (SOURCE) (TARGET) CHANNEL
HANDOVER
REQUIRED (SEE NOTE 1)
HANDOVER
OUT_INTER_BSS_HO REQUEST
ALLOC_TCH
(OUT_INTER_BSS_RE
Q_TO_MSC)
HANDOVER REQUEST MS_ACCESS_BY_TYPE
(SEE NOTE 2)
ACKNOWLEDGE
HANDOVER
HANDOVER
(SEE NOTE 3)
COMMAND OUT_INTER_BSS_HO
(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)
COMPLETE
HANDOVER
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 GSM850 target cells, bin GSM_850_HO_ATMPT pegs
for DCS1800 target cells, bin DCS_1800_HO_ATMPT pegs
for PCS1900 target cells, bin PCS1900_HO_ATMPT pegs
for EGSM target cells, bin EGSM_HO_ATMPT pegs

14 Feb 2003 68P02901W56-L 18–37
Inter-BSS interband activity GSR6

Figure 18-40 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-40 Inter-BSS handover unsuccessful with fail–recovered source cell

HANDOVER
REQUIRED (SEE NOTE 1) HANDOVER
OUT_INTER_BSS_HO REQUEST ALLOC_TCH
(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_MSC_OK
(OUT_INTER_BSS_HO_ (SEE NOTE 3)
ATMPT)
OUT_HO_CAUSE_
ATMPT
OUT_HO_NC_CAUSE_A
TMPT (BAND
INTERBAND_ACTIVITY
(PGSM_HO_ATMPT)
HANDOVER (SEE NOTE 5)
FAILURE
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO
_RETURN)
INTERBAND_ACTIVITY
(PGSM_HO_FAIL)
(SEE NOTE 5)
HANDOVER
FAILURE
HO_REQ_MSC_FAIL
NOTES:
Classmark Update message from the mobile so that the target BSS can peg the MS access
type.
OUT_HO_NC_CAUSE_ATMPT is just one possible valid cause for the inter-BSS handover.
Other causes are possible and valid as well (like powerbudget, uplink quality, downlink level,
etc). Band handover triggered handovers are done to move the mobile from its current
frequency band to a preferred frequency band.
5. For other target cell frequency bands, the appropriate bins for INTERBAND_ACTIVITY will peg.
For example, the above ladder diagram applies for other frequency bands, except that
for GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg
for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg
for PCS1900 target cells, bins PCS1900_HO_ATMPT and PCS_1900_HO_FAIL peg
for EGSM target cells, bins EGSM_HO_ATMPT and EGSM_HO_FAIL peg

18–38 68P02901W56-L 14 Feb 2003
GSR6 Inter-BSS interband activity
Handover unsuccessful fail recovered due to invalid frequency supported

Figure 18-41 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-41 Inter-BSS handover unsuccessful due to invalid frequency supported

SOURCE CELL) HANDOVER TARGET CELL)
REQUIRED (SEE NOTE 1) HANDOVER
REQUEST ALLOC_TCH
OUT_INTER_BSS_HO
(OUT_INTER_BSS_REQ
_TO_MSC) MS_ACCESS_BY
HANDOVER REQUEST _TYPE (SEE NOTE 2)
COMMAND
HANDOVER
OUT_INTER_BSS_HO
(OUT_INTER_BSS_HO_ (SEE NOTE 3)
ATMPT)
OUT_HO_CAUSE_
ATMPT
OUT_HO_NC_CAUSE_A
TMPT (BAND
INTERBAND_ACTIVITY
HANDOVER (PGSM_HO_ATMPT)
(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 GSM850 target cells, bin GSM_850_HO_ATMPT and GSM_850_HO_FAIL peg
for DCS1800 target cells, bins DCS_1800_HO_ATMPT and DCS_1800_HO_FAIL peg

14 Feb 2003 68P02901W56-L 18–39
Interband assignment GSR6
Interband assignment
Interband activity invalid frequency at assignment

Figure 18-42 shows an invalid frequency at assignment.
Figure 18-42 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–40 68P02901W56-L 14 Feb 2003
GSR6 Band Reassignment
Band Reassignment
Introduction
Figure 18-43 and Figure 18-44 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-43 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-43 Intra-BSS handover successful
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
MS_ACCESS_BY_TYPE (TARGET CELL)
(MS_PGSM_DCS1800)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)
INTERBAND_ACTIVITY
HANDOVER (DCS1800_HO_ATMPT)
COMPLETE
(RECEIVED FROM OUT_INTRA_BSS_HO
TARGET CELL) (OUT_INTRA_BSS_HO_SUC)
OUT_HO_NC_SUC

14 Feb 2003 68P02901W56-L 18–41
Band Reassignment GSR6

Figure 18-44 shows an unsuccessful band reassign.
Figure 18-44 Unsuccessful band reassign
MS BSS MSC
ASSIGNMENT
REQUEST
MA_REQ_FROM_MSC
OUT_INTRA_BSS_HO
MS_ACCESS_BY_TYPE (TARGET CELL)
(MS_PGSM_DCS1800)
HANDOVER
COMMAND
OUT_INTRA_BSS_HO
OUT_HO_CAUSE_ATMPT
OUT_HO_NC_CAUSE_ATMPT (BAND_REASSIGN)
INTERBAND_ACTIVITY
HANDOVER (DCS1800_HO_ATMPT)
FAILURE
OUT_INTRA_BSS_HO
INTERBAND_ACTIVITY
(DCS1800_HO_FAIL)

18–42 68P02901W56-L 14 Feb 2003
GSR6 RSL link scenarios
RSL link scenarios
Introduction
Figure 18-45 shows a ladder diagram scenario for the Radio Signalling Link (RSL) link.
RSL link scenarios
Figure 18-45 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)
N2_EXPIRY (note 2)
STEP 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.

14 Feb 2003 68P02901W56-L 18–43
MTL link scenarios GSR6
MTL link scenarios
Introduction to MTL link scenarios

Figure 18-46 to Figure 18-49 show four ladder diagrams as scenarios for the Message
Transfer Link (MTL) link.
MTL link (operator initiated outage)
Figure 18-46 MTL link scenario (Part I)

STEP 1:
lock of MTL
lock of associated MSI/XCDR
lock of associated MMS
front panel reset
MSI/XCDR board physically removed
MTL LINK
MTP_UNAVAILABLE
timer started
MTP_LINK_INS
STEP 2: timer stopped
unlock of MTL
unlock of associated MSI/XCDR
unlock of associated MMS
front panel restore
MSI/XCDR board physically returned
MTL LINK
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.
NOTE
Lock of MTL or associated device transitions operator and admin states from
B–U to D–L
Unlock of MTL or associated device transitions operator and admin states from
D–L to B–U.

18–44 68P02901W56-L 14 Feb 2003
GSR6 MTL link scenarios
MTL link (transition scenarios Part II)

Figure 18-47 shows an MTL transition from B–U to E–U and E–U to B–U with reason
Wait.
Figure 18-47 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

14 Feb 2003 68P02901W56-L 18–45
MTL link scenarios GSR6
MTL link (transition scenarios Part III)

Figure 18-48 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-48 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_SL_FAIL
incremented
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–46 68P02901W56-L 14 Feb 2003
GSR6 MTL link scenarios
MTL link (transition scenarios Part IV)

Figure 18-49 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-49 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_SL_FAIL
incremented
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

14 Feb 2003 68P02901W56-L 18–47
GBL statistics GSR6
GBL statistics
Introduction to GBL statistics
Figure 18-50 to Figure 18-54 show how the GBL statistics function within the BSS/PCU.
GBL_DL_DATA_THRPUT
Figure 18-50 shows GBL_DL_DATA_THRPUT.
Figure 18-50 GBL_DL_DATA_THRPUT
DLCI = 45 DLCI = 45
Bearer chan 1
DLCI = 55
DLCI = 55
GBL_DL_DATA_THRPUT
GBL_DL_DATA_THRPUT_TIME_PERIOD

18–48 68P02901W56-L 14 Feb 2003
GSR6 GBL statistics
GBL_FLOW_CTRL_SENT
Figure 18-51 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-51 GBL_FLOW_CTRL_SENT
BSS/PCU SGSN
BSSGP FLOW CONTROL PDU
GBL_FLOW_CTRL_SENT
BSSGP FLOW CONTROL ACK PDU

14 Feb 2003 68P02901W56-L 18–49
GBL statistics GSR6
CELL_FLUSH_REQS
Figure 18-52 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-52 CELL_FLUSH_REQS
SGSN GB FU PS
FLUSH PDU FLUSH PDU
CELL_FLUSH_REQS

18–50 68P02901W56-L 14 Feb 2003
GSR6 GBL statistics
GBL_PAGING_REQS
Figure 18-53 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-53 GBL_PAGING_REQS
SGSN BSS/PCU
MS
BSSGP PS PDU
GBL_PAGING_REQS
PACKET PAGING REQEST (PCH)
Channel Request (RACH)
Immediate Assignment (GCH)

14 Feb 2003 68P02901W56-L 18–51
GBL statistics GSR6
GBL_UL_DATA_THRPUT
Figure 18-54 illustrates the statistic GBL_UL_DATA_THRPUT.
Figure 18-54 GBL_UL_DATA_THRPUT
DLCI = 45 DLCI = 45
Bearer chan 1
DLCI = 55 DLCI = 55
GBL_UL_DATA_THRPUT
GBL_UL_DATA_THRPUT_TIME_PERIOD

18–52 68P02901W56-L 14 Feb 2003
GSR6 Accessibility statistics
Accessibility statistics
Introduction to accessibility statistics

Figure 18-55 to Figure 18-59 illustrate accessibility statistics.
CHANNEL_REQ_REJ
Figure 18-55 is a ladder diagram detailing the statistic CHANNEL_REQ_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-55 Accessibility CHANNEL_REQ_REJ
BSS/PCU MS
Immediate Assignment (AGCH)
Packet Resource Request
CHANNEL_REQ_REJ
PACKET ACCESS REJECT

14 Feb 2003 68P02901W56-L 18–53
Accessibility statistics GSR6
Channel request (RACH) and immediate assignment (AGCH)

Figure 18-56 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-56 GPRS_ACCESS_PER_RACH and GPRS_ACCESS_PER_AGCH
BSS/PCU MS

18–54 68P02901W56-L 14 Feb 2003
Accessibility and GBL statistics

Figure 18-57 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-57 Accessibility and GBL statistics
SGSN BSS/PCU MS
BSSGP PS PDU
GBL_PAGING_REQS
PACKET PAGING REQUEST (PCH)

14 Feb 2003 68P02901W56-L 18–55
Accessibility statistics GSR6
Pegging for MS class types

Figure 18-58 is a ladder diagram detailing three MS class type statistics and when
pegging occurs. It also shows the request and response messages sent from the
BSS/PCU to the mobile station.
Figure 18-58 MS CLASS statistics
BSS/PCU MS
Packet Resource Request
MS_CLASS_1_10_REQ
MS_CLASS_11_20_REQ
MS_CLASS_21_29_REQ
CHANNEL_REQ_REC

18–56 68P02901W56-L 14 Feb 2003
Figure 18-59 details the GPRS_CHANNELS_SWITCHED statistic.
Figure 18-59 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

14 Feb 2003 68P02901W56-L 18–57
Throughput statistics GSR6
Throughput statistics
Introduction to throughput statistics

Figure 18-60 and Figure 18-61 show throughput statistics diagrams.
AIR_UL_DATA_BLKS
Figure 18-60 is a ladder diagram detailing the statistic AIR_UL_DATA_BLKS and when
BSS/PCU to the MS.
Figure 18-60 Uplink data transfer
BSS/PCU MS
PACKET UPLINK ASSIGNMENT
DATA BLOCK
AIR_UL_DATA_BLKS
QOS1 QOS2 QOS3 QOS1 QOS2 QOS3

CS1 CS1 CS1 CS2 CS2 CS2

18–58 68P02901W56-L 14 Feb 2003
GSR6 Throughput statistics
AIR_DL_DATA_BLKS
Figure 18-61 is a ladder diagram detailing the statistic AIR_DL_DATA_BLKS and when
BSS/PCU to the MS.
Figure 18-61 Downlink data transfer
BSS/PCU MS
PACKET DOWNLINK ASSIGNMENT
DATA BLOCK
AIR_DL_DATA_BLKS
QOS1 QOS2 QOS3 QOS1 QOS2 QOS3

CS1 CS1 CS1 CS2 CS2 CS2

14 Feb 2003 68P02901W56-L 18–59
Throughput statistics GSR6

18–60 68P02901W56-L 14 Feb 2003
Chapter 19
Impacts on statistics

14 Feb 2003 68P02901W56-L 19–1
GSR6

19–2 68P02901W56-L 14 Feb 2003
GSR6 Introduction to EGSM, approximate equality, and phantom RACHs
Introduction to EGSM, approximate equality, and phantom

RACHs
Introduction
This chapter contains two main sections:
S EGSM, approximate equality, and phantom RACHs.
S Questions and answers.
Description of EGSM, approximate equality, and phantom RACHs

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 following items have an impact on statistics:
S Extended GSM (EGSM).
S Approximate equality.
S Phantom RACHs.

14 Feb 2003 68P02901W56-L 19–3
Extended GSM (EGSM) GSR6
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:
S BCCH carrier frequency.
S SDCCH configuration.
S 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.

19–4 68P02901W56-L 14 Feb 2003
GSR6 Extended GSM (EGSM)
Factors impacting statistics

Factors that contribute to the impacting of statistic values are:
S 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.
S The egsm_handover_threshold flag value.
The following examples illustrate the impact of the EGSM feature on statistics:
Example 1: MS access to a traffic channel

The following conditions must apply:
S EGSM MSs have used up the primary resources in the cell.
S Non-EGSM MSs are attempting to access the cell.
S 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
NOTE TCH_CONGESTION is lower because it is pegged when all

TCHs are busy, not just the primary band TCHs, even though
congestion exists for the primary MSs in this example.

14 Feb 2003 68P02901W56-L 19–5
Extended GSM (EGSM) GSR6
Example 2: Impact due to increased handovers

S The egsm_handover_flag encourages the handovers of EGSM MSs.
S Many EGSM MSs occupy primary resources.
S 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.
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

19–6 68P02901W56-L 14 Feb 2003
GSR6 Extended GSM (EGSM)
Example 3: Impact due to congestion

S A network has mostly non-EGSM MSs accessing the system. Although extended
resources are available, they are used infrequently.
S 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
NOTE TCH_CONGESTION is lower because it is pegged when all

TCHs are busy, not just the primary band TCHs, even though
congestion exists for the primary MSs in this example.

14 Feb 2003 68P02901W56-L 19–7
Approximate equality GSR6
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–8 68P02901W56-L 14 Feb 2003
GSR6 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
counter) OK_ACC_PROC_SUC_RACH
ACCESS_PER_RACH
(1 + unrecognized message
counter)
CHANNEL REQUEST
(INV_EST_CAUSE_ON_RACH
CHANNEL REQUEST
ALLOC_SDCCH
(CHAN_REQ_MS_FAIL)

14 Feb 2003 68P02901W56-L 19–9
Phantom RACHs GSR6
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. If the three bits are not valid, the RSS Abis pegs the
INV_EST_CAUSE_ON_RACH statistic.
NOTE 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–10 68P02901W56-L 14 Feb 2003
GSR6 Phantom RACHs
Raw statistics affected

The following statistics may be affected by phantom RACHs:
S ACCESS_PER_RACH.
S ACCESS_PER_AGCH.
S ALLOC_SDCCH.
S ALLOC_SDCCH_FAIL.
S OK_ACC_PROC_SUC_RACH.
S CHAN_REQ_MS_BLK.
S CHAN_REQ_MS_FAIL.
S SDCCH_CONGESTION.
S BUSY_SDCCH.
S 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.

14 Feb 2003 68P02901W56-L 19–11
Questions and answers GSR6
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:
S ALLOC_SDCCH.
S ALLOC_SDCCH_FAIL.
S BUSY_SDCCH.
S BUSY_TCH.
S RF_LOSSES_SD.
S RF_LOSSES_TCH.
S SDCCH_CONGESTION.
S TCH_CONGESTION.
S 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.
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.

19–12 68P02901W56-L 14 Feb 2003
GSR6 Questions and answers
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.

14 Feb 2003 68P02901W56-L 19–13
Questions and answers GSR6

19–14 68P02901W56-L 14 Feb 2003
Index

14 Feb 2003 68P02901W56-L I–1
GSR6

I–2 68P02901W56-L 14 Feb 2003
GSR6
A B
ACCESS_PER_AGCH, 4–8 BAD_HO_REFNUM_MS, 4–18
ACCESS_PER_PCH, 4–9 Band reassignment, introduction

fail recovered, 18–42
ACCESS_PER_RACH, 4–10 handover successful, 18–41
handover unsuccessful, 18–42
Accessibility statistics, 12–4, 18–53
BAND_HANDOVER, 4–73
ADJ_CHAN_INTF, 4–73
BAND_RE_ASSIGN, 4–73
AIR_DL_CONTROL_BLKS, 12–6
BER, 6–6
AIR_DL_DATA_BLKS, 12–7 Bin ranges, 2–16
AIR_INTERFACE_BW_CS1, 17–7 BSC, functions, 18–4
AIR_INTERFACE_BW_CS2, 17–8 BSS, functions, 18–4
AIR_INTERFACE_BW_CS3, 17–9 BSSLAP_ABORT_RCV, 9–16
AIR_INTERFACE_BW_CS4, 17–10 BSSLAP_ABORT_SENT, 9–15
AIR_INTERFACE_PAGING, 17–11 BSSLAP_MS_POS_CMD, 9–17

BSSLAP_MS_POS_RESP, 9–18
AIR_UL_CONTROL_BLKS, 12–8
BSSLAP_REJ, 9–13
AIR_UL_DATA_BLKS, 12–9
BSSLAP_RESET, 9–14
ALLOC_SDCCH, 4–11
BSSLAP_TA_REQ, 9–10
ALLOC_SDCCH_CARR, 6–4
BSSLAP_TA_RESP, 9–11
ALLOC_SDCCH_FAIL, 4–12 BSSLAP_TOA_REQ, 9–12
ALLOC_TCH, 4–13 BSSMAP_CONLESS_INFO_RCV, 9–19
ALLOC_TCH_CARR, 6–5 BSSMAP_CONLESS_INFO_SENT, 9–20
ALLOC_TCH_FAIL, 4–14 BSSMAP_PERF_LOC_ABORT_MSGS, 9–5
approximate equality, 19–8 BSSMAP_PERF_LOC_REQ_MSGS, 9–4

BSSMAP_PERF_LOC_RESP_MSGS, 9–6, 9–7
assignment to TCH
assignment successful, 18–13 BSSMAPLE_CONLESS_INFO_RCV, 9–21
fail recovered, 18–15 BSSMAPLE_CONLESS_INFO_SENT, 9–22
immediate assignment failure, 18–14
TCH assignment blocked, 18–14 BSSMAPLE_PERF_LOC_ABORT_MSGS, 9–8
BSSMAPLE_PERF_LOC_RESP_MSGS, 9–9
ASSIGNMENT_REDIRECTION, 4–15
BUSY_CICS, 10–5
ASSIGNMENT_RESOURCE, 4–95
BUSY_SDCCH, 4–19
ASSIGNMENT_SUCCESS_RATE, 17–12
BUSY_TCH, 4–20
ATER_PREEMPT_STATUS, 11–4
BUSY_TCH_CARR, 4–22
ATER_STATUS, 11–6
ATTEMPT_IMMED_ASSIGN_PROC, 16–6
C
AVAILABLE_PDTCH, 12–10
call clearing
AVAILABLE_SDCCH, 4–16 cipher mode fail, 18–28
queueing timeout, 18–29
AVAILABLE_TCH, 4–17
RF loss on a TCH, 18–29
Average call duration, 15–4 RF loss on an SDCCH, 18–28

14 Feb 2003 68P02901W56-L I–3
GSR6
Call model statistics, 15–3 CLASSMK_UPDATE_FAIL, 4–29

CALL_DURATION, 15–4 CLR_CMD_FROM_MSC, 4–30
CALL_SETUP_BLOCKING_RATE, 15–5
HANDOVERS_PER_CALL (H), 15–6 CLR_REQ_TO_MSC, 4–31
IMSI_DETACHES_TO_CALL (Id), 15–7 cm_lcs_request, 4–70
INTRA_BSS_HO_TO_ALL_HO (i), 15–8 CM_REESTABLISH, 4–70
LOCATION_UPDATE_FACTOR (L), 15–9
CM_SERV_REQ_CALL, 4–70
LOCATION_UPDATES_TO_CALLS (I), 15–10
PAGES_PER_CALL (PPC), 15–11 CM_SERV_REQ_EMERG, 4–70
PAGES_PER_SECOND, 15–12 CM_SERV_REQ_SMS, 4–70
PAGING_RATE (P), 15–13
CM_SERV_REQ_SUPP, 4–70
SMS_TO_CALL_RATIO (S), 15–14
CODING_SCHEME_CHANGE, 12–15
call procedure
bids, 18–6 CONGEST_EXIST_HO_ATMPT, 4–33
bids–attempt–fail–recovered, 18–6 CONGEST_STAND_HO_ATMPT, 4–34
bids–attempt–failures, 18–6 CONGESTION, 4–73
bids–attempts, 18–6
Congestion relief, intra–BSS, 18–31
bids–attempts–successes, 18–6
bids–bids blocked, 18–6 CONGESTION_LOST_MSU, 10–6
call setup and handover matrix, 18–7 CONN_REFUSED, 4–35
CALL_DURATION, 15–4 CONN_REQ_TO_MSC, 4–36
connection establishment, 18–9
CALL_SETUP_BLOCKING_RATE, 15–5
failure, 18–10
CALL_SETUP_SUCCESS_RATE, 17–13 immediate assignment blocked, 18–11
CALL_SP_VERS_REQUEST_MONITOR, 4–23 immediate assignment failure, 18–11
successful
call statistics, MS_TCH_USAGE_BY_TYPE_PCS, mobile originated, 18–9
4–64 mobile terminated call, 18–12
CALL_SUCCESS_RATE, 17–14 Counter array statistics, 1–7
Counter array bins, 1–7
CALL_VOLUME, 17–15
Interval expiry, 1–7
CALLS_QUEUED, 4–24 Maximum values, 1–7
cell statistics, introduction, 4–3 Counter statistics, 1–6, 2–13
Interval expiry, 1–6
CELL_FLUSH_REQS, 12–11
Maximum value, 1–6
CELL_TCH_ALLOCATIONS, 16–8 Threshold event reporting, 1–6
CELL_TCH_ASSIGNMENTS, 16–9 CPU_USAGE, 7–4
CELL_UPDATE, 17–16 CS1_USAGE_DL, 17–17
CHAN_DL_TX_PWR_LVL, 6–7 CS1_USAGE_UL, 17–18
CS12_ON_32K_CHAN, 12–16
CHAN_REQ_CAUSE_ATMPT, 4–25, 9–3
CS2_USAGE_DL, 17–19
CHAN_REQ_MS_BLK, 4–26
CS2_USAGE_UL, 17–20
CHAN_REQ_MS_FAIL, 4–27, 6–8
CHAN_UL_TX_PWR_LVL, 6–9 CS3_USAGE_UL, 17–22
CHANNEL_REQS_REC, 12–12 CS4_USAGE_DL, 17–23
CHANNEL_REQS_REJ, 12–13 CS4_USAGE_UL, 17–24
CHANNEL_REQS_SUCCESS, 12–14 Custom statistics, 1–4
chg_stat_prop, 2–15
chg_stat_prop command, 2–13 D
CIPHER_MODE_FAIL, 4–28 default values, 2–4

I–4 68P02901W56-L 14 Feb 2003
GSR6
Directed retry, intra–BSS, 18–32 E

disabling a statistic, 2–5
EFR_REQ_FROM_MSC, 3–4
disp_interval command, 2–12
EGSM (extended GSM), 19–4
disp_stat_prop command, 2–17
enabling a statistic, 2–4
disp_stats command, 2–8
ER_INTRA_CELL_HO_ATMPT, 4–39
Displaying a gauge statistic, 2–18
ER_INTRA_CELL_HO_SUC, 4–40
Displaying a counter array statistic, 2–19
Displaying a counter statistic, 2–17
Displaying a distribution statistic, 2–18
F
Displaying a duration statistic, 2–20 feature
3635, 12–4, 12–16, 12–29, 12–30, 12–31
Displaying statistic properties, 2–17
3725, 12–4, 12–52, 12–53
Displaying a counter array statistic, 2–19
3750, 4–9, 4–16, 4–17, 4–80, 4–81, 4–82, 12–4,
Displaying a counter statistic, 2–17 12–5, 12–10, 12–11, 12–14, 12–15, 12–17,
Displaying a distribution statistic, 2–18 12–18, 12–19, 12–20, 12–35, 12–41, 12–42,
Displaying a duration statistic, 2–20 12–43, 12–44, 12–45, 12–46, 12–47, 12–56,
Displaying a gauge statistic, 2–18 12–57, 12–58, 12–59
Displaying statistic values, 2–8 3938, 4–23
3969, 12–4, 12–5, 12–18, 12–19, 12–33, 12–34,
Displaying the statistics interval, 2–11 12–40, 12–57, 12–58
Displaying the statistics interval start times, 2–12 3974, 4–25, 4–70, 8–3, 8–5, 8–6, 8–7, 8–8, 8–9,
8–10, 8–11, 8–12, 8–13, 8–14, 8–15, 8–16,
DISTANCE, 4–73 8–17, 8–18, 8–19, 8–20, 8–21, 8–22, 8–23,
Distribution statistics, 1–9 8–24, 8–25, 8–26, 8–27, 8–28, 8–29, 8–30,
8–31, 8–32, 8–33, 8–34, 8–35, 8–36, 8–37, 9–3,
DL_AIR_INTERFACE_BW_CS1, 17–25 9–4, 9–5, 9–6, 9–7, 9–8, 9–9, 9–10, 9–11, 9–12,
DL_AIR_INTERFACE_BW_CS2, 17–26 9–13, 9–14, 9–15, 9–16, 9–17, 9–18, 9–19,
9–20, 9–21, 9–22, 13–3, 13–4, 13–5, 13–6,
DL_AIR_INTERFACE_BW_CS3, 17–27 13–7, 13–8, 13–9, 13–10, 13–11, 13–12
DL_AIR_INTERFACE_BW_CS4, 17–28 4253, 12–5, 12–6, 12–8, 12–54
4386, 12–4, 12–5, 12–14, 12–59
DL_BUSY_PDTCH, 12–17
references, 4
DL_PDTCH_CONGESTION, 12–18 tag format, 4
DL_PDTCH_Q_LENGTH, 12–19 FER, 6–10
DL_PDTCH_SEIZURE, 12–20 Flow control, description, 18–33
DOWNINTERF, 4–73 FLOW_CONTROL_BARRED, 4–41
DOWNLEVEL, 4–73 FRMR, 11–8
DOWNLINK_TRAFFIC_VOLUME, 17–29
DOWNQUAL, 4–73 G
DROP_CALL_RATE, 17–30
Gauge statistics, 1–7
Duration statistics, 1–8 Interval expiry, 1–7
Interval expiry, 1–8 Threshold event reporting, 1–7
Maximum value, 1–8
Period counter and mean value, 1–8 Gb interface, 12–3
Total duration, 1–8 Gb link, 12–3
Wraparound to next day, 1–8 GBL statistics, 12–3, 18–48
Dynamic allocation statistics, 12–5 GBL_AVAILABILITY, 17–31
DYNET_ASSIGN_FAIL, 4–37 GBL_DL_DATA_THRPUT, 12–21
DYNET_CALL_REJECTS, 4–38 GBL_DL_DATA_THRPUT_HIST, 12–22

14 Feb 2003 68P02901W56-L I–5
GSR6
GBL_FLOW_CTRL_SENT, 12–23 HO_PER_CALL, 17–38

GBL_FLUSH_REQS, see CELL_FLUSH_REQS, HO_REQ, 4–95
12–11 HO_REQ_MSC_FAIL, 4–43
GBL_LINK_INS, 12–24 HO_REQ_MSC_OK, 4–44
GBL_PAGING_REQS, 12–25 HO_REQ_MSC_PROTO, 3–5
GBL_UL_DATA_THRPUT, 12–26
GBL_UL_DATA_THRPUT_HIST, 12–27
I
GBL_UNAVAILABLE, 12–28 I_FRAMES_RX, 11–9
I_FRAMES_TX, 11–10
GPRS performance, 17–4
IDLE_PDTCH_INTF_BAND0, 12–42
GPRS_32K_CHANNELS_SWITCHED, 12–29
IDLE_PDTCH_INTF_BAND1, 12–43
GPRS_32K_DL_NOT_AVAIL, 12–30 IDLE_PDTCH_INTF_BAND2, 12–44
GPRS_32K_UL_NOT_AVAIL, 12–31 IDLE_PDTCH_INTF_BAND3, 12–45
GPRS_ACCESS_PER_AGCH, 12–32 IDLE_PDTCH_INTF_BAND4, 12–46
GPRS_ACCESS_PER_RACH, 12–35 IDLE_TCH_INTF_BAND0, 4–45
GPRS_BW_USAGE_DL, 17–32 IDLE_TCH_INTF_BAND1, 4–46
IDLE_TCH_INTF_BAND2, 4–47
GPRS_BW_USAGE_UL, 17–33
GPRS_CELL_RESELECT_ATTMPT, 12–33
GPRS_CELL_RESELECT_FAIL, 12–34
IMM_ASSGN_CAUSE, 12–47
GPRS_CHANNELS_SWITCHED, 12–36 IMSI detaches, ratio per call, 15–7
GPRS_DL_ACT_TS, 17–34 IMSI_DETACH, 4–70
GPRS_DL_BANDWIDTH_EFFICIENCY, 17–36 IMSI_DETACHES_TO_CALL, 15–7
GPRS_DYNET_FAILURES, 12–37 IN_INTER_BSS_EQUIP_FAIL, 4–50
GPRS_DYNET_RES_REQS, 12–38 IN_INTER_BSS_HO, 4–50
IN_INTER_BSS_HO_CLEARED, 4–50
GPRS_DYNET_SWI_REQS, 12–39
IN_INTER_BSS_HO_SEIZE, 4–50
GPRS_MS_NEIGHBOR_STRONG, 12–40
IN_INTER_BSS_HO_SUC, 4–50
GPRS_PCH_AGCH_Q_LENGTH, 12–41
IN_INTER_CELL_HO_TO_IN_ZONE, 4–101, 4–102
GPRS_UL_ACT_TS, 17–35 IN_INTRA_BSS_EQUIP_FAIL, 4–51
GPRS_UL_BANDWIDTH_EFFICIENCY, 17–37 IN_INTRA_BSS_HO, 4–51
IN_INTRA_BSS_HO_CLEARED, 4–51
IN_INTRA_BSS_HO_LOSTMS, 4–51
H
IN_INTRA_BSS_HO_RETURN, 4–51
handover, 18–4 IN_INTRA_BSS_HO_SUC, 4–51
handover performance, 17–5 IN_INTRA_BSS_NC_ATMPT, 5–9
Handover successful, band reassignment, IN_INTRA_BSS_NC_SUC, 5–10
introduction, 18–41 INCOMING_HO_VOLUME, 17–39
HANDOVER_FAILURE_RATE, 16–10 INNER_TO_OUTER_ZONE, 4–101, 4–102
HANDOVER_SUCCESS_RATE, 16–11 inter–BSS handover
fail lost, 18–21
Handovers, ratio per call, 15–6 fail lost mobile, 18–22
HANDOVERS_PER_CALL, 15–6 fail recovered, 18–20
handover blocked, 18–19
health check, 17–5
handover successful, 18–18
HO_FAIL_NO_RESOURCES, 4–42 standard directed retry, external, 18–23

I–6 68P02901W56-L 14 Feb 2003
GSR6
Interband activity INTRA_ZONE, 4–101, 4–102

inter–BSS INV_EST_CAUSE_ON_RACH, 4–55
handover successful, 18–37
handover unsuccessful, 18–38 INVALID_FRAMES_RX, 11–11
invalid frequency supported, 18–39
intra–BSS K
handover successful, 18–34 key statistics, 1–4, 16–3, 16–4, 16–5
handover unsuccessful, 18–35 ATTEMPT_IMMED_ASSIGN_PROC, 16–6
unsuccessful , invalid frequency supported, call summary, 16–3
18–36 CELL_TCH_ALLOCATIONS, 16–8
CELL_TCH_ASSIGNMENTS, 16–9
Interband assignment, invalid frequency, 18–40 channel usage, 16–3
INTERBAND_ACTIVITY, 4–52 connection establishment, 16–4
HANDOVER_FAILURE_RATE, 16–10
INTERNAL_LOST, 17–40
HANDOVER_SUCCESS_RATE, 16–11
INTERNAL_RECOVERED, 17–41 loss summary, 16–4
MEAN_ARRIVAL_TIME_BETWEEN_CALLS,
INTERNAL_SUCCESS, 17–42
16–12
INTF_ON_IDLE, 6–11 MEAN_INTER_ARRIVAL_TIME, 16–13
MEAN_TCH_BUSY_TIME, 16–14
Intra–BSS
MTL_UTILISATION_RX, 16–15
congestion relief, 18–31
MTL_UTILISATION_TX, 16–16
directed retry, 18–32
RF_LOSS_RATE, 16–17
intra–BSS handover SDCCH_BLOCKING_RATE, 16–18
fail–lost, 18–26 SDCCH_MEAN_ARRIVAL_RATE, 16–19
fail–recovered, 18–25 SDCCH_MEAN_HOLDING_TIME, 16–20
handover blocked, 18–25 SDCCH_RF_LOSS_RATE, 16–21
handover successful, 18–24 SDCCH_TRAFFIC_CARRIED, 16–22
standard directed retry, internal, 18–27 SUCCESS_IMMED_ASSIGN_PROC, 16–23
Intra–BSS handovers, 15–8 SUCCESS_INTERNAL_HO, 16–24
TCH_BLOCKING_RATE, 16–25
intra–cell handover TCH_MEAN_ARRIVAL_RATE, 16–26
fail lost, 18–17 TCH_MEAN_HOLDING_TIME, 16–27
fail recovered, 18–17 TCH_RF_LOSS_RATE, 16–28
handover blocked, 18–16 TCH_TRAFFIC_CARRIED, 16–29
handover successful, 18–16 template, 16–5
INTRA_BSS_HO_CAUSE_SUC, 3–6 TOTAL_CALLS_KEY, 16–31
UNSUCCESS_INTERNAL_HO_NOREEST,
INTRA_BSS_HO_TO_ALL_HO, 15–8 16–32
INTRA_CELL_EQUIP_FAIL, 4–53 UNSUCCESS_INTERNAL_HO_REEST, 16–33
INTRA_CELL_HO, 4–53
INTRA_CELL_HO_ATMPT, 4–53 L
INTRA_CELL_HO_CLEARED, 4–53 L_ROUTING_SYNTAX, 13–5
INTRA_CELL_HO_FAIL_LOST_MS, 17–43 L_ROUTING_UNKNOWN, 13–6
INTRA_CELL_HO_FAIL_RECOVERED, 17–44 L_SCCP_MSGS, 13–7
INTRA_CELL_HO_LOSTMS, 4–53 L_SCCP_MSGS_RX, 13–8
INTRA_CELL_HO_REQ, 4–53 l_sccp_msgs_rx_0, 13–8
INTRA_CELL_HO_RETURN, 4–53 l_sccp_msgs_rx_2, 13–8
INTRA_CELL_HO_SUC, 4–53 L_SCCP_MSGS_TX, 13–9
INTRA_CELL_HO_SUCCESS_RATE, 17–45 l_sccp_msgs_tx_0, 13–9

14 Feb 2003 68P02901W56-L I–7
GSR6
l_sccp_msgs_tx_2, 13–9 LOC_FLW_ON_REQ_NORM, 4–70

L_SIF_SIO_RX_OPC, 13–10 LOC_FLW_ON_REQ_SMS, 4–70
L_SIF_SIO_TX_OPC, 13–11 Location updates, ratio per call, 15–10
L_SIF_SIO_TYPE, 13–12 LOCATION_SERVICES, 4–70
l_sif_sio_type, 13–12 LOCATION_UPDATE, 4–70
l_sif_sio_type_mtp, 13–12 LOCATION_UPDATE_FACTOR, 15–9
l_sif_sio_type_test, 13–12 LOCATION_UPDATES_TO_CALLS, 15–10
LAPD_CONGESTION, 11–12
LMTP_CHANGEBACK, 8–7 M
LMTP_CHANGEOVER, 8–8
MA_CMD_TO_MS_BLKD, 4–61
LMTP_CONGESTION, 8–37
MA_COMPLETE_TO_MS, 4–57
LMTP_LINK_INS, 8–10
MA_COMPLETE_TO_MSC, 4–58
LMTP_LINKFAIL, 8–11
MA_FAIL_FROM_MS, 4–59
LMTP_LOCAL_BUSY, 8–12
MA_REQ_FROM_MSC, 4–60
LMTP_LOCAL_MGT, 8–13
MA_REQ_FROM_MSC_FAIL, 3–7
LMTP_LOCAL_SL_CONGESTION, 8–9
MAX_TCH_BUSY, 17–46
LMTP_MGT_INHIBIT, 8–14
MEAN_ARRIVAL_TIME_BETWEEN_CALLS, 16–12
LMTP_MGT_UNINHIBIT, 8–15
MEAN_INTER_ARRIVAL_TIME, 16–13
LMTP_MSU_DISCARDED, 8–6
MEAN_TCH_BUSY_TIME, 16–14
LMTP_MSU_RX, 8–16
MEAN_TIME_BETWEEN_HOs, 17–47
LMTP_MSU_TX, 8–17
MMI BSC/BTS statistics
LMTP_NEG_ACKS, 8–18 ALLOC_SDCCH_FAIL, 14–3
LMTP_RE_TX, 8–19 ALLOC_TCH_FAIL, 14–3
HO_FAIL_NO_RESOURCES, 14–3
LMTP_REMOTE_MGT, 8–20 HO_REQ_MSC_FAIL, 14–3
LMTP_REMOTE_PROC, 8–21 MA_CMD_TO_MS_BLKD, 14–3
RF_LOSSES_TCH, 14–3
LMTP_RESTORATION, 8–22
MMI PCU statistic
LMTP_SIB_RX, 8–35 CELL_FLUSH_REQS, 14–3
LMTP_SIB_TX, 8–36 CHANNEL_REQS_REJ, 14–3
GBL_LINK_INS, 14–3
LMTP_SIF_SIO_RX, 8–23
GBL_PAGING_REQS, 14–3
LMTP_SIF_SIO_TX, 8–24 GBL_UNAVAILABLE, 14–3
LMTP_SL_ACK, 8–25 Monitoring faults, 1–14
LMTP_SL_ALIGNMENT, 8–26 MS_ACCESS_BY_TYPE, 4–62
LMTP_SL_CONGESTION, 8–27 MS_CLASS_1_10_REQ, 12–49
LMTP_SL_ERROR_RATE, 8–28 MS_CLASS_11_20_REQ, 12–50
LMTP_SL_FAIL, 8–29 MS_CLASS_21_29_REQ, 12–51
LMTP_SL_FIBR, 8–30 MA_CMD_TO_MS, 4–56
LMTP_START_RPO, 8–31 MS_TCH_USAGE_BY_TYPE, 4–63
LMTP_STOP_RPO, 8–32 MS_TCH_USAGE_BY_TYPE_PCS, 4–64
LMTP_SU_ERROR, 8–33 MSC functions, 18–4
LMTP_UNAVAILABLE, 8–34 MSC_OLVD_MSGS_RX, 3–8

I–8 68P02901W56-L 14 Feb 2003
GSR6
MSC_PAGING, 17–48 MTP_RE_TX, 10–20

MSU_DISCARDED, 10–7 MTP_REMOTE_MGT, 10–21
MTP_REMOTE_PROC, 10–22
MT_LCS_ON_SDCCH, 4–65
MTP_RESTORATION, 10–23
MTL
MTP_SIF_SIO_RX, 10–24
operator initiated outage, 18–44
transition scenarios, 18–45 MTP_SIF_SIO_TX, 10–25
MTP_SL_ACK, 10–26
MTL_UTILISATION_RX, 16–15
MTP_SL_ALIGNMENT, 10–27
MTL_UTILISATION_TX, 16–16 MTP_SL_CONGESTION, 10–28
MTP_CHANGEBACK, 10–8 MTP_SL_ERROR_RATE, 10–29
MTP_CHANGEOVER, 10–9 MTP_SL_FAIL, 10–30
MTP_SL_FIBR, 10–31
MTP_CONGESTION, 10–10
MTP_START_RPO, 10–32
MTP_LINK_INS, 10–11
MTP_STOP_RPO, 10–33
MTP_LINKFAIL, 10–12 MTP_SU_ERROR, 10–34
MTP_LOCAL_BUSY, 10–13 MTP_UNAVAILABLE, 10–35
MTP_LOCAL_MGT, 10–14
MTP_MGT_INHIBIT, 10–15
N
N2_EXPIRY, 11–13
MTP_MGT_UNINHIBIT, 10–16
Network health statistics, 1–4, 17–3
MTP_MSU_RX, 10–17 AIR_INTERFACE_BW_CS1, 17–7
AIR_INTERFACE_BW_CS2, 17–8
MTP_MSU_TX, 10–18
AIR_INTERFACE_BW_CS3, 17–9
MTP_NEG_ACKS, 10–19 AIR_INTERFACE_BW_CS4, 17–10
AIR_INTERFACE_PAGING, 17–11
ASSIGNMENT_SUCCESS_RATE, 17–12
CALL_SETUP_SUCCESS_RATE, 16–7, 17–13
CALL_SUCCESS_RATE, 17–14
CALL_VOLUME, 17–15
CELL_UPDATE, 17–16
DL_AIR_INTERFACE_BW_CS1, 17–25
DOWNLINK_TRAFFIC_VOLUME, 17–29
DROP_CALL_RATE, 17–30
GBL_AVAILABILITY, 17–31
GPRS performance, 17–4
GPRS_BW_USAGE_DL, 17–32

14 Feb 2003 68P02901W56-L I–9
GSR6
GPRS_BW_USAGE_UL, 17–33 network interface statistics

GPRS_DL_ACT_TS, 17–34 BSSLAP_ABORT_RCV, 9–16
GPRS_DL_BANDWIDTH_EFFICIENCY, 17–36 BSSLAP_ABORT_SENT, 9–15
GPRS_UL_ACT_TS, 17–35 BSSLAP_MS_POS_CMD, 9–17
GPRS_UL_BANDWIDTH_EFFICIENCY, 17–37 BSSLAP_MS_POS_RESP, 9–18
handover performance, 17–5 BSSLAP_REJ, 9–13
health check, 17–5 BSSLAP_RESET, 9–14
HO_PER_CALL, 17–38 BSSLAP_TA_REQ, 9–10
INCOMING_HO_VOLUME, 17–39 BSSLAP_TA_RESP, 9–11
INTERNAL_LOST, 17–40 BSSLAP_TOA_REQ, 9–12
INTERNAL_RECOVERED, 17–41 BSSMAP_CONLESS_INFO_RCV, 9–19
INTERNAL_SUCCESS, 17–42 BSSMAP_CONLESS_INFO_SENT, 9–20
INTRA_CELL_HO_FAIL_LOST_MS, 17–43 BSSMAP_PERF_LOC_ABORT_MSGS, 9–5
INTRA_CELL_HO_FAIL_RECOVERED, 17–44 BSSMAP_PERF_LOC_REQ_MSGS, 9–4
INTRA_CELL_HO_SUCCESS_RATE, 17–45 BSSMAP_PERF_LOC_RESP_MSGS, 9–6
MAX_TCH_BUSY, 17–46 BSSMAPLE_CONLESS_INFO_RCV, 9–21
MEAN_TIME_BETWEEN_HOs, 17–47 BSSMAPLE_CONLESS_INFO_SENT, 9–22
MSC_PAGING, 17–48 BSSMAPLE_PERF_LOC_ABORT_MSGS, 9–8
OUT_INTER_BSS_HO_FAIL_LOST_MS, 17–49 BSSMAPLE_PERF_LOC_REQ_MSGS, 9–7
OUT_INTER_BSS_HO_FAIL_RECOVERED, BSSMAPLE_PERF_LOC_RESP_MSGS, 9–9
17–50 L_ROUTING_SYNTAX, 13–5
OUT_INTER_BSS_HO_SUCCESS_RATE, 17–51 L_ROUTING_UNKNOWN, 13–6
OUT_INTER_CELL_HO_FAIL_LOST_MS, 17–52 L_SCCP_MSGS, 13–7
OUT_INTER_CELL_HO_FAIL_RECOVERED, L_SCCP_MSGS_RX, 13–8
17–53 L_SCCP_MSGS_TX, 13–9
OUT_INTER_CELL_HO_SUCCESS_RATE, L_SIF_SIO_RX_OPC, 13–10
17–54 L_SIF_SIO_TX_OPC, 13–11
OUTGOING_HO_VOLUME, 17–55 L_SIF_SIO_TYPE, 13–12
paging performance, 17–5 LMTP_MSU_DISCARDED, 8–6
PAGING_COMPRESSION_RATE, 17–56 LMTP_CHANGEBACK, 8–7
PAGING_OVERFLOW_RATE, 17–57 LMTP_CHANGEOVER, 8–8
PAGING_RESPONSE, 17–58 LMTP_CONGESTION_LOST_MSU, 8–5
PAGING_SUCCESS_RATE, 17–59 LMTP_LINK_INS, 8–10
PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLI LMTP_LINKFAIL, 8–11
NK, 17–60 LMTP_LOCAL_BUSY, 8–12
radio performance reports, 17–6 LMTP_LOCAL_MGT, 8–13
RANKING_FORMULA, 17–61 LMTP_LOCAL_SL_CONGESTION, 8–9
RF_ASSIGN_FAIL_RATE_LOST_MS, 17–62 LMTP_MGT_INHIBIT, 8–14
RF_ASSIGN_FAIL_RATE_RECOVERED, 17–63 LMTP_MGT_UNINHIBIT, 8–15
RF_ASSIGNMENT_SUCCESS_RATE, 17–64 LMTP_MSU_RX, 8–16
SDCCH congestion, 17–6 LMTP_MSU_TX, 8–17
SDCCH_ACCESSES, 17–65 LMTP_NEG_ACKS, 8–18
SDCCH_BLOCKING_RATE, 17–66 LMTP_RE_TX, 8–19
SDCCH_CONGESTION_TIME, 17–67 LMTP_REMOTE_MGT, 8–20
SDCCH_TRAFFIC_CARRIED, 17–68 LMTP_REMOTE_PROC, 8–21
TCH congestion, 17–6 LMTP_RESTORATION, 8–22
TCH_ACCESSES, 17–69 LMTP_SIF_SIO_RX, 8–23
TCH_CONGESTION_TIME, 17–70 LMTP_SIF_SIO_TX, 8–24
TCH_RF_LOSS_RATE, 17–71 LMTP_SL_ACK, 8–25
TCH_TRAFFIC_CARRIED, 17–72 LMTP_SL_ALIGNMENT, 8–26
UL_AIR_INTERFACE_BW_CS1, 17–73 LMTP_SL_CONGESTION, 8–27
UL_AIR_INTERFACE_BW_CS2, 17–74 LMTP_SL_ERROR_RATE, 8–28
UL_AIR_INTERFACE_BW_CS3, 17–75 LMTP_SL_FAIL, 8–29
UL_AIR_INTERFACE_BW_CS4, 17–76 LMTP_SL_FIBR, 8–30
UPLINK_PDTCH_BLOCKING_RATE, 17–77 LMTP_START_RPO, 8–31
UPLINK_TRAFFIC_VOLUME, 17–78 LMTP_STOP_RPO, 8–32

I–10 68P02901W56-L 14 Feb 2003
GSR6
LMTP_SU_ERROR, 8–33 OUT_INTRA_BSS_HO_REQ, 4–77

LMTP_UNAVAILABLE, 8–34 OUT_INTRA_BSS_HO_RETURN, 4–77
NO_PDTCH_AVAIL, 12–52 OUT_INTRA_BSS_HO_SUC, 4–77
NO_PDTCH_AVAIL_TIME, 12–53 OUTER_TO_INNER_ZONE, 4–101, 4–102
Normal distribution statistics, 1–9 OUTGOING_HO_VOLUME, 17–55
Bins, 1–9
Histogram, 1–9
Interval expiry, 1–9 P
Mean value, 1–9 PAGE_REQ_FROM_MSC, 4–79
NUM_EMERG_ACCESS, 4–66 PAGE_REQ_FROM_MSC_FAIL, 3–9
NUM_EMERG_REJECTED, 4–67 PAGE_REQ_FROM_SMLC_FAIL, 13–4
NUM_EMERG_TCH_KILL, 4–68 PAGE_RESPONSE, 4–70
NUM_EMERG_TERM_SDCCH, 4–69 PAGES_PER_CALL, 15–11
PAGES_PER_SECOND, 15–12
paging performance, 17–5
O PAGING_COMPRESSION_RATE, 17–56
OK_ACC_PROC, 4–70, 9–3 PAGING_OVERFLOW_RATE, 17–57
OK_ACC_PROC_SUC_RACH, 4–72 PAGING_RATE, 15–13
OUT_HO_CAUSE_ATMPT, 4–73 PAGING_REQS_CS, 4–80
OUT_HO_NC_CAUSE_ATMPT, 5–11 PAGING_REQS_PS, 4–80
PAGING_REQS_TOT, 4–80
OUT_HO_NC_SUC, 5–13
PAGING_REQUESTS, 4–80
OUT_INTER_BSS_EQUIP_FAIL, 4–75
PAGING_RESPONSE, 17–58
OUT_INTER_BSS_HO, 4–75
PAGING_SUCCESS_RATE, 17–59
OUT_INTER_BSS_HO_ATMPT, 4–75
PATH_BALANCE, 6–13
OUT_INTER_BSS_HO_CLEARED, 4–75 PCH_AGCH_Q_LENGTH, 4–81
OUT_INTER_BSS_HO_FAIL_LOST_MS, 17–49 PCH_Q_PAGE_DISCARD, 4–82
OUT_INTER_BSS_HO_FAIL_RECOVERED, 17–50 PCU statistics, 12–3
OUT_INTER_BSS_HO_LOSTMS, 4–75 PERCENTAGE_OF_ALL_TRAFFIC_IN_DOWNLINK,
17–60
OUT_INTER_BSS_HO_RETURN, 4–75
phantom RACHs, 4–55, 19–9
OUT_INTER_BSS_HO_SUC, 4–75 raw statistics affected, 19–11
OUT_INTER_BSS_HO_SUCCESS_RATE, 17–51 POWERBDGT, 4–73
OUT_INTER_BSS_REQ_TO_MSC, 4–75 PRP_LOAD, 12–54
OUT_INTER_CELL_FAIL_LOST_MS, 17–52
OUT_INTER_CELL_HO_FAIL_RECOVERED, 17–53 Q
OUT_INTER_CELL_HO_SUCCESS_RATE, 17–54 Quality of Service (QoS), 12–7, 12–9, 17–17, 17–18,
OUT_INTRA_BSS_EQUIP_FAIL, 4–77 17–19, 17–20, 17–21, 17–22, 17–23, 17–24,
17–29, 17–78
OUT_INTRA_BSS_HO, 4–77 Questions and answers, 19–12
OUT_INTRA_BSS_HO_ATMPT, 4–77
OUT_INTRA_BSS_HO_CLEARED, 4–77 R
OUT_INTRA_BSS_HO_LOSTMS, 4–77
radio performance reports, 17–6
OUT_INTRA_BSS_HO_PRI_BLK, 4–77 RF_ASSIGNMENT_SUCCESS_RATE, 17–64

14 Feb 2003 68P02901W56-L I–11
GSR6
RANKING_FORMULA, 17–61 SIF_SIO_TX_OPC, 3–16

Raw statistics, 1–3 SIF_SIO_TYPE, 3–17
RBER, 6–15 SL_CONGESTION, 10–38
RF_ASSIGN_FAIL_RATE_LOST_MS, 17–62 SL_STOP_CONGESTION, 10–39
RF_ASSIGN_FAIL_RATE_RECOVERED, 17–63 SMS, ratio per call, 15–14
RF_ASSIGNMENT_SUCCESS_RATE, 17–64 SMS_INIT_ON_SDCCH, 4–88
RF_LOSS_RATE, 16–17 SMS_INIT_ON_TCH, 4–89
RF_LOSSES_SD, 4–83 SMS_NO_BCAST_MSG, 4–90
RF_LOSSES_TCH, 4–84, 6–16 SMS_TO_CALL_RATIO, 15–14
ROC, 6–17 stat_interval command, 2–10, 2–11
ROUTING_SYNTAX, 3–10 stat_mode command, 2–4
ROUTING_UNKNOWN, 3–11 SUCCESS_IMMED_ASSIGN_PROC, 16–23
RSL , link scenarios, 18–43 SUCCESS_INTERNAL_HO, 16–24
S T
SABM_TX, 11–14 TCH congestion, 17–6
SCCP_MSGS, 3–12 TCH_ACCESSES, 17–69
SCCP_MSGS_RX, 3–13 TCH_ASSIGN_TO_INNER_ZONE, 4–101, 4–102
SCCP_MSGS_TX, 3–14 TCH_BLOCKING_RATE, 16–25

TCH_CONG_INNER_ZONE, 4–92
SDCCH congestion, 17–6
TCH_CONGESTION, 4–91
SDCCH_ACCESSES, 17–65
TCH_CONGESTION_TIME, 17–70
SDCCH_BLOCKING_RATE, 16–18, 17–66
TCH_DELAY, 4–93
SDCCH_CONGESTION, 4–85
TCH_MEAN_ARRIVAL_RATE, 16–26
SDCCH_CONGESTION_TIME, 17–67
TCH_MEAN_HOLDING_TIME, 16–27
SDCCH_MEAN_ARRIVAL_RATE, 16–19
TCH_Q_LENGTH, 4–94
SDCCH_MEAN_HOLDING_TIME, 16–20
TCH_Q_REMOVED, 4–95
SDCCH_RF_LOSS_RATE, 16–21
TCH_RF_LOSS_RATE, 16–28, 17–71
SDCCH_TRAFFIC_CARRIED, 16–22, 17–68
TCH_TRAFFIC_CARRIED, 16–29, 17–72
SECOND_ASSIGN_ATMPT, 4–86
TCH_USAGE, 4–96
SECOND_ASSIGN_SUC, 4–87
TCH_USAGE_EXT_RANGE, 4–98
Setting a statistic interval, 2–10
TCH_USAGE_INNER_ZONE, 4–99
Setting a threshold, 2–13
counter statistics, 2–13 Throughput statistics, 12–5, 18–58
Setting statistic properties, 2–13 TOTAL_CALLS, 4–100
Setting a threshold, 2–13 TOTAL_CALLS_KEY, 16–31
short message service
mobile originated, 18–30
mobile terminated, 18–30 U
SIB_RX, 10–36 U_BER, 6–18
SIB_TX, 10–37 UL_AIR_INTERFACE_BW_CS1, 17–73
SIF_SIO_RX_OPC, 3–15 UL_AIR_INTERFACE_BW_CS2, 17–74

I–12 68P02901W56-L 14 Feb 2003
GSR6
UL_AIR_INTERFACE_BW_CS3, 17–75 UPQUAL, 4–73

UL_AIR_INTERFACE_BW_CS4, 17–76
UL_BUSY_PDTCH, 12–56
W
UL_PDTCH_CONGESTION, 12–57
Weighted distribution statistics, 1–10
UL_PDTCH_Q_LENGTH, 12–58
Bins, 1–10
UL_PDTCH_SEIZURE, 12–59 Histogram, 1–10
UNSUCCESS_INTERNAL_HO_NOREEST, 16–32 Interval expiry, 1–10
Mean value, 1–10
UNSUCCESS_INTERNAL_HO_REEST, 16–33 Wraparound to next day, 1–10
UPINTERF, 4–73
UPLEVEL, 4–73
UPLINK_PATH_LOSS, 6–19
Z
UPLINK_PDTCH_BLOCKING_RATE, 17–77 ZONE_CHANGE_ATMPT, 4–101
UPLINK_TRAFFIC_VOLUME, 17–78 ZONE_CHANGE_SUC, 4–102

14 Feb 2003 68P02901W56-L I–13
GSR6

I–14 68P02901W56-L 14 Feb 2003

68p02901w56-L-Uk GSM Statistics Application

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

68p02901w56-L-Uk GSM Statistics Application

Uploaded by

Copyright:

Available Formats

CHAPTER 1 CHAPTER 2 CHAPTER 3 CHAPTER 4 CHAPTER 5

E Motorola 1993 - 2003

Maintenance Information: GSM Statistics Application

Copyrights, notices and trademarks

and MOTOROLA are registered trademarks of Motorola Inc.

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Displaying enabled statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–6

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Assignment to TCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–13

Maintenance Information: GSM Statistics Application

Interband assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–40

Maintenance Information: GSM Statistics Application

Figure 1-1 Histogram of a normal distribution statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9

Maintenance Information: GSM Statistics Application

Figure 18-36 Successful intra–BSS handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18–34

Maintenance Information: GSM Statistics Application

Table 2-1 Counter statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Issue status of this manual

Manual Date of Remarks

Maintenance Information: GSM Statistics Application

Resolution of Service Requests

Service GMR Remarks

Maintenance Information: GSM Statistics Application

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

About this manual

Maintenance Information: GSM Statistics Application

The tags are positioned in text as follows:

New and amended feature information Tag position in text

Maintenance Information: GSM Statistics Application

Special key sequences

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

Maintenance Information: GSM Statistics Application

Reporting safety issues

Maintenance Information: GSM Statistics Application

Warnings and cautions

Example and format

Failure to comply with warnings

Example and format

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Potentially hazardous voltage

Maintenance Information: GSM Statistics Application

When dismantling heavy assemblies, or removing or replacing equipment, the competent

Maintenance Information: GSM Statistics Application

Maintenance Information: GSM Statistics Application

Devices sensitive to static

Special handling techniques