Net 03

CHAPTER 1
CHAPTER 2
CHAPTER 3
CHAPTER 4
CHAPTER 5
CHAPTER 6
CHAPTER 7
CHAPTER 8
APPENDIX A
APPENDIX B
BSS Subsystem Planning
NET03
Issue 11 Revision 0 Training Manual
FOR TRAINING PURPOSES ONLY
Issue 11 Revision 0 FOR TRAINING PURPOSES ONLY
Positin mark for TED spine
Training Manual Issue 11 Revision 0 NET03 Training Manual
NET03
Issue 11 Revision 0
NET03 BSS Subsystem Planning
E Motorola 1993, 1994, 1995, 1996, 1997, 1998, 1999 All Rights Reserved Printed in the U.K.
NET03: BSS Subsystem Planning

EMOTOROLA LTD. 2001
Issue 11 Revision 0
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 trademarks of Motorola Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Tandem, Integrity, Integrity S2, and Non-Stop-UX are trademarks of Tandem Computers Incorporated. X Window System, X and X11 are trademarks of the Massachusetts Institute of Technology. Looking Glass is a registered trademark of Visix Software Ltd. OSF/Motif is a trademark of the Open Software Foundation. Ethernet is a trademark of the Xerox Corporation. Wingz is a trademark and INFORMIX is a registered trademark of Informix Software Ltd. SUN, SPARC, and SPARCStation are trademarks of Sun Microsystems Computer Corporation. IBM is a registered trademark of International Business Machines Corporation. HP is a registered trademark of Hewlett Packard Inc.

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Important notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cross references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . First aid in case of electric shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Artificial respiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Burns treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reporting safety issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . High voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Laser radiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lifting equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Do not ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Toxic material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Human exposure to radio frequency energy (PCS1900 only) . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum permitted exposure ceilings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power density measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Beryllium health and safety precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inhalation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skin contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eye contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disposal methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product life cycle implications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Caution labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Specific cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre optics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Static discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 1 1 1 2 2 3 3 3 3 4 4 4 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 9 10 10 10 11 11 11 11 12 12 12 12 12 13 13 13 13 13 13

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special handling techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorola GSM manual set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Generic manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tandem OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scaleable OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Category number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Catalogue number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14 14 14 15 15 15 15 16 16 16 17 17 17
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Performance Management (PM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder Base Site Link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Software Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Radio Subsystem (RSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Configuration and FM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS A-bis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Detection and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part Layer 3 (MTPL3)/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ladder Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 14 14 14 16 18 18 18 110 110 110 112 112 112 114 116 116 116 118 120 122 122 122 122 122 124 124 126
Chapter 2 Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of statistical data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NET03: BSS Subsystem Planning
iv
i
21 21 22 24 26
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Counter Array Statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter array example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gauge statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Durational Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Distribution Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted Distribution Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28 28 210 210 212 214 216 218 220 222 224
Chapter 3 Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OML, RSL and XBL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The X.25 and LAPD protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 and LAPD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Allocation of Switch (RXCDRBSC) Circuits (DARBC) Feature . . . . . . . . . . . ATER_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATER_PREEMPT_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The C7 protocol - MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling Units (SUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The C7 protocol SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP performance and utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Busy CICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 32 32 32 34 310 312 314 320 326 326 326 330 330 330 332 338 344 350 352 354 356
Chapter 4 Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Establishment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC BTS Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 42 44 414 416 420

EMOTOROLA LTD. 2001
Issue 11 Revision 0
TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment request queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry cont. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONGEST_ STAND_HO_ ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-imperative handover rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion relief handover retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ALLOC_TCH_ FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Bit Error Ratio (BER) Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interpreting the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit Power Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classmark Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Idle Interference Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Available time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMS Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast (CB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FER (Frame Erasure Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Residual Bit Error Rate (RBER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
422 422 424 426 426 426 426 426 430 432 436 436 438 438 440 442 442 446 448 448 450 450 450 452 454 456 458 460
Chapter 5 Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-cell handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal/External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IntraCell Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful Intra-BSS Handover Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NET03: BSS Subsystem Planning
vi
i
51 51 52 52 52 52 52 54 56 510 514 516 520 522
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Outgoing Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bad Handover Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outgoing External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking Handover Failures Due to no Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
528 530 532 534 542 546 548 550 552 552 553
Chapter 6 Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Enabled Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Bin Ranges for Distribution Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Statistical Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the interval timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note: Clearing statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 62 64 66 66 66 68 610 610 610 612
Chapter 7 Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH mean holding time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH mean arrival rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH mean holding time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH mean arrival rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH congestion (for call setup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean TCH busy time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover failure rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH assignment success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total_calls key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful internal handovers, per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsuccessful internal handovers with successful re-establishment, per BSC . . Unsuccessful internal handovers with successful re-establishment, per cell . . . Unsuccessful internal handovers without re-establshment, per BSC . . . . . . . . . . Unsuccessful internal handovers without re-establishment, per cell . . . . . . . . . .
i
71 71 72 74 76 76 76 78 78 710 710 710 712 712 712 714 714 716 718 718 718 720 720 722 722

EMOTOROLA LTD. 2001
vii
Issue 11 Revision 0
RF Loss Summary Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell TCH assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean inter arrival time per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attempted immediate assignment procedures, per BSC . . . . . . . . . . . . . . . . . . . . Attempted immediate assignment procedures, per cell . . . . . . . . . . . . . . . . . . . . . Successful immediate assignment procedures, per BSC . . . . . . . . . . . . . . . . . . . . Successful immediate assignment procedure, per cell . . . . . . . . . . . . . . . . . . . . . . Mean arrival time between calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
724 724 724 726 726 728 728 728 728 730 730 732
Chapter 8 Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO_SDCCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO_TCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MEAN_TIME_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INCOMING_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASSIGN_FAILURE_RATE_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASSIGN_FAILURE_RATE_RECOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_FAILURE_RATE_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_FAILURE_RATE_RECOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 84 86 88 810 810 812 812 814 814 816 816 818 818 820 820 822 822 826 826 828 828 830 830 832 832 834 834 836 836
Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App A i Appendix B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B i

GSR3 New Raw Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B ii NET03: BSS Subsystem Planning
viii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
GSR3 New Key Statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B ii GSR3 Statistic Name Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B iii
Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos i

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos ii A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos iii B ......................................................................... Glos v
C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos vii D ......................................................................... Glos x
E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xiii F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xv G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xvii H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xviii I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xix K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxi L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxii M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxiv N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxvii O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxviii P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxix Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxxi R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxxii S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxxiv T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxxvii U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xxxix V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xl W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xli X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos xlii
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call Establishment Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B i

EMOTOROLA LTD. 2001
ix
Issue 11 Revision 0

x
EMOTOROLA LTD. 2001
Issue 11 Revision 0
General information
General information
Important notice
If this manual was obtained when you attended 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 Global System for Mobile Communications (GSM) Technical Education manuals are intended to support the delivery of Technical Education only and are not intended to replace the use of Customer Product Documentation. WARNING Failure to comply with Motorolas 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

EMOTOROLA LTD. 2001
General information
Issue 11 Revision 0
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.
Text conventions
The following conventions are used in the Motorola GSM 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 ALT-f | CR or RETURN Press the Control and c keys at the same time. Press the Alt and f keys at the same time. Press the pipe symbol key. Press the Return (Enter) key. The Return key is identified with the symbol on both the X terminal and the SPARCstation keyboards. The SPARCstation keyboard Return key is also identified with the word Return.

2
EMOTOROLA LTD. 2001
Issue 11 Revision 0
First aid in case of electric shock
First aid in case of electric shock

Warning
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.
Artificial respiration
In the event of an electric shock it may be necessary to carry out artificial respiration. Send for medical assistance immediately.
Burns treatment
If the patient is also suffering from burns, then, without hindrance to artificial respiration, carry out the following: 1. 2. 3. Do not attempt to remove clothing adhering to the burn. If help is available, or as soon as artificial respiration is no longer required, cover the wound with a dry dressing. Do not apply oil or grease in any form.

EMOTOROLA LTD. 2001
Reporting safety issues
Issue 11 Revision 0
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. 2. 3. 4. Make the equipment concerned safe, for example, by removing power. Make no further attempt to tamper with the equipment. Report the problem directly to GSM MCSC +44 (0)1793 430040 (telephone) and follow up with a written report by fax +44 (0)1793 430987 (fax). Collect evidence from the equipment under the guidance of the MCSC.

4
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Warnings and cautions
Warnings and cautions

Introduction
The following describes how warnings and cautions are used in this manual and in all manuals of the Motorola GSM manual set.
Warnings
Definition
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 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.
Cautions
Definition
A caution means that there is a possibility of damage to systems, 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 calibration due date when testing Motorola base stations.

EMOTOROLA LTD. 2001
General warnings
Issue 11 Revision 0
General warnings
Introduction
Observe the following warnings during all phases of operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these warnings, or with specific warnings elsewhere in the Motorola GSM manuals, violates safety standards of design, manufacture and intended use of the equipment. Motorola assumes no liability for the customers failure to comply with these requirements.
Warning labels
Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Warning labels must not be removed, painted over or obscured in any way.
Specific warnings
Warnings particularly applicable to the equipment are positioned on the equipment and 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 warnings given in text, on the illustrations and on the equipment.
High voltage
Certain Motorola equipment operates from a dangerous high voltage of 230 V ac single phase or 415 V ac three phase mains which is potentially lethal. Therefore, the areas where the ac mains power is present must not be approached until the warnings and cautions in the text and on the equipment have been complied with. To achieve isolation of the equipment from the ac supply, the mains input isolator must be set to off and locked. Within the United Kingdom (UK) regard must be paid to the requirements of the Electricity at Work Regulations 1989. There may also be specific country legislation which need to be complied with, depending on where the equipment is used.
RF radiation
High RF potentials and electromagnetic fields are present in the base station 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. Refer to the following standards: S S ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz. CENELEC 95 ENV 50166-2, Human Exposure to Electromagnetic Fields High Frequency (10kHz to 300GHz).
Laser radiation
Do not look directly into fibre optic cables or optical data in/out connectors. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors. NET03: BSS Subsystem Planning
6
EMOTOROLA LTD. 2001
Issue 11 Revision 0
General warnings
Lifting equipment
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.
Do not ...
... substitute parts or modify equipment. Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of equipment. Contact Motorola if in doubt to ensure that safety features are maintained.
Battery supplies
Do not wear earth straps when working with standby battery supplies.
Toxic material
Certain Motorola equipment incorporates components containing the highly toxic material Beryllium or its oxide Beryllia or both. These materials are especially hazardous if: S S S Beryllium materials are absorbed into the body tissues through the skin, mouth, or a wound. The dust created by breakage of Beryllia is inhaled. Toxic fumes are inhaled from Beryllium or Beryllia involved in a fire.
See the Beryllium health and safety precautions section for further information.

EMOTOROLA LTD. 2001
Human exposure to radio frequency energy (PCS1900 only)
Issue 11 Revision 0

Introduction
This equipment is designed to generate and radiate radio frequency (RF) energy. It should be installed and maintained only by trained technicians. Licensees of the Federal Communications Commission (FCC) using this equipment are responsible for insuring that its installation and operation comply with FCC regulations designed to limit human exposure to RF radiation in accordance with the American National Standards Institute IEEE Standard C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3kHz to 300GHz.
Definitions
This standard establishes two sets of maximum permitted exposure limits, one for controlled environments and another, that allows less exposure, for uncontrolled environments. These terms are defined by the standard, as follows:
Uncontrolled environment
Uncontrolled environments are locations where there is the exposure of individuals who have no knowledge or control of their exposure. The exposures may occur in living quarters or workplaces where there are no expectations that the exposure levels may exceed those shown for uncontrolled environments in the table of maximum permitted exposure ceilings.
Controlled environment
Controlled environments are locations where there is exposure that may be incurred by persons who are aware of the potential for exposure as a concomitant of employment, by other cognizant persons, or as the incidental result of transient passage through areas where analysis shows the exposure levels may be above those shown for uncontrolled environments but do not exceed the values shown for controlled environments in the table of maximum permitted exposure ceilings.
Maximum permitted exposures

The maximum permitted exposures prescribed by the standard are set in terms of different parameters of effects, depending on the frequency generated by the equipment in question. At the frequency range of this Personal Communication System equipment, 1930-1970MHz, the maximum permitted exposure levels are set in terms of power density, whose definition and relationship to electric field and magnetic field strengths are described by the standard as follows:
Power density (S)

Power per unit area normal to the direction of propagation, usually expressed in units of watts per square metre (W/m2) or, for convenience, units such as milliwatts per square centimetre (mW/cm2). For plane waves, power density, electric field strength (E) and magnetic field strength (H) are related by the impedance of free space, 377 ohms. In particular,
2 S + E + 377 377
H2
where E and H are expressed in units of V/m and A/m, respectively, and S in units of W/m 2. Although many survey instruments indicate power density units, the actual quantities measured are E or E2 or H or H2. NET03: BSS Subsystem Planning
8
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Maximum permitted exposure ceilings

Within the frequency range, the maximum permitted exposure ceiling for uncontrolled environments is a power density (mW/cm2) that equals f/1500, where f is the frequency expressed in MHz, and measurements are averaged over a period of 30 minutes. The maximum permitted exposure ceiling for controlled environments, also expressed in mW/cm 2, is f/300 where measurements are averaged over 6 minutes. Applying these principles to the minimum and maximum frequencies for which this equipment is intended to be used yields the following maximum permitted exposure levels: Uncontrolled Environment 1930MHz Ceiling 1970MHz Controlled Environment 1930MHz 1970MHz
1.287mW/cm 2 1.313mW/cm 2 6.433mW/cm 2 6.567mW/cm 2
If you plan to operate the equipment at more than one frequency, compliance should be assured at the frequency which produces the lowest exposure ceiling (among the frequencies at which operation will occur). Licensees must be able to certify to the FCC that their facilities meet the above ceilings. Some lower power PCS devices, 100 milliwatts or less, are excluded from demonstrating compliance, but this equipment operates at power levels orders of magnitude higher, and the exclusion is not applicable. Whether a given installation meets the maximum permitted exposure ceilings depends, in part, upon antenna type, antenna placement and the output power to which this equipment is adjusted. The following example sets forth the distances from the antenna to which access should be prevented in order to comply with the uncontrolled and controlled environment exposure limits as set forth in the ANSI IEEE standards and computed above.

EMOTOROLA LTD. 2001
Issue 11 Revision 0
Example calculation
For a base station with the following characteristics, what is the minimum distance from the antenna necessary to meet the requirements of an uncontrolled environment? Transmit frequency Base station cabinet output power, P Antenna feeder cable loss, CL Antenna input power Pin Antenna gain, G Using the following relationship: G + 4pr W Pin
2
1930MHz +39.0 dBm (8 watts) 2.0dB PCL = +39.02.0 = +37.0dB (5watts) 16.4dBi (43.65)
Where W is the maximum permissible power density in W/m2 and r is the safe distance from the antenna in metres, the desired distance can be calculated as follows: r+ GPin + 4pW 43.65 5 + 1.16m 4p 12.87
where W = 12.87 W/m2 was obtained from table listed above and converting from mW/cm 2 to W/m2. NOTE The above result applies only in the direction of maximum radiation of the antenna. Actual installations may employ antennas that have defined radiation patterns and gains that differ from the example set forth above. The distances calculated can vary depending on the actual antenna pattern and gain.
Power density measurements

While installation calculations such as the above are useful and essential in planning and design, validation that the operating facility using this equipment actually complies will require making power density measurements. For information on measuring RF fields for determining compliance with ANSI IEEE C95.1-1991, see IEEE Recommended Practice for the Measure of Potentially Hazardous Electromagnetic Fields - RF and Microwave, IEEE Std C95.3-1991. Copies of IEEE C95.1-1991 and IEEE C95.3-1991 may be purchased from the Institute of Electrical and Electronics Engineers, Inc., Attn: Publication Sales, 445 Hoes Lane, P.O. Box 1331, Piscattaway, NJ 08855-1331, (800) 678-IEEE or from ANSI, (212) 642-4900. Persons responsible for installation of this equipment are urged to consult these standards in determining whether a given installation complies with the applicable limits.
Other equipment
Whether a given installation meets ANSI standards for human exposure to radio frequency radiation may depend not only on this equipment but also on whether the environments being assessed are being affected by radio frequency fields from other equipment, the effects of which may add to the level of exposure. Accordingly, the overall exposure may be affected by radio frequency generating facilities that exist at the time the licensees equipment is being installed or even by equipment installed later. Therefore, the effects of any such facilities must be considered in site selection and in determining whether a particular installation meets the FCC requirements. NET03: BSS Subsystem Planning
10
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Beryllium health and safety precautions

Introduction
Beryllium (Be), is a hard silver/white metal. It is stable in air, but burns brilliantly in Oxygen. With the exception of the naturally occurring Beryl ore (Beryllium Silicate), all Beryllium compounds and Beryllium metal are potentially highly toxic.
Health issues
Beryllium Oxide is used within some components as an electrical insulator. Captive within the component it presents no health risk whatsoever. However, if the component should be broken open and the Beryllium Oxide, which is in the form of dust, released, there exists the potential for harm.
Inhalation
Inhalation of Beryllium Oxide can lead to a condition known as Berylliosis, the symptoms of Berylliosis are similar to Pneumonia and may be identified by all or any of the following: Mild poisoning causes fever, shortness of breath, and a cough that produces yellow/green sputum, or occasionally bloodstained sputum. Inflammation of the mucous membranes of the nose, throat, and chest with discomfort, possibly pain, and difficulty with swallowing and breathing. Severe poisoning causes chest pain and wheezing which may progress to severe shortness of breath due to congestion of the lungs. Incubation period for lung symptoms is 220 days. Exposure to moderately high concentrations of Beryllium in air may produce a very serious condition of the lungs. The injured person may become blue, feverish with rapid breathing and raised pulse rate. Recovery is usual but may take several months. There have been deaths in the acute stage. Chronic response. This condition is more truly a general one although the lungs are mainly affected. There may be lesions in the kidneys and the skin. Certain features support the view that the condition is allergic. There is no relationship between the degree of exposure and the severity of response and there is usually a time lag of up to 10 years between exposure and the onset of the illness. Both sexes are equally susceptible. The onset of the illness is insidious but only a small number of exposed persons develop this reaction.
First aid
Seek immediate medical assistance. The casualty should be removed immediately from the exposure area and placed in a fresh air environment with breathing supported with Oxygen where required. Any contaminated clothing should be removed. The casualty should be kept warm and at rest until medical aid arrives.

EMOTOROLA LTD. 2001
11
Issue 11 Revision 0
Skin contact
Possible irritation and redness at the contact area. Persistent itching and blister formations can occur which usually resolve on removal from exposure.
First aid
Wash area thoroughly with soap and water. If skin is broken seek immediate medical assistance.
Eye contact
May cause severe irritation, redness and swelling of eyelid(s) and inflammation of the mucous membranes of the eyes.
First aid
Flush eyes with running water for at least 15 minutes. Seek medical assistance as soon as possible.
Handling procedures
Removal of components from printed circuit boards (PCBs) is to take place only at Motorola approved repair centres. The removal station will be equipped with extraction equipment and all other protective equipment necessary for the safe removal of components containing Beryllium Oxide. If during removal a component is accidently opened, the Beryllium Oxide dust is to be wetted into a paste and put into a container with a spatula or similar tool. The spatula/tool used to collect the paste is also to be placed in the container. The container is then to be sealed and labelled. A suitable respirator is to be worn at all times during this operation. Components which are successfully removed are to be placed in a separate bag, sealed and labelled.
Disposal methods
Beryllium Oxide or components containing Beryllium Oxide are to be treated as hazardous waste. All components must be removed where possible from boards and put into sealed bags labelled Beryllium Oxide components. These bags must be given to the safety and environmental adviser for disposal. Under no circumstances are boards or components containing Beryllium Oxide to be put into the general waste skips or incinerated.
Product life cycle implications

Motorola GSM and analogue equipment includes components containing Beryllium Oxide (identified in text as appropriate and indicated by warning labels on the equipment). These components require specific disposal measures as indicated in the preceding (Disposal methods) paragraph. Motorola will arrange for the disposal of all such hazardous waste as part of its Total Customer Satisfaction philosophy and will arrange for the most environmentally friendly disposal available at that time. NET03: BSS Subsystem Planning
12
EMOTOROLA LTD. 2001
Issue 11 Revision 0
General cautions
General cautions
Introduction
Observe the following cautions during operation, installation and maintenance of the equipment described in the Motorola GSM manuals. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola GSM manuals may result in damage to the equipment. Motorola assumes no liability for the customers 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
The bending radius of all fibre optic cables must not be less than 30 mm.
Static discharge
Motorola equipment contains CMOS devices that are vulnerable to static discharge. Although the damage caused by static discharge may not be immediately apparent, CMOS devices may be damaged in the long term due to static discharge caused by mishandling. Wear an approved earth strap when adjusting or handling digital boards. See Devices sensitive to static for further information.

EMOTOROLA LTD. 2001
13
Devices sensitive to static
Issue 11 Revision 0
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 S S S S S Always wear an earth strap which must be connected to the electrostatic point (ESP) on the equipment. Leave the short circuit on the leads until the last moment. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. Do not wear outer clothing made of nylon or similar man made material. A cotton overall is preferable. If possible work on an earthed metal surface. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. All metal tools should be used and when not in use they should be placed on an earthed surface. Take care when removing components connected to electrostatic sensitive devices. These components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to electrostatic damage. However PCBs should be handled with care, preferably by their edges and not by their tracks and pins, they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench.

14
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Motorola GSM manual set

Introduction
The following manuals provide the information needed to operate, install and maintain the Motorola GSM equipment.
Generic manuals
The following are the generic manuals in the GSM manual set, these manuals are release dependent:
Category number
GSM-100-101 GSM-100-201 GSM-100-311 GSM-100-313 GSM-100-320 GSM-100-321 GSM-100-403 GSM-100-423 GSM-100-501 GSM-100-521 GSM-100-523 GSM-100-503 GSM-100-721
Name
System Information: General Technical Description: OMC in a GSM System Technical Description: BSS Implementation Technical Description: BSS Command Reference Installation & Configuration: GSM System Configuration Installation & Configuration: BSS Optimization Maintenance Information: Alarm Handling at the OMC Maintenance Information: Device State Transitions Maintenance Information: BSS Field Troubleshooting Maintenance Information: GSM Statistics Application Software Release Notes: BSS/RXCDR
Catalogue number
68P02901W01 68P02901W31 68P02901W36 68P02901W23 68P02901W17 68P02901W43 68P02901W26 68P02901W57 68P02901W51 68P02901W56 68P02901W72
Operating Information: GSM System Operation 68P02901W14 Technical Description: OMC Database Schema 68P02901W34
Tandem OMC
The following Tandem OMC manuals are part of the GSM manual set for systems deploying Tandem S300 and 1475:
Category number
GSM-100-202 GSM-100-712
Name
Operating Information: OMC System Administration Software Release Notes: OMC System
Catalogue number
68P02901W13 68P02901W71

EMOTOROLA LTD. 2001
15
Issue 11 Revision 0
Scaleable OMC
The following Scaleable OMC manuals replace the equivalent Tandem OMC manuals in the GSM manual set:
Category number
GSM-100-202 GSM-100-413 GSM-100-712
Name
Catalogue number
Operating Information: Scaleable OMC System 68P02901W19 Administration Installation & Configuration: Scaleable OMC Clean Install Software Release Notes: Scaleable OMC System 68P02901W47 68P02901W74
Related manuals
The following are related Motorola GSM manuals:
Category number
GSM-001-103 GSM-002-103 GSM-005-103 GSM-008-403
Name
System Information: BSS Equipment Planning System Information: DataGen System Information: Advance Operational Impact Installation & Configuration: Expert Adviser
Catalogue number
68P02900W21 68P02900W22 68P02900W25 68P02900W36
Service manuals
The following are the service manuals in the GSM manual set, 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:
Category number
GSM-100-020 GSM-100-030 GSM-105-020 GSM-106-020 GSM-201-020 GSM-202-020 GSM-101-SERIES GSM-103-SERIES GSM-102-SERIES GSM-200-SERIES
Name
Service Manual: BTS Service Manual: BSC/RXCDR Service Manual: M-Cell2 Service Manual: M-Cell6 Service Manual: M-Cellcity Service Manual: M-Cellaccess ExCell4 Documentation Set ExCell6 Documentation Set TopCell Documentation Set M-Cellmicro Documentation Set
Catalogue number
68P02901W37 68P02901W38 68P02901W75 68P02901W85 68P02901W95 68P02901W65 68P02900W50 68P02900W70 68P02901W80 68P02901W90

16
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Category number
The category number is used to identify the type and level of a manual. For example, manuals with the category number GSM-100-2xx contain operating information.
Catalogue number
The Motorola 68P 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 catalogue number. Remember, specify the manual issue required by quoting the correct suffix letter.

EMOTOROLA LTD. 2001
17
Issue 11 Revision 0

18
EMOTOROLA LTD. 2001
Chapter 1
Introduction

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Raw statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Performance Management (PM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Link (MTL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transcoder Base Site Link (XBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations and Maintenance Link (OML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast Link (CBL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Signalling Link (RSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Software Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Radio Subsystem (RSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Configuration and FM Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RSS A-bis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Detection and Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Processing (CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Transfer Part Layer 3 (MTPL3)/SCCP Preprocessor . . . . . . . . . . . . . . . . . . . . SCCP State Machine (SSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connectionless Manager (CLM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Manager (SM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Resource State Machine (RRSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Channel Interface (RCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Resource Manager (CRM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ladder Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
11 11 14 14 14 16 18 18 18 110 110 110 112 112 112 114 116 116 116 118 120 122 122 122 122 122 124 124 126

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
Introduction
Objectives
On completion of this chapter the student will be able to: S S S Identify the five signalling links within the BSS subsystem infrastructure, indicate their purpose, bandwidth and Time Slot (TS) allocations. Understand the interaction of the Central Statistics Process (CSP) with the Distributed Statistics Function (DSF). Revise their understanding of the main software entities within the BSS and also the location of these processes.

EMOTOROLA LTD. 2001
11
Introduction
Issue 11 Revision 0
The performance of a network may be monitored and measured. By monitoring the network performance an indication of the service provided to the subscriber may be measured. Statistical information is gathered from the network components, this information is used to monitor and measure the network performance. Monitoring statistical information provides a health check for the network. Problems can therefore be anticipated and prevented. This information can also be of assistance when a network is to be expanded or optimized. Measuring the performance of the network can supply important information regarding the quality of service provided to the subscriber (e.g. call set-up time). The statistical information may be gathered over periods of time to gain an insight into trends on the network (e.g. the busiest call periods). Motorola Global System for Mobile communication (GSM) Base Station System (BSS) equipment generates statistical information which may be used to measure the performance of the network. The statistics are monitored at the Operations and Maintenance Centre (OMC). During this course the origin of all the statistics output by the BSS will be investigated and methods for measuring quality of service will be established. Methods of setting up and displaying statistical information will also be covered.

12
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
Statistical information a health check" for the network

EMOTOROLA LTD. 2001
13
Introduction to Statistics
Issue 11 Revision 0
There are two categories of statistics which may be used to monitor network performance. These are raw statistics and key statistics. There are over 100 raw statistics in all, too many to keep your eye on! The key statistics provide a more general picture of how the network is operating. There are only 16 key statistics and therefore they are much easier to reliably monitor. If operators notice a problem with the network when looking at the key statistics they can then start to study the raw statistics to get a more detailed view of the problem. The raw statistics and key statistics are described below:
Raw statistics
The raw statistics produced by the Motorola BSS equipment are subcategorized into three groups: call statistics, interface statistics and processor utilization statistics. A description of these statistics is provided below. S Call statistics Call statistics are calculated during Call Processing (CP). Call assignments and failures are monitored along with handover assignments and failures. Also there are many features within the BSS which are monitored by statistics. S Interface statistics Interface statistics relate to activities on the terrestrial interfaces. These interfaces connect the network components (e.g. Mobile services Switching Centre (MSC) to BSS). Messages travelling over the interfaces are counted and signalling link outages are recorded. S Processor utilization statistics Processor utilization statistics calculate the percentage to which the Generic Processor board (GPROC) is being utilized.
Key statistics
The Operations and Maintenance Centre (OMC) uses a selection of raw call statistics described above to calculate key statistics. Key statistics provide the operator with a summary of network performance.

14
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Raw Statistic
Raw Statistic
Raw Statistic
Calculation
Key Statistic
Net03_1_02

EMOTOROLA LTD. 2001
15
BSS Performance Management (PM)
Issue 11 Revision 0

Before examining the origin of each statistic it is worth noting which software processes within the BSS collect and upload them. The Performance Management (PM) applications gather and transport to the OMC the BSS statistics defined in the software requirements section of the equipment performance specification. All processes responsible for collecting statistics in the system software will automatically create a Distributed Statistics Function (DSF) as a subprocess. This DSF is responsible for collecting and storing all statistics relevant to that process. The DSF can store up to 12 statistical files, each file containing the stats (statistics) monitored over a set period. Each statistic gathering period can be set by the operator, typically this period is one hour or one half-hour. At a remote Base Transceiver Station (BTS) a Site Statistics Process (SSP) is started, the SSP is responsible for interfacing to the Central Statistics Process (CSP) located at the BSC and is used as a message distributor between the CSP and the SSP. The reason for this is that the CSP does not have to keep track of all the DSFs. Instead for each site it can send messages to the SSP which will distribute the messages for the CSP. The Code Object Upload Process (COUP) is utilized to transfer the statistics gathered by the CSP to the OMC. The agent process reports statistics threshold alarms and the end of a data collection interval (file ready event) to the OMC. Upon request from the OMC or upon the end of a data collection interval (file ready event), the CSP gathers the statistics from the DSFs and sorts the data and then, using the COUP the CSP, uploads the statistics to the OMC.

16
EMOTOROLA LTD. 2001
Issue 11 Revision 0
OMCR OMCR BSC Agent COUP
Central Statistics CentralStatistics Process Process (CSP) (CSP)
BTS
Remote BCS Remote BCS Remote BCS
SSP DSF
NET03_Ch1_03
SSP DSF DSF
SSP DSF DSF
DSF

EMOTOROLA LTD. 2001
17
Subsystem Interfaces
Issue 11 Revision 0
The diagram opposite shows all the interfaces utilized within the Motorola subsystem infrastructure. Each of these interfaces are statistically monitored.
Message Transfer Link (MTL)

The MTL is the Motorola device name given to the signalling link between the MSC and the BSC. Each MTL has a bandwidth of 64 kbs and employs the Comit Consultative International de Telegraphy et Telephone (CCITT) signalling system N o 7 protocol. In the diagram opposite the MTL is shown crossconnected through the Remote Transcoder (RXCDR) which is a quite normal practice. Multiple MTLs can be implemented to one BSC up to a maximum of 16. A MTL could be terminated on any time slot (except 0) at the BSC, although circuit numbering conventions and historical reasons always lead the MTL to be placed on time slot 16.
Transcoder Base Site Link (XBL)

The XBL is the Motorola device name given to the Fault Management (FM) link interconnecting the RXCDR and BSC. The XBL is an essential control link and provides a robust message link between the RXCDR and the BSC. It allows runtime checks to be performed to confirm E1/T1 connectivity between the BSC and RXCDR, and also consistency between CIC devices equipped at the BSC and those at the RXCDR database to support the dynamic allocation of Ater channels carrying call traffic between the BSC and RXCDR. The XBL also performs as a fault management link. Using the XBL, if a XCDR card becomes faulty the FM in the RXCDR can inform the BSC which incoming traffic circuits are down. The BSC will then be able to notify the MSC, and this information is passed on the MTL as a blocking message. The MSC will block these circuits until it receives an unblocking message signifying the traffic circuits are repaired. The number of XBLs required depends upon the number of CICs and/or the number of Ater interface channels. A BSC can be connected to a maximum of 5 RXCDRs, and vice versa. A maximum of 10 XBLs (which may be equipped at 64 kbit/s or 16 kbit/s) can be configured for each BSC/RXCDR. The XBL can occupy any time slot on the 2Mb trunk and is positioned by a database command. The minimum number of XBLs required is 1 XBL at 64 kbit/s capacity per 1200 MSCBSC trunks, or equivalent capacity at 16 kbit/s. The XBL uses the LAPD protocol.

18
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MSC
MTLs OMLs
OMC
OMS RXCDRs
OMS CBC
CBLs
ABSS
XBL XBL
ABSS
XBL
MTP BSCs OMS
CBA AXCDR RSLs
MTP OMS
CBA AXCDR
BTS
BTS
BTS
BTS
NET03_Ch1_04

EMOTOROLA LTD. 2001
19
Operations and Maintenance Link (OML)
Issue 11 Revision 0
Operations and Maintenance Link (OML)

The Operations and Maintenance Link (OML) is the Motorola device name given to the signalling connection between OMC and one of two entities, the BSC or RXCDR. A common configuration is shown opposite. The RXCDR has a single 2 Mbit/s link from the packet switch. Time slot 1 will contain the OML for the RXCDR, which will be terminated in the operations and maintenance software. The OML and indeed CBL bound for the BSC are simply cross-connected through the RXCDR. The OML is a 64 kbs link using the X25 protocol, multiple OMLs (up to 4) can be configured to a single entity. The link will support a huge range of maintenance traffic. Time slot allocation and 2 Mbit/s termination of this link is very important and must be consistent with BSS ROM default requirements.
Cell Broadcast Link (CBL)

The Cell Broadcast Link (CBL) is the signalling connection from the BSC to the Cell Broadcast Centre (CBC). The GSM Cell Broadcast Centre (CBC) is responsible for building and maintaining air interface Cell Broadcast (CB) messages. These messages will be passed to the CB agent in the BSC on the CBL. The BSC is responsible for their distribution to individual CB schedulers within each BTS. Once again the CBL utilizes the X.25 protocol and as the diagram opposite shows it can be cross-connected through the RXCDR. Using current software only one CBL can be configured, and essentially any time slot can be utilized.
Radio Signalling Link (RSL)

The Radio Signalling Link (RSL) supports traffic signalling and maintenance operations between the BSC and BTS. The Layer 2 protocol used is LAPD and the bandwidth necessary for each link is 64 kbs. Multiple radio signalling links can be configured up to a maximum of eight. Time slot allocation and 2 Mbit/s termination is critical and must be consistent with BSS ROM default requirements.

110
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Radio Signalling Link (RSL)
MSC
Single 2Mb
RXCDR
FM
OMS OML OML CBL Single 2Mb
X.25
OMC
MTL
XBL
CBL OML
CBC
MTP CBA OMS RSL
FM
BSC
BTS
NET03_Ch1_05

EMOTOROLA LTD. 2001
111
BSS Software Review
Issue 11 Revision 0
BSS Software Review

Before studying call handling and handover statistics it is very important to revise the BSS software entities involved. Successful CP procedures depend on the interaction and messaging between individual processes. Whether successful or not each software entity will monitor every event and increment their own statistics accordingly.
BSS Radio Subsystem (RSS)

Overview
The Radio Subsystem (RSS) is a collection of application processes whose purpose is to manage the BSS RF hardware to the MSs. The RSS functions include the Layer 2 interface (LAPDm) and radio link control including the handover detection and power control process. The RSS portion of the BSS implements the interconnection between the application layer (Layer 3) and the physical channel hardware (Layer 1). Using In-Cell equipment the RSS software is designed to run on a single GPROC and at maximum can handle six carriers. Although possible, the handling of this many carriers could lead to a shortfall in processing power. Multiple instances of RSS software can co-exist in the same digital cage. Each instance will run on a separate GPROC, usually a Digital Host Processor (DHP), but also the Base Transceiver Process (BTP) can be used. The instance of RSS software must always be located in the same digital cage as the Digital Radio Interface extended Memory (DRIM) cards it is supporting. In M-Cell the RSS software will run on the Transceiver Station Manager (TSM) card within the Transceiver Control Unit (TCU), each instance therefore will handle a single carrier only. The RSS comprises of five components: 1. 2. 3. 4. 5. RSS configuration and Fault Management (FM) Layer 1 interface Layer 2 protocol RSS A-bis interface Handover detection and power control

112
EMOTOROLA LTD. 2001
Issue 11 Revision 0
BSS Radio Subsystem (RSS)
Radio Subsystem (RSS)
Software interface procedures between BSS RF hardware and mobile station (MS). One subsystem can support up to 6 carriers (InCell) Horizon one RSS per carrier MCell one RSS per carrier
NET03_Ch1_06

EMOTOROLA LTD. 2001
113
BSS Configuration and FM Interface
Issue 11 Revision 0

This process controls the configuration of its related DRCUs, and is the interface to the BTS FM system. With regard to configuration, this process is responsible for informing the hardware as to its configuration, and instructing the DRCU as to the usage of each TS (e.g. Broadcast Control Channel (BCCH), Stand-alone Dedicated Control Channel (SDCCH) 8 channel or TCH/FS). The process also has the responsibility of downloading the DRIM board during the initialization of the base site, as well as the loading and configuring the DRCU before CP is achieved. Once the site is in CP this process is essentially idle.

114
EMOTOROLA LTD. 2001
Issue 11 Revision 0
FM
CFM
FCP FTP DRI Air Interface
HDPC
L1
L2
RSS Abis External to RSS Within RSS
Call Processing (CP) RRSM/RCI
NET03_Ch1_07

EMOTOROLA LTD. 2001
115
Issue 11 Revision 0
RSS Layer 1
The functions of Layer 1: S S S S S S S S S Downloads firmware. Message link between RSS hardware. Collects fault information and reports to Fault Collection Process (FCP). Scheduling both Access Grant Channel (AGCH) and Paging Channel (PCH) messages on the air interface. Translates downlink layer 2 (LAPDm frames) into DRI/DPR messages. Translates Digital Radio Interface (DRI) into Layer 2 messages. Supports multiple pages in one message. Supports immediate assignments and immediate assignment rejects in one message. Layer is responsible for obtaining timer values for nonsynchronized handovers and passing them to the DRI.
RSS Layer 2
Layer 2 is the link between Layer 1 and the RSS A-bis (Layer 3). The purpose of Layer 2 is to perform the data link (Open Systems Interconnection (OSI) Layer 2). Layer activates from Layer 3 to Layer 1 as specified in TS GSM 04.05 and TS GSM 04.06. This activates to interpret incoming messages from both the Layer 3 interface and Layer 2 interface and act on them. Layer 3 messages are converted to LAPDm frames which are sent to Layer 1 and vice versa. Layer 2 provides the LAPDm protocol necessary to make this transfer of messages. Layer 2 is also responsible for establish an Short Message Service (SMS) link to the MS for the delivery of short messages. Layer 2 can handle SMS messages up to 255 bytes long. Layer 2 also verifies the SMS messages and performs any segmentation/reassembly of the SMS messages.
RSS A-bis
The RSS A-bis provides the interface and message protocol between the RSS and CP. The RSS A-bis support a pseudo-A-bis interface, designed by Motorola to conform closely with the GSM requirements but to provide a means for more software control of hardware and software located at the BTS site. All messages between CP and RSS go through the RSS A-bis and the pseudo-A-bis interface to Radio Resource State Machine (RRSM) and the Radio Channel Identifier (RCI). The main responsibilities of the RSS A-bis are as follows: S S S S S Initializing the RSS A-bis Checking downlink message validity Reporting and logging erroneous states via Software Fault Management (SWFM) Translates downlink messages into internal RSS messages Translates uplink messages into RSS CP interface NET03: BSS Subsystem Planning
116
EMOTOROLA LTD. 2001
Issue 11 Revision 0
FM
CFM
FCP FTP DRI Air Interface
HDPC
L1
L2
RSS Abis External to RSS Within RSS
Call Processing (CP) RRSM/RCI
NET03_Ch1_07

EMOTOROLA LTD. 2001
117
Handover Detection and Power Control
Issue 11 Revision 0

This process has by far the most functions to fulfil inside the RSS. It controls the transmission power of the MS (uplink) and also the transmission power of its related Diversity Radio Channel Unit (DRCU) (downlink) on a per time slot basis. The object is to keep both the MS and the DRCU on the lowest possible transmission power to help reduce interference between system users. This process is also responsible for calculating the MSs timing advance to keep the MS inside its allocated time slot. The handover detection and power control process takes responsibility for initiating the handover process for a MS. It detects the need for handover based on a number of criteria set up and optimized in the data base. Whilst time slots on its related DRCU are not busy, this process monitors these time slots to produce a noise interference level for the frequency on which the carrier is operating. These figures are then passed up to the Layer 3 CP software. Once a call to a MS has been established, if a MS leaves the system without deregistering, the system will waste its resources if the MS channel remains in operation. To reduce this, the handover detection and power control process monitors the Slow Associated Control Channel (SACCH) messages from all MSs on its DRCUs. If a SACCH message from a MS fails to appear, the process waits a predetermined time, if still no SACCH message appears, it instructs the CP software to close down the resources allocated to that MS.

118
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Functions Controls transmission power of MS Controls the timing advance of MS Controls the transmission power of the BSS Determine the need for handover (intraBSS and interBSS) Monitors the interference level on idle channels Detects loss of SACCH messages (conserving resources)
NET03_Ch1_08

EMOTOROLA LTD. 2001
119
Call Processing (CP)
Issue 11 Revision 0

The purpose of CP) is controlling communication between the MSC, BSC, BTS and MS. CP and RSS interact to control call setup and clearing, handover, encryption and movement of Direct Transfer Application (DTAP) messages between the MSC and MS. CP has been split into 2 levels connected by the Motorola A-bis link: CPBSC Connectionless Manager (CLM) Message Transfer Part L3 (MTPL3) Signalling Connection Control Part (SCCP) preprocessor SCCP State Machine (SSM). Radio Resource State Machine (RRSM) Cell Resource Manager (CRM) Cel Broadcast Scheduler (CBS).
CPBTS

120
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Collection of Layer 3 protocols Functions

Call setup/clearing Message transfer (DTAP/Base Station System Management Application Part (BSSMAP)) Control handovers CP RSS interface Encryption Allocation of resources Configuration of logical channels CLM MTPL3 SSM SCCP preprocessor SM RRSM/RCI CRM CBS
CPBSC
CPBTS
NET03_Ch1_09

EMOTOROLA LTD. 2001
121
Message Transfer Part Layer 3 (MTPL3)/SCCP Preprocessor
Issue 11 Revision 0

The MTPL3 is comprised of the MTPL3 and Signalling Connection Control Part (SCCP) preprocessor. The MTPL3 is responsible for maintaining the signalling link between the MSC BSS. The process within MTPL3 is responsible for the data link layer operations of MTP. The SCCP preprocessor is responsible for determining the type of message (DTAP/BSSMAP) and then routing the internal message.
SCCP State Machine (SSM)

The SSM maintains the state of the call at the MSC interface. The SSM is responsible for call initialization, maintenance, release and the primary control of the call during a handover. For all these activities the SSM can be considered the central hub and decision making process of CP. The SSM is located at the BSC where it can appear in multiple instances, one per Link Control Function (LCF).
Connectionless Manager (CLM)

The CLM handles the connectionless procedures of BSSMAP these procedures include, blocking, reset circuit, global reset and signalling point inaccessible. The connectionless procedures within GSM are needed to maintain an active interface with the MSC. The CLM is located at the BSC where a single instance can only be found on the Base Site control Processor (BSP).
Switch Manager (SM)

The SM supervises the dynamic and static connections implemented by the Kiloport Switch board (KSW) or Time slot Switch (TSW) card. The SM will be present at every site type and will appear as a single instance on the master Generic Processor Board (GPROC) device. It can be considered as part of CP when located at the BSC where it will be controlled by the SSM and prompted to make Circuit Identity Code (CIC) to Traffic Channel (TCH) connections dynamically. The SM is also involved in internal handovers, where the CIC trunk is maintained but the TCH must be switched.
Radio Resource State Machine (RRSM)

The RRSM can be considered the centre of CP at the BTS. A single instance only is necessary and can be found on the BTP. The RRSM will maintain a higher level of control of the air interface TCH resources. Upon receipt of instructions from the SSM the RRSM will supervise the activation and deactivation of TCHs. This includes the control of the RSS software and the compilation of radio resource messages to the MS. NET03: BSS Subsystem Planning
122
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CA SM CLM SSM
MTPL3 SCCP Preprocessor
CA
SM CA Man Machine Interface (MMI)
RRSM RCI CRM RSS Abis CA CBS RSS FM Cell Broadcast Agent (CBA) MMI RSS CM FM
Net03 _Ch1_10
External CP interfaces Internal CP interfacees

EMOTOROLA LTD. 2001
123
Issue 11 Revision 0
Radio Channel Interface (RCI)

The RCI performs the routing of messages from the RSS to the CP functions. The RCI and RRSM validate the uplink messages. The RCI attaches an SCCP reference number to each uplink message and maintains an accurate map of these numbers with regard to the RSS. The RCI process provides a routing and validation function between RSS and CP The RCI is also responsible for processing requests from the SCCP preprocessor and distributing paging messages.
Cell Resource Manager (CRM)

The CRM supervises the allocation of available radio resources. It utilises a dynamic data base and marks the state of each channel (SDCCH & TCH) within each cell it controls. GSM specifications demand that resources be allocated on a best to worst basis and indeed the CRM maintains an idle interference reading for each free channel. Not only does the CRM allocate resources but also provides each connection with a unique identity called the SCCP reference number. The CRM is also responsible for building system information messages using elements provided by the CM. The CRM also provides all the necessary information for the configuration of each logical channel. A number of BSS features are also supervised by the CRM, SDCCH dynamic reconfiguration and TCH flow control.

124
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CA SM CLM
MTPL3 SCCP Preprocessor SM CA MMI SSM
MSC
RRSM RCI CRM CBS RSS Abis CA CBS RSS CM MMF FM
External CP interfaces Internal CP interfacees
Net03 _Ch1_11

EMOTOROLA LTD. 2001
125
Ladder Diagrams
Issue 11 Revision 0
Ladder Diagrams
Many statistics within CP are based on the arrival or nonarrival (timer expiry) of BSS defined messages. These interprocess messages are shown as a straight line between two software processors, above the line will be the title of the message. The diagram opposite shows the framework of a ladder diagram less the messages. From this diagram the location and GPROC device type should be carefully noted, as these details are omitted from the working diagrams. The transmission mechanism of these messages is complex and an explanation is unnecessary for the subject matter covered by this course.

126
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Ladder Diagrams
Ladder Diagrams
BTS
BSC
MS
RSS
CRM RRSM
SSM
SM
MTP
MSC
Initiate assignment
DHB/BTP (multiple)
NET03_Ch1_12
BTP (single)
LCF (multiple)
BSP (single)

EMOTOROLA LTD. 2001
127
Ladder Diagrams
Issue 11 Revision 0

128
EMOTOROLA LTD. 2001
Chapter 2
Statistical Data Types

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 2 Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Description of statistical data types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter Array Statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Counter array example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gauge statistic example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Durational Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Distribution Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Weighted Distribution Statistic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
21 21 22 24 26 28 28 210 210 212 214 216 218 220 222 224

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0

Objectives
On completion of this chapter the student will be able to: S S S Name the six statistical data types. Describe how each of the statistical data types collect information. State the results each statistical data type will output.

EMOTOROLA LTD. 2001
21
Issue 11 Revision 0
Description of statistical data types

There are six statistical data types. Every statistic considered during this course will comprise of one of these types. Most statistics are either counters or durations, these are the simplest data types. The six statistical data types available are listed below: S S S S S S Counter Counter array Gauge Duration Normal distribution Weighted distribution
During this section a detailed description of each of these types will be given along with examples where appropriate.

22
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Description of Statistic Data Types
Duration
12 9 3 6
TICK TICK TICK
Counter
Normal Distribution
Counter Array
Weighted Distribution
12 9 6 3
TICK TICK TICK
12 9 6 3
TICK TICK TICK
Gauge
MAX
NET03_Ch2_01

EMOTOROLA LTD. 2001
23
Issue 11 Revision 0
Counter
The counter cumulative value is incremented by n (the reported value) each time a report is made by the application process. Therefore, the counter cumulative value represents the number of occurrences of an event within an interval. A threshold value may be specified in the case of alarm generating counters. An event is reported to the OMC when the threshold value is reached. The event will only be reported once during an interval if a threshold is reached, for it does not report multiple events if the threshold has been exceeded.

24
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Counter
Report Produced
Increment cumulative value by n. Application Process Value (n)
Statistical interval expired

FINAL REPORT Cumulative value
12 9 6 3
Final Report
NET03_Ch2_02

EMOTOROLA LTD. 2001
25
Issue 11 Revision 0
Counter statistic example

CALLS_QUEUED
After the MS has successfully completed call set-up on the SDCCH the next stage is for the network to transfer the MS to a TCH, this process is called the assignment procedure. The assignment procedure is initiated by the MSC by sending the assignment request message to the SSM, this message includes the characteristics of the channel required and the CIC trunk to be used on the A-interface. Before making any trunk connections the SSM will send the initiate assignment message to the RRSM requesting that suitable resources be activated in respect of this MS connection. The RRSM will send an assignment resource request to the CRM, which holds a dynamic data base denoting individual TCH availability. If no resource of the correct type is available the request may be queued, depending upon data base parameters and message contents. If the request can be queued then the force queue message is sent to the RRSM. For every channel request which is queued this counter statistic is incremented.

26
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Counter Example:
CALLS_QUEUED
SSM RRSM
Initiate assignment Assignment resource request
MSC
Assignmentrequest
CRM
Force queue Assignment queued Queueing indication pegs: CALL_QUEUED
NET03_Ch2_03

EMOTOROLA LTD. 2001
27
Counter Array Statistic
Issue 11 Revision 0

A counter array statistic is an enhancement of the simple counter, in that the total figure reported is supplemented with a categorical breakdown using up to 16 bin counters. Each bin value will represent a particular category depending on the statistic being monitored. Depending upon the number of bins required in the array, the array can be small (4 bins), medium (8 bins), large (12 bins) or extra large (16 bins). This number is not configurable, but is preset in software for each relevant statistic.
Counter array example

When the SSM receives a handover recognized message it will analyse the cause value before executing the appropriate handover type. At this point in time the message is also used to increment handover cause statistics. The cumulative value is incremented for each handover attempted, whilst the appropriate bin is also incremented depending on the cause value. Ten bins are utilized with the following fixed designations: 0 UPQUAL 1 UPLEVEL 2 DOWNQUAL 3 DOWNLEVEL 4 DISTANCE 5 UPINTERF 6 DOWNINTERF 7 POWERBDGT 8 CONGESTION 9 ADJ_CHAN_INTF 10 NON IMPERATIVE MULTIBAND At the end of the statistical interval the cumulative total is reported along with the bin array, showing the cause values that make up this total.

28
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Counter Array
Report Produced
Cause
Increment cumulative counter by 1 Increment relative bin by 1
Application Process

FINAL REPORT
12 9 6 3
Final Report
Cumulative total Bin array

TICK
12 9 6 3
TICK TICK
NET03_Ch2_04

EMOTOROLA LTD. 2001
29
Issue 11 Revision 0
Gauge
The gauge current value is incremented or decremented by n (the reported value) each time a report is made by the application process. A gauge adjusts readings that monitor occurrences of an event within an interval. A threshold value may be specified in the case of alarm generating gauges. An event is reported to the OMC when the threshold value is reached. The event will only be reported once during an interval if a threshold is reached, for it does not report multiple events if the threshold has been exceeded. At the end of the interval, gauge statistics give the average value and maximum value achieved during that interval.
Gauge statistic example

CHANNELS_DISABLED
One of the functions of the CRM is to provide a dynamic data base as to the state of each channel within a cell, whether in service or Out Of Service (OOS). This statistic is updated in the CRM each time a time slot changes from the OOS state to the In Service (INS) state or vice-versa.

210
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Gauge
Report Produced
Value (n)
Increment/decrement current value by n. Store Maximum value

MAX
Application Process

FINAL REPORT 12 9 6 3
Mean Value Maximum Value
Final Report
MAX
NET03_Ch2_05

EMOTOROLA LTD. 2001
211
Issue 11 Revision 0
Duration
The duration cumulative value is kept by the application process by starting and stopping the timer when events begin and cease respectively. The time in between these reports is recorded as a cumulative time value. All durations report cumulative values in milliseconds (msec). The duration maximum and minimum values are saved and reported at the end of the interval. The duration mean value is calculated each time a report is made. Mean value = cumulative duration (floating point) number of times event occurred

212
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Duration
Report Produced
Application Process
TICK
9 12 3 6
TICK TICK
Value (n)
Increment cumulative value by duration Increment number of samples Store minimum value Store maximum value
12
Start
Stop
TICK
3
TICK
9 6
TICK
FINAL REPORT Cumulative value Minimum value Maximum value Mean value TICK
12 9 6 3
Final Report
12 9 6 3
TICK TICK
NET03_Ch2_06

EMOTOROLA LTD. 2001
213
Durational Statistic Example
Issue 11 Revision 0

SDCCH_CONGESTION
When a channel request is received the network will try to assign an SDCCH subslot. The channel request is passed up to the RRSM which in turn solicits the CRM for an available SDCCH. If available, the CRM will assign one by returning the channel assigned message to the RRSM. If the last available SDCCH was assigned then an internal timer is started at the CRM. This timer is stopped only when an SDCCH subslot next becomes available.

214
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH_CONGESTION
MS
RSS
RRSM
Channel request
CRM
Channel request Channel request received Channel assigned If last SDCCH assigned start timer
RF channel released Stop timer when the ack. received first SDCCH becomes available Elapsed time update: SDCCH_CONGESTION
NET03_Ch2_07

EMOTOROLA LTD. 2001
215
Issue 11 Revision 0
Normal distribution
Normal distribution statistics record the number of times a statistical element is at a specific value. This statistic type allocates the data collected into bins. There are 10 bins available. Bin ranges for the 10 bins may be set up for each individual distribution statistic (default values may also be used). When the application process reports an event the bin representing the reported value of the event is then incremented by one. Two additional measurements are also required: the number of samples and the cumulative value. When an event is reported the number of samples is incremented by one and the cumulative value is updated by the reported value. These two measurements are used to calculate the mean value. Mean value = (floating point) cumulative value number of samples
The distribution maximum and minimum values are saved throughout the interval and reported at the end of the interval. The duration mean value is calculated each time a report is made. An array of values representing the total counts per bin is also reported.

216
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Normal Distribution
Report Produced
Value (n)
Application Process
Increment cumulative value by reported value n Increment relative bin by one Increment number of samples by one Store minimum value Store maximum value

FINAL REPORT
12 9 6
0 1 2 3 4 5 6 7 8 9
Final Report
Bin array Minimum value Maximum value Mean value
NET03_Ch2_08

EMOTOROLA LTD. 2001
217
Normal Distribution Statistic Example
Issue 11 Revision 0

INTF_ON_IDLE
The DRIM card via RSS L1 will provide the HDPC with interference information on a time slot basis. Every Time Division Multiple Access (TDMA) frame each idle time slot is monitored for interference, these values are reported using the scale 063 (110 to 47dBm). The HDPC will average these interference levels using an unweighted algorithm and produce a value representing the interference level on a SACCH multiframe basis. This value increments the cumulative total for this statistic and will also cause the appropriate bin and the number of samples count to be incremented by one.

218
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Normal Distribution Example
INTF_ON_IDLE
HDPC
Carrier
Interface level 063 Averaging process Value produced every 480ms Cumulative value Appropriate bin Increment number of samples by one
NET03_Ch2_09

EMOTOROLA LTD. 2001
219
Issue 11 Revision 0
Weighted distribution statistics record the duration for which a statistical element is at a specific value. This statistic type allocates the data collected in to bins. The data placed into the bins is weighted by time. Bin ranges for the 10 bins may be set up for each individual distribution statistic (default values may also be used). The application process reports the start of the distribution at a particular value and updates it when a change in the value occurs. This procedure starts and stops internal timers which compute the duration of an activity. Weighted distributions increment the bin count by the amount of time (in ms) that the statistic had the given value. When an event is reported the number of samples is incremented by the time difference and the cumulative value is updated by the time difference multiplied by the bin value. At interval expiry the mean value is calculated. Mean value = (floating point) sum (value x duration) time interval (ms)
The statistic result consists of an array of values representing the total time in which the value was active per bin and a mean across all bins. The distribution maximum and minimum values are also saved throughout the interval and reported at the end of the interval.

220
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Report Produced
Application Process Duration TICK
TICK
12 9 3 6
Value (n)
TICK
Increment relevant bin by duration Increment cumulative value by (duration xn) Increment number of samples by the duration Store minimum value TICK TICK TICK TICK Store maximum value
12 12 9 6 3
Start
Stop
0 1 2 3 4 5
TICK
9 6
TICK

FINAL REPORT
12 9 6
0 1 2 3 4 5 6 7 8 9
Final Report
Bin array Minimum value Maximum value Mean value
TICK
12 9 6
TICK
3
TICK
12 9 6
TICK
3
TICK
TICK
NET03_Ch2_10

EMOTOROLA LTD. 2001
221
Weighted Distribution Statistic Example
Issue 11 Revision 0

BUSY_TCH
After the MS has successfully completed call set-up on the SDCCH the next stage is for the network to transfer the MS to a TCH, this process is called the assignment procedure. The assignment procedure is initiated by the MSC by sending the assignment request message to the SSM, this message includes the characteristics of the channel required and the CIC trunk to be used on the A-interface. Before making any trunk connections the SSM will send the initiate assignment message to the RRSM requesting that suitable resources be activated in respect of this MS connection. The RRSM will send an assignment resource request to the CRM, if the CRM is able to allocate the required resources it will return an assignment channel assigned message detailing the resources to be used. Upon allocating these resources the CRM will update this statistic.

222
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Weighted Distribution Example
BUSY_TCH
CRM
RRSM
SSM
MSC Assignment request
Initiate assignment
Assignment resource request BUSY_TCH Assignment channel assigned
NET03_Ch2_11

EMOTOROLA LTD. 2001
223
Issue 11 Revision 0
Summary
Counter
Counts the number of occurrences of an event.
Counter array
Counts the number of occurrences of an event with a breakdown of applicable causes.
Gauge
Reports the mean and maximum value of the statistic in question. Incremented or decremented when an event is received.
Duration
Measures the duration of an event.
Normal distribution
Records the number of times a statistical element is at a specific value.
Weighted distribution
Records the duration for which a statistical element is at a specific value.

224
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Summary
Counter
Cumulative value (+)
Duration
Cumulative value (+time) Mean TICK Minimum Maximum
12 9 6 3
TICK TICK
Counter Array
Cumulative value Bin array
Normal Distribution
Bin value (+) Mean Minimum Maximum E F G H I J 0 1 2 3 4 5 6 7 8 9
Gauge
Mean value (+) Maximum MAX
Bin value (+time) Mean Minimum Maximum
TICK
12 9 6 3
TICK TICK
TICK
12 9 6
TICK
3
TICK
0
NET03_Ch2_12

EMOTOROLA LTD. 2001
225
Issue 11 Revision 0

226
EMOTOROLA LTD. 2001
Chapter 3
Interface Statistics

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 3 Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OML, RSL and XBL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL interface statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The X.25 and LAPD protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.25 and LAPD statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Allocation of Switch (RXCDRBSC) Circuits (DARBC) Feature . . . . . . . . . . . ATER_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ATER_PREEMPT_STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTL Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The C7 protocol - MTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Signalling Units (SUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTP C7 utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The C7 protocol SCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP performance and utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Busy CICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processor Utilization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
31 31 32 32 32 34 310 312 314 320 326 326 326 330 330 330 332 338 344 350 352 354 356

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Objectives
On completion of this chapter the student will be able to:
X.25 and Link Access Procedure D (LAPD) objectives

S S Name the variants of High level Data Link Controller (HDLC) which are used by GSM. Draw the framing structure for HDLC and identify in which fields the following parameters are sent: Service Access Point Indicator (SAPI) Frame type S Name the three frame types used by HDLC. Which type of frame is used to transmit the following messages: Frame Reject (FRMR)? Set Asynchronous Balanced Mode (SABM)? S S Name the modes used by HDLC. Which mode is the default mode? Draw signalling diagrams to illustrate how the other mode is initiated and terminated. Identify illustrated X.25 and LAPD statistics using the statistical table provided.
MTP objectives
S S S S S S State the functions of the three MTP levels. Draw a diagram of an MTP Signalling Unit (SU). Name the three SU types. Name the two parameters which make up the data field of a SU. Name the three MTP statistical groups and describe the network conditions they relate to. Identify illustrated MTP statistics using the statistical tables provided.
SCCP objectives
S S S Identify which field of the MTP SU is used to transmit SCCP messages. Name the two operating modes for SCCP and state their associated protocol class number. Identify illustrated SCCP statistics using the statistical tables provided.
Miscellaneous objectives
S Name the processor utilization statistic.

EMOTOROLA LTD. 2001
31
Introduction
Issue 11 Revision 0
Introduction
These statistics relate to activities on the network interfaces. Messages travelling over the interfaces are counted and signalling link outages are recorded. There are two groups of interface statistics; Operations and Maintenance Link (OML), Radio Signalling Link (RSL) and Transcoder to BSS Link (XBL) interface statistics and MTL interface statistics. These are detailed below:
OML, RSL and XBL interface statistics

X.25 messages are recorded travelling between the BSS and the OMC (OML). LAPD messages are recorded travelling between the BSS and RXCDR (XBL) and between the BSC and BTS (RSL). These statistics are referred to as X.25 and LAPD statistics.
MTL interface statistics

The MTL is the interface between the BSS and the network switching system. Since there are a large number of statistics pertaining to the MTL these statistics will be broken down into several categories as specified in CCITT Q.791.
SCCP performance and utilization.

SCCP makes up the transport layer of CCITT #7 and manages the establishment and release of call related connections.
MTP C7 performance.
MTP makes up the link and network layers of CCITT #7. These statistics count the different types of failure and recovery situations on the BSC to MSC interface.
MTP C7 availability.
These statistics count the durations for which the signalling links between the BSC and the MSC are OOS.
MTP C7 utilization.
These statistics count the messages received, transmitted and retransmitted on the BSC to MSC interface.

32
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
OSI Layers
Application 7 Presentation 6 Session 5 Transport 4 Network 3 Link 2 Physical 1
SS#7 Levels
SS#7
BSSAP (DTAP+BSSMAP) SCCP MTP Level3 MTP Level2 MTP Level1
X.25
X.25 Applications X.25 LAPB 2Mb/s Trunk
Others
4 3 2 1
Abis
LAPD
ACRONYMS BSSAP BSSMAP DTAP MTP LAPBD SCCP
Base Station System Application Part Base Station System Management Application Part Direct Transfer Application Part Messages Transfer Application Part Link Access Procedure BD Signalling Connection Control Part
Alignment information
Transmission of X.25 & C7 on 2 Mb/s Trunk

X.25 Packet C7 Signalling Unit
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
2 Mb/s Trunk frame structure
NET03_Ch3_01

EMOTOROLA LTD. 2001
33
Introduction
Issue 11 Revision 0
The X.25 and LAPD protocols

Before we start to look at the interface statistics it is essential that the student is familiar with the protocols used on the respective interfaces. The first protocol we will look at is the HDLC protocol. HDLC is a Layer 2 protocol and variations of it are used by both X.25 and A-bis. X.25 uses LAPB for Layer 2 messaging, while A-bis uses LAPD. Both LAPB and LAPD protocols are variants of HDLC.
HDLC frame structure

The framing structure for HDLC is illustrated on the page opposite. The component parts of the frame are described below: Flags The flags are used to denote the start and end of each frame. The end flag can also act as the start of the next frame. The flag pattern used is 01111110. If this pattern occurs within the frame bit stuffing is used to prevent the data being confused with a flag. Bit stuffing involves a 0 being inserted after any five consecutive 1s. Address Identifies the intended receiver when a command frame is sent and indicates the transmitter when a response frame is sent. The SAPI is part of the address field and indicates which Layer 3 entity has generated or is to receive the frame. SAPI 0 RSL SAPI 62 OML SAPI63 L2ML The address field also contains the Terminal endpoint identifier (Tei) which identifies a logical user on the HDLC link. Control Indicates which type of frame it is, there are three frame types. These will be described in more detail on the following page. Information frames Supervisory frame Unnumbered frames Information Layer 3 data is transmitted in this field. Frame check sequence Provides error checking for the frame, all bits between the flags are checked. If errors are found the frame will be retransmitted.

34
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
HDLC Frame Structure
first bit Flag Address Control Info Frame check sequence
last bit Flag
NET03_Ch3_02

EMOTOROLA LTD. 2001
35
Introduction
Issue 11 Revision 0

36
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
LAPB Addressing
Command 01 hex Primary Secondary Response 01 hex Command 03 hex Response 03 hex Primary Secondary
NET03_Ch3_03
LAPD Addressing
BSC
Logical Channels
RSL (SAPI 0) OML (SAPI 62) L2ML (SAPI 63)
BTS DRCU
BSP Tei= 0
Tei 003
RSL (SAPI 0) OML (SAPI 62) L2ML (SAPI 63)
DRCU Tei 002
OML (SAPI 62) L2ML (SAPI 63)
BTP Tei 001
NET03_Ch3_04
OML (SAPI 62)

EMOTOROLA LTD. 2001
37
Introduction
Issue 11 Revision 0
The X.25 and LAPD protocols continued

HDLC operating modes
The HDLC protocol can operate in two distinct modes: acknowledged mode and non-acknowledged mode. By default the protocol will operate in non-acknowledged mode, to initiate or terminate acknowledged mode the messages illustrated on the page opposite must be sent. Acknowledged mode When operating in this mode every message sent must receive an acknowledgement (e.g. assignment and assignment complete). Non-acknowledged mode When operating in this mode messages may be sent and no acknowledgement is required (e.g. measurement reports sent from the MS to the BSS).
HDLC frame types

There are three frame types used by HDLC these are detailed below: Information frames Used to convey Layer 3 information, each unit of data must be acknowledged. May be referred to as I-frames. Supervisory frames Used for flow control purposes, manages the flow of I-frames. They are used to acknowledge or request retransmission of I-frames. There are three types of S-frames: Receive Ready (RR) Receive Not Ready (RNR) Reject (REJ) Unnumbered frames Used for link establishment and release, these frames are used to initiate or terminate acknowledged mode There are several types of U-frames. Some common ones are listed below: Set Asynchronous Balanced Mode (SABM) Disconnect (DISC) Unnumbered Information (UI) Unnumbered Acknowledgement (UA) Frame Reject (FRMR)

38
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
Layer 2 Alignment
SUCCESSFUL BTS
2 Mbit/s link
BSC
BABME UA IFRAME IFRAME
BTS
DISCONNECT
DISC
BSC
UA
NET03_Ch2_05

EMOTOROLA LTD. 2001
39
Introduction
Issue 11 Revision 0
X.25 and LAPD statistics

X.25 and LAPD performance FRMR
FRMR frames Counts the number of FRMR frames received and transmitted.
INVALID_FRAMES_RX
Invalid received frames Counts the number of invalid frames received.
N2_EXPIRY
Expiration of N2 Counts the number of times the retry count threshold has been exceeded.
X.25 and LAPD utilization I_FRAMES_RX

Received I-frames Counts the number of information frames received.
I_FRAMES_TX
Transmitted I-frames Counts the number of information frames transmitted.
SABM_TX
SABM frames Counts the number of SABM frames transmitted.
OMC
OML BSC
XBL RXCDR BSC
RSL BTS BSC
NET03_Ch3_06
Note: The RSL is used to illustrate these statistics but they are also calculated for OML and XBL. NET03: BSS Subsystem Planning
310
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
X.25 and LAPD Statistics

FRMR INVALID_FRAMES_RX FRMR
BSC
Invalid Frame
BTS
IFRAME N2_EXPIRY RETRY IFRAME 1ST TIME RETRY IFRAME N2TH TIME
BSC
BTS
I_FRAME_RXI_FRAMES_TX IFRAME IFRAME
BSC
BTS
SABM_TX SABM
BSC
NET03_Ch3_07
BTS

EMOTOROLA LTD. 2001
311
Dynamic Allocation of Switch (RXCDRBSC) Circuits (DARBC) Feature
Issue 11 Revision 0

The evolved DARBC feature of GSR 5 has introduced automatic connection of Ater channels (between the RXCDR and BSC) to connect MSCallocated CICs to the BSC. The mode of operation is known as the AutoConnect mode and is the standard mode following upgrade to GSR 5. The previous GSR 4 mode, known as Backwards Compatibility Mode, is part of GSR 5 but is superceded after upgrade is complete Prior to this feature, connectivity between MSC and BSC via the transcoder was mapped statically, but with this feature the BSC treats its Ater or connecting channels as a pool resource A CIC is mapped to a through connection via the RXCDR on initiation, and when the CIC is nominated by the MSC, the Ater channel is utilised in its mapped mode. However if a fault should occur on the Ater carrying the call between the RXCDR and BSC, a new Ater cahnnel will be alocated so that the call is not lost. The BSC and RXCDR have the following responsibilities as client (BSC) and Server (RXCDR) within this feature: BSC tracks CIC and Ater utilization, and allocates/deallocates Ater channels as required. It also instructs the RXCDR via the enhanced XBL to make connections between its MSC and Ater interfaces. The BSC also carries out audit of the CIC and Ater information. The RXCDR makes switch connections between the Ater channels and the MSC interface, and informs the BSC when faults or operator actions affect the usability of CICs or Ater channels. It also ensures that the correct idle tone is connected and provides the BSC with CIC/Ater audit information. It also handles the error case where the BSC does not initiate the audit procedure
Statistics
The statistics which record the notable occurrences are as follows:
ATER_STATUS
This 7counter array will monitor the Ater channel status on a perXBL linkset basis.
ATER_PREEMPT_STATUS
This 7counter array monitors the number of calls preempted on the Ater channel.
BUSY_CICS
This weighted distribution measures the utilization of CICs MSCBSC. It is covered later under MTL statistics, of which it is a part.

312
EMOTOROLA LTD. 2001
Issue 11 Revision 0
DARBC feature
MSC
MSC allocates CIC to call
CIC RXCDR:has Ater

chans mapped to CICs, responds to BSC allocation
CIC
RXCDR
RXCDR
XBLs carry BSC RXCDR control messages for Ater
Ater chans
BSC: notes allocation Instructs RXCDR BSC to thruroute allocates Ater chan to call
A bis BTS
NET03_Ch3_07a

EMOTOROLA LTD. 2001
313
ATER_STATUS
Issue 11 Revision 0
ATER_STATUS
This 7- bin counter array records significant events associated with the allocation of Ater channels within the group of channels controlled via an XBL between a BSC and a RXCDR.

314
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_STATUS
ATER_STATUS
ATER_CHAN_REQ ATER_CHAN_REQ_FAIL
CALL_ASSIGN_FAIL_COMM_ERR
HO_FAIL_COMM_ERR
CALL_ASSIGN_FAIL_NO_ATER HO_FAIL_NO_ATER 7 bin counter array BSC_INIT_BLK_CICS_LOW_ATER
NET03_3_07b

EMOTOROLA LTD. 2001
315
ATER_STATUS
Issue 11 Revision 0
The individual bins of the ATER_STATUS statistic record information as shown below:
ATER_CHAN_REQ
(Bin 0)
This counter records the total number of Ater channels requested between the BSC and RXDCR during a statistics interval.
ATER_CHAN_REQ_FAIL (BIN 1)
This counter records the number of Ater channels requested but could not be allocated (all reasons).
CALL_ASSIGN_FAIL_COMM_ERR
(Bin 2)
Counts the number of call assignment failures due to BSC-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.

316
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_STATUS
ATER_STATUS
Allocation request
Ater assign RXCDR 0 3 31
ATER_CHAN_REQ
MSC 0 1 TS 329
BSC Groups Ater chans 31 Timeslots
Allocation request
Assign Fail ATER_CHAN_REQ_FAIL (all reasons)
MSC
RXCDR
BSC
Allocation request MSC

NET03_3_07c
CALL_ASSIGN_FAIL_COMM_ERR COMM failure RXCDR BSC

EMOTOROLA LTD. 2001
317
ATER_STATUS
Issue 11 Revision 0
HO_FAIL_COMM_ERR (BIN 3)
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.
CALL_ASSIGN_FAIL_NO_ATER (Bin 4)
Counts the number of call assignment failures 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 calls.
HO_FAIL_NO_ATER (BIN 5)
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.
BSC_INIT_BLK_CICS_LOW_ATER (BIN 6)
Counts the number of times the event BSC 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.

318
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_STATUS
ATER_STATUS (Bins 3-6)
HO_FAIL_COMM_ERR
BSS HO
MSC RXCDR
HO
BSC CALL_ASSIGN_FAIL_NO_ATER
Allocation request
MSC RXCDR
Full/blocked BSC HO_FAIL_NO_ATER
BSS HO
MSC RXCDR 0 0 3
Full/blocked BSC BSC_INIT_BLK_CICS_LOW_ATER Full/blocked 31
MSC
NET03_3_07d
RXCDR
BSC

EMOTOROLA LTD. 2001
319
ATER_PREEMPT_STATUS
Issue 11 Revision 0
ATER_PREEMPT_STATUS
This 7- bin counter array statistic monitors the number of calls pre-empted on an Ater channel.

320
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_PREEMPT_STATUS
ATER_FAIL_NO_VUL_CALL
PREEMPT_ATTEMPT
CALL_LEG_PREEMPT_EMERG_CALL
CALL_LEG_PREEMPT_PRI_CALL
PREEMPT_ATMPT_ATER_UNAVAIL
PREEMPT_ATMPT_ATER_SWITCH ATMPT_FAIL_NO_VUL_CALL 7 bin counter array PREEMPT_FAIL_COMMS_ERROR
NET03_3_07e

EMOTOROLA LTD. 2001
321
ATER_PREEMPT_STATUS
Issue 11 Revision 0
ATER_PREEMPT_STATUS
The 7 bins of the statistic ATER_PREEMPT_STATUS record in formation as shown below:
PREEMPT_ATTEMPT (Bin 0)
Counts the total number of pre-emptions attempted of existing calls using an Ater channel to make way for calls of a higher precedence or emergency nature.
CALL_LEG_PREEMPT_EMERG_CALL (Bin 1)
Counts the number of existing call legs pre-empted to support emergency calls. Each emergency call is able to pre-empt a lower priority call to obtain its Ater resource.
CALL_LEG_PREEMPT_PRI_CALL (Bin 2)
Counts the number of call legs pre-empted to support a high priority non-emergency call. The high priority call is able to pre-empt a lower priority call for an Ater resource.

322
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_PREEMPT_STATUS
ATER_PREEMPT_STATUS
ATER_PREEMPT_STATUS
Preempt PREEMPT_ATTEMPT
MSC
RXCDR All new calls
BSC
CALL_LEG_PREEMPT_EMERG_CALL Preempt
MSC
RXCDR New EMERGENCY call
BSC CALL_LEG_PREEMPT_PRI_CALL Preempt
MSC
NET03_3_07f
RXCDR New PRIORITY call
BSC

EMOTOROLA LTD. 2001
323
ATER_PREEMPT_STATUS
Issue 11 Revision 0
PREEMPT_ATMPT_ATER_UNAVAIL (Bin 3)
Counts the number of pre-emption attempts initiated due to there being no Ater channels available (i.e. all A-ter channels full or blocked). When a call assignment fails or a handover fails, due to there being no available Ater channels, the BSC will attempt to pre-empt a lower priority call to obtain its A-ter resource.
PREEMPT_ATMPT_ATER_SWITCH (Bin 4)
Counts the number of pre-emption attempts performed due to switchover of A-ter channels.
PREEMPT_FAIL_NO_VULN_CALL I(Bin 5)
Counts the number of pre-emptions which fail because no call with a lower priority is found to pre-empt in order to obtain an A-ter resource. (e.g. a caller with a high priority is unable to obtain access to the network because it is already fully utilized with calls of equal or even higher priorities).
PREEMPT_FAIL_COMM_ERR (Bin 6)
Counts the number of pre-emption failures due to BSC-RXCDR communication errors. The stat will peg when the BSC message protocol to pre-empt an Ater resource times-out after continual attempts to coordinate the pre-emption of the A-ter resource with the RXCDR.

324
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ATER_PREEMPT_STATUS
ATER_PREEMPT_STATUS
PREEMPT_ATMPT_ATER_UNAVAIL
Pre empt No chans avail
MSC
RXCDR
New priority call
BSC
PREEMPT_ATMPT_ATER_SWITCH
Pre empt
MSC
NET03_3_07g
RXCDR
Switchover After chans
BSC
Preempt NOT POSSIBLE No chans avail
PREEMPT_FAIL_NO_VULN_CALL
MSC
RXCDR
And all Emerg/Hi Pri! Ater chans Preempt Fail
BSC
PREEMPT_FAIL_COMMS_ERROR
MSC
RXCDR
Comms error Ater chans
BSC
NET03_3_07h

EMOTOROLA LTD. 2001
325
MTL Interface Statistics
Issue 11 Revision 0

The C7 protocol MTP
This group of statistics report MTP information. MTP is part of the C7 protocol which is used throughout the network. MTP provides Layers 2 and 3 of the seven Layer model. MTP is the transport system for reliable transfer of messages between users. It is broken down into 3 levels:
MTP1 - Signalling data link functions

Physical, electrical and mechanical specifications for the interface.
MTP2 - Signalling link functions

Defines the the functions and procedures for controlling the transfer of signalling messages over a signalling link.
MTP3 - Signalling network functions

Defines the methods for message handling and routeing on a signalling link.
Signalling Units (SUs)

MTP uses SUs to transmit information, there are three SU types: Message Signalling Unit (MSU) Link Status Signalling Unit (LSSU) Fill-In Signalling Unit (FISU) The basic structure of a SU is illustrated on the opposite page. There are three parts to a SU: 1. Header Carries the information to ensure that the messages are sent in sequence and a length indicator. The detail of the header is illustrated over the page. 2. Data There are two parts to the data field; the Signalling Information Field (SIF) and the Service Information Octet (SIO). 3. Tail Contains error checking for the SU.

326
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Signalling Protocol Reference Model
Ainterface
To other processes within the BSS To air interface transmission equipment OSI MODEL
Distribution Function
Other applications (e.g. call control)
Operation and Maintenance information to PLMN O &M
DTAP
BSS MAP
DTAP
BSS OMAP
BSS MAP
BSS OMAP
To other users of the SCCP and MTP
Distribution Function
Layer 47 Layer 3 Layer 13
SCCP MTP Physical Layer
SCCP MTP
DTAP: Direct Transfer Application Part BSSMAP: BSS Management Application Part MTP: Message Transfer Part BSS OMAP: BSS Operation and Maintenance Application Part BSS: Base Station System SCCP: Signalliong Conection Control Part MSC: Mobile services Switching Centre
NET03_Ch3_08

EMOTOROLA LTD. 2001
327
Issue 11 Revision 0

328
EMOTOROLA LTD. 2001
Issue 11 Revision 0
The C7 Protocols - MTP
SIGNALLING UNIT (SU)
first bit
last bit
HEADER
DATA
TAIL
MSU LSSU FISU

NET03_Ch3_09

EMOTOROLA LTD. 2001
329
Issue 11 Revision 0
The C7 Protocol MTP continued

The MTP SU is described below. There are three parts to a SU. These are described in detail below.
Header
The header sequence is the same for all types of SUs and consists of the following: Flag (F) All SUs begin and end with an 8 bit flag. The flag bit pattern is 01111110. To ensure a flag pattern is not contained in the data, a 0 is inserted after any five consecutive 1s at the transmitter. At the receiver, the 0 is removed. These processes are called bit stuffing and bit stripping. Backward Sequence Number (BSN) The BSN is the sequence number of an MSU being acknowledged. Backward Indicator Bit (BIB) Used with the the BSN to perform SU sequencing control and acknowledgement. Forward Sequence Number (FSN) The FSN is the sequence number of the SU in which it is being carried. The FSN and BSN are binary coded using modulo 128. The FSN and BSN in a particular SU bear no relationship to each other. Forward Indicator Bit (FIB) Used with the FSN to perform SU sequencing and acknowledgement. Length Indicator (LI) Indicates the length of the message in octets.
Data
Signalling Information Field (SIF) Provides routeing information and carries user traffic. Contains the Origination Point Code (OPC) and Destination Point Code (DPC). Service Information Octet (SIO) Identifies source and destination users and indicates whether traffic is national or international.
Tail
Check Bits (CK) Error checking bits. Retransmission is requested if the frame is in error.

330
EMOTOROLA LTD. 2001
Issue 11 Revision 0
The C7 Protocols MTP
first bit
Header Data Tail
last bit
FLAG 8
BSN 7
B I B 1
FSN 7
F I B 1
LI 6 2
SIO 2 8
SIF
CK 16
FLAG 8
T03_Ch3_10

EMOTOROLA LTD. 2001
331
Issue 11 Revision 0
MTP C7 performance
MTP_SL_FAIL
Signalling Link (SL) failure-All reasons Counts the number of CEPT (see Glossary) SL failures for any reason including those detailed below.
MTP_SL_FIBR
SL failure-Abnormal Forward Indicator Bit Received (FIBR) or Backward Sequence Number Received (BSNR) Counts the number of times the signalling fails due to the detection of an abnormal FIB caused by the missynchronization of the sequence numbers BSN and FSN.
MTP_SL_ERROR_RATE
SL failure-Excessive error rate Counts the number of times the signalling fails due to the Signal Unit Error Rate Monitor (SUERM) timer expiration.
MTP_SL_ACK
SL failure-Excessive delay of ACK Counts the number of times the link fails due to a timer that expired because an acknowledgement of a MSU was not sent.
MTP_SL_CONGESTION
SL failure-Excessive duration of congestion Counts the number of times the SL fails due to the remove congestion timer expiring.

332
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Performance
MTP_SL_FIBR MSU MSC N good frames MAX Bad frame BSC MTP_SL_ERROR RATE MTP_SL_FAIL FIB ERROR
MSC
BSC
MTP_SL_ACK ACK MSC MSU MTP_SL_CONGESTION BSC
MSC
BSC
NET03_Ch3_11

EMOTOROLA LTD. 2001
333
Issue 11 Revision 0
MTP C7 performance continued

MTP_SU_ERROR
Number of SUs in error Counts the number of times erroneous SUs are received on the SL due to an abnormal FIBR or BSNR.
MTP_NEG_ACKS
SL number of negative ACKs received Counts the number of times the BSS detects out of order messages from the MSC.
MTP_SL_ALIGNMENT
SL alignment failure Counts the number of times the SL tries to align with the A-interface while it is OOS.
MTP_RESTORATION
SL restoration Counts the number of times the SL starts carrying user traffic. This happens when the SL comes into service, is uninhibited, or recovers from a remote processor outage.

334
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Performance
MTP_SU_ERROR SU BSC SU SU MSC NegAck (request transmit) BSC MTP_SL_ALIGNMENT MTP_NEG_ACKS FIB ERROR!
SU MSC
MSC
BSC
GO!
MTP_RESTORATION
MSC
BSC
NET03_Ch3_12

EMOTOROLA LTD. 2001
335
Issue 11 Revision 0
MTP C7 performance continued

MTP_CHANGEOVER
Local automatic changeovers Counts the number of times MTP traffic is routed to an alternate SL.
MTP_CHANGEBACK
Local zutomatic changebacks Counts the number of times MTP traffic is diverted back to the original SL after having been routed to an alternate SL.
MTP_LINK_INS
Duration of link in the INS state Measures the duration that the SL is INS.

336
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Performance
MTP_CHANGEOVER
GO!
MSC
GO!
BSC
MTP_CHANGEBACK
GO!
MSC
GO!
BSC
MTP_LINK_INS
12
TICK
3
TICK
9 6
GO!
TICK
MSC
BSC
NET03_Ch3_13

EMOTOROLA LTD. 2001
337
Issue 11 Revision 0
MTP C7 availability
MTP_UNAVAILABLE
Duration of SL unavailability (for any reason) Measures the duration for which CEPT SL is unavailable.
MTP_LINKFAIL
Duration of SL unavailablility due to link failure Measures the duration that the SL is OOS.
MTP_LOCAL_BUSY
Duration of local busy Measures the duration that the SL is congested locally.

338
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Availability
MTP C7 Availability
MTP_UNAVAILABLE
12
TICK
3
TICK
9 6
TICK
All cases MSC BSC
MTP_LINK_FAIL
12
TICK
3
TICK
9 6
TICK
Link failure MSC BSC
MTP_LOCAL_BUSY
12
TICK
3
TICK
9 6
TICK
MSC
BSC
NET03_Ch3_14

EMOTOROLA LTD. 2001
339
Issue 11 Revision 0
MTP C7 availability continued

MTP_REMOTE_PROC
Duration of SL unavailability due to remote processor outage Measures the duration that a remote processor is OOS.
MTP_START_RPO
Start of remote processor outage Counts the number of times a remote processor outage condition is identified.
MTP_STOP_RPO
Stop of remote processor outage Counts the number of times a remote processor outage is cleared.

340
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Availability
BANG! MTP_START_RPO CLUNK! CRASH
MSC
LSSUPRO
BSC
MTP_REMOTE_PROC
12
TICK
3
TICK
9 6
TICK
.....WHIRR..... MTP_STOP_RPO
MSC
LSSU
BSC
NET03_Ch3_15

EMOTOROLA LTD. 2001
341
Issue 11 Revision 0
MTP C7 availability continued

MTP_LOCAL_MGT
Duration of SL inhibition due to local management actions Measures the duration that the SL is inhibited due to local management actions.
MTP_MGT_INHIBIT
Local management inhibit Counts the number of times the SL is inhibited by the user carrying out a lock command to the associated link.
MTP_MGT_UNINHIBIT
Local ,anagement uninhibit Counts the number of times the SL is uninhibited by the user carrying out an unlock command to the link.
MTP_REMOTE_MGT
Duration of SL inhibition due to remote management actions Measures the duration that the SL is inhibited due to remote management action.

342
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Availability
MTP_MGT_INHIBIT
MSC
BSC
MTP_LOCAL_MGT
12
TICK
3
MTP_MGT_UNINHIBIT
TICK
9 6
TICK
MSC
BSC
STOP
MTP_REMOTE_MGT
12
TICK
3
TICK
9 6
TICK
MSC
BSC
NET03_Ch3_16

EMOTOROLA LTD. 2001
343
Issue 11 Revision 0
MTP C7 utilization
MTP_CONGESTION
Cumulative duration of SL congestion Measures the duration that the SL is congested.
SL_CONGESTION
SL congestion indications Counts the number of times a SL congestion indication is received.
SL_STOP_CONGESTION
Stop of SL congestion Counts the number of times a SL congestion indication stops.
CONGESTION_LOST_MSU
Number of SL congestion events resulting in loss of MSUs Counts the number of times a congestion event occurs which results in MSUs being lost.
MSU_DISCARDED
Number of MSUs discarded due to SL congestion Counts the number of MSUs which are discarded whilst there is congestion on the SL.

344
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Utilization
SL_CONGESTION
MSC
LSSUB Congestion indication
BSC
MTP_CONGESTION
12
TICK
3
TICK
9 6
SL_STOP_CONGESTION
TICK
MSC
LSSU
BSC
CONGESTION_LOST_MSU
MSC
BSC
MSU_DISCARDED
NET03_Ch3_17

EMOTOROLA LTD. 2001
345
Issue 11 Revision 0
MTP C7 utilization continued

MTP_MSU_RX
Number of MSUs received Counts the number of MSUs received over the SL.
MTP_MSU_TX
Number of MSUs transmitted Counts the number of MSUs transmitted over the SL.
MTP_RE_TX
Number of octets retransmitted Counts the number of octets that the BSS has retransmitted to the MSC because the MSC has requested retransmission.

346
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Utilization
MTP_MSU_RX
MSC
MSU
BSC
MTP_MSU_TX
MSC
MSU
BSC
MTP_RE_TX
MSC
Retransmission request Retransmission
BSC
NET03_Ch3_18

EMOTOROLA LTD. 2001
347
Issue 11 Revision 0
MTP C7 utilization continued

MTP_SIF_SIO_RX
Number of SIF and SIO octets received Counts the number of SIFs and SIOs received over the SL.
MTP_SIF_SIO_TX
Number of SIF and SIO octets transmitted Counts the number of SIFs and SIOs transmitted over the SL.
SIF_SIO_RX_OPC
Number of SIF and SIO octets received Counts the number of SIFs or SIOs received across all SLs to a BSS.
SIF_SIO_TX_DPC
Number of SIF and SIO octets transmitted Counts the number of SIFs or SIOs transmitted across all SLs to a BSS.
SIF_SIO_TYPE
Number of SIF and SIO octets handled with given SIO Counts the number of SIFs or SIOs transmitted or received on each SL. The signal types available are MTP, Test and SCCP. This statistic pegs the sum of all SLs to the BSS.

348
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MTP C7 Utilization
MTP_SIF_SIO_RX SU data
MSC BSC
MTP_SIF_SIO_TX SU data
MSC BSC
SIF_SIO_RX_OPC SU data
MSC BSC
SIF_SIO_TYPE
SIF_SIO_TX_DPC SU data
MSC BSC
NET03_Ch3_19

EMOTOROLA LTD. 2001
349
Issue 11 Revision 0
The C7 protocol SCCP

The SCCP statistics will now be considered. SCCP builds on MTP to provide full network service. The framing structure for SCCP is illustrated on the opposite page. As can be seen SCCP is part of the SIF found in an MTP SU. SCCP can operate in four modes, two of these modes are used for GSM these are; connectionless and connection-oriented. Protocol class numbers carried in the mandatory fixed field of the SCCP message indicate which mode is being used. The two modes used for GSM are described below:
Connectionless
Protocol Class 0 Single messages are sent to other SCCP users. There is only one type of message sent in connectionless mode. UDT Unit Data
Connection-Oriented
Protocol Class 2 A signalling connection is established before messages are sent. Several SCCP message types must be passed to establish this connection. CR Connection Request CC Connection Confirm CREF Connection Refused DT1 DaTa form 1 IT Inactivity Test Once the communication is complete the link must be released. The following SCCP message types are used to release the connection: RLSD Released RLC Release Complete

350
EMOTOROLA LTD. 2001
Issue 11 Revision 0
C7 Protocol SCCP
MTP
HEADER
DATA
TAIL
SIO
SIF
ROUTEING LABEL SCCP DPC OPC SLS
SCCP MESSAGE
Message type
Mandatory fixed part
Mandatory variable part
Optional (Data) part
NET03_Ch3_20

EMOTOROLA LTD. 2001
351
Issue 11 Revision 0
SCCP performance and utilization

SCCP performance ROUTING_SYNTAX
Routing failure syntax error detected Counts when a syntax error is detected in an SCCP routeing label.
ROUTING_UNKNOWN
Routing failure reason unknown Counts the number of invalid signalling point codes received from the MSC.
SCCP utilization SCCP_MSGS_TX

Total messages sent (by classes 0 and 2) Counts the number of SCCP messages transmitted on the SL.
SCCP_MSGS_RX
Total messages received (by classes 0 and 2) Counts the number of SCCP messages received on the SL.
SCCP_MSGS
Total messages handled from local or remote subsystem Counts the number of SCCP messages which are transmitted or received on the SL per BSS.

352
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SCCP Performance and Utilization

ROUTING_SYNTAX
SCCP routeing label MSC BSC
Syntax error
OPC
MSC (SPC)
DPC
BSS (SPC)
ROUTING_UNKNOWN
SCCP roueting label MSC BSC
SCCP_MSGS_RX SCCP MSC BSC SCCP_MSGS_TX SCCP MSC BSC SCCP_MSGS
NET03_Ch3_21

EMOTOROLA LTD. 2001
353
Busy CICs
Issue 11 Revision 0
Busy CICs
The number of CICs in use during each statistics interval is recorded by the weighted distribution statistic BUSY_CICS. CICs are initially equipped at both the RXCDR and at the BSC. From the RXCDR they are mapped to the MSC, but not mapped to the BSC since they will be allocated dynamically. They carry 64 kbit/s PCM speech from MSC to RXCDR (the A Interface), and transcoded 16kbit/s channels between RXCDR and BSC (the Ater interface), and are described in the equip 0/bss cic command at both RXCDR and BSC as CIC numbers (which actually relate to the MSC outgoing multiplexer). As a CIC is allocated by the MSC in the assignment request message, the mapping to an available Ater channel is assigned by the BSC and switched by the RXCDR which receives its auto-mapping instruction from the BSC in signaling via the enhanced XBL. As the BSC detects the allocation or de-allocation of a CIC, the statistic BUSY_CICs is pegged. This weighted distribution statistic is a 10-bin device. Its bin ranges are set in initial configuration to cover the range of CICs physically available to the BSC. The statistic will record the number of CICs (as a bin range) in use and also the length of time in ms that the bin range is valid. For each bin range, a cumulative total busy time is accumulated. At the end of the statistic gathering interval, the individual bin contents, as call-milliseconds, are summated; and when divided by the total period will yield a mean ERLANG value for the BSC during the interval concerned. Also the statistic will show the minimum and maximum number of CICs in use during the interval, and the overall bin array for further analysis The statistic BUSY_CICS therefore represents the number of calls in progress from the particular MSC for the base station system concerned.

354
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Busy CICs
Busy CICS
BUSY_CICS
Tick Tick
12 9 6 3 12
Tick
9 6
MSC CICS allocated by MSC as Call is set up
RXCDR
BSC CICs mapped at BSC through RXCDR to MSC Use recorded as BUSY_CICS
NET03_3_p51

EMOTOROLA LTD. 2001
355
Processor Utilization Statistics
Issue 11 Revision 0

This statistic applies to the process utilization of GPROCs and TCUs within each site of the BSS (i.e. BTS, BSC and RXCDR).
CPU_USAGE
Records the maximum, minimum and mean values of the short-term processor utilization measurement. Every second an internal timer will expire causing the process utilization percentage to be sent to the stats process. This statistic is recorded for each GPROC and TCU under the control of a BSS.

356
EMOTOROLA LTD. 2001
Issue 11 Revision 0
PROCESSOR UTILIZATION (MAX, MIN, MEAN)
100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% 0 1
NET03_Ch3_22
MAX MIN MEAN
9 10 11
STATISTICAL INTERVAL NUMBER

EMOTOROLA LTD. 2001
357
Issue 11 Revision 0

358
EMOTOROLA LTD. 2001
Chapter 4
Call Statistics

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 4 Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Channel Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Establishment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC BTS Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Assignment Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment request queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Directed retry cont. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONGEST_ STAND_HO_ ATMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Non-imperative handover rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion relief handover retry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ALLOC_TCH_ FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Assignment delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Downlink Bit Error Ratio (BER) Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PATH_BALANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interpreting the results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmit Power Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classmark Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Idle Interference Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Available time slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMS Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Point-to-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Broadcast (CB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Emergency Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FER (Frame Erasure Rate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Residual Bit Error Rate (RBER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Establishment Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
41 41 42 44 414 416 420 422 422 424 426 426 426 426 426 430 432 436 436 438 438 440 442 442 446 448 448 450 450 450 452 454 456 458 460

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Statistics
Call Statistics
Objectives
On completion of this chapter the student will be able to: S S Name the five call statistics groups. Indicate where each call statistic is incremented given related ladder diagrams and the W56 manual.

EMOTOROLA LTD. 2001
41
Call Statistics
Issue 11 Revision 0
Introduction
Call statistics are generated during CP. Call assignments and failures are monitored along with handover assignments and failures. The handover statistics will be investigated in the next section. Call statistics fall into five categories which are detailed in the W56 manual. 1. Connection Establishment Statistics. Identifies statistics updated when attempting to establish a signalling channel. 2. TCH Assignment Statistics. These statistics are updated when attempting to establish a traffic channel. 3. Usage/Congestion Statistics. Identifies the statistics which are used to monitor usage and congestion. 4. Call Clearing Statistics. These statistics are associated with call clearing. 5. Handover Statistics. A handover is the process of transferring a MS from one RF channel to another RF channel, between cells or within a cell. These statistics will be studied separately in the next section.

42
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Statistics
Call Statistics
CONNECTION ESTABLISHMENT
TCH ASSIGNMENT
hello
USAGE / CONGESTION
CALL CLEARING
bye
HANDOVER Site
Cell Cell
NET03_Ch4_01

EMOTOROLA LTD. 2001
43
Channel Establishment
Issue 11 Revision 0
In an attempt to establish dedicated mode the MS will transmit a channel request message, packaged in the familiar access burst. The channel request contains 8 bits of intelligent information, an establishment cause value (36 bits) and a random reference (25 bits). Before transmitting this information the MS will perform an X-or function on the data using the serving cells Base transceiver Station Identity codes (BSIC). This simple encoding function will enable the receiving server to discriminate between channel requests bound for other cells utilizing similar Broadcast Control Channel (BCCH) frequencies. The channel coder decodes the message on the Random Access Channel (RACH) from the Radio Channel Unit (RCU). If the channel coder is unable to equalize and hence decode the message it will peg an internal counter for the unrecognized message. If the channel request is correctly decoded it will then be sent to RSS L1, this message also includes the status of the unrecognized message counter and an indication as to the required relative timing advance relevant to this request.
OK_ACC_PROC_SUC_RACH
RSS Layer 1 increments this statistic for each channel request received from the channel coder.
ACCESS_PER_RACH
RSS L1 will also increment this statistic once for the channel request, plus the number indicated by the unrecognized message counter.
INV_EST_CAUSE_ON RACH
Upon receipt of the channel request RSS A-bis will validate the establishment cause value which must be consistent with specified causes in TS GSM 0408. If it is not consistent , this statistic is incremented and the channel request is ignored. Providing the cause value is successfully validated and a channel required message will be formatted and sent to CP. So-called phantom RACHs could possibly contribute to incrementing the above statistics. Phantom RACHs can essentially be attributed to sporadic noise and interference. Channel requests from distant MSs can obviously be affected by such noise especially when MS output power is low. Conversely when MS output is high any transmitted signals can cause interference to other co-channel and adjacent channel cells. In Motorolas implementation it is unlikely that cells using similar frequencies will be finely synchronized. This could only happen by chance as each BTS does not have frame synchronization. It is possible though for part synchronization to occur and this could contribute to the phantom RACH problem.

44
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MS
Channel coder (DRIM) RSS L1

Channel request peg: Channel request
OK_ACC_PROC_SUC_RACH ACCESS_PER_RACH
RSS ABIS
Channel request After verification if invalid peg:
INV_EST_CAUSE_ON_RACH
CP
Channel required
NET03_Ch4_02

EMOTOROLA LTD. 2001
45
Issue 11 Revision 0
Once the RRSM has received the channel required message it will attempt to establish the MS on a dedicated channel, usually a Stand-alone Dedicated Control Channel (SDCCH).
CHAN_REQ_CAUSE_ATMPT
This counter array pegs whenever a channel required message is received by the RRSM. It tracks the cause values of channel requests occurring in a cell. The bins of the array are as below: 0 Originating call 1 Emergency call 2 CM re-establishment 3 Location update 4 Page response The RRSM is responsible for incrementing the appropriate bin depending on the cause.
ALLOC_SDCCH
This counter statistic is incremented in the CRM each time an SDCCH sub-slot is successfully allocated. SDCCH sub-slots are allocated through immediate assignment, assignment and handover procedures.
ACCESS_PER_AGCH
Pegged in the RSS and counts the number of immediate assignment, immediate assignment extended and immediate assignment reject messages sent on AGCH. This statistic counts messages, not assignments or rejects. Remember that one message could contain up to 2 immediate assignments or indeed up to 4 immediate assignment rejects.
OK_ACC_PROC
Once the link layer has been established between the RSS and MS, the RSS will send an establish indication message containing the L3 initial message originating from the MS. The L3 initial message will be dependent on the MSs requirements. 0 1 2 3 4 5 6 7 CM Service Request CM Service Request CM Service Request CM Service Request CM Re-establishment Location Update IMSI Detach Page Response Call SMS Supplementary services CM Emergency Call

46
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSS ABIS Channel required CRM Peg: ALLOC_SDCCH RSS Channel required received
RRSM
Peg:
Channel assigned
Channel activation Channel activation acknowledge Immediate assignment cmd
MS
Immediate assignment cmd SABM (L3 Initial message) UA (L3 Initial message)
Peg: ACCESS_PER_AGCH Establish indication (L3 Initial message) Peg: OK_ACC_PROC
NET03_Ch4_03

EMOTOROLA LTD. 2001
47
Issue 11 Revision 0
SDCCH_CONGESTION
When the last SDCCH available is allocated then the CRM will start the sdcch_congestion timer. This timer will only be stopped when at least one SDCCH becomes idle. SDCCH_CONGESTION is a durational statistic indicating the total time within a period that no SDCCH was available.
BUSY_SDCCH
Each time the CRM allocates an SDCCH the BUSY_SDCCH statistic is incremented. This statistic is a weighted distribution and will produce a mean value indicating the average number of SDCCHs in use per interval. When the CRM receives a channel required received but has no available SDCCHs the following two statistics will be incremented:
ALLOC _SDCCH_FAIL
This statistic is pegged each time the CRM tries to allocate a free SDCCH but is prevented because they are all busy. This statistic is also incremented in the target cell when rejecting an SDCCH handover through lack of resources.
CHAN_REQ_MS_BLKD
This statistic is pegged by the RSS and is incremented each time an immediate assignment reject message is received from the CRM.

48
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSS A-BIS Channel required CRM If last SDCCH assigned start sdcch_conjestion timer for:
SDCCH_CONGESTION
RRSM
Channel required received
Increment:
BUSY_SDCCH
Channel assigned
RSS
RRSM Channel required CRM Immediate assignment reject Channel required received
If no sdcch available increment

ALLOC_SDCCH_FAIL
On receipt of immediate assignment reject peg:

CHAN_REQ_MS_BLK
03_Ch4_04

EMOTOROLA LTD. 2001
49
Issue 11 Revision 0
CHAN_REQ_MS_FAIL
Upon sending the immediate assignment message to RSS the RRSM will start timer rr_t3101. If rr_t3101 is allowed to expire and an establish indication for that connection has not been received then this counter statistic is incremented.

410
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSS
RRSM
Immediate assignment
rr_t3101
MS
rr_t3101
If rr_t3101 expires and no establish indication is received peg: CHAN_REQ_MS_FAIL
NET03_Ch4_05

EMOTOROLA LTD. 2001
411
Issue 11 Revision 0
SCCP Connection Establishment

After receiving the establish indication from the RSS to indicate the MS has succesfully arrived on its dedicated channel, the RRSM will then forward the L3 information onto the SSM. At this stage the SSM is responsible for establishing an SCCP virtual circuit connection for this MS (in connection orientated mode) with the MSC.
CONN_REQ_TO_MSC
To establish an Switch Virtual Circuit (SVC) within the SCCP layer of C7 the BSS must send a connection request to the MSC. The connection request will contain the L3 information originally sent by the MS plus other conection orientated information.
CONN_REFUSED
The MSC should respond with a connection confirm indicating that an SVC has been established at the SCCP layer. If, for some reason, this is not possible the MSC will return with a connection refused. On receipt of these messages the SSM will increment this statistic. The connection refused messages could, depending on switch implementation, be returned as a result of successful or unsuccessful location updating, failed call re-establishment and as a result of International Mobile Subscriber Identity (IMSI) detach. Depending upon switch software the connection refused could be returned when congestion relief is employed.
MS_ACCESS_BY_TYPE
This medium counter array measures the number of accesses of the system by MSs of different frequency band capabilities. The RRSM decodes this information from the classmark 3 message, usually sent just after the L3 initial message. The bins are defined below: 0 = PGSM 1 = DCS1800 2 = PCS1900 3 = PGSM + EGSM 4 = PGSM + DCS1800 5 = PGSM + EGSM + DCS1800 6 = PGSM + PCS1900 7 = PGSM + EGSM + PCS1900

412
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SCCP Connection Establishment
RSS
Establish indication
RRSM
pegs: MS_ACCESS_BY_TYPE
MTP/MSC
SSM
Initial L3 Information After the CR is sent the SSM pegs:
CONN_REQ_TO_MSC
One of: CM service request CM re-establish Location update request IMSI detach Respond to page
<CR> <CONNECTION REQUEST> Complete L3 information
<CC> <CONNECTION CONFIRM>
OR
<CREF> <CONNECTION REFUSED>
On receipt of a CREF the SSM pegs:

CONN_REFUSED
NET03_Ch4_06

EMOTOROLA LTD. 2001
413
Connection Establishment Statistics
Issue 11 Revision 0

PAGING PROCEDURE
The MSC is responsible for initiating the paging procedure and does so by sending the BSS a paging message. This message is recieved by the SCCP preprocessor, it contains the information necessary to page the MS (i.e. IMSI,Temporary Mobile Subscriber Identity (TMSI) and the cell id list). This message is sent in the connectionless mode of the SCCP Layer.
PAGE_REQ_FROM_MSC
This statistic is pegged by the preprocessor and is simply a count of the number of paging messages received from the MSC.
PAGE_REQUEST_FROM_MSC_FAIL
The preprocessor will peg this statistic when a paging message has been recieved suffering a protocol error. Providing the paging message can be interpreted by the preprocessor, the called MSs paging group will be determined and included in the page mobile request which will then be despatched to the appropriate instances of RRSM. From there, paging commands will then be sent to the correct instances of RSS where the pages will be grouped and formatted into paging request messages ready for transmission on the air-interface at the appropriate moment in time.
ACCESS_PER_PCH
Each time a paging request message is sent on the air-interface this statisic is incremented. As with the other access statistics this is incremented per message, remember a paging request message could contain up to 4 pages if paging by TMSI and up to 2 pages if paging by IMSI.
PCH_Q_PAGE_DISCARD
This counter statistic will increment each time a page from the MSC (IMSI or TMSI number) is overwritten whilst waiting in the queue. The oldest TMSI/IMSI number is overwritten first. The maximum queue length is 8 TMSI or IMSI numbers. They will be queued awaiting their paging group to appear in time.
PCH_AGCH_Q_LENGTH
This gauge statistic tracks the average number of paging or access granting messages queueing to be transmitted. It is pegged by the RSS Layer 1 software every paging multiframe.

414
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Paging Procedure
MSC MTP L3 (pre_proc)
RCI/RRSM
Paging
RSS
Page mobile request Incremented for every decoded paging msg: PAGE_REQ_FROM_MSC Paging command Peg: PCH_AGCH_Q_LENGTH Pegged per msg: ACCESS_PER_PCH Possibly increment PCH_Q_PAGE_DISCARD
MS
Incremented for every undecoded paging msg: PAGE_REQUEST_FROM_MSC_FAIL
Paging request
NET03_Ch4_07

EMOTOROLA LTD. 2001
415
TCH Assignment Statistics
Issue 11 Revision 0

The assignment procedure is initiated by the MSC after authentication, cyphering and call set-up is completed on the SDCCH. The assignment procedure is started when the MSC transmits an assignment request for the SCCP connection specified. This message indicates the type of channel required, the CIC to be used and also any priority levels which may exist.
MA_REQ_FROM_MSC
On receipt of the assignment request the SSM will increment this counter statistic. The SSM will then send an initiate assignment message to the RRSM informing it to initialize a TCH. The RRSM must then source an appropriate channel to be used and so sends an assignment resource request to the CRM.
MA_REQ_FROM_MSC_FAIL
This counter statistic is incremented by the SSM each time an assignment request message from the MSC fails validation. In this event the MSC is notified with the assignment failure message with cause protocol error between BSC and MSC.
EFR_REQ_FROM_MSC
This counter works exactly like MA_REQ_From_MSC, but is pegged only when an assignment request is received specifying an EFR channel.
ALLOC_TCH
This counter statistic is incremented in the CRM each time a TCH is successfully allocated. The reasons for the allocation can be origination or intra-cell handover.
TCH_USAGE
When the CRM allocates a channel to the RRSM it sends an assignment channel assigned or handover channel assigned message. Upon doing this it simultaneously starts an internal timer. This timer records the duration for which the TCH is in use. When the channel is deallocated the timer is stopped. The elapsed duration increments the TCH_USAGE total for that cell, including normal range channels in extended cells and the outer zone of concentric cells.
TCH_USAGE_INNER_ZONE
This statistic pegs as for TCH_USAGE but only when a channel in the inner zone of a concentric cell is allocated.
TCH_USAGE_EXT_RANGE
This counter statistic works exactly as TCH_USAGE, but tracks the usage of extended range channels only, on a per cell basis. It is pegged at the CRM.
MS_TCH_USAGE_BY_TYPE
This is a counter array that tracks the length of time each frequency type is in use in a cell. It is pegged by the CRM on a per cell basis. Although similar to TCH_USAGE, this statistic is completely independent of it. NET03: BSS Subsystem Planning
416
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MSC SSM
Assignment request
CRM/AM
Assignment resource request Assignment channel assigned CRM pegs ALLOC_TCH TCH_USAGE (durational) MS_TCH_USAGE_BY_TYPE TCH_USAGE_EXT_RANGE TCH_USAGE_INNER_ZONE TCH_CONG_INNER_ZONE BUSY_TCH(weighted, mean) TCH_CONGESTION AM pegs DYNET_ASSIGN_FAIL DYNET_CALL_REJECT
RRSM
Initiate assignment
On receipt of msg peg: MA_REQ_FROM_MSC and maybe: EFR_REQ_FROM_MSC
NET03_Ch4_08

EMOTOROLA LTD. 2001
417
Issue 11 Revision 0
BUSY_TCH
Each time the CRM allocates a TCH the BUSY_TCH statistic is incremented, this statistic is a weighted distribution and will produce a mean value indicating the average number of TCHs in use per interval. The CRM will allocate a TCH upon assignment, immediate assignment (in the case of an emergency call) and handover.
TCH_CONGESTION
When the last TCH available is allocated then the CRM will start the tch_congestion timer, this timer will only be stopped when at least one TCH becomes idle. TCH_CONGESTION is a durational statistic indicating the total time within a period that no TCH was available.
TCH_CONG_INNER_ZONE
This statistic pegs as for TCH_CONGESTION but only when congestion exists in the inner zone of a concentric cell.

418
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MSC SSM
Assignment request
CRM/AM
Assignment resource request Assignment channel assigned CRM pegs ALLOC_TCH TCH_USAGE (durational) MS_TCH_USAGE_BY_TYPE TCH_USAGE_EXT_RANGE TCH_USAGE_INNER_ZONE TCH_CONG_INNER_ZONE BUSY_TCH(weighted, mean) TCH_CONGESTION AM pegs DYNET_ASSIGN_FAIL DYNET_CALL_REJECT
RRSM
Initiate assignment
NET03_Ch4_09

EMOTOROLA LTD. 2001
419
BSC BTS Dynamic Allocation
Issue 11 Revision 0

The BSC BTS dynamic allocation feature provides an alternative mechanism for allocating terrestrial backhaul for radio resources (terrestrial backing resources) between the BSC and BTS. Previous to the introduction of this feature, these resources were allocated when RTFs were equipped. The terrestrial backing resource is a 16 kbs portion of a time slot on a span and is allocated on demand from a pool of available resources by the BSC. The pool is shared by the BTSs that are chosen to use dynamic allocation and appear within the same network configuration. It should be noted that dynamic allocation is limited to spoke, daisy-chain and closed loop daisy-chain network configurations (maximum of 20 BTS configurations may be specified). Dynamic allocation allows greater air capacity to be equipped than terrestrial backing resources exist, whether at a BTS site or within a BTS network. The feature allows RTF equipage for coverage purposes, not capacity purposes. Additionally, capacity can move dynamically between BTSs in the same network based upon traffic considerations. Even with dynamic allocation, greater bandwidth than that provided by a single span may be wanted by an operator. Networks may have up to 3 spans between each BTS in the configuration. The same number of spans must be specified between each BTS to maintain the simplicity needed to provide dynamic allocation.
Note:
The allocation of 16 kbs terrestrial backing resources requires 16 kbs switching at the BTS site. M-Cell BTSs do not support 16 kbs switching. InCell BTSs support 16 kbs when equipped with a KSW. In-building picocellular systems also support 16 kbs.
DYNET_ASSIGN_FAIL
Pegged at the AM, this counter statistic counts the number of assignment procedure failures due to a lack of terrestrial backing resources. It is pegged per BSS.
DYNET_CALL_REJECT
This counter array is pegged at the AM in similar circumstances to DYNET_ASSIGN_FAIL, but gives causes: Bin 0 = Non emergency call blocked lack of resources 1 = Emergency calls blocked lack of resources 2 = Non emergency calls blocked resources reserved 3 = Call pre-empted due to emergency calls 4 = Calls pre-empted due to loss of resources.

420
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MSC SSM
Assignment request
CRM/AM
Assignment resource request Assignment channel assigned CRM pegs ALLOC_TCH TCH_USAGE (durational) MS_TCH_USAGE_BY_TYPE TCH_USAGE_EXT_RANGE TCH_USAGE_INNER_ZONE TCH_CONG_INNER_ZONE BUSY_TCH (weighted, mean) TCH_CONGESTION AM pegs DYNET_ASSIGN_FAIL DYNET_CALL_REJECT
RRSM
Initiate assignment
NET03_Ch4_10

EMOTOROLA LTD. 2001
421
Issue 11 Revision 0

Assignment request queueing
If no TCH resources are available at the CRM the assignment request may be queued. This is dependent upon a flag in the assignment request message received from the MSC and also a database element, queue_management_information , set in add_cell.
CALLS_QUEUED
If queueing has been allowed and no resources exist then the CRM queues the request and informs the RRSM with a force queue message. This counter statistic merely counts the number of assignment requests that have been queued in a statistical interval. This statistic does not include queued handover requests.
TCH_Q_LENGTH
This weighted distribution statistic will provide a maximum and mean number of queued assignments during the period specified. These assignments will include originations and external handovers. Queueing will obviously result from the call queueing feature but also Extended GSM (EGSM) forced handovers, emergency call pre-emption, and directed retry.
CLR_REQ_TO_MSC
An assignment request cannot be queued indefinitely and in fact will be queued for a maximum of GSM timer T11 (BSSMAP_T11). If no assignment channel assigned message is received by the RRSM and T11 is allowed to expire the RRSM will send a release request to the SSM, which will be forwarded as a clear request to the MSC. There are a number of reasons why a clear request may be sent to the MSC, these include problems with cyphering, RF loss, intra-cell handover failure and inter-cell handover failure. Each time the message is sent to the MSC this counter statistic is incremented.

422
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Assignment Request Queueing

SSM CRM
Assignment resource request If assignment is queued pegs: CALLS_QUEUED TCH_Q_LENGTH Force queue Assignment queued Queueing indication
MSC
Assignment request
RRSM
Initiate assignment
RRSM CRM
Force queue
T11
No assignment channel assigned received
SSM
Release request Clear request pegs: CLR_REQ_TO_MSC
MSC
NET03_Ch4_11

EMOTOROLA LTD. 2001
423
Issue 11 Revision 0
Directed retry
The GSM directed retry feature, if purchased and enabled, can allow an otherwise queued assignment to be allocated a traffic channel in an alternate cell. As a compliment to this feature a further congestion relief mechanism can be specified which can result in TCHs being freed up by handing over existing calls that suit the congestion relief criteria. The standard GSM directed retry feature and the congestion relief feature are purchased and enabled individually. The GSM directed retry feature can work in conjunction with one of the two congestion relief procedures available. The criteria to allow a directed retry handover, initiated by either of the above features, is the same. Criteria one and two as specified in GSM TS 05.08 must be met by neighbour candidates, albeit using a congestion handover margin instead of the familiar ho_margin specified in add_neighbor. If reported neighbours do not meet these criteria then no handover will be attempted for that MS. The initiation of the directed retry procedure is similar for standard directed retry and both congestion relief procedures. When the CRM receives an assignment resource request message from the RRSM and is unable to allocate a free TCH due to congestion, the request will be placed in a queue. The very existence of the queue and its maximum size is normally determined by a combination of a database parameter and the queueing flag sent in the original assignment request message from the MSC. When directed retry is enabled a queue is formed regardless of these factors. The CRM will inform the RRSM that the request is in a queue using the force queue message. A further message is then generated and sent to the RRSM indicating congestion and the method by which it should be resolved. This could be a combination of the standard directed retry and/or one of the congestion relief mechanisms. This will depend on purchase and database parameters.

424
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Directed Retry
CRM
RRSM
SSM
Assignment request
MSC
Force queue Assignment queued
Congestion indication
Further events depend on congest procedure employed

NET03_Ch4_12

EMOTOROLA LTD. 2001
425
Directed retry cont.
Issue 11 Revision 0

The messaging that follows will depend on the DR mechanism specified in the congestion indication message.
Standard directed retry

When instructed to implement the standard directed retry mechanism the RRSM will send a force handover request message to the instance of RSS concerned. At this point the RSS will check if it is possible to hand the queued MS to another cell based on the last received measurement report. If the congestion criteria are met by at least one neighbour reported by the specified MS, then the familiar handover recognized message will be sent to CP.
CONGEST_ STAND_HO_ ATMPT

Upon receipt of the handover recognized received message containing the cause value standard directed retry the SSM will increment this counter statistic. This statistic is incremented for both intra-BSS and inter-BSS handovers. The handover itself will be executed in the normal way.
Non-imperative handover rejection

The BSS rejects an incoming non-imperative handover (of which one reason may be congestion relief) if it will cause congestion relief procedures to be triggered in the target cell. Should such a handover be allowed, then the net result would simply be the movement of a congestion problem from one cell to another.
Congestion relief handover retry

The source cell will not attempt a congestion relief handover to a target cell which has rejected a previous non-imperative handover attempt for a period of time set by two timer parameters. It does not, however, affect any imperative handover retries. These handovers are allowed to take place regardless, as they are needed in order to keep the call active.

426
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Standard Directed Retry
RSS
RRSM
SSM
Force handover request
Force handover response

IF ANY NEIGHBOURS MEET CRITERIA
Handover recognized Handover recogized received Pegs: CONGEST_STAND_HO_ATMPT
NET03_Ch4_13

EMOTOROLA LTD. 2001
427
Issue 11 Revision 0

Congestion relief mechanisms
When instructed to execute the first of the congestion relief mechanism handover needed TCHs the RRSM will canvass each instance of RSS in the cell with a candidate list query in a search for suitable calls. To resolve congestion this mechanism will cause the RRSM to aim at handing over as many calls as assignment requests queued in the CRM, the congestion indication message will contain this number. A suitable candidate would be an existing call where the MS has reported a neighbour meeting the congestion relief handover criteria. Each instance of RSS will in turn respond with suitable candidates, specifying pbgt result. The RRSM will wait to receive all or most of the candidate list response messages (timeout) and then construct the appropriate number of handover recognised received messages based upon the best Pbgt results. When instructed to execute the second of the congestion relief mechanism the RRSM will send each instance of RSS in the cell concerned a force handover request message. This will cause each RSS concerned to engage the congestion relief handover criteria and send handover recognized messages for any candidates satisfying this new criteria.
CONGEST_EXIST_HO_ATMPT
In the case of either congestion relief mechanism being employed, upon receipt of the handover recognized received message containing either the handover needed TCHs or handover all TCHs cause values the SSM will increment this counter statistic. This statistic is incremented for both intra-BSS and inter-BSS handovers. The handover itself will be executed in the normal way.
CONGEST_ASSIGN_HO_SUC
This counter statistic is incremented in the source cell for successful internal and external handovers that were executed as a result of standard directed retry. In the case of external handovers the statistic is incremented on receipt of the clear command from the MSC with cause value successful handover. For the internal case the statistic will be incremented as the SSM transmits the handover performed to the MSC. These procedures will covered in greater detail in the Handover section of this course.

428
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Congestion Relief
Handover Needed TCHs

RSS
Candidate list query Candidate list query
RRS
RRSM
SSM
CHECK IF CALLS MEET CRTERIA

Candidate list response Candidate list response Handover recognized received Handover recognized received Pegs:
Handover all TCHS

RSS RRS
Force handover request Force handover request Force handover response Force handover response Handover recognized Handover recognized Handover recognized
RRSM
SSM
Handover recognized received Handover recognized received Handover recognized received Pegs:
NET03_Ch4_14

EMOTOROLA LTD. 2001
429
Issue 11 Revision 0
ALLOC_TCH_ FAIL
This counter statistic is incremented each time the CRM is unable to allocate a TCH channel. The reasons for attempted allocation can be origination or hand in.
MA_CMD_TO_MS_BLKD
When no queueing is allowed or indeed is allowed but has reached a maximum (queue_management_information), the CRM will send a resource not available message to the RRSM informing it that the assignment request has been blocked through lack of resources. This statistic is pegged by the RRSM on receipt of this message. This message will also be received for the same reasons when an intracell handover is blocked, this too will increment this statistic.
MA_CMD_TO_MS
After the RRSM receives the assigned channel information from the CRM it will instruct the RSS to activate the specified time slot before sending an assignment command to the MS indicating the characteristics of its new TCH. This counter statistic is incremented at the RRSM each time an assignment command is sent to an MS.
MA_FAIL_FROM_MS
Assuming the CRM can allocate a TCH, the RRSM will proceed to activate the new channel and subsequently send the assignment command to the MS. The MS will, having received the assignment command, attempt to gain a L2 connection with the new TCH. The MS will not try to make this connection for an indefinite period and in fact an internal timer limits the duration allowed for this procedure. If the MS has not established a L2 connection on the new TCH and the timer expires then it will return to the original SDCCH and send an assignment failure to the BSS. On receipt of this message the RRSM will increment this counter statistic. This statistic is also incremented in the case of a failed intracell handover, this is detailed in the next section.
SECOND_ASSIGN_ATMPT
If the BSS feature SECOND_ASSIGNMENT is set, should the first attempt at assignment fail, (i.e. the MS returns to the SDCCH and report assignment failure) the RRSM will send a second channel activation command. The RRSM will peg the counter SECOND_ASSIGN_ATMPT at this point.
SECOND_ ASSIGN_SUC
If the second assignment attempt succeeds, the counter statistic SECOND_ASSIGN_SUC will peg.

430
EMOTOROLA LTD. 2001
Issue 11 Revision 0
TCH Assignment Blocked and Failure

MSC
Assignment request
SSM CRM Assignment resource

request No queuing allowed or queue is full and all TCHs busy. DR not in operation
RRSM Initiate assignment
ALLOC_TCH_FAIL Resource not available Unsuccessful assignment pegs: MA_CMD_TO_MS_BLKD Assignment failure
CRM RSS
RRSM
SSM
Assignment resource
request Assignment channel assigned Physical context request Physical context confirm Channel activation Channel activation acknowledge Assignment command
Initiate assignment
MS
Assignment command Assignment failure
pegs:
MA_CMD_TO_MS
Assignment failure (Second) assignment command pegs: MA_FAIL_FROM_MS

SECOND_ASSIGN_ATMPT SECOND_ASSIGN_SUC
Assignment command Assignment complete
Assignment successful
NET03_Ch4_15

EMOTOROLA LTD. 2001
431
Issue 11 Revision 0
Assignment delay
As previously mentioned it is possible for assignment requests to be queued, waiting for a TCH is become available. It is also possible for a handover request to be queued under the same scheme. For queueing to take place it must be indicated in the message originating from the MSC, also certain database parameters in add_cell must be enabled.
TCH_DELAY
When an assignment or handover request is queued for a specific connection the CRM starts an internal timer which is only stopped when a channel is allocated. The elapsed time is recorded by this normal distribution statistic. This statistic is not incremented upon BSSMAP_T11 expiry or if the call is cleared before assignment.

432
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Assignment Delay
SSM RRSM
Initiate assignment
MSC
Assignment request
CRM
Start Assignment resource request T11
Force queue
Assignment queued Stop Assignment channel assignment Increments: TCH_DELAY Queueing indication
NET03_Ch4_16

EMOTOROLA LTD. 2001
433
Issue 11 Revision 0
The complete TCH assignment procedure is detailed in the diagram opposite. When the RRSM receives an initiate assignment form the SSM it will start GSM timer T10 (ASSIGN_SUCCESSFUL) for the specified SCCP connection. This timer is stopped when the RRSM receives an assignment complete from the MS, in turn the RRSM will then send an assignment successful to the SSM. If T10 is ever allowed to expire a release request will be sent to the SSM, followed by a clear request to the MSC.
MA_COMPLETE_TO_MSC
This counter statistic is incremented in the SSM each time an assignment complete message is forwarded to the MSC. It should be remembered that one call could have multiple assignments (e.g. if the subscriber switches from voice to data). Directed retry will also affect this statistic as the assignment complete message will sent from the new server and hence this statistic would not be incremented in the old source but in fact in the new cell.
TOTAL_CALLS
This counter statistic is very similar to the one above. Each time a call is initially set up and the assignment complete message is sent from SSM to the MSC this statistic will be incremented. Subsequent channel changes (assignment procedures) within the same connection will not cause this statistic to be incremented. Directed retry will also have a similar affect on this statistic as it does on the one above.

434
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Assignment
SSM CRM RRSM
MSC
Assignment request
RSS
Assignment channel assigned Physical context request Physical context confirmed Channel activation Channel activation acknowledge
MS
Assignment command Assignment complete
T10 T10
SM
Connection request Switch response success
Assignment complete pegs: TOT AL_CALLS MA_COMPLETE_TO_MSC
NET03_Ch4_17

EMOTOROLA LTD. 2001
435
Downlink Bit Error Ratio (BER) Monitoring
Issue 11 Revision 0

Whilst engaged on a TCH the MS will receive 100 downlink bursts from the BSS per SACCH multiframe. Each burst is checked for quality and an individual BER determined. Using a unweighted algorithm these 100 BER results are processed into an overall BER average for that SACCH multiframe. This average is then encoded into a GSM defined quality band and sent to the BSS in an uplink measurement report. The quality band that is reported to the BSS, for the previous SACCH multiframe, is then converted to the equivalent assumed value before further averaging and processing by the HDPC. Depending upon database parameters the assumed value may not be used and instead the reported band figures are processed. The HDPC will then decide if the MS requires power control or a handover.
BER
The BER is a normal distribution statistic determined on a time slot basis and updated every SACCH multiframe (480ms) by the downlink quality measurement reported by the MS.

436
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Downlink BER Monitoring
Uplink measurement report
Downlink transmission
GSM quality bands:

BER
0 to 0.2 0.2 to 0.4 0.4 to 0.8 0.8 to 1.6 1.6 to 3.2 3.2 to 6.4 6.4 to 12.8 Greater than 12.8
REPORTED
0 1 2 3 4 5 6 7
ASSUMED
0.14 0.28 0.57 1.13 2.26 4.53 9.05 18.1
NET03_Ch4_18

EMOTOROLA LTD. 2001
437
PATH_BALANCE
Issue 11 Revision 0
PATH_BALANCE
This normal distribution statistic provides link balance verification on a carrier basis, updated every 480 ms. Path loss can be defined as the difference between the commanded power level and that power level perceived by the receiving station. As such the following formula is used to calculate this statistic on a SACCH multiframe basis. Path_balance where: uplink pathloss = actual MS txpwr rxlev_ul = uplink Pathloss downlink pathloss
downlink pathloss = actual BS txpwr rxlev_dl The rxlev_ul/dl values are the latest reported, they are not the averaged values. The result of the above equation is based around 110, the actual statistical result will equal path_balance plus 110. Typically the path loss should be similar in both the uplink and downlink directions. With diversity gain enabled the path balance will be just below 110, indicating a lower uplink path loss.
Interpreting the results

Negative results (values below 110) indicate problems with the BTS transmit equipment, antenna, RF cabling, filters etc. Positive results (values above 110) indicate problems with the BTS receive equipment, antenna, RF cabling, receive splitter, etc.
UPLINK_PATH_LOSS
The uplink path loss can be displayed as a statistic in its own right. This statistic is a normal distribution and is updated every SACCH multiframe for every active call. However, the value is a per-carrier average, and so is intended to give a profile of the radio link propagation path rather than accurate measurements per call.

438
EMOTOROLA LTD. 2001
Issue 11 Revision 0
PATH_BALANCE
path_balance
S Path_balance = uplink path loss - downlink path loss
w here:
uplink path loss = actual MS txpw r - rxlev_ul dow nlink path loss = actual BS txpw r - rxlev_dl
S UPLINK_PATH_LOSS = Actual MS txpwr - rxlev_ul

EMOTOROLA LTD. 2001
439
Transmit Power Levels
Issue 11 Revision 0

The uplink and downlink transmit power levels can be tracked by the normal distribution statistics CHAN_UL_TX_PWR_LVL and CHAN_DL_TX_PWR_LVL respectively. Both are pegged in HDPC and updated every SACCH multiframe. They represent the average level of each carrier, across all its time slots, in dBm. With power control, each time slot could be using a different power level and so this average is intended as a guide to the average levels in use in a cell rather than providing accurate per-channel data.

440
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Transmit Levels
TX
TX
HPDC CHAN_DL_TX_PWR_LVL CHAN_UL_TX_PWR_LVL
NET03_Ch4_19

EMOTOROLA LTD. 2001
441
Call Clearing Statistics
Issue 11 Revision 0

Ciphering
The ciphering procedure is detailed on the page opposite. It is initialized by the MSC sending a cipher mode command to the SSM, this message specifies the permitted A5 algorithms that may be used, cipher key (Kc) and also how the MS should respond. The SSM will decide the A5 version to be used based upon relevant database parameters. The SSM will pass the ciphering request message to the RRSM specifying the A5 algorithm to be used for this connection, it will also contain Kc and the MS response mode, at this time the SSM will start GSM timer CIPHERING_SUCCESSFUL. The RRSM will then pass cipher mode command down to the MS via the RSS, at this time the RRSM will start an internal timer, CIPHER_COMP_MS. Kc of course is not sent to the MS. The correct reponses can be seen on the page opposite, and of course, in normal operation, the timers will not expire. However if the timer in the RRSM should expire, a radio channel released message will be sent to the SSM, which will in turn cause the SSM to send a clear request to the MSC. If MT1 should expire in the SSM and no ciphering successful is received from the RRSM then a clear request will be sent to the MSC.
CIPHER_MODE_FAIL
In either situation if a clear request is sent to the MSC due to ciphering problems then this statistic is incremented.

442
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Clearing Statistics Ciphering
SSM MS
Ciphering mode command CIPHER_COMP_MS CIPHER_COMP_MS Ciphering mode complete Ciphering successful Cipher mode complete
MSC
Cipher mode request
RRSM
Ciphering request
Ciphering successful Ciphering successful
Ciphering successful Expires No ciphering successful received Clear request peg: CIPHER_MODE_FAIL CLR_REQ_TO_MSC
NET03_Ch4_20

EMOTOROLA LTD. 2001
443
Issue 11 Revision 0
Whilst in dedicated mode the MS will transmit measurement reports to the BSS every SACCH multiframe (480ms). The HDPC maintains a counter which will be decremented by one, should a measurement report not arrive. The counter is called link_fail and its maximum value can be set within the add_cell comand of the database. If a series of measurement reports do not arrive at the BSS then this obviously indicates that the uplink connection with the MS has been lost. In this situation link_fail will successively be decrement and eventually reach zero, at this point the RSS will declare link failure and inform the RRSM by sending an error indication message. The RRSM will instruct the RSS to deactivate the TCH and also inform the SSM of the failure and subsequent release by sending a radio channel released message. The SSM will then send a clear request to the MSC.
RF_LOSSES_TCH
This counter statistic is pegged on a time slot basis when the RRSM receives an error indication message with channel type TCH. It should be noted that an error indication message contains a cause value that can indicate a number of Layer 2 problems and therefore this statistic is incremented for a number of reasons of which link failure is just one.
RF_LOSSES_SD
This counter statistic is pegged on a time slot basis when the RRSM receives an error indication message with channel type SDCCH.

444
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RF Loss
MS
Uplink measurement report Missing report Missing report Missing report
RSS
Link_fail
Link failure declared
RRSM
Pegs: RF_L OSSES_SD or RF_L OSSES_TCH Radio channel released
SSM
Error indication
MSC
Clear request Pegs: CLR_REQ_TO_MSC
NET03_Ch4_21

EMOTOROLA LTD. 2001
445
Classmark Updating
Issue 11 Revision 0
Classmark Updating
MS classmark information is sent by the MS to the BSS/MSC as part of the L3 initial message which is sent when the MS tries to establish a signalling connection at L2 on the SDCCH. The MS classmark information, depending on its type, specifies the MSs capability concerning frequency, power, SMS, cyphering and revision level. It is possible that the MS or MSC may originate a classmark update procedure whilst the MS is already engaged on a dedicated resource. An MS may originate this procedure if it were to change power class during a call, the MSC may originate the procedure after a some kind of Visitor Location Register (VLR) MS registration problem. The origination of a classmark update procedure by either party is a rare event.
CLASSMK_UPDATE_FAIL
The classmark updating procedure is shown opposite, in this example the MSC has originated the process. This counter statistic is incremented by the RRSM when an update classmark message has been received in protocol error.

446
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Classmark Updating
Classmark Update
SSM RRSM
MSC
Classmark request
RSS
Classmark enquiry
Request classmark
Classmark change Update classmark Classmark update pegs: CLASSMK_UPDATE_FAIL
NET03_Ch4_22

EMOTOROLA LTD. 2001
447
Idle Interference Monitoring
Issue 11 Revision 0

When a TCH time slot is idle it is constantly monitored for any uplink ambient noise. During a SACCH multiframe an idle time slot is monitored 104 times. These samples are then processed to produce a noise level average per 480ms. This average is then reported to the HDPC, where it is further averaged and processed. Periodically the HDPC will report the interference level of each idle slot to the CRM, which will use this information in its channel allocation procedure.
INTF_ON_IDLE
This normal distribution statistic is time slot based, it is pegged in the HDPC and is updated every 480ms by the latest calculated ambient noise level.
IDLE_TCH_INTF_BANDM (n=0 to 4)
Five gauge statistics are available to measure the averge number of idle TCHs in each of the five interferer bands. CRM pegs these statistics each time its idle channel ranking information is updated by HDPC.
Available time slots

AVAILABLE_TCH
This gauge statistic is incremented and decremented as TCH time slots become enabled and disabled. This number includes the time slots already busy. A TCH is considered available by the CRM when its operational state is enabled and its administrative state is unlocked or shutting down. A TCH is considered unavailable when its operational state is disabled or its administrative state is locked. A TCH channel may be dynamically converted to an SDCCH slot under control of the reconfiguration feature, which will also be reflected by this statistic.
AVAILABLE_SDCCH
This gauge statistic is incremented and decremented as SDCCH time slots become enabled and disabled. This number includes the sub-slots already busy. An SDCCH is considered available and unavailable under much the same conditions as a TCH. As mentioned above a SDCCH channel may be dynamically converted to an TCH slot which will also be reflected by this statistic.

448
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Idle Interference
IDLE TS 104 TDMA FRAMES
DRIM
HDPC
pegs: INTF_ON_IDLE
n=
2 3 IDLE_TCH_INTF_BAND (04)
NET03_Ch4_23

EMOTOROLA LTD. 2001
449
SMS Performance
Issue 11 Revision 0
SMS Performance
Point-to-point
SMS point-to-point provides a means to transfer messages between the MS and short message entity via a service centre. SMS can be MS originated or MS terminated. Messages can be transferred on an SDCCH, should the MS be idle at the time of origination, or SACCH, should the MS already be in dedicated mode. Before an SMS can be transferred to an MS a Layer 2 connection using SAPI 3 must be established, however before the establishment of SAPI 3 a connection at SAPI 0 must first exist. The flow diagrams opposite follow the establishment of a Layer 2 connection using SAPI 3 for both MS terminating and originating cases.
SMS_INIT_ON_SDCCH
This counter statistic is incremented in the RRSM each time an establish indication or establish confirm is received from RSS on an SDCCH channel.
SMS_INIT_ON_TCH
This counter statistic is incremented in the RRSM each time an establish indication or establish confirm is received from RSS on an TCH channel.
Cell Broadcast (CB)

The CB feature enables the MS to receive unacknowledged information messages of a general nature such as traffic conditions, advertisements etc. The MS can only receive these messages whilst idle and indeed has to be configured to do so using the MSs MMI. These messages generally originate from a Cell Broadcast Centre (CBC) which has an X.25 SVC link to the BSC. In addition to messages from a CBC a number of background messages can be initiated using the base stations customer MMI. The two software entities controlling this feature are called the Cell Broadcast Agent (CBA) and the Cell Broadcast Scheduler (CBS) which are located at the BSC and the BTS respectively.
SMS_NO_BCAST_MSG
Each time a CB message is transmitted on the air-interface this counter is incremented, the statistic is pegged in the CBS.

450
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SMS Performance
SMS Performance
MS ORIGINA TING
SAPI 0 connection already established
RSS RRSM
pegs: SMS_INIT_ON_SDCCH or SMS_INIT_ON_TCH
MS
SABM SAPI 3 UA
SSM
MSC
Establish indication (SAPI 3) SMS DATA Data indication (Link id SAPI 3)
<DTAP>
<DTAP>
MS TERMINA TING
MSC
<DTAP> Short message
SSM
<DTAP>
RRSM
Establish request (SAPI 3) pegs: SMS_INIT_ON_SDCCH or SMS_INIT_ON_TCH Establish confirm Data request
RSS
SAPI 0 connection already established SABM SAPI 3 Unnumbered Acknowledgement (UA) SMS data
MS
NET03_Ch4_24

EMOTOROLA LTD. 2001
451
Emergency Access
Issue 11 Revision 0
Emergency Access
When a MS makes an emergency call, by dialling 112, the series of events that follow to set up the call will differ significantly from the usual call set-up process. The channel request message contains a special emergency cause value (101). Receiving this cause value the CRM will immediately try to allocate a TCH, the SDCCH stage is bypassed, this is called the immediate assign mode. Limited call set-up procedures will take place on the TCH and the call will continue on the same time slot. If no TCH is available the MS will be allocated an SDCCH and queue for a TCH in the usual way. A feature exists in the BSS called emergency pre-emption and can be enabled using customer MMI. This feature enables the BSS to dislodge a call currently in progress in order to allocated the emergency request the newly available resource. When the feature is enabled and an emergency channel request is received, if no TCHs are available then the MS will be allocated an SDCCH whilst a current call in progress is dislodged. In the unlikely event that no SDCCHs are available either then the MS is sent an immediate assignment reject message, in the meantime the BSS will dislodge a call in progress in anticipation of the channel request being repeated after the wait period (expiration of T3122). A number of statistic are based on the treatment of an emergency request.
NUM_EMERG_ACCESS
This counter statistic is incremented in the CRM each time a channel request received message is received having an emergency call value. This statistic is incremented regardless of the emergency pre-emption feature being enabled.
NUM_EMERG_REJECTED
This counter statistic is incremented in the CRM each time an immediate assignment reject is sent to the MS indicating that no resource, TCH or SDCCH , is available. This statistic is incremented regardless of the emergency pre-emption feature being enabled.
NUM_EMERG_TCH_KILL
This counter statistic is incremented in the CRM and indicates the number of TCHs torn down to allow an emergency request to use the freed resource. This statistic is only incremented if the emergency pre-emption feature is enabled.
NUM_EMERG_TERM_SDCCH
This counter statistic is incremented in the CRM and indicates the number of emergency calls which although allocated a SDCCH could not be subsequently assigned a TCH. This statistic is incremented regardless of the emergency pre-emption feature being enabled.

452
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Emergency Access
Emergency Access
MS
Channel request (emergency)
RSS
RSS ABIS
Channel request Channel required pegs:
RRSM
CRM
Channel request received (value 101) Channel assigned (TCH)
NUM_EMERG_ACCESS
RSS Immediate assignment SABM (L3 inital message) UA Immediate assignment
Establish indicator (CM SERVICE REQUEST EMERGENCY)
pegs: OK_ACC_PROC [CM_SERV_EME]
CRM MS
NO SDCCH NO TCH Immediate assignment Reject (Wait indication)
RRSM
Channel request received
pegs: NUM_EMERG_REJECTED
NET03_Ch4_25

EMOTOROLA LTD. 2001
453
Flow Control
Issue 11 Revision 0
Flow Control
Invocation of the flow control process at the CRM can be initiated from the CRM itself, the RSS or SSM, or from the MSC. The overload procedure, which protects against overload both within the BSS and also at the MSC, operates by temporarily barring randomlychosen mobile station access classes, one by one, until the overload is relieved. The messages indicating the onset of process overload can be seen on the opposite page. The Flow Control procedure is quite simple in that on receipt of any of the specified messages, the CRM will dynamically alter the BCCH system information messages to reflect the barring of an access class. As more messages are received thus more access classes are barred which should lighten the load the BSS is temporarily suffering. There are internal CRM timers (T17 and T18, set by FLOW_CONTROL_T1 and FLOW_CONTROL_T2 respectively) which control the barring and unbarring of these access classes.
FLOW_CONTROL_BARRED
This durational statistic is processed in the CRM. When the first overload message is received, a pair of internal timers (T17 and T18) are started, and during the period that follows a number of access classes will be barred and unbarred. When the timer sequence stops, the last access class is unbarred. The elapsed time is added to the total duration for that period.
MSC_OVLD_MSGS_RX
This counter statistic records the number of Overload messages received from the MSC. It is pegged at the SSM.

454
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Flow Control
Flow Control
CRM
Overload onset RCI
OR
RSS overload SSM MSC_OVLD_MSGS_RX MSC
OR
Overload onset
OR
MSC overload
FlOW_CONTROL_BARRED
NET03_Ch4_26

EMOTOROLA LTD. 2001
455
FER (Frame Erasure Rate)
Issue 11 Revision 0

Frame Erasure Rate (FER) Quality is a normal distribution statistic. It is derived from a measure of the ratio of successfully decoded speech frames to unsuccessfully decoded speech frames on the Air Interface uplink. It is measured over each 480 ms period by the RSS HDPC process. FER_QUALITY is measured on a timeslot basis for active channels after decoding, deinterleaving and error correction. Data for the statistic is reported by firmware to the RSS/HO (HDPC) process, where it is pegged. The ratio calculated is taken from the 24 x 20 ms vocoded speech frames received and decoded during a 480ms SACCH multiframe. The ratio is used to refer to a lookup table where it is converted to an FER quality number between 0 and 9. The relevant bin is then incremented, as is the Cumulative value of measurements. The range of the bins in the array is not alterable. It is as follows: FER QUALITY ERASURE RATE FER Quality Number 0 1 2 3 4 5 6 7 8 9 Example: On the air interface, the HDPC successfully decodes 22 frames of the 24 measured. The resulting ratio of 2 to 24 (0.0832) results in a lookup table FER_QUALITY of 2. FER Ratio (min to max)
0.0000 to 0.0416 0.0417 to 0.0832 0.0833 to 0.1249 0.1250 to 0.1666 0.1667 to 0.2082 0.2083 to 0.2499 0.2500 to 0.2916 0.2917 to 0.3332 0.3333 to 0.3749 0.3750 to 1.0000

456
EMOTOROLA LTD. 2001
Issue 11 Revision 0
FER_QUALITY
bad frames vs all frames CHAN CODERS HDPC LOOK UP TABLE
Normal Distribution
FER_QUALITY PEG
0
NET03_Ch4_27

EMOTOROLA LTD. 2001
457
Residual Bit Error Rate (RBER)
Issue 11 Revision 0

Residual Bit Error Rate Quality (RBER_QUAL) is a normal distribution statistic having 8 bins which records a quality number between 0 and 7 on a traffic channel timeslot. The quality number is obtained via a lookup table from the measurement of a ratio of number of bits in error to the number of bits received within errordetected speech frames defined as GOOD on the air interface uplink . The statistic is pegged within the HDPC process of the Radio Sub System every 480 ms. The ratio calculated is taken from the 24 x 20 ms vocoded speech frames received and decoded during a 480ms SACCH multiframe after the frames have been received, demodulated, deinterleaved and decoded by the Channel Coder devices. The RBER Quality number is derived from the following relational lookup table: RBER Quality Number Conversion RBER Quality Number 0 1 2 3 4 5 6 7 RBER Ratio (min to max) 0 to 0.2 0.2 to 0.4 0.4 to 0.8 0.8 to 1.6 1.6 to 3.2 3.2 to 6.4 6.4 to 12.8 12.8 and greater
The statistic is used for trend analysis for target optimization effects on cell/radios with regards to quality.

458
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RBER
Error bits vs total bits CHAN CODERS HDPC LOOK UP TABLE
Cumulative score
2800 2400 2000 1600 1200 800 400 0
RBER_QUALITY
PEG
0
NET03_04_28

EMOTOROLA LTD. 2001
459
Call Establishment Exercise
Issue 11 Revision 0

The interprocess message shown opposite has resulted in an MS being able to establish on a TCH. Insert the incremented statistics at the appropriate software process at each stage of the establishment.

460
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSS MS
Channel request
L1
Channel request
ABIS
Channel required
RRSM
CRM
SM
SSM
MSC
RSS
Channel activation Channel activation acknowledge
Channel required received Channel assigned
4 SDCCHs are available
Immediate assignment L2 SABM Establish indication Initial L3 information CM Service request <CR> Complete L3 information <CC>
CM service request
L3 CALL SET UP MESSAGES

Assignment request Initiate assignment
Assignment resource
request
3 TCHs available
ACTIVATION
Assignment command
Assignment channel assigned
Assignment complete Assignment successful

Connection request
Switch response success Assignment complete

NET03_Ch4_29

EMOTOROLA LTD. 2001
461
Issue 11 Revision 0

462
EMOTOROLA LTD. 2001
Chapter 5
Handover Statistics

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 5 Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-cell handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS handover statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internal/External . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IntraCell Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-Cell Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful Intra-BSS Handover Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intra-BSS Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outgoing Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming Intra-BSS Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bad Handover Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Inter-BSS Handover Failure Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outgoing External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Incoming External Handover Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking Handover Failures Due to no Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Neighbour Cell Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
51 51 52 52 52 52 52 54 56 510 514 516 520 522 528 530 532 534 542 546 548 550 552 552 553

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Handover Statistics
Handover Statistics
Objectives
On completion of this chapter the student will be able to: S S Name the three handover statistics groups. Indicate where each handover statistic is incremented given related ladder diagrams and the W56 manual.

EMOTOROLA LTD. 2001
51
Introduction
Issue 11 Revision 0
Introduction
The statistics generated during handovers will now be considered. There are three distinct handover types, these are detailed below:
Intra-cell handover statistics.

An intra-cell handover occurs when an MS is transferred from one channel to another within a cell. This type of handover is normally controlled by the BSC.
Intra-BSS handover statistics.

This type of handover involves an MS being transferred from one cell to another, when both cells are being controlled by the same BSC. This type of handover is generally controlled by the BSC although for reasons of subscription or potential congestion can be controlled by the MSC.
Inter-BSS handover statistics.

This type of handover involves an MS being transferred from one cell to another, when the target cell is controlled by a different BSC to that of the source cell. This type of handover is alway controlled by the MSC.
Internal/External
Further to the above definitions there are also two categories of handover to consider. Internal handovers are those controlled by the BSC, in general these will be intra-cell or intra-BSS. External handovers are those controlled by the MSC, these will normally be inter-BSS. It is worth noting that both intra-cell and intra-BSS could be controlled by the MSC, depending upon database parameters resident in the SSM. In these cases the handover will be considered external and will increment only the inter-BSS handover statistics. An operator may wish the MSC to control certain handovers, the advantages of this include consideration of congestion, handover queueing at the BSS and handovers related to subscription.

52
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
Handover Statistics
MSC
BSC
BSC
BTS
BTS
BTS
BTS
INTRABSS HANDOVER
INTERBSS HANDOVER
INTRACELL HANDOVER
NET03_Ch5_01

EMOTOROLA LTD. 2001
53
Handover Initiation
Issue 11 Revision 0
Handover Initiation
The RSS will initiate the handover sequence when the HDPC sends a handover recognized message to the RRSM. This message will contain a cause value plus a number of qualified neighbours for a specified connection. The RRSM will transfer this message as a handover recognized received message to the SSM. Upon receipt of this message the BSC must decide the type of handover that should take place for this connection, one of intra-cell, intra-BSS or inter-BSS and also the entity that shall control the handover either, the BSC or the MSC. The type of handover can be influenced by the cause value and also the neighbour types, internal or external, being expressed in the message. If the list of targets contain no neighbours then this can also affect the handover type. The decision as to the controlling entity will be influenced upon two database parameters found in add_cell, intra_cell_handover_allowed and inter_cell_handover_allowed . Inter-BSS handovers, if permitted, will always be controlled by the MSC.

54
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Handover Initiation
Handover Initiation
RSS
HDPC RRSM SSM
Handover recognised
<CAUSE> plus neighbours <N1><N2><N3>...
Handover recognized received
NET03_Ch5_02

EMOTOROLA LTD. 2001
55
Intra-Cell Handover Statistics
Issue 11 Revision 0

An example of a successful intra-cell handover sequence is shown opposite. Intra-cell handovers will only be considered by the SSM if the cause value is one of interference ul or dl. The detection of interference handovers has to be enabled in add_cell along with the SSM element intra_cell_handover_allowed . When the cause value is interference the SSM will always attempt an intra-cell handover first only if this is blocked will any specified targets be considered.
INTRA_CELL_HO_REQ
This counter statistic is incremented in the SSM each time an intra-cell handover is considered the best option by the handover evaluator process. The statistic is pegged just before sending the initiate intra- cell handover message to the CRM. The value is held in a bin of the counter array INTRA_CELL_HO.
INTRA_CELL_HO_ATMPT
This counter statistic is incremented in the RRSM after the channel activation message is received from the RSS and just before the assignment command is sent to the MS. Its value is held at the SSM in a bin of the counter array INTRA_CELL_HO.
MA_CMD_TO_MS
This statistic was covered in the previous section, but it is worth noting that it is incremented each time an assignment command is sent to the MS, which of course also includes intra-cell handovers.
INTRA_CELL_HO_SUC
This counter statistic is incremented in the SSM each time a handover performed message is sent to the MSC due to an intra-cell handover. Its value is held in a bin of the counter array INTRA_CELL_HO.
INTRA_BSS_HO_CAUSE_SUC
This tracks the number of handovers in a BSS on a per cause basis. It is a counter array with the same bins defined as OUT_HO_NC_CAUSE_ATMPT, but pegs when the handover performed message is sent to the MSC to indicate that a successful handover has occurred.
ER_INTRA_CELL_HO_ATMPT
This is a small counter array that tracks intra-cell handover attempts between extended and normal range channels in either direction. It is pegged at the SSM whenever the handover evaluator decides that an extended range intra-cell handover is the best option for the call. It is also important to note that this is the only statistic pegged for an extended range intra-cell handover; no other intra-cell handover statistic is pegged under these circumstances.

56
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Intra-cell Handover Sequence
RSS
ho_recognised
RRSM
ho_rec received
SSM
SSM decides intracell pegs: INTRA_CELL_HO_REQ may peg: ER_INTRA_CELL_HO_ATMPT ZONE_CHANGE_ATMPT Transfer request Switch response
CRM
Initiate intra cell handover Internal ho assignment Internal ho initated Internal ho initiated ack
SM
Internal ho assignment ack Physical context request Physical context confirm Channel activation Channel activation ack
INTRA_CELL_HO_ATMPT MA_CMD_TO_MS
MS
Assignment cmd (FACCH) SABM UA
Assignment cmd
may peg: ER_INTRA_CELL_HO_SUC ZONE_CHANGE_SUC
MSC
Establish indication Assignment successful
Assignment complete (FACCH
ho perf INTRA_CELL_HO_SUC INTRA_BSS_HO_CAUSE_SUC
NET03_Ch5_03

EMOTOROLA LTD. 2001
57
Issue 11 Revision 0
ER_INTRA_CELL_HO_SUC
This small counter array tracks successful intra-cell handovers between extended and normal range channels. It is pegged at the SSM when the assignment_successful message is received.
ZONE_CHANGE_ATMPT
This counter statistic is pegged at the SSM whenever a zone change is attempted in a concentric cell. If the zone change is successful then ZONE_CHANGE_SUC is also pegged when the assignment_successful message arrives. Both peg under the following circumstances: S S S S S Inner to outer zone handover. Outer to inner zone handover. Handovers between different carriers in the inner zone. TCH assignment to the inner zone. Incoming inter-cell handovers directly into the inner zone.

58
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Intra-cell Handover Sequence
RSS
ho_recognised
RRSM
ho_rec received
SSM
SSM decides intracell pegs: INTRA_CELL_HO_REQ may peg: ER_INTRA_CELL_HO_ATMPT ZONE_CHANGE_ATMPT Transfer request Switch response
CRM
Initiate intra cell ho Internal ho assignment Internal ho initated Internal ho initiated ack
SM
Internal ho assignment ack Physical context request Physical context confirm Channel activation Channel activation ack
INTRA_CELL_HO_ATMPT MA_CMD_TO_MS
MS
Assignment cmd (FACCH) SABM UA
Assignment cmd Establish indication
may peg: ER_INTRA_CELL_HO_SUC ZONE_CHANGE_SUC
MSC
Assignment complete (FACCH)
ho perf INTRA_CELL_HO_SUC INTRA_BSS_HO_CAUSE_SUC
NET03_Ch5_04

EMOTOROLA LTD. 2001
59
IntraCell Handover Failure Scenarios
Issue 11 Revision 0

INTRA_CELL_HO_RETURN
Upon receipt of the assignment command the MS will essentially attempt to gain L2 establishment with the new TCH, if this attempt is not possible due to an incorrectly formatted or erroneous assignment command then the MS will send the assignment failure message in the old TCH. When the MS does attempt to gain a connection with the new TCH but fails due establishment problems or if establishment is not gained within a certain time, the MS will return to the old TCH and transmit the assignment failure message. This information is passed to the SSM as an unsuccessful assignment, which internally generates a revert to old channel message. At this moment this statistic is incremented. Its value is held in a bin of the counter array INTRA_CELL_HO.
MA_CMD_TO_MS_BLOCKED
Although this statistic is already covered in the previous section it is worth noting that it is also incremented in the case of resources not available for an intracell handover.
MA_FAIL_FROM_MS
This statistic is also covered in the previous section and again it is worth noting that an intra-cell handover resulting in an assignment failure message will increment this statistic.
INTRA_CELL_EQUIP_FAIL
If the assignment failure contains the cause equipment failure or if the Switch Manager (SM) reports a KSW/highway fault in the switch response message, then the handover can be said to have failed due to equipment failure. This increments the INTRA_CELL_EQUIP_FAIL bin of the INTRA_CELL_HO counter array statistic.
HO_FAIL_NO_RESOURCES
This is pegged every time the target CRM of a handover cannot allocate resources. It is a counter array and tracks all handover types.
INTRA_CELL_HO_CLEARED
This bin of INTRA_CELL_HO is pegged every time a call is cleared down during an intra_cell handover

510
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Failed Intra-Cell Handover
MS
Assignment failure
RRSM SSM
Pegs: MA_FAIL_FROM_MS Unsuccessful assignment INTRA_CELL_HO_RETURN INTRA_CELL_EQUIP_FAIL
Blocked IntraCell Handover

CRM
Initiate intracell handover
SSM
Handover resource not available HO_FAIL_NO_RESOURCES ALLOC_TCH_F AIL ALLOC_SDCCH_F AIL
NET03_Ch5_05

EMOTOROLA LTD. 2001
511
Issue 11 Revision 0
INTRA_CELL_HO_LOSTMS
Upon sending the assignment command the RRSM will start an internal timer, t10 (BSSMAP_t10). If this timer is allowed to expire and no assignment complete or assignment failure is received the RRSM will release both the old and new channels and simultaneously send the SSM a radio channel released message. Upon receipt of this message the SSM will clear the connection and increment this statistic. Its value is held in a bin of the counter array INTRA_CELL_HO.

512
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Mobile Lost
MS
RRSM
t10 Assignment command
Expiry
No assignment complete or assignment failure t10
SSM
Expired Radio channel released Pegs: INTRA_CELL_HO_L OSTMS CLR_REQ_TO_MSC
NET03_Ch5_06

EMOTOROLA LTD. 2001
513
Intra-Cell Handover Tracking
Issue 11 Revision 0

Several statistics that apply to intra-cell handovers are rolled up into a single counter array statistic, INTRA_CELL_HO. Each statistic is held in a bin of the array as shown below, and can only be displayed as part of the array, not individually: BIN 0 = INTRA_CELL_HO_REQ 1 = INTRA_CELL_HO_ATMPT 2 = INTRA_CELL_HO_SUC 3 = INTRA_CELL_HO_LOSTMS 4 = INTRA_CELL_HO_RETURN 5 = INTRA_CELL_EQUIP_FAIL 6 = INTRA_CELL_HO_CLEARED

514
EMOTOROLA LTD. 2001
Issue 11 Revision 0
INTRA_CELL_HO
BIN 0 1 2 3 4 5 6 = = = = = = = INTRA_CELL_HO_REQ INTRA_CELL_HO_ATMPT INTRA_CELL_HO_SUC INTRA_CELL_HO_LOSTMS INTRA_CELL_HO_RETURN INTRA_CELL_EQUIP_FAIL INTRA_CELL_HO_CLEARED
NET03_Ch5_07

EMOTOROLA LTD. 2001
515
Intra-BSS Handover Statistics
Issue 11 Revision 0

An example of a successful intra-BSS handover sequence is shown opposite.
OUT_INTRA_BSS_HO_REQ
This counter statistic is pegged each time the SSM decides to commit an intra-BSS handover. The SSM will only allow an intra-BSS handover if the SSM element inter_cell_handover_allowed is enabled in the correct way. Primarily the SSM will decide on an intra-BSS handover if the first neighbour specified in the handover recognized message is internal. Its value is held in a bin of OUT_INTRA_BSS_HO.
IN_INTRA_BSS_NC_ATMPT
This statistic is incremented after handover allocation is received from the target RRSM. It is pegged on a neighbour basis in that it is incremented in the target cell against a specific source. The procedure that follows involves the SSM requesting resources from the target CRM, the CRM allocates the resource and informs the target RRSM which in turn activates the new TCH via the RSS. Upon completion of this activation the RRSM will acknowledge the original internal handover request with a handover allocation message, this provides the SSM with the characteristics of the new TCH which now awaits the MSs arrival.

516
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Intra-BSS Handover Sequence
RSS (S) RRSM (S)

ho_rec ho_rec received
SSM
Internal handover request OUT_INTRA_BSS_HO_REQ Source cell (when SSM decides IN (pegged for target ) intra-BSS is best) OUT (pegged for source) NC per neighbour
CRM (T) RSS(t)
RRSM (t) ho_channel assigned Channel act Channel act ack MS power control Handover allocation
IN_INTRA_BS S_NC_ATMPT
MS
SSM Initiate handover ho_cmd ho_cmd OUT_INTRA_BSS_HO_ATMPT OUT_HO_CAUSE_ATMPT PT <FACCH> RSS(t) INTERBAND_ACTIVITY ho_access <FACCH> RRSM(t) ho_access ho_access SM ho_access ho_detection ho_detect received Phys info Trans req SABM Switch resp Establish indication UA MTP ho_cmplt ho_cmplt ho_succ ho_performed IN_INTRA_BSS_HO_SUC OUT_INTRA_BSS_HO_SUC IN_INTRA_BSS_NC_SUC OUT_HO_NC_SUC INTRA_BSS_HO_CAUSE_SUC
RSS (S) RRSM (S)
NET03_Ch5_08

EMOTOROLA LTD. 2001
517
Issue 11 Revision 0
OUT_INTRA_BSS_HO_ATMPT
The SSM will initiate the transfer of the MS to the target resource specified in the handover allocation message received from the target RRSM, by sending the initiate handover message. Upon sending this message this counter statistic is incremented for the source cell. Its value is held in a bin of OUT_INTRA_BSS_HO.
OUT_HO_NC_CAUSE_ATMPT
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in the source relative to a neighbour and a specified cause value. In the internal case this statistic is incremented at the same time as the one above, when the initiate handover message is sent to the source RRSM. This statistic utilises a counter array containing the following bin definitions: Bin 0 1 2 3 4 5 6 7 8 9 10 11 Cause UPQUAL UPLEVEL DOWNQUAL DOWNLEVEL DISTANCE UPINTERF DOWNINTERF POWERBDGT CONGESTION ADJ_CHAN_INTF BAND_RE_ASSIGN BAND_HANDOVER Description Handovers due to uplink quality. Handovers due to uplink level. Handovers due to downlink quality. Handovers due to downlink level. Handovers due to distance. Handovers due to uplink interference. Handovers due to downlink interference. Handovers due to power budget. Handovers due to congestion. Handovers due to adjacent channel interference. Handovers due to band reassignment. Handovers between bands.
The cause value for congestion includes standard directed retry and both congestion relief mechanisms.
OUT_HO_CAUSE_ATMPT
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is very similar to the statistic above and indeed is incremented at the same time. The difference is that this statistic is not incremented on a neighbour basis and merely shows the total number of attempted handovers out of the source cell with a breakdown per cause value. The counter array values are the same as those shown above.
INTERBAND_ACTIVITY
This counter array statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It counts the number of handovers initiated to each frequency band (PGSM, EGSM, DCS1800 and DCS2000), but is also pegged when a multiband handover fails due to incorrect frequency information.

518
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSS (S)
ho_rec
RRSM (S)
ho_rec received
SSM
OUT_INTRA_BSS_HO_REQ
CRM (T)
Internal handover request
RRSM (t) RSS(t)

ho_channel assigned Channel act Channel act ack MS power control Handover allocation
IN (pegged for target ) OUT (pegged for source) NC per neighbour
IN_INTRA_BSS_NC_ATMPT
NET03_Ch5_09

EMOTOROLA LTD. 2001
519
Issue 11 Revision 0

Upon receipt of the initiate handover message the RRSM will format the air-interface handover command, this is sent via the RSS to the MS. The command is delivered on the Fast Associated Control Channel (FACCH) , and provides the MS with details of the target TCH, these details will include characteristics such as the time slot, frequency, Training Sequence Code (TSC), handover reference number and an indication of synchronization. The MS will alter its air-interface characteristics and will attempt gain firstly a L1 then a L2 connection with the target RSS. The procedure shown opposite assumes the handover is asynchronous, and thus the MS transmits a continuous flow of L1 access bursts until it receives the physical information message (containing timing advance information) when it will then attempt L2 establishment. In the synchronized case where the MS has been able to calculate the relevant timing advance necessary, a physical information message is not necessary, the MS will send 4 consecutive L1 access bursts before attempting L2 establishment. When the target RSS detects the MS at Layer 1 it will report this event to the RRSM which in turn reports to the SSM. The detection procedure allows the SSM time to control the relevant switch transfer. When the MS has gained L2 establishment with the RSS it will send a L3 handover complete message which is passed to the SSM as a handover succesful message. Upon receipt of this the SSM will format and send a handover performed message to the MSC. After the SSM has transmitted this message a number of statistics are incremented.
IN_INTRA_BSS_HO_SUC
This statistic is pegged for the target cell and is not source cell related.
OUT_INTRA_BSS_HO_SUC
This statistic is incremented in the source cell only and is not target cell related.
IN_INTRA_BSS_NC_SUC
This statistic is incremented in the target cell in respect of a specified source.
OUT_HO_NC_SUC
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in the source cell relative to a specified neighbour. In the internal case this statistic is incremented at the same time as those above. It is pegged each time a successful handover message is received from the target RRSM resulting in a handover performed message being sent to the MSC.
INTRA_BSS_HO_CAUSE_SUC
This tracks the number of handovers in a BSS on a per cause basis. It is a counter array with the same bins defined as OUT_HO_NC_CAUSE_ATMPT, but pegs when the handover performed message is sent to the MSC to indicate that a successful handover has occurred.

520
EMOTOROLA LTD. 2001
Issue 11 Revision 0

MS RSS (S)
ho_cmd <FACCH>
RRSM (S)
Initiate handover
SSM
OUT_INTRA_BSS_HO_ATMPT OUT_HO_NC_CAUSE_ATMPT OUT_HO_CAUSE_ATMPT INTERBAND_ACTIVITY
ho_cmd
RSS(t)
ho_access <FACCH> ho_access ho_access ho_access ho_detection ho_detect received Phys info SABM Establish indication UA ho_cmplt ho_cmplt ho_succ
RRSM(t)
SM
Trans req Switch resp
MTP
ho_performed IN_INTRA_BS _HO_SUC S OUT_INTRA_BSS_HO_SUC IN_INTRA_BSS_NC_SUC OUT_HO_NC_SUC INTRA_BSS_HO_CAUSE_SUC
NET03_Ch5_10

EMOTOROLA LTD. 2001
521
Intra-BSS Handover Failure Scenarios
Issue 11 Revision 0

OUT_INTRA_BSS_HO_PRI_BLK
Upon receipt of the handover recognized received message from the source RRSM the SSM will determine the handover type, if an intra-BSS handover is necessary then resources are requested from the CRM of the primary target. The primary target is the neighbour cell in the first position of the handover recognized message, the RSS orders the neighbours best to worst generally based on RF suitability. Should these resources be unavailable the CRM will return with the handover resources not available message. Queueing is not allowed in the case of an intra-BSS handover. Upon receiving this message the SSM will increment this statistic. The SSM will only increment this statistic in the case of the primary (first) target being blocked. Subsequent targets (if available in the handover recognized message) may be tried and also blocked, these further attempts will not peg this statistic. Its value is held in a bin of OUT_INTRA_BSS_HO.
This is pegged every time the target CRM of a handover cannot allocate resources. It is a counter array and tracks all handover types.

522
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Intra-BSS Handover Blocked
Source RRSM
Handover recognized received
SSM
Target CRM
Handover resources not available Increments: OUT_INTRA_BSS_HO_PRI_BLK
NET03_Ch5_11

EMOTOROLA LTD. 2001
523
Issue 11 Revision 0
At the moment the SSM transmits the initiate handover message to the source RRSM it starts an internal timer running, the timer is called T3103 in GSM and Motorolas designation is rr_t3103. In the successful case the SSM will receive a handover successful message from the target RRSM before the expiry of the timer. Upon receipt of the handover command the MS will alter its characteristics and attempt to gain L1 establishment with the target RSS. In the asynchronous case the MS will start an internal timer, T3124, and send a continuous flow of handover access bursts until a physical information message is returned. If T3124 should expire and no physical information has been received or if a lower layer failure happens before the handover complete message is sent then the MS will deactivate the new channel and return to the old TCH.
OUT_INTRA_BSS_HO_RETURN
Upon returning to the old TCH the MS will send a handover failure message, this message has a number of cause values as specified in GSM TS 04.08. The source RRSM will translate this message to an unsuccessful handover message and send it to the SSM. Upon receipt of this message the SSM will stop timer rr_t3103 and increment this statistic for the source cell. Its value is held in a bin of OUT_INTRA_BSS_HO.
OUT_INTRA_BSS_EQUIP_FAIL
If the handover failure message contains the cause equipment failure or the SM reports a KSW/highway problem in the switch response message, then the handover can be said to have failed due to equipment failure. This statistic is incremented in a bit of OUT_INTRA_BSS_HO.
IN_INTRA_BSS_HO_RETURN
This statistic is pegged as for OUT_INTRA_BSS_HO_RETURN but is updated with respect to the target cell. It is a bin of IN_INTRA_BSS_HO.
IN_INTRA_BSS_EQUIP_FAIL
This statistic is pegged as for OUT_INTRA_BSS_EQUIP_FAIL but is updated with respect to the target cell. It is a bin of IN_INTRA_BSS_HO.

524
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Handover Failure
MS
Source RRSM
SSM
Initiate handover Handover command
rr_t3103
Expiry rr_t3103
Handover failure Unsuccessful handover
Expiry
INTERBAND_ACTIVITY OUT_INTRA_BSS_HO_RETURN OUT_INTRA_BSS_EQUIP_FAIL IN_INTRA_BSS_HO_RETURN IN_INTRA_BSS_EQUIP_FAIL
NET03_Ch5_12

EMOTOROLA LTD. 2001
525
Issue 11 Revision 0
At the moment the SSM transmits the initiate handover message to the source RRSM it starts an internal timer running, the timer is called T3103 in GSM and Motorolas designation is rr_t3103. In the successful case the SSM will receive a handover successful message from the target RRSM before the expiry of the timer. Upon receipt of the handover command the MS will alter its characteristics and attempt to gain L1 establishment with the target RSS. In the asynchronous case the MS will start an internal timer, t3124, and send a continuous flow of handover access bursts until a physical information message is returned. If T3124 should expire and no physical information has been received or if a lower layer failure happens before the handover complete message is sent then the MS will deactivate the new channel and return to the old TCH.
OUT_INTRA_BSS_HO_CLEARED
This bin of OUT_INTRA_BSS_HO pegs if a call is cleared down during an intra BSS handover.
IN_INTRA_BSS_HO_CLEARED
This bin of IN_INTRA_BSS_HO pegs if a call is cleared down during an intra BSS handover.

526
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Mobile Lost
Target RSS
Channel act acknowledge
Target RRSM
HO_COMPLETE
SSM
Expiry Handover allocation
MS
Handover command
Source RRSM
rr_t3103 Initiate handover T8 Expiry
Target RRSM
Expiry HO_COMPLETE Expired Radio channel released
T8
Source RRSM
Radio channel released
rr_t3103
Expired Expired Clear request OUT_INTRA_BSS_HO_LOSTMS CLR_REQ_TO_MSC
NET03_Ch5_13

EMOTOROLA LTD. 2001
527
Outgoing Intra-BSS Handover Tracking
Issue 11 Revision 0

Several statistics that apply to outgoing intra BSS handovers are rolled up into a single counter array statistic, OUT_INTRA_BSS_HO. Each is held in a bin of the array as shown below and can only be displayed as part of the array, not individually. All are pegged at the SSM. BIN 0 = OUT_INTRA_BSS_HO_REQ 1 = OUT_INTRA_BSS_HO_PRI_BLK 2 = OUT_INTRA_BSS_HO_ATMPT 3 = OUT_INTRA_BSS_HO_SUC 4 = OUT_INTRA_BSS_HO_LOSTMS 5 = OUT_INTRA_BSS_HO_RETURN 6 = OUT_INTRA_BSS_EQUIP_FAIL 7 = OUT_INTRA_BSS_HO_CLEARED

528
EMOTOROLA LTD. 2001
Issue 11 Revision 0
OUT_INTRA_BSS_HO
BIN 0= 1= 2= 3= 4= 5= 6= 7 = OUT_INTRA_BSS_HO_REQ OUT_INTRA_BSS_HO_PRI_BLK OUT_INTRA_BSS_HO_ATMPT OUT_INTRA_BSS_HO_SUC OUT_INTRA_BSS_HO_LOSTMS OUT_INTRA_BSS_HO_RETURN OUT_INTRA_BSS_EQUIP_FAIL OUT_INTRA_BSS_HO_CLEARED
NET03_Ch5_14

EMOTOROLA LTD. 2001
529
Incoming Intra-BSS Handover Tracking
Issue 11 Revision 0

Several statistics associated with incoming internal handovers are rolled up into a single counter array, IN_INTRA_BSS_HO. Each is held in a bin of the array as shown below, and can only be displayed as part of the array, not individually. All are pegged at the SSM. BIN 0 = IN_INTRA_BSS_HO_SUC 1 = IN_INTRA_BSS_MS_NO_SEIZE 2 = IN_INTRA_BSS_EQUIP_FAIL 3 = IN_INTRA_BSS_HO_RETURN 4 = IN_INTRA_BSS_HO_CLEARED

530
EMOTOROLA LTD. 2001
Issue 11 Revision 0
IN_INTRA_BSS_HO
BIN 0= 1= 2= 3= 4 = IN_INTRA_BSS_HO_SUC IN_INTRA_BSS_MS_NO_SEIZE IN_INTRA_BSS_EQUIP_FAIL IN_INTRA_BSS_HO_RETURN IN INTRA_BSS_HO_CLEARED
NET03_Ch5_15

EMOTOROLA LTD. 2001
531
Bad Handover Reference Number
Issue 11 Revision 0

In both the intra-BSS and inter-BSS handover a reference number is used by MS and BSS for the correct operation of handover detection. Taking the intra-BSS case as an example of this, when the SSM requests resources from the target cell, the CRM will randomly generate an 8-bit handover reference number. The number will be passed in Layer 3 information to the SSM and in turn passed to the MS in the handover command. The MS will transmit this number to the target cell within the handover access burst. The target channel coder, which knows the correct handover reference number to be used will check handover bursts arriving in the specified time slot to ensure the numbers match. Only when the handover access burst is correctly decoded will the handover reference number be checked by the Channel Coder (CC). When a handover access burst is decoded and the reference number is correct the whole message is passed to the RSS with a count of the Bad handover reference numbers received by the CC. This statistic is incremented by that number.

532
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Target CRM
SSM
ho channel assigned
Target RRSM
CHANNEL ACT
MS
ho_cmd
Source RSS
Source RRSM
ho_cmd
Handoverallocation Initiate handover
CC
Handover access burst
TARGET RSS L1
Target RRSM
Handover access Physical information
BAD_HO_REFNUM_MS ho_detection ho_detect received
NET03_Ch5_16

EMOTOROLA LTD. 2001
533
Inter-BSS Handover Statistics
Issue 11 Revision 0

An example of a successful inter-BSS handover sequence is shown opposite.
OUT_INTER_BSS_REQ_TO_MSC
This counter statistic is pegged each time the SSM sends a handover required message to the MSC, in a bin of OUT_INTER_BSS_HO. This would generally indicate that the SSM had decided that an external handover was necessary, however the SSM may refer the control of all handovers including internal to the MSC, this decision will be dependent upon the value of the SSM database element, inter_cell_handover_allowed . The SSM will generally decide on an external handover if the first neighbour specified in the handover recognize message is external. Depending upon the complexity of the switch handover algorithm the MSC will initiate the handover request procedure to the first neighbour specified in the handover required message. This procedure involves the establishment of an SCCP connection and piggy-backed on this CR will be the handover request message. This message specifies such details as the type of resource required, encryption information, classmark information, downlink Discontinuous Transmission (DTX) instructions and also an indication of the MSCBSC trunk to be utilized. The sequence of events that follow include the air-interface activation of the new TCH along with the necessary cross-connect being established by the SM.
HO_REQ_MSC_OK
The SCCP CC is then returned to the MSC containing the handover request acknowledge message. This message will contain specific channel charateristics which will, for the most part, be passed to the MS concerned. When this message is sent to the MSC the target SSM will increment this counter statistic.

534
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Inter-BSS Handover Sequence
SOURCE
MS RSS RRSM
ho_rec ho_recreceived
TARGET
SSM MSC SSM CRM RRSM RSS
ho required <cc> Handover request Handover request ho channel assigned
Channel act Channel act acknowledge
OUT_INTER_BS S_REQ_TO_MSC
SM
Handover allocation
Conn req
Initiate ho Handover cmd
Handover cmd
Switch resp <cc> Handover req HO_REQ_MSC_OK acknowledge
OUT_INTER_BSS_HO_ATMPT OUT_HO_NC_CA USE_ATMPT OUT_HO_CA USE_ATMPT
RRSM
RSS
MS
ho access FACCH ho_detect ho_detect received ho_detect ho_successful IN_INTER_BSS_HO_SUC Establish ind Phys info SABM
ho_cmplt
Clear command
ho_cmplt
OUT_INTER_BSS_HO_SUC
NET03_Ch5_17

EMOTOROLA LTD. 2001
535
Issue 11 Revision 0

536
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Inter BSS Handover Sequence
SOURCE
MS RSS RRSM SSM
ho required
TARGET
MSC SSM CRM RRSM
ho_rec
ho_reqreceived <cc>Handover request Handover request
OUT_INTER_BSS_REQ_TO_MSC
ho channel assigned
Channel act
Channel act acknowledge
SM
Conn req
Handover allocation
Switch response <cc> Handover req HO_REQ_MSC_OK acknowledge Handover cmd Initiate ho Handover cmd OUT_INTER_BSS_HO_ATMPT OUT_HO_NC_CAUSE_ATMPT OUT_HO_CAUSE_ATMPT
NET03_Ch5_18

EMOTOROLA LTD. 2001
537
Issue 11 Revision 0
OUT_INTER_BSS_HO_ATMPT
Upon receipt of the handover request acknowledge message the MSC will initiate the handover by formatting and sending the handover command to the source SSM. When the source SSM receives this message and subsequently forwards it to the MS this statistic is incremented and stored in a bin of OUT_INTER_BSS_HO_ATMPT.
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in the source relative to a neighbour and a specified cause value. In the external case this statistic is incremented at the same time as the one above, when the SSM receives the handover command from the MSC and subsequently forwards it to the MS. This statistic utilizes a counter array containing the following bin definitions: Bin 0 1 2 3 4 5 6 7 8 9 10 11 Cause UPQUAL UPLEVEL DOWNQUAL DOWNLEVEL DISTANCE UPINTERF DOWNINTERF POWERBDGT CONGESTION ADJ_CHAN_INTF BAND_RE_ASSIGN BAND_HANDOVER Description Handovers due to uplink quality. Handovers due to uplink level. Handovers due to downlink quality. Handovers due to downlink level. Handovers due to distance. Handovers due to uplink interference. Handovers due to downlink interference. Handovers due to power budget. Handovers due to congestion. Handovers due to adjacent channel interference. Handovers due to band reassignment. Handovers between bands.
The cause value for congestion includes standard directed retry and both congestion relief mechanisms.
OUT_HO_CAUSE_ATMPT
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is very similar to the statistic above and indeed is incremented at the same time. The difference is that this statistic is not incremented on a neighbour basis and merely shows the total number of attempted handovers out of the source cell with a breakdown per cause value. The counter array values are the same as those shown above.

538
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SOURCE
MS RRSM SSM MSC
Handover cmd Initiate ho Handover cmd OUT_INTER_BSS_HO_ATMPT OUT_HO_NC_CA USE_ATMPT OUT_HO_CAUSE_ATMPT
TARGET
SSM RRSM RSS
RSS
MS
ho_access FACCH
ho_detect ho_detect received Phys info SABM ho_detect Establish ind ho_cmplt ho_successful ho_cmplt Clear command OUT_INTER_BSS_HO_SUC IN_INTER_BSS_HO_SUC
ET03_Ch5_19

EMOTOROLA LTD. 2001
539
Issue 11 Revision 0
Once the MS receives the handover command it will change its characteristics and try to gain, initially L1, and then L2 establishment on the new TCH wth the target RSS. The BSS will inform the MSC when the MS has been detected at L1, this will give the MSC advance warning of the handover complete and will allow time for the MSC to switch terrestrial connections. After L2 establishment on the air interface the MS will send the L3 handover complete message, the RRSM will forward this to the SSM as the handover successful message.
IN_INTER_BSS_HO_SUC
The SSM will inform the MSC of a successful handover by sending the handover complete, each time this message is sent this statistic is incremented. For this statistic to be incremented the source cell must be external. The value is held in a bin of IN_INTER_BSS_HO.
OUT_INTER_BSS_HO_SUC
To complete the handover procedure the source TCH must be deactivated, this is initiated by the MSC by sending a clear command to the source SSM. Each time this message is received by the SSM with a cause value indicating a successful handover to an external neighbour this counter statistic is incremented. The value is held in a bin of OUT_INTER_BSS_HO.
OUT_HO_NC_SUC
This statistic is incremented in the SSM for both intra-BSS and inter-BSS cases. It is pegged in the source cell relative to a specified neighbour. In the external case this statistic is incremented at the same time as the one above, when the clear command is received from the MSC with the cause successful handover.

540
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RRSM SSM MSC
RSS
ho_access FACCH
MS
ho_detect ho_detect received Phys info SABM Establish ind ho_cmplt ho_successful ho_cmplt Clear command IN_INTER_BSS_HO_SUC
ho_detect
SSM
OUT_HO_NC_SUC OUT_INTER_BSS_HO_SUC
NET03_Ch5_20

EMOTOROLA LTD. 2001
541
Inter-BSS Handover Failure Scenarios
Issue 11 Revision 0

HO_REQ_MSC_FAIL
This counter statistic can be incremented in the source or the target SSM, depending upon where the failure occurs. It is incremented when the SSM sends the MSC the handover failure message. This message has many different cause values and hence a number of associated handover failure scenarios, the only cause value that does not increment this statistic specifies no radio resources available in the target. In the source cell this statistic is primarily incremented when the SSM receives an indication as to handover failure originating from the MS, this indicates that the MS has reverted to the old channel. A handover failure message originating from the target SSM will do so at the handover resource allocation stage and could indicate one of a number of problems examples include terrestrial circuit unavailable, terrestrial circuit in use and cyphering algorithm not supported.

542
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Handover Failure
MSC
TARGET SSM
<CR> Handover request
<CREF> Handover failure
HO_REQ_MSC_FAIL
NET03_Ch5_21

EMOTOROLA LTD. 2001
543
Issue 11 Revision 0
OUT_INTER_BSS_HO_RETURN
This counter statistic is incremented in the source SSM each time an unsuccessful handover message is received form the RRSM when the target cell is external.
OUT_INTER_BSS_EQUIP_FAIL
This is incremented in a bin of OUT_INTER_BSS_HO if the MS returns a cause of equipment failure in the handover failure message.
OUT_INTER_BSS_EQUIP_CLEARED
This is pegged in a bin of OUT_INTER_BSS_HO when a call is cleared down during an inter-BSS handover.
IN_INTER_BSS_EQUIP_FAIL
This is pegged at the target SSM when a handover failure message is received from the MSC. It is a bin of IN_INTER_BSS_HO.
OUT_INTER_BSS_HO_LOSTMS
This is pegged in a bin of OUT_INTER_BSS_HO if a clear command is not received from the MSC (indicating that the handover was successful) and no handover failure message is received either.
IN_INTER_BSS_MS_NO_SEIZE
This statistic is pegged at the target SSM whenever a MS fails to seize the new channel for any reason. It is a bin of IN_INTER_BSS_HO.
IN_INTER_BSS_HO_CLEARED
This bin of IN_INTER_BSS_HO is pegged when a call is cleared down whilst an inter-BSS handover is in progress.

544
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Handover Failure
MS
RRSM
Source SSM
Handover command Initiate handover
Handover command
Handover failure Unsuccessful handover Handover failure

OUT_INTER_BSS_HO_RETURN OUT_INTER_BSS_EQUIP_FAIL HO_REQ_MSC_FAIL
NET03_Ch5_22

EMOTOROLA LTD. 2001
545
Outgoing External Handover Tracking
Issue 11 Revision 0

Several statistics associated with outgoing external handovers are rolled up into a single counter array statistic, OUT_INTER_BSS_HO. Each is held in a bin of the array as shown below, and can only be displayed as part of the array, not individually. All are pegged at the source SSM. BIN 0 = OUT_INTER_BSS_REQ_TO_MSC 1 = OUT_INTER_BSS_HO_ATMPT 2 = OUT_INTER_BSS_HO_SUC 3 = OUT_INTER_BSS_HO_LOSTMS 4 = OUT_INTER_BSS_HO_RETURN 5 = OUT_INTER_BSS_EQUIP_FAIL 6 = OUT_INTER_BSS_HO_CLEARED

546
EMOTOROLA LTD. 2001
Issue 11 Revision 0
OUT_INTER_BSS_HO
BIN 0= 1= 2= 3= 4= 5= 6= OUT_INTER_BSS_REQ_TO_MSC OUT_INTER_BSS_HO_ATMPT OUT_INTER_BSS_HO_SUC OUT_INTER_BSS_HO_LOSTMS OUT_INTER_BSS_HO_RETURN OUT_INTER_BSS_EQUIP_FAIL OUT_INTER_BSS_HO_CLEARED
NET03_Ch5_23

EMOTOROLA LTD. 2001
547
Incoming External Handover Tracking
Issue 11 Revision 0

Several statistics associated with incoming external handovers are rolled up into a single counter array, IN_INTER_BSS_HO. Each is held in a bin of the array as shown below, and can only be displayed as part of the array, not individually. All are pegged at the target SSM. BIN 0 = IN_INTER_BSS_HO_SUC 1 = IN_INTER_BSS_MS_NO_SEIZE 2 = IN_INTER_BSS_EQUIP_FAIL 3 = IN_INTER_BSS_HO_CLEARED

548
EMOTOROLA LTD. 2001
Issue 11 Revision 0
IN_INTER_BSS_HO
BIN 0 = IN_INTER_BSS_HO_SUC 1 = IN_INTER_BSS_MS_NO_SEIZE 2 = IN_INTER_BSS_EQUIP_FAIL 3 = IN_INTER_BSS_HO_CLEARED
NET03_Ch5_24

EMOTOROLA LTD. 2001
549
Tracking Handover Failures Due to no Resources
Issue 11 Revision 0

The target CRM increments bins 0, 1 or 2 of the counter HO_FAIL_NO_RESOURCES whenever it cannot allocate resources because all channels are in use. Bins 3 to 5 are incremented whenever a handover fails due to a lack of terrestrial backing (i.e. Dynet) resources. It tracks internal, external and intra-cell handovers in the bins shown below: BIN 0 = INTRA-BSS 1 = INTER-BSS 2 = INTRA-CELL 3 = INTRA-BSS HANDOVER LACK OF RESOURCES 4 = INTER-BSS HANDOVER LACK OF RESOURCES 5 = INTRA-CELL HANDOVER LACK OF RESOURCES

550
EMOTOROLA LTD. 2001
Issue 11 Revision 0
BIN
0 1 2 3 4 5 = = = = = = INTRABSS INTERBSS INTRACELL INTRABSS HANDOVER LACK OF RESOURCES INTER BSS HANDOVER LACK OF RESOURCES INTRACELL HANDOVER LACK OF RESOURCES
NET03_Ch5_25

EMOTOROLA LTD. 2001
551
Neighbour Cell Statistics
Issue 11 Revision 0

Outline
When the BSS is configured to control intercell handovers, four neighbour cell handover statistics may be used to track handovers. These neighbour statistics provide detailed tracking information about the destination cell of an outgoing handover or the origination cell of an incoming handover. The following statistics can be enabled in the BSS software: IN_INTRA_BSS_NC_ATMPT IN_INTRA_BSS_NC_SUC OUT_HO_NC_CAUSE_ATMPT OUT_HO_NC_SUC Neighbour Cell statistics provide an opportunity to carry out detailed analysis of cell handover performance for a limited number of selected cells within a network. These statistics can only be enabled for 16 cells within a BSS. The cells at which each of the four statistics are enabled do not have to be the same. IN_INTRA_BSS_NC statistics. The two statistics which are incremented in the target cell (IN.....) can only be pegged for 32 different source cells. Priority is given to reciprocal neighbours first, then source cells are chosen on a increasing sequential basis using the local cell identity. A reciprocal neighbour occurs when both the source cell and the target cell have each other as a neighbour.
OUT_HO_NC statistics. The two statistics which are incremented in the source cell (OUT.....) will be pegged for up to 32 neighbours, but as this is the maximum number of SACCH neighbours permissible, no real limitation exists.
As an example, this statistic which is a 12bin array records outgoing handover causes from a selected source cell to each of up to 32 neighbour cells. It may be pegged for up to 16 source cells.

552
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Cell 116 OUT_HO_NC_CAUSE_ATMPT Cell 0 Cause Neighbour NC1 NC2 NC3 NC4 NC5 . . . . . NC32 UpQual UpLev DnQual DnLev Upinterf..
X X X Etc
X X X
X X X
X X X
X X X
NET03_Ch5_26

EMOTOROLA LTD. 2001
553
Issue 11 Revision 0

554
EMOTOROLA LTD. 2001
Chapter 6
Statistical MMI Commands

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 6 Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Enabled Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling and Disabling Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Statistical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying statistical properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Bin Ranges for Distribution Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting the Statistical Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying the interval timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Note: Clearing statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Statistical Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
61 61 62 64 66 66 66 68 610 610 610 612

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0

Objectives
On completion of this chapter the student will be able to: S S Enable and disable raw statistics. Display statistical information including: S S Parameter values which are set for specific statistics. List statistics which are currently active. Statistical data for a chosen statistical interval.
Set thresholds for alarm statistics. Initialize bin ranges for distribution statistics.

EMOTOROLA LTD. 2001
61
Displaying Enabled Statistics
Issue 11 Revision 0

The disp_enable_stat command will cause the BSS to generate a list of the currently enabled statistics for the specified argument. The argument is optional and may be omitted. If so the complete list of enabled statistics will be displayed including cell related (per cell cell id) and non-cell related. The argument used will abbreviate the list down to a specified cell or location. It is possible to specify a statistical name, if so the display will return a list of all cell/sites in the BSS where that statistic has been enabled. For examples of this display command check the W56 manual.

62
EMOTOROLA LTD. 2001
Issue 11 Revision 0
disp_enable_stat [ * ] * <cell_number> <cell_name> <bss> <meas_type> <location>
NET03_Ch6_01

EMOTOROLA LTD. 2001
63
Enabling and Disabling Statistics
Issue 11 Revision 0

The stat_mode command can be used to enable or disable specific statistics within the CM database. Statistics will not be collected unless enabled prior to the start of a statistical period. Some statistics are enabled in the CM database by default, a list of these and further examples of this command can be found in the W56 manual.

64
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Enabling/Disabling Statistics
stat_mode <meas_type> mode [<location>][<cell_desc>] meas_type mode location Name of statistic On or Off 0 or bsc 1 100 all cell id cell name all
cell desc
NET03_Ch6_02

EMOTOROLA LTD. 2001
65
Statistical Properties
Issue 11 Revision 0
Changing statistical properties
The chg_stat_prop command is used to change the properties of a statistic. The properties that can be altered are dependent on the statistical type specified: S S S The alarm threshold can be changed for counter and gauge statistics if applicable. Bin ranges may be changed for normal and weighted distribution statistics. Properties may not be changed for durational or counter array statistics.
After the command line the system will prompt for further information depending upon the above, examples can be found in the W56 manual.
Displaying statistical properties

Statistical properties can be displayed by use of the disp_stat_prop command. This command will cause the system to display the current properties of the specified statistic, the information and presentation format are dependent upon the statistic type. Examples of system outputs can be located in the W56 manual.

66
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Changing Statistical Properties

-
chg_stat_prop<meas_type> [<location>][<cell_desc>] meas_type location Name of statistic 0 or bsc 1 100 all cell id cell name all
cell desc
prompts follow
Displaying Statistical Properties

disp_stat_prop<meas_type>[<location>][<cell_desc>]
NET03_Ch6_03

EMOTOROLA LTD. 2001
67
Setting Bin Ranges for Distribution Statistics
Issue 11 Revision 0
A bin is a range which records the number of times or the length of time for which an event occurs. Therefore, a bin represents a pool of data Normal distribution statistics record how often a particular event or statechange occurs. Normal distribution bins contain a count.
Weighted distribution statistics record the time (in milliseconds) that an element is at a specific value. Weighted distribution bins contain a duration.
12 9 6 3
TICK TICK TICK
12 9 6 3
TICK TICK TICK
The bin ranges are set in exactly the same way for both normal and weighted distribution statistics. Each bin has a maximum and a minimum value, these values determine the range of values which may be placed in that bin. 30 45
71
0
min=0 max=10
1
min=11 max=20
2
min=21 max=30
3
min=31 max=40
4
min=41 max=50
5
min=51 max=60
6
min=61 max=70
7
min=71 max=80
8
min=81 max=90
9
min=91 max=100
The bin range for each bin may be made as large or as small as the operator requires, each bin may have a different size range. The total number of bins never changes. The diagrams opposite illustrate various scenarios which require the bin ranges to be sized in different ways.
NET03_Ch6_04

68
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Setting Bin Ranges
Constant Activity Across the Range
More Activity at the Centre of the Range
More Activity at the End of the Range
NET03_Ch6_05

EMOTOROLA LTD. 2001
69
Setting the Statistical Interval
Issue 11 Revision 0

The statistical interval can be set using the chg_element command. This period is used to control the time interval between successive uploads of statiscal information. At the end of the period specified the central statistics function at the BSC will collect statistical data from its associated distributed statistics functions and call the OMC to inform it that a statistics file is ready to be uploaded. Although it is possible to set this period anywhere between 5 and 60 minutes, the practical value will always be 30 or 60, as these are the only two values presently supported by the OMC. This period, set at the BSC, must be the same value as that being used at the OMC. The disp_element command can be used to display the current interval in use.
Displaying the interval timer

At any moment in time the BSC will retain 12 statistical files each pertaining to a particular chronological period, in length each period will be equal to the statistical interval. This command will prompt a display of the chronological range of each of the 12 start times.
Note: Clearing statistics

The command clear_stats is no longer supported and has been removed.

610
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Setting the Statistics Interval
chg_element stat_interval <*><location> * 30 or 60
Displaying the Interval Timer
disp_interval
NET03_Ch6_06

EMOTOROLA LTD. 2001
611
Displaying Statistical Reports
Issue 11 Revision 0

Once a statistical interval (stat_interval) has expired the statistical results can be displayed using the disp_stats command. Several examples of typical displays can be seen in the W56. The format of the command is as follows: disp_statso<interval>o<meas_type> o[cell_number] o[board_id]

612
EMOTOROLA LTD. 2001
Issue 11 Revision 0
disp_stats <interval><meas_type> [ * ] * cell_desc board_desc
NET03_Ch6_07

EMOTOROLA LTD. 2001
613
Issue 11 Revision 0

614
EMOTOROLA LTD. 2001
Chapter 7
Key Statistics

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 7 Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH mean holding time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH mean arrival rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Channel Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH mean holding time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH mean arrival rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH congestion (for call setup) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean TCH busy time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handover failure rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH assignment success rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Total_calls key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successful internal handovers, per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsuccessful internal handovers with successful re-establishment, per BSC . . Unsuccessful internal handovers with successful re-establishment, per cell . . . Unsuccessful internal handovers without re-establshment, per BSC . . . . . . . . . . Unsuccessful internal handovers without re-establishment, per cell . . . . . . . . . . RF Loss Summary Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell TCH assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH RF loss rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mean inter arrival time per BSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attempted immediate assignment procedures, per BSC . . . . . . . . . . . . . . . . . . . . Attempted immediate assignment procedures, per cell . . . . . . . . . . . . . . . . . . . . . Successful immediate assignment procedures, per BSC . . . . . . . . . . . . . . . . . . . . Successful immediate assignment procedure, per cell . . . . . . . . . . . . . . . . . . . . . . Mean arrival time between calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
71 71 72 74 76 76 76 78 78 710 710 710 712 712 712 714 714 716 718 718 718 720 720 722 722 724 724 724 726 726 728 728 728 728 730 730 732

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Key Statistics
Key Statistics
Objectives
On completion of this chapter the student will be able to: S S S State why we use key statistics. Name the five key statistic groups. Recognize a key statistic from a raw statistic calculation.

EMOTOROLA LTD. 2001
71
Introduction
Issue 11 Revision 0
Introduction
Key statistics provide the operator with a summary of system performance during a specific interval. They are designed to give an overall indication of the condition of the system to help detect congestion trends and possible performance degradation. Key statistics are provided to facilitate the monitoring of the most important network parameters. Key statistics are produced by combining various raw statistics values using a pre-defined formula. For example, various handover failure statistics may be combined and averaged over the total number of handover attempts to produce a handover failure rate key statistic. At the beginning of each day a key statistics report for the previous 24 hours could be obtained from which network performance could be assessed and potential problems identified. Further information could then be obtained from the raw statistics. The key statistics are divided into five groups.
S S S S S
SDCCH channel usage TCH channel usage Call summary RF loss summary Connection establishment

72
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Introduction
Key Statistics
What's Up Doc?

EMOTOROLA LTD. 2001
73
Key Statistics
Issue 11 Revision 0
Key Statistics
All key statistics are calculated on a per-cell basis except where specified. Below is a list of the 24 key statistics available:
SDCCH channel usage

S S S S SDCCH mean holding time SDCCH mean arrival rate SDCCH traffic SDCCH congestion
TCH channel usage

S S S S S TCH mean holding time TCH mean arrival rate TCH traffic TCH congestion Mean TCH busy time
Call summary
S S S S S S S Handover success rate Handover failure rate TCH assignment success rate Total calls key Unsuccessful internal handovers without re-establishment Unsuccessful internal handovers with successful re-establishment Successful internal handovers
RF loss summary
S S S S RF loss rate SDCCH RF loss rate TCH RF loss rate Cell TCH assignments
Connection establishment
S S S S Mean inter arrival time Successful immediate assignment procedures Attempted immediate assignment procedures Mean arrival time between calls NET03: BSS Subsystem Planning
74
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Key Statistics
Key Statistics
SDCCH channel usage
TCH channell usage
Call summary
RF loss summary
Connection establishment
NET03_Ch7_02

EMOTOROLA LTD. 2001
75
SDCCH Channel Usage
Issue 11 Revision 0
SDCCH Channel Usage

SDCCH mean holding time
Units: Usage: Seconds. Network planning.
This statistic measures the average duration of calls on SDCCH channels in seconds. BUSY_SDCCH is the mean number of SDCCHs occupied in the cell during the reporting interval and this, when multiplied by the duration of the interval gives the total number of call-seconds for that interval. Dividing by the number of accesses gives the average time held per access.
Raw statistics
BUSY_SDCCH
Description
Mean of BUSY_SDCCH statistic. Average number of SDCCHs carrying traffic in a cell during a collection interval. Successful accesses by process. The value used is the sum total of all the bins in the array.
OK_ACC_PROC
SDCCH mean arrival rate

Units: Usage: Calls per hour. Network planning.
This statistic indicates the call arrival rate for the SDCCHs in the cell. It is measured in calls per hour.
Raw statistics
OK_ACC_PROC
Description
Successful accesses by process. The value used is the sum total of all the bins in the array.

76
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH Channel Usage
SDCCH Mean Holding Time
SDCCH mean holding time
SUM (BUSY_SDCCH x INTERVAL x 3600 SUM (OK_ACC_PROC)
SDCCH Mean Arrival Rate
SDCCH mean arrival rate
SUM (OK_ACC_PROC)
=
SUM (INTERVAL)
NET03_Ch7_3

EMOTOROLA LTD. 2001
77
SDCCH Channel Usage
Issue 11 Revision 0
SDCCH traffic
Units: Usage: Erlangs. Network planning.
This statistic gives the total traffic on the SDCCHs of the cell. It is measured in erlangs.
Raw statistics
BUSY_SDCCH
Description
Mean of BUSY_SDCCH statistic.
SDCCH congestion
Units: Usage: Percentage. Quality of service monitoring. Network planning.
This statistic indicates the percentage of call set-ups refused due to congestion on the SDCCHs.
Raw statistics
ALLOC_SDCCH_FAIL
Description
Total number of times an attempt to allocate an SDCCH fails due to congestion. Total number of successful SDCCH allocations.
ALLOC_SDCCH

78
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH Channel Usage
SDCCH Traffic
SDCCH traffic
SUM (BUSY_SDCCH x INTERVAL) SUM (INTERVAL)
SDCCH Congestion
SUM (ALLOC_SDCCH_FAIL)
SDCCH congestion
x 100%
SUM (ALLOC_SDCCH + ALLOC_SDCCH_FAIL)
NET03_Ch7_04

EMOTOROLA LTD. 2001
79
TCH Channel Usage
Issue 11 Revision 0
TCH Channel Usage

TCH mean holding time
Units: Usage: Seconds. Network planning.
This statistic measures the average duration of calls on TCH channels in seconds. BUSY_TCH is the mean number of TCHs occupied in the cell during the reporting interval and this when multiplied by the duration of the interval gives the total number of call-seconds for that interval. Dividing by the number of calls gives the average per call.
Raw statistics
BUSY_TCH ALLOC_TCH
Description
Average number of busy TCHs. Number of successful TCH allocations.
The numerator and denominator may peg on different intervals (where a call extends across multiple collection boundaries). This will affect the accuracy of the stat for the period. Therefore, this stat should be used as a trend rather than focusing on specific values.
TCH mean arrival rate

Units: Usage: Calls per hour. Network planning.
This statistic indicates the call arrival rate in calls per hour for the cell in question.
Raw statistics
ALLOC_TCH ALLOC_TCH_FAIL
Description
Number of successful TCH allocations. Number of unsuccessful TCH allocations.

710
EMOTOROLA LTD. 2001
Issue 11 Revision 0
TCH Channel Usage
TCH Mean Holding Time
TCH mean holding time
SUM(BUSY_TCH x INTERVAL x 3600) SUM(ALLOC_TCH)
TCH Mean Arrival Rate
TCH mean arrival rate
SUM(ALLOC_TCH + ALLOC_TCH_FAIL)
=
SUM (INTERVAL)
NET03_Ch7_05

EMOTOROLA LTD. 2001
711
TCH Channel Usage
Issue 11 Revision 0
TCH traffic
Units: Usage: Erlangs. Network planning.
This statistic gives the total traffic on the TCHs of the cell. This key statisitc should be between 0 and 7 for single carrier cells, 0 and 15 for 2 carrier cells etc.
Raw statistics
BUSY_TCH
Description
Mean of BUSY_TCH statistic.
TCH congestion (for call setup)

Units: Usage: Percentage. Quality of service monitoring. Network planning. Fault finding.
The statistic indicates a percentage of call setup and intra-cell handovers refused due to congestion on the TCHs.
Raw statistics
ALLOC_TCH ALLOC_TCH_FAIL
Description
Number of successful TCH allocations. Number of unsuccessful TCH allocations.
Mean TCH busy time

Units: Usage: Seconds. Capacity planning.
This key statistic is calculated on a cell basis and will provide a mean usage time per TCH.
Raw statistics
BUSY_TCH AVAILABLE_TCH
Description
Mean number of busy TCHs in per interval. Mean number of in-service TCHs.

712
EMOTOROLA LTD. 2001
Issue 11 Revision 0
TCH Channel Usage
TCH Traffic
TCH traffic =
SUM (BUSY_TCH*INTERVAL) SUM (INTERVAL)
TCH Congestion
TCH congestion
=
SUM (ALLOC_TCH_FAIL) SUM (ALLOC_TCH + ALLOC_TCH_FAIL)
x 100%
Mean TCH Busy Time

Mean TCH busy time =
BUSY_TCH * INTERVAL * 3600 AVAILABLE_TCH
NET03_Ch7_06

EMOTOROLA LTD. 2001
713
Call Summary
Issue 11 Revision 0
Call Summary
Handover success rate
Units: Usage: Percentage. Quality of service monitoring. Optimization. Fault finding.
This statistic represents handovers which were attempted from the source cell that succeeded to establish at the destination cell. The handover attempt is counted when the handover command is sent to the MS.
Raw statistics:
OUT_INTER_BSS_HO_SUC INTRA_CELL_HO_SUC OUT_INTRA_BSS_HO_SUC OUT_INTER_BSS_HO_ATMPT INTRA_CELL_HO_ATMPT OUT_INTRA_BSS_HO_ATMPT
Description
Outgoing interBSS handover. Intra-cell handover completed. Intra-BSS handover completed. Inter-BSS handover attempts. Intra-cell handover attempts. Intra-BSS handover attempts.
This statistic is pegged after the system checks for congestion. Handover Success Rate + Handover Failure Rate 100% because the calls that fail and recover to the initial cell are not included in either of these values.

714
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Summary
Handover Success Rate
Handover = success rate

SUM(OUT_INTER_BSS_HO_SUC + INTRA_CELL_HO_SUC + OUT_INTRA_BSS_HO_SUC)
x 100%
SUM(OUT_INTER_BSS_HO_ATMPT + INTRA_CELL_HO_ATMPT + OUT_INTRA_BSS_HO_ATMPT)
NET03_Ch7_07

EMOTOROLA LTD. 2001
715
Call Summary
Issue 11 Revision 0
Handover failure rate

Units: Usage: Percentage. Quality of service monitoring. Optimization. Fault finding.
This statistics represents handovers that were attempted from the source cell that failed to establish at the destination cell. The call was also dropped as it failed to re-establish at the source cell. The handover attempt is counted when the handover command message is sent the MS.
Raw statistics
INTRA_CELL_HO_LOSTMS OUT_INTRA_BSS_HO_LOSTMS
INTER_BSS_HO_LOSTMS
Description
Intra-cell handover failed and MS lost. Intra-BSS handover failed and MS lost. Determined from the calculation opposite. Clear command from MSC. Inter-BSS handover, MS handover failed message received. Inter-BSS handover attempts. Intra-cell handover attempts. Intra-BSS handover attempts.
OUT_INTER_HO INTER_BSS_MS_FAIL OUT_INTER_BSS_HO_ATMPT INTRA_CELL_HO_ATMPT OUT_INTRA_BSS_HO_ATMPT
This statistic is pegged after the system checks for congestion.

716
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Summary
Handover Failure Rate
Handover failure = rate
SUM (INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS+ INTER_BSS_HO_LOSTMS)
x 100%
SUM (OUT_INTER_BSS_HO_ATMPT + INTRA_CELL_HO_ATMPT + OUT_INTRA_BSS_HO_ATMPT)
Where:
INTER_BSS_HO_LOSTMS = OUT_INTER_BSS_HO_ATMPT OUT_INTER_BSS_HO_RETURN OUT_INTER_BSS_HO_SUC
NET03_Ch7_08

EMOTOROLA LTD. 2001
717
Call Summary
Issue 11 Revision 0
TCH assignment success rate

Units: Usage: Percentage. Quality of service monitoring. Network planning. Fault finding.
Indicates how successful the cell is at providing a traffic channel to MSs during call set-up. Access to a traffic channel can be limited by a combination of blocking, radio loss and any other obstacles to an MS gaining access at the MSC or cell level.
Raw statistics
TOTAL_CALLS OK_ACC_PROC
Description
Total number of calls. Sum of bins: CM_SERVCALL CM_SERVSMS CM_SERVSS CM_SERVEME CM_REEST PGE_RSP
Total_calls key
Units: Usage: Number of successful TCH connections. Planning.
Indicates the number of successful TCH connections originating in the cell.
Raw statistics
TOTAL_CALLS
Description
Total number of calls.
Successful internal handovers, per BSC

Units: Usage: Number of successful handovers. Planning. Optimization.
This key statistic will provide the number of successful handovers per BSC including both intra-cell and intra-BSS.
Raw statistics
INTRA_CELL_HO_SUC OUT_INTRA_BSS_HO_SUC
Description
Number of successful intra-cell handovers. Number of successful intra-BSS handovers.

718
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Summary
TCH Assignment Success Rate

TCH assignment success rate
SUM (TOTAL_CALLS + CONGEST_ASSIGN_HO_SUC)
=
x 100%
SUM OK_ACC_PROC + OK_ACC_PROC + OK_ACC_PROC + OK_ACC_PROC + OK_ACC_PROC + OK_ACC_PROC (CM_SERVCALL) (CM_SERVSMS) (CM_SERVSS) (CM_SERVEME) (CM_REEST) (PGE_RSP)
Total_calls key
Total calls key= SUM (TOTAL_CALLS)
Successful Internal Handovers, per BSC

Successful internal handovers, per BSC =
SUM (INTRA_CELL_HO_SUC + OUT_INTRA_BSS_HO_SUC)
NET03_Ch7_09

EMOTOROLA LTD. 2001
719
Call Summary
Issue 11 Revision 0
Unsuccessful internal handovers with successful re-establishment, per BSC

Units: Usage: Number of unsuccessful handovers. Optimization. Planning.
This key statistic will provide the number of unsuccessful handovers per BSC where the MS managed to re-establish its connection to the source TCH.
Raw statistics
Description
Number of intra-cell handovers where the MS failed to gain a connection with the target TCH and managed to return the source TCH. Number of intra-BSS handovers where the MS failed to gain a connection with the target cells TCH and managed to return the source TCH.
Unsuccessful internal handovers with successful re-establishment, per cell

This key statistic will provide the number of unsuccessful handovers per cell where the MS managed to re-establish its connection to the source TCH.
Raw statistics
Description
Number of intra-cell handovers where the MS failed to gain a connection with the target TCH and managed to return the source TCH. Number of intra-BSS handovers where the MS failed to gain a connection with the target TCH and managed to return the source TCH.

720
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Summary
Unsuccessful Internal Handovers with successful re-establishment, per BSC
Unsuccessful internal handovers with successful reestablishment, per BSC =

SUM (INTRA_CELL_HO_RETURN + OUT_INTRA_BSS_HO_RETURN)
Unsuccessful Internal Handovers, with successful re-establishment, per cell
Unsuccessful internal handovers with successful reestablishment, per cell) =

(INTRA_CELL_HO_RETURN + OUT_INTRA_BSS_HO_RETURN) + OUT_INTRA_BSS_HO_RETURN)
NET03_Ch7_10

EMOTOROLA LTD. 2001
721
Call Summary
Issue 11 Revision 0
Unsuccessful internal handovers without re-establshment, per BSC

This key statistic will provide the number of unsuccessful handovers per BSC where the MS did not manage to reestablish its connection to the source TCH.
Raw statistics
Description
Number of intra-cell handovers where the MS failed to gain a connection with the target TCH and did not manage to return the source TCH. Number of intra-BSS handovers where the MS failed to gain a connection with the target TCH and did not manage to return the source TCH.
OUT_INTRA_BSS_HO_LOSTMS
Unsuccessful internal handovers without re-establishment, per cell

This key statistic will provide the number of unsuccessful handovers per cell where the MS did not manage to reestablish its connection to the source TCH.
Raw statistics
Description
Number of intra-cell handovers where the MS failed to gain a connection with the target TCH and did not manage to return the source TCH. Number of intra-BSS handovers where the MS failed to gain a connection with the target TCH and did not manage to return the source TCH.
OUT_INTRA_BSS_HO_LOSTMS

722
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Call Summary
Unsuccessful Internal Handovers, without re-establishment, per BSC
Unsuccessful internal handovers without reestablishment, per BSC=

SUM (INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS)
Unsuccessful Internal Handovers, without re-establishment, per Cell
Unsuccessful internal handovers without reestablishment per cell=

(INTRA_CELL_HO_LOSTMS + OUT_INTRA_BSS_HO_LOSTMS)
NET03_Ch7_11

EMOTOROLA LTD. 2001
723
RF Loss Summary Statistics
Issue 11 Revision 0

RF loss rate
Units: Usage: Percentage. Quality of service monitoring. Fault finding and optimization.
This statistic compares the total number of RF losses with the number of calls set up in the cell, plus the number of calls handed into the cell. It indicates the cell/system ability to preserve calls.
Raw statistics
RF_LOSSES_TCH RF_LOSSES_ SD OK_ACC_PROC
Description
RF losses on TCH. RF losses on SDCCH. Successful accesses by process. The value used is the sum total of all the bins in the array. Incoming inter-BSS handovers. Incoming intra-BSS handovers.
IN_INTER_HO IN_INTRA_BSS_HO_SUC
Cell TCH assignments

Units: Usage: Number of TCHs. Network planning.
The total number of calls that establish on a TCH. Should include both calls set up on TCHs within a cell and handovers into the cell.
Raw statistics
ALLOC_TCH
Description
Number of successful TCH allocations.

724
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RF Loss Rate
RF loss rate
SUM
RF_LOSSES_SD + ( RF_LOSSES_TCH [1] + .... + RF_LOSSES_TCH [nTCH] )
x 100%
IN_INTER_BSS_HO_SUC + IN_INTRA_BSS_HO
SUM (OK_ACC_PROC)
+ SUM
nTCH = Number of T CHsin cell.
Cell TCH Assignments
Cell TCH assignments = SUM (ALLOC_TCH)
NET03_Ch7_12

EMOTOROLA LTD. 2001
725
Issue 11 Revision 0
SDCCH RF loss rate

Units: Usage: Percentage. Quality of service monitoring. Fault finding.
This statistic compares the total number of RF losses (while using an SDCCH), as a percentage of the total number of call attempts for SDCCH channels. This statistic is intended to give an indication of how good the cell/system is at preserving calls.
Raw statistics
RF_LOSSES_SD OK_ACC_PROC
Description
RF losses on SDCCH. Successful accesses by process. The value used is the sum total of all the bins in the array.
TCH RF loss rate

Units: Usage: Percentage. Quality of service monitoring. Fault finding.
This statistic compares the total number of RF losses while using a TCH as a percentage of the total number of call attempts for TCH channels. This statistic is intended to show how good the cell/system is at preserving calls.
Raw statistics
ALLOC_TCH RF_LOSSES_TCH
Description
Number of successful TCH allocations. RF Losses on TCH.

726
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH RF Loss Rate
SDCCH RF loss rate
SUM (RF_LOSSES_SD)
x 100%
SUM (OK_ACC_PROC)
TCH RF Loss Rate

TCH RF loss rate
=
SUM ( RF_LOSSES_TCH [1] + ...+RF_LOSSES_TCH [nTCH] )
x 100%
SUM ALLOC_TCH)
nTCH = Number of T CHs in cell.
NET03_Ch7_13

EMOTOROLA LTD. 2001
727
Connection Establishment
Issue 11 Revision 0
Mean inter arrival time per BSC
Units: Usage: Seconds. Planning.
This key statistic is calculated on a BSS basis, and indicates the mean time between SDCCH acesses.
Raw statistics
OK_ACC_PROC
Description
sum of bins: CM_SERV CALL CM_SERV SS CM_SERV SMS CM_SERV EME
Attempted immediate assignment procedures, per BSC

Units: Usage: Number of attempts. Planning.
This key statistic is calculated on a BSS basis, and provides the number of attempted assignment procedures that have been verified.
Raw statistics
INV_EST_CAUSE_ON_RACH OK_ACC_PROC_SUC_RACH
Description
A-bis verified channel requests. RSS L1 decoded channel requests.
Attempted immediate assignment procedures, per cell

Units: Usage: Number of attempts. Planning.
This key statistic is calculated on a cell basis, and provides the number of attempted assignmnet procedures that have been verified.
Raw statistics
INV_EST_CAUSE_ON_RACH OK_ACC_PROC_SUC_RACH
Description
A-bis verified channel requests. RSS L1 decoded channel requests.

728
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Mean Inter Arrival Time per BSC

SUM (INTERVAL) x 3600 SUM [ OK_ACC_PROC ( CM_SERV CALL) ] + [ OK_ACC_PROC ( CM_SERV SS) ] + [ OK_ACC_PROC ( CM_SERV SMS) ] + [ OK_ACC_PROC ( CM_SERV EME) ]
Mean inter arrival time =
Attempted Immediate Assignment Procedures, per BSC

Attempted immediate assignment procedures (per BSC) =
SUM (OK_ACC_PROC_SUC_RACH INV_EST_CAUSE_ON_RACH
Attempted Immediate Assignment Procedures, per Cell

Attempted immediate assignment procedures (per cell) =
(OK_ACC_PROC_SUC_RACH INV_EST_CAUSE_ON_RACH)
NET03_Ch7_14

EMOTOROLA LTD. 2001
729
Issue 11 Revision 0
Successful immediate assignment procedures, per BSC

Units: Usage: Number of successful procedures. Planning. Network expansion.
This key statistic is calculated on a BSS basis, and provides the number of successful assignment procedures.
Raw statistics
CHAN_REQ_MS_BLK INV_EST_CAUSE_ON_RACH OK_ACC_PROC_SUC_RACH
Description
Immediate assignment rejects. A-bis verified channel requests. RSS L1 decoded channel requests.
Successful immediate assignment procedure, per cell

Units: Usage: Number of successful procedures Planning. Network expansion.
This key statistic is calculated on a cell basis, and provides the number of successful assignment procedures.
Raw statistics
CHAN_REQ_MS_BLK INV_EST_CAUSE_ON_RACH OK_ACC_PROC_SUC_RACH
Description
Immediate assignment rejects. A-bis verified channel requests. RSS L1 decoded channel requests.

730
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Successful Immediate Assignment Procedures, per BSC
Successful assignment procedures (per BSS) =

SUM (OK_ACC_PROC_SUC_RACH INV_EST_CAUSE_ON_RACH CHAN_REQ_MS_BLK)
Successful Immediate Assignment Procedures, per Cell
Successful assignment procedures (per cell) =

(OK_ACC_PROC_SUC_RACH INV_EST_CAUSE_ON_RACH) CHAN_REQ_MS_BLK)
NET03_Ch7_15

EMOTOROLA LTD. 2001
731
Issue 11 Revision 0
Mean arrival time between calls

Units: Usage: Seconds. Planning.
This key statistic is calculated on a per cell basis, and gives the average length of time between channel requests in the cell.
Raw statistics
Description
Channel request messages.

732
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Mean Arrival Time Between Calls
Mean arrival time between calls =
SUM (INTERVAL) X 3600 SUM [CHAN_REQ_CAUS_ATMPT(CM_SERV_CALL)] + [CHAN_REQ_CAUS_ATMPT(CM_SERV_EME)]

EMOTOROLA LTD. 2001
733
Issue 11 Revision 0

734
EMOTOROLA LTD. 2001
Chapter 8
Network Health Statistics

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 8 Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_SETUP_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DROP_CALL_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_SUCCESS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RANKING_FORMULA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALL_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_BLOCKING_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SDCCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO_SDCCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_ACCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO_TCH_AVAIL_TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAX_TCH_BUSY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_TRAFFIC_CARRIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_PER_CALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MEAN_TIME_HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INCOMING_VOLUME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_SUCCESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXTERNAL_RECOVERED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AIR_INTERFACE_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MSC_PAGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASSIGN_FAILURE_RATE_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASSIGN_FAILURE_RATE_RECOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_FAILURE_RATE_LOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HO_FAILURE_RATE_RECOVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH_RF_LOSS_RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
i
81 81 84 86 88 810 810 812 812 814 814 816 816 818 818 820 820 822 822 826 826 828 828 830 830 832 832 834 834 836 836

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0

Objectives
On completion of this chapter the student will be able to: S Understand the network health statistics.

EMOTOROLA LTD. 2001
81
Issue 11 Revision 0
Network health reports are calculated statistics that quantify BSS performance from the subscribers perspective. They were originally designed by Motorola Optimisation engineers who believed they were more useful than the standard key statistics, and are now available on the OMC. The OMC calculates these statistics using a combination of the raw and key statistics explained in earlier sections. The network health statistics are organized in the following groupings: S Health check CALL_SETUP_SUCCESS_RATE DROP_CALL_RATE CALL_SUCCESS_RATE RANKING_FORMULA S SDCCH congestion SDCCH_ACCESSES SDCCH_TRAFFIC_CARRIED S TCH congestion TCH_ACCESSES NO_TCH_AVAIL_TIME S Handover performance HO_PER_CALL MEAN_TIME_HO INCOMING_VOLUME OUTGOING_VOLUME INTERNAL_SUCCESS S S Paging performance AIR_INTERFACE_PAGING Radio performance ASSIGN_FAILURE_RATE_LOST ASSIGN_FAILURE_RATE_RECOVER HO_FAILURE_RATE_LOST HO_FAILURE_RATE_RECOVER TCH_RF_LOSS_RATE MSC_PAGING INTERNAL_LOST INTERNAL_RECOVERED EXTERNAL_SUCCESS EXTERNAL_LOST EXTERNAL_RECOVERED MAX_TCH_BUSY TCH_TRAFFIC_CARRIED NO_SDCCH_AVAIL_TIME CALL_VOLUME SDCCH_BLOCKING_RATE TCH_TRAFFIC_CARRIED

82
EMOTOROLA LTD. 2001
Issue 11 Revision 0
HEALTH CHECK SDCCH CONGESTION TCH CONGESTION HANDOVER PERFORMANCE PAGING PERFORMANCE RADIO PERFORMANCE
NET03_Ch8_01

EMOTOROLA LTD. 2001
83
Issue 11 Revision 0
CALL_SETUP_S UCCESS_RATE
This statistic shows the percentage of calls that successfully access a TCH when service is requested for normal calls, emergency calls, SMS messages, page responses, and calls that are re-established. Calls that do not require a TCH are excluded. Usage Quality of service. Fault finding. Service accessibility. Cell. Percentage. OK_ACC_PROC[CM_REESTABLISH]. OK_ACC_PROC[PAGE_RESPONSE]. OK_ACC_PROC[CM_SERV_REQ_CALL]. OK_ACC_PROC[CM_SERV_REQ_EMERG]. OK_ACC_PROC[CM_SERV_REQ_SMS]. SMS_INIT_ON_SDCCH. TOTAL_CALLS.
Basis Type Raw statistics

84
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CALL_SETUP_SUCCESS_RATE
CALL_SETUP_SUCCESS_RATE (%) =
SUM (TOTAL_CALLS)
* 100
SUM (OK_ACC_PROC[CM_SERV_REQ_CALL] + OK_ACC_PROC[CM_SERV_REQ_EMERG] + OK_ACC_PROC[CM_SERV_REQ_SMS] + OK_ACC_PROC[CM_REESTABLISH] + OK_ACC_PROC[PAGE_RESPONSE] SMS_INIT_ON_SDCCH)
NET03_Ch8_02

EMOTOROLA LTD. 2001
85
Issue 11 Revision 0
DROP_CALL_RA TE
This statistic shows the proportion of MSs which, having successfully accessed the TCH, subsequently experience an abnormal release, caused by either radio or equipment problems. This includes RF losses and losses during handovers. This statistic can be calculated at the cell, BSS, or network level. Usage Basis Type Raw statistics Fault finding. Service retainability. Cell, BSS, or network. Percentage. IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]. IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] . INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] . OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . RF_LOSSES_TCH. TOTAL_CALLS.

86
EMOTOROLA LTD. 2001
Issue 11 Revision 0
DROP_CALL_RATE
Cell Level DROP_CALL_RA = TE
(RF_LOSSES_TCH+ INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] + INTER_BSS_HO_LOSTMS) (TOTAL_CALLS + IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] +IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC])
* 100
BSS Level DROP_CALL_RA = TE
SUM (RF_LOSSES_TCH + INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] + INTER_BSS_HO_LOSTMS) SUM (TOTAL_CALLS + IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC])
* 100
Network Level DROP_CALL_RATE =
SUM (RF_LOSSES_TCH + INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] + INTER_BSS_HO_LOSTMS) SUM (TOTAL_CALLS)
* 100
NET03_Ch8_03

EMOTOROLA LTD. 2001
87
Issue 11 Revision 0
CALL_SUCCESS _RATE
This statistic shows the percentage of calls that end with normal completions at the radio subsystem. It provides an indication of overall network performance from the subscribers point of view. The CALL_SETUP_SUCCESS_RATE and DROP_CALL_RATE network health statistics are used to calculate this statistic. Usage Quality of service. Service retainability. Service accessibility. Fault finding. Cell. Percentage. ALLOC_TCH. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] . INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] . OK_ACC_PROC[CM_REESTABLISH]. OK_ACC_PROC[PAGE_RESPONSE]. OK_ACC_PROC[CM_SERV_REQ_CALL]. OK_ACC_PROC[CM_SERV_REQ_EMERG]. OK_ACC_PROC[CM_SERV_REQ_SMS]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . TOTAL_CALLS. RF_LOSSES_TCH.

88
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CALL_SUCCESS_RATE
CALL_SUCCESS_RATE (%)=
CALL_SETUP_SUCCESS_RATE * 1 -
DROP_CALL_RATE 100
NET03_Ch8_04

EMOTOROLA LTD. 2001
89
Issue 11 Revision 0
RANKING_FORM ULA
This statistic provides a measure by which cells can be ranked by performance. From this the cells requiring the most urgent optimization can be identified. The value of this statistic increases for cells with high call volumes and low call success rates, indicating that these cells should be optimized first. The CALL_SUCCESS_RATE and CALL_SETUP_SUCCESS_RATE network health statistics are used in this calculation. Usage Basis Type Raw statistics Optimization. Service retainability. Cell. Counter. ALLOC_TCH. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] . INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] . OK_ACC_PROC[CM_REESTABLISH]. OK_ACC_PROC[PAGE_RESPONSE]. OK_ACC_PROC[CM_SERV_REQ_CALL]. OK_ACC_PROC[CM_SERV_REQ_EMERG]. OK_ACC_PROC[CM_SERV_REQ_SMS] OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . RF_LOSSES_TCH. TOTAL_CALLS.
CALL_VOLUME
This statistic shows the total number of calls that successfully access a TCH. Usage Network planning. Installation and commissioning. Service accessibility. Cell. Counter. TOTAL_CALLS.

810
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RANKING_FORMULA
RANKING_FORMULA =
(100 CALL_SUCCESS_RATE) *
TOTAL_CALLS CALL_SETUP_SUCCESS_RATE
CALL_VOLUME
CALL_VOLUME = TOTAL_CALLS
NET03_Ch8_05

EMOTOROLA LTD. 2001
811
Issue 11 Revision 0
SDCCH_BLOCKI NG_RATE
This statistic is the percentage of SDCCH access attempts that were blocked, including handover attempts. Usage Service accessibility. Network planning. Installation and commissioning. Cell. Percentage. ALLOC_SDCCH.ALLOC_SDCCH_FAIL.
TCH_TRAFFIC_C ARRIED
This statistic is the mean number of busy TCHs during an interval, equivalent to the TCH traffic in erlangs. Usage Congestion. Quality of service. Network planning. Optimization. Cell. Counter. BUSY_TCH.

812
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH_BLOCKING_RATE
SDCCH_BLOCKING_RATE (%) =
SUM (ALLOC_SDCCH_FAIL) SUM (ALLOC_SDCCH + ALLOC_SDCCH_FAIL)
* 100
TCH_TRAFFIC_CARRIED
TCH_TRAFFIC_CARRIED = BUSY_TCH
NET03_Ch8_06

EMOTOROLA LTD. 2001
813
Issue 11 Revision 0
SDCCH_ACCESS ES
This statistic is the number of times an SDCCH is successfully seized and a layer 2 SABM command is received from the MS. Usage RF Loss. Congestion. Quality of service. Network planning. Cell. Counter. ALLOC_SDCCH. CHAN_REQ_MS_FAIL.
SDCCH_TRAFFIC _CARRIED
This statistic is the mean number of busy SDCCHs during the interval. It is equivalent to the SDCCH traffic in Erlangs. Usage RF Loss. Congestion. Network planning. Optimization. BSS. Counter. BUSY_SDCCH.

814
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDCCH_ACCESSES
SDCCH_ACCESSES
SDCCH_ACCESS = SUM (ALLOC_SDCCH_CHAN_REQ_MS_FAIL)
SDCCH_TRAFFIC_CARRIED
SDCCH_TRAFFIC_CARRIED = SUM (BUSY_SDCCH)
NET03_Ch8_07

EMOTOROLA LTD. 2001
815
Issue 11 Revision 0
NO_SDCCH_AVAI L_TIME
This statistic is the number of seconds for which no SDCCHs were available in a cell. Usage RF Loss. Congestion. Quality of service. Network planning. Optimization. Cell. Duration (total time in seconds). SDCCH_CONGESTION.
TCH_ACCESSES
This statistic is the total number of originating calls and incoming handovers to a cell, on a cell, BSS, or network level. Usage Handover. Quality of service. Network planning. Cell, BSS, or network. Counter. IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]. IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC]. TOTAL_CALLS.

816
EMOTOROLA LTD. 2001
Issue 11 Revision 0
NO_SDCCH_AVAIL_TIME
NO_SDCCH_AVAIL_TIME =
SDCCH_CONGESTION 1000
TCH_ACCESSES
Cell level TCH_ACCESSES = (TOTAL_CALLS + IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC] BSS level TCH_ACCESSES = SUM (TOTAL_CALLS + IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] ) Network level TCH_ACCESSES = SUM (TOTAL_CALLS)
NET03_Ch8_08

EMOTOROLA LTD. 2001
817
Issue 11 Revision 0
NO_TCH_AVAIL_ TIME
This statistic is the time in seconds for which all TCH channels in a cell were busy. Usage Congestion. Quality of service. Network planning. Optimization. Cell. Duration. TCH_CONGESTION.
MAX_TCH_BUSY
This statistic is the maximum number of TCHs simultaneously busy during an interval. Usage Congestion. Quality of service. Network planning. Optimization. Cell. Counter. BUSY_TCH[MAX].

818
EMOTOROLA LTD. 2001
Issue 11 Revision 0
NO_TCH_AVAIL_TIME
NO_TCH_AVAIL_TIME =
TCH_CONGESTION 1000
MAX_TCH_BUSY
MAX_TCH_BUSY = BUSY_TCH[MAX]
NET03_Ch8_09

EMOTOROLA LTD. 2001
819
Issue 11 Revision 0
TCH_TRAFFIC_C ARRIED
This statistic is the mean number of busy TCHs during an interval, equivalent to the TCH traffic in Erlangs. Usage Congestion. Quality of service. Network planning. Optimization. Cell. Counter. BUSY_TCH.
HO_PER_CALL
This statistic is the number of handovers per call in an interval. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Counter. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] . INTRA_CELL_HO[INTRA_CELL_HO_SUC] . TOTAL_CALLS.

820
EMOTOROLA LTD. 2001
Issue 11 Revision 0
TCH_TRAFFIC_CARRIED
TCH_TRAFFIC_CARRIED = BUSY_TCH
HO_PER_CALL
HO_PER_CALL =
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] + INTRA_CELL_HO[INTRA_CELL_HO_SUC]) SUM (TOTAL_CALLS)
NET03_Ch8_10

EMOTOROLA LTD. 2001
821
Issue 11 Revision 0
MEAN_TIME_HO
This statistic provides the mean time interval between successive handovers during a call. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Time interval (in seconds). TCH_USAGE. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] . INTRA_CELL_HO[INTRA_CELL_HO_SUC] .
INCOMING_VOL UME
This statistic is the number of successful incoming internal and external handovers, at the cell or BSS level. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell or BSS. Counter. IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC]. IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC].

822
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MEAN_TIME_HO
MEAN_TIME_HO=
SUM (TCH_USAGE) SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] + INTRA_CELL_HO[INTRA_CELL_HO_SUC]) * 1000
INCOMING_VOLUME
Cell Level INCOMING_VOLUME= SUM
(IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] IN_INTRA_BSS_HO[IN_INTRA_BSS_HO_SUC] )
BSS Level INCOMING_VOLUME =
SUM (IN_INTER_BSS_HO[IN_INTER_BSS_HO_SUC] )
NET03_Ch8_11

EMOTOROLA LTD. 2001
823
Issue 11 Revision 0
OUTGOING_VOLUME
This statistic is the number of outgoing internal and external handovers, at the cell or BSS level. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell or BSS. Counter. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] .
INTERNAL_SUCCESS
This statistic is the percentage of successful internal handovers. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] . INTRA_CELL_HO[INTRA_CELL_HO_SUC] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]. INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].

824
EMOTOROLA LTD. 2001
Issue 11 Revision 0
OUTGOING_VOLUME
Cell Level
OUTGOING_VOLUME = SUM(OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC])
BSS Level
OUTGOING_VOLUME = SUM(OPUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC)
INTERNAL_SUCCESS
INTERNAL_SUCCESS = (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_SUC] + INTRA_CELL_HO[INTRA_CELL_HO_SUC]) * 100% (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] )
NET03_Ch8_12

EMOTOROLA LTD. 2001
825
Issue 11 Revision 0
INTERNAL_LOST
This statistic is the percentage of attempted internal handovers that result in a lost MS. Usage Basis Type Raw statistics Quality of service.Fault finding. Cell. Percentage. OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] . INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]. INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].
INTERNAL_REC OVERED
This statistic is the percentage of attempted internal handovers that fail with the MS subsequently recovering to the source cell. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] . INTRA_CELL_HO[INTRA_CELL_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]. INTRA_CELL_HO[INTRA_CELL_HO_ATMPT].

826
EMOTOROLA LTD. 2001
Issue 11 Revision 0
INTERNAL_LOST
INTERNAL_LOST (%) = SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] + INTRA_CELL_HO[INTRA_CELL_HO_LOSTMS] ) SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] )
*100%
INTERNAL_RECOVERED
INTERNAL_RECOVERED = SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_RETURN] + INTRA_CELL_HO[INTRA_CELL_HO_RETURN] )
*100%
SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + INTRA_CELL_HO[INTRA_CELL_HO_ATMPT] )
NET03_Ch8_13

EMOTOROLA LTD. 2001
827
Issue 11 Revision 0
EXTERNAL_SUC CESS
This statistic is the percentage of successful external handovers. Usage Basis Type Raw statistics Quality of service. Fault finding. BSS. Percentage. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] . OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT].
EXTERNAL_LOS T
This statistic is the percentage of attempted external handovers that result in a lost MS. Usage Basis Type Raw statistics Quality of service. Fault finding. BSS. Percentage. 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] .

828
EMOTOROLA LTD. 2001
Issue 11 Revision 0
EXTERNAL_SUCCESS
EXTERNAL_SUCCESS =
SUM (OUT_INTER_BSS_HO]OUT_INTER_BSS_HO_SUC] )
*100%
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] )
EXTERNAL_LOST
EXTERNAL_LOST (%) =
SUM (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] )
*100%
NET03_Ch8_14

EMOTOROLA LTD. 2001
829
Issue 11 Revision 0
EXTERNAL_REC OVERED
This statistic is the percentage of attempted external handovers that fail with the MS subsequently recovering to the source cell. Usage Basis Type Raw statistics Quality of service. Fault finding. BSS. Percentage. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT.
AIR_INTERFACE _PAGING
This statistic is the total number of Paging Request messages sent on the air interface for each cell in a BSS. Usage Basis Type Raw statistics Network planning. Radio resource allocation. Cell. Counter. ACCESS_PER_PCH.

830
EMOTOROLA LTD. 2001
Issue 11 Revision 0
EXTERNAL_RECOVERED
EXTERNAL_RECOVERED=
SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] )
* 100%
AIR_INTERFACE_PAGING
AIR_INTERFACE_PAGING = SUM (ACCESS_PER_PCH)
NET03_Ch8_15

EMOTOROLA LTD. 2001
831
Issue 11 Revision 0
MSC_PAGING
This statistic is the total number of paging messages received from the MSC for each of the cells in a BSS. Usage Basis Type Raw statistics Network planning. Radio resource allocation. Cell. Counter. PAGE_REQ_FROM_MSC.
ASSIGN_FAILUR E_RATE_LOST
This statistic is the percentage of Assignment Commands sent to the MS that fail and result in lost connections. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. INTRA_CELL_HO[INTRA_CELL_HO_SUC] . MA_CMD_TO_MS.MA_COMPLETE_TO_MSC. MA_FAIL_FROM_MS.

832
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MSC_PAGING
MSC_PAGING = SUM (PAGE_REQ_FROM_MSC)
ASSIGN_FAILURE_RATE_LOST
ASSIGN_FAILURE_RATE_LOST (%) =
SUM
MA_CMD_TO_MS INTRA_CELL_HO[INTRA_CELL_HO_SUC] MA_COMPLETE_TO_MSC MA_FAIL_FROM_MS
* 100
MA_CMD_TO_MS
NET03_Ch8_16

EMOTOROLA LTD. 2001
833
Issue 11 Revision 0
ASSIGN_FAILUR E_RATE_RECOV ER
This statistic is the percentage of assignment commands that fail with the MS recovering to the source channel. Usage Basis Type Raw Statistics Quality of service. Fault finding. Cell. Percentage. MA_CMD_TO_MS.MA_FAIL_FROM_MS.
HO_FAILURE_RA TE_LOST
This statistic is the percentage of attempted handovers that result in lost connections, but does not include intra-cell handovers. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]. OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_LOSTMS] . OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_SUC] .

834
EMOTOROLA LTD. 2001
Issue 11 Revision 0
ASSIGN_FAILURE_RATE_RECOVER
ASSIGN_FAILURE_RATE_RECOVER (%) = SUM (MA_FAIL_FROM_MS) SUM (MA_CMD_TO_MS) * 100
HO_FAILURE_RATE_LOST
HO_FAILURE_RATE_LOST =
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]
SUM
* 100
SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] )
NET03_Ch8_17

EMOTOROLA LTD. 2001
835
Issue 11 Revision 0
HO_FAILURE_RA TE_RECOVER
This statistic is the percentage of attempted handovers that fail with the MS recovering to the source cell. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT]. OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] . OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT]. OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_FAIL].
TCH_RF_LOSS_ RATE
This statistic is the percentage of allocated calls on TCHs that are lost due to radio connection failure on the TCH. Usage Basis Type Raw statistics Quality of service. Fault finding. Cell. Percentage. ALLOC_TCH.RF_LOSSES_TCH .

836
EMOTOROLA LTD. 2001
Issue 11 Revision 0
HO_FAILURE_RATE_RECOVER
HO_FAILURE_RATE RECOVER (%) =

SUM (OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_RETURN] + OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_FAIL] ) *100 SUM (OUT_INTRA_BSS_HO[OUT_INTRA_BSS_HO_ATMPT] + OUT_INTER_BSS_HO[OUT_INTER_BSS_HO_ATMPT] )
TCH_RF_LOSS_RATE
TCH_RF_LOSS_RATE (%) =
SUM (RF_LOSSES_TCH [ n1] + . . . RF_LOSSES_TCH[nt])) SUM (ALLOC_TCH)
NET03_Ch8_18

EMOTOROLA LTD. 2001
837
Issue 11 Revision 0

838
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Appendix A

EMOTOROLA LTD. 2001
App A i
Issue 11 Revision 0

App A ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
GSM BURST TYPES

FRAME 1 FRAME 2
3 TB Encrypted Bits 57
NORMAL BURST (NB) Training Sequence 26 1 1 Encrypted Bits 57
3 TB GP 8.25 3 TB GP 8.25
3 TB
FREQ CORRECTION BURST (FB) Fixed Bits 142
3 TB Encrypted Bits 39
SYNCHRONISATION BURST (SB) Synchronisation Sequence 64 Encrypted Bits 39
3 TB GP 8.25
3 TB Fixed Bits 57 1
DUMMY BURST Training Sequence 26 1 ACCESS BURST Synchronisation Sequence 41 Encrypted Bits 36 TB 3 156.25 Bit Durations GP 73.25 Fixed Bits 57
3 TB GP 8.25
3 TB

EMOTOROLA LTD. 2001
App A iii
Issue 11 Revision 0

App A iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
26-FRAME MULTIFRAME
0.577ms
Time-slot
TDMA frame 7 6 5 4 4.615ms 3 2 1 0
2
7 6 5 4 3 2 1 0 7 6 5 4
1
3 2 1 0 7 6 5
0
4 3 2 1 0
Idle Multiframe
SACCH
25
24
23 22
21 20
19
18 17 16
15
14 13 12
11
10
120ms
Time

EMOTOROLA LTD. 2001
App A v
Issue 11 Revision 0

App A vi
EMOTOROLA LTD. 2001
Issue 11 Revision 0
51-FRAME MULTIFRAME Control Channel
0.577ms
Time-slot
TDMA frame 7 6 5 4 4.615ms 3 2 1 0
2
7 6 5 4 3 2 1 0 7 6 5 4
1
3 2 1 0 7 6 5
0
4 3 2 1 0
Multiframe
51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9
8 7
3 2
240ms
Time

EMOTOROLA LTD. 2001
App A vii
Issue 11 Revision 0

App A viii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CONTROL CHANNELS
CCH
Control Channel
NB
NB/AB
NB/DB
DCCH
BCCH
downlink only
SDCCH
ACCH
BCCH
Synch. Channels FB
SB
FACCH
SACCH
SCH
FCH
CCCH
AB
NB
RACH uplink
PCH/AGCH downlink
CBCH
ACRONYMS!! NB= NORMAL BURST FB = FREQUENCY BURST SB = SYCHRONISATION BURST AB = ACCESS BURST DB = DUMMY BURST

EMOTOROLA LTD. 2001
App A ix
Issue 11 Revision 0

App A x
EMOTOROLA LTD. 2001
Issue 11 Revision 0
BCCH/CCCH MULTIFRAME
50
40
30
20
10
Downlink
0
EMOTOROLA LTD. 2001

I C C S F C C S F C C S F C C S F C B S F
KEY R= B= F= S= C= I= RACH (Random) BCCH (Broadcast) FCCH (Frequency) SCH (Sync.) CCCH (Common) Idle
50
40
30
20
10
Uplink
0
R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R
NET03: BSS Subsystem Planning FOR TRAINING PURPOSES ONLY

App A xi
Issue 11 Revision 0

App A xii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
DCCH MULTIFRAME
40
30
20
D3 10 D2 D1
D3 D2 D1 D0
10
Downlink
0
D0
Uplink
0

EMOTOROLA LTD. 2001

A3 A2 A7 A6 A1 A0 D7 D6 D5 D4 A5 A4 D7 D6 D5 D4
50
I I I
I I I
50 A0
SDCCH/8 (Dedicated) SACCH/C8 (Associated) Idle
KEY D= A= I=
A4 D7 D6 D5 D4 D3 D2 D1 D0 I I I
D7 D6 D5 D4 30 D3 D2 D1 D0 I I I
40
20
A7 A6 A5
A3 A2 A1
App A xiii
Issue 11 Revision 0

App A xiv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
COMBINED MULTIFRAME
KEY R= B= F= S= C= D= A= I= RACH (Random) BCCH (Broadcast) FCCH (Frequency) SCH (Sync.) CCCH (Common) SDCCH/4 (Dedicated) SACCH/C4 (Associated) Idle
50
40
30
20
C 10 S F C B
C S F C B S F
10
Downlink
0
S F
Uplink
0

EMOTOROLA LTD. 2001

I I A1 A0 S F A3 A2 S F D3 D2 S F D1 D0 S F C D3 D2 S F D1 D0 S F C
50 D2 R R D1 40 D0 R R R R R R R R R R R R R R R R R R R R R R R D0 R R R R R R R R R R R R R R R R R R R R R R R D2 R R D1
30
20
A3 A2 R R
A1 A0 R R
D3
D3
App A xv
Issue 11 Revision 0

App A xvi
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Appendix B

EMOTOROLA LTD. 2001
App B i
GSR3 New Raw Statistics
Issue 11 Revision 0
GSR3 New Raw Statistics

Statistic Name CHAN_REQ_CAUSE_ATMPT MS_ACCESS_BY_TYPE PCH_AGCH_Q_LENGTH EFR_REQ_FROM_MSC MS_TCH_USAGE_BY_TYPE TCH_USAGE_EXT_RANGE TCH_USAGE_INNER_ZONE TCH_CONG_INNER_ZONE UPLINK_PATH_LOSS CHAN_DL_TX_PWR_LVL CHAN_UL_TX_PWR_LVL IDLE_TCH_INTF_BANDn INTRA_BSS_HO_CAUSE_SUC ER_INTRA_CELL_HO_ATMPT ER_INTRA_CELL_HO_SUC ZONE_CHANGE_ATMPT ZONE_CHANGE_SUC INTRA_CELL_EQUIP_FAIL HO_FAIL_NO_RESOURCES INTRA_CELL_HO INTERBAND_ACTIVITY IN_INTRA_BSS_EQUIP_FAIL OUT_INTRA_BSS_EQUIP_FAIL IN_INTRA_BSS_HO_RETURN IN_INTRA_BSS_MS_NO_SEIZE OUT_INTRA_BSS_HO IN_INTRA_BSS_HO OUT_INTER_BSS_EQUIP_FAIL OUT_INTER_BSS_HO_LOSTMS IN_INTER_BSS_EQUIP_FAIL IN_INTER_BSS_MS_NO_SEIZE OUT_INTER_BSS_HO IN_INTER_BSS_HO Pegged at RRSM RRSM RSS SSM CRM CRM CRM CRM HDPC HDPC HDPC CRM SSM SSM SSM SSM SSM SSM CRM SSM/RRSM SSM SSM SSM SSM SSM SSM/RRSM SSM/RRSM SSM SSM SSM SSM SSM/RRSM SSM/RRSM
GSR3 New Key Statistic

Statistic Name Mean Arrival Time Betw een Calls

App B ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
GSR3 Statistic Name Changes

Old Name INTRA_CELL_HO INTRA_CELL_HO_FAIL INTRA_BSS_HO_REQ INTRA_BSS_HO_ATMPT IN_INTRA_BSS_HO INTRA_BSS_HO INTRA_BSS_HO_PRI_BLK INTRA_BSS_HO_FAIL INTRA_BSS_HO_LOSTMS INTER_BSS_HO_ATMPT OUT_INTER_HO IN_INTER_HO INTER_BSS_MS_FAIL New Name INTRA_CELL_HO_SUC INTRA_CELL_HO_RETURN OUT_INTRA_BSS_HO_REQ OUT_INTRA_BSS_HO_ATMPT IN_INTRA_BSS_HO_SUC OUT_INTRA_BSS_HO_SUC OUT_INTRA_BSS_HO_PRI_BLK OUT_INTRA_BSS_HO_RETURN OUT_INTRA_BSS_HO_LOSTMS OUT_INTER_BSS_HO_ATMPT OUT_INTER_BSS_HO_SUC IN_INTER_BSS_HO_SUC OUT_INTER_BSS_HO_RETURN Pegged at SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM SSM

EMOTOROLA LTD. 2001
App B iii
Issue 11 Revision 0

App B iv
EMOTOROLA LTD. 2001
Chapter 9
Glossary of technical terms and abbreviations

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Chapter 9 Glossary of technical terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . .

Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A ......................................................................... B ......................................................................... C ......................................................................... D ......................................................................... E ......................................................................... F ......................................................................... G ......................................................................... H ......................................................................... I .......................................................................... K ......................................................................... L ......................................................................... M ......................................................................... N ......................................................................... O ......................................................................... P ......................................................................... Q ......................................................................... R ......................................................................... S ......................................................................... T ......................................................................... U ......................................................................... V ......................................................................... W ........................................................................ X ......................................................................... Z .........................................................................
i
91 92 95 98 912 915 917 919 921 922 924 925 927 931 933 935 938 939 942 946 949 950 951 952 953

EMOTOROLA LTD. 2001
iii
Issue 11 Revision 0

iv
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Numbers
Numbers
# 2 Mbit/s link Number. As used in this manual set, the term applies to the European 4-wire 2.048 Mbit/s digital line or link which can carry 30 A-law PCM channels or 120 16 kbit/s GSM channels. 4th Generation Language.
4GL

EMOTOROLA LTD. 2001
91
Issue 11 Revision 0
A
A interface A3 A38 A5 A8 AB Abis interface Interface between MSC and BSS. Authentication algorithm that produces SRES, using RAND and Ki. A single algorithm performing the function of A3 and A8. Stream cipher algorithm, residing on an MS, that produces ciphertext out of plaintext, using Kc. Ciphering key generating algorithm that produces Kc using RAND and Ki. Access Burst. Interface between a remote BSC and BTS. Motorola offers a GSM standard and a unique Motorola Abis interface. The Motorola interface reduces the amount of message traffic and thus the number of 2 Mbit/s lines required between BSC and BTS. Answer Bid Ratio. ACDC Power Supply module. Alternating Current. Access Class (C0 to C15). Application Context. Automatic Congestion Control. Associated Control CHannel. ACKnowledgement. Accumulated Call meter. Address Complete Message. AC Power Interface Module. Used in M-Cell6 indor ac BTS equipment. AC Power Supply Module. Used in M-Cell6 BTS equipment. Associated Control Service Element. Antenna Combining Unit. Analogue to Digital (converter). ADministration Centre. Analogue to Digital Converter. ADvanced Communications Control Protocol. ADMinistration processor. ADMINistration. Abbreviated Dialling Number. Adaptive Differential Pulse Code Modulation. Application Entity. Accoustic Echo Control. Additional Elementary Functions.
ABR acdc PSM ac AC AC ACC ACCH ACK, Ack ACM ACM ACPIM AC PSM ACSE ACU A/D ADC ADC ADCCP ADM ADMIN ADN ADPCM AE AEC AEF

92
EMOTOROLA LTD. 2001
Issue 11 Revision 0
AET
Active Events Table. Alarms and events are sent to the Events Log in the GUI. Different operators will have different subscription lists. All alarms and events are sent to the AET before they are re-routed to different subscription lists. Automatic Frequency Control. Absolute Frame Number. Automatic Gain Control. Access Grant CHannel. A GSM common control channel used to assign MS to a SDCCH or a TCH. Action indicator. Artificial Intelligence. Alarm Interface Board. A class of processor. The radio link between the BTS and the MS. Amplitude Modulation. Automatic Message Accounting (processor). Cell broadcast mobile terminated message. A message broadcast to all MSs in a cell. Advice of Change. Advice of Change Charging supplementary service. Advice of Change Information supplementary service. Automatic Output Control. Application Process. Absolute Radio Frequency Channel Number. An integer which defines the absolute RF channel number. Automatic ReQuest for retransmission. Address Resolution Protocol. Association Control Service Element. An ASE which provides an AP with the means to establish and control an association with an AP in a remote NE. Maps directly onto the Presentation layer (OMC). Application Service Element (OMC) Application Specific Entity (TCAP). Abstract Syntax Notation One. Alarm and Status Panel. Answer Seizure Ratio. All Trunks Busy. Antenna Transceiver Interface. ATTach. Automatic Trunk Testing Subsystem. Access Unit. Authentication Centre. A GSM network entity which provides the functionality for verifying the identity of an MS when requested by the system. Often a part of the HLR.
AFC AFN AGC AGCH Ai AI AIB AIO Air interface AM AMA AM/MP AoC AoCC AoCI AOC AP ARFCN ARQ ARP ASCE
ASE ASE ASN.1 ASP ASR ATB ATI ATT (flag) ATTS AU AuC

EMOTOROLA LTD. 2001
93
Issue 11 Revision 0
AUT(H) AUTO
AUThentication. AUTOmatic mode.

94
EMOTOROLA LTD. 2001
Issue 11 Revision 0
B
B Interface BA BAIC BAOC BBBX BBH BCC BCCH Interface between MSC and VLR. BCCH Allocation. The radio frequency channels allocated in a cell for BCCH transmission. Barring of All Incoming Calls supplementary service. Barring of All Outgoing Calls supplementary service. Battery Backup Board. Base Band Hopping. BTS Colour Code. Broadcast Control CHannel. A GSM control channel used to broadcast general information about a BTS site on a per cell or sector basis. Binary Coded Decimal. Base station Control Function. The GSM term for the digital control circuitry which controls the BTS. In Motorola cell sites this is a normally a BCU which includes DRI modules and is located in the BTS cabinet. Bearer Capability Information Element. Base station Control Unit. A functional entity of the BSS which provides the base control function at a BTS site. The term no longer applies to a type of shelf (see BSC and BSU). Base Controller Unit Power. Bit Error Rate. A measure of signal quality in the GSM system. Business Exchange Services. Bad Frame Indication. Busy Hour Call Attempt. all Barring of All Incoming call supplementary service. Balanced-line Interconnect Board. Provides interface to 12 balanced (6-pair) 120 ohm (37-pin D-type connector) lines for 2 Mbit/s circuits (See also T43). Barring of All Incoming Calls when Roaming outside the Home PLMN Country supplementary service. Balanced-line Interconnect Module. An area in a data array used to store information. BootLoad. Also known as download. For example, databases and software can be downloaded to the NEs from the BSS. BiLLiNG. Bits per second (bps). Full rate traffic channel. Bit Number. Number which identifies the position of a particular bit period within a timeslot. Bandpass Filter. mBCU Power Supply Module.
BCD BCF
BCIE BCU
BCUP BER BES BFI BHCA BI BIB
BICRoam BIM Bin BL BLLNG bit/s Bm BN BPF BPSM

EMOTOROLA LTD. 2001
95
Issue 11 Revision 0
BS BS
Basic Service (group). Bearer Service. A type of telecommunication service that provides the capability for the transmission of signals between user-network interfaces. The PLMN connection type used to support a bearer service may be identical to that used to support other types of telecommunication service. Base Station Controller. A network component in the GSM PLMN which has the digital control function of controlling all BTSs. The BSC can be located within a single BTS cabinet (forming a BSS) but is more often located remotely and controls several BTSs (see BCF, BCU, and BSU). Basic Service Group. Base Transceiver Station Identity Code. A block of code, consisting of the GSM PLMN colour code and a base station colour code. One Base Station can have several Base Station Colour Codes. BSIC of an adjacent cell. Base Site control Processor (at BSC). Backward Sequence Number. Base Station System. The system of base station equipment (Transceivers, controllers and so on) which is viewed by the MSC through a single interface as defined by the GSM 08 series of recommendations, as being the entity responsible for communicating with MSs in a certain area. The radio equipment of a BSS may cover one or more cells. A BSS may consist of one or more base stations. If an internal interface is implemented according to the GSM 08.5x series of recommendations, then the BSS consists of one BSC and several BTSs. BSS Application Part (of Signalling System No. 7) (DTAP + BSSMAP). Base Station System Control cabinet. The cabinet which houses one or two BSU shelves at a BSC or one or two RXU shelves at a remote transcoder. Base Station System Management Application Part (6-8). BSS Operation and Maintenance Application Part (of Signalling System No. 7). Base Station Unit shelf. The shelf which houses the digital control modules for the BTS (p/o BTS cabinet) or BSC (p/o BSSC cabinet). British Telecom. Bus Terminator. Bus Terminator Card. Base Transceiver Function. Base Transceiver Processor (at BTS). One of the six basic task groups within the GPROC.
BSC
BSG BSIC
BSIC-NCELL BSP BSN BSS
BSSAP BSSC
BSSMAP BSSOMAP BSU
BT BT BTC BTF BTP

96
EMOTOROLA LTD. 2001
Issue 11 Revision 0
BTS
Base Transceiver Station. A network component in the GSM PLMN which serves one cell, and is controlled by a BSC. The BTS contains one or more Transceivers (TRXs). A period of modulated carrier less than one timeslot. The physical content of a timeslot.
Burst

EMOTOROLA LTD. 2001
97
Issue 11 Revision 0
C
C C Interface C7 CA CA CAB CADM Conditional. Interface between MSC and HLR/AUC. ITU-TSS Signalling System 7 (sometimes referred to as S7 or SS#7). Cell Allocation. The radio frequency channels allocated to a particular cell. Central Authority. Cabinet. Country ADMinistration. The Motorola procedure used within DataGen to create new country and network files in the DataGen database. Charge Advice Information. Cell Analysis Tool. Cell Broadcast. Circuit Breaker. Cell Broadcast Centre. Cell Broadcast CHannel. Combining Bandpass Filter. Cell Broadcast Link. Circuit Breaker Module. Cell Broadcast Message Identifier. Cell Broadcast Short Message Service. Clock Bus. Connection Confirm (Part of SCCP network connectivity). Country Code. Call Control. Cavity Combining Block, a three way RF combiner. There are two types of CCB, CCB (Output) and CCB (Extension). These, with up to two CCB Control cards, may comprise the TATI. The second card may be used for redundancy. Completion of Calls to Busy Subscriber supplementary service. Common Control CHannels. A class of GSM control channels used to control paging and grant access. Includes AGCH, PCH, and RACH. Group of MSs in idle mode. Common Channel Distributor. Channel Coding Digital Signal Processor. Conditional Call Forwarding. Control CHannel. Control channels are channels which carry system management messages. Council for Communications Harmonization (referred to in GSM Recommendations).
CAI CAT CB CB CBC CBCH CBF CBL CBM CBMI CBSMS CBUS CC CC CC CCB
CCBS CCCH
CCCH_GROUP CCD CCDSP CCF CCH CCH

98
EMOTOROLA LTD. 2001
Issue 11 Revision 0
CCIT
Comit Consultatif International Tlgraphique et Tlphonique. This term has been superceded by ITUTSS (International Telecommunications Union Telecommunications Sector). Current Call Meter. Capability/Configuration Parameter. Control Channel Protocol Entity. Hundred call-seconds. The unit in which amounts of telephone traffic are measured. A single call lasting one hundred seconds is one CCS. See also erlang. Circuit. Control Driver Board. Common Desktop Environment. Part of the SUN software (crontab cron job file). Call Detail Records. Chargeable DURation. Control Equalizer Board (BTS). Called station identifier. Central Equipment Identity Register. By GSM definition, a cell is an RF coverage area. At an omni-site, cell is synonymous with site; at a sectored site, cell is synonymous with sector. This differs from analogue systems where cell is taken to mean the same thing as site. (See below).
CCM CCP CCPE CCS
Cct CDB CDE CDR CDUR CEB CED CEIR Cell
1 Cell = 1 Sector
Omni Site 1-Cell Site (1 BTS)
6-Sector Site or 6-Cell Site (6 BTSs)
CEND CEPT CERM CF CF CFB CFC CFNRc CFNRy
End of charge point. Confrence des administrations Europennes des Postes et Telecommunications. Circuit Error Rate Monitor. Conversion Facility. all Call Forwarding services. Call Forwarding on mobile subscriber Busy supplementary service. Conditional Call Forward. Call Forwarding on mobile subscriber Not Reachable supplementary service. Call Forwarding on No Reply supplementary service.

EMOTOROLA LTD. 2001
99
Issue 11 Revision 0
CFU Channel
Call Forwarding Unconditional supplementary service. A means of one-way transmission. A defined sequence of periods (for example, timeslots) in a TDMA system; a defined frequency band in an FDMA system; a defined sequence of periods and frequency bands in a frequency hopped system. Coaxial Interconnect Module. CHarging Point. Card Holder Verification information. Ciphering Key Sequence Number. Cell Identity. A block of code which identifies a cell within a location area. CUG Index. Circuit Identity Code. Carrier to Interference Ratio. Unintelligible data produced through the use of encipherment. Ciphering Key Sequence Number. Calling Line Identity. Calling Line Identification Presentation supplementary service. Calling Line Identification Restriction supplementary service. Clock. Clock Extender half size board. The fibre optic link that distributes GCLK to boards in system (p/o BSS etc). Connectionless Manager. CLeaR. Configuration Management. An OMC application. Connection Management. CoMmanD. Channel Mode Modify. Common Management Information Protocol. Common Management Information Service Element. An ASE which provides a means to transfer management information via CMIP messages with another NE over an association established by ASCE using ROSE (OMC). Cellular Manual Revision. CalliNg tone. COnnected Line Identity. Placed together; two or more items together in the same place. A cell which has a co-located neighbour whose cell boundary follows the boundary of the said cell. The coincident cell has a different frequency type, but the same BSIC, as that of the neighbour cell. COnnected Line Identification Presentation supplementary service.
CIM CHP CHV CKSN CI CI CIC CIR, C/I Ciphertext CKSN CLI CLIP CLIR CLK CLKX CLM CLR CM CM CMD CMM CMIP CMISE
CMR CNG COLI Collocated Coincident Cell
COLP

910
EMOTOROLA LTD. 2001
Issue 11 Revision 0
COLR CODEX COM COM COMB CONNACK COMM, Comms CommsLink CONF CONFIG CP CPU C/R CR CR CRC CRE CREF CRM CRM-LS/HS
COnnected Line Identification Restriction supplementary service. Manufacturers name for a type of multiplexer and packet switch commonly installed at the Motorola OMC-R. Code Object Manager. COMplete. Combiner. CONNect ACKnowledgement. COMMunications. Communications Link. (2Mbit/s) CONFerence circuit. CONFIGuration Control Program. Call Processing. Central Processing Unit. Command/Response field bit. Carriage Return (RETURN). Connection Request (Part of SCCP network connectivity). Cyclic Redundancy Check (3 bit). Call RE-establishment procedure. Connection REFused (Part of SCCP network connectivity). Cell Resource Manager. Cellular Radio Modem-Low Speed/High Speed. Low speed modem used to interwork 300 to 2400 bit/s data services under V.22bis, V.23, or V.21 standards. High speed modem used to interwork 1200 to 9600 bit/s data services under V.22bis, V.32, or V.29/V.27ter/V.21 standards. Cathode Ray Tube (video display terminal). Code Storage Facility Processor (at BSC and BTS). Central Statistics Process. The statistics process in the BSC. Circuit Switched Public Data Network. Call Transfer supplementary service. Channel Tester. Channel Type. Call Trace Product (Tool). Common Technical Regulation. Clear to Send. Method of flow control (RS232 Interface). Compact Transceiver Unit (M-Cellhorizon radio). Closed User Group supplementary service. The total value for an entire statistical interval. Call Waiting supplementary service.
CRT CSFP CSP CSPDN CT CT CT CTP CTR CTS CTU CUG Cumulative value CW

EMOTOROLA LTD. 2001
911
Issue 11 Revision 0
D
D Interface D/A DAB DAC DACS DAN DAS DAT DataGen dB DB DB DBA DBMS dc DCB DCCH Interface between VLR and HLR. Digital to Analogue (converter). Disribution Alarm Board. Digital to Analogue Converter. Digital Access Cross-connect System. Digital ANnouncer (for recorded announcements on MSC). Data Acquisition System. Digital Audio Tape. Sysgen Builder System. A Motorola offline BSS binary object configuration tool. Decibel. A unit of power ratio measurement. DataBase. Dummy Burst (see Dummy burst). DataBase Administration/Database Administrator. DataBase Management System. Direct Current. Diversity Control Board (p/o DRCU). Dedicated Control CHannel. A class of GSM control channels used to set up calls and report measurements. Includes SDCCH, FACCH, and SACCH. Data Carrier Detect signal. Data Circuit terminating Equipment. Data Communications Function. Duplexed Combining bandpass Filter. (Used in Horizonmacro). Data Communications Network. A DCN connects Network Elements with internal mediation functions or mediation devices to the Operations Systems. DC Power Supply Module. Digital Cellular System at 1800 MHz. A cellular phone network using digital techniques similar to those used in GSM 900, but operating on frequencies of 1710 1785 MHz and 1805 1880 MHz. Dual-stage Duplexed combining Filter. (Used in Horizonmacro). DataGen Directory Structure. Data Drive Storage. Direct Digital Synthesis. Diversity Equalizer Board. DETach. Decision Feedback Equalizer. Data Gathering Tool.
DCD DCE DCF DCF DCN
DC PSM DCS1800
DDF DDS DDS DDS DEQB DET DFE DGT

912
EMOTOROLA LTD. 2001
Issue 11 Revision 0
DHP DIA DINO E1/HDSL DINO T1 DISC Discon DIQ DIR DL DLCI DLD DLNB DLSP DLSP Dm DMA DMA DMR DMX DN DNIC Downlink DP DPC
Digital Host Processor. Drum Intercept Announcer. Line termination module. Line termination module. DISConnect. Discontiuous. Diversity In phase and Quadrature phase. Device Interface Routine. Data Link (layer). Data Link Connection Identifier. Data Link Discriminator. Diversity Low Noise Block. Data Link Service Process. Digital Link Signalling Processor. Control channel (ISDN terminology applied to mobile service). Deferred Maintenance Alarm. An alarm report level; an immediate or deferred response is required (see also PMA). Direct Memory Access. Digital Mobile Radio. Distributed Electronic Mobile Exchange (Motorolas networked EMX family). Directory Number. Data network identifier. Physical link from the BTS towards the MS (BTS transmits, MS receives). Dial/Dialled Pulse. Destination Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) destination point of the message. Digital Processing and Control board. Digital Private Network Signalling System (BT standard for PABX interface). Dual Path Preselector. Dual Port Random Access Memory. Digital Power Supply Module. Dynamic Random Access Memory. Data Rate Converter board. Provides data and protocol conversion between PLMN and destination network for 8 circuits (p/o IWF). Diversity Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see RCU). Generic term for radio channel unit. May be standard RCU or diversity radio channel unit DRCU.
DPC DPNSS DPP DPR, DPRAM DPSM DRAM DRC
DRCU (D)RCU

EMOTOROLA LTD. 2001
913
Issue 11 Revision 0
DRI DRIM DRIX DRX, DRx
Digital Radio Interface. Provides encoding/decoding and encryption/decryption for radio channel (p/o BSS). Digital Radio Interface extended Memory. A DRI with extra memory. DRI Extender half size board. Fibre optic link from DRI to BCU (p/o BSS). Discontinuous reception (mechanism). A means of saving battery power (for example in hand-portable units) by periodically and automatically switching the MS receiver on and off. German term for 2 Mbit/s line (PCM interface). Data Switching Exchange. Digital Speech Interpolation. Digital Signal Processor. Digital Subscriber Signalling No 1. Diversity Signal Strength Indication. Direct Transfer Application Part (6-8). Data Terminal Equipment. Digital Trunk Frame. DaTa form 1 (Part of SCCP network connectivity). Digital Trunk Interface. Dual Tone Multi-Frequency (tone signalling type). Data Terminal Ready signal. Method of flow control (RS232 Interface). Dual Transceiver Module. (Radio used in M-Cellarena and M-Cellarena macro). Discontinuous Transmission (mechanism). A means of saving battery power (for example in hand-portable units) and reducing interference by automatically switching the transmitter off when no speech or data are to be sent. A period of carrier less than one timeslot whose modulation is a defined sequence that carries no useful information. A dummy burst fills a timeslot with an RF signal when no information is to be delivered to a channel. DYnamic NETwork. Used to specify BTSs sharing dynamic resources.
DS-2 DSE DSI DSP DSS1 DSSI DTAP DTE DTF DT1 DTI DTMF DTR DTRX DTX, DTx
Dummy burst
DYNET

914
EMOTOROLA LTD. 2001
Issue 11 Revision 0
E
E E Interface EA EAS Eb/No EBCG EC ECB ECID ECM Ec/No ECT ECT EEL EEPROM EGSM900 EI EIR EIRP EIRP EL EM EMC EMF EMI eMLPP EMMI EMU EMX en bloc See Erlang. Interface between MSC and MSC. External Alarms. External Alarm System. Energy per Bit/Noise floor. Elementary Basic Service Group. Echo Canceller. Performs echo suppression for all voice circuits. Provides echo cancelling for telephone trunks for 30 channels (EC). The Motorola European Cellular Infrastructure Division. Error Correction Mode (facsimile). Ratio of energy per modulating bit to the noise spectral density. Event Counting Tool. Explicit Call Transfer supplementary service. Electric Echo Loss. Electrically Erasable Programmable Read Only Memory. Extended GSM900. Events Interface. Part of the OMC-R GUI. Equipment Identity Register. Effective Isotropic Radiated Power. Equipment Identity Register Procedure. Echo Loss. Event Management. An OMC application. ElectroMagnetic Compatibility. Electro Motive Force. Electro Magnetic Interference. enhanced Multi-Level Precedence and Pre-emption service. Electrical Man Machine Interface. Exchange office Management Unit (p/o Horizonoffice) Electronic Mobile Exchange (Motorolas MSC family). Fr. all at once (a CCITT #7 Digital Transmission scheme); En bloc sending means that digits are sent from one system to another ~ (that is, all the digits for a given call are sent at the same time as a group). ~ sending is the opposite of overlap sending. A system using ~ sending will wait until it has collected all the digits for a given call before it attempts to send digits to the next system. All the digits are then sent as a group. End of Tape. Erasable Programmable Read Only Memory.
EOT EPROM

EMOTOROLA LTD. 2001
915
Issue 11 Revision 0
EPSM EQB EQCP EQ DSP Erlang
Enhanced Power Supply Module (+27 V). Equalizer Board. Control circuit for equalization for 8 time slots each with equalizing circuitry and a DSP (p/o RCU). Equalizer Control Processor. Equalizer Digitizer Signal Processor. International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 CCS. In the US this is also known as a traffic unit (TU). Ear Reference Point. Effective Radiated Power. ERRor. Electro-static Point. Embedded SQL (Structured Query Language). An RDBMS programming interface language. Extended TACS (analogue cellular system, extended). Type of Local Area Network. ETSI Technical Report. European Telecommunication Standard. European Telecommunications Standards Institute. End of Transmission. Executive Process.
ERP ERP ERR ESP ESQL E-TACS Ethernet ETR ETS ETSI ETX EXEC

916
EMOTOROLA LTD. 2001
Issue 11 Revision 0
F
F Interface FA FA FA FAC FACCH Interface between MSC and EIR. Fax Adaptor. Full Allocation. Functional Area. Final Assembly Code. Fast Associated Control Channel. A GSM dedicated control channel which is associated with a TCH and carries control information after a call is set up (see SDCCH). Fast Associated Control Channel/Full rate. Fast Associated Control Channel/Half rate. Frequency correction Burst (see Frequency correction burst). Fibre Channel Arbitration Loop. (Type of hard disc). Frequency Correction CHannel. A GSM broadcast control channel which carries information for frequency correction of the mobile (MS). Fault Collection Process (in BTS). Frame Check Sequence. Frequency Division Multiplex. Frequency Division Multiple Access. Fixed Dialling Number. Fault Diagnostic Procedure. Forward Error Correction. Front End Processor. Frame Erasure Ratio. For Further Study. Frequency Hopping. Forward Indicator Bit. Finite Impulse Response (filter type). Foreign Key. A database column attribute; the foreign key indicates an index into another table. Fault Management (at OMC). Frequency Modulation. Fault Management Initiated Clear. Fibre optic MUltipleXer. Frame Number. Identifies the position of a particular TDMA frame within a hyperframe. First Office Application. Fibre Optic eXtender. Full Rate. Refers to the current capacity of a data channel on the GSM air interface, that is, 8 simultaneous calls per carrier (see also HR Half Rate).
FACCH/F FACCH/H FB FC-AL FCCH
FCP FCS FDM FDMA FDN FDP FEC FEP FER FFS, FS FH FIB FIR FK FM FM FMIC FMUX FN FOA FOX FR

EMOTOROLA LTD. 2001
917
Issue 11 Revision 0
FRU Frequency correction
Field Replaceable Unit. Period of RF carrier less than one timeslot whose modulation bit stream allows frequency correction to be performed easily within an MS burst. Frequency Synchronization. Free Space Loss. The decrease in the strength of a radio signal as it travels between a transmitter and receiver. The FSL is a function of the frequency of the radio signal and the distance the radio signal has travelled from the point source. Forward Sequence Number. File Transfer, Access, and Management. An ASE which provides a means to transfer information from file to file (OMC). forwarded-to number. Fault Translation Process (in BTS). File Transfer Protocol.
FS FSL
FSN FTAM
ftn FTP FTP

918
EMOTOROLA LTD. 2001
Issue 11 Revision 0
G
G Interface Gateway MSC Interface between VLR and VLR. An MSC that provides an entry point into the GSM PLMN from another network or service. A gateway MSC is also an interrogating node for incoming PLMN calls. Gigabyte. Gigabit Interface Converter. Generic Clock board. System clock source, one per site (p/o BSS, BTS, BSC, IWF, RXCDR). Group Call Register. Generic DSP Processor board. Interchangeable with the XCDR board. GDP board configured for E1 link usage. GDP board configured for T1 link usage. Giga-Hertz (109). Group ID. A unique number used by the system to identify a users primary group. GSM Multiplexer Board (p/o BSC). GSM Manual Revision. Gateway Mobile-services Switching Centre (see Gateway MSC). Gaussian Minimum Shift Keying. The modulation technique used in GSM. GrouND. Grade of Service. GSM PLMN Area. General Protocol Converter. Generic Processor board. GSM generic processor board: a 68030 with 4 to 16 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). Generic Processor board. GSM generic processor board: a 68040 with 32 Mb RAM (p/o BSS, BTS, BSC, IWF, RXCDR). General Packet Radio Service. Global Positioning by Satellite. GSM Service Area. The area in which an MS can be reached by a fixed subscriber, without the subscribers knowledge of the location of the MS. A GSA may include the areas served by several GSM PLMNs. GSM System Area. The group of GSM PLMN areas accessible by GSM MSs. Groupe Spcial Mobile (the committee). Global System for Mobile communications (the system). GSM Mobile Station. GSM Public Land Mobile Network.
GB, Gbyte GBIC GCLK GCR GDP GDP E1 GDP T1 GHz GID GMB GMR GMSC GMSK GND GOS GPA GPC GPROC
GPROC2 GPRS GPS GSA
GSA GSM GSM GSM MS GSM PLMN

EMOTOROLA LTD. 2001
919
Issue 11 Revision 0
GSR GT GTE Guard period GUI GUI client GUI server
GSM Software Release. Global Title. Generic Table Editor. The Motorola procedure which allows users to display and edit MCDF input files. Period at the beginning and end of timeslot during which MS transmission is attenuated. Graphical User Interface. A computer used to display a GUI from an OMC-R GUI application which is beingbrun on a GUI server. A computer used to serve the OMC-R GUI application process running locally (on its processor) to other computers (Gui clients or other MMI processors). GateWaY (MSC/LR) interface to PSTN.
GWY

920
EMOTOROLA LTD. 2001
Issue 11 Revision 0
H
H Interface H-M HAD, HAP HANDO, Handover Interface between HLR and AUC. Human-Machine Terminals. HLR Authentication Distributor. HANDOver. The action of switching a call in progress from one radio channel to another radio channel. Handover allows established calls to continue by switching them to another radio resource, as when an MS moves from one BTS area to another. Handovers may take place between the following GSM entities: timeslot, RF carrier, cell, BTS, BSS and MSC. Hybrid Combining Unit. (Used in Horizonmacro). High level Data Link Control. High bit-rate Digital Subscriber Line. High Layer Compatibility. The HLC can carry information defining the higher layer characteristics of a teleservice active on the terminal. Home Location Register. The LR where the current location and all subscriber parameters of an MS are permanently stored. Heat Management System. The system that provides environmental control of the components inside the ExCell, TopCell and M-Cell cabinets. HandOver. (see HANDO above). Hand Portable Unit. Call hold supplementary service. Home PLMN. Half Rate. Refers to a type of data channel that will double the current GSM air interface capacity to 16 simultaneous calls per carrier (see also FR Full Rate). HandSet. High Speed Interface card. HLR Subscriber Management. Hopping Sequence Number. Home Units. Hardware. 2048 superframes. The longest recurrent time period of the frame structure.
HCU HDLC HDSL HLC
HLR
HMS
HO HPU HOLD HPLMN HR
HS HSI/S HSM HSN HU HW Hyperframe

EMOTOROLA LTD. 2001
921
Issue 11 Revision 0
I
I IA IA5 IADU IAM IAS IC IC IC(pref) ICB ICC ICM ICMP ID, Id IDN IDS IE IEC IEEE IEI I-ETS IF IFAM IM IMACS IMEI Information frames (RLP). Incomming Access (closed user group (CUG) SS (supplementary service)). International Alphanumeric 5. Integrated Antenna Distribution Unit. (The IADU is the equivalent of the Receive Matrix used on pre-M-Cell BTSs). Initial Address Message. Internal Alarm System. Integrated Circuit. Interlock Code (CUG SS). Interlock Code op the preferential CUG. Incoming Calls Barred. Integrated Circuit(s) Card. In-Call Modification. Internet Control Message Protocol. IDentification/IDentity/IDentifier. Integrated Digital Network. INFOMIX Database Server. (OMC-R relational database management system). Information Element (signalling). International Electrotechnical Commission. Institute of Electrical and Electronic Engineers. Information Element Identifier. Interim European Telecommunication Standard. Intermediate Frequency. Initial and Final Address Message. InterModulation. Intelligent Monitor And Control System. International Mobile station Equipment Identity. Electronic serial number that uniquely identifies the MS as a piece or assembly of equipment. The IMEI is sent by the MS along with request for service. IMMediate assignment message. International Mobile Subscriber Identity. Published mobile number (prior to ISDN) (see also MSISDN) that uniquely identifies the subscription. It can serve as a key to derive subscriber information such as directory number(s) from the HLR. Intelligent Network. Interrogating Node. A switching node that interrogates an HLR, to route a call for an MS to the visited MSC. IN Service.
IMM IMSI
IN IN INS

922
EMOTOROLA LTD. 2001
Issue 11 Revision 0
INS InterAlg Interworking
Intelligent Network Service. Interference Algorithm. A single interference algorithm in a cell. The general term used to describe the inter-operation of networks, services, supplementary services and so on. See also IWF. A recording period of time in which a statistic is pegged. The end of an interval. Input/Output. Intelligent Optimization Platform. Initialisation Process. Internet Protocol. Inter-Process Communication. INtermodulation Products. Intellectual PRoperty. Integrated Power Supply Module (48 V). (A hardware component). Indexed Sequential Access Method. International Switching Centre. Integrated Services Digital Network. An integrated services network that provides digital connections between user-network interfaces. Motorola Information Systems group (formally CODEX). International Organisation for Standardization. Informix Structured Query Language. ISDN User Part (of signalling system No. 7). Inactivity Test (Part of SCCP network connectivity). Information Transfer Capability. International Telecommunication Union. International Telecommunication Union Telecommunications Sector. InterWorking Function. A network functional entity which provides network interworking, service interworking, supplementary service interworking or signalling interworking. It may be a part of one or more logical or physical entities in a GSM PLMN. InterWorking MSC. InterWorking Unit.
Interval Interval expiry I/O IOS IP IP IPC IP, INP IPR IPSM IPX ISAM ISC ISDN
ISG ISO ISQL ISUP IT ITC ITU ITUTSS IWF
IWMSC IWU

EMOTOROLA LTD. 2001
923
Issue 11 Revision 0
K
k k K KAIO kb, kbit kbit/s, kbps kbyte Kc kHz Ki KIO KSW KSWX kW kilo (103). Windows size. Constraint length of the convolutional code. Kernal Asynchronous Input/Output. kilo-bit. kilo-bits per second. kilobyte. Ciphering key. A sequence of symbols that controls the operation of encipherment and decipherment. kilo-Hertz (103). Individual subscriber authentication Key (p/o authentication process of AUC). A class of processor. Kiloport SWitch board. TDM timeslot interchanger to connect calls (p/o BSS). KSW Expander half size board. Fibre optic distribution of TDM bus (p/o BSS). kilo-Watt.

924
EMOTOROLA LTD. 2001
Issue 11 Revision 0
L
L1 L2ML L2R Layer 1. Layer 2 Management Link. Layer 2 Relay function. A function of an MS and IWF that adapts a users known layer2 protocol LAPB onto RLP for transmission between the MT and IWF. L2R Bit Orientated Protocol. L2R Character Orientated Protocol. Layer 3. Location Area. An area in which an MS may move freely without updating the location register. An LA may comprise one or several base station areas. Location Area Code. Location Area Identity. The information indicating the location area in which a cell is located. Local Area Network. LAN Extender half size board. Fibre optic distribution of LAN to/from other cabinets (p/o BSS etc). Link Access Protocol Balanced (of ITUTSS Rec. x.25). Link Access Protocol Data. Link Access Protocol on the Dm channel. Inductor Capacitor (type of filter). Link Control Function. Local Communications Network. Link Control Processor. Local Exchange. Light Emitting Diode. Line Feed. Length Indicator. Line Identity. Lower Layer Compatibility. The LLC can carry information defining the lower layer characteristics of the terminal. Traffic channel with capacity lower than a Bm. LAN Monitor Process. Least Mean Square. Local Mobile Station Identity. A unique identity temporarily allocated to visiting mobile subscribers in order to speed up the search for subscriber data in the VLR, when the MSRN allocation is done on a per cell basis. Local Maintenance Terminal. Low Noise Amplifier. Last Number Dialled.
L2R BOP L2R COP L3 LA
LAC LAI LAN LANX LAPB LAPD LAPDm LC LCF LCN LCP LE LED LF LI LI LLC Lm LMP LMS LMSI
LMT LNA LND

EMOTOROLA LTD. 2001
925
Issue 11 Revision 0
Location area
An area in which a mobile station may move freely without updating the location register. A location area may comprise one or several base station areas. Linear Predictive Code. Local PLMN. Location Register. The GSM functional unit where MS location information is stored. The HLR and VLR are location registers. Link Stations Signalling Unit (Part of MTP transport system). Listener Side Tone Rating. Long Term Average. The value required in a BTSs GCLK frequency register to produce a 16.384 MHz clock. Local Terminal Emulator. Long Term Predictive. Line Terminating Unit. Local Units. Location Update. Length and Value.
LPC LPLMN LR
LSSU LSTR LTA LTE LTP LTU LU LU LV

926
EMOTOROLA LTD. 2001
Issue 11 Revision 0
M
M M M-Cell M&TS Mandatory. Mega (106). Motorola Cell. Maintenance and Troubleshooting. Functional area of Network Management software which (1) collects and displays alarms, (2) collects and displays Software/Hardware errors, and (3) activates test diagnostics at the NEs (OMC). Mobile Allocation. The radio frequency channels allocated to an MS for use in its frequency hopping sequence. Medium Access Control. Mobile Allocation Channel Number. A cell in which the base station antenna is generally mounted away from buildings or above rooftop level. Mobile Additional Function. Mobile Access Hunting supplementary service. Mobile Allocation Index. Mean Accumulated Intrinsic Down Time. MAINTenance. Mobile Allocation Index Offset. Mobile Application Part (of signalling system No. 7). The inter-networking signalling between MSCs and LRs and EIRs. Mobile Application Part Processor. Megabyte. Megabits per second. Motorola Cellular Advanced Processor. Mobile Country Code. Motorola Customer Data Format used by DataGen for simple data entry and retrieval. Malicious Call Identification supplementary service. Motorola Customer Support Centre. Main Control Unit for M-Cell2/6. Also referred to as the Micro Control Unit in software. Main Control Unit, with dual FMUX. (Used in M-Cellhorizon). Main Control Unit for M-Cell Micro sites (M-Cellm). Also referred to as the Micro Control Unit in software. The software subtype representation of the Field Replaceable Unit (FRU) for the MCU-m. Mediation Device. (mobile) Management (entity) - Data Link (layer). Maintenance Entity (GSM Rec. 12.00).
MA MAC MACN Macrocell MAF MAH MAI MAIDT MAINT MAIO MAP MAPP MB, Mbyte Mbit/s MCAP MCC MCDF MCI MCSC MCU MCUF MCU-m MCUm MD MDL ME

EMOTOROLA LTD. 2001
927
Issue 11 Revision 0
ME
Mobile Equipment. Equipment intended to access a set of GSM PLMN and/or DCS telecommunication services, but which does not contain subscriber related information. Services may be accessed while the equipment, capable of surface movement within the GSM system area, is in motion or during halts at unspecified points. Maintenance Entity Function (GSM Rec. 12.00). MultiFrame. Multi-Frequency (tone signalling type). MultiFunction block. Management. Manager. Message Handling System. Mobile Handling Service. Mega-Hertz (106). Maintenance Information. Management Information Base. A Motorola OMC-R database. There is a CM MIB and an EM MIB. Mobile Interface Controller. A cell in which the base station antenna is generally mounted below rooftop level. Radio wave propagation is by diffraction and scattering around buildings, the main propagation is within street canyons. minute(s). micro-second (106). Micro Base Control Unit. Management Information Tree. Name of a file on the Motorola OMC-R. Man Machine. Mobility Management. Mobile Management Entity. Middle Man Funnel process. Man Machine Interface. The method in which the user interfaces with the software to request a function or change parameters. A machine configured to use the OMC-R software from an MMI server. MMI client/MMI server. A computer which has its own local copy of the OMC-R software. It can run the OMC-R software for MMI clients to mount. Man Machine Language. The tool of MMI. Multiple Serial Interface Link. (see also 2Mbit/s link) Mobile Network Code. MaiNTenance.
MEF MF MF MF MGMT, mgmt MGR MHS MHS MHz MI MIB MIC Microcell
min ms mBCU MIT MM MM MME MMF MMI
MMI client MMI processor MMI server
MML MMS MNC MNT

928
EMOTOROLA LTD. 2001
Issue 11 Revision 0
MO MO/PP MOMAP MoU MPC MPH MPTY MPX MRC MRN MRP MS MSC MSCM MSCU msec MSI MSIN MSISDN
Mobile Originated. Mobile Originated Point-to-Point messages. Motorola OMAP. Memorandum of Understanding. Multi Personal Computer (was p/o OMC). (mobile) Management (entity) - PHysical (layer) [primitive]. MultiParTY (Multi ParTY) supplementary service. MultiPleXed. Micro Radio Control Unit. Mobile Roaming Number. Mouth Reference Point. Mobile Station. The GSM subscriber unit. Mobile-services Switching Centre, Mobile Switching Centre. Mobile Station Class Mark. Mobile Station Control Unit. millisecond (.001 second). Multiple Serial Interface board. Intelligent interface to two 2 Mbit/s digital links (see 2 Mbit/s link and DS-2) (p/o BSS). Mobile Station Identification Number. Mobile Station International ISDN Number. Published mobile number (see also IMSI). Uniquely defines the mobile station as an ISDN terminal. It consists of three parts: the Country Code (CC), the National Destination Code (NDC) and the Subscriber Number (SN). Mobile Station Roaming Number. A number assigned by the MSC to service and track a visiting subscriber. Message Signal Unit (Part of MTP transport system). A signal unit containing a service information octet and a signalling information field which is retransmitted by the signalling link control, if it is received in error. Mobile Terminated. Describes a call or short message destined for an MS. Mobile Termination. The part of the MS which terminates the radio transmission to and from the network and adapts terminal equipment (TE) capabilities to those of the radio transmission. MT0 is mobile termination with no support for terminal, MT1 is mobile termination with support for an S-type interface and MT2 is mobile termination with support for an R-type interface. Mobile-To-Mobile (call). Message Transfer Part. Mobile Terminated Point-to-Point messages. Mean Time Between Failures. Message Transfer LinK. MTP Transport Layer Link (A interface).
MSRN MSU
MT MT (0, 1, 2)
MTM MTP MT/PP MTBF MTK MTL

EMOTOROLA LTD. 2001
929
Issue 11 Revision 0
MTP MTTR Multiframe
Message Transfer Part. Mean Time To Repair. Two types of multiframe are defined in the system: a 26-frame multiframe with a period of 120 ms and a 51-frame multiframe with a period of 3060/13 ms. Mark Up. Multi User Mobile Station. Multiplexer.
MU MUMS MUX

930
EMOTOROLA LTD. 2001
Issue 11 Revision 0
N
N/W NB NBIN NCC NCELL NCH ND Network. Normal Burst (see Normal burst). A parameter in the hoping sequence. Network (PLMN) Colour Code. Neighbouring (of current serving) Cell. Notification CHannel. No Duplicates. A database column attribute meaning the column contains unique values (used only with indexed columns). National Destination Code. Network Determined User Busy. Network Element (Network Entity). Network Element Function block. Norme Europennes de Telecommunications. Frequency planning tool. Network Function. Network File System. Network Health Analyst. Optional OMC-R processor feature. Network Interface Card. Network Independent Clocking. Network Information Service. It allows centralised control of network information for example hostnames, IP addresses and passwords. Network Interface Unit. Network Interface Unit, micro. Network LinK processor(s). Newton metres. Network Management (manager). NM is all activities which control, monitor and record the use and the performance of resources of a telecommunications network in order to provide telecommunication services to customers/users at a certain level of quality. Network Management Application Service Element. Network Management Centre. The NMC node of the GSM TMN provides global and centralised GSM PLMN monitoring and control, by being at the top of the TMN hierarchy and linked to subordinate OMC nodes. National Mobile Station Identification number. Nordic Mobile Telephone system. No Nulls. A database column attribute meaning the column must contain a value in all rows. A period of modulated carrier less than a timeslot. Number Plan Identifier.
NDC NDUB NE NEF NET NETPlan NF NFS NHA NIC NIC NIS
NIU NIU-m NLK Nm NM
NMASE NMC
NMSI NMT NN Normal burst NPI

EMOTOROLA LTD. 2001
931
Issue 11 Revision 0
NRZ NSAP NSP NSS NT NT NTAAB NUA NUI NUP NV NVRAM nW
Non Return to Zero. Network Service Access Point. Network Service Provider. Network Status Summary. Network Termination. Non Transparent. New Type Approval Advisory Board. Network User Access. Network User Identification. National User Part (of signalling system No. 7). NonVolatile. Non-Volatile Random Access Memory. Nano-Watt (109).

932
EMOTOROLA LTD. 2001
Issue 11 Revision 0
O
O OA O&M OASCU Optional. Outgoing Access (CUG SS). Operations and Maintenance. Off-Air-Call-Set-Up. The procedure in which a telecommunication connection is being established whilst the RF link between the MS and the BTS is not occupied. Outgoing Calls Barred within the CUG. Oversized Voltage Controlled Crystal Oscillator. Optional for operators to implement for their aim. % OverFlow. IDS shutdown state. IDS normal operatng state. Operator Initiated Clear. Off_Line MIB. A Motorola DataGen database, used to modify and carry out Radio Frequency planning on multiple BSS binary files. Overall Loudness Rating. Operations and Maintenance Application Part (of signalling system No. 7) (was OAMP). Operations and Maintenance Centre. The OMC node of the GSM TMN provides dynamic O&M monitoring and control of the PLMN nodes operating in the geographical area controlled by the specific OMC. Operations and Maintenance Centre Gateway Part. (Iridium) Operations and Maintenance Centre GPRS Part. Operations and Maintenance Centre Radio Part. Operations and Maintenance Centre Switch Part. Operations and Maintenance Function (at BSC). Operations and Maintenance Link. Operation and Maintenance Processor. Operation and Maintenance System (BSCOMC). Operation and Maintenance SubSystem. Out Of Service. Originating Point Code. A part of the label in a signalling message that uniquely identifies, in a signalling network, the (signalling) origination point of the message. Olympus Radio Architecture Chipset. Operating System. Open Systems Interconnection. OSI Reference Model. Operation Systems Function block.
OCB OCXO OD OFL offline online OIC OLM
OLR OMAP OMC
OMC-G OMC-G OMC-R OMC-S OMF OML OMP OMS OMSS OOS OPC
ORAC OS OSI OSI RM OSF

EMOTOROLA LTD. 2001
933
Issue 11 Revision 0
OSF/MOTIF OSS Overlap
Open Software Foundation Motif. The basis of the GUI used for the Motorola OMC-R MMI. Operator Services System. Overlap sending means that digits are sent from one system to another as soon as they are received by the sending system. A system using ~ will not wait until it has received all digits of a call before it starts to send the digits to the next system. This is the opposite of en bloc sending where all digits for a given call are sent at one time.

934
EMOTOROLA LTD. 2001
Issue 11 Revision 0
P
PA PAB PABX PAD Paging Power Amplifier. Power Alarm Board. Private Automatic Branch eXchange. Packet Assembler/Disassembler facility. The procedure by which a GSM PLMN fixed infrastructure attempts to reach an MS within its location area, before any other network-initiated procedure can take place. CEPT 2 Mbit/s route through the BSS network. Processor Bus. Private Branch eXchange. Personal Computer. Paging CHannel. A GSM common control channel used to send paging messages to the MSs. Paging Channel Network. Physical Channel. Pulse Code Modulation (see also 2 Mbit/s link which is the physical bearer of PCM). Personal Communications Network. Preventative Cyclic Retransmission. A form of error correction suitable for use on links with long transmission delays, such as satellite links. Packet Control Unit (p/o GPRS). Picocell Control unit (p/o M-Cellaccess). Potential difference. Protocol Discriminator. Public Data. Power Distribution Board. Power Distribution Frame (MSC/LR). Public Data Networks. Power Distribution Unit. Protected Data Unit. Pan European Digital Cellular. A single incremental action modifying the value of a statistic. Modifying a statistical value. Packet Handler. PHysical (layer). Packet Handler Interface. Presentation Indicator. A cell site where the base station antenna is mounted within a building. Protocol Implementation Conformance Statement.
PATH PBUS PBX PC PCH PCHN PCHN PCM PCN PCR
PCU PCU pd PD PD PDB PDF PDN PDU PDU PEDC Peg Pegging PH PH PHI PI Picocell PICS

EMOTOROLA LTD. 2001
935
Issue 11 Revision 0
PID PIM PIN PIN PIX PIXT PK Plaintext PlaNET PLL PLMN PM PM-UI PMA PMS PMUX PN PNE POI POTS p/o pp, p-p PP ppb PPE ppm Pref CUG Primary Cell
Process IDentifier/Process ID. PCM Interface Module (MSC). Personal Identification Number. Problem Identification Number. Parallel Interface Extender half size board. Customer alarm interface (p/o BSS). Protocol Implementation eXtra information for Testing. Primary Key. A database column attribute, the primary key is a not-null, non-duplicate index. Unciphered data. Frequency planning tool. Phase Lock Loop (refers to phase locking the GCLK in the BTS). Public Land Mobile Network. The mobile communications network. Performance Management. An OMC application. Performance Management User Interface. Prompt Maintenance Alarm. An alarm report level; immediate action is necessary (see also DMA). Pseudo MMS. PCM MUltipleXer. Permanent Nucleus (of GSM). Prsentation des Normes Europennes. Point of Interconnection (with PSTN). Plain Old Telephone Service (basic telephone services). Part of. Peak-to-peak. Point-to-Point. Parts per billion. Primative Procedure Entity. Parts per million (x 106). Preferential CUG. A cell which is already optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The primary cell has a preferred band equal to the frequency type of the coincident cell. Programmable Read Only Memory. Location probability. Periodic Supervision of Accessability. Presentation Services Access Point. Power Supply Module.
PROM Ps PSA PSAP PSM

936
EMOTOROLA LTD. 2001
Issue 11 Revision 0
PSPDN
Packet Switched Public Data Network. Public data communications network. x.25 links required for NE to OMC communications will probably be carried by PSPDN. Public Switched Telephone Network. The UK land line telephone network. Power Supply Unit. Pure Sine Wave. Public Telecommunications Operator. Price per Unit Currency Table. Permanent Virtual Circuit. Pass Word. Power. Private eXchange Public Data Network.
PSTN PSU PSW PTO PUCT PVC PW PWR PXPDN

EMOTOROLA LTD. 2001
937
Issue 11 Revision 0
Q
QA Q3 Q-adapter QAF QEI QIC QOS Quiescent mode Q (Interface) Adapter. Interface between NMC and GSM network. Used to connect MEs and SEs to TMN (GSM Rec. 12.00). Q-Adapter Function. Quad European Interface. Interfaces four 2 Mbit/s circuits to TDM switch highway (see MSI). Quarter Inch Cartridge (Data storage format). Quality Of Service. IDS intermediate state before shutdown.

938
EMOTOROLA LTD. 2001
Issue 11 Revision 0
R
R Value of reduction of the MS transmitted RF power relative to the maximum allowed output power of the highest power class of MS (A). RAndom mode request information field. Random Access Burst. Random Access Control CHannel. A GSM common control channel used to originate a call or respond to a page. Random Access CHannel. Random Access Memory. RANDom number (used for authentication). Receive Antenna Transceiver Interface. Rate Adaptation. Remote BSS Diagnostic System (a discontinued Motorola diagnostic facility). Residual Bit Error Ratio. Remote Base Transceiver Station. Radio Control Board (p/o DRCU). Radio Channel Identifier. Radio Control Processor. Radio Channel Unit. Contains transceiver, digital control circuits, and power supply (p/o BSS) (see DRCU). Receiver. Relational DataBase Management System (INFORMIX). Radio Digital Interface System. Restricted Digital Information. Reference Distribution Module. Relative Distinguished Name. A series of RDN form a unique identifier, the distinguished name, for a particular network element. RECommendation. REJect(ion). RELease. Residual Excited Linear Predictive. RELP Long Term Prediction. A name for GSM full rate (see full rate). Resynchronize/resynchronization. REQuest. A Motorola DataGen utility for producing an MMI script from a binary object database. Radio Frequency.
RA RAB RACCH RACH RAM RAND RATI RAx RBDS RBER RBTS RCB RCI RCP RCU RCVR RDBMS RDI RDIS RDM RDN
REC, Rec REJ REL RELP RELP-LTP resync REQ Revgen RF

EMOTOROLA LTD. 2001
939
Issue 11 Revision 0
RFC, RFCH
Radio Frequency Channel. A partition of the system RF spectrum allocation with a defined bandwidth and centre frequency. Receiver Front End (shelf). Receiver Front End Board (p/o DRCU II). Radio Frequency Interference. Radio Frequency Module. Reduced TDMA Frame Number. Reserved for Future Use. Network cable/Connector type. Reduced Instruction Set Computer. Remote login. Release Complete. Radio Link Protocol. An ARQ protocol used to transfer user data between an MT and IWF. See GSM 04.22. Receiver Loudness Rating. ReLeaSeD. Root Mean Square (value). Remote Mobile Switching Unit. Table of 128 integers in the hopping sequence. Read Only Memory. Remote Operations Service Element. An ASE which carries a message between devices over an association established by ASCE (a CCITT specification for O & M) (OMC). Time period between transmit and receive instant of a timeslot in the BTS, propagation determined by the response behaviour of the MS and the MS to BTS delay distance. Regular Pulse Excited. Regular Pulse Excitation - Long Term Prediction. The GSM digital speech coding scheme. Recognised Private Operating Agency. Read Privilege Required. Access to the column is allowed only for privileged accounts. Radio Resource management. Receive Ready (frame). Radio Resource State Machine. Standard serial interface. Radio System Entity. Radio Signalling Link. Radio System Link Function. Radio System Link Processor. Radio SubSystem (replaced by BSS). Received Signal Strength Indicator.
RFE RFEB RFI RFM RFN RFU RJ45 RISC RL RLC RLP RLR RLSD RMS RMSU RNTABLE ROM ROSE
Roundtrip
RPE RPE-LTP RPOA RPR RR RR RRSM RS232 RSE RSL RSLF RSLP RSS RSSI

940
EMOTOROLA LTD. 2001
Issue 11 Revision 0
RSZI RTC RTE RTF RTF RTS RU Run level Rx RXCDR RXF RXLEV-D RXLEV-U RXQUAL-D RXQUAL-U RXU
Regional Subscription Zone Identity. Remotely Tuneable Channel Combiner. Remote Terminal Emulator. Radio Transceiver Function. Receive Transmit Functions. Request to Send. Method of flow control (RS232 Interface). Rack Unit. System processor operating mode. Receive(r). Remote Transcoder. Receive Function (of the RTF). Received signal level downlink. Received signal level uplink. Received signal quality downlink. Received signal quality uplink. Remote Transcoder Unit. The shelf which houses the remote transcoder modules in a BSSC cabinet at a remote transcoder site.

EMOTOROLA LTD. 2001
941
Issue 11 Revision 0
S
S/W SABM SABME SACCH SoftWare. Set Asynchronous Balanced Mode. A message which establishes the signalling link over the air interface. SABM Extended. Slow Associated Control CHannel. A GSM control channel used by the MS for reporting RSSI and signal quality measurements. Slow Associated Control CHannel/SDCCH/4. Slow Associated Control CHannel/SDCCH/8. Slow Associated Control CHannel/Traffic channel. Slow Associated Control CHannel/Traffic channel Full rate. Slow Associated Control CHannel/Traffic channel Half rate. A brand of trunk test equipment. Service Access Point. In the reference model for OSI, SAPs of a layer are defined as gates through which services are offered to an adjacent higher layer. System Audits Process. Service Access Point Indicator (identifier). Surface Acoustic Wave. Synchronization Burst (see Synchronization burst). Serial Bus. Service Centre (used for Short Message Service). Service Code. System Change Control Administration. Software module which allows full or partial software download to the NE (OMC). Signalling Connection Control Part (6-8). Speech Coding Experts Group (of GSM). Synchronization CHannel. A GSM broadcast control channel used to carry information for frame synchronization of MSs and identification of base stations. Status Control Interface. Serial Communication Interface Processor. Status Control Manager. Sub-Channel Number. One of the parameters defining a particular physical channel in a BS. Service Control Point (an intelligent network entity). Small Computer Systems Interface. Slim Channel Unit. Slim Channel Unit for GSM900. Stand-alone Dedicated Control CHannel. A GSM control channel where the majority of call setup occurs. Used for MS to BTS communications before MS assigned to TCH.
SACCH/C4 SACCH/C8 SACCH/T SACCH/TF SACCH/TH SAGE SAP
SAP SAPI SAW SB SBUS SC SC SCCA
SCCP SCEG SCH
SCI SCIP SCM SCN SCP SCSI SCU SCU900 SDCCH

942
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SDL SDT SDU SDR SE Secondary Cell
Specification Description Language. SDL Developement Tool. Service Data Unit. Special Drawing Rights (an international basket currency for billing). Support Entity (GSM Rec. 12.00). A cell which is not optimized in the network and has a co-located neighbour whose cell boundary follows the boundary of the said cell. The secondary cell has a preferred band the same as that of its own frequency type. Support Entity Function (GSM Rec.12.00). Slow Frequency Hopping. Screening Indicator. Service Interworking. Supplementary Information. Supplementary Information A. Silence Descriptor. Signal Information Field. The bits of a message signal unit that carry information for a certain user transaction; the SIF always contains a label. Subscriber Identity Module. Removable module which is inserted into a mobile equipment; it is considered as part of the MS. It contains security related information (IMSI, Ki, PIN), other subscriber related information and the algorithms A3 and A8. Single Inline Memory module. System Integrated Memory Module. Service Information Octet. Eight bits contained in a message signal unit, comprising the service indicator and sub-service field. BSC, BTS or collocated BSC-BTS site. Serial Interface eXtender. Converts interface levels to TTL levels. Used to extend 2 serial ports from GPROC to external devices (RS232, RS422, and fibre optics). Secondary Key. A database column attribute, the secondary key indicates an additional index and/or usage as a composite key. Signalling Link. Serial Link. Send Loudness Rating. Signalling Link Test Message. Switch Manager. Summing Manager. System Management Application Entity (CCITT Q795, ISO 9596). Short Message Cell Broadcast.
SEF SFH SI SI SI SIA SID SIF
SIM
SIMM SIMM SIO
SITE SIX
SK
SL SLNK SLR SLTM SM SM SMAE SMCB

EMOTOROLA LTD. 2001
943
Issue 11 Revision 0
SME SMG SMP SMS SMSCB SMS-SC SMS/PP Smt SN SND SNDR SNR SOA SP
Short Message Entity. Special Mobile Group. Motorola Software Maintenance Program. Short Message Service. Short Message Service Cell Broadcast. Short Message Service - Service Centre. Short Message Service/Point-to-Point. Short message terminal. Subscriber Number. SeND. SeNDeR. Serial NumbeR. Suppress Outgoing Access (CUG SS). Service Provider. The organisation through which the subscriber obtains GSM telecommunications services. This may be a network operator or possibly a separate body. Signalling Point. Special Product. SPare. Signalling Point Code. Suppress Preferential CUG. Signalling Point Inaccessible. Single Path Preselector. Signal Quality Error. Structured Query Language. Service Request Distributor. Signed RESponse (authentication). Supplementary Service. A modification of, or a supplement to, a basic telecommunication service. System Simulator. SCCP messages, Subsystem-allowed (see CCITT Q.712 para 1.15). Site System Audits Processor. Supplementary Service Control string. Subservice Field. The level 3 field containing the network indicator and two spare bits. Signalling State Machine. SubSystem Number. Service Switching Point (an intelligent network element). SCCP messages, Subsystem-prohibited (see CCITT Q.712 para 1.18). SubSystem Prohibited message.
SP SP SP SPC SPC SPI SPP SQE SQL SRD SRES SS SS SSA SSAP SSC SSF SSM SSN SSP SSP SSP

944
EMOTOROLA LTD. 2001
Issue 11 Revision 0
SSS SS7 STAN STAT stats STC STMR SUERM STP Superframe Super user SURF SVC SVM SVN SW SWFM sync Synchronization burst
Switching SubSystem (comprising the MSC and the LRs). ANSI Signalling System No. 7 (alias C7). Statistical ANalysis (processor). STATistics. Statistics. System Timing Controller. Side Tone Masking rating. Signal Unit Error Rate Monitor. Signalling Transfer Point. 51 traffic/associated control multiframes or 26 broadcast/common control multiframes (period 6.12s). User account that can access all files, regardless of protection settings, and control all user accounts. Sectorized Universal Receiver Front-end (Used in Horizonmacro). Switch Virtual Circuit. SerVice Manager. Software Version Number. Software. SoftWare Fault Management. synchronize/synchronization. Period of RF carrier less than one timeslot whose modulation bit stream carries information for the MS to synchronize its frame to that of the received signal. SYStem. SYStem GENeration. The Motorola procedure for loading a configuration database into a BTS.
SYS SYSGEN

EMOTOROLA LTD. 2001
945
Issue 11 Revision 0
T
T T T T43 Timer. Transparent. Type only. Type 43 Interconnect Board. Provides interface to 12 unbalanced (6-pair) 75 ohm (T43 coax connectors) lines for 2 Mbit/s circuits (See BIB). Terminal Adaptor. A physical entity in the MS providing terminal adaptation functions (see GSM 04.02). Timing Advance. Type Approval Code. Total Access Communications System (European analogue cellular system). Terminal Adaptation Function. Transmit Antenna Transceiver Interface. The TATI consists of RF combining equipments, either Hybrid or Cavity Combining. (See CCB). Transparent Asynchronous Transmitter/Receiver Interface (physical layer). To Be Determined. Technical Basis for Regulation. TDM Bus. Transaction Capabilities. Transaction Capabilities Application Part (of Signalling System No. 7). TATI Control Board. Traffic CHannel. GSM logical channels which carry either encoded speech or user data. A full rate TCH. A full rate TCH at 2.4 kbit/s. A full rate TCH at 4.8 kbit/s. A full rate TCH at 9.6 kbit/s. A full rate Speech TCH. A half rate TCH. A half rate TCH at 2.4 kbit/s. A half rate TCH at 4.8 kbit/s. A half rate Speech TCH). Transceiver Control Interface. Transmission Control Protocol/Internet Protocol. Technical Commitee Technical Report. Transceiver Control Unit. Twin Duplexed Filter. (Used in M-Cellhorizon). Time Division Multiplexing.
TA TA TAC TACS TAF TATI
TAXI TBD TBR TBUS TC TCAP TCB TCH TCH/F TCH/F2.4 TCH/F4.8 TCH/F9.6 TCH/FS TCH/H TCH/H2.4 TCH/H4.8 TCH/HS TCI TCP/IP TC-TR TCU TDF TDM

946
EMOTOROLA LTD. 2001
Issue 11 Revision 0
TDMA TDU TE
Time Division Multiple Access. TopCell Digital Unit. Terminal Equipment. Equipment that provides the functions necessary for the operation of the access protocols by the user. Terminal endpoint identifier. Terminal Equipment Identity. TEMPorary. TEST control processor. TransFer Allowed. TransFer Prohibited. Trivial File Transfer Protocol. Transaction Identifier. The multiplex subdivision in which voice and signalling bits are sent over the air. Each RF carrier is divided into 8 timeslots. A signal sent by the BTS to the MS. It enables the MS to advance the timing of its transmission to the BTS so as to compensate for propagation delay. Type, Length and Value. Traffic Manager. TDM Modem Interface board. Provides analogue interface from IWF to modems for 16 circuits (p/o IWF). Traffic Metering and Measuring. Telecommunications Management Network. The implementation of the Network Management functionality required for the PLMN is in terms of physical entities which together constitute the TMN. Temporary Mobile Subscriber Identity. A unique identity temporarily allocated by the MSC to a visiting mobile subscriber to process a call. May be changed between calls and even during a call, to preserve subscriber confidentiality. Timeslot Number. Type Of Number. Channels which carry users speech or data (see also TCH). Equivalent to an erlang. Sequence of modulating bits employed to facilitate timing recovery and channel equalization in the receiver. Transcoder Rate Adaption Unit. TopCell Radio unit. Transceiver(s). A network component which can serve full duplex communication on 8 full-rate traffic channels according to specification GSM 05.02. If Slow Frequency Hopping (SFH) is not used, then the TRX serves the communication on one RF carrier. Technical Specification.
Tei TEI TEMP TEST TFA TFP TFTP TI Timeslot
Timing advance
TLV TM TMI TMM TMN
TMSI
TN TON Traffic channels Traffic unit Training sequence TRAU TRU TRX
TS

EMOTOROLA LTD. 2001
947
Issue 11 Revision 0
TS TS TSA TSA TSDA TSC TSI TSDI TSM TSW TTCN TTL TTY TU TUP TV Tx TXF TXPWR
TeleService. TimeSlot (see Timeslot). TimeSlot Acquisition. TimeSlot Assignment. Transceiver Speech & Data Interface. Training Sequence Code. TimeSlot Interchange. Transceiver Speech and Data Interface. Transceiver Station Manager. Timeslot SWitch. Tree and Tabular Combined Notation. Transistor to Transistor Logic. TeleTYpe (refers to any terminal). Traffic Unit. Telephone User Part (SS7). Type and Value. Transmit(ter). Transmit Function (of the RTF). Transmit PoWeR. Tx power level in the MS_TXPWR_REQUEST and MS_TXPWR_CONF parameters. Transmit Bandpass Filter.
TxBPF

948
EMOTOROLA LTD. 2001
Issue 11 Revision 0
U
UA Unnumbered Acknowledgment. A message sent from the MS to the BSS to acknowledge release of radio resources when a call is being cleared. Unrestricted Digital Information. User Datagram Protocol. User Determined User Busy. Ultra High Frequency. Unnumbered Information (Frame). Union International des Chemins de Fer. User ID. Unique number used by the system to identify the user. Upload (of software or database from an NE to a BSS). Air interface. Universal Mobile Telecommunication System. Uniform PCM Interface (13 bit). Up to Date. Physical link from the MS towards the BTS (MS transmits, BTS receives). Uninterruptable Power Supply. User Part Unavailable. That part of the burst used by the demodulator; differs from the full burst because of the bit shift of the I and Q parts of the GMSK signal. Unstructured Supplementary Service Data. User-to-User Signalling supplementary service.
UDI UDP UDUB UHF UI UIC UID UL Um UMTS UPCMI UPD Uplink UPS UPU Useful part of burst
USSD UUS

EMOTOROLA LTD. 2001
949
Issue 11 Revision 0
V
V VA VAD VAP VBS VC VCO VCXO VDU VGCS VLR Value only. Viterbi Algorithm (used in channel equalizers). Voice Activity Detection. A process used to identify presence or absence of speech data bits. VAD is used with DTX. Videotex Access Point. Voice Broadcast Service. Virtual Circuit. Voltage Controlled Oscillator. Voltage Controlled Crystal Oscillator. Visual Display Unit. Voice Group Call Service. Visitor Location Register. A GSM network element which provides a temporary register for subscriber information for a visiting subscriber. Often a part of the MSC. Very Large Scale Integration (in ICs). Visited MSC. (Recommendation not to be used). Voice Operated Transmission. Visited PLMN. Videotex Service Centre. Send state variable. Vehicular Speaker Phone. Voltage Standing Wave Ratio. The components dedecated to Videotex service.
VLSI VMSC VOX VPLMN VSC V(SD) VSP VSWR VTX host

950
EMOTOROLA LTD. 2001
Issue 11 Revision 0
W
WAN WPA WS Wide Area Network. Wrong Password Attempts (counter). Work Station. The remote device via which O&M personnel execute input and output transactions for network management purposes. Work Station Function block. World Wide Web.
WSF WWW

EMOTOROLA LTD. 2001
951
Issue 11 Revision 0
X
X.25 X.25 link XBL XCB XCDR XCDR board CCITT specification and protocols for public packet-switched networks (see PSPDN). A communications link which conforms to X.25 specifications and uses X.25 protocol (NE to OMC links). Transcoder to BSS Link. The carrier communications link between the Transcoder (XCDR) and the BSS. Transceiver Control Board (p/o Transceiver). Full-rate Transcoder. Provides speech transcoding and 4:1 submultiplexing (p/o BSS, BSC or XCDR). The circuit board required to perform speech transcoding at the BSS or (R)XCDR). Also known as the MSI (XCDR) board. Interchangeable with the GDP board. Transfer. eXchange IDentifier. X terminal window.
XFER XID X-Term

952
EMOTOROLA LTD. 2001
Issue 11 Revision 0
Z
ZC Zone Code

EMOTOROLA LTD. 2001
953
Issue 11 Revision 0

954
EMOTOROLA LTD. 2001
Answers

EMOTOROLA LTD. 2001
Issue 11 Revision 0

ii
EMOTOROLA LTD. 2001
ISSUE 10 REVISION 1
Call Establishment Exercise Answers
EMOTOROLA LTD. 2000
NET03: BSS Subsystem Performance FOR TRAINING PURPOSES ONLY
App B ii
The interprocess messages shown below have resulted in an MS being able to establish on a TCH. Insert the incremented statistics at the appropriate software process at each stage of the establishment.
L1
channel request
ABIS
RRSM
CRM
SM
SSM
MSC
OK_ACC_PROC_SUC_RACH ACCESS_PER_RACH channel request channel required MS_ACCESS_BY_TYPE CHAN_REQ_CAUSE_ATMPT channel required received channel assigned 4 SDCCH's are available
NET03: BSS Subsystem Performance
ALLOC_SDCCH BUSY_SDCCH
RSS
channel activation channel activation acknowledge
immediate assignment immediate assignment L2 SABM
ACCESS_PER_AGCH establish indiction OK_ACC_PROC [CM_SERV_CALL]
CM service request
<CR> Complete L3 information CONN_REQ_TO_MSC CC
ISSUE 10 REVISION 1
EMOTOROLA LTD. 2000
CALL SET UP MESSAGES

initiate assignment assignment resource request 3 TCHs available assignment request MA_REQ_FROM_MSC
NET03: BSS Subsystem Performance
TCH_USAGE channel assigned ACTIVATION assignment channel command MA_CMD_TO MS assignment complete assignment successful conneciton required conneciton response assignment complete Call Establishment Exercise Answers BUSY_TCH ALLOC_TCH

Net 03

Uploaded by

Document Information

Original Description:

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

Net 03

Uploaded by

Copyright:

Available Formats

CHAPTER 1

BSS Subsystem Planning

Issue 11 Revision 0 Training Manual

FOR TRAINING PURPOSES ONLY

BSS Subsystem Planning

Issue 11 Revision 0 FOR TRAINING PURPOSES ONLY

Positin mark for TED spine

Training Manual Issue 11 Revision 0 NET03 Training Manual

BSS Subsystem Planning

NET03 BSS Subsystem Planning

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Copyrights, notices and trademarks

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Chapter 2 Statistical Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

28 28 210 210 212 214 216 218 220 222 224

Chapter 3 Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4 Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Chapter 5 Handover Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Chapter 6 Statistical MMI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 7 Key Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Chapter 8 Network Health Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App A i Appendix B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B i

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Glossary of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos i

C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glos vii D ......................................................................... Glos x

Call Establishment Exercise Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . App B i

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

About this manual

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Special key sequences

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

First aid in case of electric shock

First aid in case of electric shock

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

Reporting safety issues

Reporting safety issues

NET03: BSS Subsystem Planning

FOR TRAINING PURPOSES ONLY

EMOTOROLA LTD. 2001

Warnings and cautions

Warnings and cautions

Statistical information a health check" for the network